FD006137 - Tobr - Flobr - Tcap - Segmented - of

PROPRIETARY INFORMATION INTERNAL USE ONLY
Network Systems Division

5200 Paramount Pkwy
Morrisville, NC 27560
Voice: 919-460-5500
THIS DOCUMENT AND THE DATA DISCLOSED HEREIN OR HEREWITH IS PROPRIETARY AND IS NOT TO BE
REPRODUCED, USED OR DISCLOSED IN WHOLE OR IN PART TO ANYONE WITHOUT THE WRITTEN PERMISSION
OF TEKELEC. COPYRIGHT © TEKELEC 1999-2009. ALL RIGHTS RESERVED.
Title: TCAP Opcode Based Routing (TOBR) Feature Description

Doc FD006137.doc Revision No: 2.2
Number:
Eagle® 5 ISS
Feature Description
TCAP Opcode Based Routing (TOBR)

(PR 114149)
TCAP Segmented SMS Support Phase 2

(PR 113121)
Also covers the following PRs:
Support for 16 GTT Lengths in VGTT

(PR 127100)
Increasing # of B-Trees supported on Eagle

(PR 84148)
DO NOT COPY Title: TCAP Opcode Based Routing (TOBR) Feature Description
Doc No.: TOBR_FLOBR_TCAP_SEGMENTE Rev No: 2.2
Hard copies of this document are for reference only.
D_OF.doc
The latest approved version is located under version
control. Page 1 of 88
TABLE OF CONTENTS
1.0 INTRODUCTION.............................................................................................................................................................. 6
1.1 Purpose and Scope ......................................................................................................................................................... 6
1.2 References ........................................................................................................................... Erreur ! Signet non défini.
1.3 Acronyms and Terminology........................................................................................................................................... 6
2.0 GENERAL DESCRIPTION .............................................................................................................................................. 7
2.1 VGTT with 16 GTT lengths - Enhancement .................................................................................................................. 7
2.2 Increasing # of B-Trees supported on Eagle – An Engineering Enhancement............................................................... 7
2.3 FLOBR Feature .............................................................................................................................................................. 7
2.3.1 Linkset Based Routing ......................................................................................................................................... 7
2.3.1.1 FLOBR GTT Hierarchies .................................................................................................................................... 7
2.3.1.2 GTT selection with FLOBR GTT Modes ......................................................................................................... 10
2.3.2 Flexible Routing with GTT Translations ......................................................................................................... 12
2.3.2.1 Fallback Option with FLOBR ........................................................................................................................... 14
2.3.2.1.1 Routing when subsequent GTT set search failed in FLOBR................................................................... 15
2.3.2.1.2 Routing when subsequent search for SELID failed in FLOBR............................................................... 16
2.3.2.1.3 Routing when same GTT set type is referred more than once ................................................................ 16
2.3.2.1.4 Limiting the number of database searches for FLOBR ........................................................................... 17
2.3.3 GTT for Eagle-generated MSUs ....................................................................................................................... 18
2.3.4 GTT Selector Key ............................................................................................................................................... 19
2.3.5 Searching order in GTT Selector Table with FLOBR .................................................................................... 19
2.4 TOBR ........................................................................................................................................................................... 20
2.4.1 TOBR protocol handling ................................................................................................................................... 21
2.4.2 TCAP Decoding .................................................................................................................................................. 24
2.4.2.1 ITU TCAP Transaction portion Decoding ....................................................................................................... 25
2.4.2.2 ITU TCAP Dialogue portion Decoding ............................................................................................................ 26
2.4.2.3 ITU TCAP Component Decoding ..................................................................................................................... 28
2.4.2.4 ANSI TCAP Transaction portion Decoding: ................................................................................................... 30
2.4.2.5 ANSI TCAP Dialogue portion Decoding:......................................................................................................... 31
2.4.2.6 ANSI TCAP Component portion Decoding: .................................................................................................... 31
2.4.3 TOBR GTT Sets ................................................................................................................................................. 32
2.4.4 TOBR Opcode Quantities .................................................................................................................................. 33
2.4.5 TOBR GTT Translations ................................................................................................................................... 33
2.4.5.1 TOBR CdPA SSN Translations ........................................................................................................................ 33
2.4.5.2 TOBR Opcode Translations .............................................................................................................................. 33
2.4.5.2.1 TOBR translations with ANSI Opcode ..................................................................................................... 33
2.4.5.2.2 Searching order for TOBR translations with ANSI Opcode ................................................................... 34
2.4.5.2.3 TOBR translations with ITU Opcode ........................................................................................................ 34
2.4.5.2.3.1 Searching order for TOBR translations with ITU Opcode ........................................................... 35
2.5 TCAP Segmentation SMS Support Phase 2 ................................................................................................................. 35
2.6 AMGTT usage for non-GTA translations .................................................................................................................... 36
2.7 Effect of ANSI/ITU Translation (PR 59452) feature ................................................................................................... 36
D_OF.doc
2.8 Interaction with ANSI/ITU/CHINA SCCP Conversion ............................................................................................... 36

2.9 CgPA searching for AMGTT ....................................................................................................................................... 36
2.10 Interaction with MPS-based features ........................................................................................................................... 37
2.11 Expanding the GTT selector Table capacity ................................................................................................................ 37
2.12 UIMs ............................................................................................................................................................................ 37
2.13 Test Tool ...................................................................................................................................................................... 38
2.13.1 TST-MSG ............................................................................................................................................................ 38
2.13.2 Test Mode Provisioning ..................................................................................................................................... 40
2.13.2.1 Effect of TESTMODE on a GTTSET with 10/16 GTT lengths .................................................................... 40
2.13.2.2 Effect of TESTMODE on Opcode Translations ............................................................................................ 41
2.13.2.3 Interaction between FALLBACK and TESTMODE options....................................................................... 41
2.13.3 Interpretation of “GTT Selector Found” and “GTT Selector Not Found”................................................... 41
2.13.4 Default CdPA GTTSET ..................................................................................................................................... 42
2.13.5 Capacity of GTT Selector Table ....................................................................................................................... 42
3.0 FLEXIBLE DATABASE SEARCH ALGORITHMS ..................................................................................................... 42
4.0 FUNCTIONAL REQUIREMENTS................................................................................................................................. 52
4.1 FRS Compliance Matrix............................................................................................................................................... 52
4.2 General Requirements .................................................................................................................................................. 56
4.3 Protocol Requirements ................................................................................................................................................. 56
4.4 FLOBR Test Tool / Test Mode Requirements ............................................................................................................. 62
4.5 User Interface Requirements ........................................................................................................................................ 65
4.5.1 FLOBR User Interface Requirements .............................................................................................................. 65
4.5.2 TOBR User Interface Requirements ................................................................................................................ 68
4.5.3 VGTT with 16 GTT lengths User Interface Requirements ............................................................................ 69
4.5.4 Affected Commands ........................................................................................................................................... 69
4.6 Hardware Requirements ............................................................................................................................................... 70
4.6.1 VGTT with 16 GTT lengths Hardware Requirements ................................................................................... 70
4.6.2 FLOBR Hardware Requirements ..................................................................................................................... 70
4.6.3 TOBR Hardware Requirements ....................................................................................................................... 71
4.7 Performance Requirements .......................................................................................................................................... 71
4.7.1 VGTT with 16 GTT lengths Performance Requirements ............................................................................... 71
4.7.2 FLOBR and TOBR Performance Requirements............................................................................................. 71
4.8 Measurement Requirements ......................................................................................................................................... 72
4.9 Upgrade Considerations ............................................................................................................................................... 73
4.9.1 GTT Set Table ........................................................................................................... Erreur ! Signet non défini.
4.9.2 GTTDBMM Table..................................................................................................... Erreur ! Signet non défini.
4.9.3 GTT_TBT Table ........................................................................................................ Erreur ! Signet non défini.
4.9.4 NPNAI Table ............................................................................................................. Erreur ! Signet non défini.
4.9.5 SSNSELID Table ....................................................................................................... Erreur ! Signet non défini.
4.9.6 GTT_TT2 Table ........................................................................................................ Erreur ! Signet non défini.
5.0 PERFORMANCE ............................................................................................................................................................ 73
6.0 RELIABILITY ................................................................................................................................................................. 74
7.0 SERVICEABILITY ......................................................................................................................................................... 74
D_OF.doc
8.0 TESTABILITY ................................................................................................................................................................ 75

8.1 Database provisioning sequence .................................................................................................................................. 75
8.1.1 VGTT with 16 GTT lengths............................................................................................................................... 75
8.1.2 FLOBR ................................................................................................................................................................ 76
8.1.3 TOBR .................................................................................................................................................................. 78
8.1.4 Test Tool .............................................................................................................................................................. 80
9.0 LIMITATIONS ................................................................................................................................................................ 81
10.0 PEER REVIEW CHECKLIST................................................................................ ERREUR ! SIGNET NON DEFINI.
APPENDIX A: GTT ACTIONS INFO .................................................................................................................................. 82
10.1 GTT Actions ................................................................................................................................................................ 82
10.1.1 GTT Action Types .............................................................................................................................................. 82
10.1.2 GTT Action FAKs .............................................................................................................................................. 83
10.1.3 GTT Actions User Interface Requirements ..................................................................................................... 84
10.1.4 GTT Actions Hardware Requirements ............................................................................................................ 86
10.1.5 GTT Actions Performance Requirements ........................................................................................................ 86
10.1.6 GTT Actions Set Table.............................................................................................. Erreur ! Signet non défini.
APPENDIX B: REVIEW SUMMARIES ..................................................................... ERREUR ! SIGNET NON DEFINI.
List of Tables
Table 1: Acronyms and Terminology ............................................................................................................................................ 6
Table 2: Available GTT hierarchies ............................................................................................................................................... 8
Table 3: Available GTT set types in selector table ...................................................................................................................... 10
Table 4: Flexible Routing with GTT Translations ....................................................................................................................... 13
Table 5: GTT Selector Key .......................................................................................................................................................... 19
Table 6: GTT Selector searching order with FLOBR .................................................................................................................. 20
Table 7: TCAP Transaction Validation ........................................................................................................................................ 26
Table 8: TCAP Dialog Validation ................................................................................................................................................ 28
Table 9: TCAP Component Validation ........................................................................................................................................ 28
Table 10: Invoke Component Validation ..................................................................................................................................... 29
Table 11: Return Result - L/NL Component Validation .............................................................................................................. 30
Table 12: TCAP Transaction Validation ...................................................................................................................................... 31
Table 13: Searching order for TOBR translations with ANSI Opcode ........................................................................................ 34
Table 14: Valid/Invalid ACN values ............................................................................................................................................ 35
Table 15: Searching order for TOBR translations with ITU Opcode ........................................................................................... 35
Table 16: New FLOBR UIMs ...................................................................................................................................................... 37
Table 17: FLOBR Test Tool Parameters ...................................................................................................................................... 38
Table 18: FRS Compliance Matrix .............................................................................................................................................. 52
Table 19: General Requirements Table ........................................................................................................................................ 56
Table 20: Protocol Requirements Table for FLOBR.................................................................................................................... 56
Table 21: Protocol Requirements Table for TOBR ...................................................................................................................... 60
Table 22: Protocol Requirements Table for VGTT with 16 GTT lengths.................................................................................... 62
D_OF.doc
Table 23: Test Tool / Test Mode Requirements for FLOBR/TOBR ............................................................................................ 62
Table 24: User Interface Requirements Table for FLOBR .......................................................................................................... 65
Table 25: User Interface Requirements Table for TOBR............................................................................................................. 68
Table 26: User Interface Requirements Table for VGTT with 16 GTT lengths .......................................................................... 69
Table 27: Affected Command Specifications............................................................................................................................... 69
Table 28: Hardware Requirements Table for VGTT with 16 GTT lengths ................................................................................. 70
Table 29: Hardware Requirements Table for FLOBR ................................................................................................................. 70
Table 30: Performance Requirements Table for VGTT with 16 GTT lengths ............................................................................. 71
Table 31: Performance Requirements Table for FLOBR and TOBR .......................................................................................... 71
Table 32: Measurement Requirements Table for FLOBR and TOBR ......................................................................................... 72
Table 33: Upgrade Requirements Table ....................................................................................................................................... 73
Table 34: Document Approval Checklist ............................................................................................ Erreur ! Signet non défini.
Table 35: Protocol Requirements Table for GTT Actions ........................................................................................................... 83
Table 36: User Interface Requirements Table for GTT Actions .................................................................................................. 84
Table 37: Hardware Requirements Table for GTT Actions ......................................................................................................... 86
Table 38: Performance Requirements Table for GTT Actions .................................................................................................... 86
Table 39: Measurement Requirements Table for GTT Actions ................................................................................................... 86
Table 40: Upgrade Requirements Table for GTT Actions ........................................................................................................... 87
List of Figures
Figure 1: GTT hierarchy algorithm for FLOBR............................................................................................................................. 9
Figure 2: GTT selection with FLOBR CdPA Mode .................................................................................................................... 11
Figure 3: GTT selection with FLOBR CgPA Mode .................................................................................................................... 12
Figure 4: Action when subsequent translation search fails .......................................................................................................... 15
Figure 5: Action when subsequent SELID search fails ................................................................................................................ 16
Figure 6: Action when same GTT set type is referred more than once ........................................................................................ 17
Figure 7: Limiting the number of database searches .................................................................................................................... 18
Figure 8: FLOBR/TOBR main protocol flow (1 of 2) ................................................................................................................ 22
Figure 9: FLOBR/TOBR main protocol flow (2 of 2) ................................................................................................................. 23
Figure 10: Effect of TESTMODE on a GTTSET with 10/16 GTT lengths ................................................................................. 40
Figure 11: Interaction between FALLBACK and TESTMODE options ..................................................................................... 41
Figure 12: Find CdPA GTA GTT translation (FLOBR way)....................................................................................................... 43
Figure 13: Find CgPA GTA GTT translation (FLOBR way)....................................................................................................... 44
Figure 14: Find OPC translation (FLOBR way) .......................................................................................................................... 45
Figure 15: Find CgPA SSN GTT translation (FLOBR way) ....................................................................................................... 46
Figure 16: Find CdPA SSN GTT translation (FLOBR way) ....................................................................................................... 47
Figure 17: Find CgPA PC translation (FLOBR way)................................................................................................................... 48
Figure 18: Find Opcode translation (FLOBR way) ...................................................................................................................... 49
Figure 19: Find translation using CdPA SELID (FLOBR way)................................................................................................... 50
Figure 20: Find translation using CgPA SELID (FLOBR way)................................................................................................... 51
Figure 21: Translation with GTT Action set ................................................................................................................................ 82
D_OF.doc
Figure 22: GTT Action set entry .................................................................................................................................................. 82
D_OF.doc
1.0 INTRODUCTION
1.1 Purpose and Scope
This document describes the requirements for the following features:
PR 114149 : TCAP Opcode Based Routing (TOBR) (also covers Flexible Link set Optional Based Routing feature)
PR 113121 : TCAP Segmented SMS Support Phase 2
This document also covers the following enhancements:

PR 127100 : VGTT with 16 GTT lengths (a synonym for Support for 16 GTT Lengths in VGTT feature)
PR 84148 : Increasing # of B-Trees supported on Eagle
These features shall be implemented in EAGLE.
The user of this document should be aware of the existing GTT, EGTT, VGTT, AMGTT, Hex Digit GTT, SCCP Loop
Detection, Flexible GTT load sharing and Origin Based SCCP Routing, ANSI/ITU/CHINA SCCP Conversion, SEAS and
FTRA functionalities for TOBR feature.
The user of this document should also be aware of the existing TCAP Segmented SMS Supported Phase 1 feature functionality
and MAP protocols for TCAP Segmented SMS Support Phase 2 feature.
The scope of this document is to describe:

1. General description of the feature
2. Limitations of implementation
3. Upgrade considerations
4. Inter-working with existing EAGLE features
5. External feature dependent hardware and interconnecting requirements
6. Inter-working with other systems and features.
1.2 Acronyms and Terminology
Table 1: Acronyms and Terminology

For additional acronyms, see Ref Erreur ! Source du renvoi introuvable..
Acronym Description
TOBR TCAP Opcode Based Routing feature
FLOBR Flexible Link set Optional Based Routing feature
OBSR Origin Based SCCP Routing feature
VGTT Variable length GTT feature
AMGTT Advanced GT Modification feature
GMS GSM Map Screening feature
EGMS Enhanced GMS
D_OF.doc
ACN Application Context Name

VGTT with 16 GTT A synonym for “Support for 16 GTT Lengths in VGTT” feature
lengths
2.0 GENERAL DESCRIPTION

2.1 VGTT with 16 GTT lengths - Enhancement
When VGTT feature is turned ON, GTT/EGTT feature(s) will allow the user to provision 10 different digit length B-Trees per
TT/GTTSET. We are enhancing the VGTT functionality to support up to 16 different digit length B-Trees with an ON only
FAK.
Since more search time is needed at run time, we can’t support TSM/SCCP and DSM/VSCCP cards when this feature is
enabled. E5-SM4G or better card is required to support this feature.
Only the CdPA GTA and CgPA GTA GTTSETs support VGTT with 16 GTT lengths. We continue to support 1 million
translations on Eagle.
2.2 Increasing # of B-Trees supported on Eagle – An Engineering Enhancement

Currently the number of B-Trees supported is limited to 55,220 per card on Eagle.
With VGTT with 16 B-Trees enhancement, we need to support additional (number of GTTSETs (2000) * (16 – 10) = 12,000)
B-Trees. Hence we are increasing the number of B-Trees supported to 100,000.
Many features like GTT, EGTT, VGTT, OBSR, GMS, EGMS, GWS, LNP, INP etc., use B-Trees to store the data.
2.3 FLOBR Feature

FLOBR introduces the concepts of
Link set based routing : ability to route GTT traffic based on the incoming link set and
Flexible routing : ability to route GTT traffic based on a variety of parameters (MTP, SCCP and TCAP depending on
features active) in a flexible order on a per-translation basis.
The subsequent sections describe these concepts in detail.
Throughout this document, the figures and examples are explained combining OBSR, FLOBR and TOBR features. The
FLOBR and TOBR specific examples without OBSR shall be less complicated and falls into the subset of the examples
mentioned in this document.
2.3.1 Linkset Based Routing

With FLOBR feature turned ON, Eagle 5 ISS will optionally consider incoming link set as part of GTT selection for
performing Global title translation. In other words, if Eagle receives MSUs with same routing information on different link set,
it will have the flexibility to route them based on different GTT rules. This behavior will also extend to the messages that fall
through to GTT after being processed by MPS based services on Eagle. Incoming link set of the original MSU will be used for
such fall-through messages. Eagle generated MSUs will be handled differently since they do not have a valid incoming link set.
A separate set of GTT selector entries will be provisioned for Eagle-generated MSUs. Refer Erreur ! Source du renvoi
introuvable. for an example use case of link set based routing.
D_OF.doc
2.3.1.1 FLOBR GTT Hierarchies

Apart from existing OBSR GTT hierarchies, FLOBR feature introduced four more GTT hierarchies as shown in Table 2. The
OBSR and FLOBR respective GTT hierarchies shall be available only when the respective feature is enabled/turned ON.
However, all the GTT hierarchies are available when both OBSR and FLOBR features are enabled/turned ON.
The GTT hierarchy can be provisioned per link set basis or system wide basis. The default GTT hierarchy is CdPA only.
Please see Erreur ! Source du renvoi introuvable. for more information on how to provision and change the GTT hierarchy
on per link set basis and system wide basis. (The provisioning method of a GTT hierarchy on a linkset or system wide is not
changed with FLOBR)
Table 2: Available GTT hierarchies

Available GTT Hierarchies (Default GTT Hierarchy is : CdPA only)
EGTT only OBSR only FLOBR only OBSR & FLOBR
CdPA only CdPA only CdPA only CdPA only
Adv. CdPA, CdPA FLOBR CdPA only Adv. CdPA, CdPA
CgPA, Adv. CdPA, CdPA FLOBR CgPA only CgPA, Adv. CdPA, CdPA
Adv. CdPA, CgPA, CdPA FLOBR CgPA, FLOBR CdPA Adv. CdPA, CgPA, CdPA
Adv. CdPA, CdPA, CgPA FLOBR CdPA, FLOBR CgPA Adv. CdPA, CdPA, CgPA
CgPA, CdPA CgPA, CdPA
CdPA, CgPA CdPA, CgPA
CgPA only CgPA only
FLOBR CdPA only
FLOBR CgPA only
FLOBR CgPA, FLOBR CdPA
FLOBR CdPA, FLOBR CgPA
D_OF.doc
Get the GTT hierarchy on

the Incoming LinkSet
Get the first GTT Mode

from GTT hierarchy of the
Incoming LinkSet
Perform the GTT Selector Get the next GTT Mode

lookup to determine the from GTT hierarchy of the
GTTSET incoming LinkSet
No
Is this the
Is Is there a database failure
Yes No No last GTT Mode in the
GTTSET Found? or software error? GTT hierarchy Yes
FLOBR Is GTT hierarchy specific OBSR

to FLOBR/OBSR?
Yes
Yes
Is GTTSET provisioned
No
as per OBSR rules?
Entire GTT
hierarchy Translation
Find the matching Failed
translation OBSR way Failed (and thus
Find the matching MSU failed)
translation FLOBR way (See OBSR FD for
more info)
Yes OBSR
Is Translation Found? No Is there a Database failure No Is GTT hierarchy specific FLOBR

or software error? to FLOBR/OBSR?
Yes
Return
translation
Figure 1: GTT hierarchy algorithm for FLOBR
There are some differences in which OBSR and FLOBR GTT hierarchies work.
As shown in Figure 1, in case of “FLOBR CdPA, FLOBR CgPA” GTT hierarchy, if a GTT Selector is not found for
CdPA then we use CgPA GTT mode. However, if a GTT Selector is found for CdPA and no translation is found for
CdPA, then the MSU shall be discarded, we don’t go to the next GTT mode in the hierarchy.
In OBSR, when a translation is not found in a GTT mode, we go to the next GTT mode in the hierarchy.
Table 2 shows the available GTT set types based on the feature combinations. When FLOBR is enabled/ON, user
can provision any available GTT set type (as long as that GTT set is already provisioned in GTTSET table and
domains are matching) for CdPA GTTSET and CgPA GTTSET in GTT selector table.
D_OF.doc
Table 3: Available GTT set types in selector table

Available GTT set types for
Feature Combination CdPA GTT selectors CgPA GTT selectors
EGTT CdPA GTA -
OBSR CdPA GTA CgPA GTA, CgPA PC
FLOBR CdPA GTA Same as CdPA GTT selectors
FLOBR + TOBR CdPA GTA, Opcode, CdPA SSN Same as CdPA GTT selectors
FLOBR + OBSR CdPA GTA, CgPA GTA, CgPA Same as CdPA GTT selectors
SSN, CgPA PC, OPC
FLOBR + TOBR + OBSR CdPA GTA, CgPA GTA, CgPA Same as CdPA GTT selectors
SSN, CgPA PC, OPC, Opcode,
CdPA SSN
However, the GTT hierarchy on a link set on which the MSU arrived may be OBSR specific or FLOBR specific.
If the GTT hierarchy on a link set is FLOBR specific and user has provisioned any GTT set type for CdPA and/or
CgPA GTTSET, then FLOBR works as per the functionality described in this document.
However, if the GTT hierarchy on a link set is specific to OBSR and user provisioned any GTT set type for CdPA
and/or CgPA GTTSET, then the OBSR functionality, as described in Erreur ! Source du renvoi introuvable., is
still applicable. That means
• If user has provisioned a GTT set type other than CdPA GTA for CdPA GTTSET, then this will be treated as
if the GTT Selection failed.
• If user has provisioned a GTT set type other than CgPA GTA and CgPA PC for CgPA GTTSET, then this
will be treated as if the GTT Selection failed.
Since enabling of FLOBR feature requires only EGTT feature, only EGTT and FLOBR features specific GTT
hierarchies shall be supported. Since only CdPA GTA set type is supported when EGTT feature is ON, user must be
able to provision only CdPA GTA set type for CdPA GTTSET and/or CgPA GTTSET. To provision other set types,
user needs to enable/turn ON the OBSR and/or TOBR features.
2.3.1.2 GTT selection with FLOBR GTT Modes
The following figures show how the GTT selection is made for a FLOBR GTT hierarchy.
D_OF.doc
Flexible CdPA
GTT Mode
Search GTT Selector table for

CdPA selector : GTI, Domain,
TT, NP, NAI and Linkset
Is CdPA
Yes No
GTTSET Found?
Database
search count = 0
No
Is there a database or
Is set type of Yes
software error?
CdPA GTTSET
Find CdPA GTA Find CgPA SSN

Translation CdPA GTA CgPA SSN Translation Is this the
(FLOBR way) Entire GTT
(FLOBR way) No last GTT Mode in the Yes
hierarchy
GTT hierarchy
Find CgPA GTA Find Opcode Failed and thus
Flexible CgPA
Translation CgPA GTA Opcode Translation MSU failed
GTT Mode
(FLOBR way) (FLOBR way) Translation
failed
Find CdPA SSN Find OPC
Translation CdPA SSN OPC Translation
(FLOBR way) (FLOBR way)
CgPA PC
Find CgPA PC
Translation
(FLOBR way)
Figure 2: GTT selection with FLOBR CdPA Mode
D_OF.doc
Figure 3: GTT selection with FLOBR CgPA Mode
2.3.2 Flexible Routing with GTT Translations

With OBSR, we have CdPA GTA, CgPA GTA, CgPA SSN, OPC and CgPA PC translations.
TOBR feature introduced two more new translations: CdPA SSN and Opcode.
With OBSR,
A CdPA GTA translation can have Advanced CdPA translation data, i.e., a CdPA GTA translation can point to
o CgPA PC or (CgPA)SELID or CgPA GTA GTTSET and/or
o an OPC GTTSET.
When a SELID is provisioned, the CgPA parameters in the incoming MSU shall be used to derive a GTTSET
from GTT Selector table.
A CgPA GTA, OPC and CgPA PC translations can only point to CgPA SSN GTTSET. (SELID not supported)
D_OF.doc
A CgPA SSN translation can’t point to additional GTTSETs and SELID is not supported That means CgPA SSN
translation shall be the terminating point while searching for matching translation.
As shown in Table 4, with FLOBR feature, any translation can point to any one of other GTTSETs, except to the same GTT set
type. The CdPA GTA, CdPA SSN and Opcode translations can also point to an OPC GTTSET in addition. For CdPA GTA,
CdPA SSN and Opcode translations, if a GTTSET/SELID is provisioned in addition to OPC GTTSET, then GTTSET/SELID
shall take precedence over OPC GTTSET.
When a FLOBR GTT hierarchy is provisioned on a link set, we don’t need to search the translations in a predetermined
fashion like OBSR (as described above, a specific translation can only point to specific GTTSETs and CgPA SSN translation
shall be the terminating point). As long as a translation points to another GTTSET/SELID, we keep searching in the database.
Since this leads to infinite searching, the number of searches is limited by the following conditions:
Same GTT set type can’t be referred more than once. Since we support a maximum of 7 GTT set types with TOBR
feature development, this limits the number of searches to 7. and
Number of database searches is limited to 7.
Please see sections 2.3.2.1.3 and 2.3.2.1.4 for more information on the above conditions.
The original SELID parameter is specific to CgPA selectors and is used only with OBSR feature. With FLOBR a CdPA
SELID is also supported. When a CdPA SELID/CgPA SELID is provisioned in the translation, the corresponding parameters
(CdPA/CgPA) in the incoming MSU shall be used to derive a GTTSET from GTT Selector table.
Table 4: Flexible Routing with GTT Translations

CdPA GTA Mutually exclusive
Translation Routing CdPA CgPA CdPA CgPA CgPA CdPA CgPA OPCODE OPC
Data SELID GTA GTA PC SSN SSN GTTSN GTTSN
SELID
+ GTTSN GTTSN GTTSN GTTSN GTTSN
CgPA Conversion N/A
GTTSET∗
CgPA GTA Mutually exclusive

SELID
CgPA Conversion N/A
GTTSET∗
CgPA PC Mutually exclusive

SELID
CgPA Conversion N/A
GTTSET∗
∗
Required for ANSI/ITU/CHINA SCCP Conversion on CgPA. See section 2.8 for more information.
D_OF.doc
Mutually exclusive
OPC Translation CdPA CgPA CdPA CgPA CgPA CdPA CgPA OPCODE OPC
Routing Data SELID SELID GTA GTA PC SSN SSN GTTSN GTTSN
CgPA Conversion N/A
GTTSET∗
CgPA SSN Mutually exclusive

SELID
CgPA Conversion N/A
GTTSET∗
CdPA SSN Mutually exclusive

SELID
CgPA Conversion N/A
GTTSET∗
Mutually exclusive
Opcode Translation CdPA CgPA CdPA CgPA CgPA CdPA CgPA OPCODE OPC
Routing Data SELID SELID GTA GTA PC SSN SSN GTTSN GTTSN
CgPA Conversion N/A
GTTSET∗
With FLOBR turned ON, it is possible that the translations are provisioned using flexible routing mechanism. However, the
GTT hierarchy on the link set on which the MSU arrives would have been set to one of OBSR GTT hierarchies. In this
scenario, since the GTT hierarchy is specific to OBSR, the OBSR rules shall be applied while finding the matching translation.
For example, for Advanced CdPA Mode, if a CdPA translation contains CdPA SELID and OPC Set, while finding the
matching translation the CdPA SELID shall be ignored and searched the matching translation only in OPC Set.
With FLOBR, each translation supports a CgPA GTA conversion GTTSET as part of the routing data. Please see section 2.8
for more information.
2.3.2.1 Fallback Option with FLOBR
With FLOBR, user can provision a fallback option for each translation that tells us how to route an MSU under the following
conditions:
∗
Required for ANSI/ITU/CHINA SCCP Conversion on CgPA. See section 2.8 for more information.
D_OF.doc
Routing when subsequent search failed in FLOBR

Routing when same GTT set type is referred more than once
Limiting the number of database searches for FLOBR
The fallback option shall take “Yes” or “No” values.
Under the above conditions

When fallback option in last matched translation is set to “No”, the GTT will fail and MSU shall be discarded.
When fallback option in last matched translation is set to “Yes”, the GTT will be performed based on that matched
entry.
The fallback option can be configured on a system wide basis and on a per-translation basis. The system wide option will be
configured using the SCCPOPTS command and will be used to define the default value (“No”) for all translations by default.
Each translation may then be configured to use one of the fallback values. The per-translation option will override the system
default just for that translation. Any translation that is not changed using CHG-GTA command will continue to use the system
default after upgrade.
For OBSR hierarchy the value of fallback option shall be ignored.
The scenarios for above conditions shall be discussed in subsequent sections.
2.3.2.1.1 Routing when subsequent GTT set search failed in FLOBR
For example: The GTT selector resulted in “Set 1” and the matching translation in “Set 1” points to “Set 2”. The matching
translation in “Set 2” points to “Set 3” and there is no matching translation found in “Set 3”. Since the fallback option in “Set
2” matched translation is set to “No”, the MSU shall be dropped.
Figure 4: Action when subsequent translation search fails
If the matching translation would have not found in “Set 2” (that means “Set 2 Translation” in Figure 4 is not found) and since
the fallback option value in “Set 1” translation is set to “Yes”, the MSU shall be routed based on the routing data in “Set 1
Translation”.
D_OF.doc
If the matching translation in “Set 2” doesn’t contain any GTTSET/SELID (that means “Set 3” GTTSET as shown in Figure 4
is not provisioned), then the fallback option shall be ignored and the MSU shall be routed based on routing data in the “Set 2
Translation”.
If the matching translation in “Set 1” is not found, then the MSU shall be discarded.
2.3.2.1.2 Routing when subsequent search for SELID failed in FLOBR
For example: The GTT selector resulted in “Set 1” and the matching translation in “Set 1” (i.e., CdPA SSN/Opcode/CdPA
GTA translation) contains SELID/”Set 2” and also “Set 3” (in this case “Set 3” shall be OPC GTTSET).
Figure 5: Action when subsequent SELID search fails
If a matching GTT selector is not found when “Set 1 Translation” contains SELID, we continue to search for matching
translation in “Set 3”. If a matching translation is found in “Set 3” and no matching translation is found in “Set 4”, the fallback
option “No” in “Set 3 Translation” shall be executed and hence the MSU shall be discarded.
If a matching GTT selector is not found when “Set 1 Translation” contains SELID AND if a matching translation is not found
in “Set 3”, the fallback option “Yes” in “Set 1 Translation” shall be executed and hence the MSU shall be routed based on the
routing data in “Set 1 Translation”.
If a GTT selector with SELID results in already referred GTT set type, action based on fallback option in “Set 1 Translation”
shall be taken.
2.3.2.1.3 Routing when same GTT set type is referred more than once
With FLOBR feature, since any translation can point to any other GTTSET (except to the same GTT set type) and/or
CdPA/CgPA SELID, it is possible that the same GTT set type can be referred more than once in that chain (as indicated in
Figure 6). This condition can be detected at run time, but can’t be prevented while provisioning. At run time when same set
type is referred more than once, then the GTT processing shall be stopped and action will be taken based on the fallback option
in the last matched translation. This logic is not applicable for CGPA/CDPA SELID. That means CGPA/CDPA SELID can be
referred more than once during the search process as long as number of searches are limited to 7.
D_OF.doc
Since the same set type is not searched more than once, this also prevents the infinite searching for a matching translation.
Since we have only CdPA GTA, CgPA GTA, CgPA PC, OPC, CdPA SSN, CgPA SSN, Opcode set types, we never search
beyond 7 set types to find a matching translation.
Figure 6: Action when same GTT set type is referred more than once
Set 1
(Resulted from GTT Selector) Set 1 set type : CgPA GTA
Translation Routing Data +

Set 1 Translation Fallback = Yes Set 2 Set 2 set type : Opcode
CgPA Conversion GTTSET
Search Translation Table

Set 2 Translation Fallback = No Set 3 Set 3 set type : CdPA GTA

Set 3 Translation Fallback = Yes Set 4 Set 4 set type : CdPA SSN
Translation Routing Data + Set 5 set type : CgPA SSN

Set 4 Translation Fallback = Yes Set 5

Set 5 Translation Fallback = No Set 6 Set 6 set type :OPC

Set 6 Translation Fallback = Yes Set 7 Set 7 set type : CgPA PC

Set 7 Translation Fallback = No Set 8 Set 8 set type : Opcode
In Figure 6, since Opcode set type is already searched (“Set 2”), we don’t try to find a matching translation in “Set 8”. Since
the last matched translation is found in “Set 7” and the fallback option is set to “No”, the MSU will be discarded. A UIM
“1413: GTT(FLOBR) failure: duplicate set type” shall be generated to describe the condition.
In Figure 6, if “Set 7 Translation” doesn’t contain any GTTSET/SELID (if “Set 8” is not provisioned in “Set 7 Translation”),
the MSU shall be routed based on the routing data in the “Set 7 Translation”.
In Figure 6, if “Set 7 Translation” would have not found and since the fallback option in “Set 6 Translation” is set to “Yes”, the
MSU shall be routed based on the data in “Set 6 Translation”.
2.3.2.1.4 Limiting the number of database searches for FLOBR
To maintain the E5-SM4G card performance numbers, the number of database searches is limited to 7 when FLOBR is turned
ON. This includes searching the GTT Selector table when a translation contains CgPA/CdPA SELID parameter.
D_OF.doc
Figure 7: Limiting the number of database searches
As shown in Figure 7, when a translation contains CdPA/CgPA SELID, the search in the GTT Selector table is also counted
towards maximum 7 searches. After completing 7 searches, if the search is terminated because of maximum 7 search criteria,
the action defined in the last matched “Set 4 Translation” fallback option (in this case “No”) shall be executed and MSU shall
be discarded. A UIM “1412: GTT(FLOBR) failure: max search depth” shall be generated to describe the condition.
After completing 7 searches, if the last matched translation contains no GTTSET/SELID data (if CdPA SELID data is not
provisioned in “Set 4 Translation”) , the MSU shall be routed based on the routing data in “Set 4 Translation”.
Please note that the first GTT selector search when the GTT functionality is selected (deriving “Set 1” in Figure 7) won’t be
counted towards maximum 7 search criteria.
2.3.3 GTT for Eagle-generated MSUs
Eagle performs GTT on some messages generated by itself. These messages are sent in response to queries received by local
subsystems. SCCP UDTS and XUDTS messages also fall under this category. GTT is performed to find the destination for the
responses when SCCP Calling party address in query messages was Route-on-GT. Since there is no valid incoming link set for
such Eagle-generated messages, a special set of GTT selector entries will be used when FLOBR is turned ON.
ENT/CHG/RTRV/DLT-GTTSEL commands shall support a new parameter, “EAGLEGEN”, to provision a GTT selector for
Eagle-generated MSUs. This parameter shall take “YES” as a parameter value. The initial value in the database is “NO”.
User can provision a GTT selector for Eagle-generated MSUs by specifying EAGLEGEN=YES along with GTI, domain, TT
and (NP and NAI if GTII/GTIN/GTIN24=4).
D_OF.doc
While provisioning, when user specifies EAGLEGEN=Yes

Any CgPA related parameters, Link set Id and SELID parameters are not valid.
FLOBR feature must be turned ON.
A GTTSET with CdPA GTA set type must be specified.
A dummy link set name “Eagle-Gen” shall be displayed in the RTRV-GTTSEL command response.
After creating the GTT selector entry for Eagle-generated MSUs with ENT-GTTSELcommand, user must be able to change
the GTTSET to point to any other GTTSET (other than “none”) as long as the set type is same and EAGLEGEN=YES is
specified in CHG-GTTSEL command.
User must be able to delete the GTTSET for Eagle generated MSUs with DLT-GTTSEL command by specifying
EAGLEGEN=YES.
If no match is found in the entries with EagleGen=Yes, the entries with LinkSetID=ANY will be searched for. If a matching
entry is still not found, for GTIx=4 entries, the GTTSET with CdPA set type for NP=Default NAI=Default shall be returned
(For GTIx=2, match not found shall be returned) FLOBR hierarchies will NOT apply on Eagle-generated messages and
“CDPA Only” mode will be used for such translations.
2.3.4 GTT Selector Key
Table 5 defines the keys into GTT Selector table based on the feature combination. Please note that if a feature supports
specific parameters and if that feature is not enabled, then default values shall be entered into the database.
Table 5: GTT Selector Key

Feature Selector GTI, Domain, TT, (NP and NAI if CgPA SSN SELID Link set Id
Combination Type GTII/GTIN/GTIN24=4)
EGTT CdPA only √ - - -
CdPA √ - - -
OBSR CgPA √ √ √ -
CdPA √ - √ √
FLOBR CgPA √ - √ √
CdPA √ - √ √
FLOBR + OBSR CgPA √ √ √ √
Eagle-generated CdPA only √ - - √
MSUs (See section
2.3.3
2.3.5 Searching order in GTT Selector Table with FLOBR
Table 6 shows the searching order for CgPA and CdPA GTT selectors when FLOBR is turned ON.
D_OF.doc
Table 6: GTT Selector searching order with FLOBR

CdPA GTT selector keys with FLOBR
Priority GTI, Domain, TT, (NP and NAI if Link set Id SELID CdPA GTT Selector Found /
GTII/GTIN/GTIN24=4) Not Found
1 Exact Exact Exact If “meaningful” CdPA GTTSET
2 Exact Any Exact is provisioned for the GTT
Selector keys, the GTT Selector
is considered found. Else not
found.
CgPA GTT Selector keys with FLOBR

Priority GTI, Domain, TT, (NP and NAI if Link set Id SELID CgPA CgPA GTT Selector
GTII/GTIN/GTIN24=4) SSN Found /
Not Found
1 Exact Exact Exact Exact If “meaningful”
2 Exact Exact Exact Any CgPA GTTSET is
provisioned for the
3 Exact Any Exact Exact GTT Selector keys,
4 Exact Any Exact Any the GTT Selector is
considered found.
Else not found.
Eagle-Gen GTT selector keys with FLOBR

Priority GTI, Domain, TT, (NP and NAI if Link set Id Eagle-Gen GTT Selector Found /
GTII/GTIN/GTIN24=4) Not Found
1 Exact “Eagle-Gen” If CdPA GTTSET with CDGTA set type is
2 Exact Any provisioned for the GTT Selector keys, the
GTT Selector is considered found. Else not
3 For GTIx = 4, the GTTSET with Any found.
NP=DFLT and NAI=DFLT
NOTE : In case of OBSR GTT hierarchy “meaningful” means following the OBSR rules (CdPA GTTSET must be of
type CDGTA and CgPA GTTSET must be of type CGGTA/CGPC). However, if it is a FLOBR GTT
hierarchy any GTTSET is okay.
2.4 TOBR
TOBR provides Eagle with the ability to route messages based on their Operation codes. With TOBR feature ON, Eagle will
consider the following information contained in TCAP portion of messages for performing GTT.
ITU Messages
• Message Type / Package Type
• Application Context Name
• Operation Code
ANSI Messages
D_OF.doc
• Package Type
• Operation Code Family
• Operation Code Specifier
2.4.1 TOBR protocol handling
The flowchart below gives an overview of how FLOBR and TOBR fit into the existing GTT functionality.
D_OF.doc
Figure 8: FLOBR/TOBR main protocol flow (1 of 2)
GTT required on MSU

(including "fall through
to GTT" cases from
Services)
Set GTT hierarchy to

CDPA only. Set a flag to
Eagle-
indicate that
generated Yes
"EagleGen=yes" selector
MSU?
entries are to be
searched.
No
Set LinksetID to
incoming Link set for
GTT Selector search.
Set GTT hierarchy

based on incoming
linkset
Perform GTT
Is GTT hierarchy
No as per EGTT/
FLOBR type?
OBSR
Yes
Is TOBR ON? No
Perform GTT FLOBR way

based on linksetID, GTT
Yes hierarchy, CDPA and CGPA
information from the MSU.
A A1
Done
D_OF.doc
Figure 9: FLOBR/TOBR main protocol flow (2 of 2)
Segmented
XUDT/XUDTS
No
Decode TCAP portion and derive {MsgType/

opcode/ACN} from ITU TCAP messages or Yes
{PkgType/opcode spec/opcode Family} from ANSI
TCAP messages.
TCAP Msg type

No
supported
Yes
Set Opcode/Family/ACN to
Set Message Type to "INVALID"
"NONE" for performing GTT if Decoding
No for performing GTT. This is not
decoder was unable to decode successful
considered an error.
these fields.
Yes

based on this TCAP
A1 based on CDPA SSN,
information, CDPA SSN,
LinksetID, GTT hierarchy along
LinksetID, GTT hierarchy along
with other CDPA and CGPA
with other CDPA and CGPA
information
information
Pre-FLOBR/
Is GTT
No TOBR Error
successful
Handling
Yes
Route MSU based

on GTT results
Done
D_OF.doc
2.4.2 TCAP Decoding
As part of TOBR feature, Eagle will attempt to decode TCAP portion of all UDT/UDTS/Unsegmented XUDT/Unsegmented
XUDTS queries coming to SCCP cards for GTT. Messages will be decoded only if any Opcode Quantity feature is turned ON.
The objective of this decoder is not to validate the correctness of the message but simply to fetch the required TCAP data. It
will thus validate the message for only as much encoding rules as are required to successfully decode the required TCAP
information. In general, Tag-Length-Value encoding is validated; unsupported Tag values will be skipped if encountered,
unless a specific Tag order is expected. If decoding fails, the message will still undergo GTT using some default values for the
TCAP data that denote their absence in the message.
TOBR supports the following messages:

ITU TCAP:
• Begin
• Continue
• End
• Abort
• Unidirectional
ANSI TCAP:
• Unidirectional
• QueryWithPermission
• QueryWithoutPermission
• Response
• ConversationWithPermission
• ConversationWithoutPermission
• Abort
If the message/package type is NOT one of those mentioned in the list above, Eagle will treat it as an unknown message type
and will not proceed with the decoding. This is not considered an error, because many non-TCAP SCCP messages are
processed by EAGLE. For these messages, TCAP data will not be used for routing. If an opcode translation set is encountered
while performing GTT, it will be considered as “translation not found” case in that set.
Note: Such messages can still be routed based on last matched translation depending on its fallback option. Refer Section
2.3.2.1 for more details on Fallback option.
ACN will be used for all supported ITU TCAP messages except ABORT. No attempt to retrieve ACN will be made for Abort
messages. All other supported messages may have a Dialog portion containing Dialogue Request / Unidirectional Dialogue /
Dialogue Response PDU, from which the ACN will be retrieved. If no Dialog portion is detected, then ACN is assumed to be
NONE.
TOBR will attempt to find Operation Code (Opcode) in all supported ITU TCAP messages except ABORT. These messages
must contain Invoke or Return Result (Last or Not Last) as the first component. If not, Opcode is assumed to be NONE.
TOBR will attempt to find Operation Family and Specifier in all supported ANSI TCAP messages (except ABORT) containing
an INVOKE component. For all other messages, Family and Opcode are assumed to be NONE.
D_OF.doc
Unless otherwise specified, TCAP length fields shall be validated as follows:

All formats of TCAP lengths (short, long and indefinite) will be supported for ITU TCAP messages. Indefinite form of lengths
will NOT be supported for ANSI TCAP messages. However, Primitive Elements in ITU or ANSI TCAP messages will not be
allowed to have long format or indefinite lengths.
In long format, TOBR will NOT allow more than two bytes of length field. This limitation is considered acceptable because:
1. SCCP Data portion for UDT(S) /Unsegmented XUDT(S) is a 1 byte length field. It has a maximum value of 255
bytes.
2. All TCAP lengths of 255 bytes or less can be encoded with a 2 byte length field.
At any point of time during decoding, if it is found that the current position in TCAP message is extending beyond the SCCP
data portion length, decoder will not proceed.
2.4.2.1 ITU TCAP Transaction portion Decoding
Transaction portion is validated as follows for ITU TCAP messages. Shaded portion indicates the data required by TOBR. If
transaction portion decoding fails, ACN and Opcode are considered to be NONE for performing GTT.
TCAP Layer
0023 01101001 69 .....-- TCAP Length 105
0024 01100010 62 .T-..E. Message Type 98
0025 01100111 67 .....-- Message Length 103
Transaction Portion
0026 01001000 48 .--..-. Originating TX ID 72
0027 00000001 01 .....-- Transaction ID Length 1
0028 00000000 00 ----.-- Originating Transaction ID 00
0026 01001000 49 .--..-. Destination TX ID 72
0027 00000001 01 .....-- Dest Transaction ID Length 1
0028 00000000 00 ----.—- Destination Transaction ID 00
Field Action/Validation
TCAP Length Used to verify that TCAP portion does not extend beyond this length.
Message Type Tag Must be
• Begin (h’62)
• Continue (h’65)
• End (h’64)
• Abort (h’67)
• Unidirectional (h’61).
Note: TOBR will not decode Abort messages any further; Opcode and
ACN are assumed to be NONE.
Message Length Must be correctly encoded as described in Section 2.4.2
D_OF.doc
Origination TX ID Optional. Identified by Tag = h’48
Transaction ID Length Must be in short form. Used to skip the OTID value.
Originating Transaction Skipped
ID
Destination TX ID Optional. Identified by Tag = h’49
Destination Transaction Must be in short form. Used to skip the DTID value.
ID Length
Destination Transaction Skipped
ID
Table 7: TCAP Transaction Validation
2.4.2.2 ITU TCAP Dialogue portion Decoding

TOBR will check for the Dialogue portion immediately after the transaction portion in ITU TCAP messages. The Dialog
Portion is optional. If it is not present or if the decoding fails, ACN is assumed to be NONE. If present, it should be formatted
exactly as defined below. Another objective of the dialogue portion decoder is to find the start of the component portion
irrespective of whether it could successfully decode the dialogue portion to obtain the ACN or not. This is fairly simple if the
Dialogue portion length is encoded as definite since that will tell us the end of dialog portion. However, if the dialog portion
length is encoded as indefinite, decoder will try to traverse the whole dialogue portion based on tag-length-value format. If it
does not succeed in finding the start of component portion, Opcode will be assumed to be NONE for performing GTT.
Dialog portion is validated as follows: shaded portion indicates the data required by TOBR.
Dialogue Portion
0029 01101011 6b .--..-. Dialogue Portion Tag 107
0030 00011000 18 .....-- Length 24
0031 00101000 28 .--..-. External Tag 40
0032 00010110 16 .....-- Length 22
0033 00000110 06 .--..-. Object Identifier Tag 06
0034 00000111 07 .--..-- Length 7
Dialogue-as-ID value
0035 00000000 00 .--..-. CCITT Q Recommendation 00
0036 00010001 11 .....-. Q 17
0037 10000110 86 .--..-. Document 773 (X'305) 1414
0038 00000101 05
0039 00000001 01 .....-.
as(1) 01
0040 00000001 01 .--..-.
dialoguePDU 01
0041 00000001 01 .--..-.
Version1 (1) 01
0042 10100000 a0 .--..-.
ASN.1-type Tag 160
0043 00001011 11 .....--
ASN.1-type Length 11
0044 01100000 60 .....--
Dialogue PDU Selection Dialogue Request Tag
0045 00001001 09 .....--
Request Length 9
Optional Protocol Version
0046 10000000 80 ------- Protocol Version Tag 128
0047 00000010 02 ------- Protocol Version Length 2
0048 00000000 00 ------- Number unused bits in last 0
Octet
D_OF.doc
0049 00000000 01 ------- Protocol Version 1
0050 10100001 a1 .--..-. Application Context name Tag 161

0051 00000011 03 .....-- AC Length 3
0052 00000110 06 .--..-. Object Identifier Tag 6
0053 00000001 01 .....-- Length 1
0054 00000000 00 ----.-- Context Data 00
Optional User Information
Dialog Portion Tag If present, then dialog portion is decoded. If not present, then decoder will
expect this to be component portion.
Dialog Portion Must be correct. This length is stored to be used later for reaching at the start
Length of component portion.
External Tag Must be present
External Tag Length Must be correct
Object ID Tag Must be present
Object ID Length Must be correctly encoded in short form.. Used to skip Dialog-as-
ID/Unidialogue-as-ID value. No restriction has been put on the length value.
(Standards say it must be 7).
Object ID value Skipped. Example above contains Dialogue-as-ID. The only difference in
(Dialogue-as-ID UniDialogue-as-ID is that it has unidialoguePDU (2) in place of
value / dialoguePDU (1).
UniDialogue-as-ID
value)
ASN.1-type Tag Must be present
ASN.1-type Length Must be correctly encoded as described in Section 2.4.2
PDU type tag Must be Dialog Request tag (h’60) or Unidirectional Dialogue tag (h’60) or
Dialogue Response tag (h’61)
PDU Length Must be correctly encoded as described in Section 2.4.2 .
Protocol version tag This is optional. Skipped if present.
Protocol version Must be correctly encoded in short form. Used to skip the remaining bytes in
length Protocol version.
Protocol version Skipped if present
Application Context Must be present
Name Tag
Application Context Must be correctly encoded as described in Section 2.4.2
Length
Object ID Tag Must be present
Object ID Length Must be between 1 and 7 both inclusive.
Context Data This is returned to be used as ACN. It can be of upto 7 bytes.
D_OF.doc
Result Tag This is optional. Skipped if present.1
Result Length Note1: These fields are present only in Response PDUs (AARE APDU).
INTEGER Tag
INTEGER Length
Result
Result Source This is optional. Skipped if present. 1
Diagnostic Tag Note: These fields are present only in Response PDUs (AARE APDU).
Result Source
Diagnostic Length
Result Source
Diagnostic
Optional User This is optional. Skipped if present. 1
information
Table 8: TCAP Dialog Validation
2.4.2.3 ITU TCAP Component Decoding

Component portion for ITU TCAP messages is validated as follows:
Component Portion
0051 01101100 6c .--..-. Component Portion Tag 108
0052 00101111 2f .....-- Component Portion Length 47
Component
0053 10100001 a1 .--..-. Component Tag 161
0054 00101101 2d .....-- Component Length 45
Component Must be h’6C (Component Sequence)
Portion Tag
Component Must be correctly encoded as described in Section 2.4.2
Portion Length
Component Tag Must be
• Invoke (h’A1)
• Return Result – (Last RR-L) (h’A2)
• Return Result – Not Last (RR-NL) (h’A7)
Component Length Must be correctly encoded as described in Section 2.4.2
Table 9: TCAP Component Validation
Only INVOKE and RR-L / RR-NL components are decoded further.
1
These fields are decoded only if the Dialog portion length is encoded as indefinite. It is required to reach at the starting point
for component portion. Lengths are required to skip the fields. If length is invalid, DCD_QRY_INV_LEN_IN_DIALOG error
is returned.
D_OF.doc
INVOKE component is validated as follows. Shaded portion indicates the data required by TOBR. Opcode precedes the
parameter sequence tag.
Invoke ID
0055 00000010 02 .--..-. Invoke ID Tag 2
0056 00000001 01 .....-- Invoke ID Length 1
0057 00000111 07 ----.-- Invoke ID 7
Optional Linked ID
Operation Code
0058 00000010 02 .....-- Operation Code Tag Local Operation Code
0059 00000001 01 .--..-. Operation Code Length 01
0060 00000000 00 .--..-. Operation Code value 0
0061 00110000 30 .--..-. Parameter Sequence Tag 48
0062 00100101 25 .....-- Parameter Length 37
…
…
Invoke ID Tag Must be 2
Invoke ID Length Must be correctly encoded in short form. Used to skip Invoke ID. No
restriction has been put on the allowed length (Standards mention that it must
be 1).
Invoke ID Skipped
Linked ID Tag This is optional. Identified by Tag = h’80.
Linked ID Length Must be correctly encoded in short form. Used to skip Linked ID.
Linked ID Skipped
Operation Tag Must be 2 (Local Operation) or 6 (Global Operation)
Op Code Length Must be correctly encoded and equal to 1.
Op Code Value Returned to be used as Opcode value for performing GTT.
Note: Only 1 byte opcodes are supported.
Table 10: Invoke Component Validation
Return Result-Last and Return Result-Not Last components are validated as follows. Shaded portion indicates the data required
by TOBR. RR-L and RR-NL have the Opcode within a sequence tag
Invoke ID
0073 00000010 02 .--..-. Invoke ID Tag 2
0074 00000001 01 .--..-. Invoke ID Length 1
0075 00000000 00 ----.-- Invoke ID 0
Optional Operation Sequence
MAP Operation Sequence
0076 00110000 30 .--..-. Sequence Tag 48
0077 00010100 14 .--..-. Length 20
D_OF.doc
Operation Code
0078 00000010 02 ---..-. Operation Code Tag Local Operation Code
0080 00101101 2d -T-..E. MAP Operation RoutingInfoForSM
…
…
Invoke ID Tag Must be 2
Invoke ID Length Must be correctly encoded in short form. Used to skip Invoke ID. Used to skip
Invoke ID. No restriction has been put on the allowed length (Standards
mention that it must be 1).
Invoke ID Skipped
Sequence Tag This is optional but is required for an Opcode to be present. Identified by tag
h’30.
Sequence Length Must be correctly encoded as described in Section 2.4.2 .
Operation Tag Must be 2 (Local Operation) or 6 (Global Operation).
Op Code Length Must be 1.
Op Code Value Returned to be used as Opcode value for performing GTT.
Note: Only 1 byte opcodes are supported.
Table 11: Return Result - L/NL Component Validation
Note: TOBR will decode only the first component in the TCAP message.
2.4.2.4 ANSI TCAP Transaction portion Decoding:

Transaction portion of ANSI TCAP message is verified as follows. Shaded portion indicates the data required by TOBR. If
transaction portion decoding fails, Family and Opcode are considered to be NONE for performing GTT.
queryWithPermission
0034 00100111 27 .--..-. Data Portion Length 39
0035 11100010 e2 -T-..E. Package Type ID (Query With Permission) 226
0036 00100101 25 .--..-. Total TCAP Message Length 37
Transaction ID
0037 11000111 c7 .--..-. Transaction ID Identifier 199
0038 00000100 04 .--..-. Transaction ID Length 4
0039 00000000 00 K---.-- Transaction ID 00 01 02 03
0040 00000001 01
0041 00000010 02
0042 00000011 03
D_OF.doc
Data Portion Length Used to verify that the TCAP portion does not extend beyond this length.
Package Type ID Must be one of the following:
• Unidirectional (h’E1)
• QueryWithPermission (h’E2)
• QueryWithoutPermission (h’E3)
• Response (h’E4)
• ConversationWithPermission (h’E5)
• ConversationWithoutPermission (h’E6)
• Abort (h’F6)
Message Length Must be correctly encoded as described in Section 2.4.2
Transaction ID This is optional. Identified by Tag = h’C7.
Transaction ID Length Must be correctly encoded in short form. Used to skip the TID value. No
restriction has been put on the length value (Standards say that it must be
0, 4 or 8 depending on the package type).
Transaction ID Skipped
(Origination and/or
Responding transaction
IDs)
Table 12: TCAP Transaction Validation
2.4.2.5 ANSI TCAP Dialogue portion Decoding:

TOBR will skip the Dialogue portion, if present, in ANSI TCAP messages.
Dialogue Portion Optional. Identified by tag h’F9.
Identifier
Dialogue Portion Must be correctly encoded as described in Section 2.4.2 .
length
Dialogue Portion Skipped
contents
2.4.2.6 ANSI TCAP Component portion Decoding:

Only Invoke (last) and Invoke (not last) components are decoded further to derive Opcode and Family. For all other
components or when the Invoke component decoding fails, Opcode and Family are assumed to be NONE. Component portion
of ANSI TCAP messages is validated as follows. Shaded portion indicates the data required by TOBR.
Component Sequence
0043 11101000 e8 .--..-. Component Sequence Identifier 232
0044 00011101 1d .--..-. Component Sequence Length 29
Invoke
0045 11101001 e9 .--..-. Component Type ID (Invoke) 233
D_OF.doc
0046 00011011 1b .--..-. Component Length 27

Component ID
0047 11001111 cf .--..-. Component ID Identifier 207
0048 00000001 01 .--..-. Component ID Length 1
0049 00101010 2a ----.-- Invoke ID 2a
Operation Code
0050 11010001 d1 .--..-. Operation Code Identifier 209
0052 00001001 09 KT-..E. Operation Family SMSRequest
0053 00110111 37 .--..-. Operation Specifier
…
…
Component Must be h’E8 (Component Sequence)
Sequence
Identifier
Component Must be correctly encoded as described in Section 2.4.2 .
Sequence Length
Component Type Must be
Identifier • Invoke Last (h’E9), or
• Invoke Not Last (h’ED)
Note: Unlike the ITU standards, Return Result (Last or not Last) components
in ANSI do not contain operation codes.
Component Length Must be correctly encoded as described in Section 2.4.2 .
Component ID Must be h’CF
Identifier
Component ID Must be correctly encoded in short form.
Length Used to skip Component ID. No restriction has been put on the length (As per
standards, it must be 0, 1 or 2 octets).
Component IDs Skipped
(Invoke IDs and/or
Correlation IDs)
Operation Code Must be National TCAP (h’D0) or Private TCAP (h’D1)
Identifier
Operation Code Must be equal to 2.
Length
Operation Code Returned to be used as Family and Opcode value for performing GTT.
Note: Only 2 byte Operation Codes are supported. First byte is treated as
Family and second byte as Opcode.
Note: TOBR will decode only the first component in the TCAP message.
2.4.3 TOBR GTT Sets
TOBR feature introduces two new GTT Sets, Opcode and CdPA SSN, with set types “opcode” and “cdssn”.
D_OF.doc
The CdPA SSN GTT set shall behave exactly like CgPA SSN GTT set (as in OBSR).
The opcode GTT set supports translations for ANSI and ITU opcodes.
2.4.4 TOBR Opcode Quantities
Based on the quantity FAK, the translation table shall support a maximum of
3 opcode translations (part number : 893027901) or
1 Million opcode translations (part number : 893027907) (the GTT translation table capacity is controlled by "XGTT
Table Expansion" feature)
The opcodes can be ANSI or ITU. User shall be allowed to provision the Opcode translations only when one of the
quantity FAKs are turned ON.
2.4.5 TOBR GTT Translations
All the TOBR GTT translations shall support AMGTT, SCCP Loop detection, Intermediate GTT load sharing,
ANSI/ITU/CHINA SCCP Conversion and Flexible GTT load sharing features. As indicated in Table 4, the TOBR GTT
translations shall also support flexible routing.
2.4.5.1 TOBR CdPA SSN Translations

User shall be able to provision the CdPA SSN translations with routing data and flexible routing data as shown in Table 4.
2.4.5.2 TOBR Opcode Translations
The opcode translations shall support ANSI or ITU opcodes.
2.4.5.2.1 TOBR translations with ANSI Opcode
The key into ANSI opcode translations is: ANSI opcode specifier (as defined in Erreur ! Source du renvoi introuvable.),
ANSI TCAP Package Type and Family (part of ANSI TCAP opcode field).
The ANSI opcode specifier shall take 0 to 255, “None” and “*” (denotes “Any”) as parameter values. The “none” value
indicates the absence of the opcode in the incoming MSU.
The ANSI TCAP Package Type shall take “Unidirectional”, “Query with Permission”, “Query without Permission”,
“Response”, “Conversation with Permission”, “Conversation without Permission”, “Abort” and “Any” as parameter values.
D_OF.doc
The Family shall take 0 to 255, “None” and “*” (denotes “Any”) as parameter values.
While provisioning, when ANSI TCAP Package type is specified as “Abort”, then ANSI opcode specifier and Family must
only accept “none” value.
Since opcode specifier and family parameters exist together in the incoming MSU, one (opcode specifier or family) parameter
can’t be specified as “none”. Both can be specified as “none” or other than “none”.
2.4.5.2.2 Searching order for TOBR translations with ANSI Opcode
Table 13 shows the searching order for TOBR translations with ANSI Opcode when TOBR is turned ON. The ANSI opcode
translations shall only be matched to ANSI MSUs.
Table 13: Searching order for TOBR translations with ANSI Opcode
Priority TCAP Package Type Opcode (ANSI) Family
1 Exact Exact Exact
(value) (none or number) (none or number)
2 Exact Exact Any
3 Exact Any Exact
4 Exact Any Any
5 Any Exact Exact
6 Any Exact Any
7 Any Any Exact
8 Any Any Any
2.4.5.2.3 TOBR translations with ITU Opcode
The key into ITU opcode translations is: ITU opcode (as defined in Erreur ! Source du renvoi introuvable., Erreur ! Source
du renvoi introuvable., Erreur ! Source du renvoi introuvable.), ITU TCAP Package Type and ACN.
The ITU opcode shall take 0 to 255, “None” and “*” (denotes “Any”) as parameter values. The “none” value indicates the
absence of the opcode in the incoming MSU.
The ITU TCAP Package Type shall take “Begin”, “End”, “Continue”, “Abort”, “Unidirectional” and “Any” as parameter
values.
The ACN shall support 1 to 7 bytes. Each byte shall support 0 – 255, “none” and “Any”. User can provision 1 to 7 bytes. The
“none” value indicates the absence of ACN in the incoming MSU. Though VGTT is not supported for opcode GTT set, user
can provision different digit length ACNs for the opcode GTT set.
While provisioning, when ITU TCAP Package type is specified as “Abort”, then ITU opcode and ACN must only accept
“none” value.
D_OF.doc
Due to performance reasons, user is not allowed to mix the numbers, “None” and “Any” for an ACN. For example,
Table 14: Valid/Invalid ACN values

ACN Does TOBR Info
support this
ACN?
1-2-3-4-5 Yes 6th and 7th bytes will be treated as None.
1-2-3-4-5-6-7 Yes
1 Yes 2nd, 3rd, 4th, 5th, 6th and 7th bytes will be treated as None.
None Yes All the bytes will be treated as None.
Any Yes All the bytes will be treated as any.
1-none-2 No
1-any-3-4 No
Any-1 No
None-any-1 No
2.4.5.2.3.1 Searching order for TOBR translations with ITU Opcode
Table 15 shows the searching order for TOBR translations with ITU Opcode when TOBR is turned ON. The ITU opcode
translations shall only be matched to ITU MSUs.
If any MSU comes with 7 bytes ACN, we try to match the 7 bytes ACN in the database. If we don’t find the 7 bytes match, we
don’t match to 6/5/4/3/2/1 bytes ACN in the database. However, we match to ACN=any entry, if provisioned, in the database.
Table 15: Searching order for TOBR translations with ITU Opcode
Priority TCAP Package Type Opcode (ITU) ACN
1 Exact Exact Exact
(value) (none or number) (none or number)
2 Exact Exact Any
3 Exact Any Exact
4 Exact Any Any
5 Any Exact Exact
6 Any Exact Any
7 Any Any Exact
8 Any Any Any
2.5 TCAP Segmentation SMS Support Phase 2

An objective of TOBR is to provide Eagle with the capability to route segmented TCAP SMS messages in the same manner as
non-segmented TCAP messages are routed. This would mean routing all TCAP SMS messages within a particular transaction
D_OF.doc
to the same place. Routing rules based on OpCode are used route messages for special application handling. These rules work
well for non-segmented TCAP messages. However they do not work well for segmented TCAP messages, because the initial
BEGIN message does not contain an OpCode. These messages must be identified for special routing based on other criteria.
TOBR achieves this discrimination by allowing Eagle to route messages based on the TCAP OpCode and Dialogue portion
information, as already explained in Section 2.4. Eagle shall now be able to use Application Context Name from Dialogue
portion to route TCAP Begin messages without component portion (and thus without Operation code). This way, Eagle can
now apply the same routing rules to messages with ACN and OpCode, ACN only, and OpCode only.
GSM SMS messages work particularly well in this solution, because there is a 1 to 1 correspondence between the ACN and
OpCode (see Section 17.1.6 in Erreur ! Source du renvoi introuvable. for info on shortMsgMO-RelayContext and mo-
forwardSM.)
Refer Erreur ! Source du renvoi introuvable. for more details and use-case examples of how TCAP segmentation is
supported using Opcode based routing.
2.6 AMGTT usage for non-GTA translations

Any translation (CdPA GTA, CgPA GTA, CgPA PC, OPC, CgPA SSN, CdPA SSN and Opcode) can be provisioned with
AMGTT data. However, the AMGTT data will be applied to an appropriate GTA (CdPA or CgPA) only if the GTA existed in
the incoming MSU. If CdPA/CgPA part of the MSU doesn’t contain GTA, the AMGTT data from the matched translation
shall be ignored.
2.7 Effect of ANSI/ITU Translation (PR 59452) feature

The ANSI/ITU translation feature introduced the “CROSS” domain for CdPA GTA GTTSETs. We continue to support
“CROSS” domain only for CdPA GTA GTTSETs with the features defined in this document. However, it is possible that a
CdPA GTA GTTSET with “CROSS” domain can be assigned to CgPA GTT Selector when FLOBR feature is turned ON.
2.8 Interaction with ANSI/ITU/CHINA SCCP Conversion

All translations (CdPA GTA, CgPA GTA, CgPA PC, OPC, CgPA SSN, CdPA SSN and Opcode) support ANSI/ITU/CHINA
SCCP Conversion feature. As a result of the ANSI/ITU/CHINA SCCP Conversion feature, the MSU can be routed to a
different network domain. This is detected by comparing the incoming network domain against the network domain of the
result of GTT (including GTT loadsharing).
ANSI/ITU/CHINA SCCP Conversion performs GTT on CgPA, one of 2 methods will be used:
• If the translation includes a CgPA Conversion Set, then that set will be used with the CgPA GTA information from
MSU to perform GTT in “CdPA-only” mode. Failure to locate translation information in the CgPA Conversion Set
will be fall back to Default Conversion GT information.
• If the translation does not include a CgPA Conversion Set, then CGPA selectors and GT digits from MSU will be
used to perform GTT in CDPA only mode. Note: This is how OBSR was implemented. However, with FLOBR, it is
now possible that the “CdPA-only mode” entry in the GTT Selector table is not of type CdPA GTT. This will be
considered a Conversion failure.
For additional information on ANSI/ITU/CHINA SCCP Conversion, see Erreur ! Source du renvoi introuvable..
For a description of full CgPA processing, see Erreur ! Source du renvoi introuvable.
D_OF.doc
2.9 CgPA searching for AMGTT

If AMGTT is on and the CgPA does not require processing by the ANSI/ITU/China SCCP Conversion feature, then the
EAGLE may search for AMGTT data for the CgPA (depending on the setting of the incoming linkset, or the results of the
GTT). See Erreur ! Source du renvoi introuvable. for details on AMGTT.
This search will be done using the standard CdPA-Only search hierarchy. FLOBR rules will not be applied.
2.10 Interaction with MPS-based features

The MSUs arriving to the GTT from the MPS-based features (fall through to GTT case), will be processed by GTT in the same
fashion as the MSUs arriving to the GTT directly, i.e., the GTT hierarchy and the incoming linkset required for GTT selector
search will be derived from the link set, on which these MSUs came to the Eagle.
2.11 Expanding the GTT selector Table capacity

As part of the FLOBR feature, the capacity of the GTT selector table is increased to support 100,000 GTT selectors (see
section 2.13.5 ). The GTT selector table capacity is increased without any FAK. Hence OBSR, FLOBR and TOBR features
can utilize the increased capacity. However, with EGTT user can only provision a maximum of 21,248 (256 + 256 + 256 +
(256 * 16 * 5)) GTT selectors.
2.12 UIMs
FLOBR and TOBR have not introduced any new UIMs for existing GTT failure cases. They will use the the pre-existing
EGTT/OBSR UIMs. For more information on existing UIMs and the scenarios in which they are raised, refer Erreur ! Source
du renvoi introuvable. section 2.7.
FLOBR will introduce the following new UIMs for new error conditions now possible while performing GTT.
Table 16: New FLOBR UIMs

UIM # Message Text UIM Format Output Group
1 2 3 4
1234567890123456789012345678901234567890
1412 GTT(FLOBR) failure: max search depth I43 (INV CDPA 2) GTT
1413 GTT(FLOBR) failure: duplicate set type I43 (INV CDPA 2) GTT
1414 GTT(FLOBR) warning: max search depth I43 (INV CDPA 2) GTT
1415 GTT(FLOBR) warning: duplicate settype I43 (INV CDPA 2) GTT
1418 SCCP did not route - no SSN in CgPA I43 (INV CDPA 2) GTT
1419 SCCP did not route - no SSN in CdPA I43 (INV CDPA 2) GTT
UIMs 1412 and 1413 will be issued when a MSU is discarded due to the error condition. UIMs 1414 and 1415 will be issued
when the MSU is routed based on fallback information after encountering the error condition.
UIMs 1418 and 1419 will be issued when a CdPA SSN or CgPA SSN GTT Set type is encountered, but the message did not
contain the required SSN, and the message was discarded.
TOBR will NOT generate any UIMs for TCAP decoding error scenarios. If user wants to know the TCAP decoding results, he
can do so by using the trace functionality on Eagle. This will tell him if TCAP decoding was successful and what values were
used for performing GTT. If decoding failed, trace dump will display text that can help identifying the error occurred during
D_OF.doc
decode. An additional service “TOBR” will be supported in the service parameter of ent-trace command. If a trace condition is
entered with service as TOBR, all MSUs which were decoded by TOBR will get trapped. TOBR decoding information will be
displayed if trace is configured in Detailed or Debug Mode.
Note: This would trap even those messages on which no TOBR GTT rule was applied.
2.13 Test Tool
2.13.1 TST-MSG
In order to debug complex FLOBR/TOBR/OBSR rules, a field-safe Test Tool shall be developed. This Test Tool shall be an
extension of the TST-MSG testing method. (For an example implementation see Erreur ! Source du renvoi introuvable.).
The user shall be able to store information required to perform GTT, and then send that information to a Service Module for
GTT analysis. A report shall be generated based on the outcome of GTT. In order to access the Test Tool, FLOBR must be
on.
The user shall have access to 10 test messages in a TST-MSG table for testing. These messages shall be separate from TIF or
TTR messages. The following parameters shall be used:
Table 17: FLOBR Test Tool Parameters

Parameter Description Range Initial Table
Value
Active Is data allowed to be sent to Service Yes, No Yes
Module?
MSGN Message Number in the table 1-10 1 to 10 (this is the
table entry number)
OPC Defines the OPC and the network type Standard PC values ANSI 10-10-10
EagleGen Is this an EAGLE generated message? Yes, No No
Linkset Incoming Linkset Name. Only used if 1 to 10 characters None
EagleGen=No
CdPAGTI Called Party Global Title Indicator 2, 4 2
CdPATT Called Party Translation Type 0-255 0
CdPASSN Called Party Subsystem 0-255, none 6
CdPAPC Called Party Point Code Standard PC values, ANSI 10-10-10
none
CdPANP Called Party Numbering Plan 0-127 1
CdPANAI Called Party Nature of Address Indicator 0-15 1
CdPAGTA Called Party Address 1 to 21 hexadecimal 1234567890
digits
CgPAGTI Calling Party Global Title Indicator 0, 2 or 4 2
CgPATT Calling Party Translation Type 0-255 0
CgPASSN Calling Party Subsystem 0-255, none 8
CgPAPC Calling Party Point Code Standard PC values, ANSI 20-20-20
none
CgPANP Calling Party Numbering Plan 0-127 1
CgPANAI Calling Party Nature of Address Indicator 0-15 1
D_OF.doc
Parameter Description Range Initial Table

Value
CgPAGTA Calling Party Address 1 to 21 hexadecimal 1234567890
digits
TCAPPkg TCAP Package/Message Type (TOBR 0xE1-0xE6, 0xF6 None
only) (ANSI)
0x61, 0x62, 0x65,
0x64, 0x67 (ITU)
none
TCAPOpCode TCAP OpCode (TOBR only) 0-255, none None
TCAPFamily TCAP Family (TOBR only). Only used if 0-255, none None
Package/Message Type is ANSI
TCAPACN TCAP ACN (TOBR only). Only used if ACN input (0 to 7 None
Package/Message Type is ITU numbers), none
The following commands will be impacted:

TST-MSG: This existing command will be updated to allow SCCP data to be sent to service module cards to test
GTT rules. This command invokes the test routine and generates test output.
CHG-SCCP-MSG: this new command will allow the user to change all information required to test
FLOBR/TOBR/OBSR functionality. This command is used to modify test parameters to match the customer’s
provisioning. It does not invoke the test process.
RTRV-SCCP-MSG : this new command will allow the user to display either a single SCCP test message, or all of
the entries in the table. This command is used to display the parameter data that can be modified by CHG-SCCP-
MSG.
Sample Output from TST-MSG (actual output may vary):

1 2 3 4 5 6 7 8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
FLOBR Trace Tool
Input:
OPCN=1024-aa
EAGLE-Generated? No
LSN=ABCD123
CDPA: GTIN=04 TT=250 NP=01 (e164) NAI=04 (intl)
SSN=005 PCN=4096-aa
ADDR=123456789012345678901
CGPA: GTIN=04 TT=100 NP=01 (e164) NAI=04 (intl)
SSN=004 PCN=2046-aa
ADDR=012345678901234567890
TCAP:
Package Type=0x62 (ITUBGN) OpCode=0x16 ACN=None Family=None
GTT Search Results:

Search Hierarchy: FLOBR CdPA
CgPA/CdPA
GTT Set Name Set Type SELID TestMode FallBack Found Matching Key
D_OF.doc
CDPASET1 CDPA -/- Off No Yes 123456789012345678901

CGPASET2 CGPA 10/- Off Yes Yes 0123456789
CGPA GTTSEL 10/- Off No No -
OPCSET1 OPC -/- On No Yes 1-1-1
Maximum Number of Searches: No

Duplicate GTT Set Type Encountered: No
Translation Results:
Transation Found: Yes [GTT Set Name = OPCSET1]
DPCN = 5175-aa
RI = SSN
SSN = 100
2.13.2 Test Mode Provisioning

In order for users to test new rules before they are used for routing, each GTT rule shall have a TESTMODE = ON or OFF
option.
This mode will allow users to enter new rules and validate them with the TST-MSG tool, but not have them change the routing
of actual traffic
If TESTMODE=OFF, then the rule is used for routing purposes. TESTMODE=OFF is the default setting, and represents
standard GTT behavior.
If TESTMODE=ON, then the rule shall have the following characteristics:
• If encountered during processing of a TST-MSG, the rule shall be treated as an active rule. The test data shall follow
this rule, and be a part of the output. This will allow the craftsperson to see what would happen during routing when
TESTMODE is set to OFF
• If encountered during MSU routing, this rule shall be ignored.
Notes about provisioning TESTMODE=ON rules:

1. If an existing rule is changed from TESTMODE=OFF to TESTMODE=ON, for normal routing purposes it is
equivalent to deleting the rule.
2. If entering a GTA that splits an existing range, this is equivalent to deleting that GTA from the range. This is because
the range will be split, and a new entry created. This new entry will not be accessible for routing.
3. If a new rule is entered, but there is a wildcard entry with TESTMODE=OFF in that set, then the wildcard entry will
still be valid and used. For example, if an OpCode set with PackageType=ITUBGN, ACN=None, OpCode=* exists,
and a new rule with PackageType=ITUBGN, ACN=None, OpCode=21, Testmode=ON is added, then normal routing
will ignore the OpCode=21 rule and use the OpCode=* rule.
2.13.2.1 Effect of TESTMODE on a GTTSET with 10/16 GTT lengths
As shown in Figure 10, assume that we have a GTTSET with 10/16 different digit length GTTs and we have a match for a 20
digit translation in that GTTSET to real-time traffic (that means TESTMODE is set to OFF for that translation). Now the user
makes TESTMODE = ON for that 20 digit matching translation using CHG-GTA command.
D_OF.doc
Figure 10: Effect of TESTMODE on a GTTSET with 10/16 GTT lengths
Since TESTMODE is set to ON in 20 digit matching translation, we don’t match that translation for real-time traffic anymore.
We treat this condition as if we didn’t find the 20 digit matching translation and we keep looking for a matching translation in
lesser digit GTTs (i.e., 19, …..8,7,…3 digit GTTs as shown in Figure 10.
However we match that 20 digit number for a test message that contains 20 digit matching number, generated from the TST-
MSG tool.
2.13.2.2 Effect of TESTMODE on Opcode Translations
If user makes TESTMODE = ON for an opcode translation which was matching to real-time traffic previously, the same
translation won’t be matched to real-time traffic anymore. Rather, as specified in section 2.4.5.2.2 , the best matching
translation shall be selected.
2.13.2.3 Interaction between FALLBACK and TESTMODE options
For example: While searching for a matching translation FLOBR way for real-time traffic, say we got “Set 1 Translation”.
We found matching translations with TESTMODE = ON in SELID/Set 2 (and OPC Set) as shown in Figure 11. In this
scenario, since the matching translation with TESTMODE = OFF is not found, we use FALLBACK option of “Set 1
Translation”. Since FALLBACK option is set to YES, we route the MSU based on the “Set 1 Translation” routing data.
Figure 11: Interaction between FALLBACK and TESTMODE options
If “Set1” is the very first GTTSET we found in the searching process and “Set 1 Translation” would have been provisioned
with TESTMODE = ON, then the MSU shall be discarded.
D_OF.doc
2.13.3 Interpretation of “GTT Selector Found” and “GTT Selector Not Found”
While provisioning GTT Selectors, if no CgPA SSN is specified, it is possible that a GTT Selector can have both CdPA
GTTSET and CgPA GTTSET. However, at run-time, if the GTT hierarchy is OBSR specific and resultant CdPA GTTSET /
CgPA GTTSET for a GTT Selector is not following OBSR rules (CdPA GTTSET must be of type CdGTA and CgPA
GTTSET must be of type CgGTA/CgPC), then it is considered as if the GTT Selector is not found. Else it is considered that
GTT Selector is found.
However, the interpretation of GTT Selector found/Not Found is straight forward for FLOBR specific hierarchies. Since the
GTT Selector can contain any type of GTTSET for CdPA and/or CgPA GTTSET, at run-time if a CdPA/CgPA GTT Selector
is found with any GTTSET, it is considered a match. Else it is considered that GTT Selector is not found.
2.13.4 Default CdPA GTTSET
When only basic GTT feature is turned ON, when user enters a GTT selector with GTII=2, a default CdPA GTTSET with
GTII=4 shall be added internally in the database. User can’t see them when only GTT feature is turned ON. However, once
EGTT is turned ON, user can see the selectors with default CdPA GTTSET and change them. But user can’t add any more
default CdPA GTTSET entries.
With FLOBR feature, user can change this default CdPA GTTSET to point to any GTT set type and find the translation
flexibly.
2.13.5 Capacity of GTT Selector Table
Though user perceives the GTT Selector table as a single table, it is actually more than one table in the database. Due to that
reason, the capacity of GTT Selector table shall be calculated as:
100,000 regular CdPA and/or CgPA Selector entries

20,992 Eagle-Gen entries
256 Default CdPA entries
Hence a total of 121,248 GTT Selector entries shall be supported in the database. The RTRV-TBL-CAPACITY command
displays only the SSNSELID table capacity of 100,000 (The remaining entries are stored in other GTT Selector tables).
However, FTRA/CSVGEN(X) shall indicate the total capacity as 121,248.
3.0 FLEXIBLE DATABASE SEARCH ALGORITHMS
The following flowcharts describe the flexible search algorithms for FLOBR and TOBR.
D_OF.doc
D_OF.doc
Figure 12: Find CdPA GTA GTT translation (FLOBR way)

Find CdPA GTA
Translation (FLOBR way)
The “fallback check needed” is an
Search for input parameter for this function and
shall be requested by the called
matching CdPA search function in case the previously
GTA translation found translation has multiple
GTTSETs.
Did we find CdPA

Yes No
GTA Translation?
Fallback No Is there a database failure? Yes
If no B-Tree found
for the number of digits Yes
Store CdPA GTA
in the GTTSET?
translation (This is the
Is fallback option
last matched translation) Return
in last matched translation No No GTT_INV_DIALED_DIGITS
set to yes
Increment
Database search Any other internal
Yes No
count Yes error found? Yes
Return
Any CgPA SELID / Is fallback
Is Database
Yes CdPA SELID / GTTSET (including No check needed?
search count 7
OPC SET) provisioned?
Return that error
Yes
No Go to No
Yes
Fallback Yes
Do we have a last
Any Did we come No
matched translation?
GTTSET found in the across this set type
Yes No
CdPA GTA Translation (other already during search
than OPC SET)? Return
process?
GTT_ENTRY_NOT_FOUND
No
Route the MSU based on Entire GTT
the routing data in the last hierarchy
matched translation Failed and thus
CgPA SELID found in the CdPA SELID found in the No MSU
No
CdPA GTA Translation? CdPA GTA Translation? failed
No
Yes Yes
Find translation using Find translation using Find translation using Any CgPA SELID /
CgPA SELID (FLOBR way) CdPA SELID (FLOBR way) that GTTSET (FLOBR way) CdPA SELID / GTTSET (including
OPC SET) provisioned in CdPA GTA
Translation?
If first translation is not found successfully in above functions, then we take this path. Yes
Else we will be searching for matching translation in above functions flexible way.
No
Go to
Fallback
Is return value Is return value

Is OPC SET
SETTYPE ALREADY ENTRY NOT FOUND / INV DIALED Yes
Yes No found in the CdPA GTA
SEARCHED / MAX SEARCH DIGITS / CDPA SEL NOT FOUND / CGPA
Translation?
COUNT REACHED? SEL NOT FOUND
Go to Yes
Fallback
Did we come
Find OPC Translation across this set type Is Database
No No Yes
(FLOBR way) already during search search count 7
process?
Yes
No
D_OF.doc
Figure 13: Find CgPA GTA GTT translation (FLOBR way)

Find CgPA GTA

input parameter for this function and
Search for
matching CgPA search function in case the previously
GTA translation found translation has multiple
GTTSETs.
Did we find CgPA

Yes No
GTA Translation?
If no B-Tree found
for the number of digits Yes
Store CgPA GTA
in the GTTSET?
Is fallback option
last matched translation) Return
in last matched translation No No GTT_INV_DIALED_DIGITS
set to yes
Increment
Database search Any other error
Yes No
count Yes found? Yes
Return
Any CgPA SELID / Is fallback
Is Database
Yes CdPA SELID / GTTSET No check needed?
search count 7
provisioned?
Return that error
Yes
No Go to No
Yes
Fallback Yes
Do we have a last
Did we come No
Any matched translation?
across this set type
GTTSET found in the Yes No
already during search
CgPA GTA Translation? Return
process?
GTT_ENTRY_NOT_FOUND
No
Route the MSU based on
the routing data in the last Entire GTT
matched translation hierarchy
CgPA SELID found in the CdPA SELID found in the Failed and thus
No No
CgPA GTA Translation? CgPA GTA Translation? MSU
failed
Yes Yes
Find translation using Find translation using Find translation using

CgPA SELID (FLOBR way) CdPA SELID (FLOBR way) that GTTSET (FLOBR way)
D_OF.doc
Figure 14: Find OPC translation (FLOBR way)
Find OPC Translation

(FLOBR way)
matching OPC search function in case the previously
translation found translation has multiple
GTTSETs.
Did we find OPC

Yes No
Translation?
Any other error Entire GTT

Yes
Store OPC translation found? hierarchy
(This is the last matched Failed and thus
translation) Is fallback option Return that error MSU
No No
in last matched translation failed
set to yes
Increment
Database search Is fallback
Yes
count Yes check needed? Return
No
Yes
Any CgPA SELID /
Is Database
Yes CdPA SELID / GTTSET No
search count 7 Yes
provisioned? Do we have a last
No Go to
Yes
Fallback
No
Did we come Return
Any GTT_ENTRY_NOT_FOUND
OPC Translation?
process? Route the MSU based on
the routing data in the last
No matched translation
CgPA SELID found in the CdPA SELID found in the

No No
OPC Translation? OPC Translation?
Yes Yes

D_OF.doc
Figure 15: Find CgPA SSN GTT translation (FLOBR way)
Find CgPA SSN


SSN translation found translation has multiple
GTTSETs.
Did we find CgPA

Yes No
SSN Translation?
Fallback No Is there a database failure?

Yes
Any other error

Yes
Store CgPA SSN found?
translation (This is the Entire GTT
Is fallback option Return that error hierarchy
last matched translation) No
in last matched translation No Failed and thus
set to yes MSU
Increment
failed
Yes
count Yes check needed?
Return
Yes No
Any CgPA SELID /
Is Database
search count 7 Yes
No Go to
Yes
Fallback
No
Did we come Return
CgPA SSN Translation?

No No
CgPA SSN Translation? CgPA SSN Translation?
Yes Yes

D_OF.doc
Figure 16: Find CdPA SSN GTT translation (FLOBR way)

Find CdPA SSN

Search for
matching CdPA search function in case the previously
SSN translation found translation has multiple
GTTSETs.
Did we find CdPA

Yes No
SSN Translation?
Fallback
No Is there a database failure? Yes
Store CdPA SSN

Is fallback option
last matched translation) Any other internal
in last matched translation No Yes Return that error
error found?
set to yes
Increment
Database search No
Yes
count Yes
Return
Is fallback
Any CgPA SELID / No
Is Database check needed?
Yes CdPA SELID / GTTSET (including No
search count 7
Yes
No Go to
Yes
Fallback Yes
Do we have a last
Any Did we come No
Yes No
CdPA SSN Translation (other already during search
than OPC SET)? Return
process?
GTT_ENTRY_NOT_FOUND
No
CgPA SELID found in the CdPA SELID found in the MSU
No No
CdPA SSN Translation? CdPA SSN Translation? failed
No
Yes Yes
Translation?
No
Go to
Fallback
Is return value
Is return value
ENTRY NOT FOUND / Is OPC SET
SETTYPE ALREADY Yes
Yes No INV DIALED DIGITS / found in the CdPA SSN
SEARCHED / MAX SEARCH
CDPA SEL NOT FOUND / Translation?
COUNT REACHED?
CGPA SEL NOT FOUND
Go to Yes
Fallback
Did we come
No No Yes
process?
Yes
No
D_OF.doc
Figure 17: Find CgPA PC translation (FLOBR way)
Find CgPA PC
PC translation found translation has multiple
GTTSETs.
Did we find CgPA

Yes No
PC Translation?
Fallback No Is there a database failure?

Yes
Any other error

Yes
Store CgPA PC found?
Entire GTT
translation (This is the hierarchy
last matched translation) Is fallback option Return that error
in last matched translation No No Failed and thus
set to yes MSU
Increment failed
Yes
count Yes check needed?
Yes No
Return
Any CgPA SELID /
Is Database
search count 7 Yes
No Go to
Yes
Fallback
No
Did we come Return
CgPA PC Translation?

No No
CgPA PC Translation? CgPA PC Translation?
Yes Yes

D_OF.doc
Figure 18: Find Opcode translation (FLOBR way)

Find Opcode Translation
(FLOBR way)

matching Opcode search function in case the previously
translation found translation has multiple
GTTSETs.
Did we find Opcode

Yes No
Translation?
Fallback
No Is there a database failure? Yes
Store Opcode translation

(This is the last matched
translation) Is fallback option
Any other internal
in last matched translation No Yes Return that error
error found?
set to yes
Increment
Database search No
Yes
count Yes
Return
Is fallback
Any CgPA SELID / check needed?
Is Database
Yes CdPA SELID / GTTSET (including No No
search count 7
Yes
No Go to
Yes
Fallback Yes
Do we have a last
Any Did we come No
Yes No
Opcode Translation (other than already during search
OPC SET)? Return
process?
GTT_ENTRY_NOT_FOUND
No
CgPA SELID found in the CdPA SELID found in the MSU
No No
Opcode Translation? Opcode Translation? failed
No
Yes Yes
Translation?
No
Go to
Fallback
Is return value Is return value
SETTYPE ALREADY ENTRY NOT FOUND / Is OPC SET
Yes
Yes No INV DIALED DIGITS / found in the Opcode
SEARCHED / MAX SEARCH
COUNT REACHED? CDPA SEL NOT FOUND / Translation?
CGPA SEL NOT FOUND
Go to Yes
Fallback
Did we come
No No Yes
process?
Yes
No
D_OF.doc
Figure 19: Find translation using CdPA SELID (FLOBR way)
D_OF.doc
Figure 20: Find translation using CgPA SELID (FLOBR way)

Find translation using
CgPA SELID (FLOBR way)
Is CgPA PC
The “fallback check needed” is an Is CgPA GTI = 0? Yes Yes
Present in the MSU?
search function in case the previously Yes ANSI MSU? No
found translation has multiple No
No
GTTSETs.
Is Is
Search GTT Selector table for Yes
DFLTCGPCASET DFLTCGPCISET
CgPA selector : GTI, Domain,
provisioned in SCCPOPTS provisioned in SCCPOPTS
TT, NP, NAI, CgPA SELID,
table? table?
CgPA SSN and Linkset Find CgPA PC
Translation
No
No (FLOBR way)
Increment
Is CgPA
Database search Yes No
Selector Found?
count
Is there a database failure? Yes

Set
Yes max_search_count_reached = TRUE
Is Database Entire GTT
No
search count 7 hierarchy
Set Failed and thus
No settype_already_searched = TRUE Any other internal MSU
Yes
error found? failed
Did we come Yes Do we have a last

across this set type Yes Return that error
Yes
process? Is fallback
Is fallback option check needed?
No
in last matched translation
No
set to yes
No Return
Find translation using that
GTTSET (FLOBR way) Yes
Is
settype_already_searched
Route the MSU based on == TRUE
matched translation No
No
Yes Is
If first translation is not found successfully in max_search_count_reached No
above function, then we take this path. Else we will == TRUE
Yes
be searching for matching translation in above Return
functions flexible way. GTT_CGPA_SEL_NOT_FOUND
Return
GTT_MAX_SEARCH_COUNT_REACHED
Return
GTT_SETTYPE_ALREADY_SEARCHED
Return
GTT_ENTRY_NOT_FOUND
D_OF.doc
4.0 FUNCTIONAL REQUIREMENTS

4.1 FRS Compliance Matrix
The following table lists each of the FRS requirements along with a cross-reference to the FD requirement(s) in this document
that addresses that requirement.
FC — Fully compliant
PC — Partially compliant
NA — Not applicable
NC — Not compliant
Table 18: FRS Compliance Matrix
D_OF.doc
FRS Requirement Compliance FD Requirement Numbers or Applicable FD

[R-114149-1000] FC FD-90
[R-114149-1010] FC FD-92
[R-114149-1020] FC FD-91
[R-114149-1030] FC FD-93
[R-114149-1035] FC FD-1
[R-114149-1040] FC FD-96, FD-30
[R-114149-1050] FC FD-29
[R-114149-1060] FC FD-94
[R-114149-1070] NC Due to significant development effort, this
requirement won’t be implemented as part of this
feature. (See PR 137049 for more info)
[R-114149-1080] FC FD-30, FD-96, FD-97
[R-114149-1090] FC FD-95
[R-114149-1200] FC FD-9, FD-10, FD-11, FD-98, FD-99, FD-117, FD-118
[R-114149-1210] FC FD-101, FD-104
[R-114149-1220] FC FD-102, FD-103
[R-114149-1230] FC FD-105
[R-114149-1240] FC FD-7, FD-119, FD-120
[R-114149-1250] FC FD-103
[R-114149-1260] FC FD-9
[R-114149-1270] FC FD-10
[R-114149-1280] FC FD-9, FD-24
[R-114149-1310] FC FD-19, FD-106
[R-114149-1320] FC FD-6, FD-8, FD-19
[R-114149-1325] FC FD-5, FD-13, FD-14, FD-15, FD-16, FD-17, FD-18,
FD-107, FD-108, FD-114
[R-114149-1330] FC FD-106
[R-114149-1332] FC FD-109, FD-116
[R-114149-1335] FC FD-23, FD-100
[R-114149-1340] FC FD-25
[R-114149-1350] FC FD-25, FD-137
[R-114149-1360] FC FD-110
[R-114149-1365] FC FD-26, FD-111, FD-112, FD-113, FD-115
[R-114149-1370] FC FD-4, FD-171
[R-114149-1380] FC FD-8, FD-27, FD-34
[R-114149-1390] FC FD-106, FD-116
[R-114149-1400] FC FD-13, FD-14, FD-15, FD-16, FD-17
[R-114149-1410] FC FD-25, FD-26
[R-114149-1420] FC FD-21
[R-114149-1430] FC FD-22
D_OF.doc
[R-114149-1440] FC FD-25
[R-114149-1443] FC FD-121, FD-122
[R-114149-1445] FC FD-32
[R-114149-1450] FC FD-57 through FD-89
[R-114149-1460] FC FD-57 through FD-89
[R-114149-1470] FC Erreur ! Source du renvoi introuvable., Erreur !
Source du renvoi introuvable., FD-154
TSM/SCCP is obsolete in Eagle Rel 41.0 through
PR 132578
[R-114149-1480] FC FD-156
[R-114149-1490] FC FD-155
TSM/SCCP is obsolete in Eagle Rel 41.0 through
PR 132578
[R-114149-1500] FC FD-155
[R-114149-1510] FC , FD-159, FD-160
[R-114149-1520] FC FD-170
[R-114149-2000] FC FD-123
[R-114149-2010] FC FD-125
[R-114149-2020] FC FD-124
[R-114149-2030] FC FD-123
[R-114149-2040] FC FD-126
[R-114149-2045] FC FD-1
[R-114149-2050] FC FD-36, FD-37, FD-136
[R-114149-2060] FC FD-127, FD-128, FD-129
[R-114149-2070] FC FD-41, FD-43, FD-138
[R-114149-2080] FC FD-41, FD-139, FD-140
[R-114149-2090] FC FD-42, FD-139, FD-140
[R-114149-2100] FC FD-42, FD-139, FD-140
[R-114149-2110] FC FD-42, FD-139, FD-140
[R-114149-2120] PC FD-42, FD-139, FD-140, FD-141, FD-142
Note : Due to performance reasons, mixing
numbers, none and any are not supported
for ACN.
[R-114149-2130] FC FD-42, FD-139, FD-142, FD-141
[R-114149-2135] FC FD-42, FD-135, FD-137
[R-114149-2140] FC FD-143
[R-114149-2145] FC FD-132, FD-133, FD-134
[R-114149-2150] FC FD-42
[R-114149-2160] FC FD-128, FD-130
[R-114149-2170] FC FD-129
[R-114149-2180] FC FD-130
[R-114149-2185] FC FD-131
[R-114149-2200] FC FD-37
[R-114149-2210] FC FD-133, FD-135, FD-136
[R-114149-2220] FC FD-38, FD-39, FD-136
D_OF.doc
[R-114149-2230] FC FD-57 through FD-89

[R-114149-2240] FC FD-154, FD-155
[R-114149-2250] FC FD-156
[R-114149-2260] FC FD-159
[R-114149-2270] FC FD-154
[R-114149-2280] FC FD-155
[R-114149-2290] FC FD-159, FD-160
[R-114149-2300] FC FD-170, FD-171
[R-114149-3000] NC
[R-114149-3010] NC
[R-114149-3020] NC
[R-114149-3030] NC
[R-114149-3040] NC
[R-114149-3050] NC
[R-114149-3060] NC
[R-114149-3070] NC
[R-114149-3080] NC
[R-114149-3090] NC
[R-114149-3100] NC
[R-114149-3110] NC
[R-114149-3120] NC
[R-114149-3200] NC
[R-114149-3210] NC
[R-114149-3220] NC
[R-114149-3230] NC
[R-114149-3240] NC
[R-114149-3260] NC
[R-114149-3270] NC
[R-114149-3280] NC
[R-114149-3290] NC
[R-114149-3300] NC
[R-114149-3310] NC
[R-114149-3320] NC
[R-114149-3322] NC
[R-114149-3323] NC
[R-114149-3324] NC
[R-114149-3328] NC
[R-114149-3329] NC
[R-114149-3330] NC
[R-114149-3340] NC
[R-114149-3350] NC
[R-114149-3360] NC
D_OF.doc
[R-114149-3370] NC
[R-114149-3380] NC
[R-114149-3390] NC
[R-114149-3400] NC
[R-114149-3410] NC
[R-114149-3420] NC
[R-114149-3430] NC
[R-114149-3440] NC
[R-114149-3450] NC
[R-114149-3460] NC
[R-114149-3470] NC
[R-114149-3480] NC
[R-114149-3490] NC
4.2 General Requirements
Table 19: General Requirements Table
FD Req’t Required Requirement Description Affected

No. or (and any additional comments if necessary) GPLs
Optional
(R or O)
FD-1 R The FLOBR, TOBR and “VGTT with 16 GTT lengths” features shall support EOAM,
FTRA. OAMHC,
IPS, IPSHC
FD-2 R The FLOBR, TOBR features shall not be supported for SEAS, but must EOAM,
maintain backward compatibility with SEAS. OAMHC
FD-3 R The “VGTT with 16 GTT lengths” feature shall be supported through SEAS. EOAM,
i.e., user must be able to provision 16 GTT lengths per TT with SEAS OAMHC
commands.
4.3 Protocol Requirements
Table 20: Protocol Requirements Table for FLOBR

Optional
(R or O)
FD-4 R When FLOBR is NOT turned ON, MSUs shall be processed as per existing VSCCP,
GTT features. i.e. EGTT and OBSR. SCCPHC
D_OF.doc

Optional
(R or O)
FD-5 R Eagle shall support GTT based on the following four additional GTT SCCPHC
hierarchies introduced by FLOBR.
o FLOBR CDPA only
o FLOBR CGPA only
o FLOBR CDPA and FLOBR CGPA
o FLOBR CGPA and FLOBR CDPA
FD-6 R Eagle shall continue to use the link set based GTT hierarchy for performing VSCCP,
GTT on MSUs arriving on link set. SCCPHC
FD-7 R For Eagle-generated MSUs, GTT shall be performed based on existing “CDPA SCCPHC
only” mode.
FD-8 R When OBSR and FLOBR are turned ON and the link set on which the MSU SCCPHC
arrived contain a OBSR specific GTT hierarchy and CdPA GTTSET and/or
CgPA GTTSET contain any set type other than that allowed by OBSR (i.e.
other than CdPA GTA set type for CdPA GTTSET or other than CgPA
GTA/CgPA PC for CgPA GTTSET), then the GTT selection in GTT selector
table shall be considered not found.
However, if the link set contains FLOBR GTT hierarchy, the GTT selection
should be successful regardless of the set type for CdPA GTTSET and/or
CgPA GTTSET.
FD-9 R When FLOBR is turned ON, incoming link set ID shall be used along with SCCPHC
CDPA and CGPA fields to construct the key for searching into the GTT
Selector tables as described in Table 5.
FD-10 R For Eagle-generated MSUs, link set ID shall NOT be used for GTT selector SCCPHC
search. Instead, Eagle shall search for those GTT selector entries which have
been configured with EagleGen=Yes as described in Section 2.3.3
FD-11 R When FLOBR is NOT turned ON, only those GTT selector entries having VSCCP,
“ANY” Linkset Id shall be considered. SCCPHC
FD-12 R FLOBR shall process messages that fall through to GTT from MPS based SCCPHC
features as specified in Section 2.10
FD-13 R When GTT hierarchy is “FLOBR CDPA only”, CDPA fields in the MSU shall SCCPHC
be used for GTT selector search and GTT set shall be taken from CDPA
GTTSET configured in the selector entry.
FD-14 R When GTT hierarchy is “FLOBR CGPA only”, CGPA fields in the MSU will SCCPHC
be used for GTT selector search and GTT set shall be taken from CGPA
GTTSET configured in the selector entry.
FD-15 R When GTT hierarchy is “FLOBR CDPA and FLOBR CGPA”, GTT selectors SCCPHC
shall be searched as defined in FD-13. If no selector match is found or CDPA
GTTSET is not provisioned, GTT selectors shall be searched as defined in FD-
14.
FD-16 R When GTT hierarchy is “FLOBR CGPA and FLOBR CDPA”, GTT selectors SCCPHC
shall be searched as defined in FD-14. If no selector match is found or CGPA
GTTSET is not provisioned, GTT selectors shall be searched as defined in FD-
13.
FD-17 R If GTT selectors are not found as specified in FD-13, FD-14, FD-15 or FD-16, SCCPHC
Eagle shall consider this as translation failure.
D_OF.doc

Optional
(R or O)
FD-18 R If GTT selectors are found as specified in FD-13, FD-14, FD-15 or FD-16, SCCPHC
Eagle shall start performing translation from the GTTSET derived from the
selector entry. Global Title Translation shall be performed as described in
section 3.0
FD-19 R When FLOBR feature is turned ON, flexible routing as described in section SCCPHC
2.3.2 shall be allowed.
FD-20 R When FLOBR feature is turned ON, flexible routing shall be allowed for SCCPHC
default CdPA GTTSET as described in section 2.13.4 ..
FD-21 R FLOBR shall NOT traverse through more than 7 different translation tables for SCCPHC
a single translation. An appropriate action shall be taken as specified in Section
2.3.2.1.4 UIM 1412: GTT(FLOBR) failure: max search depth or
UIM 1414: GTT(FLOBR) warning: max search depth shall be
generated to indicate this condition. (1412 is issued if the MSU is discarded;
1414 is issued if the MSU is routed.)
FD-22 R FLOBR shall not traverse through the same GTT set type more than once on a SCCPHC
single translation. An appropriate action shall be taken as specified in Section
2.3.2.1.3 . UIM 1413: GTT(FLOBR) failure: duplicate set type
or UIM 1415: GTT(FLOBR) warning: duplicate set type shall be
generated to indicate this condition. (1413 is issued if the MSU is discarded;
1415 is issued if the MSU is routed.)
FD-23 R CDPA SelID or CGPA SelID shall be treated as “Don’t Care” for the initial SCCPHC
search in GTT selectors. Subsequent selector searches for the same translation
shall use a valid SelID. (SelID shall be taken from translations)
FD-24 R When FLOBR is turned ON, the searching order for CdPA and CgPA GTT SCCPHC
Selectors shall be as described in section 2.3.5
FD-25 R When performing GTT on a MSU, if a tranlsation points to an OPC GTTSET SCCPHC
along with another SELID or non-OPC GTTSET, the non-OPC GTTSET /
SelID shall be searched first. If no match is found in that set, the OPC
GTTSET shall be searched.
Note: As described in section 2.3.2 , any GTT translation can point to at

most one other GTTSET or SELID. However, CdPA GTA, Opcode and CdPA
SSN translations can additionally point to an OPC GTTSET.
FD-26 R The fallback option as specified in section 2.3.2.1 shall be applicable only SCCPHC
when FLOBR is turned ON and the GTT hierarchy on the link set on which the
MSU arrives is specific to FLOBR.
However, when the GTT hierarchy is specific to OBSR the fallback option
value in the last found translation shall be ignored.
FD-27 R As described in section 2.3.2 , when GTT translations are provisioned in a SCCPHC
FLOBR way and the GTT hierarchy on the link set is set to one of OBSR
hierarchies, then the matching translation shall be found based on the rules
defined by OBSR feature.
That means if any GTTSET provisioned in the translation is not understood by

OBSR, that GTTSET shall be be ignored and assumed to be absent by OBSR.
D_OF.doc

Optional
(R or O)
FD-28 R If one of the following GTTSet types is encountered while performing GTT SCCPHC
and the corresponding information is not present in MSU, FLOBR shall treat
this as “translation not found” in that set.
- CGPA GTA set
- CGPA SSN
- CGPA PC
- CDPA SSN (Available only when TOBR is ON)
FD-29 R FLOBR shall support the following protocol stacks: SCCPHC
• ANSI TCAP / ANSI SCCP-MTP
• ANSI TCAP / ITU SCCP-MTP
• ITU TCAP / ANSI SCCP-MTP
• ITU TCAP / ITU SCCP-MTP
• UDT/UDTS/XUDTS/XUDT/and segmented
XUDTS/XUDT
FD-30 R FLOBR shall co-exist with following GTT features, exactly like CDPA GTT SCCPHC
mode or OBSR does.
• VGTT
• EGTT
• TBGTTLS
• WGTTLS
• AMGTT
• Hex Digit GTT
• SCCP Loop Detection
• ANSI/ITU/CHINA SCCP Conversion
• Flexible GTT Loadsharing
• Intermediate GTT Loadsharing
FD-31 R The result of all global title translation, regardless of which mode, shall SCCPHC
continue to affect only the CdPA or CGPA parameter. In other words, as the
result of any type of Global title translation only SCCP part will be updated,
the TCAP part will not be changed.
FD-32 R If the result of global title translation requires domain crossing, and CgPA is SCCPHC
Rt-on-GT, and ANSI/ITU/SCCP Conversion feature is turned on, then the
CgPA Conversion Set provisioned in the final rule shall be used to convert
CGPA. This set will be search for a GTA match only, and the results will be
used. No subsequent searches will be made into additional set types.
Note: Failure to locate translation information in the CgPA Conversion set will
fall back to Default GTT Conversion information
If the CgPA Conversion Set is not provisioned, then the CgPA conversion data
shall be determined based on a CdPA-only search mode (Note: this is identical
to OBSR).
FD-33 R If the result of global title translation does not require domain crossing and SCCPHC
CgPA is Rt-on-GT, and the AMGTT feature is turned on, and AMGTT data is
requested by either the incoming linkset or the initial GTT, then EAGLE shall
search for CgPA AMGTT using standard CdPA-only hierarchy
(Note: this is identical to OBSR processing)
D_OF.doc

Optional
(R or O)
FD-34 R FLOBR shall mostly use the existing UIMs to describe the conditions of GTT SCCPHC
failure. Few new UIMs have been introduced by FLOBR as specified in
section 2.12.
FD-35 R If GTI = 0 for CgPA in incoming MSU, we continue to use the GTTSET SCCPHC
specified by DFLTCGPCISN / DFLTCGPCASN parameters in SCCPOPTS
for finding the matching translation.
NOTE : OBSR works same way and this doesn’t change with FLOBR.
Table 21: Protocol Requirements Table for TOBR

Optional
(R or O)
FD-36 R Eagle shall support routing the MSUs based on their TCAP information when SCCPHC
any TOBR Opcode Quantity feature is turned ON.
FD-37 R Eagle shall support routing the MSUs based on SCCP CdPA SSN when TOBR SCCPHC
is turned ON.
FD-38 R The searching order for CdPA SSN translations shall be as defined in section SCCPHC
2.4.5.1
FD-39 R The flexible routing shall be supported for CdPA SSN translation as described SCCPHC
in section 2.3.2
FD-40 R TOBR shall support CdPA SSN, Message/Package Type, ACN/Family, and SCCPHC
OpCode for the following protocol stacks:
• ANSI TCAP / ANSI SCCP-MTP
• ANSI TCAP / ITU SCCP-MTP
• ITU TCAP / ANSI SCCP-MTP
• ITU TCAP / ITU SCCP-MTP
FD-41 R TOBR shall use the following information from the TCAP message for SCCPHC
performing GTT:
- 1 byte Message/Package Type
- 1 byte Opcode
- up to 7 bytes of ACN (Only for ITU TCAP messages)
- 1 byte Operation Family (Only for ANSI TCAP messages)
FD-42 R The searching order for opcode translations shall be as described in sections SCCPHC
2.4.5.2.2 and 2.4.5.2.3.1.
FD-43 R TOBR shall support ITU and ANSI TCAP messages as specified in section SCCPHC
2.4.2 .
FD-44 R TOBR shall support Message/Package Type, ACN/Family, and OpCode for SCCPHC
routing UDT(S) and unsegmented XUDT(S) messages.
D_OF.doc

Optional
(R or O)
FD-45 R If any of the Opcode Quantity features is turned ON and the GTT hierarchy SCCPHC
being used is FLOBR specific, Eagle shall decode the TCAP portion of all
TCAP messages coming to Eagle for GTT as described in Section 2.4.2 .
Note: Only UDT(S) and non-segmented XUDT(S) messages shall be decoded.
FD-46 R For segmented XUDT / XUDTS, TOBR shall consider the message to have no SCCPHC
Message/Package type, no ACN/Family , and no Opcode. i.e TCAP data shall
not be used for such messages. CDPA SSN shall however be used for
performing GTT on these messages.
Note: Otherwise, the first message of a segmented sequence may have

different routing rules applied, since it would be the only message with
decodable TCAP information
FD-47 R For non-TCAP messages (Messages of type other than those supported), SCCPHC
TCAP translation data shall NOT be used for performing GTT. If a
provisioned opcode translation set is encountered while performing GTT, it
shall be treated as “translation not found” in that set.
Note: Such messages can still be routed based on last matched translation
depending on its fallback option.
FD-48 R If TOBR is not able to determine Opcode, ACN or Family due to decoding SCCPHC
errors or otherwise, these shall be assumed to have a value of “None” for
performing GTT.
FD-49 R TOBR shall use only the first component in the TCAP message to find Opcode SCCPHC
and Operation Family.
FD-50 R In case of Dialogue portion decoding failure, TOBR shall still decode the SCCPHC
component portion of ITU TCAP messages provided it is able to determine the
starting point of the component portion.
Note: Determination of starting point depends on whether the dialogue portion
length was encoded as definite / indefinite and if indefinite, the type of error
encountered during dialogue portion decoding. Refer Section 2.4.2.2 for
more details.
FD-51 R TOBR shall support only upto 9 levels of indefinite lengths while skipping SCCPHC
Dialogue portion to find the start of component portion as mentioned in FD-50.
Note: This holds true only if Dialogue portion length is indefinite. If it is

definite, this length will be used to skip the Dialogue portion.
FD-52 R TOBR shall trap and display the TCAP decoding results and the TCAP SCCPHC
information used for performing GTT if any trace criterion (provisioned using
ent-trace command with detail or debug mode) is met for the corresponding
MSU.
FD-53 R TOBR shall trap all TCAP messages that are decoded if a trace condition on SCCPHC
Service=TOBR is set using ent-trace command. TCAP decoding information
shall be displayed if a “TOBR” service trace condition is active with mode as
Detail or Debug. This would be irrespective of whether that TCAP information
was used while performing GTT or not.
D_OF.doc
Table 22: Protocol Requirements Table for VGTT with 16 GTT lengths

Optional
(R or O)
FD-54 R When VGTT feature only is turned ON, Eagle shall continue to support 10 EOAM,
GTT lengths for CdPA GTA and CgPA GTA GTTSETs. OAMHC,
VSCCP,
SCCPHC
FD-55 R When “VGTT with 16 GTT lengths” feature is turned ON, Eagle shall support EOAM,
16 GTT lengths for CdPA GTA and CgPA GTA GTTSETs. OAMHC,
SCCPHC
FD-56 R When “VGTT with 16 GTT lengths” feature is turned ON, Eagle shall OAMHC,
continue to find a best matching translation in a CdPA/CgPA GTA GTTSET. SCCPHC
4.4 FLOBR Test Tool / Test Mode Requirements
Table 23: Test Tool / Test Mode Requirements for FLOBR/TOBR

Optional
(R or O)
FD-57 R TST-MSG shall be enhanced to allow FEAT= GTT and PROT=SCCP to be EOAM,
specified. OAMHC
FD-58 R TST-MSG with FEAT=GTT and PROT=SCCP shall only be allowed if EOAM,
FLOBR feature is on. OAMHC
FD-59 R CHG-SCCP-MSG shall be created to allow modification of all parameters EOAM,
listed in 2.13.1 . CHG-SCCP-MSG shall have access to all 10 FLOBR test OAMHC
messages.
FD-60 R In addition to numerical input, CHG-SCCP-MSG shall support the following EOAM,
mnemonics for CDPANP and CGPANP: OAMHC
e164 = 1
generic = 2
x121 = 3
f69 = 4
e210 = 5
e212 = 6
e214= 7
private=8,
Note: These match the values for existing gttsel commands
D_OF.doc

Optional
(R or O)
FD-61 R In addition to numberical input, CHG-SCCP-MSG shall support the following EOAM,
mnemonics for CDPANAI and CGPANNAI OAMHC
sub =1
rsvd = 2
natl = 3
intl = 4
Note: These match the values for existing gttsel commands
FD-62 R In addition to numerical input, CHG-SCCP-MSG shall also support the EOAM,
mnemonics for Package/Message Type as are supported by ent-gta command OAMHC
for PKGTYPE parameter..
FD-63 R RTRV-SCCP-MSG shall be created to allow retrieval of the TST-MSG EOAM,
information for FLOBR. It shall allow for a single entry to be displayed, or for OAMHC
all 10 messages to be displayed.
FD-64 R Each translation shall have a TESTMODE field. Values shall be ‘On’ or ‘Off’. EOAM,
‘Off’ shall be the default. OAMHC,
SCCPHC
FD-65 R TESTMODE=ON shall only be allowed on ENT-GTA and CHG-GTA EOAM,
commands if the FLOBR feature is on OAMHC
FD-66 R While provisioning TESTMODE=ON data, ENT-GTA and CHG-GTA EOAM,
commands shall display a warning, saying that the processing of traffic shall OAMHC,
be affected. SCCPHC
FD-67 R If FLOBR is on, RTRV-GTA shall be enhanced to display TESTMODE status EOAM,
OAMHC
FD-68 R When performing GTT on an MSU, and a translation with TESTMODE = SCCPHC
OFF is encountered, then standard GTT behavior shall occur.
FD-69 R When performing GTT on an MSU, and a translation with TESTMODE=ON SCCPHC
is encountered, then GTT shall ignore that rule. GTT shall continue as if that
rule was not present.
Note: This means that for MSU routing, changing an entry from
TESTMODE=OFF to TESTMODE=ON is equivalent to deleting the rule
FD-70 R 10 sets of FLOBR data shall be stored to support for message testing EOAM,
OAMHC
FD-71 R Upon receipt of user test data from TST-MSG command, Service Module shall SCCPHC
perform global title translation on the user data as if the data has been decoded
from an actual MSU.
Note: No MSU is actually routed. This is for simulation purposes only.
FD-72 R When processing TST-MSG data, and EAGLEGen is set to Yes, then EOAM,
• incoming linkset name shall be ignored OAMHC,
SCCPHC
• Search hierarchy will be CdPA only (standard GTT)
FD-73 R When processing the TST-MSG command and EAGLEGen is set to NO, EOAM,
EOAM shall convert the incoming linkset name into a linkset id to pass to the OAMHC
Service Module. If the incoming linkset name does not match and provisioned
linkset, then an error indication shall be given to the user and processing shall
stop
D_OF.doc

Optional
(R or O)
FD-74 R When processing TST-MSG data, if the OPC, CdPA PC and CgPA PC are not EOAM,
of the same network type, then TST-MSG output shall indicate that PC types OAMHC
are inconsistent and processing shall stop
FD-75 R When processing TST-MSG data, if the OPC is ANSI and CdPA GTI is not 2, EOAM,
then TST-MSG output shall indicate that CdPA GTI is invalid and processing OAMHC
shall stop
FD-76 R When processing TST-MSG data, if ACTIVE is set to NO, then TST-MSG EOAM,
output shall indicate that the data is inactive, and processing shall stop OAMHC
FD-77 R When processing TST-MSG data and EAGLEGen is set to NO, the Service SCCPHC
Module shall use the incoming linkset ID to determine the search hierarchy.
FD-78 R When processing TST-MSG data and EAGLEGen is set to NO, then the SCCPHC
following hierarchies are supported on the Service Module:
• CdPA
• OBSR: Advanced CdPA, CdPA
• OBSR: CgPA, Advanced CdPA, CdPA
• OBSR: Advanced CdPA, CgPA, CdPA
• OBSR: Advanced CdPA, CdPA, CgPA
• OBSR: CgPA, CdPA
• OBSR: CdPA, CgPA
• OBSR: CgPA
• FLOBR CdPA
• FLOBR CdPA CgPA
• FLOBR CgPA
• FLOBR CgPA CdPA
FD-79 R When processing TST-MSG data, the Service Module shall treat rules with SCCPHC
TESTMODE=ON as actual GTT rules, and continue processing based on that
data
Note: This means that TST-MSG makes no differentiation between rules with
TESTMODE=ON and TESTMODE=OFF. They are treated identically.
FD-80 R When processing TST-MSG data with CDPA or CGPA GTI = 2, the Service SCCPHC
Module will ignore the NP and NAI fields
FD-81 R When processing TST-MSG data with CGPA GTI = 0, the Service Module SCCPHC
will ignore the TT, GTA, NP and NAI fields
FD-82 Engineering When processing TST-MSG data, the Service Module shall perform the SCCPHC
Requirement processing at the same priority level as an MSU (to prevent reentrancy
problems)
FD-83 R After processing, TST-MSG shall generate a output report on the terminal that EOAM,
issued the command OAMHC,
SCCPHC
D_OF.doc

Optional
(R or O)
FD-84 R TST-MSG output shall include the following fields from the test MSU: EOAM,
• OPC OAMHC,
• EAGLE Generated status SCCPHC
• Incoming Linkset name (not required if EAGLE Generated Status=Yes)
• CdPA: GTI, TT, NP, NAI, SSN, PC, GTA
• CgPA: GTI, TT, NP, NAI, SSN, PC, GTA
Note: When displaying NP and NAI, output shall provide support for the
mnemonics indicated in FD-60 and FD-61
FD-85 R When processing TST-MSG data with CDPA or CGPA GTI = 2, the TST- EOAM,
MSG output will not include the NP or NAI field OAMHC,
SCCPHC
FD-86 R When processing TST-MSG data with CGPA GTI = 0, the TST-MSG output EOAM,
will not include the TT, GTA, NP or NAI field OAMHC,
SCCPHC
FD-87 R If TOBR feature is on, then the TST-MSG output display shall include: EOAM,
• TCAP Package/Message Type OAMHC,
• Opcode SCCPHC
• Family/ACN (based on Package/Message Type)
Note: Package/Message Type will also display mnemonic from FD-62
FD-88 R If TOBR is on, then during processing of TST-MSG TCAP data: SCCPHC
If Package Message Type is 0xE1, 0xE2, 0xE3, 0xE4, 0xE5, 0xE6, or 0xF6,
then Family shall be used for processing and ACN shall be ignored
If Package/Message Type is 0x62, 0x65, 0x64, 0x67 or 0x61, then ACN shall
be used for processing and Family shall be ignored.
For all other Package/Message Types, ACN/Family/OpCode shall all be
considered ‘none’.
FD-89 R Results display from the TST-MSG shall include: EOAM,
• Number of GTT searches performed OAMHC,
• If a loop was detected (GTT Set Type is duplicated) SCCPHC
• Any GTT Set Name and Set Type used during the search
• Indication of where the test mode was encountered
• Indication of final GTT results (Translation Successful or not. If
Successful output should include Set Name used for routing and DPC,
SSN (if appropriate), RI)
(Note: Final GTT results are before any loadsharing algorithms are applied by
MRN or MAP)
D_OF.doc
4.5 User Interface Requirements
4.5.1 FLOBR User Interface Requirements
Table 24: User Interface Requirements Table for FLOBR

Optional
(R or O)
FD-90 R A new FAK (part number: 893-0277-01) is required for the FLOBR feature. EOAM,
This FAK will be an ON only FAK. The default will be disabled and OFF. OAMHC
FD-91 Engineering Once FLOBR feature is enabled, the FAK can’t be disabled. EOAM,
Requirement OAMHC
FD-92 R A temporary FAK is not supported for FLOBR feature. EOAM,
OAMHC
FD-93 R Once the FLOBR feature is enabled and turned ON, it can’t be turned OFF. EOAM,
OAMHC
FD-94 R Prior to FLOBR feature development, GTI=2 ANSI GTT selectors and EOAM,
GTII/GTIN/GTIN24=2 and GTII/GTIN/GTIN24=4 ITU GTT selectors are OAMHC
supported.
With FLOBR development, we continue to support the same selectors.

FD-95 R The FLOBR feature can’t be enabled unless EGTT feature is turned ON. EOAM,
OAMHC
FD-96 R All FLOBR translations must support AMGTT, SCCP Loop Detection, EOAM,
ANSI/ITU/CHINA SCCP Conversion and Flexible GTT Load sharing OAMHC
(intermediate and final) functionalities.
FD-97 R Apart from AMGTT, SCCP Loop Detection, ANSI/ITU/CHINA SCCP EOAM,
Conversion and Flexible GTT Load sharing (intermediate and final) features, OAMHC
the CdPA GTA and CgPA GTA FLOBR translations also support VGTT and
Hex Digit GTT features.
FD-98 R With FLOBR feature, the incoming link set shall also be added to the GTT EOAM,
Selector key (for both CdPA and CgPA GTT Selectors) as described in section OAMHC
2.3.4
FD-99 R When a link set is referred in the GTT selector table, that link set can’t be EOAM,
deleted in the link set table. OAMHC
FD-100 R With FLOBR feature, the SELID parameter shall be added to the CdPA GTT EOAM,
Selector key as described in section 2.3.4 OAMHC
NOTE: With OBSR, SELID was allowed only for CgPA GTT Selector
key.
FD-101 R When FLOBR is NOT turned ON, user is not allowed to specify the incoming EOAM,
link set parameter in GTTSEL commands. OAMHC
FD-102 R The incoming link set shall be an optional (even if FLOBR feature is turned EOAM,
ON) parameter in GTTSEL commands. OAMHC
FD-103 R Since the link set parameter is optional in GTT selector commands, if user EOAM,
don’t specify while provisioning, a value of “ANY” shall be assumed in the OAMHC
database.
D_OF.doc

Optional
(R or O)
FD-104 R The linkset domain must match the domain of the GTT selector. That means EOAM,
for ANSI selectors only linkset with ANSI adjacent point code must be OAMHC
specified. For ITU selectors only linkset with ITU adjacent point code must be
specified.
FD-105 R User shall be able to provision 100,000 GTT Selectors (CdPA and CgPA GTT EOAM,
selectors) as described in section 2.11. (also see section 2.13.5 ) OAMHC
NOTE: Each combination of GTI, Domain, TT, (NP and NAI if GTI=4),
CgPA SSN, Selid and incoming link set shall constitute an entry.
It is possible that a single GTT selector entry can have both
CdPA and CgPA GTTSETs. This will be treated as single entry
in the database. It is also possible that a GTT selector entry
can contain either CdPA GTTSET or CgPA GTTSET only. This
also will be treated as single entry in the database.
FD-106 R When FLOBR feature is turned ON and based on available GTT set types (as EOAM,
described in Table 3) user must be able to provision any available GTT set OAMHC
type for CdPA GTTSET and/or CgPA GTTSET in GTT Selector Table. (as
described in section 2.3.1 )
FD-107 R The new FLOBR GTT hierarchies, as specified in section 2.3, shall be EOAM,
supported for link set commands (ENT/CHG/RTRV-LS) when FLOBR feature OAMHC
is turned ON.
FD-108 R The default GTT hierarchy for a link set is “CdPA only”
FD-109 R All the GTT selector entries shall contain at least one of CdPA or CgPA EOAM,
GTTSET. Based on the GTT selector key combination (as described in Table OAMHC
5), it is possible that a GTT selector entry can have both CdPA and CgPA
GTTSETs. This especially true when user doesn’t specify CgPA SSN
parameters in GTT selector commands.
FD-110 R While provisioning, a GTT translation is not allowed to point to the GTTSET EOAM,
of same set type. OAMHC
FD-111 R When FLOBR is turned ON, a new provision able fallback option shall be EOAM,
supported for all translations as described in section 2.3.2.1 OAMHC
FD-112 R The fallback option specified in FD-111 shall take “Yes” or “No” or “System EOAM,
Default” values in the database. The default value is “System Default”. OAMHC
FD-113 R A new system wide default fallback option shall be supported through EOAM,
CHG/RTRV-SCCPOPTS commands when FLOBR feature is turned ON. OAMHC
FD-114 R The new FLOBR GTT hierarchies, as specified in section 2.3, shall be EOAM,
supported for DFLTGTTMODE parameter in CHG/RTRV-SCCPOPTS OAMHC
commands when FLOBR feature is turned ON.
FD-115 R The initial value for the system wide default fallback option shall be “No”. EOAM,
OAMHC
FD-116 R With CHG-GTTSEL command user must be able to change only the CdPA EOAM,
and/or CgPA GTTSET(s) data in the GTT selector entry. If a GTT selector OAMHC
entry is having both CdPA and CgPA GTTSETs, user can make any one of the
GTTSET to contain “none” (No GTTSET is provisioned). However, at any
point of time any provisioned GTT selector must have at least one valid
GTTSET.
D_OF.doc

Optional
(R or O)
FD-117 R The RTRV-GTTSEL command must be cancelable. EOAM,
OAMHC
FD-118 R Apart from existing functionality, user must be able to retrieve the GTT EOAM,
selector entries based on link set parameter. OAMHC
FD-119 R As described in section 2.3.3 , ENT/CHG/DLT/RTRV-GTTSEL commands EOAM,
shall provide support for Eagle-generated MSUs. OAMHC
FD-120 R User must be able to retrieve specified/all Eagle-generated entries in the EOAM,
database. OAMHC
FD-121 R When FLOBR and ANSI/ITU/CHINA SCCP Conversion features are turned EOAM,
ON, each translation shall support a “CgPA Conversion GTTSET”. OAMHC
FD-122 R The “CgPA Conversion GTTSET” shall accept CdPA GTA and CgPA GTA EOAM,
GTTSETs. (NOTE : OBSR must be enabled to support CgPA GTA GTTSET) OAMHC
4.5.2 TOBR User Interface Requirements
Table 25: User Interface Requirements Table for TOBR

Optional
(R or O)
FD-123 R A new FAK (part number: 893-0278-01) is required for the TOBR feature. EOAM,
This FAK will be an ON only FAK. The default will be disabled and OFF. OAMHC
FD-124 Engineering Once TOBR feature is enabled, the FAK can’t be disabled. EOAM,
Requirement OAMHC
FD-125 R A temporary FAK is not supported for TOBR feature. EOAM,
OAMHC
FD-126 R The TOBR feature can’t be enabled unless FLOBR feature is turned ON. EOAM,
OAMHC
FD-127 R TOBR feature shall support the opcode translation quantities as described in EOAM,
section 2.4.4 OAMHC
FD-128 R User must be able to provision the opcode translations through EOAM,
ENT/CHG/DLT/RTRV-GTA Commands only when one of the quantity keys OAMHC
is turned ON.
FD-129 R The TOBR quantity FAK can be turned ON only when TOBR feature is turned
ON.
FD-130 R The quantity associated with the quantity FAK shall decide the number of EOAM,
opcode translations allowed in the system as described in section 2.4.4 OAMHC
FD-131 R As per existing quantity feature key rules, user must be able to turn ON any EOAM,
quantity key (in ascending order only) as long as one of the lower quantity OAMHC
FAK is turned ON. (i.e., the quantity increment needn’t be sequential)
FD-132 R The ENT/DLT/RTRV-GTTSET commands shall support provisioning of EOAM,
opcode and CdPA SSN GTT sets, as described in section 2.4.3 , with OAMHC
“Opcode” and “CdSSN” set types when TOBR feature is turned ON.
FD-133 R User shall be able to provision CdPA SSN translations with routing data and EOAM,
D_OF.doc
flexible routing data as shown in Table 4. OAMHC

FD-134 R User can provision different length ACNs in the same opcode set. EOAM,
OAMHC
FD-135 R User must be able to provision opcode and CdPA SSN GTT sets for any EOAM,
selector (CdPA or CgPA) when TOBR feature is turned ON. OAMHC
FD-136 R User must be able to provision CdPA SSN translations through EOAM,
ENT/CHG/DLT/RTRV-GTA commands only when TOBR feature is turned OAMHC
ON.
FD-137 R The opcode and CdPA SSN translations shall support AMGTT, SCCP loop EOAM,
detection, Intermediate GTT load sharing and Flexible GTT load sharing and OAMHC
flexible routing (as shown in Table 4), apart from routing data.
FD-138 R The opcode translations shall support ANSI and ITU opcodes. EOAM,
OAMHC
FD-139 R The key for ANSI opcode translation and parameter values shall be as EOAM,
described in section 2.4.5.2.1 OAMHC
FD-140 R The key for ITU opcode translation and parameter values shall be as described EOAM,
in section 2.4.5.2.3 OAMHC
FD-141 R For any opcode translation entry, the ANSI or ITU key parameters or EOAM,
parameter values are mutually exclusive. OAMHC
FD-142 R For ITU opcode translations, due to performance reasons, mixing the numbers, EOAM,
“None” and “Any” for an ACN are not allowed. Only ACN=all numbers, or OAMHC
ACN=any or ACN=none allowed.
FD-143 R The opcode and CdPA SSN translations shall share the existing translation EOAM,
table with 1 million entries. (the quantity of translation table is supported OAMHC
through "XGTT Table Expansion" feature)
FD-144 R ENT-TRACE command shall support “TOBR” as a value for service EOAM,
parameter when TOBR feature is turned ON. OAMHC
4.5.3 VGTT with 16 GTT lengths User Interface Requirements
Table 26: User Interface Requirements Table for VGTT with 16 GTT lengths

Optional
(R or O)
FD-145 R A new FAK (part number: 893-0248-01) is required for the “VGTT with 16 EOAM,
GTT lengths” feature. This FAK will be an ON only FAK. The default will be OAMHC
disabled and OFF.
FD-146 Engineering Once the “VGTT with 16 GTT lengths” feature is enabled, the FAK can’t be EOAM,
Requirement disabled. OAMHC
FD-147 R A temporary FAK is not supported for the “VGTT with 16 GTT lengths” EOAM,
feature. OAMHC
FD-148 R Once the the “VGTT with 16 GTT lengths” feature is enabled and turned ON, EOAM,
it can’t be turned OFF. OAMHC
FD-149 R The “VGTT with 16 GTT lengths” feature can’t be enabled unless VGTT EOAM,
feature is turned ON. OAMHC
FD-150 R User must be able to provision 16 GTT lengths per TT/GTTSET only when EOAM,
D_OF.doc
“VGTT with 16 GTT lengths” feature is turned ON. OAMHC
4.5.4 Affected Commands
Table 27: Affected Command Specifications
Commands Changes
CHG/RTRV-CTRL-FEAT Feature Control support for new features.
ENT/CHG/DLT/RTRV-GTTSEL Updated to support TOBR and FLOBR functionalities.
ENT/CHG/DLT/RTRV-GTTSET Updated to support TOBR and VGTT with 16 GTT lengths functionalities.
ENT/CHG/DLT/RTRV-GTA Updated to support FLOBR and TOBR functionalities and testing tool.
ENT/CHG/DLT/RTRV-TT Adopted for GTT design change.
ENT/CHG/DLT/RTRV-GTT Adopted for GTT design change.
ENT-CARD DSM/E5-SM4G card verification.
ENT/CHG/DLT/RTRV-LS Provision new hierarchies and prevent deletion of a link set when the link set is used
in the GTT Selector table.
CHG/RTRV-SCCPOPTS Updated to support new GTT hierarchies. A global default fallback option shall be
added.
RTRV-TBL-CAPACITY New tables shall be added to the response.
TST-MSG Updated for the tool.
CHG-SCCP-MSG This is a new command for the tool.
RTRV-SCCP-MSG This is a new command for the tool.
ENT-TRACE Updated to support “TOBR” as a new service.
4.6 Hardware Requirements
4.6.1 VGTT with 16 GTT lengths Hardware Requirements
Table 28: Hardware Requirements Table for VGTT with 16 GTT lengths

Optional
(R or O)
FD-151 R The “VGTT with 16 GTT lengths” feature can’t be enabled when EOAM,
DSM/VSCCP card is in IS-NR/IS-ANR state on Eagle. OAMHC
FD-152 R The DSM/VSCCP card shall be auto inhibited when plugged in after enabling EOAM,
the “VGTT with 16 GTT lengths” feature. OAMHC
FD-153 R The “VGTT with 16 GTT lengths” feature requires E5-SM4G or better card. EOAM,
OAMHC
D_OF.doc
4.6.2 FLOBR Hardware Requirements
Table 29: Hardware Requirements Table for FLOBR

Optional
(R or O)
FD-154 R The FLOBR feature can’t be enabled when DSM/VSCCP card is in IS-NR/IS- EOAM,
ANR state on Eagle. OAMHC
FD-155 R The DSM/VSCCP card shall be auto inhibited when plugged in after enabling EOAM,
the FLOBR feature. OAMHC
FD-156 R The FLOBR feature can be enabled when DSM/VSCCP card type is EOAM,
provisioned in the database. When user plugs-in E5-SM4G card, the E5- OAMHC
SM4G card must be able to load successfully.
4.6.3 TOBR Hardware Requirements
Since TOBR feature is dependent on FLOBR, no specific hardware requirements are added for TOBR.
4.7 Performance Requirements
4.7.1 VGTT with 16 GTT lengths Performance Requirements
Table 30: Performance Requirements Table for VGTT with 16 GTT lengths

Optional
(R or O)
FD-157 R E5-SM4G shall continue to support the following rates with VGTT with 16
GTT lengths:
Without E5-SM4G throughput increase feature: SCCPHC
850 TPS with one or more of EPAP DB feature(s) and “VGTT with
16 GTT lengths” feature turned ON
1700 TPS with “VGTT with 16 GTT lengths” feature turned ON
without EPAP DB features and with ELAP features.
With E5-SM4G throughput increase feature:

3125 TPS with one or more of EPAP DB feature(s) and “VGTT with
16 GTT lengths” feature turned ON
5000 TPS with “VGTT with 16 GTT lengths” feature turned ON
without EPAP DB features and with ELAP features.
FD-158 R Without VGTT with 16 GTT lengths feature, DSM/VSCCP card shall continue
to support the following rates:
1700 TPS without EPAP DB features and with ELAP features. VSCCP
850 TPS with OBSR and/or one or more of EPAP DB feature(s)
D_OF.doc
4.7.2 FLOBR and TOBR Performance Requirements
Table 31: Performance Requirements Table for FLOBR and TOBR

Optional
(R or O)
FD-159 R E5-SM4G shall continue to support the following rates with FLOBR/TOBR
feature:
Without E5-SM4G throughput increase feature: SCCPHC
850 TPS with FLOBR and/or TOBR feature(s) and with one or more
of EPAP DB feature(s)
1700 TPS with FLOBR and/or TOBR feature(s) without EPAP DB
Feature(s) and with ELAP features.
With E5-SM4G throughput increase feature:

3125 TPS with FLOBR and/or TOBR feature(s) and with one or more
of EPAP DB feature(s)
5000 TPS with FLOBR and/or TOBR feature(s) without EPAP DB
Feature(s) and with ELAP features.
FD-160 R Without FLOBR feature, DSM/VSCCP card shall continue to support the
following rates:
1700 TPS without EPAP DB features and with ELAP features. VSCCP
850 TPS with OBSR and/or one or more of EPAP DB feature(s)
4.8 Measurement Requirements
Table 32: Measurement Requirements Table for FLOBR and TOBR

Optional
(R or O)
FD-161 R A single request for a measurements report with TYPE=SYSTOT and EOAM,
ENTTYPE=TT shall cause either one or two actual reports to be generated on OAMHC,
both the OAM and the MCP. MCP,
SCCPHC
FD-162 R The first report shall always be generated and shall be a modified version of EOAM,
the existing SYSTOT-TT report. The second, optional, report shall be existing OAMHC,
SYSTOT-CGTT report. MCP,
SCCPHC
Note : SYSTOT-CGTT report shall be generated only if OBSR feature is
Enabled and ON or FLOBR Feature is ON
D_OF.doc
FD-163 R A register FCGGTTPRFD indicating the total number of MSUs that EOAM,
successfully completed Flexible CgPA GTT (per TT) shall be added to the OAMHC,
existing SYSTOT-CGTT report on both the OAM and the MCP (see MCP,
TR005822 for the details of report formatting).
SCCPHC
FD-164 R A register FCDGTTPRFD indicating the total number of MSUs that EOAM,
successfully completed Flexible CdPA Global Title Translation (per TT) shall OAMHC,
be added to the existing SYSTOT-TT report on both the OAM and the MCP MCP,
(see TR005822 for the details of report formatting).
SCCPHC
FD-165 R For TOBR/FLOBR feature existing registers shall be pegged for SYSTOT- EOAM,
CGTT report on both the OAM and the MCP (see TR005822 for the details of OAMHC,
report formatting): MCP,
Note : SYSTOT-CGTT report shall be generated only if OBSR feature is SCCPHC
Enabled and ON or FLOBR feature is ON
FD-166 R For TOBR/FLOBR feature existing registers shall be pegged for SYSTOT- EOAM,
STP report on both the OAM and the MCP (see TR005822 for the details of OAMHC,
report formatting): MCP,
SCCPHC
FD-167 R Existing register GTTUN1NT in SYSTOT-TT report shall be modified to EOAM,
indicate OAMHC,
“CdPA GTTs Unable to Perform – Diagnostic 1: MCP,
FLOBR CdPA mode used, and translation failed for any of the
SCCPHC
following reasons:
o maximum search depth is reached
o duplicate GTTSET type is encountered
o translation not found (any GTTSET type)
o CdPA SSN required, but not present in the MSU
o CgPA SSN required, but not present in the MSU
o CgPA PC required, but not present in the MSU
o Default CgPA PC Set is required, but not provisioned (ANSI
or ITU)
Note: This register is also used by OBSR. Use by OBSR is unchanged.
FD-168 Existing register CGGTTUN1NT in SYSTOT-CGTT report shall be modified EOAM,

to indicate OAMHC,
“CgPA GTTs Unable to Perform – Diagnostic 1: MCP,
FLOBR CgPA mode used, and translation failed for any of the
SCCPHC
reasons listed in FD-167
Note: This register is also used by OBSR. Use by OBSR is unchanged.
4.9 Upgrade Considerations
Table 33: Upgrade Requirements Table
FD Req’t Required or Requirement Description Affected

No. Optional (R GPLs
D_OF.doc
or O) (and any additional comments if necessary)

FD-169 Engineering After upgrade verify that only 100,000 B-Trees are supported in OAM, EOAM,
Requirement SCCP, VSCCP and SCCPHC GPLs. OAMHC,
SCCP,
VSCCP,
SCCPHC
FD-170 R After upgrade, Eagle should continue to process the GTT traffic (GTT, EOAM,
EGTT, OBSR, VGTT, AMGTT etc.,) successfully with the same OAMHC,
performance numbers. SCCP,
VSCCP,
SCCPHC
FD-171 R After upgrade, Eagle should continue to process the GTT traffic (GTT, SCCP,
EGTT, OBSR, VGTT, AMGTT etc.,) successfully with the same algorithms VSCCP,
as in the source release. (For example fixed traversal algorithms that were SCCPHC
following in OBSR etc.,)
5.0 PERFORMANCE
Existing performance figures shall be maintained for this feature. Hence the performance of Eagle is not impacted with the
introduction of these features.
6.0 RELIABILITY
The reliability of EAGLE® 5 ISS is not impacted with the introduction of these enhancements.
7.0 SERVICEABILITY
The way the commands were working prior to FLOBR shall change in FLOBR release.
GTT Selector Commands

For example:
ENT-GTTSEL:GTI=<GTI>:TT=<TT>:CDGTASN=<CDPA GTTSN>:CGSSN=<CGSSN>:SELID=<SELID>:CGGTASN=<CGPA GTTSN>
Due to the reason that CGSSN is specific to CGPA GTT selector, the above command must be split into the following
commands.
ENT-GTTSEL:GTI=<GTI>:TT=<TT>:CDGTASN=<CDPA GTTSN>:
ENT-GTTSEL:GTI=<GTI>:TT=<TT>:CGSSN=<CGSSN>:SELID=<SELID>:CGGTASN=<CGPA GTTSN>
However, the following command should work before and after Rel 41.0 as long as only OBSR feature is turned ON..
ENT-GTTSEL:GTI=<GTI>:TT=<TT>:CDGTASN=<CDPA GTTSN>:CGGTASN=<CGPA GTTSN>
Same logic applies to CHG-GTTSEL command also.
D_OF.doc
In Rel 41.0, when only OBSR feature is enabled and FLOBR is not turned ON, the parameters CDGTASN, CGPCSN
and CDGTASN are still valid in GTTSEL commands. However, once FLOBR feature is turned ON, CDGTASN,
CGPCSN and CDGTASN are not valid, instead use CDGTTSN and CGGTTSN. That means when FLOBR is turned
ON,
CDGTASN shall be replaced by CDGTTSN and
CGGTASN and CGPCSN shall be replaced by CGGTTSN.
GTA Commands
In OBSR, we introduced the CGGTASN, CGSSNSN and CGPCSN parameters in ENT/CHG-GTA commands. With
FLOBR, we are also going to support CDGTASN, CDSSNSN and OPCODESN. Keeping the 40 parameters per
command limit in mind, we used OPTSN (optional set name) parameter to support all above parameters. The OPCSN
shall remain same.
Hence if customer was using any of those parameters, they need to replace with OPTSN name.
For example:
ENT-GTA:GTTSN=<CDPA GTA GTTSET>:GTA=<GTA>:EGTA=<EGTA>:……..……:CGGTASN=<CGGTASN>:OPCSN=<OPCSN>
ENT-GTA:GTTSN=<CDPA GTA GTTSET>:GTA=<GTA>:EGTA=<EGTA>:……..……:CGPCSN=<CGPCSN>:OPCSN=<OPCSN>
ENT-GTA:GTTSN=<CDPA GTA GTTSET>:GTA=<GTA>:EGTA=<EGTA>:……..……:SELID=<CGPASELID>:OPCSN=<OPCSN>
ENT-GTA:GTTSN=<CGPA GTA GTTSET>:GTA=<GTA>:EGTA=<EGTA>:……..……:CGSSNSN=<CGSSNSN>
In above examples, CGGTASN, CGPCSN and CGSSNSN need to be replaced with OPTSN and SELID with
CGSELID.
8.0 TESTABILITY
This feature shall be delivered to PV in phased manner for team testing.
Since “Increasing # of B-Trees supported on Eagle” is an engineering enhancement, PV can’t test this feature directly.
However, while PV is testing FLOBR and TOBR, this feature gets tested partially by PV in the background. Also, software
development team shall test this feature during module testing.
First the FLOBR feature content shall be delivered to PV for team testing. While PV is team testing the FLOBR feature,
TOBR content shall be delivered to PV for team testing.
A new Test Tool shall be provided. This tool shall show the GTT Selectors and Sets used during translation. See Section 2.13
for additional details.
8.1 Database provisioning sequence
8.1.1 VGTT with 16 GTT lengths
// In the following procedure, the provisioning sequence for VGTT with 16 GTT lengths
// is shown with EGTT feature. The VGTT with 16 GTT lengths shall also works with
// plain GTT.
D_OF.doc
Turn VGTT with 16 GTT lengths Feature ON with EGTT.
CHG-FEAT:GTT=ON:EGTT=ON:VGTT=ON
ENABLE-CTRL-FEAT:PARTNUM=893024801:FAK=<Feature Access Key>
CHG-CTRL-FEAT:PARTNUM=893024801:STATUS=ON
// Turn on other features, if necessary. (EGTT, OBSR, AMGTT, SCCP Loop detection, ANSI/ITU
Translation features etc.,)
Provision Destinations, Linksets, links, routes, MRN and MAP entries.

……………………………………………………..
……………………………………………………..
Provision E5-SM4G card with VSCCP Application.
ENT-CARD:LOC=<location>:APPL=VSCCP
// Allow the card.
Provision GTTSETs.
// CGPA GTA, CGPA PC, CGPA SSN and OPC GTTSETs can be provisioned only when OBSR feature is
turned ON.
ENT-GTTSET:GTTSN=ACDGTA:NETDOM=ANSI:SETTYPE=CDGTA // Provision ANSI CDPA GTA SET.

ENT-GTTSET:GTTSN=ICDGTA:NETDOM=ITU:SETTYPE=CDGTA // Provision ITU CDPA GTA SET.
Provision GTT Translations.
ENT-GTA:GTTSN=ACDGTA:GTA=123456789012345678901:< ………….Routing data………….>:…………….

ENT-GTA:GTTSN=ACDGTA:GTA=12345678901234567890 :< ………….Routing data………….>:…………….
// Provision ITU translations in a similar fashion.
D_OF.doc
Provision GTT Selectors.

ENT-GTTSEL:GTIA=2:TT=1:GTTSN=ACDGTA // ANSI Selector
ENT-GTTSEL:GTII=2:TT=1:GTTSN=ICDGTA // ITU Selector
Retrieve the provisioned data and run the traffic through Eagle.
8.1.2 FLOBR
Turn FLOBR feature ON.
CHG-FEAT:GTT=ON:EGTT=ON
// Turn on other features, if necessary.(VGTT, OBSR, AMGTT, SCCP Loop detection, ANSI/ITU
Change the system wide default GTT hierarchy OR user can choose to provision
the GTT hierarchy per linkset basis.
CHG-SCCPOPTS:DFLTGTTMODE=FCDFCG
Change the system wide default FALLBACK option OR user can choose to provision
the FALLBACK option per translation basis.
CHG-SCCPOPTS:DFLTFALLBACK=YES

……………………………………………………..
ENT-LS:LSN=<Linkset Name>:LST=<Linkset Type>:………:GTTMODE=FCG // Flexible CgPA Mode
……………………………………………………..
ENT-CARD:LOC=<location>:APPL=VSCCP
// Allow the card.
Provision GTTSETs.
turned ON.
ENT-GTTSET:GTTSN=ACDGTA:NETDOM=ANSI:SETTYPE=CDGTA // Provision ANSI CDPA GTA SET.

ENT-GTTSET:GTTSN=ACGGTA:NETDOM=ANSI:SETTYPE=CGGTA // Provision ANSI CGPA GTA SET.
ENT-GTTSET:GTTSN=ACGSSN:NETDOM=ANSI:SETTYPE=CGSSN // Provision ANSI CGPA SSN SET.
ENT-GTTSET:GTTSN=ACGPC :NETDOM=ANSI:SETTYPE=CGPC // Provision ANSI CGPA PC SET.
D_OF.doc
ENT-GTTSET:GTTSN=AOPC :NETDOM=ANSI:SETTYPE=OPC // Provision ANSI OPC SET.
ENT-GTTSET:GTTSN=ICDGTA:NETDOM=ITU:SETTYPE=CDGTA // Provision ITU CDPA GTA SET.

ENT-GTTSET:GTTSN=ICGGTA:NETDOM=ITU:SETTYPE=CGGTA // Provision ITU CGPA GTA SET.
ENT-GTTSET:GTTSN=ICGSSN:NETDOM=ITU:SETTYPE=CGSSN // Provision ITU CGPA SSN SET.
ENT-GTTSET:GTTSN=ICGPC :NETDOM=ITU:SETTYPE=CGPC // Provision ITU CGPA PC SET.
ENT-GTTSET:GTTSN=IOPC :NETDOM=ITU:SETTYPE=OPC // Provision ITU OPC SET.
ENT-GTTSET:GTTSN=CCDGTA:NETDOM=CROSS:SETTYPE=CDGTA // Provision CROSS CDPA GTA SET.

♦ Provisiion ANSI Translations.
// Provision CDPA GTA Translation.
ENT-GTA:GTTSN=ACDGTA:<………….Routing data………….>:OPTSN=ACGSSN:OPCSN=AOPC
// Provision CGPA GTA Translation.

ENT-GTA:GTTSN=ACGGTA:<………….Routing data………….>:OPTSN=ACDGTA
// Provision CGPA PC Translation.

ENT-GTA:GTTSN=ACGPC:<………….Routing data………….>:OPCSN=AOPC
// Provision CGPA SSN Translation.

ENT-GTA:GTTSN=ACGSSN:<………….Routing data………….>:CGSELID=200
// Provision OPC Translation.

ENT-GTA:GTTSN=AOPC:<………….Routing data………….>:OPTSN=ACGSSN
♦ Provisiion ITU Translations.

// Provision CDPA GTA Translation.
ENT-GTA:GTTSN=ICDGTA:<………….Routing data………….>:CGSELID=30
// Provision CGPA GTA Translation.

ENT-GTA:GTTSN=ICGGTA:<………….Routing data………….>:OPCSN=IOPC
// Provision CGPA PC Translation.

ENT-GTA:GTTSN=ICGPC:<………….Routing data………….>:OPTSN=ICGGTA
// Provision CGPA SSN Translation.

ENT-GTA:GTTSN=ICGSSN:<………….Routing data………….>:CDSELID=20
// Provision OPC Translation.

ENT-GTA:GTTSN=IOPC:<………….Routing data………….>:OPTSN=ICGGTA

ENT-GTTSEL:GTIA=2:TT=1:CDGTTSN=AOPC:CGGTTSN=ACDGTA // ANSI Selector
ENT-GTTSEL:GTIA=2:TT=1:CDGTTSN=AOPC:CGGTTSN=ACDGTA:LSN=LSA4 // ANSI Selector
ENT-GTTSEL:GTIA=2:TT=1:SELID=100:LSN=ABC:CDGTTSN=AOPC // ANSI Selector
ENT-GTTSEL:GTIA=2:TT=1:CDGTTSN=ACGGTA:EAGLEGEN=YES // ANSI Selector for Eagle Generated MSUs
D_OF.doc
ENT-GTTSEL:GTII=2:TT=2:CDGTTSN=ICGSSN:SELID=10:LSN=LSI1 // ITU GTI=2 Selector

ENT-GTTSEL:GTII=2:TT=2:CGGTTSN=ICDGTA:LSN=LSI1:SELID=5:CGSSN=10 // ITU GTI=2 Selector
ENT-GTTSEL:GTII=2:TT=2:CDGTTSN=ACGGTA:EAGLEGEN=YES // ITU GTI=2 Selector for Eagle Generated MSUs
ENT-GTTSEL:GTIN=4:TT=3:NPV=3:NAIV=4:CDGTTSN=ICGSSN:SELID=10:LSN=LSI1 // ITU GTI=2 Selector

ENT-GTTSEL:GTIN=4:TT=3:NPV=3:NAIV=4:CGGTTSN=ICDGTA // ITU GTI=2 Selector
ENT-GTTSEL:GTIN=4:TT=3:NPV=3:NAIV=4:CDGTTSN=ACDGTA:EAGLEGEN=YES // ITU GTI=2 Selector for
// Eagle Generated MSUs
Change GTTSETs for default CGPCxSET in SCCP Options.

CHG-SCCPOPTS:DFLTCGPCASN=ACGPC:DFLTCGPCISN=ICGPC.
8.1.3 TOBR
Turn TOBR feature ON.
// Turn FLOBR feature ON first.

CHG-FEAT:GTT=ON:EGTT=ON
// Turn TOBR feature ON.

CHG-CTRL-FEAT:PARTNUM= 893027801:STATUS=ON
// Turn ANY TOBR quantity FAK ON

// Turn on other features, if necessary.(VGTT, OBSR, AMGTT, SCCP Loop detection, ANSI/ITU
Change the system wide default GTT hierarchy OR user can choose to provision
the GTT hierarchy per linkset basis.
CHG-SCCPOPTS:DFLTGTTMODE=FCDFCG
Change the system wide default FALLBACK option OR user can choose to provision
the FALLBACK option per translation basis.
CHG-SCCPOPTS:DFLTFALLBACK=YES

……………………………………………………..
D_OF.doc
ENT-LS:LSN=<Linkset Name>:LST=<Linkset Type>:………:GTTMODE=FCDFCG // Flexible CdPA and

Flexible CgPA Mode
……………………………………………………..
ENT-CARD:LOC=<location>:APPL=VSCCP:TYPE=DSM
// Allow the card.
Provision GTTSETs.
turned ON.
ENT-GTTSET:GTTSN=ACDSSN:NETDOM=ANSI:SETTYPE=CDSSN // Provision ANSI CDPA SSN SET.

ENT-GTTSET:GTTSN=ICDSSN:NETDOM=ITU :SETTYPE=CDSSN // Provision ITU CDPA SSN SET.
ENT-GTTSET:GTTSN=OPCODESET:NETDOM=ANSI:SETTYPE=OPCODE // Provision OPCODE SET.

// Provision Opcode Translatins.
ENT-GTA:GTTSN=OPCODESET:PKGTYPE=QWP:OPCODE=45:FAMILY=25:<………….Routing data………….>:
OPCSET=AOPC:CDSELID=100:FALLBACK=YES
ENT-GTA:GTTSN=OPCODESET:PKGTYPE=QWOP:OPCODE=NONE:FAMILY=*:<………….Routing data………….>:
OPCSET=AOPC:OPTSN=ACDGTA
ENT-GTA:GTTSN=OPCODESET:PKGTYPE=ANY:OPCODE=*:FAMILY=*:<………….Routing data………….>:
OPTSN=ACGGTA:FALLBACK=YES
ENT-GTA:GTTSN=OPCODESET:PKGTYPE=BGN:OPCODE=50:ACN=1-2-3-4-5-6-7:<………….Routing data………….>:
OPCSET=IOPC:OPTSN=ACDSSN
ENT-GTA:GTTSN=OPCODESET:PKGTYPE=BGN:OPCODE=50:ACN=1-2-3-4-5:<………….Routing data………….>:
OPCSET=IOPC:OPTSN=ACDSSN:FALLBACK=YES
ENT-GTA:GTTSN=OPCODESET:PKGTYPE=CNT:OPCODE=NONE:ACN=*:<………….Routing data………….>:
OPCSET=IOPC:OPTSN=ACGSSN
ENT-GTA:GTTSN=OPCODESET:PKGTYPE=ANY:OPCODE=*:ACN=*:<………….Routing data………….>:
OPCSET=AOPC:OPTSN=ACGGTA:FALLBACK=YES
// Provision CDPA SSN translations.

ENT-GTA:GTTSN=ACDSSN:cdssn=4:ecdssn=15:<………….Routing data………….>:
OPCSN=AOPC:CDSELID=100
ENT-GTA:GTTSN=ICDSSN:cdssn=20:<………….Routing data………….>:
OPCSN=IOPC:OPTSN=OPCODESET:FALLBACK=NO

ENT-GTTSEL:GTIA=2:TT=1:CDGTTSN=OPCODESET:CGGTTSN=ACDSSN // ANSI Selector
ENT-GTTSEL:GTIA=2:TT=1:LSN=<LSN>:CGSSN=100:CGGTTSN=OPCODESET // ANSI Selector
D_OF.doc
ENT-GTTSEL:GTII=2:TT=3:LSN=<LSN>:SELID=500:CGSSN=10:CGGTTSN=OPCODESET // ITU GTI=2 Selector

ENT-GTTSEL:GTII=2:TT=3:LSN=<LSN>:SELID=500:CDGTTSN=OPCODESET:CGGTTSN=OPCODESET // ITU GTI=2
// Selector
Change GTTSETs for default CGPCxSET in SCCP Options.
CHG-SCCPOPTS:DFLTCGPCASN=ACGPC:DFLTCGPCISN=ICGPC.
8.1.4 Test Tool
Using the test tool involves 2 steps: setting up the test parameters and invoking the test message. There are 10 entries provided
for use. Each can be individually customized for different test scenarios. Initial values are provided for all fields, but it
expected that the user will have to alter the data to meet the provisioning of their system.
Setting Up Test Parameters:

The test data can be set up over several commands. The data is simply stored in the table based on the msgn (message
number).
CHG-SCCP-MSG:MSGN=1:ACTIVE=YES:OPCA=5-5-5:EAGLEGEN=NO:LSN=LS123ABC:CDPAGTI=2
CHG_SCCP-MSG:MSGN=1:CDPATT=0:CDPASSN=8:CDPAPC=7-7-7:CGPATT=0:CGPASSN=6:CGPAPC=5-5-5
Once the data is entered, it can be displayed via the RTRV-SCCP-MSG command.
If the data is all correct, then the test can be invoked
Invoking the test tool:

The test tool is invoked via TST-MSG command
TST-MSG:FEAT=GTT:PROT=SCCP:LOC=<E5-SM4G>:MSGN=1:MODE=DEBUG
9.0 LIMITATIONS
♦ Due to database design changes, the way ENT/CHG-GTTSEL commands that were working with OBSR feature
shall change after moving to this Eagle release. See section 7.0 for more information.
♦ Due to 40 parameters limit per command restriction, a generic parameter name is used in place of existing
parameters. (see section 7.0 for more information)
♦ Due to the addition of more parameters, the formats of retrieve commands are modified and also the parameter
names are changed to support future expansion.
♦ TOBR does not support indefinite form of lengths for ANSI TCAP messages.
♦ TOBR supports only upto two bytes of long format length in TCAP messages.
♦ TOBR might not fully support some of the proprietary TCAP implementations. LRNQT feature in Eagle supports
one of such implementations where it handles ITU TCAP messages containing ANSI operations and parameters.
TOBR is unable to route such messages based on Opcode/Family. These messages however could be routed based
on Message/package type.
D_OF.doc
APPENDIX A: GTT ACTIONS INFO
The GTT Action feature is not reconciled in to the release in which FLOBR supported at the time of approving FLOBR and
TOBR feature requirements. Once GTT Action feature is reconciled, the FLOBR/TOBR FD shall be updated with GTT
Actions requirements.
9.1 GTT Actions

As part of OBSR feature, Discard and UDTS actions are supported (through XLAT parameter) per translation. As part of
TOBR feature development, two more action values shall be supported per translation, namely Duplicate and TCAP Error.
However, unlike OBSR feature, the GTT action entries shall be provisioned through GTT action sets. Each translation can
refer to one GTT action set. For example,
Figure 21: Translation with GTT Action set
User shall be able to provision the GTT Action sets through ENT/CHG/DLT/RTRV-GTTASET commands. Each GTT Action
set shall contain a GTT Action set name, the GTT Action, Action specific data and reference count as shown in Erreur !
Source du renvoi introuvable..
Figure 22: GTT Action set entry
The GTT Action set name shall be the key into GTT Action set table. When a GTT Action set is created, the reference count
for that entry shall be set to zero. As shown in Erreur ! Source du renvoi introuvable., when a GTT translation refers to a
GTT Action set, the reference count for that GTT Action set shall be incremented by 1. Whenever a GTT translation
dereference that GTT Action set, the reference count for that GTT Action set shall be decremented by 1.
The GTT Action set entry can be deleted only when the reference count is zero.
The GTT Action set table can have a maximum of 2000 entries.
9.1.1 GTT Action Types
The GTT Action set shall support two types of actions – discard and duplicate.
D_OF.doc
The discard type can be:

Discard: The MSU shall be discarded as per the functionality defined in OBSR. A UIM shall be displayed, if a
request is provisioned in the database.
UDTS: The MSU shall be discarded as per the functionality defined in OBSR. A UDTS/XUDTS message shall be
returned with an error code, if provisioned in the database. A UIM shall be displayed, if a request is provisioned in
the database.
TCAP Error: The MSU shall be discarded and a reject message shall be generated to the originator with an error
code, if the error code is provisioned in the dataase. If an error code is not provisioned, default error code zero shall
be used. A UIM shall be displayed, if a request is provisioned in the database.
The duplicate action type supports only one action, duplicate. When the action is duplicate, a copy of the MSU shall be sent to
the duplicate node. If Eagle fails to route the duplicated MSU, a UIM shall be generated indicating the duplicate routing
failure. This duplicate behavior is in addition to the normal processing and routing of the original MSU.
Each GTT Action set shall contain only one of the following actions:
DISC
UDTS
TCAP Error
DUP
Each translation can have only one GTT Action set and each GTT Action set shall have only one action.
When a translation contains a GTT Action set which has Discard or UDTS or TCAP Error action, that translation is not
allowed to have routing data. However, when a translation contains a GTT Action set which has DUP action, then that
translation is allowed to have routing data.
9.1.2 GTT Action FAKs
The discard and duplicate action types are controlled through FAKs. The discard action types are controlled through ON only
FAK and duplicate action type is controlled through ON/OFF FAK.
User can provision the discard action types when discard action type FAK is turned ON.
User can provision the duplicate action type when duplicate action type FAK is enabled. However, the message processing
doesn’t take place unless the duplicate action type FAK is turned ON. When user turns the duplicate action type FAK OFF
(but enabled), the already provisioned data shall remain in the database. However, messages will be processed based on the
routing data and duplicate action won’t be processed.
Table 34: Protocol Requirements Table for GTT Actions

Optional
(R or O)
D_OF.doc

Optional
(R or O)
FD-172 R If a translation is not associated with any GTT Action, the MSUs shall be EOAM,
routed as per the routing data. OAMHC,
VSCCP,
SCCPHC
FD-173 R When the "GTT Act - DUPLICATE" feature is turned OFF (but still enabled), EOAM,
the previously provisioned data shall remain in the database. The message OAMHC,
shall be routed as per the translation routing data. However, the duplication VSCCP,
action shall be disabled for all translations. SCCPHC
If Eagle is unable to route the MSU based on the routing data in the
translation, the MSU shall be discarded.
FD-174 R If a translation is associated with any GTT Action, the MSUs shall be VSCCP,
processed as per description in section Erreur ! Source du renvoi SCCPHC
introuvable.
9.1.3 GTT Actions User Interface Requirements
Table 35: User Interface Requirements Table for GTT Actions

Optional
(R or O)
FD-175 R A new FAK (part number: 893-0275-01) is required for the "GTT Action - EOAM,
DISCARD" feature. This FAK will be an ON only FAK. The default will be OAMHC
disabled and OFF.
FD-176 R The "GTT Action - DISCARD" feature can’t be enabled unless EGTT feature EOAM,
is turned ON. OAMHC
FD-177 R Once "GTT Action - DISCARD" FAK is enabled, the FAK can’t be disabled. EOAM,
OAMHC
FD-178 R A temporary FAK is not supported for "GTT Action - DISCARD". EOAM,
OAMHC
FD-179 R A new FAK (part number: 893-0276-01) is required for the "GTT Action - EOAM,
DUPLICATE" feature. This FAK will be an ON/OFF FAK. The default will OAMHC
be disabled and OFF.
FD-180 R The "GTT Action - DUPLICATE" feature can’t be enabled unless EGTT EOAM,
feature is turned ON. OAMHC
FD-181 R Once "GTT Action - DUPLICATE" FAK is enabled, the FAK can’t be EOAM,
disabled. OAMHC
FD-182 R A temporary FAK is not supported for "GTT Action - DUPLICATE". EOAM,
OAMHC
FD-183 R Once the "GTT Action - DUPLICATE" feature is enabled and turned ON, it EOAM,
can be turned OFF. OAMHC
FD-184 R The GTT actions shall be supported through GTT Action sets as shown in EOAM,
Erreur ! Source du renvoi introuvable.. OAMHC
D_OF.doc
FD-185 R A new command set, ENT/CHG/DLT/RTRV-GTTASET, shall support the EOAM,

provisioning of GTT Action Sets in the database. OAMHC
FD-186 R The RTRV-GTTASET command shall be cancelable. EOAM,
OAMHC
FD-187 R The GTT Action commands should support, at minimum, “GTT Action Set EOAM,
Name” and “GTT Action” parameters and associated data with that action. OAMHC
FD-188 R Each GTT Action Set shall support only one action. (“Discard” or “UDTS” or EOAM,
“TCAP Error” or “Duplicate”) OAMHC
FD-189 R When the "GTT Action - DISCARD" feature is turned ON, the “GTT Action” EOAM,
parameter shall support provisioning of “Discard”, “UDTS” and “TCAP Error” OAMHC
actions.
FD-190 R Only when the "GTT Action - DUPLICATE" feature is enabled, the “GTT EOAM,
Action” parameter shall support “Duplicate” action. OAMHC
FD-191 R When the “GTT Action” is “Duplicate”, user can specify the duplicating node EOAM,
information. (Routing Indicator, Point Code, Subsystem Number and OAMHC
translation type)
FD-192 R When the “GTT Action” is “Duplicate”, user can optionally specify the EOAM,
MAPSET/MRNSET Id based on routing indicator. OAMHC
FD-193 R When the “GTT Action” is “Discard” or “UDTS” or “TCAP Error”, user can EOAM,
optionally request that an UIM be displayed. OAMHC
FD-194 R When the “GTT Action” is “UDTS” or “TCAP Error”, user can optionally EOAM,
provision the error code. OAMHC
FD-195 R User shall be able to specify the “GTT Action Set Name” per GTT translation EOAM,
as shown in Erreur ! Source du renvoi introuvable.. OAMHC
FD-196 R Each GTT translation shall take “GTT Action Set Name” as an optional EOAM,
parameter. OAMHC
FD-197 R If the GTT translation doesn’t use “GTT Action Set Name”, the translation EOAM,
entry shall continue to contain and use the route (translation) data. OAMHC
FD-198 R When user specifies the “GTT Action Set Name” per GTT translation and if EOAM,
the GTT action for this GTT Action Set is “Discard” or “UDTS” or “TCAP OAMHC
Error”, then that translation entry shouldn’t accept any other routing
(translation) data.
FD-199 R When user specifies the “GTT Action Set Name” per GTT translation and if EOAM,
the GTT action for this GTT Action Set is “Duplicate”, then that translation OAMHC
entry must accept the routing (translation) data also (to be applied to the
original MSU).
FD-200 R In the database, a reference count shall be maintained for each GTT Action EOAM,
Set. Whenever a GTT Action Set is being referred by a translation, the OAMHC
reference count for that GTT Action Set shall be incremented by 1.
FD-201 R Whenever a GTT Action Set is de-referred by a translation, the reference count EOAM,
for that GTT Action Set shall be decremented by 1. OAMHC
FD-202 R The RTRV-GTTASET command shall display the reference count for EOAM,
specified/all GTT Action Sets when requested by the user. OAMHC
FD-203 R The RTRV-GTTASET command shall be cancelable. EOAM,
OAMHC
FD-204 R User must be able to retrieve single or all GTT Action Set(s) through RTRV- EOAM,
GTTASET command. OAMHC
FD-205 R A GTT Action Set can be deleted only when the reference count for that GTT EOAM,
Action Set is zero. OAMHC
D_OF.doc
FD-206 R User must be able to provision multiple GTT Action Sets with same or EOAM,
different GTT Actions as long as space is available in the table. OAMHC
FD-207 R A maximum of 2000 GTT Action Sets shall be supported. EOAM,
OAMHC
FD-208 R No SEAS support is required for the GTT Action Set table. EOAM,
OAMHC
FD-209 R In CHG-GTA command, when user specifies the GTT Action set with EOAM,
“Discard” action to the already existing translation, the routing data in the OAMHC
existing translation (if already provisioned) shall be deleted in the database.
FD-210 R In CHG-GTA command, when user specifies the GTT Action set with EOAM,
“Duplicate” action to the already existing translation (with GTT Action OAMHC
“Discard or “UDTS” or “TCAP Error”) and if the existing translation doesn’t
have the routing data, user needs to specify the routing data for that translation.
9.1.4 GTT Actions Hardware Requirements
Table 36: Hardware Requirements Table for GTT Actions

Optional
(R or O)
FD-211 R The GTT Action features (the "GTT Action - DISCARD" and "GTT Action - EOAM,
DUPLICATE") can’t be enabled unless DSM or better card with VSCCP OAMHC
application is provisioned in the database.
FD-212 R ENT-CARD command shall be updated not to allow the provisioning of EOAM,
TSM/SCCP card when GTT Action features is/are enabled. OAMHC
9.1.5 GTT Actions Performance Requirements
Table 37: Performance Requirements Table for GTT Actions

Optional
(R or O)
FD-213 R The performance numbers for DSM and E5-SM4G card shall remain same VSCCP,
with GTT Actions feature. SCCPHC
FD-214 R E5-SM4G shall continue to support the following rates:
3125 TPS with one or more of EPAP DB feature(s) and GTT Action
features turned ON SCCPHC
5000 TPS with Action features turned ON without EPAP DB features
and with ELAP features.
Table 38: Measurement Requirements Table for GTT Actions

D_OF.doc
Optional
(R or O)
FD-215 R Following new registers shall be added to the SYSTOT-STP (system wide) VSCCP,
and SYSTOT-TT (per translation type) 30 min reports SCCPHC
REGISTER DESCRIPTION
GTTACTPER This register shall represent the total number of
message receiving either duplicate or discard
treatment.
GTTACTDUP This register shall represent the number of messages
duplicated by the "GTT Action - DUPLICATE"
feature.
GTTACTDISC This register shall represent the number of messages
silently discarded by the "GTT Action - DISCARD"
feature.
GTTACTUDTS This register shall represent the number of messages
discarded with UDTS/XUDTS error by the
"GTT Action - DISCARD" feature.
GTTACTTCER This register shall represent the number of messages
discarded with TCAP error by the
“GTT Action - DISCARD” feature.
FD-216 R The Eagle 5 ISS shall support all measurements for this feature on the MCP,
measurements platform (measurements platform is required to retrieve these EOAM,
measurements in SYSTOT-STP and SYSTOT-TT reports). OAMHC
FD-217 R If measurements platform is not available, this feature shall operate normally MCP,
without measurements. EOAM,
OAMHC
Table 39: Upgrade Requirements Table for GTT Actions
FD Req’t Required or Requirement Description Affected

No. Optional (R (and any additional comments if necessary) GPLs
or O)
FD-218 R Prior to upgrade if OBSR feature is enabled, then "GTT Action -DISCARD" EOAM,
feature shall be enabled and turned ON after the upgrade. OAMHC
FD-219 R Prior to upgrade if OBSR feature is not enabled and OBSR feature is enabled EOAM,
after upgrade, then "GTT Action - DISCARD" feature won’t be enabled OAMHC
automatically.
That means the XLAT=DISC and XLAT=UDTS functionality won’t be part

of OBSR after upgrade. The FAK for "GTT Action - DISCARD" feature
must be enabled and turned ON to use “Discard” and “UDTS” actions
functionality.
FD-220 R Prior to upgrade if OBSR feature is enabled and any translation(s) is/are EOAM,
provisioned with XLAT=DISC/UDTS, then during upgrade the OAMHC
corresponding GTT Action Set(s) (with GTT Action=Discard/UDTS) shall be
created in the GTT Action Set table and the translation(s) shall be updated to
refer to that GTT Action Set.
NOTE : Only one GTT Action Set with GTT Action=Discard and only
D_OF.doc
one GTT Action Set with GTT Action=UDTS shall be created

during upgrade.
D_OF.doc

FD006137 - Tobr - Flobr - Tcap - Segmented - of

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FD006137 - Tobr - Flobr - Tcap - Segmented - of

Uploaded by

Copyright:

Available Formats

PROPRIETARY INFORMATION INTERNAL USE ONLY

Network Systems Division

Title: TCAP Opcode Based Routing (TOBR) Feature Description

TCAP Opcode Based Routing (TOBR)

TCAP Segmented SMS Support Phase 2

Also covers the following PRs:

Support for 16 GTT Lengths in VGTT

Increasing # of B-Trees supported on Eagle

2.8 Interaction with ANSI/ITU/CHINA SCCP Conversion ............................................................................................... 36

8.0 TESTABILITY ................................................................................................................................................................ 75

Figure 22: GTT Action set entry .................................................................................................................................................. 82

This document also covers the following enhancements:

These features shall be implemented in EAGLE.

The scope of this document is to describe:

1.2 Acronyms and Terminology

Table 1: Acronyms and Terminology

ACN Application Context Name

2.0 GENERAL DESCRIPTION

2.2 Increasing # of B-Trees supported on Eagle – An Engineering Enhancement

2.3 FLOBR Feature

The subsequent sections describe these concepts in detail.

2.3.1 Linkset Based Routing

2.3.1.1 FLOBR GTT Hierarchies

Table 2: Available GTT hierarchies

Get the GTT hierarchy on

Get the first GTT Mode

Perform the GTT Selector Get the next GTT Mode

FLOBR Is GTT hierarchy specific OBSR

Is Translation Found? No Is there a Database failure No Is GTT hierarchy specific FLOBR

Figure 1: GTT hierarchy algorithm for FLOBR

Table 3: Available GTT set types in selector table

2.3.1.2 GTT selection with FLOBR GTT Modes

Search GTT Selector table for

Find CdPA GTA Find CgPA SSN

Figure 2: GTT selection with FLOBR CdPA Mode

Figure 3: GTT selection with FLOBR CgPA Mode

2.3.2 Flexible Routing with GTT Translations

Table 4: Flexible Routing with GTT Translations

CgPA GTA Mutually exclusive

CgPA PC Mutually exclusive

CgPA SSN Mutually exclusive

CdPA SSN Mutually exclusive

2.3.2.1 Fallback Option with FLOBR

Routing when subsequent search failed in FLOBR

The fallback option shall take “Yes” or “No” values.

Under the above conditions

For OBSR hierarchy the value of fallback option shall be ignored.

The scenarios for above conditions shall be discussed in subsequent sections.

2.3.2.1.1 Routing when subsequent GTT set search failed in FLOBR

Figure 4: Action when subsequent translation search fails

2.3.2.1.2 Routing when subsequent search for SELID failed in FLOBR

Figure 5: Action when subsequent SELID search fails

Translation Routing Data +

Translation Routing Data +

Translation Routing Data +

Translation Routing Data + Set 5 set type : CgPA SSN

Translation Routing Data +

Translation Routing Data +

Translation Routing Data +

2.3.2.1.4 Limiting the number of database searches for FLOBR

Figure 7: Limiting the number of database searches

2.3.3 GTT for Eagle-generated MSUs

While provisioning, when user specifies EAGLEGEN=Yes