Charging Specification CS3.0

s

MOBNET

DescriptionVersion 3

D900Charging in MSC – Description of Record LayoutsVersion SR11MAF AWCC Afghanistan

Issued byICN, Information and Communication NetworksHofmannstrasse 51, D-81359 Munich

Copyright Siemens AG 2023 All Rights Reserved.

SIEMENS AKTIENGESELLSCHAFT

Author: Mr S. Kunjebeharie XSDATGTranslator:

No Replacement Service

DOCDB Status: ___________________ Retrieval Date: ________

DOCDB Title: _______________________________________________________

Version 3

In addition to the authors named on the cover page the following persons havecollaborated on this document:

The document comprises 182 pages, all pages have issue no 03.

The document is based on template .

This issue was last saved on 07.02.2007 15:22.

This document was edited with MS WinWord version 10.0.

2

TN WinWord Templates, 01/03/-1,

Use menu item Document->Update Document Statistics to update these fields

0 General Information 7

0.1 Issue Control........................................................................................................................70.2 History..................................................................................................................................70.3 History of Changes..............................................................................................................8

0.3.1 New Features.........................................................................................................................................80.3.2 Other Changes.....................................................................................................................................100.3.3 Changes resulting from document review........................................................................................100.3.4 Changes resulting from error correction during FT2.....................................................................100.3.5 Changes resulting from error correction during project specific FT2..........................................11

0.4 References..........................................................................................................................120.5 Glossary and Abbreviations.............................................................................................150.6 Keyword / Descriptor........................................................................................................200.7 List of Figures and Tables................................................................................................21

1 Billing Record Structure 22

1.1 Some explanations to the ASN.1 Encoding rules...........................................................221.1.1 Encoding of the Tag............................................................................................................................231.1.2 Encoding of the length........................................................................................................................261.1.3 Encoding of the content......................................................................................................................27

1.2 Differences in the Charging behaviour beetween ChaSer and GDC...........................271.3 Differences in the Administration of the Charging Client Records (CDRs) on CP and MP............................................................................................................................................28

2 MCR and ITR: CALL / EVENT RECORDS 30

2.1 SELECTED OPTIONS....................................................................................................302.1.1 Options for Buffer / File Attributes for MCR records....................................................................302.1.2 Options for Buffer / File Attributes for ITR records.......................................................................36

2.2 RECORD CONTENTS....................................................................................................372.2.1 Billing record tag.................................................................................................................................372.2.2 General Billing record contents.........................................................................................................372.2.3 Description of the different records...................................................................................................442.2.3.1 MOC - Mobile Originating Call Record........................................................................................452.2.3.2 MODPAD - Mobile Originating Call to dedicated PAD Access Record (not in PCS)...............482.2.3.3 EMY- Emergency Call Record (MOC/Emergency record).........................................................502.2.3.4 MTC - Mobile Terminating Call Record.......................................................................................522.2.3.5 ROA - Roaming Record...................................................................................................................542.2.3.6 CFU - Billing Records for Call Forwarding Unconditional.........................................................562.2.3.7 CFC - Billing Records for Call Forwarding Conditional.............................................................592.2.3.8 SCI - Billing Records for Subscriber Controlled Input................................................................622.2.3.9 TRANSIT - Transit Records...........................................................................................................642.2.3.10 SMSMT - Mobile terminating SMS point to point Record........................................................662.2.3.11 SMSMO - Mobile originating SMS point to point Record.........................................................672.2.3.12 PABXOG - PABX Originating Call Record (not in PCS)..........................................................692.2.3.13 PABXIC - PABX Terminating Call Record (not in PCS)..........................................................712.2.3.14 ECT - Emergency Call Trace Record..........................................................................................732.2.3.15 MOCATT - Mobile Originating Call Attempt Record...............................................................742.2.3.16 ROAATT - Roaming Attempt Record.........................................................................................762.2.3.17 EMYATT - Emergency Call Attempt Record (MOC/Emergency attempt record)................782.2.3.18 MTCATT - Mobile Terminating Call Attempt Record..............................................................802.2.3.19 CFUATT - Call Forwarding Attempt Record in case of CFU...................................................822.2.3.20 CFCATT - Call Forwarding Attempt Record in case of CFC...................................................842.2.3.21 MOCTRAC - Mobile Originating Call Record IMSI Trace......................................................86

2.2.3.22 MTCTRAC - Mobile Terminating Call Record IMSI Trace.....................................................892.2.3.23 SMSTTRAC- Mobile terminating SMS point to point Record IMSI Trace............................912.2.3.24 SMSOTRAC - Mobile originating SMS point to point Record IMSI Trace............................92

2.3 DESCRIPTION OF CALL / EVENT RECORD FIELDS............................................942.3.1 additionalBearerServiceInfo (not for PCS projects)........................................................................942.3.2 aOCParameter.....................................................................................................................................952.3.3 backwardChargingInfoCBA..............................................................................................................952.3.4 backwardChargingInfoCHT..............................................................................................................962.3.5 backwardChargingInfoITX...............................................................................................................962.3.6 backwardChargingInfoTAX..............................................................................................................962.3.7 basicService..........................................................................................................................................972.3.8 biccCallInstCodeOut, biccCallInstCodeInc......................................................................................982.3.9 callDuration.........................................................................................................................................982.3.10 callHoldInvocCount..........................................................................................................................992.3.11 callReferenceNumber......................................................................................................................1002.3.12 callTransactionType........................................................................................................................1012.3.13 callTransferThirdParty..................................................................................................................1062.3.14 callWaitInvocCount........................................................................................................................1062.3.15 camelCommonData.........................................................................................................................1062.3.16 camelDialog......................................................................................................................................1062.3.17 camelFFDataIncAppendInd...........................................................................................................1072.3.18 camelFFDataIncLeg........................................................................................................................1072.3.19 camelFFDataOutAppendInd..........................................................................................................1072.3.20 camelFFDataOutLeg.......................................................................................................................1082.3.21 camelInitCfIndicator......................................................................................................................1082.3.22 carrierAccessCode...........................................................................................................................1082.3.23 causeForTermination......................................................................................................................1092.3.24 cellId.................................................................................................................................................1092.3.25 changeFlags......................................................................................................................................1122.3.26 channelCoding (not for PCS projects)..........................................................................................1132.3.27 chargeAdviceElement.....................................................................................................................1132.3.28 chargeAdviceInfo............................................................................................................................1132.3.29 chargeAdviceInformation...............................................................................................................1142.3.30 chargeBandNumber........................................................................................................................1142.3.31 chargeIndicator...............................................................................................................................1142.3.32 chargingInformation.......................................................................................................................1152.3.33 chargingPulses.................................................................................................................................1152.3.34 chargingtimeData............................................................................................................................1152.3.35 chrgContainer1................................................................................................................................1152.3.36 chrgContainer2 ... 5.........................................................................................................................1162.3.37 cicIc, cicOg.......................................................................................................................................1162.3.38 cphIndication (not for PCS projects)............................................................................................1172.3.39 connectedSwitchId..........................................................................................................................1172.3.40 dAId (not for PCS projects)...........................................................................................................1172.3.41 dateOfCAMELLeg..........................................................................................................................1182.3.42 defaultCallHandling........................................................................................................................1182.3.43 destByOptimalRoutingMmcEcf.....................................................................................................1182.3.44 dialledOtherParty............................................................................................................................1182.3.45 drcCallId..........................................................................................................................................1192.3.46 drcCallRN........................................................................................................................................1202.3.47 drcChrgOrigin.................................................................................................................................1212.3.48 drcTariffClass..................................................................................................................................1212.3.49 durationBeforeAnswer....................................................................................................................1212.3.50 durationOfCAMELLeg..................................................................................................................1222.3.51 e1, e2, e3, e4, e5, e6, e7....................................................................................................................1222.3.52 esrkNumber (only in PCS1900 projects).......................................................................................1232.3.53 exchangeId.......................................................................................................................................1232.3.54 fixedNetworkUserRate (not for PCS projects).............................................................................1242.3.55 gsmScfAddress.................................................................................................................................1242.3.56 guaranteedBitRate..........................................................................................................................1242.3.57 hotTransferResult...........................................................................................................................125

2.3.58 identificationVGSInitiator..............................................................................................................1252.3.59 iMSIVGSInitiator............................................................................................................................1252.3.60 inAoC................................................................................................................................................1252.3.61 inatIndicator....................................................................................................................................1252.3.62 incTgTCompBlock..........................................................................................................................1262.3.63 individualBearerserviceNumber....................................................................................................1262.3.64 individualTeleserviceNumber........................................................................................................1262.3.65 inFlag................................................................................................................................................1272.3.66 initiatorIndicationOfVGCS............................................................................................................1272.3.67 inServiceKey....................................................................................................................................1272.3.68 intermediateSequenceNumber.......................................................................................................1282.3.69 inTransPar.......................................................................................................................................1292.3.70 iSDNBasicService............................................................................................................................1292.3.71 lCSCause..........................................................................................................................................1292.3.72 lCSCauseforTermination................................................................................................................1312.3.73 lCSClientDialedByMSID................................................................................................................1322.3.74 lCSClientExternalID.......................................................................................................................1332.3.75 lCSClientIdentity.............................................................................................................................1332.3.76 lCSClientInternalID........................................................................................................................1342.3.77 lcsClientType...................................................................................................................................1342.3.78 lCSMoLr..........................................................................................................................................1342.3.79 lCSPriority.......................................................................................................................................1342.3.80 lCSQoS.............................................................................................................................................1352.3.81 lCSRequestType..............................................................................................................................1362.3.82 lCSSSCode.......................................................................................................................................1362.3.83 levelOfCAMELService...................................................................................................................1362.3.84 locationAreaCode............................................................................................................................1372.3.85 locationEstimate..............................................................................................................................1382.3.86 locationEstimateType......................................................................................................................1392.3.87 locationNumber...............................................................................................................................1402.3.88 locationServiceInfo..........................................................................................................................1402.3.89 maximumBitRate............................................................................................................................1402.3.90 mcrDestinationNumber..................................................................................................................1402.3.91 mcrDestinationNumberSMS..........................................................................................................1412.3.92 measureDuration.............................................................................................................................1422.3.93 mlcNumber......................................................................................................................................1422.3.94 msAccessRate...................................................................................................................................1422.3.95 mscAddress......................................................................................................................................1432.3.96 msClassmark....................................................................................................................................1432.3.97 multipleSMTransfer........................................................................................................................1442.3.98 nMTForwardedIndicator...............................................................................................................1452.3.99 noOfDispatcherInVGSGroup........................................................................................................1452.3.100 noOfDispatWithSuccSetup...........................................................................................................1452.3.101 noOfRmscsInGroup......................................................................................................................1452.3.102 noOfRmscsWithSuccSetup...........................................................................................................1462.3.103 noOfUsedTrafficChannels (not for PCS projects).....................................................................1462.3.104 notificationToMSUser...................................................................................................................1462.3.105 numberOfCellsInVGSGroup.......................................................................................................1462.3.106 numberOfCellsWithSuccSetup....................................................................................................1472.3.107 numberOfDpEncountered............................................................................................................1472.3.108 oneTimeCharge.............................................................................................................................1472.3.109 optimalRoutingLcf........................................................................................................................1472.3.110 optimalRoutingMmcEcf...............................................................................................................1482.3.111 origTermBscId...............................................................................................................................1482.3.112 origTermMscId..............................................................................................................................1482.3.113 otherMSRN....................................................................................................................................1492.3.114 otherParty3a..................................................................................................................................1502.3.115 otherPartyLocation.......................................................................................................................1502.3.116 otherPartyLongNumber...............................................................................................................1512.3.117 otherPartyShortNumber..............................................................................................................1532.3.118 otherPartySMS..............................................................................................................................154

2.3.119 outgTgTCompBlock......................................................................................................................1552.3.120 pABXNumber (not for PCS projects).........................................................................................1552.3.121 partialRecordCorrelationId.........................................................................................................1562.3.122 partialRecordType........................................................................................................................1562.3.123 positioningData..............................................................................................................................1572.3.124 privacyOptionsInvoked................................................................................................................1592.3.125 privacyOverride............................................................................................................................1592.3.126 protocolIdForSMS........................................................................................................................1592.3.127 rateIndication................................................................................................................................1592.3.128 reasonForTermination..................................................................................................................1602.3.129 recordType.....................................................................................................................................1602.3.130 recordUse.......................................................................................................................................1612.3.131 redirectionCounter........................................................................................................................1622.3.132 secondCellId...................................................................................................................................1622.3.133 sequenceNumber...........................................................................................................................1632.3.134 sequenceOfCamelDialogs.............................................................................................................1642.3.135 servedIMEI....................................................................................................................................1642.3.136 servedIMSI.....................................................................................................................................1652.3.137 servedMSIsdn................................................................................................................................1652.3.138 servedMSRN..................................................................................................................................1662.3.139 servedOtherNumber.....................................................................................................................1662.3.140 servedSubscriberLocation............................................................................................................1672.3.141 serviceCentreAddress...................................................................................................................1672.3.142 sMReference..................................................................................................................................1682.3.143 sMTransmissionResult..................................................................................................................1682.3.144 speechCode.....................................................................................................................................1682.3.145 speechCodeVgs..............................................................................................................................1702.3.146 sSCode............................................................................................................................................1702.3.147 sSInvocCode...................................................................................................................................1732.3.148 sSInvocDate....................................................................................................................................1742.3.149 sSInvocSucc....................................................................................................................................1742.3.150 sSInvocTime...................................................................................................................................1742.3.151 sSSequenceOf.................................................................................................................................1752.3.152 startOfChargingdate.....................................................................................................................1752.3.153 startOfChargingtime.....................................................................................................................1762.3.154 subscriberCategory.......................................................................................................................1762.3.155 supplServiceInfo............................................................................................................................1772.3.156 systemType.....................................................................................................................................1782.3.157 tariffInfo.........................................................................................................................................1782.3.158 tariffInfoPack................................................................................................................................1782.3.159 termCamelRecordInVMSC..........................................................................................................1792.3.160 tgrpNameIc, tgrpNameOg............................................................................................................1792.3.161 thirdParty.......................................................................................................................................1802.3.162 timeOfCAMELLeg........................................................................................................................1802.3.163 timeQuality....................................................................................................................................1812.3.164 timeStamp......................................................................................................................................1812.3.165 timeTariff.......................................................................................................................................1822.3.166 traceReference...............................................................................................................................1822.3.167 traceType........................................................................................................................................1822.3.168 transactionIdentification..............................................................................................................1822.3.169 translatedOtherParty....................................................................................................................1832.3.170 transmissionMode.........................................................................................................................1842.3.171 transmittedZone............................................................................................................................1852.3.172 usedEmlppPriority........................................................................................................................1852.3.173 ussdAccessCode.............................................................................................................................1852.3.174 ussdCodingScheme........................................................................................................................1862.3.175 ussdNotifyCounter........................................................................................................................1862.3.176 ussdRequestCounter.....................................................................................................................1862.3.177 ussdString.......................................................................................................................................1862.3.178 voiceGroupServiceReference..........................................................................................................187

General Information

0 General Information

Note!

Particular GSM parts are marked blue, particular PCS parts are marked green.

This document is only applicable for subscriber charging and not for Interadministrative Charging (IACHASTA).

Interadministrative Charging (IACHASTA) is described in a separate document (see /IAC/).

0.1 Issue Control

The document comprises 182 pages, all pages have issue no 03.

0.2 History

Issue Date Reason for Changes

01 14.02.06 First issue, AFI version, for the project SR11MAF AWCC Afghanistan.

02 23.02.06 IUS Version

03 14.12.06 USSD Fields added:

ussdData – H’FF1F

ussdAccessCode – H’81

ussdString – H’82

ussdCodingScheme – H’83

ussdNotifyCounter – H’83

ussdRequestCounter – H’84

Table 1: History

General Information

0.3 History of Changes

This section summarizes all important changes in this document beginning with SR7(availablein the corresponding documents of SR7/SR8/CS1.0/CS2.0). In this chapter all important changes since the beginning of CS2.1 are available.It is distinguished between changes that are made because of new features and changes that are made for other reasons.

0.3.1 New Features

LM, CR Release Line New Element(s) Record(s)

43149 53-01 GSM

Enhanced Call TransferNew Parameter is: callTransferThirdParty

MOC, MODPAD, MOCOACSU, MOCATT, MTC, MTCATT

45558 53-05 GSM

Charging DB:Simple Ticket Layout Administration

Chapter 1.3

45632 53-01 GSM

UMTS BS20New parameters are:guaranteedBitRatemaximumBitRate

MOC, MODPAD, MOCATT, MOCTRAC,MTC, MTCATT,MTCTRAC

General Information

45826 53-01 GSM

LCSNew parameters are:lCSCauseforTerminationmeasureDuration

locationEstimateTypeprivacyOverridenotificationToMSUser

lCSMoLrlCSSSCode

Renamed Parameters to be standard conform:mlcNumber (CS2.1: gmlcNumber)positioningData (CS2.1: positioningMethodUsed)lCSCause (CS2.1 lCSFailureCause)lCSQoS (CS2.1 lCSQualityOfService)

Introduction of choice parameterslocationChoiceprivacyChoiceto unite the old ChaSer and new GDC Charging handling

MTLR, MOLR, NILR

MTLR

MOLR

FRQ86403, LM 48435

53-05 GSM

Common source for FRQ86403: Incorporation of NAT/INAT Identifier

New parameter is:inatIndicator

MTC, TRANSIT, ROA, CFC, CFU, PABXIC

Table 2: History of new Features

General Information

0.3.2 Other Changes

Nr. Issue Reason for Changes

1 53-01 Definition of default values for enumerated parameter2 53-01 For parameter with coding a/b as integer/octet string a homogeneous

handling is defined from CS3.0 on:- coding a is defined as integer with variable length, this

definition appears in the General table and in the parameter description part.

- coding b is defined as octed string with fixed lenght, this appears in the parameter description part.

Table 3: History of other Changes

0.3.3 Changes resulting from document review

3 53-03 mscAddress and gsmScfAddress defined as u(4)

4 53-03 description of the IMSI changed, the MNC can be 3 digits long.

Table 4: History of changes from document Review

0.3.4 Changes resulting from error correction during FT2

5 53-05 Parameter ssInvocCode changed back to octect string.

6 53-05 The value “transferToThirdParty” is deleted from Parameter LocationEstimateType. Parameter LocationEstimateType is deleted from the MOLR ticket. A new parameter lCSSSCode (value transferToThirdParty) is added in the MOLR ticket. The parameter locationChoice is extended.

7 53-05 Description examples for parameter lCSCauseForTermination added.

8 53-05 Default/filler for parameter recordingEntity corrected to FF.

9 53-05 Parameter inatIndicator added to MTC, TRANSIT, ROA, CFC, CFU, PABXIC.

10 53-05 Restriction for fileRecordSize for FRQ85235 (table 10) removed in CS3.0.

11 53-05 chapter 1.3. Differences in the Administration of the Charging Client Records (CDRs) on the CP and the MP added.

12 53-05 sequenceNumber description improved.

13 53-05 drcCallId and drcCallRN description improved.

14 53-05 Chapter 2.1.1 Options for Buffer / File Attributes for MCR records

General Information

adapted.

Table 5: History of changes from FT2

0.3.5 Changes resulting from error correction during project specific FT2

Table 6: History of changes from PI

General Information

0.4 References

The following documents are referenced throughout this specification. Where no version number is indicated, the latest version is taken.

/22.003/ 3rd Generation Technical Specification 3G TS 22.003"Circuit Teleservices supported by a Public Land Mobile Network (PLMN)"

/22.004/ 3rd Generation Technical Specification 3G TS 22.004"General on Supplementary services"

/02.20/ GSM Technical Specification 02.20 v. 3.0.1"Collection Charges"

/22.024/ 3rd Generation Technical Specification 3G TS 22.024 "Description of Charge Advice Information"

/22.067/ 3rd Generation Technical Specification 3G TS 22.067 Service Aspects" Enhanced Multi-Level Precedence and Pre-emption service(eMLPP) - Stage 1”

/22.081/ 3rd Generation Technical Specification 3G TS 22.081"Line identification Supplementary Services; Stage 1"

/22.082/ 3rd Generation Technical Specification 3G TS 22.082"Call Forwarding (CF) supplementary services - Stage 1"

/22.083/ 3rd Generation Technical Specification 3G TS 22.083"Call Waiting (CW) and Call Holding (HOLD); Supplementary

Services Stage 1"

/22.084/ 3rd Generation Technical Specification 3G TS 22.084"MultiParty (MPTY) Supplementary Services - Stage 1"

/22.085/ 3rd Generation Technical Specification 3G TS 22.085"Closed User Group (CUG) Supplementary Services - Stage 1"

/22.086/ 3rd Generation Technical Specification 3G TS 22.086"Advice of Charge (AoC) Supplementary Services - Stage 1"

/22.088/ 3rd Generation Technical Specification 3G TS 22.088"Call Barring (CB) Supplementary Services - Stage 1"

/23.003/ 3rd Generation Technical Specification 3G TS 23.003 "Numbering, Addressing and Identification"

General Information

/23.032/ 3rd Generation Technical Specification 3G TS 23.032 " Universal Geographical Area Description (GAD) "

/23.040/ 3rd Generation Technical Specification 3G TS 23.040"Technical realization of the Short Message Service (SMS); Point-to-point (PP)"

/23.067/ 3rd Generation Technical Specification 3G TS 23.067 " Enhanced Multi-Level Precedence and Pre-emption service (eMLPP) - Stage 2 "

/24.011/ 3rd Generation Technical Specification 3G TS 24.011"Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface"

/24.008/ 3rd Generation Technical Specification 3G TS 24.008/24.010/ 3rd Generation Technical Specification 3G TS 24.010

"Mobile Radio Interface Layer 3 - Supplementary Services"

/24.011/ 3rd Generation Technical Specification 3G TS 24.011"Point-to-Point (PP) Short Message Service (SMS) support onmobile radio interface"

/24.080/ 3rd Generation Technical Specification 3G TS 24.080

/25.413/ 3rd Generation Technical Specification 3G TS 25.413"Technical Specification Group Radio Access Network; UTRAN Iu interface RANAP signalling (Release 5)”

/28.062/ 3rd Generation Technical Specification 3G TS 28.062" Technical Specification Group Services and System Aspects;Inband Tandem Free Operation (TFO) of speech codecs;Service description; Stage 3”

/29.002/ 3rd Generation Technical Specification 3G TS 29.002 “Mobile Application Part (MAP)"

/29.078/ 3rd Generation Technical Specification 3G TS 29.078“Customised Applications for Mobile network Enhanced Logic

(CAMEL) Phase 4; CAMEL Application Part (CAP) specification(Release 5)”

/32.005/ 3rd Generation Technical Specification 3G TS 32.005

“3G call and event data for the Circuit Switched (CS) domain”

/32.200/ 3rd Generation Technical Specification 3G TS 32.200“Technical Specification Group Services and System Aspects;Telecommunication management; Charging management;

" Mobile radio interface Layer 3 specification; Core network protocols; Stage 3"" Mobile radio interface Layer 3 specification; supplementary services specification; Formats and coding

General Information

Charging principles (Release 5)

/32.205/ 3rd Generation Technical Specification 3G TS 32.205“Technical Specification Group Services and System Aspects;Telecommunication management; Charging management;Charging data description for the Circuit Switched (CS) domain(Release 5)

/32.005/ 3rd Generation Technical Specification 3G TS 32.005“3G call and event data for the Circuit Switched (CS) domain”

/49.031/ 3rd Generation Technical Specification 3G TS 49.031 “Technical Specification Group GSM/EDGE Radio Access Network;

Location Services (LCS); Base Station System Application PartLCS Extension (BSSAP-LE) (Release 5)”

/CAUS/ CatalogP30308-X2200-S321-**-7622D900: Mapping of causesVersion CS2.1

/E.164/ "Operating, numbering, routing and mobile services - International operation –Numbering plan of the international telephone service“ITU-T Recommendation E.164

/IAC/ DescriptionP30308-A7628-A134-**-7617Common IACHASTA Description, CS2.xBased on Meters (IACMET)Based on Tickets (IACAMA)

/Q.763/ "Formats and Codes of the ISDN USER PART OFSIGNALLING SYSTEM No. 7"ITU-T Recommendation Q.763

/X.208/ "Specification of Abstract Syntax Notation One (ASN.1)"CCITT Blue Book, Volume VIII, Fascicle VIII.4, 1989

/X.209/ "Specification of Basic Encoding Rules for AbstractSyntax Notation One (ASN.1)" CCITT Blue Book, VolumeVIII, Fascicle VIII.4, 1989

/CH-DB/ DescriptionP30308-A0113-A053-**-7618CHARGING DATABASE FOR SR8 - CS3.0 COMMON

/MCR/ DescriptionP30308-A3078-A053-**-7618

General Information

D900/PCS1900: Charging in MSC, Version CS3.0 Common

/IN/ DescriptionP30308-A7203-A053-**-7618D900/PCS1900: Charging of IN Services in MSC, Version CS3.0 Common

/TPD/ Technical Project DataSales Feature List

/TOOLS/ Siemens Intranet ICN CA MS E Berlin Toolpage - http://camse.bln.icn.siemens.de/-> ICM N MC E-> Projekte MS EE-Tools -> CCD

/GDCS_BASIC_LM1/ LM Functional Specification Level 1LM 43237, General Data Collection Service - BasicsCS 2.0P30309-A1330-A030-**-76J1

/GDCS_USER_LM1/ LM Functional Specification Level 1LM 43238, General Data Collection Service - User ChargingCS 2.0P30309-A1331-A030-**-76J1

/GDCS_BASIC_LM2/ LM Functional Specification Level 2LM 43237, General Data Collection Service (GDCS) - BasicsCS2.0P30309-A1330-A030-02-76H1

/GDCS_USER_LM2/ LM Functional Specification Level 2LM 43238, Usage of General Data Collection Service (GDCS) for Application ChargingCS2.0P30309-A1331-A030-02-76H1

/Simple_Ticket_LM1/ LM Functional Specification Level 1LM 45558,Simple Ticket layout Administration- SGSN/ MSC CS 3.0P30309-A2390-A153-**-76J1

/Simple_Ticket_LM2/ LM Functional Specification Level 2LM 45558,Simple Ticket layout Administration- SGSN/ MSCCS 3.0P30309-A2390-A153-**-76H1

0.5 Glossary and Abbreviations

GMSC: Gateway Mobile Services switching Center

"GMSC" in this document refers to the interrogating MSC. It is not required that the

GMSC is also a port for direct PLMN/PSTN interconnections, although this is the case

for incoming calls in most of the PLMN's.

General Information

VMSC: Visitor Mobile Services switching Center

ISC: International Switching Center

General Information

TBCD-string: Technical BCD coded digits

The octet string contains the digits 0 to F, two digits per octet.

Bit 4 to 1 of octet n encoding digit 2(n-1)+1, Bit 5 to 8 of octet n encoding digit 2n, bit 8

being most significant bit.

e.g. number = 12345 stored in following order :

2143F5FFFF... ( FF... only for fixed length)

network option:

Network operator choice between different options applicable for a certain feature or feature aspect.

Unless otherwise specified, the required administration of a network option is minimal at system installation time (One-time administration).

In some cases, administration of a network option can be done during normal system operation (Unrestricted administration).

One-time administration:

The administration of the network option is done by the supplier at system installation time.

Unrestricted administration:

The administration of the network option is done by the network operator during normal system operation (i.e. via MML).

General Information

AAL2 ATM Adaptation Layer Type 2ABC Administration and Billing CenterAoC SS: Advice of ChargeAMSC Anchor Mobile Switching CenterASCI Advanced Speech Call ItemBA Basic AccessBCIE Bearer Capability Information ElementBIC SS: Barring of Incoming CallsBOC SS: Barring of Outgoing CallsCAC Carrier Access CodeCAI Charge Advice InfoCAMEL Customised Applications Mobile network Enhanced LogicCCBS Call Completion to Busy SubscriberCCBS Call Completion to Busy SubscriberCDR Charging Data RecordCFNRc SS: Call Forwarding on Mobile Subscriber Not ReachableCFNRy SS: Call Forwarding on No ReplyCF SS: Call ForwardingCFC SS: Call Forwarding ConditionalCFU SS: Call Forwarding UnconditionalCH SS: Call HoldChaSer Charging Service CLIP SS: Calling Line Identification PresentationCLIR SS: Calling Line Identification RestrictionCPH Call Party HandlingCRN Call Reference NumberCSI CAMEL Subscription InformationCTR Connect To ResourceCUG SS: Closed User GroupCW SS: Call WaitingDA Direct AccessDAOC DA Originating CallDATC DA Terminating CallD_CSI Dialled CAMEL Subcription InformationDN Directory NumberDPPS Data Postprocessing SystemDRC Distance Related ChargingECT Emergency Call TraceEDP Event Detection PointeMLPP Enhanced Multi Level Preemption and PrecedenceE-OTD Enhanced Observed Time DifferenceESRK Emergency Services Routing Key ETC Establish Temporary ConnectionFCI Furnish Charge Information (IN operation)FFD Free Format DataFTN ForwardedToNumberFTP File Transfer Protocol GDC General Data CollectorGDCS General Data Collector ServiceGMLC Gateway Mobile Location Center

General Information

GPS Global Positioning SystemGSM Global System for Mobile communicationgsmSCF GSM Service Control FunctiongsmSSF GSM Service Switching FunctionHOTOP Hot OperationHSCSD High Speed Circuit Switched DataIACHASTA InterAdministration CHArging and STAtisticIACTRA InterAdministrative Charging via TRAnsit recordsICA Initiate Call AttemptIMSI International Mobile Subscriber IdentityIN Intelligent NetworkIP Intelligent PeripheryITR IMSI TraceLSN Line Service NumberLCS Location ServicesLine Service NumberMAP Mobile Application PartMCR Mobile Call RecordMCRI Mobile Call Record ImmediatelyMMC Mobile Mobile CallMML Man Machine LanguageMOC Mobile Originated CallMP Main ProcessorMPTY SS: Multi Party ServiceMS Mobile StationMSC Mobile Switching CenterMSISDN Mobile Subscriber ISDN numberMTC Mobile Terminated CallNIP Network Identifier PrefixO_CSI Originating CAMEL Subscribtion Information (TDP12)OCI Operator Controlled InputOP OperationORECF Optimal Routing Early Call ForwardingORLCF Optimal Routing Late Call ForwardingORMMC Optimal Routing Mobile Mobile CallPAD Package Assembler/DisassemblerPA Primary AccessPABX Private Automatic Branch ExchangePBX Private Branch ExchangePIC Preferred Interexchange CarrierPLMN Public Land Mobile NetworkPP Point to pointRCF Reason for Call FailureRNC Radio Network ControllerRMSC Relay Mobile Switching CenterSCCP Signalling Connection Control PartSCI Subscriber Controlled InputSCI Send Charging Information (SINAP Message)SCF Service Control FunctionSCP Service Control PointSM MO Short Message Mobile OriginatedSM MT Short Message Mobile Terminated

General Information

SMS Short Message ServiceSMS-GMSC Gateway MSC (for Short Message Service)SMS-IWMSC Interworking MSC (for Short Message Service)SMS-SC Service Center (for Short Message Service)SPC Signalling Point CodeSS Supplementary ServiceSSF Service Switching FunctionSUB SubscriberTCAP Transaction Capability Application PartT_CSI Terminating Camel Subscription Information (TDP12)VT_CSI Visited Terminating Camel Subscription Information (TDP12 in VMSC)TDP Trigger Detection PointTDP3 Trigger Detection Point 3 (dialled IN service)UMTS Universal Mobile Telecommunication SystemVBS Voice Broadcast ServiceVGCS Voice Group Call ServiceVGS Voice Group ServiceVPLMN Visited PLMN

0.6 Keyword / Descriptor

Billing Records, Description of Charging Client Records

General Information

0.7 List of Figures and Tables

Error! No table of figures entries found.

Table 1: History...............................................................................................................................7Table 2: History of new Features.....................................................................................................9Table 3: History of other Changes.................................................................................................10Table 4: History of changes from document Review....................................................................10Table 5: History of changes from FT2...........................................................................................11Table 6: History of changes from PI..............................................................................................11Table 7: Differences in Charging between ChaSer and GDC.......................................................28Table 8: Administration of CDR layout in CS3.0 for CP and MP................................................29Table 9: Options for file buffer attributes of MCR records...........................................................31Table 10: Options for file attributes of MCR records....................................................................31Table 11: Choosing of storage method..........................................................................................33Table 12: Options for file buffer attributes of ITR records...........................................................36Table 13: Options for file attributes of ITR records......................................................................36Table 14: Billing record tag for MCR and ITR..........................................................................37Table 15: General MCR and ITR billing record contents.........................................................40Table 16: MOC record..................................................................................................................47Table 17: MODPAD record..........................................................................................................49Table 18: EMY record...................................................................................................................51Table 19: MTC record...................................................................................................................53Table 20: ROA record...................................................................................................................55Table 21: CFU record....................................................................................................................58Table 22: CFC record....................................................................................................................61Table 23: SCI record.....................................................................................................................63Table 24: TRANSIT record..........................................................................................................65Table 25: SMSMT record.............................................................................................................66Table 26: SMSMO record.............................................................................................................68Table 27: PABXOG record...........................................................................................................70Table 28: PABXIC record.............................................................................................................72Table 29: ECT record....................................................................................................................73Table 30: MOCATT record..........................................................................................................75Table 31: ROAATT record...........................................................................................................77Table 32: EMYATT record..........................................................................................................79Table 33: MTCATT record..........................................................................................................81Table 34: CFUATT record............................................................................................................83Table 35: CFCATT record............................................................................................................85Table 36: MOCTRAC record.......................................................................................................88Table 37: MTCTRAC record.......................................................................................................90Table 38: SMSTTRAC record......................................................................................................91Table 39: SMSOTRAC record.....................................................................................................93

Billing Record Structure

1 Billing Record Structure

Records

───────────────────── physical record (R) ────────────────── ─── L1 ────── L2 ── ──── Ln ── ┌─┬─┬────────┬─┬─┬────────┬──────//──────┬─┬─┬────────┬──────────┐ │T│L│ │T│L│ │ │T│L│ │ │ │A│E│ │A│E│ │ . . │A│E│ │ fillers │ │G│N│ │G│N│ │ │G│N│ │ │ ─────┴─┴─┴────────┴─┴─┴────────┴──────//──────┴─┴─┴────────┴──────────┴──────── │ 1 logical │ record ─

The physical record contains one or more (n) logical records with variable lengths (Li). The physical record has a fixed size (R). It is filled with logical records until there is no more room to add the next record. The rest of the fixed size physical record will then be filled with fillers.

Blocks (tape only)

(a*R) bytes (b*R) bytes ─────────────────────── ─────────────────── ╓───┬───┬───┬─────────┬───╥───────//───╥───┬───┬─────────┬───╖ ║ │ │ │ │ ║ ║ │ │ │ ║ ║ │ │ │ ... │ ║ . . ║ │ │ ... │ ║ ║ │ │ │ │ ║ ║ │ │ │ ║ ─────╨───┴───┴───┴─────────┴───╨───────//───╨───┴───┴─────────┴───╨──────── ─ 1 physical record └─ start of first block │ └ start of last block │ end of first block ────┘ end of last block ──┘

The block size of the destination file can be entered and changed by MML. The entered block size normally is a multiple of the physical record size with a block size equal to the physical record size as a minimum.

The system will use the highest possible block size which is a multiple of the physical record size with the entered block size as the upper limit (Bi=a*R).

The last block will be limited to the useful information only, i.e. it will have a length which is the sum of the available physical records. This is also the case when the file only contains one block.

The last block is specified as Bl = b * R with 1 <= b <= a.

1.1 Some explanations to the ASN.1 Encoding rules

Encoding of a data value consists of 4 components (in correct order) :

identifier octets

length octets

contents octets

end-of-contents octets (not supported for billing applications)


1.1.1 Encoding of the Tag

The identifier octets encode the ASN.1 tag of the data value. Two possibilities exist:

1. single octet encoding for tag numbers from 0 to 30 (inclusive)

8 7 6 5 4 3 2 1

+-------+---+-------------------¦ 1 ¦ CLASS ¦P/C¦ NUMBER of TAG ¦ +-------------------------------+

Bits 8-7: Class identifier: +----------------------------+ ¦ Bit: 8 7 ¦ +----------------------------¦ ¦ Universal 0 0 ¦ ¦ Application 0 1 ¦ ¦ Context-specific 1 0 ¦ ¦ Private 1 1 ¦ +----------------------------+ Bit 6 : Primitive (0) or Constructed (1) Bits 5-1: binary integer with bit 5 as msb

2. Use of a leading octet for tag numbers bigger than or equal to 31

The leading octet is encoded as follows:

8 7 6 5 4 3 2 1 +-------+---+---+---+---+---+---¦ 1 ¦ CLASS ¦P/C¦ 1 ¦ 1 ¦ 1 ¦ 1 ¦ 1 ¦ +-------------------------------+

Bits 8-7: Class identifier as for single octet id Bit 6 : Primitive (0) or Constructed (1) Bits 5-1: all bits set to 1


Subsequent octets are encoded as:

8 7 6 5 4 3 2 1 +---+---------------------------¦ first 2 ¦ 1 ¦ NUMBER of TAG (msb) ¦ subsequent +-------------------------------¦ . . . . +-------------------------------¦ last ¦ 0 ¦ NUMBER of TAG (lsb) ¦ subsequent +-------------------------------+

Bits 8 : set to 1 in all non-last subsequent octets Bits 7-1: Bits 7-1 of all subsequent octets encoded as a binary integer equal to the tag number with bit 7 of the first subsequent octet as most significant bit. Note: Only one subsequent octet is supported (Tag values<128)

Classes of tags

The data items in the billing records are tagged in the following way:

ASN.1 universal tagged: u(x)

ASN.1 application wide tagged: a(x)

ASN.1 context specific tagged: c(x)

ASN.1 private tagged: p(x)

The universal tagging is applied per default. The universal tag numbers correlate with the type of the data value encoded.

Tag number data type

u(1) booleanu(2) integeru(3) bit stringu(4) octet stringu(10) enumerated typesu(16) sequence / sequence ofu(17) set / set ofu(22) IA5 string


Examples:

recordType ::= p(2) IMPLICIT INTEGER

The tag value (2) of the above definition is represented by a single octet identifier:

8 7 6 5 4 3 2 1 +-------+---+-------------------¦ 1 ¦ 1 1 ¦ 0 ¦ 0 0 0 1 0 ¦ +-------------------------------+

Bits 8-7: Class identifier: Private Bit 6 : Primitive (0) Bits 5-1: Tag number: binary integer decimal '2'

The hex representation of the tag is 'C2'.

incTgTCompBlock ::= p(33) IMPLICIT SEQUENCE {tgrpName,cicIc}

The tag value (33) of the above definition is represented by the leading octet followed by one subsequent octet:

The leading octet:

8 7 6 5 4 3 2 1 +-------+---+-------------------¦ 1 ¦ 1 1 ¦ 1 ¦ 1 1 1 1 1 ¦ +-------------------------------+

Bits 8-7: Class identifier : Private Bit 6 : Constructed (1) Bits 5-1: all bits set to 1

There is one subsequent octet encoded as:

8 7 6 5 4 3 2 1

+---+---------------------------¦ ¦ 0 ¦ 0 1 0 0 0 0 1 ¦ +-------------------------------+

Bit 8 : set to 0 (last subsequent octet) Bits 7-1: Tag number: binary integer decimal '33'

The hex representation of the tag is 'FF 21'


1.1.2 Encoding of the length

The length octets encode the length of the following content of the data item. Three possibilities exist in ASN.1: short, long and indefinite. The indefinite variant is not supported and that is why it is not covered by this explanation.

1. short length encoding for length from 0 to 127 (inclusive)

8 7 6 5 4 3 2 1 +-------------------------------¦ 1 ¦ 0 L L L L L L L ¦ +-------------------------------+

LLLLLLL represents the length of the content

2. long length encoding for length > 127

8 7 6 5 4 3 2 1 +---+---------------------------¦ 1 ¦ 1 ¦ 0 < n < 127 ¦ +-------------------------------+ +-------------------------------¦ 2 ¦ L L L L L L L L ¦ +-------------------------------+ ... +-------------------------------¦ n+1¦ L L L L L L L L ¦ +-------------------------------+

LLLLLLLL represents the length of the content


1.1.3 Encoding of the content

The numbering of bits within one octet and the encoding of a binary value in an octet structure can be found in the following figure:

8 7 6 5 4 3 2 1

+-------------------------------¦ ¦ most significant byte ¦ octet 1 +-------------------------------¦ ¦ ¦ octet 2 +-------------------------------¦ . . . . +-------------------------------¦ ¦ least significant byte ¦ octet n +-------------------------------+

bit 8 of octet 1 is the most significant bit (msb)

bit 1 of octet n is the least significant bit (lsb)

In this document, the above rule is followed as much as possible. Exceptions can occur due to:

content definition is copied from a standard (e.g. GSM TS) or

overruling of 'Basic Encoding Rules' (BER) /X.209/ by customer requirements.

In this case the alternative encoding is fully described.

In some cases a primitive parameter that contains an integer value can be encoded using a fixed length. But its content is still an integer value. For example the callDuration would be encoded acc. ASN.1 as INTEGER (selecting coding a). So value 0 would be encoded as H'00, value 127 as H'7F and from 128 on in kind of H'0080. If coding b) would be selected, a fixed length of two bytes would always be encoded: H'0000, H'007F and H'0080. Be aware that thus the given default value (H'FF) will be encoded as H'00FF (both coding a and b).

1.2 Differences in the Charging behaviour beetween ChaSer and GDC

In CS2.1 the new Charging concept for the MP (GDCS General Data Collection System, see references /GDCS_xxxxx/) was developed in parallel to the existing Charging concept with the ChaSer. The goal is to replace the ChaSer by the GDCS in CS4.0. Some minor functional improvement and differences in the Charging behaviour beetween ChaSer and GDCS are listed below:

#Affected

parametersCall Scenario

Chaser Behaviour

GDCS Behaviour Remarks

1

tgrpNameOgcicOg

Attempt tickets after CF announcements, the call is released before routing to FTN is started.

The CF attempt ticket contains announcement specific outgoing trunk data.

The CF attempt ticket does not contain announcement specific outgoing trunk data.

In case of routing to a FTN, the outgoing trunk data will be overwritten at routing time.

2 ROA ticket T-CSI dialog with MTC of Bsub; follow-on call (EDP-R) to another

The ROA ticket will be continued after MTC release.

The ROA ticket will be closed after MTC release i.e. after the ROA leg is


destination after Bsub release

closed. The ROA ticket is of the RecordType 'singleType'.

3

servedPartyotherParty

Multinumbering (multiple MSISDN)

The differences for Served Party, Other Party, etc. in the ROA, MTC tickets or in case of Call Forwarding will be listed in the Multinumbering feature section of the CCD Description part /MCR/.

4

locationAreaCodecellIDAbscIDlocationNumber

CFNRc(‚no paging response’)

The ChaSer enters the location related values into the CF tickets which are taken from the VLR database and not from the paging response due to the fact that paging was not successful.

The GDCS does not enter the values into the CF tickets, because the paging response was not successful when the call was carried out.

The ChaSer writes the values from the last location update into the record, which may be close to the values valid for the time of the call, but this is only a probability - not certain.

5

basicServicetransactionIdentificationtransmissionMode

Call Forwarding:- CFU - and CFC before setup

to MS i.e. CFNRc [‚IMSI detach’ and ‚no paging response’], CFB [NDUB and MDUB]

- CFB [MDUB] *

where CF-MSC = VMSC of forwarded-to subscriber

If certain parameters are available in the VMSC of the forwarded-to subscriber which are not available during CF handling, the Chaser provides these parameters also in the CF ticket for the forwarding subscriber. Furthermore, parameters being available during CF handling are overwritten by the ones being available from the VMSC of the forwarded-to subscriber.

The GDCS strictly separates all call legs (i.e. forwarding leg and following MTC leg, or one forwarding leg and next forwarding leg). Therefore all information from a particular leg is not provided in the ticket(s) for any preceding leg(s).

The forwarding subscriber must not be charged for any service chosen by the forwarded-to subscriber as the forwarding subscriber cannot influence them. Furthermore, the presence of the MTC leg of the forwarded-to subscriber in the CF-MSC is pure chance depending of the roaming scenario.The transactionIdentifier always relates to one BSSAP transaction i.e. it relates to one particular call leg only.

Table 7: Differences in Charging between ChaSer and GDC

* In case of CFB[MDUB], the MSC sends a message DT1(SET_UP) to the MS which does contain the transactionIdentification and might contain proposed values for the service (basicService, transmissionMode). Due to MDUB the MS responds with DT1(DISC) i.e. the transaction is not being established. Because of the unsuccessful establishment of the transaction, the corresponding data is not collected. This does also apply for the transactionIdentification although the MSC assigned it before the setup attempt.

1.3 Differences in the Administration of the Charging Client Records (CDRs) on CP and MP

In CS3.0 a new handling of the administration of the Charging ticket layout for CDRs is introduced with LM 45558 – “Simple Ticket Layout Administration” (see /Simple_Ticket_LM1/2/). Since CS3.0 the administration of the Charging Client Records (CDRs) is separate on the CP and on the MP:

on the CP, the administration of CDR layouts is still done by means of MML administration commands (BILLREC command group).

on the MP, the administration of CDR layouts is done via a text based configuration file, which is copied with FTP to the disc of the MP:OAM and is activated with the Q3 command ACT MCHRGCONFF. The syntax of this configuration file is like the CP MML and can be still generated from the CCD/PCD by means of the CCD tool.


Please note that from CS3.0 on all new record fields are only implemented in the GDC on the MP and are not supported and not administrable on the CP. Therefore in CS3.0 on the CP only a CS2.1-version of the CDR database (BICOM) can be used. The default Charging configuration is the usage of the GDC and therefore a CDR database on the CP should only be used for the fallback to CP storage in case of major problems on the MP (please refer to /CH-DB/).

Exception: The Trailer record RECLAY1 (LM46826) was implemented as a change request for CS2.1 per patch and was contained in the common CDR database for the CP and MP, which was administered by MML via the CP. The Trailer Record functionality is only available on the MP and therefore since CS3.0 the Trailer RECLAY1 cannot be administered on the CP and must be deleted from the CS2.1-database for an administration in CS3.0 on the CP.

The following table summarizes the steps to create the CDR databases in CS3.0:

CS3.0

CDR database on:

generate from CCD/PCD:

use CCD/PCD Tooling:

Exception: Administration:

CP CCD/PCD CS2.1 CS2.1 No Trailer Record!

BILLREC command group

MP CCD/PCD CS3.0 CS3.0 Config file activation on the

MP:OAM via Q3: ACT

MCHRGCONFF

Table 8: Administration of CDR layout in CS3.0 for CP and MP

MCR and ITR: CALL / EVENT RECORDS

2 MCR and ITR: CALL / EVENT RECORDS

2.1 SELECTED OPTIONS

The tables below show the available 'network options' for record encoding and transfer.

2.1.1 Options for Buffer / File Attributes for MCR records

These options are used to generate the storage device inside the switch for client records as described below.

Since SR9 (CS1) it is possible to select between the classical storage of Charging data on the CP-disk or the new storage device MP-disk (introduced with new signalling controller SSNC). With the introduction of the GDCS in CS2.1 only the storage on MP is possible.

The storage device is directly coupled with the transfer protocol that is used. In case of the classic CP-disk the transfer is done via X.25 using FTAM. In case of the MP-disk the new Ethernet link has to be used where FTP via TCP/IP is the transfer protocol.

When storing charging data at the CP-disk the cyclic file format known from former releases will be used. At the MP this format is not supported. Instead a new, more flexible format called SAM file array (SAMAR) is introduced that will be used for storage of charging data. This file format is identical to the one used in MP based packet switched Network Entities (e.g. GPRS SGSN).

The tables below give a common solution to select parameters for both selections of data storage.

Note1: in case of MP storage it is required, that the SAMAR is arranged before the buffer feature is activated. The correct sequence of administration actions is guaranteed by using the CCD tool.

Note2: some lines of the tables are only used for one of the storage type; in these cases a remark is added in the 1st column. Other lines can never be changed for circuit switched SW lines. They are only present for display of default values and for compatibility reasons with table documents for packet switched SW lines. Theses lines are resisted to entries in their 'define' column.

Note3: for dimensioning local storage file it must be considered that Call Data Records have an average size of about 0,5-1kByte, independently of the resulting client ticket size.


switching node option range default defineaccUserBufferbufferTime (in min) (3) 0..60 0 0dataType MCR MCR MCRsamarId (5) IA.ICMCR or n/a n/a IA.ICMCRfiller(former:physical filler value)

H'00 .. H'FF H'FF H'FF

Table 9: Options for file buffer attributes of MCR records

switching node option range default definefileName (= samarId) IA.ICMCR IA.ICMCR IA.ICMCRnumberOfFiles (4) (MP storage only)

2 .. 200 10 10

fileSize (in Mbyte) (4) 1 .. 500 20 20fileRecordForm fix fix fixfileRecordSize (in kByte) (depends on fileRecordForm)

8 (6) 8 8

retentionPeriod (in days)(CP storage only)

0 .. 36526 0 0

transferMode(MP storage only)

one(FileView) / multiple(FileView)

multiple one

copySize (N*fileRecordSize) 1..N 1 1maxCopySize(4)

(oneFileView or CP storage only) numberOfFiles * fileSize - 200

safetyCopiesRequired 1 .. 3 1 1alarmThreshold (in %) upGrade / downGradealarmThresholdMinor 0 .. 98 / 0 .. 97 (1) 55 / 50 55 / 50alarmThresholdMajor 0 .. 99 / 0 .. 98 (1) 75 / 70 75 / 70alarmThresholdCritical 0 .. 100 / 0 .. 99 (1) 95 / 90 95 / 90

destinationRetentionPeriod(CP storage only)

0 .. 65535 0 0

logicalRecordForm(2) variable / fix variable variablelogicalFillerValue H'00 .. H'FF H'00 H'00logicalRecordSize(fixed logical record size)

3 .. 2048 or n/a n/a

physicalRecordSize 3... 16384 2048 2048

Table 10: Options for file attributes of MCR records

Notes:(1) no one or both must be zero, if value 0 / 0 is entered then the alarmAction is set to “noalarm”, in all other cases upgrade>downgrade and alarmThresholdMinor-upGrade< alarmThresholdMajor-downGrade, alarmThresholdMajor-upGrade< alarmThresholdCritical-downGrade(2) subsequent values are only relevant for fix format (3) if 0 is used no forced storage of buffer content is done; in this case after every 5 min it is checked if a certain limit of fill grade is overrun, and only then this part of the buffer is saved to disk(4) both values must correspond to the available disk space(5) if samarID is entered the value is taken for parameter FILEAR in MML command ACT IAFEAT; no entry means: storage on cyclic CP disk file is selected (refer also to [SSNC_SFD])(6) value is valid for the collection on CP and for the GDC with collection and formatting on the MP.


All greyed lines are not yet supported by CCD tool generation and should be compared against used parameters in the project MML command files according relations described below. Q.3 object generation is supported also for greyed lines.


The following table gives an overview about the necessary steps to realize the desired storage method. The commands must be entered in the following sequence:

Command Storage on CP ChaSer

Storage on MP ChaSer

Storage on MP GDC

SETFGRPATT a1 - -

CR SAMAR - a2 a2

ACT MCHRGCONFF - a3 a3

ACTBILLREC b - -

ACTIAFEAT c1 c2 -

MODIAFEAT (only if bufferTime >0 was entered)

d d -

Table 11: Choosing of storage method

From the table entries following administration data must be generated:

a1) storage on CP -> if no FILEAR is entered in c1) or c2)

Note: This command is only allowed in installation mode.

SET FGRPATT:FRGP=<fileName>[, PRNAME=MRFOR][, COPATT=<copySize>*<fileRecordSize>*<1024> [-<destinationRetentionPeriod>][, RETPER=<retentionPeriod>][, SAFCOP=<safetyCopiesRequired>][, THRU=<aT1uG>-<aT2uG>-<aT3uG>][, THRD=<aT1dG>-<aT2dG>-<aT3dG>][, THRF=<aT1stat>-<aT2stat>-<aT3stat>][, MAXCOPLE=<maxCopySize>];

or

a2) storage on MP ->if a samarId is entered in Table 9:

This Q3-Command must be entered on MP. The command is available in the generated <FileNAME>.nsi file if a samarID was entered in table “ Options for file buffer attributes of MCR records.

M-CREATE REQUEST ( INVOKE IDENTIFIER 0, MANAGED OBJECT CLASS samfileArray, MANAGED OBJECT INSTANCE { samarID = "<samarId>" }, ATTRIBUTE LIST { samarID "<samarId>", noOfFiles <numberOfFiles>, fileSize <fileSize>, fileRecordForm <fileRecordForm>, transMode <transferMode>, maxCopySize <maxCopySize>,


safetyCopies <safetyCopiesRequired>, recordSize <fileRecordSize>*<1024>, alarmThresholdMinor { downgrade <numberOfFiles>*<aT1dG>%, upgrade <numberOfFiles>*<aT1uG>% }, alarmThresholdMajor { downgrade <numberOfFiles>*<aT2dG>%, upgrade <numberOfFiles>*<aT2uG>% }, alarmThresholdCritical { downgrade <numberOfFiles>*<aT3dG>%, upgrade <numberOfFiles>*<aT3uG>% }, alarmActionMinor aT1stat, alarmActionMajor aT2stat, alarmActionCritical aT3stat })

where aT<n>stat can be ALARM or NOALARM

a3) This command must be executed on the MP to activate the CDR layout configuration file. The CDR layout configuration file must be first transferred to the MP.OAM via FTP.

ACTMCHRGCONFF: Config. file name="xxxxx"

b) activation of billing records

Note: This command is only allowed in installation mode.

ACT BILLREC:FILE=<fileName>,RECFORM=<logicalRecordFormat>, RECSIZE=<physicalRecordSize>[-<logicalRecordSize>],FILLER=<filler>[-<logicalFillerValue>];

c) choosing the storage entity

note: -this command must be entered separate

-parameter FILEAR and parameter SIZE of MML-Command are exclusive parameters

-parameter FILRECSZ is only applicable for INA-Records.

For MCR and ITR only FILRECSZ = 8192 is possible.8192 is the internal default for ACTIAFEAT and must not be entered for

ACTIAFEATcreation. For INA only 1024/2048/8192 is possible.


If you want change the value for INA-Records please note that the parameter recordSize of corresponding Q3-Command must be have the same value.

c1) if storage on CP should be done

ACT IAFEAT:TYPE=dataType[, SIZE=<fileSize*1024*1024/2048>][, FILRECSZ=<fileRecordSize>*1024];

c2) if storage on MP with ChaSer should be done

ACT IAFEAT:TYPE=dataType [, FILEAR=<samarId>][, FILRECSZ=<fileRecordSize>*1024];

d) changing the buffertime if necessary

note: -the MOD IAFEAT command is only required if a bufferTime > 0 is entered in the table

-the usage doesn´t depend from the storage method, applicable for CP or MP storage

-the command must be entered separate

MOD IAFEAT:TYPE=dataType, SAVTIMER=<bufferTime>;

The following data format is valid for transferred files:

+--------+--------+ ----+--------+- -+ ¦ PDU ¦LF¦ PDU¦ LF¦ ...PF¦ PDU ¦LF¦ ...PF¦ +------------------ --------------- -+

¦log.rec¦ ¦file record¦ ¦copy size¦

PDU Packet Data Unit (ASN.1 encoded data record)LF logical FillersPF physical Fillers

The PDU and the logical filler represent one logical record. If variable logical record format is selected, the PDU itself represents the logical record. This is the standard usage for ASN.1 decoders.One ore more logical records constitute a physical record of a size defined via FileRecordSize. The physical record format is always fixed. The physical record is used to define a new begin of a bulk of logical records in periodic distances for a possible reentry in case of errors while decoding.If no options are selected, the default values are taken.The copySize is only important in case of CP disk storage and for local file transfers via MML command TRANSFILE to define a block size for copies of the cyclic file. As real value the highest multiple value of the physical record size, less or equal to the entered copy size, will be generated.


For file transfers via remote FTAM or FTP access only the FileRecordSize is relevant. Results of a transfer will have a multiple size of this value, limited by maxCopySize.

2.1.2 Options for Buffer / File Attributes for ITR records

switching node option range default defineaccUserBufferbufferTime (in min) (3) 0..60 0 0dataType ITR ITR ITRsamarId (5) IA.ICITR or n/a n/a IA.ICITRfiller(former:physical filler value)

H'00 .. H'FF H'FF H'FF

Table 12: Options for file buffer attributes of ITR records

switching node option range default definefileName (= samarId) IA.ICITR IA.ICITR IA.ICITRnumberOfFiles (4) (MP storage only)

2 .. 200 10 10

fileSize (in Mbyte) (4) 1 .. 500 20 20fileRecordForm fix fix fixfileRecordSize (in kByte)(depends on fileRecordForm)

8 8 8

retentionPeriod(CP storage only)

0 .. 36526 0 0

transferMode(MP storage only)

one(FileView) / multiple(FileView)

multiple one

copySize (N*fileRecordSize) 1..N 1 1maxCopySize(4)

(oneFileView or CP storage only) numberOfFiles * fileSize - 200

safetyCopiesRequired 1 .. 3 1 1alarmThreshold (in %) upGrade / downGradealarmThresholdMinor 0 .. 98 / 0 .. 97 (1) 55 / 50 55 / 50alarmThresholdMajor 0 .. 99 / 0 .. 98 (1) 75 / 70 75 / 70alarmThresholdCritical 0 .. 100 / 0 .. 99 (1) 95 / 90 95 / 90

destinationRetentionPeriod(CP storage only)

0 .. 65535 0 0

logicalRecordForm(2) variable / fix variable variablelogicalFillerValue H'00 .. H'FF H'00 H'00logicalRecordSize(former:fixed logical record

size)

3 .. 2048 or n/a n/a

physicalRecordSize 3... 16384 2048 2048

Table 13: Options for file attributes of ITR records


2.2 RECORD CONTENTS

2.2.1 Billing record tag

default define valuebilling record tag u(16) p(1) E1

Table 14: Billing record tag for MCR and ITR

2.2.2 General Billing record contents

All the record layouts described in this document contain a default layout (including tags, lengths etc.) of each record and give additionally the possibility to define a project specific layout within a table format.

Note: The given defaults for the tags are definitions for a universal tagging; this tagging may lead to inconsistencies if not adapted for a project.

Note: If it is allowed to enter a length (no ‘-‘ in column length(define)) then there can be entered a single value or a range (x..y). In both cases the value of entered lengths must be in the range give in column length(default). If in column length(default) is given a single value, then the defined fixed output length is generated. If a range is given in length(default) or length(define) the length of output will be in this range. For further information refer to /TOOLS/, Filling rules.

If the length is not possible to be defined, then the variable or fixed default length will be generated.

Therefore all record layouts described here contain all possible fields in the records.

(A legend for the table is given below.)


elementavailablecoding

availability

tag length 10) filler default value

range define define default define value default define default definetraceType - O u(4) p(99) DF63 1 - H'00 H'00traceReference - O u(4) p(98) DF62 1..2 H'FF H'FFrecordType a / b a M u(2) p(2) C2 1 - H'00 H'00callTransactionType a / b / c c M u(2) p(3) C3 1 - H'00 H'00servedPartyIdentity -

servedOtherNumber - O u(4) p(40) DF28 2..17 11 H'FF H'80servedMobileNumber - M u(16) p(39) FF27

servedIMSI 9) - O u(4) p(6) C6 1..8 H'FF H'FFservedMSIsdn 9) - O u(4) p(7) C7 1..8 H'FF H'FFservedIMEI - O u(4) p(8) C8 8 - H'FF H'FFservedMSRN 9) - O u(4) p(29) DD 1..8 H'FF H'FFpABXNumber - u(4) 2..17 H'FF H'FF

chargingtimeData - M u(16) p(13) EDstartOfChargingdate - M u(4) p(19) D3 3 - H'00 H'00startOfChargingtime - M u(17) p(20) F4 1..6

timeStamp - M u(4) p(28) DC 3 - H'00 H'00callDuration a / b 12) b O u(2) p(17) D1 1..3 - H'00 H'00

timeQuality - O u(2) p(4) C4 1 - H'00 H'00transactionIdentification - O u(4) p(5) C5 1 - H'00 1)

servedSubscriberLocation - u(4) 2..17 H’FF H’FFotherPartyLocation u(4) 2..17 H’FF H’FFotherParty -

otherPartyShortNumber a / b a O u(4) p(45) DF2D 2..17 6 H'FF H'80otherParty3a - O u(4) p(52) DF34 3..18 12 H'FF H’80otherPartyLongNumber - O u(4) p(44) DF2C 2..17 11 H'FF H’80otherPartySMS - O u(4) p(54) DF36 3..18 12 H’FF H'FF

otherPartySequence - u(16) dialledOtherParty - u(4) 2..17 H'FF H’80translatedOtherParty - u(4) 2..17 H'FF H’80

otherMSRN 9) - O u(4) p(75) DF4B 1..8 8 H'FF H'FFcallTransferThirdParty - u(4) 2..17 H'FF H'80carrierAccessCode - u(4) 1..3 H’FF H’FFinatIndicator - u(4) 1 - H’00 H’00origTermMscId 11) - O u(4) p(10) CA 2..3 2 H’00 H'00connectedSwitchId -

origTermBscId 11) - O u(4) p(11) CB 2..3 2 H’00 H’00dAId - O u(4) p(25) D9 1..17 12 H’FF H’FF

exchangeId - O u(22) p(30) DE 1..11 9 H’20 H’20basicService -

individualTeleserviceNumber - O u(4) p(12) CC 1 - H'00 H'00individualBearerserviceNumber - O u(4) p(14) CE 1 - H'00 H'00iSDNBasicService - O u(4) p(55) DF37 1 - H'00 H'00

transmissionMode a / b a u(4) 1 - H'00 H'00speechCode - u(4) 1 - H'00 H'00outgTgTCompBlock - O u(16) p(27) FB 13

tgrpNameOg - O u(22) 16 6 - H'20 H'20cicOg - O u(4) p(16) D0 3 - H'00 H'00biccCallInstCodeOut - u(4) 4 - H'00 H'00

causeForTermination a / b a O u(4) p(18) D2 1 - H'00 H'00reasonForTermination - O u(4) p(71) DF47 1 - H'00 H’00msClassmark - O u(4) p(21) D5 1..15 3 H'00 H'00incTgTCompBlock - O u(16) p(33) FF21 13

tgrpNameIc - O u(22) 16 6 - H'20 H'20cicIc - O u(4) p(16) D0 3 - H'00 H'00biccCallInstCodeInc - u(4) 4 - H'00 H'00

sequenceNumber a / b a O u(4) p(48) DF30 3 / 4 - H'00 H'00intermediateSequenceNumber - O u(4) p(34) DF22 1 - H'FF H'FFsupplServiceInfo - O u(16) p(23) F7

callHoldInvocCount - O u(2) p(41) DF29 1 - H’00 H’00callWaitInvocCount - O u(2) p(42) DF2A 1 - H’00 H’00sSSequenceOf - O u(16) p(43) FF2B 1..56

sSCode a / b / c - O u(4) p(9) C9 1..56 / 1 H’00 H’00sSInvocation - O u(16) p(56) FF38

sSInvocCode - O u(4) p(57) DF39 1 - H'00 H'00sSInvocSucc - O u(4) p(58) DF3A 1 - H'00 H'01sSInvocDate - O u(4) p(59) DF3B 3 - H'00 H'00



availability


range define define default define value default define default definesSInvocTime - O u(4) p(60) DF3C 3 - H'00 H'00

ussdData - O u(16) p(31) FF1FussdAccessCode - O u(4) c(1) 81 2 H'FF H'FFussdString - O u(4) c(2) 82 1..20 H'FF H'FFussdCodingScheme - O u(4) c(3) 83 1 - H'00 H'00ussdNotifyCounter - O u(4) c(4) 84 1 - H'00 H'00ussdRequestCounter - O u(4) c(5) 85 1 - H'00 H'00

msAccessRate - O u(2) p(24) D8 1 - H'00 H'00chargeAdviceInformation - O u(16) p(49) FF31 1..6

chargeAdviceInfo - chargeAdviceElement a 2) - O u(4) p(26) DA 14 - H'00 H'00aOCParameter b 2) - u(16)

e1 - u(4) 2 - H'00 H'00e2 - u(4) 2 - H'00 H'00e3 - u(4) 2 - H'00 H'00e4 - u(4) 2 - H'00 H'00e5 - u(4) 2 - H'00 H'00e6 - u(4) 2 - H'00 H'00e7 - u(4) 2 - H'00 H'00

chargingInformation - u(17) 1..6tariffInfoPack - u(16)

tariffInfo - u(4) 3 - H'00 H'00oneTimeCharge - u(4) 2 - H'00 H'00timeTariff - u(4) 3 - H'00 H'00

backwardChargingInfo - u(16) backwardChargingInfoTAX - u(4) 6 - H'FF H'00backwardChargingInfoCHT - u(4) 3 - H'FF H'00backwardChargingInfoITX - u(4) 1 - H'FF H'00backwardChargingInfoCBA - u(4) 1 - H'FF H'00

chargingPulses - u(2) 2 - H'00 H'00chargeIndicator - O u(2) p(47) DF2F 1 - H'00 H'00thirdParty - O u(4) p(32) DF20 2..17 11 H'FF H'80redirectionCounter - O u(2) p(61) DF3D 1 - H'00 H'00nMTForwardedIndicator - O u(4) p(63) DF3F 1 - H’00 H'00locationAreaCode - u(4) 2 - H'FF H'00cellId a / b / d a O u(4) p(22) D6 7/2/7 - H'FF 3)

secondCellId - u(4) 4 - H'FF H’00locationNumber - u(4) 1..8 H'FF H'FFserviceCentreAddress - O u(4) p(38) DF26 2..17 11 H'FF H'80sMTransmissionResult - O u(4) p(50) DF32 1 - H'00 H'01sMReference - O u(4) p(51) DF33 1 - H'FF H'FFprotocolIdForSMS - u(4) 1 - H'00 H'00multipleSMTransfer - O u(4) p(62) DF3E 1 - H'00 H'00hotTransferResult - O u(4) p(46) DF2E 1 - H'00 H'00subscriberCategory - O u(4) p(64) DF40 1 - H'00 H'00callReferenceNumber 5) - O u(4) p(76) DF4C 1..8 H’FF H’FFmscAddress 5) - O u(4) p(77) DF4D 1..9 H’FF H’80drcCallNumber -

drcCallId a / b 6) - u(4) 3 / 7 - H'00 H'00drcCallRN a / b 6) - u(4) 3 / 7 - H'00 H'00

drcChrgOrigin - u(4) 1 - H'00 H'00drcTariffClass - u(4) 2 - H'00 H'00chrgContainer1 - u(4) 1..32 H'00 H'00chrgContainer2 - u(4) 2 - H'00 H'00chrgContainer3 - u(4) 2 - H'00 H'00chrgContainer4 - u(4) 2 - H'00 H'00chrgContainer5 - u(4) 2 - H'00 H'00durationBeforeAnswer 7) - u(2) 1..3 - H'00 H'00recordUse 7) - u(3) 2 - H'00 H'00additionalBearerServiceInfo - u(16)

noOfUsedTrafficChannels - u(2) 1..2 - H’FF H’FFfixedNetworkUserRate - u(4) 1 - H’00 H’00channelCoding - u(10) 1 - H’FF H’FFmaximumBitRate - u(10) 1 - H’00 H’00guaranteedBitRate - u(10) 1 - H’00 H’00

rateIndication - u(4) 1 H'00 H'00identificationVGSInitiator - u(4) 2..17 H’FF H’80iMSIVGSInitiator 9) - u(4) 1..8 H’FF H’FF



availability


range define define default define value default define default defineinitiatorIndicationOfVGS - u(10) 1 - H’FF H’FFvoiceGroupServiceReference - u(2) 1..4 - H’FF H’FFnumberOfCellsInVGSGroup - u(2) 1..2 - H’FF H’FF numberOfCellsWithSuccSetup - u(2) 1..2 - H’FF H’FFnoOfDispatcherInVGSGroup - u(2) 1..2 - H’FF H’FFnoOfDispatWithSuccSetup - u(2) 1..2 - H’FF H’FFnoOfRmscsInGroup - u(2) 1..2 - H’00 H’00noOfRmscsWithSuccSetup - u(2) 1..2 - H’00 H’00speechCodeVgs - u(4) 1 - H'00 H'00usedEmlppPriority - u(4) 1 - H’00 H’00camelCommonData - u(16)

inFlag 5) - u(4) 1 - H'00 H'00timeOfCAMELLeg - u(4) 3 - H’00 H’00dateOfCAMELLeg - u(4) 3 - H’00 H’00durationOfCAMELLeg a / b 5) 12) u(2) 1..3 - H’00 H’00camelInitCfIndicator 5) - u(4) 1 - H'00 H'00chargeBandNumber a / b 5) 12) u(2) 1..3 - H'FF H'FFtransmittedZone a / b 5) 12) u(2) 1..3 - H'FF H'FFinAoC 5) - u(4) 1 - H'00 H'00termCamelRecordInVMSC - u(4) 1 - H'00 H'00

sequenceOfCamelDialogs - u(16) 1..2camelDialog - u(16)

inServiceKey a / b 5) 12) u(2) 1..4 - H'00 H'00gsmScfAddress 5) - u(4) 1..9 H’FF H’80defaultCallHandling 5) - u(4) 1 - H'00 H'00levelOfCAMELService 5) - u(3) 2 - H’00 H’00changeFlags 5) - u(3) 2 - H’00 H’00numberOfDpEncountered 5) - u(2) 1 - H’00 H’00mcrDestinationNumber a / b 5) u(4) 2..17/2..18 H'FF H'FFmcrDestinationNumberSMS - u(4) 3..18 H’FF H'FFinTransPar 5) - u(4) 1..40 H'00 H'00camelFFDataIncLeg 5) - u(4) 1..160 H’00 H’00camelFFDataIncAppendInd - u(4) 1 - H’00 H’00camelFFDataOutLeg 5) - u(4) 1..160 H’00 H’00camelFFDataOutAppendInd - u(4) 1 - H’00 H’00

partialRecordType - u(10) 1 - H’FF H’FFpartialRecordCorrelationId - u(4) 6..9 H’FF H’FFcphIndication 5) - u(10) 1 - H’00 H’00locationServiceInfo - u(16)

mlcNumber - u(4) 1..9 H’FF H’80positioningData - u(4) 2..33 H’FF H’00locationEstimate - u(4) 1..91 H’FF H’00esrkNumber - u(4) 1..5 H’FF H’FFlCSCause - u(4) 1..2 H’FF H’00lCSCauseforTermination u(4) 1..2 H’00 H’00

lCSClientType - u(10) 1 - H'FF H'FFlocationChoice

lCSRequestType - u(10) 1 - H'FF H'FFlocationEstimateType u(10) 1 - H'FF H'FFlCSMoLr u(10) 1 - H'FF H'FF

lCSSSCode - u(4) 1 - H’00 H'00lCSPriority - u(4) 1 - H'FF H'FFlCSClientIdentity u(16)

lCSClientExternalID - u(4) 2..20 H'FF H'80lCSClientDialedByMSID - u(4) 2..20 H'FF H'80lCSClientInternalID - u(10) 1 - H'FF H'FF

lCSQoS - u(4) 4 H'00 H'00privacyChoice

privacyOptionsInvoked - u(10) 1 - H'FF H'FFprivacyOverride - u(1) 1 - H'FF H'00

notificationToMSUser u(10) 1 - H’FF H’FFmeasureDuration a / b u(2) 1..3 H’00 H’00systemType - u(10) 1 - H'00 H'00optimalRoutingMmcEcf - u(4) 1 - H'00 H'00optimalRoutingLcf - u(4) 1 - H'00 H'00destByOptimalRoutingMmcEcf - u(4) 2..17 H'FF H'80

Table 15: General MCR and ITR billing record contents


Notes1) The default value is H'80 always for MTC, MTC attempt and SMS MT records. It

is H'00 for all other records and should therefore not be changed.2) These two fields are different coding of the same data (refer to the description of

the fields). The chosen coding for the project is given by the availability. 3) The default value is described in the description of the coding for this field. It

should not be changed.4) The different coding are determined by defining a length or not.5) Refer /IN/ chapter 86) The different codings are determined by the features Distance Related

Charging/General Call ID. These features and ODFEAT10 determine the real length and therefore it is recommended not to choose a fixed length. A fixed length has consequences on the counterpart only, not on the SPC.

7) Since the feature IACTRA is not released, these parameters must not be used!8) This parameter applies only for CDMA. It is element of the GSM/UMTS/PCS

CCD as a reminder only.9) Beginning with CS2.1 these fields have a variable length. To fix it to the value

from previous releases enter a value in column “length (define)”.10) Beginning with CS1.0 the column “length (define)” can now contain a range. It

must be within the predefined range from column “length (default)”. This also means, that no other value must be entered in “length (define)”, where a single entry is contained at “length (default)”.

11) The default length is 3 octets, but the length can be defined (2 or 3) according to the related SPC length in the network.

12) New homogeneous handling for all parameters with coding a/b as integer/octet string. Coding a is defined as integer with variable length (see table and parameter description), coding b is defined as octed string with fixed length (see parameter description).

For some fields the names were project specific in former releases. Therefore such fields may have new names within a special project. These names are handled as synonyms. Where this is the case one can find the synonyms in the comments for the field in the next chapter.

Legend

available coding for the range of available codings and related descriptions,refer to chapter 2.3, the chosen coding is given at 'define'

availability is the general static availability of a field in the billing records acc. ASN.1

M – mandatory


O – optional

tag refer to chapter 1

length The 'length (default)' column gives the valid range in octets of a field in case of primitive parameters and in number of appearance in case of SETOF/SEQUENCEOF structures.In some cases of different codings (e.g. callDuration) the length is given per coding and the selected coding decides which length will appear in the tickets; in this case no entry must be done at 'length (define)'.In other cases no entry at 'coding (define)' is possible (e.g. sSCode), here the entered length determines the valid coding.If a single value is given at 'length (default)', no other value must be entered at 'length (define)'.If no value is entered at 'length (define)', the value respective range from 'length (default)' is valid.

filler indicates the end of valid data in a field of fixed length; 'define' is used if another value than 'default' is required

default value is used if a field is mandatory for a certain billing record type, but no valid data are available

The length of a Billing record depends on the number of fields in the record. Some fields may be optional. Hence the record length can vary from record to record.

Therefore the ASN.1 tag and length identifier must be used to retrieve the billing records from the transport medium.

The encoding rules for tag and length are also valid for the whole record.

Explanations

available coding:

A selection has to be made for fields with different coding available. For projects using a CS2.1 preceding SW release the right coding can be found in the specification for that release. For "new" projects any coding can be taken.

availability:

The entries in this column have to be built from the related entries in the tables for the different billing records as a "sum" acc. to the following rules. These values are needed for the billing record postprocessing when receiving and disassembling the records (e.g. for a mediation function in a multivendor environment assigning the data of each billing record to objects for further processing).

rules:

enter M when M(andatory) is required for all billing record types

enter O when at least for one billing record the field is O(ptional) or M(andatory)

enter - or nothing when the field is not required at all billing record types (all other definitions are invalid)


To 'define' other than the 'default'

order of the fields in the record: re-order the general table

tags for the fields (the default values may lead to ambiguous usage): use the “tag (define)” column

lengths for the fields: use the column for “length (define)”

default values for the case that a field is mandatory: use the column for “default value (define)”.

No defaults are given for ASN.1 structures. The defaults given are only available for ASN.1 primitives.

Note: 'define' fields being already closed by “-” can not be changed! For an empty 'define' the 'default' will be taken.


2.2.3 Description of the different records

Each Billing record type will be described as a table, which comprises all possible fields of the record. For each field the availability for the billing record is defined. If the field is not required (entry at 'field required define' is 'no') the entry for availability is invalid.

The following notes are used for the comments:*) Different coding are available for these parameters - refer to the General billing

record description in 2.2.2.**) Due to introduction of a more general format for this document the names of the

ASN.1 structure and the primitives belonging to it may be changed related to the document version for the last MSC release. Especially for some projects (without a structure for those fields) the name of the primitive became here the name of the structure. So the primitive’s name is new now. But this doesn’t change the data presentation itself.

***) These parameters can occur more than one time in the record, depending on the number of tariff changes during the call.

The field sSSequenceOf in the following tables is only valid if in general table coding ‘c’ is required for sSCode.

Field required:

yes field required, availability definition is to be used

no field is to be omitted in this billing record type

Availability:

M - mandatory information must be available, values acc. to the definitions default value used in abnormal cases only

O - optional information available under certain conditions (see comment) if data are not available, the field has to be omitted

D - default value only default value available (if not wanted, use 'no' for 'field required'), in the deviation from ASN.1 this is also a mandatory field

- - if field is not required

Notation for subscribers / parties:

A-subscriber calling party.

B-subscriber called party/forwarding party.

C-subscriber forwarded-to party.


2.2.3.1 MOC - Mobile Originating Call Record

This record is generated at the VMSC of the calling party.

avail- field requiredelement ability comment range define

recordType M record type A and record type B available yes / no yescallTransactionType M *) 'MOC' or 'inCallModMoc' yes / no yesservedMobileNumber M (also synonym for servedMobileIdentity); A

subscriberyes / no yes

servedIMSI M yes / no yesservedMSIsdn M Basic MSISDN yes / no yesservedIMEI O if available yes / no yesservedMSRN D only default possible <value>/ no no

chargingtimeData M yes / no yesstartOfChargingdate M yes / no yesstartOfChargingtime M **) yes / no yes

timeStamp M ***) yes / no yescallDuration M yes / no yes

timeQuality M if insecure yes / no yestransactionIdentification M yes / no yesservedSubscriberLocation only in case of (Local) Number Portability yes / no nootherPartyLocation only in case of (Local) Number Portability yes / no nootherParty **) choice of different coding yes / no no

otherPartyShortNumber M B subscriber yes / no yesotherPartyLongNumber M **) yes / no yes

otherPartySequence yes / no nodialledOtherParty yes / no notranslatedOtherParty yes / no no

otherMSRN M MSRN of other party yes / no yescallTransferThirdParty yes / no nocarrierAccessCode if available yes / no noorigTermMscId M yes / no yesconnectedSwitchId choice of origTermBscId (or DAId) yes / no no

origTermBscId M yes / no yesexchangeId M yes / no yesbasicService choice of service types yes / no no

individualTeleserviceNumber M if basic service = teleservice yes / no yesindividualBearerserviceNumber M if basic service = bearer service yes / no yes

transmissionMode yes / no nospeechCode if a speech service was supported yes / no nooutgTgTCompBlock M yes / no yes

tgrpNameOg M yes / no yescicOg M yes / no yesbiccCallInstCodeOut in case of a AAL2 connection yes / no no

causeForTermination M in case of abnormal release *) yes / no yesreasonForTermination M system internal reason for call termination yes / no yesmsClassmark M yes / no yesincTgTCompBlock M yes / no yes

tgrpNameIc M yes / no yescicIc M yes / no yesbiccCallInstCodeInc in case of a AAL2 connection yes / no no

sequenceNumber M yes / no yesintermediateSequenceNumber M if intermediate records are generated yes / no yessupplServiceInfo M **) yes / no yes

callHoldInvocCount M yes / no yescallWaitInvocCount M yes / no yessSSequenceOf M **) sequence of sSCode yes / no yes

sSCode M *) yes / no yessSInvocation M yes / no yes

sSInvocCode M yes / no yessSInvocSucc M yes / no yessSInvocDate M yes / no yessSInvocTime M yes / no yes

msAccessRate M if basic service <> telephony yes / no yeschargeAdviceInformation M **) yes / no yes

chargeAdviceElement M ***), **) all e-parameters as octet string yes / no yesaOCParameter ***) sequence of e-parameters yes / no no



e1 yes / no noe2 yes / no noe3 yes / no noe4 yes / no noe5 yes / no noe6 yes / no noe7 yes / no no

chargingInformation yes / no notariffInfoPack ***) yes / no no

tariffInfo yes / no nooneTimeCharge yes / no notimeTariff yes / no no

backwardChargingInfo yes / no nobackwardChargingInfoTAX if available (e.g. for yes / no nobackwardChargingInfoCHT if available international yes / no nobackwardChargingInfoITX if available destinations, yes / no nobackwardChargingInfoCBA if available special services) yes / no no

chargingPulses yes / no nochargeIndicator M also synonym for chargeType yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yessecondCellId if DIRECTED RETRY is released yes / no nolocationNumber yes / no nohotTransferResult M if Hot Billing active yes / no yessubscriberCategory M yes / no yescallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no

drcCallId *) yes / no nodrcChrgOrigin DRC has to be released yes / no nodrcTariffClass DRC has to be released yes / no nochrgContainer1 if available yes / no nochrgContainer2 if available yes / no nochrgContainer3 if available yes / no nochrgContainer4 if available yes / no nochrgContainer5 if available yes / no nodurationBeforeAnswer NOT RELEASED yes / no norecordUse NOT RELEASED yes / no noadditionalBearerServiceInfo for HSCSD calls/ UMTS data services yes / no no

noOfUsedTrafficChannels yes / no nofixedNetworkUserRate yes / no nochannelCoding yes / no nomaximumBitRate yes / no noguaranteedBitRate yes / no no

rateIndication UMTS yes / no nousedEmlppPriority for eMLPP supplementary service yes / no nocamelCommonData yes / no no

inFlag if an IN service was triggered yes / no notimeOfCAMELLeg yes / no nodateOfCAMELLeg yes / no nodurationOfCAMELLeg yes / no nochargeBandNumber if received from IN service yes / no noinAoC if IN AoC data available yes / no no

sequenceOfCamelDialogs yes / no nocamelDialog yes / no no

inServiceKey if an IN service was triggered yes / no nogsmScfAddress only for IN calls triggered by CSI if available yes / no nodefaultCallHandling only for IN calls triggered by CSI if available yes / no nolevelOfCAMELService yes / no nochangeFlags yes / no nonumberOfDpEncountered yes / no nomcrDestinationNumber only for IN calls if available yes / no noinTransPar if received from IN service yes / no nocamelFFDataIncLeg free format data for incoming leg yes / no nocamelFFDataIncAppendInd yes / no nocamelFFDataOutLeg free format data for outgoing leg yes / no nocamelFFDataOutAppendInd yes / no no

partialRecordType yes / no nopartialRecordCorrelationId for correlation of partial records yes / no no



systemType UMTS indication yes / no nocphIndication in case of call party handling yes / no nooptimalRoutingMmcEcf in case of ORMMC or ORECF yes / no nodestByOptimalRoutingMmcEcf in case of ORMMC or ORECF if available yes / no no

Table 16: MOC record


2.2.3.2 MODPAD - Mobile Originating Call to dedicated PAD Access Record (not in PCS)

This record is generated at the VMSC of the calling party if dedicated PAD Access Bearer Service is detected.


recordType M record type A and record type B available yes / no yescallTransactionType M *) 'MOC', define extra value, if required yes/no/value yesservedMobileNumber M (also synonym for servedMobileIdentity); A


servedIMSI M yes / no yesservedMSIsdn M yes / no yesservedIMEI O if available yes / no yesservedMSRN D only default possible <value>/ no no



timeQuality M if insecure yes / no yestransactionIdentification M yes / no yesotherParty **) choice of different coding yes / no no

otherPartyShortNumber M B subscriber yes / no yesotherPartyLongNumber M yes / no yes


otherMSRN M MSRN of other party yes / no yescallTransferThirdParty yes / no noorigTermMscId M yes / no yesconnectedSwitchId choice of origTermBscId (or DAId) yes / no no



transmissionMode yes / no nooutgTgTCompBlock M yes / no yes






sSCode M *) yes / no yesmsAccessRate M if basic service <> telephony yes / no yeschargeAdviceInformation M **) yes / no yes

chargeAdviceElement M ***), **) all e-parameters as octet string yes / no yesaOCParameter ***) sequence of e-parameters yes / no no







chargingPulses yes / no nochargeIndicator M also synonym for chargeType yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yessecondCellId if DIRECTED RETRY is released yes / no nolocationNumber yes / no nohotTransferResult M if Hot Billing active yes / no yessubscriberCategory M yes / no yescallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no




inFlag if an IN service was triggered yes / no notimeOfCAMELLeg yes / no nodateOfCAMELLeg yes / no nodurationOfCAMELLeg yes / no no



partialRecordType yes / no nopartialRecordCorrelationId for correlation of partial records yes / no nosystemType UMTS indication yes / no nocphIndication in case of call party handling yes / no nooptimalRoutingMmcEcf in case of ORMMC or ORECF yes / no nodestByOptimalRoutingMmcEcf in case of ORMMC or ORECF if available yes / no no

Table 17: MODPAD record


2.2.3.3 EMY- Emergency Call Record (MOC/Emergency record)

This record is generated at the VMSC of the calling party if any emergency call indication is detected.


recordType M record type A and record type B available yes / no yescallTransactionType M *) 'Emergency call' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; A


servedIMSI O if SIM card used yes / no yesservedMSIsdn M yes / no yesservedIMEI O if available yes / no yesservedMSRN D only default possible <value>/ no no


timeStamp M **) yes / no yescallDuration M yes / no yes



otherPartySequence yes / no nodialledOtherParty LMN: Location Mark yes / no notranslatedOtherParty yes / no no

otherMSRN M MSRN of other party yes / no yescarrierAccessCode if available yes / no noorigTermMscId M yes / no yesconnectedSwitchId choice of origTermBscId (or DAId) yes / no no


individualTeleserviceNumber M ‘Emergency call’ or ‘Speech’ yes / no yesindividualBearerserviceNumber D only default possible <value>/ no no





sequenceNumber M yes / no yesintermediateSequenceNumber M if intermediate records are generated yes / no yessupplServiceInfo **) yes / no no

callHoldInvocCount yes / no nocallWaitInvocCount yes / no nosSSequenceOf **) sequence of SSCode yes / no no

sSCode *) yes / no nosSInvocation yes / no no

sSInvocCode yes / no nosSInvocSucc yes / no nosSInvocDate yes / no nosSInvocTime yes / no no


tariffInfo yes / no no



oneTimeCharge yes / no notimeTariff yes / no no


chargingPulses yes / no nochargeIndicator M also synonym for chargeType yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yessecondCellId if DIRECTED RETRY is released yes / no nolocationNumber yes / no nohotTransferResult M if Hot Billing active yes / no yescallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no

drcCallId *) yes / no nodrcChrgOrigin DRC has to be released yes / no nodrcTariffClass DRC has to be released yes / no nochrgContainer1 if available yes / no nochrgContainer2 if available yes / no nochrgContainer3 if available yes / no nochrgContainer4 if available yes / no nochrgContainer5 if available yes / no nodurationBeforeAnswer NOT RELEASED yes / no norecordUse NOT RELEASED yes / no nopartialRecordType yes / no nopartialRecordCorrelationId in case of partial records yes / no nosystemType UMTS indication yes / no no

Table 18: EMY record


2.2.3.4 MTC - Mobile Terminating Call Record

This record is generated at the VMSC of the called party.


recordType M record type A and record type B available yes / no yescallTransactionType M *) 'MTC' or 'inCallModMtc' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; B


servedIMSI M yes / no yesservedMSIsdn M Service MSISDN, if not present then basic

MSISDNyes / no yes

servedIMEI O if available yes / no yesservedMSRN O available if VMSC = GMSC yes / no yes




otherPartyShortNumber see description part and /MCR/ yes / no nootherParty3a M yes / no yesotherPartyLongNumber Calling party number if available **) yes / no no


callTransferThirdParty yes / no noinatIndicator yes / no noorigTermMscId M yes / no yesconnectedSwitchId choice of origTermBscId (or DAId) yes / no no












chargeAdviceElement M ***), **) all e-parameters as octet string yes / no yesaOCParameter ***)sequence of e-parameters yes / no no

e1 yes / no no



e2 yes / no noe3 yes / no noe4 yes / no noe5 yes / no noe6 yes / no noe7 yes / no no

thirdParty A subscriber if available by signalling yes / no noredirectionCounter M yes / no yesnMTForwardedIndicator M yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yessecondCellId if DIRECTED RETRY is released yes / no nolocationNumber yes / no nohotTransferResult M if Hot Billing active yes / no yescallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no

drcCallId *) yes / no nodrcCallRN *) , instead of drcCallId if Call Related Number is

releasedyes / no no

drcChrgOrigin DRC has to be released yes / no nodrcTariffClass DRC has to be released yes / no nochrgContainer2 if available yes / no nochrgContainer3 if available yes / no nochrgContainer4 if available yes / no nochrgContainer5 if available yes / no nodurationBeforeAnswer NOT RELEASED yes / no norecordUse NOT RELEASED yes / no noadditionalBearerServiceInfo for HSCSD calls/ UMTS data services yes / no no


rateIndication UMTS yes / no nousedEmlppPriority for eMLPP supplementary service yes / no nopartialRecordType yes / no nopartialRecordCorrelationId for correlation of partial records yes / no nosystemType UMTS indication yes / no nooptimalRoutingMmcEcf in case of ORMMC or ORECF yes / no no

Table 19: MTC record


2.2.3.5 ROA - Roaming Record

This record is generated at the GMSC of the called party.


recordType M record type A and record type B available yes / no yescallTransactionType M *) 'Roaming' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity

B subscriber / C subscriber after CFyes / no yes

servedIMSI M yes / no yesservedMSIsdn M yes / no yesservedIMEI D only default possible <value>/ no noservedMSRN M FTN in case of HLR detected CF

(CHCFROA active)yes / no yes



timeQuality M if insecure yes / no yestransactionIdentification D only default possible <value>/ no nootherParty **) choice of different coding yes / no no

otherPartyShortNumber A subscriber / B subscriber yes / no nootherPartyLongNumber M **) yes / no yes

otherPartySequence yes / no nodialledOtherParty after call forwarding yes / no notranslatedOtherParty yes / no no

carrierAccessCode if available yes / no noinatIndicator yes / no noorigTermMscId M yes / no yesconnectedSwitchId choice of origTermBscId (or DAId) yes / no no

origTermBscId yes / no noexchangeId M yes / no yesbasicService choice of service types yes / no no

individualTeleserviceNumber yes / no noindividualBearerserviceNumber yes / no no

transmissionMode D only default possible <value>/ no nooutgTgTCompBlock M yes / no yes


causeForTermination M in case of abnormal release *) yes / no yesreasonForTermination M system internal reason for call termination yes / no yesmsClassmark D only default possible <value>/ no noincTgTCompBlock M yes / no yes


sequenceNumber M yes / no yesintermediateSequenceNumber M if intermediate records are generated yes / no yesbackwardChargingInfo yes / no no

backwardChargingInfoTAX if available (e.g. for yes / no nobackwardChargingInfoCHT if available international yes / no nobackwardChargingInfoITX if available destinations, yes / no nobackwardChargingInfoCBA if available special services) yes / no no

chargingPulses yes / no noredirectionCounter M yes / no yesnMTForwardedIndicator M yes / no yeslocationAreaCode yes / no nocellId yes / no nolocationNumber yes / no nocallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no


releasedyes / no no



drcChrgOrigin DRC has to be released yes / no nodrcTariffClass DRC has to be released yes / no nochrgContainer2 if available yes / no nochrgContainer3 if available yes / no nochrgContainer5 if available yes / no nocamelCommonData yes / no no

inFlag if an IN service was triggered yes / no notimeOfCAMELLeg yes / no nodateOfCAMELLeg yes / no nodurationOfCAMELLeg yes / no nocamelInitCfIndicator yes / no notransmittedZone if received from IN service yes / no no



durationBeforeAnswer NOT RELEASED yes / no norecordUse NOT RELEASED yes / no nopartialRecordType yes / no nopartialRecordCorrelationId for correlation of partial records yes / no nocphIndication in case of call party handling yes / no nooptimalRoutingMmcEcf in case of ORMMC or ORECF yes / no nooptimalRoutingLcf in case of late call forwarding yes / no no

Table 20: ROA record


2.2.3.6 CFU - Billing Records for Call Forwarding Unconditional

Following records will be created for concerned subscribers in case of call forwarding unconditional:

a standard billing record at the VMSC of the calling MS A-Subscriber (in case of mobile to mobile call).

This record is identical to the MOC record, described above.

a 'call forwarding' record at the Gateway MSC of the called subscriber B-Subscriber forwarding the call.

a billing record at VMSC of the forwarded-to-subscriber C-Subscriber.

This record is identical to the MTC record, described above, with the remark that the servedMobileNumber refers to the C subscriber, and the otherParty to the A or B subscriber.

This table describes the call forwarding record.

Remark: If ‘camelInitCfIndicator’ is set to TRUE, then a CAMELCF record will be generated,i.e. ‘callTransactionType’ will be set to ‘cAMELCF’


recordType M record type A and record type B available yes / no yescallTransactionType M 'mtc' for GSM-CF or 'cAMELCF' for CAMEL-

CF at coding a);'callForwarding' at coding b) and c)

yes / no yes

servedMobileNumber M also synonym for servedMobileIdentity; B subscriber

yes / no yes

servedIMSI M yes / no yesservedMSIsdn M yes / no yesservedIMEI D only default possible <value>/ no noservedMSRN D only default possible <value>/ no no



timeQuality M if insecure yes / no yestransactionIdentification D only default possible <value>/ no noservedSubscriberLocation only in case of (Local) Number Portability yes / no nootherPartyLocation only in case of (Local) Number Portability yes / no nootherParty **) choice of different coding yes / no no

otherPartyShortNumber C subscriber yes / no nootherPartyLongNumber M forwarded-to number **) yes / no yes


otherMSRN M MSRN of other party yes / no yescarrierAccessCode if available yes / no noinatIndicator yes / no noorigTermMscId M yes / no yesconnectedSwitchId choice of origTermBscId (or DAId) yes / no no

origTermBscId D only default possible <value>/ no noexchangeId M yes / no yesbasicService choice of service types yes / no no

individualTeleserviceNumber D only default possible <value>/ no noindividualBearerserviceNumber D only default possible <value>/ no no


tgrpNameOg M yes / no yes



cicOg M yes / no yesbiccCallInstCodeOut in case of a AAL2 connection yes / no no




sSSequenceOf M **) sequence of sSCode yes / no yessSCode M *) at least sSCode CFU yes / no yes




chargingPulses yes / no nochargeIndicator M also synonym for chargeType yes / no yesthirdParty M A subscriber if available by signalling yes / no yesredirectionCounter M yes / no yesnMTForwardedIndicator M yes / no yeslocationAreaCode yes / no nocellId D *) only default possible <value>/ no nolocationNumber D only default possible <value>/ no nohotTransferResult M if Hot Billing active yes / no yescallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no


released and new call Id by CF not releasedyes / no no

drcChrgOrigin DRC has to be released yes / no nodrcTariffClass DRC has to be released yes / no nochrgContainer1 if available yes / no nochrgContainer2 if available yes / no nochrgContainer3 if available yes / no nochrgContainer5 if available yes / no nodurationBeforeAnswer NOT RELEASED yes / no norecordUse NOT RELEASED yes / no norateIndication UMTS yes / no nocamelCommonData yes / no no

inFlag if an IN service was triggered yes / no notimeOfCAMELLeg yes / no nodateOfCAMELLeg yes / no nodurationOfCAMELLeg yes / no nocamelInitCfIndicator in case of CAMEL-CF yes / no nochargeBandNumber if received from IN service yes / no noinAoC if IN AoC data available yes / no no


inServiceKey if an IN service was triggered yes / no nogsmScfAddress only for IN calls triggered by CSI if available yes / no nodefaultCallHandling only for IN calls triggered by CSI if available yes / no nolevelOfCAMELService yes / no nochangeFlags yes / no nonumberOfDpEncountered yes / no nomcrDestinationNumber only for IN calls if available yes / no noinTransPar if received from IN service yes / no nocamelFFDataIncLeg free format data for incoming leg yes / no nocamelFFDataIncAppendInd yes / no no



camelFFDataOutLeg free format data for outgoing leg yes / no nocamelFFDataOutAppendInd yes / no no

partialRecordType yes / no nopartialRecordCorrelationId for correlation of partial records yes / no nocphIndication in case of call party handling yes / no nooptimalRoutingMmcEcf in case of ORMMC or ORECF yes / no no

Table 21: CFU record


2.2.3.7 CFC - Billing Records for Call Forwarding Conditional

Following records will be created for concerned subscribers in case of call forwarding conditional:

a standard billing record at the VMSC of the calling MS A-Subscriber (in case of mobile to mobile call)

This record is identical to the MOC record, described above.

a 'call forwarding' record at the Visitor MSC of the called subscriber B-Subscriber forwarding the call conditionally.

a billing record as VMSC of the forwarded-to-subscriber C-Subscriber.

This record is identical to the MTC record, described above, with the remark that the servedMobileNumber refers to the C subscriber, and the otherParty to the B subscriber.

Note: For CFNRc, call forwarding condition detected during HLR interrogation, a 'call forwarding' record is generated at the G-MSC according to the CFU case described above except for the included SS code (CFNRc).

This table describes the call forwarding record.


recordType M record type A and record type B available yes / no yescallTransactionType M 'mtc' for GSM-CF at coding a);

'callForwarding' at coding b) and c)yes / no yes

servedMobileNumber M also synonym for servedMobileIdentity; B subscriber

yes / no yes

servedIMSI M yes / no yesservedMSIsdn M yes / no yesservedIMEI if available yes / no noservedMSRN M if VMSC = GMSC, if available yes / no yes



timeQuality M if insecure yes / no yestransactionIdentification yes / no noservedSubscriberLocation only in case of (Local) Number Portability yes / no nootherPartyLocation only in case of (Local) Number Portability yes / no nootherParty **) choice of different coding yes / no no

otherPartyShortNumber C subscriber yes / no nootherPartyLongNumber M forwarded-to number **) yes / no yes


otherMSRN M MSRN of other party yes / no yescarrierAccessCode if available yes / no noinatIndicator yes / no noorigTermMscId M yes / no yesconnectedSwitchId choice of origTermBscId (or DAId) yes / no no

origTermBscId M only for CFNRy and CFUDBusy yes / no yesexchangeId M yes / no yesbasicService choice of service types yes / no no

individualTeleserviceNumber M if basic service = teleserviceif available

yes / no yes

individualBearerserviceNumber M if basic service = bearer serviceif available

yes / no yes


tgrpNameOg M yes / no yescicOg M yes / no yes



biccCallInstCodeOut in case of a AAL2 connection yes / no nocauseForTermination M in case of abnormal release *) yes / no yesreasonForTermination M system internal reason for call termination yes / no yesmsClassmark yes / no noincTgTCompBlock M yes / no yes



sSSequenceOf M **) sequence of sSCode yes / no yessSCode M *) at least sSCode CFB / CFNRy / CFNRc yes / no yes

msAccessRate M if basic service <> telephony, if applicable yes / no yeschargingInformation yes / no no

tariffInfoPack ***) yes / no notariffInfo yes / no nooneTimeCharge yes / no notimeTariff yes / no no


chargingPulses yes / no nochargeIndicator M also synonym for chargeType yes / no yesthirdParty M A subscriber if available by signalling yes / no yesredirectionCounter M yes / no yesnMTForwardedIndicator M yes / no yeslocationAreaCode yes / no nocellId M *) if available yes / no yeslocationNumber if available yes / no nohotTransferResult M if Hot Billing active yes / no yescallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no




noOfUsedTrafficChannels yes / no nofixedNetworkUserRate yes / no nochannelCoding yes / no no

rateIndication UMTS yes / no nocamelCommonData yes / no no

inFlag if an IN service was triggered yes / no notimeOfCAMELLeg yes / no nodateOfCAMELLeg yes / no nodurationOfCAMELLeg yes / no nochargeBandNumber if an IN service was triggered yes / no noinAoC if IN AoC data available yes / no no


inServiceKey if an IN service was triggered yes / no nogsmScfAddress only for IN calls triggered by CSI if available yes / no nodefaultCallHandling only for IN calls triggered by CSI if available yes / no nolevelOfCAMELService yes / no nochangeFlags yes / no nonumberOfDpEncountered yes / no nomcrDestinationNumber only for IN calls if available yes / no no



inTransPar if received from IN service yes / no nocamelFFDataIncLeg free format data for incoming leg yes / no nocamelFFDataIncAppendInd yes / no nocamelFFDataOutLeg free format data for outgoing leg yes / no nocamelFFDataOutAppendInd yes / no no

partialRecordType yes / no nopartialRecordCorrelationId for correlation of partial records yes / no nocphIndication in case of call party handling yes / no nooptimalRoutingMmcEcf in case of ORMMC or ORECF yes / no nooptimalRoutingLcf in case of late call forwarding yes / no no

Table 22: CFC record


2.2.3.8 SCI - Billing Records for Subscriber Controlled Input

timeStamp for SCI: In case of SCI the start-timeStamp is set, when the SCI operation was successful, i.e. when the HLR signal 'operateSSack' was received. Unsuccessful SCI-operations are not subject to respective billing.


recordType M record type A and record type B available; 'single' yes / no yescallTransactionType M *) SS action / USSD yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; A


servedIMSI M yes / no yesservedMSIsdn O Basic MSISDN yes / no yesservedIMEI if available yes / no noservedMSRN only default possible <value>/ no no


timeStamp M **) yes / no yescallDuration M is '0' yes / no yes


otherPartyShortNumber yes / no nootherPartyLongNumber Set only in case of CF registration: forwarded-to

number **)yes / no no


origTermMscId M yes / no yesconnectedSwitchId choice of origTermBscId (or DAId) yes / no no

origTermBscId M yes / no yesexchangeId M yes / no yesbasicService choice of service types

not available for password registrationyes / no no


transmissionMode D only default possible <value>/ no nooutgTgTCompBlock yes / no no

tgrpNameOg D only default possible <value>/ no nocicOg D only default possible <value>/ no nobiccCallInstCodeOut D in case of a AAL2 connection <value>/ no no

causeForTermination D only default possible <value>/ no nomsClassmark M yes / no yesincTgTCompBlock yes / no no

tgrpNameIc D only default possible <value>/ no nocicIc D only default possible <value>/ no nobiccCallInstCodeInc D in case of a AAL2 connection <value>/ no no

sequenceNumber M yes / no yessupplServiceInfo M **) yes / no yes

sSSequenceOf M **) sequence of sSCode yes / no yessSCode M *) yes / no yes

ussdData O yes / no yesussdAccessCode M yes / no yesussdString M yes / no yesussdCodingScheme O yes / no yesussdNotifyCounter O yes / no yesussdRequestCounter O yes / no yes

locationAreaCode yes / no nocellId M *) yes / no yeslocationNumber yes / no nohotTransferResult M if Hot Billing active yes / no yeschrgContainer4 if available yes / no nochrgContainer5 if available yes / no nosystemType UMTS indication yes / no no


Table 23: SCI record


2.2.3.9 TRANSIT - Transit Records

avail- field requiredElement ability comment range definerecordType M record type A and record type B available yes / no yescallTransactionType M *) 'Transit' yes / no yesservedOtherNumber M calling party number yes / no yeschargingtimeData M yes / no yes

startOfChargingdate M yes / no yesstartOfChargingtime M **) yes / no yes



otherPartyShortNumber called party number from signalling Interface yes / no nootherPartyLongNumber M **) yes / no yes


carrierAccessCode if available yes / no noinatIndicator yes / no noorigTermMscId yes / no noconnectedSwitchId choice of origTermBscId (or DAId) yes / no no





causeForTermination D only default possible <value>/ no noreasonForTermination M system internal reason for call termination yes / no yesmsClassmark D only default possible <value>/ no noincTgTCompBlock M yes / no yes


sequenceNumber M yes / no yesintermediateSequenceNumber M if intermediate records are generated yes / no yesredirectionCounter M yes / no yesnMTForwardedIndicator M indicates preceding CF yes / no yescellId D *) only default possible <value>/ no nolocationNumber D only default possible <value>/ no nocallReferenceNumber if available yes / no nomscAddress if available yes / no nodrcCallNumber Only if General Call Id has to be released yes / no no



chrgContainer2 if available yes / no nochrgContainer3 if available yes / no nochrgContainer5 if available yes / no nodurationBeforeAnswer NOT RELEASED yes / no norecordUse NOT RELEASED yes / no nocamelCommonData yes / no no

inFlag if an IN service was triggered yes / no notimeOfCAMELLeg yes / no nodateOfCAMELLeg yes / no nodurationOfCAMELLeg yes / no no


inServiceKey if an IN service was triggered yes / no no


avail- field requiredElement ability comment range define

mcrDestinationNumber only for IN calls if available yes / no nopartialRecordType yes / no nopartialRecordCorrelationId if available yes / no nocphIndication in case of call party handling yes / no no

Table 24: TRANSIT record


2.2.3.10 SMSMT - Mobile terminating SMS point to point Record


recordType M record type A and record type B available; 'single'

yes / no yes

callTransactionType M *) 'mobile terminating SMS PP' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; B


servedIMSI M yes / no yesservedMSIsdn M ServedMSISDN, if not present then

BasicMSISDNyes / no yes

servedIMEI if available (only possible in case of parallel transactions)

yes / no no

servedMSRN D only default possible <value>/ no nochargingtimeData M yes / no yes




otherPartyShortNumber D only default possible <value>/ no nootherPartyLongNumber D only default possible <value>/ no nootherPartySMS M yes / no yes



individualTeleserviceNumber M 'short message MT/PP' (TS H'21) yes / no yesindividualBearerserviceNumber D only default possible <value>/ no no


tgrpNameOg D only default possible <value>/ no nocicOg D only default possible <value>/ no nobiccCallInstCodeOut D only default possible <value>/ no no

msClassmark M yes / no yesincTgTCompBlock yes / no no

tgrpNameIc D only default possible <value>/ no nocicIc D only default possible <value>/ no nobiccCallInstCodeInc D only default possible <value>/ no no

sequenceNumber M yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yeslocationNumber yes / no noserviceCentreAddress M SMC address yes / no yessMTransmissionResult M if unsuccessful attempt (see network options) yes / no yesprotocolIdForSMS yes / no nomultipleSMTransfer M if multiple SM transfer was used yes / no yeshotTransferResult M if Hot Billing active yes / no yeschrgContainer4 if available yes / no nosystemType UMTS indication yes / no no

Table 25: SMSMT record


2.2.3.11 SMSMO - Mobile originating SMS point to point Record


recordType M record type A and record type B available; 'single' yes / no yescallTransactionType M *) 'mobile originating SMS PP' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; A


servedIMSI M yes / no yesservedMSIsdn M Basic MSISDN yes / no yesservedIMEI if available (only possible in case of parallel

transactions)yes / no no

servedMSRN D only default possible <value>/ no nochargingtimeData M yes / no yes




otherPartyShortNumber yes / no nootherPartyLongNumber D only default possible <value>/ no nootherPartySMS M **) yes / no yes




individualTeleserviceNumber M 'short message MO/PP' (TS H'22) yes / no yesindividualBearerserviceNumber D only default possible <value>/ no no





sequenceNumber M yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yeslocationNumber yes / no noserviceCentreAddress M SMC address yes / no yessMTransmissionResult M if unsuccessful attempt (see network options) yes / no yessMReference M yes / no yesprotocolIdForSMS yes / no nomultipleSMTransfer M if multiple SM transfer was used yes / no yeshotTransferResult M if Hot Billing active yes / no yescallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yeschrgContainer4 if available yes / no nochrgContainer5 if available yes / no nocamelCommonData yes / no no

inFlag if an IN service was triggered yes / no nosequenceOfCamelDialogs yes / no no

camelDialog yes / no noinServiceKey if an IN service was triggered yes / no nogsmScfAddress only for IN calls triggered by CSI if available yes / no nodefaultCallHandling only for IN calls triggered by CSI if available yes / no no

mcrDestinationNumberSMS only for IN calls if available yes / no no

camelFFDataIncLeg free format data for incoming leg yes / no nocamelFFDataOutLeg free format data for outgoing leg yes / no no



systemType UMTS indication yes / no no

Table 26: SMSMO record


2.2.3.12 PABXOG - PABX Originating Call Record (not in PCS)


recordType M record type A and record type B available yes / no yescallTransactionType M *) 'PBX Originating record' / 'pbxOutgoingCall' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; A


servedIMSI D only default possible <value>/ no noservedMSIsdn M PABX Directory Number yes / no yesservedIMEI D only default possible <value>/ no noservedMSRN D only default possible <value>/ no nopABXNumber yes / no no




otherPartyShortNumber B subscriber yes / no nootherPartyLongNumber M **) yes / no yes


carrierAccessCode if available yes / no noorigTermMscId M yes / no yesconnectedSwitchId choice of origTermBscId or DAId yes / no no

origTermBscId D only default possible <value>/ no nodAId M yes / no yes

exchangeId M yes / no yesbasicService choice of service types yes / no no

individualTeleserviceNumber D only default possible <value>/ no noindividualBearerserviceNumber D only default possible <value>/ no noiSDNBasicService M yes / no yes


tgrpNameOg yes / no nocicOg yes / no nobiccCallInstCodeOut in case of a AAL2 connection yes / no no

causeForTermination M in case of abnormal release *) yes / no yesreasonForTermination M system internal reason for call termination yes / no yesmsClassmark D only default possible <value>/ no noincTgTCompBlock yes / no no





chargingInformation yes / no notariffInfoPack ***) yes / up to 6 notariffInfo yes / no nooneTimeCharge yes / no notimeTariff yes / no no

chargeIndicator M also synonym for chargeType yes / no yescellId D *) only default possible <value>/ no nolocationNumber D only default possible <value>/ no no



subscriberCategory M yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no

drcCallId *) yes / no nodrcChrgOrigin D only default possible <value>/ no nodrcTariffClass D only default possible <value>/ no nochrgContainer5 if available yes / no nocamelCommonData yes / no no

chargeBandNumber if received from IN service yes / no nodurationBeforeAnswer NOT RELEASED yes / no norecordUse NOT RELEASED yes / no nopartialRecordType yes / no nopartialRecordCorrelationId for correlation of partial records yes / no no

Table 27: PABXOG record


2.2.3.13 PABXIC - PABX Terminating Call Record (not in PCS)


recordType M record type A and record type B available yes / no yescallTransactionType M *) 'PBX Terminating record' / 'pbxIncomingCall' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; B


servedIMSI D only default possible <value>/ no noservedMSIsdn M PABX Directory Number yes / no yesservedIMEI D only default possible <value>/ no noservedMSRN D only default possible <value>/ no nopABXNumber yes / no no



timeQuality M if insecure yes / no yestransactionIdentification D only default possible <value>/ no nootherParty **) choice of different coding yes / no no

otherPartyShortNumber see description part and /MCR/ yes / no nootherPartyLongNumber M **) yes / no yes


inatIndicator yes / no noorigTermMscId M yes / no yesconnectedSwitchId choice of origTermBscId or DAId yes / no no

origTermBscId D only default possible <value>/ no nodAId M yes / no yes

exchangeId M yes / no yesbasicService choice of service types yes / no no

individualTeleserviceNumber D only default possible <value>/ no noindividualBearerserviceNumber D only default possible <value>/ no noiSDNBasicService M yes / no yes



causeForTermination M in case of abnormal release *) yes / no yesreasonForTermination M system internal reason for call termination yes / no yesmsClassmark D only default possible <value>/ no noincTgTCompBlock yes / no no

tgrpNameIc yes / no nocicIc yes / no nobiccCallInstCodeInc in case of a AAL2 connection yes / no no



cellId D *) only default possible <value>/ no nolocationNumber D only default possible <value>/ no nodrcCallNumber General Call Id or DRC has to be released yes / no no


releasedyes / no no

drcChrgOrigin D only default possible <value>/ no nodrcTariffClass D only default possible <value>/ no nocamelCommonData yes / no no

inFlag if an IN service was triggered by subscriber own TLT

yes / no no

chrgContainer5 if available yes / no nodurationBeforeAnswer NOT RELEASED yes / no norecordUse NOT RELEASED yes / no nopartialRecordType yes / no no



partialRecordCorrelationId for correlation of partial records yes / no no

Table 28: PABXIC record


2.2.3.14 ECT - Emergency Call Trace Record


recordType M record type A and record type B available; 'single' yes / no yescallTransactionType M *) 'Emergency call trace (ECT)' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; A






otherPartyShortNumber M B subscriber yes / no yesotherPartyLongNumber **) yes / no no

otherPartySequence yes / no nodialledOtherParty yes / no no



individualTeleserviceNumber M 'Emergency calls' yes / no yesspeechCode if a speech service was supported yes / no nomsClassmark M yes / no yessequenceNumber M yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yeslocationNumber yes / no nohotTransferResult M yes / no yeschrgContainer3 if available yes / no nochrgContainer4 if available yes / no nochrgContainer5 if available yes / no no

Table 29: ECT record


2.2.3.15 MOCATT - Mobile Originating Call Attempt Record

This record is generated at the VMSC of the calling party if no answer state is set.


recordType M record type A and record type B available; 'single' yes / no yescallTransactionType M *) 'MOC Attempt' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; A




timeStamp M **) yes / no yescallDuration D only default possible <value>/ no no




otherMSRN M MSRN of other party yes / no yescallTransferThirdParty yes / no nocarrierAccessCode if available yes / no noorigTermMscId M yes / no yesconnectedSwitchId choice of origTermBscId (or DAId) yes / no no









sSInvocation M yes / no yessSInvocCode M yes / no yessSInvocSucc M yes / no yessSInvocDate M yes / no yessSInvocTime M yes / no yes

msAccessRate M if basic service <> telephony yes / no yeschargeIndicator M also synonym for chargeType yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yessecondCellId if DIRECTED RETRY is released yes / no nolocationNumber yes / no no



hotTransferResult M if Hot Billing active yes / no yessubscriberCategory M yes / no yescallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no







partialRecordType yes / no nopartialRecordCorrelationId for correlation of partial records yes / no nosystemType UMTS indication yes / no nocphIndication in case of call party handling yes / no no

Table 30: MOCATT record


2.2.3.16 ROAATT - Roaming Attempt Record

This record is generated at the GMSC of the called party (GSM and PSC)


recordType M record type A and record type B available yes / no yescallTransactionType M *) 'RoamingAttempt' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity


servedIMSI M yes / no yesservedMSIsdn M yes / no yesservedIMEI D only default possible <value>/ no noservedMSRN M FTN in case of HLR detected CF

(CHCFROA active)yes / no yes



timeQuality M if insecure yes / no yestransactionIdentification D only default possible <value>/ no noservedSubscriberLocation only in case of local number portability yes / no nootherPartyLocation Only for Loc. Numb. Portab. yes / no nootherParty **) choice of different coding yes / no no

otherPartyShortNumber A subscriber / B subscriber yes / no nootherPartyLongNumber M **) yes / no yes

otherPartySequence yes / no nodialledOtherParty after call forwarding yes / no notranslatedOtherParty yes / no no

carrierAccessCode if available yes / no noorigTermMscId M yes / no yesconnectedSwitchId choice of origTermBscId (or DAId) yes / no no

origTermBscId yes / no noexchangeId M yes / no yesbasicService choice of service types yes / no no

individualTeleserviceNumber yes / no noindividualBearerserviceNumber yes / no no





sequenceNumber M yes / no yesintermediateSequenceNumber M if intermediate records are generated yes / no yesredirectionCounter M yes / no yesnMTForwardedIndicator M indicates preceding CF yes / no yeslocationAreaCode yes / no nocellId yes / no nolocationNumber yes / no nosubscriberCategory yes / no nocallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no


releasedyes / no no

drcChrgOrigin DRC has to be released yes / no nodrcTariffClass DRC has to be released yes / no nochrgContainer2 if available yes / no no



chrgContainer3 if available yes / no nochrgContainer5 if available yes / no nocamelCommonData yes / no no

inFlag if an IN service was triggered yes / no notimeOfCAMELLeg yes / no nodateOfCAMELLeg yes / no nodurationOfCAMELLeg yes / no nocamelInitCfIndicator yes / no notransmittedZone if received from IN service yes / no no


inServiceKey if an IN service was triggered yes / no nogsmScfAddress only for IN calls triggered by CSI if available yes / no nodefaultCallHandling only for IN calls triggered by CSI if available yes / no nolevelOfCAMELService yes / no nochangeFlags yes / no nomcrDestinationNumber only for IN calls if available yes / no noinTransPar if received from IN service yes / no nocamelFFDataIncLeg free format data for incoming leg yes / no nocamelFFDataIncAppendInd yes / no nocamelFFDataOutLeg free format data for outgoing leg yes / no nocamelFFDataOutAppendInd yes / no no

durationBeforeAnswer NOT RELEASED yes / no norecordUse NOT RELEASED yes / no nopartialRecordType yes / no nopartialRecordCorrelationId for correlation of partial records yes / no nocphIndication in case of call party handling yes / no nooptimalRoutingMmcEcf in case of ORMMC or ORECF yes / no nooptimalRoutingLcf in case of late call forwarding yes / no no

Table 31: ROAATT record


2.2.3.17 EMYATT - Emergency Call Attempt Record (MOC/Emergency attempt record)

This record is generated at the VMSC of the calling party if no answer state is set.


recordType M record type A and record type B available; 'single' yes / no yescallTransactionType M *) 'Emergency call attempt' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; A


servedIMSI O if SIM card used yes / no yesservedMSIsdn M yes / no yesservedIMEI O if available yes / no yesservedMSRN D only default possible <value>/ no no



timeQuality M if insecure yes / no yestransactionIdentification M if available yes / no yesservedSubscriberLocation only in case of (Local) Number Portability yes / no nootherPartyLocation only in case of (Local) Number Portability yes / no nootherParty **) choice of different coding yes / no no





individualTeleserviceNumber M ‘Emergency calls’ or ‘Speech’ yes / no yesindividualBearerserviceNumber D only default possible <value>/ no no





sequenceNumber M yes / no yesintermediateSequenceNumber M if intermediate records are generated yes / no yessupplServiceInfo **) yes / no no

sSSequenceOf **) sequence of sSCode yes / no nosSCode *) yes / no no

sSInvocation yes / no nosSInvocCode yes / no nosSInvocSucc yes / no nosSInvocDate yes / no nosSInvocTime yes / no no

chargeIndicator M also synonym for chargeType yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yessecondCellId if DIRECTED RETRY is released yes / no nolocationNumber yes / no nohotTransferResult M if Hot Billing active yes / no yescallReferenceNumber M if available yes / no yes



mscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no

drcCallId *) yes / no nodrcChrgOrigin DRC has to be released yes / no nodrcTariffClass DRC has to be released yes / no nochrgContainer1 if available yes / no nochrgContainer2 if available yes / no nochrgContainer3 if available yes / no nochrgContainer4 if available yes / no nochrgContainer5 if available yes / no nodurationBeforeAnswer NOT RELEASED yes / no norecordUse NOT RELEASED yes / no nopartialRecordType yes / no nopartialRecordCorrelationId for correlation of partial records yes / no nosystemType UMTS indication yes / no no

Table 32: EMYATT record


2.2.3.18 MTCATT - Mobile Terminating Call Attempt Record

This record is generated at the VMSC of the called party if no answer state is set.


recordType M record type A and record type B available; 'single' yes / no yescallTransactionType M *) 'MTC Attempt' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity


servedIMSI M yes / no yesservedMSIsdn M yes / no yesservedIMEI O if available yes / no yesservedMSRN O available if VMSC = GMSC yes / no yes




otherPartyShortNumber if available, A subscriber / B subscr. after CF yes / no nootherParty3a M yes / no yesotherPartyLongNumber **) yes / no no


callTransferThirdParty yes / no noorigTermMscId M yes / no yesconnectedSwitchId choice of origTermBscId (or DAId) yes / no no

origTermBscId M if available yes / no yesexchangeId M yes / no yesbasicService choice of service types yes / no no






sequenceNumber M yes / no yessupplServiceInfo M **) yes / no yes


msAccessRate M if basic service <> telephony yes / no yesredirectionCounter M yes / no yesnMTForwardedIndicator M indicates preceding CF yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yessecondCellId if DIRECTED RETRY is released yes / no nolocationNumber yes / no nohotTransferResult M if Hot Billing active yes / no yescallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no


releasedyes / no no

drcChrgOrigin DRC has to be released yes / no no



drcTariffClass DRC has to be released yes / no nochrgContainer2 if available yes / no nochrgContainer3 if available yes / no nochrgContainer4 if available yes / no nochrgContainer5 if available yes / no nodurationBeforeAnswer NOT RELEASED yes / no norecordUse NOT RELEASED yes / no noadditionalBearerServiceInfo for HSCSD calls/ UMTS data services yes / no no


rateIndication UMTS yes / no nousedEmlppPriority for eMLPP supplementary service yes / no nosystemType UMTS indication yes / no nooptimalRoutingMmcEcf in case of ORMMC or ORECF yes / no no

Table 33: MTCATT record


2.2.3.19 CFUATT - Call Forwarding Attempt Record in case of CFU

This record is generated at the Gateway MSC of the called subscriber B-Subscriber forwarding the call if no answer state is set.


recordType M record type A and record type B available; single' yes / no yescallTransactionType M *) 'Call forwarding attempt' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; B






otherPartyShortNumber C subscriber yes / no nootherPartyLongNumber M **) yes / no yes










sSSequenceOf M **) sequence of sSCode yes / no yessSCode M *) at least sSCode CFU yes / no yes




chargingPulses yes / no no



chargeIndicator M also synonym for chargeType yes / no yesthirdParty M A subscriber if available by signalling yes / no yesredirectionCounter M yes / no yesnMTForwardedIndicator M indicates preceding CF yes / no yeslocationAreaCode yes / no nocellId D *) only default possible <value>/ no nolocationNumber D only default possible <value>/ no nohotTransferResult M if Hot Billing active yes / no yescallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no


released and new call Id by CF is not releasedyes / no no

drcChrgOrigin DRC has to be released yes / no nodrcTariffClass DRC has to be released yes / no nochrgContainer1 if available yes / no nochrgContainer2 if available yes / no nochrgContainer3 if available yes / no nochrgContainer5 if available yes / no nodurationBeforeAnswer NOT RELEASED yes / no norecordUse NOT RELEASED yes / no norateIndication UMTS yes / no nocamelCommonData yes / no no

inFlag if an IN service was triggered yes / no notimeOfCAMELLeg yes / no nodateOfCAMELLeg yes / no nodurationOfCAMELLeg yes / no nocamelInitCfIndicator yes / no nochargeBandNumber if received from IN service yes / no noinAoC if IN AoC data available yes / no no



partialRecordType yes / no nopartialRecordCorrelationId for correlation of partial records yes / no nocphIndication in case of call party handling yes / no nooptimalRoutingMmcEcf in case of ORMMC or ORECF yes / no no

Table 34: CFUATT record


2.2.3.20 CFCATT - Call Forwarding Attempt Record in case of CFC

This record is generated at the Visited MSC of the called subscriber B-Subscriber forwarding the call conditionally if no answer state is set.

Note: For CFNRc, call forwarding condition detected during HLR interrogation, a 'call forwarding' record is generated at the G-MSC according to the CFU case described above except for the included SS code (CFNRc).


recordType M record type A and record type B available; 'single' yes / no yescallTransactionType M *) 'Call forwarding attempt' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; B


servedIMSI M yes / no yesservedMSIsdn M yes / no yesservedIMEI if available yes / no noservedMSRN M if VMSC = GMSC, if available yes / no yes



timeQuality M if insecure yes / no yestransactionIdentification yes / no noservedSubscriberLocation only in case of (Local) Number Portability yes / no nootherPartyLocation only in case of (Local) Number Portability yes / no nootherParty **) choice of different coding yes / no no

otherPartyShortNumber C subscriber yes / no nootherPartyLongNumber M **) yes / no yes










sSSequenceOf M **) sequence of sSCode yes / no yessSCode M *) at least sSCode CFB / CFNRy / CFNRc yes / no yes



backwardChargingInfo yes / no nobackwardChargingInfoTAX if available (e.g. for yes / no no



backwardChargingInfoCHT if available international yes / no nobackwardChargingInfoITX if available destinations, yes / no nobackwardChargingInfoCBA if available special services) yes / no no

chargingPulses yes / no nochargeIndicator M also synonym for chargeType yes / no yesthirdParty M A subscriber if available by signalling yes / no yesredirectionCounter M yes / no yesnMTForwardedIndicator M indicates preceding CF yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yeslocationNumber yes / no nohotTransferResult M if Hot Billing active yes / no yescallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no


released and new call Id by CF is not releasedyes / no no


noOfUsedTrafficChannels yes / no nofixedNetworkUserRate yes / no nochannelCoding yes / no no

rateIndication UMTS yes / no nocamelCommonData yes / no no




partialRecordType yes / no nopartialRecordCorrelationId for correlation of partial records yes / no nocphIndication in case of call party handling yes / no nooptimalRoutingMmcEcf in case of ORMMC or ORECF yes / no nooptimalRoutingLcf in case of late call forwarding yes / no no

Table 35: CFCATT record


2.2.3.21 MOCTRAC - Mobile Originating Call Record IMSI Trace

This record is generated at the VMSC of the calling party.


traceType M yes / no yestraceReference M yes / no yesrecordType M record type A and record type B available yes / no yescallTransactionType M *) 'MOC' yes / no yesservedMobileNumber M (also synonym for servedMobileIdentity); A



















msAccessRate if basic service <> telephony yes / no nochargeAdviceInformation M **) yes / no yes

chargeAdviceElement M ***), **) all e-parameters as octet string yes / no yes



aOCParameter ***) sequence of e-parameters yes / no noe1 yes / no noe2 yes / no noe3 yes / no noe4 yes / no noe5 yes / no noe6 yes / no noe7 yes / no no




chargingPulses yes / no nochargeIndicator M also synonym for chargeType yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yessecondCellId if DIRECTED RETRY is released yes / no nolocationNumber yes / no nohotTransferResult M if Hot ITR active yes / no yessubscriberCategory M yes / no yescallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no







partialRecordType yes / no no



partialRecordCorrelationId for correlation of partial records yes / no nosystemType UMTS indication yes / no nocphIndication in case of call party handling yes / no nooptimalRoutingMmcEcf in case of ORMMC or ORECF yes / no nodestByOptimalRoutingMmcEcf in case of ORMMC or ORECF if available yes / no no

Table 36: MOCTRAC record


2.2.3.22 MTCTRAC - Mobile Terminating Call Record IMSI Trace

This record is generated at the VMSC of the called party.


traceType M yes / no yestraceReference M yes / no yesrecordType M record type A and record type B available yes / no yescallTransactionType M *) 'MTC' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; B


servedIMSI M yes / no yesservedMSIsdn M yes / no yesservedIMEI O if available yes / no yesservedMSRN O available if VMSC = GMSC yes / no yes




otherPartyShortNumber yes / no nootherParty3a M yes / no yesotherPartyLongNumber **) see description part and /MCR/ yes / no no














chargeAdviceElement M ***), **) all e-parameters as octet string yes / no yesaOCParameter ***)sequence of e-parameters yes / no no




redirectionCounter M yes / no yesnMTForwardedIndicator M yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yessecondCellId if DIRECTED RETRY is released yes / no nolocationNumber yes / no nohotTransferResult M if Hot ITR active yes / no yescallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yesdrcCallNumber General Call Id or DRC has to be released yes / no no


releasedyes / no no



rateIndication UMTS yes / no nousedEmlppPriority for eMLPP supplementary service yes / no nopartialRecordType yes / no nopartialRecordCorrelationId for correlation of partial records yes / no nosystemType UMTS indication yes / no no

Table 37: MTCTRAC record


2.2.3.23 SMSTTRAC- Mobile terminating SMS point to point Record IMSI Trace


traceType M yes / no yestraceReference M yes / no yesrecordType M record type A and record type B available;

'single'yes / no yes

callTransactionType M *) 'mobile terminating SMS' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; B






otherPartyShortNumber D only default possible <value>/ no nootherPartyLongNumber D **) only default possible <value>/ no nootherPartySMS M yes / no yes



individualTeleserviceNumber M 'short message MT/PP' (TS H'21) yes / no yesindividualBearerserviceNumber D only default possible <value>/ no no





sequenceNumber M yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yeslocationNumber yes / no noserviceCentreAddress M SMC address yes / no yessMTransmissionResult M if unsuccessful attempt (see network options) yes / no yesprotocolIdForSMS yes / no nomultipleSMTransfer M if multiple SM transfer was used yes / no yeshotTransferResult M if Hot ITR active yes / no yeschrgContainer4 if available yes / no nosystemType UMTS indication yes / no no

Table 38: SMSTTRAC record


2.2.3.24 SMSOTRAC - Mobile originating SMS point to point Record IMSI Trace


traceType M yes / no yestraceReference M yes / no yesrecordType M record type A and record type B available; 'single' yes / no yescallTransactionType M *) 'mobile originating SMS' yes / no yesservedMobileNumber M also synonym for servedMobileIdentity; A






otherPartyShortNumber yes / no nootherPartyLongNumber D **) only default possible <value>/ no nootherPartySMS M yes / no yes




individualTeleserviceNumber M 'short message MO/PP' (TS H'22) yes / no yesindividualBearerserviceNumber D only default possible <value>/ no no





sequenceNumber M yes / no yeslocationAreaCode yes / no nocellId M *) yes / no yeslocationNumber yes / no noserviceCentreAddress M SMC address yes / no yessMTransmissionResult M if unsuccessful attempt (see network options) yes / no yessMReference M yes / no yes

protocolIdForSMS yes / no no

multipleSMTransfer M if multiple SM transfer was used yes / no yeshotTransferResult M if Hot ITR active yes / no yescallReferenceNumber M if available yes / no yesmscAddress M if available yes / no yeschrgContainer4 if available yes / no nochrgContainer5 if available yes / no nocamelCommonData yes / no no

inFlag if an IN service was triggered yes / no nosequenceOfCamelDialogs yes / no no

camelDialog yes / no noinServiceKey if an IN service was triggered yes / no nogsmScfAddress only for IN calls triggered by CSI if available yes / no nodefaultCallHandling only for IN calls triggered by CSI if available yes / no no

mcrDestinationNumberSMS only for IN calls if available yes / no no



camelFFDataIncLeg free format data for incoming leg yes / no nocamelFFDataOutLeg free format data for outgoing leg yes / no no

systemType UMTS indication yes / no no

Table 39: SMSOTRAC record


2.3 DESCRIPTION OF CALL / EVENT RECORD FIELDS

General Note: Different coding for a field are given related to the range values in the preceding chapter (a, b ...).

The following parameter is only used for definition:

AddressString:

Leading octets: Digits coded like described in ITU Q.763 or GSM04.08.For details please refer the description of concerned parameter.

Subsequent octets : digits coded as TBCD-string.

AddressString ::= OCTET STRING (SIZE(1..maxAddressLength)) MaxAddressLength ::= INTEGER

BcdString:

BcdString ::= OCTET STRING (SIZE(1..maxBcdStringLength)) MaxBcdStringLength ::= INTEGER -- Example for coding: Time Stamp: 10.12.2000 -- coded: 001210 [JJMMDD]

TBCD-String:

TBCD-String ::= OCTET STRING (SIZE(1..maxTbcdStringLength)) MaxTbcdStringLength ::= INTEGER -- example '0173 45678' -- as TBCD-String (SIZE(8)) coded as '10375476F8FFFFFF' -- as TBCD-String (SIZE(1..8)) coded as '10375476F8'

!If the number of Adress Signals is odd, the Adress Signal string can end with H’F0, where the first digit H’F is the End Of Pulsing signal and the second digit is the fill up code for an odd number of digits. If the length of the field is defined longer than the number of received digits, the rest of the field is filled up with the filler as defined in the general record contents table.

2.3.1 additionalBearerServiceInfo (not for PCS projects)

AdditionalBearerServiceInfo ::= SEQUENCE { noOfUsedTrafficChannels NoOfUsedTrafficChannels,


fixedNetworkUserRate FixedNetworkUserRate, channelCoding ChannelCoding, maximumBitRate MaximumBitRate, guaranteedBitRate GuaranteedBitRate

}

For HSCSD calls and UMTS data calls this parameter specifies the attributes, negotiated between the MS and the network at call setup time.

For UMTS calls only the " fixedNetworkUserRate" applies.

additionalBearerServiceInfo::= SEQUENCE {

noOfUsedTrafficChannels,fixedNetworkUserRate,channelCoding}

Remark: If there is a change of HSCSD parameters during the call, then intermediate records are written

2.3.2 aOC


2.3.3 Parameter

AOCParameter ::= SEQUENCE { e1 E1, e2 E2, e3 E3, e4 E4, e5 E5, e6 E6, e7 E7}

This parameter contains the elements e1 to e7 according to GSM /04.80/ and /02.24/. E-Parameters which are not sent towards the mobile are set to "0".

2.3.4

2.3.5 backwardChargingInfoCBA

BackwardChargingInfoCBA ::= OCTET STRING (SIZE(1))

Note: Only in projects with SSUTR2-signalling.

This parameter contains the information stored in the CBA bits of the message indicator field of the 'User-To-User Facilities ISDN Address Complete Message'.

+-------------------------------------------------------------------+¦ backwardChargingInfoCBA ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ ¦ ¦¦ +---------------+ ¦ ¦¦ 1 octet ¦not relev¦a¦a¦a¦ ¦ aaa - CBA bits ¦¦ +---------------+ ¦ ¦¦ ¦ ¦+-------------------------------------------------------------------+

Only the first 3 bits are significant.

2.3.6 BackwardChargingInfoCBA ::= OCTET STRING (SIZE(1))

2.3.7 backwardChargingInfoCHT

BackwardChargingInfoCHT ::= OCTET STRING (SIZE (3))


This parameter contains the elements that are sent via SSUTR2 in the CHT messages.


+-------------------------------------------------------------------+¦ backwardChargingInfoCHT ¦ ¦+--------------------------------+----------------------------------+¦ content ¦ meaning ¦+--------------------------------+----------------------------------+¦ ¦ ¦¦ +---------------+ ¦ ¦¦ octet 1 ¦b b b b¦a a a a¦ ¦ aaaa - message indicators ¦¦ +---------------¦ ¦ bbbb - charge indicators ¦¦ 2 ¦ charge rate ¦ ¦ ¦¦ +---------------¦ ¦ ¦¦ 3 ¦ time indicator¦ ¦ ¦¦ +---------------+ ¦ ¦¦ ¦ ¦+-------------------------------------------------------------------+

2.3.8 BackwardChargingInfoCHT ::= OCTET STRING (SIZE (3))

2.3.9 backwardChargingInfoITX

BackwardChargingInfoITX ::= OCTET STRING (SIZE (1))


This parameter contains the elements that are sent via SSUTR2 in the ITX messages. In case of multiple ITX messages, the accumulated value is stored and copied in the record.

+-------------------------------------------------------------------+¦ backwardChargingInfoITX ¦ ¦+--------------------------------+----------------------------------+¦ content ¦ meaning ¦+-------------------------------------------------------------------+¦ ¦¦ +-----------------+ ¦¦ 1 octet ¦charge back field¦ ¦¦ +-----------------+ ¦¦ ¦+-------------------------------------------------------------------+

2.3.10 backwardChargingInfoTAX

BackwardChargingInfoITX ::= OCTET STRING (SIZE (1))

BackwardChargingInfoTAX ::= OCTET STRING (SIZE(6))


This parameter contains the elements that are sent via SSUTR2 in the TAX messages.


+-------------------------------------------------------------------+¦ backwardChargingInfoTAX ¦ ¦+--------------------------------+----------------------------------+¦ content ¦ meaning ¦+--------------------------------+----------------------------------+¦ ¦ ¦¦ +-----------------+ ¦ ¦¦ octet 1 ¦message indicator¦ ¦ aaaa - charge unit ¦¦ +-----------------¦ ¦ ¦¦ 2 ¦b b b b ¦a a a a ¦ ¦ bbbb - charge indicators ¦¦ +-----------------¦ ¦ ¦¦ 3 ¦ charge rate ¦ ¦ cccc - next charge unit ¦¦ +-----------------¦ ¦ ¦¦ 4 ¦ time indicator ¦ ¦ dddd - next charge indicators ¦¦ +-----------------¦ ¦ ¦¦ 5 ¦d d d d ¦c c c c ¦ ¦ ¦¦ +-----------------¦ ¦ ¦¦ 6 ¦next charge rate ¦ ¦ ¦¦ +-----------------+ ¦ ¦+-------------------------------------------------------------------+

2.3.11 BackwardChargingInfoTAX ::= OCTET STRING (SIZE(6))

2.3.12

2.3.13 basicService

BasicService ::= CHOICE { individualTeleserviceNumber IndividualTeleserviceNumber, individualBearerserviceNumber IndividualBearerserviceNumber, iSDNBasicService ISDNBasicService}

The applied Basic Service (tele service or bearer service) is negotiated between the MS and the serving MSC i.e. the VMSC. 3GPP TS do not foresee to signal the basic service back to the GMSC, therefore the basic service is not known in the GMSC if the GMSC is different from the VMSC.Furthermore, the applied BasicService might even be unknown in the VMSC if the signalling to the MS failed (e.g. CFBusy network determined [NDUB]; CFNRc radio congestion).In order to always get a BasicService value in the ticket, the parameter BasicService should not be defined as an optional parameter, and the parameter individualTeleService should be provided with a default value e.g. H'11 = speech. This affects ROA, Transit, CF, and TCR tickets.

Note related to Call Forwarding:The basicService is only available in case of a service negotation between MSC and MS before the CF condition was detected, i.e. only in case of CFNRy and CFB(UDUB).If the CF is followed by an MTC, both being handled in the same MSC i.e. CF-MSC = VMSC of the forwarded-to subscriber, the Chaser provides the basicService as collected for the MTC leg of the forwarded-to subscriber also in the CF ticket for the forwarding subscriber.


The GDCS strictly separates both (forwarding and forwarded-to) legs, so the CF ticket generated by the GDCS will contain a default value only, if administered, in all cases except CFNRy and CFB(UDUB). This is illustrated by the following table:

Charging method basicService present basicService not present remarkGDCS CFNRy

CFB(UDUB)CFUCFB(NDUB and MDUB)CFNRc

behaviour independent of the further call processing

Chaser CFNRyCFB(UDUB)

CFUCFB(NDUB and MDUB)CFNRc

in case of outgoing traffic after CF detection

all CF types in case of any basicService availability in the CF-MSC following the CF (i.e. CFNRy or CFB[UDUB] of the forwarded-to subscriber, or MTC of the last subscriber)

See also ch. 1.2.

2.3.14 biccCallInstCodeOut, biccCallInstCodeInc

BiccCallInstCodeInc ::= OCTET STRING (SIZE(4))BiccCallInstCodeOut ::= OCTET STRING (SIZE(4))

The biccCircuitIdentCode is an identifier for the circuit used in BICC signalling for AAL2 connections. As result the parameters indicates the call instance code of used BICC Trunk. The parameter biccCallInstCodeOut stands for the call instance code of used outgoing BICC Trunk and biccCallInstCodeInc for the call instance code of used incoming BICC Trunk.

2.3.15

2.3.16 BiccCallInstCodeInc ::= OCTET STRING (SIZE(4))

2.3.17

2.3.18 BiccCallInstCodeOut ::= OCTET STRING (SIZE(4))

2.3.19

2.3.20 callDuration

coding a:

CallDurationA ::= INTEGER -- strictly ASN.1 like integer coding -- example: 127 sec coded as '7F' -- example: 128 sec coded as '0080'


+-------------------------------------------------------------------+¦ callDuration ¦ length = 1..3 ¦+--------------------------------+----------------------------------+¦ content ¦ meaning ¦+-------------------------------------------------------------------+¦ call duration time up to x seconds ¦¦ (x is the time for the intermediate records in seconds, ¦¦ e.g. for 30 minutes timer x = 1800) ¦+-------------------------------------------------------------------+

The value of CallDuration has to be the greatest integer less or equal to the actual value e.g. 0,9s = 0s. Thus, CallDuration = 0 is a valid value for answered calls.

In case of recordType indicating "first", "intermediate" or "last" this field contains the duration between opening and closure of the record (i.e. is different from the conversation duration).

In case of recordType indicating "first" or "intermediate" and partialRecordType indicating “timeLimit” the value of CallDuration will be the administered intermediate record timer value (T114), e.g. 1800s, +/- 1s.

Range is 0 to x seconds,

callDuration = 0 is a valid value for answered calls

Integer value with variable length (theoretically 1..3 bytes, according to ASN.1 Basic Encoding Rules).


CallDurationA ::= INTEGER -- strictly ASN.1 like integer coding -- example: 127 sec coded as '7F' -- example: 128 sec coded as '0080'


coding b:

CallDurationB ::= OCTET STRING (SIZE(2)) -- coded with a fixed length of 2 bytes -- range 0 to 1800 seconds -- example: 35 sec coded as '0023'

+-------------------------------------------------------------------+¦ callDuration ¦ length = 2 ¦+--------------------------------+----------------------------------+¦ content ¦ meaning ¦+-------------------------------------------------------------------+¦ call duration time up to x seconds ¦¦ (x is the time for the intermediate records in seconds, ¦¦ e.g. for 30 minutes timer x = 1800) ¦+-------------------------------------------------------------------+



Octet string with fixed length = 2.


2.3.21

2.3.22 CallDurationB ::= OCTET STRING (SIZE(2)) -- coded with a fixed length of 2 bytes -- range 0 to 1800 seconds -- example: 35 sec coded as '0023'

2.3.23 callHoldInvocCount

CallHoldInvocCount ::= INTEGER -- Number Of SS Call Hold Invocations -- range 0-127


2.3.24 callReferenceNumber

CallReferenceNumber ::= OCTET STRING (SIZE (1..8))

+-------------------------------------------------------------------+¦ callReferenceNumber ¦ length = 1..8 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ ¦¦ 8 7 6 5 4 3 2 1 ¦¦ +-------------------------------¦ ¦¦ 1 ¦ \ ¦ ¦¦ ¦ ¦ ¦ ¦¦ 2 ¦ ¦ ¦ ¦¦ ¦ \ CRN as generated by ¦ ¦¦ 3 ¦ / Siemens MSC ¦ ¦¦ ¦ ¦ ¦ ¦¦ 4 ¦ ¦ ¦ ¦¦ ¦ ¦ ¦ ¦¦ 5 ¦ / ¦ ¦¦ ¦ - - - - - - - - - - - - - - - ¦ ¦¦ 6 ¦ ¦ ¦¦ ¦ ¦ ¦¦ 7 ¦ ¦ ¦¦ ¦ ¦ ¦¦ 8 ¦ ¦ ¦¦ +-------------------------------+ ¦¦ ¦+-------------------------------------------------------------------+

The Call Reference Number (CRN) is introduced to give the possibility to correlate all call tickets of one subscriber in different network entities or even within the same network entity (e.g. TIR+ROA+CF, TIR+ROA+MTC).

A Call Reference Number will be allocated for all incoming calls, if no Call Reference Number is available yet. Incoming calls means, all calls over an incoming trunk but no calls coming in from a BSSAP-LTG.

If a Call Reference Number is already available for an incoming call, this one applies. A new Call Reference Number will not be allocated in this case. Example: If in MAP:ProvideRoamingNumber a Call Reference Number is included, this will be used as call reference number in the VMSC.

It is signalled via MAP (phase 3 and up) from GMSC to VMSC and via INAP/CAP from SSP to SCP to be included in all tickets, which will be generated in these entities.

In general a CRN is always assigned to one mobile subscriber.

Exception:

In case of a mobile originating call a MOC Ticket is generated for the originating subscriber. In this case a call reference number will be allocated only if the originating mobile subscriber

1. has O-CSI

2. dials an IN-Number

3. has SCM

In all other cases no call reference is allocated because no other Tickets in other network entities must be correlated with the MOC-Ticket of this subscriber.


The CRN generated in a Siemens MSC will have a size of 5 bytes so it will be unique within a period of at least 45 days (based on a high load traffic model with 1,2’ VLR subscribers making 0,5 calls/h). The CRN will be incremented every time a new CRN has to be generated.

The CRN is safe against recoveries.

A CRN received from another PLMN (within MAP:ProvideRoamingNumber) may have a size of up to 8 bytes.

2.3.25 callTransactionType

2.3.26

2.3.27 CallReferenceNumber ::= OCTET STRING (SIZE (1..8))

This parameter specifies the call type or the transaction type according to the following table:

Values indicated with "n/a" (= not applicable) are for future use.

"Emergency call" is only applicable when using the emergency key or dialling the emergency number (e.g. 112).

coding a:

CallTransactionTypeA ::= INTEGER { default ( 0), moc ( 1), mtc ( 2), emergencyCall ( 3), pbxOutgoingCall ( 4), pbxIncomingCall ( 5), mocOACSU ( 6), inCallModMoc ( 8), inCallModMtc ( 9), sSRegistration (10), sSErasure (11), sSActivation (12), sSDeactivation (13), sSInterrogation (14), sSInvocation (15), mocSMS (16), mtcSMS (17), mocDPAD (20), inAttempt (21), inAnswered (22), roaming (26), transit (27), callForwarding (29), emergencyCallTrace (32), roaAttempt (34), mtLocationRequest (35),


mtLocationRequestAttempt (36), moLocationRequest (37), moLocationRequestAttempt (38), niLocationRequest (39), niLocationRequestAttempt (40), camelCallForwarding (42), termCAMELRecord (43), voiceGroupServiceAMSC (44), termCAMELIntAttemptRecord (45), voiceGroupServiceRMSC (46), sSUnstructuredProcessingPh1 (58), processUnstructuredSSRequestMo (59), unstucturedSSRequestNi (60), unstucturedSSNotifyNi (61), mocAttempt (65), mtcAttempt (66), emyAttempt (67)}


+-------------------------------------------------------------------+¦ callTransactionType ¦ ¦+--------------------------------+----------------------------------¦¦ binary hex dec ¦ meaning ¦+--------------------------------+----------------------------------¦¦ 0000 0000 00 0 ¦ default ¦¦ 0000 0001 01 1 ¦ moc ¦¦ 0000 0010 02 2 ¦ mtc ¦¦ 0000 0011 03 3 ¦ emergencyCall ¦¦ 0000 0100 04 4 ¦ pbxOutgoingCall ¦¦ 0000 0101 05 5 ¦ pbxIncomingCall ¦¦ 0000 0110 06 6 ¦ mocOACSU ¦¦ 0000 1000 08 8 ¦ inCallModMoc ¦¦ 0000 1001 09 9 ¦ inCallModMtc ¦¦ 0000 1010 0A 10 ¦ sSRegistration ¦¦ 0000 1011 0B 11 ¦ sSErasure ¦¦ 0000 1100 0C 12 ¦ sSActivation ¦¦ 0000 1101 0D 13 ¦ sSDeactivation ¦¦ 0000 1110 0E 14 ¦ sSInterrogation ¦¦ 0000 1111 0F 15 ¦ sSInvocation ¦¦ 0001 0000 10 16 ¦ mocSMS ¦¦ 0001 0001 11 17 ¦ mtcSMS ¦¦ 0001 0100 14 20 ¦ mocDPAD (n/a) ¦¦ 0001 0101 15 21 ¦ inAttempt ¦¦ 0001 0110 16 22 ¦ inAnswered ¦¦ 0001 1010 1A 26 ¦ roaming ¦¦ 0001 1011 1B 27 ¦ transit ¦¦ 0001 1101 1D 29 ¦ callForwarding (n/a) ¦¦ 0010 0000 20 32 ¦ emergencyCallTrace ¦¦ 0010 0010 22 34 ¦ roaAttempt ¦¦ 0010 0011 23 35 ¦ mtLocationRequest ¦¦ 0010 0100 24 36 ¦ mtLocationRequestAttempt ¦¦ 0010 0101 25 37 ¦ moLocationRequest ¦¦ 0010 0110 26 38 ¦ moLocationRequestAttempt ¦¦ 0010 0111 27 39 ¦ niLocationRequest ¦¦ 0010 1000 28 40 ¦ niLocationRequestAttempt ¦¦ 0010 1010 2A 42 ¦ cAMELCF ¦¦ 0010 1011 2B 43 ¦ tCR ¦¦ 0010 1100 2C 44 ¦ voiceGroupServiceAMSC ¦¦ 0010 1101 2D 45 ¦ tCRAttempt ¦¦ 0010 1110 2E 46 ¦ voiceGroupServiceRMSC ¦¦ 0011 1010 3A 58 ¦ sSUnstructuredProcessingPh1 ¦¦ 0011 1011 3B 59 ¦ processUnstructuredSsRequestMo ¦¦ 0011 1100 3C 60 ¦ unstructuredSsRequestNi ¦¦ 0011 1101 3D 61 ¦ unstructuredSsNotifyNi ¦¦ 0100 0001 41 65 ¦ mocAttempt ¦¦ 0100 0010 42 66 ¦ mtcAttempt ¦¦ 0100 0011 43 67 ¦ emyAttempt ¦+-------------------------------------------------------------------+


T-Mobil: MocOACSU, mtcOACSU, SSInvocation are not used. The generation of INAttempt records is suppressed.

CallTransactionTypeA ::= INTEGER { default (0), moc (1), mtc (2), emergencyCall (3), pbxOutgoingCall (4), pbxIncomingCall (5), mocOACSU (6), inCallModMoc (8), inCallModMtc (9), sSRegistration (10), sSErasure (11),

sSActivation (12), sSDeactivation (13), sSInterrogation (14), sSInvocation (15), mocSMS (16), mtcSMS (17), mocDPAD (20), inAttempt (21), inAnswered (22), roaming (26), transit (27), callForwarding (29), emergencyCallTrace (32), roaAttempt (34), mtLocationRequest (35), mtLocationRequestAttempt (36), moLocationRequest (37), moLocationRequestAttempt (38), niLocationRequest (39), niLocationRequestAttempt (40), camelCallForwarding (42), termCAMELIntRecord (43), voiceGroupServiceAMSC (44), termCAMELIntAttemptRecord (45), voiceGroupServiceRMSC (46), sSUnstructuredProcessingPh1 (58), processUnstructuredSSRequestMo (59), unstucturedSSRequestNi (60), unstucturedSSNotifyNi (61), mocAttempt (65), mtcAttempt (66), emyAttempt (67) }


coding b:

CallTransactionTypeB ::= INTEGER { default ( 0), moc ( 1), mtc ( 2), emergencyCall ( 3), pbxOutgoingCall ( 4), pbxIncomingCall ( 5), mocOACSU ( 6), inCallModMoc ( 8), inCallModMtc ( 9), sSRegistration (10), sSErasure (11), sSActivation (12), sSDeactivation (13), sSInterrogation (14), sSUnstructuredProcessingPh1 (15), mODPAD (19), roaming (26), transit (27), callForwarding (29), sMS-MTC (30), sMS-MOC (31), emergencyCallTrace (32), sSInvocation (33), roaAttempt (34), mtLocationRequest (35), mtLocationRequestAttempt (36), moLocationRequest (37), moLocationRequestAttempt (38), niLocationRequest (39), niLocationRequestAttempt (40), termCAMELIntRecord (43), voiceGroupServiceAMSC (44), termCAMELIntAttemptRecord (45), voiceGroupServiceRMSC (46), processUnstructuredSSRequestMo (59), unstucturedSSRequestNi (60), unstucturedSSNotifyNi (61), mocAttempt (65), mtcAttempt (66), emyAttempt (67), cFAttempt (93)}+-------------------------------------------------------------------+


¦ callTransactionType ¦ ¦+--------------------------------+----------------------------------¦¦ binary hex dec ¦ meaning ¦+--------------------------------+----------------------------------¦¦ 0000 0000 00 0 ¦ default ¦¦ 0000 0001 01 1 ¦ moc ¦¦ 0000 0010 02 2 ¦ mtc ¦¦ 0000 0011 03 3 ¦ emergencyCall ¦¦ 0000 0100 04 4 ¦ pbxOutgoingCall ¦¦ 0000 0101 05 5 ¦ pbxIncomingCall ¦¦ 0000 0110 06 6 ¦ mocOACSU ¦¦ 0000 1000 08 8 ¦ inCallModMoc ¦¦ 0000 1001 09 9 ¦ inCallModMtc ¦¦ 0000 1010 0A 10 ¦ sSRegistration ¦¦ 0000 1011 0B 11 ¦ sSErasure ¦¦ 0000 1100 0C 12 ¦ sSActivation ¦¦ 0000 1101 0D 13 ¦ sSDeactivation ¦¦ 0000 1110 0E 14 ¦ sSInterrogation ¦¦ 0000 1111 0F 15 ¦ sSUnstructuredProcessingPh1 ¦¦ 0001 0011 13 19 ¦ moDPAD ¦¦ 0001 1010 1A 26 ¦ roaming ¦¦ 0001 1011 1B 27 ¦ transit ¦¦ 0001 1101 1D 29 ¦ callForwarding ¦¦ 0001 1110 1E 30 ¦ mtcSMS ¦¦ 0001 1111 1F 31 ¦ mocSMS ¦¦ 0010 0000 20 32 ¦ emergencyCallTrace ¦¦ 0010 0001 21 33 ¦ sSInvocation ¦¦ 0010 0010 22 34 ¦ roaAttempt ¦¦ 0010 0011 23 35 ¦ mtLocationRequest ¦¦ 0010 0100 24 36 ¦ mtLocationRequestAttempt ¦¦ 0010 0101 25 37 ¦ moLocationRequest ¦¦ 0010 0110 26 38 ¦ moLocationRequestAttempt ¦¦ 0010 0111 27 39 ¦ niLocationRequest ¦¦ 0010 1000 28 40 ¦ niLocationRequestAttempt ¦¦ 0010 1011 2B 43 ¦ tIR ¦¦ 0010 1100 2C 44 ¦ voiceGroupServiceAMSC ¦¦ 0010 1101 2D 45 ¦ tIRAttempt ¦¦ 0010 1110 2E 46 ¦ voiceGroupServiceRMSC ¦¦ 0011 1011 3B 59 ¦ processUnstructuredSsRequestMo ¦¦ 0011 1100 3C 60 ¦ unstructuredSsRequestNi ¦¦ 0011 1101 3D 61 ¦ unstructuredSsNotifyNi ¦¦ 0100 0001 41 65 ¦ mocAttempt ¦¦ 0100 0010 42 66 ¦ mtcAttempt ¦¦ 0100 0011 43 67 ¦ emyAttempt ¦¦ 0101 1101 5D 93 ¦ cfAttempt ¦+-------------------------------------------------------------------+


CallTransactionTypeB ::= INTEGER { default ( 0), moc ( 1), mtc ( 2), emergencyCall ( 3), pbxOutgoingCall ( 4), pbxIncomingCall ( 5), mocOACSU ( 6), inCallModMoc ( 8), inCallModMtc ( 9), sSRegistration (10), sSErasure (11), sSActivation (12), sSDeactivation (13), sSInterrogation (14), sSUnstructuredProcessingPh1 (15), mODPAD (19), roaming (26), transit (27), callForwarding (29), sMS-MTC (30), sMS-MOC (31), emergencyCallTrace (32), sSInvocation (33), roaAttempt (34), mtLocationRequest (35), mtLocationRequestAttempt (36), moLocationRequest (37), moLocationRequestAttempt (38), niLocationRequest (39), niLocationRequestAttempt (40), termCAMELIntRecord (43), voiceGroupServiceAMSC (44), termCAMELIntAttemptRecord (45), voiceGroupServiceRMSC (46), processUnstructuredSSRequestMo (59), unstucturedSSRequestNi (60), unstucturedSSNotifyNi (61), mocAttempt (65), mtcAttempt (66), emyAttempt (67), cFAttempt (93)}coding c:


CallTransactionTypeC ::= INTEGER { -- strictly limited to 1 byte coding -- therefor last part described as negative values default ( 0), moc ( 1), mtc ( 2), emergencyCall ( 3), mocOACSU ( 6), inCallModMoc ( 8), inCallModMtc ( 9), sSRegistration (10), sSErasure (11), sSActivation (12), sSDeactivation (13), sSInterrogation (14), sSUnstructuredProcessingPh1 (15), mODPAD (19), roaming (26), transit (27), callForwarding (29), mtcSMS (30), mocSMS (31), emergencyCallTrace (32), sSInvocation (33), roaAttempt (34), mtLocationRequest (35), mtLocationRequestAttempt (36), moLocationRequest (37), moLocationRequestAttempt (38), niLocationRequest (39), niLocationRequestAttempt (40), termCAMELIntRecord (43), voiceGroupServiceAMSC (44), termCAMELIntAttemptRecord (45), voiceGroupServiceRMSC (46), processUnstructuredSSRequestMo (59), unstucturedSSRequestNi (60), unstucturedSSNotifyNi (61), mocAttempt (65), mtcAttempt (66), emyAttempt (67), cfAttempt (93), sUBOG (-127), -- (129), sUBIC (-126), -- (130), pBXOG (-111), -- (145), pBXIC (-110), -- (146), pBX-SS-REG (-102), -- (154), pBX-SS-ERAS (-101) -- (155)}

+-------------------------------------------------------------------+¦ callTransactionType ¦ ¦+--------------------------------+----------------------------------¦


¦ binary hex dec ¦ meaning ¦+--------------------------------+----------------------------------¦¦ 0000 0000 00 0 ¦ default ¦¦ 0000 0001 01 1 ¦ moc ¦¦ 0000 0010 02 2 ¦ mtc ¦¦ 0000 0011 03 3 ¦ emergencyCall ¦¦ 0000 0110 06 6 ¦ mocOACSU ¦¦ 0000 1000 08 8 ¦ inCallModMoc ¦¦ 0000 1001 09 9 ¦ inCallModMtc ¦¦ 0000 1010 0A 10 ¦ sSRegistration ¦¦ 0000 1011 0B 11 ¦ sSErasure ¦¦ 0000 1100 0C 12 ¦ sSActivation ¦¦ 0000 1101 0D 13 ¦ sSDeactivation ¦¦ 0000 1110 0E 14 ¦ sSInterrogation ¦¦ 0000 1111 OF 15 ¦ sSUnstructuredProcessingPh1 ¦¦ 0001 0011 13 19 ¦ moDPAD ¦¦ 0001 1010 1A 26 ¦ roaming ¦¦ 0001 1011 1B 27 ¦ transit ¦¦ 0001 1101 1D 29 ¦ callForwarding ¦¦ 0001 1110 1E 30 ¦ mtcSMS ¦¦ 0001 1111 1F 31 ¦ mocSMS ¦¦ 0010 0000 20 32 ¦ emergencyCallTrace ¦¦ 0010 0001 21 33 ¦ sSInvocation ¦¦ 0010 0010 22 34 ¦ roaAttempt ¦¦ 0010 0011 23 35 ¦ mtLocationRequest ¦¦ 0010 0100 24 36 ¦ mtLocationRequestAttempt ¦¦ 0010 0101 25 37 ¦ moLocationRequest ¦¦ 0010 0110 26 38 ¦ moLocationRequestAttempt ¦¦ 0010 0111 27 39 ¦ niLocationRequest ¦¦ 0010 1000 28 40 ¦ niLocationRequestAttempt ¦¦ 0010 1011 2B 43 ¦ tIR ¦¦ 0010 1100 2C 44 ¦ voiceGroupServiceAMSC ¦¦ 0010 1101 2D 45 ¦ tIRAttempt ¦¦ 0010 1110 2E 46 ¦ voiceGroupServiceRMSC ¦¦ 0011 1011 3B 59 ¦ processUnstructuredSsRequestMo ¦¦ 0011 1100 3C 60 ¦ unstructuredSsRequestNi ¦¦ 0011 1101 3D 61 ¦ unstructuredSsNotifyNi ¦¦ 0100 0001 41 65 ¦ mocAttempt ¦¦ 0100 0010 42 66 ¦ mtcAttempt ¦¦ 0100 0011 43 67 ¦ emyAttempt ¦¦ 0101 1101 5D 93 ¦ cfAttempt ¦¦ 1000 0001 81 -127 ¦ sUBOG ¦¦ 1000 0010 82 -126 ¦ sUBIC ¦¦ 1001 0001 91 -111 ¦ pBXOG ¦¦ 1001 0010 92 -110 ¦ pBXIC ¦¦ 1001 1010 9A -102 ¦ pBX-SS-REG ¦¦ 1001 1011 9B -101 ¦ pBX-SS-ERAS ¦¦ ¦+-------------------------------------------------------------------+

2.3.28 callTransferThirdParty

CallTransferThirdParty ::= OCTET STRING (SIZE (2..17)) -- according to 3G TS 24.008 -- OCTET 1 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2-17 digits, digits are coded as TBCD-string

The parameter callTransferThirdPartycontains the other party of the transferred call. It is inroduced for the feature Enhanced Call Transfer in CS3.0.


2.3.29


2.3.30 CallTransactionTypeC ::= INTEGER { -- strictly limited to 1 byte coding -- therefor last part described as negative values default (0), moc (1), mtc (2), emergencyCall (3), mocOACSU (6), inCallModMoc (8), inCallModMtc (9), sSRegistration (10), sSErasure (11), sSActivation (12), sSDeactivation (13), sSInterrogation (14), sSUnstructuredProcessingPh1 (15), mODPAD (19), roaming (26), transit (27), callForwarding (29), mtcSMS (30), mocSMS (31), emergencyCallTrace (32), sSInvocation (33), roaAttempt (34), mtLocationRequest (35), mtLocationRequestAttempt (36), moLocationRequest (37), moLocationRequestAttempt (38), niLocationRequest (39), niLocationRequestAttempt (40), termCAMELIntRecord (43), voiceGroupServiceAMSC (44), termCAMELIntAttemptRecord (45), voiceGroupServiceRMSC (46), processUnstructuredSSRequestMo (59), unstucturedSSRequestNi (60), unstucturedSSNotifyNi (61), mocAttempt (65), mtcAttempt (66), emyAttempt (67), cfAttempt (93), sUBOG (-127), -- (129), sUBIC (-126), -- (130), pBXOG (-111), -- (145), pBXIC (-110), -- (146), pBX-SS-REG (-102), -- (154), pBX-SS-ERAS (-101) -- (155) }


2.3.31 callWaitInvocCount

CallWaitInvocCount ::= INTEGER -- Number Of SS Call Waiting Invocations -- range 0-127


2.3.32 camelCommonData

CamelCommonData ::= SEQUENCE { timeOfCAMELLeg TimeOfCAMELLeg OPTIONAL, dateOfCAMELLeg DateOfCAMELLeg OPTIONAL, durationOfCAMELLeg DurationOfCAMELLeg OPTIONAL, camelInitCfIndicator CamelInitCfIndicator OPTIONAL, chargeBandNumber ChargeBandNumber OPTIONAL}

2.3.33 camelDialog

CamelDialog ::= SEQUENCE { inServiceKey InServiceKey , gsmScfAddress GsmScfAddress OPTIONAL, defaultCallHandling DefaultCallHandling OPTIONAL, levelOfCamelService LevelOfCamelService OPTIONAL, changeFlags ChangeFlags OPTIONAL, numberOfDpEncountered NumberOfDpEncountered OPTIONAL, mcrDestinationNumber McrDestinationNumber , chargingTimeData ChargingTimeData , camelInitCfIndicator CamelInitCfIndicator OPTIONAL, camelFFDataIncLeg camelFFDataIncLeg OPTIONAL, camelFFDataIncAppendInd camelFFDataIncLegAppendInd OPTIONAL, camelFFDataOutLeg camelFFDataOutLeg OPTIONAL, camelFFDataOutAppendInd camelFFDataOutLegAppendInd OPTIONAL}

Data belonging to the outgoing leg of a CAMEL call.

2.3.34 camelFFDataIncAppendInd

CamelFFDataIncAppendInd ::= OCTET STRING (SIZE (1)) -- BOOL

The parameter indicates that the free format data received for the incoming leg has to be appended to previously sent free format data which might be present in a previous partial ticket.


2.3.35

2.3.36 CamelFFDataIncAppendInd ::= OCTET STRING (SIZE (1) )

2.3.37 camelFFDataIncLeg

CamelFFDataIncLeg ::= OCTET STRING (SIZE (1..160))

This attribute contains transparent charging data, received from the gsmSCF (sent by SCP as Free Format Data in an FCI message of a CAMEL-Call for the incoming leg). With CAP PH3 a maximal length of 160 bytes is possible.

+-------------------------------------------------------------------+¦ camelFFDataIncLeg ¦ length = 1..160 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ free format data for incoming CAMEL leg ¦+-------------------------------------------------------------------+

2.3.38

2.3.39 CamelFFDataIncLeg ::= OCTET STRING (SIZE (1..160))

2.3.40 camelFFDataOutAppendInd

CamelFFDataOutAppendInd ::= OCTET STRING (SIZE (1)) -- BOOL

The parameter indicates that the free format data received for the outgoing leg has to be appended to previously sent free format data which might be present in a previous partial ticket.


2.3.41

2.3.42 CamelFFDataOutAppendInd ::= OCTET STRING (SIZE (1) )

2.3.43 -- BOOL

2.3.44 camelFFDataOutLeg

CamelFFDataOutLeg ::= OCTET STRING (SIZE (1..160))

This attribute contains transparent charging data, received from the gsmSCF (sent by SCP as Free Format Data in an FCI message of a CAMEL-Call for the outgoing leg). With CAP PH3 a maximal length of 160 bytes is possible.

+-------------------------------------------------------------------+¦ camelFFDataOutLeg ¦ length = 1..160 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ free format data for outgoing CAMEL leg ¦+-------------------------------------------------------------------+CamelFFDataOutLeg ::= OCTET STRING (SIZE (1..160))-- BOOL


2.3.45 camelInitCfIndicator

CamelInitCfIndicator ::= OCTET STRING (SIZE (1)) -- BOOL

The parameter must be present in records with call transaction type CAMEL_CF and TermCAMELIntRecord if the following conditions apply:

The called subscriber owns both T-CSI and O-CSI

T-CSI based TDP12 dialog changing the destination

SCP sends ‘O-CSI applicable’ flag

The purpose of this field is to distinguish CAMEL call forwarding service scenarios from standard GSM call forwarding scenarios.The flag for a CAMEL initiated call forwarding is generated, if a TDP12-Trigger is followed by a TDP2-Trigger, both triggers are CSI based and both are belonging to the same subscriber.In addition the SCP has to be send a OP:CON with the flag OCSI_Applicable with the CDPA ofthe new subscriber( see /IN/).

+-------------------------------------------------------------------+¦ camelInitCfIndicator ¦ length = 1 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ 00000000 false ¦ no call forwarding indicated ¦¦ 00000001 true ¦ call forwarding indicated ¦+-------------------------------------------------------------------+

The parameter is only present with the value ‘1’.

2.3.46 CamelInitCfIndicator ::= OCTET STRING (SIZE (1)) -- BOOL

2.3.47

2.3.48 carrierAccessCode

CarrierAccessCode ::= TBCD-String (SIZE(1..3))

+-------------------------------------------------------------------+¦ carrierAccessCode ¦ length = 1..3 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure ¦¦ ¦¦ octet string (max. 6 digits) coded as TBCD string ¦¦ ¦+-------------------------------------------------------------------+

If there are less than 4 digits available, the filler is used to indicate that no more valid digits will follow.


With the preliminary work for Carrier Routing in CS2.0 this is also available for GSM and UMTS. It is possible to insert up to 6 digits (carrier prefix and carrier code together could have a length of up to six digits).

2.3.49

2.3.50 CarrierAccessCode ::= TBCD-String (SIZE(1..3))

2.3.51 causeForTermination

coding a:

CauseForTerminationA ::= OCTET STRING (SIZE(1)) -- System Internal Reasons For Call Failure -- range B'00 to B'FF

+-------------------------------------------------------------------+¦ causeForTermination ¦ ¦+--------------------------------+----------------------------------¦¦ content (binary) ¦ meaning ¦+--------------------------------+----------------------------------¦¦ 0000 0000 ¦ ¦¦ 0000 0001 ¦ system internal reasons for call ¦¦ : ¦ failure ¦¦ 1111 1111 ¦ ¦¦ ¦ ¦+-------------------------------------------------------------------+

This field will contain the system internal reasons for call failure (RCF). For details see /CAUS/.

CauseForTerminationA ::= OCTET STRING (SIZE(1)) -- System Internal Reasons For Call Failure -- range B'00 to B'FF


coding b:

CauseForTerminationB ::= OCTET STRING (SIZE(1)) -- abnormalTermination CauseForTerminationB ::= '64'H -- coding according to T-Mobil requirement: fault : 100

+-------------------------------------------------------------------+¦ causeForTermination ¦ ¦+--------------------------------+----------------------------------¦¦ content (decimal) ¦ meaning ¦+--------------------------------+----------------------------------¦¦ 100 ¦ AbnormalTermination ¦¦ ¦ ¦+-------------------------------------------------------------------+

Only one value is applicable: H’64 = D'100'.

2.3.52 CauseForTerminationB ::= OCTET STRING (SIZE(1)) -- abnormalTermination CauseForTerminationB ::= '64'H -- coding according to T-Mobil requirement: fault : 100

2.3.53

2.3.54 cellId

This parameter contains the cell identity as described by /23.003/.

coding a:

CellIdA ::= OCTET STRING (SIZE(7)) -- M1M2M3 Mobile Country Code (MCC) -- N1N2N3 Mobile Network Code (MNC) -- LAC Location Area Code -- CI Cell Identification -- (*) If Not Used: Filled With B'1111 -- OCTET 1-3 -- XXXXXXXX = M2 M1 -- XXXXXXXX = N3(*) M3 -- XXXXXXXX = N2(*) N1 -- OCTET 4-7 -- XXXXXXXX = LAC(LSB) -- XXXXXXXX = LAC(MSB) -- XXXXXXXX = CI(LSB) -- XXXXXXXX = CI(MSB) -- if CDMA coding: octet 1..3 filled with '00'


+-------------------------------------------------------------------+¦ cellId ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ internal structure: ¦ ¦¦ +--------------+ ¦ M1M2M3 Mobile Country Code (MCC) ¦¦ octet 1 ¦ M2 M1 ¦ ¦ ¦¦ +--------------¦ ¦ N1N2N3 Mobile Network Code (MNC) ¦¦ 2 ¦ N3(*) M3 ¦ ¦ LAC Location Area Code ¦¦ +--------------¦ ¦ CI Cell Identification ¦¦ 3 ¦ N2(*) N1 ¦ ¦ (*) if not used: filled ¦¦ +--------------¦ ¦ with value B'1111 ¦¦ 4 ¦ LAC (lsb) ¦ ¦ ¦¦ +--------------¦ ¦ ¦¦ 5 ¦ LAC (msb) ¦ ¦ ¦¦ +--------------¦ ¦ ¦¦ 6 ¦ CI (lsb) ¦ ¦ ¦¦ +--------------¦ ¦ ¦¦ 7 ¦ CI (msb) ¦ ¦ ¦¦ +--------------+ ¦ ¦+-------------------------------------------------------------------+

The cell identity from the start of the call is always entered in this field.

MCC is coded as TBCD string (octets 1, 2). The default value is H'FFF'.MNC is coded as TBCD string (octet 2, 3). The default value is H'FFF'.LAC and CI are binary coded as shown above. The default value for octets 4..7 is H'00'.

Note!

The byte 6 and 7 (CI) contains in case of 3G (UMTS) the service area code- SAC defined in3G TS 24.008, 3G TS 25.413 (3G TS 32.005).

CellIdA ::= OCTET STRING (SIZE(7)) -- M1M2M3 Mobile Country Code (MCC) -- N1N2N3 Mobile Network Code (MNC) -- LAC Location Area Code -- CI Cell Identification -- (*) If Not Used: Filled With B'1111 -- OCTET 1-3 -- XXXXXXXX = M2 M1 -- XXXXXXXX = N3(*) M3 -- XXXXXXXX = N2(*) N1 -- OCTET 4-7 -- XXXXXXXX = LAC(LSB) -- XXXXXXXX = LAC(MSB) -- XXXXXXXX = CI(LSB) -- XXXXXXXX = CI(MSB) -- if CDMA coding: octet 1..3 filled with '00'


coding b:

CellIdB ::= OCTET STRING (SIZE(2)) -- OCTET 1-2 -- XXXXXXXX = CI(MSB) -- XXXXXXXX = CI(LSB)

+-------------------------------------------------------------------+¦ cellId ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ internal structure: ¦ ¦¦ +--------------+ ¦ ¦¦ octet 1 ¦ CI (msb) ¦ ¦ CI Cell Identification ¦¦ +--------------¦ ¦ ¦¦ 2 ¦ CI (lsb) ¦ ¦ ¦¦ +--------------+ ¦ ¦+-------------------------------------------------------------------+

The cell identity from the start of the call is always entered in this field.The default value is H'0000'.

Note!

The byte 1 and 2 (CI) contains in case of 3G (UMTS) the service area code - SAC defined in3G TS 24.008, 3G TS 25.413 (3G TS 32.005).

CellIdB ::= OCTET STRING (SIZE(2)) -- OCTET 1-2 -- XXXXXXXX = CI(MSB) -- XXXXXXXX = CI(LSB)


coding d:

CellIdD ::= OCTET STRING (SIZE(7)) -- M1M2M3 Mobile Country Code (MCC) -- N1N2N3 Mobile Network Code (MNC) -- LAC Location Area Code -- CI Cell Identification -- (*) If Not Used: Filled With B'1111 -- OCTET 1-3 -- XXXXXXXX = M2 M1 -- XXXXXXXX = N3(*) M3 -- XXXXXXXX = N2(*) N1 -- OCTET 4-7 -- XXXXXXXX = LAC(MSB) -- XXXXXXXX = LAC(LSB) -- XXXXXXXX = CI(MSB) -- XXXXXXXX = CI(LSB) -- if CDMA coding: octet 1..3 filled with '00'

+-------------------------------------------------------------------+¦ cellId ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ internal structure: ¦ ¦¦ +--------------+ ¦ M1M2M3 Mobile Country Code (MCC) ¦¦ octet 1 ¦ M2 M1 ¦ ¦ ¦¦ +--------------¦ ¦ N1N2N3 Mobile Network Code (MNC) ¦¦ 2 ¦ N3(*) M3 ¦ ¦ LAC Location Area Code ¦¦ +--------------¦ ¦ CI Cell Identification ¦¦ 3 ¦ N2(*) N1 ¦ ¦ (*) if not used: filled ¦¦ +--------------¦ ¦ with value B'1111 ¦¦ 4 ¦ LAC (msb) ¦ ¦ ¦¦ +--------------¦ ¦ ¦¦ 5 ¦ LAC (lsb) ¦ ¦ ¦¦ +--------------¦ ¦ ¦¦ 6 ¦ CI (msb) ¦ ¦ ¦¦ +--------------¦ ¦ ¦¦ 7 ¦ CI (lsb) ¦ ¦ ¦¦ +--------------+ ¦ ¦+-------------------------------------------------------------------+

The cell identity from the start of the call is always entered in this field.

MCC is coded as TBCD string (octets 1, 2). The default value is H'FFF'.

MNC is coded as TBCD string (octet 2, 3). The default value is H'FFF'.

LAC and CI are binary coded as shown above. The default value for octets 4..7 is H'00'.

Note!


2.3.55 changeFlags

ChangeFlags ::= BIT STRING (SIZE(2)) -- callingPartyNumberModified (0),


-- callingPartyCategoryModified (1), -- originalCalledPartyNumberModified (2), -- genericNumbersModified (3), -- redirectingPartyNumberModified (4), -- redirectionCounterModified (5)

This parameter indicates which parameters have been modified by SCP during a CAMEL call.It will be set by the SSF, dependent on which new call parameters have been received.

Remark for CS2.1:In case of no parameter change in OP:CON from SCP, the SSF does not set up the changeFlags , i.e. the parameter will not be provided.In case of no parameter change in OP:CUE from SCP, the SSF does not set up the changeFlags , i.e. the parameter will not be provided.

The parameter is coded as BIT-String.

+-------------------------------------------------------------------+¦ changeFlags ¦ length = 2 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ ¦¦ First octet: ¦¦ ¦¦ according ASN1 encoding of BIT-String ¦¦ ¦¦ Second octet: ¦¦ ¦¦ 8 7 6 5 4 3 2 1 ¦¦ +-------------------------------¦ ¦¦ ¦ ¦ ¦¦ +-------------------------------¦ ¦¦ coded as follows ¦¦ ¦¦ BIT 8 used for ’callingPartyNumberModified’ ¦¦ BIT 7 used for ’callingPartyCategoryModified’ ¦¦ BIT 6 used for ’originalCalledPartyNumberModified’ ¦¦ BIT 5 used for ’genericNumbersModified’ ¦¦ BIT 4 used for ’redirectingPartyNumberModified’ ¦¦ BIT 3 used for ’redirectionCounterModified’ ¦¦ BIT 2..1 reserved ¦¦ ¦+-------------------------------------------------------------------+


2.3.56

2.3.57 ChangeFlags ::= BIT STRING (SIZE(2)) -- callingPartyNumberModified (0), -- callingPartyCategoryModified (1), -- originalCalledPartyNumberModified (2), -- genericNumbersModified (3), -- redirectingPartyNumberModified (4), -- redirectionCounterModified (5)

2.3.58

2.3.59 channelCoding (not for PCS projects)

ChannelCoding ::= ENUMERATED { tch-F9komma6 (2), tch-F14komma4 (3), not-applicable (255)}

For HSCSD calls (see 2.3.1 additionalBearerServiceInfo ) this parameter specifies the used channel coding.

2.3.60 ChannelCoding ::= ENUMERATED { tch-F9komma6 (2), ch-F14komma4 (3) }

2.3.61 chargeAdviceElement

ChargeAdviceElement ::= OCTET STRING (SIZE(14)) -- containing e1 .. e7 -- two byte per e parameter -- example: e1=100 coded as '0064 XXXX XXXX XXXX XXXX XXXX XXXX'

This parameter contains the elements e1 to e7 according to /24.080/ and /22.024/.

Two octets per e-parameter, the elements e1 to e7 have a fixed format.

Each element is coded as a 2 byte integer according to the following table:

e1: range 0 - 819.1 resolution 0.1






e6: range 0 - 8191 resolution 1.0


Elements which are not present, are coded as zero.

2.3.62

2.3.63 ChargeAdviceElement ::= OCTET STRING (SIZE(14)) -- containing e1 .. e2 -- two byte per e parameter -- example: e1=100 coded as '0064 XXXX XXXX XXXX XXXX XXXX XXXX'

2.3.64

2.3.65 chargeAdviceInfo

ChargeAdviceInfo ::= CHOICE { chargeAdviceElement ChargeAdviceElement, aOCParameter AOCParameter}

chargeAdviceInfo is a choice of chargeAdviceElement and AOCParameter.

If the feature flag CAITARSW is active, a maximum of 6 e-parameter sets can be written in the record if they are available.

If this flag is not active, only the last e-paramter set is available in the record.

In case of Advice of Charge Charginglevel each chargeAdviceElement / AOCParameter has a corresponding timestamp noted in the same record. If more than 5 tariff switches occur, the last AOCParameter will contain the data corresponding to the last tariff switch.


2.3.66 The number of chargeAdviceElement / AOCParameter fields depends from the featureflag CAITARSW. If this flag is released a maximum of 5 e-parameter sets can be write in the record if they are available.

2.3.67 If this Flag is not released only the last e-paramter set is available in the record.

2.3.68 In case of Advice of Charge Charginglevel each chargeAdviceElement / AOCParameter has a corresponding timestamp noted in the same record.

2.3.69 chargeAdviceInformation

ChargeAdviceInformation ::= SEQUENCE { chargeAdviceElement ChargeAdviceElement OPTIONAL, aOCParameter AOCParameter OPTIONAL}

chargeAdviceInformation is a SEQUENCE OF chargeAdviceElement or AOCParameter.The length of this field is depending on the number of available e-parameter sets.

Hence the length can change from one record to the other.


2.3.70 chargeBandNumber

The chargeBandNumber is the chargeBandCallingLine from the SCP.

coding a:

ChargeBandNumberA ::= INTEGER

+-------------------------------------------------------------------+¦ chargeBandNumber ¦ length = 1..3 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ chargeBandCallingLine from SCP ¦+-------------------------------------------------------------------+


ChargeBandNumberA ::= INTEGER -- like a mobile zone

coding b:

ChargeBandNumberB ::= OCTET STRING (SIZE(2)) -- containing the chargeband in the old fixed coding -- 2 bytes, e.g. 1 coded as 0001

2.3.71 chargeIndicator

ChargeIndicator ::= INTEGER { undefined (0), charge (1), nocharge (2)}

The contents of this field will be derived from the charge indicator recieved from the B-side of the call (in case of Call Forwarding records, the charge indicator received from the C-party) and in the case of call attempt from the mapping result of the RCF or RCT. For both cases, the current charge status of the call will be also taken into account. That means a current charge status of ‚no charge‘ can not be changed any more. The charge indicator can be also determined from the charging zone and from the GCOS settings of announcement groups. For special IN-calls the charge indicator can be determined by SCP exclusively.

ChargeIndicator ::= INTEGER{ undefined (0), charge (1), nocharge (2) }


2.3.72 chargingInformation

This field is for the project specific Finnish concept of ISUP backward charging messages.+-------------------------------------------------------------------+¦ chargingInformation ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ SET OF up to 6 tariffInfoPack ¦¦ ¦+-------------------------------------------------------------------+

The length is depending on the number of tariffInfoPack noted in the record. Hence the length can change from one record to the other.

2.3.73 chargingPulses

ChargingPulses ::= OCTET STRING (SIZE(2)) -- containing meterpulses -- example: 500 coded as '01F4' -- Range 1..32000

This parameter contains the number of charging pulses for that call (received via meterpulse messages).

ChargingPulses ::= OCTET STRING (SIZE(2)) -- containing meterpulses -- example: 500 coded as '01F4' -- Range 1..32000

2.3.74 chargingtimeData

ChargingTimeData ::= SEQUENCE { startOfChargingdate StartOfChargingdate, startOfChargingtime StartOfChargingtime, callDuration CallDuration OPTIONAL}

This parameter contains all charging-relevant time data.

+-------------------------------------------------------------------+¦ chargingtimeData ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ SEQUENCE containing ¦¦ startOfChargingdate ¦¦ startOfChargingtime ¦¦ callDuration ¦+-------------------------------------------------------------------+

The length depends on the number of available fields in startOfChargingTime.



2.3.75 chrgContainer1

ChrgContainer1 ::= OCTET STRING (SIZE(1..32))

This parameter is provided for flexible use (e.g. for additional charging data, required by Change Requests).

+-------------------------------------------------------------------+¦ chrgContainer1 ¦ variable or define length ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ ¦¦ 1 ... 32 octets handled transparently ¦¦ ¦+-------------------------------------------------------------------+

ChrgContainer1 ::= OCTET STRING (SIZE(1..32))


2.3.76 chrgContainer2 ... 5

ChrgContainer2 ::= OCTET STRING (SIZE(2))ChrgContainer3 ::= OCTET STRING (SIZE(2))ChrgContainer4 ::= OCTET STRING (SIZE(2))ChrgContainer5 ::= OCTET STRING (SIZE(2))

These parameters are provided for flexible use (e.g. for additional charging data, required by Change Requests).+-------------------------------------------------------------------+¦ chrgContainerX ¦ length = 2 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ ¦¦ 2 octets handled transparently ¦¦ ¦+-------------------------------------------------------------------+

ChrgContainer2 ::= OCTET STRING (SIZE(2))ChrgContainer3 ::= OCTET STRING (SIZE(2))ChrgContainer4 ::= OCTET STRING (SIZE(2))ChrgContainer5 ::= OCTET STRING (SIZE(2))

2.3.77 cicIc, cicOg

CicIc ::= OCTET STRING (SIZE(3)) -- OCTET 1-2 -- pcmUnitOfCic -- OCTET 3 -- channelOfCic

CicOg ::= OCTET STRING (SIZE(3)) -- OCTET 1-2 -- pcmUnitOfCic -- OCTET 3 -- channelOfCic

The cic is an identifier for the circuit used in #7 signalling, cicOg stands for the outgoing circuit and cicIc for the incoming circuit.


+-------------------------------------------------------------------+¦ cic ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ ¦¦ internal structure: ¦¦ ¦¦ 8 7 6 5 4 3 2 1 ¦¦ +-------------------------------¦ pcmUnitOfCic 2 Bytes ¦¦ 1 ¦ pcmUnitOfCic (msb) ¦ (range 0:681) ¦¦ +-------------------------------¦ ¦¦ 2 ¦ pcmUnitOfCic (lsb) ¦ ¦¦ +-------------------------------¦ channelOfCic 1 Byte ¦¦ 3 ¦ channelOfCic ¦ (range 0: 31) ¦¦ +-------------------------------+ ¦¦ ¦+-------------------------------------------------------------------+

pcmUnitOfCic: 2 bytes binary coded, range 0:681

channelOfCic: 1 byte binary coded, range 0:31

CicIc ::= OCTET STRING (SIZE(3)) -- OCTET 1-2 -- pcmUnitOfCic -- OCTET 3 -- channelOfCic

CicOg ::= OCTET STRING (SIZE(3)) -- OCTET 1-2 -- pcmUnitOfCic -- OCTET 3 -- channelOfCic


2.3.78 cphIndication (not for PCS projects)

CphIndication ::= ENUMERATED { noCallPartyHandlingInvoked (0), callPartyHandlingInvoced (1)}

This field gives an indication of the invocation of call party handling.

CphIndication ::= ENUMERATED { noCallPartyHandlingInvoked (0), callPartyHandlingInvoced (1) }

2.3.79 connectedSwitchId

connectedSwitchId ::= CHOICE { origTermBscId OrigTermBscId, dAId DAId}

2.3.80 dAId (not for PCS projects)

DAId ::= TBCD-String (SIZE(1..17))

This parameter identifies the access between MSC and the wired PABX. The common MSISDN of the PABX will be used for this purpose. The value is specific for each DA-system, i.e. PABX directory number with or without extension.

+-------------------------------------------------------------------+¦ dAId ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ ¦¦ MSISDN PABX ISDN number ¦+-------------------------------------------------------------------+

This number contains a country code, national destination code and the direct access digits (max. 32 digits, coded as TBCD-string).

If a fixed length for the MSISDN is selected, the remaining octets will be filled up with the filler value.

DAId ::= TBCD-String (SIZE(8)) -- OCTET 1-8 -- Country Code (CC) = 1-3 digits as in CCITT Rec. E 163 -- National Destination Code (NDC)= variable length -- Subscriber Number (SN)


2.3.81 dateOfCAMELLeg

DateOfCAMELLeg ::= OCTET STRING (SIZE(3)) -- octets BCD coded -- yy: year (2 digits) -- mm: month (2 digits) -- dd: day (2 digits) -- example: march 14th. 1997 coded as -- '970314'

This parameter specifies the date when a CAMEL outgoing leg was set up and is only present if an IN service was actually triggered.

DateOfCAMELLeg ::= OCTET STRING (SIZE(3)) -- octets BCD coded -- yy: year (2 digits) -- mm: month (2 digits) -- dd: day (2 digits) -- example: march 14th. 1997 coded as -- '970314'

2.3.82 defaultCallHandling

DefaultCallHandling ::= OCTET STRING (SIZE (1)) -- RANGE (0:127)

+-------------------------------------------------------------------+¦ defaultCallHandling ¦ length = 1 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ not present ¦ IN-dialogue (if IN triggered) ¦¦ ¦ successful ¦¦ 00000000 false ¦ IN-dialogue failed, DCH-continue ¦¦ ¦ call with dialled digits ¦¦ 00000001 true ¦ IN-dialogue failed, DCH-release ¦¦ ¦ call ¦+-------------------------------------------------------------------+

The defaultCallHandling (DCH) is evaluated if a CSI is received during the SCP dialogue.

The parameter reflects the call handling in case of a failed IN dialogue with the gsmSCF.

The parameter shows the response of the MSC if the dialogue to the SCP fails.

DefaultCallHandling ::= OCTET STRING (SIZE (1)) -- RANGE (0:127)

2.3.83 destByOptimalRoutingMmcEcf

DestByOptimalRoutingMmcEcf ::= OCTET STRING (SIZE (2..17)) -- according to 3G TS 24.008 -- OCTET 1 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan


-- OCTET 2-17 -- maximal 32 digits coded as TBCD-String -- and filled up with fillers

In case of ORMMC this parameter contains the E.164 address of the VLR where the B-party is roaming and which the call is routed to.

In case of ORECF the destByOptimalRoutingMmcEcf contains the FTN (C-party).

DestinationByOptimalRoutingMmcEcf ::= OCTET STRING(SIZE (2..17))-- according to 3G TS 24.008-- OCTET 1-- BIT 8 = extension bit (always 1)-- BIT 7-5 = type of number-- BIT 4-1 = numbering plan-- OCTET 2-17-- maximal 32 digits coded as TBCD-String-- and filled up with fillers

2.3.84 dialledOtherParty

DialledOtherParty ::= OCTET STRING (SIZE(2..17)) -- according to 3G TS 24.008 -- OCTET 1 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2-17 -- maximal 32 digits coded as TBCD-String -- and filled up with fillers

This parameter identifies the partner of the call. For example in case of MOC it will be the called party number, in case of MTC the calling party number. For details please refer to /MCR/.


+-------------------------------------------------------------------+¦ dialledOtherParty ¦ length = 2..17 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure as defined in GSM 04.08 : ¦¦ ¦¦ First octet default: ¦¦ ¦¦ BIT 8 (msb): extension bit (always 1) B'1 ¦¦ BIT 7-5 : type of number B'000 ¦¦ BIT 4-1 : numbering plan B'0000 ¦¦ ¦¦ Following octets: ¦¦ max. 32 digits coded as TBCD-string B'1111 ¦¦ ¦+-------------------------------------------------------------------+

The maximum number of digits available in this field depends on the length of the field itself (if the default length was changed to a lower value). If not the full length of the field is used for the digits, the filler is used to indicate that no more significant digits will follow.

DialledOtherParty ::= OtherPartyLongNumber

2.3.85 drcCallId

DrcCallId ::= OCTET STRING (SIZE(3..7)) -- length 3 or 4 for feature Distance Related Charging (coding 'a') -- length 6 or 7 for feature General Call ID (coding 'b') -- the minor length is available if ODFEAT10 is released

For the parameter drcCallId several codings exist.

Coding ‘a’ of the parameter comprises a value which is unique for at least 11 days (based on a high load traffic model with 1,2’ VLR subscribers making 0,5 calls/h). The ID will be incremented every time a new call ID has to be generated. The validity is limited within the MSC.

The ID is safe against recoveries.

Coding ‘b’ of the parameter contains first the Signalling Point Code (3 byte) of the MSC in which the Id is generated. The available SPC (International Network 0 or 1, or National Network 0 or 1) will be taken. The SPC will be followed by the 3..4 byte value as described by coding ‘a’. The validity is limited within the own PLMN.

Note that the codings are fixed for each project.


coding a:+-------------------------------------------------------------------+¦ drcCallId ¦ length = 3..4 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning : see before ¦+-------------------------------------------------------------------¦¦ ¦¦ 8 7 6 5 4 3 2 1 ¦¦ +-------------------------------¦ ¦¦ 1 ¦ ¦ ¦¦ ¦ ¦ ¦¦ 2 ¦ variable length! ¦ ¦¦ ¦ recovery safe value being ¦ ¦¦ 3 ¦ unique for at least 11 days ¦ ¦¦ ¦ ¦ ¦¦ 4 ¦ ¦ ¦¦ +-------------------------------+ ¦¦ ¦+-------------------------------------------------------------------+

coding b:+-------------------------------------------------------------------+¦ drcCallId ¦ length = 6..7 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning : see before ¦+-------------------------------------------------------------------¦¦ ¦¦ 8 7 6 5 4 3 2 1 ¦¦ +-------------------------------¦ ¦¦ 1 ¦ ¦ ¦¦ +- -¦ ¦¦ 2 ¦ signalling point code of MSC ¦ ¦¦ +- -¦ ¦¦ 3 ¦ ¦ ¦¦ +-------------------------------¦ ¦¦ 4 ¦ ¦ ¦¦ ¦ ¦ ¦¦ 5 ¦ variable length! ¦ ¦¦ ¦ recovery safe value being ¦ ¦¦ 6 ¦ unique for at least 11 days ¦ ¦¦ ¦ ¦ ¦¦ 7 ¦ ¦ ¦¦ +-------------------------------+ ¦¦ ¦+-------------------------------------------------------------------+

DrcCallId ::= OCTET STRING (SIZE(3..6)) -- only valid if validity of origin billing id is set in active

-- fields and CRN flag is false -- length 3 or 6 bytes depending on GENERAL_CALL_ID flag in input -- for 3 byte version use in overlay mode MMMCCBO.DETAILS.CALL_ID -- for 6 byte version take MMMCCBO.ARR(1:6) -- will be copied transparent from input


2.3.86 drcCallRN

DrcCallRN ::= OCTET STRING (SIZE(3..7)) -- length 3 or 4 for feature Distance Related Charging (coding 'a') -- length 6 or 7 for feature General Call ID (coding 'b') -- the minor length is available if ODFEAT10 is released

For the parameter drcCallRN the same codings are available and the same rules apply as for the parameter drcCallId.

The parameter drcCallRN is present if either the feature ‘Distance Related Charging’ or the feature ‘General Call ID’ is active and in addition the feature ‘Call Related Number’ is active. If the ID was generated in a previous call leg, then it will be displayed in the ticket as ‘call related number’ which implies that there must be a ‘drc call ID’ with the same value in a previous ticket. For example, in an MMC the MOC ticket will contain a ‘drc call ID’ while the ROA and MTC tickets will contain a ‘call related number’.

DrcCallRN ::= OCTET STRING (SIZE(3..6)) -- only valid if validity of origin billing id is set in active

-- fields and CRN flag is true -- length 3 or 6 bytes depending on GENERAL_CALL_ID flag in input -- for 3 byte version use in overlay mode MMMCCBO.DETAILS.CALL_ID -- for 6 byte version take MMMCCBO.ARR(1:6) -- will be copied transparent from input


2.3.87 drcChrgOrigin

DrcChrgOrigin ::= OCTET STRING (SIZE(1)) -- only valid if distance info is valid -- will be copied transparently from location code

For Distance Related Charging, this parameter (together with theparameter drcTariffClass ) indicates the current location of the subscriber.

DrcChrgOrigin ::= OCTET STRING (SIZE(1)) -- only valid if validity of distance info is set in active fields -- will be copied transparent from location code

2.3.88 drcTariffClass

DrcTariffClass ::= OCTET STRING (SIZE(2)) -- only valid if distance info is valid -- will be copied transparently from location code

For Distance Related Charging, this parameter (together with the parameter drcChrgOrigin)indicates the current location of the subscriber.+-------------------------------------------------------------------+¦ drcTariffClass ¦ length = 2 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ ¦¦ two octet Kind of call or ¦¦ location information ¦¦ ¦+-------------------------------------------------------------------+

DrcTariffClass ::= OCTET STRING (SIZE(2)) -- only valid if validity of distance info is set in active fields -- will be copied transparent from tariff class

2.3.89 durationBeforeAnswer

DurationBeforeAnswer ::= INTEGER -- range 0 to 65535 seconds -- strictly ASN.1 like integer coding -- example: 127 sec coded as '7F' -- example: 128 sec coded as '0080'

+-------------------------------------------------------------------+¦ durationBeforeAnswer ¦ length = 1..3 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure : ¦¦ ¦¦ INTEGER value of call duration before answer in seconds ¦¦ ¦+-------------------------------------------------------------------+


This is only usable when the feature IACTRA is released. The length of this field depends on the value of durationBeforeAnswer.

for example: 127s 1 octet (hex ‘7F’)

128s 2 octets (hex ’0080’) and so on

Note that IACTRA is not released for CS2.1!

DurationBeforeAnswer ::= INTEGER -- range 0 to 65535 seconds -- strictly ASN.1 like integer coding -- example: 127 sec coded as '7F' -- example: 128 sec coded as '0080'

2.3.90 durationOfCAMELLeg

This parameter is only present if an IN service was actually triggered. The same rules apply like for callDuration.

coding a:

DurationOfCAMELLegA ::= INTEGER -- range 0 to 1800 seconds -- example: 35 sec coded as '0023'

+-------------------------------------------------------------------+¦ durationOfCAMELLeg ¦ length = 1..3 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure : ¦¦ ¦¦ INTEGER value: duration in seconds ¦¦ ¦+-------------------------------------------------------------------+

The length of this field depends on the value of durationOfCAMELLeg.

for example: 127s 1 octet (hex ‘7F’)


DurationOfCAMELLegA ::= INTEGER -- range 0 to 1800 seconds -- example: 35 sec coded as '0023'

coding b:


DurationOfCAMELLegB ::= OCTET STRING (SIZE(3)) -- coded with a fixed length of 3 bytes -- range 0 to 1800 seconds

+-------------------------------------------------------------------+¦ durationOfCAMELLeg ¦ length = 3 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure : ¦¦ ¦¦ OCTET STRING with fixed length of 3 Bytes ¦¦ ¦+-------------------------------------------------------------------+

The length of this field doesn´t depends on the value of durationOfCAMELLeg.

for example: 127s 3 octets (hex ‘00007F’)


2.3.91 e1, e2, e3, e4, e5, e6, e7

E1 ::= OCTET STRING (SIZE(2))E2 ::= OCTET STRING (SIZE(2))E3 ::= OCTET STRING (SIZE(2))E4 ::= OCTET STRING (SIZE(2))E5 ::= OCTET STRING (SIZE(2))E6 ::= OCTET STRING (SIZE(2))E7 ::= OCTET STRING (SIZE(2))

These parameters are the advice of charge elements e1 to e7 acc. /24.008/ and /22.024/.They have all the same ASN.1 format as E-Parameter:+-------------------------------------------------------------------+¦ EParameter ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ two octets ¦+-------------------------------------------------------------------+

e1 to e7 have a fixed format:

e1: range 0 - 819.1 resolution 0.1 e2: range 0 - 819.1 resolution 0.1 e3: range 0 - 81.91 resolution 0.01 e4: range 0 - 819.1 resolution 0.1 e5: range 0 - 819.1 resolution 0.1 e6: range 0 - 8191 resolution 1.0 e7: range 0 - 819.1 resolution 0.1

E1 ::= OCTET STRING (SIZE(2)) -- containing e1 -- example: e1=100 coded as '0064'E2 ::= OCTET STRING (SIZE(2)) -- containing e2 -- example: e2=100 coded as '0064'


E3 ::= OCTET STRING (SIZE(2)) -- containing e3 -- example: e3=100 coded as '0064'E4 ::= OCTET STRING (SIZE(2)) -- containing e4 -- example: e4=100 coded as '0064'E5 ::= OCTET STRING (SIZE(2)) -- containing e5 -- example: e5=100 coded as '0064'E6 ::= OCTET STRING (SIZE(2)) -- containing e6 -- example: e6=100 coded as '0064'E7 ::= OCTET STRING (SIZE(2)) -- containing e7 -- example: e7=100 coded as '0064'

2.3.92 esrkNumber (only in PCS1900 projects)

EsrkNumber ::= OCTET STRING (SIZE (1..5)) -- Note: the ESRK Number is always 10 digits with the following -- structure: -- ESRK = NPA-YYY-XXXX -- NPA = NPA for the PSAP or PCS1900 network -- YYY = some non-dialable NXX (e.g. 911) -- XXXX = 4 digits (no restrictions)

The esrkNumber is the MSISDN which identifies the emergencyservice. The ESRK Number is always 10 digits long.

EsrkNumber ::= OCTET STRING (SIZE (1..5)) -- Note: the ESRK Number is always 10 digits with the following

-- structure: -- ESRK = NPA-YYY-XXXX -- NPA = NPA for the PSAP or PCS1900 network -- YYY = some non-dialable NXX (e.g. 911) -- XXXX = 4 digits (no restrictions)

2.3.93 exchangeId

ExchangeId ::= IA5String (SIZE(1..11))

This parameter contains the ASCII representation of the exchange identity (MSC generating the record).


+-------------------------------------------------------------------+¦ exchangeId ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ variable or fixed length of up 11 ASCII characters ¦+-------------------------------------------------------------------+If the identity is less than 11 characters and a fixed length for the exchangeId is selected, the remaining characters will be filled up with "SPACE" characters.

If the identity is not available, the parameter is completely filled with ASCII "SPACE" characters (if default value not changed).

ExchangeId ::= IA5String (SIZE(1..11))

2.3.94 fixedNetworkUserRate (not for PCS projects)

This parameter is coded according to /24.008/. The parameter indicates the user rate applied for the connection in the fixed network, The parameter is only present in case of 2G HSCSD connections and for UMTS data connections.

FixedNetworkUserRate ::= OCTET STRING (SIZE (1)) -- coding according 3G TS 24.008. -- definition of fixed network user rate in octet 6d of the

-- Bearer capability information element: -- xxxnnnnn -- xxx : spare (0) -- nnnnn: fixed network user rate -- 00'H = FixedNetworkUserRate_NOT_APPLICABLE, -- 01'H = FixedNetworkUserRate_9_COMMA_6_KBITS, -- 02'H = FixedNetworkUserRate_14_COMMA_4_KBITS, -- 03'H = FixedNetworkUserRate_19_COMMA_2_KBITS, -- 04'H = FixedNetworkUserRate_28_COMMA_8_KBITS, -- 05'H = FixedNetworkUserRate_38_COMMA_4_KBITS, -- 06'H = FixedNetworkUserRate_43_COMMA_2_KBITS, -- 07'H = FixedNetworkUserRate_57_COMMA_6_KBITS, -- 08'H = FixedNetworkUserRate_64_COMMA_0_KBITS, -- 09'H = FixedNetworkUserRate_33_COMMA_6_KBITS, -- 0A'H = FixedNetworkUserRate_32_COMMA_0_KBITS, -- 0B'H = FixedNetworkUserRate_31_COMMA_2_KBITS,

This parameter is coded according to /24.008/. The parameter indicates the user rate applied for the connection in the fixed network, The parameter is only present in case of 2G HSCSD connections and for UMTS data connections.


2.3.95

2.3.96 GmlcAddress ::= AddressString (SIZE (1..9)) -- the Gateway Mobile Location Center address -- as an E.164 number

2.3.97 gsmScfAddress

GsmScfAddress ::= OCTET STRING (SIZE (1..9))

+-------------------------------------------------------------------+¦ gsmScfAddress ¦ length = 1..9 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure ¦¦ ¦¦ First octet default: ¦¦ ¦¦ BIT 8 (msb): extension bit (always 1) B'1 ¦¦ BIT 7-5 : type of number B'000 ¦¦ BIT 4-1 : numbering plan B'0000 ¦¦ ¦¦ Following octets: ¦¦ ¦¦ max. 16 digits coded as TBCD-string B'1111 ¦¦ ¦+-------------------------------------------------------------------+

This GSM SCF address is an E.164 number as described in /E.164/.

2.3.98 guaranteedBitRate

This parameter is applicable for 3G data calls via UTRAN and the value depends on the categorie of the service. For transparent services the guaranteedBitRate is always equal to the maximumBitRate. For non transparent services the guaranteedBitRate is always fix and is set in CS3.0 to 14.4 kbit/s.

GuaranteedBitRate ::= ENUMERATED { not-applicable (0), tch14-COMMA-4-KBITS (1), tch28-COMMA-8-KBITS (2) }


2.3.99

2.3.100 GsmScfAddress ::= AddressString (SIZE (1..9))

2.3.101 hotTransferResult

HotTransferResult ::= OCTET STRING (SIZE(1)) defaultValue HotTransferResult ::= '00'H successfulHotTransfer HotTransferResult ::= '01'H unsuccessfulHotTransfer HotTransferResult ::= '02'H

This parameter identifies the result of the record transfer between MSC and OS in case of Hot Billing / ECT / Hot IMSI Trace.

2.3.102

2.3.103

2.3.104 HotTransferResult ::= OCTET STRING (SIZE(1)) defaultValue HotTransferResult ::= '00'H successfulHotTransfer HotTransferResult ::= '01'H unsuccessfulHotTransfer HotTransferResult ::= '02'H

2.3.105

2.3.106 identificationVGSInitiator

IdentificationVGSInitiator ::= AddressString (SIZE (2..17)

For VGS calls, this is the MSISDN of the subscriber, who initiated the VGS call.

2.3.107

2.3.108 IdentificationVGSInitiator ::= AddressString (SIZE (2..17)

2.3.109

2.3.110 iMSIVGSInitiator

IMSIVGSInitiator ::= OCTET STRING (SIZE (1..8))


For VGS calls, this is the IMSI of the subscriber, who initiated the VGS call.

IMSIVGSInitiator ::= OCTET STRING (SIZE (1..8))

2.3.111 inAoC

InAoC ::= OCTET STRING (SIZE(1)) -- AOC within IN service

This flag indicates whether Charge Advice Information (CAI) has been received from the SCP. If true, CAI has been received within operation SCI from the SCP. If false, CAI has been retrieved from the local database. For more details please refer to /IN/.

+-------------------------------------------------------------------+¦ inAoC ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ 00000000 ¦ CAI retrieved from database ¦¦ 00000001 ¦ CAI received from SCP ¦+-------------------------------------------------------------------+

2.3.112 inatIndicator

InatIndicator ::= OCTET STRING (SIZE (1)) -- BOOL -- TRUE = 1 is international call -- FALSE = 0 is national call

The parameter matches the NAT/INAT indicator flag of the Forward Call Indicator parameter of the O: IAM and can be used to distinguish the call situation.

2.3.113

2.3.114 InAoC ::= INTEGER -- AOC within IN service

2.3.115 incTgTCompBlock

IncTgTCompBlock ::= SEQUENCE { tgrpNameIc TgrpNameIc, cicIc CicIc, biccCallInstCodeInc BiccCallInstCodeInc}


Note: trunkgroup and trunk composite blockContains the trunkgroup data and trunk data of the incoming side. These trunks can come from another exchange or a BSS.+-------------------------------------------------------------------+¦ incTgTCompBlock ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ SEQUENCE containing ¦¦ tgrpName ¦¦ cic ¦¦ biccCallInstCodeInc ¦+-------------------------------------------------------------------+

2.3.116 individualBearerserviceNumber

IndividualBearerserviceNumber ::= OCTET STRING (SIZE(1)) -- values and internal structure according to 3G TS 29.002 -- default value = 0 -- most significant bit has no meaning

This parameter represents a bearer service or a group of bearer services.+-------------------------------------------------------------------+¦ individualBearerserviceNumber ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ X0000000 ¦ all bearer services ¦¦ X0001000 ¦ 3.1 KHz group ¦¦ X0010000 ¦ data c.d.a. ¦¦ X0010001 ¦ data c.d.a. 300 b/s ¦¦ : ¦ : ¦¦ : ¦ : ¦+-------------------------------------------------------------------+

Values and internal structure are according to /29.002/.

The most significant bit has no meaning.

IndividualBearerserviceNumber ::= OCTET STRING (SIZE(1)) -- values and internal structure according to 3G TS 29.002 -- default value = 0 -- most significant bit has no meaning

2.3.117 individualTeleserviceNumber

IndividualTeleserviceNumber ::= OCTET STRING (SIZE(1)) -- values and internal structure according to 3G TS 29.002

This parameter represents a teleservice or a group of teleservices.


+-------------------------------------------------------------------+¦ individualTeleserviceNumber ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ 00000000 ¦ all teleservices ¦¦ 00010000 ¦ speech transmission ¦¦ 00010001 ¦ telephony ¦¦ : ¦ : ¦¦ : ¦ : ¦+-------------------------------------------------------------------+

Values and internal structure are according to /29.002/

Teleservice "emergency call" is used only when invoked via emergency key or when dialling 112.

In case of a dual service (e.g. Alternate Speech/Fax), the dual service is entered into this field at all records, the records before and after in-call modification. The service which was applicable for that part of the call the record is generated for, can be derived from other fields (e.g. msAccessRate).

2.3.118

2.3.119 IndividualTeleserviceNumber ::= OCTET STRING (SIZE(1)) -- values and internal structure according to 3G TS 29.002

2.3.120 inFlag

InFlag ::= OCTET STRING (SIZE (1)) -- IN service was triggered inRelatedCall InFlag ::= '01'H

If an IN service was actually triggered during the processing of a call in the MSC, the related call records are marked with an ‘IN flag’. For a detailed description please refer to /IN/ .


+-------------------------------------------------------------------+¦ inFlag ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ 00000000 ¦ IN service was not triggered ¦¦ 00000001 ¦ IN service was triggered ¦+-------------------------------------------------------------------+

2.3.121

2.3.122 InFlag ::= OCTET STRING (SIZE (1)) -- IN service was triggered inRelatedCall InFlag ::= '01'H

2.3.123

2.3.124 initiatorIndicationOfVGCS

For VGS calls.This parameter specifies the role of the subscriber, who initiated the VGS call.

InitiatorIndicationOfVGS ::= ENUMERATED { pLMN-Dispatcher (0), pSTN-Dispatcher (1), mobileServiceSubscriber (2), mobileServiceSubscriberRMSC (3), not-applicable (255) }

For VGS calls.This parameter specifies the role of the subscriber, who initiated the VGS call.

2.3.125 inServiceKey

coding a:

InServiceKeyA ::= INTEGER -- range 0 to 2147483647


+-------------------------------------------------------------------+¦ inServiceKey ¦ length = 1..4 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure : ¦¦ ¦¦ INTEGER value of the IN Service Indicator ¦¦ ¦+-------------------------------------------------------------------+

For CSI based IN dialogs the parameter inServiceKey is taken from the CSI. For all other IN dialogs the parameter inServiceKey is taken from the IN triggerprofile. In normal call records it is possible to bill the IN Service Key without additional IN records.

InServiceKeyA ::= INTEGER -- range 0 to 2147483647

coding b:

InServiceKeyB ::= OCTET STRING (SIZE(4))

+-------------------------------------------------------------------+¦ inServiceKey ¦ length = 4 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure : ¦¦ ¦¦ OCTET STRING with varible length with a maximum of 4 Bytes ¦¦ ¦+-------------------------------------------------------------------+

For CSI based IN dialogs the parameter inServiceKey is taken from the CSI. For all other IN dialogs the parameter inServiceKey is taken from the IN triggerprofile. In normal call records it is possible to bill the IN Service Key without additional IN records.

InServiceKeyB ::= OCTET STRING (SIZE(4))

2.3.126 intermediateSequenceNumber

IntermediateSequenceNumber ::= OCTET STRING (SIZE (1)) -- according to 3G TS 32.005

This parameter identifies the intermediateSequenceNumber as defined in 3G TS 32.005 v3.4.0.

The first record of a sequence of intermediate records (recordType 'First Intermediate Billing Record') contains a '0', the second one a '1' and so on up to the record with recordType 'Last Billing Record'.


2.3.127

2.3.128 IntermediateSequenceNumber ::= OCTET STRING (SIZE (1)) -- according to 3G TS 32.005

2.3.129 inTransPar

InTransPar ::= OCTET STRING (SIZE(1..40))

+-------------------------------------------------------------------+¦ inTransPar ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ octet string of variable length ¦¦ ¦+-------------------------------------------------------------------+

Data are received from SCP via operation SCI (Transparent Data).The field contains all available octets to be transparently transferedfrom the SCP to billing center.

2.3.130 iSDNBasicService

This parameter identifies the ISDN Basic service as defined in ETSI specification ETS 300 196.

ISDNBasicService ::= OCTET STRING (SIZE(1)) -- coded according to ETSI rec. aLL-SERVICES ISDNBasicService ::= '00'H sPEECH ISDNBasicService ::= '01'H uNRESTRICTED ISDNBasicService ::= '02'H aUDIO-3K1HZ ISDNBasicService ::= '03'H tELEPHONY-3K1HZ ISDNBasicService ::= '20'H tELETEXT ISDNBasicService ::= '21'H tELEFAX-GROUP-4 ISDNBasicService ::= '22'H vIDEOTEXT ISDNBasicService ::= '23'H vIDEOTEL ISDNBasicService ::= '24'H tELEFAX-GROUP-23 ISDNBasicService ::= '25'H tELEPHONY-7KHZ ISDNBasicService ::= '26'H

This parameter identifies the ISDN Basic service as defined in ETSI specification ETS 300 196.

2.3.131 lCSCause

This parameter is renamed in CS3.0, the former name in CS2.1 was lcsFailureCause.


LCSCause ::= OCTET STRING (SIZE(1..2)) -- OCTET 1: Cause value -- Cause as defined in 3G TS 49.031 -- OCTET 2: Diagnostic value -- coded like PositionMethodFailure-Diagnostic in -- 3G TS 29.002. -- Values outside those defined in 3G TS 29.002. shall -- be ignored by a receiver

+-------------------------------------------------------------------+¦ lCSCause ¦ Length = 1..2 ¦+--------------------------------+----------------------------------+¦ content ¦ meaning ¦+-------------------------------------------------------------------+¦ internal structure: ¦¦ ¦¦ 8 7 6 5 4 3 2 1 ¦¦ +--------------------------------------+ ¦¦ 1 ¦ LCS CAUSE ¦ ¦¦ +--------------------------------------+ ¦¦ 2 ¦ DIAGNOSTIC VALUE ¦ ¦¦ +--------------------------------------+ ¦¦ ¦¦ ¦¦ 1. First octet: LCS CAUSE ¦¦ ¦¦ Coding: LCS CAUSE defined in /49.031/ ¦¦ ¦¦ +------------------------+----------------------------------+ ¦¦ ¦ binary hex dec ¦ meaning ¦ ¦¦ +------------------------+----------------------------------+ ¦¦ ¦ 0000 0000 00 0 ¦ unspecified ¦ ¦¦ ¦ 0000 0001 01 1 ¦ system failure ¦ ¦¦ ¦ 0000 0010 02 2 ¦ protocoll error ¦ ¦¦ ¦ 0000 0011 03 3 ¦ data missing to positioning ¦ ¦¦ ¦ ¦ request ¦ ¦¦ ¦ 0000 0100 04 4 ¦ unexpexted data value in ¦ ¦¦ ¦ ¦ positioning request ¦ ¦¦ ¦ 0000 0101 05 5 ¦ positioning method failure ¦ ¦¦ ¦ 0000 0110 06 6 ¦ target MS unreachable ¦ ¦¦ ¦ 0000 0111 07 7 ¦ location request aborted ¦ ¦¦ ¦ 0000 1000 08 8 ¦ facillity not supported ¦ ¦¦ ¦ 0000 1001 09 9 ¦ Inter-BSC Handover ongoing ¦ ¦¦ ¦ 0000 1010 0A 10 ¦ Inter-BSC Handover complete ¦ ¦¦ ¦ 0000 1011 0B 11 ¦ congestion ¦ ¦¦ ¦ 0000 1100 0C 12 ¦ Inter NSE cell change ¦ ¦¦ ¦ 0000 1101 0D 13 ¦ Routing Area Update ¦ ¦¦ ¦ 0000 1110 0E 14 ¦ PTMSI reallocation ¦ ¦¦ ¦ 0000 1111 0F 15 ¦ Suspension of GPRS services ¦ ¦¦ ¦ 0001 0000 10 16 ¦ reserved ¦ ¦¦ ¦ to ¦ ¦ ¦¦ ¦ 1111 1111 FF 255 ¦ reserved ¦ ¦¦ +------------------------+----------------------------------+ ¦¦ ¦¦ 2. Second octet: DIAGNOSTIC VALUE ¦¦ ¦¦ Additional info if LCS Cause = positioning method failure ¦¦ Coding: positioningFailure-Diagnostic defined in /29.002/: ¦¦ ¦¦ PositionMethodFailure-Diagnostic ::= ENUMERATED { ¦¦ congestion (0), ¦¦ insufficientResources (1), ¦¦ insufficientMeasurementData (2), ¦¦ inconsistentMeasurementData (3), ¦


¦ locationProcedureNotCompleted (4), ¦¦ locationProcedureNotSupportedByTargetMS (5), ¦¦ qoSNotAttainable (6), ¦¦ positionMethodNotAvailableInNetwork (7 ), ¦¦ positionMethodNotAvailableInLocationArea (8 )) ¦+-------------------------------------------------------------------+

2.3.132 lCSCauseforTermination

LCSCauseforTermination ::= OCTET STRING (SIZE(1..2))

A more detailed information about the Cause for Termination if any failure or partial success happened:

a MAP error from TS 29.002

a Cause from TS 24.008

a Cause from TS 29.078

a Cause from ITU-T Recommendation Q.767

a LCS diagnostics according TS 29.002

ATTENTION: only if GDC (MP) is used !

The following list extracts some examples of causes from the TS 29.002, chapter 17.6.6. This list is not complete, for all causes refer to the list of standards above!

+-------------------------------------------------------------------+¦ lCSCauseforTermination ¦ Length = 1..2 ¦+--------------------------------+----------------------------------+¦ content ¦ meaning ¦+-------------------------------------------------------------------+¦ internal structure: ¦¦ ¦¦ 8 7 6 5 4 3 2 1 ¦¦ +--------------------------------------+ ¦¦ 1 ¦ MAP Error ¦ ¦¦ +--------------------------------------+ ¦¦ 2 ¦ MAP Error specific ¦ ¦¦ +--------------------------------------+ ¦¦ ¦¦ ¦¦ 1. First octet: MAP Error ¦¦ ¦¦ Coding: MAP Error defined in /29.002, chapter 17.6.6/ ¦¦ ¦¦ +-----------------------------------------------------------+ ¦¦ ¦ hex dec ¦ meaning ¦ ¦¦ +-----------------------------------------------------------+ ¦¦ ¦ 01 01 ¦ unknownSubscriber ¦ ¦¦ ¦ 15 21 ¦ facilityNotSupported ¦ ¦¦ ¦ 1B 27 ¦ absentSubscriber ¦ ¦¦ ¦ 22 34 ¦ systemFailure ¦ ¦¦ ¦ 34 52 ¦ unauthorizedRequestingNetwork ¦ ¦


¦ ¦ 35 53 ¦ unauthorizedLCSClient ¦ ¦¦ ¦ 36 54 ¦ positionMethodFailure ¦ ¦¦ ¦ 3A 58 ¦ unknownOrUnreachableLCSClient ¦ ¦¦ +-----------------------------------------------------------+ ¦¦ ¦¦ 2. Second octet: MAP Error specific ¦¦ ¦¦ Coding: depending on the MAP error as defined in /29.002/: ¦¦ ¦¦ UnknownSubscriberParam ::= SEQUENCE { ¦¦ extensionContainer ExtensionContainer, ¦¦ unknownSubscriberDiagnostic UnknownSubscriberDiagnostic } ¦¦ ¦¦ UnknownSubscriberDiagnostic ::= ENUMERATED { ¦¦ imsiUnknown (0), ¦¦ gprsSubscriptionUnknown (1), ¦¦ npdbMismatch (2)} ¦¦ ¦¦ FacilityNotSupParam ::= SEQUENCE { ¦¦ extensionContainer ExtensionContainer, ¦¦ shapeOfLocationEstimateNotSupported [0], ¦¦ neededLcsCapabilityNotSupportedInServingNode [1]} ¦¦ ¦¦ AbsentSubscriberParam ::= SEQUENCE { ¦¦ extensionContainer ExtensionContainer, ¦¦ absentSubscriberReason [0] AbsentSubscriberReason } ¦¦ ¦¦ AbsentSubscriberReason ::= ENUMERATED { ¦¦ imsiDetach (0), ¦¦ restrictedArea (1), ¦¦ noPageResponse (2), ¦¦ purgedMS (3)} ¦¦ ¦¦ SystemFailureParam ::= CHOICE { ¦¦ networkResource NetworkResource, ¦¦ extensibleSystemFailureParam ExtensibleSystemFailureParam} ¦¦ ¦¦ NetworkResource ::= ENUMERATED { ¦¦ plmn (0), ¦¦ hlr (1), ¦¦ vlr (2), ¦¦ pvlr (3), ¦¦ controllingMSC (4), ¦¦ vmsc (5), ¦¦ eir (6), ¦¦ rss (7)} ¦¦ ¦¦ ExtensibleSystemFailureParam ::= SEQUENCE { ¦¦ networkResource NetworkResource, ¦¦ extensionContainer ExtensionContainer} ¦¦ ¦¦ UnauthorizedRequestingNetwork-Param ::= SEQUENCE { ¦¦ extensionContainer ExtensionContainer} ¦¦ ¦¦ UnauthorizedLCSClient-Param ::= SEQUENCE { ¦¦ unauthorizedLCSClient-Diagnostic [0] ¦¦ UnauthorizedLCSClient-Diagnostic¦¦ extensionContainer [1] ExtensionContainer} ¦¦ ¦¦ UnauthorizedLCSClient-Diagnostic ::= ENUMERATED { ¦¦ noAdditionalInformation (0), ¦¦ clientNotInMSPrivacyExceptionList (1), ¦¦ callToClientNotSetup (2), ¦¦ privacyOverrideNotApplicable (3), ¦¦ disallowedByLocalRegulatoryRequirements (4), ¦¦ unauthorizedPrivacyClass (5), ¦¦ unauthorizedCallSessionUnrelatedExternalClient (6), ¦


¦ unauthorizedCallSessionRelatedExternalClient (7)} ¦¦ ¦¦ PositionMethodFailure-Param ::= SEQUENCE { ¦¦ positionMethodFailure-Diagnostic [0] ¦¦ PositionMethodFailure-Diagnostic,¦¦ extensionContainer [1] ExtensionContainer} ¦¦ ¦¦ PositionMethodFailure-Diagnostic ::= ENUMERATED { ¦¦ congestion (0), ¦¦ insufficientResources (1), ¦¦ insufficientMeasurementData (2), ¦¦ inconsistentMeasurementData (3), ¦¦ locationProcedureNotCompleted (4), ¦¦ locationProcedureNotSupportedByTargetMS (5), ¦¦ qoSNotAttainable (6), ¦¦ positionMethodNotAvailableInNetwork (7), ¦¦ positionMethodNotAvailableInLocationArea (8),} ¦¦ ¦¦ UnknownOrUnreachableLCSClient-Param ::= SEQUENCE { ¦¦ extensionContainer ExtensionContainer} ¦+-------------------------------------------------------------------+


2.3.133 lCSClientDialedByMSID

The "Call related Class" mobile terminating LCS request is allowed by any LCS client to which the MS originated a call that is currently established. This parameter specifies the LCS client Id.

LCSClientDialedByMSID ::= AddressString (SIZE (2..20)) -- This type is used to represent a number for addressing purposes.

-- It is composed of -- a) one octet for nature of address, and numbering plan indicator. -- b) digits of an address encoded as TBCD-String. -- a) The first octet includes a one bit extension indicator, a 3 -- bits nature of address indicator and a 4 bits numberingplan -- indicator, encoded as follows: -- bit 8: 1 (no extension) -- bits 765: nature of address indicator -- 000 unknown -- 001 international number -- 010 national significant number -- 011 network specific number -- 100 subscriber number -- 101 reserved -- 110 abbreviated number -- 111 reserved for extension -- bits 4321: numbering plan indicator -- 0000 unknown -- 0001 ISDN/Telephony Numbering Plan (Rec CCITT E.164) -- 0010 spare -- 0011 data numbering plan (CCITT Rec X.121) -- 0100 telex numbering plan (CCITT Rec F.69) -- 0101 spare -- 0110 land mobile numbering plan (CCITT Rec E.212) -- 0111 spare -- 1000 national numbering plan -- 1001 private numbering plan -- 1111 reserved for extension -- all other values are reserved. -- b) The following octets representing digits of an address -- encoded -- as a TBCD-STRING. -- Note:LCSClientIdentity as defined in 3G TS 29.002 (LCS-ClientID)

The "Call related Class" mobile terminating LCS request is allowed by any LCS client to which the MS originated a call that is currently established. This parameter specifies the LCS client Id.

2.3.134 lCSClientExternalID

LCSClientExternalID ::= AddressString (SIZE (2..20)) -- (see also lCSClientDialedbyMSID)


A mobile terminating LCS request is accepted in case the mobile subscriber is subscribed to the "call unrelated class" and the LCS client supplied by the GMLC matches the identity of any LCS client contained in the MS subscribers external LCS client list.

The E.164 number of the LCS client is stored in this parameter.

2.3.135 lCSClientIdentity

lCSClientIdentity ::= SEQUENCE { lCSClientExternalID lCSClientExternalID OPTIONAL, lCSClientDialedByMSID lCSClientDialedByMSID OPTIONAL, lCSClientInternalID lCSClientInternalID OPTIONAL}

2.3.136

2.3.137 LCSClientExternalID ::= AddressString (SIZE (2..20)) -- (see also lCSClientDialedbyMSID)

2.3.138 lCSClientInternalID

If the LCS Client Type is "PLMN Operator Class" , then the LCS client's identity is located in the LCS Client Internal ID parameter.

LCSClientInternalID ::= ENUMERATED { broadcastService (0), o-andM-HPLMN (1), o-andM-VPLMN (2), anonymousLocation (3), targetMSsubscribedService (4), not-applicable (255) }

If the LCS Client Type is "PLMN Operator Class" , then the LCS client's identity is located in the LCS Client Internal ID parameter.

2.3.139 lcsClientType

This parameter specifies the type of an external LCS client who requests the current location of a target MS:

LCSClientType ::= ENUMERATED { emergencyServices (0), valueAddedServices (1), plmnOperatorServices (2), not-applicable (255) } -- Note: The definition is according to 3G TS 29.002


This parameter specifies the type of an external LCS client who requests the current location of a target MS:


2.3.140 lCSMoLr

The lCSMoLr parameter refers to the MO-LR response parameters which are sent to the MS by the network.

LCSMoLr ::= ENUMERATED { locationEstimate (0), assistanceData (1), deCipheringKeys (2), not-applicable (255)}

-- according to 3G TS 24.080


2.3.141 lCSPriority

This parameter specifies the possible priorities of the LCS request.

LCSPriority ::= OCTET STRING (SIZE (1)) -- 0 = highest priority -- 1 = normal priority -- all other values treated as 1

This parameter specifies the possible priorities of the LCS request.

2.3.142 lCSQoS

LCSQoS ::= OCTET STRING( SIZE(4)) -- Note: as defined in 3G TS 49.031

This parameter will indicate the LCS Quality of Service for a location request.

It is renamed in CS3.0, the former name in CS2.1 was lCSQualityOfService.

8 7 6 5 4 3 2 1

Octet 1 spare VERT

Octet 2 HA Horizontal Accuracy

Octet 3 VA Vertical Accuracy

Octet 4 RT spare

Octet 1 : VERT = vertical coordinate indicator

0 : vertical coordinate not requested


1 : vertical coordinate is requested

Octet 2 : bit 8 HA = horizontal accuracy indicator

0 : Horizontal Accuracy is not specified

1 : Horizontal Accuracy is specified

bits 7-1 Horizontal Accuracy :

spare (set all zeroes) if HA=0

set to 7 bit uncertainty code in 3 G TS 23.032 if HA=1

Octet 3 : – applicable only if VERT = 1

bit 8 VA = vertical accuracy indicator

0 : Vertical Accuracy is not specified

1 : Vertical Accuracy is specified

bits 7-1 Vertical Accuracy :

spare (set all zeroes) if VA=0

set to 7 bit uncertainty code in 3G TS 23.032 if VA=1


Octet 4 : bits 8-7 RT = response time category

00 : Response Time is not specified

01 : Low Delay

10 : Delay Tolerant

11 : reserved

bits 6-1 spare

2.3.143

2.3.144 LCSQualityOfService ::= OCTET STRING( SIZE( 4 )) -- Note: as defined in 3G TS 29.032

2.3.145

2.3.146 lCSRequestType

LCSRequestType ::= ENUMERATED { currentLocation (0), currentOrLastKnownLocation (1), initialLocation (2), decipheringKeys (3), assistanceData (4), not-applicable (255)} -- Note: LCSRequestType as defined in 3G TS 29.002 -- (LocationEstimateType)

This parameter specifies the location estimate request type.

ATTENTION: only if ChaSer (CP) is used !Current Location: after a location attempt has successfully delivered a location estimate (geographic location of an MS and/or valid Mobile Equipment expressed in latitude and longitude data) and its associated time stamp, the location estimate and time stamp is referred to as the "current location" at that point in time.Last Known Location: this is the last location estimate that was obtained by the MSC for any MS, and should be stored in the VLR along with the date and time.Initial Location: in the context of an originating emergency call the location estimate and the associated time stamp at the commencement of the call set-up is referred to as "initial location".Deciphering Keys: ciphering of key portions of broadcast assistance data can be employed by an SLMC to restrict access to some MS users.Assistance Date: with this variant of the MOLR, an MS could request assistance data for E-OTD or GPS and in the cases of GPS , could indicate which types of assistance data are needed.

2.3.147 lCSSSCode

LCSSSCode ::= OCTET STRING (SIZE(1)) ssdefaultValue LCSSSCode ::= '00'H transferToThirdParty LCSSSCode ::= '01'H


This parameter indicates, if a transfer to a third party was required by an MS in case of an MOLR. This information is additionally to the parameter lCSMoLr which shows the requested type of data for the MOLR.

LCSRequestType ::= ENUMERATED { currentLocation (0), currentOrLastKnownLocation (1), initialLocation (2) } -- Note: LCSRequestType as defined in 3G TS 29.002 -- (LocationEstimateType)

2.3.148 levelOfCAMELService

LevelOfCAMELService ::= BIT STRING (SIZE (2)) -- basic (0), -- callDurationSupervision (1), -- onlineCharging (2)

This parameter describes briefly the complexity of the CAMEL feature invocation and is only present if an IN service was actually triggered. The paramter is coded as BIT-String.

+-------------------------------------------------------------------+¦ levelOfCAMELService ¦ length = 2 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ ¦¦ First octet: ¦¦ ¦¦ according ASN1 encoding of BIT-String ¦¦ ¦¦ Second octet: ¦¦ ¦¦ 8 7 6 5 4 3 2 1 ¦¦ +-------------------------------¦ ¦¦ ¦ ¦ ¦¦ +-------------------------------¦ ¦¦ ¦¦ coded as follows ¦¦ ¦¦ BIT 8 used for ’basic’ ¦¦ BIT 7 used for ’callDurationSupervision’ ¦¦ BIT 6 used for ’onlineCharging’ ¦¦ BIT 5..1 reserved ¦¦ ¦+-------------------------------------------------------------------+

- ‘basic’ means, that CAMEL feature is invoked during the call setup phase only.

- ‘onlineCharging’ means, that CAMEL supported AoC parameter were sent to the MS (SCI is received from the gsmSCF).

- ‘callDurationSupervision’ is set, whenever the call duration supervision is applied in the


gsmSSF of the VPLMN (apply charging message is received from the gsmSCF).

2.3.149

2.3.150 LevelOfCAMELService ::= BIT STRING (SIZE (2)) -- basic (0), -- callDurationSupervision (1), -- onlineCharging (2)

2.3.151 locationAreaCode

LocationAreaCode ::= OCTET STRING ( SIZE (2)) -- OCTET 1-2 -- XXXXXXXX = LAC(MSB) -- XXXXXXXX = LAC(LSB)

This parameter gives the Location Area Code.+-------------------------------------------------------------------+¦ locationAreaCode ¦ length = 2 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ ¦¦ 8 7 6 5 4 3 2 1 ¦¦ +-------------------------------¦ ¦¦ 1 ¦ LAC (msb) ¦ ¦¦ +-------------------------------¦ ¦¦ 2 ¦ LAC (lsb) ¦ ¦¦ +-------------------------------+ ¦¦ ¦+-------------------------------------------------------------------+

LocationAreaCode ::= OCTET STRING ( SIZE (2)) -- OCTET 1-2 -- XXXXXXXX = LAC(MSB) -- XXXXXXXX = LAC(LSB)


2.3.152 locationEstimate

LocationEstimate ::= OCTET STRING (SIZE (1..91))-- Note: the MS Location as defined as geographical Information-- in 3G TS 23.032

In case of a location request or emergency call (service E911) the parameter indicates the MS Location.

The MS Location is defined as geographical Information like in /23.032/.

Ext-GeographicalInformation ::= OCTET STRING (SIZE (1.. 91))

-- Octet 1: Type of shape, only the following shapes in /23.032/ are allowed:

-- (a) Ellipsoid point with uncertainty circle-- (b) Ellipsoid point with uncertainty ellipse-- (c) Ellipsoid point with altitude and uncertainty ellipsoid

(d) Ellipsoid Arc Any other value in octet 1 shall be treated as invalid

case a)

-- Octets 2 to 8 – Ellipsoid point with uncertainty circle-- Degrees of Latitude 3 octets-- Degrees of Longitude 3 octets-- Uncertainty code 1 octet

case b)

-- Octets 2 to 11 – Ellipsoid point with uncertainty ellipse:-- Degrees of Latitude 3 octets-- Degrees of Longitude 3 octets-- Uncertainty semi-major axis 1 octet-- Uncertainty semi-minor axis 1 octet-- Angle of major axis 1 octet-- Confidence 1 octet

case c)

-- Octets 2 to 14 – Ellipsoid point with altitude and uncertainty ellipsoid-- Degrees of Latitude 3 octets-- Degrees of Longitude 3 octets-- Altitude 2 octets-- Uncertainty semi-major axis 1 octet-- Uncertainty semi-minor axis 1 octet-- Angle of major axis 1 octet-- Uncertainty altitude 1 octet-- Confidence 1 octet

case (d)

-- Octets 2 to 13 – Ellipsoid Arc-- Degrees of Latitude 3 octets-- Degrees of Longitude 3 octets-- Inner radius 2 octets-- Uncertainty radius 1 octet-- Offset angle 1 octet-- Included angle 1 octet-- Confidence 1 octet---- An Ext-GeogrpahicalInformation parameter containing any other shape or an incorrect number of octets or coding according to 3G TS 23.032 shall be treated as invalid data by a receiver


2.3.153 locationEstimateType

LocationEstimateType ::= ENUMERATED { currentLocation (0), currentOrLastKnownLocation (1), initialLocation (2), activateDeferredLocation (3), cancelDeferredLocation (4), not-applicable (255)}

-- according to 3GPP TS 29.002


2.3.154 locationNumber

LocationNumber ::= OCTET STRING (SIZE (1..8))

This parameter identifies the locationNumber assigned to the cell identifier. The length of this field is limited to 8 bytes.If no length is given in table 8 (‘varies’), the length can vary from one record to the other.If a length is entered in table 8, this field contains the locationNumber up to the numbers of octets entered as length for this field. Any remaining octets are filled with the filler.+-------------------------------------------------------------------+¦ locationNumber ¦ length varies ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ locationNumber ¦ as assigned to the corresponding ¦¦ ¦ cellIdentity ¦¦ ¦ digits are coded as TBCD string ¦+-------------------------------------------------------------------+

2.3.155 locationServiceInfo

locationServiceInfo ::= SEQUENCE { mlcNumber mlcNumber OPTIONAL, positioningData positioningData OPTIONAL, locationEstimate locationEstimate OPTIONAL, esrkNumber esrkNumber OPTIONAL, lCSCause lCSCause OPTIONAL, lCSCauseforTermination lCSCauseforTermination OPTIONAL

2.3.156 maximumBitRate

This parameter is applicable for 3G data calls via UTRAN.

MaximumBitRate ::= ENUMERATED { not-applicable (0), tch14-COMMA-4-KBITS (1), tch28-COMMA-8-KBITS (2), tch57-COMMA-6-KBITS (3) }


2.3.157

2.3.158

2.3.159 LocationNumber ::= OCTET STRING (SIZE (1..8))

2.3.160

2.3.161

2.3.162 mcrDestinationNumber

This field contains the destination number which is received as an result of an executed IN trigger. For a detailed description please refer to /IN/ (mcrDestinationNumber).

coding a:McrDestinationNumberA ::= AddressString (SIZE (2..17))

coded as specified in /24.008/

+-------------------------------------------------------------------+¦ mcrDestinationNumber ¦ length = 2..17 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure ¦¦ ¦¦ First octet default: ¦¦ ¦¦ BIT 8 (msb): extension bit (always 1) B'1 ¦¦ BIT 7-5 : type of number B'000 ¦¦ BIT 4-1 : numbering plan B'0000 ¦¦ ¦¦ Following octets: ¦¦ ¦¦ max. 32 digits coded as TBCD-string B'1111 ¦+-------------------------------------------------------------------+

McrDestinationNumberA ::= AddressString (SIZE (2..17))


coding b:McrDestinationNumberB ::= OCTET STRING (SIZE (2..18)) -- Mapping of McrDestinationNumber from GSM to ITU

coded as specified in ITU Q.763

+-------------------------------------------------------------------+¦ mcrDestinationNumber ¦ length = 2..18 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ address string, coded as specified by Q.763 ¦¦ ¦¦ First octet ¦¦ BIT 8 (msb): Odd/Even indicator ¦¦ BIT 7-1 : Nature Of Address indicator ¦¦ ¦¦ Second octet ¦¦ BIT 8 (msb): Internal Network Number indicator (INN ind.) ¦¦ BIT 7-5 : Numbering Plan indicator ¦¦ BIT 4-1 : spare ¦¦ ¦¦ ¦¦ Following octets: ¦¦ max. 16 octets (32 digits), each octet coded as: ¦¦ BIT 8-5 : Address Signal 2n ¦¦ BIT 4-1 : Address Signal 2n-1 ¦¦ ¦+-------------------------------------------------------------------+

Spare bits are coded 0 unless indicated otherwise.

2.3.163

2.3.164 McrDestinationNumberB ::= OCTET STRING (SIZE (2..18)) -- Mapping of McrDestinationNumber from GSM to ITU

2.3.165

2.3.166 mcrDestinationNumberSMS

McrDestinationNumberSMS ::= OCTET STRING (SIZE(3..18)) -- according to 3G TS 23.040 -- OCTET 1 -- Address Length -- OCTET 2 -- Type Of Address -- OCTET 3-N -- Address Value transparent

This parameter identifies the destination address where the short message was finally routed in case of SMS-MO and if an IN dialogue influenced the transaction establishment.

Be aware that this number can not be verified in any case by the MSC, neither for its structure nor for its contents. The data are fully transparent.


+-------------------------------------------------------------------+¦ mcrDestinationNumberSMS ¦ length = 3..18 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure as defined in 3G TS 23.040 for the ¦¦ TP-Destination-Address (TP-DA): ¦¦ ¦¦ formatted according to the formatting rules of address fields ¦¦ ¦¦ octett 1 Address-Length ¦¦ 2 Type-of-Address ¦¦ 3 first octet of Address-Value ¦¦ : ¦¦ ¦+-------------------------------------------------------------------+

The Type-of-Address can also be "alphanumeric". So the field is coded as a transparent octet string even in case of TBCD coded digits !

2.3.167 measureDuration

The duration of the proceeding of the location request.

coding a:

MeasureDurationA ::= INTEGER -- strictly ASN.1 like integer coding -- example: 127 sec coded as '7F' -- example: 128 sec coded as '0080'





CallDurationA ::= INTEGER -- strictly ASN.1 like integer coding -- example: 127 sec coded as '7F' -- example: 128 sec coded as '0080'coding b:

MeasureDurationB ::= OCTET STRING (SIZE(2)) -- coded with a fixed length of 2 bytes -- range 0 to 1800 seconds -- example: 35 sec coded as '0023'



2.3.168 mlcNumber

MlcNumber ::= AddressString (SIZE (1..9)) -- the Gateway Mobile Location Center address -- as an E.164 number

This parameter has been renamed, the former name in CS2.1 was gmlcAddress.The parameters indicates the address of the gateway mobile location center in case of a emergency call (service E911).

The address is a E.164 number.

2.3.169 msAccessRate

2.3.170 McrDestinationNumberSMS ::= OCTET STRING (SIZE(1..17)) -- according to 3G TS 23.040 -- OCTET 1 -- Address Length -- OCTET 2 -- Type Of Address -- OCTET 3-N -- Address Value transparent

2.3.171

MsAccessRate ::= INTEGER { undefined (0), bps300 (1), bps1200 (2), bps2400 (3), bps4800 (4), bps9600 (5), bps12000 (6), bps120075 (7)} -- according to 3G TS 24.008 -- valid only for basic service <> telephony or emergency call -- value 6 is curently not supported

This parameter specifies the user access rate at the mobile terminal.

Structure and values are according 3G TS 24.008.msAccessRate is valid only for basic service <> telephony or emergency call.For dual services (e.g. teleservice) this parameter has the default value for the speech phase and the relevant user access rate for the data phase of the connection.


2.3.172

2.3.173 MsAccessRate ::= INTEGER { undefined (0), bps300 (1), bps1200 (2), bps2400 (3), bps4800 (4), bps9600 (5), bps12000 (6), bps120075 (7) } -- according to 3G TS 24.008 -- valid only for basic service <> telephony or emergency call

2.3.174 -- value 6 is curently not supported

2.3.175 mscAddress

MscAddress ::= OCTET STRING (SIZE (1..9))

+-------------------------------------------------------------------+¦ mscAddress ¦ length = 1..9 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure ¦¦ ¦¦ First octet default: ¦¦ ¦¦ BIT 8 (msb): extension bit (always 1) B'1 ¦¦ BIT 7-5 : type of number B'000 ¦¦ BIT 4-1 : numbering plan B'0000 ¦¦ ¦¦ Following octets: ¦¦ ¦¦ max. 16 digits coded as TBCD-string B'1111 ¦¦ ¦+-------------------------------------------------------------------+

The address of the MSC, where the Call Reference Number is generated, is written into the field mscAddress.

The availability of the parameter mscAddress depends on the availability of the parameter callReferenceNumber in the same MCR Ticket. If the parameter callReferenceNumber is not available in the MCR Ticket the parameter mscAddress is also not available in this MCR Ticket. For more details see the description of callReferenceNumber in this document and in /IN/.

This MSC address is an E.164 number as described in /E.164/.

2.3.176 msClassmark


2.3.177 MscAddress ::= AddressString (SIZE (1..9))

This parameter is used to provide the network with information concerning aspects of high priority of the mobile station equipment. Structure and values of msClassmark are according to the definitions of Mobile Station Classmark 1, 2 and 3 in /24.008/.

Note: SS screening indicator of Mobile Station Classmark 2 : octet 4 not indicated. Unused octets are filled with default filler value.

+-------------------------------------------------------------------+¦ msClassmark ¦ length depends on classmark type ¦¦ ¦ or define ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ ¦¦ 8 7 6 5 4 3 2 1 ¦¦ +-------------------------------¦ ¦¦ 1 ¦ octet 2/3 of MSClassmark 1/2 ¦ ¦¦ +-------------------------------¦ ¦¦ 2 ¦ octet 4 ¦ ¦¦ +------ of MSClassmark 2 --¦ ¦¦ 3 ¦ octet 5 ¦ ¦¦ +-------------------------------¦ ¦¦ 4 ¦ octet 3 ¦ ¦¦ +------ --¦ ¦¦ : ¦ : of MSClassmark 3 ¦ ¦¦ +------ --¦ ¦¦ 15 ¦ octet 14 ¦ ¦¦ +-------------------------------+ ¦¦ ¦+-------------------------------------------------------------------+

MsClassmarkA ::= OCTET STRING (SIZE(3)) -- msClassmark1 or msClassmark2 -- if msClassmark1: byte 2,3 filled with fillerMsClassmarkB ::= OCTET STRING (SIZE(2)) -- msClassmark1 or msClassmark2 -- coded like type A without 3rd byte -- type is only a dummy description -- type B is selected by using Type A combined -- with "LEN=2"MsClassmarkC ::= OCTET STRING (SIZE(1..3)) -- msClassmark1 or msClassmark2 -- msClassmark1: 1 byte -- msClassmark2: 3 byteMsClassmarkD ::= OCTET STRING (SIZE(1)) -- msClassmark1 or msClassmark2 -- both coded as msClassmark1MsClassmark ::= OCTET STRING (SIZE(1..15)) -- byte 1 = octet 2 from msClassmark1 -- or octet 3 from msClassmark2 -- byte 2 = octet 4 from msClassmark2 -- byte 3 = octet 5 from msClassmark2 -- byte 4 = octet 3 from msClassmark3 -- byte 5 = octet 3bis from msClassmark3 -- byte 6..15 spare bytes from msClassmark3 -- available since SR6.0 -- if fixed length selected the current ms classmark info is


-- filled up with fillers -- containing MS Classmark info according GSM 04.08 -- byte 1 = octet 2 from msClassmark1 -- or octet 3 from msClassmark2 -- byte 2 = octet 4 from msClassmark2 -- byte 3 = octet 5 from msClassmark2 -- byte 4 = octet 3 from msClassmark3 -- byte 5 = octet 3bis from msClassmark3 -- byte 6..15 spare bytes from msClassmark3 -- bit mask |__|__|__|__||__|__|__|__| -- byte 1 |S1|RL |ES||A1|RP | -- byte 2 |S3|PS|SS ||SM|VB|VG|FC| -- byte 3 |C3|S4 |A3|A2| -- byte 4 |E |B3|B2|B1||A7|A6|A5|A4| -- byte 5 |R2 ||R1 | -- with -- S1 Spare 1 -- RL Revision Level -- ES ES IND -- A1 A5-1 -- RP RF Power Capability -- S3 Spare 3 -- PS PS Capability -- SS SS Screening Indicator -- SM SM Capability -- VB VBS notification reception -- VG VGCS notification reception -- FC Frequency Capability -- C3 CM3 -- S4 Spare 4 -- A3 A5-3 -- A2 A5-2 -- E E-Bit -- B3 Band-3 -- B2 Band-2 -- B1 Band-1 -- A7 A5-7 -- A6 A5-6 -- A5 A5-5 -- A4 A5-4 -- R2 Associated Radio Capability 2 -- R1 Associated Radio Capability 1

This parameter is used to provide the network with information concerning aspects of high priority of the mobile station equipment. Structure and values of msClassmark are according to the definitions of Mobile Station Classmark 1, 2 and 3 in /24.008/.

Note: SS screening indicator of Mobile Station Classmark 2 : octet 4 not indicated. Unused octets are filled with default filler value.


+-------------------------------------------------------------------+¦ msClassmark ¦ length depends on classmark type ¦¦ ¦ or define ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ ¦¦ 8 7 6 5 4 3 2 1 ¦¦ +-------------------------------¦ ¦¦ 1 ¦ octet 2/3 of MSClassmark 1/2 ¦ ¦¦ +-------------------------------¦ ¦¦ 2 ¦ octet 4 ¦ ¦¦ +------ of MSClassmark 2 --¦ ¦¦ 3 ¦ octet 5 ¦ ¦¦ +-------------------------------¦ ¦¦ 4 ¦ octet 3 ¦ ¦¦ +------ --¦ ¦¦ : ¦ : of MSClassmark 3 ¦ ¦¦ +------ --¦ ¦¦ 15 ¦ octet 14 ¦ ¦¦ +-------------------------------+ ¦¦ ¦+-------------------------------------------------------------------+

2.3.178 multipleSMTransfer

MultipleSMTransfer ::= INTEGER { singleShortMessage (0), multipleMessageTransferUsed (1)}

This field indicates the usage of the same connection between MS and VMSC to transfer a sequence of short messages.

+-------------------------------------------------------------------+¦ multipleSMTransfer ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ 00000000 (FALSE, see note) ¦ single short message ¦¦ 00000001 (TRUE, see note) ¦ multiple message transfer used ¦+-------------------------------------------------------------------+

Note: The indication TRUE isn’t always used in case of Multiple SMS :

1st record foll. record last recordSMS MO : FALSE TRUE TRUESMS MT : TRUE TRUE FALSE

2.3.179 nMTForwardedIndicator


2.3.180

2.3.181 MultipleSMTransfer ::= INTEGER { singleShortMessage (0), multipleMessageTransferUsed (1) }

NMTForwardedIndicator ::= OCTET STRING (SIZE(1)) -- 0 for false, -- 1 for true -- no-nmt-forwarding NMTForwardedIndicator ::= '00'H -- nmt-forwarding NMTForwardedIndicator ::= '01'H

This field indicates whether the call has already been forwarded before, regardless whether the forwarding took place inside or outside the MSC, where the record is generated.

+-------------------------------------------------------------------+¦ nMTForwardedIndicator ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ 00000000 FALSE ¦ no call forwarding indicated ¦¦ 00000001 TRUE ¦ call forwarding indicated ¦+-------------------------------------------------------------------+

2.3.182

2.3.183 NMTForwardedIndicator ::= OCTET STRING (SIZE(1)) -- 0 for false, -- 1 for true -- no-nmt-forwarding NMTForwardedIndicator ::= '00'H -- nmt-forwarding NMTForwardedIndicator ::= '01'H

2.3.184 noOfDispatcherInVGSGroup

NoOfDispatcherInVGSGroup ::= INTEGER -- range 0 to 255 (max. H'FF)

For VGS calls, this parameter specifies the number of dispatchers, involved in the group call.

noOfDispatcherInVGSGroup ::= INTEGER (0..255)


2.3.185

2.3.186 NoOfDispatcherInVGSGroup ::= INTEGER -- range 0 to 255 (max. H'FF)

2.3.187 noOfDispatWithSuccSetup

NoOfDispatWithSuccSetup ::= INTEGER -- range 0 to 255 (max. H'FF)

For VGS calls, this parameter specifies the number of dispatchers with successful call setup, involved in the group call.

2.3.188

2.3.189 NoOfDispatWithSuccSetup ::= INTEGER -- range 0 to 255 (max. H'FF)

2.3.190 noOfRmscsInGroup

NoOfRmscsInGroup ::= INTEGER -- range 0 to 255 -- the number of Remote MSCs being notified from the VGS call

For VGS calls, this parameter specifies the number of R-MSC´s (Relay MSC) partaking in the VGCS/VBS group call.

2.3.191

2.3.192 NoOfRmscsInGroup ::= INTEGER -- range 0 to 255 -- the number of Remote MSCs being notified from the VGS call

2.3.193 noOfRmscsWithSuccSetup

NoOfRmscsWithSuccSetup ::= INTEGER -- range 0 to 255 -- the number of Remote MSCs involved in the VGS call

For VGS calls, this parameter contains the number of R-MSC´s (Relay MSC) partaking in the VGCS/VBS group call with successful call setup.


2.3.194

2.3.195 NoOfRmscsWithSuccSetup ::= INTEGER -- range 0 to 255 -- the number of Remote MSCs involved in the VGS call

2.3.196

2.3.197 noOfUsedTrafficChannels (not for PCS projects)

NoOfUsedTrafficChannels ::= INTEGER -- range 0 to 255 (max. H'FF)

For HSCSD calls (see 2.3.1 additionalBearerServiceInfo) this parameter specifies the number of used traffic channels.

According to the 3GPP standard up to four traffic channels and by the SAG two traffic channels are supported.

2.3.198 notificationToMSUser

This parameter is applicable to the call/session unrelated privacy class and call/session related privacy class. For non-call/call related privacy class it indicates whether the MS user shall be notified for that class MT-LR from any value added LCS client when the MT-LR is restricted and be enabled to accept or override the restriction.

NotificationToMSUser ::= ENUMERATED { notifyLocationAllowed ( 0 ), notifyAndVerify-LocationAllowedIfNoResponse ( 1 ), notifyAndVerify-LocationNotAllowedIfNoResponse ( 2 ), locationNotAllowed ( 3 ), not-applicable (255)}ATTENTION: only if GDC (MP) is used !

This parameter is defined according to 3G 29.002.

2.3.199 NoOfUsedTrafficChannels ::= INTEGER -- range 0 to 255 (max. H'FF)

2.3.200

2.3.201 numberOfCellsInVGSGroup

NumberOfCellsInVGSGroup ::= INTEGER -- range 0 to 255 (max. H'FF)


For VGS calls, this parameter specifies the number of local cells in the A-MSC (Anchor MSC), involved in the group call.

2.3.202

2.3.203 NumberOfCellsInVGSGroup ::= INTEGER -- range 0 to 255 (max. H'FF)

2.3.204

2.3.205 numberOfCellsWithSuccSetup

NumberOfCellsWithSuccSetup ::= INTEGER -- range 0 to 255 (max. H'FF)

For VGS calls, this parameter specifies the number of local cells in the A-MSC with successful call setup, involved in the group call.

2.3.206

2.3.207 NumberOfCellsWithSuccSetup ::= INTEGER -- range 0 to 255 (max. H'FF)

2.3.208 numberOfDpEncountered

NumberOfDpEncountered ::= INTEGER -- range 0 to 127 -- the number of DetectionPoints for -- CAMEL Services encountered in the call

This field shows how many detection points (TDP´s as well as EDP´s) armed by the gsmSCF, have been encountered for a certain IN dialog during a call.

2.3.209 oneTimeCharge


2.3.210 NumberOfDpEncountered ::= INTEGER -- range 0 to 127 -- the number of DetectionPoints for -- CAMEL Services encountered in the call

OneTimeCharge ::= OCTET STRING (SIZE(2)) -- octet 1 [aaaCurrency] aaa – Multiplier -- octet 2 [amount 000]

This field is for the project specific concept of ISUP backward charging messages.

+-------------------------------------------------------------------+¦ oneTimeCharge ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ +---------------+ ¦¦ octet 1 ¦a a a¦ Currency¦ aaa - Multiplier ¦¦ +------ ------¦ ¦¦ 2 ¦ amount ¦0¦0¦0¦ ¦¦ +---------------+ ¦+-------------------------------------------------------------------+

The currency amount means Pennies.

The least significant bits of octet 2 are always set to B'0.

2.3.211

2.3.212 OneTimeCharge ::= OCTET STRING (SIZE(2)) -- octet 1 [aaaCurrency] aaa – Multiplier -- octet 2 [amount 000]

2.3.213 optimalRoutingLcf

OptimalRoutingLcf ::= OCTET STRING (SIZE (1)) -- BOOL

This flag is set to TRUE if optimal Routing of late Call Forwarding (ORLCF) was performed successfully, otherwise it is FALSE.

2.3.214

2.3.215 OptimalRoutingLcf ::= OCTET STRING (SIZE (1)) -- BOOL

2.3.216 optimalRoutingMmcEcf

OptimalRoutingMmcEcf ::= OCTET STRING (SIZE (1)) -- BOOL


This flag is set to TRUE if either optimal Routing of Mobile to Mobile Calls (ORMMC) or optimal Routing of Early Call Forwarding (ORECF) was performed successfully, otherwise it is FALSE.

2.3.217

2.3.218 OptimalRoutingMmcEcf ::= OCTET STRING (SIZE (1)) -- BOOL

2.3.219 origTermBscId

OrigTermBscId ::= OCTET STRING (SIZE (3)) -- or if selected (SIZE (2)) -- Signalling Point Code (SPC) of the BS -- for content look at OrigTermMscId

This parameter identifies the originating/terminating BSC. It is the signaling point code of the BSC controlling the area where the MS was roaming at the beginning of the call (or transaction).

For 3G calls this parameter contains the SPC of the RNC.

This parameter identifies the originating/terminating BS. It is the signalling point code of the BSC controlling the area where the MS was roaming at the beginning of the call (or transaction).

+-------------------------------------------------------------------+¦ origTermBscId ¦ Length = 2..3 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ two / three octets ¦¦ ¦+-------------------------------------------------------------------+

The octets contain the signalling point code (SPC) of the BSC (2G) of RNC (3G).

The default length is 3 octets, but the length can be defined (2 or 3) according to therelated SPC length in the network.

If the length is 2, only 14 bit are relevant, the least significant bits are set to B'0'.

If the length is 3, all 24 bit are relevant.

2.3.220 origTermMscId


2.3.221 OrigTermBscId ::= OCTET STRING (SIZE (3)) -- or if selected (SIZE (2)) -- Signalling Point Code (SPC) Of The BS -- content look at OrigTermMscId

2.3.222

OrigTermMscId ::= OCTET STRING (SIZE (3)) -- or if selected (SIZE (2)) -- Signalling Point Code (SPC) Of The MSC -- different coding if SIZE (2) or (3) is selected: -- 2 or 3 octets containing the signalling point code (SPC) -- of the MSC. -- if (SIZE(2)) is selected it is assumed that only 14 bits are -- relevant, the least significant 2 bits are set to 0. -- Example: SPC = 03 - 5 - 01 - 0 -- 14 bit: 0011 101 0001 000 -- 16 bit: 0011 101 0001 000 00 -- Nibbles: 0011 1010 0010 0000 -- 2 Byte coding: 3 A 2 0 -- -- Example: SPC = 03 - 5 - 01 - 0 -- 14 bit: 0011 101 0001 000 -- 24 bit: 0000 0000 00 0011 101 0001 000 -- Nibbles: 0000 0000 0000 1110 1000 1000 -- 3 Byte coding: 0 0 0 E 8 8

This parameter identifies the originating/terminating MSC. In case of MOC, MTC, CFC, SMS, SCI, it is the signalling point code (SPC) of the VMSC, where the MS was roaming at the beginning of the call (or transaction).

In all other cases (e.g. CFU, transit), it is the SPC of the GMSC.

The first SPC that will be found will be used as origTermMscId, started at INAT-0 (International Network 0) to NAT-1 (National Network 1). TMD: NAT-0 applies.

The octets contain the signalling point code (SPC) of the MSC.

The default length is 3 octets, but the length can be defined (2 or 3) according to therelated SPC length in the network.

If the length is 2, only 14 bit are relevant, the least significant bits are set to B'0'.

If the length is 3, all 24 bit are relevant.


2.3.223 OrigTermMscId ::= OCTET STRING (SIZE (3)) -- or if selected (SIZE (2)) -- Signalling Point Code (SPC) Of The MSC -- different coding if SIZE (2) or (3) is selected: -- 2 or 3 octets containing the signalling point code (SPC) -- of the MSC. -- if (SIZE(2)) is selected it is assumed that only 14 bits are -- relevant, the least significant 2 bits are set to 0. -- Example: SPC = 03 - 5 - 01 - 0 -- 14 bit: 0011 101 0001 000 -- 16 bit: 0011 101 0001 000 00 -- Nibbles: 0011 1010 0010 0000 -- 2 Byte coding: 3 A 2 0 -- -- Example: SPC = 03 - 5 - 01 - 0 -- 14 bit: 0011 101 0001 000 -- 24 bit: 0000 0000 00 0011 101 0001 000 -- Nibbles: 0000 0000 0000 1110 1000 1000 -- 3 Byte coding: 0 0 0 E 8 8

2.3.224 otherMSRN

OtherMSRN ::= ServedMSRN -- using the same coding like ServedMSRN but containing the MSRN -- of the other party in MOC and CF records

The MSRN (Mobile Station Roaming Number) of the other party.

This field is available in the concerned record only- if the other party is a mobile subscriber,- if the HLR interrogation takes place in the same MSC, where the record is generated and- if the call was not routed out of the MSC (e.g. by forced routing) before HLR interrogation.

+-------------------------------------------------------------------+¦ otherMSRN ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ Internal structure (less/equal 15 digits) Coded as TBCD-String ¦¦ ¦¦ Country Code (CC): 1 to 3 digits as in CCITT Rec. E 164 ¦¦ National Destination Code (NDC): variable length ¦¦ Subscriber Number (SN): variable length ¦¦ ¦+-------------------------------------------------------------------+

Max. 15 digits, if the MSRN is shorter than 15 digits the filler is used to indicate that no more significant digits will follow.


If data are not available, the filler is used for all digits.

CC, NDC, SN are concatenated in this order.

2.3.225 OtherMSRN ::= ServedMSRN -- using the same coding like ServedMSRN -- but containing the B-MSRN in MOC records

2.3.226

2.3.227 otherParty3a

OtherParty3a ::= OCTET STRING (SIZE(18)) -- according to 3G TS 04.08 -- OCTET 1 -- BIT 8 = extension bit (always 0) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2 -- BIT 8 = extension bit (always 1) -- BIT x-y = screening indicator -- BIT u-v = presentation restriction -- OCTET 3-18 -- maximal 32 digits coded as TBCD-String -- and filled up with fillers

This parameter identifies the partner of the call. The contents are the same as for otherPartyLongNumber, but additionally the octet 3a from signalling interface acc. GSM 04.08, containing the screening and presentation indications, is copied into the field.

This field may be applied for MTC records instead of the field otherPartyLongNumber to assure also for the Billing tickets that the called party doesn't get information about the calling party if the calling party has subscribed to CLIR (especially for foreign subscribers).

If the parameter otherParty is available, it will be composed as shown in the following table. If the parameter is not available and required as mandatory, then the 1st OCTET = H'80 and subsequent OCTETs = H'FF, i.e. without Octet 3a.


+-------------------------------------------------------------------+¦ otherParty3a ¦ length = 3..18 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure as defined in 3G TS 24.008 : ¦¦ ¦¦ First octet default: ¦¦ ¦¦ BIT 8 (msb): extension bit B'0 ¦¦ BIT 7-5 : type of number B'000 ¦¦ BIT 4-1 : numbering plan B'0000 ¦¦ ¦¦ Second octet ¦¦ ¦¦ BIT 8 (msb): extension bit (always 1) B'1 ¦¦ BIT 7-6 : presentation indicator B'00 ¦¦ BIT 5-3 : spare (always 0) B'000 ¦¦ BIT 2-1 : screening indicator B'00 ¦¦ ¦¦ Following octets: ¦¦ max. 32 digits coded as TBCD-string B'1111 ¦¦ ¦+-------------------------------------------------------------------+

2.3.228 otherPartyLocation


2.3.229 OtherParty3a ::= OCTET STRING (SIZE(18)) -- according to 3G TS 04.08 -- OCTET 1 -- BIT 8 = extension bit (always 0) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2 -- BIT 8 = extension bit (always 1) -- BIT x-y = screening indicator -- BIT u-v = presentation restriction -- OCTET 3-18 -- maximal 32 digits coded as TBCD-String -- and filled up with fillers

OtherPartyLocation ::= OCTET STRING (SIZE (2..17)) -- OCTET 1 : OriginIndicator -- 0 ORIGIN_NOT_USED (default) -- 1 ORIGIN_IS_SCP -- 2 ORIGIN_IS_MSC_VLR -- 3 ORIGIN_IS_SIGNALLING -- 4 ORIGIN_IS_DEFAULT_ROUTING -- > 4 reserved -- OCTET (2..17) : LOC_DIGITS (TBCD coded)

+-------------------------------------------------------------------+¦ otherPartyLocation ¦ length = 2..17 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure ¦¦ ¦¦ First octet ¦¦ ¦¦ origin indicator: 0 : origin not used (default) ¦¦ 1 : origin is SCP ¦¦ 2 : origin is MSC/VLR ¦¦ 3 : origin is signalling ¦¦ 4 : origin is default routing ¦¦ >4 : reserved ¦¦ ¦¦ Following octets: default: ¦¦ ¦¦ max. 24 location digits coded as TBCD-string B'1111 ¦¦ ¦+-------------------------------------------------------------------+

The otherPartyLocation is created in case of Number Portability / Local Number Portability and in correlation with a ported subscriber.The parameter shows the Location Roaming Number (LRN) as result of the NP query if a Network Identifier Prefix (NIP) is recognized by the MSC. It is always presented in unknown format. Usually the LRN is the called party with the NIP (a certain prefix that is used for further call processing/routing of the call), e.g.:

number received during NP query type of number number in octet 2..17 as TBCD

0049 D078 177... unknown 0049 D078 177...DD 112345 177... unknown DD 112345 177...


+49 D124 177... international 0049 D124 177...

2.3.230

2.3.231 OtherPartyLocation ::= OCTET STRING (SIZE (2..13)) -- OCTET 1 : OriginIndicator -- 0 ORIGIN_NOT_USED (default) -- 1 ORIGIN_IS_SCP -- 2 ORIGIN_IS_MSC_VLR -- 3 ORIGIN_IS_SIGNALLING -- 4 ORIGIN_IS_DEFAULT_ROUTING -- > 4 reserved -- OCTET (2..13) : LOC_DIGITS (TBCD coded)

2.3.232 otherPartyLongNumber

OtherPartyLongNumber ::= OCTET STRING (SIZE(2..17))

-- according to 3G TS 24.008 -- OCTET 1 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2-17 -- maximal 32 digits coded as TBCD-String -- and filled up with fillers

This parameter identifies the partner of the call.

+-------------------------------------------------------------------+¦ otherPartyLongNumber ¦ length = 2..17 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure as defined in 3G TS 24.008 : ¦¦ ¦¦ First octet default: ¦¦ ¦¦ BIT 8 (msb): extension bit (always 1) B'1 ¦¦ BIT 7-5 : type of number B'000 ¦¦ BIT 4-1 : numbering plan B'0000 ¦¦ ¦¦ Following octets: ¦¦ max. 32 digits coded as TBCD-string B'1111 ¦¦ ¦+-------------------------------------------------------------------+


The field has to be interpreted as follows:

MOC record


This parameter contains the called party number as dialled. The coding is according to the called party BCD number as defined in [04.08]. All dialled digits contained in the called party BCD number are transferred without modification to the OtherPartyLongNumber in the Billing Record.The numbering plan (NP) field is also transferred without modification, except a received NP=’unknown’ is presented as ‘E.164 (ISDN)’.

Format for call/transaction type = MOC

Dialled number OtherPartyLongNumbertype of number Number as TBCD

dialled number type of number number as TBCDipCCNDCXXXX...

unknown ipCCNDCXXXX...

npNDCXXXX... unknown npNDCXXXX...npXXXX... unknown npXXXX...XXXX Unknown XXXX+CCNDCXXXX... international CCNDCXXXX...ip : international prefix CC : Country Codenp: national prefix NDC : National Destination code+ : MS ‘+’ key XX... : number

with: ip: international prefix CC : Country Codenp: national prefix NDC: National Destination code+ : MS + key XX...: number

Emergency call:

In case of dialled EMC, this field contains the dialled number.

In case of an Emergency Set Up, this field is not available.

Format for emergency call:

This field will contain the dialled number.

MTC record

The parameter always contains the ISUP calling party number even if a call forwarding occurred before. The coding is according to the calling party BCD number as defined in [04.08] i.e. incl. octet3a if available (i.e. if extension bit in octet3 = 0).

In case the trunk signalling doesn't contain the calling party or is unable to transfer the calling party address, then the parameter is not available in the MTC record. In case of incomplete other party number, then this field will contain the default value. In all other cases the other party number will be transparently copied from trunk signalling.

Format for call/transaction type = MTC

In case the trunk signalling doesn't contain the calling party or is unable to transfer the calling party address, then the 'other party' is not available or will contain the default value. In case of incomplete other party number, then this field


will contain the default value. In all other cases the other party number will be transparently copied from trunk signalling.

CF record

This field contains the forwarded-to number. In this case the same format as in the VLR/HLR database will be used.

SMSMO/SMSMT records

This field contains the SMSC address.

SCI record

The parameter is only relevant for call forwarding registration: Then it contains the forwarded-to number.

Format for call forwarding record

In this case the same format as in the VLR/HLR database will be used.

2.3.233 otherPartyShortNumber

This parameter identifies the partner of the call in its abbreviated form (short code).

coding a:

OtherPartyShortNumberA ::= OCTET STRING (SIZE(17)) -- according to 3G TS 24.008 -- OCTET 1 = Default H'0 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2-17 -- maximal 4 digits coded as TBCD-String -- and filled up with fillers

+-------------------------------------------------------------------+¦ otherPartyShortNumber ¦ length = 2..17 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure as defined in 3G TS 24.008 : ¦¦ ¦¦ First octet default: ¦¦ ¦¦ BIT 8 (msb): extension bit (always 1) B'1 ¦¦ BIT 7-5 : type of number B'000 ¦¦ BIT 4-1 : numbering plan B'0000 ¦¦ ¦¦ Following octets: ¦¦ max. 4 digits coded as TBCD-string B'1111 ¦¦ ¦+-------------------------------------------------------------------+

This field is only used if a maximum of 4 digits are received. If 5 or more digits are received, the field is not applicable. The filler is used to indicate that no more significant digits will follow.


The parameter is not relevant for supplementary service programming actions such as registration, erasure etc.

The first byte contains always the default value.

OtherPartyShortNumberA ::= OCTET STRING (SIZE(17)) -- according to 3G TS 24.008 -- OCTET 1 = Default H'0 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2-17 -- maximal 4 digits coded as TBCD-String -- and filled up with fillers

coding b:

OtherPartyShortNumberB ::= OCTET STRING (SIZE(2..17)) -- according to 3G TS 24.008 -- OCTET 1 = Default H'0 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2-17 -- maximal 5 digits coded as TBCD-String -- and filled up with fillers

+-------------------------------------------------------------------+¦ otherPartyShortNumber ¦ length = 2..17 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure as defined in 3G TS 24.008 : ¦¦ ¦¦ First octet default: ¦¦ ¦¦ BIT 8 (msb): extension bit (always 1) B'1 ¦¦ BIT 7-5 : type of number B'000 ¦¦ BIT 4-1 : numbering plan B'0000 ¦¦ ¦¦ Following octets: ¦¦ max. 5 digits coded as TBCD-string B'1111 ¦¦ ¦+-------------------------------------------------------------------+

This field is only used if a maximum of 5 digits are received. If 6 or more digits are received, the field is not applicable. The filler is used to indicate that no more significant digits will follow.

The parameter is not relevant for supplementary service programming actions such as registration, erasure etc.

The first byte contains always the default value.


2.3.234

2.3.235 OtherPartyShortNumberB ::= OCTET STRING (SIZE(2..17)) -- according to 3G TS 24.008 -- OCTET 1 = Default H'0 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2-17 -- maximal 5 digits coded as TBCD-String -- and filled up with fillers

2.3.236

2.3.237 otherPartySMS

OtherPartySMS ::= OCTET STRING (SIZE(3..18)) -- according to 3G TS 23.040 -- OCTET 1 -- Address Length -- OCTET 2 -- Type Of Address -- OCTET 3-N -- Address Value transparent

This parameter identifies the destination address the short message was addressed to in case of SMS MO PP or the origination address the short message was addressed from in case of SMS MT PP.

The address is copied transparently from the Short Message Transfer Layer SM-TL (refer to /23.040/).

Be aware that this number can not be verified in any case by the VMSC, neither for its structure nor for its contents. The data are fully transparent.

It is available only in case of a SMS-SUBMIT type. In the case of a SMS-COMMAND type this parameter is not available. A default value can be provided in those cases.


+-------------------------------------------------------------------+¦ otherPartySMS ¦ length = 3..18 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure as defined in 3G TS 23.040 for the ¦¦ TP-Destination-Address (TP-DA): ¦¦ ¦¦ formatted according to the formatting rules of address fields ¦¦ ¦¦ octett 1 Address-Length ¦¦ 2 Type-of-Address ¦¦ 3 first octet of Address-Value ¦¦ : ¦¦ ¦+-------------------------------------------------------------------+

The Type-of-Address can also be "alphanumeric". So the field is coded as a transparent octet string even in case of TBCD coded digits !

2.3.238 outgTgTCompBlock

2.3.239 OtherPartySMS ::= OCTET STRING (SIZE(1..17)) -- according to 3G TS 23.040

2.3.240 -- OCTET 1 -- Address Length -- OCTET 2 -- Type Of Address -- OCTET 3-N -- Address Value transparent

2.3.241

OutgTgTCompBlock ::= SEQUENCE { tgrpNameOg TgrpNameOg, cicOg CicOg, biccCallInstCodeOut BiccCallInstCodeOut}

Note: outgoing trunkgroup and trunk composite block

Contains the trunk-group-data and trunk-data of the outgoing side.

+-------------------------------------------------------------------+¦ outgTgTCompBlock ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ SEQUENCE containing ¦¦ tgrpName ¦¦ cic ¦¦ biccCallInstCodeOut ¦+-------------------------------------------------------------------+

Outgoing trunk-data will always be available in the records for answered calls.


In case of call forwarding, the trunk-data of the last forwarded-to side in the MSC will be present.

2.3.242 pABXNumber (not for PCS projects)

PABXNumber ::= OCTET STRING (SIZE (2..17)) -- Type of number and numbering plan (first octet) + -- transparent copy of SIGNALLED-NUM-ID of PABX calls -- filled up with fillers

This field contains all digits of the PABX number as, including the PABX extension.

+-------------------------------------------------------------------+¦ pABXNumber ¦ Length = 2...17 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ ¦¦ First octet default: ¦¦ ¦¦ BIT 8 (msb): extension bit (always 1) B'1 ¦¦ BIT 7-5 : type of number B'000 ¦¦ BIT 4-1 : numbering plan B'0000 ¦¦ ¦¦ Following octets: ¦¦ max. 32 digits coded as TBCD-string B'1111 ¦¦ ¦¦ fillers up to the end of the field ¦¦ ¦+-------------------------------------------------------------------+

If not the full length of the field is used for the digits, the filler is used to indicate that no more significant digits will follow.


2.3.243

2.3.244 PABXNumber ::= OCTET STRING (SIZE(1..13)) -- Type of number and numbering plan (first octet) + -- transparent copy of SIGNALLED-NUM-ID of PABX calls -- filled up with fillers

2.3.245

2.3.246 partialRecordCorrelationId

PartialRecordCorrelationId ::= OCTET STRING (SIZE(9))

The partialRecordCorrelationId is valid for partial records. Partial records within a call with the same callTransactionType are correlated by the same partialRecordCorrelationId.

Structure:4 bit CallTransactionType according to a switch internal coding4 bit cyclic counter5 byte CallReferenceNumber

2.3.247 partialRecordType

2.3.248 PartialRecordCorrelationId ::= OCTET STRING (SIZE(9))

PartialRecordType ::= ENUMERATED { timeLimit (0), serviceChange (1), locationChange (2), classmarkChange (3), aocParmChange (4), radioChannelChange (5), hSCSDParmChange (6), changeOfCAMELDestination (7), callTransferInvocation (8), changeOfChargeParam (9), changeOfCAMELDestinationSubsequentDialogue (10), changeOfDestination (14), not-applicable (255)}

For CS2.1 the only possible parameter values are ‘timeLimit’ , ‘hSCSDParmChange’, ‘changeOfCAMELDestination’, ‘changeOfDestination’, ' callTransferInvocation', 'changeOfChargeParam' and ' changeOfCAMELDestinationSubsequentDialoge'.


‘time limit’ will be set, if the partial record generation was triggered by an Intermediate Call Duration Timeout (timer T114),

‘hSCSDParmChange’ applies for HSCSD calls and will be set, if the partial record generation was triggered by a change of HSCSD parameters during the call,

‘changeOfCAMELDestination’ applies in case of partial records which are written due to follow-on handling based on a CSI related IN scenario,

the proprietary value ‘changeOfDestination’ will be set in case of partial record generation due to follow-on handling based on a national IN service TDP3 or based on IN SCM service.

the 'callTransferInvocation' is set in case of call transfer invocation. the 'changeOfChargeParam' is set if the SCP sends a new Charge Band Number (CBN) or if

another CBN is sent from another switch (via ISUP). the ' changeOfCAMELDestinationSubsequentDialoge' is set in the case where both T-CSI

and O-CSI dialogues are active: if follow-on for the O-CSI dialogue applies. In this case a partial TIR-Record and a partial CF-Record is created. The partial TIR ticket contains in this special case this partialRecordType.

2.3.249 positioningData

PositioningData ::= OCTET STRING (SIZE (2..33)) -- take input from pseudo data package -- (CDPN_LOCATION_SERVICE_INFO)

This parameter has been renamed, the former name in CS2.1 was positioningMethodUsed.

In case of a loaction request or emergency call (service E911) the parameter indicates the used

positioning method to locate the mobile subscriber.



+-------------------------------------------------------------------+¦ positioningData ¦ Length = 2..33 ¦+--------------------------------+----------------------------------+¦ content ¦ meaning ¦+-------------------------------------------------------------------+¦ internal structure: ¦¦ ¦¦ 8 7 6 5 4 3 2 1 ¦¦ +--------------------------------------+ ¦¦ ¦ ¦ positioning data ¦ ¦¦ 1 ¦ spare ¦ discrimator ¦ ¦¦ +--------------------------------------+ ¦¦ 2 ¦ positioning method¦ usage ¦ positioning method 1 ¦¦ +--------------------------------------+ ¦¦ . ¦¦ +--------------------------------------+ ¦¦ m ¦ positioning method¦ usage ¦ positioning method n ¦¦ +--------------------------------------+ ¦¦ ¦¦ Coding: position method defined in 3G TS 49.031 ¦¦ ¦¦ 1. First octet: Bit 8-5 spare ¦¦ ¦¦ Bit 4-1 positioning data discriminator ¦¦ +----------------------+------------------------------------+ ¦¦ ¦ binary hex dec ¦ meaning ¦ ¦¦ +----------------------+------------------------------------+ ¦¦ ¦ 0000 00 0 ¦ each positioning method ¦ ¦¦ ¦ ¦ used (success or unsuccess) ¦ ¦¦ ¦ all other values ¦ reserved ¦ ¦¦ +----------------------+------------------------------------+ ¦¦ ¦¦ 2. Second and following octets: ¦ ¦ ¦¦ Bit 8-4 positioning method ¦¦ +----------------------+------------------------------------+ ¦¦ ¦ binary hex dec ¦ meaning ¦ ¦¦ +----------------------+------------------------------------+ ¦¦ ¦ 00000 00 0 ¦ timing advance ¦ ¦¦ ¦ 00001 01 1 ¦ time of arival (TOA) ¦ ¦¦ ¦ 00010 02 2 ¦ a of arival (AOA) ¦ ¦¦ ¦ 00011 03 3 ¦ mobile assisted E-OTD ¦ ¦¦ ¦ 00100 04 4 ¦ mobile bassed E-OTD ¦ ¦¦ ¦ 00101 05 5 ¦ mobile assisted GPS ¦ ¦¦ ¦ 00110 06 6 ¦ mobile bassed GPS ¦ ¦¦ ¦ 00111 07 7 ¦ conventional GPS ¦ ¦¦ ¦ 01111 0F 15 ¦ ¦ ¦¦ ¦ . . . ¦ reserved for GSM ¦ ¦¦ ¦ 11111 1F 31 ¦ ¦ ¦¦ +----------------------+------------------------------------+ ¦¦ ¦¦ Bit 3-1 usage ¦¦ +----------------------+------------------------------------+ ¦¦ ¦ binary hex dec ¦ meaning ¦ ¦¦ +----------------------+------------------------------------+ ¦¦ ¦ 000 00 0 ¦ attempt unsuccessfull due to ¦ ¦¦ ¦ ¦ failure or interruption ¦ ¦¦ ¦ 001 01 1 ¦ attempt successfull, result not ¦ ¦¦ ¦ ¦ used to generate location ¦ ¦¦ ¦ 010 02 2 ¦ attempt successfull, result used ¦ ¦¦ ¦ ¦ to verify-not generate location ¦ ¦¦ ¦ 011 03 3 ¦ attempt successfull, result used ¦ ¦¦ ¦ ¦ to generate location ¦ ¦¦ ¦ 100 04 4 ¦ attempt successfull, MS supports ¦ ¦¦ ¦ ¦ multiple mobile based positioning ¦ ¦¦ ¦ ¦ methods, actual used methods by MS ¦ ¦ ¦ ¦ ¦ cannot be determined ¦ ¦ ¦ +----------------------+------------------------------------+ ¦


¦ ¦+-------------------------------------------------------------------+

2.3.250

2.3.251 PartialRecordType ::= ENUMERATED { timeLimit (0), serviceChange (1), locationChange (2), classmarkChange (3), aocParmChange (4), radioChannelChange (5), hSCSDParmChange (6), changeOfCAMELDestination (7), callTransferInvocation (8), changeOfChargeParam (9), changeOfCAMELDestinationSubsequentDialogue (10), changeOfDestination (14) }

2.3.252


2.3.253

2.3.254 PositioningMethodUsed ::= OCTET STRING (SIZE (2..33)) -- take input from pseudo data package (CDPN_LOCATION_SERVICE_INFO)

2.3.255 privacyOptionsInvoked

This parameter indicates if the privacy options of the subscriber (downloaded to the VLR during the location update) were checked according to the different privacy classes and were overridden, if anMT-LR request was notified to the target MS or if a notified MS used the subscription option of verifying to the VMSC whether or not the location is to be allowed.

PrivacyOptionsInvoked ::= ENUMERATED { privacyOverride (0), notificationToMS (1), verificationByMS (2), not-applicable (255) }

ATTENTION: only if ChaSer (CP) is used !This parameter indicates if the privacy options of the subscriber (downloaded to the VLR during the location update) were overridden without indication to MSUB, with notification to MSUB, with confirmation from MSUB. if an MT-LR request was notified to the target MS or if a notified MS used the subscription option of verifying to the VMSC whether or not the location is to be allowed.

2.3.256 privacyOverride

PrivacyOverride ::= BOOLEAN


This parameter indicates if MS privacy is overridden by the LCS client when the GMLC and VMSC or SGSN for an MT-LR are in the same country (acc. 3GPP TS 29.002).

It is set to TRUE, if the LCS client overrides the MS privacy. If not then the parameter is not present in the ticket and the parameter is set to optional.


2.3.257

2.3.258 protocolIdForSMS

ProtocolIdForSMS ::= OCTET STRING (SIZE (1)) -- contains TP-PID acc. 3G TS 23.040 -- take input from CHARGING_INFO.TRANSACTION_INFO.PROTOCOL_ID

This field indicates in case of a short message the particular type of service or device.

For protocolIdForSMS parameter TP-Protocol-Identifier available in /23.040/ is used.

2.3.259 ProtocolIdForSMS ::= OCTET STRING (SIZE(1)) -- contains TP-PID acc. 3G TS 23.040 -- take input from CHARGING_INFO.TRANSACTION_INFO.PROTOCOL_ID

2.3.260 rateIndication

RateIndication ::= OCTET STRING (SIZE (1)) -- content defined as: -- xxxxbbaa where is -- aa - rate adaptation from BCIE -- bb - other rate adaptation from BCIE acc.... -- xxxx - not valid -- See Bearer Capability TS 24.008, “rate adaption” & -- “other rate adaption” -- xxxx0000 noRateAdaption, -- xxxx0001 v110I460X30 , -- xxxx0010 iTUTX31 , -- xxxx0011 v120 , -- xxxx0111 h223H245

This parameter specifies the rate adaptation that was used for the connection. The content is assembled from the parameters rate adaption and other rate adaption signalled between the MS and the network, acc. to BCIE definition of 3G TS 24.008.


2.3.261

2.3.262 RateIndication ::= OCTET STRING (SIZE(1))

2.3.263 -- content defined as:

2.3.264 -- xxxxbbaa where is

2.3.265 -- aa - rate adatpation from BCIE

2.3.266 -- bb - other rate adaptation from BCIE acc....

2.3.267 -- xxxx - not valid

2.3.268

2.3.269 reasonForTermination

ReasonForTermination ::= OCTET STRING (SIZE (1)) -- System Internal Reasons For Call Termination -- range H'00 to H'FF

+-------------------------------------------------------------------+¦ reasonForTermination ¦ length = 1 ¦+--------------------------------+----------------------------------¦¦ content (binary) ¦ meaning ¦+--------------------------------+----------------------------------¦¦ 0000 0000 ¦ ¦¦ 0000 0001 ¦ system internal reasons for ¦¦ . ¦ call termination is sending ¦¦ . ¦ from LTG ¦¦ 1111 1111 ¦ ¦+-------------------------------------------------------------------+

This field will contain the system internal reasons for call termination (RCT). For details see /CAUS/.

2.3.270 recordType

2.3.271 ReasonForTermination ::= OCTET STRING (SIZE(1)) -- System Internal Reasons For Call Termination -- range H'00 to H'FF

RecordTypeA ::= INTEGER { singleTypeA (0), firstTypeA (1),


intermediateTypeA (2), lastTypeA (3), undefined (8)}RecordTypeB ::= INTEGER { singleTypeB (4), firstTypeB (5), intermediateTypeB (6), lastTypeB (7), undefined (8)} -- 1 Byte integer number -- handling of single, first, intermediate and last -- type A / type B is used as indicator for change of -- data record format

+-------------------------------------------------------------------+¦ recordType ¦ ¦+----------------------+--------------------------------------------¦¦ contents ¦ meaning ¦+----------------------+--------------------------------------------¦¦ ¦ ¦¦ 00000000 ¦ type A : Single Billing Record ¦¦ 00000001 ¦ First Intermediate Billing Record ¦¦ 00000010 ¦ Intermediate Billing Record ¦¦ 00000011 ¦ Last Billing Record ¦¦ 00001000 ¦ undefined ¦¦ ¦ ¦¦ 00000100 ¦ type B : Single Billing Record ¦¦ 00000101 ¦ First Intermediate Billing Record ¦¦ 00000110 ¦ Intermediate Billing Record ¦¦ 00000111 ¦ Last Billing Record ¦¦ 00001000 ¦ undefined ¦+-------------------------------------------------------------------+

This is a 1 Byte integer number.

Generally all calls with a duration smaller than the timer for intermediate records produce a 'Single Billing Record'.

For detailed description for generation of intermediate Records please refer /MCR/ and /IN/.

Type A and type B are used to indicate a change of the data record format if two different feature packages are in use within the same PMLN. Only type A shall be used unless specified otherwise.

RecordTypeA ::= INTEGER { singleTypeA (0), firstTypeA (1), intermediateTypeA (2), lastTypeA (3), undefined (8)}RecordTypeB ::= INTEGER { singleTypeB (4), firstTypeB (5), intermediateTypeB (6), lastTypeB (7), undefined (8)


} -- 1 Byte integer number -- handling of single, first, intermediate and last -- type A / type B is used as indicator for change of -- data record format

2.3.272 recordUse

RecordUse ::= BIT STRING (SIZE (2)) -- coding the used Record Use as bitstring: -- 0000 0110 XX00 0000 -- bit 0 : record used for subscriber charging -- bit 1 : record used for interadministrative -- charging -- bit 2..7: reserve

The parameter is coded as BIT-String.

+-------------------------------------------------------------------+¦ recordUse ¦ length = 2 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ ¦¦ First octet: ¦¦ ¦¦ according ASN1 encoding of BIT-String ¦¦ ¦¦ Second octet: ¦¦ ¦¦ 8 7 6 5 4 3 2 1 ¦¦ +-------------------------------¦ ¦¦ ¦ ¦ ¦¦ +-------------------------------¦ ¦¦ coded as follows ¦¦ ¦¦ BIT 8 used for subscriber charging ¦¦ BIT 7 used for interadministrative charging ¦¦ BIT 6 reserved ¦¦ . ¦¦ . ¦¦ BIT 1 reserved ¦¦ ¦+-------------------------------------------------------------------+

The recordUse gives the opportunity of interadministrative charging with the help of call records. For charging purposes it could be possible that the call records are evaluated first for subscriber charging and then for interadministrative charging or only for one. This is only usable if the feature IACTRA is released.

Note that IACTRA is not released for CS2.1!


2.3.273

2.3.274 RecordUse ::= BIT STRING (SIZE (2)) -- coding the used Record Use as bitstring: -- 0000 0110 XX00 0000 -- bit 0 : record used for subscriber charging -- bit 1 : record used for interadministrative charging -- bit 2..7: reserve

2.3.275

2.3.276 redirectionCounter

RedirectionCounter ::= INTEGER -- Number Of Call Forwardings Performed

+-------------------------------------------------------------------+¦ redirectionCounter ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ number of call forwardings performed ¦¦ ¦+-------------------------------------------------------------------+

Range depends on maximum number of call forwardings.

The redirectionCounter can be omitted if the counter is '0' (no call forwarding performed).

2.3.277

2.3.278 RedirectionCounter ::= INTEGER -- Number Of Call Forwardings Performed

2.3.279

2.3.280 secondCellId

SecondCellId ::= OCTET STRING (SIZE (4)) -- LAC Location Area Code -- CI Cell Identification -- OCTET 1-4 -- XXXXXXXX = LAC(MSB) -- XXXXXXXX = LAC(LSB) -- XXXXXXXX = CI(MSB) -- XXXXXXXX = CI(LSB)


+-------------------------------------------------------------------+¦ secondCellId ¦ length = 4 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ ¦¦ 8 7 6 5 4 3 2 1 ¦¦ +-------------------------------¦ ¦¦ 1 ¦ LAC (MSB) ¦ Location Area Code ¦¦ +-------------------------------¦ ¦¦ 2 ¦ LAC (LSB) ¦ ¦¦ +-------------------------------¦ ¦¦ 3 ¦ CI (MSB) ¦ Cell Identification ¦¦ +-------------------------------¦ ¦¦ 4 ¦ CI (LSB) ¦ ¦¦ +-------------------------------+ ¦¦ ¦+-------------------------------------------------------------------+

The second cell identity is available if the feature DIRECTED RETRY is released. LAC and CI are binary coded as shown above. The default value for octets 1..4 is H’00’.

Note!


2.3.281

2.3.282 SecondCellId ::= OCTET STRING (SIZE (4)) -- USE SECOND_CELL_ID OUT OF THE SUBSCRIBER BAR PART -- LAC Location Area Code -- CI Cell Identification -- OCTET 1-4 -- XXXXXXXX = LAC(MSB) -- XXXXXXXX = LAC(LSB) -- XXXXXXXX = CI(MSB) -- XXXXXXXX = CI(LSB)

2.3.283 sequenceNumber

This identifier contains a unique record sequence number. After a recovery of level ISTART1 or higher, as well as after a new activation of the GDCS feature, the sequenceNumbering is reinitiated and starts again with sequenceNumber 0. Several features and database settings can influence the sequence numbering, so that gaps in the sequences of client tickets indicate no fault.

coding a)

SequenceNumberA ::= OCTET STRING (SIZE (3)) -- OCTET 1 -- sequenceNumber MSB -- OCTET 2 -- sequenceNumber continued


-- OCTET 3 -- sequenceNumber LSB

In the sequenceNumber field, bit 8 of octet 1 is the most significant bit and bit 1 of octet 3 is the least significant bit.


coding b)

SequenceNumberB ::= OCTET STRING (SIZE(4)) -- OCTET 1 -- H'00 -- OCTET 2 -- sequenceNumber MSB -- OCTET 3 -- sequenceNumber continued -- OCTET 4 -- sequenceNumber LSB

In the sequenceNumber field, bit 8 of octet 2 is the most significant bit and bit 1 of octet 3 is the least significant bit.

Range: all values are possible

2.3.284 sequenceOfCamelDialogs

SequenceOfCamelDialogs ::= SEQUENCE OF CamelDialog

2.3.285

2.3.286 SequenceNumberB ::= OCTET STRING (SIZE(4)) -- OCTET 1 -- H'00

2.3.287 -- OCTET 2 -- sequenceNumber MSB -- OCTET 3 -- sequenceNumber continued -- OCTET 4 -- sequenceNumber LSB

2.3.288 servedIMEI

ServedIMEI ::= TBCD-String (SIZE (8))

The IMEI is the international mobile station equipment identity.


+-------------------------------------------------------------------+¦ ServedIMEI ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ Internal structure (15 or 16 digits, see below) ¦¦ coded as TBCD-String ¦¦ ¦¦ Type Approval Code (TAC) : 6 digits ¦¦ Final Assembly Code (FAC) : 2 digits ¦¦ Serial Number (SNR) 6 digits ¦+-------------------------------------------------------------------¦¦ GSM Phase < 2+ : ¦¦ Spare for further assignments (SP) : 1 digit ¦+-------------------------------------------------------------------¦¦ GSM Phase >= 2+ : ¦¦ Software Version Number (SVN) : 1 digit (LSN) ¦¦ Software Version Number (SVN) : 1 digit (MSN) ¦+-------------------------------------------------------------------+

LSN = Least Significant Nibble MSN = Most Significant Nibble

The ServedIMEI is coded according to 3G TS 23.003, the length depends on the GSM phase. TAC, FAC, SNR, SP/SVN are concatenated in the above order.

In case of the 15 digit format a filler is used for the last digit. The filler is also used for all digits if no data are available.

Note: From CS2.1 on the digits of servedIMEI can have the following values: 0..9,A..F.

Note: The IMEI is only present in the SMS tickets if and only if the IMEI check (MSECHAND) is activated for SMS and if there is a call in parallel (parallel transaction).

ServedIMEI ::= TBCD-String (SIZE(8)) -- Type Approval Code (TAC) = 6 digits -- Final Assembly Code (FAC) = 2 digits -- Serial Number (SNR) = 6 digits -- Spare for further (SP) = 1 digit

2.3.289 servedIMSI

ServedIMSI ::= TBCD-String (SIZE (1..8))

The IMSI is the international mobile subscriber identity according to CCITT Rec. E 212.

+-------------------------------------------------------------------+¦ servedIMSI ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ Internal structure (less/equal 15 digits) Coded as TBCD-String ¦¦ ¦¦ Mobile Country Code (MCC) : 3 digits ¦¦ Mobile Network Code (MNC) : 2..3 digits ¦¦ Mobile Subscriber Identification Number (MSIN) : n digits ¦¦ ¦+-------------------------------------------------------------------+

Max. 15 digits, if the IMSI is shorter than 15 digits the filler is used to indicate that no more significant digits will follow.


MCC, MNC, MSIN are concatenated in this order.

2.3.290 servedMSIsdn

ServedMSIsdn ::= TBCD-String (SIZE (1..8))

The MSIsdn is the mobile station ISDN number.

+-------------------------------------------------------------------+¦ servedMSIsdn ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ Internal structure (less/equal 15 digits) Coded as TBCD-String ¦¦ ¦¦ can contain: ¦¦ Country Code (CC): 1 to 3 digits as in CCITT Rec. E 164 ¦¦ National Destination Code (NDC): variable length ¦¦ Subscriber Number (SN) ¦¦ ¦+-------------------------------------------------------------------+

Max. 15 digits, if the MSISDN is shorter than 15 digits the filler is used to indicate that no more significant digits will follow.

CC, NDC, SN are concatenated in this order.

Remark on number format in case of multinumbering:

basic MSISDN is the MSISDN, as stored in the VLRdialled MSISDN is the MSISDN, as dialled by subscriber (e.g. without CC, NDC)service MSISDN in case of multinumbering: the MSISDN relating to the applied BasicService

In case of a mobile originating call always the basic MSISDN can be found in the MOC ticket.

In case of a mobile terminating call, the VMSC always considers the basic MSISDN during MTC handling.If, during an MTC attempt to the MS, CFC is detected by the VLR, the VMSC considers the service MSISDN during CF handling.

Therefore the MTC ticket always contains the basic MSISDN.

The content of servedMSISDN in the CF ticket is as follows:

HLR detected CF: CFU, CFNRc(IMSI detach) dialled MSISDN VLR detected CF: CFB, CFNRy, CFNRc[no paging reponse]) service MSISDN

See also ch. <Multiple MSISDN (Multinumbering)> in /CCD(MCR)/.

2.3.291 servedMSRN

ServedMSRN ::= TBCD-String (SIZE (8))

The MSRN is the mobile station roaming number.


+-------------------------------------------------------------------+¦ servedMSRN ¦ length = 1..8 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ Internal structure (less/equal 15 digits) Coded as TBCD-String ¦¦ ¦¦ Country Code (CC): 1 to 3 digits as in CCITT Rec. E 164 ¦¦ National Destination Code (NDC): variable length ¦¦ Subscriber Number (SN): variable length ¦¦ ¦+-------------------------------------------------------------------+

Max. 15 digits, if the MSRN is shorter than 15 digits the filler is used to indicate that no more significant digits will follow.

If data are not available, the filler is used for all digits.

CC, NDC, SN are concatenated in this order.ServedMSRN ::= TBCD-String (SIZE(8)) -- OCTET 1-8 -- Country Code (CC) = 1-3 digits as in CCITT Rec. E 163 -- National Destination Code (NDC) = variable length -- Subscriber Number (SN)

2.3.292 servedOtherNumber

ServedOtherNumber ::= OCTET STRING (SIZE (2..17)) -- OCTET 1 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2-17 digits coded as TBCD-String

This parameter identifies another number than a mobile subscriber.

In TRANSIT records, this number is used to specify the calling party.

In VGS records, it specifies the dialled number of the voice group service.It is only available for dispatcher initiated VGS calls in the AMSC only, because in case of subscriber initiated VGS calls, no number dialling takes place for call setup.+-------------------------------------------------------------------+¦ servedOtherNumber ¦ length = 2..17 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ ¦¦ First octet default: ¦¦ ¦¦ BIT 8 (msb): extension bit (always 1) B'1 ¦¦ BIT 7-5 : type of number B'000 ¦¦ BIT 4-1 : numbering plan B'0000 ¦¦ ¦¦ Following octets: ¦¦ max. 32 digits coded as TBCD-string B'1111 ¦¦ ¦+-------------------------------------------------------------------+

If less digits are used than available in this field, the filler value is used to indicate that no more digits will follow.


2.3.293

2.3.294 ServedOtherNumber::= OCTET STRING (SIZE(2..17)) -- OCTET 1

2.3.295 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2-17 digits coded as TBCD-String

2.3.296

2.3.297 servedSubscriberLocation

The servedSubscriberLocation is created in case of Number Portability / Local Number Portability and in correlation with a ported subscriber.This parameter is a E.164 address of the MSC wich performs the NP query..

ServedSubscriberLocation ::= OCTET STRING (SIZE (2..17)) -- OCTET 1 : OriginIndicator -- 0 ORIGIN_NOT_USED (default) -- 1 ORIGIN_IS_SCP -- 2 ORIGIN_IS_MSC_VLR -- 3 ORIGIN_IS_SIGNALLING -- 4 ORIGIN_IS_DEFAULT_ROUTING -- > 4 reserved -- OCTET (2..13) : LOC_DIGITS (TBCD coded)

The servedSubscriberLocation is created in case of Number Portability / Local Number Portability and in correlation with a ported subscriber.This parameter is a E.164 address of the MSC wich performs the NP query. It is only present if the parameter otherPartyLocation is present.

2.3.298

2.3.299 serviceCentreAddress

ServiceCentreAddress ::= OCTET STRING (SIZE (2..17)) -- according to GSM 03.40 and 09.02 -- OCTET 1 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2-11 -- maximal 20 digits coded as TBCD string


This identifier refers to the network address of a short message service center.

+-------------------------------------------------------------------+¦ serviceCentreAddress ¦ length = 2..17 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure ¦¦ ¦¦ First octet default: ¦¦ ¦¦ BIT 8 (msb): extension bit (always 1) B'1 ¦¦ BIT 7-5 : type of number B'000 ¦¦ BIT 4-1 : numbering plan B'0000 ¦¦ ¦¦ Following octets: ¦¦ max. 32 digits coded as TBCD-string B'1111 ¦¦ ¦+-------------------------------------------------------------------+

The short message centre address is a E.164 number as described in /03.40/.

The internal structure is specified in /09.02/.

Max. 32 digits, if the number is shorter than 20 digits the filler is used to indicate that no more significant digits will follow.

ServiceCentreAddress ::= OCTET STRING (SIZE(2..17)) -- according to GSM 03.40 and 09.02 -- OCTET 1 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2-11 -- maximal 20 digits coded as TBCD string

2.3.300 sMReference

SMReference ::= OCTET STRING (SIZE (1)) -- range 0-25

This is the short message identifier between VMSC and MS, acc. /23.040/, also called short message reference in the short message relay layer, acc. /24.011/.

+-------------------------------------------------------------------+¦ sMReference ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ one octet ¦¦ ¦+-------------------------------------------------------------------+

Range: 0 ... 255


2.3.301

2.3.302 SMReference ::= OCTET STRING (SIZE(1)) -- range 0-25

2.3.303

2.3.304 sMTransmissionResult

SMTransmissionResult ::= OCTET STRING (SIZE (1))

This parameter represents the result of the transmission of a short message.

+-------------------------------------------------------------------+¦ sMTransmissionResult ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ 00000000 ¦ unsuccessful ¦¦ 00000001 ¦ successful ¦+-------------------------------------------------------------------+

2.3.305

2.3.306 SMTransmissionResult ::= OCTET STRING (SIZE(1))

2.3.307 speechCode

SpeechCode ::= OCTET STRING (SIZE (1)) -- OCTET 1: -- for PCS1900 coded according to J-STD-007 Air Interface: -- Volume 2 Part 2 Table 2.10.72, -- Bearer capability information element -- BIT 8 = 0/1 indicating extension -- (1) for no extension -- BIT 7 = coding (0) -- BIT 56 = spare (00) -- BIT 4321 = Speech Version Indication -- 0000 = speech full rate version 1 -- 0010 = speech full rate version 2 -- 0100 = speech full rate version 3 -- 0001 = speech half rate version 1 -- 0011 = speech half rate version 2 -- 0101 = speech half rate version 3 -- for GSM/UMTS coded according 3G TS 28.062 -- BIT 8 = spare (0) -- BIT 765 4321 = Speech Version Indication -- 000 0001 = speech full rate version 1


-- 001 0001 = speech full rate version 2 -- 010 0001 = speech full rate version 3 -- 000 0101 = speech half rate version 1 -- 001 0101 = speech half rate version 2 -- 010 0101 = speech half rate version 3 speechfullrateversion1 SpeechCode ::= '01'H speechfullrateversion2 SpeechCode ::= '11'H speechfullrateversion3 SpeechCode ::= '21'H speechhalfrateversion1 SpeechCode ::= '05'H speechhalfrateversion2 SpeechCode ::= '15'H speechhalfrateversion3 SpeechCode ::= '25'H pCSspeechfullrateversion1 SpeechCode ::= '80'H pCSspeechhalfrateversion1 SpeechCode ::= '81'H pCSspeechfullrateversion2 SpeechCode ::= '82'H pCSspeechhalfrateversion2 SpeechCode ::= '83'H pCSspeechfullrateversion3 SpeechCode ::= '84'H pCSspeechhalfrateversion3 SpeechCode ::= '85'H

This element indicates the speech version being used by the BSS.

For GSM/UMTS projects, this element is coded according to 3 G TS 28.062 .

For PCS1900 project, it is coded according to J-STD-007 Air Interface:Volume 2 Part 2 Table 2.10.72 .


+-------------------------------------------------------------------+¦ speechCode ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ GSM coding ¦ ¦¦ ¦ ¦¦ Bit 8 ¦ = spare (0) ¦¦ Bit 765 4321 ¦ = Speech Version Indication ¦¦ ¦ ¦¦ binary hex ¦ ¦¦ 0 ¦ ¦¦ 000 0001 01 ¦ GSM speech full rate version 1 ¦¦ 001 0001 11 ¦ GSM speech full rate version 2 ¦¦ 010 0001 21 ¦ GSM speech full rate version 3 ¦¦ 000 0101 05 ¦ GSM speech half rate version 1 ¦¦ 001 0101 15 ¦ GSM speech half rate version 2 ¦¦ 010 0101 25 ¦ GSM speech half rate version 3 ¦+--------------------------------+----------------------------------+¦ PCS coding ¦ ¦¦ ¦ ¦¦ Bit 8 ¦ = indicating extension ¦¦ ¦ (1) for no extension ¦¦ Bit 7 ¦ = coding (0) ¦¦ Bit 65 ¦ = spare (00) ¦¦ Bit 4321 ¦ = Speech Version Indication ¦¦ ¦ ¦¦ binary hex ¦ ¦¦ 1 ¦ ¦¦ 0 ¦ ¦¦ 00 ¦ ¦¦ 0000 80 ¦ PCS speech full rate version 1 ¦¦ 0001 81 ¦ PCS speech half rate version 1 ¦¦ 0010 82 ¦ PCS speech full rate version 2 ¦¦ 0011 83 ¦ PCS speech half rate version 2 ¦¦ 0100 84 ¦ PCS speech full rate version 3 ¦¦ 0101 85 ¦ PCS speech half rate version 3 ¦+--------------------------------+----------------------------------+

2.3.308


2.3.309 SpeechCode ::= OCTET STRING (SIZE(1)) -- OCTET 1: -- for PCS1900 coded according to J-STD-007 Air Interface: -- Volume 2 Part 2 Table 2.10.72, -- Bearer capability information element -- BIT 8 = 0/1 indicating extension -- (1) for no extension -- BIT 7 = coding (0) -- BIT 56 = spare (00) -- BIT 4321 = Speech Version Indication -- 0000 speech full rate version 1 -- 0010 speech full rate version 2 -- 0100 speech full rate version 3 -- 0001 speech half rate version 1 -- 0011 speech half rate version 2 -- 0101 speech half rate version 3 -- for GSM/UMTS coded according 3G TS 28.062 -- Bit 8 = spare (0) -- Bit 765 4321 = Speech Version Indication -- 000 0001 speech full rate version 1 -- 001 0001 speech full rate version 2 -- 010 0001 speech full rate version 3 -- 000 0101 speech half rate version 1 -- 001 0101 speech half rate version 2 -- 010 0101 speech half rate version 3 speechfullrateversion1 SpeechCode ::= '01'H speechfullrateversion2 SpeechCode ::= '11'H speechfullrateversion3 SpeechCode ::= '21'H speechhalfrateversion1 SpeechCode ::= '05'H speechhalfrateversion2 SpeechCode ::= '15'H speechhalfrateversion3 SpeechCode ::= '25'H pCSspeechfullrateversion1 SpeechCode ::= '80'H pCSspeechhalfrateversion1 SpeechCode ::= '81'H pCSspeechfullrateversion2 SpeechCode ::= '82'H pCSspeechhalfrateversion2 SpeechCode ::= '83'H pCSspeechfullrateversion3 SpeechCode ::= '84'H pCSspeechhalfrateversion3 SpeechCode ::= '85'H

2.3.310

2.3.311 speechCodeVgs

SpeechCodeVgs ::= SpeechCode -- speech code used in the VGS call

This parameter defines the Codec type or speech version being used by the BSS for the Downlink Listeners Link setups for VGCS/VBS group calls.

This element has the same coding as parameter speechCode (see 2.3.307).


2.3.312

2.3.313 SpeechCodeVgs ::= SpeechCode -- speech code used in the VGS call

2.3.314

2.3.315 sSCode

SSCode ::= OCTET STRING (SIZE(1..56))

This parameter identifies invoked supplementary services for the call / transaction.

coding a:

This coding gives all invoked supplementary services in one octet string.

It can be used when sSSequenceOf is not used.

+-------------------------------------------------------------------+¦ sSCode ¦ length varies ¦+--------------------------------+----------------------------------¦¦ content (values per octet) ¦ meaning ¦+-------------------------------------------------------------------¦¦ ¦¦ As defined in GSM 29.002 ¦¦ ________________________________________________________________ ¦¦ ¦¦ PLMN specific values ¦¦ (as defined in the project database): ¦¦ ¦¦ Hot Billing ¦¦ Call Back ¦¦ PRM rate call barring: ¦¦ - Information type ¦¦ - Entertainment type ¦¦ Call Transfer*) ¦¦ CCBS*) ¦¦ IN Service Class Mark_MOC ¦¦ IN Service Class Mark_MTC ¦+-------------------------------------------------------------------+

*)Call Transfer is implemented as PLMN specific supplementary service

only, the value acc. 3G TS 29.002 are not applicable. The same handling

exists for CCBS if the Mobile Station is a Mobile Station Phase 1 or 2.

For Mobile Stations using Mobile Station Phase 2+ values acc. 3G

TS 29.002 for CCBS are applicable.

Values and internal structure according to /29.002/ (MAP).

Every octet identifies one supplementary service invocation.

The length is limited to the number of available supplementary services. Hence the length can vary from one record to the other.

SSCode ::= OCTET STRING (SIZE(1..40)) -- if fixed length selected then filled up with fillers -- if used in SEQUENCE OF then coded as SIZE(1))


-- according to 3G TS 29.002 (MAP) -- one Supplementary Service entry per octet

coding b:

This coding is used when a length is entered for SSCode. In other words, to get this coding,a length of this field must be entered (may be the same as the maximun default value).

It can be used when sSSequenceOf is not used.

In this case this field contains all invoked supplementary services (one per octet in the octet string) up to the number of octets entered as length for this field. Any remaining octets are filled with the filler.

+-------------------------------------------------------------------+¦ sSCode ¦ length as entered ¦+--------------------------------+----------------------------------¦¦ content (values per octet) ¦ meaning ¦+-------------------------------------------------------------------¦¦ ¦¦ as defined in /29.002/ ¦¦ or ¦¦ PLMN specific values as defined in the project database ¦¦ ¦¦ Hot Billing ¦¦ Call Back ¦¦ PRM rate call barring: ¦¦ - Information type ¦¦ - Entertainment type ¦¦ Call Transfer*) ¦¦ CCBS*) ¦¦ IN Service Class Mark_MOC ¦¦ IN Service Class Mark_MTC ¦¦ _________________________________________________________________ ¦¦ ¦¦ Following octets (up to the value entered for length): ¦¦ filler value ¦¦ ¦+-------------------------------------------------------------------+




For Mobile Stations using Mobile Station Phase 2+ values acc.

3G TS 29.002 for CCBS are applicable.

Values and internal structure of the first octet are according to /29.002/ (MAP).

Every octet up to the first filler octet identifies one supplementary service invocation.


coding c:

This coding is used when SSCode is element of a SEQUENCE OF. In other words, to get this coding, sSSequenceOf has to be used.

In this case this field contains one invoked supplementary service. The definition of an ASN.1 structure SEQUENCE OF (sSSequenceOf) allows to get all invoked supplementary services in the billing record (up to the maximum number of SSCode defined for sSSequenceOf in Table 15:).

+-------------------------------------------------------------------+¦ sSCode ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ First octet: ¦¦ as defined in /29.002/ ¦¦ or ¦¦ PLMN specific values ¦¦ ¦¦ Hot Billing ¦¦ Call Back ¦¦ PRM rate call barring: ¦¦ - Information type ¦¦ - Entertainment type ¦¦ Call Transfer*) ¦¦ CCBS*) ¦¦ IN Service Class Mark_MOC ¦¦ IN Service Class Mark_MTC ¦¦ _________________________________________________________________ ¦¦ ¦¦ Following octets (if any): ¦¦ filler value ¦¦ ¦+-------------------------------------------------------------------+




For Mobile Stations using Mobile Station Phase 2+ values acc. 3G TS 29.002

for CCBS are applicable.

Values and internal structure of the first octet are according to 3G TS 29.002 (MAP).

Any following octets are filled with the filler.


2.3.316 sSInvocCode

SSInvocCode ::= OCTET STRING (SIZE(1)) -- according to /29.002/ (MAP) -- or PLMN Specific Values

This field is only available for Call Transfer.

This field contains the code of the invoked supplementary service. It has the same internal structure as SSCode coding c.

+-------------------------------------------------------------------+¦ sSInvocCode ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ First octet: ¦¦ as defined in /29.002/ (not applicable) ¦¦ or ¦¦ PLMN specific values ¦¦ ¦¦ Call Transfer*) ¦¦ CCBS*) ¦¦ _________________________________________________________________ ¦¦ ¦¦ Following octets (if any): ¦¦ filler value ¦¦ ¦+-------------------------------------------------------------------+


only, the values acc. 3G TS 29.002 are not applicable.

2.3.317 SSInvocCode ::= OCTET STRING (SIZE(1)) -- according to /29.002/ (MAP) -- or PLMN Specific Values

2.3.318 sSInvocDate

SSInvocDate ::= OCTET STRING (SIZE (3)) -- yy: year (2 digits) -- mm: month (2 digits) -- dd: day (2 digits)


This field contains the date of the invocation of the supplementary service.


+-------------------------------------------------------------------+¦ sSInvocDate ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure : ¦¦ YY, MM, DD ¦+-------------------------------------------------------------------+

2.3.319

2.3.320 SSInvocDate ::= OCTET STRING (SIZE(3)) -- yy: year (2 digits) -- mm: month (2 digits) -- dd: day (2 digits)

2.3.321 sSInvocSucc


This parameter represents the result of the supplementary service invocation.

SSInvocSucc ::= OCTET STRING (SIZE (1)) -- 00000000 = unsuccessful -- 00000001 = successful -- unsuccessfulSSInvoc SSInvocSucc ::= '0'H -- successfulSSInvoc SSInvocSucc ::= '1'H


This parameter represents the result of the supplementary service invocation.


2.3.322 sSInvocTime

SSInvocTime ::= OCTET STRING (SIZE (3)) -- hh: hour (2 digits) -- mm: minutes (2 digits) -- ss: seconds (2 digits)


This field contains the time of the invocation of the supplementary service.

+-------------------------------------------------------------------+¦ sSInvocTime ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure : ¦¦ HH, MM, SS ¦¦ ¦+-------------------------------------------------------------------+

2.3.323

2.3.324 SSInvocTime ::= OCTET STRING (SIZE(3)) -- hh: hour (2 digits) -- mm: minutes (2 digits) -- ss: seconds (2 digits)

2.3.325 sSSequenceOf

sSSequenceOf ::= SEQUENCE OF sSCode

This field contains a sequence of invoked supplementary services and is only available if ‘SSCode = coding “c” ‘.

+-------------------------------------------------------------------+¦ sSSequenceOf ¦ variable length ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ SEQUENCE OF SSCode ¦+-------------------------------------------------------------------+

The number of SSCode is given by the length value in Table 15: . If no length is given there, the length varies with the number of active supplementary services for the call / transaction during record generation time.

SSSequenceOf is also available as a SET OF SSCode (doesn't impact the data presentation, but the universal tag if used).


2.3.326 startOfChargingdate

StartOfChargingdate ::= OCTET STRING (SIZE (3)) -- octets BCD coded -- yy: year (2 digits) -- mm: month (2 digits) -- dd: day (2 digits) -- example: march 14th. 1997 coded as '970314'

+-------------------------------------------------------------------+¦ startOfChargingdate ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure : ¦¦ YY, MM, DD ¦+-------------------------------------------------------------------+

In case the recordType indicates "intermediate" or "last", this field contains the date of the opening of the record (i.e. may be different from the conversation begin date).

2.3.327

2.3.328 StartOfChargingdate ::= OCTET STRING (SIZE(3)) -- octets BCD coded -- yy: year (2 digits) -- mm: month (2 digits) -- dd: day (2 digits) -- example: march 14th. 1997 coded as '970314'

2.3.329 startOfChargingtime

StartOfChargingtime ::= SET OF TimeStamp

+-------------------------------------------------------------------+¦ startOfChargingtime ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ SET OF up to 6 Timestamps ¦¦ ¦+-------------------------------------------------------------------+

startOfChargingtime is also available as a SEQUENCE OF timeStamps (doesn't impact the data presentation, but the universal tag if used).

In case the recordType indicates "intermediate" or "last", the first timeStamp contains the time of the opening of the record (i.e. may be different from the conversation begin time).

The use of more than one timestamp is possible in case of occurrences of tariff switches during that part of the call that is covered by the current record (advice of charge).

The length depends on the number of timestamps noted in the record. Hence the length can change from one record to the other.


2.3.330 subscriberCategory

SubscriberCategory ::= OCTET STRING (SIZE (1)) -- GSM 09.02

This parameter contains the ‘calling party’s category’ for mobile subscriber management of MAP interface in mobile originated case as defined in ISUP Whitebook (Q.763).

+-------------------------------------------------------------------+¦ subscriberCategory ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ ¦¦ 'calling party’s category' as defined in ISUP Whitebook (Q.763): ¦¦ ¦¦ 00000000 unknown at this time ¦¦ 00000001 operator, language French ¦¦ 00000010 operator, language English ¦¦ 00000011 operator, language German ¦¦ 00000100 operator, language Russian ¦¦ 00000101 operator, language Spanish ¦¦ 00000110 available to administration for ¦¦ 00000111 selecting a particular language ¦¦ 00001000 by mutual agreement ¦¦ 00001001 reserved (see Recommendation Q.104) ¦¦ 00001010 ordinary calling subscriber ¦¦ 00001011 calling subscriber with priority ¦¦ 00001100 data call (voice band data) ¦¦ 00001101 test call ¦¦ 00001110 spare ¦¦ 00001111 payphone ¦¦ 00010000 ¦¦ to spare ¦¦ 11011111 ¦¦ 11100000 ¦¦ to reserved for national use ¦¦ 11111110 ¦¦ 11111111 spare ¦¦ ¦+-------------------------------------------------------------------+

Remark for SUBOG record:- for digital subscriber, subscriberCategory is H’0A- for analogue subscriber, subscriberCategory is H’0E

2.3.331

2.3.332 SubscriberCategory ::= OCTET STRING (SIZE(1)) -- GSM 09.02

2.3.333 supplServiceInfo

SupplServiceInfo ::= SEQUENCE { callHoldInvocCount CallHoldInvocCount OPTIONAL, callWaitInvocCount CallWaitInvocCount OPTIONAL, sSCode SSCode OPTIONAL, sSInvocation SSInvocation OPTIONAL


}

This parameter identifies all invoked supplementary services.

+-------------------------------------------------------------------+¦ supplServiceInfo ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ SEQUENCE containing ¦¦ callHoldInvocCount ¦¦ callWaitInvocCount ¦¦ sSCode ¦¦ sSInvocation ¦+-------------------------------------------------------------------+

The length is limited to the number of available fields. Hence the length can change from one record to the other.


2.3.334 systemType

This flag indicates the use of the UMTS 3G-air-interface.SystemType ::= ENUMERATED { unknown (0), iuUTRAN (1), not-applicable (255)}This field is present conditionally, indicating the use of a 3G air-interface for the provision of service recorded by this CDR.In the case of service provided by a GSM air interface, the field is not present.

GERAN access is not supported.

The parameter systemType is not provided in CFU and CFC records because the radio access is unknown if the switch generating the CF record is different from the switch accessing the radio network.

2.3.335 tariffInfo

TariffInfo ::= OCTET STRING (SIZE (3)) -- octet 1 [Point ] -- octet 2 [Code 00] -- octet 3 [aaaa b000] aaaa - Tariff Type -- b - Advice of Charge Indicator


+-------------------------------------------------------------------+¦ tariffInfo ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ +---------------+ ¦¦ octet 1 ¦ Point ¦ aaaa - Tariff Type ¦¦ + +---¦ ¦¦ 2 ¦ Code ¦0¦0¦ b - Advice of Charge ¦¦ +-----------+-+-¦ Indicator ¦¦ 3 ¦a a a a¦b¦0¦0¦0¦ ¦¦ +---------------+ ¦+-------------------------------------------------------------------+

The first two octets contain the signalling point code (SPC) of the transit switch which has sent this tariffInfoPack. Only 14 Bit are relevant, the least significant bits are set to B'0.

The Advice of Charge Indicator is always set to B'0.

The least significant bits of octet 3 are always set to B'0.


2.3.336

2.3.337 TariffInfo ::= OCTET STRING (SIZE(3)) -- octet 1 [Point ] -- octet 2 [Code 00] -- octet 3 [aaaa b000] aaaa - Tariff Type -- b - Advice of Charge Indicator

2.3.338 tariffInfoPack

TariffInfoPack ::= SEQUENCE { tariffInfo TariffInfo OPTIONAL, oneTimeCharge OneTimeCharge OPTIONAL, timeTariff TimeTariff OPTIONAL}


+-------------------------------------------------------------------+¦ tariffInfoPack ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure: ¦¦ SEQUENCE containing ¦¦ tariffInfo ¦¦ oneTimeCharge ¦¦ timeTariff ¦+-------------------------------------------------------------------+

The length is limited to the number of available fields.



2.3.339 termCamelRecordInVMSC

TermCamelRecordInVMSC ::= OCTET STRING (SIZE (1)) -- BOOL

The parameter indicates that this TCR-Record was generated due to VT_CSI triggered IN-Dialog of the corresponding subscriber in the VMSC.

Note:

Since CS2.1 two TCR-Records can be generated for one subscriber in one call. The first Record results from the T_CSI triggered IN-Dialog, the second record results from the VT_CSI triggered IN-Dialog of the same subscriber.

The TCR-Record resulting from a T_CSI triggered IN-Dialog is always generated in the GMSC. The TCR-Record resulting from the VT_CSI triggered IN-Dialog is always generated in the VMSC.

As result two separate TCR-Records or sequences of TCR-Records can be generated for one subscriber. Note that if GMSC=VMSC then also 2 TCR-Records are generated in the same MSC. With the help of the parameter termCamelRecordInVMSC the TCR-Records or the sequence of TCR-Records can be distinguished.

2.3.340

2.3.341 TermCamelRecordInVMSC ::= OCTET STRING (SIZE (1)) -- BOOL

2.3.342 tgrpNameIc, tgrpNameOg

This parameter is the symbolic name of a trunk group, as entered by the MSC Trunkgroup Administration MML-Command. If not available, the field is completely filled with ASCII 'SPACE' (default value)

TgrpNameIc ::= IA5String (SIZE (6)) -- Up To 6 Characters -- left justified -- not used characters contain ASCII 'Space'

TgrpNameOg ::= IA5String (SIZE (6)) -- Up To 6 Characters -- left justified -- not used characters contain ASCII 'Space'

This parameter is the symbolic name of a trunk group, as entered by the MSC Trunkgroup Administration MML-Command. If not available, the field is completely filled with ASCII 'SPACE' (default value)


2.3.343 thirdParty

ThirdParty ::= OCTET STRING (SIZE (2..17)) -- according to 3G TS 24.008 -- OCTET 1 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2-17 digits

This parameter identifies the third party which may be involved in a call.

Application: identification of the calling party (A-party) in the billing records for a forwarding leg (B-C). In case of a preceding CF, the thirdParty can contain the A-party (calling) or B-party (forwarding), depending on ADIGCPN.

+-------------------------------------------------------------------+¦ thirdParty ¦ length = 2..17 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure as defined in /24.008/ : ¦¦ ¦¦ First octet default: ¦¦ ¦¦ BIT 8 (msb): extension bit (always 1) B'1 ¦¦ BIT 7-5 : type of number B'000 ¦¦ BIT 4-1 : numbering plan B'0000 ¦¦ ¦¦ Following octets: ¦¦ max. 32 digits coded as TBCD-string B'1111 ¦¦ ¦+-------------------------------------------------------------------+

Max. 32 digits. If less than 32 digits are used, the filler is used to indicate that no more significant digits will follow.

The most significant bit of first octet is always "1".

ThirdParty ::= OCTET STRING (SIZE(2..17)) -- according to 3G TS 24.008 -- OCTET 1 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2-17 digits


2.3.344 timeOfCAMELLeg

TimeOfCAMELLeg ::= OCTET STRING (SIZE (3)) -- octets BCD coded -- hh: hour (2 digits) -- mm: minutes (2 digits) -- ss: seconds (2 digits) -- example: 08:27:56 coded as '082756'

This parameter specifies the time when a CAMEL outgoing leg was set up and is only present if an IN service was actually triggered.+-------------------------------------------------------------------+¦ timeOfCAMELLeg ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure : ¦¦ HH, MM, SS ¦¦ ¦+-------------------------------------------------------------------+

2.3.345

2.3.346 TimeOfCAMELLeg ::= OCTET STRING (SIZE(3)) -- octets BCD coded -- hh: hour (2 digits) -- mm: minutes (2 digits) -- ss: seconds (2 digits) -- example: 08:27:56 coded as '082756'

2.3.347 timeQuality

TimeQuality ::= INTEGER { secure (0), insecure (1)}

This parameter specifies, whether the time fields are reliable or not.

+-------------------------------------------------------------------+¦ timeQuality ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ 00000000 ¦ secure ¦¦ 00000001 ¦ insecure ¦¦ ¦ ¦+-------------------------------------------------------------------+

Time quality becomes insecure only if both system clocks are malfunctioning or after a System Recovery as long as the time is not set "secure" via MML input.


The time quality in CP and GP might differ in case of a manual time adjustment in the CP when the CP time is set to insecure intentionally before the time is entered. Upon time entering, the CP and GP times are synchronized and remain insecure until they are set to secure manually. After 5 minutes the times are set to secure automatically.

2.3.348

2.3.349 TimeQuality ::= INTEGER { secure (0), insecure (1) }

2.3.350

2.3.351 timeStamp

TimeStamp ::= OCTET STRING (SIZE (3)) -- octets BCD coded -- hh: hour (2 digits) -- mm: minutes (2 digits) -- ss: seconds (2 digits) -- example: 08:27:56 coded as '082756'

see 2.3.329 startOfChargingtime+-------------------------------------------------------------------+¦ timeStamp ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure : ¦¦ HH, MM, SS ¦¦ ¦+-------------------------------------------------------------------+

2.3.352

2.3.353 TimeStamp ::= OCTET STRING (SIZE(3)) -- octets BCD coded -- hh: hour (2 digits) -- mm: minutes (2 digits) -- ss: seconds (2 digits) -- example: 08:27:56 coded as '082756'

2.3.354 timeTariff

TimeTariff ::= OCTET STRING (SIZE (3)) -- octet 1 [aabbbccc] aa - Effect of tariff


-- octet 2 [currency amount] bbb - Length of time unit -- octet 3 [ 000000] ccc - Multiplier


+-------------------------------------------------------------------+¦ timeTariff ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure : ¦¦ +---------------+ ¦¦ octet 1 ¦a a¦b b b¦c c c¦ aa - Effect of tariff ¦¦ +---------------¦ ¦¦ 2 ¦currency amount¦ bbb - Length of time unit ¦¦ + ------------¦ ¦¦ 3 ¦ ¦0¦0¦0¦0¦0¦0¦ ccc - Multiplier ¦¦ +---------------+ ¦¦ ¦+-------------------------------------------------------------------+

The currency amount means Pennies.

The least significant bits of octet 3 are always set to B'0'.

2.3.355

2.3.356 TimeTariff ::= OCTET STRING (SIZE(3)) -- octet 1 [aabbbccc] aa - Effect of tariff -- octet 2 [currency amount] bbb - Length of time unit -- octet 3 [ 000000] ccc - Multiplier

2.3.357

2.3.358 traceReference

TraceReference ::= OCTET STRING (SIZE (1..2)) -- according to 3G TS 29.002 (MAP)

2.3.359

2.3.360 traceType

TraceType ::= OCTET STRING (SIZE (1)) -- allEventsNormalTrace TraceType ::= '0'H -- callsOnlyNormalTrace TraceType ::= '1'H -- allEventsPriorityTrace TraceType ::= '2'H -- callsOnlyPriorityTrace TraceType ::= '3'H


2.3.361

2.3.362 transactionIdentification

TransactionIdentification ::= OCTET STRING (SIZE (1)) -- according to 3G TS 24.008 / 24.007 not all bits are relevant -- default value = B'X0000000' -- BIT 8 = TI-Flag -- '1' for mTC, mTCATT, sMSMT -- '0' for all other's -- BIT 7-5 = TI-Value -- '111' reserved for further usage -- BIT 4-1 = not relevant

The TransactionIdentifier is necessary to identify different records with following identical parameters:- ServedMSIsdn, ServedIMSI, ServedIMEI- Other Party- time fields- BasicServiceThe transactionIdentification is necessary, if the following parameters are identical:

mobile number

time fields

basic services (individual teleservice/bearerservice)


+-------------------------------------------------------------------+¦ transactionIdentification ¦ ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+--------------------------------+----------------------------------¦¦ as defined in /24.008/ ¦ ¦¦ ¦ ¦¦ BIT 8 (msb) ¦ TI-Flag ¦¦ BIT 7-5 ¦ TI-Value ¦¦ BIT 4-1 ¦ not relevant ¦¦ ¦ ¦+-------------------------------------------------------------------+

2.3.363 According to /24.008/ not all bits are relevant.

2.3.364 The TI-Flag is '1' for MTC, MTC attempt and SMS MT records. It is '0' for all other records.

2.3.365

2.3.366 TransactionIdentification ::= OCTET STRING (SIZE(1)) -- according to 3G TS 24.008 / 24.007 not all bits are relevant -- default value = B'X0000000' -- BIT 8 = TI-Flag -- '1' for mTC, mTCATT, sMSMT -- '0' for all other's -- BIT 7-5 = TI-Value -- '111' reserved for further usage -- BIT 4-1 = not relevant

2.3.367

2.3.368 translatedOtherParty

TranslatedOtherParty ::= OCTET STRING (SIZE(2..17)) -- according to 3G TS 24.008 -- OCTET 1 -- BIT 8 = extension bit (always 1) -- BIT 7-5 = type of number -- BIT 4-1 = numbering plan -- OCTET 2-17 -- maximal 32 digits coded as TBCD-String -- and filled up with fillers

This parameter identifies the partner of the call. For example in case of MOC it will be the called party number, in case of MTC the calling party number. For details please refer to /MCR/.


+-------------------------------------------------------------------+¦ translatedOtherParty ¦ length = 2..17 ¦+--------------------------------+----------------------------------¦¦ content ¦ meaning ¦+-------------------------------------------------------------------¦¦ internal structure as defined in /24.008/ : ¦¦ ¦¦ First octet default: ¦¦ ¦¦ BIT 8 (msb): extension bit (always 1) B'1 ¦¦ BIT 7-5 : type of number B'000 ¦¦ BIT 4-1 : numbering plan B'0000 ¦¦ ¦¦ Following octets: ¦¦ max. 32 digits coded as TBCD-string B'1111 ¦¦ ¦+-------------------------------------------------------------------+


2.3.369 transmissionMode

2.3.370

2.3.371 TranslatedOtherParty ::= OtherPartyLongNumber

coding a:

This parameter indicates whether a fullrate or a halfrate channel is used and whether a transparent or non-transparent connection is used (data call) .

TransmissionModeA ::= OCTET STRING (SIZE (1)) -- containing XXXXTTCC with -- XXXX not used -- TT transparency -- CC chosen channel rate -- Combination Of -- XXXXXX00 = unknown (default) -- XXXXXX01 = fullrate -- XXXXXX10 = halfrate -- XXXX00XX = unknown (default) -- XXXX01XX = transparent -- XXXX10XX = non transparent

This parameter indicates whether a fullrate or a halfrate channel is used and whether a transparent or non-transparent connection is used (data call) .

coding b:

This parameter indicates:

which channel rate has been requested by the Mobile Station

which channel rate finally has been chosen by the MSC/BSS system


whether a transparent or non-transparent connection is used (data call).

TransmissionModeB ::= OCTET STRING (SIZE (1)) -- containing XXRRTTCC with -- XXXX not used -- TT transparency -- CC chosen channel rate -- RR requested channel rate -- Combination Of -- XXXXXX00 = unknown (default) -- XXXXXX01 = fullrate -- XXXXXX10 = halfrate -- XXXX00XX = unknown (default) -- XXXX01XX = transparent -- XXXX10XX = non transparent -- XX00XXXX = unknown (default) -- XX01XXXX = fullrate -- XX10XXXX = dual halfrate preferred -- XX11XXXX = dual fullrate preferred

This parameter indicates:

which channel rate has been requested by the Mobile Station

which channel rate finally has been chosen by the MSC/BSS system

whether a transparent or non-transparent connection is used (data call).

2.3.372 transmittedZone

The transmittedZone is the ChargeBandCallingLine and is received from the SCP during T_CSI dialog.

Note: the parameter is not available if the property SENDTAX is set.

coding a:


TransmittedZoneA ::= INTEGER-- length 1..3-- like a mobile zone

coding b:

TransmittedZoneB ::= OCTET STRING (SIZE(2)) -- 2 bytes, e.g. 1 coded as 0001


2.3.373 usedEmlppPriority

This parameter contains the eMLPP priority as specified by 3GPP. The eMLPP priority is coded as defined in the corresponding specifications /22.067/, /23.067/, /24.008/, /28.008/ and /29.002/. If no eMLPP priority is signalled, the networks default priority will be used.

UsedEmlppPriority ::= OCTET STRING (SIZE (1)) -- coding according 3G TS 22.067, 23.067, 24.008 -- bit 1..3: priority, bit 4..8: unused (0) -- Used-eMLPPPriority Meaning Used for Priority -- H'00 NoPriorityApplied -- H'01 CallPriorityLevel4 subscription lowest -- H'02 CallPriorityLevel3 subscription -- H'03 CallPriorityLevel2 subscription -- H'04 CallPriorityLevel1 subscription -- H'05 CallPriorityLevel0 subscription -- H'06 CallPriorityLevelB network internal use -- H'07 CallPriorityLevelA network internal use highest

This parameter contains the eMLPP priority as specified by 3GPP. The eMLPP priority is coded as defined in the corresponding specifications /22.067/, /23.067/, /24.008/ and /29.002/. If no eMLPP priority is signalled, the networks default priority will be used.

2.3.374 ussdAccessCode

UssdAccessCode ::= OCTET STRING (SIZE (2))

This parameter contains the feature code from the first mobile initiated USSD request.

The feature codes are defined project dependend and are used to trigger a special service in the network.

Note: In case of network initiated USSD request this parameter will be not present.

2.3.375

2.3.376 ussdCodingScheme

UssdCodingScheme ::= OCTET STRING (SIZE (1))

The parameter contains the data coding scheme of the first mobile intiated USSD request

Note: In case of a network initiated USSD request this parameter will be not present.

The parameter will be not present if USSD Phase 1 for mobile initiated USSD request is

used. In case of USSD Phase 1 only the default is given out.

The parameter will be also not present if the data coding scheme of received USSD string


is unknown.

2.3.377 UssdCodingScheme ::= OCTET STRING (SIZE(1))

2.3.378 ussdNotifyCounter

UssdNotifyCounter ::= OCTET STRING (SIZE (1))

The parameter contains the number of successful transmitted Notifications.

These Notifications can be sent from the SCP to request some additional information from the MS. The number of Notifications in the dialog is counted.

The parameter will be present in case of mobile and network initiated requests.

Note: The parameter will be not present if USSD Phase 1 for mobile initiated USSD request is


Please note that for network intiated USSD Request USSD Phase 2 is mandatory.

UssdNotifyCounter ::= OCTET STRING (SIZE(1))

2.3.379 ussdRequestCounter

UssdRequestCounter ::= OCTET STRING (SIZE (1))

The parameter contains the number of successful transmitted Requests.

These Requests can be send from the SCP to request some additional information from the MS. The number of Requests in the dialog is counted.

The parameter will be present in case of mobile and network initiated requests.

Note: The parameter will be not present if USSD Phase 1 for mobile initiated USSD request is


Please note that for network intiated USSD Request USSD Phase 2 is mandatory.

UssdRequestCounter ::= OCTET STRING (SIZE(1))

2.3.380 ussdString

UssdString ::= OCTET STRING (SIZE (1..20))

The parameter contains the leading digits of the first mobile initiated USSD request without

the entered Access Code. The Access Code is present in parameter ussdAccessCode.


Note: In case of a network initiated USSD request this parameter will be not present.

UssdString ::= OCTET STRING (SIZE(1..20))

2.3.381 voiceGroupServiceReference

VoiceGroupServiceReference ::= INTEGER -- range 0 to 134217727 (max. H' 7FF FFFF)


... this

is the

end ...

Documents

Charging Specification CS3.0