TM - Reference Data Model For Domestic V0.2

TELEKOM MALAYSIA
Reference Data Document v0.2
"The information contained within this document is the property of Intec Telecom Systems PLC
("Intec") which is confidential and protected by international copyright laws. No part of this document
may be photocopied, reproduced or translated in any form or by any means, or stored in a retrieval
system or transmitted electronically or otherwise, without the prior written consent of Intec. Although
every endeavor has been made to ensure that the information contained within this document is up
to date and accurate, Intec cannot be held responsible for any inaccuracy or error in the information
contained within this document. Intec makes no warranty of any kind with regard the information
contained within this document and Intec shall not be liable for any direct, indirect, incidental or
consequential damages which may arise in connection with the furnishing, reliance or use of the
information contained within this document. Intec reserves the right to change the information
contained within this document and any product specification without notice."
530144068.doc4 ‘One-stop Network Profitability TM’ ©2008 Intec Telecom Systems PLC
Customer Confidential Page 1 of 55 July 1, 2021

Revision History
Release History
Version Date Author Description
0.1 10-04-2009 Li Keng, Toh Draft version
0.2 22-04-2009 Frederic Review of v0.1 wıth all changes updated
Guesdon and
Jın Yee
(Revıewer)
Lı Keng
(Update)
Distribution
Version Name Role Responsibility Date Distributed
Release and Approval

Version Name Role Date Approved
530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

Profitability TM’
Table of Contents
1 INTRODUCTION..................................................................................................................5
1.1 OBJECTIVES......................................................................................................................5
1.2 SCOPE...........................................................................................................................5
1.3 TESTING........................................................................................................................6
1.4 START DATES..................................................................................................................6
1.5 BULK LOADER..................................................................................................................6
2 GLOSARRY..........................................................................................................................7
3 AGREEMENT DATA..............................................................................................................8
3.1 ORGANIZATION GROUP......................................................................................................8
3.2 ORGANIZATION................................................................................................................9
3.3 MAINTAIN AGREEMENT.....................................................................................................11
3.3.1 Agreement................................................................................................................11
3.3.2 Agreement Parameters..............................................................................................12
3.4 CONTACT DETAILS.....................................................................................................14
3.4.1 Job Designation........................................................................................................14
3.4.2 Contact Category......................................................................................................14
3.4.3 Contact Details..........................................................................................................15
3.5 OPERATION CATEGORY...............................................................................................17
3.5.1 Operation Category...................................................................................................17
3.6 CATALOGUE...................................................................................................................18
3.6.1 Product Group Categories..........................................................................................18
3.6.2 Product Group...........................................................................................................19
3.6.3 Product.....................................................................................................................20
3.6.4 Product Derivation Network Address...........................................................................20
3.6.5 Network Address Group.............................................................................................21
3.6.6 Network Address Group Membership..........................................................................22
3.6.7 Product Derivation.....................................................................................................23
3.7 RATING........................................................................................................................24
3.7.1 Rating Scenarios.......................................................................................................24
3.7.2 Rating Scenario Determination...................................................................................26
3.7.3 Component Parameter Category.................................................................................28
3.7.4 Rating Components...................................................................................................28
3.7.5 Rating Rules.............................................................................................................29
4 NETWORK DATA...............................................................................................................32
4.1 CIRCUIT SWITCHED.........................................................................................................32
4.1.1 Network Node / Switch..............................................................................................32
4.1.2 Point Of Interconnect................................................................................................32
4.1.3 Trunk Group.............................................................................................................34
4.1.4 Network Address.......................................................................................................36
4.1.5 Network Address Owner............................................................................................37
4.1.6 Network Address Aggregation....................................................................................37
4.1.7 Aggregation Hierarchy Level......................................................................................38
4.1.8 Network Address Aggregation Membership.................................................................39
5 BILLING DATA...................................................................................................................40
5.1 TIERS..........................................................................................................................40
5.1.1 Tier Maintenance.......................................................................................................40
5.1.1.1 Tier...................................................................................................................40
5.1.1.2 Tier Hierarchy....................................................................................................40
5.1.2 Tier Derivation Style..................................................................................................42
5.1.2.1 TDST Non-distance............................................................................................42
Profitability TM’
5.1.2.2 TDST Distance...................................................................................................43
5.1.2.3 TDST Retail Aggregation (Ag A# Ag B#).............................................................43
5.1.2.4 Cash Flow B number..........................................................................................44
5.1.2.5 TDST Distance – EBC B number based................................................................45
5.2 CALENDAR....................................................................................................................46
5.2.1 Time Premium...........................................................................................................46
5.2.2 Base Calendar...........................................................................................................47
5.2.3 Rating Calendar........................................................................................................48
5.3 CURRENCY....................................................................................................................49
5.4 RATES.........................................................................................................................50
5.5 BILLING PERIOD.............................................................................................................53
6 REFERENCE DATA DOCUMENT SIGN OFF...........................................................................55
7 APPENDIX A......................................................................................................................56

Profitability TM’
1 INTRODUCTION
1.1 OBJECTIVES
The objective of this document is to record the manner in which collected Reference Data is to be
entered into the Interconnect application and includes the identification of naming standards where
applicable.
1.2 SCOPE
The naming standards and reference data included in this document are as a result of discussions
between Intec Systems and TELEKOM MALAYSIA. Table lists the sources used where data has been
provided in the format of Excel worksheets, Word documents, e-mails and notes.
Filename Source
Table 1.2-1 Data Sources
The list of source filename used is as below;

TM - Call Scenario for Domestic v1.3.doc
TM - Interconnect Specs v0.8.doc
In this project, the scopes only cover reference data for the below attached agreements.
MAXIS BROADBAND SDN. BHD.

CELCOM TRANSMISSION (M) SDN. BHD.
TIME dotCom BERHAD
MAXIS MOBILE SDN. BHD.
CELCOM (MALAYSIA) BERHAD
U MOBILE SDN. BHD.
DIGI TELECOMMUNICATION SDN. BHD.
UMW E-TECHNOLOGIES SDN. BHD.
REDTONE TELECOMMUNICATIONS SDN. BHD.
VENUS TELECOMMUNICATIONS SDN. BHD.
CALLPLUS TELECOMMUNICATIONS SDN. BHD.
PACKET ONE NETWORKS (MALAYSIA) SDN. BHD.
PERNEC PAYPOINT SDN. BHD.
TIME REACH SDN. BHD.

Profitability TM’
1.3 TESTING
The data layout in this document gives the reference data required for Acceptance Testing as agreed
by the cut off date for Reference Data Collection.
Any data changes required for production will be the responsibility of TELEKOM MALAYSIA.
1.4 START DATES

All Start Dates will be entered as 01 January 2009 unless stated otherwise.
End Dates will be entered as blank. Blank end dates are set to the default end date of 31/12/2999
1.5 BULK LOADER

It strongly recommended making use of the bulk loader templates for the modelling of large
quantities of data. Bulk loader templates are available for most reference data types; please check
the bulk loader to see which templates are available.

Profitability TM’
2 GLOSARRY
Term Description
NOP Network Operator
CNP Charging Number Prefix
POI Point of Interconnect
NAA Network Address Aggregation
TDST Tier Derivation Style
WSID Wholesale ID of the Network Operator

Profitability TM’
3 AGREEMENT DATA
3.1 ORGANIZATION GROUP
An Organization Group is usually the telecommunications network owner and the owner of the
Interconnect system. Organization groups may be defined to group the Interconnect owner’s
Franchises together as well as group other operators under groups such as national, international or
other operator groups.
At least one Organization Group must be defined.
Field Length Mandat Comments

ory
ID 6 Y Short name of Organization Group.
Name 30 Y Full name of Organization Group.
Table 3.1-2 Organisation Group Fields
ID Name
Note: Please refer to : 01a - Agreement Data (Domestic - Interconnect).xml and 01b - Agreement Data
(Domestic-VOIP & Payphone).xml under the ‘Organisation Group’ tab for a complete details.
Table 3.1-3 Organisation Groups

Profitability TM’
3.2 ORGANIZATION
Organization is used to maintain details of Network Operators (NOP) and Franchises (FRN).
A Franchise is used when there are separate business units within Interconnect owner’s company.
Typical examples of Franchises are Mobile and Fixed business units.
In the context of the Interconnect application the Network Operator (NOP) is the operator with whom
the Interconnection is made.
Field Length Mandator Comment

y
ID 6 Y Short name of network operator. In this case, TM is using
WSID as the network operator ID.
Note:
Set system configuration Inter Franchise Billing Indicator
to Y for inter franchise billing
Specific for TM:

Wholesale id will be use as Organisation id.
Name 30 Y Network operator name
Type 3 Y Defines the network operator as a NOP or Franchise.
Value is either:
FRN (Franchise)
OPR (Operator)
Organization 6 Y Associates the network operator or franchise to an
Group organization group.
R/S NAA Ind 1 N Indicates if Rating Scenario Network Address Aggregation
overrides can be set.
Note:
Default value will be ‘Y’
This option is only relevant when the organization type is
Franchise
R/S DOW Ind 1 N Indicates if Rating Scenario Day of Week/Time of day and
trunk overrides can be set.
Note:
Default value will be ‘Y’
R/S NAA Ind will be automatically set to ‘Y’ if this item is
set to ‘Y’
This option is only relevant when the organization type is
Franchise
Rating Style 1 N Not Applicable for TELEKOM MALAYSIA’s case.
Table 3.2-4 Organisation Fields

Profitability TM’
ID Name Type Org R/S NAA R/S DOW Rating
Group Ind Ind Style
Note: Please refer to : 01a - Agreement Data (Domestic - Interconnect).xml and 01b - Agreement
Data (Domestic-VOIP & Payphone).xml under the ‘Organisation’ tab for a complete details.
Table 3.2-5 Organisations

Profitability TM’
3.3 MAINTAIN AGREEMENT
3.3.1 Agreement
An Agreement is defined between a Franchise and a Network Operator. An Agreement is required to

rate calls. If during the rating process it is determined that no agreement has been defined the call
record will be placed under error CDR management.
Field Length Mandatory Comment

Franchise 6 Y The Franchise ID the agreement belongs to
Network 6 Y The NOP ID the agreement belongs to
Operator
Start Date Date Y Indicates the date from which the agreement is
effective
End Date Date N Indicates the date when the agreement will expire.
Recovery 7 N Stored as the actual percentage being declared by
Percentage NOP. Only applicable for financial summaries where
statement direction is Received.
Use 1 Y Use Weighted Indicator. A Weighted Rates call is
Weighted assumed to originate from the Incoming path
Rates operators network, but the rate is adjusted based
on historical data to reflect the proportion of calls
that do not originate in that network, but that
originate elsewhere.
Note:
This option is only applicable to ITU module. Default
value will be ‘N’
Local 1 Y Local Network Operator Indicator
Operator Note:
This option is only applicable to ITU. Default value
will be ‘N’
Table 3.3-6 Agreement Fields
Franchise Network Operator Start Date End Date Recovery Use Local
Percentage Weighted Operator
Rates
Note: Please refer to : 01a - Agreement Data (Domestic - Interconnect).xml and 01b -
Agreement Data (Domestic-VOIP & Payphone).xml under the ‘Agreement’ tab for a complete
details.
Table 3.3-7 Agreements

Profitability TM’
3.3.2 Agreement Parameters
Agreement Parameter is used to define which products are supported per NOP and to define Call
Attempt Rules and Thresholds per NOP.
All products or only specific products may be associated with an Agreement

Franchise 6 Y The Franchise ID the agreement belongs to
Network 6 Y The NOP ID the agreement belongs to
Operator
Product 14 Y The product ID that the agreement belongs to
Note:
All Products are represented by a ‘*’
Start Date Date Y Indicates the date from which the agreement is effective
End Date Date N Indicates the date when the agreement will be terminated or
come to an end
Mask Suffix A 2 N Indicate the number of digits that should be ignored for A
Number numbers when a CDR export is performed by entering a
numeric value in the Mask Suffix A text field
Mask Suffix B 2 N Indicate the number of digits that should be ignored for B
Number numbers when a CDR export is performed by entering a
numeric value in the Mask Suffix B Numbers text field
Comp 2 N Indicates the direction of a call component. It has a pre-
Direction loaded values of:
I - Incoming
O – Outgoing
T - Transit
TI - Incoming Transit
TO - Outgoing Transit
Note:
Only need to set up if there’s a need to set the call attempt
charge.
Unit of 8 N The unit of a call attempt, for example, 5 seconds or 50 bytes.
Measure The Unit of Measure specified must be the Base Unit of
Measure.
Note:
charge.
Rating 2 N Describes the types of traffic that can have a Call Attempt
parameter 1 Threshold against it, for example Conversation Duration and
Network Duration for telephony calls and four data volume
fields for data calls and enhanced telephony.
Note:
charge.
Profitability TM’
Call Attempt 1 N Indicates the Rule rating should apply if the Duration of a call
Rule 1 is less than the Call Attempt specified. The options available for
the Call Attempt Rule are Accept and Charge, Accept and No
Charge and Reject.
Note:
charge.
Table 3.3-8 Agreement Parameters Fields
Franchise Network Product Start Date End Date Mask Suffix Mask Suffix B
Operator A Number Number
Data (Domestic-VOIP & Payphone).xml under the ‘Agreement Parameter’ tab for a complete details.
Table 3.3-9 Agreement Parameters

Profitability TM’
3.4 CONTACT DETAILS
3.4.1 Job Designation
Job designation is used to maintain Job Title or Job Descriptions to be used when filling in contact
details.
ID 3 Y Short name for the Job Designation
Name 30 Y Name of the Job Designation
Table 3.4-10 Job Designation Fields
ID Name
Agreement Data (Domestic-VOIP & Payphone).xml under the ‘Job Designation’ tab for a
complete details
Table 3.4-11 Job Designation
3.4.2 Contact Category
Contact category is used to maintain Contact Categories that allows user to group or categorise
contacts.
ID 3 Y Short name for the Contact Category
Name 30 Y Name of the Contact Category
Table 3.4-3 Contact Category Fields
ID Name
Agreement Data (Domestic-VOIP & Payphone).xml under the ‘Contact Category’ tab for a
complete details.
Table 3.4-4 Contact Category
3.4.3 Contact Details

Profitability TM’
Contact Details is used to record store various addresses and Contact Details for the NOP. Contacts
must be associated with at least one Organisation. This table is customised for Oracle Customer
Number data use as well.

Title 10 N Title of the contact. Example: Mr, Ms, Mrs, etc.
First Name 30 N First name of the contact.
Surname 50 Y Surname of the contact.
Job 3 Y Job Designation of the contact.
Designation
Contact 3 Y Contact category the contact belongs to.
Category
Office 30 N Office telephone of the contact.
Telephone
Office Cell 30 N Office cell phone of the contact.
Office Fax 30 N Office facsimile of the contact.
Office 50 N Office email address of the contact.
Email
Sundry 250 N To store the TM’s contact details.
Information E.g. TM Contact Details: Sahmalah Nataraja
Postal 250 N Corresponding address 1 of the contact.
Address_1
Postal 250 N Corresponding address 2 of the contact.
Address_2
Associated 6 Y Network Operator the contact belongs to
Organisatio
n_1
Table 3.4-5 Contact Details Fields
Surn Job Office Office Office Office Sundr Postal Postal Conta Associ
ame Designati Telep Cell Fax Email y Addre Addre ct ated
on hone Infor ss_1 ss_2 Categ Organi
matio ory sation
n _1
Data (Domestic-VOIP & Payphone).xml under the ‘Contact Detail’ tab for a complete details.
Table 3.4-6 Contact Details

Profitability TM’
3.5 OPERATION CATEGORY
3.5.1 Operation Category
Operation Category in this case is used to store the Relationship Code, Segment Code, Cost Centre,
Industry Code and Trading Partner ID.

ID 20 Y Concatenation of Relationship Code (X), Segment
Code (NNN), Cost Centre (CCCCC), Trading Partner
ID (TTTT) and Industry Code (III). The format will
be XNNNCCCCCCTTTTIII.
Name 30 Y Concatenation of Wholesale ID(5) and Operator
Name(24).
Table 3.5-12 Operation Category Fields
ID Name Description
EW30WMSA6T 50151 REDTONE TELECOMM.

EW30WMSA6V 50592 CALLPLUS TELECOM. SB
Note: This data needs to be configured manually in the system. Please refer to : 01a - Agreement
Data (Domestic - Interconnect).xml and 01b - Agreement Data (Domestic-VOIP & Payphone).xml
under the ‘Operation Category’ tab for a complete detail.
Table 3.5-13 Operation Category Fields

Profitability TM’
3.6 CATALOGUE
There are three types of Catalogue reference data, namely:
Product Group Categories
Product Group
Products
Setting up a Product involves creating Product Group Categories and then Product Groups.
You add Product Groups to Product Group Categories and then add Products to the Product Groups.
This association allows Products and Product Groups to be grouped in a variety of ways for billing
purposes.
NOTE:
At least one Product Group Category must have the Billing Indicator set. This ensures that at least
one Category, it’s Product Groups and Products are used for rating purposes and appears on the Daily
Summary.
When you set a Product Group Category as mandatory for billing, all Product Groups and Products
must be associated with it.
You can create other optional Product Group Categories and use them to categorise Product Groups
and Products for reporting purposes.
3.6.1 Product Group Categories
Product Group Categories are created for high level grouping of Product Groups. Examples include
Billing Category, Non-Billing, and so on.
Typically only the default Product Group Category is required.

ory
ID 3 Y Short name for the Product Group Categories
Name 30 Y Name of the Product Group Categories
Table 3.6-14 Product Group Categories Fields
ID Name
BIL Billing
Note: This data needs to be configured manually in the system.
Table 3.6-15 Product Group Categories

Profitability TM’
3.6.2 Product Group
The Product Group refers to the grouping of Products. A Product can be part of any number of
Groups. Examples are, telephony, mobile content, and so on.
Field Length Mandatory Comments
ID 4 Y Short name for product group.

Name 30 Y Name for product group.
Category 3 Y Product Group Category the Product Group belongs to.
Table 3.6-16 Product Group Fields
ID Name Category
under the ‘Product Group’ tab for a complete detail.
Table 3.6-17 Product Group

Profitability TM’
3.6.3 Product
Products offered by the Franchise and Network Operators. It is used to determine the way in which
calls are rated. To allow for greatest flexibility, products are defined under Product Group, which
specifies a catalogue of products.
Field Length Manda Comment

tory
ID 14 Y Short name of product
Name 30 Y Product name
Reverse 1 N Indicates if a product is a reverse product or not.
Charge Value is either:
Y (Yes), it is a reverse product
N (No), it is not a reverse product
Tier 8 N Indicates if product applies to all tiers.
All Tiers are represented by a ‘*’
Event 3 N Indicates for which event direction the product exists.
Direction All Event Direction are represented by a ‘*’
Start Date Date Y Indicates the date from which the product is effective
End Date Date N Indicates the date when the product will be terminated or
come to an end.
Category_1 3 Y The product category into which the product falls, e.g. BIL
(Billing)
Product 4 Y Product Group into which Product falls e.g. DOM, PPH, VDA,
Group_1 VDI, VDP
Table 3.6-18 Product Fields
ID Name Rev Tier Event Start End Cat_1 Prod

Charge Direction Date Date Grp_1
under the ‘Product’ tab for a complete detail.
Table 3.6-19 Product

Profitability TM’
3.6.4 Product Derivation Network
Address
Product Derivation is used to derive the Product if it is not supplied on the EDR. Product will be
determined independently on Incoming and Outgoing portions of the call. When the application needs
to derive a Product, the Product must have a unique number, in other words the A or B Number.

tory
ID 20 Y Network address
Table 3.6-7 Product Derivation Network Address Field
ID
Note: Please refer to : 04a - Product Derivation Data (Domestic - Interconnect).xml and 04b -
Product Derivation Data (Domestic-VOIP & Payphone).xml under the ‘Product Derivation Network
Addr’ tab for a complete details.
Table 3.6-8 Product Derivation Network Address
3.6.5 Network Address Group
Network Address Group is used to group the product derivation network address.

tory
ID 8 Y Network Address group short name.
Name 30 Y Network address group name.
Table 3.6-9 Network Address Group Fields
ID Name
Product Derivation Data (Domestic-VOIP & Payphone).xml under the ‘Network Addr Group’ tab for
a complete details.
Table 3.6-10 Network Address Group

Profitability TM’
3.6.6 Network Address Group
Membership
Associate the Product derivation Network address to a Network address group.

tory
Product 20 Y Network Address
Derivation
Network
Address
Network 8 Y Short name of Network Address Group.
Address
Group
Network 6 Y Short name of network operator.
Operator
Start Date Date Y Indicates the date from which the network address group
membership is effective
End Date Date N Indicates the date when the network address group
membership will be terminated or come to an end.
Table 3.6-11 Network Address Group Membership Fields
Product Derivation Network Address Group Network Operator Start Date End Date
Network Address
Product Derivation Data (Domestic-VOIP & Payphone).xml under the ‘Network Addr Group
Membership’ tab for a complete details.
Table 3.6-12 Network Address Group Membership

Profitability TM’
3.6.7 Product Derivation
Set up the parameters use to derive a product.

tory
Franchise 6 Y The Franchise ID
Event 3 Y Indicates the base direction of the call. These options are
Direction available, i.e. :
I – Incoming, only incoming values on CDR is populated
O – Outgoing, only outgoing values on CDR is populated
T – Transit, both incoming and outgoing values are specified
on CDR
Direction Ind 1 Y The direction where the product id should be derived.
Example: Incoming leg or the outgoing for a transit
scenario.
User Data 20 Y Predefined data that will be send to ICT by IME. For eg:
PPRC, VIRC, VARC, VOIP and etc.
Network 6 Y The network operator ID
Operator
Path 20 Y The path or trunk ID
B-Num Group 8 Y B number network address group
A-Num Group 8 Y A number network address group
B-Num Prefix 20 Y B number product derivation network address ID
A-Num Prefix 20 Y A number product derivation network address ID
Start Date Date Y Indicates the date from which the product derivation is
effective
End Date Date N Indicates the date when the product derivation will be
terminated or come to an end.
Product 14 Y The product ID
Table 3.6-13 Product Derivation Fields
Fran Event Directio User Netw Path B- A- B- A- St End Produ

chis Directio n Ind Data ork Num Num Num Num art Date ct
e n Oper Grou Group Prefi Prefi Da
ator p x x te
Product Derivation Data (Domestic-VOIP & Payphone).xml under the ‘Product Derivation’ tab for a
complete details.
Table 3.6-14 Product Derivation

Profitability TM’
3.7 RATING
3.7.1 Rating Scenarios
Rating Scenario is used to create Scenarios that best suit the user’s business.

tory
ID 8 Y Short name of rating scenario.
Specific to TM:
For example,
ICISDC = Inc Std Distance Calls
ICOEA = Out Equal Access
ACTVACF = Transit VOIP Access fr Fix
TCTVTERM = Transit VOIP for IP/PSTN Term
OCIVOTC = Inc VOIP One Time Charge
The first 2 characters represent the charges type:

1. IC = Interconnect Charges
2. AC = Access Charges
3. TC = Termination Charges
4. OC = One time Charges
The 3rd character represent the Direction:

1. I = Incoming
2. O = Outgoing
3. T = Transit
The remaining characters represent the initial of the rating

scenario name.
Name 30 Y Name of rating scenario

Base 1 Y Indicates the base direction of the call. There options are
Direction available, i.e. :
I – Incoming,
O – Outgoing
T – Transit,
Event 3 Y Event Scenario will be required for each different type of
Scenario CDR to be rated. Example : TEL (Telephony)
Table 3.7-20 Rating Scenarios Fields

Profitability TM’
ID Name Base Direction Event Scenario
Note: Please refer to : 05a - Rating Data (Domestic - Interconnect).xml and 05b - Rating Data
(Domestic-VOIP & Payphone).xml under the ‘Rating Scenario’ tab for a complete details.
Table 3.7-21 Rating Scenarios

Profitability TM’
3.7.2 Rating Scenario Determination
Rating Scenario Determination is used to define the parameters to be used to rate a CDR. Examples
of parameters are Event Direction, Product and so on. The values specified on this table will be used
by rating to derive the Rating Scenario.

Franchise 6 Y Indicates the franchise
Refers to Organization ID where the Organization Type is
‘FRN’
Event Direction 3 Y Indicates the base direction of the call. There options are
available, i.e. :
I – Incoming, only incoming values on CDR is populated
O – Outgoing, only outgoing values on CDR is populated
T – Transit, both incoming and outgoing values are
specified on CDR
Incoming 14 Y Represent the Product ID for Incoming calls or the
Product Incoming leg of Transit calls
Incoming NOP 6 Y Select operator of the Incoming Path or Trunk
Outgoing 14 Y Represent the Product ID for Outgoing calls or the
Product Outgoing leg of Transit calls
Outgoing NOP 6 Y Select operator of the Outgoing Path or Trunk
NAA A Number 8 Y Indicate the A Number Name of point of origination, for
example Country or City.
NAA B Number 8 Y Indicate the B Number Name of point of termination, for
example Country or City.
Day of Week Day Y Indicate day of week
Incoming Path 20 Y Indicate path of the associated Incoming Product
Incoming Net 20 Y Indicate the incoming network node (switch)
Node
Outgoing Path 20 Y Indicate path of the associated Outgoing Product
Outgoing Net 20 Y Indicate the outgoing network node (switch)
Node
Start Date Date Y Indicates the start date from which the rating is effective
End Date Date N Indicates the dates when the rating will expire.
Start Time Time Y Indicates the start time from which the rating is effective
End Time Time Y Indicates the time when the rating will expire.
Rating Scenario 10 Y When selecting the parameters for the Rating Scenario,
both NAA A number and NAA B number are mandatory
whether the Event Direction is Incoming or Outgoing

Profitability TM’
Table 3.7-22 Rating Scenario Determination Fields
Fr Ev IC IC OG OG NAA NA Day IC IC OG OG Sta En Sta En Rat

n en Pro NO Prod NO A A Of Pat Net Pat Net rt d rt d .
t d P P Num B Wee h No h Nod Dat Dat Ti Ti Sce
Di Nu k de e me me
r m
Note: Please refer to : 05a - Rating Data (Domestic - Interconnect).xml and 05b - Rating Data (Domestic-
VOIP & Payphone).xml under the ‘Rating Scenario Determination’ tab for a complete details.
Table 3.7-23 Rating Scenario Determinations

Profitability TM’
3.7.3 Component Parameter
Category
Component Parameter Category is use to categorise the rating component.

tory
ID 8 Y Indicates the short name of a component parameter
category. E.g.: REVSHARE, etc.
Name 30 Y Indicates the descriptive name the ID e.g. Revenue Share,
etc.
Rating Param 1 Y Indicates the type of the parameter. E.g.: D for Discrete,
Type etc.
Table 3.7-5 Component Parameter Category fields
ID Name Base Direction
REVSHARE Revenue Share V

Table 3.7-6 Component Parameter Category
3.7.4 Rating Components
Products can be broken down into charging components, known as rating components. Examples of
rating components are Standard Connection Fee, Access Charge. These are set up independently of
network operators as many will offer the same products and components to their customers.

tory
ID 8 Y Indicates the short name of a charge, e.g. INTTRAN, etc.
Name 30 Y Indicates the descriptive name of a charge, e.g. Usage
Charge, etc.
Time or Data 1 Y Indicates whether rating is based on duration (Time) or
data.
LCFA 1 Y LCFA (Long call / Short call) indicator.
Value is either:
Y (Yes)
N (No)

Profitability TM’
tory
TM Specific:
Always set to N.
Rate 1 N Indicates if the call is rated to the exact duration (Precision)
Derivation or rounded up (Unit) duration
Logic Value is either:
P (Precision billing)
U (Unit billing)
Rating 1 Y The rating component type indicates whether the rate will
Component be looked up directly or whether the rate look-up is
Type dependent on the rate parameters and rate matrix.
Value is either:
S (Standard)
E (Enhanced) – for content rating
R (Revenue Share)
Note:
Default value is ‘S’
Revenue 8 N Component Parameter Category.
Share 1
Category ID
Revenue 8 N The currency of the revenue share.
Share 1
Currency ID
Rating 1 N The parameter is which the quantity (i.e. duration, unit) will
Quantity be used to do rating.
Table 3.7-7 Rating Component Fields
ID Name Time LCF Rate Ratin Revenue Revenue Rating Quantity

Or A Deriv g Share 1 Share 1
Data Logic comp Category Currency
Type ID ID
Note: Please refer to : 05a - Rating Data (Domestic - Interconnect).xml and 05b - Rating Data
(Domestic-VOIP & Payphone).xml under the ‘Rating Component’ tab for a complete details.
Table 3.7-8 Rating Components
3.7.5 Rating Rules

Rating Rules is used to define rating criteria, namely:-
the ‘what’ (Rating Scenario and Rating Component), the ‘who’ (Billing Operator Type) and the ‘how’
(Tier Derivation Style and Time Apportionment Rule, Digits to Ignore, and so on).

Profitability TM’
Field Length Mand Comment
atory
Refers to Organization ID where the Organization Type is ‘FRN’
Rating 10 Y Indicate the type of the rating scenario
Scenario
Rating 8 Y Indicates the business name for a charge e.g. TERM,ORIG, etc
Component
Component 2 Y Indicates the component direction of the call. There options
Direction are available, i.e. :
I – Incoming,
O – Outgoing
T – Transit,
Billing 1 Y Indicates how the Billing Operator will be derived.
Operator
Type
Specified 6 N Indicates if rating rule applies to all operators.
Operator All operators are represented by a ‘*’
Inbound 6 Y If Event direction is set to Incoming or Transit then an
Network Operator Id will need to be supplied here. This Id can be
Operator ID generic (*).
Outgoing 6 Y If Event direction is set to Outgoing or Transit then an
Network Operator Id will need to be supplied here. This Id can be
Operator ID generic (*).
NAA A 8 Y Network Address Aggregation for A Number
Number
NAA B 8 Y Network Address Aggregation for B Number
Number
Cash Flow 1 Y Gives the cash flow for the element in respect to the
Franchise. Values include:
Expense (money payable by the Franchise)
Revenue (money due to the Franchise)
Statement 1 Y Indicates who will receive the statement from the Franchise
Direction perspective. The franchise will:
Send a Statement
Receive a Statement
Billing 1 Y The Billing Method is used on the Rating Rules to indicate the
Method Billing Period on which a charge should appear. For example :
I – Invoice
D - Declaration
Tier 4 Y Determine how the Tier will be derived, in other words, copy
Derivation values from static reference data.
Style Example:
[B] – Derive Tier based on B Number
[PB] – Derive Tier based on POI and B number
[EBC B] – Derive Tier based on B number and POI targeting

Profitability TM’
the membership first
[AB] - Derived from originating number (A# CNP) and
terminating number (B# CNP)
[N] – User defined tier
Tier 8 N Tier ID
B Number 2 Y Indicates the first X digits that should be ignored.
Digits to
ignore
A Number 2 Y Indicates the first X digits that should be ignored.
Digits to
ignore
Time 1 Y Indicate if the call should be completely rated in the time
Apportionme premium in which it started or if it should be apportioned
nt Rule across time premiums
Start Date Date Y Indicates the date from which the rating rule is effective.
End Date Date Y Indicates the date when the rating rule will be terminated or
come to an end.
Time 4 Y Indicates if the number of hours that should be added to or

Variance subtracted from the CDR start-time to accommodate summer
time
Note:
Will only be used for indirect routes where the accounting
method is ‘Direct’
Table 3.7-9 Rating Rules Fields
Fra Rat Rat Co Bil Sp Inb Out NA NA Cas Sta Tie Bn An Ti Sta En Tim
n Sce Co mp Op ec NO g A A h t r um um me rt d e
mp Dir er Op P NO A B Flo Dir Der Dig Dig Ap Dat Dat Var
Ty era ID P Nu Nu w iv it it por e ian
pe tor ID m m Sty ign ign Rul ce
r r e
Note: Please refer to : 05a - Rating Data (Domestic - Interconnect).xml and 05b - Rating Data (Domestic-VOIP &
Payphone).xml under the ‘Rating Rules’ tab for a complete details.
Table 3.7-10 Rating Rules

Profitability TM’
4 NETWORK DATA
4.1 CIRCUIT SWITCHED
4.1.1 Network Node / Switch
A switch is a piece of hardware which interconnects with another operator's network via a trunk
group and which creates Call Detail Records (CDRs) of calls made by customers. Both franchises and
network operators have switches in their systems.
A franchise may have many switches, each of which is connected to many different network operator
switches, each via a different trunk group.
Although both franchises and network operators have switches in their system Interconnect is only
concerned with the franchise’s switches where the call is passed to (or received from) the network
operator. Switches belong to a franchise, POIs to network operators.

tory
ID 20 Y Short name of switch
Name 30 Y Name of switch
Franchise 6 Y The Franchise ID the switch belongs to
Table 4.1-24 Switch Fields
ID Name Franchise ID
Note: Please refer to : 02a - Network Data (Domestic - Interconnect).xml and 02b - Network Data
(Domestic-VOIP & Payphone).xml under the ‘Network Node’ tab for a complete details.
Table 4.1-25 Switches
4.1.2 Point Of Interconnect

Profitability TM’
In the context of the Interconnect application the Point Of Interconnect (POI) is a logical point within
the other operators’ network at which a call enters the terminating (or transit) network from the
originating network. It is used to determine the logical start point of a call for charging purposes.
Field Length Mand Comment

atory
ID 8 Y Short name of POI.
Note:
ID consists of the Network operator’s name and location in
short.
Name 50 Y Name of POI
Network 6 Y The NOP ID the POI belongs to
Operator Note:
POI is always specified for a network operator.
A POI will only be specified for a franchise in the case of
inter-franchise billing
Type 3 Y Defines the POI as tandem or exchange.
Value is either:
TAN (Tandem), i.e. call can transit POI
EXC (Exchange), i.e. call terminates in POI
Table 4.1-26 Point of Interconnect Fields
ID Name NOP ID Type
(Domestic-VOIP & Payphone).xml under the ‘POI’ tab for a complete details.
Table 4.1-27 Points of Interconnect

Profitability TM’
4.1.3 Trunk Group
A Trunk Group (sometimes called a circuit group) provides a communication link between switches in
different networks i.e. between an NOP’s POI and an Interconnect owner’s switch.

tory
ID 20 Y Short name of Path or Trunk Group
Name 30 Y Name of Path or Trunk Group
Path Type 3 Y Defines the path as being of type:
Value is either:
ICR (Inter-carrier)
INT (Internal)
OVL (Switch overflow)
Note:
Default value is ICR
Medium Type 3 N Refers to the medium a path uses, for example terrestrial,
undersea cable, digital satellite, analogue cable and so on.
Node 20 Y Short name of switch
1
International N Indicates if the trunk group is an international or domestic
Value is either:
Y (Yes), i.e. international trunk
N (No), i.e. domestic trunk
POI 1 Y Indicates how the POI will be derived.
Determinatio Value is either:
n Method
N (Number), i.e. POI derivation is based on the A or B
number (only used for instances where network operators
share paths or trunks)
P (Path), i.e. POI derivation is based on the trunk group or
path
Shared Ind 1 Y 'Y' - implies that a Path may be associated with more than
one POI at a point in time as the Path is Shared.
When the path is not shared, it may only be associated with
one POI at a time.
Note:
Default value is N
Start Date Date Y Indicates the start date from which the trunk group or path
is effective
End Date Date N Indicates the dates when the trunk group or path will
expire.
POI Operator 6 Y The NOP ID the POI belongs to

Profitability TM’
tory
Point Of 8 Y Short name of POI
Interconnect Note:
_1
A Path Type of Internal and Overflow CANNOT be
associated with a POI.
Table 4.1-28 Trunk Group Fields
ID Name Path Medium Node Interna POI Shared Start End POI POI_
Type Type tional Det. Ind Date Date Oper 1
Method
(Domestic-VOIP & Payphone).xml under the ‘Trunk Group’ tab for a complete details.
Table 4.1-29 Trunk Groups

Profitability TM’
4.1.4 Network Address
A telephone receiver for charging purposes is specified by its Network Address. This is made up of
the area code plus one or more additional digits from the telephone number to uniquely identify a
specific location.

tory
ID 20 Y Network address e.g. 0044, 0061, 0027, etc
Can be at any level, e.g. could be the dial code for a country
or a city, etc.
Location 30 Y Name of network address
Network 3 N Gives a value to the network address, e.g. a network
Address Type address can be defined as mobile or fixed line or by any
other user definable value
Billing Start Date Y Date from Network address is effective
Date_1
Billing End Date N Date when network address will expire
Date_1
Billing 6 Y Defines the billing operators for this network address
Operator_1 Note:
Default value is ‘*’
This does not represent an override value, but rather an
“ALL”
Network 4 N Define whether the network address is a NP (POI based) or
Address NN (Non-POI based)
Determination
Style_1
Table 4.1-30 Network Address Fields
ID Location Network Start Date End Date Billing Network Address

Address Operator Determination Style
Type
Note: Please refer to : 03a - Network Address Data (Domestic - Interconnect).xml and 03b - Network Address
Data (Domestic-VOIP & Payphone).xml under the ‘Network Address’ tab for a complete details.
Table 4.1-31 Network Address Prefix

Profitability TM’
4.1.5 Network Address Owner
Indicates List of network addresses and its Network Operator.

tory
Network 20 Y Refers to Network address or CNP ID in Network Address.
address
Start Date Date Y Date from Network address aggregation is effective
End Date Date N Date when network address aggregation will expire
Network 6 Y ID of network operator
Operator
Table 4.1-9 Network Address Owner Fields
Network Address Start Date End Date Network Operator
Note: Please refer to : 03a - Network Address Data (Domestic - Interconnect).xml and 03b -
Network Address Data (Domestic-VOIP & Payphone).xml under the ‘Network Address Owner’ tab for
a complete details.
Table 4.1-10 Network Address Owner
4.1.6 Network Address Aggregation
Network Address Aggregation is used to define a grouping of network addresses that can be used for
deriving specific rating scenarios. based on geographical location.

tory
ID 8 Y Short name of network address aggregation.
Name 30 Y Name of network address aggregation

Country 1 Y Defines whether the network address aggregation indicates a
Indicator country or not. In this case it will be a ‘N’.
Table 4.1-11 Network Address Aggregation Fields

Profitability TM’
ID Name Country Level
Note: Please refer to : 03a - Network Address Data (Domestic - Interconnect).xml and 03b - Network
Address Data (Domestic-VOIP & Payphone).xml under the ‘NAA’ tab for a complete details.
Table 4.1-12 Network Address Aggregations
4.1.7 Aggregation Hierarchy Level
Aggregation Hierarchy Level is used to define the various levels of the network address aggregation
hierarchy. The maximum level of aggregation is 6 levels.
Note:
The number of levels is determined by the nature of the business.

tory
Start Date Date Y Date from which network address aggregation hierarchy is
effective
End Date Date Date when the network address aggregation hierarchy will
terminate
Network 8 Y Network address aggregation id.
Address
Aggregation_
0
Network 8 N Network address aggregation id. This is at a level lower
Address than level 0 above.
Aggregation_
1
Network 8 N Network address aggregation id. This is at a level lower
Address than level 1 above
Aggregation_
2
Table 1-13 Aggregation Hierarchy Level Fields
Start Date End Date NAA_0 NAA_1 NAA_2
Note: Please refer to : 03a - Network Address Data (Domestic - Interconnect).xml and 03b -
Network Address Data (Domestic-VOIP & Payphone).xml under the ‘NAA Hierarchy’ tab for a
complete details.
Table 4.1-14 Aggregation Hierarchy Levels

Profitability TM’
4.1.8 Network Address Aggregation
Membership
Indicates into which network address aggregation the network address is grouped.

Network 20 Y Refers to Network address or CNP ID in Network
address Address.
Start Date Date N Date from Network address aggregation is effective
End Date Date N Date when network address aggregation will expire
Network 8 Y Refers to Network address aggregation id in NAA.
Address Can be defined at country level or city level or any other
Aggregation level lower than country.
Table 4.1-15 NAA Membership Fields
ID Start Date End Date NAA
Note: Please refer to : 03a - Network Address Data (Domestic - Interconnect).xml and 03b - Network
Address Data (Domestic-VOIP & Payphone).xml under the ‘NAA Membership’ tab for a complete
details.
Table 4.1-326 NAA Membership

Profitability TM’
5 BILLING DATA
5.1 TIERS
5.1.1 Tier Maintenance
A Tier is a logical Rating concept. It indicates where a call originates and terminates and is used as a
key component of the Rate. In other words, whenever Rates need to be varied, a different Tier may
be used. Tiers are derived using the Tier Derivation Styles on the Rating Rules panel. Tiers are set up
in a Hierarchical Structure using three levels, Tier Type, Tier Group and Tier.
5.1.1.1 Tier

tory
ID 8 Y Short name for the tier e.g. VOIP, RECCHG, PAYPHONE, etc.
Name 30 Y Name of the tier.

Hierarchy 1 Y 1 – Tier Type
Level 2 – Tier Group
3 – Tier
Table 5.1-33 Tier Fields
ID Name Hierarchy Level

VOIP VOIP 1
RECCHG Recurring Charge 2
VOTC VoIP One Time Charge 3
Note: Please refer to : 06a - Tier Data (Domestic - Interconnect).xml and 06b - Tier Data (Domestic-
VOIP & Payphone).xml under the ‘Tier’ tab for a complete details.
Table 5.1-34 Tiers
5.1.1.2 Tier Hierarchy

tory
Start Date Date Y Indicates the date from which the date is effective
End Date Date N Indicates the date from which the date will be terminated or
come to the end
Tier_1 8 Y Tier Type.
Tier_2 8 Y Tier Group

Note:

Profitability TM’
Tier_3 8 Y Tier ID. This is the lowest level referred to by other
templates. Refer to tier for the convention.
Note:
Table 5.1-35 Tier Hierarchy Fields
Start Date End Date Tier 1 Tier 2 Tier 3
1/1/2009 VOIP RECCHG

1/1/2009 VOIP RECCHG PAYPHONE
Note: Please refer to : 06a - Tier Data (Domestic - Interconnect).xml and 06b - Tier Data (Domestic-
VOIP & Payphone).xml under the ‘Tier Hierarchy’ tab for a complete details.
Table 5.1-36 Tier Hierarchy

Profitability TM’
5.1.2 Tier Derivation Style
The Tier Derivation is used to set up the required reference data in order to determine the Tier to be
derived when rating. There are six Tier Derivation Styles, each of which derives a Tier based on
different properties. The Tier can be derived using only the Network Address (CNP), the Point of
Interconnect and Network Address (CNP), the Network Address Aggregation and also the style
specified on the Network Address (CNP) itself.
5.1.2.1 TDST Non-distance

Tier derivation based on B or A Number Network Address. Specific to TM, this applies to Telegram,
One Number Service (ONS), SMS, Freephone, Special Services and VOIP Access.

Network 20 Y Network address or CNP, e.g. 0099650, 00996543, etc. Can
Address be at any level, e.g. could be the dial code for a country or a
city, etc.
Note:
This tier derivation style covers all network addresses except
for International numbers and PSTN numbers.
Billing 6 Y Defines the billing operator for this network address
Operator
Start Date Date Y Indicates the date from which the call is effective
End Date Date N Indicates the date from which the call will be terminated or
come to the end
Tier 8 Y Indicate the tier associated with Tier Derivation Style. Only
refers to Tier of the lowest level i.e. level 3.
Table 5.1-37 TDST Non-Distance Field
Network Billing Start Date End Date Tier

Add Operator
Note: Please refer to : 06a - Tier Data (Domestic - Interconnect).xml under the ‘TDST Non Distance
(B#)’ tab for a complete details.
Table 5.1-38 TDST Non-Distance

Profitability TM’
5.1.2.2 TDST Distance
Tier derivation based on Point of Interconnect and B Number Network Address. Specific to TM, this
applies to Mobile, IP Tele, Incoming Fixed and Incoming Equal Access.

Operator
Network 20 Y Network address or CNP, e.g. 0099650, 00996543, etc.
Address Can be at any level, e.g. could be the dial code for a
country or a city, etc.
Point of 8 Y Indicates the Point of Interconnect
Interconnect
POI Operator 6 Y Indicates to which operator the POI belongs to
End Date Date N Indicates the date from which the date will be terminated
or come to the end
Tier 8 Y Indicate the tier associated with Tier Derivation Style.
Only refers to Tier of the lowest level i.e. level 3.
Table 5.1-39 TDST Distance Field
Billing Network POI POI Start Date End Date Tier

Operator Address Operator
Note: Please refer to : 06a - Tier Data (Domestic - Interconnect).xml under the ‘TDST Distance
(POI-B#)’ tab for a complete details.
Table 5.1-40 TDST Distance
5.1.2.3 TDST Retail Aggregation (Ag A# Ag B#)
Tier derivation based on Network address aggregation A# and network address aggregation B#.
Specific to TM, this applies to Outgoing Equal Access.
NAA A 8 Y Network address aggregation A#
Number
NAA B 8 Y Network address aggregation B#
Number
Billing 6 Y Defines the billing operator for this NAA
Operator

Profitability TM’
or come to the end
Table 5.1-9 TDST Retail Aggr Field
NAA A NAA B Billing Start Date End Date Tier

Number Number Operator
Note: Please refer to : 06b - Tier Data (Domestic-VOIP & Payphone).xml under the ‘TDST Retail
Aggr (Ag A# Ag B#)’ tab for a complete details.
Table 5.1-10 TDST Retail Aggr
5.1.2.4 Cash Flow B number
Derive Tier for a given Network Address based on whether the call is an Expense to the Franchise or
Revenue for the Franchise. Specific to TM, this applies to VOIP IP Termination Standard and VOIP IP
Termination Premium.

Refers to Organization ID where the Organization Type is
‘FRN’
Operator
Cash Flow 1 Y R for Revenue and E for Expense.
or come to the end
Network 20 Y Network address or CNP. Can be at any level, e.g. could
Address be the dial code for a country or a city, etc.
Specific to TM:
The format for VOIP is prefixed with 003 and for VOIPP
with 004.
For example, country code for UK is 44, the network
address will be 00344 for VOIP and 00444 will be for
VOIPP.

Profitability TM’
Table 5.1-11 TDST Cash Flow B number Field
Billing Network POI POI Start Date End Date Tier

Operator Address Operator
Note: Please refer to : 06b - Tier Data (Domestic-VOIP & Payphone).xml under the ‘TDST Cash
Flow (B#)’ tab for a complete detail.
Table 5.1-12 TDST Cash Flow B number

Profitability TM’
5.2 CALENDAR
5.2.1 Time Premium
Time Premiums are names given to a segment of a day that is used to determine the rate, for which
Rates vary from a Rating point of view. Examples of these are 'Peak', 'Off Peak' and 'Standard'. These
are used to allow the setup of a Rate per Time Premium. The Rating Calendar and Calendar are used
to determine the Time Premium applicable to a particular CDR during the Rating process.

ory
ID 3 Y Short name of segment of a day.
Name 30 Y Name of segment of the day.
Table 5.2-41 Time Premium Fields
ID Name
ALL All days

Table 5.2-42 Time Premiums

Profitability TM’
5.2.2 Base Calendar
A Calendar is used in rating to determine the Time Premium, for example 'Peak' into which a CDR
falls for rating purposes. Calendar is used to determine the way days are broken into Time Premiums.
Special day is used to determine a special date on a particular month
Field Length Mand Comments

atory
ID 8 Y Short name of Base Calendar.
Name 30 Y Name of Base Calendar
Day - Y Day which the Base Calendar will be use. (from Monday to
Sunday)
Time Premium 3 Y ID for Time premium.
Start Time Time Y Start Time for Time premium.
End Time Time Y End Time for Time premium.
Table 5.2-43 Base Calendar Fields
ID Name Day Time Premium Start Time End Time
Note: Please refer to : 07a - Billing Data (Domestic - Interconnect).xml and 07b - Billing Data
(Domestic - VOIP & Payphone).xml under the ‘Calendar Base’ tab for a complete details.
Table 5.2-44 Base Calendar

Profitability TM’
5.2.3 Rating Calendar
A Rating Calendar gives the user the option to decide which Calendar is to be used when Rating.
Typically only a Franchise is specified and the rest of the values, Billing Network Operator, Tier,
Product and Direction are default ('*') values, which means that any value encountered in Rating will
match on it.

ory
Start Date Date Y Start date of the rating calendar.
End Date Date N End date of the rating calendar.
Franchise 6 Y ID of Franchise.
Network 6 Y ID of network operator
Operator
Tier 8 Y ID of Tier when the rating calendar will be used.
Product 14 Y ID of Product when the rating calendar will be used.
Normally use generic (*).
Component 2 Y Direction of which the rating calendar will be used. Normally
Direction use generic (*).
Calendar 8 Y ID of Base Calendar.
Table 5.2-45 Rating Calendar Fields
Franchise NOP ID Tier Product Comp Start End Calendar

Direction Date Date
TMB * * * * 1/1/2009 All – See
above
comment
s
Note: Please refer to : 07a - Billing Data (Domestic - Interconnect).xml and 07b - Billing Data
(Domestic - VOIP & Payphone).xml under the ‘Rating Calendar’ tab for a complete details.
Table 5.2-46 Rating Calendars

Profitability TM’
5.3 CURRENCY
The Currency is used to create currencies which are used within the system. The only
Currency which is pre-loaded is the Euro. Currency Types, 'OTH' and 'NCU' are derived.
It is recommended that ISO 4217 currency codes are used.
Field Length Mand Comments

atory
ID 3 Y Short name of currency.
Name 30 Y Descriptive name of currency.
Symbol Unit 5 Y The symbol of the currency, e.g. $
Fraction Name 30 Y The name of the fraction part of the currency, e.g. cents
Fraction 5 Y The symbol used for the fraction part of the currency, e.g. ‘c’
Symbol for cents
Fraction Ratio 8 Y The number of fraction units in the main unit, e.g. 100 cents
in $1
Type 3 Y National Currency Unit (NCU) or Other Currency (OTH).
Table 5.3-47 Currency Fields
ID Name Symbol Unit Fraction Fraction Fraction Ratio Type

Name Symbol
Ringgit
MYR Malaysia RM Cents c 100 OTH
Note: Please refer to : 07a - Billing Data (Domestic-Interconnect).xml and 07b - Billing Data
(Domestic-VOIP & Payphone).xml under the ‘Currency’ tab for a complete detail.
Table 5.3-48 Currency

Profitability TM’
5.4 RATES
Rates are Franchise and Network Operator specific and for this reason users have to select a
Franchise and Network Operator before filtering. The Billing Network Operator can either be specified
as a specific Billing Network Operator or a Common Rate Book, which is where a Rate applies to all
Network Operators.

Refers to Organization ID where the Organization
Type is ‘FRN’
Network 6 Y The NOP ID the Rate belongs to
Operator
Rating 8 Y Indicates the business name for a charge e.g.
Component STD, TRANS, TERM etc
Product 14 Y Indicate the associated product
Component 2 Y Indicates the direction of a call component. It has
Direction a pre-loaded values of:
I - Incoming
O – Outgoing
TI - Incoming Transit
TO - Outgoing Transit
Tier 8 Y Indicates where a call originates and terminates
Time 3 Y Name given to a segment of a day that is used to
Premium determine the rate, such as Peak, Off-peak,
Economy and so on
Start Date Date Y Indicates the date from which the rate is effective.
End Date Date N Indicates the date when the rate will expire.
Rate Unit 7 Y Indicates the unit of measure the rate is
negotiated for, e.g. minute, kilo segment, word,
etc.
Call Attempt 15,6 N Indicates the rate that should be applied to call
Charge attempts. Applicable to CDRs which is regarded
as having zero duration.
E.g. User can define calls with duration less than
20 seconds as a call attempt. A fixed fee called
the call attempt charge can be applied to these
calls.
Note:
Call attempt rule is specified in agreement
parameters.
Additional 6 N Indicates the surcharge that should be applied to
Charge the call count and not the duration of the call
Profitability TM’
Minimum 10,0 N Indicates the minimum duration that should be
Usage applied to a call, i.e. if the CDR duration is less
than the minimum duration specified, the
minimum duration will be the overriding factor
Maximum 10,0 N Indicates the maximum duration that should be
Usage applied to a call, i.e. if the CDR duration is greater
than the maximum duration specified, the
maximum duration will be the overriding factor
Setup Unit 3,0 Y Indicates the number of units applicable to pulse
Count calls.
Minimum 15,6 N Indicates the minimum amount that should be
Charge applied to a call, i.e. if the amount of a rated CDR
is less than the minimum value specified, the
minimum value will be the overriding factor.
Maximum 15,6 N Indicates the maximum amount that should be
Charge applied to a call, i.e. if the amount of a rated CDR
is greater than the maximum value specified, the
maximum value will be the overriding factor
Currency 3 Y Indicates the rate currency
Free Usage 10,0 Y Indicates the duration (in base unit) that is
regarded as being free of charge.
Rounding 8 N Will only be used for instances where the Rate
Unit Unit and Duration Unit differ, e.g. every 6 seconds
= 1 unit, but the rate is negotiated as a rate per
minute and not as a rate per unit.
If left blank, the system assumes it to have the
same value as Rate Unit
Stepped Rate 1 Y Indicates the type of rate step.
Type Value is either:
N – No Step
S – Slabbed Stepping
T – Threshold Stepping
Step Usage_1 10 N Indicates the duration of each rate step.
Will be used for precision billing.
Step Unit_1 10 N Indicates the number of units the rate step is
applicable for.
Will only be populated for unit billing
Unit Cost_1 6 Y Indicates the rate that should be applied to the
call.
If rate step type is N (No steps), then this field
will represent the rate applied to the call
If the rate step type is not N (No steps), then this
field represents the rate that should be applied to
the first step of the call
Will be populated for precision or unit billing.

Profitability TM’
Flat 6 N Identifies the flat/fix amount that should be
Charge_1 applied to a particular step.
Table 5.4-49 Rate Fields
FR NO Rat PR Co Tie Ti Sta E Rat Call A Min M Set C Min M F Rd S S U Fl

N P Co D mp r me Dat n Uni Att d Us a up u Ch a r g t t n a
ID ID mp ID Dir pre d t chg d g x Uni r g x e Uni e e it t
m D C U t C e t p p C C
a h s Cnt h U U U o h
t g g g s s n s g
g g it t _
_ _ _ 1
1 1 1
Note: Please refer to : 07a - Billing Data (Domestic-Interconnect).xml and 07b - Billing Data (Domestic-VOIP &
Payphone).xml under the ‘Rate’ tab for a complete detail.
Table 5.4-50 Rate

Profitability TM’
5.5 BILLING PERIOD
Billing Periods allow user to define at a granular level how and when the system summarises CDR
records and then calculates bills over a set period. The Billing Period defines the settlement cycle.

ory
Name 30 N Prefix of the frequency of the billing period followed by the
Start and End date of the billing period.
Example of the value of the Start Date and End Date of the
billing dates for different frequency:
Monthly billing:
2009/01/01 - 2009/01/31
Weekly billing:
2009/02/01 - 2009/02/07
2009/02/08 - 2009/02/14
2009/02/15 - 2009/02/21
2009/02/22 - 2009/02/28
Quarterly billing:
2009/01/01 - 2009/03/31
2009/04/01 - 2009/06/30
2009/07/01 - 2009/09/30
2009/10/01 - 2009/12/31
Network 6 Y The NOP ID the billing period belongs to

Operator
Franchise 6 Y ID Franchise.
Billing method 1 Y Use ‘D’ for declaration and ‘I’ for invoice.
Statement 1 Y Direction of statement. ‘R’ for receives statement and ‘S’ for
Direction sends statement. Use generic (*) for both.
Product Group 4 Y Product Group into which Billing Period falls e.g. TELE
(Telephony), DATA (Data), CONT (Content)
Start date Date Y Indicates the date from which the billing period is effective.
End date Date Y Indicates the date when the billing period will expire.
Schedule 3 Y Number of days to extract period end report after end date.
Extract Date
Schedule Close 3 Y Number of days to close period end after end date.
Date
Table 5.5-51 Billing Period Fields
Name NOP Franchise Billing Statement Product Start End Relative Relative

Profitability TM’
ID ID Method Direction Group Date Date Sche Sche
Extract Close
Note: Please refer to : 07a - Billing Data (Domestic-Interconnect).xml and 07b - Billing Data
(Domestic-VOIP & Payphone).xml under the ‘Billing Period’ tab for complete details.
Table 5.5-2 Billing Period Fields

Profitability TM’
6 REFERENCE DATA DOCUMENT SIGN OFF
Document Title: TELEKOM MALAYSIA Reference Data Model For Domestic v0.2.doc
In witness hereof, the undersigned, an authorized representative of TELEKOM MALAYSIA, has read
and understood this document;
Signature:
Name:
Title:
Date:
In witness hereof, the undersigned, an authorized representative of INTEC, has read and
understood this document;
Intec Signature:
Name:
Title:
Date:

Profitability TM’
7 APPENDIX A
This zipped file contains all the reference data files for all of the following below:
 01a - Agreement Data (Domestic - Interconnect).xml
 01b - Agreement Data (Domestic-VOIP & Payphone).xml
 02a - Network Data (Domestic - Interconnect).xml
 02b - Network Data (Domestic-VOIP & Payphone).xml
 03a - Network Address Data (Domestic - Interconnect).xml
 03b - Network Address Data (Domestic-VOIP & Payphone).xml
 04a - Product Derivation Data (Domestic - Interconnect).xml
 04b - Product Derivation Data (Domestic-VOIP & Payphone).xml
 05a - Rating Data (Domestic - Interconnect).xml
 05b - Rating Data (Domestic-VOIP & Payphone).xml
 06a - Tier Data (Domestic - Interconnect).xml
 06b - Tier Data (Domestic - VOIP & Payphone).xml
 07a - Billing Data (Domestic - Interconnect).xml
 07b - Billing Data (Domestic - VOIP & Payphone).xml

Profitability TM’

TM - Reference Data Model For Domestic V0.2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TM - Reference Data Model For Domestic V0.2

Uploaded by

Copyright:

Available Formats

TELEKOM MALAYSIA

Reference Data Document v0.2

Customer Confidential Page 1 of 55 July 1, 2021

Release and Approval

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

Table 1.2-1 Data Sources

The list of source filename used is as below;

MAXIS BROADBAND SDN. BHD.

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

1.4 START DATES

1.5 BULK LOADER

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

3.1 ORGANIZATION GROUP

Field Length Mandat Comments

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

Field Length Mandator Comment

Specific for TM:

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

An Agreement is defined between a Franchise and a Network Operator. An Agreement is required to

Field Length Mandatory Comment

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

All products or only specific products may be associated with an Agreement

Field Length Mandatory Comment

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

3.4.1 Job Designation

Table 3.4-10 Job Designation Fields

Table 3.4-11 Job Designation

3.4.2 Contact Category

Table 3.4-3 Contact Category Fields

3.4.3 Contact Details

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

Field Length Mandatory Comment

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

3.5.1 Operation Category

Field Length Mandatory Comment

EW30WMSA6T 50151 REDTONE TELECOMM.

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

3.6.1 Product Group Categories

Field Length Mandat Comments

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

Field Length Mandatory Comments

ID 4 Y Short name for product group.

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

Field Length Manda Comment

ID Name Rev Tier Event Start End Cat_1 Prod

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

Field Length Manda Comment

3.6.5 Network Address Group

Field Length Manda Comment

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

Associate the Product derivation Network address to a Network address group.

Field Length Manda Comment

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

Field Length Manda Comment

Fran Event Directio User Netw Path B- A- B- A- St End Produ

530144068.doc1 ‘One-stop Network ©2008 Intec Telecom Systems PLC

3.7.1 Rating Scenarios

Field Length Manda Comment

The first 2 characters represent the charges type:

The 3rd character represent the Direction:

The remaining characters represent the initial of the rating