3gpp Cdrs Specs Alcatel

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

3BL76381ACAADSZZAEdition 14 Released 1/51

COVER SHEET

MOBILE COMMUNICATION GROUP

Title 5060 WCS charging 3GPP format W5.x

Classification Alcatel-Lucent 5060 Wireless Call Server (WCS)
GSM/MTS CS CORE NETWORK
SYSTEM DOCUMENTATION
TECHNICAL REQUIREMENT SPECIFICATION

Edition
15

Date 20111226
Change Note

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Originator(s) Xia Jing

Approval(s)

ABSTRACT This document describes the 3GPP Billing Format of the Charging
Data Records (CDRs) performed by the 5060 Wireless Call
Server/WCS Release W5.x

DATE REVISION AUTHOR COMMENTS
3
th
July 2009 1.0 Xia Jing First draft base on TRS 3GPP CDR R4.x.
1) Add new trunk type for RDS10893a AoIP
2) Replace CUG outgoing access used by
CUG outgoing access suppressed
(RDS9804b) and implement RDS9804b for
MOC, MOC FW, MTC, MTC FW CDR
3) Update ASN.1 part for CUG (RDS9804b)
4) Add w4.49 and R5.0 RDS in appendix B.
5) Update Diagnostics in chapter 5.2.18 and
ASN.1 to emphasize only support
manufacturerSpecificCause.
6) Add one note in chapter 5.2.44 for
location/changeoflocation field
7) Update CDR sample analyze result about
Diagnostics fields.
8) Update RDS9804b in 5.1.4 (MTC), 5.1.5
(MTC-CF)
9) Update IP connection fields description in
chapter 5.1.1 and 5.1.3.
10) Update the GUI picture in chapter 6.1.1. Add
transit record option in chapter 6.1.
11) Add description about The called number in
outgoing GW record in chapter 5.2.6.
12) Move chapter 5.1.29 to appendix B and
update for RDS9804b.
13) Update appendix C CDR CONTENTS
EVOLUTION
14) Add one note for RDS7502b, because this
function is redesigned in R4.40 and billing is
not impacted.
15) Add one note in chapter 5.2.82 to mention
the extended SS code can be adjusted in GUI
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


for each customer.
16) Add synchronousGeneralData in
BasicServiceCode-struct in ASN.1 part
17) Add ISDN-BC-struct in ASN.1 part
18) Add note for RDS8242 about 5.2.68.32
MSC incoming/outgoing trunk group
extension in chapter 5.2.68.32
19) Remove RDS list in reference documents part.
Its replaced by appendix C. (CDR contents
evolution)
20) 32 Add comment for Cellid in chapter
5.2.44.

14
th
Sep 2009 2.0 Xia Jing 1) Update the document number in page bottom
and chapter 1 (in red color).
2) Add the ASN.1 definition for compile and
CDR sample in dedicated file in internal
reference document.
3) Update for RDS6029 Support of SIP with
Encapsulated ISUP (SIP-I), add SIP-I in
TrunkGroupType of TrunkGroupExtension.
(reference RDS13820 solution)
4) Update appendix B for RDS9804b.
5) Replace 10893a by RDS13186 for AoIP.
6) Update for RDS12458 Disable SMSMT CDR
in case of delivery notification to calling party
7) Update for RDS14086 Release Link Trunk -
Reorigination based on Redirection Number
8) Add chapter 6.4 summary on CDR difference
between R5.x and R4.x
9) Add appendix B for CDR field flag description
10) Add one note for 5.2.68.32 MSC
incoming/outgoing trunk group extension to
clarify trunkCircuit CDR filed does not apply
to VOIP case and may contain internal index.
11) Add one note for Diagnostics field.(RDS5617
Phase 1 enhanced Multi-Level Precedence &
Pre-emption (eMLPP))
2
nd
Nov 2009 3.0 Xia Jing Add one note for RDS14086 Release Link Trunk -
Reorigination based on Redirection Number
5
th
Feb 2010 4.0 Xia Jing Attach to W5.1.
Update for RDS14064 Capture OSSS Codes in
3GPP CDRs
Add Roaming, HLRINT CDR in appendix B
Update 5.2.74 Served IMEI
Add H31 SS code value for RDS14282
Update for RDS14844 Support tkgpName in
TrunkGroup for 3GPP CDR
Update point 6 in chaper 6.4

4
th
Mar 2010 5.0 Xia Jing Update for RDS14064 in chapter 5.2.83

26
th
April 2010 6.0 Xia Jing Update for RDS8242 Iu-cs over IP (WCS) and
RDS4419b IP Trunk Groups on several MGWs
Add a note for trunk group number. remove
IndicatorPresentationIndictor from translated
number CDR field.
Updte for RDS10893a AoIP (WCS) - Full IP
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


architecture
Remove OSSS code from MOC EMY in chapter
5.1.2, 5.2.83 and appendix D.
Correct the GEDI fiel id in foot page.
1
st
July 2010 7.0 Xia Jing add RDS14064 for R449 sp9 in appendix D.2
remove SMS result code
Insert a new appendix for CDR changes for
CU/TMV MNP solution.
Update Full SmsTpDestinationNumber Generation
definition.
Update for RDS13870 LTE Circuit Switch Fallback
for SMS
Update PR77823 about IMEI store logic
Include gap analyze for 3GPP R8 standard.
(search key word is R8)
9
th
Sep 2010 8.0 Xia Jing Update for RDS13870 LTE Circuit Switch Fallback
for SMS after review HLD. - All CDR changes
are deferred except only part of the E-CGI is
stored in the existing CGI field in the CDR for SMS
CSFB case. (RDS13870)
Add one note about all partial CDR call duration
will be closest irrespective what has been
configured on WEM
Update for RDS14221 Supporting and managing
ALCAP termination on 754x MGW
Update CDR difference between R4.x and w5.x in
section 6.4.
27
th
Sep 2010 9.0 Xia Jing Correct MRBT SS-code to 252 in ASN.1 definition.
(HFC)
3GPP CDR should record MME adjusted time zone for
SMS-over-SGs case (RDS13870)
20
th
Oct 2010 10.0 Xia Jing For VALID.
30
th
Nov 2010 11.0 Xia Jing Add one comment in roaming number in MOC-
CF CDR definition. (chapter 5.1.3)
Merge 6.1.1 into 6.1 for Options dynamically
modifiable
Update for RDS16253 Enhance Outgoing
gateway CDR TELNET MNP solution
Add case 4) in appdix D CDR IMPACT FOR MNP
SOLUTION
25
th
Jan 2011 11.0 Xia Jing RDS16318 Record 1st received MSRN in roaming
number CDR Field for 3GPP MOC CDR
Add a note about WCS only record the first 8 SS code
value in this CDR field.
Update 3GPP standard number (32.200->32.240,
32.205 to 32.250, Add 32.298)
After implement RDS5680 Outpulse MAP CLI
changes, WCS supports store different translated
number (before Outpulsed or after Outpulsed in
CDR
Update diagnostic description for PR59210.
25
th
July 2011 12.0 Xia Jing 1) Update NOA from 2 bit to 3 bit for record entity
CDR field in Appendix B.
2) Add cause code in Appendix F
3) Add one static DB flag for PR85393
4) Update appendix D about MNP solution
5) Update chapter 6.2 for RDS16380/16380a Add
an option for unsuccessful SMS CDR
6) Update Diagnostic definition in Appendix B
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


7) Remove RDS16308, because its move to W6.0
8) Update chapter 6.4 summary on CDR difference
between R5.x and R4.x
9) Update ASN.1 part : Remove BasicServiceCode-
struct and correct SubscribedOSSSCodes
definition
10) Correct one type error in ASN.1 about
hlrIntRecordExtension
11) Add note for transparent indicator in chapter
5.2.9.1
12) Remove Fields optionality from chapter 6.2
13) Add a note for basic service CDR field in chapter
5.2.3.
2
nd
Nov 2011 12.0 Xia Jing 1) Update for RDS16308 Support flexible value for
closest method for the call duration in 3GPP CDR
26
nd
Dec 2011 15.0 Xia Jing 1) Correct Supplyment service used tag value in
MOC CDR in appendix B

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.

3BL76381ACAADSZZA Edition 14 Released 1/332

Alcatel-Lucent 5060 Wireless Call Server

TECHNICAL REQUIREMENT SPECIFICATION

5060 WCS charging 3GPP format W5.x

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Table of contents
REFERENCED DOCUMENTS ............................................................................................................. 14
1 INTRODUCTION............................................................................................................................ 16
2 DEFINITIONS AND ABBREVIATIONS......................................................................................... 16
2.1 Definitions.........................................................................................................................16
2.2 Abbreviations ...................................................................................................................17
3 FILE FORMAT ............................................................................................................................... 18
4 TS 32.240 CIRCUIT-SWITCHED DOMAIN................................................................................ 18
4.1 Charging Principles.........................................................................................................18
4.1.1 Requirements according to TS 22.115................................................................18
4.1.2 General architecture ............................................................................................19
4.1.3 Charging Information ...........................................................................................20
4.1.3.1 Subscriber billing......................................................................................20
4.1.3.2 Settlements of Charges............................................................................20
4.1.3.3 Service Information ..................................................................................21
4.1.4 General Aspects of Charging Data......................................................................22
4.2 Collection of Charging Data Records............................................................................23
4.2.1 Charging Data Record (CDR) generation............................................................23
4.2.1.1 AoC service..............................................................................................24
4.2.1.2 CAMEL services.......................................................................................24
4.2.1.3 Use of supplementary services ................................................................24
4.2.1.4 Use of call forwarding...............................................................................25
4.2.1.5 Use of call hold and multi-party services..................................................25
4.2.1.6 Partial records ..........................................................................................26
4.2.1.7 Use of circuit-switched data services .......................................................27
4.2.1.8 Inter-MSC server handover ......................................................................27
4.2.1.9 Call re-establishment................................................................................28
4.2.1.10 Restricted directory numbers ...................................................................28
4.2.1.11 IMEI Observation......................................................................................29
4.2.1.12 Triggers for LCS-MT-CDR, LCS-MO-CDR and LCS-NI-CDR Charging
Information Collection..............................................................................................29
4.2.2 Charging scenarios..............................................................................................30
4.2.2.1 Mobile to land (outgoing) call ...................................................................31
4.2.2.2 Land to mobile (incoming) call .................................................................32
4.2.2.3 Mobile to mobile call within the same network.........................................33
4.2.2.4 Incoming call to a roaming subscriber......................................................34
4.2.2.5 Incoming call to a PLMN service centre...................................................35
4.2.2.6 Call forwarding unconditional ...................................................................36
4.2.2.7 Call forwarding conditional (on busy) .......................................................37
4.2.2.8 Delivery of a mobile terminated short message.......................................39
4.2.2.9 Call hold and multi-party service..............................................................40
4.2.2.10 Outgoing call handled by CAMEL ............................................................41
4.2.2.11 Incoming call handled by CAMEL without redirection..............................42
4.2.2.12 Incoming call to a roaming subscriber handled by CAMEL .....................43
4.2.2.13 Incoming call handled by CAMEL with redirection decided and forwarding leg
handled by CAMEL..................................................................................................45
4.2.2.14 Incoming call handled by CAMEL without redirection and forwarded early
using GSM SS but controlled by CAMEL ................................................................47
4.2.2.15 Incoming call handled by CAMEL without redirection and forwarded late
using GSM SS but controlled by CAMEL ................................................................48
4.2.2.16 Early forwarded call controlled by CAMEL...............................................51
4.2.2.17 Late forwarded call controlled by CAMEL................................................53
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.18 Incoming call handled by CAMEL with redirection initiated by CAMEL feature
55
4.2.2.19 CAMEL Scenario for Visiting Terminator Trigger Calls............................56
4.2.2.20 Outgoing call handled by CAMEL with Dialled CSI Trigger .....................58
4.2.2.21 Incoming call handled by CAMEL with redirection decided and forwarding leg
handled by CAMEL with Dialled CSI Trigger...........................................................59
4.2.2.22 Mobile terminated location request ..........................................................62
4.2.2.23 Mobile to land (outgoing) call, handovers ................................................63
4.2.2.24 Mobile to land (outgoing) call, inter PLMN handover ...............................63
4.2.2.25 Short Message Service originating ..........................................................64
4.2.2.26 Short Message Service originating with CAMEL invocation ....................64
4.2.2.27 Emergency call .........................................................................................64
4.2.2.28 Multiple call forwarding in the same GMSC.............................................64
4.2.2.29 Multiple call forwarding in the same VMSC..............................................65
4.2.2.30 Originating call with IN-CS1 invocation Continue .................................65
4.2.2.31 Originating call with IN-CS1 invocation Connect ..................................66
4.2.2.32 Terminating call with IN-CS1 invocation Connect .................................67
4.2.2.33 Originating call with CAMEL Connect and user interaction ..................69
4.2.2.34 Originating call with CAMEL follow-on calls..........................................71
4.2.2.35 Originating call with CAMEL follow-on calls with successful and
unsuccessfull calls ...................................................................................................73
4.2.2.36 Originating call with CAMEL Furnish Charging Information..................74
4.2.2.37 Originating call with CAMEL Send Charging Information .....................74
4.2.2.38 Supplementary Service operation............................................................74
4.2.2.39 Supplementary Service operation mobile initiated USSD.....................75
4.2.2.40 Supplementary Service operation network initiated USSD...................76
4.2.2.41 Call with optimal routeing, successful case..............................................77
4.2.2.42 Call with optimal routeing, unsuccessful case..........................................77
4.2.2.43 Call with optimal routeing, early call forwarding.......................................78
4.2.2.44 Call with optimal routeing, late call forwarding.........................................79
4.2.2.45 Terminating call to a ported MS MNP/SRF...........................................80
4.2.2.46 Terminating call to a ported MS MNP/IN...............................................80
4.2.2.47 Call re-origination (14086)........................................................................81
5 TS 32.250 CHARGING DATA DESCRIPTION.......................................................................... 83
5.1 Record types and contents.............................................................................................83
5.1.1 Mobile originated call attempt ..............................................................................86
5.1.2 Mobile originated emergency call attempt ...........................................................89
5.1.3 Mobile originated call forwarding attempt ............................................................90
5.1.4 Mobile terminated call attempt.............................................................................92
5.1.5 Mobile terminated call attempt call forwarding .................................................94
5.1.6 Roaming call attempt ...........................................................................................97
5.1.7 Incoming gateway call attempt ............................................................................98
5.1.8 Outgoing gateway call attempt ..........................................................................100
5.1.9 Transit call attempt ............................................................................................101
5.1.10 Supplementary service actions..........................................................................103
5.1.11 HLR interrogation...............................................................................................104
5.1.12 Location update (VLR).......................................................................................105
5.1.13 Location update (HLR).......................................................................................105
5.1.14 Short message service, mobile originated.........................................................106
5.1.15 SMS Short message service, mobile terminated...............................................107
5.1.16 SMS-MO interworking record ............................................................................107
5.1.17 SMS-MT gateway record...................................................................................108
5.1.18 Common equipment usage record ....................................................................108
5.1.19 Terminating CAMEL call attempt .......................................................................110
5.1.20 IMEI observation ticket ......................................................................................111
5.1.21 Mobile terminated location request (MT-LR) .....................................................113
5.1.22 Mobile originated location request (MO-LR)......................................................114
5.1.23 Network induced location request (NI-LR).........................................................115
5.1.24 Mobile originated call attempt (CAMEL CPH adapted version).........................116
5.1.25 gsmSCF initiated CAMEL CPH call attempt......................................................119
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.26 New Call Segment in a MO, CF and MT CAMEL Dialogue ..............................121
5.1.27 Mobile originated call forwarding attempt (CAMEL CPH adapted version).......122
5.1.28 Terminating CAMEL call attempt (CAMEL CPH adapted version)....................124
5.2 Description of Record Fields........................................................................................127
5.2.1 Additional Charging Information ........................................................................127
5.2.2 AoC parameters / change of AoC parameters ..................................................127
5.2.3 Basic Service / change of service / ISDN Basic Service...................................128
5.2.4 Call duration.......................................................................................................129
5.2.5 Call reference ....................................................................................................130
5.2.6 Calling / called / connected / translated number................................................131
5.2.6.1 Mapping of Numbering Plan and Nature of Adress for ISUP V3 interface
(SPIROU) (RDS4394)............................................................................................132
5.2.7 Calling Party Number.........................................................................................132
5.2.8 CAMEL call leg information ...............................................................................132
5.2.9 CAMEL information............................................................................................133
5.2.10 CAMEL initiated CF indicator.............................................................................133
5.2.11 CAMEL modified Service Centre.......................................................................134
5.2.12 CAMEL SMS Information...................................................................................134
5.2.13 Cause for termination ........................................................................................134
5.2.14 Channel Coding Accepted/Channel Coding Used.............................................136
5.2.15 Data volume.......................................................................................................136
5.2.16 Default call/SMS handling..................................................................................136
5.2.17 Destination Subscriber Number.........................................................................136
5.2.18 Diagnostics ........................................................................................................136
5.2.19 EMS-Digits.........................................................................................................136
5.2.20 EMS-Key............................................................................................................137
5.2.21 Entity number.....................................................................................................137
5.2.22 Equipment id......................................................................................................137
5.2.23 Equipment type..................................................................................................137
5.2.24 E-UTRAN Cell Global Identity (RDS13870) (deferred) .....................................137
5.2.25 Event time stamps .............................................................................................137
5.2.26 Fixed Network User Rate...................................................................................139
5.2.27 Free format data ................................................................................................140
5.2.28 Free format data append indicator ....................................................................140
5.2.29 GsmSCF address ..............................................................................................140
5.2.30 Guaranteed Bit Rate..........................................................................................140
5.2.31 HSCSD parameters / Change of HSCSD parameters ......................................141
5.2.32 Incoming/ outgoing trunk group.........................................................................141
5.2.33 Interrogation result .............................................................................................141
5.2.34 IMEI Check Event ..............................................................................................142
5.2.35 IMEI Status ........................................................................................................142
5.2.36 JIP Parameter ....................................................................................................142
5.2.37 JIP Query Status Indicator.................................................................................142
5.2.38 JIP Source Indicator ..........................................................................................143
5.2.39 LCS Cause.........................................................................................................143
5.2.40 LCS Client Identity.............................................................................................143
5.2.41 LCS Client Type.................................................................................................143
5.2.42 LCS Priority........................................................................................................143
5.2.43 LCS QoS............................................................................................................143
5.2.44 Level of CAMEL service ....................................................................................143
5.2.45 Location / change of location.............................................................................145
5.2.46 Location Estimate ..............................................................................................145
5.2.47 Location Extension (not implemented) ..............................................................145
5.2.48 Location Routing Number (LRN) .......................................................................145
5.2.49 Location Type ....................................................................................................146
5.2.50 LRN Query Status Indicator...............................................................................147
5.2.51 LRN Source Indicator ........................................................................................147
5.2.52 Maximum Bit Rate .............................................................................................147
5.2.53 Measure Duration ..............................................................................................148
5.2.54 Message reference............................................................................................148
5.2.55 MLC Number......................................................................................................148
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.56 Mobile station classmark / change of classmark ...............................................148
5.2.57 MOLR Type........................................................................................................148
5.2.58 MSC Address.....................................................................................................148
5.2.59 MSC Server Indication.......................................................................................149
5.2.60 Network Call Reference.....................................................................................149
5.2.61 Notification to MS user.......................................................................................149
5.2.62 Number of DP encountered...............................................................................149
5.2.63 Number of forwarding ........................................................................................149
5.2.64 Old /new location ...............................................................................................150
5.2.65 OutgoingIAMcallednumber (RDS16253) ...........................................................150
5.2.66 Partial Record Type...........................................................................................150
5.2.67 Positioning Data.................................................................................................150
5.2.68 Privacy Override ................................................................................................150
5.2.69 Radio channel requested / radio channel used / change of radio channel .......150
5.2.70 Rate Indication...................................................................................................151
5.2.71 Record extensions .............................................................................................151
5.2.71.1 BSCId of first BSC..................................................................................151
5.2.71.2 CS ARP..................................................................................................151
5.2.71.3 CUG incoming access used...................................................................151
5.2.71.4 CUG interlock code ................................................................................151
5.2.71.5 CUG index..............................................................................................151
5.2.71.6 CUG outgoing access indicator..............................................................151
5.2.71.7 CUG outgoing access suppressed........................................................151
5.2.71.8 Hot billing subscriber ..............................................................................151
5.2.71.9 IP connection..........................................................................................152
5.2.71.10 MS Category ..........................................................................................152
5.2.71.11 Multimedia call........................................................................................152
5.2.71.12 Redirecting counter ................................................................................152
5.2.71.13 Redirecting number ................................................................................152
5.2.71.14 RNCId of first RNC.................................................................................152
5.2.71.15 SMS originating number.........................................................................152
5.2.71.30 Interconnect Facility ...............................................................................152
5.2.71.32 MSC incoming/outgoing trunk group extension .....................................152
5.2.71.46 Service duration .....................................................................................153
5.2.72 Record type........................................................................................................153
5.2.73 Recording Entity ................................................................................................153
5.2.74 Roaming number ...............................................................................................153
5.2.75 Routing number .................................................................................................153
5.2.76 Sequence number .............................................................................................153
5.2.77 Served IMEI .......................................................................................................153
5.2.78 Served IMSI .......................................................................................................154
5.2.79 Served MSISDN ................................................................................................154
5.2.80 Service centre address......................................................................................154
5.2.81 Service key ........................................................................................................154
5.2.82 SGs cause (RDS13870) (deferred) ...................................................................154
5.2.83 Short message service result ............................................................................155
5.2.84 Speech version supported / Speech version used ............................................155
5.2.85 System type.......................................................................................................155
5.2.86 Supplementary service(s) ..................................................................................157
5.2.87 Subscribed OSSS Codes (RDS14064) .............................................................158
5.2.88 Supplementary service action............................................................................158
5.2.89 Supplementary service action result..................................................................159
5.2.90 Supplementary service parameters...................................................................159
5.2.91 Transparency indicator ......................................................................................159
5.2.92 Tracking Area Identity (RDS13870) (deferred)..................................................159
5.2.93 Update result .....................................................................................................159
5.3 Charging Data Record Structure..................................................................................160
5.3.1 ASN.1 definitions for CDR information ..............................................................160
6 OPTIONS ..................................................................................................................................... 209
6.1 Options dynamically modifiable...................................................................................209
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


6.2 Options statically modifiable........................................................................................211
6.3 summary on CDR difference between R4.x and R3.x ................................................214
6.4 summary on CDR difference between R5.x and R4.x ................................................216
A EXAMPLE OF MOBILE ORIGINATED CALL CDR.................................................................... 218
B 5060 WCS 3GPP CDR FIELD FLAG DESCRIPTION ................................................................ 219
MOC Call Record(include Forwarding Call Record) .............................................................219
Header 219
MOC Call Type.................................................................................................................219
Served IMSI .....................................................................................................................219
Served IMEI .....................................................................................................................219
Served MSISDN...............................................................................................................219
Calling Number ................................................................................................................220
Called Number .................................................................................................................220
Translated Number ..........................................................................................................220
Connected Number(not implemented).............................................................................220
Roaming Number .............................................................................................................221
Recording Entity...............................................................................................................221
Incoming Trunk Group .....................................................................................................221
Outgoing Trunk Group .....................................................................................................221
Location 222
Change Of Location.........................................................................................................222
Basic Service ...................................................................................................................223
Transparency Indicator ....................................................................................................223
Supplementary Services Used.........................................................................................224
Ms Class Mark .................................................................................................................224
Seizure Time Stamp ........................................................................................................224
Answer Time Stamp.........................................................................................................224
Release Time Stamp .......................................................................................................224
Call Duration ....................................................................................................................225
Radio Channel Used........................................................................................................225
Cause For Termination ....................................................................................................225
Diagnostics Value ............................................................................................................225
Call Reference .................................................................................................................225
Sequence Number of Partial Record...............................................................................226
Additional Chg Information...............................................................................................226
Record Extension.............................................................................................................226
Content of MOC Record Extension..................................................................................227
Hot Billing Subscriber ............................................................................................227
Ip Connection.........................................................................................................227
RNCid of First RNC ...............................................................................................227
Ms Category ..........................................................................................................227
Cs ARP 227
CUG Inter Lock ......................................................................................................227
CUG Index .............................................................................................................227
CUG Outgoing Access Suppressed ......................................................................227
CUG Outgoing Access Indicator............................................................................228
BSCid of First BSC................................................................................................228
Multi Media Call .....................................................................................................228
Inter Connect Facility(not implemented)................................................................228
Msc Incoming TKGP Extension.............................................................................228
Msc Outgoing TKGP Extension.............................................................................229
Subscribed OSSS Codes ......................................................................................229
Gsm SCF Address ...........................................................................................................230
Service Key......................................................................................................................230
Network Call Reference...................................................................................................230
MSC Address...................................................................................................................230
Camel Init CF Indicator ....................................................................................................231
Default Call Handling .......................................................................................................231
FNUR 231
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Channel Coding Used......................................................................................................231
Speech Version Used ......................................................................................................231
Number of DP Encountered.............................................................................................232
Level of Camel Service....................................................................................................232
Free Format Data.............................................................................................................232
Camel Leg Information.....................................................................................................232
Content of Camel Leg Information...................................................................................232
Camel Destination Number....................................................................................232
Connected Number(not implemented) ..................................................................233
Roaming Number(not implemented) .....................................................................233
Msc Outgoing Trunk Group(not implemented) ......................................................233
Seizure Time Stamp(not implemented) .................................................................233
Answer Time Stamp(not implemented) .................................................................234
Release Time Stamp(not implemented) ................................................................234
Call Duration(not implemented) .............................................................................234
Data Volume(not implemented) .............................................................................234
Camel Init CF Indicator ..........................................................................................234
Cause For Termination(not implemented).............................................................234
Camel Modification ................................................................................................235
Free Format Data ..................................................................................................237
Diagnostics Value(not implemented).....................................................................238
Free Format Data Append(not implemented)........................................................238
Free Format Data-2 ...............................................................................................238
Free Format Data Append-2(not implemented) ....................................................238
Free Format Data Append(not implemented) ..................................................................238
Default Call Handling-2....................................................................................................239
Gsm SCF Address-2........................................................................................................239
Service Key-2...................................................................................................................239
Free Format Data-2 .........................................................................................................239
Free Format Data Append-2(not implemented)...............................................................239
System Type ....................................................................................................................239
Rate Indication .................................................................................................................240
Location Routing Number ................................................................................................240
LRN Source Indicator.......................................................................................................240
LRN Query Status Indicator .............................................................................................240
Partial Record Type .........................................................................................................240
Guaranteed Bit Rate ........................................................................................................241
Maximum Bit Rate............................................................................................................241
MTC Call Record.......................................................................................................................241
Header 241
MTC Call Type .................................................................................................................242
Served IMSI .....................................................................................................................242
Served IMEI .....................................................................................................................242
Served MSISDN...............................................................................................................242
Calling Number ................................................................................................................242
Connected Number ..........................................................................................................243
Location 244
Change Of Location.........................................................................................................244
Basic Service ...................................................................................................................245
Ms Class Mark .................................................................................................................246
Call Duration ....................................................................................................................247
Radio Channel Used........................................................................................................247
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Call Reference .................................................................................................................247
Additional Chg Info...........................................................................................................248
MSC Address...................................................................................................................249
FNUR 249
Channel Code Used.........................................................................................................249
Speech Version Used ......................................................................................................249
System Type R5...............................................................................................................250
Rate Indication .................................................................................................................250
Guaranteed Bit Rate ........................................................................................................251
Maximum Bit Rate............................................................................................................251
System Type ....................................................................................................................252
Content of MTC Record Extension ..................................................................................252
Gsm SCF Address (O_CSI Data) ..........................................................................252
Service Key (O_CSI Data).....................................................................................252
Redirecting Counter...............................................................................................252
Ms Category ..........................................................................................................253
Cs ARP 253
CUG Inter Lock ......................................................................................................253
CUG Index .............................................................................................................253
CUG Incoming Access Used.................................................................................253
Multi Media Call .....................................................................................................253
Redirecting Number...............................................................................................253
CUG Outgoing Access Indicator............................................................................255
TCAMEL Call Record ...............................................................................................................256
Header 256
TCAMEL Call Type ..........................................................................................................256
Served IMSI .....................................................................................................................256
Served MSISDN...............................................................................................................256
Interrogation Time Stamp ................................................................................................257
Destination Routing Address ...........................................................................................257
Gsm SCF Address ...........................................................................................................257
Service Key......................................................................................................................257
MSC Address...................................................................................................................258
Default Call Handling .......................................................................................................258
Record Extension (not implemented)...............................................................................258
Content of Tcamel Record Extension (not implemented) ................................................259
Called Number .................................................................................................................260
Calling Number ................................................................................................................260
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Call Duration ....................................................................................................................261
Call Reference .................................................................................................................262
Number of DP Encountered.............................................................................................263
Level of Camel Service....................................................................................................263
Free Format Data.............................................................................................................263
Camel Leg Information.....................................................................................................263
Content of Camel Leg Information(refer to 1.1.45) ..........................................................263
Free Format Data Append(not implemented) ..................................................................263
Default Call Handling-2....................................................................................................264
Gsm SCF Address-2........................................................................................................264
Service Key-2...................................................................................................................264
Free Format Data-2 .........................................................................................................264
Free Format Data Append-2(not implemented)...............................................................264
MSC Server Indication(not implemented) ........................................................................264
Incoming Gateway Record......................................................................................................265
Header 265
IncGateway Call Type......................................................................................................266
Calling Number ................................................................................................................266
Called Number .................................................................................................................266
Call Duration ....................................................................................................................268
Call Reference .................................................................................................................268
Content of IncGateway Record Extension.......................................................................269
Roaming Number...................................................................................................269
Gsm SCF Address.................................................................................................271
Service Key............................................................................................................271
Default Call Handling.............................................................................................271
Free Format Data ..................................................................................................271
Camel Leg Information ..........................................................................................272
Network Call Reference.........................................................................................272
IsdnBasicService ...................................................................................................272
Basic Service.........................................................................................................273
ISDN- Bearer capability ...................................................................................................274
LLC 274
HLC 274
Outgoing Gateway Record......................................................................................................274
Header 274
OutGateway Call Type.....................................................................................................274
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Calling Number ................................................................................................................274
Called Number .................................................................................................................275
Call Duration ....................................................................................................................276
Call Reference .................................................................................................................277
Content of OutGateway Record Extension......................................................................278
Roaming Number...................................................................................................278
ISDN-Bearer capability ....................................................................................................279
LLC 280
HLC 280
IsdnBasicService ...................................................................................................280
Basic Service.........................................................................................................280
OutgoingIAMcallednumber (RDS16253) ...............................................................281
Transit Call Record ..................................................................................................................282
Header 282
Transit Call Type..............................................................................................................282
Calling Number ................................................................................................................283
Called Number .................................................................................................................283
ISDN Basic Service..........................................................................................................283
Call Duration ....................................................................................................................284
Call Reference .................................................................................................................285
Content of Transit Record Extension...............................................................................286
Gsm SCF Address.................................................................................................287
Service Key............................................................................................................287
Default Call Handling.............................................................................................288
Free Format Data ..................................................................................................288
Camel Leg Information ..........................................................................................288
Network Call Reference.........................................................................................288
MO SMS.....................................................................................................................................289
Header 289
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


MO SMS Call Type ..........................................................................................................289
Served IMSI .....................................................................................................................290
Served IMEI .....................................................................................................................290
Served MSISDN...............................................................................................................290
Ms Class Mark .................................................................................................................290
Service Centre .................................................................................................................290
Location 291
Message Reference.........................................................................................................291
Origination Time Stamp ...................................................................................................291
Sms Result.......................................................................................................................291
Content of MO SMS Record Extension ...........................................................................292
Destination Number .........................................................................................................293
Camel SMS Information...................................................................................................293
Camel SMS Content ........................................................................................................293
Gsm SCF Address.................................................................................................293
Service Key............................................................................................................293
Default Sms Handling............................................................................................294
Free Format Data ..................................................................................................294
Calling Party Number.............................................................................................294
Destination Subscriber Number.............................................................................294
Camel SMSCAddress............................................................................................294
Sms Reference Number(not implemented) ...........................................................295
System Type ....................................................................................................................295
MT SMS .....................................................................................................................................295
Header 295
MT SMS Call Type...........................................................................................................295
Service Centre .................................................................................................................295
Served IMSI .....................................................................................................................296
Served IMEI .....................................................................................................................296
Served MSISDN...............................................................................................................296
Ms Class Mark .................................................................................................................296
Location 297
Delivery Time Stamp........................................................................................................297
Sms Result.......................................................................................................................297
Content of MT SMS Record Extension............................................................................298
Sms Originating Number .......................................................................................298
Subscribed OSSS Codes (RDS14064) .................................................................298
SGs Cause (RDS13870) (not implemented) .........................................................299
System Type ....................................................................................................................299
SS Action Call ...........................................................................................................................299
Header 299
SS Action Call Type.........................................................................................................299
Served IMSI .....................................................................................................................300
Served IMEI .....................................................................................................................300
Served MSISDN...............................................................................................................300
Ms Class Mark .................................................................................................................300
Location 300
Basic Service ...................................................................................................................301
Supplementary Service....................................................................................................301
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


SS Action Type ................................................................................................................301
SS Action Time Stamp.....................................................................................................302
SS Parameters.................................................................................................................302
SS Parameters Content ...................................................................................................302
Forwarded-To Number ..........................................................................................302
Unstructured Data..................................................................................................302
SS Action Result ..............................................................................................................302
SS Call Reference............................................................................................................302
Content of SS Action Record Extension..........................................................................303
Ussd Service Duration...........................................................................................303
System Type ....................................................................................................................304
Roaming Record.......................................................................................................................304
Header 304
Roaming CDR Type.........................................................................................................304
Served IMSI .....................................................................................................................304
Served MSISDN...............................................................................................................305
Calling Number ................................................................................................................305
Roaming Number .............................................................................................................305
Basic Service ...................................................................................................................306
Call Duration ....................................................................................................................307
Call Reference .................................................................................................................308
Content of Roaming Record Extension ...........................................................................309
Additional Chg Information ....................................................................................310
NationalIndicator....................................................................................................310
NationalIndicator....................................................................................................310
operatorIndicator....................................................................................................310
operatorIndicator....................................................................................................310
upstreamCarrier.....................................................................................................311
downstreamCarrier ................................................................................................311
callingPartyLocationNumber..................................................................................311
redirectingNumber .................................................................................................311
originalCalledNumber ............................................................................................311
pRBTIndication ......................................................................................................311
timeExtensions ......................................................................................................311
optimalRouteingType.............................................................................................312
disconnectingParty ................................................................................................312
MSC Address...................................................................................................................313
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


HLRINT Record.........................................................................................................................314
Header 314
Roaming CDR Type.........................................................................................................314
Served IMSI .....................................................................................................................315
Served MSISDN...............................................................................................................315
Basic Service ...................................................................................................................315
Routing Number ...............................................................................................................315
interrogationTime.............................................................................................................316
numberOfForwarding.......................................................................................................316
interrogationResult ...........................................................................................................316
Content of MOC Record Extension..................................................................................317
C DEFINITIONS............................................................................................................................... 318
Definition of NOA and NPI .......................................................................................................318
Definition of PRI and SI............................................................................................................318
Time Stamp(05-12-11 13:14:05 and Time Zone Offset = -8:15 .............................................318
Basic Service Code..................................................................................................................318
Supplementary Service Code .................................................................................................318
ISDN Basic Service Code ........................................................................................................319
CISS Result ...............................................................................................................................319
LRN Source Indicator and LRN Query Status Indicator.......................................................320
Trunk group type......................................................................................................................320
Interface type............................................................................................................................320
D CDR IMPACT FOR MNP SOLUTION ......................................................................................... 322
E SYNTHESIS OF THE CDRS CONTENTS................................................................................... 325
F CAUSE CODE ............................................................................................................................. 329
G CDR CONTENTS EVOLUTION................................................................................................... 330

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


REFERENCED DOCUMENTS
[1] Charging principles
TS 32.240, v8.6.0 (R8)
[2] Charging data description for the circuit switched domain
TS 32.250, v 8.2.0 (R8)
[3] Charging data description for the circuit switched domain
TS 32.298, v 8.8.0 (R8)
[4] CDR generation and distribution mechanisms
3BL 76380 AAAA DSZZA
[5] Charging and Billing
TS 22.115, v 4.1.0 v 5.4.0
[6] Advice of Charge (AoC) supplementary services, stage 1
TS 22.086
[7] Description of Charge Advice Information (CAI)
TS 22.024
[8] Handover procedures
TS 23.009
[9] Mobile radio interface Layer 3 specification; Core network protocols; stage 3
TS 24.008
[10] Advice of Charge (AoC) supplementary services stage 3
TS 24.086
[11] Mobile Application Part (MAP) specification
TS 29.002
[12] CAMEL Application Part (CAP) specification
TS 29.078
[13] Application of the ISDN user part of CCITT signalling System No.7 for international ISDN
interconnections
Q.767
[14] Numbering, addressing and identification
TS 23.003
[15] The international public telecommunication numbering plan
E.164
[16] General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)
TS 27.001
[17] Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)
TS 22.002
[18] Location Services ; Base Station System Application Part LCS Extension (BSSAP-LE)
TS 49.031
[19] Technical realization of the Short Message Service (SMS)
TS 23.040
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


[20] Mobile radio Layer 3 supplementary service specification; Formats and coding
TS 24.080
[21] General on Supplementary Services
TS 22.004
[22] Specification of Abstract Syntax Notation One (ASN.1)
X.208
[23] Information technology Abstract Syntax Notation One (ASN.1): Specification of basic notation
X.680
[24] 5060 TRS External/Internal Cause Codes Mapping
3BL7657AAAADSZZA

Internal reference documents
[25] Atrium Billing format specification, version 2.3
[26] FS Charging Data Collection
AAC020017800DS
[27] Elaboration and format of the CRA in the SSPs of the PLMN
AAC010520600DS
[28] CDR gateway: charging data interface ASN.1 format
[29] MSC SARA CDR gateway
[30] Atrium CDR format description Ed. 05P02
[31] TRS - WCS CAMEL
[32] A5020 WCS : TRS IN-CS1
[33] TRS-CUG
3BL76769AAAADSZZA
[34] ASN.1 definition file for compile W5.x
3HP700334107QAZZA
[35] CDR sample with decode result W5.x
3HP700334108QAZZA

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


1 INTRODUCTION
This document describes the format for the CDRs generated by the Alcatel-Lucent 5060 WCS in W5.x. It
is based on the 3GPP recommendations with private extensions allowed by the standard.
The section 4 is an inclusion of the section 5 of TS 32.240 (release 8), which deals with the generation of
CDR by the Circuit-Switched domain. This section contains notably a number of call scenarios. The text is
included as-is. The specificities of the Alcatel-Lucent 5060 WCS are marked by paragraphs in boxes, and
beginning with : 5060 WCS position.
The section 5 is an inclusion of TS 32.250 (release 8), which deals with the format of the CDR. It contains
the ASN.1 description of the records, as well as information on the way their fields shall be filled. Here
again, the specificities of the 5060 WCS are marked by paragraphs in boxes, and beginning with : 5060
WCS position. In the format description, the 5060 WCS-specific information elements are added in
extension fields, and the information elements that are specified by 3GPP but not stored by the 5060
WCS are crossed out. This format is compliant with the format defined by the 3GPP, there is not
incompatibility.
2 DEFINITIONS AND ABBREVIATIONS
2.1 Definitions

For the purposes of the present document, the following terms and definitions apply:
(GSM only): indicates that this clause or paragraph applies only to a GSM system. For multi-system
cases this is determined by the current serving radio access network.
(UMTS only): indicates that this clause or paragraph applies only to a UMTS system. For multi-system
cases this is determined by the current serving radio access network.
Advice of charge: real-time display of the network utilisation charges incurred by the Mobile Station. The
charges are displayed in the form of charging units. If a unit price is stored by the MS then the display
may also include the equivalent charge in the home currency.
Aoc service: combination of one or more services, both basic and supplementary, together with a
number of other charging relevant parameters to define a customised service for the purpose of advice of
charge.
CAMEL: network feature that provides the mechanisms to support operator specific services even when
roaming outside HPLMN.
CAMEL subscription information: identifies a subscriber as having CAMEL services.
CDR (Charging Data Record): record generated by a network element for the purpose of billing a
subscriber for the provided service. It includes fields identifying the user, the session and the network
elements as well as information on the network resources and services used to support a subscriber
session. In the traditional circuit domain, CDR has been used to denote Call Detail Record, which is
subsumed by Charging Data Record hereafter.
Charging destination: also referred to as a destination for charging, this is a nominal reference defining
the point of termination of a connection for charging purposes.
Charging origin: nominal reference defining the point of origin of a connection for charging purposes.
Observed IMEI ticket: record used to describe an EIR relevant event e.g. a blacklisted IMEI.
Successful call: connection that reaches the communication or data transfer phase. It corresponds to
the answered state. All other connection attempts are regarded as unsuccessful.
Gateway MSC: a MSC at the frontier of a PLMN
Interrogating MSC: a MSC which interrogates the HLR in order to obtain a roaming number
Transit MSC: a MSC which performs an intra-PLMN transit call
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


2.2 Abbreviations

For the purposes of the present document, the following abbreviations apply. Additional applicable
abbreviations can be found in TR 21.905 [1].
AoC Advice of Charge
BCSM Basic Call State Model
CAI Charge Advice Information
CAMEL Customised Applications for Mobile network Enhanced Logic
CDR Call Detail Record
DP Detection Point
EDP Event Detection Point
EIR Equipment Identity Register
EMS-Digits North American Emergency Service Routing Digits
EMS-Key North American Emergency Service Routing Key
ETSI European Telecommunications Standard Institute
FCI Furnish Charging Information
FTAM File Transfer, Access and Management
GMSC Gateway MSC
gsmSCF GSM Service Control Function
gsmSSF GSM Service Switching Function
HLR Home Location Register
HPLMN Home PLMN
HSCSD High Speed Circuit Switched Data
IMEI International Mobile Equipment Identity
IMSC Interrogating MSC
IMSI International Mobile Subscriber Identity
ISDN Integrated Services Digital Network
LAC Location Area Code
LR Location Request
MLC Mobile Location Center
MOC Mobile Originated Call (attempt)
MO-LR Mobile Originated Location Request
MS Mobile Station
MSC Mobile Switching Centre
MSRN Mobile Station Roaming Number
MTC Mobile Terminated Call (attempt)
MT-LR Mobile Terminated Location Request
NE Network Element
NI-LR Network Induced Location Request
O_CSI Originating CAMEL Subscription Information
PLMN Public Land Mobile Network
SAC Service Area Code
SCF Service Control Function
SCI Subscriber Controlled Input or Send Charging Information
SMS Short Message Service
SS7 Signalling System No. 7
T_CSI Terminating CAMEL Subscription Information
TDP Trigger Detection Point
TMN Telecommunications Management Network
TMSC Transit MSC
USIM User Service Identity Module
USSD Unstructured Supplementary Service Data
UTRAN UMTS Terrestrial Radio Access Network
VAS Value Added Service
VLR Visitor Location Register
VMSC Visited MSC
VPLMN Visited PLMN
VT-CSI Visited Terminating CAMEL Subscription Information
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


3 FILE FORMAT
The CDRs (Call Detail Records) are gathered in files stored on the MSC. This document focuses only on
the contents of these files.
Files contain no header or trailer information. They just contain a sequence of records.
Backward compatibility with the previous Billing formats will be supported
An ASN.1 description of the CDRs formats is provided in this document. The CDRs are encoded
with the Basic Encoding Rules (BER), and are stored in TLV binary format in the files, with no
delimitation between fields.
The records have variable length. It is possible to pass from one record to the other thanks to the
length of the record, which is stored next to the type of the record.
Some fields can be defined as optional in a record format. In this case, they can be present or not in
a record, depending on the data of the call.
Some fields can also have a default value, defined in the ASN.1 notation. In this case, they are
present in a record only if their value defer from the default value.
The location of the files on disk, the conditions of closure and their transfer to the billing system is out of
scope of this document. This information can be found in [4].
4 TS 32.240 CIRCUIT-SWITCHED DOMAIN
4.1 Charging Principles
4.1.1 Requirements according to TS 22.115
The following high-level requirements summarize the more detailed requirements of TS 22.115 [5].
a) to provide a CDR for all charges incurred and requiring settlement between the different commercial
roles;
b) to allow itemized billing for all services (including CAMEL) charged to each subscription, including
voice and data calls, and services offered by home environments, taking into account:
information provided by the user (including authentication parameters, etc.);
information provided by the serving network (including Serving Network Id, timestamps, etc.);
information provided by the service (including charged party, long calling, multimedia, etc.).
c) to allow fraud control by the Home Environment and the Serving network.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.1.2 General architecture
The general functional architecture of the charging function is described in the following figure
:

Gn
Billing
System
GGSN
VMSC
Server
SGSN
CS Domain
PS Domain
CDR
CDR
CDR
Ga
CGF
MGW
GMSC
Server
MGW
HLR
SCF
CDR
Mc
Mc
MMS
Relay
Server
Gn
Billing
System
GGSN
VMSC
Server
SGSN
PS Domain
CDR
CDR
CDR
Ga
Ga
CGF
MGW
GMSC
Server
MGW
HLR
SCF
CDR
Mc
Mc
MMS
Relay
Server
CDR
CAP
CAP
CDR
Service Domain
Gn
Billing
System
GGSN
VMSC
Server
SGSN
PS Domain
CDR
CDR
CDR
Ga
CGF
MGW
GMSC
Server
MGW
HLR
SCF
CDR
Mc
Mc
MMS
Relay
Server
Gn
Billing
System
GGSN
VMSC
Server
SGSN
PS Domain
CDR
CDR
CDR
Ga
Ga
CGF
MGW
GMSC
Server
MGW
HLR
SCF
CDR
Mc
Mc
MMS
Relay
Server
CDR
CAP
CAP
CDR
Service Domain
Gr
C
D
Gc
IuPS
IuCS A
IuPS
IuCS
Gb Gb
A
Gp
Gn
Billing
System
GGSN
VMSC
Server
SGSN
PS Domain
CDR
CDR
Ga
CGF
MGW
GMSC
Server
MGW
HLR
SCF
CDR
Mc
Mc
MMS
Relay
Server
Gn
Billing
System
GGSN
VMSC
Server
SGSN
PS Domain
CDR
CDR
Ga
Ga
CGF
MGW
GMSC
Server
MGW
HLR
SCF
CDR
Mc
Mc
MMS
Relay
Server
CDR
CAP
CAP
CDR
Service Domain
Gn
Billing
System
GGSN
VMSC
Server
SGSN
PS Domain
CDR
CDR
CDR
Ga
CGF
MGW
GMSC
Server
MGW
HLR
CDR
Mc
Mc
MMS
Relay
Server
Gn
Gi
PSTN
Billing
System
GGSN
VMSC
Server
SGSN
PS Domain
CDR
CDR
Ga
Ga
CGF
MGW
GMSC
Server
MGW
HLR
gsm
SCF
CDR
Mc
Mc
MMS
Relay
Server
CDR
CAP
CAP
CAP
CDR
Service Domain
Gr
C
Gc
IuPS
IuCS A
IuPS
IuCS A
Gp
gsm
SSF
gprs
SSF
gsm
SSF
VMSC
Server
MGW
Mc
VMSC
Server
MGW
Mc
VMSC
Server
MGW
Mc
VMSC
Server
MGW
Mc
VMSC
Server
MGW
Mc
VMSC
Server
MGW
Mc
VMSC
Server
MGW
Mc
TMSC
Server
MGW Mc
gsm
SSF
CAP

Figure 1: 3G charging logical architecture
The scope of this document is limited to the CDRs generated in the CS domain, by the MSC server
(VMSC, GMSC or TMSC).
The CDRs generated by the HLR and the gsmSCF are out of scope of this document.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.1.3 Charging Information
The MSC server (VMSC) and Gateway MSC server are responsible for the collection of all charging
relevant info for each MS and PSTN connection and for the storage of this information in the form of
CDR.
The charging relevant information include notably (not exhaustive list) :
- the identity of the mobile subscriber
- the identity of the second party
- the answer time and release time of the call
- the supplementary services invoked during the call
- the CAMEL services invoked during the call
Charging Data Records related to a circuit switched call are generated in one MSC server (the anchor
MSC server) where all relevant data is available. That is guaranteed by routing all signalling information
through the anchor MSC server even if the traffic channel of a call is routed through another MSC server
due to handover.
The Gateway MSC server acts as a gateway into other PLMN or fixed networks. Within the PLMN, the
GMSC server is responsible for the generation of CDRs for calls routed from or into other networks.
If subscribed CAMEL services apply to MS, the (G)MSC servers contain CAMEL subscription data
providing the information required for invocation of the CAMEL dialogues for controlling the MS
terminating and MS originating calls. Charging data record parameters resulting from the CAMEL
treatment applying to MS calls is derived from the CAMEL subscription data.
In addition to user subscribed services, specific dialled CAMEL services might be invoked which also
influence existing records or even trigger the generation of separate records steered by service logic.
4.1.3.1 Subscriber billing
The charging data collected from the HPLMN, interrogating PLMN, and/or VPLMN network elements is
employed to determine the network utilization charges for the basic and supplementary services utilized
by the home subscribers of the PLMN. The charges calculated are then combined with the network
access (subscription) charges and billed to those customers directly serviced by the PLMN.
For those subscribers handled by Service Providers, the billing information is employed for both
wholesale (Network Operator to Service Provider) and retail (Service Provider to Subscriber) billing.
Consequently, having been processed by the PLMN Billing System, the charging data collected from the
network elements may also be sent to the Service Provider for further processing.
4.1.3.2 Settlements of Charges
4.1.3.2.1 Inter-PLMN accounting
Inter-PLMN accounts for roaming traffic are determined in accordance with ITU-T principles (see ITU-T
Recommendation D.93 [18]) and are settled by means of the GSM Associations Transferred Account
Procedure (TAP).
4.1.3.2.2 Visitors from other PLMNs
The CDRs collected from the network also include details of the services employed by visiting (roaming)
subscribers. The charges for mobile originated calls (MOCs) and for supplementary services used are
calculated as for home subscribers, converted to an agreed accounting currency and included in the
CDRs for the TAP. Even if mobile terminated calls (MTCs) are zero-priced in the visited network
(VPLMN), in the absence of optimised routing the MTC TAP records are still required by the home
network (HPLMN) in order to determine the re-routing charges from the HPLMN to the VPLMN.

The TAP records generated are exchanged with each HPLMN on a regular basis. These TAP records
form the basis of the invoice submitted by the VPLMN for the traffic carried.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.1.3.2.3 Home subscribers roaming in other PLMNs
The HPLMN receives TAP records from each VPLMN for services employed by home subscribers whilst
roaming. These records are employed to verify the invoices from the VPLMN and to bill the home
subscribers for the services used. The charges contained in the TAP records are converted from the
accounting currency to the local currency and a handling surcharge (mark-up) is added if required. The
TAP records are subsequently passed to the subscriber billing process described in subclause 4.1.3.1.
4.1.3.2.4 Fixed network operators and other service providers
The settlement of accounts with the operators of fixed networks for traffic carried, is generally performed
on a bulk basis according to the principles outlined in the ITU-T D-series recommendations.
The traffic accounted for in this manner may include:
outgoing (Mobile to Land) traffic;
incoming (Land to Mobile) traffic;
transit traffic, carried by intermediate networks;
signalling (MAP/SCCP, CAP/SCCP) traffic such as location updates.
5060 WCS position : signalling traffic is not recorded (the location updates, HLR interrogation)
Accounting information may also be required for the use of services provided by other operators such as
short message service centres and other value added service (VAS) providers. The charges for the
various traffic shares may be determined on the basis of the CDRs generated by the network elements or
on the basis of bulk counters (accounting meter records) in the gateway MSC servers (GMSC servers).
For the purpose of the present document, the management information required is assumed to be derived
from CDRs. The management of accounting meters is outside the scope of the present document.
4.1.3.3 Service Information
The charging data collected from the network elements may be used to provide statistical information
concerning the use of services, by both home and visiting subscribers, within the network. In addition, the
introduction of new services and/ or modifications to the tariffs of existing services may also require the
distribution of the appropriate tariff information to the network elements for Advice of Charge purposes.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.1.4 General Aspects of Charging Data
Charging data record (CDR) generation and contents should be flexible and unnecessary redundancy in
data should be avoided. Charging data are collected for successful and selected unsuccessful subscriber
transactions. The subscriber transaction is seen as being successful in the MSC server (where the CDR
is generated) either if a call is answered or if the Short Message Service Centre has confirmed the
successful receipt of a mobile originated short message.
Unsuccessful call attempts are recorded in the case of partial record generation due to CAMEL
FollowOnCalls. If in such a call constellation the answer state is reached at least once, subsequent
unsuccessful set-up of a connection configuration is also recorded in order to provide a complete
sequence of FIRST, INTERMEDIATE and LAST records.
5060 WCS position : Partial Record handling is only implemented due to time limit event.
All other triggers to generate Partial records, e.g. due to CAMEL FollowOnCalls as described above,
are not implemented yet.
Charging data is also collected for supplementary service activity.
At termination of the subscriber transaction these data are formatted into CDRs. These records are
forwarded onto MSC servers disk file, which constitute the source for further transportation of that data to
a Billing System. For the purpose of the present document, the CDRs are considered to be collected, in
near real-time, by the following network elements: the MSC servers, MGWs, and location registers.
5060 WCS position : the hot-billing functionality is also offered. The records generated for certain
subscribers, who have a specific subscriber category or OSSS code, are not only stored onto the 5060
WCSs disk, but also sent in near-real time to a billing centre. This billing centre can be the same as the
billing centre that processes the CDR, or can be a dedicated hot-billing centre.
The data collected by the network elements are sent to, or collected by, the appropriate Billing System for
storage and further processing. Similarly, the tariff data required by the network elements to provide on-
line charging information are distributed by the appropriate management system.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2 Collection of Charging Data Records
4.2.1 Charging Data Record (CDR) generation
In order to provide the data required for the management activities outlined in the previous subclauses
(billing, accounting, statistics etc.), the NEF of the MSC server and/or Location Registers shall be able to
produce an charging data record for each of the following:
Mobile originated call attempt;
Mobile originated emergency call attempt;
Mobile originated, call forwarding attempt;
Mobile originated with IP;
Mobile terminated call attempt;
Mobile terminated call attempt, call forwarding attempt;
Roaming call attempt in a gateway MSC server;
Incoming call attempt in a gateway MSC server;
Outgoing call attempt from a gateway MSC server;
Transit call attempt;
Terminating CAMEL call attempt;
Supplementary service actions;
HLR interrogation;
Location updating (HLR & VLR);
Short message service (point-to-point), mobile originated;
Short message service (point-to-point), mobile terminated;
Short message service (point-to-point), mobile originated interworking MSC server;
Short message service (point-to-point), mobile terminated gateway MSC server;
Common equipment usage;
Mobile terminated location request;
Mobile originated location request;
Network induced location request.
The purpose of each of these records is described in the following subclauses. A detailed formal
description of the data defined in the present document is to be found in TS 32.250 Error! Reference
source not found..
5060 WCS position : The following records are not generated by the 5060 WCS :
Roaming call attempt in a gateway MSC server and the HLR interrogation; RDS6904
Location updating;
Short message service mobile originated interworking MSC server;
Short message service mobile terminated gateway MSC server;
Common equipment usage;
Mobile terminated location request;
Mobile originated location request
Network induced location request.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.1.1 AoC service
5060 WCS position : this service is not implemented, and this paragraph is not relevant.
In addition to the information collected from these Network Elements, network management functions are
required for the administration of on-line charging data stored in the MSC server. Two levels of AoC
service are available: information level and charging level. The information level is used only to provide
AoC information to the user. For the charging level, if no approval of the AoC information by the MS is
received in the MSC server, the call is released immediately.
This data is employed to drive the charge display in the Mobile Station (MS) as required by the advice of
charge (AoC) service and defined by 3GPP TS 22.086 [6] and 3GPP TS 22.024 [7]. Information used by
the AoC service shall include a combination of the following:
one or more basic services; and/or
one or more supplementary services; and/or
one or more network specific services; and/or
one or more power capability classes (MS classmark); and/or
the type of radio traffic channel used/ requested;
the transparency mode of the basic service employed (transparent/non-transparent);
the type of call or connection (e.g. MOC/ MTC).
This list may also be extended to include additional network specific parameters.
Parameters sent to the mobile station during the operation of the AoC service are recorded in the
appropriate CDRs.
4.2.1.2 CAMEL services
A CAMEL service can be activated for originating, forwarded and terminated calls and originating SMS.
Several fields describing CAMEL subscription and free format data are recorded to appropriate CDR. For
originating and forwarded calls two different CAMEL services can be active and part of stored information
is different depending on the CAMEL call model and which triggers occur. CAMEL fields describing usage
level of service, CAMEL modified parameters and CAMEL initiated call forwarding include information for
one call leg including impacts on all CAMEL services.
4.2.1.3 Use of supplementary services
The recording of supplementary service usage permits the Billing System (BS) to specify the
supplementary service actions (invocation, registration etc.).
In addition to specifying the actions to be recorded, the BS may also determine how these events are to
be recorded. Non-call related events, such as the administration of supplementary services by the
subscriber via the MMI of the MS, shall result in the production of supplementary service action records.
Call related events (e.g. invocation of supplementary services) shall be recorded in-line in the
appropriate CDR and/ or in a separate SS-action record depending on the configuration specified by the
BS.
5060 WCS position : the call related events are only recorded in-line in the appropriate CDR.
Where the use of a supplementary service results in the production of further connections (e.g. call
forwarding, multi-party service etc.) additional CDRs shall be produced to describe the relevant
connections. The use of such services is described in more detail both in this subclause and in the
example scenarios.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.1.4 Use of call forwarding
When one of the call forwarding services is used, the charging function of the MSC server that forwards
the call, shall produce the MTC-CF record and MOC-CF record for the forwarded part of the call.
For further information concerning the recording of call forwarding services see the example scenarios in
subclauses 4.2.2.6 and 4.2.2.7.
4.2.1.5 Use of call hold and multi-party services
The use of the call hold service shall be recorded either in-line in the appropriate CDR or in a separate
supplementary service invocation record as described above. The duration for which the call is held, i.e.
is inactive, is not recorded.
The use of the multi-party service requires a minimum of 3 subscribers and the use of a conference
circuit. For the purpose of the following description the subscriber invoking the service is referred to as
the conference originator (A) and the conference call is regarded as consisting of a number of individual
legs between the conference originator and the other parties (B, C, etc.) in the call.
Normal MOC and MTC CDRs shall be generated for each party and each leg of the call. In addition, if
common equipment records are enabled, a common equipment record shall be produced for the
conference originator in order to record the use of a conference bridge and to record the total duration of
the conference connection.
EXAMPLE:
Subscriber C calls subscriber A. Subscriber A places the call from C on hold and makes a second
call to subscriber B. Subscriber A then invokes the multi-party service in order to set-up a conference
call with B and C.
Assuming that the appropriate types of record are enabled, the following CDRs shall be produced:
An MOC record for subscriber C and the C->A leg of the call;
An MTC record for subscriber A and the C->A leg of the call;
An MOC record for subscriber A and the A->B leg of the call;
An SS-Action record for the invocation of the call hold service by subscriber A;
An MTC record for subscriber B and the A->B leg of the call;
An SS-Action record for the invocation of the multi-party service by subscriber A;
A common equipment record for the use of the conference bridge by subscriber A.
Each of the MOC/MTC records for the conference originator (A) shall include the supplementary service
code for the multi-party service.
Any subsequent action affecting only one leg of the connection shall be recorded either in a separate
supplementary service action record or in-line in the appropriate CDR. Any action affecting the
conference as a whole e.g. the originator holding the conference shall be recorded either in a separate
supplementary service action record or in the common equipment usage record.
For further information concerning the recording of multi-party services see the example scenario in
subclause 4.2.2.9.
5060 WCS position : the Common equipment records are not supported by the 5060 WCS, and SS-
Action records are not generated for call-related services.
In case of call waiting, the SS code for call waiting is only included in the MTC record generated for the
call placed in call waiting. The initial call does not contain the SS code for call waiting.
In case of call Hold, the MOC generated for A->B contains the Call Hold SS code in the list of suppl.
services.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.1.6 Partial records
In order to increase the security of the recording process and to simplify post-processing, it may be
desirable to generate a sequence of CDRs to describe a single connection or transaction.
In case of connections of extended duration, the loss of a single CDR may result in an unacceptable loss
of revenue. If the connection is, for example, recorded in a number of consecutive partial records
generated at say hourly intervals, then the maximum loss of revenue is the equivalent of a one hour
continuous connection.
Most modern billing systems employ some form of cumulative credit-limit checking based on the stream
of input CDRs. If however, a CDR is only produced at the end of the connection then a subscriber may
avoid such credit checking by employing a connection for days, weeks or even months without a single
CDR being produced.
All of the records defined in TS 32.250 Error! Reference source not found. are of variable length and
some at least are potentially unlimited in size (SET OF, SEQUENCE OF etc.). However, the storage
capacity of the internal records within the network element is normally subject to strict size limitations.
Under such conditions a partial record may be required in order to circumvent internal resource
limitations. For example, if an internal MOC record can only support the use of four supplementary
service invocations then the use of a fifth may result in the generation of a partial record.
Alternatively, for those manufacturers whose systems are based on fixed length records, partial records
may be employed instead of the various lists contained within the present document definitions. In such
cases a partial record will be produced each time one of the key fields alters during the connection.
5060 WCS position : the records generated by the 5060 WCS are variable length records, and the
storage of data in lists is supported.
Finally, in case of radio link failure and subsequent call re-establishment partial records shall be
generated to record the duration of the call prior to the radio link failure and the subsequent duration of
the call once the call has been re-established.
5060 WCS position : call re-establishment is not supported by the 5060 WCS. If a radio link failure
occurs, the call is released and a non-partial CDR is generated for the call.
To summaries, the following events may result in the generation of a partial record:
expiry of the partial record timer;
change of basic service during a connection;
change of location (LAC or Cell Id. Or the Service Access Code, for UMTS) during a connection;
change of MS classmark during a connection;
change of AoC Parameters during a call;
change of Radio Channel Type (full/half rate) during a call;
radio link failure and subsequent call re-establishment;
change of HSCSD Parameters (for GSM only) during a call;
change of CAMEL destination (CAMEL controlled/initiated) during a call.
5060 WCS position : the expiry of the partial record timer and the change of CAMEL destination are is
the only supported criteriona for generating a partial record.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


All partial records for the same connection shall contain the same call reference and shall be ordered via
a running sequence number. The time stamps involved shall apply to the individual partial records rather
than the connection as a whole i.e. the end time stamp (duration) of one record shall, in general,
coincide with the start time stamp (answer time) of the next. Each time a new partial record is created
the cause for termination field of the previous record shall contain the value partial record. The cause for
termination of the final partial record shall contain the true cause for termination of the connection.
It should be noted that the records produced in case of call re-establishment are not contiguous and that
the value of the cause for term field in the record that is closed on radio link failure contains the value
partial record call re-establishment.
5060 WCS position : the previous paragraph is not applicable.
The partial records generated may repeat each of the non-varying fields contained in the original record.
Alternatively, a form of reduced partial record may be generated which includes only those fields required
to identify the original record together with the field(s) that actually change.
5060 WCS position : the partial records repeat each of the non-varying fields.
4.2.1.7 Use of circuit-switched data services
If data services are employed in conjunction with a Packet-Switched Public Data Network (PSPDN) then
an MOC/MTC CDR may be produced in the originating/terminating MSC server and a gateway record in
the gateway/interworking MSC server. If the packet volume is not available within the PLMN then this
information may also be provided in the form of a CDR from the PSPDN. In such cases the Billing System
is responsible for the correlation of the various records describing the connection. The definition of such
PSPDN CDRs is outside the scope of the present document.
5060 WCS position : the volume of data is not provided in the 5060 WCSs CDRs.
4.2.1.8 Inter-MSC server handover
In the case of an inter-MSC server handover the controlling MSC server, as defined by TS 23.009 [8],
remains in control of the connection and shall therefore, produce the CDR. For the avoidance of doubt, it
is not necessary to produce CDRs in the subsequent MSC server(s).
5060 WCS position : a handover is recorded as a change of location in the MOC/MTC record generated
in the controlling MSC server.
Up to 8 locations can be recorded in a MOC/MTC CDR. The first location is recorded in the location
field. The 7 subsequent locations are recorded in the change of location field. In case more than 7
handovers occurred during a call, the MOC/MTC CDR contains the 7 first locations plus the last location
of the call.
All the kinds of handovers are recorded : intra BSC, inter BSC and inter MSC.
Incoming gateway, outgoing gateway and transit records can also be generated for the handover leg,
when the conditions are met to generate them. The incoming/outgoing gateway records are generated in
case the target MSC is in another PLMN, or in the same PLMN but the handover leg uses the PSTN.
They can be used for the settlement of charges between the operators. The fact that they are records
generated for a handover leg is only determined by the called number field which contains a HO number
and the Internal Network Number indicator which is set to 1.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.1.9 Call re-establishment
In case of radio link failure as described in TS 24.008 [9], the MS may attempt to re-establish the call
using the procedures described in TS 24.008 [9].
For the time period between the detection of the radio link failure by the mobile station and the successful
re-establishment of the call, the advice of charge function in the MS is suspended as described in TS
24.086 [10]. In order to minimize the difference in charges between the on-line calculations performed by
the MS and the off-line processing on the basis of the CDRs, it is necessary to exclude the time taken for
the re-establishment phase from the chargeable duration stored in the CDRs.
If the re-establishment attempt fails then an ordinary CDR (MOC/MTC) shall be produced with the cause
for termination value stable call abnormal termination. The chargeable duration stored in this record
covers the time period from Answer to the detection of the radio link failure by the MSC server.
If, the attempt to re-establish the call succeeds then the current CDR shall be closed with the cause for
termination value partial record call re-establishment and a new partial record shall be opened for the
re-established call. The chargeable duration stored in the original record is once again the time period
from answer to detection of the radio link failure by the MSC server. Both the seizure and answer
times of the subsequent partial record correspond to the time at which the new traffic channel is allocated
for the re-established call.
Further radio link failures during the re-established call may result in the generation of additional partial
records as described above. All of the partial records belonging to the same connection are identified by
the same call reference and a running sequence number.
N.B. As the MS and MSC server may detect the radio link failure at different points in time, it is not
possible to guarantee that the duration used for the AOC display corresponds to that recorded in
the CDRs. The purpose of the above procedure is merely to minimize any discrepancies that may
occur.
5060 WCS position : call re-establishment is not supported by the 5060 WCS. If a radio link failure
occurs, the call is released and an ordinary CDR is generated for the call.
4.2.1.10 Restricted directory numbers
In addition to the information pertaining to the served mobile subscriber (IMSI, MSISDN, etc.), the CDRs
defined in the present document also contain the directory numbers of other parties involved in the
recorded connections or transactions. In order to comply with data protection legislation, it is necessary to
distinguish between those numbers that may be passed on to third parties and those that needs to be
handled confidentially. As a result, each of the number fields (e.g. calling/connected number) contains the
presentation and screening information defined in both TS 24.008 [9] and the available trunk signallings
(ISUP,TUP,BICC,SIP). If the network supports this information, then even restricted numbers may be
included in the appropriate records and suppressed off-line by the administration or billing system. If this
information is not supported then the entire directory number shall be suppressed by the MSC
server/VLR.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.1.11 IMEI Observation
In order to provide the data required by the mobile equipment management activities outlined in the
previous subclauses, the MSC server shall be capable of producing IMEI tickets for each of the following
events:
usage of a blacklisted IMEI;
usage of a greylisted IMEI;
usage of an IMEI not found on the white list.
An observed IMEI ticket is generated whenever greylisted, blacklisted or non-whitelisted mobile
equipment is detected during an IMEI check. The purpose of the ticket is to link the mobile equipment
under observation with its current user (IMSI). The ticket also includes information describing when and
where the equipment was used to enable the tracking of such equipment. Finally, if the ticket was
triggered by a call attempt, a call reference is provided in order to locate the corresponding CDR.
The IMEI tickets are generated by the MSC server performing the IMEI check.
5060 WCS position : The IMEI tickets are not generated by the 5060 WCS.
4.2.1.12 Triggers for LCS-MT-CDR, LCS-MO-CDR and LCS-NI-CDR Charging Information
Collection
The LCS CDRs (LCS-MT-CDR, LCS-MO-CDR and LCS-NI-CDR) are used to collect charging information
related to the LCS features that the PLMN provides in the Packet-Switched domain.
These records include details such as Record Type, Served IMSI, Sequence Number etc. The LCS
records are generated based on the following trigger conditions:
the LCS-MO-CDR, when the MSC receives the RANAP Location report message from the RNC;
the LCS-MT-CDR, when the MSC receives the RANAP Location report message from the RNC;
the LCS-NI-CDR, when the MSC receives the RANAP Location report message from the RNC.
5060 WCS position : these kinds of records are not supported by the 5060 WCS.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2 Charging scenarios
This subclause contains a number of example scenarios illustrating the purpose and practical usage of
the various types of records defined in the previous subclauses. These examples are by no means
exhaustive.
For the purpose of these examples, the following assumptions have been made:
that the MSC server and VLR are co-located;
that the records are sent to a post-processing system;
that the generation of all of the record types described in this subclause has been enabled;
that the HLR interrogation records are produced in the HLR and not the interrogating MSC server;
that supplementary service actions are recorded in separate CDRs.
The following conventions have been used for the figures contained within this subclause:
a) Network connections and signalling transactions are illustrated by means of solid lines and
referenced by number e.g. (1).
b) Operation & Maintenance actions, such as the transfer of CDRs, are represented by means of
dotted lines and referenced by letter e.g. (A).
c) The Billing System has been included in some, but not all, of the examples. The only reason for this
decision is to simplify the resulting figures. The presence of a Billing System is assumed even if not
explicitly included.
The following examples are included:
Mobile to Land (outgoing) call;
Land to Mobile (incoming) call;
Mobile to Mobile call within the same network;
Incoming call to a roaming subscriber;
Incoming call to a PLMN Service Centre;
Call Forwarding Unconditional / Call Forwarding conditional (on Busy);
Delivery of a Mobile Terminated Short Message;
Call Hold and Multi-party services;
Outgoing call handled by CAMEL;
Incoming call handled by CAMEL without redirection;
Incoming call to a roaming subscriber handled by CAMEL;
Incoming call handled by CAMEL with redirection decided and forwarding leg handled by CAMEL;
Incoming call handled by CAMEL without redirection and forwarded early using GSM SS but
controlled by CAMEL;
Incoming call handled by CAMEL without redirection and forwarded late using GSM SS but
controlled by CAMEL;
Early forwarded call controlled by CAMEL;
Late forwarded call controlled by CAMEL;
Incoming call handled by CAMEL with redirection imitated by CAMEL feature;
Incoming call handled by CAMEL in MSC Server without redirection;
Outgoing call handled by CAMEL Dialled CSI Trigger;
Incoming call handled by CAMEL with redirection decided and forwarding leg handled by CAMEL;
Mobile terminated location request.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.1 Mobile to land (outgoing) call
Figure 6 illustrates a simple outgoing call from a PLMN subscriber A to a fixed network subscriber B
(1).
The originating MSC server (MSC-A) shall generate an MOC record for subscriber A.
The GMSC server shall create an outgoing gateway record for accounting with the fixed network including
details of the point at which the call left the PLMN i.e. the GMSC server id. And outgoing trunk group. This
record also includes time stamps to determine both the holding time of the outgoing trunk and the
duration of the conversation.
Even if the MSC server (VMSC) and GMSC server are co-located both records shall be produced.
The records generated are subsequently transferred to the Billing System of the PLMN (A).
B
1
1
A
ISDN/PSTN
HPLMN
GMSC
MSC-A
HLR
Billing
System
1
B
A
B
1
1
A
ISDN/PSTN
HPLMN
GMSC GMSC
MSC-A MSC-A
HLR HLR
Billing
System
Billing
System
1
BB
A

Figure 6: Mobile to land (outgoing) call
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.2 Land to mobile (incoming) call
Figure 7 illustrates a simple incoming call from a fixed network subscriber A to a PLMN subscriber B.
The incoming call is first routed to a GMSC server (1). The GMSC server shall create an incoming
gateway record for fixed network accounting purposes to record the point at which the call entered the
network together with the time stamps required to calculate the holding time of the incoming trunk and the
conversation duration. This gateway record shall contain the IMSI of the called subscriber.

The GMSC server interrogates the HLR of the called subscriber in order to determine his current location
(2). The HLR shall create an HLR interrogation CDR.
The GMSC server routes the call to the MSC server at which the subscriber is currently registered (3).
This terminating MSC server (MSC-B) shall create an MTC record for subscriber B.
Even if the MSC server (VMSC) and GMSC server are co-located both the MTC and gateway records
shall be produced.
5060 WCS position : Optionally a HLR-interrogation Record will be created . (RDS6904)
A
3
1
A
ISDN/PSTN
HPLMN
GMSC
MSC-A
HLR
Billing
System
1
B
B
A
2
A
3
1
A
ISDN/PSTN
HPLMN
GMSC GMSC
MSC-A MSC-A
HLR HLR
Billing
System
Billing
System
1
BB
B
A
2

Figure 7: Land to mobile (incoming) call
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.3 Mobile to mobile call within the same network
Figure 8 illustrates a simple mobile to mobile call from subscriber A to subscriber B both within the
same PLMN.
The originating MSC server (MSC-A) shall produce an MOC record for the call to subscriber B.
Having received a set-up request from subscriber A (1), MSC-A interrogates the HLR of the called
subscriber in order to determine his current location (2). The HLR shall create an HLR interrogation CDR.
MSC-A routes the call to the MSC server at which subscriber is currently registered (3). In the TMSCs,
Transit records shall be created.This terminating MSC server (MSC-B) shall create an MTC record for
subscriber B. If MSC-A and MSC-B are co-located, then both the MOC and the MTC records shall be
produced in the same MSC for this call.
The records generated are subsequently transferred to the Billing System of the PLMN.

3
A
HPLMN
TMSC
MSC-A
HLR
Billing
System
B
A
A
MSC-B
B
B
2
A
3
1
3
3
A
HPLMN
TMSC TMSC
MSC-A MSC-A
HLR HLR
Billing
System
Billing
System
BB
A
A
MSC-B MSC-B
BB
B
2
A
3
1
3

Figure 8: Mobile to mobile call
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.4 Incoming call to a roaming subscriber
Figure 9 illustrates an incoming call from a fixed network subscriber A to a PLMN subscriber B who is
currently roaming in another PLMN.
The call is first routed to a GMSC server (1) and the GMSC server shall create an incoming gateway
record for accounting purposes as described in subclause 4.2.2.2. The GMSC server interrogates the
HLR of the called subscriber in order to determine his current location (2). The HLR shall create an
Interrogation event record.
The GMSC server routes the call to the VPLMN in which subscriber B is currently located (3). The
GMSC server shall create an outgoing gateway record for accounting purposes. The GMSC server shall
also create a roaming record. This record includes the IMSI of the B subscriber and may be used as a
cross-check for the TAP information received from the VPLMN.
Note: IMSI is defined as Optional parameter in roaming record.
The call is then routed by the VPLMN to the MSC server at which the subscriber is currently located (4).
The GMSC server of the VPLMN shall produce an incoming gateway record and the terminating MSC
server shall create an MTC record for the call to B.
The records generated are subsequently transferred to the Billing System of the appropriate PLMN (A).
The MTC record generated by the terminating MSC server shall be employed to create the appropriate
MTC TAP record. The TAP records shall be included in a TAP file and transmitted to the HPLMN (B).
5060 WCS position : Optionally a Roaming record will be generated. (RDS6904)
HPLMN
GMSC
HLR
Billing
System
A
2
3
4
A
VPLMN
GMSC
MSC-B
Billing
System
B
B
4
A
1
ISDN/PSTN
1
4
A B
HPLMN
GMSC GMSC
HLR HLR
Billing
System
Billing
System
A
2
3
4
A
VPLMN
GMSC GMSC
MSC-B MSC-B
Billing
System
Billing
System
BB
B
4
A
1
ISDN/PSTN
1
4
A B

Figure 9: Incoming call to a roaming subscriber
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.5 Incoming call to a PLMN service centre
Figure 10 illustrates an incoming call from a fixed network subscriber A to a Service Centre directly
connected to an MSC server within a PLMN network. Examples for services provided by such a Service
Centre include Voice Mail services, Operator services, etc.
The call is routed to a GMSC server within the PLMN (1). The GMSC server analyses the dialled digits
and routes the call directly to the MSC server to which the Service Centre is connected (2).
As HLR interrogation is not required, there will be no HLR Interrogation record. The GMSC server shall
however, create an incoming gateway record based on the point at which the call entered the network
and the destination (Service Centre) of the call.
The MSC server then connects the calling subscriber to the service centre. As no mobile subscriber is
involved, the MSC server will not create an MTC record, however, the MSC server shall create a transit
record describing the destination of the call.
It should be noted that without the transit record, the MSC server would not generate a record for this
connection.
A
1
ISDN/PSTN
HPLMN
GMSC
Transit
MSC
Billing
System
1
2
Service
Center
A
2
A
A
1
ISDN/PSTN
HPLMN
GMSC GMSC
Transit
MSC
Billing
System
Billing
System
1
2
Service
Center
Service
Center
A
2
A

Figure 10: Incoming call to a PLMN service centre
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.6 Call forwarding unconditional
Figure 11 illustrates an incoming call from a fixed network subscriber A to a mobile subscriber B who
has registered and activated Call Forwarding Unconditional (CFU) for the appropriate service. The call is
subsequently forwarded to a second fixed network subscriber C.
For simplicity the registration and activation of CFU have not been included in the diagram. These actions
shall of course be recorded in the appropriate supplementary service records.
The incoming call is routed to a GMSC server (1). This part of the connection is identical to the scenario
outlined in subclause 4.2.2.2.
The GMSC server interrogates the HLR of the called subscriber in order to determine his current location
(2). The HLR shall create an HLR interrogation CDR. The HLR informs the GMSC server that B has
activated CFU to subscriber C.
The GMSC server forwards the call to the fixed network subscriber C (3). The GMSC server shall create
an MTC (call forwarding) record for the B subscriber for the call from A and an MOC (call forwarding)
record for the B subscriber for the call to C. Both records shall contain the supplementary service
employed (CFU). The GMSC server shall also produce an outgoing gateway record as described in
subclause 4.2.2.1.
The records generated are subsequently transferred to the Billing System of the HPLMN (A).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


A
1
ISDN/PSTN
HPLMN
GMSC
MSC
HLR
Billing
System
1
B
B
A
2
3
C
3
A
1
ISDN/PSTN
HPLMN
GMSC GMSC
MSC MSC
HLR HLR
Billing
System
Billing
System
1
BB
B
A
2
3
C
3

Figure 11: Call forwarding unconditional
4.2.2.7 Call forwarding conditional (on busy)
Figure 12 illustrates a mobile originated call from subscriber A to a second mobile subscriber B who
has registered and activated Call Forwarding on Busy (CFB) for the appropriate service. The call is
subsequently forwarded to a third mobile subscriber C. In this example, all three subscribers are
currently located within the same (the home) network.
For simplicity the registration and activation of CFB have not been included in the diagram.
Having received a set-up request from subscriber A (1), the originating MSC server (MSC-A)
interrogates the HLR of subscriber B in order to determine his current location (1a). The call is then
routed to MSC-B (2).
MSC-A shall create an MOC record for subscriber A containing details of the call to B. The HLR shall
produce an HLR interrogation record.
On determining that subscriber B is busy and that CFB is active, the forwarding MSC server/VLR (MSC-
B) interrogates the HLR of subscriber C to determine his current location (2a) and forwards the call
accordingly (3).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


MSC-B shall produce an MTC record for the B subscriber for the call from A and an MOC record
(MOC-CF) for the B subscriber for the call to C. Both records shall include the supplementary service
employed (CFB). The HLR shall produce an Interrogation record.
The terminating MSC server (MSC-C) shall create a normal MTC record for subscriber C.
The records generated are subsequently transferred to the Billing System of the PLMN.

2
HPLMN
MSC-B
MSC-A
HLR
B
A
MSC-C
1
3
B
B
B
C
busy
3
2a
1a
2
HPLMN
MSC-B MSC-B
MSC-A MSC-A
HLR HLR
BB
A
MSC-C MSC-C
1
3
BB
B
BB
C
busy
3
2a
1a

Figure 12: Call forwarding conditional (busy)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.8 Delivery of a mobile terminated short message
Figure 13 illustrates the delivery of a short message to a mobile subscriber.
The short message service centre delivers the message to a GMSC server or gateway function (1). The
GMSC server shall create an SMS gateway MT record.
The GMSC server then interrogates the HLR of the subscriber to determine his current location (2). The
HLR shall create an HLR interrogation record.
5060 WCS position : the 5060 WCS does not support the SMS gateway function.
The message is subsequently transmitted to the MSC server serving the mobile subscriber and finally to
the mobile station of that subscriber (3). The MSC server shall create an SMS MT record.
The records generated are subsequently transferred to the post-processing system of the HPLMN (A).

HPLMN
SMS-
GMSC
MSC-B
HLR
Billing
System
B
B
A
2
SMS-SC
1
3
A
HPLMN
SMS-
GMSC
MSC-B MSC-B
HLR HLR
Billing
System
Billing
System
BB
B
A
2
SMS-SC SMS-SC
1
3
A

Figure 13: Delivery of a short message to a mobile subscriber
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.9 Call hold and multi-party service
Figure 14 illustrates the use of the call hold and multi-party services.
A mobile subscriber (A) sets up an outgoing call (1) to an ISDN subscriber (B). This call is recorded as
outlined in subclause 4.2.2.1. Subscriber A then invokes the call hold service. MSC-A shall produce a
supplementary service action record for the invocation.
5060 WCS position : the supplementary service action records are not generated by the 5060 WCS for
the invocation of services. Instead, the MOC generated for A->B contains the Call Hold SS code in the list
of supplementary services.
Subscriber A then sets up a side-call (2) to a second mobile subscriber (C) within the same network.
This call is recorded as outlined in subclause 4.2.2.3.
Subscriber A subsequently invokes the multi-party service in order to set up a three-party conference
with B and C. MSC-A shall produce a common equipment record for the use of a conference circuit by
subscriber A. This record shall record the duration of the whole conference irrespective of the number of
parties subsequently added to, or removed from the conference connection.
Note that the MOC records produced by MSC-A for both the A -> B and A -> C legs of the conference
shall contain the supplementary service code for multi-party.
5060 WCS position : the common equipment records are not generated by the 5060 WCS.

1
A
HPLMN
GMSC
MSC-A
Billing
System
B
A
A
MSC-C
B
C
1
2
B
1
ISDN/PSTN
1
2
1
A
HPLMN
GMSC GMSC
MSC-A MSC-A
Billing
System
Billing
System
BB
A
A
MSC-C MSC-C
BB
C
1
2
B
1
ISDN/PSTN
1
2

Figure 14: Call hold and multi-party service
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.10 Outgoing call handled by CAMEL
Figure 15 illustrates an outgoing CAMEL call from a mobile CAMEL subscriber A to a fixed network
subscriber B (1). The A subscriber has an active O-CSI (stored in the VLR). Therefore MSC server-A
requests instructions from the gsmSSF which passes the CAMEL service key to the gsmSCF to indicate
which service logic it should apply (2). The gsmSCF may interrogate the HLR for subscriber information.
As a network option, the operator may refuse to provide the requested information.
When gsmSCF processing is complete the call control is returned to MSC-A.
MSC server-A generates an MOC record for the A subscriber. This record may be linked to an optional
SCF-record. The record includes O-CSI data. The GMSC server routes the call to the B subscriber (3).
The GMSC server shall create an outgoing gateway record as described in subclause 4.2.2.1.
The generated records are subsequently transferred to the Billing System of the HPLMN (A).
The following records are generated in HPLMN in this call scenario.
Table 1: Records Generated for an Outgoing Call Handled by CAMEL
GMSC server MSC server HLR
Outgoing gateway record MOC record -

ISDN/PSTN
A
MSC-A/
gsmSSF
GMSC/
gsmSSF
gsmSCF
B
Billing
System
A
1
2
3
O- CSI(A-B)
3
HPLMN
HLR
ISDN/PSTN
A
MSC-A/
gsmSSF
GMSC/
gsmSSF
gsmSCF
B
Billing
System
A
1
2
3
O- CSI(A-B)
3
HPLMN
HLR

Figure 15: Outgoing call handled by CAMEL
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.11 Incoming call handled by CAMEL without redirection
Figure 16 illustrates an incoming call from a fixed network subscriber A to a mobile CAMEL subscriber
B. The incoming call is first routed to the GMSC server (1). The GMSC server shall create an incoming
gateway record for fixed network accounting purposes.The GMSC server interrogates the HLR of the
called subscriber in order to fetch the T-CSI (2). The HLR shall create an HLR interrogation record. The
B subscriber has an active T-CSI. Therefore the GMSC server requests instructions from the gsmSSF
which passes the CAMEL service key to a gsmSCF to indicate which service logic it should apply (3). The
gsmSCF may interrogate the HLR for subscriber information. As a network option, the operator may
refuse to provide the requested information. When gsmSCF processing is complete the call control is
returned to the GMSC server. The GMSC server shall generate a terminating CAMEL record which
contains T-CSI data. The GMSC server interrogates the HLR in order to determine his current location(4).
The HLR shall create an HLR interrogation record. The call is routed to MSC-B (5). An MTC record shall
be generated. For avoidance of doubt, even if the MSC server and GMSC server are co-located both the
MTC and gateway records shall be produced. The generated records are subsequently transferred to the
Billing System of the HPLMN (A). The following records are generated in HPLMN in this call scenario.
Table 2: Records Generated for an Incoming Call Handled by CAMEL without Re-direction
Incoming gateway record MTC record HLR interrogation record
Terminating CAMEL record
5060 WCS position : the GMSC creates optionally a HLR-interrogation Record (RDS6904)

ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC/
gsmSSF
gsmSCF
A
Billing
System
A
1
2
5
T-CSI(A-B)
3
1
6
4
HLR
ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC/
gsmSSF
gsmSCF
A
Billing
System
A
1
2
5
T-CSI(A-B)
3
1
6
4
HLR

Figure 16: Incoming call handled by CAMEL without redirection
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.12 Incoming call to a roaming subscriber handled by CAMEL
B who is currently roaming in another PLMN.
The call is first routed to a GMSC server (1) and the GMSC server shall create an incoming gateway
record for fixed network accounting purposes.
The GMSC server interrogates the HLR of the called subscriber in order to fetch the T-CSI (2). The HLR
shall create an HLR interrogation record.
The B subscriber has an active T-CSI. Therefore the GMSC server requests instructions from the
gsmSSF which passes the CAMEL service key to a gsmSCF to indicate which service logic it should
apply (3).
The gsmSCF may interrogate the HLR for subscriber information. As a network option, the operator may
refuse to provide the requested information.
When gsmSCF processing is complete the call control is returned to the GMSC server . The GMSC
server shall generate a terminating CAMEL record which contains T-CSI data.
The GMSC server interrogates the HLR in order to determine his current location (4). The HLR shall
create an HLR interrogation record.
The GMSC server routes the call to the VPLMN in which subscriber B is currently located (5). The
GMSC server shall create an outgoing gateway record for accounting purposes. The GMSC server shall
also create a roaming record. This record include the IMSI of the B subscriber and may be used as a
cross-check for the TAP information received from the VPLMN.
Note: IMSI is defined as Optional parameter in roaming record.
The call is then routed by the VPLMN to the MSC server at which the subscriber is currently located (6).
The GMSC server of the VPLMN shall produce an incoming gateway record and the terminating MSC
server shall create an MTC record for the call to B.
The records generated are subsequently transferred to the Billing System of the appropriate PLMN (A).
The MTC record generated by the terminating MSC server shall be employed to create the appropriate
MTC TAP record. The TAP records shall be included in a TAP file and transmitted to the HPLMN (B).
Table 3: Records Generated in the HPLMN for an
Incoming Call to a Roaming Subscriber Handled by CAMEL
Incoming gateway record - HLR interrogation record
Roaming record
Outgoing gateway record

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


The following records are generated in VPLMN in this call scenario.
Table 4: Records Generated in the VPLMN for an
Incoming Call to a Roaming Subscriber Handled by CAMEL
Incoming gateway record MTC record -

5060 WCS position : the GMSC creates optionally a Roaming record and a HLR-interrogation Record
(RDS6904)

ISDN/PSTN
B
GMSC/
gsmSSF
gsmSCF
A
Billing
Syst em
A
1
2
5
T-CSI (A-B)
3
1
6
4
GMSC/
gsmSSF
MSC-B/
gsmSSF
Billing
Syst em
gsmSCF
5
6
B A
HPLMN VPLMN
HLR
ISDN/PSTN
B
GMSC/
gsmSSF
gsmSCF
A
Billing
Syst em
A
1
2
5
T-CSI (A-B)
3
1
6
4
GMSC/
gsmSSF
MSC-B/
gsmSSF
Billing
Syst em
gsmSCF
5
6
B A
HPLMN VPLMN
HLR

Figure 17: Incoming call to a roaming subscriber handled by CAMEL
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.13 Incoming call handled by CAMEL with redirection decided and forwarding leg handled by
CAMEL
B. The call is subsequently forwarded to a second fixed network subscriber C by CAMEL initiated Call
Forwarding.
The incoming call is routed to the GMSC server (1). The GMSC server shall create an incoming gateway
The GMSC server interrogates the HLR of the called subscriber in order to fetch the T-CSI and O-CSI (2).
apply (3).
The gsmSCF modifies the Called Party number and sets the CAP parameter Apply O-CSI. When
gsmSCF processing is complete the call control is returned to the GMSC server. The GMSC server shall
generate a terminating CAMEL record which contains T-CSI data.
The B subscriber has an active O-CSI. Therefore the GMSC server requests instructions from the
apply (4).
When gsmSCF processing is complete the call control is returned to the GMSC server.
The GMSC server redirects the call to the fixed network subscriber C (5). The GMSC server shall
generate an MTC record for the B subscriber for the call from A and an MOC (call forwarding) (Note 1)
record for the B subscriber for the call to C. The MOC record includes O-CSI data and the parameter
CAMEL initiated CF indicator. The GMSC server shall also produce an outgoing gateway record as
described in subclause 4.2.2.1.
Table 5: Records Generated in the Incoming Call with
Redirection Decided and Forwarded Leg Handled by CAMEL
MTC record
MOC (CF) record (Note 1)
Note 1: MOC (CF) Record means in this case, that we have a MOC-record with parameter CAMEL
initated CF indicator.
5060 WCS position : the GMSC creates optionally a HLR-interrogation Record (RDS6904)

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC/
gsmSSF
gsmSCF
A
Billing
System
A
1
2 3
4
T-CSI(A-B)
O- CSI(B-C)
C
5
1 5
HPLMN
HLR
ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC/
gsmSSF
gsmSCF
A
Billing
System
A
1
2 3
4
T-CSI(A-B)
O- CSI(B-C)
C
5
1 5
HPLMN
HLR

Figure 18: Incoming call handled by CAMEL with redirection decided
and forwarding leg handled by CAMEL
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.14 Incoming call handled by CAMEL without redirection and forwarded early using GSM SS
but controlled by CAMEL
B. The call is subsequently forwarded to a second fixed network subscriber C by GSM SS Call
Forwarding Unconditional (CFU) but controlled by CAMEL.
For simplicity the activation and registration of CFU have not been included in the diagram. These actions
shall of course be registered in the appropriate supplementary service records.
The HLR shall create an HLR interrogation record. The HLR informs the GMSC server that B has
activated CFU.
apply (3).
When gsmSCF processing is complete the call control is returned to the GMSC server. The GMSC server
shall generate a terminating CAMEL interrogation record which contains T-CSI data.
The B subscriber has an active O-CSI. Because the B subscriber has activated CFU he acts as the
originating party for the forwarded leg. Therefore the GMSC server requests instructions from the
apply (5).
generate an MTC record for the B subscriber for the call from A and an MOC (call forwarding) record
for the B subscriber for the call to C. The MOC record includes O-CSI data. The GMSC server shall
also produce an outgoing gateway record as described in subclause 4.2.2.1.
If the B-subscriber does not have an active O-CSI the call is forwarded to the C subscriber after the first
gsmSCF invocation.
Table 6: Records Generated in the Incoming call handled by CAMEL without redirection
and forwarded early using GSM SS but controlled by CAMEL
MTC (CF) record
MOC (CF) record

5060 WCS position : the GMSC creates (optionally) a HLR-interrogation Record (RDS6904)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC/
gsmSSF
gsmSCF-A
A
Billing
System
A
1
2
3
T-CSI(A-B)
O- CSI(B-C)
4
C
5
1 5
CFU activated
HPLMN
HLR
ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC/
gsmSSF
gsmSCF-A
A
Billing
System
A
1
2
3
T-CSI(A-B)
O- CSI(B-C)
4
C
5
1 5
CFU activated
HPLMN
HLR

and forwarded early using GSM SS but controlled by CAMEL
4.2.2.15 Incoming call handled by CAMEL without redirection and forwarded late using GSM SS
but controlled by CAMEL
B who has registered and activated Call Forwarding on No Reply (CFNRY) for the appropriate service.
The call is subsequently forwarded to a second fixed network subscriber C.
For simplicity the registration and activation of CFNRY have not been included in this diagram. These
actions shall be recorded in the appropriate supplementary service records.
The HLR shall create an HLR interrogation record.
gsmSSF which passes the CAMEL service key to the gsmSCF to indicate which service logic it should
apply (3).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


When gsmSCF processing is complete the call control is returned to the GMSC server. The GMSC server
shall generate a terminating CAMEL interrogation record which contains T-CSI data.
The GMSC server interrogates the HLR in order to determine his current location (4). The HLR shall
create an HLR interrogation record.
The call is routed to MSC-B (5). The B subscriber does not answer the call. MSC-B shall produce an
MTC (call forwarding) record for the B subscriber for the call from A.
The B subscriber has an active O-CSI. Because the B subscriber has activated CFNRY he acts as the
originating party for the forwarded leg. Therefore MSC-B requests instructions from the gsmSSF which
passes the CAMEL service key to the gsmSCF to indicate which service logic it should apply (6).
When gsmSCF processing is complete the call control is returned to MSC-B.
MSC-B forwards the call via the GMSC server to the C subscriber (7). MSC-B shall produce an MOC
(call forwarding) for the B subscriber for the call to C. The record includes O-CSI data. The GMSC
server shall also produce an outgoing gateway record as described in subclause 4.2.2.1.
If the B-subscriber does not have an active O-CSI the call is forwarded to the C subscriber after
detecting the call forwarding condition.
Table 7: Records Generated in the Incoming call handled by CAMEL without redirection
and forwarded late using GSM SS but controlled by CAMEL
Incoming gateway record MTC (CF) record -
Terminating CAMEL record MOC (CF) record


A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC/
gsmSSF
gsmSCF
A
Billing
System
A
1
2
3
4
T-CSI(A-B)
O- CSI(B-C)
C
5
6
1
CFNRY Activated
7
Call attempt
7
7
HPLMN
HLR
ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC/
gsmSSF
gsmSCF
A
Billing
System
A
1
2
3
4
T-CSI(A-B)
O- CSI(B-C)
C
5
6
1
CFNRY Activated
7
Call attempt
7
7
HPLMN
HLR

and forwarded late using GSM SS but controlled by CAMEL
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.16 Early forwarded call controlled by CAMEL
B. The call is subsequently forwarded to a second fixed network subscriber C by GSM SS Call
Forwarding Unconditional (CFU) but controlled by CAMEL.
For simplicity the activation and registration of CFU have not been included in the diagram. These actions
shall of course be registered in the appropriate supplementary service records.
The GMSC server interrogates the HLR of the called subscriber in order to fetch the O-CSI (2). The HLR
shall create an HLR interrogation record. The HLR informs the GMSC server that B has activated CFU.
The B subscriber has an active O-CSI. Because the B subscriber has activated CFU he acts as the
originating party for the forwarded leg. Therefore the GMSC server requests instructions from the
apply (3).
generate an MTC (call forwarding) record for the B subscriber for the call from A and an MOC (call
forwarding) record for the B subscriber for the call to C. The MOC record includes O-CSI data. The
GMSC server shall also produce an outgoing gateway record as described in subclause 4.2.2.1.
Table 8: Records Generated in the Early forwarded call controlled by CAMEL
MTC (CF) record
MOC (CF) record

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


ISDN/PSTN
B
MSC-B/
gs mSSF
GMSC/
gs mSSF
gsmSCF-A
A
Billing
System
A
1
2
3
O-CSI (B-C)
C
4
1 4
CFU acti vated
HPLMN
HLR
ISDN/PSTN
B
MSC-B/
gs mSSF
GMSC/
gs mSSF
gsmSCF-A
A
Billing
System
A
1
2
3
O-CSI (B-C)
C
4
1 4
CFU acti vated
HPLMN
HLR

Figure 21: Early forwarded call controlled by CAMEL
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.17 Late forwarded call controlled by CAMEL
B who has registered and activated Call Forwarding on No Reply (CFNRY) for the appropriate service.
The call is subsequently forwarded to a second fixed network subscriber C.
For simplicity the registration and activation of CFNRY have not been included in this diagram. These
actions shall be recorded in the appropriate supplementary service records.
The GMSC server interrogates the HLR of the called subscriber in order to determine the current location
(2). The HLR shall create an HLR interrogation record.
The call is routed to MSC-B (3). The B subscriber does not answer the call. MSC-B shall produce an
MTC (call forwarding) record for the B subscriber for the call from A.
The B subscriber has an active O-CSI. Because the B subscriber has activated CFNRY he acts as the
originating party for the forwarded leg. Therefore MSC-B requests instructions from the gsmSSF which
passes the CAMEL service key to gsmSCF-B to indicate which service logic it should apply (4).
When gsmSCF processing is complete the call control is returned to MSC-B.
MSC-B forwards the call via the GMSC server to the C subscriber (5). MSC-B shall produce an MOC
(call forwarding) for the B subscriber for the call to C. The record includes O-CSI data. The GMSC
server shall also produce an outgoing gateway record as described in subclause 4.2.2.1.
Table 9: Records Generated in the Late forwarded call controlled by CAMEL
Incoming gateway record MTC (CF) record HLR interrogation record
Outgoing gateway record MOC (CF) record


A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC/
gsmSSF
gsmSCF
A
Billing
System
A
1
2
4
3
O- CSI(B-C)
C
5
1 5
CFNRY activated
5
Call at tempt
HPLMN
HLR
ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC/
gsmSSF
gsmSCF
A
Billing
System
A
1
2
4
3
O- CSI(B-C)
C
5
1 5
CFNRY activated
5
Call at tempt
HPLMN
HLR

Figure 22: Late forwarded call controlled by CAMEL
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.18 Incoming call handled by CAMEL with redirection initiated by CAMEL feature
B. The call is subsequently redirected to a second fixed network subscriber C by CAMEL initiated
redirection.
The GMSC server interrogates the HLR of the called subscriber in order to fetch the T-CSI (2) and the O-
CSI (2). The HLR shall create an HLR interrogation record.
Since subscriber B has an active T-CSI and the trigger criteria are met the GMSC server requests
instructions from the gsmSSF which passes the CAMEL service key to a gsmSCF to indicate which
service logic it should apply (3). A terminating CAMEL interrogation record is generated in the GMSC
server for invoking the terminating CAMEL call handling.
The gsmSCF returns a modified destination routing address to the GMSC server (without the option
apply O-CSI). Therefore for the redirection leg (B-C) the CAMEL feature is not invoked.
The GMSC server redirects the call to the fixed network subscriber C (4). For fixed network accounting
purposes the GMSC server shall generate an outgoing gateway record as described in subclause 4.2.2.1.
5060 WCS position : An MTC and an MOC are generated for B in the GMSC. The MOC contains the
address of C received in the CONNECT operation.
Restriction:
In case of CAMEL CF and no O-CSI, MOC will be suppressed for PRBT with CAMEL CF solution.

Table 10: Records Generated in the Incoming call handled by CAMEL
with redirection initiated by CAMEL feature
Incoming gateway record HLR interrogation record
Terminating CAMEL
interrogation record

MTC
MOC (cond., see above)


A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC/
gsmSSF
gsmSCF-A
A
Billing
System
A
1
2
3
T-CSI (A-B)
C
4
1 4
HPLMN
HLR
O-CSI (B-C)
ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC/
gsmSSF
gsmSCF-A
A
Billing
System
A
1
2
3
T-CSI (A-B) T-CSI (A-B)
C
4
1 4
HPLMN
HLR
4
1 4
HPLMN
HLR
4
1 4
HPLMN
HLR
1 4
HPLMN
HLR
4
HPLMN
HLR HLR HLR HLR
O-CSI (B-C) O-CSI (B-C)

Figure 23: Incoming call handled by CAMEL with redirection initiated and by CAMEL feature
4.2.2.19 CAMEL Scenario for Visiting Terminator Trigger Calls
Figure 24 illustrates an inc-call from a fixed network subscriber A to a mobile CAMEL subscriber B.
The incoming call is first routed to the GMSC (1). The GMSC shall create an incoming gateway record for
fixed network accounting purposes.
The GMSC interrogates the HLR (2) of the called subscriber. The HLR shall create an HLR interrogation
record. The call is routed to MSC-B(3). An MTC record shall be generated in MSC-B.
The B subscriber has an active VT-CSI (stored in the VLR). For avoidance of doubt in this scenario, the
B subscriber does not have an active T-CSI in the HLR. Therefore MSC-B requests instructions from the
gsmSSF which passes the CAMEL service key to the gsmSCF to indicate which service logic it should
apply (4).
When gsmSCF processing is complete the call control is returned to the MSC-B. The MSC-B shall
generate a terminating CAMEL (TCR) record which contains VT-CSI data.
Note: Concerning the support of VT-CSI inside 5060 WCS, please refer to document [31].
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


The MSC-B routes the call to the B subscriber (5).
For avoidance of doubt, even if the MSC and GMSC are co-located both the MTC/TCR and gateway
records shall be produced.
The generated records are subsequently transferred to the OS (A) either as event reports following the
release of the connection or when collected by the OS.
Table 11: Records Generated for Visiting Terminating Trigger Calls
GMSC MSC-B HLR
Incoming gateway record MTC record HLR interrogation record


ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC/
gsmSSF
gsmSCF
A
ADC/BC
A
1
2
5
VT-CSI(A-B)
3
1
4
HLR

Figure 24: Incoming call handled by CAMEL in MSC Server without redirection
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.20 Outgoing call handled by CAMEL with Dialled CSI Trigger
Figure 25 illustrates an outgoing CAMEL call from a mobile CAMEL subscriber A to a fixed network
subscriber B (1).
The A subscriber has an active D-CSI (stored in the VLR and modified Called Party number matches D-
CSI). Therefore MSC server-A requests instructions from the gsmSSF which passes the CAMEL service
key to the gsmSCF to indicate which service logic it should apply (2).
When gsmSCF processing is complete the call control is returned to MSC-A.
MSC server-A generates an MOC record for the A subscriber which contains D-CSI data. This record
may be linked to an optional SCF-record.
The GMSC server routes the call to the B subscriber (3). The GMSC server shall create an outgoing
gateway record as described in TS 32.250 Error! Reference source not found..
The generated records are subsequently transferred to the post-processing system (A) either as event
reports following the release of the connection or when collected by the post-processing system.
Table 12: Records Generated for an Outgoing Call Handled by CAMEL
Outgoing gateway record MOC record -

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


ISDN/PSTN
A
MSC-A/
gsmSSF
GMSC
gsmSSF
gsmSCF
B
Billing
System
A
1
2
3
3
HPLMN
HLR
ISDN/PSTN
A
MSC-A/
gsmSSF
GMSC
gsmSSF
gsmSCF
B
Billing
System
A
1
2
3
D-CSI(A-B)
3
HPLMN
HLR

Figure 25: Outgoing call handled by CAMEL with Dialled CSI Trigger
4.2.2.21 Incoming call handled by CAMEL with redirection decided and forwarding leg handled by
CAMEL with Dialled CSI Trigger
B. The call is subsequently forwarded to a second fixed network subscriber C by CAMEL initiated Call
Forwarding.
The GMSC server interrogates the HLR of the called subscriber in order to fetch the T-CSI, O-CSI and D-
CSI (2).
apply (3).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


The gsmSCF modifies the Called Party number and sets the CAP parameter Apply O-CSI. When
gsmSCF processing is complete the call control is returned to the GMSC server. The GMSC server shall
generate a terminating CAMEL interrogation record which contains T-CSI data.
The B subscriber has an active O-CSI. Therefore the GMSC server requests instructions from the
apply (4).
The gsmSCF modifies the Called Party number. When gsmSCF processing is complete the call control is
returned to the GMSC server.
The B subscriber has an active D-CSI (modified Called Party number matches D-CSI). Therefore the
GMSC server requests instructions from the gsmSSF which passes the CAMEL service key to a gsmSCF
to indicate which service logic it should apply (5).
refuse to provide the requested information. When gsmSCF processing is complete the call control is
returned to the GMSC server.
generate an MTC record for the B subscriber for the call from A and an MOC (call forwarding)(Note1)
record for the B subscriber for the call to C. The MOC record includes O-CSI data, the parameter
CAMEL initiated CF indicator and D-CSI data. The GMSC server shall also produce an outgoing
gateway record as described in TS 32.250 Error! Reference source not found..
The generated records are subsequently transferred to the post-processing system (A) either as event
reports following the release of the connection or when collected by the post-processing system.
Table 13: Records Generated in the Incoming Call with
Redirection Decided and Forwarded Leg Handled by CAMEL
MTC record
MOC (CF) record (Note 1)
Note 1: MOC (CF) Record means in this case, that we have a MOC-record with parameter CAMEL
initated CF indicator.


A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC
gsmSSF
gsmSCF
A
Billing
System
A
1
2 3
4
T-CSI( -B)
O-CSI(B-C)
C
5
1 5
HPLMN
HLR
ISDN/PSTN
B
MSC-B/
gsmSSF
GMSC
gsmSSF
gsmSCF
A
Billing
System
A
1
2 3
4
T-CSI(A-B)
C
6
1 6
HPLMN
HLR
5 5
O-CSI(B-C)
D-CSI(B-C)

Figure 26: Incoming call handled by CAMEL with redirection decided
and forwarding leg handled by CAMEL with Dialled CSI Trigger
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.22 Mobile terminated location request
Figure 27 illustrates general network positioning for LCS clients external to the PLMN.
An external LCS client requests the current location of a target UE from a GMLC (1). In this release the
GMLC shall not create any LCS record.
The GMLC server then interrogates the HLR of the target UE to be located to determine his current
location (2). The HLR shall create an HLR interrogation record.
The GMLC sends the location service request to the MSC indicated by the HLR. The MSC sends a
Location Request message to RAN that initiates the positioning procedure (3). The MSC shall create an
LCS-MT record.
5060 WCS position : no record is created for this scenario.

HPLMN
SM -
GMS
MS - B
HLR
Billin
Syste
B
B
A
2
SM - SC
1
3
A
HPLMN
GMLC
S
MS - B MSC
C
HLR HLR
Billin
Syste
Billing
System
B B
B
A
2
SM - SC
LCS
client
1
3
A

Figure 27: Mobile terminated location request

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.23 Mobile to land (outgoing) call, handovers
The situation is the same as in section 4.2.2.1. The subscriber is moving during the call, and an inter
MSC handover occurs.
The MOC CDR generated at the end of the call contains :
- in the location field, the location of the subscriber at the beginning of the call
- in the change of location field, the location of the subscriber after the handover, and the
timestamp of the handover (reception of the ANM message on the handover leg)
- If another inter MSC handover occurs, the new location and timestamp are recorded also in the
change of location field, next to the previous location.
Up to eight locations can be recorded in a MOC or MTC record; the first one in the location field, and the
next ones in the change of location field.
If the MS already changed of location seven times (hence eight location are available), and changes of
location once more, then the last location in the MOC/MTC is overwritten with the new location.
All the kinds of handovers are recorded.
4.2.2.24 Mobile to land (outgoing) call, inter PLMN handover
The situation is the same as in section 4.2.2.1. The subscriber is moving during the call, and an inter
MSC handover occurs. The target MSC is in a different PLMN as the controlling MSC.

SM -
MS - B
B
B
HPLMN
GMSC-A
MS
MSC-A
B B
B
FPLMN
MSC-B
B
B
B B
B
SM -
GMSC-B
1
2
2
2

First, the HO number is obtained from MSC-B, then the HO leg is created between MSC-A and MSC-B.
The CDR generated by MSC-A is exactly the same as described in 4.2.2.23.
If the inter-network trunk group characteristic is set on the trunk group used to route the call to GMSC-B,
then the GMSC-A generates an outgoing gateway CDR.
If the inter-network trunk group characteristic is set on the trunk group coming from the GMSC-A, then
the GMSC-B generates an incoming gateway CDR.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.25 Short Message Service originating
A MS sends a Short Message.
The short message is forwarded to the SMS interworking gateway.
The VMSC generates a Short Message Service originating with the following information (non
exhaustive) :
- the message reference
- the result of the Short Message delivery
- the Short Message destination address
The 5060 WCS does not generate SMS-MO interworking CDRs.
4.2.2.26 Short Message Service originating with CAMEL invocation
A MS sends a Short Message.
The short message is forwarded to the SMS interworking gateway.
The VMSC generates a Short Message Service originating with the following information (non
exhaustive) :
- the message reference
- the result of the Short Message delivery
- the Short Message destination address
- The CAMEL information :
o SCFAddress, serviceKey, defaultSMSHandling as present in the SMS-CSI
o The calling party number if modified by the SCP
o The destination subscriber number if modified by the SCP
o The Service Centre if modified by the SCP
o The SMS reference number if modified by the SCP
o The Free Format Data if received from the SCP in a FCI operation
The 5060 WCS does not generate SMS-MO interworking CDRs.
4.2.2.27 Emergency call
A MS does an emergency call, by issuing an Emergency SETUP message.
The VMSC generates an originated call CDR as in section 4.2.2.1.
The Served IMSI is present in the record only if the information is available. It depends on the presence of
the SIM card in the Mobile phone.
The Basic service is set with the Emergency call teleservice. This information permits to differentiate the
CDRs for emergency calls from the CDRs for ordinary calls.
4.2.2.28 Multiple call forwarding in the same GMSC
In case of an incoming call towards B, B forwarded unconditionnaly to C, C forwarded unconditionnaly to
D, the CDRs MTC(B), MOC(B), MTC(C), MOC(C) all contain :
- information on the incoming trunk group and termination used for the A-B call
- information on the outgoing trunk group and termination used for the C-D call
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.29 Multiple call forwarding in the same VMSC
The same principle as described in section 4.2.2.28 applies in a VMSC, in case of multiple conditional call
forwarding by subscribers located in the same VMSC.
4.2.2.30 Originating call with IN-CS1 invocation Continue

HLR MSC SCP
Fixed
network
ISD (OSS, category) At location
updating
Call to B
IDP
Continue
IAM

The MSC generates an Mobile originated CDR at the end of the call. This CDR contains the same
information as for a basic call, except :
- The gsm-SCFAddress field is set with the address of the SCP
- The Service Key field is set with the service key of the IN-CS1 service triggered
- the Number of DP encountered field is present and set to 1
- the Level Of CAMEL Service field is present and set to basic.
Note: Concerning the support of IN-CS1 inside 5060 WCS, please refer to document [32].
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.31 Originating call with IN-CS1 invocation Connect

HLR MSC SCP
Fixed
network
ISD (OSS, category) At location
updating
Call to B
IDP
Connect (C)
IAM (towards C)

The MSC generates a Mobile originated CDR at the end of the call. This CDR contains the same
information as for a basic call, except :
- The called number is set with the number dialled, which is the B number
- The translated number is set with the result of the translation of the B number
- The Service Key field is set with the service key of the IN-CS1 service triggered
- A CAMEL Leg Information field is present with :
o CAMEL Destination Number set with the C number as received in the CONNECT
operation
o the CAMEL modification field is present if the SCP modified some information of the
call, as the calling party number or the calling party category
o The other information elements are not present in the CAMEL Leg Information, the
relevant information elements are set in the top level (outgoing TKGP, seizure time,
answer time, etc)

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.32 Terminating call with IN-CS1 invocation Connect

HLR GMSC SCP
Fixed
network
SRI (B)
IDP
Connect (C)
IAM (towards B)
SRI_ack (MSRN, OSS, category)
Fixed
network
IAM (towards C)

The GMSC generates three records at the end of the call : one MTC for the call to B, one Term_CAMEL
for the IN-CS1 service, and one MOC for the call between B and C.
The MTC contains the same information as for a basic call, except :
- The information related to the subscriber access are not present
- The outgoing TKGP is set with the characteristics of the trunk group used to reach C
- the network call reference field is set to the same value as the call reference field
- the MSC Address field is set to the same value as the recording entity
The T_CAMEL CDR contains :
- the time of the interrogation of the SCP
- the CAMEL Destination Number field is set with the address of C as received from the SCP
- the GsmSCF address field is set with the address of the SCP
- the service key of the service
- the network call reference field is set to the same value as the call reference field
- the MSC Address field is set to the same value as the recording entity
- the default call handling field is set according to the characteristic of the service
- the number of DP encountered field is set to 1 (only one DP in the scenario)
- the Level of CAMEL service field is set to basic
- the free format data field is not present (no FCI operation in the scenario)
- In the Camel Service Extension field,
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


- the called number field is set to the same value as the called number in the MTC. It contains
the address of B.
- the calling number field is set to the same value as the calling number in the MTC. It contains
the address of A.
- the other fields are set to the same value as the fields in the MTC record.
The MOC record contains the same value as for a basic call except :
- the called number field is set with the address of C as received from the SCP
- the translated number field is set with the address of C after translation
- the GsmSCF address, and other IN related parameters are not present in the record, because in
the scenario, no IN service is triggered on the call to C.
- the network call reference and the MSC address fields are set to the same value as in the
MTC and the Term_CAMEL.
- The incoming TKGP field is set with the same trunk group as in the MTC CDR.


A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.33 Originating call with CAMEL Connect and user interaction

HLR MSC SCP
Fixed
network
ISD (O-CSI)
At location
updating
Call to B
IDP
CTR (IP-address, both way connection)
IAM (towards C)
IP
IAM (towards IP)
ACM
ANM
DFC
Connect to B
UUI (P&C)
In-band user interaction
UUI (P&C result)
P&C result (digits dialled by A)
Connect (C)
REL
RLC
P&C
MOC CDR for
user interaction
MOC CDR
ACM+ANM
REL+RLC

An MOC is generated at the end of the call with C. This CDR contains the same information as for a basic
call, except :
- The called number is set with the number dialled, which is the B number
- The translated number is set with the result of the translation of the B number
- The answer time is set to the time when the ANM message is received for the answer of C
- The release time is set to the time of the release of the call with C
- The Service Key field is set with the service key of the CAMEL service triggered
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


o CAMEL Destination Number set with the C number as received in the CONNECT
operation
answer time, etc)
- Leg to external IP is absent
If the option Records_for_IP_connection is active, then an additional MOC is generated for the
connection to the IP. It is generated when the CONNECT to C is received from the SCP. It contains :
- Leg to external IP is set to TRUE
- the called address and translated address refer to the number dialled by the subscriber, and
are the same as in the main CDR for A-B call described above.
- The answer time field is set with the time of the reception of the ANM message from the
external IP
- The release time field is set with the time of the sending/reception of the REL message to/from
the external IP
- The cause for termination is set to normal release
- The gsm-SCFAddress, Service Key, Number of DP encountered, Level of CAMEL service
are set according to the characteristics of the CAMEL service, and take the same values as in the
main CDR for A-B call described above.
o CAMEL Destination Number set with the address of the external IP as received in the
ConnectToResource operation
answer time, etc)

Note: Concerning the support of CAMEL inside 5060 WCS, please refer to document [31].
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.34 Originating call with CAMEL follow-on calls
Note: The partial record handling based on change of CAMEL destination decribed below is not
implemented yet.

HLR MSC SCP
Fixed
network
ISD (O-CSI)
At location
updating
Release of A
IDP
RBE (DP O_Disconnect)
IP
IAM (towards B)
ACM+ANM
Continue
CDR2
REL+RLC
ERB (DP O_Disconnect)
Connect(B)
In-band user interaction (exchanged messageds not shown)
Connect(C)
IAM (towards C)
ACM+ANM
REL+RLC
RBE (DP O_Disconnect)
CDR1
Optionally, 1st
CDR for IP
connexion
Optionally, 3rd
CDR for IP
connexion
Optionally, 2nd
CDR for IP
connexion

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Two MOC CDRs are generated in this scenario for the calls made by A :
The first MOC is a partial record generated when the Connect is received at DP O_Disconnect, and
records the call to B. It contains :
- the called address and translated address refer to the number dialled by A
- The answer time field is set with the time of the reception of the ANM message corresponding
to the answer of B
- The release time field is set with the time of the reception of the second Connect operation
- The partial record type is set to the value ChangeOfCamelDestination, and the cause for
termination field is set to partial record
o CAMEL Destination Number set with the B number as received in the first CONNECT
operation
answer time, etc)
The second MOC is generated at the end of the call. This CDR contains the same information as for a
basic call, except :
- the called address and translated address refer to the number dialled by A
- The answer time field is set with the time of the reception of the ANM message corresponding
to the answer of C
- The release time field is set with the time of the release of A
- The partial record type is absent, and the cause for termination field is set to normal release
o CAMEL Destination Number set with the C number as received in the first CONNECT
operation
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


answer time, etc)
If there is a connection to an external IP and the option MOC-IP is active, then three additional CDRs are
generated for the succeeding connections to the IP (with address of the IP and Leg to external IP set to
TRUE), following the principles explained in sections 4.2.2.33.

4.2.2.35 Originating call with CAMEL follow-on calls with successful and unsuccessfull calls

HLR MSC SCP
Fixed
network
ISD (O-CSI)
At location
updating
Release of A
IDP
IP
IAM (towards B)
Continue
CDR3
REL (busy) + RLC
ERB (DP O_Busy)
Connect(B)
Connect(C)
IAM (towards C)
ACM+ANM
REL+RLC
Connect(D)
IAM (towards D)
REL (busy) + RLC
ERB (DP O_Busy)
Connect(E)
IAM (towards E)
ACM+ANM
REL+RLC
CDR1
CDR2
First call,
unsuccessful
Second call,
successful
Third call,
unsuccessful
Fourth call,
successful
Optionally, first CDR
for the unanswered
call

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Note that the user interactions are not shown in this figure. Other CDRs can be generated if the option
Records for IP connection is active.
In this scenario, the CDR for the first unsuccessful is optional, it is only generated if the option Billing for
unanswered calls is active.
If this option is not active, only CDR1, CDR2 and CDR3 are generated. Though the third call is
unsuccessful, CDR2 is generated whether the Billing for unanswered calls is active or not. CDR1 and
CDR2 are partial records, respectively with sequence number 1 and 2, and CDR3 is a normal release
record with sequence number 3.
The principle is that once a call reached the answered state once, then partial records are generated for
all the following elementary calls.
4.2.2.36 Originating call with CAMEL Furnish Charging Information
The scenario for this case is the same as mentioned above in chapter 4.2.2.10 with the addition, that a
Furnish Charging Information operation (FCI) is received by 5060 WCS which carries free format data.
All the CAMEL parameters are transparently stored in the CDR record (in this case in the MOC-record).
If free format data for the indicated leg is already stored in the concerned record, the new received data
overwrite the already stored data.
Note:
The FCI operation is supported in CAP Phase 2 and in CAP Phase 3. CAP Phase 1 does not support any
charging operation. The CAP Phase 2 operation FCI allows to send free format data of up to 40 octets,
CAP Phase 3 can carry a maximum size of 160 octets.
The CAP Phase 3 FCI operation supports an append option. This allows to append the free format data
received in an FCI operation to the free format data which are already stored in the record.

4.2.2.37 Originating call with CAMEL Send Charging Information
The scenario for this case is a similar one with the addition, that a Send Charging Information (SCI)
operation is received by 5060 WCS.
The Send Charging Information (SCI) operation is currently not supported by 5060 WCS.

4.2.2.38 Supplementary Service operation
TBC
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.39 Supplementary Service operation mobile initiated USSD

MS MSC HLR USSD/
SCP
SS-REGISTER
Facility-IE (Invoke=
ProcessUSSDrequest,
ussdstring)
Invoke=ProcessUSSDRequest
ussdstring
Invoke=ProcessUSSDRequest
ussdstring
Invoke=USSDRequest
ussdstring
Invoke=USSDRequest,
ussdstring
SS-FACILITY
Facility-IE (RetRes=
USSD Request,
ussdstring)
SS-FACILITY
USSD-Request,
ussdstring)
CDR
RetRes=USSDRequest,
ussdstring
RetRes=USSDRequest,
ussdstring
RetRes=ProcessUSSDRequest,
ussdstring
SS-RELEASE COMPLETE
Facility-IE(RetRes =
ProcessUSSDRequest,
ussdstring)

RetRes=ProcessUSSDRequest,
ussdstring

Since Release W3.2 of 5060 WCS, mobile initated USSD is supported.
As usual, the creation of this CDR-type (SS-action) can be switched ON/OFF.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.40 Supplementary Service operation network initiated USSD

MS MSC HLR USSD/
SCP
SS-REGISTER
USSD-Request,
ussdstring)
Invoke=USSDRequest
ussdstring
Invoke=USSDRequest,
ussdstring
SS-FACILITY
USSD-Request,
ussdstring)
SS-FACILITY
USSD-Notify,
ussdstring)
CDR
RetRes=USSDRequest,
ussdstring
RetRes=USSDRequest,
ussdstring
Invoke=USSD-SS-Notify
ussdstring

SS-RELEASE COMPLETE
Cause=Normal Clearing
Invoke=USSDNotify,
ussdstring
Paging+MM
SS-FACILITY
Facility-IE (RetRes)
RetRes=USSDNotify
RetRes=USSDNotify
TC-End: Empty
TC-End: Empty
Invoke=SendRouting
Info(msisdn)
RetRes=SendRoutingInfo
(msisdn, MSC-Address)

Since Release W3.2 of 5060 WCS, network initated USSD is supported.
As usual, the creation of this CDR-type (SS-action) can be switched ON/OFF.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.41 Call with optimal routeing, successful case

MSCA IMSCA VMSCB
Call to B
HLRB
Connect to B
REL
RLC
CDR1 CDR2
SRI (call reference, IMSCA address)
PRN (call reference, IMSCA address)
PRN ack (VMSCB address, MSRN)
SRI ack (VMSCB address, MSRN)
IAM
ACM
ANM
ACM
ANM (VMSCB address or MSRN)
Alerting to B
IAM

MSCA is the originating MSC, IMSCA is the interrogating MSC and is in the same PLMN as MSCA,
HLRB is the HLR of the PLMN of B, and VMSCB is the MSC on which B is located (it can be in any
PLMN). In this figure, MSCA and IMSCA are different MSCs, but they can be co-localized.
CDR1 is a basic MOC CDR.
CDR2 is a MTC CDR. The call reference received in the PRN is stored in the network call reference
field, and the IMSCA address is stored in the MSC address field.
If IMSCA and VMSCB are in different PLMNs, an outgoing gateway CDR can be generated by the IMSCA
(in case the inter-network trunk group characteristic is set).
4.2.2.42 Call with optimal routeing, unsuccessful case
TBC
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.43 Call with optimal routeing, early call forwarding

MSCA IMSCA GMSCC
or fixed
network
Call to B
HLRB
Connect to B
REL
RLC
CDR1
Same charging information as
for a normal incoming call
SRI ack (FTN)
IAM (called party = FTN)
ACM
ANM
ACM
ANM (FTN)
Alerting to B
CDR2
IAM
CDR3
CDR4

HLRB is the HLR of the PLMN of B, and GMSCC is the MSC on which the forwarded-to subscriber I is
located (it can be also the PSTN). In this figure, MSCA and IMSCA are different MSCs, but they can be
co-localized.
CDR1 is a basic MOC CDR. CDR2 is a MTC CDR for call forwarding.
CDR3 is a MOC CDR, for call forwarding.
CDR4 is an outgoing gateway CDR generated by the IMSCA in case the inter-network trunk group
characteristic is set.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.44 Call with optimal routeing, late call forwarding

MSCA IMSCA VMSCB
Call to B
HLRB
Connect to B
REL
RLC
CDR1
PRN (call reference, IMSCA address)
PRN ack (VMSCB address, MSRN)
SRI ack (VMSCB address, MSRN)
IAM (MSRN)
RCH (FTNc)
ANM
ACM
ANM (FTNc)
Alerting to B
CDR2
IAM
REL
RLC
RCH ack
GMSCC
IAM (FTNc)
ACM
CDR3
CDR4

HLRB is the HLR of the PLMN of B, VMSCB is the VMSC on which B is located and GMSCC is the
GMSC of the PLMN on which the forwarded-to subscriber I is located (it can be also the PSTN if the
ultipart-to subscriber is a fixed subscriber). In this figure, MSCA and IMSCA are different MSCs, but
they can be co-localized.
CDR1 is a basic MOC CDR.
CDR2 is a MTC-CF CDR.
CDR3 is a MOC-CF CDR.
CDR4 is an outgoing gateway CDR generated by the IMSCA in case the inter-network trunk group
characteristic is set.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.45 Terminating call to a ported MS MNP/SRF

MNP/SRF GMSC-A GMSC-B
Fixed
network
SRI (B)
IAM (towards B)
SRI_ack (RN and MSISDN)
IAM (RN+MSISDN)
CDR1
CDR2

GMSC-A belongs to the ported number range owner.
It detects that the MSISDN of B can be ported out, and the SRI is sent to the SRF. The SRF detects that
the MSISDN of B is ported out to another PLMN, and sends in the SRI_ack a Routeing Number
concatenated with the MSISDN.
CDR1 is an incoming gateway record, generated if the inter-network trunk group characteristic is set on
the incoming trunk group.
CDR2 is an outgoing gateway record, generated if the inter-network trunk group characteristic is set on
the outgoing trunk group.
The MSRN field of these two CDRs is set with the MSRN parameter received in the SRI_ack. It contains
the Routeing Number, concatenated or not with the MSISDN according to a MNP/SRF option. This
information permits to know the calls received in the GMSC for the ported-out subscribers.
4.2.2.46 Terminating call to a ported MS MNP/IN
Detail information about all call scenario see 3HP700335047DSZZA.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


4.2.2.47 Call re-origination (14086)

Reference to the section 4.2.2.5 incoming call to a PLMN service centre.
If the A5060 is also the originating MSC as well as the terminating VMSC, the A5060 shall generate a
MOC CDR capturing the overall call duration including the duration of all redirections.
If the A5060 is also the GMSC as well as the terminating VMSC, the A5060 shall write an Incoming
Gateway CDR for the connection to the Call Centre via the VMSC.
As the terminating VMSC, the A5060 shall write a Transit CDR for the connection to the Call Centre.
Beside above Records, VMSC should Re-origination Records.
As the terminating VMSC, the A5060 shall indicate in the special MOC CDR that a Re-origination attempt
has been made using:
SupplServiceCode-struct ::= ENUMERATED {

explicitCallTransfer (49),

While re-origination is not technically an example of explicit call transfer, the customer has indicated a
preference for this designation as the associated SS.
GSM

Call
Centre

Call Setup
IAM

IVR

ACM
ANM
REL, Cause XX, Redirection No. YY
IAM, B Number =
YY
ACM
ANM
RLC
RLC
A5060
VMSC
REL
MOC
CDR
MOC
CDR
with
ECT
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


For each re-origination, the A5060 shall write a MOC CDR including:
The received A party number as calling party,
The new called party number IVR, Call Centre, etc. as the called B party for the outgoing call,
which is the Redirection Number received from the REL
The redirecting number is recorded as Served MSISDN
The ECT SS-Code.
Note1: The special MOC CDR for ECT should use MOC-CF format (to record three party numbers) with
ECT ss-code but without CF ss-code.
Note2: In the case of multiple re-origination s, A5060 shall write a separate special MOC CDR for each
re-origination.
Note3: If IMSI is Mandatory, but IMSI is unavailable for some special case (for example: served party is
call center), then Servied IMSI will be filled with all F.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5 TS 32.250 CHARGING DATA DESCRIPTION
5.1 Record types and contents
The following tables describe the contents of each of the call and event records generated in the CS
domain, e.g. by the MSCs (see the example scenarios in TS 32.240 [1]). For each CDR type the field
definition includes the field name, description and category.
Equipment vendors shall be able to provide all of the fields listed in the CDR content table in order to
claim compliance with the present document. However, since CDR processing and transport consume
network resources, operators may opt to eliminate some of the fields that are not essential for their
operation. This operator provisionable reduction is specified by the field category.
A field category can have one of two primary values:
M This field is Mandatory and shall always be present in the CDR.
C This field shall be present in the CDR only when certain Conditions are met. These Conditions
are specified as part of the field definition.
All other fields are designated as Operator (O) provisionable which replaced the Optional category
specified in an earlier release. Using TMN management functions or specific tools provided by an
equipment vendor, operators may choose if they wish to include or omit the field from the CDR. Once
omitted, this field is not generated in a CDR. To avoid any potential ambiguity, a CDR generating
element MUST be able to provide all these fields. Only an operator can choose whether or not these
fields should be generated in their system.
Those fields that the operator wishes to be present are further divided into a mandatory and conditional
category:
O
M
This is a field that, if provisioned by the operator to be present, shall always be included in the
CDRs. In other words, an O
M
parameter that is provisioned to be present is a mandatory parameter.
O
C
This is a field that, if provisioned by the operator to be present, shall be included in the CDRs
when the required conditions are met. In other words, an O
C
parameter that is configured to be present is
a conditional parameter.
The content of the CDRs shall be specified on the interface from the core network to the billing system
that is used for CDR transport. The rules governing the CDR specifications on these interfaces are
summarized in the following clause.
During a long user session several Partial CDRs may be generated for the same session. In this case,
some information can be eliminated rather than repeated in all the partial CDRs for that session. Only
changes from one CDR to the next, in addition to mandatory information, can be reported. All the missing
information can be reconstructed from fields in previous partial CDRs for the session. For instance, if the
subscriber did not change location, the Reduced Partial CDR would not include any location information.
Two formats are considered for Partial CDRs:
- a Full Qualified Partial CDR that contains the Complete CDR Fields; and
- a Reduced Partial CDR that contains all the Mandatory fields (M) and ONLY the changes that
occurred in any other field relative to the previous Partial CDR.
The first CDR generated when a session is opened shall be a Full Qualified Partial CDR. Subsequent
partial CDRs may be Reduced Partial CDRs.
5060 WCS position : The subsequent partial CDRs are Full Qualified Partial CDRs.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Thus, the convention is that when any non-mandatory field is missing from a Reduced Partial CDR, it
should be interpreted that the same field as in the previous partial CDR could be used. Only Mandatory
(M) fields MUST always be included.
The anchor MSC is the creator of the CDRs. The column 2G indicates a qualifier for the presence of the
parameter in a 2G anchor MSC. The column 3G indicates a qualifier for the presence of the parameter
in a 3G anchor MSC.
For MSCs capable of CAMEL Call Party Handling (CPH), one separate record is generated per call
segment. The record is closed when the last leg of the call segment disappeared (moved out,
disconnected, etc. ) from the call segment. The leg specific fields listed below shall be recorded in the
grouped field 'CAMEL Call Leg Information' instead of using the counterpart in the main body. The
counterparts of those fields in the main body are maintained for compatibility reasons to earlier releases.
- CAMEL Destination Number
- Translated Number (not impl.)
- Connected Number (not impl.)
- Roaming Number (not impl.)
- Outgoing TKGP (in 'CAMEL Call Leg Information' this item is called MSC outgoing TKGP) (not impl.)
- Additional Chg. Info
- Default call handling 2
- GsmSCF address 2
- Service key 2
- Free format data 2 (in 'CAMEL Call Leg Information' this item is called Free format data incoming 2)
- Free format data append indicator 2 (in 'CAMEL Call Leg Information' this item is called Free format
data append incoming 2) (not impl.)
- Location Routing Number (LRN) (not impl.)
- LRN Source Indicator (not impl.)
- LRN Query Status Indicator (not impl.)
- JIP Parameter (not impl.)
- JIP Source Indicator (not impl.)
- JIP Query Status Indicator (not impl.)
5060 WCS position : in the following tables,
- The rows in gray indicate extensions to the standard format.
- The striked through rows indicate information elements defined in the standard format, but not
supported by the 5060 WCS
- The 2G column indicates that the call is initiated in 2G, and the 3G column indicates that the call is
initiated in 3G.
- The information M, C, O
M
and

O
c
are kept from the 3GPP specification. However, this information is not
relevant. A field is present in a CDR generated by the WCS if :
1. the corresponding row is not striked through
2. the information is available for the call
3. no option prevents the generation of this field
Note:
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


WCS support to generate unsuccessful call CDR by control flag in WEM, but the M (mandatory) or
C(conditional) kind of field cant be promise exist in unsuccessful call CDR.

Note:
The grey color in table in chapter 5 means non 3GPP standard fields. This kind of fields are stored in the
Record extensions field.

Note: For all mandatory CDR field, if content is unavailable for some special case, then the mandatory
CDR field will be filled with all F.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.1 Mobile originated call attempt
If the generation of these records is enabled then an MOC record shall be created for each outgoing call
attempt made by a mobile station. These MOC records shall be produced in the originating MSC.
Note: The generation of this record type is not switchable. It will be generated always.
NB. In CDMA, this record format also applies to emergency calls, which are determined by the called
number translation.
Table 14: MOC record
Field 2G 3G Description
Record Type M M Mobile originated.
Served IMSI M M IMSI of the calling party.
If CDMA, then it is the MIN or the calling party.
Served IMEI C C IMEI of the calling ME, if available.
Served MSISDN OM OM The primary MSISDN of the calling party.
If CDMA, then it is the MDN of the calling party.
Called Number M M The address of the called party i.e. the number dialled by the calling subscriber.
Translated
Number
OC OC The called number after digit translation within the MSC (if applicable) (WCS
supports store different translated number (before Outpulsed or after Outpulsed in
CDR RDS5680)
Connected
Number
OC OC The number of the connected party if different to the Called Number
Roaming Number OC OC The Mobile Station Roaming Number employed to route this connection, if
applicable. If CDMA, then it is the TLDN. RDS5700
Recording Entity M M The E.164 number of the visited MSC producing the record.
Incoming TKGP OM Oc The MSC trunk group on which the call originated , usually from the BSS. If
available in 3G, this parameter shall be supplied.
Outgoing TKGP OM Oc The trunk group on which the call left the MSC. If available in 3G, this parameter
shall be supplied.
Location M M The identity of the cell or the SAC at the beginning of the call, including the location
area code. It can also be the cell or SAC that caused the generation of a partial
record due to change of location.
Change of
Location
OC OC A list of changes in Location Area Code / Service Area Code / Cell Id. Each time-
stamped.
Basic service M M Bearer or teleservice employed.
Rate Indication OC OC Present if rate adaption parameters for the basic service were signalled between
the MS/UE and the network, see TS 24.008.
Transparency
Indicator
C C Indicates whether the basic service was used in transparent or non-transparent
mode. This parameter is provided only for those basic services which may be
employed in both transparent and non-transparent mode.
Change Of
Service
OC OC A list of changes of basic service during a connection each time-stamped.
Supp. Services C C Supplementary services invoked as a result of this connection. This field shall be
present when one or more supplementary services have been invoked.
AOC Parameters OC OC The charge advice parameters sent to the MS on call set-up. This field shall be
supplied only when AoC parameters have been sent.
Change of AOC
Parameters
OC OC New AOC parameters sent to the MS e.g. as a result of a tariff switch over,
including the time at which the new set was applied. This field shall be supplied only
when AoC parameters have been sent.
MS Classmark M M The mobile station classmark employed on call setup.
Change of
Classmark
OC OC A list of changes to the classmark during the connection each time-stamped
C C Seizure time: time of incoming traffic channel seizure (for unsuccessful call
attempts)
C C Answer: time of answer (for successful calls)
Event time
stamps:
OM OM Release time: time of traffic channel release
Call duration M M The chargeable duration of the connection for successful calls, the holding time for
call attempts.
Data volume C - The number of data segments transmitted if available at the MSC
Radio Chan.
Requested
OM - The type of radio traffic channel (full / half etc.) requested by the MS.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Radio Chan.
Used
M - The type of radio channel actually used (full or half rate).
Change of Rad.
Chan.
OC - A list of changes each time stamped
Cause for
termination
M M The reason for the release of the connection.
Diagnostics OM OM A more detailed reason for the release of the connection.
Call reference M M A local identifier distinguishing between different services (e.g. calls) involving the
same mobile subscriber
Sequence no. C C Partial record sequence number, only present in case of partial records.
Additional Chg.
Info
OC OC Charge/no charge indicator and additional charging parameters, when available.
It can also hold the contents of the ISUP messages received from downstream.
Record
extensions
OC OC A set of network / manufacturer specific extensions to the record, when available.
See description below
GsmSCF address C C Identifies the CAMEL server serving the subscriber. Shall be present only if CAMEL
is applied.
Service key C C The CAMEL service logic to be applied. Shall be present only if CAMEL is applied.
Network call
reference
C C An identifier to correlate transactions on the same call taking place in different
network nodes, shall be present if CAMEL is applied.
MSC Address C C This field contains the E.164 number assigned to the MSC that generated the
network call reference. Shall be present only if CAMEL is applied.
Default call
handling
OC OC Indicates whether or not a CAMEL call encountered default call handling. This field
shall be present only if default call handling has been applied.
Number of
HSCSD Channels
Requested
C - The maximum number of HSCSD channels requested as received from the MS at
call set-up. Shall only be present for HSCSD connections.
Number of
HSCSD Channels
Allocated
C - The number of HSCSD channels allocated to the MS at call set-up. Shall only be
present for HSCSD connections.
Change of
HSCSD
Parameters
C - A list of network or user initiated changes of number of HSCSD channels during a
connection each timestamped. Shall only be present in case of an HSCSD call, if
the basic HSCSD parameters are modified due the user or network initiated
modification procedure.
Fixed Network
User Rate
OC OC Indicates the user data rate applied for the connection in the fixed network. Shall
only be present for 2G HSCSD connections and for UMTS data connections.
RDS5440
Air Interface User
Rate Requested
C - The total Air Interface User Rate Requested by the MS at call setup. Shall only be
present for non-transparent HSCSD connections.
Channel Coding
Accepted
C - A list of the traffic channels codings accepted by the MS. Shall only be present for
HSCSD connections.
Channel Coding
Used
C - The traffic channels codings negotiated between the MS and the network at call
setup. Shall only be present for HSCSD connections.
Guaranteed bit
rate
- Oc Describes the bitrate the UMTS bearer service shall guarantee to the user or
application. Guaranteed Bit Rate may be used to facilitate admission control based
on available resources, and for resource allocation within UMTS. Shall only be
present for UMTS data connections.
RDS5440
Maximum bit rate - Oc Maximum Bit Rate can be used to make code reservations in the downlink of the
radio interface. Its purpose is: 1) to limit the delivered bitrate to applications or
external networks with such limitations, 2) to allow maximum wanted user bitrate to
be defined for applications able to operate with different rates (e.g. applications with
adapting codecs). Shall only be present for UMTS data connections. RDS5440
Speech Version
Supported
OM - Speech version supported by the MS with highest priority indicated by MS
Speech Version
Used
OM - Speech version used for that call
Number of DP
encountered
OC OC Number that counts how often armed detection points (TDP and EDP) were
encountered. Shall be present only if CAMEL is applied.
Level of CAMEL
service
OC OC Indicator for the complexity of the CAMEL feature used. Shall be present only if
CAMEL is applied.
Free format Data C C This field contains data sent by the gsmSCF in the Furnish Charging Information
(FCI) message(s). The data can be sent either in one FCI message or several FCI
messages with append indicator. Shall be present only if CAMEL is applied.
It contains the data related to the controlling leg.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


CAMEL call leg
information
C C Set of CAMEL information Ies. Each of these Ies contains information related to one
outgoing CAMEL call leg. Shall be present only if CAMEL is applied.
The Free format data contained in this element is the one received in a FCI for the
corresponding leg.
Free format data
append indicator
C C Indicator if free format data from this CDR is to be appended to free format data in
previous partial CDR. Shall be present only if CAMEL is applied.
Default call
handling 2
OC OC Indicates whether or not a CAMEL call encountered default call handling for 2
nd

service such as dialled service. This field shall be present only if default call
handling has been applied.
GsmSCF address
2
C C Identifies the CAMEL server serving the subscriber for 2
nd
service such as dialled
service. Shall be present only if CAMEL is applied for 2
nd
service.
Service key 2 C C The CAMEL service logic to be applied for 2
nd
service such as dialled service. Shall
be present only if CAMEL is applied for 2
nd
service.
Free format Data
2
C C This field contains data sent by the gsmSCF in the FCI message(s) for 2
nd
service
such as dialled service. The data can be sent either in one FCI message or several
FCI messages with append indicator. Shall be present only if CAMEL is applied for
2
nd
service.
Free format data
append indicator
2
C C Indicator if free format data for 2
nd
service from this CDR is to be appended to free
format data in previous partial CDR. Shall be present only if CAMEL is applied for
2
nd
service.
System Type - M This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is
present when either the UTRAN or GERAN air-interface is used on call setup. For
an open CDR in a 2G NE (responsible for the CDR), the field is not present (even if
the call is handed off to a 3G air interface). For a CDR in a 3G NE (responsible for
the CDR), the value unknown shall be used after handover.
Location Routing
Number (LRN)
- OC Location Routing Number for Number Portability feature RDS9189
LRN Source
Indicator
- OC LRN Source Indicator tells the source of the LRN RDS9189
LRN Query Status
Indicator
- OC Status of Number Portability query. RDS9189
JIP Parameter - OC Jurisdiction Information Parameter
JIP Source
Indicator
- OC JIP Source Indicator tells the source of the JIP
JIP Query Status
Indicator
- OC Status of Number Portability query.
Partial Record
Type
- OC Indicates the event (time limit etc.) that caused the generation of a partial record.
Note: Only time limit is supported
Reason for
service change
- OC Indicates the type of service change and fallback. (R8)
Service change
initiator
- OC Indicates the service change initiator. (R8)
Redial Attempt OC OC Indicates to the network that a call is the result of a redial attempt to switch from
speech to multimedia or vice-versa (R8)
Hot billing
subscriber
C C Indicates that the subscriber is a hot billing subscriber.
IP connection OC OC This field indicates that the CDR is related to SRF connection, ordered by a CAMEL
service.
RNCIdOfFirstRNC - C This field indicates the RNCid on which the user is located at the time of call
establishment. RDS5440
MS category C C This field indicates the category of the MS, obtained from the VLR RDS5440
CS ARP C C This field indicates the priority of the MS subscriber RDS5440
CUG interlock
code
O O This field indicates the CUG interlock code
RDS9804b
CUG index O O This field indicates the CUG index
RDS9804b
CUG outgoing
access
suppressed
O O This field indicates whether suppression of Outgoing Access capability.
RDS9804b
CUG outgoing
access indicator
O O This field indicates the calling MS's CUG OA subscription information RDS9804b
BSCIdOfFirstBSC C - This field indicates the BSCid on which the user is located at the time of call
establishment.
Multimedia call - C This field indicates that the call is a multimedia call. Shall only be present for UMTS
calls. RDS5440
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Interconnect
Facility
C C This field describes the interconnect facility used between the two media-gateways
used for the call. This field is absent if the call uses only one media-gateway (no
interconnect facility used). (not implemented
yet)
MSC incoming
trunk group
extension
C C This field carries information about the incoming trunk group : its signalling type, its
transport interface type, the media-gateway identity, and the circuit number used.
RDS9851
MSC outgoing
trunk group
extension
C C This field carries information about the outgoing trunk group : its signalling type, its
transport interface type, the media-gateway identity, and the circuit number used.
RDS9851
Subscribed OSSS
Codes
OC OC This field describe used OSSS code
RDS14064
5.1.2 Mobile originated emergency call attempt
If the generation of MOC records is enabled then an MOC emergency record shall be created for each
outgoing emergency call attempt made by a mobile station. These records shall be produced in the
originating MSC. Note: The generation of this record type is not switchable. It will be generated always.
Table 15: MOC emergency record
Served IMSI C C IMSI of the calling party in case of an emergency call with a SIM card.
Served IMEI C C IMEI of the calling mobile equipment if available.
Served MSISDN OC OC The primary MSISDN of the calling party in case of an emergency call with a
SIM card.
Translated Number OC OC The called number after digit translation within the MSC (if applicable)
Incoming TKGP OM OC The MSC trunk group on which the call originated, usually from the BSS. If
Outgoing TKGP OM OC The trunk group on which the call left the MSC. If available in 3G, this
parameter shall be supplied.
Location M M The identity of the cell or the SAC in which the call originated including the
location area code. It can also be the cell or SAC that caused the generation of
a partial record due to change of location.
Change of Location OC OC A list of changes in Location Area Code / Service Area Code / Cell Id. Each
time-stamped.
Basic service M M Teleservice emergency call.
AOC Parameters OC OC The charge advice parameters sent to the MS on call set-up. This field shall be supplied
only when AoC parameters have been sent.
Change of AOC Parameters OC OC New AOC parameters sent to the MS e.g. as a result of a tariff switch over, including the
time at which the new set was applied. This field shall be supplied only when AoC
parameters have been sent.
MS Classmark M M The mobile station classmark employed on call set-up.
Change of classmark OC OC A list of changes to the classmark during the connection each time-stamped
Event time stamps: C C Seizure time: time of incoming traffic channel seizure (for unsucc. call attempts)
C C Answer time: time of answer (for successful calls)
OM OM Release time: time of traffic channel release
Call duration M M The chargeable duration of the connection for successful calls, the holding time
for call attempts.
Radio Chan. Requested OM - The type of radio traffic channel (full / half etc.) requested by the MS.
Radio Chan. Used M - The type of radio channel used (full or half rate).
Change of Rad. Chan. OC - A list of changes each time stamped
Cause for termination M M The reason for the release of the connection.
Call reference M M A local identifier distinguishing between different services (e.g. calls) involving
the same mobile subscriber
Record extensions OC OC A set of network/manufacturer specific extensions to the record, when available.
System Type - M This field indicates the use of GERAN, UTRAN (or a value of unknown). This
field is present when either the UTRAN or GERAN air-interface is used on call
setup. For an open CDR in a 2G NE (responsible for the CDR), the field is not
present (even if the call is handed off to a 3G air interface). For a CDR in a 3G
NE (responsible for the CDR), the value unknown shall be used after handover.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Partial Record Type C C Indicates the reason of the generation of a partial record. It is absent if the
Cause for termination is different from Partial Record). It can be due to a time
limit, or due to change of CAMEL destination number.
Hot billing subscriber C C Indicates that the subscriber is a hot billing subscriber.
BSCIdOfFirstBSC C - This field indicates the BSCid on which the user is located at the time of call
establishment.
Interconnect Facility C C This field describes the interconnect facility used between the two media-
gateways used for the call. This field is absent if the call uses only one media-
gateway (no interconnect facility used). (not implemented yet)
MSC incoming trunk group
extension
C C This field carries info about the inc. trunk group: its signalling type, its transport
interface type, the media-gateway id and the circuit nbr used. RDS9851
MSC outgoing trunk group
extension
C C This field carries info about the outg.trunkgroup: its signalling type, its transport
interface type, the media-gateway id and the circuit nbr used. RDS9851

5.1.3 Mobile originated call forwarding attempt
If the generation of MOC records is enabled in the forwarding MSC then the forwarding MSC shall
produce an MOC record for the forwarded-leg of the call.
Table 16: MOC, call forwarding record
Served IMSI M M IMSI of the forwarding party.
Served IMEI C C IMEI of the forwarding party if available (IMEI field will be present in CF
CDR in case of CFNRy and CFB).
RDS8184 / D46475
Served MSISDN OM OM The MSISDN of the forwarding party.
Calling Number OM OM The address of the calling party.
Called Number M M The address of the forwarded-to party.
Translated Number OC OC The called number after digit translation within the MSC (if applicable)
Connected Number OC OC The number of the connected party if different to the Called Number
Roaming Number OC OC The Mobile Station Roaming Number employed to route this connection,
if applicable. (Its the roaming number for called party not for forward-to part.
Roaming number is not present for CFU case.) RDS5700
Recording Entity M M The E.164 number of the forwarding MSC
Incoming TKGP OM OM The MSC trunk group on which the call originated at the forwarding MSC.
Outgoing TKGP OM OM The trunk group on which the call left the forwarding MSC
Location C C The identity of the cell or the SAC (including the location area code) in
which the forwarding party is located (location field is only exist in CF
RDS8184 / D46475
Basic service C C Bearer or teleservice employed, not always available e.g. in case of call
forwarding unconditional.
Rate Indication OC OC Present if rate adaption parameters for the basic service were signalled
between the MS/UE and the network, see TS 24.008. May not always be
available in this CDR type.
Transparency Indicator C C Indicates whether the basic service was used in transparent or non-
transparent mode. This parameter is provided only for those basic services
which may be employed in both transparent and non-transparent mode.
Fixed Network User Rate OC OC Indicates the user data rate applied for the connection in the fixed network.
Shall only be present for 2G HSCSD connections and for UMTS data
connections. RDS5440
ChangeOfService OC OC A list of changes of basic service during a connection each time-stamped.
Supplementary Services C C Supplementary services invoked as a result of this connection, if this
information is available to the forwarding node. This field shall be present
when one or more supplementary services have been invoked.
Event time stamps: C
C
OM
C
C
OM
Seizure time: time of incoming traffic channel seizure (for unsuccessful call
attempts)
Answer time: time of answer (for successful calls)
Release time: time of traffic channel release
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Call duration M M The chargeable duration of the connection for successful calls, the holding
time of call attempts.
Data volume C - The number of data segments transmitted if available at the MSC
Call reference M M A local identifier distinguishing between different services (e.g. calls)
involving the same mobile subscriber
Additional Chg. Info OC O Charge/no charge indicator and additional charging parameters, when
available.
Record extensions OC OC A set of network/ manufacturer specific extensions to the record, when
available. See description below.
GsmSCF address C C Identifies the CAMEL server serving the subscriber. Shall be present only if
CAMEL is applied.
Service key C C The CAMEL service logic to be applied. Shall be present only if CAMEL is
applied.
Network call reference C C An identifier to correlate transactions on the same call taking place in
different network nodes shall be present if CAMEL is applied.
CAMEL initiated CF
indicator
C C Indicates that the CAMEL server initiated call forwarding. Shall be present
only if CAMEL is applied.
Default call handling OC OC Indicates whether or not a CAMEL call encountered default call handling.
This field shall be present only if default call handling has been applied.
Number of DP
encountered
encountered. Shall be present only if CAMEL is applied.
Level of CAMEL service OC OC Indicator of the complexity of the CAMEL feature used. Shall be present only
if CAMEL is applied.
Free format Data C C This field contains data sent by the gsmSCF in the Furnish Charging
Information (FCI) messages. The data can be sent either in one FCI
message or several FCI messages with append indicator. Shall be present
only if CAMEL is applied.
CAMEL call leg
information
C C Set of CAMEL information Ies. Each of these Ies contains information related
to one outgoing CAMEL call leg. Shall be present only if CAMEL is applied.
Free format data append
indicator
C C Indicator if free format data from this CDR is to be appended to free format
data in previous partial CDR. Shall be present only if CAMEL is applied.
Default call handling 2 OC OC Indicates whether or not a CAMEL call encountered default call handling for
2
nd
service such as dialled service. This field shall be present only if default
call handling has been applied.
GsmSCF address 2 C C Identifies the CAMEL server serving the subscriber for 2
nd
service such as
dialled service. Shall be present only if CAMEL is applied for 2
nd
service.
nd
service such as dialled
service. Shall be present only if CAMEL is applied for 2
nd
service.
Free format Data 2 C C This field contains data sent by the gsmSCF in the FCI message(s) for 2
nd

service such as dialled service. The data can be sent either in one FCI
only if CAMEL is applied for 2
nd
service.
Free format data append
indicator 2
nd
service from this CDR is to be appended
to free format data in previous partial CDR. Shall be present only if CAMEL is
applied for 2
nd
service.
Location Routing Number
(LRN)
- Oc Location Routing Number for Number Portability feature RDS9189
LRN Source Indicator - OC LRN Source Indicator tells the source of the LRN RDS9189
LRN Query Status
Indicator
JIP Source Indicator - OC JIP Source Indicator tells the source of the JIP
JIP Query Status
Indicator
Partial Record Type C C Indicates the reason of the generation of a partial record. It is absent if the
Cause for termination is different from Partial Record). It can be due to a
time limit, or due to change of CAMEL destination number.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Hot billing subscriber C C Indicates that the subscriber is a hot billing subscriber. It means that one
record is transmitted in real time towards the billing system (or a dedicated
system), and that a second record is transmitted towards the billing system
as the others.
IP connection OC OC This field indicates that the CDR is related to SRF connection, ordered by a
CAMEL service.
CUG interlock code O O This field indicates the CUG interlock code RDS9804b
CUG outgoing access ind O O This field indicates the CUG interlock indicator RDS9804b
Multimedia call - C This field indicates that the call is a multimedia call. Shall only be present for
UMTS calls.
gateways used for the call. This field is absent if the call uses only one
media-gateway (no interconnect facility used). (not implemented yet)
MSC incoming trunk
group extension
C C This field carries information about the incoming trunk group : its signalling
type, its transport interface type, the media-gateway identity, and the circuit
number used. RDS9851
MSC outgoing trunk
group extension
C C This field carries information about the outgoing trunk group : its signalling
Subscribed OSSS Codes OC OC This field describe OSSS code from HLR
RDS14064
5.1.4 Mobile terminated call attempt
If the generation of these records is enabled, then an MTC record shall be created for each incoming call
attempt made for a mobile station. The MTC records shall be produced in the terminating MSC.
Note: The generation of this record type is not switchable. It will be generated always.
Table 17: MTC record
Record Type M M Mobile Terminated.
Served IMSI M M IMSI of the called party.
Served IMEI C C IMEI of the called ME, if available.
Served MSISDN OM OM The MSISDN of the called party.
Calling Number C C The number of the calling party if available.
Connected Number OC OC Only relevant in case of call forwarding where the forwarded-to number is
recorded.
Recording Entity M M The E.164 number of the MSC
Incoming TKGP OM OM The MSC trunk group on which the call originated.
Outgoing TKGP OM OC The trunk group on which the call left the MSC, usually to the BSS. If
Location C C The identity of the cell or the SAC occupied by the called party when the call
was set up, including the location area code. It can also be the cell or SAC
that caused the generation of a partial record due to change of location.
time-stamped.
Basic Service M M Bearer or teleservice employed
between the MS/UE and the network, see TS 24.008.
transparent mode. This parameter is provided only for those basic services,
Change of Service OC OC A list of changes of basic service during a connection each time-stamped.
Supplementary services C C Supplementary services invoked as a result of this connection. This field
shall be present when one or more supplementary services have been
invoked.
AOC Parameters OC OC The charge advice parameters sent to the MS on call set-up. This field shall
be supplied only when AoC parameters have been sent.
Change of AOC
Parameters.
OC OC New AOC parameters sent to the MS e.g. as a result of a tariff switch-over,
including the time at which the new set was applied. This field shall be
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


MS Classmark M M The mobile station class mark.
Change of Classmark OC OC A list of changes to the classmark during the connection each time-stamped
C
OM
C
C
OM
Seizure time: time of traffic channel seizure for unsuccessful call attempts
Answer time: time of answer for successful calls
Call duration M M The chargeable duration of the connection if successful, the holding time of
the call if unsuccessful.
Data volume C - The number of data segments transmitted, if available at the MSC
Radio Chan. Used M - The type of radio channel used (full or half rate).
Change of Rad. Chan OC - A list of changes each time stamped
Cause for termination M M The reason for the release of the call.
Call reference M M A local identifier distinguishing between transactions at the same MS
Additional Chg. Info OC OC Charge/no charge indicator and additional charg. parms, when available.
available. See below.
Number of HSCSD
Channels Requested
OC - The maximum number of HSCSD channels requested as received from the
MS at call set-up. Shall only be present for HSCSD connections.
Number of HSCSD
Channels Allocated
OC - The number of HSCSD channels allocated to the MS at call set-up. Shall
only be present for HSCSD connections.
Change of HSCSD
Parameters
OC - A list of network or user initiated changes of number of HSCSD channels
during a connection each timestamped. Shall only be present in case of an
HSCSD call, if the basic HSCSD parameters are modified due the user or
network initiated modification procedure.
Fixed Network User Rate OC - Indicates the user data rate applied for the connection in the fixed network.
connections. RDS5440
Air Interface User Rate
Requested
C C The total Air Interface User Rate Requested by the MS at call setup. Shall
only be present for non-transparent HSCSD connections.
Channel Coding
Accepted
C - A list of the traffic channels codings accepted by the MS. Shall only be
present for HSCSD connections.
Channel Coding Used C - The traffic channels codings negotiated between the MS and the network at
call setup. Shall only be present for HSCSD connections.
Guaranteed bit rate - Oc Describes the bitrate the UMTS bearer service shall guarantee to the user or
application. Guaranteed Bit Rate may be used to facilitate admission control
based on available resources, and for resource allocation within UMTS. Shall
only be present for UMTS data connections. RDS5440
Maximum bit rate - Oc Maximum Bit Rate can be used to make code reservations in the downlink of
the radio interface. Its purpose is: 1) to limit the delivered bitrate to
applications or external networks with such limitations, 2) to allow maximum
wanted user bitrate to be defined for applications able to operate with
different rates (e.g. applications with adapting codecs). Shall only be present
for UMTS data connections. RDS5440
Speech Version Used OM - Speech version used for that call
Speech Version
Supported
System Type - M This field indicates the use of GERAN, UTRAN (or a value of unknown). This
field is present when either the UTRAN or GERAN air-interface is used on
call setup. For an open CDR in a 2G NE (responsible for the CDR), the field
is not present (even if the call is handed off to a 3G air interface). For a CDR
in a 3G NE (responsible for the CDR), the value unknown shall be used after
handover.
(LRN)
LRN Query Status
Indicator
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.



JIP Query Status
Indicator
Partial Record Type - Oc Indicates the event (time limit) that caused the generation of a partial record.
Note: only time limit event is supported.
Reason for service
change
- OC Indicates the type of service change and fallback. (R8)
Service change initiator - OC Indicates the service change initiator. (R8)
as the others.
GsmSCF Address OC OC The CAMEL server serving the subscriber.
It is the gsmSCF address associated with the O-CSI trigger of the subscriber.
Service key OC OC The CAMEL service logic to be applied.
It is the Service Key associated with the O-CSI trigger of the subscriber.
Redirecting counter C C This field contains the number of call forwarding that occurred on the call, as
obtained from the IAM message.
CUG interlock code O O This field indicates the CUG interlock code
RDS9804b
CUG index O O This field indicates the CUG index
RDS9804b
CUG Incoming Access
Used
O O This field indicates that the call is received from outside the CUG of the
subscriber.
RDS9804b
BSCIdOfFirstBSC C - This field indicates the BSC id on which the user is located at the time of call
establishment.
Multimedia call - C This field indicates that the call is a multimedia call
Redirecting number C C This field indicates the address of the last forwarding number
MSC incoming trunk
group extension
MSC outgoing trunk
group extension
RDS14064
5.1.5 Mobile terminated call attempt call forwarding
If the generation of these records is enabled, then an MTC record shall be created for each incoming call
attempt forwarded to another destination. The MTC records shall be produced in the terminating MSC or
in the IMSC.
Table 18: MTC call forwarding record
Record Type M M Mobile Terminated.
Served IMSI M M IMSI of the called party.
Served IMEI OC OC IMEI of the forwarding party if available (IMEI field will be present in CF
RDS8184 / D46475
Calling Number C C The number of the calling party if available.
Connected Number OC OC Only relevant in case of call forwarding where the forwarded-to number is
recorded.
Recording Entity M M The E.164 number of the MSC (visited or interrogating)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Incoming TKGP OM OM The MSC trunk group on which the call originated.
Outgoing TKGP OM OC The trunk group on which the call left the MSC, in order to reach the
forwarded-to subscriber
Location OC OC The identity of the cell or the SAC (including the location area code) in
which the forwarding party is located. (location field is only exist in CF
RDS8184 / D46475
Basic Service M M Bearer or teleservice employed
Change of Service OC OC A list of changes of basic service during a connection each time-stamped.
Supplementary services C C Supplementary services invoked as a result of this connection. This field
invoked.
C
OM
C
C
OM
Seizure time: time of traffic channel seizure for unsuccessful call attempts
Answer time: time of answer for successful calls
Call duration M M The chargeable duration of the connection if successful, the holding time of
the call if unsuccessful.
Data volume C - The number of data segments transmitted, if available at the MSC
Cause for termination M M The reason for the release of the call.
Call reference M M A local identifier distinguishing between transactions at the same MS
Additional Chg. Info OC OC Charge/no charge indicator and additional charging parameters, when
available.
Fixed Network User Rate OC - Indicates the user data rate applied for the connection in the fixed network.
connections.
JIP parameter O O The 6-digit ultipartyn information (NPA-NXX) contained in the Juridiction
Information Parameter (JIP) of the received IAM, if present.
Partial Record Type - Oc Indicates the event (time limit ) that caused the generation of a partial record.
Note: only time limit event is supported
as the others.
GsmSCF Address OC OC The CAMEL server serving the subscriber.
It is the gsmSCF address associated with the O-CSI trigger of the subscriber.
Service key OC OC The CAMEL service logic to be applied.
It is the Service Key associated with the O-CSI trigger of the subscriber.
Redirecting counter C C This field contains the number of call forwarding that occurred on the call, as
obtained from the IAM message.
CUG interlock code O O This field indicates the CUG interlock code
RDS9804b
CUG outgoing access
Indicator
O O This field indicates the calling MS's CUG OA subscription info.
RDS9804b
Multimedia call - C This field indicates that the call is a multimedia call
Redirecting number C C This field indicates the address of the last forwarding number
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


MSC incoming trunk
group extension
MSC outgoing trunk
group extension
RDS14064

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.6 Roaming call attempt
If the generation of these records is enabled then, a roaming record shall be created for each call
redirected to a mobile subscriber roaming outside the HPLMN. These roaming records shall be produced
in the GMSC of the roaming subscribers HPLMN.
5060 WCS position : This record type is not supported (RDS6904).
Because WCS5060 system limitation (roam CDR is generated in other TRIO), network call reference and
and MSC address parameters never present in Roam record currently.
Table 19: Roaming record (RDS6904)
Record Type M M Roaming record.
Served IMSI M M IMSI of the called (roaming) party.
Served MSISDN OM OM The MSISDN of the called (roaming) party.
Calling Number C C The address of the calling party, if available.
Roaming Number M M The Mobile Station Roaming Number employed to route this connection.
Recording Entity M M The E.164 number of the GMSC
Incoming TKGP OM OM The GMSC trunk group on which the call originated.
Outgoing TKGP OM OM The trunk group on which the call left the GMSC
Basic service M M Bearer or teleservice employed.
Supplementary Services C C Supplementary services invoked as a result of this connection. This field
invoked.
Event time stamps C
C
OM
C
C
OM
Seizure time: time of incoming traffic channel seizure (for unsuccessful call attempts)
Data volume C C The number of data segments transmitted if available at the GMSC
Call reference M M A local identifier distinguishing between different services (e.g. calls)
involving the same mobile subscriber
Location Routing Number - OC Location Routing Number for Number Portability feature RDS9189
LRN Query Status Ind. - OC Status of Number Portability query. RDS9189
JIP Query Status
Indicator
Partial Record Type - Oc Indicates the event (time limit ) that caused the generation of a partial record.
Note: only time limit event is supported
MSC incoming trunk
group extension
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


MSC outgoing trunk
group extension
RDS14064
5.1.7 Incoming gateway call attempt
If generation of these records is enabled, an incoming gateway record shall be created for each incoming
call attempt received by a gateway MSC from another network. These records, produced in the gateway
MSC, may be used to settle accounts with other networks. The generation of gateway records shall not
be influenced by the production of MTC records i.e. even if the GMSC and terminating MSC are co-
located a gateway record shall still be produced.
5060 WCS position : the criteria used to determine that the incoming call attempt is received from
another network is based on a trunk group characteristic : inter-network trunk group. An incoming
gateway call attempt CDR is only generated if this characteristic is present on the incoming trunk group.
Table 20: Incoming gateway record
Record Type M M Incoming gateway record
Calling Number C C The number of the calling party if available at this node.
Called Number M M The address of the called party as received in the IAM by the GMSC. This
is the number employed by the GMSC for routing.
Incoming TKGP M M The incoming GMSC trunk group on which the call originated.
Outgoing TKGP OM OC The trunk group on which the call left the GMSC. If available in 3G, this
Event time stamps: M
C
OM
M
C
OM
Seizure time: time of incoming trunk seizure
Answer time: time of answer (successful calls only)
Release time: time of incoming trunk release
Call duration M M The accountable duration (answer -> release of incoming trunk) of the
connection if successful, the call holding time of the incoming trunk for
call attempts.
Data Volume C - If applicable and known at the GMSC
ISDN Bearer Capability OC OC Present if this parameter is available (in the access transport parameter
of the Answer message (ANM)), see TS 29.007 (RDS6904)
Low Layer Compatibility OC OC Present if this parameter is available (in the access transport parameter
of the Answer message (ANM)), see TS 29.007 . (RDS6904)
High Layer Compatibility OC OC Present if this parameter is available (in the access transport parameter
of the Answer message (ANM)), see TS 29.007 . (RDS6904)
Call Reference M M A local identifier distinguishing between transactions.
Sequence no. C C Partial record sequence number, if applicable.
JIP Query Status Indicator - OC Status of Number Portability query.
Partial Record Type - OC Indicates the event (time limit etc.) that caused the generation of a partial
record.
Roaming Number C C The Mobile Station Roaming Number employed to route this connection.
MSC incoming trunk group
extension
C C This field carries information about the incoming trunk group : its
signalling type, its transport interface type, the media-gateway identity,
and the circuit number used. (RDS9851)
MSC outgoing trunk group
extension
C C This field carries information about the outgoing trunk group : its
signalling type, its transport interface type, the media-gateway identity,
and the circuit number used. (RDS9851)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


GsmSCF address C C Identifies the CAMEL server serving the subscriber. Shall be present only
if CAMEL N_CSI is applied. (RDS6034)
Service key C C The CAMEL service logic to be applied. Shall be present only if CAMEL
N_CSI is applied. (RDS6034)
Default call handling OC OC Indicates whether or not a CAMEL call encountered default call. This field
shall be present only if default call handling has been applied, for a
CAMEL service triggered by a N_CSI. (RDS6034)
Information (FCI) message(s). The data can be sent either in one FCI
message or several FCI messages with append indicator. Shall be
present only if CAMEL N_CSI is applied.
It contains the data related to the controlling leg. (RDS6034)
CAMEL call leg information C C Set of CAMEL information Ies. Each of these Ies contains information
related to one outgoing CAMEL call leg. Shall be present only if CAMEL
N_CSI is applied. The Free format data contained in this element is the
one received in a FCI for the corresponding leg. (RDS6034)
(RDS6034)
different network nodes, shall be present if CAMEL is applied. (RDS6034)
ISDN Basic Service OM OM The ISDN basic service employed (RDS6904)
Basic service OC OC Bearer or teleservice employed. (RDS9365)

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.8 Outgoing gateway call attempt
If generation of these records is enabled, an outgoing gateway record shall be created for each outgoing
call attempt from a gateway MSC to another network. These records, produced in the gateway MSC, may
be used to settle accounts with other networks. The generation of gateway records shall not be influenced
by the production of MOC records i.e. even if the GMSC and originating MSC are co-located a gateway
record shall still be produced.
5060 WCS position : the criteria used to ultipart that the outgoing gateway call attempt is going to
another network is based on a trunk group characteristic : inter-network trunk group. An outgoing
gateway call attempt CDR is only generated if this characteristic is present on the outgoing trunk group.
Table 21: Outgoing gateway record
Record Type M M Outgoing gateway record
Called Number M M The address of the called party as received in the IAM by the GMSC. This
is the number employed by the GMSC for routing.
Incoming TKGP OM OC The incoming GMSC trunk group on which the call originated. If available
in 3G, this parameter shall be supplied.
Outgoing TKGP M M The trunk group on which the call left the GMSC.
Event time stamps: M
C
OM
M
C
OM
Seizure time: time of outgoing trunk seizure
Release time: time of outgoing trunk release
Call duration M M The accountable duration (answer -> release of outgoing trunk) of the
connection if successful, the call holding time of the outgoing trunk for call
attempts.
Data Volume C - If applicable and known at the GMSC
(LRN)
LRN Query Status
Indicator
JIP Query Status
Indicator
record.
Roaming Number C C The Mobile Station Roaming Number employed to route this connection,
when applicable. Only present when the CDR is generated by the IMSC.
MSC incoming trunk
group extension
number used. (RDS9851)
MSC outgoing trunk
group extension
number used. (RDS9851)
ISDN Bearer Capability OC OC Present if this parameter is available, see TS 29.007 (RDS6904)
Low Layer Compatibility OC OC Present if this parameter is available, see TS 29.007 (RDS6904)
High Layer Compatibility OC OC Present if this parameter is available, see TS 29.007 (RDS6904)
ISDN basic service C C Basic service sent downstream (RDS6904)
Basic service Oc Oc Bearer or teleservice employed. (RDS9365)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.9 Transit call attempt
If generation of these records is enabled then a transit record may be generated for each incoming call
attempt received by a Transit MSC i.e. neither originating nor terminating. For the avoidance of doubt, a
transit record shall only be produced if no MOC or MTC record is produced for this call attempt by this
MSC. The transit records, produced in the TMSC, may be used to record traffic from particular origins or
to particular destinations.
The transit records are generated only in pure transit MSC, for intra-PLMN transit calls. An inter-PLMN
transit call leads to the generation of an incoming gateway CDR (if the call comes from another
PLMN/PSTN), the generation of an outgoing gateway CDR (if the call comes from inside the PLMN and
goes to another PLMN/PSTN), or the generation of an incoming gateway CDR plus an outgoing gateway
CDR (if the call comes from another PLMN/PSTN and goes out to another PLMN/PSTN).
Table 22: Transit record
Record Type M M Transit.
Recording Entity M M The E.164 number of the transit MSC
Incoming TKGP M M The TMSC trunk group on which the call originated.
Outgoing TKGP M M The trunk group on which the call left the TMSC.
Called Number M M The address of the called party as received in the IAM by the TMSC.
ISDN Basic Service OM OM The ISDN basic service employed
C
OM
C
C
OM
Seizure time: time of incoming trunk seizure for unsuccessful call attempts
Call duration M M The chargeable duration of the connection if successful, the call holding
time for call attempts.
Data Volume C - If applicable and known at the transit MSC
Cause for term. M M The reason for the release of the connection.
JIP Query Status Ind. - OC Status of Number Portability query.
record.
MSC incoming trunk
group extension
MSC outgoing trunk
group extension
GsmSCF address C C Identifies the CAMEL server serving the subscriber. Shall be present only if
CAMEL N_CSI is applied. RDS6034
Service key C C The CAMEL service logic to be applied. Shall be present only if CAMEL
N_CSI is applied. RDS6034
Default call handling OC OC Indicates whether or not a CAMEL call encountered default call. This field
shall be present only if default call handling has been applied, for a CAMEL
service triggered by a N_CSI. RDS6034
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


only if CAMEL N_CSI is applied. It contains the data related to the
controlling leg. RDS6034
CAMEL call leg
information
C C Set of CAMEL information Ies. Each of these Ies contains information
related to one outgoing CAMEL call leg. Shall be present only if CAMEL
N_CSI is applied. The Free format data contained in this element is the one
received in a FCI for the corresponding leg. RDS6034
different network nodes, shall be present if CAMEL is applied. RDS6034

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.10 Supplementary service actions
A supplementary service record may be produced in the NEF of the appropriate MSC or HLR for each
supplementary service action (activation, deactivation, invocation etc.) performed or initiated by the
subscriber.
There are two fundamental types of SS-actions: Call related i.e. as a result of a connection
e.g. Invocation of CLIP / CLIR / AOC etc.
Non-call related i.e. as a result of subscriber controlled input (SCI) e.g. Registration of call
forwarding.
Each supplementary service action shall be performed on one or more basic service groups. If the action
applies to all teleservices and all bearer services (i.e. to all basic services) then the basic services field
shall be omitted.
SCI actions may be recorded in individual SS-action records. Call related actions might be recorded in
either the appropriate call record (MOC/MTC) or in separate SS-action records.
Additional non-standard supplementary service actions may be made available within some networks in
the form of Unstructured Supplementary Service Data (USSD). These actions may also be recorded in
SS-action records. However, as these actions are non-standard they may not include an appropriate
action type, supplementary service code or basic service code.
5060 WCS position : SS-action records are not generated for call related SS, they are only generated for
non-call related actions.
Mobile initiated USSD as well as and network initated USSD are supported since W3.2 (RDS4207).
The records generated by the HLR are out of scope of this document.
Table 23: SS-action record
Record Type M M Supplementary service action.
Served IMSI M M The IMSI of the MS performing the action.
Served IMEI OC OC The IMEI of the ME performing the action.
Served MSISDN OM OM The primary MSISDN of the party performing the action.
MS Classmark M M The mobile station classmark.
Recording Entity M M The E.164 number of the visited MSC.
Location OM OM The identity of the cell or the SAC, including the location area code, from
which the request originated.
Basic Services C C The basic service group(s) to which the supplementary service applies.
This field is not provided if the action applies to all basic services.
Supplementary Service C C The supplementary service for which the request was made.
SS Action C C Activation, deactivation, interrogation etc. Information not available in case
of USSD.
SS Action time stamp M M The time at which the action was requested.
SS Parameters C C Service dependent parameters or unstructured supplementary service
data, if defined for the SS action recorded in this CDR.
SS Action Result C C Result of the requested transaction if unsuccessful.
Call Reference M M A local identifier distinguishing between transactions at the same MS.
available.
System Type - M This field is present when either the UTRAN or GERAN air-interface is
used. It is omitted when the service is provided by a GSM air interface
Service Duration C C Duration of the USSD dialog, if applicable.
RNCIdOfFirstRNC - C This field indicates the RNCid on which the user is located when the SS
action is requested RDS5440
BSCIdOfFirstBSC C - This field indicates the BSCid on which the user is located when the SS
action is requested
RDS14064
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.11 HLR interrogation
If enabled, a HLR interrogation record shall be created for each interrogation performed for a mobile
subscriber. These records may be produced in either the HLR itself or the interrogating MSC.
5060 WCS position: this record type is supported only in case of terminating calls
to a MS (not supported for e.g MT-SMS or USSD). (RDS6904)
If HLR interrogation fails, then fill dummy value (all F) in Roaming number in HLR record (PR D54993).
Table 24: HLR interrogation record (RDS6904)
Record Type M M HLR interrogation.
Served IMSI C C The IMSI of the party being interrogated, if successful
Served MSISDN M M The MSISDN of the subscriber being interrogated.
Recording Entity M M The E.164 Number of the HLR / MSC.
Basic Service OC OC Only for teleservice 21 (SMS-MT).
Routing Number M M Routing number (MSRN, forwarding no.) provided by the HLR if the
interrogation was successful.
Interrogation time stamp M M Time at which the interrogation was invoked.
Number of Forwarding C C The number of times the call has been forwarded if provided by ISUP.
Interrogation Result C C The result of the interrogation request if unsuccessful.
available.
RDS14064

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.12 Location update (VLR)
If enabled, a VLR location update record shall be produced in the VLR for each location registration or
location update received by the VLR for a mobile subscriber.
5060 WCS position : this record type is not supported.
Table 25: Location update (VLR) record
Record Type M M Location update.
Served IMSI M M IMSI of the served MS.
Served MSISDN OM OM The primary MSISDN of the party performing the location update
Recording Entity M M The E.164 number of the entity (VLR or MSC/VLR) generating the record.
Old location
C
C

C
C
Not present for registration:
VMSC E.164 Number
Location Area Code
New location M
M
OM
M
M
OM
VMSC E.164 Number
Location Area Code
Cell Identification or Service Area Code
MS Classmark M M The mobile station classmark.
Update time stamp M M Time at which the update was invoked.
Update Result C C The result of the location update if unsuccessful.
available.
5.1.13 Location update (HLR)
If enabled, an HLR location update record shall be produced in the HLR for each location registration or
location update received by the HLR for a mobile subscriber including location updates received from
subscribers roaming in foreign PLMNs.
Table 26: Location Update (HLR) record
Record Type M M Location update.
Served IMSI M M IMSI of the served MS.
Recording Entity M M The E.164 Number of the HLR.
Old location OC
OC
OC
OC
VMSC E.164 Number
VLR E.164 Number
New location M
M
M
M
VMSC E.164 Number
VLR E.164 Number
Update time stamp M M Time at which the update was invoked.
Update Result C C The result of the location update if unsuccessful.
available.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.14 Short message service, mobile originated
If enabled, an SMS-MO record shall be produced, within the originating MSC, for each short message
sent by a mobile subscriber.
Note: Only one common Option existing on WEM to switch ON/OFF the creation of SMS records. No
separate switch for SMS-MO and SMS-MT.

Table 27: SMS-MO record
Field 2G 3G SMS
over
SGs
Description
Record Type M M M SMS-Mobile originated.
Served IMSI M M M The IMSI of the subscriber sending the short message.
Served IMEI OC OC OC The IMEI of the ME sending the message, if available.
Served
MSISDN
OM OM OM The primary MSISDN of the subscriber sending the message.
MS Classmark M M M The mobile station classmark.
Service Centre M M M The address (E.164) of the SMS-service centre.
Recording
Entity
M M M The E.164 number of the visited MSC
Location OM OM OM The Location Area Code and Cell Identity / Service Area Code from which the
message originated. (R4)
Only part of the E-CGI is stored in the existing CGI field in the CDR for SMS CSFB
case. (RDS13870)
Event Time
stamp
M M M Origination time: The time at which the message was received by the MSC from the
subscriber.
3GPP CDR should record MME adjusted time zone for SMS-over-SGs case
(RDS13870)
Message
Reference
M M M A reference, provided by the MS uniquely identifying this message.
SMS Result C C C The result of the attempted delivery if unsuccessful.
Record
extensions
OC OC OC A set of network/ manufacturer specific extensions to the record, when available.
Destination
number
OM OM OM The destination number dialled by the MS sending the short message.
CAMELSMSInf
ormation
C C C Set of CAMEL information Ies. Each of these Ies contains information related to
CAMEL call leg related for the SMS. Shall be present only if CAMEL is applied.
System Type - M M This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is
present when either the UTRAN or GERAN air-interface is used on call setup. For
an open CDR in a 2G NE (responsible for the CDR), the field is not present (even if
the call is handed off to a 3G air interface). For a CDR in a 3G NE (responsible for
the CDR), the value unknown shall be used after handover.
Location
Extension
- - O
M

The 12 most significant bits of the E-UTRAN Cell Identity are included if E-UTRAN is
used to deliver the SMS. (R8)
Hot billing
subscriber
C C C Indicates that the subscriber is a hot billing subscriber. It means that one record is
transmitted in real time towards the billing system (or a dedicated system), and that
a second record is transmitted towards the billing system as the others.
RNCIdOfFirstR
NC
- C C This field indicates the RNCid on which the user is located when the Short Message
is sent RDS5440
BSCIdOfFirstB
SC
C - - This field indicates the BSCid on which the user is located when the Short Message
is sent
SMS size OM OM OM This field indicates the size in bytes of the SMS (not implemented yet)
Subscribed
OSSS Codes
OC OC OC This field describe OSSS code from HLR
RDS14064
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.15 SMS Short message service, mobile terminated
If enabled, an SMS-MT record shall be produced, within the terminating MSC, for each short message
received by a mobile subscriber.
Note: Only one common Option existing on WEM to switch ON/OFF the creation of SMS records. No
separate switch for SMS-MO and SMS-MT.
Table 28: SMS-MT record
Field 2G 3G SMS
over
SGs
Description
Record Type M M M SMS-Mobile Terminated.
Service Centre M M M The E.164 address of the SMS centre.
Served IMSI M M M The IMSI of the receiving party.
Served IMEI OC OC OC The IMEI of the receiving party, if available.
Served
MSISDN
OM OM OM The MSISDN of the receiving party.
MS Classmark M C C The mobile station classmark.
Recording
Entity
M M M The E.164 number of the visited MSC.
Location OM OM OM The Location Area Code and Cell Identity /Service Area Code to which the message
was delivered.
Only part of the E-CGI is stored in the existing CGI field in the CDR for SMS CSFB
case. (RDS13870)
Event time
stamp
M M M Delivery time: time at which message was sent to the MS by the MSC.
3GPP CDR should record MME adjusted time zone for SMS-over-SGs case
(RDS13870)
SMS Result C C C The result of the attempted delivery if unsuccessful.
Record
extensions
OC OC OC A set of network/ manufacturer specific extensions to the record, when available.
See below.
System Type C M M This field is present when either the UTRAN or GERAN air-interface is used. It is
omitted when the service is provided by a GSM air interface
CAMELSMSInf
ormation
C C C Set of CAMEL information Ies. Each of these Ies contains information related to
CAMEL call leg related for the SMS. Shall be present only if CAMEL is applied.
( 3GPP Release 5, not implemented yet)
Location
Extension
- - O
M

The 12 most significant bits of the E-UTRAN Cell Identity are included if E-UTRAN is
used to deliver the SMS. (R8)
Hot billing
subscriber
C C C Indicates that the subscriber is a hot billing subscriber. It means that one record is
transmitted in real time towards the billing system (or a dedicated system), and that
a second record is transmitted towards the billing system as the others.
SMS
Originating
Number
C C C The number of the sender of the SMS RDS4318
RNCIdOfFirstR
NC
- C C This field indicates the RNCid on which the user is located when the Short Message
is sent RDS5440
BSCIdOfFirstB
SC
C - - This field indicates the BSCid on which the user is located when the Short Message
is sent
SMS size OM OM OM This field indicates the size in bytes of the SMS (not implemented yet)
Subscribed
OSSS Codes
OC OC OC This field describe OSSS code from HLR
RDS14064
5.1.16 SMS-MO interworking record
If enabled, an SMS-MO interworking record shall be produced, within the interworking MSC, for each
short message generated by a mobile subscriber. These records may be used to settle accounts between
PLMNs and SMS service centres. Where the Interworking MSC is also the originating MSC, an SMS-MO
CDR will also be generated.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Table 29: SMS-MO interworking record
Record Type M M SMS-MO interworking record.
Service Centre M M The E.164 address of the SMS service centre.
Served IMSI M M The IMSI of the sending party.
Event Time stamp M M The time at which the message was received by the interworking function.
SMS Result C C The result of the attempted delivery if unsuccessful, when available.
Record extensions OC OC A set of network/ manufacturer specific extensions to the record.

5.1.17 SMS-MT gateway record
If enabled, an SMS-MT gateway record shall be produced, within the gateway MSC, for each short
message sent to a mobile subscriber. Where the Gateway MSC is also the terminating MSC, an SMS-MT
CDR will also be generated.
Table 30: SMS-MT gateway record
Record Type M M SMS-MT gateway record.
Service Centre M M The E.164 address of the SMS service centre.
Served IMSI M M The IMSI of the receiving party.
Served MSISDN OM OM The MSISDN of the receiving party.
Event Time stamp M M The time at which the message was received by the gateway.
SMS Result C C The result of the attempted delivery if unsuccessful.
available.
5.1.18 Common equipment usage record
If enabled, a common equipment usage record shall be created in the VMSC to record the usage
(duration) of common equipment, e.g. conference circuits, employed by a mobile subscriber.
Table 31: Common equipment usage record
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Record Type M M Common equipment usage record.
Equipment type M M e.g. Conference circuit.
Equipment Id. C C The local id. Of the equipment employed.
Served IMSI M M The IMSI of the party responsible for the seizure of the equipment.
Served MSISDN OM OM The primary MSISDN of the served party.
Recording Entity M M The E.164 number of the MSC in which the equipment is located.
Basic service C C Bearer or teleservice employed, if appropriate.
Rate Adaptation OC OC Present if rate adaption parameters for the basic service were signalled
Fixed Network User Rate OC OC Indicates the user data rate applied for the connection in the fixed network.
connections.
Supp. Services C C Supplementary services invoked in connection with this equipment.
Event Time Stamp M
OM
M
OM
Seizure time: the time at which the equipment was seized.
Release time: the time at which the equipment was released.
Call Duration M M The total duration of the usage of the equipment.
Sequence no. C C Partial record sequence number if applicable.
available.
System Type - M This field indicates the use of GERAN, UTRAN (or a value of unknown).
This field is present when either the UTRAN or GERAN air-interface is
used on call setup. For an open CDR in a 2G NE (responsible for the
CDR), the field is not present (even if the call is handed off to a 3G air
interface). For a CDR in a 3G NE (responsible for the CDR), the value
unknown shall be used after handover.
record.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.19 Terminating CAMEL call attempt
If the generation of these records is enabled, a terminating CAMEL call attempt record shall be generated
for each call toward a subscriber with a T-CSI or VT-CSI and if the terminating trigger criteria are met.
The record is generated in the GMSC/gsmSSF carrying out the terminating CAMEL call handling and in
the MSC server/gsmSSF carrying out the visited terminating CAMEL call attempt.
Table 32: Terminating CAMEL record
Record Type M M Terminating CAMEL interrogation.
Served IMSI M M IMSI of the called party
Recording Entity M M The E.164 number of the GMSC.
Interrogation time
stamp
M M Time at which the interrogation was invoked.
CAMEL Destination
Number
M M The number available for routing after the CAMEL server enquiry.
GsmSCF Address M M The CAMEL server serving the subscriber.
Service key M M The CAMEL service logic to be applied.
Network call
reference
M M An identifier to correlate transactions on the same call taking place in different
network nodes.
MSC Address M M This field contains the E.164 number assigned to the MSC that generated the
network call reference.
Default call
handling
OC OC Indicates whether or not a CAMEL call encountered default call handling. This
field shall be present only if default call handling has been applied.
Called Number M M The address of the called party as received by the GMSC/gsmSSF.
Incoming TKGP OM OC The GMSC trunk group on which the call originated. If available in 3G, this
Outgoing TKGP OM OC The trunk group on which the call left the GMSC. If available in 3G, this
C
OM
C
C
OM
attempts)
Call duration M M The chargeable duration of the connection for successful calls, the holding time
of call attempts.
Data volume C - The number of data segments transmitted if available at the GMSC
Cause for
termination
M M The reason for the release of the connection.
Call reference M M A local identifier distinguishing between different services (e.g. calls) involving
the same mobile subscriber
Number of DP
encountered
encountered.
Level of CAMEL
service
OC OC Indicator of the complexity of the CAMEL feature used.
Information (FCI) message(s). The data can be sent either in one FCI message
or several FCI messages with append indicator.
CAMEL call leg
information
C C Set of CAMEL information Ies. Each of these Ies contains information related to
one outgoing CAMEL call leg.
Free format data
append indicator
C C Indicator if free format data from this CDR is to be appended to free format data
in previous partial CDR.
MSC server
indication
C C Indication if the CAMEL call handling is active in the MSC server.
Default call
handling 2
OC OC Indicates whether or not a CAMEL call encountered default call handling for 2
nd

service such as dialled service. This field shall be present only if default call
handling has been applied.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


GsmSCF address
2
C C Identifies the CAMEL server serving the subscriber for 2
nd
service such as
dialled service. Shall be present only if CAMEL is applied for 2
nd
service.
nd
service such as dialled service.
Shall be present only if CAMEL is applied for 2
nd
service.
Free format Data 2 C C This field contains data sent by the gsmSCF in the FCI message(s) for 2
nd

service such as dialled service. The data can be sent either in one FCI message
or several FCI messages with append indicator. Shall be present only if CAMEL
is applied for 2
nd
service.
Free format data
append indicator 2
nd
service from this CDR is to be appended to
free format data in previous partial CDR. Shall be present only if CAMEL is
applied for 2
nd
service.
Location Routing
Number (LRN)
- Oc Location Routing Number for Number Portability feature RDS9189
LRN Source
Indicator
- OC LRN Source Indicator tells the source of the LRN RDS9189

LRN Query Status
Indicator
JIP Source
Indicator
- OC JIP Source Indicator tells the source of the JIP
JIP Query Status
Indicator
Partial Record
Type
- OC Indicates the event (time limit etc.) that caused the generation of a partial
record.
MSC incoming
trunk group
extension
C C This field carries information about the incoming trunk group : its signalling type,
its transport interface type, the media-gateway identity, and the circuit number
used. RDS9851
MSC outgoing
trunk group
extension
C C This field carries information about the outgoing trunk group : its signalling type,
its transport interface type, the media-gateway identity, and the circuit number
used. RDS9851
Subscribed OSSS
Codes
OC OC This field describe OSSS code from HLR
RDS14064
5.1.20 IMEI observation ticket
An observed IMEI ticket is generated whenever greylisted, blacklisted or non-whitelisted mobile
equipment is detected during an IMEI check. The purpose of the ticket is to link the mobile equipment
under observation with its current user (IMSI). The ticket also includes information describing when and
where the equipment was used to enable the tracking of such equipment. Finally, if the ticket was
triggered by a call attempt, a call reference is provided in order to locate the corresponding call record.
The IMEI tickets are generated by the NEF of the MSC performing the IMEI check.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Table 33: IMEI ticket
Served IMEI M M IMEI of the observed mobile equipment
IMEI Status M M The result of the IMEI check e.g. blacklisted, greylisted, unknown.
Served IMSI M M The IMSI of the subscriber currently using the mobile equipment.
Served MSISDN C C The MSISDN of the subscriber currently using the observed mobile
equipment, only available if the event that triggered the IMEI check was an
MOC, MTC, SMS-MO or SMS-MT
Recording Entity M M The E.164 number of the recording MSC.
Event Time Stamp M M The time at which the IMEI check was performed.
Location M M The location area code and cell identity of the cell from which the mobile
equipment was used.
IMEI Check Event OM OM The event that caused IMEI checking to take place
Call Reference OC OC Only available if the IMEI check was related to an MOC or MTC
available.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.21 Mobile terminated location request (MT-LR)
If enabled, an LCS-MT record shall be produced, within the visited MSC, for each mobile a terminated
location request is performed for.
Table 34: LCS-MT record
Record Type M M LCS-MT record.
LCS Client Type M M The type of the LCS client that invoked the LR.
LCS Client Identity M M Further identification of the LCS client.
Served IMSI M M The IMSI of the subscriber the LR is invoked for.
Served MSISDN OM OM The MSISDN of the subscriber the LR is invoked for.
Location Type M M The type of the location request.
LCS QoS C C QoS of the LR, if available.
LCS Priority C C Priority of the LR, if available.
MLC Number M M The E.164 address of the requesting GMLC.
Event Time Stamp M M The time at which the LR was received by the MSC.
MeasureDuration OM OM The duration of proceeding the location request.
Notification To MS User C C The privacy notification to MS user that was applicable when the LR was
invoked, if available.
Privacy Override C C This parameter indicates if MS privacy was overridden by the LCS client, if
available.
Location OM - The LAC and CI when the LR is received.
Location Estimate OC OC The location estimate for the subscriber if contained in geographic position
and the LR was successful.
Positioning Data C C The positioning method used or attempted, if available.
LCS Cause OC OC The result of the LR if any failure or partial success happened as known at
the radio interface.
Cause for Termination M M The reason for the termination of the location service.
Diagnostics C C A more detailed information about the Cause for Termination if any failure
or partial success happened.
System Type - M This field indicates the use of GERAN or UTRAN at the time of the LCS request.
This field is present when either the UTRAN or GERAN air-interface is used on
call setup.
Hot billing subscriber C C Indicates that the subscriber is a hot billing subscriber. RDS5440
RNCIdOfFirstRNC - C This field indicates the RNCid on which the user is located when the Short
Message is sent RDS5440
BSCIdOfFirstBSC C - This field indicates the BSCid on which the user is located when the Short
RDS14064

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.22 Mobile originated location request (MO-LR)
If enabled, an LCS-MO record shall be produced, within the visited MSC, for each mobile an originated
location request is performed for.
Table 35: LCS-MO record
Record Type M M LCS-MO record.
LCS Client Type C C The type of the LCS client that invoked the LR, if available.
LCS Client Identity C C Further identification of the LCS client, if available.
Served IMSI M M The IMSI of the subscriber the LR is invoked for.
Served MSISDN OM OM The MSISDN of the subscriber the LR is invoked for.
MOLR Type M M The type of the LR.
LCS Priority OC OC Priority of the LR, if available.
MLC Number C C The E.164 address of the involved GMLC, if available.
LCS Cause C C The result of the LR if any failure or partial success happened as known at
call setup.
RDS14064

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.23 Network induced location request (NI-LR)
If enabled, an LCS-NI record shall be produced, within the visited MSC, for each network induced location
request performed for a MS e.g. in case of emergency call.
Table 36 : LCS-NI record
Record Type M M LCS-NI record.
LCS Client Type C C The type of the LCS client that invoked the LR, if available.
LCS Client Identity C C Further identification of the LCS client, if available.
Served IMSI C C The IMSI of the calling party the LR is executed for if supplied by the UE.
Served MSISDN C C The MSISDN of the calling party the LR is executed for if supplied by the
UE.
Served IMEI C C The IMEI of the calling party the LR is executed for if available.
EMS-Digits OC OC The emergency service routing digits, if emergency call.
EMS-Key OC OC The emergency service routing key, if emergency call.
LCS Priority C C Priority of the LR, if available.
MLC Number C C The E.164 address of the involved GMLC, if available.
LCS Cause C C The result of the LR if any failure or partial success happened as known at
call setup.
RDS14064

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.24 Mobile originated call attempt (CAMEL CPH adapted version)
If the MSC / gsmSCF is able to provide CAMEL CPH services, this kind of record shall replace records
according to clause 4.1 Mobile originated call attempt. This applies to all mobile originated call attempts,
even if no CPH operations are used in the individual call. Record fields that are specific to individual
outgoing legs are recorded in the grouped field Camel Call Leg Information.
If the generation of this kind of record is enabled then the MSC shall produce one MOC record. The
incoming leg is recorded in the main body. Whenever there is a CAMEL dialogue, outgoing legs of the
same call segment are recorded in the grouped field "CAMEL call leg information". Further legs in new
call segments are recorded in CDRs of type "4.y New Call Segment in a MO, CF or MT CAMEL
Dialogue".
Examples for call situations where this type of record applies are the following:
- Mobile originating call without CPH being involved,
- Mobile originating call continuing after disconnect of the incoming leg in case of no partial record
generation.
When partial records are generated, they are of type4.y New Call Segment in a MO, CF or MT CAMEL
Dialogue,
- Mobile originating call with more than one outgoing leg on this call segment,
- Mobile originating call in which the original outgoing leg has been disconnected by gsmSCF.
Disconnect of the incoming leg is recorded by filling the related record fields in the main body of the
record. Optionally a partial record may be generated. This partial record is of type 4.y gsmSSF initiated
CAMEL CPH call attempt.
Disappearing (DisconnectLeg, SplitLeg, etc.) of an outgoing leg is recorded by filling the related record
fields in the Camel Call Leg Information field for the disappearing leg. Optionally a partial record may be
generated. This partial record does not contain information of the leg that disappeared, i.e. it does not
contain a Camel Call Leg Information field for that leg.
Connection of a further leg to this call segment is recorded by adding a further field 'Camel Call Leg
Information'. Optionally a partial record may be generated.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Table 37: MOC record (CAMEL CPH adapted version)
Served IMSI M M IMSI of the calling party.
Served IMEI C C IMEI of the calling ME, if available.
Served MSISDN OM OM The primary MSISDN of the calling party.
Called Number M M The address of the called party i.e. the number dialled by the calling
subscriber.
Incoming TKGP OM OC The MSC trunk group on which the call originated, usually from the BSS. If
Location M M The identity of the cell or the SAC at the time of CDR creation, including the
location area code.
time-stamped.
Basic service M M Bearer or teleservice employed. 'speech' in case of CAMEL CPH calls.
Supp. Services C C Supplementary services invoked as a result of this connection. This field
invoked.
AOC Parameters OC OC The charge advice parameters sent to the MS on call set-up. This field shall
be supplied only when AoC parameters have been sent.
Change of AOC
Parameters
OC OC New AOC parameters sent to the MS e.g. as a result of a tariff switch over,
including the time at which the new set was applied. This field shall be
MS Classmark M M The mobile station classmark employed on call set-up.
Change of Classmark OC OC A list of changes to the classmark during the connection each time-stamped.
C
OM
C
C
OM
attempts)
Answer: time of answer (for successful calls)
for the incoming leg.
Call duration M M The chargeable duration of the connection of the incoming leg for successful
calls, the holding time of the incoming leg for call attempts.
Radio Chan. Used M - The type of radio channel actually used (full or half rate).
Change of Rad. Chan. OC - A list of changes each time stamped.
Call reference M M A local identifier distinguishing between transactions on the same MS
Record extensions OC OC A set of network / manufacturer specific extensions to the record, when
available.
GsmSCF address M M Identifies the CAMEL server serving the subscriber.
Service key C C The CAMEL service logic to be applied.
Network call reference M M An identifier to correlate transactions on the same call taking place in
different network nodes.
Speech Version
Supported
Speech Version Used OM - Speech version used for that call
Number of DP
encountered
OM OM Number that counts how often armed detection points (TDP and EDP) were
encountered. Sum of all DPs encountered in this call.
Level of CAMEL service OM OM Indicator for the complexity of the CAMEL feature used.
message or several FCI messages with append indicator.
CAMEL call leg
information
C C Set of CAMEL information IEs. Each of these IEs contains information
related to one outgoing CAMEL call leg.
CAMEL Destination
Number
- - Destination modified by camel service.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Translated Number - - Called number after digit translation within the MSC.
Connected Number - - Number of connected party if different from 'CAMEL Destination Number'.
Roaming Number - - MSRN to route this leg (if applicable).
MSC outgoing TKGP - - Trunk on which the leg leaves the MSC.
Seizure Time - - Time of traffic channel seizure for this leg.
Answer Time - - Time when the answer message is received for this leg.
Release Time - - Time when the leg is released or moved into another call segment.
Call Duration - - Time between answer and release timestamp of this leg.
Additional Chg. Info - - Charge/no charge indicator and additional charging parameters, when
available.
Free Format Data - - If received in the FCI message from SCF.
Free Format Data
Append
- - If received in the FCI message from SCF.
Free Format Data 2 - - If provided in the FCI message for a 2
nd
service.
Free Format Data
Append 2
- - If provided in the FCI message for a 2
nd
service.
Diagnostics - - Detailed reason for disappearing of the leg in this call segment.
Cause for Termination - - The reason for disappearing of the leg in this call segment.
Default Call Handling 2 - - Present if a 2
nd
service (DP3) is triggered.
gsm-SCF Address 2 - - Present if a 2
nd
Service Key 2 - - Present if a 2
nd
Free Format Data
Incoming 2
nd
service.
Free Format Data
Append Incoming 2
nd
service.
Location Routing
Number (LRN)
- - For Number Portability feature, not available in 2G records.
LRN Source Indicator - - Source of the LRN, not available in 2G records.
LRN Query Status
Indicator
- - Status of Number Portability query, not available in 2G records.
JIP Parameter - - Jurisdiction Information Parameter, not available in 2G records.
JIP Source Indicator - - The source of the JIP, not available in 2G records.
JIP Query Status
Indicator
Free Format Data
Append Indicator
data in previous partial CDR. Shall be present only if CAMEL id applied.
System Type - M This field indicates the use of GERAN, UTRAN (or a value of unknown) of
the incoming leg. This field is present when either the UTRAN or GERAN air-
interface is used on call set-up. For an open CDR in a 2G NE (responsible
for the CDR), the field is not present (even if the call is handed off to a 3G air
interface).For a CDR in a 3G NE (responsible for the CDR), the value
unknown shall be used after handover.
record.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.25 gsmSCF initiated CAMEL CPH call attempt
If the generation of these records is enabled then an MOC record shall be created for each gsmSCF
initiated call attempt and for new parties in new call segments, which are created in a new call dialogue.
Examples for call situations where this type of record applies are the following:
- gsmSCF initiated call segment association (new call):
There is only one call segment. It contains the outgoing leg, which is created via CPH initiate call attempt
operation (ICA).
This outgoing leg can be connected to an SRF, which is recorded in the same record in the field
'Camel Call Leg Information'.
- gsmSCF initiated new party in an already established gsmSCF initiated CAP dialogue (new leg):
In a new call dialogue a further call leg in a new call segment is initiated via ICA operation.
This call segment contains one outgoing leg, which can be connected to an SRF. This leg and if
used the SRF are recorded in the record for this call segment in the field 'Camel Call Leg Information'.
This leg can be connected to the other outgoing leg. This would terminate the call segment and
thus the call record. The 'Cause for Termination' indicates the reason for disappearing of the leg in this
call segment. The Timestamps ('Call Duration', 'Release Time', etc.) are filled in. The record of the call
segment the leg is moved to records the leg in a further field 'Camel Call Leg Information'.
The other leg could be connected to this leg which is recorded by adding a further field 'Camel
Call Leg Information'.
Record fields for an incoming leg do not exist, because there is no incoming leg in the call segment this
record is created for.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Table 38: MOC CPH record (gsmSCF initiated)
Served MSISDN OM OM The number of the initiating party. Calling Party Number as received in the
ICA operation.
Called Number M M The address of the called party.
available.
GsmSCF address C C Identifies the CAMEL server serving the subscriber (network call reference).
record.
Number of DP
encountered
Level of CAMEL service OC OC Indicator for the complexity of the CAMEL feature used.
CAMEL call leg
information
C C Set of CAMEL information IEs. Each of these IEs contains information related
to one outgoing CAMEL call leg.
CAMEL Destination
Number
- - Destination as received in the ICA operation.
available.
Free Format Data
Append
nd
service.
Free Format Data
Append 2
nd
service.
nd
nd
nd
Free Format Data
Incoming 2
nd
service.
Free Format Data
Append Incoming 2
nd
service.
Location Routing
Number (LRN)
LRN Query Status
Indicator
JIP Query Status
Indicator
record.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.1.26 New Call Segment in a MO, CF and MT CAMEL Dialogue
If the generation of these records is enabled then an MOC record shall be created for call segments
without incoming leg, generated by a CAMEL dialogue for mobile originated, call forwarding or mobile
terminating call attempts. Examples for call situations where this type of record applies are the following:
- Additional call segment, which is created by means of a SplitLeg operation or ICA (new party)
operation.
This call segment contains one outgoing leg, which can be connected to an SRF. This leg and if
used the SRF are recorded in the record for this call segment in the field 'Camel Call Leg Information'.
This leg can be connected to the other outgoing leg. This would terminate the call segment and
thus the call record. The 'Cause for Termination' indicates the reason for disappearing of the leg in this
call segment. The Timestamps ('Call Duration', 'Release Time', etc.) are filled in. The record of the call
segment the leg is moved to records the leg in a further field 'Camel Call Leg Information'.
The other leg could be connected to this leg which is recorded by adding a further field 'Camel
Call Leg Information'.
- Call segment where the incoming leg disappeared (e.g. due to SplitLeg or DisconnectLeg
operation). A record of this type is generated if partial records are generated.
Although an incoming leg does not exists, the 'IMSI', the 'IMEI' and the 'Service Key' is recorded in the
main body.

Table 39: MOC CPH record (new call segment)
Served IMSI M M IMSI of the served party (calling party in case of MOC, forwarding party in
case of call forwarding respectively called party in case of MTC).
Served IMEI C C IMEI of the served ME, if available (calling party in case of MOC, forwarding
party in case of call forwarding respectively called party in case of MTC).
Served MSISDN OM OM The MSISDN of the served party (calling party in case of MOC, forwarding
party in case of call forwarding respectively called party in case of MTC).
Called Number M M The address of the called party.
Supp. Services C C Supplementary services invoked as a result of this connection. This field
invoked.
available.
GsmSCF address C C Identifies the CAMEL server serving the subscriber.
Service Key C C The CAMEL service logic to be applied.
Number of DP
encountered
Level of CAMEL service OC OC Indicator for the complexity of the CAMEL feature used.
CAMEL call leg
information
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


CAMEL Destination
Number
- - Destination as received in the ICA operation.
available.
Free Format Data
Append
nd
service.
Free Format Data
Append 2
nd
service.
nd
nd
nd
Free Format Data
Incoming 2
nd
service.
Free Format Data
Append Incoming 2
nd
service.
Location Routing
Number (LRN)
LRN Query Status
Indicator
JIP Query Status
Indicator
record.

5.1.27 Mobile originated call forwarding attempt (CAMEL CPH adapted version)
according to clause 4.3 Mobile originated call forwarding attempt. This applies to all mobile originated call
forwarding attempts, even if no CPH operations are used in the individual call.
If the generation of MOC records is enabled in the forwarding MSC then the forwarding MSC shall
produce an MOC record for the forwarded-leg of the call.
If further legs in new call segments are generated by this CAMEL dialogue, they are recorded in CDRs of
type 4.y New Call Segment in a MO, CF or MT CAMEL Dialogue.
Connection of a further leg to this call segment is recorded by adding a further field 'Camel Call Leg
Information'. Optionally a partial record may be generated.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Table 40: MOC, call forwarding record (CAMEL CPH adapted version)
Served IMSI M M IMSI of the forwarding party.
Served MSISDN OM OM The MSISDN of the forwarding party.
Calling Number OM OM The address of the calling party.
Called Number M M The address of the forwarded-to party.
Recording Entity M M The E.164 number of the forwarding MSC
Incoming TKGP OM OM The MSC trunk group on which the call originated at the forwarding MSC.
Basic service C C 'speech' in case of CAMEL CPH, not always available e.g. in case of call
forwarding unconditional.
Supplementary
Services
C C Supplementary services invoked as a result of this connection, if this
information is available to the forwarding node. This field shall be present when
one or more supplementary services have been invoked.
C
OM
C
C
OM
attempts)
available.
GsmSCF address C C Identifies the CAMEL server serving the subscriber.
Service key C C The CAMEL service logic to be applied.
Network call reference C C An identifier to correlate transactions on the same call taking place in different
network nodes.
CAMEL initiated CF
indicator
OC OC Indicates that the CAMEL server initiated call forwarding. Not available in case
of gsm call forwarding.
Default call handling OC OC Indicates whether or not a CAMEL call encountered default call handling. This
field shall be present only if default call handling has been applied.
Number of DP
encountered
Level of CAMEL service OC OC Indicator of the complexity of the CAMEL feature used.
Information (FCI) messages. The data can be sent either in one FCI message
or several FCI messages with append indicator.
CAMEL call leg
information
C C Set of CAMEL information IEs. Each of these IEs contains information related
to one outgoing CAMEL call leg.
CAMEL Destination
Number
- - Destination modified by CAMEL service.
available.
Free Format Data
Append
nd
service.
Free Format Data
Append 2
nd
service.
nd
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


nd
nd
Free Format Data
Incoming 2
nd
service.
Free Format Data
Append Incoming 2
nd
service.
Location Routing
Number (LRN)
LRN Query Status
Indicator
JIP Query Status
Indicator
Free format data
append indicator
data in previous partial CDR. Shall be present only if CAMEL is applied.
record.

5.1.28 Terminating CAMEL call attempt (CAMEL CPH adapted version)
according to clause 4.18 Terminating CAMEL call attempt. This applies to all terminating CAMEL call
attempts, even if no CPH operations are used in the individual call.
If the generation of these records is enabled, a terminating CAMEL call attempt record shall be generated
for each call involving CAMEL CPH operations. The record is generated in the GMSC/gsmSSF carrying
out the terminating CAMEL call handling and in the MSC server/gsmSSF carrying out the visited
terminating CAMEL call attempt.
If further legs in new call segments are generated by this CAMEL dialogue, they are recorded in CDRs of
type 4.y New Call Segment in a MO, CF or MT CAMEL Dialogue.

Table 41: Terminating CAMEL record (CPH adapted version)
Record Type M M Terminating CAMEL interrogation.
Served IMSI M M IMSI of the called party
Recording Entity M M The E.164 number of the GMSC.
Interrogation time
stamp
M M Time at which the interrogation was invoked.
GsmSCF Address M M The CAMEL server serving the subscriber.
Service key M M The CAMEL service logic to be applied.
MSC Address M M This field contains the E.164 number assigned to the MSC that generated
the network call reference.
available.
Called Number M M The address of the called party as received by the GMSC/gsmSSF.
Incoming TKGP OM OC The GMSC trunk group on which the call originated. If available in 3G, this
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


C
OM
C
C
OM
attempts)
dSequence no. C C Partial record sequence number, only present in case of partial records.
Number of DP
encountered
Level of CAMEL service OC OC Indicator of the complexity of the CAMEL feature used.
message or several FCI messages with append indicator.
CAMEL call leg
information
CAMEL Destination
Number
- - Destination as received in the ICA operation or overwritten by TDP3.
Roaming Number - - MSRN or B-party (if applicable).
CAMEL Init CF
Indicator
- - Indicates that the CAMEL server initiated call forwarding.
available.
Free Format Data
Append
nd
service.
Free Format Data
Append 2
nd
service.
nd
nd
nd
Free Format Data
Incoming 2
nd
service.
Free Format Data
Append Incoming 2
nd
service.
Location Routing
Number (LRN)
LRN Query Status
Indicator
JIP Query Status
Indicator
Free format data
append indicator
data in previous partial CDR.
MSC server indication C C Indication if the CAMEL call handling is active in the MSC server.
record.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2 Description of Record Fields
This clause contains a brief description of each field of the CDRs described in the previous clause.
5.2.1 Additional Charging Information
This field consists of two parts, a charge indicator and additional charging parameters. The charge
indicator is derived from the information contained within the ISUP (or BICC) backward call indicator and
may be used to store a charge indicator (charge/no charge) received from another network node. The
additional charging parameters are non-standard and intended to permit the inclusion of further charging
information received from Intelligent Network and/or Value Added Service nodes.
5060 WCS position : in the MOC CDR, the field only contains the charge/no charge indication received
in the backward call indicators. In the MTC CDR, this field is only present in case of OPTION
3GPP_ADD_CHG_INF_CHARGE is set to Y (RDS7564a). In case this parameter is present in MTC, it
is set hardcoded to the charge value.
5.2.2 AoC parameters / change of AoC parameters
The AoC parameter field contains the set of charge advice (AoC) parameters sent to the MS on call set-
up. If further sets of parameters are sent during the call, as a result of a tariff switch-over for example,
then this may be recorded in the Change of AoC Parameter field including the time at which the change
occurred.
It should be noted that the Change of AoC Parms. Field is optional and not required if partial records are
generated on tariff switch-over.
The AoC parameters are defined in TS 22.024 [7].
5060 WCS position : these parameters are not recorded. They will be recorded when the AoC function
will be available.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.3 Basic Service / change of service / ISDN Basic Service
The basic service field contains the code of the basic service employed on call set-up. Any alteration to
the basic service during the connection may be recorded in the change of service field including the time
at which the change took place.
The change of service field is optional and may be omitted if partial records are created whenever the
basic service is changed.
The coding of basic services is defined in detail in TS 29.002 [11].
In the case of the transit record the GSM basic service employed is generally not available. However, if
the device on which the call originates/terminates is connected via ISDN digital subscriber signalling then
the appropriate ISDN basic service code may be recorded in the record. One possible example includes
the direct connection of an ISDN PABX to an MSC/VLR.
5060 WCS position : the change of service is not recorded. It will be recorded when the 5060 WCS will
support the change of service during the call functionality.
The available values for teleservices are :
- telephony
- emergency calls
- automatic facsimile Group 3
The available values for bearer services are :
- asynchronous bearer service 9.6 kbps (0x16)
- asynchronous bearer service General data (0x17)
- synchronous bearer service general data (0x1F)
The synchronous bearer service general data (GBS30) is used to record multimedia calls.
The available values for the ISDN basic service are :
- speech (0x01)
- unrestricted digital information (0x02)
- 3.1 kHz audio (0x03)
The value depends on the TMR received in the IAM message. If the TMR received is different from
speech, unrestricted digital information or 3.1 kHz audio, then the ISDN basic service is set to
unrestricted digital information.
Above are most used value and not complete value list, detail in TS 29.002 [12].

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.4 Call duration
This field contains the relevant call duration in seconds. For incomplete calls (call attempts) the relevant
duration is the call holding time from the seizure to the release of the traffic channel. For complete
(answered) calls this is the chargeable duration from answer to release of the traffic channel. For partial
records this is the duration of the individual partial record and not the cumulative duration of the call.
It should be noted that the time stamps may be expressed in terms of tenths of seconds or even
milliseconds and, as a result, the calculation of the call duration may result in the rounding or truncation of
the measured duration to a whole number of seconds.
Whether or not rounding or truncation is to be used is considered to be outside the scope of the present
document subject to the following restrictions:
1) A call duration of zero seconds shall not be accepted.
2) The same method of truncation/rounding shall be applied to both single and partial records.

5060 WCS position :
The timestamps and the call duration are expressed in terms of seconds.
Three rounding methods are implemented :
- the up method rounds the duration to the next superior integer
- the truncate method rounds to the next inferior integer
- the closest method rounds to the closest integer; when the fractional part is 0.5, then the method
rounds to the next superior integer
- In the cases where the call duration would be normally 0 for a successful call, then the call duration is
forced to 1.
Note: 5060 WCS does not support yet the CAMEL call duration recording mentioned below.
Note: all partial CDR call duration will be closest irrespective what has been configured on WEM.
(PR79087)
WCS support flexible value for closest method for the call duration in CDR for 3GPP CDR format.
(RDS16308) detail see 3GPP_CDR_value_for_closest in chapter 6.2.

If CAMEL is invoked for the call and a control relationship is existing, the call might continue after a
RELEASE or a DISCONNECT from the called party side received by the gsmSSF. The call duration of
the incoming leg is stored in the main body of the call record. For each outgoing leg the call duration is
stored in the respective CAMELInformation module. If a call leg does not reach answer status and
attempt charging is enabled a CAMELInformation module containing the holding time is generated.
An example of how to use the call duration and the timestamps is given in Figure 2. It shows a CAMEL
controlled mobile originated follow-on scenario. The uppermost arrow marks the over all duration of the
call that is to be measured and stored in the main body of the respective MOC record. The duration
before t
5
(incoming leg) or t
4
(outgoing leg) needs not to be stored since the call is answered later on. The
call duration in the first outgoing leg module contains the time interval from t
4
to t
6
(period ). The call
duration measurement of the second outleg is started with t
9
and ended with t
10
(interval ).
Since the last outgoing leg is not answered, the respective module contains the holding time starting with
t
11
and ending with t
13
(period ).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


(The timestamps t
1
, t
2
, t
3
,

t
7
,

t
8
and t
12
are mentioned for completion reasons only.)
time
outg. leg 1
outg. leg 2
outg. leg 3
inc. leg
t
2
t
3
t
5
t
6
t
1
t
7
t
8
t
9
t
10
t
11
t
12
t
13
call duration of incoming leg =
call duration of outgoing leg =
holding time of outgoing leg =

t
4

Point in time Signalling message sent/received
trigger detection point encountered
Duration logging
t1 SETUP; TDP(control)
t2 IAM seizure of outg. Leg 1
t3 ACM
t4 ANSWER start of call duration (outg. Leg 1)
t5 CONNECT start of call duration (inc. leg)
t6 RELEASE; EDP(control) stop of call duration (outg. Leg 1)
t8 ACM
t9 ANSWER start of call duration (outg. Leg 2)
t10 RELEASE; EDP(control) stop of call duration (outg. Leg 2)
start of holding time (outg. Leg 3)
t12 ACM
t13 RELEASE; EDP(control) stop of holding time (outg. Leg 3)
Figure 2: Call duration measurement in follow-on scenarios
5.2.5 Call reference
This field uniquely identifies a call or transaction on one side of the interface (i.e. A or B side) and is
derived from the transaction identifier of TS 24.008 [9]. It is also used to identify all partial records and
transactions belonging to the same connection.
For the avoidance of doubt, there is no global call reference defined within GSM and the call reference
field cannot be used to combine, for example, the MOC and MTC records of a mobile-to-mobile
connection.
5060 WCS position :
- In a call where both mobile subscribers are localised on the same VMSC (local call), the MOC and the MTC
contain the same call reference. If partial records are generated during the call, the sequence numbers
contained in the MOC and the MTC are incremented independently.
- When a call is forwarded by a MS, the MTC and the MOC generated for this MS contain different call
references. The two calls are considered as independent calls.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.6 Calling / called / connected / translated number
In general a CCITT E.164 [15] number but may also include other numbering plans e.g. ITU-T
Recommendation X.121. Each of these fields includes the type of number and number plan as specified
in detail in TS 24.008 [9]. Where appropriate, these fields may also contain the presentation and
screening information also specified in TS 24.008 [9].
The called number is the number received from the mobile station on mobile originated call set-up as
defined in TS 24.008 [9]. Similarly, the calling number is the number received from the network on mobile
terminated call set-up. In case of CAMEL initiated call forward (CF), the called (forwarded-to) number is
returned by CAMEL.
The translated number is the result of any digit translation performed by the MSC on the called number
received from the mobile station on mobile originated call set-up. This parameter is not included in the
CDR if no digit translation has taken place. (After implement RDS5680 Outpulse MAP CLI changes, WCS
supports store different translated number (before Outpulsed or after Outpulsed in CDR)
The connected number is the number of the actual party reached as defined in TS 24.008 [9]. Although
this is normally identical to the called number it may differ. This parameter is not included if identical to
the called number.
5060 WCS position : the connected number is only stored in the MTC CDR in case of call forwarding,
and is set with the forwarded-to number.
The called number in outgoing GW record is The address of the called party as received in the IAM by
the GMSC. This is the number employed by the GMSC for routing. For example: If customer dialed the
short number we will see in the outgoing GW record the long (translated number) in the called number
field.
The following examples are intended to explain the use of these fields:
EXAMPLE 1: Called Number = Connected Number
Normal call from a mobile subscriber to a mobile subscriber or to a PSTN subscriber.
EXAMPLE 2: Called Number != Connected Number
In case of routing to a PABX with Automatic Call Distribution or to an ISDN Basic Access
with several devices attached. The connected number is that of the party actually reached. N.B.
The recording of the actual number connected may be limited by the capability of intermediate
signalling connections.
EXAMPLE 3: MTC record for Call Forwarding (A -> B -> C)
In case of call forwarding, the connected number recorded in the MTC record of the B
subscriber is that of the forwarded-to party or C subscriber. The calling party field contains
the number of the A subscriber.
EXAMPLE 4: Translated Number
This field is only present if digit translation is applied by the MSC to the called number
received from the mobile station. Examples include abbreviated dialling codes and service
numbers.
5060 WCS position : The addresses present in the CDRs generated by the WCS can have up to 31
digits.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.6.1 Mapping of Numbering Plan and Nature of Adress for ISUP V3 interface (SPIROU)
(RDS4394)
There exists special ISUP variants, which supports additional Nature of Address values and separate
numbering plan values. Not all of the values can be supported by our 5060 WCS in the 3GPP Billing
Format and therefore a mapping has to be done for (see the mapping tables below).
Numbering Plan Mapping
ISUP SPIROU WCS-NPI
unknown unknown
ISDN (Telephony) numbering plan (Recommendation E.164) iSDNtelephony
Data numbering plan (Rec. X.121) data
Telex numbering plan (Rec. F.69) telex
Reserved for national numbering plan 1 unknown
Reserved for national numbering plan 2 landMobile
ELSE numberPlanInvalid

Numbering Type / Nature of Adress Mapping
ISUP SPIROU WCS-NOA
Unknown unknown
Subscriber Number subscriberNumber
national (significant) number nationalNumber
international number internationalNumber
network specific number networkSpecificNumber
Service Special unknown
National number with N carrier indication nationalNumber
International number with N carrier indication internationalNumber
National number with M carrier indication nationalNumber
International number with M carrier indication internationalNumber
ELSE nationalNumber
5.2.7 Calling Party Number
This field contains Calling Party Number modified by CAMEL service.
5.2.8 CAMEL call leg information
This field contains a set of CAMEL information Ies according to the number of outgoing CAMEL call legs.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.9 CAMEL information
This field contains a list of parameters with information related to one CAMEL outgoing call leg. This
parameter list is an information element (IE) used in the CAMEL Call Leg Information field.
As a network option, parameters that are identical to the corresponding values in the top level structure of
the record are not recorded again. That means whenever a value is not mentioned in this set the value
provided in the basic record is valid instead. This might lead to an empty or even absent structure, if no
parameter was modified.
5060 WCS position : The parameters that are identical to the corresponding values in the top level
structure are never recorded again.
5060 WCS position : the list of parameters that are supported by 5060 WCS

Content of Camel Leg Information

1 Camel Destination Number (see TRS chapter 5.2.17)
2 Connected Number (not implemented)
3 Roaming Number (not implemented)
4 Msc Outgoing Trunk Group (not implemented)
5 Seizure Time Stamp (not implemented)
6 Answer Time Stamp (not implemented)
7 Release Time Stamp (not implemented)
8 Call Duration (not implemented)
9 Data Volume (not implemented)
10 Camel Init CF Indicator (see TRS chapter 5.2.10)
11 Cause For Termination (not implemented)
12 Camel Modification (see TRS chapter 5.2.26)
12.1 Camel Modification Bit Map (supported)
12.2 Modification Content (supported)
1 Calling Party Number (for layout, see TRS chapter 5.2.26)
2 Calling Party Category (not implemented)
3 Original Called Party Number (not implemented)
4 Generic Numbers (supported)
5 Redirecting Party Number (not implemented)
6 Redirection Counter (not implemented)
13 Free Format Data (see TRS chapter 5.2.26)
14 Diagnostics Value (not implemented)
15 Free Format Data Append (not implemented)
16 Free Format Data-2 (see TRS chapter 5.2.26)
17 Free Format Data Append-2 (not implemented)
18 translatedNumber (not implemented)
19 additionalChgInfo (not implemented)
20 defaultCallHandling-2 (not implemented)
21 gsm-SCFAddress-2 (not implemented)
22 serviceKey-2 (not implemented)
23 freeFormatDataIncoming-2 (not implemented)
24 freeFormatDataAppendInc-2 (not implemented)
25 locationRoutNum (not implemented)
26 lrnSoInd (not implemented)
27 lrnQuryStatus (not implemented)
28 jIPPara (not implemented)
29 jIPSoInd (not implemented)
30 jIPQuryStatus (not implemented)

5.2.10 CAMEL initiated CF indicator
The purpose of this field is to distinguish CAMEL call forwarding service scenarios from standard GSM
call forwarding scenarios.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


From the Basic Call State Model (BCSM)s point of view this field is set to CF whenever the Originating
CAMEL Subscription Information (O_CSI) was applied after terminating CAMEL call processing had been
taken place changing the call destination. For the avoidance of doubt: this flag does not depend on other
modified call parameter(s) (e.g.: redirection information, etc.) received in the CAP_CONNECT message
of the Terminating CAMEL Subscription Information (T_CSI) service.
This flag also indicates that another record might be generated, one containing the charging information
related to the terminating CAMEL service and one containing the charging information related to the
originating CAMEL service.
5.2.11 CAMEL modified Service Centre
This field contains SMS-C address modified by CAMEL service. If this field is present the field Service
Centre contain SMS-C address before CAMEL modification.
5.2.12 CAMEL SMS Information
This field contains following CAMEL information for mobile originated SMS:
Default SMS handling
This field indicates whether or not a CAMEL encounters default SMS handling. This field shall be
present only if default SMS handling has been applied.
Free format data
See clause 5.22.
Calling Party Number
This field contains Calling Party Number modified by CAMEL service.
CAMEL modified Service Centre
This field contains SMS-C address modified by CAMEL service.
CAMEL Destination Subscriber Number
This field contains short message Destination Number modified by CAMEL service.
SMS Reference Number
This field contains the SMS Reference Number assigned to the Short Message by the MSC.
5.2.13 Cause for termination
This field contains a generalised reason for the release of the connection including the following:
- normal release;
- CAMEL initiated call release;
- partial record generation;
- partial record call re-establishment;
- unsuccessful call attempt;
- abnormal termination during the stable phase;
- unauthorized network originating a location service request;
- unauthorized client requesting a location service;
- position method failure at a location service execution;
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


- unknown or unreachable LCS client at a location service request.
- A more detailed reason may be found in the diagnostics field.
5060 WCS position : the cause for termination due to the location service is not implemented. The partial
record call re-establishment cause for termination is not implemented either.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.14 Channel Coding Accepted/Channel Coding Used
A list of traffic channel codings for HSCSD connections accepted/negotiated by the MS.
These parameters are only present in the CDRs for HSCSD connections.
5060 WCS position : the HSCD feature is not implemented. However, Channel Coding Used is recorded.
5.2.15 Data volume
This field includes the number of 64 octet segments transmitted during the use of data services if known
(see clause B.1.3).
5060 WCS position : this information is not stored in the CDR.
5.2.16 Default call/SMS handling
This field indicates whether or not a CAMEL encountered default call/SMS handling. This field shall be
present only if default call/SMS handling has been applied. Parameter is defined in HLR as part of
CAMEL subscription information.
5.2.17 Destination Subscriber Number
This field contains Destination/Called Subscriber Number modified by CAMEL service. If not modified
then this field may contain original Destination Number also when CAMEL is not active.
5.2.18 Diagnostics
This field includes a more detailed technical reason for the release of the connection and may contain
one of the following:
- a MAP error from TS 29.002 [11];
- a Cause from TS 24.008 [9];
- a Cause from TS 29.078 [12];
- a Cause from ITU-T Recommendation Q.767 [13] ;
- a LCS diagnostics according TS 29.002 [11];
The diagnostics may also be extended to include manufacturer and network specific information.
5060 WCS position : WCS diagnostics has many private cause value and not limited in gsm0408 cause
value scope, so WCS uses manufacturerSpecificCause [4] Diagnostics field in CDR. (PR59210)
Nevertheless, we still can force WCS always generate gsm0408Cause for Diagnostic by static DB option
(3GPP_GSM0408_DIAGNOSTIC_TYPE) (PR85393), if customer insists it.
5.2.19 EMS-Digits
This parameter only applies to location for an emergency services call in North America and gives the
North American Emergency Services Routing Digits as defined in TS 29.002 [11].
5060 WCS position : this information is not recorded. It is present in the NI-LCS record which is not
generated.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.20 EMS-Key
This parameter only applies to location for an emergency services call in North America and gives the
North American Emergency Services Routing Key as defined in TS 29.002 [11].
5060 WCS position : this information is not recorded. It is present in the NI-LCS record which is not
generated.
5.2.21 Entity number
This field contains the ITU-T Recommendation E.164 [12] number assigned to the entity (MSC, VLR, HLR
etc.) that produced the record. For further details concerning the structure of MSC and location register
numbers see 3GPP TS 23.003 [14].
5.2.22 Equipment id
This field contains a local identifier used to distinguish between equipment of the same equipment type
e.g. the number of the conference circuit employed if more than one is available.
5060 WCS position : this information is not recorded. It is present in the Common Equipment record
which is not generated.
5.2.23 Equipment type
This field contains the type of common equipment employed e.g. conference circuit for multi-party
service.
5060 WCS position : this information is not recorded. It is present in the Common Equipment record
which is not generated.
5.2.24 E-UTRAN Cell Global Identity (RDS13870) (deferred)
This field indicates the UE's current E-UTRAN Cell Global Identity.
The E-UTRAN Cell Global Identification (ECGI) shall be composed of the concatenation of the PLMN
Identifier (PLMN-Id) and the E-UTRAN Cell Identity (ECI) as shown in figure 19.6.1 and shall be globally
unique: (TS23.003 V8.80 section 19.6, TS 29.118 V8.6.0 section 94.3a, TS29.274 V8.5.0 section 8.21.5)
Bits
Octets 8 7 6 5 4 3 2 1
e MCC digit 2 MCC digit 1
e+1 MNC digit 3 MCC digit 3
e+2 MNC digit 2 MNC digit 1
e+3 Spare ECI
e+4 to e+6 ECI (E-UTRAN Cell Identifier)
The E-UTRAN Cell Identifier (ECI) consists of 28 bits. The ECI field shall start with Bit 4 of octet e+3,
which is the most significant bit. Bit 1 of Octet e+6 is the least significant bit. The coding of the E-UTRAN
cell identifier is the responsibility of each administration. Coding using full hexadecimal representation
shall be used.
5.2.25 Event time stamps
These fields contain the event time stamps relevant for each of the individual record types.
The call records may contain three significant call handling time stamps:
- The time at which the resource in question was seized (Seizure time).
- The time at which the call was answered or at which charging commences (Answer time).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


- The time at which the resource was released (Release time).
For both Mobile Originated and Mobile Terminated calls, the Seizure time is the time at which the traffic
channel is allocated i.e. the time at which the ASSIGN COMMAND message is sent to the MS.
For Mobile Originated calls the Answer time is the time at which the CONNECT message is sent to the
calling party. For Mobile Terminated calls the time at which the CONNECT message is received from the
called party. However, if the subscriber has subscribed to the advice of charge charging level service,
then the answer time shall be derived from the time at which the FACILITY message is received from the
MS containing the acknowledgement of receipt of the AOC parameters. Similarly, if the AOC parameters
are changed during the call then the change time recorded for a subscriber with AOC charging level is the
receipt of the FACILITY message from the MS. For a subscriber with AOC information level the change
time recorded is the time at which the FACILITY is sent to the MS. Finally, in case of call re-establishment
the answer time is the time at which the new traffic channel is allocated by the MSC i.e. when the
ASSIGN COMMAND is sent to the MS.
5060 WCS position : the AoC function is not implemented.
The Release time is the time at which the connection is released by either party i.e. a DISCONNECT or
RELEASE is sent by the network or a DISCONNECT is received from the MS. In the case of a radio link
failure, the release time is the time at which the failure was detected by the MSC.
For unsuccessful call attempts the Seizure time is mandatory. The Release time is optional and the call
duration recorded is the call holding time i.e. the difference between the two.
For successful calls the Answer time is mandatory and both the Seizure and Release times are optional.
The call duration recorded is the chargeable duration i.e. the difference between the Answer and Release
time stamps.
The event records include the following time stamps:
- HLR-int time: The receipt of a MAP_SEND_ROUTING_INFO request by the HLR.
- Loc.Upd. time: The receipt of a MAP_UPDATE_LOCATION_AREA request by the VLR or the
receipt of a MAP_UPDATE_LOCATION request by the HLR.
- SS-Action: The receipt of a supplementary service request by the VLR.
e.g. MAP_REGISTER_SS, MAP_INVOKE_SS
- SMS-MO: The receipt of an RP_DATA message from the MS containing an
SMS_SUBMIT PDU.
- SMS-MT: The transmission of an RP_DATA message to the MS containing an
SMS_DELIVER PDU.
- LCS: The time the LR was processed.
It should be noted that the events listed above are only examples in order to demonstrate the principles
and that the list is by no means exhaustive.
5060 WCS position : the HLR-int time the SS-Action time and the Loc Upd time items are not relevant
since the 5060 WCS doesnt generate these kinds of records. (RDS6904)
All time-stamps include a minimum of date, hour, minute and second.
5060 WCS position :The format contains the date, hour, minute, second and delta with GMT.
Format: YYMMDDHHNNSS2DHHNN
YYMMDDHHNNSS is local time and
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


2D(2B)HHNN is the delta between local time and GMT time. In case of missing location info,
the delta time can not be provided and the structure 2DHHNN is set to 000000.
5.2.26 Fixed Network User Rate
This field indicates the user data rate applied for the connection in the fixed network. In UMTS, it shall be
present for all bearer services as specified in TS 22.002. In GSM, this parameter is part of the HSCSD
connection parameters, see clause 5.29.
5060 WCS position : the HSCSD feature is not implemented.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.27 Free format data
This field contains charging information sent by the gsmSCF in the Furnish Charging Information (FCI)
messages as defined in TS 29.078 [12]. The data can be sent either in one FCI message or several FCI
messages with append indicator. This data is transferred transparently in the CAMEL clauses of the
relevant call records. Free format data sent to the legID=1 is always stored in the top level of the
respective record. Free format data sent to the legID >1 is stored in the appropriate CAMEL call leg
information field.
If the FCI is received more then once during one continuing incoming/outgoing CAMEL call leg, the
append indicator defines whether the FCI information is appended to previous FCI and stored in the
relevant record or the information of the last FCI received is stored in the relevant record (the previous
FCI information shall be overwritten).
In the event of partial output the currently valid Free format data is stored in the partial record.
5.2.28 Free format data append indicator
This field contains an indicator whether free format data is to be appended to free format data stored in
previous partial CDR. This field is needed in CDR post processing to sort out valid free format data for
that call leg from sequence of partial records. Creation of partial records is independent on received FCIs
and thus valid free format data may be divided to different partial records.
If field is missing then free format data in this CDR replaces all received free format data in previous
CDRs. Append indicator is not needed in the first partial record. In following partial records indicator shall
get value true if all FCIs received during that partial record have append indicator. If one or more of the
received FCIs for that call leg during the partial record do not have append indicator then this field shall
be missing.
5060 WCS position : the Free format data append indicator is not supported by the 5060 WCS. In case
all FCIs since the last partial CDR are received with the append indicator, the next partial CDR contains
the concatenated Free format data. The contents of the Free format data in the new partial record
override the contents of previous partial CDR, and the Free format data append indicator is useless.

5.2.29 GsmSCF address
This field identifies the CAMEL server serving the subscriber. Address is defined in HLR as part of
CAMEL subscription information.
5.2.30 Guaranteed Bit Rate
This field contains the Guaranteed Bit Rate based on the FNUR for transparent and Wanted AIUR for
non-transparent CS data services based on the described mapping in TS 27.001 [16]. The Guaranteed
Bit Rate may be used to facilitate admission control based on available resources, and for resource
allocation within UMTS. The bitrate of the UMTS bearer service shall guarantee to the user or
applications refer TS 22.002 [17].
Operator may choose any of the possible values less or equal to wanted air interface user rate (WAIUR).
(If WAIUR is less or equal to 14,4 kbit/s then Guaranteed Bit Rate and Maximum Bit Rate shall be set to
14,4 kbit/s).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.31 HSCSD parameters / Change of HSCSD parameters
The basic HSCSD parameters are negotiated between the MS and the network at call setup time. They
comprise of the following parameters:
- the FNUR (Fixed Network User Rate) (optionally);
- the total AIUR (Air Interface User Rate) requested by the MS (for non-transparent HSCSD
connections only);
- a list of the channel codings accepted by the MS;
- the maximum number of traffic channels accepted by the MS (this is noted in the channels
requested field);
- the channel coding and the number of traffic channels actually used for the call.
In case the network or user initiated modification procedure takes place during the call, the AIUR
requested, the channel coding used and the number of traffic channel requested/used might be recorded
in the Change of HSCSD parameters field including the time at which the change occurred and which
entity requested the change.
It should be noted that the Change of HSCSD Parameters field is optional and not required if partial
records are generated when a Change of HSCSD Parameters takes place.
5060 WCS position : the HSCSD feature is not implemented. This information is not recorded in the
CDR.
5.2.32 Incoming/ outgoing trunk group
The incoming trunk group describes the trunk on which the call originates as seen from the MSC. For
mobile originated calls this will generally be a BSS trunk. Similarly, the outgoing trunk group describes the
trunk on which the call leaves the MSC.
For 3G, this parameter may not be available. When available, this parameter shall be supplied in the
CDRs.
5060 WCS position : Note: To ensure Trunk Group Number is compatible with 3GPP, the value is
between 1 and 4294967259. Either 'trunk group number' or 'trunk group name' will be present in the CDR.
(RDS14844)
5.2.33 Interrogation result
This field contains the result of the HLR interrogation attempt as defined in the MAP (TS 29.002 [11]).
NOTE: This field is only provided if the attempted interrogation was unsuccessful.
5060 WCS position : this information is not recorded in the HLR-INT CDR. (RDS6904)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.34 IMEI Check Event
This field identifies the type of event that caused the IMEI check to take place:
- Mobile originating call attempt;
- Mobile terminating call attempt;
- Mobile originating SMS;
- Mobile terminating SMS;
- Supplementary service actions performed by the subscriber;
- Location update.
5060 WCS position : this information is not recorded in the CDR.
5.2.35 IMEI Status
This field contains the result of the IMEI checking procedure:
- Greylisted;
- Blacklisted;
- Non-whitelisted.
5.2.36 JIP Parameter
This Jurisdiction Information Parameter (JIP) is populated if received via one of the methods listed as JIP
Source. The field shall identify the actual originating exchange and may be equal to 6 or 10 digits for
North America Region (NAR). Note that this field may not apply for international areas, as it is not
currently used. Additionally, it is also possible to use the LRN as the JIP if it properly identifies the
originating switch.
5.2.37 JIP Query Status Indicator
This field indicates the status of Location Routing Number (LRN) query as follows:
- Number Portability Data Base (NPDB) returns LRN or NULL response (free of any error).
- No response was received to the query; the query timed out.
- Protocol error in received response message.
- Error detected in response data.
- Query rejected
- No query performed
- Query unsuccessful, reason unknown
If the JIP is equal to the LRN, then the JIP query status shall be the same as the LRN query status. If not,
this field shall be set to one of the values listed above.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.38 JIP Source Indicator
This indicator shall be populated if the Jurisdiction Information Parameter is derived. Identifies the method
in which the value was derived. Shall be set to the values listed in the LRN Source Indicator.

5.2.39 LCS Cause
The LCS Cause parameter provides the reason for an unsuccessful location request according TS 49.031
[18].
5060 WCS position : this information is not recorded in the CDR, as the LCS records are not generated.
5.2.40 LCS Client Identity
This field contains further information on the LCS Client identity:
Client External ID
Client Dialled by MS ID
Client Internal ID
5.2.41 LCS Client Type
This field contains the type of the LCS Client as defined in TS 29.002 [11]
5.2.42 LCS Priority
This parameter gives the priority of the location request as defined in TS 49.031 [18]
5.2.43 LCS QoS
This information element defines the Quality of Service for a location request as defined in TS 49.031 [18]
5.2.44 Level of CAMEL service
This field describes briefly the complexity of CAMEL invocation.
- Basic means that CAMEL feature is invoked during the setup phase (e.g.: to modify the
destination) of the call only.
- Online charging means that CAMEL supported AoC parameter were sent to the mobile station
(the Send Charging Information message, SCI, is received from the gsmSCF).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


- The flag call duration supervision is set whenever the call duration supervision is applied in the
gsmSSF of the VPLMN (apply charging message is received from the gsmSCF).
5060 WCS position : the Online charging value is in restriction until the AoC function is implemented.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.45 Location / change of location
The location field contains a combination of the location area code (LAC) and cell identity (CI) of the cell
in which the served party is currently located. Any change of location may be recorded in the change of
location field including the time at which the change took place.
The change of location field is optional and not required if partial records are generated when the location
changes.
The LAC and CI are both 2 bytes quantities and coded according to TS 24.008 [9].
5060 WCS position : The first location of the call is recorded in the location field. The subsequent
locations are recorded in the change of location field. Up to 7 new locations can be recorded in this field.
In case more locations are involved in a call, then the 7 first locations and the last location are recorded.
The other locations are discarded.
All the kinds of handovers are recorded : intra BSC, inter BSC, inter MSC, and inter RAN.
Note: As SAC/Cell is not available in case of 3G->3G handover (target is specified in terms of
PLMN_LAC_RNCID), an invalid value (0xFFFF) will be recorded in the Cell-Id field of "Change of
Location" field of CDR.
Note: If CELLID is not available, it will be filled with all F.
Note: Only part of the E-CGI is stored in the existing CGI field in the CDR for SMS CSFB case.
(RDS13870)
5.2.46 Location Estimate
The Location Estimate field is providing an estimate of a geographic location of a target MS according to
TS 29.002 [11].
5.2.47 Location Extension (not implemented)

The Location Externsion field contains the 12 most significant bits from the Cell Identity field. This is used
when SMS over SGs (defined in 3GPP TS 36.413 [95]) is applied and the access is E-UTRAN.
(wait RDS15633)
5.2.48 Location Routing Number (LRN)
This field contains Ten-digit Location Routing Number (LRN) for the Number Portability feature. It is
populated if received via one of the methods listed as LRN Source. It identifies the new location of a
ported subscriber. For North America Region (NAR) this may be a 10-digit E.164 number. For Europe,
other formats may apply.
If more than 10 digits are received, the first ten digits received are recorded. If fewer than 10 digits are
received, the information is left justified in the field and padded with 0xF.
5060 WCS position : RDS9189
If the Number has been ported, the NP database returns a HOC (Hand-Off Code) which will be stored in
the LRN parameter.

Generally, a maximum of 10 digit number can be stored, but in some countries this may only contain
a few digits.

Example of a 6 digit number used in New Zealand:

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


011XNT where

X is customer specific digit
N identifies the Host Carrier Network
T identifies the service LNP, or MNP

5.2.49 Location Type
This field contains the type of the location as defined in TS 29.002 [11]
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.50 LRN Query Status Indicator
This field indicates the status of Location Routing Number (LRN) query as follows:
- Number Portability Data Base (NPDB) returns LRN or NULL response (free of any error).
- No response was received to the query; the query timed out.
- Protocol error in received response message.
- Error detected in response data.
- Query rejected
- No query performed
- Query unsuccessful, reason unknown
It is populated if an NP query was performed.
5060 WCS position : this parameter is used for Number Portability feature. RDS9189

5.2.51 LRN Source Indicator
This field indicates whether the Location Routing Number is obtained from LRN NP database or it came
in incoming signalling or switching system data.
It is populated if routing information for a ported subscriber is received from one of the methods listed
below. It shall be equal to one of the following enumerated values:
- LRN NP Database.
- SwitchingSystemData.
- Incomingsignaling.
- Unknown.

5060 WCS position : this parameter is used for Number Portability feature. RDS9189
5.2.52 Maximum Bit Rate
This field contains the Maximum Bit Rate based on the FNUR (Fixed Network User Rate) for transparent
and WAIUR (Wanted Air Interface User Rate) for non-transparent CS data services based on the
described mapping in 3GPP TS 27.001 [16]. The parameter can be used to make code reservations in
the downlink of the radio interface for the UMTS bearer service (BS20 and BS30) refer 3GPP TS 22.002
[17]. Its purpose is:
1. to limit the delivered bitrate to applications or external networks with such limitations,
2. to allow maximum wanted user bitrate to be defined for applications able to operate with different
rates (e.g. applications with adapting codecs).]
Maximum bit rate is set to the highest value WAIUR (If WAIUR is less or equal to 14,4 kbit/s then
Guaranteed Bit Rate and Maximum Bit Rate shall be set to 14,4 kbit/s).

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.53 Measure Duration
This field contains the duration for the section of the location measurement corresponding to the location
request and the location report messages.
5.2.54 Message reference
This field contains a unique message reference number allocated by the mobile station when transmitting
a short message to the service centre. This field corresponds to the TP-Message-Reference element of
the SMS_SUBMIT PDU defined in TS 23.040 [19].
5.2.55 MLC Number
This parameter refers to the ISDN (E.164) number of an MLC.
5.2.56 Mobile station classmark / change of classmark
This MS classmark field contains the mobile station classmark employed by the served MS on call set-up
as defined in TS 24.008 [9] (see mobile station classmark 2). Any alteration in the classmark during the
connection may be recorded in the change of classmark field and will include the time at which the
change took place.
It should be noted that the change of classmark field is optional and not required if partial records are
created when the classmark is altered.
5060 WCS position : a change of classmark is not recorded.
5.2.57 MOLR Type
The MOLR-Type identifier refers to the type of MO-LR that was invoked as defined in TS 24.080 [20]
5.2.58 MSC Address
This field contains the ITU-T Recommendation E.164 [15] number assigned to the MSC that produced the
record. For further details concerning the structure of MSC numbers see TS 23.003 [14].
5060 WCS position : more precisely, it is the address of the MSC which generated the Network Call
Reference (see below). The combination MSC address Network Call Reference allows the correlation
of all the CDR generated for a given call in all the MSCs and possibly the SCPs of the network.
For an originating call, it is set to the address of the VMSC. The same value is sent in the MSC address
field of the initialDP operation.
For a terminating call in GMSC, it is set with the address of the GMSC. The same value is sent in the
MSC address field or the Send Routing Information operation, and in the MSC address field of the
initial DP when a T-CSI is triggered. In case the CAMEL service sends a CONNECT with an Apply
OCSI indication, then the same value is also sent in the initialDP operation of the OCSI.
In case the CAMEL service sends a CONNECT without an "Apply OCSI" indication, the "MSC address" is
not required in MOC-CFCDR.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


For a terminating call in VMSC, it is set to the same value as the MSC address received in the Provide
Roaming Number operation. In case VT-CSI applies, the same value is sent in the GMSC address of
the initialDP operation sent by the VMSC.
5.2.59 MSC Server Indication
This field contains an indicator whether the CAMEL subscription information is active. The parameter is
present for the VT-CSI in the VMSC and not present for the T-CSI in the GMSC.
This indication should be used for differentiation between the validity of the record content for T-CSI in the
GMSC and VT-CSI in the VMSC.
Note: Concerning the support of VT-CSI inside 5060 WCS, please refer to document [31].
5.2.60 Network Call Reference
Whenever CAMEL is applied, this field is used for correlation of call records outputted from the originating
MSC (when applicable), the GMSC and the terminating MSC, and a network optional call record from the
gsmSCF.
5060 WCS position :
For an originating call, it is set to the same value as the call reference sent in the initial DP operation.
For a terminating call in GMSC, it corresponds to the call reference sent in the initial DP when a T-CSI is
triggered. This information is also sent in the Send Routing Information operation. In case the CAMEL
service sends a CONNECT with an Apply OCSI indication, then the same value is also sent in the
initialDP operation of the OCSI.
In case the CAMEL service sends a CONNECT without an "Apply OCSI" indication, the " Network Call
Reference " is not required in MOC-CF CDR.
For a terminating call in VMSC, it corresponds to the call reference received in the Provide Roaming
Number operation. In case VT-CSI applies, the same value is sent in the call reference of the initialDP
operation sent by the VMSC.
5.2.61 Notification to MS user
This field contains the privacy notification to MS user that was applicable when the LR was invoked as
defined in TS 29.002 [11]
5.2.62 Number of DP encountered
This field indicates how often CAMEL armed detection points (TDP and EDP) were encountered and is a
measure of signalling between serving network and CAMEL service and complements Level of CAMEL
service field. Detection points from all applied CAMEL services for a single call leg and processed in the
same gsmSSF shall be counted together.
5.2.63 Number of forwarding
This field, if provided via ISUP signalling, contains the number of times a call has been forwarded prior to
the interrogation of the HLR and is defined in TS 29.002 [11].
5060 WCS position : this information is not recorded in the HLR interrogation CDR. (RDS6904)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.64 Old /new location
These fields contain the location of a mobile subscriber before and after a location update. In case of VLR
location update the location information consists of a VMSC number and location area code. In case of
HLR location update the field contains the VMSC number and the VLR number.
5060 WCS position : this information is not recorded in the CDR, as the VLR location update and the
HLR location update records are not generated.
5.2.65 OutgoingIAMcallednumber (RDS16253)
This field contains the called number from outgoing IAM message in new OutgoingIAMcallednumber
CDR Field in outgoing gateway CDR with static DB control flag.
(3GPP_OUTGOINGIAMCALLEDNUMBER).
5.2.66 Partial Record Type
This field indicates the event that caused the generation of a partial record.
5060 WCS position : the expiry of the partial record timer is and the change of CAMEL destination are
the only supported criterion for generating a partial record.
5.2.67 Positioning Data
This information element is providing positioning data associated with a successful or unsuccessful
location attempt for a target MS according TS 49.031 [18].
5.2.68 Privacy Override
This parameter indicates if MS privacy is overridden by the LCS client when the GMLC and VMSC/SGSN
for an MT-LR are in the same country as defined in TS 29.002 [11]
5.2.69 Radio channel requested / radio channel used / change of radio channel
The radio channel requested field contains the type of channel requested by the user. The following
values are permitted:
- full rate;
- half rate;
- dual mode half rate preferred;
- dual mode full rate preferred.
The radio channel used field indicates the type of traffic channel actually employed for the connection i.e.
either full rate (Bm) or half rate (Lm) as described in GSM 05.01. Any change in the type of channel used
may be recorded in the change of radio channel used field including the time at which the change
occurred and the speech version used after the change of radio channel.
5060 WCS position : Only the radio channel used is recorded by the 5060 WCS.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.70 Rate Indication
This parameter specifies the rate adaptation that was used for the connection. The field is constructed
from the information in the parameters rate adaption and other rate adaption signalled between the
MS/UE and the network, see TS 24.008.
The format of this field is a single octet with the following format:
Bits 0-1: the Rate Adaption field as defined in TS 24.008;
Bits 2-3: the Other Rate Adaption field as defined in TS 24.008;
Bits 4-7: not used.
5.2.71 Record extensions
The field enables network operators and/ or manufacturers to add their own extensions to the standard
record definitions.
5060 WCS position : the contents of the 5060 WCSs extensions in detailed in the next sections.
5.2.71.1 BSCId of first BSC
This field contains the BSCid of the BSC on which the subscriber is located when a service (call, SS
action or SMS) is invoked. Only available if the service is invoked under BSC coverage. This field is set
with the Point Code of the BSC.
5.2.71.2 CS ARP
This field indicates the CS Allocation/Retention priority of the MS subscriber, as received from the HLR in
the Insert Subscriber Data operation (CMCC feature).
5.2.71.3 CUG incoming access used
This field indicates that the call is received from outside the CUG of the subscriber. Please refer to
document [32]. (RDS9804b)
5.2.71.4 CUG interlock code
This field indicates the CUG interlock code used for the call, if applicable. Please refer to document [32].
(RDS9804b)
5.2.71.5 CUG index
This field indicates the CUG index used for the call, if applicable. Please refer to document [32].
(RDS9804b)
5.2.71.6 CUG outgoing access indicator
This field indicates the calling MS's CUG OA subscription info. Please refer to document [32].
(RDS9804b)
5.2.71.7 CUG outgoing access suppressed
This field indicates whether suppression of Outgoing Access capability. Please refer to document [32].
(RDS9804b)
5.2.71.8 Hot billing subscriber
This field indicates that the subscriber is a hot-billing subscriber. This information depends on a specific
subscriber category or on a specific OSSS code.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


The presence of this information means that on one side the record is stored with the other records, and
on the other side is sent in real-time to the billing centre (or to a dedicated hot-billing centre). See [4] for
more details.
5.2.71.9 IP connection
This field indicates that the CDR is related to the connection to an external Intelligent Peripheral (IP)
ordered by a CAMEL service. It is only set if the user interaction requires a both-way connection, and if an
answer signal is received from the IP (can be e.g. an external Announcement Equipment).

This field is only present if the option (on EMS) that conditions the recording of the calls towards external
Ips is active. If this is the case there will be a MOC record with IP connection flag attached in CDR. The
call duration indicates the announcement duration. Additionally, there will be generated another MOC
without IP connection flag in which the call duration reflects the real call duration.
5.2.71.10 MS Category
Category of the subscriber.
5.2.71.11 Multimedia call
This field indicates that a call is a multimedia call. It is set when the Basic service code (0x1F) and Bearer
Capability received from the MS contains other rate adaptation set to H223&H245, and when the Fixed
Network User Rate is 64kbps.
5.2.71.12 Redirecting counter
This field contains the redirecting counter received in the IAM message in the redirection information IE. It
is the number of call forwarding that occurred upstream.
5.2.71.13 Redirecting number
This field contains the address of the last forwarding subscriber. When the last call forwarding occurred in
another MSC, this field is set with the redirecting number IE received in the IAM message.
5.2.71.14 RNCId of first RNC
This field contains the RNCid of the RNC on which the subscriber is located when a service (call, SS
action or SMS) is invoked. Only available if the service is invoked under UTRAN coverage. This field is
set with the Point Code of the RNC.
5.2.71.15 SMS originating number
This field contains the address of the sender of a Short Message.
5.2.71.30 Interconnect Facility
This field contains the information about the interconnect facility used between two media-gateways
involved in a call. It consists in the interconnect group number as defined with the Wireless Element
Manager and the interconnect facility type (TDM, ATM or IP).
5.2.71.32 MSC incoming/outgoing trunk group extension
This field contains additional information on the trunk groups :
- the type of trunk group (ISUP, BSS, UTAN, SIP, SIP-I (RDS6029) )
- the type of transport interface (TDM, ATM, IP)
- the number of the media-gateway used for the call
- the circuit identifier used for the call
Note: In case of parameter (e.g. mGWNumber or trunkcircuit) is not usefull / present (e.g. for SIP),
the default value should be setup (all Bits should be set to 1).
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Note: For A over IP calls, CDR shall indicate the ' BSC' trunk group type and the 'VoIP'
interface type. TrunkCircuit CDR filed does not apply to VOIP case and may contain internal
index. (RDS13186) (RDS10893a)
Note: For Iu over IP calls, CDR shall indicate the ' UTRAN (Iu-Interface) Trunk ' trunk group
type and the 'VoIP' interface type. (RDS8242)
Note : FOR ALCAP termination on 754x MGW case, CDR shall indicate the ' aAL2 ' interface
type. (RDS14221)
5.2.71.46 Service duration
In case of Mobile Initiated USSD dialogue, this field indicates the duration between the first response to
the first message and the last message on MAP interface.
In case of Network Initiated USSD dialogue, this field indicates the duration between the first message on
A-interface and the last message on MAP interface.
5.2.72 Record type
The field identifies the type of the record e.g. mobile originated, mobile terminated etc.
5.2.73 Recording Entity
This field contains the ITU-T E.164 [15] number assigned to the entity (MSC, VLR, HLR etc.) that
produced the record. For further details concerning the structure of MSC and location register numbers
see 3GPP TS 23.003 [14].
5.2.74 Roaming number
The roaming number field of the MOC record contains the mobile station roaming number as defined in
TS 23.003 [14] and coded according to TS 29.002 [11].
5060 WCS position : this field is also stored in the incoming gateway and outgoing gateway CDRs.
Additionally, this information is stored in the ROAM CDR. (RDS6904). Record 1st received MSRN in
roaming number CDR Field for 3GPP MOC CDR by control falg (RDS16318)
5.2.75 Routing number
The routing number field of the HLR interrogation record contains either a mobile station roaming number
or, in case of call forwarding, a forwarded-to number.
5060 WCS position : this information is not recorded in the HLR interrogation CDR. (RDS6904)
5.2.76 Sequence number
This field contains a running sequence number employed to link the partial records generated for a
particular connection.
5.2.77 Served IMEI
This field contains the international mobile equipment identity (IMEI) of the equipment served. The term
served equipment is used to describe the ME involved in the transaction recorded e.g. the called ME in
case of an MTC record.
The structure of the IMEI is defined in TS 23.003 [14].
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5060 WCS position : If a 15-digit IMEI is indicated, then that means that no SVN (Software Version
Number) is present, and the 15th digit is always coded as 0 (0000) per 3GPP TS 23.003. If a 16-digit
IMEISV is indicated, then digits 15 and 16 comprise the SVN.
Note: Billing area records received IMEI in CDR transparently without check IMEI length or content. IMEI
CDR field will be always fixed length (8byte=16 digits) with F as filler; e.g. if received IMEI =123456789
(obviously the length is too short), then the IMEI in CDR will be 123456789FFFFFFF. (PR77823)
5.2.78 Served IMSI
This field contains the international mobile subscriber identity (IMSI) of the served party. The term
served party is used to describe the mobile subscriber involved in the transaction recorded e.g. the
calling subscriber in case of an MOC record.
The structure of the IMSI is defined in TS 23.003 [14].

5060 WCS position : If IMSI is Mandatory, but IMSI is unavilable for some special case (for example:
served party is call center), then Servied IMSI will be filled with all F. (RDS14086)

5.2.79 Served MSISDN
This field contains the mobile station ISDN number (MSISDN) of the served party. The term served
party is used to describe the mobile subscriber involved in the transaction recorded e.g. the called
subscriber in case of an MTC record. In case of multi-numbering the MSISDN stored in a MOC record will
be the primary MSISDN (i.e. the MSISDN stored in the VLR) of the calling party.
The structure of the MSISDN is defined in TS 23.003 [14].
5.2.80 Service centre address
This field contains an ITU-T Recommendation E.164 [15] number identifying a particular service centre
e.g. short message service centre (see TS 23.040 [19]).
5.2.81 Service key
This field identifies the CAMEL service logic applied. Service key is defined in HLR as part of CAMEL
subscription information.
5.2.82 SGs cause (RDS13870) (deferred)
This field identifies an error to the receiving entity in SMS-MT CDR. This could be a protocol data error, to
indicate to the VLR the reason why a paging procedure could not be performed or to indicate to the VLR
that the mobile terminating CS fallback call has been rejected by the user. The SGs cause information
element is coded as below. (TS 29.118 V8.6.0 section 9.4.18)

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


SGs cause value (octet 3)
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 Normal, unspecified in this version of the protocol.
0 0 0 0 0 0 0 1 IMSI detached for EPS services
0 0 0 0 0 0 1 0 IMSI detached for EPS and non-EPS services
0 0 0 0 0 0 1 1 IMSI unknown
0 0 0 0 0 1 0 0 IMSI detached for non-EPS services
0 0 0 0 0 1 0 1 IMSI implicitly detached for non-EPS services
0 0 0 0 0 1 1 0 UE unreachable
0 0 0 0 0 1 1 1 Message not compatible with the protocol state
0 0 0 0 1 0 0 0 Missing mandatory information element
0 0 0 0 1 0 0 1 Invalid mandatory information
0 0 0 0 1 0 1 0 Conditional information element error
0 0 0 0 1 0 1 1 Semantically incorrect message
0 0 0 0 1 1 0 0 Message unknown
0 0 0 0 1 1 0 1 Mobile terminating CS fallback call rejected by the user
0 0 0 0 1 1 1 0
to Normal, unspecified in this version of the protocol
1 1 1 1 1 1 1 1

NOTE: "Normal, unspecified" has the same meaning than in 3GPP TS 24.008 [8],
informative Annex H (UMTS specific cause values for call control). It is used to report a
normal event, and should not be interpreted as syntactically incorrect nor unknown if
received.
5.2.83 Short message service result
This field contains the result of an attempt to deliver a short message either to a service centre or to a
mobile subscriber (see TS 29.002 [11]). Note that this field is only provided if the attempted delivery was
unsuccessful.
5.2.84 Speech version supported / Speech version used
The speech version supported field contains the speech version supported by the MS with the highest priority. The
speech version used field contains the speech codec version assigned for that call. The coding is according GSM
08.08 speech version identifier with the extension bit 8 set to 0.
It should be noted that the change of radio channel field is optional and not required if partial records are
generated.
5060 WCS position : Only the Speech Version used is supported.
5.2.85 System type
This field indicates the use of GERAN, UTRAN (or a value of unknown). This field is present when either
the UTRAN or GERAN air-interface is used on call setup. For an open CDR in a 2G NE (responsible for
the CDR), the field is not present (even if the call is handed off to a 3G air interface). For a CDR in a 3G
NE (responsible for the CDR), the value unknown shall be used after handover.
Note:
This parameter is based on the Air interface technology. In case of UMTS (3G) and GPRS/Edge (2.5G),
this IE is present. In a 2G environment (only BSCs connected, using simple GSM technology ), this field
is not necessary / useless.

Note: (PR D55218)
system type field will be present if controlled flag is ON and will not present when this flag is OFF.
(see chapter 6.2 Options statically modifiable)
For pure 2G WCS, system type field should never be presented in CDR.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


For pure 2G/3G combo, pure 3G WCS, system type field should always be presented in CDR as
mandatory field.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.86 Supplementary service(s)
The supplementary service field in the Supplementary Service record type contains the code of the
supplementary service on which the action was performed.
The supplementary services field in the MOC / MTC records contains the codes of the supplementary
services invoked as a result of, or during, a connection.
The coding of supplementary service is described in detail in TS 29.002 [11].
5060 WCS position : SuppServiceUsed field only provide ssCode. SuppServiceUsed field dont provide
ssTime.
SS Code list
11 Calling line id. present.
12 Calling line id. restrict.
13 Connected line id. present.
14 Connected line id. restrct.
20 All call forwarding
21 Call fwd. unconditional
28 All conditional call fwd.
29 Call fwd. on subscr. busy
2A Call fwd. on no reply
2B Call fwd. on not reachable
31 ExplicitCallTransfer (RDS14282)
41 Call waiting
42 Call hold
43 Completion of Calls to Busy Subscriber originating side
44 Completion of Calls to Busy Subscriber destinating side
51 Multiparty
61 CUG
71 Advice of charge - inform.
72 Advice of charge - charging
81 User to User Signalling - Service 3 (UUS3)
90 All call barring
91 Barring of outgoing calls
92 Barring, all outgoing calls
93 Bar., all outg. int. calls
94 Bar., all outg. int. ex-HPLMN
99 Barring of incoming calls1
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


9A Barring, all incoming calls
9B Bar., all inc. calls, roaming
A0 Priority Call in state of disaster
E0 Delayed Hot Line
E1 Call Deflection
F1 Hot Billing
FC MRBT
FE PRBT

Note: The extended SS code (start with HF) can be adjusted in GUI for each customer.
Note: WCS only record the first 8 SS code value in this CDR field.

5.2.87 Subscribed OSSS Codes (RDS14064)
This field contains the OSSS code from HLR while the call start.
IGMSC,OGMSC, Transit Record is generated for inter network charging purpose. (not for dedicated
subscriber charging purpose). So Subscribed OSSS Codes is not include in IGMSC,OGMSC, Transit
Record types.
MOC EMY doesnt include OSSS code due to system limitation.
New OSSS code CDR fileld only record private OSSS code from VLR with high priority and doesnt
record OSSS code from HLR during the call, except HLR-INT CDR and T-CAMEL CDR get OSSS code
from HLR as high priority.
Limitations for COMBO (GMSC+T-VMSC) scenarios:
In combo scenarios, OSSS codes present in VLR will be recorded. If VLR OSSS codes are not
available then the available HLR OSSS codes are recorded.
For HLR-INT CDR created due to T-CSI data and T-CAMEL CDR, OSSS codes from HLR are
recorded.
5.2.88 Supplementary service action
This field contains the type of supplementary service action requested by the subscriber or performed by
the network. Possible values include:
- registration;
- erasure;
- activation;
- deactivation;
- interrogation;
- invocation.
For further details see TS 22.004 [21].
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.2.89 Supplementary service action result
This field contains the result of an attempted supplementary service action (see TS 29.002 [11]). Note
that this field is only provided if the SS-action was at least partially unsuccessful.
5.2.90 Supplementary service parameters
This field contains the parameters associated with a supplementary service action requested by the
subscriber. For further details of the parameters involved see the GSM 02.8n series of documents.
5.2.91 Transparency indicator
This field indicates whether the basic service was employed in transparent or non-transparent mode. It
should also be noted that this field is only relevant for those services, which may be operated, in both
transparent and non-transparent modes.
5060 WCS position : this field will present in CDR if WCS know transparent or non-transparent mode.
For example: CDR shows the transparency indicator as transparentfor basic service is BS30.

5.2.92 Tracking Area Identity (RDS13870) (deferred)
This field uniquely identifies one Tracking Area. The Tracking Area Identity is constructed from the MCC
(Mobile Country Code), MNC (Mobile Network Code) and TAC (Tracking Area Code).The Tracking Area
Identity information element is coded as below. (TS 29.118 V8.6.0 section 9.4.21, TS24.301 V8.6.0
section 9.9.3.32)
5.2.93 Update result
This field contains the result of the location update request as defined in the MAP (TS 29.002 [11]). Note
that this field is only provided if the attempted update was unsuccessful.
5060 WCS position : this information is not recorded in the CDR, as the VLR location update and the
HLR location update records are not generated.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


5.3 Charging Data Record Structure
5.3.1 ASN.1 definitions for CDR information
Within the current 3GPP TS 32-series of specifications the ASN.1 definitions are based on ITU-T
Recommendation X.208 [22], which has been superseded by ITU-T Recommendation X.680. This newer
version not only includes new features but also removes some that were present in ITU-T
Recommendation X.208. It was agreed that where possible, the GPRS work would be based on those
ASN.1 features that were common to both. However, where necessary, the new features in ITU-T
Recommendation X.680 [23] be used in some places. ITU-T Recommendation X.208 [22] feature that are
no longer in ITU-T Recommendation X.680 [23] will not be used.
Notes:
1. The syntax of the ASN.1 part was verified with the
OSS Nokalva ASN.1 Compiler Version 5.4.3
Copyright I OSS Nokalva, Inc. 1989-2001. All rights reserved.
Note: A product license is needed for usage.
2. The ASN.1 definitions at the end shows the parameter values used in 5060 WCS.
Please note, that there exists private extensions (marked in red) to the standard e.g. for
NumberingType.
For details, please refer to document [30] .
3. Info to interprete the ASN.1 definition correctly:The information after
a. is remark/comment or
b. one field which has not be developed.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


TS32205-DataTypes {itu-t (0) identified-organization (4) etsi(0) mobileDomain
(0) umts-Operation-Maintenance (3) ts-32-205 (205) informationModel (0)
asn1Module (2) version1 (1)}
DEFINITIONS IMPLICIT TAGS ::=
BEGIN
-- Note that use of more recent module versions is allowed as long as
-- the imported parameters are identical the ones in the module versions
-- specified below.
CallEventRecord ::= CHOICE
{
-- Record values 0..19 are 3G circuit switch specific
-- 20..27 are 3G packet switch specific
-- 30..50 are application specific
moCallRecord [0] MOCallRecord,
mtCallRecord [1] MTCallRecord,
-- RDS6904 Start
roamingRecord [2] RoamingRecord,
-- RDS6904 End
incGatewayRecord [3] IncGatewayRecord,
outGatewayRecord [4] OutGatewayRecord,
transitRecord [5] TransitCallRecord,
moSMSRecord [6] MOSMSRecord,
mtSMSRecord [7] MTSMSRecord,
-- moSMSIWRecord [8] MOSMSIWRecord,
-- mtSMSGWRecord [9] MTSMSGWRecord,
ssActionRecord [10] SSActionRecord,
-- RDS6904 Start
hlrIntRecord [11] HLRIntRecord,
-- RDS6904 End
-- locUpdateHLRRecord [12] LocUpdateHLRRecord,
-- locUpdateVLRRecord [13] LocUpdateVLRRecord,
-- commonEquipRecord [14] CommonEquipRecord,
-- recTypeExtensions [15] AlcatelManagedExtensions,
termCAMELRecord [16] TermCAMELRecord,
-- sgsnPDPRecord [20] SGSNPDPRecord,
-- ggsnPDPRecord [21] GGSNPDPRecord,
-- sgsnMMRecord [22] SGSNMMRecord,
-- sgsnSMORecord [23] SGSNSMORecord,
-- sgsnSMTRecord [24] SGSNSMTRecord,
-- sgsnLCTRecord [25] SGSNMTLCSRecord,
-- sgsnLCORecord [26] SGSNMOLCSRecord,
-- sgsnLCNRecord [27] SGSNNILCSRecord,
-- mmO1Srecord [30] MMO1Srecord,
-- mmO4FrqRecord [31] MMO4FrqRecord,
-- mmO4FrsRecord [32] MMO4FrsRecord,
-- mmO4Drecord [33] MMO4Drecord,
-- mmO1Drecord [34] MMO1Drecord,
-- mmO4Rrecord [35] MMO4Rrecord,
-- mmO1Rrecord [36] MMO1Rrecord,
-- mmOMDRecord [37] MMOMDRecord,
-- mmR4Frecord [38] MMR4Frecord,
-- mmR1NrqRecord [38] MMR1NrqRecord,
-- mmR1NrsRecord [40] MMR1NrsRecord,
-- mmR1RtRqRecord [41] MMR1RtRecord,
-- mmR1AFRecord [43] MMR1Arecord,
-- mmR4DrqRecord [44] MMR4DrqRecord,
-- mmR4DrsRecord [45] MMR4DrsRecord,
-- mmR1RRRecord [46] MMR1RRRecord,
-- mmR4RrqRecord [47] MMR4RrqRecord,
-- mmR4RrsRecord [48] MMR4RrsRecord,
-- mmRMDRecord [49] MMRMDRecord,
-- mmFRecord [50] MMFRecord
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


}

MOCallRecord ::= SET
{
recordType [0] CallEventRecordType,
servedIMSI [1] IMSI OPTIONAL,
servedIMEI [2] IMEI OPTIONAL,
-- served IMEI is also used for MOC-CF (RDS8184 / D46475)
servedMSISDN [3] MSISDN OPTIONAL,
callingNumber [4] CallingNumber OPTIONAL,
calledNumber [5] CalledNumber OPTIONAL,
translatedNumber [6] TranslatedNumber OPTIONAL,
-- connectedNumber [7] ConnectedNumber OPTIONAL,
roamingNumber [8] RoamingNumber OPTIONAL,
recordingEntity [9] RecordingEntity,
mscIncomingTKGP [10] TrunkGroup OPTIONAL,
mscOutgoingTKGP [11] TrunkGroup OPTIONAL,
location [12] LocationAreaAndCell OPTIONAL,
-- location info used also in case of MOC-CF (RDS8184 / D46475)
changeOfLocation [13] SEQUENCE OF LocationChange OPTIONAL,
basicService [14] BasicServiceCode OPTIONAL,
transparencyIndicator [15] TransparencyInd OPTIONAL,
-- changeOfService [16] SEQUENCE OF ChangeOfService OPTIONAL,
supplServicesUsed [17] SEQUENCE OF SuppServiceUsed OPTIONAL,
-- aocParameters [18] AOCParameters OPTIONAL,
-- changeOfAOCParms [19] SEQUENCE OF AOCParmChange OPTIONAL,
msClassmark [20] Classmark OPTIONAL,
-- changeOfClassmark [21] ChangeOfClassmark OPTIONAL,
seizureTime [22] TimeStamp OPTIONAL,
answerTime [23] TimeStamp OPTIONAL,
releaseTime [24] TimeStamp OPTIONAL,
callDuration [25] CallDuration,
-- dataVolume [26] DataVolume OPTIONAL,
-- radioChanRequested [27] RadioChanRequested OPTIONAL,
radioChanUsed [28] TrafficChannel OPTIONAL,
-- changeOfRadioChan [29] ChangeOfRadioChannel OPTIONAL,
causeForTerm [30] CauseForTerm,
diagnostics [31] Diagnostics OPTIONAL,
callReference [32] CallReference,
sequenceNumber [33] INTEGER OPTIONAL,
additionalChgInfo [34] AdditionalChgInfo OPTIONAL,
recordExtensions [35] AlcatelManagedExtensions OPTIONAL,
gsm-SCFAddress [36] Gsm-SCFAddress OPTIONAL,
serviceKey [37] ServiceKey OPTIONAL,
networkCallReference [38] NetworkCallReference OPTIONAL,
mSCAddress [39] MSCAddress OPTIONAL,
cAMELInitCFIndicator [40] CAMELInitCFIndicator OPTIONAL,
defaultCallHandling [41] DefaultCallHandling OPTIONAL,
-- hSCSDChanRequested [42] NumOfHSCSDChanRequested OPTIONAL,
-- hSCSDChanAllocated [43] NumOfHSCSDChanAllocated OPTIONAL,
-- changeOfHSCSDParms [44] SEQUENCE OF HSCSDParmsChange OPTIONAL,
fnur [45] Fnur OPTIONAL,
-- aiurRequested [46] AiurRequested OPTIONAL,
-- chanCodingsAcceptable [47] SEQUENCE OF ChannelCoding OPTIONAL,
chanCodingUsed [48] ChannelCoding OPTIONAL,
-- speechVersionSupported [49] SpeechVersionIdentifier OPTIONAL,
speechVersionUsed [50] SpeechVersionIdentifier OPTIONAL,
numberOfDPEncountered [51] INTEGER OPTIONAL,
levelOfCAMELService [52] LevelOfCAMELService OPTIONAL,
freeFormatData [53] FreeFormatData OPTIONAL,
cAMELCallLegInformation [54] SEQUENCE OF CAMELInformation OPTIONAL,
-- freeFormatDataAppend [55] BOOLEAN OPTIONAL,
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


defaultCallHandling-2 [56] DefaultCallHandling OPTIONAL,
gsm-SCFAddress-2 [57] Gsm-SCFAddress OPTIONAL,
serviceKey-2 [58] ServiceKey OPTIONAL,
freeFormatData-2 [59] FreeFormatData OPTIONAL,
-- freeFormatDataAppend-2 [60] BOOLEAN OPTIONAL,
systemType [61] SystemType OPTIONAL,
rateIndication [62] RateIndication OPTIONAL,
-- RDS9189 Start
locationRoutNum [63] LocationRoutingNumber OPTIONAL,
lrnSoInd [64] LocationRoutingNumberSourceIndicator OPTIONAL,
lrnQuryStatus [65] LocationRoutingNumberQueryStatus OPTIONAL,
-- RDS9189 End
-- jIPPara [66] JurisdictionInformationParameter OPTIONAL,
-- jIPSoInd [67] JurisdictionInformationParameterSourceIndicator OPTIONAL,
-- jIPQuryStatus [68] JurisdictionInformationParameterQueryStatus OPTIONAL,
partialRecordType [69] PartialRecordType OPTIONAL, -- Rel 5
guaranteedBitRate [70] GuaranteedBitRate OPTIONAL,
maximumBitRate [71] MaximumBitRate OPTIONAL
-- redial [72] BOOLEAN OPTIONAL, -R8
-- reasonForServiceChange [73] ReasonForServiceChange OPTIONAL, -R8
-- serviceChangeInitiator [74] BOOLEAN OPTIONAL -R8
}

-- The MOCallRecordExtensionType with the object identifier mOC-Extension-OID define
-- a AlcatelManagedExtension contained in the recordExtensions of the MOCallRecord
MOCallRecordExtensionType ::= SET
{
hotBillingSubscriber [0] BOOLEAN DEFAULT FALSE,
iPConnection [1] BOOLEAN DEFAULT FALSE,
rNCIdOfFirstRNC [2] RNCId OPTIONAL,
mSCategory [3] Category OPTIONAL,
cSARP [4] OCTET STRING (SIZE (1)) OPTIONAL,
-- RDS9804b Start
cUG-Interlock [5] CUG-Interlock OPTIONAL,
cUG-Index [6] CUG-Index OPTIONAL,
cUGOutgoingAccessSuppressed [7] BOOLEAN OPTIONAL,
cUGOutgoingAccessIndicator [8] BOOLEAN OPTIONAL,
-- RDS9804b End
bSCIdOfFirstBSC [9] BSCId OPTIONAL,
multimediaCall [10] BOOLEAN DEFAULT FALSE, -- TRUE if multimedia call
-- the next parameter is not implemented yet
interconnectFacility [11] InterconnectFacility OPTIONAL,
-- RDS9851 Start
mscIncomingTKGPExtension [12] TrunkGroupExtension OPTIONAL,
mscOutgoingTKGPExtension [13] TrunkGroupExtension OPTIONAL,
-- RDS9851 End
-- RDS14064 Start
subscribedOSSSCodes [14] SEQUENCE OF SubscribedOSSSCodes
OPTIONAL
-- RDS14064 End
-- eMLPPindication removed
}
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


MTCallRecord ::= SET
{
servedIMSI [1] IMSI,
-- served IMEI is also used for MTC-CF (RDS8184 / D46475)
servedMSISDN [3] CalledNumber OPTIONAL,
connectedNumber [5] ConnectedNumber OPTIONAL,
-- location info used also in case of MTC-CF (RDS8184 / D46475)
changeOfLocation [10] SEQUENCE OF LocationChange OPTIONAL,
-- aocParameters [15] AOCParameters OPTIONAL,
-- changeOfAOCParms [16] SEQUENCE OF AOCParmChange OPTIONAL,
msClassmark [17] Classmark OPTIONAL,
-- changeOfClassmark [18] ChangeOfClassmark OPTIONAL,
-- radioChanRequested [24] RadioChanRequested OPTIONAL,
radioChanUsed [25] TrafficChannel OPTIONAL,
-- changeOfRadioChan [26] ChangeOfRadioChannel OPTIONAL,
-- hSCSDChanRequested [35] NumOfHSCSDChanRequested OPTIONAL,
-- hSCSDChanAllocated [36] NumOfHSCSDChanAllocated OPTIONAL,
-- changeOfHSCSDParms [37] SEQUENCE OF HSCSDParmsChange OPTIONAL,
fnur [38] Fnur OPTIONAL,
-- aiurRequested [39] AiurRequested OPTIONAL,
-- chanCodingsAcceptable [40] SEQUENCE OF ChannelCoding OPTIONAL,
chanCodingUsed [41] ChannelCoding OPTIONAL,
-- speechVersionSupported [42] SpeechVersionIdentifier OPTIONAL,
speechVersionUsed [43] SpeechVersionIdentifier OPTIONAL,
-- gsm-SCFAddress [44] Gsm-SCFAddress OPTIONAL,
-- serviceKey [45] ServiceKey OPTIONAL,
systemTypeR5 [46] SystemType OPTIONAL, -- Rel 5 !!
-- RDS9189 Start
-- RDS9189 End
-- jIPSoInd[52]JurisdictionInformationParameterSourceIndicator OPTIONAL,
-- jIPQuryStatus[53] JurisdictionInformationParameterQueryStatus OPTIONAL,
partialRecordType [54] PartialRecordType OPTIONAL, -- Rel 5
guaranteedBitRate [55] GuaranteedBitRate OPTIONAL,
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


maximumBitRate [56] MaximumBitRate OPTIONAL,
-- reasonForServiceChange [57] ReasonForServiceChange OPTIONAL, --R8
-- serviceChangeInitiator [58] BOOLEAN OPTIONAL --R8
systemType [61] SystemType OPTIONAL Rel 4 !!
}

-- Note to parameter SystemType/systemTypeR5:
-- Due to incompatibility between
-- Release 4 standard 3GPP TS32.205 v4.7.0 using TAG value 61)
-- and Release 5 standard 3GPP TS 32.298 v8.8.0 using TAG value 46),
-- both TAG-values are defined
-- for the MTCCallrecord, but only one is present.
-- Logic on decoder side has to check the presence and has to assign it
-- it accordingly.

-- The MTCallRecordExtensionType with the object identifier mTC-Extension-OID define
-- a AlcatelManagedExtension contained in the recordExtensions of the MTCallRecord
MTCallRecordExtensionType ::= SET
{
gsm-SCFAddress [1] Gsm-SCFAddress OPTIONAL,-- set with the O_CSI data
serviceKey [2] ServiceKey OPTIONAL,-- set with the O_CSI data
redirectingCounter [3] INTEGER OPTIONAL,
mSCategory [5] Category OPTIONAL,
cSARP [6] OCTET STRING (SIZE (1)) OPTIONAL,
-- RDS9804b Start
cUG-Interlock [7] CUG-Interlock OPTIONAL,
cUG-Index [8] CUG-Index OPTIONAL,
cUGIncomingAccessUsed [9] BOOLEAN OPTIONAL,
-- RDS9804b End
multimediaCall [11] BOOLEAN DEFAULT FALSE, -- TRUE if multimedia call
redirectingNumber [12] BCDDirectoryNumber OPTIONAL,
-- RDS9851 Start
-- RDS9851 End
-- RDS9804b Start
cUGOutgoingAccessIndicator [16] BOOLEAN OPTIONAL, only for MT CF CDR
-- RDS9804b End
-- RDS14064 Start
subscribedOSSSCodes [17] SEQUENCE OF SubscribedOSSSCodes OPTIONAL
-- RDS14064 End

}

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


TermCAMELRecord ::= SET
{
recordtype [0] CallEventRecordType,
servedIMSI [1] IMSI, -- was OPTIONAL
interrogationTime [4] TimeStamp,
destinationRoutingAddress [5] DestinationRoutingAddress,
gsm-SCFAddress [6] Gsm-SCFAddress,
serviceKey [7] ServiceKey,
calledNumber [12] CalledNumber,
numberOfDPEncountered [25] INTEGER OPTIONAL,
levelOfCAMELService [26] LevelOfCAMELService OPTIONAL,
defaultCallHandling-2 [30] DefaultCallHandling OPTIONAL,
gsm-SCFAddress-2 [31] Gsm-SCFAddress OPTIONAL,
serviceKey-2 [32] ServiceKey OPTIONAL,
freeFormatData-2 [33] FreeFormatData OPTIONAL,
-- freeFormatDataAppend-2 [34] BOOLEAN OPTIONAL,
mscServerIndication [35] BOOLEAN OPTIONAL,
-- RDS9189 Start
lrnQuryStatus [38] LocationRoutingNumberQueryStatus OPTIONAL
-- RDS9189 End
-- partialRecordType [42] PartialRecordType OPTIONAL

}
-- The TermCAMELRecordExtensionType with the object identifier termCAMEL-
Extension-OID
-- define a AlcatelManagedExtension contained in the recordExtensions of the
-- TermCAMELRecord
TermCAMELRecordExtensionType ::= SET
{
-- RDS9851 Start
-- RDS9851 End
-- RDS14064 Start
-- RDS14064 End
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


}

IncGatewayRecord ::= SET
{
-- RDS9189 Start
-- RDS9189 End
-- partialRecordType [22] PartialRecordType OPTIONAL,
-- RDS6904 Start
iSDN-BC [23] ISDN-BC OPTIONAL,
lLC [24] LLC OPTIONAL,
hLC [25] HLC OPTIONAL,
-- RDS6904 End
-- below is R8 content
-- partialRecordType ,iSDN-BC, lLC, hLC are removed in R8
-- reasonForServiceChange [22] ReasonForServiceChange OPTIONAL,
-- serviceChangeInitiator [23] BOOLEAN OPTIONAL}
-- end of r8 content
}

-- The IncGatewayRecordExtensionType with the object identifier
-- incGateway-Extension-OID define a AlcatelManagedExtension contained
-- in the recordExtensions of the IncGatewayRecord
IncGatewayRecordExtensionType ::= SET
{
-- RDS9851 Start
-- RDS9851 End
-- RDS6034 Start --
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


-- RDS6034 End --
-- RDS6904 Start
isdnBasicService [10] BasicService OPTIONAL,
-- RDS6904 End
-- RDS9365 Start
basicService [11] BasicServiceCode OPTIONAL
-- RDS9365 End
}

OutGatewayRecord ::= SET {
-- RDS9189 Start
-- RDS9189 End

-- below is R8 content
-- partialRecordType is removed in R8
-- reasonForServiceChange [22] ReasonForServiceChange OPTIONAL,
-- serviceChangeInitiator [23] BOOLEAN OPTIONAL}
-- end of r8 content

}

-- The OutGatewayRecordExtensionType with the object identifier
-- outGateway-Extension-OID define a AlcatelManagedExtension contained
-- in the recordExtensions of the OutGatewayRecord
OutGatewayRecordExtensionType ::= SET {
-- RDS9851 Start
-- RDS9851 End
-- RDS6904 Begin
iSDN-BC [4] ISDN-BC OPTIONAL,
lLC [5] LLC OPTIONAL,
hLC [6] HLC OPTIONAL,
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


-- RDS6904 End
-- RDS9365 Start
-- RDS9365 End
-- RDS16253 Start
OutgoingIAMcallednumber [9] CalledNumber OPTIONAL
-- RDS16253 End

}

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


TransitCallRecord ::= SET {
seizureTimestamp [7] TimeStamp OPTIONAL,
answerTimestamp [8] TimeStamp OPTIONAL,
releaseTimestamp [9] TimeStamp OPTIONAL,
-- RDS9189 Start
-- RDS9189 End
-- partialRecordType is removed in R8
}

-- The TransitGatewayRecordExtensionType with the object identifier
-- transit-Extension-OID define a AlcatelManagedExtension contained
-- in the recordExtensions of the TransitGatewayRecord

TransitRecordExtensionType ::= SET {
-- RDS9851 Start --
-- RDS9851 End --
-- RDS6034 Start --
networkCallReference [9] NetworkCallReference OPTIONAL
-- RDS6034 End --
}

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


MOSMSRecord ::= SET {
msClassmark [4] Classmark,
serviceCentre [5] AddressString,
messageReference [8] MessageReference,
originationTime [9] TimeStamp,
smsResult [10] SMSResult OPTIONAL,
destinationNumber [12] SmsTpDestinationNumber OPTIONAL,
cAMELSMSInformation [13] CAMELSMSInformation OPTIONAL,
systemType [14] SystemType OPTIONAL
-- locationExtension [15] LocationCellExtension OPTIONAL R8
}

-- The MOSMSRecordExtensionType with the object identifier
-- mOSMS-Extension-OID define a AlcatelManagedExtension contained
-- in the recordExtensions of the MOSMSRecord
MOSMSRecordExtensionType ::= SET {
hotBillingSubscriber[0] BOOLEAN DEFAULT FALSE,
sMSSize [3] INTEGER OPTIONAL,
-- RDS14064 Start
-- RDS14064 End
-- RDS13870 Start
--trackingAreaIdentity [TBD] TAI OPTIONAL,
--eCGI [TBD] ECGI OPTIONAL
-- RDS13870 End
}

MTSMSRecord ::= SET{
serviceCentre [1] AddressString,
deliveryTime [8] TimeStamp,
smsResult [9] SMSResult OPTIONAL,
systemType [11] SystemType OPTIONAL,
cAMELSMSInformation [12] CAMELSMSInformation OPTIONAL -- R5
-- locationExtension [13] LocationCellExtension OPTIONAL R8

}

-- The MTSMSRecordExtensionType with the object identifier
-- mTSMS-Extension-OID define a AlcatelManagedExtension contained
-- in the recordExtensions of the MTSMSRecord
MTSMSRecordExtensionType ::= SET {
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


sMSoriginatingNumber [1] BCDDirectoryNumber OPTIONAL,
sMSSize [4] INTEGER OPTIONAL,
-- RDS14064 Start
-- RDS14064 End
-- RDS13870 Start
--sGscause [TBD] SGscause OPTIONAL
--trackingAreaIdentity [TBD] TAI OPTIONAL,
--eCGI [TBD] ECGI OPTIONAL
-- RDS13870 End
}

SSActionRecord ::= SET {
basicServices [7] BasicServices OPTIONAL,
supplService [8] SS-Code OPTIONAL,
ssAction [9] SSActionType OPTIONAL,
ssActionTime [10] TimeStamp,
ssParameters [11] SSParameters OPTIONAL,
ssActionResult [12] SSActionResult OPTIONAL,
systemType [15] SystemType OPTIONAL
}

-- The SSActionRecordExtensionType with the object identifier
-- sSAction-Extension-OID define a AlcatelManagedExtension contained
-- in the recordExtensions of the SSActionRecord
SSActionRecordExtensionType ::= SET {
serviceDuration [2] ServiceDuration OPTIONAL,
-- RDS14064 Start
-- RDS14064 End
}
-- RDS6904 Start
RoamingRecord ::= SET {
servedIMSI [1] IMSI, -- was OPTIONAL
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


-- RDS9189 Start
-- RDS9189 End
partialRecordType [30] PartialRecordType OPTIONAL, - Rel 5, not 24 !!

}

-- The RoamingRecordExtensionType with the object identifier
-- rOAM-Extension-OID define a AlcatelManagedExtension contained
-- in the recordExtensions of the roamingRecord
RoamingRecordExtensionType ::= SET
{
-- the next 5 parameters are not implemented yet
recordNumber [0] INTEGER OPTIONAL,
versionNumber [1] INTEGER OPTIONAL,
numberPortabilityInformation [2] NumberPortabilityInformation OPTIONAL,
tariffType [4] INTEGER OPTIONAL,
-- RDS6904 Start
-- RDS6904 End
-- the rest of the parameters are not implemented yet
nationalIndicator [8] NationalIndicator OPTIONAL, -- Ux
operatorIndicator [9] OperatorIndicator OPTIONAL, -- Ux
hotBillingSubscriber [10] BOOLEAN DEFAULT FALSE, -- Ux and LM
upstreamCarrier [11] CarrierNumber OPTIONAL, -- Ux
downstreamCarrier [12] CarrierNumber OPTIONAL, -- Ux
callingPartyLocationNumber [13] BCDDirectoryNumber OPTIONAL,
redirectingNumber [14] BCDDirectoryNumber OPTIONAL,
originalCalledNumber [15] BCDDirectoryNumber OPTIONAL,
pRBTIndication [16] BOOLEAN DEFAULT FALSE,
timeExtensions [17] TimeExtensions OPTIONAL,
optimalRouteingType [18] OptimalRouteingType OPTIONAL,
disconnectingParty [19] DisconnectingParty OPTIONAL,
-- RDS14064 Start
-- RDS14064 End
}
-- RDS6904 End

--MOSMSIWRecord ::= SET
--{
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


-- recordType [0] CallEventRecordType,
-- serviceCentre [1] AddressString,
-- servedIMSI [2] IMSI,
-- recordingEntity [3] RecordingEntity,
-- eventTime [4] TimeStamp,
-- smsResult [5] SMSResult OPTIONAL,
-- recordExtensions [6] AlcatelManagedExtensions OPTIONAL
--}
--
--MTSMSGWRecord ::= SET
--{
-- serviceCentre [1] AddressString,
-- servedMSISDN [3] MSISDN OPTIONAL,
-- smsResult [6] SMSResult OPTIONAL,
--}

-- RDS6904 Start
HLRIntRecord ::= SET
{
servedMSISDN [2] MSISDN,
routingNumber [5] RoutingNumber, -- was OPTIONAL
interrogationTime [6] TimeStamp,
numberOfForwarding [7] NumberOfForwarding OPTIONAL,
interrogationResult [8] HLRIntResult OPTIONAL,
recordExtensions [9] AlcatelManagedExtensions OPTIONAL
}
-- RDS6904 End
HLRIntRecordExtensionType ::= SET {
-- RDS14064 Start
subscribedOSSSCodes [1] SEQUENCE OF subscribedOSSSCodes OPTIONAL
-- RDS14064 End
}

--LocUpdateHLRRecord ::= SET
--{
-- oldLocation [3] Visited-Location-info OPTIONAL,
-- newLocation [4] Visited-Location-info,
-- updateTime [5] TimeStamp,
-- updateResult [6] LocUpdResult OPTIONAL,
--}
--LocUpdateVLRRecord ::= SET
--{
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


-- oldLocation [4] Location-info OPTIONAL,
-- newLocation [5] Location-info,
-- msClassmark [6] Classmark,
-- updateTime [7] TimeStamp,
-- updateResult [8] LocUpdResult OPTIONAL,
--}
--
--CommonEquipRecord ::= SET
--{
-- equipmentType [1] EquipmentType,
-- equipmentId [2] EquipmentId,
-- basicService [6] BasicServiceCode OPTIONAL,
-- supplServicesUsed [8] SEQUENCE OF SuppServiceUsed OPTIONAL,
-- seizureTime [9] TimeStamp,
-- releaseTime [10] TimeStamp OPTIONAL,
-- callDuration [11] CallDuration,
-- callReference [12] CallReference,
-- sequenceNumber [13] INTEGER OPTIONAL,
-- recordExtensions [14] AlcatelManagedExtensions OPTIONAL,
-- systemType [15] SystemType OPTIONAL,
-- rateIndication [16] RateIndication OPTIONAL,
-- fnur [17] Fnur OPTIONAL
-- partialRecordType [18] PartialRecordType OPTIONAL
--}
-- OBSERVED IMEI TICKETS
--
-- ObservedIMEITicket ::= SET
--{
-- servedIMEI [0] IMEI,
-- imeiStatus [1] IMEIStatus,
-- location [6] LocationAreaAndCell ,
-- imeiCheckEvent [7] IMEICheckEvent OPTIONAL,
-- callReference [8] CallReference OPTIONAL,
--}
-- LOCATION SERVICE TICKETS

-- FTAM / FTP / TFTP FILE CONTENTS

----------------------------------------------------------------------------
-- ALCATEL-LUCENT 5060 WCSs proprietary extension data
--

root-3GPP-Billing-Extensions OBJECT IDENTIFIER ::= { iso(1) identified-
organization(3) icd-ecma(12) member-company(2) ALCATEL(1006) amc(53) switch-
infra-gsm-E10(2) billing-3GPP-extensions(5) }
mOC-Extension-OID OBJECT IDENTIFIER ::= { root-3GPP-Billing-Extensions moc(0)
}
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


mTC-Extension-OID OBJECT IDENTIFIER ::= { root-3GPP-Billing-Extensions mtc(1)
}
-- RDS6904 Start
rOAM-Extension-OID OBJECT IDENTIFIER ::= { root-3GPP-Billing-Extensions
roam(2) }
-- RDS6904 End

incGateway-Extension-OID OBJECT IDENTIFIER ::= { root-3GPP-Billing-Extensions
incGateway(3) }
outGateway-Extension-OID OBJECT IDENTIFIER ::= { root-3GPP-Billing-Extensions
outGateway(4) }
transit-Extension-OID OBJECT IDENTIFIER ::= { root-3GPP-Billing-Extensions
transit(5) }
mOSMS-Extension-OID OBJECT IDENTIFIER ::= { root-3GPP-Billing-Extensions
mosms(6) }
mTSMS-Extension-OID OBJECT IDENTIFIER ::= { root-3GPP-Billing-Extensions
mtsms(7) }
sSAction-Extension-OID OBJECT IDENTIFIER ::= { root-3GPP-Billing-Extensions
ssAction(10) }

hLRINT-Extension-OID OBJECT IDENTIFIER ::= { root-3GPP-Billing-Extensions
hlrint(11) }

termCAMEL-Extension-OID OBJECT IDENTIFIER ::= { root-3GPP-Billing-Extensions
termCAMEL(16) }

-- For example:
-- MO_EXT => '1.3.12.2.1006.53.2.5.0';
-- MT_EXT => '1.3.12.2.1006.53.2.5.1';
-- why 1.3 will be encoded as 2B, because 1 means ISO, the beneath arc will
be encoded by arc number + 40T, so 3+40=43 i.e. 2B
-- why 1006 encoded as 876E, originally 1006 is 03EE i.e 0000 0011 1110 1110,
divide the bit array to 7 bits each and take them as OCTET, then we can
get 0000 0111,0110 1110, that is 076E at last change the MSB is first OCTET
to 1 ,then we get 876E

BSCId ::= INTEGER
-- Point Code of the BSC

CUG-Index ::= INTEGER (0..32767)
-- The internal structure is defined in ETS 300 138.

CUG-Interlock ::= OCTET STRING (SIZE (4))

InterconnectFacility ::= SEQUENCE
{
interconnectGroupNumber [0] INTEGER (0..65535),
interconnectType [1] InterfaceType
}
-- RDS9851 Start
InterfaceType ::= ENUMERATED
{
unknown (0), -- currently not used for billing
tDM-T1 (1),
aAL1-TRUNK-IF (2),
aAL2 (3),
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


dSL-AAL2-IF (4),
voIP (5), -- also used for SIP-trunk
vOIP-IF-EXT (6),
aAL2-TRUNK-IF (12),
gTP-IF (13),
vOIP-IF (14),
tDM-E1 (15),
nB-IP (16),
nB-ATM (17),
ePH-IF (18),
TDM (19), -- PR D49950
noItfTypPresent (255)
}
-- RDS9851 End

RNCId ::= INTEGER
-- Point Code of the RNC

ServiceDuration ::= INTEGER -- Duration in seconds of the USSD service

-- RDS9851 Start
TrunkGroupType ::= ENUMERATED
{
iNVALID (0),
iSUPTrunkGroup (1),
gR303TMC (2),
gR303CSC (3),
cASTrunkGroup (4),
cASLine (5),
pRITrunkGroup (6),
nFAS-PRI (7),
cASDAL (8),
bICCTrunkGroup (9),
cASLES (10),
bSSTrunkGroup (11), --RDS13186
sIPTrunkGroup (12),
gPRS (13),
iNTERCONNECT (14),
bNC (15),
iNTERWORKING (16),
uTRANTrunkGroup (17),
bSSIDVOIP (18),
tUP (19),
uMATrunkGroup (20),
nBAAL2 (21),
iMSSIP (22),
SIP-I (25), -- RDS6029
noTrunkGroupPresent (255)
}
-- RDS9851 End
TrunkGroupExtension ::= SEQUENCE
{
trunkGroupType [0] TrunkGroupType,
interfaceType [1] InterfaceType,
mGWNumber [2] INTEGER,
trunkCircuit [3] INTEGER
}
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


-----------------------------------------------------------------------------
---
-- COMMON DATA TYPES
--
AdditionalChgInfo ::= SEQUENCE
{
chargeIndicator [0] ChargeIndicator OPTIONAL,
chargeParameters [1] OCTET STRING OPTIONAL
}

AiurRequested ::= ENUMERATED
{
--
-- See Bearer Capability TS 24.008
-- (note that value 4 is intentionally missing
-- because it is not used in TS 24.008)
--
aiur09600BitsPerSecond (1),
aiur38400BitsPerSecond1 (9),
aiur38400BitsPerSecond4 (12)
}

AOCParameters ::= SEQUENCE
{
--
-- See TS 22.024.
--
e1 [1] Eparameter OPTIONAL,
e7 [7] Eparameter OPTIONAL
}

AOCParmChange ::= SEQUENCE
{
changeTime [0] TimeStamp,
newParameters [1] AOCParameters
}

BasicServices ::= SET OF BasicServiceCode

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


BCDDirectoryNumber ::= OCTET STRING
--
-- This type contains the binary coded decimal representation of
-- a directory number e.g. calling/called/connected/translated number.
-- The encoding of the octet string is in accordance with the
-- the elements Calling party BCD number, Called party BCD number
-- and Connected number defined in TS 24.008.
-- This encoding includes type of number and number plan information
-- together with a BCD encoded digit string.
-- It may also contain both a presentation and screening indicator
-- (octet 3a).
-- For the avoidance of doubt, this field does not include
-- octets 1 and 2, the element name and length, as this would be
-- redundant.
--
-- A directory number can have up to 31 digits

CallDuration ::= INTEGER
--
-- The call duration in seconds.
-- For successful calls this is the chargeable duration.
-- For call attempts this is the call holding time.
--

CallEventRecordType ::= INTEGER
{
moCallRecord (0),
mtCallRecord (1),
roamingRecord (2),
incGatewayRecord (3),
outGatewayRecord (4),
transitCallRecord (5),
moSMSRecord (6),
mtSMSRecord (7),
moSMSIWRecord (8),
mtSMSGWRecord (9),
ssActionRecord (10),
hlrIntRecord (11),
locUpdateHLRRecord(12),
locUpdateVLRRecord(13),
commonEquipRecord (14),
moTraceRecord (15),
mtTraceRecord (16),
termCAMELRecord (17),
--
-- Record values 18..22 are GPRS specific.
-- The contents are defined in TS 32.015
--
sgsnPDPRecord (18),
ggsnPDPRecord (19),
sgsnMMRecord (20),
sgsnSMORecord (21),
sgsnSMTRecord (22),

--
-- Record values 23..25 are CS-LCS specific.
-- The contents are defined in this specification
--
mtLCSRecord (23),
moLCSRecord (24),
niLCSRecord (25),
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


--
-- Record values 26..28 are PS-LCS specific.
--
sgsnMtLCSRecord (26),
sgsnMoLCSRecord (27),
sgsnNiLCSRecord (28),
--
-- Record values 29..49 are MMS specific.
--
mmO1Srecord (29),
mmO4FrqRecord (30),
mmO4FrsRecord (31),
mmO4Drecord (32),
mmO1Drecord (33),
mmO4Rrecord (34),
mmO1Rrecord (35),
mmOMDRecord (36),
mmR4Frecord (37),
mmR1NrqRecord (38),
mmR1NrsRecord (39),
mmR1RtRecord (40),
mmR1Arecord (42),
mmR4DrqRecord (43),
mmR4DrsRecord (44),
mmR1RRRecord (45),
mmR4RrqRecord (46),
mmR4RrsRecord (47),
mmRMDRecord (48),
mmFRecord (49)
}

CalledNumber ::= BCDDirectoryNumber

-- Structure of Called Number
--
-- 1. Octet: TAG
-- 2. Octet: Length
-- 3. Octet: Bit 7 reserved
-- Bit 6-4 NOA / Numbering Type (NumberingType-struct)
-- Bit 0-3 NPI / Numbering Plan (NumberingPlan-struct)
-- 4.- n. Octet: BCD-Digits (2 digits per Octet, odd digit ending with
F as filler as filler)

CallingNumber ::= BCDDirectoryNumber

-- Structure of Calling Number
--
-- 1. Octet: TAG
-- 2. Octet: Length
-- Bit 6-5 Presentation IndicatorPresentationIndicator-struct)
-- Bit 4-2 reserved
-- Bit 0-1 Screening Indicator (ScreeningIndicator-struct)

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


CallingPartyCategory ::= Category

CallReference ::= INTEGER

CallType ::= INTEGER
{
mobileOriginated (0),
mobileTerminated (1)
}

CallTypes ::= SET OF CallType

CAMELDestinationNumber ::= DestinationRoutingAddress

CAMELInformation ::= SET
{
cAMELDestinationNumber [1] CAMELDestinationNumber OPTIONAL,
-- connectedNumber [2] ConnectedNumber OPTIONAL,
-- roamingNumber [3] RoamingNumber OPTIONAL,
-- mscOutgoingTKGP [4] TrunkGroup OPTIONAL,
-- seizureTime [5] TimeStamp OPTIONAL,
-- answerTime [6] TimeStamp OPTIONAL,
-- releaseTime [7] TimeStamp OPTIONAL,
-- callDuration [8] CallDuration OPTIONAL,
cAMELInitCFIndicator [10] CAMELInitCFIndicator OPTIONAL,
-- causeForTerm [11] CauseForTerm OPTIONAL,
cAMELModification [12] ChangedParameters OPTIONAL,
-- diagnostics [14] Diagnostics OPTIONAL,
freeFormatData-2 [16] FreeFormatData OPTIONAL
-- freeFormatDataAppend-2 [17] BOOLEAN OPTIONAL
-- Below contents are all removed in R8
-- translatedNumber [18] TranslatedNumber OPTIONAL,
-- additionalChgInfo [19] AdditionalChgInfo OPTIONAL,
-- defaultCallHandling-2 [20] DefaultCallHandling OPTIONAL,
-- gsm-SCFAddress-2 [21] Gsm-SCFAddress OPTIONAL,
-- serviceKey-2 [22] ServiceKey OPTIONAL,
-- freeFormatDataIncoming-2 [23] FreeFormatData OPTIONAL,
-- freeFormatDataAppendInc-2 [24] BOOLEAN OPTIONAL,
-- locationRoutNum [25] LocationRoutingNumber OPTIONAL,
-- lrnSoInd [26] LocationRoutingNumberSourceIndicator OPTIONAL,
-- lrnQuryStatus [27] LocationRoutingNumberQueryStatus OPTIONAL,
-- jIPQuryStatus [30] JurisdictionInformationParameterQueryStatus OPTIONAL
}

CAMELInitCFIndicator ::= ENUMERATED
{
noCAMELCallForwarding (0),
cAMELCallForwarding (1)
}

CAMELModificationParameters ::= SET
{
--
-- The list contains only parameters changed due to CAMEL call
-- handling.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


--
callingPartyNumber [0] CallingNumber OPTIONAL,
-- callingPartyCategory [1] CallingPartyCategory OPTIONAL,
-- originalCalledPartyNumber [2] OriginalCalledNumber OPTIONAL,
genericNumbers [3] GenericNumbers OPTIONAL
-- redirectingPartyNumber [4] RedirectingNumber OPTIONAL,
-- redirectionCounter [5] NumberOfForwarding OPTIONAL
}

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


CAMELSMSInformation ::= SET
{
defaultSMSHandling [3] DefaultSMS-Handling OPTIONAL,
callingPartyNumber [5] CallingNumber OPTIONAL,
destinationSubscriberNumber [6] SmsTpDestinationNumber OPTIONAL,
cAMELSMSCAddress [7] AddressString OPTIONAL,
smsReferenceNumber [8] CallReferenceNumber OPTIONAL
}

Category ::= OCTET STRING (SIZE(1))
--
-- The internal structure is defined in CCITT Rec Q.763.
--

CauseForTerm ::= INTEGER
{ --
-- Cause codes from 16 up to 31 are defined in GSM12.15 as
-- CauseForRecClosing(cause for record closing).
-- There is no direct correlation between these two types.
-- LCS related causes belong to the MAP error causes acc. TS 29.002.
--
normalRelease (0),
partialRecord (1),
partialRecordCallReestablishment (2),
unsuccessfulCallAttempt (3),
stableCallAbnormalTermination (4),
cAMELInitCallRelease (5),
unauthorizedRequestingNetwork (52),
unauthorizedLCSClient (53),
positionMethodFailure (54),
unknownOrUnreachableLCSClient (58)
}

CellId ::= OCTET STRING (SIZE(2))
--
-- Coded according to TS 24.008
--

ChangedParameters ::= SET
{
changeFlags [0] ChangeFlags,
changeList [1] CAMELModificationParameters OPTIONAL
}

ChangeFlags ::= BIT STRING
{
callingPartyNumberModified (0),
callingPartyCategoryModified (1),
originalCalledPartyNumberModified (2),
genericNumbersModified (3),
redirectingPartyNumberModified (4),
redirectionCounterModified (5)
}

ChangeOfClassmark ::= SEQUENCE
{
classmark [0] Classmark,
changeTime [1] TimeStamp
}
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


ChangeOfRadioChannel ::= SEQUENCE
{
radioChannel [0] TrafficChannel,
speechVersionUsed [2] SpeechVersionIdentifier OPTIONAL
}

ChangeOfService ::= SEQUENCE
{
basicService [0] BasicServiceCode,
transparencyInd [1] TransparencyInd OPTIONAL,
fnur [4] Fnur OPTIONAL
}

ChannelCoding ::= ENUMERATED
{
tchF4800 (1),
tchF9600 (2),
tchF14400 (3)
}

ChargeIndicator ::= INTEGER
{
noCharge (0),
charge (1)
}

Classmark ::= OCTET STRING
--
-- See Mobile station classmark 2, TS 24.008
--

ConnectedNumber ::= BCDDirectoryNumber

-- Structure of Connected Number
--
-- 1. Octet: TAG
-- 2. Octet: Length
-- Bit 4-2 reserved

DataVolume ::= INTEGER
--
-- The volume of data transferred in segments of 64 octets.
--

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Diagnostics ::= CHOICE
{
gsm0408Cause [0] INTEGER,
-- See TS 24.008
-- gsm0902MapErrorValue [1] INTEGER,
-- Note: The value to be stored here corresponds to
-- the local values defined in the MAP-Errors and
-- MAP-DialogueInformation modules, for full details
-- see TS 29.002.
-- ccittQ767Cause [2] INTEGER,
-- See CCITT Q.767
-- networkSpecificCause [3] INTEGER,
-- To be defined by network operator
manufacturerSpecificCause [4] INTEGER,
-- To be defined by manufacturer
-- positionMethodFailureCause [5] PositionMethodFailure-Diagnostic,
-- see TS 29.002
-- unauthorizedLCSClientCause [6] UnauthorizedLCSClient-Diagnostic
-- see TS 29.002
}

EmergencyCallIndEnable ::= BOOLEAN

EmergencyCallIndication ::= SEQUENCE
{
cellId [0] CellId,
callerId [1] IMSIorIMEI
}

Eparameter ::= INTEGER (0..1023)
--
-- Coded according to TS 22.024 and TS 24.080
--
EquipmentId ::= INTEGER
EquipmentType ::= INTEGER { conferenceBridge (0)}
FileType ::= INTEGER{
callRecords (1),
traceRecords (9),
observedIMEITicket (14)
}

Fnur ::= ENUMERATED {
--
--
fnurNotApplicable (0),
fnur9600-BitsPerSecond (1),
fnur14400BitsPerSecond (2),
fnur31200BitsPerSecond (11)
}

ForwardToNumber ::= AddressString

FreeFormatData ::= OCTET STRING (SIZE(1..160))
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


--
-- Free formatted data as sent in the FCI message
-- See TS 29.078
--

GuaranteedBitRate ::= ENUMERATED {
gBR14400BitsPerSecond (1), -- BS20 non-transparent
gBR28800BitsPerSecond (2), -- BS20 non-transparent and transparent,
-- BS30 transparent and multimedia
gBR32000BitsPerSecond (3), -- BS30 multimedia
gBR33600BitsPerSecond (4), -- BS30 multimedia
gBR56000BitsPerSecond (5), -- BS30 transparent and multimedia
gBR57600BitsPerSecond (6), -- BS20 non-transparent
gBR64000BitsPerSecond (7) -- BS30 transparent and multimedia
}

GenericNumber ::= BCDDirectoryNumber

-- Structure of Generic Number
--
-- 1. Octet: TAG
-- 2. Octet: Length
-- Bit 4-2 reserved

GenericNumbers ::= SET OF GenericNumber

Gsm-SCFAddress ::= ISDN-AddressString
--
-- See TS 29.002
--
-- Structure of SCF-Address
--
-- 1. Octet: TAG
-- 2. Octet: Length
-- 4.- n. Octet: BCD-Digits (2 digits per Octet, odd digit ending
with F as filler as filler)

HLC ::= OCTET STRING

-- this parameter is a 1:1 copy of the contents
-- (i.e. starting with octet 3) of the high layer compatibility
-- parameter of ITU-T Q.931 [35].

HLRIntResult ::= Diagnostics

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


HSCSDParmsChange ::= SEQUENCE {
hSCSDChanAllocated [1] NumOfHSCSDChanAllocated,
initiatingParty [2] InitiatingParty OPTIONAL,
aiurRequested [3] AiurRequested OPTIONAL,
chanCodingUsed [4] ChannelCoding,
hSCSDChanRequested [5] NumOfHSCSDChanRequested OPTIONAL
}

IMEICheckEvent ::= INTEGER {
mobileOriginatedCall (0),
mobileTerminatedCall (1),
smsMobileOriginating (2),
smsMobileTerminating (3),
ssAction (4),
locationUpdate (5)
}

IMEIStatus ::= ENUMERATED {
greyListedMobileEquipment (0),
blackListedMobileEquipment (1),
nonWhiteListedMobileEquipment (2)
}

IMSIorIMEI ::= CHOICE {
imsi [0] IMSI,
imei [1] IMEI
}

InitiatingParty ::= ENUMERATED {
network (0),
subscriber (1)
}

ISDN-BC ::= OCTET STRING

-- (i.e. starting with octet 3) of the bearer capability

JurisdictionInformationParameter ::= OCTET STRING (SIZE (5))
--
-- /* JIP Parameter */
--

JurisdictionInformationParameterSourceIndicator ::= INTEGER
{ --
-- Identical to LocationRoutingNumberSourceIndicator
--
lRN-NP-Database (1),
switchingSystemData (2),
incomingsignaling (3),
unknown (9)
}

JurisdictionInformationParameterQueryStatus ::= INTEGER
{
successfulQuery (1),
noQueryResponseMsg (2),
queryProtocolErr (4),
queryResponseDataErr (5),
queryRejected (6),
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


queryNotPerformed (9),
queryUnsuccessful (99)
}

LCSCause ::= OCTET STRING (SIZE(1))
--
-- See LCS Cause Value, 3GPP TS 49.031
--

-- LCSClientIdentity ::= SEQUENCE {
-- lcsClientExternalID [0] LCSClientExternalID OPTIONAL,
-- lcsClientDialedByMS [1] AddressString OPTIONAL,
-- lcsClientInternalID [2] LCSClientInternalID OPTIONAL }

LCSQoSInfo ::= OCTET STRING (SIZE(4))
--
-- See LCS QoS IE, 3GPP TS 49.031
--

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


LevelOfCAMELService ::= BIT STRING
{
basic (0),
callDurationSupervision (1),
onlineCharging (2)
}

LLC ::= OCTET STRING

-- (i.e. starting with octet 3) of the low layer compatibility

LocationAreaAndCell ::= SEQUENCE
{
locationAreaCode [0] LocationAreaCode,
cellId [1] CellId
-- mCC-MNC [2] MCC-MNC OPTIONAL -R8
-- layout of LocationAreaAndCell
-- 1. Octet: TAG
-- 2. Octet: Length (8 Octets fixed)
-- 3. Octet: TAG of Area Code (H80)
-- 4. Octet: Length of Area Code (2 Octets fixed)
-- 5.+6. Octet: Area Code value
-- 7. Octet: TAG of CellId or SA
-- 8. Octet: Length of CellId/SA (2 Octets fixed)
-- 9.+10. Octet: CellId/SA value

}

LocationAreaCode ::= OCTET STRING (SIZE(2))
--
-- See TS 24.008
--

LocationChange ::= SEQUENCE
{
location [0] LocationAreaAndCell,
changeTime [1] TimeStamp
}

Location-info ::= SEQUENCE
{
mscNumber [1] MscNo OPTIONAL,
location-area [2] LocationAreaCode,
cell-identification [3] CellId OPTIONAL
}

LocUpdResult ::= Diagnostics

AlcatelManagedExtensions ::= SET OF AlcatelManagedExtension

MaximumBitRate ::= ENUMERATED
{
mBR14400BitsPerSecond (1), -- BS20 non-transparent
mBR28800BitsPerSecond (2), -- BS20 non-transparent and transparent,
-- BS30 transparent and multimedia
mBR32000BitsPerSecond (3), -- BS30 multimedia
mBR33600BitsPerSecond (4), -- BS30 multimedia
mBR56000BitsPerSecond (5), -- BS30 transparent and multimedia
mBR57600BitsPerSecond (6), -- BS20 non-transparent
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


mBR64000BitsPerSecond (7) -- BS30 transparent and multimedia
}

MCCMNC ::= GraphicString (SIZE(6))
--
-- This type contains the mobile country code (MCC) and the mobile
-- network code (MNC) of a PLMN.
--

MessageReference ::= OCTET STRING

Month ::= INTEGER (1..12)

MSCAddress ::= AddressString
-- Layout of MSC Address
--
-- 1. Octet: TAG
-- 2. Octet: Length
-- 3.-n. Octet: BCD-Digits (2 digits per Octet, odd digit ending with
F as filler)

MscNo ::= ISDN-AddressString
--
-- See TS 23.003
--
-- Structure of MSC Number
--
-- 1. Octet: TAG
-- 2. Octet: Length
with F as filler)

MSISDN ::= ISDN-AddressString
--
-- See TS 23.003
--
-- Layout of MSISDN
--
-- 1. Octet: TAG
-- 2. Octet: Length
F as filler)

MSPowerClasses ::= SET OF RFPowerCapability

NetworkCallReference ::= CallReferenceNumber
--
-- See TS 29.002
--

NetworkSpecificCode ::= INTEGER
--
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


-- To be defined by network operator
--

NetworkSpecificServices ::= SET OF NetworkSpecificCode

NumOfHSCSDChanRequested ::= INTEGER

NumOfHSCSDChanAllocated ::= INTEGER

ObservedIMEITicketEnable ::= BOOLEAN

OriginalCalledNumber ::= BCDDirectoryNumber

-- Structure of Original Called Number
--
-- 1. Octet: TAG
-- 2. Octet: Length
-- Bit 4-2 reserved
F as filler)

OriginDestCombinations ::= SET OF OriginDestCombination

OriginDestCombination ::= SEQUENCE
{
origin [0] INTEGER OPTIONAL,
destination [1] INTEGER OPTIONAL
--
-- Note that these values correspond to the contents
-- of the attributes originId and destinationId
-- respectively. At least one of the two must be present.
--
}

PartialRecordTimer ::= INTEGER

PartialRecordType ::= ENUMERATED
{
timeLimit (0),
serviceChange (1), -- not supported
locationChange (2), -- not supported
classmarkChange (3), -- not supported
aocParmChange (4), -- not supported
radioChannelChange (5), -- not supported
hSCSDParmChange (6), -- not supported
changeOfCAMELDestination (7), -- not supported
intraMSCHandoverInAnchor (8), -- not supported
basicInterMSCHandoverToMSCB (9), -- not supported
subsequentIntraMSCHandoverWithinTarget (10), -- not supported
subsequentInterMSCHandoverToMSCC (11), -- not supported
subsequentHandoverBackToAnchor (12) -- not supported
}

PartialRecordTypes ::= SET OF PartialRecordType

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


PositioningData ::= OCTET STRING (SIZE(1..33))
--
-- See Positioning Data IE (octet 3..n), 3GPP TS 49.031
--

RadioChannelsRequested ::= SET OF RadioChanRequested

RadioChanRequested ::= ENUMERATED
{
--
--
halfRateChannel (0),
fullRateChannel (1),
dualHalfRatePreferred (2),
dualFullRatePreferred (3)
}

RateIndication ::= OCTET STRING(SIZE(1))

RecordingEntity ::= AddressString

-- Layout of Recording Entity
--
-- 1. Octet: TAG
-- 2. Octet: Length
F as filler)

RecordingMethod ::= ENUMERATED
{
inCallRecord (0),
inSSRecord (1)
}

RedirectingNumber ::= BCDDirectoryNumber

-- Structure of Redirecting Number
--
-- 1. Octet: TAG
-- 2. Octet: Length
-- Bit 4-2 reserved
F as filler)

RFPowerCapability ::= INTEGER
--
-- This field contains the RF power capability of the
-- Mobile station
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


-- classmark 1 and 2 of TS 24.008 expressed as an integer.
--
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


RoamingNumber ::= ISDN-AddressString
--
-- See TS 23.003
--
-- Structure of Roaming Number
--
-- 1. Octet: TAG
-- 2. Octet: Length
with F as filler)

RoutingNumber ::= CHOICE
{
roaming [1] RoamingNumber,
forwarded [2] ForwardToNumber
}

Service ::= CHOICE
{
teleservice [1] TeleserviceCode,
bearerService [2] BearerServiceCode,
supplementaryService [3] SS-Code,
networkSpecificService [4] NetworkSpecificCode
}

ServiceDistanceDependencies ::= SET OF ServiceDistanceDependency

ServiceDistanceDependency ::= SEQUENCE
{
aocService [0] INTEGER,
chargingZone [1] INTEGER OPTIONAL
--
-- Note that these values correspond to the contents
-- of the attributes aocServiceId and zoneId
-- respectively.
--
}

SimpleIntegerName ::= INTEGER

SimpleStringName ::= GraphicString

SMSResult ::= Diagnostics

SmsTpDestinationNumber ::= OCTET STRING
--
-- This type contains the binary coded decimal representation of
-- the SMS address field the encoding of the octet string is in
-- accordance with the definition of address fields in TS 23.040.
-- This encoding includes type of number and numbering plan indication
-- together with the address value range.
--

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


SpeechVersionIdentifier ::= OCTET STRING (SIZE(1))
--
-- see GSM 08.08
--
-- 000 0001 GSM speech full rate version 1
-- 001 0001 GSM speech full rate version 2 used for enhanced full rate
-- 010 0001 GSM speech full rate version 3 for future use
-- 000 0101 GSM speech half rate version 1
-- 001 0101 GSM speech half rate version 2 for future use
-- 010 0101 GSM speech half rate version 3 for future use

SSActionResult ::= Diagnostics

SSActionType ::= ENUMERATED
{
registration (0),
erasure (1),
activation (2),
deactivation (3),
interrogation (4),
invocation (5),
passwordRegistration (6)
}

SSParameters ::= CHOICE
{
forwardedToNumber [0] ForwardToNumber,
unstructuredData [1] OCTET STRING
}

SupplServices ::= SET OF SS-Code

SuppServiceUsed ::= SEQUENCE
{
ssCode [0] SS-Code,
ssTime [1] TimeStamp OPTIONAL
}

SwitchoverTime ::= SEQUENCE
{
hour INTEGER (0..23),
minute INTEGER (0..59),
second INTEGER (0..59)
}

TariffId ::= INTEGER

TariffPeriod ::= SEQUENCE
{
switchoverTime [0] SwitchoverTime,
tariffId [1] INTEGER
--
-- Note that the value of tariffId corresponds
-- to the attribute tariffId.
--
}

TariffPeriods ::= SET OF TariffPeriod

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


TariffSystemStatus ::= ENUMERATED
{
available (0), -- available for modification
checked (1), -- frozen and checked
standby (2), -- frozen awaiting activation
active (3) -- frozen and active
}

TimeStamp ::= OCTET STRING (SIZE(6..9))
--
-- The contents of this field are a compact form of the UTCTime format
-- containing local time plus an offset to universal time. Binary coded
-- decimal encoding is employed for the digits to reduce the storage and
-- transmission overhead
-- The format of the timestamps is the following :
-- YYMMDDhhmmss2DHHMM
-- where
-- YY = Year 00 to 99 BCD encoded
-- MM = Month 01 to 12 BCD encoded
-- DD = Day 01 to 31 BCD encoded
-- hh = hour 00 to 23 BCD encoded
-- mm = minute 00 to 59 BCD encoded
-- ss = second 00 to 59 BCD encoded
-- 2D = Sign: 00 = unknown, +(H2B), -(H2D) ASCII encoded
-- HH = hour 00 to 23 BCD encoded
-- MM = minute 00 to 59 BCD encoded

-- For example: BeiJing local time is 2006-12-13 09:23:11.
-- The time stamp is encoded in CDR Record as following:
-- 0612130923112D0800
-- The time zone offset is 2D0800 = -8.
-- Local time 8H = GMT Time.And 2D=-; 2B=+

TrafficChannel ::= ENUMERATED
{
fullRate (0),
halfRate (1)
}

TranslatedNumber ::= BCDDirectoryNumber

-- Structure of translated Number
--
-- 1. Octet: TAG
-- 2. Octet: Length
-- 4. n. Octet: BCD-Digits (2 digits per Octet, odd digit ending with F
as filler)

TransparencyInd ::= ENUMERATED
{
transparent (0),
nonTransparent (1)
}

TrunkGroup ::= CHOICE
{
tkgpNumber [0] INTEGER,
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


tkgpName [1] GraphicString -RDS14844

-- Layout of TrunkGroup
-- 1. Octet: TAG
-- 2. Octet: Length
-- 3. Octet: Mode of Trunk-TAG
-- (H80 trunk Group Number, H81 Trunk Group Name)
-- 4.- n. Octet: Binary(Trunk Number) or String (Trunk Name)
}
-- Either 'trunk group number' or 'trunk group name' will be present
-- in the CDR.

TSChangeover ::= SEQUENCE
{
newActiveTS [0] INTEGER,
newStandbyTS [1] INTEGER,
changeoverTime [2] GeneralizedTime OPTIONAL,
authkey [3] OCTET STRING OPTIONAL,
checksum [4] OCTET STRING OPTIONAL,
versionNumber [5] OCTET STRING OPTIONAL
--
-- Note that if the changeover time is not
-- specified then the change is immediate.
--
}

TSCopyTariffSystem ::= SEQUENCE
{
oldTS [0] INTEGER,
ulti [1] INTEGER
}

TSNextChange ::= CHOICE
{
noChangeover [0] NULL,
tsChangeover [1] TSChangeover
}

TypeOfSubscribers ::= ENUMERATED
{
home (0), -- HPLMN subscribers
visiting (1), -- roaming subscribers
all (2)
}

TypeOfTransaction ::= ENUMERATED
{
successful (0),
unsuccessful (1),
all (2)
}

Visited-Location-info ::= SEQUENCE
{
mscNumber [1] MscNo,
vlrNumber [2] VlrNo
}

VlrNo ::= ISDN-AddressString
--
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


-- See TS 23.003
--
-- Structure of Vlr Number
--
-- 1. Octet: TAG
-- 2. Octet: Length
with F as filler)

-- definition out of ETS 300 196

BasicService ::= ENUMERATED
{
allServices (0),
speech (1),
unrestrictedDigitalInformation (2),
audio3k1Hz (3),
unrestrictedDigitalInformationWithTonesAndAnnouncements (4),
multirate (5),
telephony3k1Hz (32),
teletex (33),
telefaxGroup4Class1 (34),
videotexSyntaxBased (35),
videotelephony (36),
telefaxGroup2-3 (37),
telephony7kHz (38),
euroFileTransfer (39),
fileTransferAndAccessManagement(40),
videoconference (41),
audioGraphicConference (42),
...
}

-- definitions out of 29.002

BearerServiceCode ::= OCTET STRING (SIZE (1))
TeleserviceCode ::= OCTET STRING (SIZE (1))

BasicServiceCode ::= CHOICE
{
bearerService [2] BearerServiceCode,
teleservice [3] TeleserviceCode

-- layout of BasicServiceCode
-- 1. Octet: TAG
-- 2. Octet: Length (3 octets fixed)
-- 3. Octet: TAG of Basic Service Type
-- H82 Bearer Service, H83 Tele Service
-- 4. Octet: Length of Basic Service Type (1 octet fixed)
-- 5. Octet: Basic Service Code
}

DefaultSMS-Handling ::= ENUMERATED
{
continueTransaction (0) ,
releaseTransaction (1) ,
...}

CallReferenceNumber ::= OCTET STRING (SIZE (1..8))
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


DefaultCallHandling ::= ENUMERATED
{
continueCall (0) ,
releaseCall (1) ,
...}

-- LCSClientExternalID ::= SEQUENCE
-- {
-- externalAddress [0] AddressString OPTIONAL,
-- extensionContainer [1] ExtensionContainer OPTIONAL,
-- ... }

LCSClientInternalID ::= ENUMERATED
{
broadcastService (0),
o-andM-HPLMN (1),
o-andM-VPLMN (2),
anonymousLocation (3),
targetMSsubscribedService (4),
... }

NumberOfForwarding ::= INTEGER (1..5)

PositionMethodFailure-Diagnostic ::= ENUMERATED {
congestion (0),
insufficientResources (1),
insufficientMeasurementData (2),
inconsistentMeasurementData (3),
locationProcedureNotCompleted (4),
locationProcedureNotSupportedByTargetMS (5),
qoSNotAttainable (6),
positionMethodNotAvailableInNetwork (7),
positionMethodNotAvailableInLocationArea (8),
... }

ServiceKey ::= INTEGER (0..2147483647)

SS-Code ::= OCTET STRING (SIZE (1))
-- layout of a single SS-Code, if there is a list
-- there is a TAG/Length for the list in front of
-- 1. Octet: TAG
-- 2. Octet: Length
-- 3. Octet: Supplementary Service Code
-- values, see in SupplServiceCode-struct

UnauthorizedLCSClient-Diagnostic ::= ENUMERATED
{
noAdditionalInformation (0),
clientNotInMSPrivacyExceptionList (1),
callToClientNotSetup (2),
privacyOverrideNotApplicable (3),
disallowedByLocalRegulatoryRequirements (4),
...,
unauthorizedPrivacyClass (5),
unauthorizedCallSessionUnrelatedExternalClient (6),
unauthorizedCallSessionRelatedExternalClient (7)
}

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


SystemType ::= ENUMERATED
{
unknown (0),
iuUTRAN (1),
gERAN (2)
}


CalledPartyNumber ::= OCTET STRING (SIZE(1..16))

DestinationRoutingAddress ::= SEQUENCE SIZE(1) OF CalledPartyNumber
-- The Layout of Destination Routing Address
--
-- 1. Octet: TAG (DestRoutAddr)
-- 2. Octet: Length
-- 3. Octet: TAG (Seq-TAG CalledPartyNumber)
-- 4. Octet: Length (CalledPartyNumber)
F as filler)

IMEI ::= OCTET STRING ( SIZE(8) )
-- The Layout of IMEI
--
-- 1. Octet: TAG
-- 2. Octet: Length
F as filler)

IMSI ::= OCTET STRING ( SIZE(3..8) )
-- The Layout of IMSI
--
-- 1. Octet: TAG
-- 2. Octet: Length
F as filler)

maxAddressLength INTEGER ::= 20
maxISDN-AddressLength INTEGER ::= 9

AddressString ::= OCTET STRING (SIZE(1..maxAddressLength))
-- Layout, see below

ISDN-AddressString ::= OCTET STRING (SIZE(1..maxISDN-AddressLength))
-- The Layout of AddressString and ISDN-AddressString
--
-- 1. Octet: TAG
-- 2. Octet: Length
F as filler)

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


AlcatelManagedExtension ::= SEQUENCE {
identifier DMI-EXTENSION.&id({AlcatelManagedExtensionSet}),
significance[1] BOOLEAN DEFAULT FALSE,
information [2] DMI-
EXTENSION.&Value({AlcatelManagedExtensionSet}{@.identifier})

-- layout of AlcatelManagedExtensions
--
-- Example for MOC-extension:
--
-- layout of ManagedExtensions
--
-- TAG of the recordExtensions (its different for each kind of CDR type)
-- Length (total length of the recordExtensions)
-- TAG of Alcatel Managed Extension
-- (fixed value H30 means UNIVERSAL16 for SEQUENCE OF)
-- Length of Alcatel Managed Extension
-- TAG of xxx-ObjectId (xxx = e.g. Moc)
-- (its fixed value H06 meansUNIVERSAL6 for OBJECT IDENTIFY)
-- Length of xxx-ObjectId
-- xxx-ObjectId value
-- TAG of information of Extension (HA2)
-- Length of Information of Extension
-- TAG of Record Extension
-- (fixed value H31 means UNIVERSAL 17 for SET OF)
-- Length of Record Extension
-- Content of Record Extension
--
-- Example for MOC-extension:
--
-- Byte layout:
-- Bf 23 15
-- 30 13 06 09 2b 0c 02 87 6e 35 02 05 00
-- a2 06 31 04 80 01 01
--
-- Decoded Fields:
-- BF 23 is Tag of Record Extension of MOC record,
-- 15 is the length of Record Extension
-- 30 is Tag of Managed Extension
-- 13 is Length of Managed Extension
-- 06 is Tag of MOC Object ID, 09 is Length of MOC Object ID
-- 2b 0c 02 87 6e 35 02 05 00 is MOC Object ID Value
-- means MO_EXT => '1.3.12.2.1006.53.2.5.0'
-- why 1.3 will be encoded as 2B, because 1 means ISO, the beneath arc
will be encoded by arc number + 40T, so 3+40=43 i.e. 2B
-- why 1006 encoded as 876E, originally 1006 is 03EE i.e 0000 0011 1110
1110, divide the bit array to 7 bits each and take them as OCTET, then we can
get 0000 0111,0110 1110, that is 076E at last change the MSB is first OCTET
to 1 ,then we get 876E
-- a2 is Tag of information of Extension,
-- 06 is Length of information of Extension
-- 31 is Tag of Record Extension
-- 04 is Length of Record Extension
-- 80 is hotBillingSubscriber
-- 01 is the length of hotBillingSubscriber
-- 01 is the content of hotBillingSubscriber (=TRUE)

}
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


DMI-EXTENSION ::= DMI-TYPE-IDENTIFIER
DMI-TYPE-IDENTIFIER ::= CLASS {
&id OBJECT IDENTIFIER UNIQUE,
&Value
}WITH SYNTAX {TYPE &Value
ID &id
}

AlcatelManagedExtensionSet DMI-EXTENSION ::= {
mOCallRecordExtension |
mTCallRecordExtension |
rOAMRecordExtension | -- RDS6904
incGatewayRecordExtension |
outGatewayRecordExtension |
transitRecordExtension |
mOSMSRecordExtension |
mTSMSRecordExtension |
sSActionRecordExtension |
termCAMELRecordExtension|
...

}

mOCallRecordExtension DMI-EXTENSION::={TYPE MOCallRecordExtensionType
ID mOC-Extension-OID }
mTCallRecordExtension DMI-EXTENSION::={TYPE MTCallRecordExtensionType
ID mTC-Extension-OID }
incGatewayRecordExtension DMI-EXTENSION::={TYPE IncGatewayRecordExtensionType
ID incGateway-Extension-OID }
outGatewayRecordExtension DMI-EXTENSION::={TYPE OutGatewayRecordExtensionType
ID outGateway-Extension-OID }
transitRecordExtension DMI-EXTENSION ::={TYPE TransitRecordExtensionType
ID transit-Extension-OID }
mOSMSRecordExtension DMI-EXTENSION::={TYPE MOSMSRecordExtensionType
ID mOSMS-Extension-OID }
mTSMSRecordExtension DMI-EXTENSION::={TYPE MTSMSRecordExtensionType
ID mTSMS-Extension-OID }
sSActionRecordExtension DMI-EXTENSION::={TYPE SSActionRecordExtensionType
ID sSAction-Extension-OID }
termCAMELRecordExtension DMI-EXTENSION::={TYPE TermCAMELRecordExtensionType
ID termCAMEL-Extension-OID }
-- RDS6904 Start
rOAMRecordExtension DMI-EXTENSION::={TYPE RoamingRecordExtensionType
ID rOAM-Extension-OID }
-- RDS6904 End

hlrIntRecordExtension DMI-EXTENSION::={TYPE HLRINTRecordExtensionType
ID hLRInt-Extension-OID }
-- mTLCSRecordExtension DMI-EXTENSION::={TYPE MTLCSRecordExtensionType
-- ID mTLCS-Extension-OID }
-- mOLCSRecordExtension DMI-EXTENSION::={TYPE MOLCSRecordExtensionType
-- ID mOLCS-Extension-OID }
-- nILCSRecordExtension DMI-EXTENSION::={TYPE NILCSRecordExtensionType
-- ID niLCS-Extension-OID }

-----------------------------------------------------------------------------
-
--
-- NP Fields
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


--
-----------------------------------------------------------------------------
-
-- RDS9189 Start

LocationRoutingNumber ::= OCTET STRING (SIZE (5))

LocationRoutingNumberSourceIndicator ::= INTEGER
{
lRN-NP-Database (1),
switchingSystemData (2),
incomingsignaling (3),
unknown (9)
}

LocationRoutingNumberQueryStatus ::= INTEGER
{
successfulQuery (1),
noQueryResponseMsg (2),
queryProtocolErr (4),
queryResponseDataErr (5),
queryRejected (6),
queryNotPerformed (9),
queryUnsuccessful (99)
}

-- RDS9189 End

----------------------------------------------------------
-- private definitions

NumberingPlan-struct ::= ENUMERATED {
unknown (0),
iSDNtelephony (1),
data (3),
telex (4),
landMobile (6), -- WCS private extension
national (8),
private (9),
numberPlanInvalid (15),
...
}

NumberingType-struct ::= ENUMERATED {
unknown (0),
internationalNumber (1),
nationalNumber (2),
networkSpecificNumber (3),
subscriberNumber (4),
abbreviatedNumber (6),
numberTypeInvalid (7),
...
}

PresentationIndicator-struct ::= ENUMERATED {
presentationAllowed (0),
presentationRestricted (1),
addressNotAvailable (2), -- name in off. Spec:
-- Number not available due
-- to interworking
...
}
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


ScreeningIndicator-struct ::= ENUMERATED {
userProvidedNotScreened (0),
userProvidedVerifiedAndPassed (1),
userProvidedVerifiedAndFailed (2),
networkProvided (3),
...
}

ISDN-BC-struct ::= ENUMERATED {

allServices (0),
speech (1),
audio3k1Hz (3),
unrestrictedDigitalInformationWithTonesAndAnnouncements (4),
multirate (5),
teletex (33),
telefaxGroup2_3 (37),
telephony7kHz (38),
fileTransferAndAccessManagement (40),
audioGraphicConference (42)
}

SupplServiceCode-struct ::= ENUMERATED {
allSS (0), -- not used
allLineIdentificationSS (16), -- not used
callingLineIdpresent (17),
callingLineIdrestricted (18),
connectedLineIdpresent (19),
connectedLineIdrestricted (20),
maliciousCallIdentifaction (21),
allNameIdentificationSS (24),
callingNamePresentation (25),
allCallForwarding (32),
callfwdunconditional (33),
callDeflection (36), -- 3GPP definition
allConditionalCallFwd (40),
callFwdOnSubscrBusy (41),
callFwdOnNoReply (42),
callFwdOnNotReachable (43),
allCallOfferingSS (48),
explicitCallTransfer (49),
mobileAccessHunting (50),
allCallCompletionSS (64),
callWaiting (65),
callHold (66),
completionOfCallsToBusySubscriberOrig (67),
completionOfCallsToBusySubscriberDest (68),
multicall (69),
allMultiPartySS (80),
multiparty (81),
allCommunityOfInterest-SS (96),
cug (97),
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


allChargingSS (112),
adviceOfChargeInform (113),
adviceOfChargeCharging (114),
allAdditionalInfoTransferSS (128),
userToUserSignallingService1 (129),
allCallBarring (144),
barringOfOutgoingCalls (145),
barringOfAllOutgoingCalls (146),
barringOfAllOutIntCalls (147),
barringOfAllOutgIntExHPLMN (148),
barringOfIncomingCalls1 (153),
barringOfAllIncomingCalls (154),
barringOfAllIncCallsRoaming (155),
priorityCallInStateOfDisaster (160), -- WCS private extension
emlpp (161),
allLCSPrivacyException (176),
universal (177),
callSessionRelated (178),
callSessionUnrelated (179),
plmnoperator (180),
serviceType (181),
allMOLR-SS (192),
basicSelfLocation (193),
autonomousSelfLocation (194),
transferToThirdParty (195),
delayedHotLine (224), -- WCS private extension
callDeflectionWCS (225), -- WCS private extension
hotBilling (241), -- WCS private redefinition
mrbt (253), -- WCS private extension
prbt (254), -- WCS private extension
...
}

MOSMSResult-struct ::= ENUMERATED {
rpmoUNASSIGNEDNUMBER (1),
rpmoOPERATORDETERMINEDBARRING (8),
rpmoCALLBARRED (10),
rpmoRESERVED (11),
rpmoSHORTMESSAGETRANSFERREJECTED (21),
rpmoDESTINATIONOUTOFORDER (27),
rpmoUNIDENTIFIEDSUBSCRIBER (28),
rpmoFACILITYREJECTED (29),
rpmoUNKNOWNSUBSCRIBER (30),
rpmoNETWORKOUTOFORDER (38),
rpmoTEMPORARYFAILURE (41),
rpmoCONGESTION (42),
rpmoRESOURCEUNAVAILABLEUNSPECIFIED (47),
rpmoREQUESTEDFACILITYNOTSUBSCRIBED (50),
rpmoREQUESTEDFACILITYNOTIMPLEMENTED (69),
rpmoINVALIDSHORTMESSAGETRANSFERREFERENCEVALUE (81),
rpmoSEMANTICALLYINCORRECTMESSAGE (95),
rpmoINVALIDMANDATORYINFORMATION (96),
rpmoMESSAGETYPENONEXISTENDNOTIMPLEMENTED (97),
rpmoMESSAGENOTCOMPITABLEWITHSMPROTOCOLSTATE (98),
rpmoINFORMATIONELEMENTNONEXISTENDNOTIMPLEMENTED (99),
rpmoPROTOCOLERRORUNSPECIFIED (111),
rpmoINTERWORKINGUNSPECIFIED (127),
...
}

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


MTSMSResult-struct ::= ENUMERATED {
rpmtMEMORYCAPACITYEXCEED (22),
rpmtINVALIDSHORTMESSAGETRANSFERREFERENCEVALUE (81),
rpmtSEMANTICALLYINCORRECTMESSAGE (95),
rpmtINVALIDMANDATORYINFORMATION (96),
rpmtMESSAGETYPENONEXISTENDNOTIMPLEMENTED (97),
rpmtMESSAGENOTCOMPITABLEWITHSMPROTOCOLSTATE (98),
rpmtINFORMATIONELEMENTNONEXISTENDNOTIMPLEMENTED (99),
rpmtPROTOCOLERRORUNSPECIFIED (111),
...
}

CISSResult-struct ::= ENUMERATED {
ssresultSUCCESS (1),
ssresultFAILURE (2),
ssresultRETURNERROR (3),
ssresultPROVIDERERROR (4),
ssresultREJECTERROR (5),
ssresultINVALID (255),
...
}

--- -------------------------------------------------------
-- definitions for not implemented parameters
-- RDS9851 Start

CarrierNumber ::= OCTET STRING
-- same format as IE Transit Network Selection defined in Q.763 contains
-- the Type of Network Identification, the Network Identification plan
-- and the Carrier Identification Digits

DisconnectingParty ::= ENUMERATED
{
invalidParty (0),
originationSideInitiated (1),
terminationSideInitiated (2),
networkInitiated (3)
}

NationalIndicator ::= ENUMERATED
{
nationalCall (0),
internationalCall (1)
}

OperatorIndicator ::= ENUMERATED
{
normalCall (0),
operatorCall (1)
}

OptimalRouteingType ::= ENUMERATED
{
basic (0),
earlyCF (1),
lateCF (2)
}

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


OptimalRouteingNumber ::= SEQUENCE
{
optimalRouteingType [0] OptimalRouteingType,
destinationNumber [1] BCDDirectoryNumber
-- nbr used by GMSC to route call with OR
}

PortabilityProcessInvoked ::= ENUMERATED
{
signalingRelay (1),
qoHR (2),
tQoD (3),
oQoD (4)
}

PortabilityStatus ::= ENUMERATED
{
unknown (0),
ownNumberPortedOut (1),
foreignNumberPortedToForeignNetwork (2),
portedIn (3)
}

TimeExtensions ::= SEQUENCE
{
callDurationms [0] INTEGER OPTIONAL, -- in steps of 100ms
seizureTimems [1] INTEGER OPTIONAL, -- in steps of 10ms
answerTimems [2] INTEGER OPTIONAL, -- in steps of 10ms
releaseTime [3] INTEGER OPTIONAL -- in steps of 10ms
}

NumberPortabilityInformation ::= SEQUENCE
{
portabilityProcessInvoked [0] PortabilityProcessInvoked,
portabilityStatus [1] PortabilityStatus,
locationRoutingNumber [2] BCDDirectoryNumber
}

-- RDS9851 End

SubscribedOSSSCodes ::= OCTET STRING (SIZE (1))
-- layout of a single OSSS CODES RDS14064

END

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


6 OPTIONS
6.1 Options dynamically modifiable

The options listed below can be configured on the WEM GUI.

MOC-CF Records Generated (Y/N): If set to N, no MOC-CF records are generated. If set to Y, MOC-
CF records are generated. Default is Y.

MTC Forwarding Records Generated (Y/N): If set to N, no MTC records are generated for forwarded
calls (on either GMSC or VMSC). If set to Y, such MTC records are generated
on VMSC, and are eligible to be generated on GMSC depending on the value of MTC Records on
Gateway MSC below. Default is Y.

Important: The next 2 Options have been deleted by PR5925 on the WEM.
If available on WEM, please dont modify it !

MTC Records on Gateway MSC (Y/N): If set to N, no MTC records (for call forwarding) shall be
generated on a pure GMSC (i.e. one which is not also serving as a VMSC for the
call), even if MTC Forwarding Records Generated is set to Y. If set to Y, such MTC records
are generated. Please note that this parameter will not be allowed to be set to Y if
MTC Forwarding Records Generated is N. Default is N. ( Deleted by
PR5925 )

Billing on Visited MSC for Late Call Forwarding Cases (Y/N): If set to N, no records will be
generated on the visited MSC for late call forwarding cases where Optimal Routing applies (and
the forwarding is thus done on the GMSC). If set to Y, such records are generated.
Default is N. ( Deleted by PR5925 )

Roaming Records Generated (Y/N) (Option name: 3GPP_ROAM_CDR / on WEM: Roaming):
If set to N, no ROAM records are generated. If set to Y, ROAM records are generated. Default is Y.
(RDS6904)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Incoming Gateway Call Attempt Records Generated (Y/N): If set to N, no IC-GMSC records are
generated. If set to Y, IC-GMSC records are generated. Default is Y.

Outgoing Gateway Call Attempt Records Generated (Y/N): If set to N, no OG-GMSC records are
generated. If set to Y, OG-GMSC records are generated. Default is Y.

Transit Call Attempt Records Generated (Y/N): If set to N, no Transit records are generated. If set to
Y, Transit records are generated. Default is Y.

SS actions Records Generated (Y/N): If set to N, no SS actions records are generated. If set to Y, SS
actions records are generated. Default is Y.

HLR interrogation Records Generated (Y/N)(Option name: 3GPP_HLRInt_CDR / on WEM: HLR-Int):
If set to N, no HLR interrogation records are generated. If set to Y, HLR interrogation records are
generated. Default is Y. (RDS6904)

Terminating CAMEL Records Generated (Y/N): If set to N, no T-CAMEL records are generated. If set
to Y, T-CAMEL records are generated. Default is N.

Short Message Service Records Generated (Y/N): If set to N, no SMS-MO or SMS-MT records are
generated. If set to Y, such records are generated. Default is Y.
After RDS16380a, Original SMS flag should split to successful SMS and unsuccessful SMS flags.
There are 4 kinds of selections:
successful SMS unsuccessful SMS CDR generation
Y Y Both successful and unsuccessful SMS CDR are generated.
Y N Only successful SMS CDR is generated.
N Y Only unsuccessful SMS CDR is generated.
N N Neither successful nor unsuccessful SMS CDR is generated.
Default is successful SMS =Y and unsuccessful SMS =N

Billing of Unanswered Calls (Y/N): If set to N, no records of any type will be generated for calls that are
not answered (i.e. have no Answer Time). This includes T-CAMEL records (if active) for calls that were
not answered (even though T-CAMEL has no Answer Time in the record per se). If set to Y, such records
will be generated. Default is N.

Partial Records Enabled (Y/N): If set to N, no partial records (of any type) will be generated for long-
duration calls. If set to Y, partial records will be generated. Default shall be N.

Generation of MOC records for user interaction with external IP (Y/N): If set to Y, records are
generated for the connection of an external IP by a CAMEL/IN service. Default is N.

Call duration rounding method (up/truncate/closest) : this option indicates how must be rounded the
call duration. When the option is up, the duration is rounded to the next superior integer. When the
option is truncate, the duration is rounded to the next inferior integer. When the duration is closest, the
duration is rounded to the closest integer. A 0.5 second is rounded up. The exception is that when the
result of the rounding should normally be 0, then the value 1 is used instead. Default is closest.

Examples :
Call duration Up Truncate closest
0.4 1 1 1
3.0 3 3 3
3.1 4 3 3
3.5 4 3 4
3.9 4 3 4

Add area code in the calling party for incoming PSTN calls (Y/N): (Option Name: OverrideInCDR )
(RDS7502b, flag used by Cpcallm)
If set to Y, the calling party number Parameter in the CDR includes the area code in front of the number.
If set to N, the calling party number Parameter is remaining unchanged.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Default is N.
6.2 Options statically modifiable

The options listed below can only be modified by Alcatel. They are not configurable on the GUI.

ISDN Basic Service Generation (Y/N): (Option name: 3GPP_ISDN_BS) (RDS6904)
If this option is set, the IE has to be formatted in case of having valid data, otherwise kept out of the CDR.
Default is N.

ISDN Bearer Capability Generation (Y/N): (Option name: 3GPP_ISDN_BC) (RDS6904)
Default is N.

Low Layer Compatibility Generation (Y/N): (Option name: 3GPP_LLC) (RDS6904)
Default is N.

High Layer Compatibility Generation (Y/N): (Option name: 3GPP_HLC) (RDS6904)
Default is N.

Full SmsTpDestinationNumber Generation (Y/N): (Option name: 3GPP_FULL_SMS_DESTNUM)
(PR5307) (D42927)
If set to Y, the Destination number of SMS-MO record in the CDR includes
Nature of Address
Numbering Plan
E.164 MS number
If set to N, only E.164 MS number is contained.
Default is N.

Support of IMEI in CF-records (Y/N): (Option name: 3GPP_SUPP_IMEI_IN_CF_RECORD)
RDS8184 / D46475
If set to Y, the IMEI has to be formatted into all CF-records (MOC-CF, MTC-CF) in case of having valid
data, otherwise kept out of the CDR. If set to N, the IMEI is not contained in MOC-/MTC-CF.
Default is N.

Support of Location info in CF-records (Y/N): (Option name: 3GPP_SUPP_LOC_IN_CF_RECORD)
RDS8184 / D46475
If set to Y, the LOCATION IE has to be formatted into all CF-records (MOC-CF, MTC-CF) in case of
having valid data, otherwise kept out of the CDR. If set to N, the LOCATION is not contained in MOC-
/MTC-CF.
Default is N.

Support of Basic Service in Incoming/Outgoing Gateway CDR (Y/N): RDS9365
(Option name: 3GPP_BS_INC_OUTG_GTWY)
If set to Y, the Basic service has to be formatted into the incoming/outgoing gateway Record in case of
having valid data, otherwise kept out of the CDR.
If set to N, the Basic service is not contained in incoming/outgoing gateway Record.
Default is N.

Support of MSC Inc/Outgoing TKGP Extension in all CDRs (Y/N): RDS9851
(Option name: 3GPP_MSC_INC_OUTG_TKGP_EXT)
If set to Y, the trunk group extension parameters have to be formatted into all kind of Records in case of
having valid data, otherwise kept out of the CDR.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


If set to N, these parameters are not contained in the Records.
Default is N.
CDR Field
M
O
C

M
O
C

E
M
Y

M
O
C

F
W

M
T
C

M
T
C

F
W

I
C

G
M
S
C

O
G
-
G
M
S
C

T
R
A
N
S
I
T

T
-
C
A
M
E
L

S
S

S
M
S

M
O

S
M
S

M
T

MSC incoming trunk
group extension x x x x x x X x x
MSC outgoing trunk
group extension x x x x x x x x x
New CAMEL fields in incoming gateway CDR and transit CDR for N-CSI (Y/N): RDS7564a/RDS6034
(Option name: 3GPP_CAMEL_N-CSI )
If set to Y, all new CAMEL fields defined in incoming gate way CDR and transit CDR for N-CSI are
included. If set to N, suppress all new CAMEL fields defined in incoming gate way CDR and transit CDR
for N-CSI.
Default is N.
Below are impacted CDR fields.
- gsm-SCFAddress,
- serviceKey,
- defaultCallHandling,
- freeFormatData,
- cAMELCallLegInformation,
- networkCallReference

Full Recording Entity Generation (Y/N): (Option name: 3GPP_FULL_REC_ENT) (RDS7564a)
If set to Y, the Recording Entity Parameter in the CDR includes
- Nature of Address
- Numbering Plan
- E.164 MSC number
If set to N, only E.164 MSC number is contained.
Default is N.

Additional Charge info (Y/N): (Option name: 3GPP_ADD_CHG_INF_CHARGE) (RDS7564a)
If set to Y, the additional charging info Parameter in the MTC-CDR is created and includes hardcoded
the value CHARGE.
If set to N, the additional charging info Parameter will not be created for MTC-CDR.
Default is N.

Support of LRN parameters (Y/N): (Option name: 3GPP_SUPP_LRN_PARMS) (RDS9189)
If set to Y, the LRN Parameters () will be formatted into all call releated Records in case of having valid
data, otherwise kept out of the CDR.
Default is N.

CDR Field
M
O
C

M
O
C

E
M
Y

M
O
C

F
W

M
T
C

M
T
C

F
W

I
C

G
M
S
C

O
G
-
G
M
S
C

T
R
A
N
S
I
T

T
-
C
A
M
E
L

S
S

S
M
S

M
O

S
M
S

M
T

Location Routing
Number x

x x

x x x x
LRN Source Indicator
x

x x

x x x x
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


CDR Field
M
O
C

M
O
C

E
M
Y

M
O
C

F
W

M
T
C

M
T
C

F
W

I
C

G
M
S
C

O
G
-
G
M
S
C

T
R
A
N
S
I
T

T
-
C
A
M
E
L

S
S

S
M
S

M
O

S
M
S

M
T

LRN Query Status
Indicator x

x x

x x x x

Full MSC-Address Generation (Y/N): (Option name: 3GPP_FULL_MSC_ADDRESS)
(PR D48317 and D48179)
If set to Y, the MSC Address Parameter in the CDR includes
- Nature of Address / Numbering Type
- Numbering Plan
- E.164 MSC number
If set to N, only E.164 MSC number is contained.
Default is N.

System type Generation (Y/N): (Option name: 3GPP_SYSTEM_TYPE) (PR D55218)
If this option is set Y, the system type has to be formatted in related CDR types as mandatory field.
If this option is set N, the system type should not to be formatted in related CDR types.
Default is Y.

Fill CUG in MOC and MOC FW CDR (Y/N): (Option name: 3GPP_CUG_MOC_MOCFW_CDR)
(RDS9804b)
If set to Y, the CUG Parameters will be formatted into MOC and MOC FW Records in case of having
valid data, otherwise kept out of the CDR.
If set to N, CUG parameters are not contained in the MOC and MOC FW Records.
Default is N.

Fill CUG in MTC and MTC FW CDR (Y/N): (Option name: 3GPP_CUG_MTC_MTCFW_CDR)
(RDS9804b)
If set to Y, the CUG Parameters will be formatted into MTC and MTC FW Records in case of having
valid data, otherwise kept out of the CDR.
If set to N, CUG parameters are not contained in the MTC and MTC FW Records.
Default is N.

DISABLE SMS MT CDR FOR DELIVERY NOTIFICATION (Y/N): (Option name: DisStatusSmsCdr)
(RDS12458)
If set to Y, Disable SMSMT CDR in case of delivery notification to calling party
If set to N, Enable SMSMT CDR in case of delivery notification to calling party.
Default is N.
Note: before implement RD12458, WCS enable SMSMT CDR in case of delivery notification to calling
party.

Support Subscribed OSSS Codes (Y/N):
(Option name: 3GPP_SUBSCRIBED_OSSS_CODES ) (RDS14064)
If set to Y, the Subscribed OSSS Codes parameters have to be formatted into the applicable CDR
record types, in case of having valid data, otherwise kept out of the CDR.
Default is N.

Support tkgpName (Y/N):
(Option name: 3GPP_TKGP_NAME) (RDS14844)
If set to Y, the TrunkGroup will be recorded by tkgpName format.
If set to N, TrunkGroup will be recorded by tkgpNumber format.
Default is N.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Record the IAM called number in OutgoingIAMcallednumber CDR Field (Y/N):
(Option name: 3GPP_OUTGOINGIAMCALLEDNUMBER) (RDS16253)
If this option is set Y, the OutgoingIAMcallednumber has to be formatted into the outgoing gateway
CDR, in case of having valid data, otherwise kept out of the CDR.
If this option is set N, the Routing number is not contained in outgoing gateway CDR.
Default is N.

Record 1st received MSRN in roaming number CDR Field for 3GPP MOC CDR (Y/N):
(Option name: 3GPP_FIRST_MSRN_ROAMINGNUMBER) (RDS16318)
If this option is set Y, then record 1st received MSRN from SRI_ACK in roaming number CDR Field for
3GPP MOC CDR and cant be overwrite. For example: If there is no MSRN in the 1st SRI_ACK, then
record MSRN from 2nd SRI_ACK if data available. Once available MSRN is received from SRI_ACK,
then its forbidden overwrite 1st received MSRN in CDR.
If this option is set N, then fill roaming number CDR field for MOC CDR as before.
Default is N.

Force to use gsm0408Cause for Diagnostic (Y/N):
(Option name: 3GPP_GSM0408_DIAGNOSTIC_TYPE) (PR85393)
If set to Y, always use gsm0408Cause[0] for Diagnostic
If set to N, work as normal. Use manufacturerSpecificCause[4] for Diagnostic
Default is N.

Generate unsuccessful SMS CDR (Y/N):
(Option name: ENABLE_UNSUCCESSFUL_SMS_CDR) (RDS16380)
If this option is set Y, the CDR for unsuccessful SMS shall be generated and written to normal billing file.
If this option is set N, the CDR for unsuccessful SMS shall not be generated and written to normal billing
file.
Default is N.
Note: this flag is only used in R5.0 FF, after RDS16380a this flag is removed to WEM and become
dynamic option.

Support flexible value for closest method the call duration in CDR (range: 001-999):
(Option name: 3GPP_CDR_value_for_closest) (RDS16308)
If the call duration fractional part is less than the value, then the method rounds to 0 second, if the
fractional part is equal or more than the value, then round to 1 second.
Default is 500
For example:
If the value of '3GPP_CDR_value_for_closest_method' is 100ms. Then 5.101 sec would be considered
as 6 sec
Note:
For short duration call, This RDS should affect call duration in CDR.
For long duration call, more than one CDR are generated. This RDS only affect the last
CDR for long call. First and intermediate CDR duration should follow PR79087 solution and not
affected by this RDS.
If customer set wrong value out of 001-999 scope, WCS should use default value 500.

6.3 summary on CDR difference between R4.x and R3.x

1. Black color means the changes has control flag. BS may ignore them.
2. Blue color means the change depend on the feature.
3. Red color means BS need to confirm their decode software already support it.

Control flag description default
1. Adjust the head of
RecordingEntity field
It solved 3GPP compatibility
problem. We strongly recommend
OFF
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


(3GPP_FULL_REC_ENT) customer BS to support it.
Control flag is available.

2. Add AdditionalChgInfo
field in MTC CDR
(3GPP_ADD_CHG_INF_CHARGE)
It solved CMCC specification
compatibility problem. CMCC WCS has
to enable it.
OFF
3. Fixed tag value in Gsm
SCF Address 2 fileds in TCAMEL
CDR (Binary;Fixed Value
40735(H9F 1F))
It solved one internal ASN.1 encode
error. Although there is no service
will trigger Gsm SCF Address-2
fields in TCAMEL CDR, but we still
recommend customer modify BSS decode
software.
Note: If customer has no plan to
implement service trigger Gsm SCF
Address-2 fields, BS may ignore
this error.
Always
on, no
control
flag.
4. Addbasic servicefield in
incoming/outgoing gateway CDR.
(3GPP_BS_INC_OUTG_GTWY)
It solved CMCC and CU specification
compatibility problem. CMCC and CU
WCS has to enable it.

OFF
5. Add
Synchronous_GeneralData = 0x1F
in basic service code field
Only 3G service will trigger this
new value, We strongly recommend
customer to BS to support it.

Always
on, no
control
flag.
6. Add Msc Incoming TKGP
Extension and Msc Outgoing TKGP
Extension field
(3GPP_MSC_INC_OUTG_TKGP_EXT)

OFF
7. Add three new fields for LRN
function.
(3GPP_SUPP_LRN_PARMS)
customer BS to support it.
No control flag exist.
Note: These three new fields will be
present in CDR only when LRN
function is enabled.
OFF
8. Add IMEI and LOCATION
field in MOC CF CDR
(3GPP_SUPP_IMEI_IN_CF_RECORD)
(3GPP_SUPP_LOC_IN_CF_RECORD)

OFF
8. Add CAMEL related fields in
incoming gateway CDR and
Transit CDR
(3GPP_CAMEL_N-CSI)

OFF
10. Add more CAMEL
information in
CAMELSMSInformation field in
SMS MO CDR
This CDR fields are already defined
in SMS MO CDR in R3.4, although they
are not generated really. But R4.4
WCS will generate them. we recommend
customer BS to confirm support them.
Always
on, no
control
flag.
11. Add ISDN- Bearer capability
field in incoming/outgoing
gateway CDR
3GPP_ISDN_BC
It solved CMCC and CU specification
compatibility problem. CMCC and CU
WCS has to enable it.
OFF
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


12. Add LLN field in
incoming/outgoing gateway CDR
3GPP_LLC

OFF
13. Add HLC field in
incoming/outgoing gateway CDR
3GPP_HLC

OFF
14. Add IsdnBasicService
field in incoming/outgoing
gateway CDR3GPP_ISDN_BS

OFF
15. Adjust the head of
SmsTpDestinationNumber field
3GPP_FULL_SMS_DESTNUM

OFF
16. Adjust the head of MSC
Address field
(3GPP_FULL_MSC_ADDRESS

OFF
17. Add connected number field
in MTC CDR
These CDR fields are already defined
in SMS MO CDR in R3.4, although they
are not generated really. But R4.4
WCS will generate them. we recommend
customer BS to confirm support them.
Always
on, no
control
flag.
18. store OSSS code in 3GPP CDR
for OSSS based routing.
(3GPP_SUBSCRIBED_OSSS_CODES)
(RDS14064)
Its Unitech requirement

OFF
19. Fill CUG in MOC and MOC FW
CDR
(3GPP_CUG_MOC_MOCFW_CDR)
(RDS9804)
MTNL WCS other other market need it
has to enable it.
OFF
20. Support store different translated
number (before Outpulsed or after
Outpulsed) in CDR
(RDS5680)
Normal use the default value for all
market.
OFF

6.4 summary on CDR difference between R5.x and R4.x

1. Black color means the changes has control flag. BS may ignore them.
2. Blue color means the change depend on the feature.
3. Red color means BS need to confirm their decode software already support it.

Control flag description default Release
1. Fill CUG in MOC and
MOC FW CDR
(3GPP_CUG_MOC_MOCF
W_CDR)
(RDS9804b)
Its Global, MNTL, BSNL,
Unitech requirement.
OFF W5.0
2. Fill CUG in MTC and MTC
FW CDR
(3GPP_CUG_MTC_MTCFW
_CDR) (RDS9804b)
Its Global, MNTL, BSNL,
Unitech requirement.
OFF W5.0
3. DISABLE SMS MT CDR
FOR DELIVERY
TIGO and Mobinil Egypt have
to enable it.
OFF W5.0 SP6
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


NOTIFICATION
(DisStatusSmsCdr)
(RDS12458)
4. Support of SIP with
Encapsulated ISUP (SIP-I),
add SIP-I in
TrunkGroupType of
TrunkGroupExtension.
(RDS6029)
Only MGCF service will
trigger this new value.

Always on, no
control flag.
W5.0SP6
5. Record 1st received
MSRN in roaming number
CDR Field for 3GPP MOC
CDR
(3GPP_FIRST_MSRN_ROA
MINGNUMBER)
(RDS16318)
Its GO MALTAs requirement.
(for MNP CDR)
OFF W5.0 SP6
6. Generate special MOC
with ECT ss-code for call re-
origination. (RDS14086)
Its Unitech requirement
Control flag is
available.(controled by
feature flag)

OFF W5.0SP7
7. Support tkgpName in
TrunkGroup for 3GPP CDR
(3GPP_TKGP_NAME)
(RDS14844)
Its Uninor & BSNL (India)
requirement.
OFF W5.0SP7
8. Support Generate
unsuccessful SMS CDR
(ENABLE_UNSUCCESSFU
L_SMS_CDR) (RDS16380)
Its Vodafone Qatars
requirement

OFF W5.0FF
9. tag value of
subscribedOSSSCodes in
MTCallRecordExtension is
changed from [16] to [17]
(RDS14064a)
Its MNTL, BSNL, Unitech
requirement.
If customer use OSSSCode CDR
field in R449, then customer
has to modify their CDR
decode software.
If customer doesnt use
OSSSCode CDR field in R449,
then customer may ignore it.
No control option
for the tag change.
But OSSS code CDR
field has control
option to suppress
whole OSSS code CDR
field in CDR. See
point 1 and 2 in
this table.
W5.0 SP7
10. Force to use
gsm0408Cause for
Diagnostic
(3GPP_GSM0408_DIAGNO
STIC_TYPE) (PR85393)
Enabled only when customer
insist to use gsm0408 as
Diagnostic type.
OFF W5.1
11. Add
OutgoingIAMcallednumber
to record the called number
from outgoing IAM message
CDR Field in Outgoing
gateway CDR
(3GPP_OUTGOINGIAMCAL
LEDNUMBER) (RDS16253)
Its TELNETs requirement. (for
MNP CDR)
OFF W5.1 FF

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


A EXAMPLE OF MOBILE ORIGINATED CALL CDR
Binary encoding of a Mobile Originated call CDR :
00000000: a081 b380 0100 8108 6400 1260 0000 10f1
00000010: 8208 6400 7794 0097 8000 8308 9168 3109
00000020: 7100 10f1 8505 8163 5054 1186 05a1 6350
00000030: 5411 8906 6831 0910 00f1 aa04 8002 04b0
00000040: ab03 8001 01ac 0880 0200 0181 0200 01ae
00000050: 0383 0111 8f01 0194 0320 0081 960a 0511
00000060: 2518 2652 2d08 0000 970a 0511 2518 2658
00000070: 2d08 0000 980a 0511 2518 2718 2d08 0000
00000080: 9901 149c 0100 9e01 00bf 1f03 8001 109f
00000090: 2004 0400 002c bf23 1530 1306 092b 0c02
000000a0: 876e 3502 0500 a206 3104 8902 080d 9f32
000000b0: 0101 9f3d 0102

The grayed octets show the level 1 tags. The underlined tags show the tags at level > 1. The octet following
a grayed or underlined tag contain the length of the field.

The same Mobile Originated Call CDR, decoded :
value CallEventRecord ::= moCallRecord :
{ recordType moCallRecord,
servedIMSI 64001260000010F1H,
servedIMEI 6400779400978000H,
servedMSISDN 91683109710010F1H,
calledNumber 8163505411H,
translatedNumber A163505411H,
recordingEntity 916831091000F1H,
mscIncomingTKGP tkgpNumber : 1200,
mscOutgoingTKGP tkgpNumber : 1,
location
{
locationAreaCode 0001H,
cellId 0001H
},
basicService teleservice : 11H,
transparencyIndicator nonTransparent,
msClassmark 200081H,
seizureTime 0511251826522D080000H,
answerTime 0511251826582D080000H,
releaseTime 0511251827182D080000H,
callDuration 20,
radioChanUsed fullRate,
causeForTerm normalRelease,
diagnostics manufacturerSpecificCause: 16,
callReference 67108908,
recordExtensions
{
{ identifier { 1 3 12 2 1006 53 2 5 0 },
information MOCallRecordExtensionType :
{ bSCIdOfFirstBSC 2061
}
}
},
speechVersionUsed 01H,
systemType gERAN
}
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


B 5060 WCS 3GPP CDR FIELD FLAG DESCRIPTION

MOC Call Record(include Forwarding Call Record)
Header
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value
160(HA0)
2 2 1 Reserved Length of packages
length(n).
Binary;The Length of
Packages length.
3 3 n Package Length Binary;Total Length of
package
Note: If the Second byte < 0x81,the second byte is the real length of the package. And the 3th
byte will be suppressed.
For example:
A0 79: The length of the package is 0x79
A0 81 B2:The length of the package is 0xB2

MOC Call Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 128(H
80)
2 2 1 Package Length Binary;Fixed Value 1(H
01)
3 3 1 Value of Call Type Binary;Fixed Vaue 0(H
00)
Served IMSI
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
81)
2 2 1 Package Length (n) Binary
3 3 n Digit(i+1) Digit(i) Packed Digits
Digit(i): i is incremented every next byte as follows:i=1,3,2n-1 and Digits is
encoded by TBCD with end of F
Served IMEI
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
82)
Served MSISDN
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


131(H83)
3 3 1 Reserved NOA NPI Binary;NOA and NPI
refer to description
4 4 n-1 Digit(i+1) Digit(i) Packed Digits
Calling Number
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed
Value 132(H
84)
3 3 1 Reserved NOA NPI Binary;NOA and
NPI refer to
description
4 4 1 Reserved PRI Reserved SI Binary;PRI and
SI refer to
description
Called Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
133(H85)
Translated Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
134(H86)
Connected Number(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
Value 135(H
87)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


NPI refer to
description
SI refer to
description
Roaming Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
136(H88)
Recording Entity
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
137(H89)
Incoming Trunk Group
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AA)
3 3 1 Mode of Trunk Binary;Fixed Value 128(H
80):Trunk Group
Number;129(h81):Trunk
Group Name
4 4 1 Length of Trunk Binary;Length of Trunk
Group Number or Name
5 5 n-2 Trunk Group Value Binary(Trunk Number) or
String(Trunk Name)
Outgoing Trunk Group
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AB)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


80):Trunk Group
Group Name
String(Trunk Name)
Location
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AC)
08)
3 3 1 Tag of Area Code Binary;Fixed Value 128(H
80):Area Code Tag
4 4 1 Length of Area Code Binary;Fixed value 2(H
02):The length of Area
Code
5 5 2 Area Code Value Binary;Area Code Value
6 7 1 Tag of Cell Id Binary;Fixed Value 129(H
81):Cell Id Tag
7 8 1 Length of Cell Id Binary;Fixed value 2(H
02):The length of Cell
Id
8 9 2 Cell Id Value Binary;Cell Id Value
Change Of Location
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AD)
3 3 1 Tag Of NO i Location
Information
Binary;Fixed Value 48(H
30)
4 4 1 Length of NO. i Location
Information
Binary;Length of NO i
Location Information
5 5 1 Tag of AreaAndCell Binary;Fixed Value 160(H
A0)
6 6 1 Length of AreaAndCell Binary;Fixed Value 8(H
08)
80):Area Code Tag
Code
81):Cell Id Tag
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Id
13 15 1 Tag of Location Change Time
Stamp
81)
14 16 1 Length of Location Change
Time Stamp
Binary;Fixed Value 9(H 9(H 9(H 9(H
09) 09) 09) 09)
15 17 10 Location Change Time Stamp Refer to Time Stamp
Description
16 27 1 Tag Of NO i+1 Location
Information
30)
17 28 1 Length of NO. i+1 Location
Information
Binary;Length of NO i+1
A0)
08)
80):Area Code Tag
Code
81):Cell Id Tag
Id
Stamp
81)
27 40 1 Length of Location Change
Time Stamp
09) 09) 09) 09)
Description
Max number of location change is 7.If exceed 7,the last location will be update each
time.
Basic Service
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AE)
03)
3 3 1 Tag of Basic Service Type Binary;130(H82):Bear
Service;131(H83):Tele
Service
4 4 1 Length of Basic Service Code Binary;Fixed Value 1(H
01)
5 5 1 Basic Service Code Binary;Refer to Basic
Service Code Description
Transparency Indicator
Field Byte Length(Bytes) Field Name Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


NO. Pos 7 6 5 4 3 2 1 0
1 1 1 Package Number Binary;Fixed Value 143(H8F)
2 2 1 Package Length Binary;Fixed Value 1(H01)
3 3 1 Transparency Indicator
Value
Binary;0(H00):transparent;1(H
01):non Transparent
Supplementary Services Used
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
B1)
3 3 1 First SS code Binary:Refer Supp
Service Description
4 4 1 Second SS code Binary:Refer Supp
Service Description

Max number of supp services is 11.
Ms Class Mark
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
94)
2 2 1 Package Length(n) Binary
3 3 n Ms Class Mark Value Binary;
Seizure Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
96)
2 2 1 Package Length Binary;Fixed Value 9(H 9(H 9(H 9(H
09) 09) 09) 09)
3 3 10 Seizure Time Stamp Refer to Time Stamp
Description
Answer Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
97)
09) 09) 09) 09)
3 3 10 Answer Time Stamp Refer to Time Stamp
Description
Release Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
98)
09) 09) 09) 09)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


3 3 10 Release Time Stamp Refer to Time Stamp
Description
Call Duration
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
99)
2 2 1 Package Length(n) Binary;
3 3 n Call Duration Binary;Total duration by
seconds
Radio Channel Used
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
9C)
01)
3 3 1 Radio Channel Used Binary;0(H00):Full
Rate;
1(H01):Half Rate
Cause For Termination
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
9E)
2 2 1 Package Length(n) Binary;Length of the
value
3 3 n Cause For Termination Binary;Refer to
CauseForTermination
Description
Diagnostics Value
Field Name Field
NO.
Byte Pos Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
BF 1F)
2 2 1 Package Length(n) Binary;Length of
Diagnostics Information
3 3 1 Tag of Diagnostics Type Binary;Fixed Value 128(H
80 Gsm0408Cause)
or
84
manufacturerSpecificCause)
4 4 1 Length of Cause value(M) Binary;
5 5 M Cause Value Binary;
WCS can control the Diagnostics Type (Gsm0408Cause or manufacturerSpecificCause) by
3GPP_GSM0408_DIAGNOSTIC_TYPE.
Call Reference
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


40736(H9F 20)
value
3 3 n Call Reference Binary;
Sequence Number of Partial Record
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40737(H9F 21)
value
3 3 n Sequence Number of Partial
Record
Binary;
Additional Chg Information
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 48930(HBF
22)
3 3 1 Tag of Additional Chg
Type
Binary;Fixed Value 128(H80)
4 4 1 Length of Additional
Chg Value
5 5 1 Additional Chg Value Binary;0(H00):noCharge;1(H
01):Charge

Record Extension
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 35(HBF 23)
3 3 1 Tag of Alcatel Managed
Extension
4 4 1 Length of Alcatel
Managed Extension(m)
Binary;
5 5 1 Tag of CDR TYPE Object
ID
6 6 1 Length of CDR TYPE
Object ID
7 7 9 CDR TYPE Object ID
Value
Fixed Value (H
8 16 1 Tag of information of
Extension
Binary;Fixed Value 162(HA2)
9 17 1 Length of information
of Extension(k)
Binary;
10 18 1 Tag of Record Extension Binary;Fixed Value 49(H31)
11 19 1 Length of Record
Extension(j)
Binary;
12 20 J The Content of Record
Extension
Refer to the Content of MOC
Record Extension
Only when the content of record extension is not empty,the extension will occur.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Content of MOC Record Extension
Hot Billing Subscriber
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 128(H80)
3 3 1 Hot Billing Flag Binary;0(H00):False;1(H
FF):True;Only when true,it is
present
Ip Connection
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 Ip Connection Flag Binary;0(H00):False;1(H
present
RNCid of First RNC
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 n RNCid of First RNC Binary;
Ms Category
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 Ms Category Binary;
Cs ARP
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 Cs ARP Binary;
CUG Inter Lock
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 4 CUG Inter Lock Binary;
CUG Index
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 n CUG Index Binary;
CUG Outgoing Access Suppressed
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


3 3 1 CUG Outgoing Access
Used
Binary;0(H00):False;1(H
present
CUG Outgoing Access Indicator
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Indicator
present
BSCid of First BSC
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 N BSCid of First BSC Binary;
Multi Media Call
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 138(H8A)
3 3 1 Multi Media Call Binary;0(H00):False;1(H
FF):True;Default False, True
means multimedia call
Inter Connect Facility(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 171(HAB)
3 3 1 Tag of Interconnect
Group Number
4 4 1 Length of Interconnect
Group Number
5 5 2 Value of Interconnect
Group Number
Binary;
Type
Type
Type
Binary; isupTrunkGroup = 1,
casTrunkGroup = 4,
biccTrunkGroup = 9,
bssTrunkGroup = 11
Msc Incoming TKGP Extension
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 172(HAC)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


3 3 1 Tag of Trunk Group
Type
4 4 1 Length of Trunk
Group Type
5 5 1 Value of Trunk
Group Type
Binary;
6 6 1 Tag of Interface
Type
7 7 1 Length of Interface
Type
8 8 1 Value of Interface
Type
Binary;

9 9 1 Tag of MGW number Binary;Fixed Value 130(H82)
10 10 1 Length of MGW
Number(n)
Binary;
11 11 n Value of MGW Number Binary;
12 11+n 1 Tag of Trunk
Circuit
13 11+n+1 1 Length of Trunk
Circuit(m)
14 11+n+1+1 m Value of Trunk
Circuit
Binary;
Msc Outgoing TKGP Extension
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 173(HAD)
Type
Group Type
Group Type
Binary;
Type
Type
Type
Binary;
Number(n)
Binary;
Circuit
Circuit(m)
Circuit
Binary;
Subscribed OSSS Codes
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


1 1 1 Package Number Binary;Fixed Value 142(H8E)
3 3 1 Subscribed OSSS Codes
(1)
Binary;
(2)
Binary;
(3)
Binary;
6 6 1 ... Binary;
(i)
Binary;

Gsm SCF Address
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40740(H9F 24)
3 3 1 Reserved NOA NPI Binary;NOA and NPI refer
to description
Service Key
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40741(H9F 25)
value
3 3 n Service Key Binary;
Network Call Reference
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40742(H9F 26)
value
3 3 n Network Call Reference Binary;
MSC Address
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40743(H9F 27)
value
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Camel Init CF Indicator
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40744(H9F 28)
01)
3 3 1 Camel Init CF Indicator Binary;0(H00) no
CF;1(H01):CF
Default Call Handling
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40745(H9F 29)
01)
3 3 1 Default Call Handling Binary;0(H00):Continue
Call;1(H01):Release
Call
FNUR
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 40752(H9F 2D)
3 3 1 Fnur Binary;
fnur9600-BitsPerSecond:1(H' 01)
fnur14400BitsPerSecond:2(H' 02)
fnur32000BitsPerSecond:10(H' 0A)
fnur31200BitsPerSecond:11(H' 0B)

Channel Coding Used
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 40752(H9F 30)
3 3 1 Channel Coding Used Binary;1(H01):tchF4800 ;2(H
02):tchF9600;
3(H03):tchF14400
Speech Version Used
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 32)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


01)
3 3 1 Speech Version Used Binary;
Number of DP Encountered
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40755(H9F 33)
3 3 n Number of DP Encountered Binary;
Level of Camel Service
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 40756(H9F
34)
3 3 1 Level of Camel Service Binary;128(H50 50 50 50 80):
LevelOfCAMELService_basic;64(H
50 50 50 50 40):
callDurationSupervision;32(H 50 50 50 50
20): onlineCharging
Note: H50 means last 5 "0" of next byte is not used.
Free Format Data
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40757(H9F 35)
3 3 n Free Format Data Hex String
Record Free Format Data of O_CSI(First Service) and Party to Charge=1
Camel Leg Information
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
48950(HBF 36)
3 3 1 Tag of NO i Camel Leg
Information
31)
4 4 1 Length of NO i Camel Leg
Information(m)
Binary;
5 5 M Content of NO i Camel Leg
Information
Refer to Camel Leg
Information
6 5+m 1 Tag of NO i+1 Camel Leg
Information
31)
7 5+m+1 1 Length of NO i+1 Camel Leg
Information(m)
Binary;
8 5+m+2 K Content of NO i+1 Camel Leg
Information
Refer to Camel Leg
Information
Content of Camel Leg Information
Camel Destination Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


A1)
3 3 1 Tag of Destination Number Binary;Fixed Value 4(H
04)
4 4 1 Length of Destination
Number(m)
Binary;
5 5 M Reserved NOA NPI Binary;NOA and NPI refer
to description
4 4 m-1 Digit(i+1) Digit(i) Packed Digits
Connected Number(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
82)
to description
Roaming Number(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
83)
to description
Msc Outgoing Trunk Group(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A4)
80):Trunk Group
Group Name
String(Trunk Name)
Seizure Time Stamp(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


85)
09) 09) 09) 09)
Description
Answer Time Stamp(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
86)
09) 09) 09) 09)
Description
Release Time Stamp(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
87)
09) 09) 09) 09)
Description
Call Duration(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
88)
3 3 N Call Duration Binary;Total duration by
seconds
Data Volume(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
89)
3 3 N Data Volume Binary
Camel Init CF Indicator
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8A)
01)
3 3 1 Camel Init CF Indicator Binary;0(H00) no
CF;1(H01):CF
Cause For Termination(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


8B)
value
3 3 N Cause For Termination Binary;Refer to
CauseForTermination
Description
Camel Modification
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AC)
value
3 3 1 Tag of modification change
list
80)
4 4 1 Length of modification change
list
02)
5 5 1
6 6 1 Modification change list value Bit map;Refer to
modification bit map
7 5+m 1 Tag of modification content Binary;Fixed Value 161(H
A1)
8 5+m+1 1 Length of modification
content(k)
Binary;
9 5+m+2 k Modification Content Refer to modification
content
Camel Modification Bit Map
Field Name Field
NO.
Byte
Pos
Length
(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Calling
Party
Number
Modified
Calling
Party
Category
Modified
Original
Called
Party
Number
Modified
Generic
Numbers
Modified
Redirecting
Party
Number
Modified
Redirection
Counter
Modified

If the bit value is 1,it means the parameter corresponding to the bit is modified.The value
of the parameter can be found in the modification content.
Modification Content
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8B)
value
3 3 N Cause For Termination Binary;Refer to
CauseForTermination
Description
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Modification Content
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
Value 128(H
80)
NPI refer to
description
SI refer to
description
Calling Party Category(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
Value 129(H
81)
2 2 1 Package Length Binary;Fixed
Value 1(H01)
3 3 1 Calling Party Category Modified Value Binary
Original Called Party Number(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
Value 130(H
82)
NPI refer to
description
SI refer to
description
Generic Numbers
Field Byte Length(Bytes Field Name Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


NO. Pos ) 7 6 5 4 3 2 1 0
Value 131(H
83)
3 3 1 Tag of Generic Number Binary;Fixed
Value 4(H04)
4 4 1 Length of Generic Number(m) Binary
NPI refer to
description
SI refer to
description
Redirecting Party Number(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
Value 132(H
84)
NPI refer to
description
SI refer to
description
Redirection Counter(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
Value 133(H
85)
2 2 1 Package Length (n) Binary;
3 3 n Redirection Counter Binary;
Free Format Data
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8D)
Record Free Format Data of O_CSI or T_CSI(First Service) and Party to Charge=2
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Diagnostics Value(not implemented)
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
AE)
80 Gsm0408Cause)
or
84
Free Format Data Append(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8F)
01)
3 3 1 Free Format Data Append Binary;0(H00):Over
Write;1(H01):Append
Free Format Data-2
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
90)
3 3 n Free Format Data-2 Hex String
Record Free Format Data of D_CSI or N_CSI(Second Service) and Party to Charge=2
Free Format Data Append-2(not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
91)
01)
3 3 1 Free Format Data Append-2 Binary;0(H00):Over
Write;1(H01):Append
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40764(H9F 37)
01)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Write;1(H01):Append
Default Call Handling-2
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40760(H9F 38)
01)
Call;1(H01):Release
Call
Gsm SCF Address-2
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40761(H9F 39)
to description
Service Key-2
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40762(H9F 3A)
value
3 3 N Service Key Binary;
Free Format Data-2
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40763(H9F 3B)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40764(H9F 3C)
01)
Write;1(H01):Append
System Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 40765(H9F 3D)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


3 3 1 System Type Binary;0(H00):UnKnown;1(H01):3G;2(H
02):2G
Rate Indication
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 3E)
01)
3 3 1 Rate Indication Binary;

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 3F)
05)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 40)
01)
3 3 1 LRN Source Indicator Binary;

LRN Query Status Indicator
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 41)
01)
3 3 1 LRN Query Status Indicator Binary;

Partial Record Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40773(H9F 45)
01)
3 3 1 Partial Record Type See Comments
timeLimit = 0,
serviceChange = 1,(not supported)
locationChange = 2, (not supported)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


classmarkChange = 3, (not supported)
aocParmChange = 4, (not supported)
radioChannelChange = 5, (not supported)
hSCSDParmChange = 6, (not supported)
changeOfCAMELDestination = 7, (not supported)
intraMSCHandoverInAnchor = 8, (not supported)
basicInterMSCHandoverToMSCB = 9, (not supported)
subsequentIntraMSCHandoverWithinTarget = 10, (not supported)
subsequentInterMSCHandoverToMSCC = 11, (not supported)
subsequentHandoverBackToAnchor = 12(not supported)
Guaranteed Bit Rate
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
46)
3 3 1 Guaranteed Bit Rate Binary;
14.4 kbit/s:1(H' 01)
28.8 kbit/s:2(H' 02)
32.0 kbit/s:3(H' 03)
33.6 kbit/s:4(H' 04)
56.0 kbit/s:5(H' 05)
57.6 kbit/s:6(H' 06)
64.0 kbit/s:7(H' 07)

Maximum Bit Rate
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
47)
3 3 1 Maximum Bit Rate Binary;
14.4 kbit/s:1(H' 01)
28.8 kbit/s:2(H' 02)
32.0 kbit/s:3(H' 03)
33.6 kbit/s:4(H' 04)
56.0 kbit/s:5(H' 05)
57.6 kbit/s:6(H' 06)
64.0 kbit/s:7(H' 07)

MTC Call Record
Header
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
161(HA1)
length(n)
Packages length
package
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


For example:

MTC Call Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
80)
01)
01)
Served IMSI
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
81)
Served IMEI
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
82)
Served MSISDN
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
83)
to description
Calling Number
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
Value 132(H
84)
NPI refer to
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


description
SI refer to
description
Connected Number
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
Value 133(H
85)
NPI refer to
description
SI refer to
description
Recording Entity
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
134(H86)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A7)
80):Trunk Group
Group Name
String(Trunk Name)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


A8)
80):Trunk Group
Group Name
String(Trunk Name)
Location
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A9)
08)
80):Area Code Tag
Code
81):Cell Id Tag
Id
Change Of Location
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AA)
3 3 1 Tag Of NO i Location
Information
30)
4 4 1 Length of NO. i Location
Information
Binary;Length of NO i
A0)
08)
80):Area Code Tag
Code
81):Cell Id Tag
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Id
Stamp
81)
14 16 1 Length of Location Change Time
Stamp
09) 09) 09) 09)
Description
16 27 1 Tag Of NO i+1 Location
Information
30)
17 28 1 Length of NO. i+1 Location
Information
Binary;Length of NO i+1
A0)
08)
80):Area Code Tag
Code
81):Cell Id Tag
Id
Stamp
81)
27 40 1 Length of Location Change Time
Stamp
09) 09) 09) 09)
Description
Max number of location change is 7.If exceed 7,the last location will be update each
time.
Basic Service
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AB)
03)
Service
01)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


NO. Pos 7 6 5 4 3 2 1 0
1 1 1 Package Number Binary;Fixed Value 140(H8C)
3 3 1 Transparency Indicator
Value
Binary;0(H00):transparent;1(H
01):non Transparent
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AE)
Service Description
Service Description

Ms Class Mark
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
91)
Seizure Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
93)
09) 09) 09) 09)
Description
Answer Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
94)
09) 09) 09) 09)
Description
Release Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
95)
09) 09) 09) 09)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Description
Call Duration
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
96)
seconds
Radio Channel Used
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
99)
01)
3 3 1 Radio Channel Used Binary;0(H00):Full
Rate;
1(H01):Half Rate
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
9B)
value
CauseForTermination
Description
Diagnostics Value
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
BC)
80 Gsm0408Cause)
or
84
Call Reference
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


9D)
value
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
9E)
value
Record
Binary;
Additional Chg Info
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1F)
Type
Chg Value
01):Charge

Record Extension
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Extension
Binary;
ID
Object ID
Value
Fixed Value (H
Extension
of Extension(k)
Binary;
Extension(j)
Binary;
Extension
Refer to the Content of MTC Record
Extension
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40742(H9F 21)
value
MSC Address
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40743(H9F 22)
value
FNUR
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 Fnur Binary;
fnur9600-BitsPerSecond:1(H' 01)
fnur32000BitsPerSecond:10(H' 0A)
fnur31200BitsPerSecond:11(H' 0B)

Channel Code Used
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 Channel Coding Used Binary;1(H01):tchF4800 ;2(H
02):tchF9600;
3(H03):tchF14400

Speech Version Used
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 2B)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


01)
3 3 1 Speech Version Used Binary;

System Type R5
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
2F)
3 3 1 System Type Binary;0(H00):UnKnown;1(H
01):3G;2(H02):2G

Rate Indication
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 2F)
01)
3 3 1 Rate Indication Binary;

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 30)
05)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 31)
01)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 32)
01)

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Partial Record Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40773(H9F 36)
01)
timeLimit = 0,

Guaranteed Bit Rate
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
37)
3 3 1 Guaranteed Bit Rate Binary;
14.4 kbit/s:1(H' 01)
28.8 kbit/s:2(H' 02)
32.0 kbit/s:3(H' 03)
33.6 kbit/s:4(H' 04)
56.0 kbit/s:5(H' 05)
57.6 kbit/s:6(H' 06)
64.0 kbit/s:7(H' 07)

Maximum Bit Rate
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
38)
3 3 1 Maximum Bit Rate Binary;
14.4 kbit/s:1(H' 01)
28.8 kbit/s:2(H' 02)
32.0 kbit/s:3(H' 03)
33.6 kbit/s:4(H' 04)
56.0 kbit/s:5(H' 05)
57.6 kbit/s:6(H' 06)
64.0 kbit/s:7(H' 07)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


System Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3D)
3 3 1 System Type Binary;0(H00):UnKnown;1(H
01):3G;2(H02):2G

Content of MTC Record Extension
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
present
Gsm SCF Address (O_CSI Data)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
81)
to description
Service Key (O_CSI Data)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
82)
value
Redirecting Counter
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 n Redirecting Counter Binary; It occurs only when >0.
RNCid of First RNC
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Ms Category
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 Ms Category Binary;
Cs ARP
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 Cs ARP Binary;
CUG Inter Lock
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 4 CUG Inter Lock Binary;
CUG Index
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 n CUG Index Binary;
CUG Incoming Access Used
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Used
present
BSCid of First BSC
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 N BSCid of First BSC Binary;
Multi Media Call
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 139(H8B)
3 3 1 Multi Media Call Binary;0(H00):False;1(H
FF):True;Default False, True
means multimedia call
Redirecting Number
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Value 140(H
8C)
NPI refer to
description
SI refer to
description
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 173(HAD)
Group Number
Group Number
Group Number
Binary;
Type
Type
Type
casTrunkGroup = 4,
biccTrunkGroup = 9,
bssTrunkGroup = 11
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 174(HAE)
Type
Group Type
Group Type
Binary;
Type
Type
Type
Binary;
Number(n)
Binary;
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Circuit
Circuit(m)
Circuit
Binary;
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 175(HAF)
Type
Group Type
Group Type
Binary;
Type
Type
Type
Binary;
Number(n)
Binary;
Circuit
Circuit(m)
Circuit
Binary;
CUG Outgoing Access Indicator
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Used
present
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
(1)
Binary;
(2)
Binary;
(3)
Binary;
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


6 6 1 ... Binary;
(i)
Binary;

TCAMEL Call Record
Header
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
176(HB0)
length(n)
Packages length
package
For example:
B0 79: The length of the package is 0x79
B0 81 B2:The length of the package is 0xB2

TCAMEL Call Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
80)
01)
11)
Served IMSI
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
81)
Served MSISDN
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
82)
to description
Recording Entity
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


NO. Pos 7 6 5 4 3 2 1 0
131(H83)
Interrogation Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
84)
09) 09) 09) 09)
3 3 10 Interrogation Time Stamp Refer to Time Stamp
Description
Destination Routing Address
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A5)
3 3 1 Tag of Destination Number Binary;Fixed Value 4(H
04)
4 4 1 Length of Destination
Number(m)
Binary;
to description
6 6 m-1 Digit(i+1) Digit(i) Packed Digits
Digit(i): i is incremented every next byte as follows:i=1,3,2m-3 and Digits is
Gsm SCF Address
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
86)
to description
Service Key
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
87)
value
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
88)
value
MSC Address
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
89)
value
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8A)
01)
Call;1(H01):Release
Call
Record Extension (not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Extension
Binary;
5 5 1 Tag of MOC Object ID Binary;Fixed Value 6(H06)
6 6 1 Length of MOC Object ID Binary;Fixed Value 9(H09)
7 7 9 MOC Object ID Value Fixed Value (H
Extension
of Extension(k)
Binary;
Extension(j)
Binary;
Extension
Refer to the Content of Tcamel
Record Extension
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Content of Tcamel Record Extension (not implemented)
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 160(HA0)
Type
Group Type
Group Type
Binary;
Type
Type
Type
Binary;
Number(n)
Binary;
Circuit
Circuit(m)
Circuit
Binary;
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
Type
Group Type
Group Type
Binary;
Type
Type
Type
Binary;
Number(n)
Binary;
Circuit
13 11+n+1 1 Length of Trunk Binary;Fixed Value 1(H01)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Circuit(m)
Circuit
Binary;
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
(1)
Binary;
(2)
Binary;
(3)
Binary;
6 6 1 ... Binary;
(i)
Binary;

Called Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8C)
to description
Calling Number
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
Value 141(H
8D)
NPI refer to
description
SI refer to
description
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AE)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


80):Trunk Group
Group Name
String(Trunk Name)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AF)
80):Trunk Group
Group Name
String(Trunk Name)
Seizure Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
90)
09) 09) 09) 09)
Description
Answer Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
91)
09) 09) 09) 09)
Description
Release Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
92)
09) 09) 09) 09)
Description
Call Duration
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


NO. Pos 7 6 5 4 3 2 1 0
93)
seconds
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
95)
value
CauseForTermination
Description
Diagnostics Value
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
B6)
80 Gsm0408Cause)
or
84
Call Reference
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
97)
value

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
98)
value
Record
Binary;
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Number of DP Encountered
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
99)
3 3 n Number of DP Encountered Binary;
Level of Camel Service
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 Level of Camel Service Binary;128(H50 50 50 50 80):
LevelOfCAMELService_basic;64(H
50 50 50 50 40):
callDurationSupervision;32(H 50 50 50 50
20): onlineCharging
Note: H50 means last 5 "0" of next byte is not used.
Free Format Data
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
9B)
Record Free Format Data of T_CSI(First Service) and Party to Charge=1
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
BC)
Information
31)
Information(m)
Binary;
Information
Refer to Camel Leg
Information
Information
31)
Information(m)
Binary;
Information
Refer to Camel Leg
Information
Content of Camel Leg Information(refer to 1.1.45)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40764(H9D)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


01)
Write;1(H01):Append
Default Call Handling-2
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
9E)
01)
Call;1(H01):Release
Call
Gsm SCF Address-2
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40735(H9F 1F)
to description
Service Key-2
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40736(H9F 20)
value
Free Format Data-2
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40737(H9F 21)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40764(H9F 22)
01)
Write;1(H01):Append
MSC Server Indication(not implemented)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


NO. Pos 7 6 5 4 3 2 1 0
40738(H9F 23)
01)
3 3 1 MSC Server Indication Binary;

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 24)
05)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 25)
01)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 26)
01)

Incoming Gateway Record
Header
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
163(HA3)
length(n)
Packages length
package
For example:
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


IncGateway Call Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
80)
01)
03)
Calling Number
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
Value 129(H
81)
NPI refer to
description
SI refer to
description
Called Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
82)
to description
Recording Entity
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
131(H83)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


A4)
80):Trunk Group
Group Name
String(Trunk Name)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A5)
80):Trunk Group
Group Name
String(Trunk Name)
Seizure Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
86)
09) 09) 09) 09)
Description
Answer Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
87)
09) 09) 09) 09)
Description
Release Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
88)
09) 09) 09) 09)
Description
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Call Duration
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
89)
seconds
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8B)
value
CauseForTermination
Description
Diagnostics Value
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
AC)
80 Gsm0408Cause)
or
84
Call Reference
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8D)
value
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8E)
value
3 3 n Sequence Number of Partial Binary;
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Record
Record Extension
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Extension
Binary;
ID
Object ID
Value
Fixed Value (H
Extension
of Extension(k)
Binary;
Extension(j)
Binary;
Extension
Refer to the Content of INC_GW
Record Extension
Content of IncGateway Record Extension
Roaming Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
128(H80)

Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
Type
Group Type
Group Type
Binary;
Type
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Type
Type
Binary;
Number(n)
Binary;
Circuit
Circuit(m)
Circuit
Binary;
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
Type
Group Type
Group Type
Binary;
Type
Type
Type
Binary;
Number(n)
Binary;
Circuit
Circuit(m)
Circuit
Binary;

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Group Number
Group Number
5 5 2 Value of Interconnect Binary;
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Group Number
Type
Type
Type
casTrunkGroup = 4,
biccTrunkGroup = 9,
bssTrunkGroup = 11

Gsm SCF Address
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40740(H84)
to description

Service Key
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40741(H85)
value

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40745(H86)
01)
Call;1(H01):Release
Call

Free Format Data
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40757(H87)

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
48950(HA8)
Information
31)
Information(m)
Binary;
Information
Refer to Camel Leg
Information
Information
31)
Information(m)
Binary;
Information
Refer to Camel Leg
Information

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40742(H89)
value

IsdnBasicService
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
2 2 1 Package Length(n) Binary;Length of the value
3 3 n ISDN Basic Service Binary;
allServices (0),
speech (1),
audio3k1Hz (3),

unrestrictedDigitalInformationWithTonesAndAnnouncements
(4),
multirate (5),
teletex (33),
telephony7kHz (38),
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.



Basic Service
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AB)
03)
Service
01)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H8F)
05)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 11)
01)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H 9F 12)
01)

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


ISDN- Bearer capability
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 17)
2 2 1 Package Length Binary;
3 3 1 ISDN-Bearer capability Binary;
LLC
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 18)
3 3 1 LLC Binary
HLC
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 19)
3 3 1 HLC Binary

Outgoing Gateway Record
Header
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
164(HA4)
length(n)
Packages length
package
For example:

OutGateway Call Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
80)
01)
04)
Calling Number
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Value 129(H
81)
NPI refer to
description
SI refer to
description
Called Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
82)
to description
Recording Entity
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
131(H83)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A4)
80):Trunk Group
Group Name
String(Trunk Name)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


A5)
80):Trunk Group
Group Name
String(Trunk Name)
Seizure Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
86)
09) 09) 09) 09)
Description
Answer Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
87)
09) 09) 09) 09)
Description
Release Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
88)
09) 09) 09) 09)
Description
Call Duration
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
89)
seconds
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8B)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


value
CauseForTermination
Description
Diagnostics Value
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
AC)
3 3 1 Tag of Diagnostics
Type(Gsm0408Cause)
80):Gsm0408Cause
4 4 1 Length of Gsm0408Cause
value(m)
Binary;
5 5 M Gsm0408Cause Value Binary;
Call Reference
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8D)
value
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8E)
value
Record
Binary;
Record Extension
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Extension
Binary;
ID
Object ID
Value
Fixed Value (H
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Extension
of Extension(k)
Binary;
Extension(j)
Binary;
Extension
Refer to the Content of MOC Record
Extension
Content of OutGateway Record Extension
Roaming Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
128(H80)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Group Number
Group Number
Group Number
Binary;
Type
Type
Type
casTrunkGroup = 4,
biccTrunkGroup = 9,
bssTrunkGroup = 11

Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
Type
Group Type
5 5 1 Value of Trunk Binary;
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Group Type
Type
Type
Type
Binary;
Number(n)
Binary;
Circuit
Circuit(m)
Circuit
Binary;
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
Type
Group Type
Group Type
casTrunkGroup = 4,
biccTrunkGroup = 9,
bssTrunkGroup = 11
Type
Type
Type
Binary;
InterfaceType_unknown =
0,
tdm_T1 = 1,
aal2 = 3,
voip = 5,
tdm_E1 = 15
Number(n)
Binary;
Circuit
Circuit(m)
Circuit
Binary;
ISDN-Bearer capability
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


NO. Pos 7 6 5 4 3 2 1 0
84)
3 3 10 ISDN-Bearer capability Binary;
LLC
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H85)
3 3 1 LLC Binary
HLC
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H86)
3 3 1 HLC Binary
IsdnBasicService
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
2 2 1 Package Length(n) Binary;Length of the value
3 3 n ISDN Basic Service Binary;
allServices (0),
speech (1),
audio3k1Hz (3),

unrestrictedDigitalInformationWithTonesAndAnnouncements
(4),
multirate (5),
teletex (33),
telephony7kHz (38),

Basic Service
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A8)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


03)
Service
01)
OutgoingIAMcallednumber (RDS16253)
Field Name Remarks Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
133(H89)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H8F)
05)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 11)
01)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 12)
01)

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Transit Call Record
Header
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
165(HA5)
length(n)
Packages length
package
For example:

Transit Call Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
80)
01)
05)
Recording Entity
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
129(H81)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A2)
80):Trunk Group
Group Name
String(Trunk Name)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A3)
80):Trunk Group
Group Name
String(Trunk Name)
Calling Number
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
Value 132(H
84)
NPI refer to
description
SI refer to
description
Called Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
85)
to description
ISDN Basic Service
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
86)
01)
3 3 10 ISDN Basic Service Refer to
ISDNBasicService
Description
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Seizure Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
87)
09) 09) 09) 09)
Description
Answer Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
88)
09) 09) 09) 09)
Description
Release Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
89)
09) 09) 09) 09)
Description
Call Duration
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8A)
seconds
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8C)
value
CauseForTermination
Description
Diagnostics Value
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
AD)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Type(Gsm0408Cause)
80):Gsm0408Cause
value(m)
Binary;
Call Reference
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8E)
value
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8F)
value
3 3 N Sequence Number of Partial
Record
Binary;
Record Extension
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 176(HB0)
Extension
Binary;
ID
Object ID
Value
Fixed Value (H
Extension
of Extension(k)
Binary;
Extension(j)
Binary;
Extension
Refer to the Content of Transit
Record Extension
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Content of Transit Record Extension
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
Type
Group Type
Group Type
Binary;
Type
Type
Type
Binary;
Number(n)
Binary;
Circuit
Circuit(m)
Circuit
Binary;
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
Type
Group Type
Group Type
casTrunkGroup = 4,
biccTrunkGroup = 9,
bssTrunkGroup = 11
Type
Type
Type
Binary;
InterfaceType_unknown =
0,
tdm_T1 = 1,
aal2 = 3,
voip = 5,
tdm_E1 = 15
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Number(n)
Binary;
Circuit
Circuit(m)
Circuit
Binary;
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Group Number
Group Number
Group Number
Binary;
Type
Type
Type
casTrunkGroup = 4,
biccTrunkGroup = 9,
bssTrunkGroup = 11

Gsm SCF Address
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40740(H84)
to description

Service Key
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40741(H85)
value
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40745(H86)
01)
Call;1(H01):Release
Call

Free Format Data
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40757(H87)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
48950(HA8)
Information
31)
Information(m)
Binary;
Information
Refer to Camel Leg
Information
Information
31)
Information(m)
Binary;
Information
Refer to Camel Leg
Information

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40742(H89)
value

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H9F 11)
05)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H 9F 12)
01)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
40754(H 9F 13)
01)

MO SMS
Header
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
166(HA6)
length(n)
Packages length
package
For example:

MO SMS Call Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
80)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


01)
06)
Served IMSI
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
81)
Served IMEI
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
82)
Served MSISDN
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
83)
to description
Ms Class Mark
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
84)
Service Centre
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
85)
to description
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Recording Entity
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
134(H86)
Location
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A7)
08)
80):Area Code Tag
Code
81):Cell Id Tag
Id
Message Reference
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
88)
01)
3 3 n Message Reference Binary;
Origination Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
89)
09) 09) 09) 09)
3 3 10 Origination Time Stamp Refer to Time Stamp
Description
Sms Result
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


AA)
3 3 1 Tag of Result Binary;Fixed Value 128(H
80)
4 4 1 Length of Result Value(m) Binary;
5 5 m Value of Result Binary;
Record Extension
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Extension
Binary;
ID
Object ID
Value
Fixed Value (H
Extension
of Extension(k)
Binary;
Extension(j)
Binary;
Extension
Refer to the Content of MO SMS
Record Extension
Content of MO SMS Record Extension
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
present
RNCid of First RNC
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
BSCid of First BSC
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


3 3 n BSCid of First BSC Binary;
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
(1)
Binary;
(2)
Binary;
(3)
Binary;
6 6 1 ... Binary;
(i)
Binary;

Destination Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8C)
3 3 N Digit(i+1) Digit(i) Packed Digits
Camel SMS Information
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AD)
3 3 N Camel SMS Content Refer to Camel SMS
Content
Camel SMS Content
Gsm SCF Address
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
81)
to description
Service Key
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Default Sms Handling
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 Default Sms Handling Binary;continueTransaction = 0,
releaseTransaction = 1
Free Format Data
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks

Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
Value 133(H
85)
NPI refer to
description
SI refer to
description

Destination Subscriber Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
86)
01)
3 3 10 Destination Subscriber Number Refer to
ISDNBasicService
Description

Camel SMSCAddress
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
87)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


to description

Sms Reference Number(not implemented)

System Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8E)
01)
3 3 n System Type Binary;0(H
00):UnKnown;1(H
01):3G;2(H02):2G

MT SMS
Header
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
167(HA7)
length(n)
Packages length
package
For example:

MT SMS Call Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
80)
01)
07)
Service Centre
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
81)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


to description
Served IMSI
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
82)
Served IMEI
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
83)
Served MSISDN
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
84)
to description
Ms Class Mark
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
85)
Recording Entity
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
134(H86)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Location
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A7)
08)
80):Area Code Tag
Code
81):Cell Id Tag
Id
Delivery Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
88)
09) 09) 09) 09)
Description
Sms Result
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A9)
80)
5 5 m Value of Result Binary;
Record Extension
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 170(HAA)
Extension
Binary;
ID
Object ID
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Value
Fixed Value (H
Extension
of Extension(k)
Binary;
Extension(j)
Binary;
Extension
Record Extension
Content of MT SMS Record Extension
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
present
Sms Originating Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
81)
to description
RNCid of First RNC
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
BSCid of First BSC
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Subscribed OSSS Codes (RDS14064)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
(1)
Binary;
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


(2)
Binary;
(3)
Binary;
6 6 1 ... Binary;
(i)
Binary;

SGs Cause (RDS13870) (not implemented)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
2 2 1 Package Length(n) Binary;Fixed Value 1(H01)
3 3 1 SGs cause value Binary;

System Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8B)
01)
3 3 N System Type Binary;0(H
00):UnKnown;1(H
01):3G;2(H02):2G

SS Action Call
Header
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
170(HAA)
length(n)
Packages length
package
For example:
AA 79: The length of the package is 0x79
AA 81 B2:The length of the package is 0xB2

SS Action Call Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
80)
01)
0A)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Served IMSI
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
81)
Served IMEI
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
82)
Served MSISDN
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
83)
to description
Ms Class Mark
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
84)
Recording Entity
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
133(H85)
Location
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


A6)
08)
80):Area Code Tag
Code
81):Cell Id Tag
Id
Basic Service
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A7)
03)
Service
01)
Supplementary Service
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
88)
3 3 n Supplementary Service Code Refer to Supplementary
Service Code
SS Action Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
89)
5 5 m Value of SS Action Type Binary;
registration = 0,
erasure = 1,
activation = 2,
deactivation = 3,
interrogation = 4,
invocation = 5,

passwordRegistration=6
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


SS Action Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8A)
09) 09) 09) 09)
Description
SS Parameters
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AB)
3 3 n Content of SS Parameters Refer to SS Parameters
Content
SS Parameters Content
It only includes two parameters(FWD-to Number and UnstructuredData).Only one of them
should be present.
Forwarded-To Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
80)
to description
Unstructured Data
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 n Unstructured Data Hex String
SS Action Result
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AC)
80)
5 5 M Value of Result Binary;
SS Call Reference
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


8D)
3 3 n SS Call Reference Binary;
Record Extension
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 170(HAE)
Extension
Binary;
ID
Object ID
Value
Fixed Value (H
Extension
of Extension(k)
Binary;
Extension(j)
Binary;
Extension
Record Extension
Content of SS Action Record Extension
RNCid of First RNC
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
BSCid of First BSC
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Ussd Service Duration
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 n Ussd Service Duration Binary;Total Duration by Second
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


(1)
Binary;
(2)
Binary;
(3)
Binary;
6 6 1 ... Binary;
(i)
Binary;

System Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8F)
01)
3 3 N System Type Binary;0(H
00):UnKnown;1(H
01):3G;2(H02):2G

Roaming Record
Header
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
162(HA2)
length(n).
Packages length.
package
For example:

Roaming CDR Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
80)
01)
0A)
Served IMSI
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


81)
Served MSISDN
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
82)
to description
Calling Number
Field Name Field
NO.
Byte
Pos
Length(Bytes
)
7 6 5 4 3 2 1 0
Remarks
Value 131(H
83)
NPI refer to
description
SI refer to
description
Roaming Number
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
132(H84)
Recording Entity
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
133(H85)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
86)
80):Trunk Group
Group Name
String(Trunk Name)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
87)
80):Trunk Group
Group Name
String(Trunk Name)
Basic Service
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
88)
03)
Service
01)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 Transparency Indicator Binary;0(H00):transparent;1(H
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Value 01):non Transparent
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
AE)
Service Description
Service Description

Seizure Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8C)
09) 09) 09) 09)
Description
Answer Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8D)
09) 09) 09) 09)
Description
Release Time Stamp
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8E)
09) 09) 09) 09)
Description
Call Duration
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
8F)
seconds
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
91)
value
CauseForTermination
Description
Diagnostics Value
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
92)
Type(Gsm0408Cause)
80):Gsm0408Cause
value(m)
Binary;
Call Reference
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
93)
value
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
94)
value
Record
Binary;
Record Extension
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Extension
Binary;
5 5 1 Tag of CDR TYPE Object Binary;Fixed Value 6(H06)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


ID
Object ID
Value
Fixed Value (H
Extension
of Extension(k)
Binary;
Extension(j)
Binary;
Extension
Refer to the Content of MTC Record
Extension
Content of Roaming Record Extension
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
Type
Group Type
Group Type
Binary;
Type
Type
Type
Binary;

Number(n)
Binary;
Circuit
Circuit(m)
Circuit
Binary;
Field Name Field
NO.
7 6 5 4 3 2 1 0
Remarks
Type
Group Type
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Group Type
Binary;
Type
Type
Type
Binary;
Number(n)
Binary;
Circuit
Circuit(m)
Circuit
Binary;
Additional Chg Information
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
27)
Type
Chg Value
01):Charge
NationalIndicator
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 NationalIndicator

Binary; nationalCall (0);
internationalCall (1)
operatorIndicator
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 operatorIndicator

Binary; normalCall (0);
operatorCall (1)
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


present
upstreamCarrier
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 139(H8B)
3 3 n upstreamCarrier Binary;
downstreamCarrier
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 140(H8C)
3 3 n donwstreamCarrier Binary;

callingPartyLocationNumber
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 141(H8D)
3 3 n callingPartyLocationNumber Binary;
redirectingNumber
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 142(H8E)
3 3 n redirectingNumber Binary;
originalCalledNumber
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
1 1 1 Package Number Binary;Fixed Value 40754(H8F)
3 3 n originalCalledNumber Binary;
pRBTIndication
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 n pRBTIndication Binary;0(H00):False;1(H
present;
timeExtensions
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 timeExtensions.
callDurationms Package
Number
callDurationms Package
Binary;Fixed Value 9(H 9(H 9(H 9(H 09) 09) 09) 09)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Length
callDurationms
Refer to Time Stamp Description
seizureTimems Package
Number
seizureTimems Package
Length
seizureTimems
answerTimems Package
Number
answerTimems Package
Length
seizureTimems
releaseTime Package
Number
releaseTime Package
Length
seizureTimems
optimalRouteingType
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 optimalRouteingType Binary;
basic(0);earlyCF(1);lateCF (2)
disconnectingParty
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
3 3 1 disconnectingParty Binary;
invalidParty (0),
originationSideInitiated (1),
terminationSideInitiated (2),
networkInitiated (3)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
(1)
Binary;
4 4 1 Subscribed OSSS Codes Binary;
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


(2)
(3)
Binary;
6 6 1 ... Binary;
(i)
Binary;

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
96)
value
MSC Address
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
97)
value
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
98)
05)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
99)
01)

Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


9A)
01)

Partial Record Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
9B)
01)
timeLimit = 0,

HLRINT Record
Header
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
171(HB1)
length(n).
Packages length.
package
For example:

Roaming CDR Type
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
80)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


01)
0A)
Served IMSI
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
81)
Served MSISDN
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
82)
to description
Recording Entity
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
131(H83)
Basic Service
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
84)
03)
Service
01)
Routing Number
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


NO. Pos 7 6 5 4 3 2 1 0
85)
05)
interrogationTime
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
86)
09) 09) 09) 09)
3 3 10 interrogationTime Refer to Time Stamp
Description
numberOfForwarding
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
87)
value
3 3 n numberOfForwarding Binary;
interrogationResult
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
88)
value
3 3 n interrogationResult See Diagnostics;

Record Extension
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
Extension
Binary;
ID
Object ID
Value
Fixed Value (H
Extension
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


of Extension(k)
Binary;
Extension(j)
Binary;
Extension
Refer to the Content of MOC
Record Extension
Content of MOC Record Extension
Field Name Field
NO.
Byte
Pos
Length(Bytes)
7 6 5 4 3 2 1 0
Remarks
(1)
Binary;
(2)
Binary;
(3)
Binary;
6 6 1 ... Binary;
(i)
Binary;

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


C DEFINITIONS
Definition of NOA and NPI
NPI(Numbering Plan ID):
I_Unknown = 0,
ISDN_Telephony = 1,
Data = 3,
Telex = 4,
LandMobile = 6,
National = 8,
Private = 9,
I_Invalid = 15
NOA(Numbering Type):
T_Unknown = 0,
International = 1,
NationalSignificant = 2,
NetworkSpecific = 3,
Subscriber = 4,
Abbreviated = 6,
T_Invalid = 7

Definition of PRI and SI
SI(Screening Indicator):
UserProvidedNotVerified = 0x0,
UserProvided = 0x1,
UserProvidedVerifyFailed = 0x2,
NetworkProvided = 0x3
PRI(Presentation Indicator):
PresentationAllowed = 0x0,
PresentationRestricted = 0x1,
AddressNotAvailable = 0x2

Time Stamp(05-12-11 13:14:05 and Time Zone Offset = -8:15
Year Month Day Hour Minute Second Time
Zone
Offset
Flag
Hour Minute
H05 H12 H11 H13 H14 H05 - H08 H15

Basic Service Code
Data Call service = 0x10,
Telephony = 0x11,
EmergencyCalls = 0x12,
AutomaticFacsimileGroup = 0x62,
Asynchronous_9_6kbps = 0x16,
Asynchronous_GeneralData = 0x17,
Synchronous_GeneralData = 0x1F,
S_Invalid = 0xFF

Supplementary Service Code
11 Calling line id. present.
12 Calling line id. restrict.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


13 Connected line id. present.
14 Connected line id. restrct.
20 All call forwarding
21 Call fwd. unconditional
28 All conditional call fwd.
29 Call fwd. on subscr. busy
2A Call fwd. on no reply
2B Call fwd. on not reachable
41 Call waiting
42 Call hold
43 Completion of Calls to Busy Subscriber originating side
44 Completion of Calls to Busy Subscriber destinating side
51 Multiparty
61 CUG
71 Advice of charge - inform.
72 Advice of charge - charging
81 User to User Signalling - Service 3 (UUS3)
90 All call barring
91 Barring of outgoing calls
92 Barring, all outgoing calls
93 Bar., all outg. int. calls
94 Bar., all outg. int. ex-HPLMN
99 Barring of incoming calls1
9A Barring, all incoming calls
9B Bar., all inc. calls, roaming
A0 Priority Call in state of disaster
E0 Delayed Hot Line
E1 Call Deflection
F1 Hot Billing
FC MRBT
FE PRBT
ISDN Basic Service Code
allServices = 0,
speech = 1,
unrestrictedDigitalInformation = 2,
audio3k1Hz = 3,
unrestrictedDigitalInformationWithTonesAndAnnouncements = 4,
multirate = 5,
telephony3k1Hz = 32,
teletex = 33,
telefaxGroup4Class1 = 34,
videotexSyntaxBased = 35,
videotelephony = 36,
telefaxGroup2_3 = 37,
telephony7kHz = 38,
euroFileTransfer = 39,
fileTransferAndAccessManagement = 40,
videoconference = 41,
audioGraphicConference = 42

CISS Result
SS_RESULT_SUCCESS = 1,
SS_RESULT_FAILURE = 2,
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


SS_RESULT_RETURN_ERROR = 3, //The corresponding code defined in
SS_RESULT_PROVIDER_ERROR = 4, //The corresponding code defined in
SS_RESULT_REJECT_ERROR = 5, //The corresponding code defined in
SS_RESULT_INVALID =0xFF

LRN Source Indicator and LRN Query Status Indicator

lRN-NP-Database =1,
switchingSystemData =2,
incomingsignaling =3,
unknown =9

successfulQuery =1,
noQueryResponseMsg =2,
queryProtocolErr =4,
queryResponseDataErr =5,
queryRejected =6,
queryNotPerformed =9,
queryUnsuccessful =99

Trunk group type

Invalid =0,
isupTrunkGroup =1,
gR303TMC =2,
gR303CSC =3,
casTrunkGroup =4,
casLine =5,
priTrunkGroup =6,
nfas-PRI =7,
casDAL =8,
biccTrunkGroup =9,
casLES =10,
bssTrunkGroup =11,
sipTrunkGroup =12,
gPRS =13,
iNTERCONNECT =14,
bnc =15,
iNTERWORKING =16,
utranTrunkGroup =17,
bssIDVOIP =18,
tup =19,
umaTrunkGroup =20,
nBAAL2 =21,
imssip =22,
SIP-I =25,
noTrunkGroupPresent =255
Interface type

Unknown =0,
tdm-T1 =1,
aal1-TRUNK-IF =2,
aal2 =3,
dsl-aal2-IF =4,
voip =5,
voip-IF-EXT =6,
aal2-TRUNK-IF =12,
gtp-IF =13,
voip-IF =14,
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


tdm-E1 =15,
nb-IP =16,
nb-ATM =17,
eph-IF =18,
tdm =19
noItfTypPresent =255

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


D CDR IMPACT FOR MNP SOLUTION
SMS CDR is not impacted for all MNP solution. Only voice CDR is impacted for MNP solution.
There are three kinds MNP solution (MNP, IN, CAMEL) on high level:
Note: In fact, each customer maybe has their own special MNP scenario, because 3GPP hasnt defined
MNP solution clearly.
MNP_SRF based
solution
MNP_IN based
solution
MNP_CAMEL
based solution
Ref doc TRS MNP
3BL76578AAAADSZZA
RDS9189 HLD MNP
3HP700335047DSZZA
Its CAMEL basic
function and not
special for MNP.
message SRI and SRI_ACK NPREQ and
NPREQ_RR
IDP and
CONNECT
Impacted NE
for WCS
WCS and HLR WCS, NPDB, HLR WCS and SCP
Impacted CDR
field.
roaming number Location Routing
Number (LRN)
LRN Query Status
Indicator
CAMEL
Destination
Number in
CAMEL Leg
Information

1) MNP_SRF based solution:
CU, GO MALTA, Mobitel Georgia are general MAP based MNP solution.
B part is port out
subscriber ?
early CF? CF case?
Roaming number CDR
field in MOC CDR for A
part
Y or N Y Y not present
N N Y or N MSRN
Y N Y or N
National-RC+MSISDN-
B
C part is port out
subscriber ?
Roaming number CDR
field in MOC-CF CDR for
B part
N MSRN
Y
National-
RC+MSISDN-B
called part is port
out subscriber ?
Callednumber CDR field
in incoming gateway CDR
Callednumber CDR field
in Outgoing gateway CDR
N MSRN MSRN
Y
National-RC+MSISDN-
B
National-RC+MSISDN-
B
Note: GO MALTA needs RDS16318 Fill 1st SRI in roaming number CDR field for 3GPP CDR.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


2) MNP_IN based solution: (RDS9189)
TNZ use Number Portability Query and response (NPREQ and NPREQ_RR) message to communicate
with NPDB. 3GPP CDR use below three CDR field to record the MNP result from NPDB.
Location Routing Number (LRN) - OC Location Routing Number for Number Portability feature
RDS9189
LRN Source Indicator - OC LRN Source Indicator tells the source of the LRN
RDS9189
LRN Query Status Indicator - OC Status of Number Portability query.
RDS9189

3) MMP_CAMEL based solution
Ghana Glo use MNP_CAMEL based solution.
Assume A call B, A part is Postpaid subscriber
B part is port out
subscriber or
foreign number
(non-ported)?
early CF? CF case?
Roaming number
CDR field in MOC CDR
for A part
N N Y or N MSRN
Y N Y or N
National-
RC+MSISDN-B
Assume A call B forward to C, B part is postpaid subscriber
C part is port out
subscriber or foreign
number (non-ported)?
Roaming number CDR field in
MOC-CF CDR for B part
N MSRN
Y National-RC+MSISDN-B

4) Ture Move/Glo MNP solution:
Use different call scenario for postpaid and prepaid subscriber
Postpaid subscriber uses MAP based MNP solution.
prepaid subscriber uses IN based MNP solution.
Assume A call B, A part is Postpaid subscriber
B part is port out
subscriber or
foreign number
(non-ported)?
early CF? CF case?
Roaming number
CDR field in MOC CDR
for A part
N N Y or N MSRN
Y N Y or N
National-
RC+MSISDN-B
Assume A call B forward to C, B part is postpaid subscriber
C part is port out
subscriber or foreign
number (non-ported)?
Roaming number CDR field in
MOC-CF CDR for B part
N MSRN
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


Assume A call B, A part is prepaid subscriber
B part is port out
subscriber or
foreign number
(non-ported)?
CAMEL Destination Number in CAMEL
Leg Information CDR field in MOC CDR for
A pat
N
National-
MSISDN-B
Assume A call B forward to C, B part is prepaid subscriber
C part is port out
subscriber or
foreign number
(non-ported)?
CAMEL Destination Number in CAMEL
Leg Information CDR field in MOC CDR for
B part
N
National-
MSISDN-B
Note: CAMEL Destination Number is only supported by 3GPP CDR format and not support by Atrium
CDR format.
5) TELENET special MNP solution:
TELENET use MNP_CAMEL based solution for MOC and MNP_SRF based solution for MTC.
TELENET is a special network. There is no own VMSC for TELNET. All MOC and MTC call will route
back to own GMSC to handle it.
Because TELENETs special network, we added new OutgoingIAMcallednumber CDR field in outgoing
gateway CDR for TELENET MNP charging purpuse. (RDS16253)
Called part is
port out
subscriber ?
OutgoingIAMcallednumber
CDR field in outgoing
gateway CDR (RDS16253
Enhance Outgoing gateway
CDR TELNET MNP solution)
N MSRN
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


E SYNTHESIS OF THE CDRS CONTENTS

CDR Field
M
O
C

M
O
C

E
M
Y

M
O
C

F
W

M
T
C

M
T
C

F
W

I
C

G
M
S
C

O
G
-
G
M
S
C

T
R
A
N
S
I
T

T
-
C
A
M
E
L

S
S

S
M
S

M
O

S
M
S

M
T

M
O
-
L
R

M
T
-
L
R

N
I
-
L
R

H
L
R
-
I
N
T

R
O
A
M

Additional Chg. Info
x x x x
X
Answer Time
x x x x x X x x x
X
Basic Service
(RDS9365) x x x x x X X X
X X
BSCIdOfFirstBSC
x x x x X x
x x x
Call duration
x x x x x X x x x
X
Call Reference
x x x x x X x x x x
X
Called Number
x x X x x x

Calling Number
x x x X x x x
X
CAMEL call leg
information (Note1) x x X X X

CAMEL Destination
Number X X

CAMEL initiated CF
indicator X x

CAMEL SMS
Information (Note1) X X

X x x x x X x x x x x x
X
Change Of Location
X x x

Channel Coding Used
X x

CLI Additional calling
party address x x

Connected Number
X X X x

CS ARP
X X x

CUG Incoming
Access Used
(RDS9804b) X

CUG Index
(RDS9804b) X

X

CUG Interlock Code
(RDS9804b) X X X X

CUG Outgoing
Access Indicator
(RDS9804b) X X X

CUG outgoing access
suppressed
(RDS9804b) X

Default call handling
x x X X x

Default call handling 2
x x x

Default SMS handling
X

Delivery Time
x

Destination number
X

Diagnostics
x x x x x X x x x x x x
X
EMS-Digits
X

EMS-Key
X

Fixed network user rate
x x x x

Free format Data
x x X X x X

Free format Data 2
x x x

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


CDR Field
M
O
C

M
O
C

E
M
Y

M
O
C

F
W

M
T
C

M
T
C

F
W

I
C

G
M
S
C

O
G
-
G
M
S
C

T
R
A
N
S
I
T

T
-
C
A
M
E
L

S
S

S
M
S

M
O

S
M
S

M
T

M
O
-
L
R

M
T
-
L
R

N
I
-
L
R

H
L
R
-
I
N
T

R
O
A
M

Free format Data 3 x x
Free format data
append indicator x x x

Free format data
append indicator 2 x x X

Free format data
append indicator 3 x x

GsmSCF address
x x x x X X X X

GsmSCF address 2
x x X

GsmSCF address 3 x x
Guaranteed bit rate
x x

High Layer
Compatibility
(RDS6904) X X X

Hot billing subscriber
x x x x X x x
x x x X
Incoming TKGP
x x x x X X x x X
X
Interconnect Facility x x x x X X x x X
Interrogation time
stamp
X

X

Interrogation Result

X
IP Connection
x x

ISDN Basic Service
X X x

ISDN Bearer Capability
(RDS6904) X X X

JurisdictionInformation
Parameter x x x x x x x x

x
ParameterSourceIndica
tor x x x x x x x x

x
ParameterQueryStatus x x x x x x x x

x
Location Routing
Number (RDS9189) x x x x

x x x x

x
Low Layer Compatibility
(RDS6904) X X X

LCS Cause

x x x
LCS Client Identity

x x x
LCS Client Type

x x x
LCS Priority

x x x
LCS QoS

x x x
Level of CAMEL
service x x x

Location
(RDS8184 / D46475) x x X x X x x x x

Location Estimate
x x x

Location Type
x

(RDS9189) x x x x

x x x x

x
LRN Query Status
Indicator (RDS9189) x x x x

x x x x

x
Maximum bit rate
x x

MeasureDuration

x X x
Message Reference
x

MLC Number

x x x
MOLR Type

x
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


CDR Field
M
O
C

M
O
C

E
M
Y

M
O
C

F
W

M
T
C

M
T
C

F
W

I
C

G
M
S
C

O
G
-
G
M
S
C

T
R
A
N
S
I
T

T
-
C
A
M
E
L

S
S

S
M
S

M
O

S
M
S

M
T

M
O
-
L
R

M
T
-
L
R

N
I
-
L
R

H
L
R
-
I
N
T

R
O
A
M

MS Category
x x x x

MS Classmark
x x x x x x

MSC Address
x x x x x
X
MSC incoming trunk
X
MSC outgoing trunk
X
MSC server indication
x

Multimedia call
x x x x

Network call reference
x x x x X X x
X
Notification to MS User

x
Number of DP
encountered x x x

Number of Forwarding

X
Origination Time
x

OutgoingIAMcallednum
ber (RDS16253) x

Outgoing TKGP
x x x x x x x x x
X
Partial Record Type
x x x x x
X
Positioning Data
x x x

Privacy Override

x
Radio Chan. Used
x x x

Rate indication
x x x x

Record extensions
x x x x x x x x x x x x x x x
X X
Record number x x x x x x x x x x x x x x x X X
Record Type
X X
Recording Entity
X X
Redirecting counter
x x

Redirecting number
x x
X
Release Time
x x x x x x x x x
X
RNCIdOfFirstRNC
x x x x x x
x x x
Roaming Number
x x x x x
X
Routing Number

X X
Seizure Time
x x x x x x x x x
X
Sequence number
x x x x x x x x x
X
Served IMEI
(RDS8184 / D46475) x x X x X x x x
x
Served IMSI
x x x x x x x x x x x x
X X
Served MSISDN
x x x x x x x x x x x x
X X
Service Centre
x x

Service Duration
x

Service key
x x x x X X x x

Service key 2
x x x

SMS Originating
Number x

SMS Result
x x

SMS Size
x x

Speech Version Used
x x

SS Action Type
x

SS Action Result
x

SS Action time stamp
x

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


CDR Field
M
O
C

M
O
C

E
M
Y

M
O
C

F
W

M
T
C

M
T
C

F
W

I
C

G
M
S
C

O
G
-
G
M
S
C

T
R
A
N
S
I
T

T
-
C
A
M
E
L

S
S

S
M
S

M
O

S
M
S

M
T

M
O
-
L
R

M
T
-
L
R

N
I
-
L
R

H
L
R
-
I
N
T

R
O
A
M

SS Parameters
x

subscribedOSSSCodes
(RDS14064)
x x x x x x x x x x x x x
Supplementary Service
x

Supplementary
Services x x x x
X
System Type
x x x x x x x x x

Translated Number
x x x

x x x x
X

Note (1): This parameter is a container which may include several subparameters.

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


F CAUSE CODE

Please reference External causes / internal codes mapping 3BL76757AAAADSZZA

A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


G CDR CONTENTS EVOLUTION
Note:
In the table below, only W4.x and W5.x Releases are explicitly mentioned, in which improvements have
been made for the 3GPP Billing format. Especially Service Packs (SP) are mentioned only in case of RDS or
PR implementation took place.

RDS
Number
RDS Title Option Updated parameter

Release W4.0
RDS4394 French ISUP
No
See chapter 5.2.6.1
RDS5440 Generation of 3GPP-compliant CDRs
PART 2
No
Several parameters in MOC/MTC for
UMTS,

RDS5700 Insert MSRN to camel MOC CDR
No
Roaming number in MOC-records,
RDS5680 Outpulse MAP CLI changes Yes store different translated number (before
Outpulsed or after Outpulsed) in CDR
Release W4.20 SP1
RDS6034 Evolutions for N-CSI CAPV2 when
triggering at transit WSS level
YES Adding of CAMEL parameter in trunk-
Records,

RDS6904 Enhancement of the 3GPP billing
format for Orange UK
YES Support of ROAM-/HLRint-Record,
Add-on Bearer Service Parameter into
trunk-records,

Release W4.21
RDS9365 Charging and announcement
requirements for videophone service
(China CDE)
YES Adding Basic service parameter into
trunk-records,

Release W4.21 SP2
D46475
(patch to impl.
RDS8184
partly)
Full IMEI-Support in 3GPP billing
YES Inclusion of IMEI and Location info into
CF-CDRs (MOC-CF, MTC-CF),
search with PR-number (D46475)
Release W4.21 SP3
RDS7502b Add area code in the calling party for
incoming PSTN call (support LLN)
YES Change of content of calling party
number in the trunk-CDRs.
(This function is redesigned in R4.40 and
billing is not impacted.)
Release W4.21 SP11
RDS9804 CUG charging requirement for 3GPP
CDR
YES Adding of CUG fields in MOC CDR
search with RDS-number
Release W4.3x
These Releases doesnt contain RDS9365, because it is China specific.
These Releases doesnt contain RDS9804, because it is implemented in R4.21SP11.
No other changes.
Release W4.31 (SP6)
RDS13186 TMO AoIP Phase 1 No Suppot AoIP in trunk group type
Release W4.32 (SP2)
RDS13186a TMO AoIP Phase 1 No Suppot AoIP in trunk group type
Release W4.40 SP1 (based on W.21)
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


RDS
Number

RDS9851 3GPP Billing Aspects for MGCF-
function
YES Adding of INC/OUTG-TKGP-extensions
into all CDR-records,

RDS7564a CDR back compatible function from
R4.x to R3.2
YES Changes
a) format of Recording Entity parameter
changeable via Option
b) Option for RDS6034 added
c) Content of additional charging info
parameter changeable via Option

RDS5700a Insert MSRN to camel MOC CDR
No
Roaming number in MOC-records,
RDS5700
RDS8184

Full IMEI-Support in 3GPP billing
YES Inclusion of IMEI and Location info into
CF-CDRs (MOC-CF, MTC-CF),

RDS9189 5060 WCS MNP - NPDB Interface over
3GPP2 IS-41
YES Adding LRN-parameters into all call
related CDRs
Release W4.49 (based on W4.40)
These Releases doesnt contain RDS9804, because it is implemented in R4.21SP11.
No other changes.
Release W4.49 SP6 (based on W.4.49)
RDS9804a CUG charging requirement for 3GPP
CDR
YES Adding of CUG fields in MOC CDR
search with RDS-number
Release W4.49 SP9
RDS14064 Capture OSSS Codes in 3GPP CDRs YES Capture OSSS Codes in 3GPP CDRs
Release W5.0 (based on W4.49)
RDS8242 Iu-cs over IP (WCS)
No
Impact MSC incoming/outgoing trunk
group extension

RDS9804b CUG charging requirement for 3GPP
CDR
YES Adding of CUG fields in MOC, MTC CDR

Release W5.0 SP6
RDS6029 Support of SIP with Encapsulated ISUP
(SIP-I)
No
Support of SIP with Encapsulated ISUP
(SIP-I), add SIP-I in TrunkGroupType of
TrunkGroupExtension.
RDS12458 Disable SMSMT CDR in case of
delivery notification to calling party
YES Disable SMSMT CDR in case of delivery
notification to calling party by control
flag.
RDS14064a Capture OSSS Codes in 3GPP CDRs YES Capture OSSS Codes in 3GPP CDRs
Release W5.0 SP7
RDS14086 Release Link Trunk - Reorigination
based on Redirection Number
YES Generate special MOC with ECT ss-
code for call re-origination.
RDS14844 Support tkgpName in TrunkGroup for
3GPP CDR
YES Support tkgpName in TrunkGroup for
3GPP CDR
Release W5.0 SP8
RDS16318 Record 1st received MSRN in roaming
number CDR Field for 3GPP MOC
CDR
YES Record 1st received MSRN in roaming
for GO MALTA MNP solution
Release W5.0 FF
RDS16380 Add an option for unsuccessful SMS
CDR for Atrium and 3GPP CDR format
YES Support to generate unsuccessful SMS
CDR by DB flag.
A
l
l

r
i
g
h
t
s

r
e
s
e
r
v
e
d
.

P
a
s
s
i
n
g

o
n

a
n
d

c
o
p
y
i
n
g

o
f

t
h
i
s

d
o
c
u
m
e
n
t
,

u
s
e

a
n
d

c
o
m
m
u
n
i
c
a
t
i
o
n

o
f

i
t
s

c
o
n
t
e
n
t
s

n
o
t

p
e
r
m
i
t
t
e
d

w
i
t
h
o
u
t

w
r
i
t
t
e
n

a
u
t
h
o
r
i
z
a
t
i
o
n

f
r
o
m

A
l
c
a
t
e
l
-
L
u
c
e
n
t
.


RDS
Number

RDS16253 Enhance Outgoing gateway CDR
TELNET MNP solution
YES Add OutgoingIAMcallednumber to
record the called number from outgoing
IAM message CDR Field in Outgoing
gateway CDR

Release W5.1.1
RDS14064b Capture OSSS Codes in 3GPP CDRs YES Capture OSSS Codes in 3GPP CDRs
RDS10893a AoIP (WCS) - Full IP architecture No Suppot AoIP in trunk group type
RDS13870 LTE Circuit Switch Fallback for SMS YES Only part of the E-CGI is stored in the
existing CGI field in the CDR for SMS
CSFB case.
RDS16380a Add an option for unsuccessful SMS
CDR for Atrium and 3GPP CDR format
via the WEM
YES Support to generate unsuccessful SMS
CDR by WEM flag.
RDS16253a Enhance Outgoing gateway CDR
TELNET MNP solution
YES Add OutgoingIAMcallednumber to
record the called number from outgoing
IAM message CDR Field in Outgoing
gateway CDR
RDS16318a Record 1st received MSRN in roaming
number CDR Field for 3GPP MOC
CDR
YES Record 1st received MSRN in roaming
for GO MALTA MNP solution
Release W5.1 B8/B9
RDS!6308 Capture OSSS Codes in 3GPP CDRs YES Capture OSSS Codes in 3GPP CDRs

END OF DOCUMENT

3gpp Cdrs Specs Alcatel

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

3gpp Cdrs Specs Alcatel

Загружено:

Авторское право:

Доступные форматы

A

holding time of outgoing leg =

Вам также может понравиться