Ver 3.4 FD005693

PROPRIETARY INFORMATION
INTERNAL USE ONLY
Network Systems Division

5200 Paramount Pkwy
Morrisville, NC 27560
Voice: 919-460-5500
THIS DOCUMENT AND THE DATA DISCLOSED HEREIN OR HEREWITH IS PROPRIETARY AND IS NOT TO BE
REPRODUCED, USED OR DISCLOSED IN WHOLE OR IN PART TO ANYONE WITHOUT THE WRITTEN PERMISSION
OF TEKELEC. COPYRIGHT TEKELEC 1999-2008. ALL RIGHTS RESERVED.
Title:
Prepaid IDP Query Relay Feature Description
Doc
Number:
341058866.doc
Revision No:
3.4
<EAGLE>
Feature Description
Prepaid IDP Query Relay

<57095, 122188>
REVIEW TYPE: Desk Review, Working Session or Peer Review
DATE:
TIME:
LOCATION:
MODERATOR:
QUORUM MEMBERS
MEMBER (Representative or Delegate)
Documentation
Product Management
CS-FOA
Product Verification
Software
System Engineering
Quality
REVIEWERS
REVIEWER (Representative or Delegate)
Hardware
Manufacturing
Project Management
CS - NPT
CS SW Operations
Platform
<Product Release Team>
COPY ONLY:
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 1 of 68
INTERNAL USE ONLY
CHANGE HISTORY
Date
Revision No.
Author
Revision Description
Approved
7/15/05
1.0
New document
No
8/22/05
8/23/05
8/25/05
2/19/07
1.2
1.3
2.0
2.1..2.3
(Obsolete)
Updates from internal review.

Updates from internal review.
Updates from Formal review.
Additional requirements from field, for PR 115300:
IDP Relay TCAP CDPN/CGPN Prefix Action
No
No
Yes
Yes
4/23/07
Updates based on PV test issues
Yes
10/25/07
2.4, 2.5
(Obsolete)
3.0
D.Agarwal
B.Hayden
D.Agarwal
D.Agarwal
D.Agarwal
D.Agarwal
V.Hamrick
W.Ferguson
W.Ferguson
Updates for PR 122188: Flexible Prepaid IDP

Query Relay
No
12/05/2007
3.1
Updates as per review comments and NPP FD
No
12/17/2007
3.2
Updated the document based on review

comments and NPP FD changes.
No
12/26/2007
3.2
Suku Pandiyattu
Rakhi Verma
Suku Pandiyattu
Rakhi Verma
Suku Pandiyattu
Rakhi Verma
Suku Pandiyattu
Checked in the approved document
Yes
1/28/2008
2/1/2008
3.3
3.4
Suku Pandiyattu
Suku Pandiyattu
Updates for the tst-msg commands

Checked in the approved version
No
Yes
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 2 of 68
INTERNAL USE ONLY
TABLE OF CONTENTS
1.0
INTRODUCTION.............................................................................................................................................................5
1.1
Purpose and Scope...............................................................................................................................................5
1.2
References............................................................................................................................................................5
1.3
Acronyms and Terminology.................................................................................................................................6
1.4
Problem/Need.......................................................................................................................................................7
1.5
Suggested Solution...............................................................................................................................................7
1.6
Obsolescence........................................................................................................................................................8
2.0
GENERAL DESCRIPTION..............................................................................................................................................8
2.1
Message Flow for IDP Relay feature...................................................................................................................9
2.2
Common Screening List (CSL)..........................................................................................................................13
2.3
Service Key (SK) parameter and BCSM Parameter..........................................................................................13
2.4
SRVSEL Command for IDP Relay....................................................................................................................13
2.5
REPT-STAT-SCCP.............................................................................................................................................13
2.6
Enhanced Number processing requirements and the use of NPP feature..........................................................13
2.7
Conditioning Actions used by IDPRCDPN and IDPRCGPN Services.............................................................15
2.8
Service Actions used by IDPRCDPN and IDPRCGPN Services......................................................................15
2.9
TTROPTS Table.................................................................................................................................................15
2.10
Prepaid IDP Query Relay Supported Conditioning and Service Actions.......................................................19
2.11
REPT-STAT-SCCP Support................................................................................................................................20
3.0
FUNCTIONAL REQUIREMENTS................................................................................................................................21
3.1
FRS Compliance Matrix....................................................................................................................................21
3.2
General Requirements........................................................................................................................................24
3.3
Protocol Requirements.......................................................................................................................................25
3.4
Hardware Requirements.....................................................................................................................................28
3.5
User Interface Requirements..............................................................................................................................28
3.6
Measurement Requirements...............................................................................................................................31
3.7
Upgrade Considerations.....................................................................................................................................32
4.0
PERFORMANCE............................................................................................................................................................41
5.0
RELIABILITY.................................................................................................................................................................41
6.0
SERVICEABILITY.........................................................................................................................................................41
6.1
Service provisioning sequence examples...........................................................................................................42
7.0
TESTABILITY................................................................................................................................................................43
7.1
Prepaid IDP Query Relay: PR 122188 Testability.............................................................................................44
8.0
LIMITATIONS................................................................................................................................................................50
9.0
PEER REVIEW CHECKLIST........................................................................................................................................51
APPENDIX A: SAMPLE INCOMING INITIALDP (CAP) MESSAGE.................................................................................52
APPENDIX B: CALLED PARTYNUMBER PARAMETER FORMAT..................................................................................59
APPENDIX C: REVIEW SUMMARIES..................................................................................................................................62
List of Tables
Table 1: Acronyms and Terminology.........................................................................................................................6
Table 2: Sample NPP Configuration for IDPRCDPN Service...................................................................................14
Table 3: IDP Relay feature handling Table................................................................................................................16
Table 4: CHG-TTROPTS command Parameters.......................................................................................................17
Table 5: IDPRCDPN Service specific Conditioning Actions...................................................................................19
Table 6: IDPRCDPN Service Actions........................................................................................................................19
Table 7: IDPRCGPN Service Actions........................................................................................................................20
Table 8: FRS Compliance Matrix..............................................................................................................................21
Table 9: FD General Requirement Table...................................................................................................................24
Table 10: FD Protocol Requirements Table...............................................................................................................25
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 3 of 68
INTERNAL USE ONLY
Table 11: FD User Interface Requirement Table.......................................................................................................28

Table 12: Affected Command Specifications.............................................................................................................31
Table 13: FD Measurement Requirement Table........................................................................................................31
Table 14: Affected Measurement documents.............................................................................................................32
Table 15: EGLEOPTS Table definition.....................................................................................................................32
Table 16: IDP Relay Number Conditioning Table.....................................................................................................35
Table 17: TTROPTS Configuration to be performed during Upgrade......................................................................36
Table 18: NPP Configuration to be performed during Upgrade for IDPRCDPN Service.........................................37
Table 19: TESTMSG Table definition.......................................................................................................................38
Table 20: FD Upgrade Requirement Table................................................................................................................40
Table 21: NAI value mappings for Prepaid IDP Service Provisionig........................................................................42
Table 22: TTR Test table parameters.........................................................................................................................44
Table 23: Parameters supported by CHG-TTR-MSG command...............................................................................44
Table 24: Parameters supported by RTRV-TTR-MSG command..............................................................................45
Table 25 : TST-MSG parameters...............................................................................................................................46
Table 26: Document Approval Checklist...................................................................................................................51
List of Figures
Figure 1: IDP Query Relay Feature Call Flow..........................................................................................................8
Figure 2: Message flow for Prepaid IDP Query Relay feature..................................................................................10
Figure 3: Message flow for Prepaid IDP Query Relay feature (cont)...................................................................12
Figure 4: Message flow for Prepaid IDP Relay feature.............................................................................................12
Figure 5: REPT-STAT-SCCP general format.............................................................................................................21
Figure 6: REPT-STAT-SCCP format: Card Specific..................................................................................................21
Figure 7 TESTMSG Table organization....................................................................................................................38
Figure 8: RTRV-TTR-MSG display format...............................................................................................................46
Figure 9: TST-MSG output in BRIEF format............................................................................................................48
Figure 10: TST-MSG output in FULL format...........................................................................................................50
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 4 of 68
1.0
INTRODUCTION
1.1
Purpose and Scope
INTERNAL USE ONLY
This document describes the requirements for Feature Number 57095, the original Prepaid IDP Query Relay and PR 122188
Flexible Prepaid IDP Query Relay enhancement. The Flexible Prepaid IDP Query Relay enhancement feature shall be
implemented in EAGLE Release 39.0. It is assumed that the reader of the document is very familiar with NPP implementation
[10] and prior versions [version 2.0] of this document.
The scope of this document is to describe:
1. General description of the feature
2.
Limitations of implementation
3.
Upgrade considerations
4.
Inter-working with existing EAGLE 5 ISS features
5.
External feature dependent Hardware and interconnecting requirements
6.
Inter-working with other systems and features (e.g. EPAP).
1.2
1.2.1
References
Internal References:
[1] TEKELEC Acronym Guide, MS005077.doc, Current Revision

[2] Feature Description Template, TM005011, Revision 1.10, May 2003
[3] FORM, INVENTION DISCLOSURE FOR PATENTS, 907-0771-01
[4] Formal Peer Review Procedure, PD001866, V 6.1, Formal Peer Review Committee, July 2005
[5] Feature Requirements Specifications (FRS), FE005168 , V 2.7
[6] Common Screening List High Level Design(HD), HD005196, V 2.7
[7] Prepaid IDP Query Relay, TR005861 V 1.7
[8] Test Plan Prepaid IDP Query Relay, TP006172
[9] EAGLE 5 ISS Measurements, TR005822 V 1.10
[10] Numbering Plan Processor, FD005979, V 1.3
[11] CDT, WS 255
[12] TR005904, Eagle Options Table Design, V1.3
[13] PF005397 - EAGLE 5 ISS Release 39.0, V 1.2
[14] IDPR Handling of RNs with Leading Zero, FD005968 V1.5
1.2.2
External References:
[15] ITU Q.1218 for INAP specification

[16] 3GPP TS 24.008 version 3.0.0
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 5 of 68
1.3
INTERNAL USE ONLY
Acronyms and Terminology
Table 1: Acronyms and Terminology

Acronyms
BCSM
CA(s)
CdPA
CdPN
CgPA
CgPN
DN
FA(s)
GTA
INAP
IDP
IDPR
IEC
LAI
LAC
NEC
SA(s)
SK
Basic Call State Model

NPP Conditioning Action(s)
SCCP Called Party Address
TCAP Called Party Number
SCCP Calling Party Address
TCAP Calling Party Number
Dialed Number
NPP Formatting Actions(s)
Global Title Address
Intelligent Network Application Protocol
Initial Detection Point
Prepaid IDP Query Relay Feature
International Escape Code
Location Area Information
Location Area Code
National Escape Code
NPP Service Actions(s)
Service Key
Terminology
CSL
CSL CCNC
CSL SKBCSM
CSP
DEFCC
GTA
IDP Query
SRVSEL
TCAP DN
NPP
Common Screening List. This is a command used to enter list of numbers or point
code which are used for screening messages in various features. IDP Relay shall
use this command for screening 4 lists defined in section 2.2.
This refers to the list of prefixes which have country code (CC) and Network Code
(NDC) for which the IDP Relay is applicable.
This refers to the list of concatenated string of service key (SK) and basic call state
model (BCSM) parameter for which the IDP Relay is applicable.
Carrier Selection Point
This is the default country code parameter in the existing STPOPTS table.
Global Title Address. In case of IDP Relay feature it refers to the SCCP CDPA GTA
from the incoming message.
IDP is the INAP Initial Detection Point message. When the message comes in a
TCAP Begin package, it is referred to as an IDP Query message.
This specifies the service selected using the ent-srvsel command. This is an
existing command used for services like GPORT,GFLEX,etc. It has been enhanced
to support IDP Relay feature.
The TCAP part of the message could have either CalledPartyNumber or
CalledPartyBCDNumber but never both. TCAP DN refers to CalledPartyNumber
or CalledPartyBCDNumber parameter - whichever is present.
Numbering Plan Processor. The Numbering Plan Processor (NPP) provides the
flexible service application behavior that satisfies the needs of customers resident
in complex signaling networks. It can be used for number conditioning, RTDB
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 6 of 68
TTROPTS
1.4
INTERNAL USE ONLY
lookup and outgoing number formatting.

Virtual table representing Triggerless TCAP Relay options in EGLEOPTS table
Problem/Need
With many countries and many operators in each country, often requirements fluctuate with the multitude of variations found.
Anatel, the regulatory body for Brazil, is mandating the introduction of Number Portability in Brazil in early 2008. Given the
strength of Tekelecs Number Portability (NP) solutions and Tekelecs current EAGLE 5 ISS footprint in the several Brazilian
operators; this provides a lucrative opportunity for Tekelec. Brazil has adopted a unique number portability scheme with some
additional differences between regional operators. Most importantly for the feature described here, Brazil and its regional
operators send prepaid and VPN queries to SCPs in a number of formats based on certain information, some of which are not
supported by the original EAGLE 5 ISS Prepaid IDP Query Relay feature. Felxible IDP Relay feature enhancement is intended
to address those gaps.
Some operators provide their SCP Prepaid numbers in already number conditioned format. But sometimes, the complex
numbering schemes are used and the Prepaid IDP Relay feature is required to do significant manipulation of the incoming
CdPN before doing the NP lookup, and again before sending the query to the SCP.
Following are some examples:
The Nature of address Indicator (NAI) is used in a non-compliant manner (to varying degrees). e.g. it is incorrectly set
to International and the number format is not international. In fact, given that the NAI is always set to International, no
matter the format, the incoming NAI is irrelevant
The Local Area Code (LAC) 2-byte field of the Local Area Identification (LAI) information element is used:
o as the AC in cases where the AC is not provided in the CdPN and is needed.
o to determine how to format the outgoing CdPN in the IDP query.
The collect calls escape codes 90 and 9090 might need to be stripped and then re-added after the RN
The Carrier Selection Point(CSP) can also be removed from the incoming number, and sometimes re-added. e.g.
0+CSP should only be re-added if the LAC not equal to AC.
To further complicate matters, there might be a desire to provide the RN for the Calling Party(CgPN) when the call is
identified to be a collect call.
Sometimes customers have number plans and routing numbers that overlap and make it difficult to parse the
numbering strings. This might require a delimiter to be introduced into the outgoing number.
Service key selection could also vary and change is required for number of bytes present in the service key.
Un-segmented XUDT message type might be required in some markets
Sometimes only the RN is desired but not the SP, or vice versa, and sometimes both are required. Flexibility is
required to add the RN, SP or RN/SP to the outgoing number format.
It is important to note that while these requirements primarily refer to a set of regional operators in Brazil, this feature is
intended to introduce new flexibility points in number conditioning and outgoing message formats that are reusable in other
markets.
1.5
Suggested Solution
Original Prepaid IDP Query Relay feature intercepts IDP messages destined to a service application node (e.g. SCP) and
executes a number portability database lookup. Number portability information is included in the IDP message destined for the
service application node. The messages selected for RTDB lookups are determined by matching incoming messages with preselected service application nodes (using CdPA GTA), and a combination of INAP/CAP service key (SK) and Event Type
BCSM.
The Prepaid IDP Query Relay feature will be enhanced to provide a flexible configuration which allows: easy modification of
the incoming dialed digits for RTDB lookups, the operator to request RTDB lookups for both the Calling and Called Parties,
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 7 of 68
INTERNAL USE ONLY
and flexible formatting of the outgoing numbers. This feature shall use the services of Numbering Plan Processor (NPP) to
achieve the flexibility.
The Numbering Plan Processor (NPP) feature provides the flexible service application behavior that satisfies the needs of
customers resident in complex signaling networks. The NPP consists of three major functions. First, the NPP allows the
customer to provision message filters to classify a particular incoming digit string. Secondly, the NPP allows the customer to
provision customized Eagle feature behavior on a filter basis. Thirdly, the NPP allows the customer ultimate flexibility when
encoding outgoing messages on a filter basis. The Figure below depicts the Prepaid IDP Query message flow using NPP.
Figure 1: IDP Query Relay Feature Call Flow
1.6
Obsolescence
The Prepaid IDP Query Relay feature consolidates all configurable IDPR Options at one place and obsoletes many existing
configurable parameters used by the original IDP Query Relay feature (prior to EAGLE Release 39.0). FEATPFX Table and
some of the fields in the CSL tables are either moved into new TTROPTS Table (defined in this document) or into the NPP
feature. CHG-PREFIX command for IDPR feature is obsolete.
This document describes the only the new IDP Query relay functionality. Customers who use IDPR feature prior to EAGLE 5
ISS Release 39.0 need to refer to the previous versions of this document for requirements.
2.0
GENERAL DESCRIPTION
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 8 of 68
INTERNAL USE ONLY
The Prepaid IDP Query Relay feature (referred to hereafter as simply IDP Relay) provides a mechanism to insure correct
charging for calls from prepaid subscribers in a portability environment.
The concept of IDP Relay is that instead of the MSC routing the prepaid IDP query directly to the prepaid SCP, and forcing the
SCP to perform its own number portability database query, the IDP query shall instead be intercepted by the number portability
database node itself. The number portability database node, it this case EAGLE 5 ISS, shall perform a portability check on the
called number, insert the portability information (i.e. Routing Number or HLR Address), and forward the IDP query to a
prepaid SCP for processing. When the SCP receives the IDP query, it shall have all of the information it needs to correctly
charge for and process the call, without the need to launch a separate number portability database query of its own.
For message discrimination on DSM cards, Prepaid IDP Relay feature uses service selector framework already present in
EAGLE. Also note that only some of the messages identified for IDP Relay service based on SRVSEL shall have their
outgoing TCAP DN modified.
For messages applicable to the Prepaid IDP Relay feature, following additional filters/checks are performed:
1. SRVSEL match points to IDP Relay service.
2. MSU has ITU TCAP package
3. MSU Opcode = IDP
4. SCCP and TCAP part of the message are successfully decoded
5. SK and event BCSM parameters are present and decoded correctly.
6. CDPN or CDPN(BCD) parameter is present and decoded correctly
7. SCCP CDPA is found in the common screening GTA list for IDP Relay feature.
8. SK+BCSM is found in the common screening SKBCSM list for IDP Relay feature
9. Number condition on TCAP DN is successful based on Table 2. This functionality is achieved through NPP feature.
10. Based on CGPACCCK field in the TTROPTS Table, SCCP CGPA is checked for DEFCC match. .
11. Conditioned TCAP DN is found in RTDB single/Range table with SP, RN or DN entity type. . This functionality is
achieved through NPP feature.
12. Based on the parameter fields of the TTROPTS Table, the outgoing TCAP DN is formatted. See table 2 more details. .
This functionality is achieved through NPP feature.
13. The message is forward to GTT handling based on original incoming SCCP CDPA.
The above checks/filters are described in detail in this document.
.
2.1
Message Flow for IDP Relay feature
The figures below depict the details of the IDP message processing.
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 9 of 68
INTERNAL USE ONLY
Figure 2: Message flow for Prepaid IDP Query Relay feature
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 10 of 68
DO NOT COPY
INTERNAL USE ONLY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 11 of 68
INTERNAL USE ONLY
Figure 3: Message flow for Prepaid IDP Query Relay feature (cont)
Figure 4: Message flow for Prepaid IDP Relay feature
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 12 of 68
2.2
INTERNAL USE ONLY
Common Screening List (CSL)
Common screening list a new command introduced in EAGLE 5 ISS for handling screening requirements of various features.
The screening could be done on digit string or point codes. For IDP Relay feature, 3 such screening lists are required. Each of
the three screening is based on digit string..
2.2.1
GTA screening list
This screening list is used to compare the SCCP CDPA GT from the incoming message into this list. If not found, the message
falls to GTT handling.
2.2.2
SKBCSM screening list
This screening list is used to compare the concatenated SK + BCSM from the incoming message into this list. If not found, the
message falls to GTT handling.
2.2.3
CCNDC screening list
This screening list is used to compare the conditioned TCAP DN in international format into this list. If not found, the message
falls to GTT handling.
2.3
Service Key (SK) parameter and BCSM Parameter
For the IDP Relay feature, the two values shall be concatenated and treated as five byte strings. This shall then be used to
search the common screening list SKBCSM table. The Service key can be up to 4 bytes. [These changes have been done in
EAGLE Release 37.5 as part of PR 123877]
2.4
SRVSEL Command for IDP Relay
IDPR is defined for the SRVSEL command. GTII and GTIN are supported..
GTI,TT,SSN and SERV are mandatory parameters.
NP and NAI are optional parameters.
SNP and SNAI are not supported for IDP Relay feature.
2.5
REPT-STAT-SCCP
From EAGLE Release 39.0, REPT-STAT-SCCP shall support IDPR message statistics. Please refer section 2.11for details.
2.6
Enhanced Number processing requirements and the use of NPP feature
The Prepaid IDP Query Relay feature shall use NPP for TCAP CdPN and/or CgPN number conditioning. NPP feature provides
the ability to filter messages and apply customized behavior to the particular IDP message. This feature shall be associated
with a pair of NPP Ruleset, by provisioning a set of NPP Rules. An NPP Rule contains a single NPP Filter and NPP Action set.
IDPR shall use two different rulesets IDPRCDPN and IDPRCGPN for CdPN and CgPN number conditioning and formatting
respectively. The rulesets associated with IDPR feature will be provisioned by NPP commands. IDPR feature will establish
relationship with NPP services during compile time.
NPP rules shall be defined to support the required formats for CdPN and/or CgPN. The table below provides a sample NPP
configuration for the Prepaid IDP Query Relay feature.
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 13 of 68
INTERNAL USE ONLY
Table 2: Sample NPP Configuration for IDPRCDPN Service

IDPR
Service
Rule Set
Rule
Filter
Action Set
FNAI
INTL
FPFX
*
FDIGLEN
8
CA
CCDEF
ACLAC
SNX
SA
CDPNNP
INTL
13
FPFX
PFXA2 ( CSP)
CCDEF
AC2
SNX
CDPNNP
LACCK
INTL
11
FPFX
CCDEF
DN10
CDPNNP
INTL
9090
12
FPFX
CCDEF
ACLAC
SNX
CDPNNP
RN
FPFX
CC
AC
SN
INTL
INTL
90
14
FPFX
PFXA2 ( CSP)
CCDEF
DN10 ( AC+SN)
CDPNNP
INTL
UNKNOWN
11
FPFX
CCDEF
DN10 ( AC+SN)
CDPNNP
UNKNOWN
10
CCDEF
DN9
CDPNNP
RN
FPFX
PFXA ( CSP)
CC
DN
FPFX
DLM3
RN
DN
DLM3
RN
DN
IDPRCDPN
NPP
Service
FA
RN
CC
AC
SN
RN
FPFX
PFXA ( CSP)
CC
AC
SN
RN
CC
DN
OFNAI
INTL
INTL
INTL
UNKNOWN
UNKNOWN
Design Notes:
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 14 of 68
1.
2.
3.
4.
5.
6.
7.
8.
9.
2.7
2.8
2.9
INTERNAL USE ONLY
ACLAC shall be performed by IDPR as a service-specific conditioning action and AC shall be updated in
NPPSTATE:AC and appended to the incoming digit string(AC+SN). Here, AC is same as LAC that shall be obtained
from LAI during IDPR handling. This Service Action is applicable only to IDPRCDPN service.
LACCK is a SA action to verify if LAC=AC. LAC shall be identified by IDPR and AC(in NPPSTATE) shall be
supplied by NPP to be perform this action. If (LAC == NPPSTATE:AC) then FPFX shall be set to NONE and
PFXA(=CSP) shall be set to NONE. NONE indicates that the NPSTATE variable shall be set to no value.
CDPNNP is IDPR specific service action to do a RTDB lookup for the conditioned number and analyze success
criteria based on TTROPTS: NPTYPE . This shall also populate NPPSTATE:RN (or SP) with RTDB successful result.
In these examples, CC is assumed to be 2 digits, AC=2, CSP=2 and SN =8 digits.
CCDEF is a NPP CA to add CC to the conditioned digits and also populate NPPSTATE:CC for FA.
AC2 is a NPP CA to update NPPSTATE:AC using 2 digits from the conditioned digit string.
SNX is a NPP CA to update NPPSTATE:SN using the conditioned digit string. It should be used if we need to process
AC separately.
DN[1..15] is a NPP CA to update NPPSTATE:DN using the conditioned digit string. This could be AC+SN.
NPPSTATE:DLM3 would be updated using TTROPTS:DLM3, if configured.
Conditioning Actions used by IDPRCDPN and IDPRCGPN Services

Conditioning Action
IDPRCDPN
IDPRCGPN
Conditioning Actions
Specified by NPP FD [10]
YES
YES
ACLAC
YES
NO
Service Actions used by IDPRCDPN and IDPRCGPN Services

Service Action
IDPRCDPN
IDPRCGPN
CDPNNP
YES
NO
LACCK
CCNCCHK
CGPNNPRQD
CGPNNP
YES
YES
YES
NO
NO
NO
NO
YES
TTROPTS Table
TTROPTS table contains the IDPR feature specific configuration. Provisioning and retrieving this table can be possible only
when the IDPR feature is enabled. Feature can be activated after provisioning the required fields.
2.9.1
TTROPTS Table Structure
This table shall consist of the following options:

Table 3: IDP Relay feature handling Table
NPTYPE
Possible Value
SP
DO NOT COPY
Comments
When the lookup in the RTDB has entitytype=SP, then the
lookup is considered successful. This entity_data is now used to
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 15 of 68
INTERNAL USE ONLY
RN
RNSP
(Default)
ANYMATCH
ALWAYS
RNSPDN
SNAI
INCOMING
(Default)
INTL
NATL
UNKN
CGNPTYPE
SP
RN
RNSP
(Default)
ANYMATCH
ALWAYS
CGSNAI
set up the outgoing CdPN .

When the lookup in the RTDB has entitytype=RN, then the
lookup is considered successful. This entity_data is now used to
set up the outgoing CdPN.
When the lookup in the RTDB has entitytype=SP or RN, then
the lookup is considered successful. This entity_data is now
used as RN to set up the outgoing CdPN. This is the default
value.
When the lookup in the RTDB has entitytype=RN, SP or DNor
match with no entity, then the lookup is considered successful.
The entity_data is used as the RN to set up the outgoing CdPN.
When the lookup in the RTDB results in a match irrespective of
the entitytype or even if no match is found, the lookup is
considered successful.
When the lookup in the RTDB has entitytype=RN, SP or DN,
then the lookup is considered successful.
Default value. When the value is set to INCOMING then the
incoming CdPN NAI is used for number conditioning.
When the value is set to INTL, then CdPN NAI is always set
to International for number conditioning.
When the value is set to NATL, then CdPN NAI is always set
to national for number conditioning.
When the value is set to UNKN, then CdPN NAI is always set
to Unknown for number conditioning.
When the lookup in the RTDB, using CgPN, has entitytype=SP,
then the lookup is considered successful. This entity_data is now
used to set up the outgoing CgPN.
When the lookup in the RTDB, using CgPN, has entitytype=RN,
then the lookup is considered successful. This entity_data is now
used to set up the outgoing CgPN.
When the lookup in the RTDB, using CgPN, has entitytype=SP
or RN, then the lookup is considered successful. This
entity_data is now used as RN to set up the outgoing CgPN.
This is the default value.
When the lookup in the RTDB using CgPN, has entitytype=RN
or SP or match with no entity, then the lookup is considered
successful.
The entity_data is used as the RN to set up the outgoing CgPN.
When the lookup in the RTDB, using CgPN, results in a match
irrespective of the entitytype or even if no match is found, the
lookup is considered successful.
RNSPDN
When the lookup in the RTDB has entity type RN, SP or DN,
then the lookup is considered successful.
INCOMING
(Default)
INTL
Default value. When the value is set to INCOMING then the

incoming CgPN NAI is used for number conditioning.
When the value is set to INTL, then CgPN NAI is always set
to International for number conditioning.
When the value is set to NATL, then CgPN NAI is always set
to national for number conditioning.
NATL
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 16 of 68
INTERNAL USE ONLY
UNKN
When the value is set to UNKN, then CgPN NAI is always set
to Unknown for number conditioning.
These are 1 to 16 digit hexadecimal delimiters to be used for
formatting outgoing TCAP DN.
DLM1
<1..16>
DLM2
NONE
(Default)
<1..16>
The default value is none. It indicates no value, or changes the

current value to no value.
NONE
(Default)

<1..16>

NONE
(Default)

CGPACCCK
ALWAYS
DFLTRN
NON-INTL
(Default)
OFF
<1..15>
This parameter is used to verify if the DEFCC check is to made

on the incoming CgPA.
ALWAYS value indicates to perform CGPA NAI check always,
before RTDB lookup.
DEFCC check to be performed on incoming CgPA, if CdPN
NAI is not International.
Never perform the DEFCC check
This is 1 to 15 digit hexadecimal prefix to be used as RN when
NPTYPE is set as SP or RNSP and when the CdPN DB lookup
returns entitytype=SP.
The default value is NONE. It indicates no value, or changes the
DLM3
NONE
(Default)
2.9.2
CHG-TTROPTS Command
There shall be a CHG-TTROPTS command to modify the TTROPTS parameters. This command shall have the following
mandatory and optional parameters.
Table 4: CHG-TTROPTS command Parameters
Parameter
M/O
Possible Values
Default
NPTYPE
Optional
SP
RN
RNSP
ANYMATCH
ALWAYS
RNSPDN
RNSP
INCOMING
INTL
NATL
UNKN
INCOMING
SNAI
Optional
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 17 of 68
INTERNAL USE ONLY
CGNPTYPE
Optional
CGSNAI
Optional
SP
RN
RNSP
ANYMATCH
ALWAYS
RNSPDN
RNSP
INCOMING
INTL
NATL
UNKN
INCOMING
DLM1
Optional
Digit string 1..16 digits, NONE
NONE
DLM2
Optional
NONE
DLM3
Optional
NONE
NON-INTL
CGPACCCK
Optional
ALWAYS
NON-INTL
OFF
DFLTRN
Optional
NONE
NOTE: A digit string can have the following valid values : 0..9, a..f, or A..F.
NONE indicates no value, or changes the current value to no value.
2.9.3
RTRV-TTROPTS Command
There shall be a RTRV-TTROPTS command to retrieve the TTROPTS parameters. This command shall have the following
format
1
12345678901234567890123456789012345678901234567890123456789012345678901234567890
IDPR OPTIONS
------------------------------------------------------------CDPN DETAILS
CGPN DETAILS
NPTYPE
SNAI
CGNPTYPE
CGSNAI
RNSP
INCOMING
CGPACCCK
NATL
DLM1
0123456789abcdef
DLM2
0123456789abcdef
DLM3
0123456789abcdef
DFLTRN
0123456789abcde
RNSP
INCOMING
NOTE: If the parameter value is NONE, the string NONE is displayed.
2.10 Prepaid IDP Query Relay Supported Conditioning and Service Actions.
Prepaid IDP Query Relay feature uses following condition Actions and Service Actions
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 18 of 68
2.10.1
INTERNAL USE ONLY
IDPRCDPN Conditioning Actions
IDPRCDPN NPP Service defines the following new number conditioning actions.
Table 5: IDPRCDPN Service specific Conditioning Actions
IDPR Conditioning Action Token
Action in STP
ACLAC
Get AC from LAC.

In this case, Area Code is not
included in the incoming DN and
should be obtained from LAI
AC present in LAI would be updated
in NPPSTATE:AC to be used in FA
and also appended to the incoming
digit string(SN).
2.10.2
IDPRCDPN Service Actions
IDPRCDPN NPP Service shall support the following service actions. These service actions shall have the specified precedence.
Table 6: IDPRCDPN Service Actions
IDPR Service Action
Token
Precedence
Action in STP
CGPNNPRQD
60
CCNCCHK
100
CDPNNP
80
Set a flag in IDPR feature logic to indicate whether

IDPRCGPN service is to be invoked. This implies that CgPN
number conditioning, Service Actions and formatting is done
based on the configured CgPN Ruleset.
Verify the conditioned number is available under CSL
NOTE: This Service Action is only used for upgrade purpose.
NPP SA shall do a RTDB lookup for the conditioned number
and analyses success criteria. If RTDB lookup is successful,
entity-data shall be updated in RN or SP, as per the entity-type.
If entity-type is SP, DFLTRN is configured and FA contains
RN, RN shall be replaced by DFLTRN.
NOTE: If the number returned from RTDB is less than 5 digits,
IDP feature shall send an errot and fall into GTT. If the number
returned from RTDB is greater than 15 digits, the first 15 digits
must be used as the returned number; remaining digits are
ignored.
LACCK
60
This defines a SA to compare the LAC (obtained for LAI) with

the AC present in the incoming DN.
This action shall be used to format the outgoing number by
removing the digit and length prefixes (filter prefix in NPP)
from the outgoing digit string if LAC =AC.
Note: TTROPTS:DLM[1,2, 3] value shall be populated into NPSTATE:DLM[1..3], if configured. This would be done
implicitly and no service action is required for this.
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 19 of 68
2.10.3
INTERNAL USE ONLY
IDPRCGPN Conditioning Actions
IDPRCGPN NPP Service does not require any new number Conditioning Actions.
2.10.4
IDPRCGPN Service Actions
IDPRCGPN service shall support the following Service Actions. These Service Actions shall have the specified precedence.
Table 7: IDPRCGPN Service Actions
IDPR Service Action
Token
Precedence
Action in STP
CGPNNP
100
NPP SA shall do a RTDB lookup for the conditioned number

and analyses success criteria. If RTDB lookup is successful,
entity-data shall be updated in RN or SP, as per the entity-type.
If entity-type is SP, DFLTRN is configured and FA contains
RN, RN shall be replaced by DFLTRN.
2.11 REPT-STAT-SCCP Support

REPT-STAT-SCCP command shall be updated to include the IDPR statistics. Note that to GTT will be the messages send for
GTT processing. This will be the same as the Total messages.
1.
REPT-STAT-SCCP shall display IDPR service statistics if IDPR feature is ON. The display format shall be as shown in
Figure 5
e1090701 07-10-10 13:54:34 EST
UNKNOWN ??.?.?-58.20.63
SCCP SUBSYSTEM REPORT IS-NR
Active
-----
SCCP ALARM STATUS = No Alarms

MNP SERVICE REPORT IS-NR
MNP ALARM STATUS
Active
-----
= No Alarms
SCCP Cards Configured= 2
Cards IS-NR= 2
System Daily Peak SCCP Load
TPS 07-10-10 00:00:05
System Overall Peak SCCP Load
TPS 00-00-00 00:00:00
System Total SCCP Capacity
1700
TPS (1700
max SCCP Capacity)
System SCCP Capacity Calc. Method (N)

System TPS Alarm Threshold
1360
CARD
SST
VERSION
PST
TPS (80% System

AST
N SCCP Capacity)
MSU
CPU
USAGE USAGE
-----------------------------------------------------------------1105 P 128-020-063
IS-NR
Active
-----
0%
6%
1107
IS-NR
Active
-----
0%
5%
128-020-063
-----------------------------------------------------------------SCCP Service Average MSU Capacity =
0%
Average CPU Capacity =
5%
AVERAGE CPU USAGE PER SERVICE:

GTT
0%
MNP
0%
IDPR
DO NOT COPY
0%
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 20 of 68
INTERNAL USE ONLY
TOTAL SERVICE STATISTICS:

FAIL
REROUTE\
SUCCESS
ERRORS
RATIO
WARNINGS
TO GTT
TOTAL
GTT:
1995
0%
2000
MNP:
800
0%
10
815
TTR:
60
0%
71
71
SERVICE
FORWARD
Figure 5: REPT-STAT-SCCP general format

2.
REPT-STAT-SCCP shall provide status on the services for a specified card. The output format shall be as shown in Figure
6, if IDPR feature is ON.
e1090701 07-10-10 13:55:09 EST
UNKNOWN ??.?.?-58.20.63
CARD
VERSION
TYPE
PST
SST
AST
1105
128-020-063
DSM
IS-NR
Active
-----
CARD ALARM STATUS
= **
0446 RTDB database capacity is 80% full
GTT:
STAT = ACT
CPU USAGE = 10%
TTR:
STAT = ACT
CPU USAGE =
8%
--------------TOTAL
= 18%
CARD SERVICE STATISTICS

SERVICE
SUCCESS
ERRORS
WARNINGS
FORWARD TO GTT
TOTAL
GTT:
TTR:
Figure 6: REPT-STAT-SCCP format: Card Specific
3.0
FUNCTIONAL REQUIREMENTS
3.1
FRS Compliance Matrix
The following table lists each of the FRS requirements along with a cross-reference to the FD requirement(s) in this document
that addresses that requirement.
FC
Fully compliant
PC
Partially compliant
NA
Not applicable
Table 8: FRS Compliance Matrix
FRS Requirement
R-57095-10
R-57095-15
R-57095-17
R-57095-19
R-57095-20
R-57095-25
Compliance
FC
FC
FC
FC
FC
FC
DO NOT COPY
FD Requirement Numbers or Applicable FD

FD400, FD410
FD430, FD435
FD270
FD265
FD510-FD520
FD531, FD532
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 21 of 68
INTERNAL USE ONLY
FRS Requirement
R-57095-30
R-57095-40
R-57095-45
R-57095-50
R-57095-55
Compliance
FC
FC
FC
FC
FC

FD480- FD490
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD115, FD120
FD115, FD120
R-57095-60
FC
FD115, FD120
R-57095-65
R-57095-70
R-57095-75
R-57095-80
R-57095-85
R-57095-90
R-57095-95
R-57095-100
R-57095-105
R-57095-110
R-57095-112
R-57095-115
R-57095-120
R-57095-125
R-57095-130
R-57095-135
R-57095-140
R-57095-145
R-57095-150
R-57095-155
R-57095-160
R-57095-165
R-57095-170
R-57095-175
R-57095-180
R-57095-190
R-57095-195
R-57095-200
R-122188-200
R-122188-230
R-122188-240
R-122188-245
R-122188-247
R-122188-250
R-122188-260
R-122188-270
R-122188-280
R-122188-290
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FD170,FD180,FD190
FD115
FD140
FD120
FD200
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD 260, FD265,
FD 260, FD265,
FD 260, FD265,
FD 260, FD265,
FD005979[10], 2.10, Table 18
FD 205
FD 205
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD 310
FD300, FD-312
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD700-FD750
FD-122188-190
FD380
FD390
FD-122188-100
FD-122188-110
Section 2.9, Section 7.1
Section 3.7
Section 2.11
FD-150
FD-150
FD-150
FD-122188-200,
FD-122188-210
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 22 of 68
FRS Requirement
R-122188-300
R-122188-310
R-122188-320
R-122188-330
R-122188-340
R-122188-350
R-122188-355
R-122188-360
R-122188-370
R-122188-380
R-122188-400
R-122188-410
R-122188-420
R-122188-430
R-122188-440
R-122188-450
R-122188-460
R-122188-470
R-122188-480
R-122188-490
R-122188-500
R-122188-510
R-122188-520
R-122188-530
R-122188-540
R-122188-550
R-122188-560
R-122188-570
R-122188-580
R-122188-595
R-122188-600
R-122188-610
R-122188-620
R-122188-630
R-122188-650
R-122188-660
R-122188-670
R-122188-680
R-122188-690
INTERNAL USE ONLY
Compliance
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
FC
NA
FC
FC
FC
FC
FC

FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD-122188-220, FD-122188-260
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD-122188-260, FD-122188-280
FD-122188-1010,FD-122188-1020
FD-122188-270
FD-122188-280
FD-122188-290
FD-122188-300
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD-122188-370
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
FD005979[10], 2.10, Table 18
TINP 2DN interactions not to be considered
FD-122188-220,
FD005979, Section 4
FD005979
FD-122188-340
Section 7.1
Note: PC means that some of the functionality shall be provided by NPP.
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 23 of 68
3.2
INTERNAL USE ONLY
General Requirements
Table 9: FD General Requirement Table

FD Reqt No.
FD-100
FD-110
Required
or
Optional
(R or O)
R
R
Requirement Description (and any additional comments if

necessary)
Affected
GPLs
Only GT routed messages are handled by IDP Relay feature.

IDP Relay feature shall only handle message with ITU
MTP/SCCP/TCAP. Else the message falls to GTT handling.
The Prepaid IDP Query Relay shall support all requirements
and interactions of the base IDP Prepaid Relay Requirements
as described in [R-57095-000] thru [R-57095-199]. Refer [5]
The Prepaid IDP Query Relay Feature shall maintain the
EAGLE 5 ISS system performance and shall not degrade the
overall capacity of any card/component of the EAGLE 5 ISS
Prepaid IDP Query Relay shall support of REPT-STAT-SCCP
as per Section 2.11
VSCCP
VSCCP
FD-122188100
FD-122188110
FD-122188120
FD-122188130
Prepaid IDP Query Relay shall support of test tool as per

Section 7.1
FD-122188140
Prepaid IDP Query Relay feature shall use IDPRCDPN NPP

service for CdPN number processing.
FD-122188150
Prepaid IDP Query feature shall use IDPRCGPN NPP Service

for CgPN number processing.
FD-122188160
FD-122188170
Prepaid IDP Query Relay feature shall have a testing utility to

verify IDPRCDPN or IDPRCGPN NPP Service by using sample
IDPR messages for number conditioning and formatting. These
test messages shall never be routed to the live network. NPP
Test task shall be used for this utility. The purpose of this is
limited to studying the INAP and CAP messages
Prepaid IDP Query Relay feature shall implement EGLEOPTS
Table as described in section 3.7.1
FD-122188180
Prepaid IDP Query Relay feature shall implement TESTMSG

FD-122188185
Prepaid IDP Query Relay feature shall implement TESTMSG

FD-122188190
FD-122188190
The IDP Relay service shall be capable of processing a

minimum of 850 IDPs/sec per EAGLE 5 ISS DSM card, for a
total of at least 20,400 IDPs/sec per EAGLE 5 ISS node.
Prepaid IDP Relay feature shall support all NPP Actions
described under section 2.10
DO NOT COPY
VSCCP,
SCCPHC,
EOAM
VSCCP,
SCCPHC,
VSCCP,
SCCPHC,
EOAM
VSCCP,
SCCPHC,
EOAM
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
EOAM,
VSCCP,
SCCPHC
EOAM,
VSCCP,
SCCPHC
EOAM,
VSCCP,
SCCPHC
VSCCP,
SCCPHC
EOAM,
VSCCP,
SCCPHC
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 24 of 68
3.3
INTERNAL USE ONLY
Protocol Requirements
Table 10: FD Protocol Requirements Table

FD Reqt No.
FD-115
Required
or
Optional
(R or O)
R
FD-120
FD-130
FD-140
FD-150
FD-160
FD-170
FD-180
FD-190
FD-200
FD-205
FD-260
FD-265

necessary)
Affected
GPLs
The SCCP CDPA parameters shall be matched with the

SRVSEL parameters. If the parameters match and the SERV
points to IDP Relay, then IDP Relay feature handling is applied
to this MSU.
MSU applicable to IDP Relay service has to be INAP or CAP
message with Opcode = IDP.
MSU must pass existing SCCP/TCAP/INAP decoding. If there
is a decoding error, MSU falls to GTT handling.
SCCP CDPA must be found in the CSL GTA table. If it is not
found, MSU falls to GTT handling.
INAP or CAP IDP message must have the ServiceKey
Parameter with Tag value of 0 and length up to 4 bytes. If it is
not true, MSU falls to GTT handling.
INAP or CAP IDP message must have the EventBCSM
Parameter with Tag value of 28 and length of 1 byte. If it is not
true, MSU falls to GTT handling.
CAP IDP message must have the either CalledPartyNumber or
CalledPartyBCDNumber parameter. If both CalledPartyNumber
and CalledPartyBCDNumber are present, then message is
forward to GTT handling.
If CalledPartyNumber parameter(CdPN) is present, it has Tag
value of 2 and length of 2-18 bytes. If it is not true, MSU falls
to GTT handling.
If CalledPartyBCDNumber(CdPN) parameter is present, it has
Tag value of 0x9F38 and length of 2-18 bytes. If it is not true,
MSU falls to GTT handling.
SK+BCSM value must be found in the CSL SKBCSM list. If it is
not found, MSU falls to GTT handling.
Before performing RTDB lookup, the conditioned TCAP DN
shall be searched against the CSL CCNDC list. If the
conditioned TCAP DN prefix is not matched in CCNDC list, the
MSU falls to GTT handling.
This functionality shall be achieved by using NPP Service
Action.
When CGPACCCK check is to be made against the SCCP
CgPA, the SCCP GTI must indicate GT is present and SCCP
NAI must be International. If not, no SCCP CgPA check is
made and IDP Relay processing is continued without the SCCP
CgPA check.
VSCCP,
SCCPHC
If the TTROPTS:CGPACCCK enum indicates whether the

incoming CgPA needs to be verified against DEFCC. If the
VSCCP,
SCCPHC
DO NOT COPY
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 25 of 68
INTERNAL USE ONLY
values is ALWAYS then the SCCP CGPA DEFCC check is

considered to be turned ON for all incoming messages.
FD-280
FD-300
FD-310
FD-312
FD-315
FD-320
FD-330
FD-340
FD-370
FD-380
FD-122188200
FD-122188210
FD-122188220
FD-122188260
FD-122188270
If the TCAP DN NAI is not National, International or Unknown,

then TCAP DN NAI is considered as Unknown.
Please see appendix B for possible values of NAI.
RTDB lookup shall be first performed in the single entry table. If
not successful, then RTDB lookup in the range table shall be
performed.
When RTDB lookup is successful and the entity_type is either
SP or RN, then the entity_id shall be populated in SP or RN
Formatting Tokens. The message shall then fall to GTT
handling based on the original incoming SCCP CDPA address.
If RTDB lookup is not successful the IDP message shall fall into
GTT handling
The message shall always fall to GTT handling based on the
original incoming SCCP CDPA address. The SCCP CDPA is
never modified within IDP Relay feature. It maybe modified as
part of GTT handling.
If CalledPartyNumber(CdPN) parameter is to be modified, then
1111 shall be used as the filler nibble if the outgoing DN has
odd number of digits.
If CalledPartyBCDNumber(CdPN) parameter is to be modified,
then 1111 shall be used as the filler nibble if the outgoing DN
has odd number of digits.
If in any of the number conditioning above, if the outgoing
number is more then 32 digits, then no digit modification is
made and the message is forwarded for GTT handling.
IDP Relay feature has no impact on the per second transaction
capability of DSM cards.
IDP Relay feature has no impact on EPAP capacity or
capability. There are no new EPAP requirements for IDP Relay
feature.
VSCCP,
SCCPHC
TTROPTS:SNAI shall be used to indicate if incoming CdPN

NAI is used in non-compliant manner. The NAI shall be
changed accordingly before number conditioning.
TTROPTS CGSNAI shall be used to indicate if incoming CgPN
NAI is used in non-compliant manner. The NAI shall be
changed accordingly before number conditioning. This shall be
done if CgPN NP is required.
Calling Number lookup:
CGPNNPRQD Service Action shall indicate if IDPRCGPN
service has to be invoked.
When RTDB lookup using CgPN (calling party) is performed,
the outgoing CgPN is only modified when the entity_type is
same as the TTROPTS:CGNPTYPE. If the entity_type does not
match TTROPTS:CGNPTYPE, or the lookup fails, then the
CgPN is not modified and the processing continues for CDPN.
When CDPN RTDB lookup is successful and the entity_type
(TTROPTS:NPTYPE) match is successful, then the entity_id
VSCCP,
SCCPHC,
DO NOT COPY
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 26 of 68
INTERNAL USE ONLY
shall be treated as the RN, Sp or DN which shall be used to

modify the outgoing CdPN. The message shall then fall to GTT
handling based on the original incoming CdPA address.
When CdPN RTDB lookup is successful but the entity_type
match is not successful, EAGLE 5 ISS shall terminate the IDP
Relay function and simply route the message via standard GTT
to the SCP. The EAGLE 5 ISS shall not modify the INAP/CAP
portion of the message, and shall only modify the MTP and
CdPA modifications if required by standard GTT. This
requirement is applicable when only CdPN lookup is required
for the IDPR number processing logic.
When both CdPN and CgPN RTDB lookups are required, and
the result of the first lookup (CdPN) is unsuccessful, processing
shall continue for the second RTDB lookup(CgPN), however
the first number shall not be altered by the IDP relay service.
Prepaid IDP Relay Feature shall support two different service
rule sets for NPP services IDPRCDPN and IDPRCGPN. These
NPP services support CdPN and CgPN number processing
respectively.
A Service Action LACCK to compare LAC with AC can be
performed, if configured in NPP rule.
FD-122188280
FD-122188290
FD-122188300
FD-122188310
When outgoing TCAP DN is modified, the CdPN NAI is set

based on the provisioned value in NPPSTATE: OFNAI.
FD-122188340
Un-segmented XUDT message type shall be supported for IDP

queries.
FD-122188350
Prepaid IDP Query Relay feature shall support the conditioning

action(s) as mentioned in sections 2.102.10.3
FD-122188360
Prepaid IDP Query Relay feature shall support the Service

action(s) as mentioned in sections 2.10.2and 2.10.4
FD-122188370
FD-122188380
When a SP is returned from the RTDB and is considered a

successful match and RN is requested as part of the outgoing
format, then the outgoing RN can be populated with
TTROPTS:DFLTRN.
All provisioned parameters and values of IDPRCDPN and
IDPRCGPN Service shall be based INAP CS1 protocol.
FD-122188390
IDPRCDPN and IDPRCGPN NPP Services shall support GSM

CAP protocol by internally mapping the required parameters to
work correctly with NPP provisioning rules. Please refer Table
21 for NAI mappings.
NOTE: Please refer Section 2.9for TTROPTS parameter details.
3.4
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
Hardware Requirements
FD Reqt No.
FD-390
Required
or
Optional
(R or O)
R
FD-420

necessary)
Affected GPLs
Prepaid IDP Relay cannot be enabled if TSM cards running

SCCP application are in the system
Prepaid IDP Relay feature runs on the VSCCP or SCCPHC
gpls with DSM/E5-SM4G cards connected with EPAP.
EOAM
DO NOT COPY
EOAM,
VSCCP
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 27 of 68
INTERNAL USE ONLY
SCCCPHC
3.5
User Interface Requirements
Table 11: FD User Interface Requirement Table

FD Reqt No.
FD-400
Required
or
Optional
(R or O)
R
FD-410
FD-425
FD-430
FD-435
FD-440
FD-480
FD-490
FD-510
FD-520
FD-531
FD-532
FD-580
FD-590

necessary)
Affected GPLs
The CHG/ENABLE-CTRL-FEAT commands shall support

provisioning of the Feature Activation Key (FAK) to enable and
turned on the Prepaid IDP Query Relay feature.
The RTRV-CTRL-FEAT commands shall support retrieval of
provisioned Feature Activation Key (FAK) data for the Prepaid
IDP Query Relay feature.
Once Prepaid IDP Relay Feature is enabled, no TSM cards
running the SCCP application can be installed in the system.
The ENT/CHG/DLT/RTRV-SRVSEL commands shall support
provisioning of the TT, SERV,SSN and GTI(N/I/A/) mandatory
service selector parameters.
A new service for SRVSEL command (SERV=IDPR) shall be
defined for IDP Relay feature.
The ENT/CHG/DLT/RTRV-SRVSEL command shall support
provisioning of the NP and NAI optional service selector
parameters.
The ENT/CHG/DLT/RTRV-CSL Common Screening List (CSL)
commands shall be utilized to support provisioning and retrieval
of Country Code + National Destination Code (CCNC) entries.
EOAM
The CCNC screening list shall contain a maximum of 20 Digit

String (DS) entries. Each digit string shall consist of 1 to 6
hexadecimal digits.
commands shall be utilized to support enter, delete, change
and retrieval of Prepaid SCP GT addresses (GT) which shall be
used as an additional service filter for the IDP Relay feature.
The GT list shall contain a maximum of 50 digit string (DN)
entries. Each digit string shall consist of 1 to 15 hexadecimal
digits.
commands shall be utilized to support enter, delete, change
and retrieval of SK+BCSM (SKBCSM) table which shall be
used as an additional service filter for the IDP Relay feature.
The SKBCSM shall contain a maximum of 10 digit string (DN)
entries. Each digit string shall consist of 4 hexadecimal digits.
DEFCC must be provisioned for this feature to be enabled.
STPOPTS DEFCC parameter shall be made available for
provisioning when the IDP Relay feature is enabled.
If GTT is not turned on, IDP Relay cannot be enabled.
This functionality is similar to other features likes
EOAM,
VSCCP
DO NOT COPY
EOAM
EOAM
EOAM,VSCCP
EOAM,
VSCCP
EOAM,
VSCCP
EOAM,
VSCCP
EOAM,
VSCCP
EOAM,
VSCCP
EOAM,
VSCCP
EOAM,
VSCCP
EAOM
EOAM
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 28 of 68
INTERNAL USE ONLY
GPORT/GFLEX/INP/etc.
If LNP is enabled, IDP Relay cannot be enabled.
If VSCCP is the first SCCP application enabled on an DSM/E5SM4G card, the application shall initiate a RTDB download
from EPAP.[user must init the card]
Feature enhancement PR 122188, Flexible IDPR feature
shall support new CHG/RTRV-TTROPTS command set.
EOAM
FD-600
FD-610
FD-1221881000
FD-1221881005
CHG/RTRV-TTROPTS command shall be functional only when

the Prepaid IDP Query Relay feature is enabled.
EOAM
FD-1221881010
The user shall be able to select successful criteria for the CdPN
lookup, to use for ported in or non ported numbers.
The option values for NPTYPE are: SP, RN, RNSP, RNSPDN,
ANYMATCH and ALWAYS.
The default value for NPTYPE is RNSP.
EOAM,
VSCCP,
SCCPHC
FD-1221881020
The user shall be able to select successful criteria for the CgPN
lookup.
The option values for CGNPTYPE are: SP, RN, RNSP,
RNSPDN, ANYMATCH and ALWAYS.
The default value for CGNPTYPE is RNSP.
This shall be used if CgPN lookup is required.
EOAM,
VSCCP,
SCCPHC
FD-1221881070
RTRV-TTROPTS command support for the TTROPTS shall

retrieve all database values of the TTROPTS table parameters.
EOAM
FD-1221881080
The existing range of values of FEATPFX::Prefixnum= 4 shall

be enhanced and moved to CGPACCCK parameter of the
TTROPTS Table. CHG/RTRV-TTROPTS commands to support
provisioning and retrieval of a CGPACCCK which shall support
the values OFF, NON-INTL and ALWAYS. The value
shall be used to determine if the DEFCC check shall be done
on in coming CgPA digits or not.
EOAM,
VSCCP,
SCCPHC
FD-1221881090
The existing range of values of FEATPFX:Prefixnum 3 shall be

enhanced and moved to NPP commands to support
provisioning and retrieval of a outgoing TCAP DN NAI which
shall support the values as listed in 2.9
EOAM,
VSCCP,
SCCPHC
FD-1221881100
The FEATPFX:Prefixnum 1 and FEATPFX:Prefixnum 2 shall be

used to populate TTROPTS:DLM1 and TTROPTS:DLM2
respectively and specified in formatting actions. This
requirement is valid only during the upgrade of the existing
functionality.
EOAM,
VSCCP,
SCCPHC
FD-1221881110
CHG/RTRV-TTROPTS parameters SNAI and CGSNAI shall be

used to indicate the incoming NAI processing for CDPN and
CGPN number conditioning.
FD-1221881140
CHG/RTRV/ TTR-MSG commands shall be supported as
EOAM,
VSCCP,
SCCPHC
EOAM,
VSCCP,
DO NOT COPY
EOAM
EOAM,
VSCCP,
SCCPHC
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 29 of 68
INTERNAL USE ONLY
specified in setcion 7.1
SCCPHC
FD-1221881150
Prepaid IDP Relay feature shall support TST-MSG as specified

in section 7.1
FD-1221881160
CHG/RTRV-TTR-MSG and TST-MSG:FEAT=TTR shall not

function if IDPR FEAT is NOT enabled. MTT Error E4498 Cmd
Rej: The Prepaid IDP Query Relay feature must be enabled
shall be issued, if the above commands are issued, without
enabling the service.
FD-1221881190
MTT Error E4819 Cmd Rej: TESTMSG table entry does not
exist shall be generated for TESTMSG.TBL access failure.
EOAM
FD-1221881200
MTT error E4818 Cmd Rej: Specified TTR message does not
exist shall be generated if the message specified by
CHG/RTRV-TTR-MSG command does not exist.
EOAM,
VSCCP,
SCCPHC
FD-1221881210
IDPRCDPN service must be ENABLED, while activating(turning

on) Prepaid IDP Query Relay feature.
MTT Error E4861 Cmd Rej:IDPR FEAT can NOT be activated
if NPP service status is OFF shall be issued if an attempt is
made to activate IDPR feature without turning on IDPRCDPN
NPP Service.
EOAM,
FD-1221881215
While enabling Prepaid IDP Query Relay feature, an

information message indicating IDPRCDPN NPP service and
possibly the IDPRCGPN service must be enabled for activating
IDPR service shall be issued.
EOAM,
FD-1221881220
MTT Error E4820 Cmd Rej: Failure reading EGLEOPTS Table

shall be issued if the EGLEOPTS Table read fails.
EOAM,
FD-1221881230
Provisioning of TTROPTS table shall only be possible only if

Prepaid IDP Relay feature is enabled. MTT Error E4498 Cmd
Rej: The Prepaid IDP Query Relay feature must be enabled
shall be issued, if an attempt to use CHG/RTRV-TTROPTS
commands before enabling the feature.
EOAM
FD-1221881240
MTT Error E4821 Cmd Rej: If TCAP_TYPE is specified then

NAI should also be specified." shall be issued, if the CHG-TTRMSG is executed with a TCAP-TYPE parameter. CdPN NAI is
needed, if CdPN_digits parameter is provisioned. CgPN NAI is
required, if CgPN_digits parameter is provisioned.
EOAM
FD-1221881250
UIM 1392 IDPRCDPN NPP SERVICE is Disabled shall be

issued if the status of the IDPRCDPN service is OFF while
processing an IDP message. This UIM shall have I1 format
and Output Group GTT.
VSCCP,
SCCPHC
FD-1221881260
UIM 1393 IDPRCGPN NPP SERVICE is Disabledshall be

issued if the status of the IDPRCGPN service is OFF while
processing an IDP message. This UIM shall have I1 format
and Output Group GTT.
VSCCP,
SCCPHC
FD-1221881270
UIM 1392 shall be paced such that no more than one UIM
appears on the console within a minute. The same requirement
applies to UIM 1393 also.
VSCCP,
SCCPHC
Any command examples provided are meant to enhance understanding of the requirements and to provide one suggestion for
names and output. The complete functionality commands shall be described in detail in their associated Command
Specifications. These documents shall also provide the actual parameter names, valid values, and output for the commands.
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 30 of 68
INTERNAL USE ONLY
The user interface requirements related to the DCM card are listed in other Tekelec command specifications shown in the Table
below.
Table 12: Affected Command Specifications
Document
Number
CDT
CDT
3.6
Doc Name
Changes
WS 268
WS 255
NPP command specifications

Changes for CHG/RTRV-TTROPTS, REPT-STAT-SCCP,
CHG/RTRV-TTR-MSG and TST-MSG.
CHG_PREFIX command becomes obsolete for IDPR.
ENT/CHG/DLT/RTRV CSL commands shall not allow del prefix
tables being used for IDPR feature.
Measurement Requirements
4 new pegs are defined for the original Prepaid IDP Relay feature. These pegs shall be added in the existing SYSTOT
measurement report. No new measurement reports are defined for IDP Relay feature.
Table 13: FD Measurement Requirement Table
FD Reqt No.
FD-700
Required
or
Optional
(R or O)
R
FD-710
FD-720
FD-730
FD-740
FD-750

necessary)
Affected
GPLs
A measurement register shall be added to track the number of

MSUs targeted for the IDP Prepaid Query Relay service for
which RTDB lookup is performed.
A measurements register shall be added to track the number of
MSUs processed by the IDP Prepaid Query Relay service for
which the outgoing CDPN was successfully modified.
A single measurements register shall be added to track the
total number of MSUs processed by the IDP Prepaid Query
Relay service for which the RTDB lookup failed or no SP/RN
was found.
A single measurements register shall be added to track the
total number of MSUs processed by the IDP Prepaid Query
Relay service for which an encoding or other error was
encountered.
All registers added in this feature shall be reported in the
systot-stp report.
The new registers for this feature shall be supported on both
the EOAM and the MCP.
EOAM, MCP
EOAM, MCP
EOAM, MCP
EOAM, MCP
EOAM, MCP
EOAM, MCP
Table 14: Affected Measurement documents

Document
Number
TR005822
Doc Name
Changes
EAGLE 5 ISS
Added description of 4 new pegs for systot-stp report.
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 31 of 68
Document
Number
INTERNAL USE ONLY
Doc Name
Changes
Measurements.
3.7
3.7.1
Upgrade Considerations
EGLEOPTS.TBL
Table 15: EGLEOPTS Table definition.

DOS Filename:
Change History:
EGLEOPTS
Rel 39.0 (PR 122188) Flexible IDPR feature
TABLE
BACKUP
TBL
BKP
547
546
Storing IDPR related configurable parameters
CRNT
BKUP
CURR_MTP
BKUP_MTP
SMDATA
BACKUP
64
128
8192
655361
65536
0
0
8192
0
0
65536
0
0
YES
NO
RI_FIX
RI_FIX_SYS
DOS File extensions

DMS Table Id
Comment about table
Partition
DB Audit Subset
Table Class
Number of Entries
Entry Size
DOS File Size
Fixed Disk Space Req.
RMS Cache Space Req.
DRMS Space Req.
System Removable Cartridge Space Req.
Measurements Removable Cartridge Space Req.
Format-disk Initialization
Residency Indicator
Note 1: Considering 64K cluster size
/* EGLEOPTS Table definition */

#define MAX_NUM_VIRTUAL_TBL_ENTRIES
64
enum e_virtual_optn_tbl_id
{
/* All existing Option Tables prior to
** added first. The new virtual tables
*/
enum e_virtual_optn_tbl_id
{
/* All existing Option Tables prior to
** added first. The new virtual tables
*/
EGLE_NETOPTS_VTBL
= 0,
EGLE_STPOPTS_VTBL
= 1,
DO NOT COPY
/* Maximum virtual tables allowed */
Eagle Release 39.0 are

are appended at the end.
Eagle Release 39.0 are

are appended at the end.
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 32 of 68
INTERNAL USE ONLY
EGLE_LNPOPTS_VTBL
= 2,
EGLE_MEASOPTS_VTBL
= 3,
EGLE_MEASOPTS_VTBL_SEG_1 = EGLE_MEASOPTS_VTBL,
/* 3
EGLE_MEASOPTS_VTBL_SEG_2 = EGLE_MEASOPTS_VTBL+1, /* 4
EGLE_XSTPOPTS_VTBL
= 7,
EGLE_INPOPTS_VTBL
= 8,
EGLE_INPOPTS_VTBL_SEG_1
= EGLE_INPOPTS_VTBL,
/* 8
= EGLE_INPOPTS_VTBL+1, /* 9
EGLE_IP_OPTS_VTBL
= 12,
EGLE_IP_OPTS_VTBL_SEG_1
= EGLE_IP_OPTS_VTBL,
/* 12
EGLE_IP_OPTS_VTBL_SEG_2
= EGLE_IP_OPTS_VTBL+1, /* 13
EGLE_GSMOPTS_VTBL
= 14,
EGLE_GSMOPTS_VTBL_SEG_1
= EGLE_GSMOPTS_VTBL,
/* 14
= EGLE_GSMOPTS_VTBL+1, /* 15
EGLE_IS41OPTS_VTBL
= 18,
/* New virtual option table IDs are added here */
EGLE_TTROPTS_VTBL
= 19,
MAX_VIRTUAL_OPTN_TBL_IDS = MAX_NUM_VIRTUAL_TBL_ENTRIES
};
typedef
t_u8
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
t_virtual_optn_tbl_id;
/*****
** IMPORTANT NOTE: Developer needs to make sure that the total number of data
** bytes used in the virtual table does not exceed the EAGLE sys_bfr size
** (487 bytes), while using all 4 segments of the EGLEOPTS table.
*****/
#define EGLEOPTS_MAX_VIRTUAL_TBL_SEGMENTS
4 /* Max num of segments allowed */
#define EGLEOPTS_INITIAL_REV_NUM
0 /* First revision number */
#define EGLEOPTS_MAX_REV_NUM
255 /* MAX revision number allowed */
enum e_virtual_optn_tbl_seg_num
{
EGLEOPTS_SINGLE_SEG
EGLEOPTS_FISRT_SEG
EGLEOPTS_SECOND_SEG
EGLEOPTS_THIRD_SEG
EGLEOPTS_FOURTH_SEG
};
typedef
t_u8
=
=
=
=
=
0,
1,
2,
3,
EGLEOPTS_MAX_VIRTUAL_TBL_SEGMENTS
e_virtual_optn_tbl_seg_num;
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 33 of 68
INTERNAL USE ONLY
#define MAX_VIRTUAL_TBL_ENTRY_DATA_SIZE
125
struct s_egleopts_tbl_entry
{
t_virtual_optn_tbl_id
optn_id;
/* 1 byte */
t_u8
revision_num;
/* 1 byte */
e_virtual_optn_tbl_seg_num segment_num;
/* 1 byte */
union
{
t_ttr_opts_data
idpr_opts_data;
/* New virtual tables will be added here */
t_u8 max_virtual_tbl_data[MAX_VIRTUAL_TBL_ENTRY_DATA_SIZE]; /* 125 bytes */
} u_option_data;
};
/* Total 128 bytes */
typedef s_egleopts_tbl_entry t_egleopts_tbl_entry;
/* Table Structure for TTR Virtual Options Table */

#define
TTR_MAX_PREFIX_DIGITS
16
#define
TTR_MAX_PREFIX_BYTES (TTR_MAX_PREFIX_DIGITS+1)/2
struct s_ttr_digits
{
t_u8
length;
t_u8
digits[TTR_MAX_PREFIX_BYTES];
}
typedef struct s_ttr_digits t_ttr_digits;
struct s_disk_ttr_options_tbl
{
t_u8
nptype;
t_u8
snai;
t_u8
cg_nptype;
t_u8
cg_snai;
t_ttr_digits
dlim1;
t_ttr_digits
dlim2;
t_ttr_digits
dlim3;
t_u8
cgpa_cc_check;
t_ttr_digits
dfltrn;
t_u8
pad[84];
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
1 byte
1 byte
1 byte
1 byte
9 bytes
9 bytes
9 bytes
1 byte
9 bytes
84 bytes
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
}
typedef struct s_disk_ttr_options_tbl t_disk_ttr_options_tbl;
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 34 of 68
3.7.2
INTERNAL USE ONLY
PR 122188 upgrade considerations
There are two options to be considered for Upgrading the existing IDP Query Relay feature to NPP based feature. The first
option is Upgrade only in which the customer shall have the new NPP functionality integrated, once the upgrade is complete.
The NPP rule sets, filters and action sets shall be automatically populated in the NPP database for the existing IDPR message
processing functionality.
The second option is to do an Upgrade, followed by Migration. This approach requires Customer to run a migration after the
upgrade. The existing code shall continue to run after upgrade using the new TTROPTS virtual table. The user can conduct
tests before a decision to integrate with NPP feature is made. This migration option has testing and maintenance related issues.
So, the first approach of Upgrade is considered for the Prepaid IDP Query Relay feature.
1.
2.
3.
4.
5.
6.
Prepaid IDP Query Relay Feature shall have a new TTROPTS table to contain the feature specific values.
Prefix entries in FEATPFX.TBL shall be moved to TTROPTS table.
DELPFX list in CSL.TBL shall be moved to NPP for the number conditioning.
The TTROPTS Table shall have the default values for all the fields as mentioned in Section 2.9
FEATPFX:Prefixnum1, FEATPFX:Prefixnum 2 and FEATPFX:Prefixnum 4 shall be moved to TTROPTS DLM1, DLM2,
and CGPACCCK fields respectively.
FEATPFX:Prefixnum 3 shall be moved to IDPRCDPN NPP action set (OFNAI)
3.7.2.1 Handling of incoming digits Original Prepaid IDP Query Relay feature
The following table describes how the original Prepaid IDP Relay feature handles the incoming digits.
Table 16: IDP Relay Number Conditioning Table
Message
Type
Incoming Address Format

TCAP
DN
NAI
Intern
ational
FEATPFX:Prefixnu
m4?
No
Number
Conditioning
Outgoing Address Format
TCAP DN
Format
<CC><DN>
NAI
None.
Do RTDB Lookup
If
FEATPFX:Prefixnum
3=UNKN
NAI=unknown
Else
NAI=International
Nation
al
If
FEATPFX:Prefixnum
4==ON
<DN>
Add DEFCC.
Do RTDB Lookup
If
FEATPFX:Prefixnum
3=UNKN
NAI=unknown
Else
NAI=National
Unkno
wn
If
FEATPFX:Prefixnum
4==ON
<IEC><CC><DN>
CSL Delete prefix

found,
NAI=unknown
Format
<FEATPFX:Prefixnum
1><CC><RN><DN>
[ If the outgoing NAI is
not international,
FEATPFX:Prefixnum 1
is prefixed ]
< FEATPFX:Prefixnum
2><RN><DN>
[ If the outgoing NAI is
not national,
FEATPFX:Prefixnum 2
is prefixed ]
<IEC><CC><RN><DN>
(P1=International),
remove it,
Do RTDB Lookup
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 35 of 68
Unkno
wn
INTERNAL USE ONLY
If
FEATPFX:Prefixnum
4==ON
<NEC><DN>
CSL Delete prefix

found, (P1=National),
NAI=unknown
<NEC><RN><DN>
NAI=unknown
<RN><DN>
remove it,
Add DEFCC,
Do RTDB Lookup
Unkno
wn
If
FEATPFX:Prefixnum
4==ON
<DN>
no delete prefix found,

Add DEFCC,
Do RTDB Lookup
In EAGLE Release 39.0, the number conditioning shall be handled by NPP for the Prepaid IDP Query Relay. The prefixes shall
be moved to TTROPTS table. The existing rules shall be populated into NPP filters and rules as part of EAGLE upgrade
procedure.
Table 17: TTROPTS Configuration to be performed during Upgrade
Parameter
Value
NPTYPE
RNSP [1]
SNAI
INCOMING
CGNPTYPE
RNSP
CGSNAI
INCOMING
DLM3
NONE
CGPACCCK
Prefixnum 4 value present in

FEATPFX.TBL
If the values is ON, CGPACCCK
is set to NON_INTL
If the values is OFF,
CGPACCCK is set to OFF
DLM1

FEATPFX.TBL
DLM2

FEATPFX.TBL
NOTE[1] : If the source release is ENG 58.41.2 [ EAGLE 37.5.1 ], NPTYPE shall have the default value SP.
The message types described in Table 16 shall be processed by IDPRCDPN Service ruleset as specified in the following table.
Table 18: NPP Configuration to be performed during Upgrade for IDPRCDPN Service
Rule
Filter
Action Set
Message
FNAI
FPFX
FDIGLEN
CA
SA
FA
OFNAI
Type
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 36 of 68
INTERNAL USE ONLY
INTL
SNX
CDPNNP
DLM1
CC
RN(or SP)
SN
If
FEATPFX:P
refixnum
3==UNKN,
OFNAI=
UNKNOW
N
else
OFNAI=IN
TL
NATL
CCDEF
DNX
CDPNNP
DLM2
RN(or SP)
DN
See note [1]
If
FEATPFX:P
refixnum
3==UNKN
OFNAI=
UNKNOW
N
else
OFNAI=NA
TL
UNKNOWN
CSL
DEFPFX
P1=Intern
ational
FPFX
CC[len][2]
SNX
CDPNNP
UNKNOWN
CSL
DEFPFX
P1=Natio
nal
FPFX
CCDEF
SNX
CDPNNP
UNKNOWN
CCDEF
SNX
CDPNNP
FPFX
CC
RN(or SP)
SN
FPPFX
See note [1]
RN(or SP)
SN
RN(or SP)
SN
UNKNO
WN
UNKNO
WN
UNKNO
WN
Note1: If the source Release is EAGLE Release 37.10 and IDPR INTL Normalization feature is ON [14], then if
FEATPFX:Prefixnum3 == UNKN, NPP Formatting Action shall be 00+CC+RN/SP+DN
Note 2: [len] is the actual length of the DEFCC in the source release.
3.7.3
Storage for all Test Messages
IDPR service implements a new table structure, TESTMSG.TBL for storing test messages for various features. This table can
store 100 test massage entries. The largest test message that can be stored in one entry is 450 bytes excluding the Protocol ID
byte. The first byte of the entry is used for storing the Protocol ID. This byte identifies the protocol that is being used by the
test message. Every protocol can store up to 10 messages in this Table. The test messages for every protocol must use
consecutive entries. The first protocol uses entry 1 through entry 10, second service use entries from 11 through 20 and so on.
This table is stored only on OAM card.
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 37 of 68
INTERNAL USE ONLY
Figure 7 TESTMSG Table organization.

Table 19: TESTMSG Table definition.
DOS Filename:
Change History:
TESTMSG
Rel 39.0 (PR 122188) Flexible IDPR feature
DOS File extensions

DMS Table Id
Comment about table
Partition
DB Audit Subset
Table Class
Number of Entries
Entry Size
DOS File Size
Fixed Disk Space Req.
RMS Cache Space Req.
DO NOT COPY
TABLE
BACKUP
TBL
BKP
138
137
Storing Service related Test Messages
CRNT
BKUP
CURR_MTP
BKUP_MTP
SMDATA
BACKUP
100
451
51200
655361
65536
0
0
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 38 of 68
INTERNAL USE ONLY
DRMS Space Req.

System Removable Cartridge Space Req.
Measurements Removable Cartridge Space Req.
Format-disk Initialization
Residency Indicator
0
0
0
YES
RI_FIX
0
0
0
NO
RI_FIX_SYS
Note 1: Considering 64K cluster size
/* Generic TESTMSG.TBL entry structure */

#define MAX_TEST_MSG_SIZE
450
/* Maximum allowed size is 486 bytes */
#define MAX_TEST_PROTOCOLS_SUPPORTED 10 /* Maximum number of features supported */
/* test message protocol_id enum definition */
enum e_protocol_id
{
TTR_TST_MSG_ID = 0,
/* New protocol IDs are added here */
MAX_PROTOCOL_TST_MSG_ID = MAX_TEST_PROTOCOLS_SUPPORTED
}
typedef t_u8 e_protocol_id
struct s_test_msg_tbl_entry
{
e_protocol_id
protocol_id;
union
{
t_idpr_test_msg
idpr_test_msg;
/* New service test messages will be added here */
t_u8 max_test_msg_data[MAX_TEST_MSG_SIZE];
} u_test_msg;
};
typedef s_test_msg_tbl_entry t_test_msg_tbl_entry;
/* 1 byte */
/* 450 bytes */
/*IDPR Test Table Structure */

#define TTR_MAX_SK_DIGITS 8
#define TTR_MAX_SK_BYTES (TTR_MAX_SK_DIGITS+1)/2
struct s_ttr_servicekey
{
t_u8
length;
t_u8
service_key_data[TTR_MAX_SK_BYTES];
}
typedef struct s_ttr_servicekey t_ttr_servicekey;
#define TTR_MAX_BCSM_DIGITS 2
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 39 of 68
INTERNAL USE ONLY
#define TTR_MAX_BCSM_BYTES (TTR_MAX_BCSM_DIGITS+1)/2

struct s_ttr_bcsm_digits
{
t_u8
length;
t_u8
digits[TTR_MAX_BCSM_BYTES];
}
typedef struct s_ttr_bcsm_digits t_ttr_bcsm_digits;
typedef struct
{
t_u8
t_u8
t_ttr_servicekey
t_ttr_bcsm_digits
t_u8
t_u8
t_sccp_gt_address
t_u8
t_u8
t_sccp_gt_address
t_u8
t_ttr_digits
t_u8
t_ttr_digits
t_u8
}
t_ttr_test_msg;
msg;
tcap_type;
service_key;
bcsm_digits;
cgpa_gt;
cgpa_gt_nai;
cgpa_gt_address;
cdpa_gt;
cdpa_gt_nai;
cdpa_gt_address;
CdPN_nai;
CdPN_digits;
CgPN_nai;
CgPN_digits
pad[393];
/* 1 byte
*/
/* 1 byte
*/
/* 5 bytes
*/
/* 2 byte
*/
/* 1 byte
*/
/* 1 byte
*/
/* 12 bytes
*/
/* 1 byte
*/
/* 1 byte
*/
/* 12 bytes
*/
/* 1 byte
*/
/* 9 bytes
*/
/* 1 byte
*/
/* 9 bytes
*/
/* 393 bytes */
Table 20: FD Upgrade Requirement Table

FD Reqt
No.
FD1221881500
Required or
Optional (R or O)
R
User Interface Requirement Description (and any

additional comments if necessary)
Upon completion of upgrade, the TTROPTS:DLM1 shall be
set to the Prefixnum1 value present in FEATPFX table.
FD1221881510
Upon completion of upgrade, the TTROPTS table:DLM2

shall be set to the Prefixnum2 value present in FEATPFX
table.
FD-
Upon completion of upgrade, the NPP:OFNAI shall be set
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
Affected
GPLs
EOAM,
VSCCP,
SCCPHC
EOAM,
VSCCP,
SCCPHC
EOAM,
3.4
Page 40 of 68
1221881520
INTERNAL USE ONLY
to the Prefixnum3 value present in FEATPFX table.
FD1221881530
Upon completion of upgrade, the TTROPTS

table:CGPACCCK shall be set to the Prefixnum4 value
present in FEATPFX table.
FD1221881540
Upon completion of upgrade, the TTROPTS table entry

(other than the fields mentioned above) shall be set to the
default parameter values as mentioned in Section 2.9.
FD1221881550
Upon completion of upgrade, the NPP table entry shall be

populated with the filters and actions required for the
current IDPR functionality. Please refer Section 2.6.
FD1221881560
Upgrade from EAGLE releases described by Release 39.0

PFX shall be supported.
FD1221881570
Upon completion of upgrade, the IDPR DELPFX entries in

CSL table with P1=International or National, shall be
moved to NPP rules.
FD1221881580
Upon completion of upgrade, the IDPR DELPFX entries in

CSL table with P1=International or National, shall be
deleted.
FD1221881590
Upon completion of upgrade, the FEATPFX table entries

corresponding to IDPR table shall be removed.
CHG/RTRV-PREFIX commands for IDPR feature shall be
obsolete.
4.0
VSCCP,
SCCPHC
EOAM,
VSCCP,
SCCPHC
EOAM,
VSCCP,
SCCPHC
EOAM,
VSCCP,
SCCPHC
EOAM,
VSCCP,
SCCPHC
EOAM,
VSCCP,
SCCPHC
EOAM,
VSCCP,
SCCPHC
EOAM,
VSCCP,
SCCPHC
PERFORMANCE
This feature has no impact on the performance of LIM cards or the service module cards. Impacts on the system performance
for Calling Party(CgPN) lookups shall be quantified and documented.
5.0
RELIABILITY
No impact on EAGLE 5 ISS reliability due to this feature.
6.0
SERVICEABILITY
An example for feature provisioning is provided to show the order of provisioning. Note that the customer specific data in the
example is underlined. The IDPR feature defines IDPRCDPN and IDPRCGPN service while developing the service. All data
provisioned for NPP are based on INAP CS1 protocol. This means the NPP FNAI mappings are based on INAP CS1 protocol
The Prepaid IDP Relay feature shall map NAIs for the CAP protocol internally within the code, before invoking NPP functions.
The numerical values mapped to NPPs chg-npp-serv are given below. The values not provisioned are treated as UNKNOWN
by NPP service.
Table 21: NAI value mappings for Prepaid IDP Service Provisionig.
CHG-NPP-SERV
NAI
intl
DO NOT COPY
Values as per INAP

CS1. This shall be the
default provisioned
value for IDPRCDPN
and IDPRCGPN
services
4
CAP protocol NAI value.

This value is mapped to
corresponding INAP CS1
value before invoking NPP
functions.
natl
nai1
Hard copies of this document are
for reference only. The
Title:
NONE
NONE
Doc
No.:
341058866.doc
Rev No:
nai2
NONE
NONE
nai3
NONE
NONE
3.4
Page 41 of 68
6.1
INTERNAL USE ONLY
Service provisioning sequence examples
1. Entersystemserialnumberandlock:
ent-serial-num:serial=NT00001659
ent-serial-num:serial=NT00001659:lock=yes
Note: The serial number shown above is for example only. Contact Tekelec Sales for the customer site serial number.
2. EnablethePrepaidIDPQueryRelayfeatureandDEFCC:
enablectrlfeat:partnum=893016001:fak=CONTACT_TEKELEC_SALES
3. EnabletheDEFCC(ifnotalreadypresent/enteredduetoanotherfeature)
chgstpopts:DEFCC=48
4. Thefeaturemaynowbeturnedonusingthechangecontrolfeaturecommand:
chgctrlfeat:partnum=893016001:status=ON
5. AssigntheserviceselectorforPrepaidIDPQueryRelayfeature.
entsrvsel:gtii=4:tt=20:np=e164:nai=intl:serv=idpr:ssn=*
Therecanbemultipleentriesforthiscommand.
6. OptionalEnterthenationalinsertPrefixintheTTROPTStable:
chgttropts:DLM2=0
7. OptionalControlforNAIintheincomingTCAPDN
chgttropts:snai=Unknown
8. OptionaliftheSCCPCGPADEFCCcheckisNONINTLorOFForALWAYS
chgttropts:IDPR=always
9. EnterDigitString(DS)entriesintheCC+NDClist
entcsl:pn=893016001:list=ccnc:ds=48
Thereshouldbeminimumofoneentryforthefeaturetowork.
TheentrycanbejustwithcountrycodesamevalueasinDEFFCCparameter.
10.
EnterDigitString(DS)entriesintheGTlist.
entcsl:pn=893016001:list=gt:ds=456
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 42 of 68
INTERNAL USE ONLY
ThisdigitshouldmatchthecalledpartynumberintheSCCPCDPA.
11.
EnterDigitString(DS)entriesintheSKBCSMlist.
entcsl:pn=893016001:list=skbcsm:ds=h0x0000001402
ThisdigitshouldmatchtheservicekeyvalueandtheeventBCSMvaluefromtheIDP
message.
12.
ProvisiontheNAImappingforIDPRCDPNservice
chgnppserv:srvn:IDPRCDPN:intl=4:natl=3:
13.
OptionalProvisiontheNAImappingforIDPRCGPNservice
chgnppserv:srvn:IDPRCGPN:intl=4:natl=3:nai1=2
14.
Defineanewactionsets
entnppas:asn=localcall:ca1=addcc:ca2=ACLAC:ca3:sn:sa1=CDPNNP:
fa1=cc,fa2=rn:fa3:ac:fa4=sn:ofnai=intl
NOTE:Therewillbemanyactionsetstobedefinedbasedontherequirements
15.
Defineandaddaruletoservice
Entnppsrs:srvn=IDPRCDPN:fnai=intl:fpfx=*:fdl=8:asn=localcall
NOTE:Therewillbemanyrulestobedefinedbasedontherequirements
16.
TurntheIDPRCDPNservicestatusON
chgnppserv:srvn=IDPRCDPN:status=on
17.
OptionalTurntheIDPRCGPNservicestatusON
chgnppserv:srvn=IDPRCGPN:status=on
7.0
TESTABILITY
AUT code shall be added which can be compiled for lab testing to see various function calls and values.
EPAP shall be required for testing the feature on EAGLE.
7.1
Prepaid IDP Query Relay: PR 122188 Testability
A trace tool shall be implemented to allow customers and Tekelec Support Personnel to test the Prepaid IDP Query Relay
feature. The tool shall allow TTR messages (CS1 or CAP initially) to be fed into the system, and display information related to
all NPP filters, rules and formatting applied to the message. The TTR message shall flow through already defined IDPRCDPN
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 43 of 68
INTERNAL USE ONLY
and IDPRCGPN services and display the results on console. The trace tool shall also be used for debugging and tracing the
changes introduced to the incoming TCAP Called Party(CdPN) and/or Calling Party(CgPN) digits.
Prepaid IDP Query Relay feature shall support up to 10 TTR messages for test purpose. Initial value of the parameters of all 10
messages are as given in Table 22. All parameters given in Table 22 shall be modified using CHG-TTR-MSG command. Note
that CdPN represents either INAP CS1 CalledPartyNumber parameter or GSM Camel Application Part (CAP)
CalledPartyBCDNumber parameter of the TTR message.
Table 22: TTR Test table parameters
Parameter
7.1.1
Range
Default Value
sk
8 digits fixed
00006b00
bcsm
2 digits fixed
02 (Info Collected)
tcap_type
enum : INAP/CAP
INAP
cgpagt
0..15
2 (GT with Tr Type)
cgpagtnai
0..127
4 (International)
cgpadgts
Digit string 1..15 digits
01234567890abcde
cdpagt
0..15
2 (GT with Tr Type)
cdpagtnai
0..127
4 (International) INAP
cdpadgts
digit string 1..15 digits
01234567890abcde
CdPNnai
0..127
4 (International)
CdPNdgts
01234567890abcdef
CgPNnai
0..127
4 (International)
CgPNdgts
01234567890abcdef
ACTIVE
YES, NO
NO
CHG-TTR-MSG
There shall be a CHG-TTR-MSG command to modify the parameters of an existing TTR message. This command shall have
the following mandatory and optional parameters.
Table 23: Parameters supported by CHG-TTR-MSG command
Parameter
Mandatory/
Optional
Range
msgn
1..10
tcap_type
INAP or CAP
sk
8 digits
bcsm
2 digits
cgpagt
0..15
cgpagtnai
0..127
cgpadgts
Hex digit string: 1..15 digits
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 44 of 68
INTERNAL USE ONLY
cdpagt
0..15
cdpagtnai
0..127
cdpadgts
CdPNnai
0..127 [see Note 1]
CdPNdgts
CgPNnai
0..127 [see Note 1]
CgPNdgts
ACTIVE
YES, NO
RESET
YES, NO
Note 1: Valid values for CAP messages are 0..7
Initial value of the ACTIVE parameter of all messages shall be NO. Only messages that have ACTIVE value set to
YES shall only be sent to the network card.
If CHG-TTR-MSG command is issued by RESET value set with YES value, all parameters of the MSGN message
shall be reset to the default values shown in Table 22.
RESET parameter is mutually exclusive with all other optional parameters. When RESET is one of the parameters in
the CHG-TTR-MSG, no other optional parameters shall be present in the command. If other parameters are present
MTT Error No other optional parameters shall be present if RESET is one of the parameters shall be issued.
7.1.2
RTRV-TTR-MSG
There shall be a RTRV-TTR-MSG command to view the contents of the TTR test message parameters. This command shall
have the following parameters. Details of the message are displayed irrespective of the value of the ACTIVE parameter.
Table 24: Parameters supported by RTRV-TTR-MSG command.
Mandatory/
Optional
Parameter
msgn
Range
1..10
This command displays the configurable IDP parameters in the format depicted by Figure 8.
1
12345678901234567890123456789012345678901234567890123456789012345678901234567890
MSG = XX
TCAP_TYPE = INAP
SK = 12345678
ACTIVE = YES
BCSM = FA
CGPA_GT = 2
CGPA_GT_NAI = XXX
CGPA =1234567890ABCDEF
CDPA_GT = 2
CDPA_GT_NAI = XXX
CDPA = 1234567890ABCDEF
CGPN_NAI = 2
CGPN = 1234567890ABCDEF1234567890ABCDEF
CDPN_NAI = 2
CDPN = 1234567890ABCDEF1234567890ABCDEF
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 45 of 68
INTERNAL USE ONLY
Figure 8: RTRV-TTR-MSG display format
7.1.3
TST-MSG
TST-MSG command shall be used for sending a message provisioned under TSTMSG Table to an EAGLE Service Feature
indicated by the FEAT parameter. The purpose of the test message that is sent to the EAGLE Service Feature is not for creating
a new raw MSU and testing. It is used only to modify the internal data structures of the Service Feature and to study the call
flow behavior when a message with the specified parameters is injected into the call path. The test message shall never be sent
out to the network. The format of the TST-MSG shall be as below.
TST-MSG: LOC=<loc>:PROT=<TTR>:MSGN=<MESSAGE #>: FEAT=<TTR>:[MODE=<BRIEF/FULL>]
TST-MSG Parameters:
LOC: The location of the network card where the test message is sent to.
PROT: The type of the test message. The PROT shall be mnemonic name of the PROT message.
There can be a maximum of 10 PROT message types in the TSTMSG Table. Flexible IDPR Relay Feature uses a
message type PROT=TTR. Please refer section 7.1.1for more details on this message. There will be new message
types defined and added by other features into the TSTMSG Table.
MSGN: The message number of the test message within the PROT type messages.
FEAT: EAGLE Service Feature that process the message on the network card. The FEAT shall be mnemonic name of
the Eagle Service Feature.
Table 25 : TST-MSG parameters.

Parameter
Mandatory/
Optional
Default
Range
Char string [max 10 chars]. This

will be mnemonic name.
No default value
MSGN
1..10
No default value
LOC
4 digit EAGLE card number
No default value
Char string [max 10 chars]. This

will be mnemonic name.
No default value
BRIEF/FULL
BRIEF
PROT
FEAT
MODE
Only the messages with the ACTIVE parameter set to YES value shall be sent to the Feature.
If the MSGN selected by the TST-MSG command has an ACTIVE parameter value set to NO, a MTT Error Only
messages with ACTIVE=YES value shall be sent to the Feature shall be displayed.
There shall be corresponding MTT Errors for all missing or invalid mandatory parameters in the TST message. These
errors shall be:
1. Missing mandatory PROT parameter
2. Missing mandatory MSGN parameter
3. Missing mandatory FEAT parameter
4. Missing mandatory LOC parameter
If the FEAT parameter specified is TTR and the PROT parameter is not TTR, an MTT Error TEST MSG
protocol does not match with the FEAT specified shall be issued.
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 46 of 68
INTERNAL USE ONLY
The command shall display the following processing information in BRIEF MODE. This is the default output mode. See
Figure 9..
1
12345678901234567890123456789012345678901234567890123456789012345678901234567890
TST-NPP-MSG - RESULT
====================
MSG = XX
TCAP_TYPE = INAP
SCCP
CGPA_GT = 2
CGPA_GT_TR_TYPE = 17
CGPA_GT_NAI = XXX
CGPA = 0123456789ABCDE
CDPA_GT = 2
CDPA_GT_TR_TYPE = 17
CDPA_GT_NAI = XXX
CDPA = 0123456789ABCDE
TCAP
SK = 12345678
BCSM = FA
CGPN_NAI = 2
CDPN_NAI = 2
CDPN NPP PROCESSING

SERVICE NAME = IDPRCDPN
SERVICE STATUS = ON/OFF
INC DIGITS = 1234567890ABCDEF123456789ABCDEF

NAI = 255 FNAI = NATL FDIGLEN = 16
MATCHING RULE
FNAI = NATL FDIGLEN = 16 FPFX = 1234567890ABCDEF
ACTION SET NAME = ACTSETNAME
CONDITIONING RESULT = SUCCESS/FAIL
INC
DIGITS = 1234567890ABCDEF123456789ABCDEF
COND DIGITS = 1234567890ABCDEF123456789ABCDEF

FORMATING RESULT = SUCCESS/FAIL
OUTG DIGITS = 1234567890ABCDEF123456789ABCDEF
OUTG FNAI = INTL
CGPN NPP PROCESSING
SERVICE NAME = IDPRCGPN

MATCHING RULE
INC

DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 47 of 68
INTERNAL USE ONLY
OUTG FNAI = INTL
Figure 9: TST-MSG output in BRIEF format
When MODE=FULL, TST-MSG outputs all NPP actions executed and the corresponding changes to digits. See Figure 10.
Note that the NPP processing details (CAs, SAs, FAs) are displayed in the same format as supplied by NPP[10].
1
12345678901234567890123456789012345678901234567890123456789012345678901234567890
TST-NPP-MSG - RESULT
====================
MSG = XX
TCAP_TYPE = INAP
SCCP
CGPA_GT = 2
CGPA_GT_TR_TYPE = 17
CGPA_GT_NAI = XXX
CGPA = 0123456789ABCDE
CDPA_GT = 2
CDPA_GT_TR_TYPE = 17
CDPA_GT_NAI = XXX
CDPA = 0123456789ABCDE
TCAP
SK = 12345678
BCSM = FA
CGPN_NAI = 2
CDPN_NAI = 2
CDPN NPP PROCESSING

SERVICE NAME = IDPRCDPN

MATCHING RULE
CA1 = CA1NAMEXXX
CA2 = CA2NAMEXXX
CA3 = CA2NAMEXXX
CA4 = CA2NAMEXXX
CA5 = CA2NAMEXXX
CA6 = CA2NAMEXXX
CA7 = CA2NAMEXXX
CA8 = CA2NAMEXXX
INC

SERVICE APPLICATION
SA1 = SA1NAMEXXX
EXECUTED = Y/N FORMAT IND = Y/N
SA2 = SA2NAMEXXX
SA3 = SA2NAMEXXX
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 48 of 68
INTERNAL USE ONLY
SA4 = SA2NAMEXXX
SA5 = SA2NAMEXXX
SA6 = SA2NAMEXXX
SA7 = SA2NAMEXXX
SA8 = SA2NAMEXXX

FA1
= FA1NAMEXXX
FA2
= FA2NAMEXXX
FA3
= FA2NAMEXXX
FA4
= FA2NAMEXXX
FA5
= FA2NAMEXXX
FA6
= FA2NAMEXXX
FA7
= FA2NAMEXXX
FA8
= FA2NAMEXXX
FA9
= FA2NAMEXXX
FA10 = FA2NAMEXXX
FA11 = FA2NAMEXXX
FA12 = FA2NAMEXXX
OUTG FNAI = INTL
CGPN NPP PROCESSING
SERVICE NAME = IDPRCGPN

MATCHING RULE
CA1 = CA1NAMEXXX
CA2 = CA2NAMEXXX
CA3 = CA2NAMEXXX
CA4 = CA2NAMEXXX
CA5 = CA2NAMEXXX
CA6 = CA2NAMEXXX
CA7 = CA2NAMEXXX
CA8 = CA2NAMEXXX
INC

SERVICE APPLICATION
SA1 = SA1NAMEXXX
SA2 = SA2NAMEXXX
SA3 = SA2NAMEXXX
SA4 = SA2NAMEXXX
SA5 = SA2NAMEXXX
SA6 = SA2NAMEXXX
SA7 = SA2NAMEXXX
SA8 = SA2NAMEXXX
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 49 of 68
INTERNAL USE ONLY

FA1
= FA1NAMEXXX
FA2
= FA2NAMEXXX
FA3
= FA2NAMEXXX
FA4
= FA2NAMEXXX
FA5
= FA2NAMEXXX
FA6
= FA2NAMEXXX
FA7
= FA2NAMEXXX
FA8
= FA2NAMEXXX
FA9
= FA2NAMEXXX
FA10 = FA2NAMEXXX
FA11 = FA2NAMEXXX
FA12 = FA2NAMEXXX
OUTG FNAI = INTL
Figure 10: TST-MSG output in FULL format
8.0
LIMITATIONS
None.
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 50 of 68
9.0
INTERNAL USE ONLY
PEER REVIEW CHECKLIST
Do not delete this checklist. It shall be used at each peer review to ensure that all
necessary attributes of the document are included. The moderator is responsible for
asking these questions to the quorum prior to the document being voted on.
Table 26: Document Approval Checklist
Item
Compliance
(Yes, No or N/A)
Was the template used and are all sections included (NA sections are so noted, not
deleted)?
Do the version numbers in the change history, header and footer of this document match
the version number in the document control system?
Were the correct quorum members present or represented per the Peer Review
procedure?
Are all applicable TEKELEC reference documents are cited?
Are all applicable FRS requirements documented in the FRS Compliance Matrix section?
Are the FD requirements correctly numbered and documented?
Are there any patentable ideas that exist as a result of the specification or design work in
this document?
Is there an explanation in the Limitations section of all FD requirements that were not
fully compliant?
Are the requirements testable?
Were soak time requirements addressed in the performance section?
Are there any changes to existing outputs or new error outputs that may impact the
customer? If so, are they identified and appropriately documented in the user interface
and serviceability sections?
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 51 of 68
APPENDIX A:
INTERNAL USE ONLY
SAMPLE INCOMING INITIALDP (CAP) MESSAGE
Decoded signal unit

# User:
djancero
# Date:
18-07-2005 13:46:45
# Octets: 225
-------------------------------------------------------------------------------Octet001 ITU-T SS7
Count=000001 Time=18-07-2005 13:44:36:024
-------------------------------------------------------------------------------11001111 BIB/BSN
(207) 1/79
10101001 FIB/FSN
(169) 1/41
..111111 SU type/length
(63) MSU63
00...... Spare
0
-------------------------------------------------------------------------------Octet004 Service information octet
-------------------------------------------------------------------------------....0011 Service indicator
(3) SCCP Signalling Connection Control Part
..00.... Message priority
0
10...... Network indicator
(2) N National network
-------------------------------------------------------------------------------Octet005 Routing label
-------------------------------------------------------------------------------........ DPC
4959 SCP_09
........ OPC
4752 MSC_KATOD
1110.... SLS
14
-------------------------------------------------------------------------------Octet009 Message type
-------------------------------------------------------------------------------00001001 Message type
(9) UDT
Unitdata
-------------------------------------------------------------------------------Octet010 SCCP Protocol Class parameter
-------------------------------------------------------------------------------....0001 Protocol class
(1) Class 1
1000.... Message handling
(8) Return message on error
00000011 Ptr -> Called number
3
00001110 Ptr -> Calling #
14
00011001 Pointer -> Data
25
-------------------------------------------------------------------------------Octet014 SCCP Called Party Address parameter
-------------------------------------------------------------------------------00001011 Parameter length
11
.......0 Sgnl pt code bit
(0) SPC not present
......1. Subsystem # bit
(1) SSN present
..0100.. Global title ind
(4) Global title incl. translation type, numbering plan, encoding scheme
& addr nature
.0...... Routing bit
(0) Global title based routing
0....... Reserved natl use
0
11110001 Subsystem number
(241) SINAP
Siemens INAP 7M+
00000000 Translation
(0) unknown
....0001 Encoding scheme
(1) BCD odd
0001.... Numbering plan
(1) ISDN (Telephony) numbering plan (Rec. E.164/E.163)
.0000100 Nature of address
(4) International number
0....... Spare
0
........ Address signals
48602009090
0000.... Filler
0
-------------------------------------------------------------------------------Octet026 SCCP Calling Party Address parameter
11
.......0 Sgnl pt code bit
(0) SPC not present
......1. Subsystem # bit
(1) SSN present
..0100.. Global title ind
(4) Global title incl. translation type, numbering plan, encoding scheme
& addr nature
.0...... Routing bit
(0) Global title based routing
0....... Reserved natl use
0
11110001 Subsystem number
(241) SINAP
Siemens INAP 7M+
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 52 of 68
INTERNAL USE ONLY
00000000 Translation
(0) unknown
....0001 Encoding scheme
(1) BCD odd
0001.... Numbering plan
(1) ISDN (Telephony) numbering plan (Rec. E.164/E.163)
0....... Spare
0
48602001220
0000.... Filler
0
-------------------------------------------------------------------------------Octet038 SCCP Data parameter
187
01100010 Tag
(98) BGN Begin, constructor, application-wide
10000001 Length
129
........ Long form length
184
-------------------------------------------------------------------------------Octet042 OriginatingTransactionID
-------------------------------------------------------------------------------...01000 Tag
(8) OriginatingTransactionID
010..... Class and form
(2) Application-wide, primitive
00000100 Length
4
........ Originating ID
8B304E7D
-------------------------------------------------------------------------------Octet048 DialoguePortion
-------------------------------------------------------------------------------...01011 Tag
(11) DialoguePortion
(3) Application-wide, constructor
00011101 Length
29
-------------------------------------------------------------------------------Octet050 External
-------------------------------------------------------------------------------...01000 Tag
(8) External
(1) Universal, constructor
00011011 Length
27
-------------------------------------------------------------------------------Octet052 Object identifier
-------------------------------------------------------------------------------...00110 Tag
(6) Object identifier
(0) Universal, primitive
00000111 Length
7
00000000 Organization
(0) itu-t recommendation
00010001 q
(17) Q
........ 773 (X'305)
773
00000001 as(1)
1
00000001 Protocol data unit
(1) dialogue PDU(1)
00000001 version(1)
1
-------------------------------------------------------------------------------Octet061 Single ASN.1-Type
-------------------------------------------------------------------------------10100000 Single-ASN.1-typeTag
(160) Single ASN.1-Type
00010000 Length
16
-------------------------------------------------------------------------------Octet063 DialogueRequest
-------------------------------------------------------------------------------...00000 Tag
(0) DialogueRequest
00001110 Length
14
-------------------------------------------------------------------------------Octet065 Application-context-name
-------------------------------------------------------------------------------...00001 Tag
(1) Application-context-name
(5) Context-specific, constructor
00001100 Length
12
-------------------------------------------------------------------------------Octet067 Object Identifier
-------------------------------------------------------------------------------...00110 Tag
(6) Object identifier
00001010 Length
10
00101011 Protocol
(43) iso-identified-organization (1) (3)
00001100 Subprotocol
(12) ecma (12)
00000010 Domain
(2) member-company (2)
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 53 of 68
INTERNAL USE ONLY
........ Units
(1107) siemens-units (1107)
00000011 Value
(3) oen (3)
00000011 Network
(3) inap (3)
00000000 AC Name
(0) ac (0)
00000000 Service
(0) cs1-ssp-to-scp (0)
00010110 Version
(22) UnexpectedValue
-------------------------------------------------------------------------------Octet079 ComponentPortion
-------------------------------------------------------------------------------...01100 Tag
(12) ComponentPortion
10000001 Length
129
144
-------------------------------------------------------------------------------Octet082 Invoke
-------------------------------------------------------------------------------...00001 Tag
(1) Invoke
10000001 Length
129
141
-------------------------------------------------------------------------------Octet085 InvokeID
-------------------------------------------------------------------------------...00010 Tag
(2) InvokeID
00000001 Length
1
00000001 InvokeID
01
-------------------------------------------------------------------------------Octet088 Operation Code
-------------------------------------------------------------------------------...00010 Tag
(2) Local
00000001 Length
1
........ Operation Code
(0) IDP InitialDP
-------------------------------------------------------------------------------Octet091 Parameter Sequence
-------------------------------------------------------------------------------...10000 Tag
(16) Parameter Sequence
(1) Universal, constructor
10000001 Length
129
132
-------------------------------------------------------------------------------Octet094 ServiceKey
-------------------------------------------------------------------------------...00000 Tag
(0) ServiceKey
(4) Context-specific, primitive
00000001 Length
1
........ Service key
107
-------------------------------------------------------------------------------Octet097 CallingPartyNumber
-------------------------------------------------------------------------------...00011 Tag
(3) CallingPartyNumber
00001000 Length
8
1....... Odd/even
(1) odd number of address signals
......11 Screening Indicator
(3) Network provided
....00.. Presentation?
(0) Presentation allowed
.001.... Numbering plan
(1) ISDN (Telephony) numbering plan (Rec. E.164)
0....... Number Incomplete?
(0) Number complete
48889021750
0000.... Filler
0
-------------------------------------------------------------------------------Octet107 CallingPartysCategory
-------------------------------------------------------------------------------...00101 Tag
(5) CallingPartysCategory
00000001 Length
1
11100000 CallngPartyCategory
(224) Reserved for national use
-------------------------------------------------------------------------------Octet110 LocationNumber
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 54 of 68
INTERNAL USE ONLY
-------------------------------------------------------------------------------...01010 Tag
(10) LocationNumber
00001001 Length
9
(3) national (significant) number
0....... Odd/even
(0) even number of address signals
......11 Screening Indicator
(3) network provided
....01.. Presentation?
(1) Presentation restricted
.001.... Numbering plan
(1) ISDN (Telephony) numbering plan (Rec. E.164)
1....... Internal network #
(1) Routing to internal network number not allowed
03200000051511
-------------------------------------------------------------------------------Octet121 HighLayerCompatibility
-------------------------------------------------------------------------------...10111 Tag
(23) HighLayerCompatibility
00000010 Length
2
......01 Presentn Method
(1) HighLayerProtocolProfile
...100.. Interpretation
(4) FirstHighLayerCharIDToBeUsedInTheCall
.00..... Coding Standard
(0) GSM standardized coding
1....... Extension Bit
1
.0000001 HighLayerCharID
(1) Telephony
(1) last octet
-------------------------------------------------------------------------------Octet125 ForwardCallIndicators
-------------------------------------------------------------------------------...11010 Tag
(26) ForwardCallIndicators
00000010 Length
2
.......0 Nat'l/International
(0) Call to be treated as a national call
.....00. End-to-end method
(0) No end-to-end method available
....0... Interworking
(0) No interworking encountered (No. 7 signalling all the way)
...0.... End-to-end info
(0) No end-to-end information available
..1..... ISUP indicator
(1) ISDN user part used all the way
00...... ISUP preference
(0) ISDN user part preferred all the way
.......1 Orig ISDN access
(1) Originating access ISDN
.....00. SCCP method
(0) No indication
....0... Spare
0
0000.... ReservedForNat'lUse
0
-------------------------------------------------------------------------------Octet129 BearerCapability
-------------------------------------------------------------------------------...11011 Tag
(27) BearerCapability
00000101 Length
5
-------------------------------------------------------------------------------Octet131 Bearer Cap
-------------------------------------------------------------------------------...00000 Tag
(0) Bearer Cap
00000011 Parameter length
3
-------------------------------------------------------------------------------Octet133 User service info octet 3
-------------------------------------------------------------------------------...00000 Transfer capability
(0) Speech
.00..... Coding standard
(0) ITU-T standardized coding, as described below
1....... Extension bit
(1) Last Octet
-------------------------------------------------------------------------------...10000 Transfer rate
(16) 64 kbit/s
.00..... Transfer mode
(0) circuit mode
(1) Last Octet
-------------------------------------------------------------------------------...00011 Layer 1 protocol
(3) Recommendation G.711 A-law
.01..... Layer 1 Identifier
(1) User information layer 1 protocol
(1) Last Octet
-------------------------------------------------------------------------------Octet136 EventTypeBCSM
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 55 of 68
INTERNAL USE ONLY
-------------------------------------------------------------------------------...11100 Tag
(28) EventTypeBCSM
00000001 Length
1
00000010 EventTypeBCSM
(2) collectedInfo
-------------------------------------------------------------------------------Octet139 MapIMSI
-------------------------------------------------------------------------------...11111 Tag
(31) Extended Tag
........ Extended Tag
(50) MapIMSI
00001000 Length
8
........ IMSI
260021660021755F
-------------------------------------------------------------------------------Octet150 LocationInformation
-------------------------------------------------------------------------------...11111 Tag
(31) Extended Tag
(52) LocationInformation
00100001 Length
33
-------------------------------------------------------------------------------Octet153 AgeOfLocationInformation
-------------------------------------------------------------------------------...00010 Tag
(2) Integer
00000001 Length
1
........ Value
0
-------------------------------------------------------------------------------Octet156 GeographicalInformation
-------------------------------------------------------------------------------...00000 Tag
(0) GeographicalInformation
00001000 Length
8
....0000 Spare
0
0001.... Type of Shape
(1) Ellipsoid point with uncertainty circle
0....... Sign of Latitude
(0) North
........ Degrees of Latitude
4666614
........ Degrees of Longitude
4651532
.0111000 Uncertainty Code
(56) 2.06 km
0....... Spare
0
-------------------------------------------------------------------------------Octet166 VLR-Number
-------------------------------------------------------------------------------...00001 Tag
(1) VLR-Number
00000111 Length
7
....0001 Numbering Plan
(1) ISDN/Telephony Number Plan (REC E.164)
.001.... Nature of Address
(1) International Number
(1) Not Extended
48602002220F
-------------------------------------------------------------------------------Octet175 CellIdOrLAI
-------------------------------------------------------------------------------...00011 Tag
(3) CellIdOrLAI
00001001 Length
9
-------------------------------------------------------------------------------Octet177 CellIDFixedLength
-------------------------------------------------------------------------------...00000 Tag
(0) CellIDFixedLength
00000111 Length
7
........ Mobile Country Code
260
1111.... Filler
15
........ Mobile Network Code
02
........ Location Area Code
7255
........ Cell Identity
14281
-------------------------------------------------------------------------------Octet186 Ext-BasicServiceCode
-------------------------------------------------------------------------------...11111 Tag
(31) Extended Tag
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 56 of 68
INTERNAL USE ONLY

(53) Ext-BasicServiceCode
00000011 Length
3
-------------------------------------------------------------------------------Octet189 Ext-Teleservice
-------------------------------------------------------------------------------...00011 Tag
(3) Ext-Teleservice
00000001 Length
1
00010001 Ext-Teleservice Code
(17) Telephony (TeleSvcGrp # 1)
-------------------------------------------------------------------------------Octet192 CallReferenceNumber
-------------------------------------------------------------------------------...11111 Tag
(31) Extended Tag
(54) CallReferenceNumber
00000101 Length
5
........ Contents
5C 32 B7 17 4F
-------------------------------------------------------------------------------Octet200 MscAddress
-------------------------------------------------------------------------------...11111 Tag
(31) Extended Tag
(55) MscAddress
00000111 Length
7
(1) ISDN/Telephony Number Plan (REC E.164)
.001.... Nature of Address
(1) International Number
(1) Not Extended
48602002220F
-------------------------------------------------------------------------------Octet210 CalledPartyBCDNumber
-------------------------------------------------------------------------------...11111 Tag
(31) Extended Tag
(56) CalledPartyBCDNumber
00000111 Length
7
(1) ISDN/telephony numbering plan (Rec. E.164/E.163)
.001.... Type of Number
(1) Not Extended
48696550124F
-------------------------------------------------------------------------------Octet220 SFEncountered
-------------------------------------------------------------------------------...00001 Tag
(1) SFEncountered
(6) Private use, primitive
00000001 Length
1
00000000 Boolean
(0) FALSE
-------------------------------------------------------------------------------Octet223 GapInterval
-------------------------------------------------------------------------------...00010 Tag
(2) GapInterval
(6) Private use, primitive
00000001 Length
1
........ Value
0
-------------------------------------------------------------------------------Checksum CRC16................ 0000000000000000 hex=0000
--------------------------------------------------------------------------------
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 57 of 68
APPENDIX B:
INTERNAL USE ONLY
CALLED PARTYNUMBER PARAMETER FORMAT
The format of the called party number(CdPN) parameter field is shown in Figure 10.
1
2
3
:
:
m
8
O/E
INN
5
4
3
2
Nature of address indicator
Numbering plan indicator
spare
2nd address signal
1st address signal
Filler (if necessary)
nth address signal
Figure 10/Q.763 Called party number(CdPN) parameter field

The following codes are used in the subfields of the called party number parameter field:
a)
Odd/even indicator (O/E)
b)
0
even number of address signals
1
odd number of address signals
Nature of address indicator
0000000
0000001
0000010
0000011
0000100
0000101
0000110
0000111
0001000
0001000
to
1111111
c)
Spare/Reserved
Internal Network Number indicator (INN)

0
1
d)
Spare
subscriber number (national use)
unknown (national use)
national (significant) number
international number
network-specific number (national use)
network routing number in national (significant) number format (national
use)
network routing number in network-specific number format (national use)
network routing number concatenated with Called Directory Number
(national use)
routing to internal network number allowed

routing to internal network number not allowed
Numbering plan indicator

000
001
010
011
100
Spare
ISDN (Telephony) numbering plan (ITU-T Recommendation E.164)
Spare
Data numbering plan (ITU-T Recommendation X.121) (national use)
Telex numbering plan (ITU-T Recommendation F.69) (national use)
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 58 of 68
101
110
111
e)
reserved for national use

reserved for national use
Spare
Address signal
0000
0001
0010
0011
0100
0101
0110
0111
1000
1001
1010
1011
1100
1101
1110
1111
f)
INTERNAL USE ONLY
digit 0
digit 1
digit 2
digit 3
digit 4
digit 5
digit 6
digit 7
digit 8
digit 9
spare
code 11
code 12
spare
spare
ST
The most significant address signal is sent first. Subsequent address signals are sent in successive
4-bit fields.
Filler
In case of an odd number of address signals, the filler code 0000 is inserted after the last address
signal.
Called PartyBCD Number

8
7
6
5
4
3
2
1
+-----------------------------------------------+
Called party BCD number IEI

octet
+-----------------------------------------------
Length of called party BCD number contents octet

+-----------------------------------------------
1
type of
Numbering plan
ext
number
identification
octet
+-----------------------+-----------------------
Number digit 2
Number digit 1
octet
+-----------------------+-----------------------
Number digit 4
Number digit 3
octet
+-----------------------+-----------------------
:
2)
:
+-----------------------------------------------+
1
2
3
4*
5*
Figure 10.5.91/TS 24.008 Called party BCD number information element
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 59 of 68
INTERNAL USE ONLY
NOTE 1: The number digit(s) in octet 4 precedes the digit(s) in octet 5 etc. The number digit which shall be entered first is
located in octet 4, bits 1 to 4.
NOTE 2: If the called party BCD number contains an odd number of digits, bits 5 to 8 of the last octet shall be filled with
an end mark coded as "1111".
Since the information element must contain the complete called party BCD number there is no need for an additional complete
indication.
Table 10.5.118/TS 24.008: Called party BCD number
+-------------------------------------------------------+
Type of number
Bits
7 6 5
0 0 0
unknown
0 0 1
international number
0 1 0
national number
0 1 1
network specific number
1 0 0
dedicated access, short code
1 0 1
reserved
1 1 0
reserved
1 1 1
reserved for extension
+-------------------------------------------------------+
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 60 of 68
APPENDIX C:
INTERNAL USE ONLY
REVIEW SUMMARIES
Review: Peer Review

Document:
Prepaid IDP Query Relay
Revision:
1.3
Date:
8/25/05
Author:
Devesh Agarwal, Bill Hayden
Review #:
1
Moderator:
Devesh Agarwal
Recorder:
Devesh Agarwal
Reviewers:
Name
Functional Area
Paul Hardin
Software
Rick Allison
Prod. management
Carol Arsmstrong Documentation
Michael Campbell NPI
Rick Cummings NPI
Dale Hemrick
PV
Pat Baldwin
s/w Architecture
Vincent Hemrick s/w Protocol
Shalliam Hayden s/w DB
Review Time
40 min
30 min
60 min
30 min
30 min
60 min
30 min
Score
3
3
3
3
3
3
3
Review conclusion by Moderator: 3

Average review preparation time: 40 min
Actions & Issues:
General Comments
None.
Actions
Specific Comments
Fix CGH to CHG in terminology
Misc Spelling correction
Sec 2.4 update default to incoming
sec 3 - Udpate affected GPLs
FD-270 align with FD 580
FD-350 not required
Sec 3.5 add description, list meas documents
Actions
Updated
Updated
Updated
Updated
Updated
Updated
Updated
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 61 of 68
INTERNAL USE ONLY
Peer Review Meeting Minutes: 12/13/2007

Review Type: Formal
Document: Prepaid IDP Query Relay FD005693 Ver 3.1
http://rightsite3.nc.tekelec.com/rs-bin/RightSite.dll/getcontent/FD005693?
DMW_DOCBASE=NSD&DMW_OBJECTID=0900372b8014b2f3
Moderator: Vincent Hamrick
Date: 12/7/2007
Time: 10:00AM
CHANGES:
A new Table, TTROPTS has been introduced; consolidated all IDPR configurable
parameters at one place.
Document has been updated to make use of NPP feature.
Test messages for testing the IDPRCDPN and IDPRCGPN NPP services.
Complete document will be reviewed.
Review Team:
Name
Functional Area
C/S
Vote
------------------------------------------------------------------------Rick Cummings
First Office Application
C
4
Carol Armstrong
Documentation
C
4
Sarah Cornel
Product Management
C
4
Meza Art
C
< Delegated to Vince >
Michael Sams
Technical Services
C
4
Mark Kanode
Software Architecture
C
<Delegated to Jonathan>
Vincent Hamrick
Software
C
4
Jonathan Nocjar
Software
C
4
Aricent Team(India) Software
C
4
Conclusion: 4
Comments from first day review (12/7/2007)
General:
1.
2.
3.
4.
Remove all the old stuff and obsoletes make this FD clean.
Remove obsolete requirements.
Change Flexible IDPR to Prepaid IDP Query Relay all places.
Replace NP DB with RTDB throughout the document.
Specific:
1.
2.
3.
4.
5.
Remove references 7, 8, 9 and 11.

Replace Ref 10 with TR5861
Remove ref 15 and 16; replace it with TR5822
Add a new section obsolesce and briefly describe what is obsolete.
Remove old reference like prefinum from terminology.
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 62 of 68
INTERNAL USE ONLY
6. Figure 1,2 ,3 and 4 Message flow for IDPR Relay feature. Redraw the pictures just showing
how it works with NPP
7. Remove section 2.2 and 2.3. CalledParty parameter formats. These are present in Appendix.
8. Remove section 2.4
9. Remove section2.5.4 Delete prefix screening list.
10. Section 2.8 Remove the first sentence in rept-stat-sccp section.
11. Section 2.10.1 Description move it to close to introduction section.
12. Section 2.10.3: State that IDR uses two rulesets. Do not say could be.
13. Remove Figure 7.
14. Table 3.GETACLAI is applicable only to Called Party Number conditioning.
15. Table 3. Change Notes to Design Notes. Add subscripts to explain the new actions.
16. Table 4. Rename CDDBSUCCESS to NPTYPE
17. Table 4. Add a new value for NPTYPE RNSPDN (New requirement)
18. Table 4. Change CDPNINNAI to SNAI
19. Table 4. Change CGDBSUCCESS to CGNPTYPE
20. Table 4. Change CGPNINNAI to CGSNAI
21. Table 4. Add a new value for CGNPTYPE RNSPDN. (New requirement)
22. Add separate fields for DLM1, DLm2 and DLM3 add NONE as one of the values.
23. Change HOMERN to DFLTRN
24. Update CGH/RTRV-TTROPTS command to reflect the TTROPTS table changes
25. Remove CGPNLKUP and add this as a new service action CGPNNP.
26. Make sure ENT/CHG/RTRV IDPR commands are functional only after enabling Prepaid IDP
Relay Feature
27. State conditioning actions and service actions for IDPRCDPN IDPRCGPN services separately.
These actions will be required during service registration.
28. Use ACLAC for GETLACAC or GETACLAC, use the term consistently.
29. FRS complaint matrix Need to be cleaned up.
30. Many tables have more data bytes than can be supported by 3 entries in virtual options table.
Like measopts.tbl, gsmopts.tbl, inpopts.tbl, ipoption.tbl, netopts.tbl requires more that 375
bytes (125 * 3). Since we need to provide generic read/write functions for tables in Virtual
Options table so we wanted to bring this to notice.
31. The generic read functions that shall be provided as a part of Flex IDPR feature, for reading
tables from Virtual Options table, have some design issues as follows:
The read function should provide the facility to read entire table data even if it is stored in
multiple segments. As per the TR document, there are seperate Virtual Table IDs for each
segment of table rather than same virtual table ID for all 3 segments. What ID will be
provided in read function while making a read call. We could not find any advantage of adding
3 seperate table IDs for single table.
We suggest that same virtual table ID be used for all the segments of the table.
32. Section 7.1.3 says ". If the msg parameter is not specified, all messages in the msgset shall
be displayed one after another."
There is no concept of msgset now
33. The design notes shared by Aricent should be added to the appendix of FD.
34. Figure 3. The decision box should say "CGPNLKUP ON" instead of "CDPNLKUP ON"
35. Section 3.3 Protocol Requirements: SCCPHC should also be mentioned in affected GPLs.
36. Table 13: Command chg/rtrv-prtefix shall also be mentioned in CDT WS 255.
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 63 of 68
INTERNAL USE ONLY
37. Please see the corrections to be made in Section 6:

5. Turn the IPPRCDPN IDPRCDPN service status OFF, if already ON( It is OFF by default)
chg-npp-serv:srvn:IPPRCDPNIDPRCDPN:status=off
Optional - Turn the IPPRCGPN IDPRCGPN service status OFF, if already ON( It is OFF by
default)
38. chg-npp-serv:srvn:IPPRCGPN IDPRCGPN:status=off
16. Provision the NAI mapping for IDPRCDPN service
39. chg-npp-serv:srvn:IPPRCDPN IDPRCDPN:intl=4:natl=3: nai1=2
17. Optional - Provision the NAI mapping for IDPRCGPN service
40. chg-npp-serv:srvn:IPPRCGPN IDPRCGPN:intl=4: natl=3: nai1=2
41. At places the parameter name is mentioned as CGPAACCK and at places it is CGPACCCK. It
should be consistent.
42. FD-122188-1200 says "MTT error Specified IDPR message or message set does not exist
shall be generated if message specified by CHG/RTRV-IDPR-MSG does not exist."
43. Now there is no concept of message set thus message set should be removed.
44. Upgrade requirements FD-122188-1520, FD-122188-1550, FD-122188-1570 and FD-1221881580 refers to NPP table updates. These requirements shall be implemented as a part of Flex
IDPR or NPP.
45. Section 2.10.6 : RTRV-TTROPTS output should also be specified when CGPN service/ruleset is
not defined UAM/UIM required for the feature should also be mentioned.
46. Virtual options table definition and storage should also be mentioned in FD since it shall be
implemented as part of Flex IDPR.
47. Section 3.7.5 says IDPRTEST.TBL in section header and NPPTEST.TBL in description.
48. Table 27, range of cgpadgts parameter is mentioned as 1..15 digits but default value is
mentioned as 01234567890abcdef .
Comments form second day review (12/13/2007) on partially updated FD.
General:
1. Change words existing feature/FD or current feature/FD to original
2. Remove Called Party Number/ Calling Party Number globally and use CdPA, CdPN, CgPA,
CgPN for consistency.
3. Change ENT/CHG/DLT/RTRV/TST-IDPR-TEST command to ENT/CHG/DLT/RTRV/TST-NPP<IDPRCDPN/IDPRCGPN> Each service will have a test command.
Specific:
Add CSP into Terminology and clarify CSP in the bulleted items(4) of section 1.4
1.6 change CHG-PFX to CHG-PREFIX command
2.0 numbered item 10: DEFCCCK => CGPACCCK, remove that this functionality is through
NPP feature.
4. 2.0 numbered item 12: Just state formatted, remove DLM1..etc.
5. Move Table 2 to upgrade section and show how this logic is implemented by NPP actions.
6. Table 3: Show NPP Actions for IDPRCDPN and IDPRCGPN separately. (may be separate
tables)
7. Table 3: Show the list conditioning and formatting actions and which ones are used by
DPRCGPN and IDPRCGPN
8. Cleanup section 2.7 and state that IDPR will use two services IDPRCDPN and IDPRCGPN.
9. Table 4: DLM1,2,3 length 16 digits only.
10. Section 2.8.5 Add a note that CCNCCHK service action is only for upgrade purpose
1.
2.
3.
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 64 of 68
INTERNAL USE ONLY
11. Explain how the contents of DLM variables get moved into NPP DLM state variables < Discuss
with Brain Holmes, avoid another service action >
12. Section 2.8.8 rept-stat-sccp command section 2. state that IDPR Feature is ON, like section
1.
13. Complete FRS Compliance Matrix
14. FD-122188-390 : Show how CAP NAI and INAP NAI are mapped into NPP NAIs.
15. FD-425: Use the application in place of GPL.
16. FD-500/530/533 are not testable. Remove?
17. FD-610 Use VSCCP Application, not GPL. State that feature will download RTDB, if IDPR
feature is the first number portability application turned on.
18. Table 13: Explicitly state all the table changes in this section. Documentation refers to this
table. CHG-PREFIX command should not be operational for IDPR feature after the upgrade.
Add an explicit requirement.
19. Table 15: Both measurement TRs are obsolete. The correct TR number TR005822.
20. Table 18: Move DLM3 to the bottom of the list.
21. Table 19: PFX is confusing with the NPP PFX explicitly state FEATPFX:Prefixnum X
22. Table 19: Cleanup the filters based on the discussion.
23. Add a Table showing the mapping of NPP variables and EAGLE Tables where they are derived
from eg. CC, DLMx
24. Section 3.7.4 Call this as NPPTEST.TBL IDPR uses first 10 messages from it.
25. Keep the message size to 450bytes and 1 byte for header.
26. Table 21: FD-122188-1560. Refer PFS, do not state the releases.
27. Table 21: Add requirements that IDPR feature commands on FEATPFX and CSL DLTPFX should
be prohibited after the upgrade. The existing prefixes on these tables must be cleaned up
after the upgrade.
28. Section 6.0: IDPR GPL to IDPR feature.
29. Section 6.0. Remove steps 4,5,6 and 9 from serviceability. Change the word Enable to
Enter in step 3.
30. Section 7.1.4: Needs to add lines in the beginning of the output to show what EAGLE
command got executed.
31. Section 7.1.4: Show a failure case and show the expected output.
32. Add requirements stating the how all NPP NAIs are mapped for IDPRCDPN and IDPRCGPN
service.
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 65 of 68
INTERNAL USE ONLY
Document Peer Review Meeting Minutes 12/19/2007

Review Type: Formal
Document: Prepaid IDP Query Relay FD005693 Ver 3.2.
Date: 12/19/2007
Time: 12:00 Noon
Review Team:
Name
Functional Area
C/S
Vote
------------------------------------------------------------------------Rick Cummings
C
3
Terri Boykin
Documentation
C
3
Sarah Cornel
Product Management
C
3
Meza Art
C
3
Mark Kanode
C
<Delegated to Jonathan>
Vincent Hamrick
Software
C
3
Jonathan Nocjar
Software
C
3
Aricent Team(India) Software
C
3
Conclusion: 3
Comments:
General:
None
Specific:
1. FD-610: user must init-card if VSCCP is the first application enabled on the card.
2. Remove CSL table description from FD
3. Table 19: Verify 3rd row NPP actions.
4. Structure definition of NPP test table :
5.
struct s_npp_test_msg_tbl_entry
{
e_feature_id
protocol_id;
/* 1 byte */
Should be:
e_protocol_id
protocol_id;
/* 1 byte */
union
{
t_idpr_test_msg idpr_test_msg;
/* New service test messages will be added here */
t_u8 max_test_msg_data[MAX_TEST_MSG_SIZE];
/* 450 bytes */
} u_test_msg;
};
FD-122188-250 & FD-122188-290 contradicts each other for the case when CDPN RTDB
lookup fails.
FD-122188-250 says
When RTDB lookup is performed, the outgoing CdPN is only modified when the entity_type is
same as the TTROPTS:NPTYPE. If the entity_type does not match TTROPTS:NPTYPE or the
lookup fails, the MSU falls to GTT handling.
FD-122188-290 says
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 66 of 68
6.
INTERNAL USE ONLY
When both CdPN and CgPN RTDB lookups are required, and the result of the first
lookup(CdPN) is unsuccessful, processing shall continue for the second RTDB lookup(CgPN),
however the first number shall not be altered by the IDP relay service. Prepaid IDp Relay
Feature shall support two different service rule sets for NPP services IDPRCDPN
and IDPRCGPN. These NPP services support CdPN and CgPN number processing respectively.
FD-122188-280 is covered in FD-122188-250.
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 67 of 68
INTERNAL USE ONLY
Document Review Meeting Minutes 2/1/2008

Review Type: Formal
Document: Prepaid IDP Query Relay FD005693 Ver 3.3.
Date: 1/30/2008
Time: 3:00PM
Review Team:
Name
Functional Area
C/S
Vote
------------------------------------------------------------------Rick Cummings
C
3
Carol Armstrong
Documentation
C
3
Meza Art
C
3
Mark Kanode
C
Delegated to SW
Vincent Hamrick
Software
C
3
Jonathan Nocjar
Software
C
3
Conclusion: 3
Comments:
1. Section 7.1.3 Replace indented for intended
2. Section 7.1.3 Replace used to only to for used only to
3. Section &.1.3 Add the list of valid PROT and FEAT character string to be used in the TSTMSG command.
4. Section 7.1.3 Replace EGLE Service feature for EAGLE Service Feature
5. No new comments. Agree with the PROT parameter not being a string though.
6. Section 7.1.3 Table 25
Why is the PROT parameter a char string? It should be a mnemonic list of well-known
protocols list the protocols.
For the FEAT parameter, I believe you are saying that it is a mnemonic list of wellknown features list the features.
7. Is tst-msg to be documented to customers in the Commands Manual (and in CDT)?
8. The Change History says test-msg; should say tst-msg.
9. A correction in 7.1.3: The test message that is sent to the service is not indented intended
DO NOT COPY
Title:
Doc No.:
341058866.doc
Rev No:
3.4
Page 68 of 68

Ver 3.4 FD005693

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ver 3.4 FD005693

Uploaded by

Copyright:

Available Formats

PROPRIETARY INFORMATION

INTERNAL USE ONLY

Network Systems Division

Prepaid IDP Query Relay Feature Description

Prepaid IDP Query Relay

INTERNAL USE ONLY

Updates from internal review.

Updates based on PV test issues

Updates for PR 122188: Flexible Prepaid IDP

Updates as per review comments and NPP FD

Updated the document based on review

Checked in the approved document

Updates for the tst-msg commands

INTERNAL USE ONLY

INTERNAL USE ONLY

Table 11: FD User Interface Requirement Table.......................................................................................................28

Purpose and Scope

INTERNAL USE ONLY

Inter-working with existing EAGLE 5 ISS features

External feature dependent Hardware and interconnecting requirements

Inter-working with other systems and features (e.g. EPAP).

[1] TEKELEC Acronym Guide, MS005077.doc, Current Revision

[15] ITU Q.1218 for INAP specification

INTERNAL USE ONLY

Acronyms and Terminology

Table 1: Acronyms and Terminology

Basic Call State Model

INTERNAL USE ONLY

lookup and outgoing number formatting.

INTERNAL USE ONLY

Figure 1: IDP Query Relay Feature Call Flow

INTERNAL USE ONLY

Message Flow for IDP Relay feature

INTERNAL USE ONLY

Figure 2: Message flow for Prepaid IDP Query Relay feature

INTERNAL USE ONLY

INTERNAL USE ONLY

Figure 4: Message flow for Prepaid IDP Relay feature

INTERNAL USE ONLY

Common Screening List (CSL)

GTA screening list

SKBCSM screening list

CCNDC screening list

Service Key (SK) parameter and BCSM Parameter

SRVSEL Command for IDP Relay

Enhanced Number processing requirements and the use of NPP feature

INTERNAL USE ONLY

Table 2: Sample NPP Configuration for IDPRCDPN Service

INTERNAL USE ONLY

Conditioning Actions used by IDPRCDPN and IDPRCGPN Services

Service Actions used by IDPRCDPN and IDPRCGPN Services

TTROPTS Table Structure

This table shall consist of the following options:

INTERNAL USE ONLY

set up the outgoing CdPN .

Default value. When the value is set to INCOMING then the

INTERNAL USE ONLY

The default value is none. It indicates no value, or changes the

The default value is none. It indicates no value, or changes the

These are 1 to 16 digit hexadecimal delimiters to be used for

The default value is none. It indicates no value, or changes the

This parameter is used to verify if the DEFCC check is to made

INTERNAL USE ONLY

Digit string 1..16 digits, NONE