Professional Documents
Culture Documents
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:
Doc
Number:
341058866.doc
Revision No:
3.4
<EAGLE>
Feature Description
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 1 of 68
PROPRIETARY INFORMATION
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)
No
No
Yes
Yes
4/23/07
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
No
12/05/2007
3.1
No
12/17/2007
3.2
No
12/26/2007
3.2
Suku Pandiyattu
Rakhi Verma
Suku Pandiyattu
Rakhi Verma
Suku Pandiyattu
Rakhi Verma
Suku Pandiyattu
Yes
1/28/2008
2/1/2008
3.3
3.4
Suku Pandiyattu
Suku Pandiyattu
No
Yes
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 2 of 68
PROPRIETARY INFORMATION
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 3 of 68
PROPRIETARY INFORMATION
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 4 of 68
PROPRIETARY INFORMATION
1.0
INTRODUCTION
1.1
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.
5.
6.
1.2
1.2.1
References
Internal References:
1.2.2
External References:
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 5 of 68
PROPRIETARY INFORMATION
1.3
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 6 of 68
PROPRIETARY INFORMATION
TTROPTS
1.4
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 7 of 68
PROPRIETARY INFORMATION
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.
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 8 of 68
PROPRIETARY INFORMATION
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
The figures below depict the details of the IDP message processing.
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 9 of 68
PROPRIETARY INFORMATION
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 10 of 68
PROPRIETARY INFORMATION
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 11 of 68
PROPRIETARY INFORMATION
Figure 3: Message flow for Prepaid IDP Query Relay feature (cont)
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 12 of 68
PROPRIETARY INFORMATION
2.2
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
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
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
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
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
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
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 13 of 68
PROPRIETARY INFORMATION
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 14 of 68
PROPRIETARY INFORMATION
1.
2.
3.
4.
5.
6.
7.
8.
9.
2.7
2.8
2.9
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.
IDPRCDPN
IDPRCGPN
Conditioning Actions
Specified by NPP FD [10]
YES
YES
ACLAC
YES
NO
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
Possible Value
SP
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Comments
When the lookup in the RTDB has entitytype=SP, then the
lookup is considered successful. This entity_data is now used to
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 15 of 68
PROPRIETARY INFORMATION
RN
RNSP
(Default)
ANYMATCH
ALWAYS
RNSPDN
SNAI
INCOMING
(Default)
INTL
NATL
UNKN
CGNPTYPE
SP
RN
RNSP
(Default)
ANYMATCH
ALWAYS
CGSNAI
RNSPDN
When the lookup in the RTDB has entity type RN, SP or DN,
then the lookup is considered successful.
INCOMING
(Default)
INTL
NATL
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 16 of 68
PROPRIETARY INFORMATION
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>
NONE
(Default)
<1..16>
NONE
(Default)
CGPACCCK
ALWAYS
DFLTRN
NON-INTL
(Default)
OFF
<1..15>
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 17 of 68
PROPRIETARY INFORMATION
CGNPTYPE
Optional
CGSNAI
Optional
SP
RN
RNSP
ANYMATCH
ALWAYS
RNSPDN
RNSP
INCOMING
INTL
NATL
UNKN
INCOMING
DLM1
Optional
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
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 18 of 68
PROPRIETARY INFORMATION
2.10.1
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
2.10.2
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
LACCK
60
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 19 of 68
PROPRIETARY INFORMATION
2.10.3
IDPRCGPN NPP Service does not require any new number Conditioning Actions.
2.10.4
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
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
Active
-----
Active
-----
= No Alarms
Cards IS-NR= 2
1700
TPS (1700
1360
CARD
SST
VERSION
PST
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
0%
5%
0%
MNP
0%
IDPR
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
0%
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 20 of 68
PROPRIETARY INFORMATION
REROUTE\
SUCCESS
ERRORS
RATIO
WARNINGS
TO GTT
TOTAL
GTT:
1995
0%
2000
MNP:
800
0%
10
815
TTR:
60
0%
71
71
SERVICE
FORWARD
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
-----
= **
GTT:
STAT = ACT
TTR:
STAT = ACT
CPU USAGE =
8%
--------------TOTAL
= 18%
SUCCESS
ERRORS
WARNINGS
FORWARD TO GTT
TOTAL
GTT:
TTR:
3.0
FUNCTIONAL REQUIREMENTS
3.1
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
3.4
Page 21 of 68
PROPRIETARY INFORMATION
FRS Requirement
R-57095-30
R-57095-40
R-57095-45
R-57095-50
R-57095-55
Compliance
FC
FC
FC
FC
FC
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 22 of 68
PROPRIETARY INFORMATION
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
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
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 23 of 68
PROPRIETARY INFORMATION
3.2
General Requirements
FD-100
FD-110
Required
or
Optional
(R or O)
R
R
Affected
GPLs
VSCCP
VSCCP
FD-122188100
FD-122188110
FD-122188120
FD-122188130
FD-122188140
FD-122188150
FD-122188160
FD-122188170
FD-122188180
FD-122188185
FD-122188190
FD-122188190
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
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:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 24 of 68
PROPRIETARY INFORMATION
3.3
Protocol Requirements
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
Affected
GPLs
VSCCP,
SCCPHC
VSCCP,
SCCPHC
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
VSCCP,
SCCPHC
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 25 of 68
PROPRIETARY INFORMATION
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
VSCCP,
SCCPHC
VSCCP,
SCCPHC,
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
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:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 26 of 68
PROPRIETARY INFORMATION
FD-122188280
FD-122188290
FD-122188300
FD-122188310
FD-122188340
FD-122188350
FD-122188360
FD-122188370
FD-122188380
FD-122188390
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
Affected GPLs
EOAM
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
EOAM,
VSCCP
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 27 of 68
PROPRIETARY INFORMATION
SCCCPHC
3.5
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
Affected GPLs
EOAM
EOAM,
VSCCP
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
EOAM
EOAM
EOAM,VSCCP
EOAM,
VSCCP
EOAM,
VSCCP
EOAM,
VSCCP
EOAM,
VSCCP
EOAM,
VSCCP
EOAM,
VSCCP
EOAM,
VSCCP
EAOM
EOAM
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 28 of 68
PROPRIETARY INFORMATION
GPORT/GFLEX/INP/etc.
If LNP is enabled, IDP Relay cannot be enabled.
This functionality is similar to other features likes
GPORT/GFLEX/INP/etc.
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]
This functionality is similar to other features likes
GPORT/GFLEX/INP/etc.
Feature enhancement PR 122188, Flexible IDPR feature
shall support new CHG/RTRV-TTROPTS command set.
EOAM
FD-600
FD-610
FD-1221881000
FD-1221881005
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
EOAM
FD-1221881080
EOAM,
VSCCP,
SCCPHC
FD-1221881090
EOAM,
VSCCP,
SCCPHC
FD-1221881100
EOAM,
VSCCP,
SCCPHC
FD-1221881110
FD-1221881140
EOAM,
VSCCP,
SCCPHC
EOAM,
VSCCP,
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
EOAM
EOAM,
VSCCP,
SCCPHC
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 29 of 68
PROPRIETARY INFORMATION
SCCPHC
FD-1221881150
FD-1221881160
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
EOAM,
FD-1221881215
EOAM,
FD-1221881220
EOAM,
FD-1221881230
EOAM
FD-1221881240
EOAM
FD-1221881250
VSCCP,
SCCPHC
FD-1221881260
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 30 of 68
PROPRIETARY INFORMATION
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
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
Affected
GPLs
EOAM, MCP
EOAM, MCP
EOAM, MCP
EOAM, MCP
EOAM, MCP
EOAM, MCP
Doc Name
Changes
EAGLE 5 ISS
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 31 of 68
PROPRIETARY INFORMATION
Document
Number
Doc Name
Changes
Measurements.
3.7
3.7.1
Upgrade Considerations
EGLEOPTS.TBL
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
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 32 of 68
PROPRIETARY INFORMATION
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_MEASOPTS_VTBL_SEG_3 = EGLE_MEASOPTS_VTBL+2, /* 5
EGLE_MEASOPTS_VTBL_SEG_4 = EGLE_MEASOPTS_VTBL+3, /* 6
EGLE_XSTPOPTS_VTBL
= 7,
EGLE_INPOPTS_VTBL
= 8,
EGLE_INPOPTS_VTBL_SEG_1
= EGLE_INPOPTS_VTBL,
/* 8
EGLE_INPOPTS_VTBL_SEG_2
= EGLE_INPOPTS_VTBL+1, /* 9
EGLE_INPOPTS_VTBL_SEG_3
= EGLE_INPOPTS_VTBL+2, /* 10
EGLE_INPOPTS_VTBL_SEG_4
= EGLE_INPOPTS_VTBL+3, /* 11
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_SEG_2
= EGLE_GSMOPTS_VTBL+1, /* 15
EGLE_GSMOPTS_VTBL_SEG_3
= EGLE_GSMOPTS_VTBL+2, /* 16
EGLE_GSMOPTS_VTBL_SEG_4
= EGLE_GSMOPTS_VTBL+3, /* 17
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 33 of 68
PROPRIETARY INFORMATION
#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;
/*
/*
/*
/*
/*
/*
/*
/*
/*
/*
1 byte
1 byte
1 byte
1 byte
9 bytes
9 bytes
9 bytes
1 byte
9 bytes
84 bytes
*/
*/
*/
*/
*/
*/
*/
*/
*/
*/
}
/* Total 125 bytes */
typedef struct s_disk_ttr_options_tbl t_disk_ttr_options_tbl;
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 34 of 68
PROPRIETARY INFORMATION
3.7.2
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
Intern
ational
FEATPFX:Prefixnu
m4?
No
Number
Conditioning
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>
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 35 of 68
PROPRIETARY INFORMATION
Unkno
wn
If
FEATPFX:Prefixnum
4==ON
<NEC><DN>
NAI=unknown
<NEC><RN><DN>
NAI=unknown
<RN><DN>
remove it,
Add DEFCC,
Do RTDB Lookup
Unkno
wn
If
FEATPFX:Prefixnum
4==ON
<DN>
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
DLM1
DLM2
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 36 of 68
PROPRIETARY INFORMATION
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
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 37 of 68
PROPRIETARY INFORMATION
TESTMSG
Rel 39.0 (PR 122188) Flexible IDPR feature
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:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 38 of 68
PROPRIETARY INFORMATION
0
0
0
YES
RI_FIX
0
0
0
NO
RI_FIX_SYS
/* 1 byte */
/* 450 bytes */
/* Total 451 bytes */
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 39 of 68
PROPRIETARY INFORMATION
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 */
/* Total 450 bytes */
Required or
Optional (R or O)
R
FD1221881510
FD-
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
Affected
GPLs
EOAM,
VSCCP,
SCCPHC
EOAM,
VSCCP,
SCCPHC
EOAM,
3.4
Page 40 of 68
PROPRIETARY INFORMATION
1221881520
FD1221881530
FD1221881540
FD1221881550
FD1221881560
FD1221881570
FD1221881580
FD1221881590
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
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
natl
nai1
Hard copies of this document are
for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
NONE
NONE
Doc
No.:
341058866.doc
Rev No:
nai2
NONE
NONE
nai3
NONE
NONE
3.4
Page 41 of 68
PROPRIETARY INFORMATION
6.1
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
Therecanbemultipleentriesforthiscommand.
Thereshouldbeminimumofoneentryforthefeaturetowork.
TheentrycanbejustwithcountrycodesamevalueasinDEFFCCparameter.
10.
EnterDigitString(DS)entriesintheGTlist.
entcsl:pn=893016001:list=gt:ds=456
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 42 of 68
PROPRIETARY INFORMATION
Therecanbemultipleentriesforthiscommand.
Thereshouldbeminimumofoneentryforthefeaturetowork.
ThisdigitshouldmatchthecalledpartynumberintheSCCPCDPA.
11.
EnterDigitString(DS)entriesintheSKBCSMlist.
entcsl:pn=893016001:list=skbcsm:ds=h0x0000001402
Therecanbemultipleentriesforthiscommand.
Thereshouldbeminimumofoneentryforthefeaturetowork.
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
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 43 of 68
PROPRIETARY INFORMATION
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
cgpagtnai
0..127
4 (International)
cgpadgts
01234567890abcde
cdpagt
0..15
cdpagtnai
0..127
4 (International) INAP
cdpadgts
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
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 44 of 68
PROPRIETARY INFORMATION
cdpagt
0..15
cdpagtnai
0..127
cdpadgts
CdPNnai
CdPNdgts
CgPNnai
CgPNdgts
ACTIVE
YES, NO
RESET
YES, NO
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 45 of 68
PROPRIETARY INFORMATION
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.
Mandatory/
Optional
Default
Range
No default value
MSGN
1..10
No default value
LOC
No default value
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 46 of 68
PROPRIETARY INFORMATION
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
CGPN = 0123456789ABCDEF0123456789ABCDEF
CDPN_NAI = 2
CDPN = 0123456789ABCDEF0123456789ABCDEF
DIGITS = 1234567890ABCDEF123456789ABCDEF
DIGITS = 1234567890ABCDEF123456789ABCDEF
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 47 of 68
PROPRIETARY INFORMATION
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
CGPN = 0123456789ABCDEF0123456789ABCDEF
CDPN_NAI = 2
CDPN = 0123456789ABCDEF0123456789ABCDEF
DIGITS = 1234567890ABCDEF123456789ABCDEF
SA2 = SA2NAMEXXX
SA3 = SA2NAMEXXX
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 48 of 68
PROPRIETARY INFORMATION
SA4 = SA2NAMEXXX
SA5 = SA2NAMEXXX
SA6 = SA2NAMEXXX
SA7 = SA2NAMEXXX
SA8 = SA2NAMEXXX
= FA1NAMEXXX
FA2
= FA2NAMEXXX
FA3
= FA2NAMEXXX
FA4
= FA2NAMEXXX
FA5
= FA2NAMEXXX
FA6
= FA2NAMEXXX
FA7
= FA2NAMEXXX
FA8
= FA2NAMEXXX
FA9
= FA2NAMEXXX
FA10 = FA2NAMEXXX
FA11 = FA2NAMEXXX
FA12 = FA2NAMEXXX
OUTG DIGITS = 1234567890ABCDEF123456789ABCDEF
OUTG FNAI = INTL
CGPN NPP PROCESSING
SERVICE NAME = IDPRCGPN
DIGITS = 1234567890ABCDEF123456789ABCDEF
SA2 = SA2NAMEXXX
SA3 = SA2NAMEXXX
SA4 = SA2NAMEXXX
SA5 = SA2NAMEXXX
SA6 = SA2NAMEXXX
SA7 = SA2NAMEXXX
SA8 = SA2NAMEXXX
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 49 of 68
PROPRIETARY INFORMATION
= FA1NAMEXXX
FA2
= FA2NAMEXXX
FA3
= FA2NAMEXXX
FA4
= FA2NAMEXXX
FA5
= FA2NAMEXXX
FA6
= FA2NAMEXXX
FA7
= FA2NAMEXXX
FA8
= FA2NAMEXXX
FA9
= FA2NAMEXXX
FA10 = FA2NAMEXXX
FA11 = FA2NAMEXXX
FA12 = FA2NAMEXXX
OUTG DIGITS = 1234567890ABCDEF123456789ABCDEF
OUTG FNAI = INTL
8.0
LIMITATIONS
None.
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 50 of 68
PROPRIETARY INFORMATION
9.0
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 51 of 68
PROPRIETARY INFORMATION
APPENDIX A:
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 52 of 68
PROPRIETARY INFORMATION
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
48602001220
0000.... Filler
0
-------------------------------------------------------------------------------Octet038 SCCP Data parameter
-------------------------------------------------------------------------------10111011 Parameter length
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
011..... Class and form
(3) Application-wide, constructor
00011101 Length
29
-------------------------------------------------------------------------------Octet050 External
-------------------------------------------------------------------------------...01000 Tag
(8) External
001..... Class and form
(1) Universal, constructor
00011011 Length
27
-------------------------------------------------------------------------------Octet052 Object identifier
-------------------------------------------------------------------------------...00110 Tag
(6) Object identifier
000..... Class and form
(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
011..... Class and form
(3) Application-wide, constructor
00001110 Length
14
-------------------------------------------------------------------------------Octet065 Application-context-name
-------------------------------------------------------------------------------...00001 Tag
(1) Application-context-name
101..... Class and form
(5) Context-specific, constructor
00001100 Length
12
-------------------------------------------------------------------------------Octet067 Object Identifier
-------------------------------------------------------------------------------...00110 Tag
(6) Object identifier
000..... Class and form
(0) Universal, primitive
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 53 of 68
PROPRIETARY INFORMATION
........ 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
011..... Class and form
(3) Application-wide, constructor
10000001 Length
129
........ Long form length
144
-------------------------------------------------------------------------------Octet082 Invoke
-------------------------------------------------------------------------------...00001 Tag
(1) Invoke
101..... Class and form
(5) Context-specific, constructor
10000001 Length
129
........ Long form length
141
-------------------------------------------------------------------------------Octet085 InvokeID
-------------------------------------------------------------------------------...00010 Tag
(2) InvokeID
000..... Class and form
(0) Universal, primitive
00000001 Length
1
00000001 InvokeID
01
-------------------------------------------------------------------------------Octet088 Operation Code
-------------------------------------------------------------------------------...00010 Tag
(2) Local
000..... Class and form
(0) Universal, primitive
00000001 Length
1
........ Operation Code
(0) IDP InitialDP
-------------------------------------------------------------------------------Octet091 Parameter Sequence
-------------------------------------------------------------------------------...10000 Tag
(16) Parameter Sequence
001..... Class and form
(1) Universal, constructor
10000001 Length
129
........ Long form length
132
-------------------------------------------------------------------------------Octet094 ServiceKey
-------------------------------------------------------------------------------...00000 Tag
(0) ServiceKey
100..... Class and form
(4) Context-specific, primitive
00000001 Length
1
........ Service key
107
-------------------------------------------------------------------------------Octet097 CallingPartyNumber
-------------------------------------------------------------------------------...00011 Tag
(3) CallingPartyNumber
100..... Class and form
(4) Context-specific, primitive
00001000 Length
8
.0000100 Nature of address
(4) International number
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
........ Address signals
48889021750
0000.... Filler
0
-------------------------------------------------------------------------------Octet107 CallingPartysCategory
-------------------------------------------------------------------------------...00101 Tag
(5) CallingPartysCategory
100..... Class and form
(4) Context-specific, primitive
00000001 Length
1
11100000 CallngPartyCategory
(224) Reserved for national use
-------------------------------------------------------------------------------Octet110 LocationNumber
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 54 of 68
PROPRIETARY INFORMATION
-------------------------------------------------------------------------------...01010 Tag
(10) LocationNumber
100..... Class and form
(4) Context-specific, primitive
00001001 Length
9
.0000011 Nature of address
(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
........ Address signals
03200000051511
-------------------------------------------------------------------------------Octet121 HighLayerCompatibility
-------------------------------------------------------------------------------...10111 Tag
(23) HighLayerCompatibility
100..... Class and form
(4) Context-specific, primitive
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....... Extension Bit
(1) last octet
-------------------------------------------------------------------------------Octet125 ForwardCallIndicators
-------------------------------------------------------------------------------...11010 Tag
(26) ForwardCallIndicators
100..... Class and form
(4) Context-specific, primitive
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
101..... Class and form
(5) Context-specific, constructor
00000101 Length
5
-------------------------------------------------------------------------------Octet131 Bearer Cap
-------------------------------------------------------------------------------...00000 Tag
(0) Bearer Cap
100..... Class and form
(4) Context-specific, primitive
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
-------------------------------------------------------------------------------Octet134 User service info octet 4
-------------------------------------------------------------------------------...10000 Transfer rate
(16) 64 kbit/s
.00..... Transfer mode
(0) circuit mode
1....... Extension bit
(1) Last Octet
-------------------------------------------------------------------------------Octet135 User service info octet 5
-------------------------------------------------------------------------------...00011 Layer 1 protocol
(3) Recommendation G.711 A-law
.01..... Layer 1 Identifier
(1) User information layer 1 protocol
1....... Extension bit
(1) Last Octet
-------------------------------------------------------------------------------Octet136 EventTypeBCSM
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 55 of 68
PROPRIETARY INFORMATION
-------------------------------------------------------------------------------...11100 Tag
(28) EventTypeBCSM
100..... Class and form
(4) Context-specific, primitive
00000001 Length
1
00000010 EventTypeBCSM
(2) collectedInfo
-------------------------------------------------------------------------------Octet139 MapIMSI
-------------------------------------------------------------------------------...11111 Tag
(31) Extended Tag
100..... Class and form
(4) Context-specific, primitive
........ Extended Tag
(50) MapIMSI
00001000 Length
8
........ IMSI
260021660021755F
-------------------------------------------------------------------------------Octet150 LocationInformation
-------------------------------------------------------------------------------...11111 Tag
(31) Extended Tag
101..... Class and form
(5) Context-specific, constructor
........ Extended Tag
(52) LocationInformation
00100001 Length
33
-------------------------------------------------------------------------------Octet153 AgeOfLocationInformation
-------------------------------------------------------------------------------...00010 Tag
(2) Integer
000..... Class and form
(0) Universal, primitive
00000001 Length
1
........ Value
0
-------------------------------------------------------------------------------Octet156 GeographicalInformation
-------------------------------------------------------------------------------...00000 Tag
(0) GeographicalInformation
100..... Class and form
(4) Context-specific, primitive
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
100..... Class and form
(4) Context-specific, primitive
00000111 Length
7
....0001 Numbering Plan
(1) ISDN/Telephony Number Plan (REC E.164)
.001.... Nature of Address
(1) International Number
1....... Extension Bit
(1) Not Extended
........ Address signals
48602002220F
-------------------------------------------------------------------------------Octet175 CellIdOrLAI
-------------------------------------------------------------------------------...00011 Tag
(3) CellIdOrLAI
101..... Class and form
(5) Context-specific, constructor
00001001 Length
9
-------------------------------------------------------------------------------Octet177 CellIDFixedLength
-------------------------------------------------------------------------------...00000 Tag
(0) CellIDFixedLength
100..... Class and form
(4) Context-specific, primitive
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 56 of 68
PROPRIETARY INFORMATION
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 57 of 68
PROPRIETARY INFORMATION
APPENDIX B:
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
a)
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
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)
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 58 of 68
PROPRIETARY INFORMATION
101
110
111
e)
Address signal
0000
0001
0010
0011
0100
0101
0110
0111
1000
1001
1010
1011
1100
1101
1110
1111
f)
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.
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*
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 59 of 68
PROPRIETARY INFORMATION
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 60 of 68
PROPRIETARY INFORMATION
APPENDIX C:
REVIEW SUMMARIES
Review Time
40 min
30 min
60 min
30 min
30 min
60 min
30 min
Score
3
3
3
3
3
3
3
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 61 of 68
PROPRIETARY INFORMATION
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
Product Verification
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.
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 62 of 68
PROPRIETARY INFORMATION
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 63 of 68
PROPRIETARY INFORMATION
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 64 of 68
PROPRIETARY INFORMATION
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 65 of 68
PROPRIETARY INFORMATION
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 66 of 68
PROPRIETARY INFORMATION
6.
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
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 67 of 68
PROPRIETARY INFORMATION
DO NOT COPY
Hard copies of this document are for reference only. The
latest approved version is located under version control.
Title:
Prepaid IDP Query Relay Feature Description
Doc No.:
341058866.doc
Rev No:
3.4
Page 68 of 68