Subscriber and Equipment Trace

Subscriber and Equipment Trace

DN99576581Issue 4-0 en

# Nokia Siemens Networks 1 (61)

MSCDOCM14PDFCDMSC/HLR, Rel. M14.0, Product Documentation,v.3

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2008. All rights reserved.

2 (61) # Nokia Siemens Networks DN99576581Issue 4-0 en


Contents

Contents 3

List of tables 4

List of figures 5

Summary of changes 7

1 Subscriber and equipment trace 91.1 Trace invoking events 101.2 Trace activation/deactivation and record generation 121.3 Support of GPRS 221.4 Trace priorities 241.5 Restrictions on trace 251.6 Trace reports 271.7 Trace-related protocols 341.8 Trace-related network elements 371.9 Trace-related files and PRFILE parameters 38

2 Checking the settings for subscriber and equipment trace 432.1 Setting up the output I/O device 432.2 Defining the call phases that produce a report 442.3 Setting up the trace report transfer method and report format 452.4 Setting up trace support in other network elements 45

3 Activating and deactivating subscriber trace in HLR 47

4 Activating and deactivating subscriber, equipment, and EIR list tracein VLR 51

4.1 Activating and deactivating subscriber trace in VLR 524.2 Activating and deactivating equipment trace in VLR 554.3 Activating and deactivating EIR list category trace in VLR 58



Contents

List of tables

Table 1. Phase 2 report heading information fields 27

Table 2. Trace report transfers 30

Table 3. Trace type conversion table for the HLR-MSC/VLR interface (in binaryformat) 35

Table 4. Trace type conversion table for MSC-MSC handover (in binary format) 36



List of figures

Figure 1. Trace of a subscriber or an equipment 12

Figure 2. Core network architecture 19

Figure 3. Trace activation from the HLR to the GPRS network 23

Figure 4. Possible report transfer mechanisms 30

Figure 5. Connection between logical files where trace reports are output by thereport forming services and the physical devices 31

Figure 6. The bit structure of the parameter REPORT_IN_CALL_PHASE 39



List of figures



Summary of changes

Changes between document issues are cumulative. Therefore, the latestdocument issue contains all changes made to previous issues.

Changes made between issues 4-0 and 3-2

Trace can be activated in the HLR separately for the Packet-Switched (PS)and Circuit-Switched (CS) domain, or to both domains with different tracetypes.

With PLMN-based activation control, the operator can control whether toaccept trace activation coming from foreign networks or not. The PLMN-specific parameter file (VICTOR) contains Trace restriction data that storestrace activation restriction for each PLMN.

The output format of the trace report can be defined by theOBS_REPORT_FORMAT (50:0) PRFILE parameter (ASCII, binary, XML,or a combination of the three).

In MSS environment, when two MGWs are used, the MSS sends traceactivation also to the backbone side MGW.


No content changes.


Effects of updated Feature 593: GSM Phase 2 Trace added: informationon offline and online report transfer mechanisms and logical files added.



Summary of changes

Trace activation/deactivation and record generation, section EIR listcategory trace activation in the VLR

The following information has been added: In case of EIR list trace, thetrace type consists of the following values:

. PRIORITY: UNPRIOR also known as off-line transfer method

. Invoking events: all events

. BASIC BSS Record Type

. BASIC MSC Record Type



1 Subscriber and equipment trace

Trace functionality is a maintenance aid and tool which can be used duringsystem testing. In particular, it may be used in conjunction with test mobilestations (MSs) to ascertain the digital cell 'footprint', the network integrity,and also the network quality of service, as perceived by the Public LandMobile Network (PLMN) customers.

The network management can use trace for subscriber observation, forexample, following a customer complaint, or if equipment malfunction issuspected.

Trace enables customer administration and network management to tracethe activities of various entities (IMSIs and IMEIs), which result in eventsoccurring in the PLMN. This function also enables the trace of allinformation that is available to the PLMN concerning the call path used bythe associated entity.

trace includes:

. subscriber trace (trace of IMSI), which can be defined for a certainsubscriber in the HLR or in a specific VLR/SGSN

. equipment trace (trace of IMEI), which can be defined in the VLR/SGSN

. Equipment Identity Register (EIR) list trace, which can be defined inthe VLR

The Home Public Land Mobile Network (HPLMN) operators can use tracein the following ways:

. to trace the operators' own IMSIs in the HPLMN

. to trace the HLR activities of the operators' own IMSIs while they areroaming in a Visited Public Land Mobile Network (VPLMN)



Subscriber and equipment trace

. to trace foreign roaming IMSIs in the HPLMN at their own initiative,or at the request of other PLMN operators

. to activate an equipment trace for any subscriber's equipment (IMEI)

The trace of roaming IMSIs and the exchange of data are subject tobilateral agreements, and the request to trace a particular IMSI comesthrough administrative channels. The HPLMN operator can use the HLRparameters to define whether the trace settings are sent to the VPLMN.

Trace can be activated in the HLR separately for the Packet-Switched (PS)and Circuit-Switched (CS) domain, or to both domains with different tracetypes. This can be set on a subscriber basis.

With PLMN-based trace activation control in the MSC, the operator cancontrol whether to accept trace activation coming from foreign networks ornot. This provides trace activation restriction from different PLMNs.

The way trace is used and organised, including restrictions due to nationallaws and regulations, is the responsibility of the PLMN operator.

1.1 Trace invoking events

The following events in the HLR invoke trace:

. location update

. location update from SGSN

. routing inquiry (SRI) and provide roaming number (subscriber B'snumber fetching procedure)

. routing inquiry (SRI) for LCS

. SS activity (activation/deactivation/registration/erasure/interrogation)

. register password

. SMS: alert service center/Send Routing Info for SMS

. CCBS recall

The report is generated only if the HLR trace type parameter has a valueother than 'no trace'.

The events in the MSC/VLR that invoke trace are:



. call setup, conversation phase, and release within the MSC (MOCand MTC, including attempts)

. use of supplementary services

. location update (normal and periodic)

. SMS-MO and SMS-MT

. IMSI attach and detach

. GPRS detach

. use of location services

. rate change in the case of UMTS CS data call

. handovers

. MGW resource reservation (successful and unsuccessful)

. route selection

When trace activation and deactivation is done from the OMC, it ispossible to create trace cases which have individual trace referencenumbers in the whole HPLMN area.

Trace reference numbers uniquely identify a record or collection of recordsfor one particular trace in conjunction with the IMSI/IMEI. The number canbe an integer between 1 and 65534. However, it is 0 if the case ismalicious call identification or list (black or grey) trace. The trace referencenumber for the emergency call observation is 65535.

The operator's personnel have to take care of providing unique tracereference numbers if subscriber or equipment trace is activated in aparticular network element by means of the local MMI, as they are notchecked in the network elements.

As the amount of information that can be collected for a single call is verylarge, the HLR, VLR, and MGW can limit the number of simultaneoustraces by rejecting the trace requests. For more information, see sectionRestrictions on trace.

Trace records are generated in the managed elements by the trace controlfunction. One trace record is always associated with one invoking event,and during one call a set of trace records may be generated by the HLR,MSC, BSC, RNC, R99 MGW, and MGW. The trace record structure variesdepending on the invoking event, the network element, and the subscriber-specific record type.




1.2 Trace activation/deactivation and recordgeneration

The following figure provides an overview of the trace procedures.

Figure 1. Trace of a subscriber or an equipment

For information on each procedure designated by numbers in the figure,see the detailed descriptions according to the numbers below.

1. Subscriber trace activation/deactivation in the HLR

You can monitor a subscriber in the network by activating trace for thesubscriber events in the HLR. When you place a subscriber underobservation, a report is automatically output when, for example, thesubscriber makes a call or uses supplementary services.

EquipmentVisiting Sub. Home Sub.

MSC ‘B‘MSC ‘A‘

R99 MGW

2. SubscriberTrace Activation

1. Subscriber Trace Activation3. EquipmentTrace Activation

18. Trace Record Generation

5. MAP-ACTIVATE-TRACE MODEMAP-DEACTIVATE-TRACE MODE

9. MAP-PREPARE-HANDOVER 10. MSC_INVOKE_TRACE

16. Trace RecordGeneration



11. CN_INVOKE_TRACE


HLR

BSS

7. CN_INVOKE_TRACE

8. Trace package inADD/MODIFY command6. MSC_INVOKE_

TRACE


MWCcommand

OMC


MSC/VLR MSS/VLR

MTTcommand

4. Subscriber Trace Activation

RNS

MGW

RNS

WETcommand



You can activate and deactivate the subscriber trace for an HPLMN'ssubscriber in the HLR with MML commands, and the trace functionbecomes active immediately. The HLR sends the trace settings to theappropriate MSC/VLR if trace is needed from that MSC/VLR. The trace isset to active state in the PLMN's VLR if the subscriber is active in thenetwork. Otherwise, subscriber trace is activated in the VLR when thesubscriber makes a location update in his VLR area, or by other meansbecomes an active subscriber in the VLR area.

Trace can be activated in the HLR separately for the Packet-Switched (PS)and Circuit-Switched (CS) domain, or to both domains with different tracetypes. This can be set on a subscriber basis. These settings can beadjusted with an MML command and in the HLR database (HOSTEL).

The subscriber's trace status changes when the subscriber roams out of ormoves into the HPLMN area and the trace is activated in the specific VLRarea. It is possible to request the current status of a specific IMSI from theHLR by giving an inquiry command.

The following parameters are provided for the trace activation:

. IMSI/MSISDN

. Trace Reference

. OMC ID

. Trace Type

. HLR Trace Type

The operator allocates each trace case a unique trace reference number,and this reference number is used to identify the collection of records forone particular trace.

Call Forwarding Unconditional (CFU) and Call Forwarding on SubscriberNot Reachable IMSI detach (CFNR-IMSI detach) supplementary servicescan only be traced by setting the trace active in the HLR. The usage ofthese services can only be seen in the HLR observation report.

You can deactivate the subscriber trace by deleting the subscriber's tracesettings in the HLR. The HLR sends a deactivation message to the VLR. Ifthe deleting request from the HLR to the VLR does not succeed, the tracesettings are deleted from the HLR. Then later on, when the subscriberroams out of the previous VLR area into another, the trace settings areforgotten. If the subscriber makes a handover into another MSC/VLR areawhile the call connection is on, the trace settings are sent from MSC-A tothe subsequent MSC-B within a handover procedure.




2. Subscriber trace activation/deactivation in the MSC/VLR

The subscriber trace is activated/deactivated for the HPLMN's own orforeign subscribers.

The trace is activated for a subscriber by giving an MML command to theVLR. The trace becomes immediately active for the registered subscriberentity if there is no higher priority trace set.

If the subscriber is not currently registered, the subscriber trace is put on apending list and activated in the VLR on the subsequent location update. Itis possible to request the current status of the subscriber trace from theVLR by giving an inquiry command.

If subscriber trace is defined in both the HLR and the VLR for the samesubscriber, the trace case defined in the HLR is used. If the equipment isdefined to be traced in the VLR, and the equipment belongs to asubscriber who is traced, the subscriber trace overrules the equipmenttrace. For more information, see sections trace priorities and Restrictionson trace.

The following parameters are provided for the trace activation:

. IMSI/MSISDN

. Trace Reference

. OMC ID

. Trace Type

The subscriber trace can be deactivated by deleting the subscriber's tracesettings in the VLR.

3. Equipment trace activation/deactivation in the MSC/VLR

Equipment trace is activated/deactivated to the VLR by using MMLcommands. If the equipment is used in the VLR area, and no subscribertrace is defined for the subscriber using the equipment, the trace becomesactive immediately. If the subscriber and the equipment are both traced, orthe equipment belongs to a traced EIR list, only one trace case becomesactive in the MSC.

trace reports are generated for the equipment activated to be traced,although no SIM card is used by the subscriber if the call is an emergencycall.



If no one uses the equipment for the moment, the equipment trace is put toa pending list and is activated in the VLR on the subsequent locationupdate. The change in the equipment state of a specific trace case can berequested from the VLR with an MML command.

For more information, see section Trace priorities and Restrictions ontrace.

The following parameters are provided for the equipment trace activation:

. IMEI

. Trace Reference

. OMC ID

. Trace Type

The equipment trace can be deactivated in the VLR by giving a deletecommand.

Subscriber and equipment trace cases can be defined to a certain VLReven if the subscriber or equipment is not active in the VLR area.

Note that IMEI checking needs to be switched on in the MSC when usingequipment trace, otherwise the trace will not work properly and some ofthe traced equipment can be missed.

4. Subscriber trace activation/deactivation to the R99 MGW

The trace is activated locally in the R99 MGW by an MML command. Thetrace is stored in a local file and trace is started when the R99 MGWreceives the BSSMAP COMMON_ID or the HANDOVER_REQUESTmessage from the MSC via the A' interface. The following traceparameters are provided during the activation:

. IMSI

. Trace events (signalling, user plane, both, no trace)

. Code point

Code point is used when user plane trace events are activated. Itdetermines how and when trace information is stored in a cyclicbuffer. The code point (dword) can have values from 0 to FFFFFFFF.




5. Trace activation/deactivation from the HLR to the MSC/VLR

If the subscriber is registered and is roaming in a PLMN area, the HLRinitiates the MAP-ACTIVATE-TRACE-MODE request to the VLR acrossthe MAP-D interface. The MAP-D operation is confirmed from the VLR tothe HLR. Note that the HLR parameters have to allow the sending of theinformation to the VLR in question. The HLR parameters control thesending of the information on PLMN level.

If the subscriber has been roaming in the VPLMN, and then returns to theHPLMN and a location update occurs, the trace becomes active in theVLR due to the MAP ACTIVATE-TRACE-MODE operation. The trace thatis active in the VLR is marked in the HLR database.

If the subscriber is active in the HPLMN, the trace information can be sentfrom the HLR to the VLR in the MAP-ACTIVATE-TRACE-MODE.

The following parameters are provided for the trace activation from theHLR to the MSC/VLR:

. IMSI

. Trace Reference

. OMC ID

. Trace Type

If the subscriber and equipment are both defined to be traced, only thesubscriber trace case becomes active and generates trace reports. If thesubscriber trace is defined in the HLR and locally in the VLR for the samesubscriber, the trace case defined in the HLR is activated.

If the operator deactivates the trace in the HLR, the deactivationinformation is sent in the MAP-DEACTIVATE-TRACE-MODE messagefrom the HLR to the VLR where the subscriber is registered.

The following parameters are provided for the trace deactivation from theHLR to the MSC/VLR:

. IMSI

. Trace Reference

With PLMN-based trace activation control, the operator can controlwhether to accept trace activation coming from foreign networks or not.This provides trace activation restriction from different PLMNs.



6. Trace activation/deactivation to the BSS

The MSC invokes the trace by sending a BSSMAPMSC_INVOKE_TRACE message to the BSS at the beginning of the callconnection or in case of a location update, if the BSS Record Type is set toa value other than 'No BSS Trace' and if the invoking event defined in thetrace type allows it. When the BSS receives this message, it starts trace.The BSS does not send an acknowledgement of the BSSMAP message tothe MSC.

The following parameters are provided in the MSC_INVOKE_TRACEmessage for the trace activation:

. Message Type

. IMSI or IMEI

. Trace Reference

. Trigger ID

. OMC ID

. Trace Type

. Transaction ID

There is no separate trace deactivation to the BSS, trace is deactivatedwhen the connection is released.

7. Trace activation/deactivation to the RNS

The MSS invokes the trace in the RNC by sending the RANAPCN_INVOKE_TRACE message at the beginning of a call or together witha location updat,e when the BSS Record Type is set to a value other than'No BSS Trace' and if the invoking event defined in the trace type allows it.The RNC starts trace when it receives this message.

The following parameters are provided in the CN_INVOKE_TRACEmessage for the trace activation:

. Message Type

. IMSI or IMEI

. Trace Reference

. Trigger ID




. OMC ID

. Trace Type

The trace is deactivated in the RNC from the MSC Server when the Iuconnection is released.

8. Trace activation/deactivation to the MGW

The MSS sends trace activation to the MGW through the MEGACOprotocol in a Nokia-specific package using the ADD or MODIFY commandwhen the termination reservation is requested by the MSS. The ADDcommand adds a termination to a context. The MODIFY commandmodifies the termination parameters. The MSS can resend the traceactivation when the termination is replaced or moved within the context ofthe connection.

The ADD/MODIFY command contains the following trace information:

. IMSI or IMEI

. Trace Reference

. OMC ID

. Trace Type

. Indication (IMSI or IMEI – if trace package version 2 is used)

Note that the maximum number of simultaneous trace cases in one MGWis limited, and if the number of trace cases reaches the limit, the MGWdiscards the trace activation. If trace is active in the MSS, it activates traceto the MGW. The trace is deactivated in the MGW when the termination tobe traced is released.

If version 1 of the trace package is used, the IMSI is sent, and the IMEI isnot. If version 2 of the trace package is used, the command contains anindication whether the IMSI or the IMEI is sent.

The MSS sends a trace activation also to the backbone-side MGW toenable the sending of 3G TFO observation reports from the MGW. Thismeans that when two MGWs are used, the MSS sends a trace activationto both MGWs. As shown in Figure Core network architecture below, theMSS-A activates the trace both to the MGW-A1 and MGW-A2 if the Asubscriber is traced. If the B subscriber is traced, MSS-B activates thetrace to MGW-B1 and MGW-B2.



Figure 2. Core network architecture

9. Trace activation/deactivation in inter-MSC handover

If an inter-MSC handover occurs when the subscriber or the equipment istraced, the MAP-E transfers the trace information to the subsequent MSC.The MAP-TRACE-SUBSCRIBER-ACTIVITY operation is sent from theMSC-A to the subsequent one if the used MAP interface is of phase 1. Ifthe MAP interface is of phase 2, the MAP-PREPARE-HANDOVERoperation includes the MSC_INVOKE_TRACE in the BSS extension partof the operation. The subsequent MSC-B sends an acknowledgment ofthe message to the MSC-A.

The following parameters are provided in the MSC_INVOKE_TRACEmessage for the trace activation:

. Message Type

. IMSI or IMEI

. Trace Reference

. Trigger ID

. OMC ID

For example,ISUP/BICC/SIP-T

PSTN/PLMN

BSS IP MM/IP Trunk

RAN

IP/ATM

For example,ISUP

TDMH.248BSSAP

H.248 H.248

TDM

TDM

H.248TDM

RANAP

IP

SIP/SIP-T

ATM AAL2

TDM

TDM

MSSA MSSB

MGWA1 MGWA2 MGWB1 MGWB2




. Trace Type

. Transaction ID

If the inter-MSC handover happens to be an inter-PLMN handover, theoperator can define that the trace is not transferred to the PLMN where thesubscriber is roaming, that is, to the visited PLMN. The operator can definethe PLMN with its name, address, or index.

10. Trace activation/deactivation from the MSC to the R99 MGW

The MSC always activates the trace in the R99 MGW regardless of thetrace type. Trace activation to the R99 MGW needs local activation beforereceiving the BSSMAP MSC_INVOKE_TRACE message. After localactivation, the R99 MGW starts trace when it receives the BSSMAPMSC_INVOKE_TRACE message from the MSC, which contains thefollowing information:

. Message Type

. IMSI or IMEI

. Trace Reference

. Trigger ID

. OMC ID

. Trace Type

. Transaction ID

11. Trace activation/deactivation from the R99 MGW to the RNC

The R99 MGW can activate the trace to the RNC. When the R99 MGWreceives a BSSMAP MSC_INVOKE_TRACE message, it translates it intoa RANAP CN_INVOKE_TRACE message. The R99 MGW checks thetrace type and it sends the CN_INVOKE_TRACE message only if thetrace type's BSS Record Type has a value other than 'No BSS Trace'. TheCN_INVOKE_TRACE message contains the following information:

. Message Type

. IMSI or IMEI

. Trace Reference

. Trigger ID

. OMC ID

. Trace Type



Trace is deactivated in the RNC when the Iu connection is released.

12., 13., 14., 15., 16., 17., and 18. Trace record generation

The trace records which are generated in the HLR, MSC/VLR, BSC, RNC,and MGW are sent to the OMC either as real time or by file transfer. Thedecision concerning the trace type of the report transfer is definedsubscriber-specifically in the priority indication bit of the trace type.

The following reports are generated based on the trace records:


. MSC observation report

. MSC SMS observation report

. Handover observation report

. Location update observation report


. BSS Trace reports


. MGW Trace reports


. RNS Trace reports





. R99 MGW Trace reports


. HLR subscriber observation report




EIR list category trace activation in the VLR

The black, grey or unknown list category of EIR can be set to be traced.

The list trace is not activated if the subscriber or equipment trace is definedfor the equipment or for a subscriber using the equipment that belongs tothe traced list category. In other words, the subscriber and equipmenttraces overrule the list trace. See section Trace priorities.

In case of EIR list trace, the trace type consists of the following values:

. PRIORITY: UNPRIOR also known as off-line transfer method

. Invoking events: all events

. BASIC BSS Record Type

. BASIC MSC Record Type

The EIR list trace reports are generated in MSC, BSC, RNC, and MGWstatistics. The reports are printed in the logical output files of their own.Each equipment EIR category causes the record to be generated to theEIR category-specific logical output file.

Note

If the trace settings are changed or deactivated during a call, thechanges do not become active during the ongoing call.

1.3 Support of GPRS

The GPRS system brings the packet-switched bearer services to theexisting GSM system. The support for General Packet Radio Service(GPRS) in the HLR includes GPRS subscriber data storage, standardMAP interface to Serving GPRS Support Node (SGSN), and a subscriberdata management interface for GPRS subscriber data.



Figure 3. Trace activation from the HLR to the GPRS network

1. Subscriber trace activation for GPRS subscriber

The subscriber trace is activated and deactivated for a HPLMN'ssubscriber, and the trace function is immediately active in the HLR. Thetrace is set to active state in the HPLMN's SGSN if the subscriber is activein the network. Otherwise, subscriber trace is activated in the SGSN whenthe subscriber roams to the SGSN area. Note that the HLR parametershave to allow the sending of information to the SGSN in question, andthese parameters control the sending of the information on PLMN level. Inthe trace activation operation, the HLR sends the same trace type to theSGSN as it sends to the MSC.

The subscriber's trace status changes when the subscriber roams out of ormoves into the HPLMN area and the trace is activated in the specificSGSN area. It is possible to request the current status of a certain IMSI orMSISDN from the HLR by giving an inquiry command.

1: Trace Activationa) IMSI or MSISDNb) Trace Referencec) OMC IDd) Trace Typee) HLR Trace Type

3: Trace Record Generation

Home Sub.

2: MAP-ACTIVATE-TRACE-MODEa) IMSIb) Trace Referencec) OMC IDd) Trace Type

2: MAP-DEACTIVATE-TRACE-MODEa) IMSIb) Trace Reference

SGSN

HLR

OMCMTTcommand




Trace can be activated in the HLR separately for the Packet-Switched (PS)and Circuit-Switched (CS) domain, or to both domains with different tracetypes. This can be set on a subscriber basis. These settings can beadjusted with an MML command and in the HLR database (HOSTEL).

2. Trace activation from the HLR to the SGSN

When trace is activated for the subscriber, the MAP-ACTIVATE-TRACE-MODE operation is done as part of the 'Update GPRS Location'procedure.

The subscriber trace can be deactivated by deleting the subscriber's tracesettings in the HLR. The HLR sends a deactivation message (MAP-DEACTIVATE-TRACE-MODE operation) to the SGSN. If the deletingrequest from the HLR to the SGSN does not succeed, the trace settingsare deleted from the HLR.

Trace activation or deactivation can be done as standalone operation fromthe HLR to SGSN.

1.4 Trace priorities

If the subscriber trace is defined in the HLR and locally in the VLR for thesame subscriber, the trace parameters in the HLR rule over theparameters in the VLR.

If the subscriber uses traced equipment, or the subscriber trace is definedboth in the HLR and VLR, or the equipment activated for trace belongs tothe EIR category (black, gray, or unknown), only one trace definition canbe activated in the VLR. The trace reports are generated according to thespecific trace settings. The lower priority trace stays in active pendingstate.

When more than one trace case is defined for a subscriber or anequipment (multiple trace cases), the following priorities are used to selectthe trace case to be activated:

1. Subscriber trace in the HLR

If the subscriber trace (IMSI or MSISDN) is activated in the HLR andVLR, the trace settings in the HLR rule over the ones in the VLR.

2. IMSI trace in the VLR



The MSC-specific trace definition for IMSI in the VLR is strongerthan other trace cases defined in the VLR. In other words, the IMSItrace rules over the primary MSISDN, ALS MSISDN, equipmenttrace, and EIR list activated trace.

3. Primary MSISDN trace in the VLR

The MSC-specific trace definition for the primary MSISDN in theVLR rules over the ALS MSISDN, equipment trace, and EIR listactivated trace.

4. ALS MSISDN trace in the VLR

The MSC-specific trace definition for the ALS MSISDN in the VLRrules over equipment trace and EIR activated trace.

5. Equipment trace in the VLR

The subscriber and equipment traces are stronger than the traceresulting from the black, gray or unknown list of EIR category.

6. EIR-list trace in the VLR

Trace resulting from the black, gray, or unknown list of EIR categoryis activated only if no equipment or subscriber trace is defined for theequipment or the subscriber who uses the equipment.

1.5 Restrictions on trace

As the amount of information that can be collected for a single call is verylarge, the HLR and VLR can limit the number of simultaneous traces byrejecting the trace request.

Trace limitations in the HLR

The maximum number of traced subscribers in the HLR is 800.

Trace limitations in the VLR

The number of trace cases that can be defined locally in one VLR is 200,including both the active and pending trace cases.

The number of subscriber and equipment trace cases which can besimultaneously active in one VLR is limited to 200. This number includesall active trace cases in one VLR (both the ones originally defined in theVLR and the ones defined in the HLR).




Each VLRU pair counts its share of the total number of active trace casesin the VLR. For instance, if there are 5 VLRU pairs, the active trace limit foreach pair is 40.

There are no limitations for EIR list trace cases as these are not stored inthe subscriber database.

Trace limitations in the R99 MGW

The number of trace connections at the same time can be any numberbetween 0 and 1000. The default value is set to 50.

The number of traced events is limited to a maximum of 50.

Trace limitations in the MGW

Each computer unit (ISU) can have a maximum number of 20 active tracecases in an MGW. This means that there can be up to 200 trace cases inone physical MGW, as each MGW can contain a maximum of 10 ISUs.

Trace capacity considerations

The production of observation reports causes substantial load to the MSC.It is assumed that an average subscriber makes only a few calls per day.Setting stricter limits is recommended if the traced subscribers areexpected to make a lot of calls roughly at the same time. In the case of EIRlist trace, it is also very important to bear in mind that these trace casescan create a substantial load, thus they can cause capacity problems inthe system. For information on capacity problems with traffic observationssee section Traffic observations in NSS Statistics.

As trace generates a very large amount of information, the chosen reporttransfer method should also be considered. If the chosen report transfermechanism is on-line from the HLR or MSC to the OMC for too many tracecases, the Q3 interface can be overloaded. Thus, the recommended reporttransfer mechanism is off-line. The trace cases which need real timetransfer have priority indication set, and reports are sent to the OMC on-line.

Note

XML reports are larger in size than binary reports. However,compression is possible.



The traceReport event sending of the Q3 interface shares the interfaceresources with alarm report events of the HLR and MSC/VLR. In someoccasions when several alarms are generated simultaneously, there maybe some delay and overflow in the Q3 OMU buffer. The Q3 transfercapacity depends on the capacity of the used OMC connection.

The maximum capacity in the MGW is 20 trace cases/ISU. However, theoperator can adjust this number between 0 and 20 by using theMGW_TRACE_MAX PRFILE parameter. For more information, seesection Trace-related files and PRFILE parameters.

If CEIR is used and EIR list trace is activated, and there is a large numberof entries in the grey, black, or unknown list, it can cause a big load to theMSC, as the number of trace reports can be huge.

If the operator uses the CEIR to download the black and grey list IMEIs,and meanwhile the black and grey lists are set to be traced in his network,this can cause a significant load to the system as the number of entries inthose lists can be large.

1.6 Trace reports

Trace report format

Trace records are generated in the managed elements by the trace controlfunction. One trace record is always associated with one invoking event,and during one call a set of trace records may be generated by the MSS,HLR, BSC, RNC, MGW, R99 MGW, SGSN, and GGSN. The trace recordstructure varies depending on the invoking event, the network element,and the subscriber-specific record type.

All phase 2 reports, in accordance with the GSM 12.08 specification, havea similar heading to make the identification of a trace case easier.

The heading information may contain the following fields:

Table 1. Phase 2 report heading information fields

Field Explanation

REPORTING TIME The time when the report request was received by the statisticalreporting program.

REPORT NUMBER A report-type-specific consecutive number.




Table 1. Phase 2 report heading information fields (cont.)

Field Explanation

TRACED IMSI or TRACED IMEI The international mobile subscriber identity or the internationalmobile equipment identity of the party traced. Note that in theHLR only the IMSI can be traced.

TRACE REFERENCE The trace identifier that you gave in the trace activation MML.

OMC ID The ISDN address of the operation and maintenance centre.This is not currently used by the HLR or MSC/VLR but it can beused at the OMC to identify the OMC that set the trace.

TRACE TYPE Determines what event occurrences are requested to invoke thetrace report generating function in a network element.

TRACE TYPE USED Determines what event occurrences are provided in a networkelement to invoke the trace report generating function.

START TIME The time when the compilation of the trace record was started.The start time always appears in the record header.

END TIME The time when the statistics generated the last trace record ofthe invoking event. The end time always appears in the lastrecord header.

RECORDING ENTITY The E.164 number of the network element that generates thereport.

REPORT REASON Corresponds to the 'Reason for Record' field of the trace recordheader and specifies why the record was generated by thenetwork element. The report reason is fixed to EVENT. Thenetwork element generates a trace record every time a particularrecordable event occurs.

INVOKING EVENT Specifies the event that invoked the trace in the networkelement.

For the description of the report format for the following reports, see NSSStatistics, Reports.

. HLR subscriber observation report


. MSC SMS observation report


. Location update observation report



Trace report transfer

The trace records which are generated in the HLR, MSC/VLR, and BSSare sent to the OMC either as on-line notifications or by using off-line bulktransfer if OSI protocol stack is used. The decision about which of the tracereport transfer possibilities is used is defined subscriber-specifically in thetrace type's priority indication bit (for more information on the trace typecomponents, see ETSI Specification 12.08: Subscriber and EquipmentTrace). The trace type's priority indication bit is set with the MTT commandin the HLR, and the parameters are <priority of trace in HLR> (HPRI) and<priority of trace in MSC and BSS> (MPRI). In the MSC the parameter is<priority of trace in MSC and BSS> (PRI), and the priority indication bit isset with the MWC command.

The other way of transferring trace reports from the HLR and the MSC/VLR is using XML over HTTP. In this case, the format of the trace reports isin XML and FTP is used as transfer protocol. When the file which containsthe trace reports is ready for transfer, an XML notification is sent overHTTP to Nokia NetAct.

There are two ways of handling the transfer:

. off-line or FTP report transfer: the trace results are stored on a localdisk in the HLR and MSC/VLR, and the full report files aretransferred to the OMC off-line or using FTP. When the file is readyfor transfer, an XML notification is sent to the OMC over HTTP. Thereports transferred off-line are in binary format, or in XML format fromM12 level. See section Logical files for trace reports.

. On-line report transfer mode: the trace results are sent to the OMCas soon as the trace report is generated by using an on-line eventcalled 'traceRecord', or they are sent as XML notification usingHTTP. This trace report format is Nokia-specific. The XML format isNokia-specific as well.

The PRFILE parameter TRACE_TRANSFER_MODE (002:386) and thepriority field of the TRACE TYPE together control whether the trace reportsare transferred in on-line or off-line mode. In an on-line transfer the binaryreports are sent through the Q3 interface on-line, or the XML reports aresent by FTP in the same way as in off-line reporting. However, the reportsare directed to their own logical files and the file is closed immediately afterthe report is made. In off-line reporting the reports are sent to the OMC off-line or using FTP. The parameter is read once a minute.

The report transfer mode is controlled by the priority parameter of the MTTand MWC commands (in the HLR and VLR, respectively) and theTRACE_TRANSFER_MODE (2:386) PRFILE parameter. The table belowillustrates the possible transfer cases:




Table 2. Trace report transfers

TRACE_TRANSFER_MODE TRACE TYPE PRIORITYPARAMETER=Y

TRACE TYPEPRIORITYPARAMETER=N

0 no transfer no transfer

1 on-line transfer on-line transfer

2 off-line transfer off-line transfer

3 on-line transfer off-line transfer

The recommended report transfer mode is off-line/FTP. For moreinformation, see section Trace capacity considerations.

The following figure shows the possible trace report transfer mechanisms:

Figure 4. Possible report transfer mechanisms

Report format can be XML,ASCII or M11-level binary

M11-levelbinary reports

are sentover Q3

Defined byTRACE_TRANSFER_MODE

PRFILE parameter +trace_type

Depends onwhere you directed

the logical file

YES NO

Binary

XML XMLBinary

ASCII

Reportformat?

Defined byTRACE_TRANSFER_

MODE PRFILEparameter +trace_type

YES

NO

ONLINEreporting?

OSI

XML reportsare sent byFTAM andthe reportsare directedinto separatelogical files

M11-levelbinary reports

are sentby FTAM

ASCII reportsare sentby FTAM

XML reportsare sentby FTAM

Reportformat?

XMLreports aresent over

HTTP. OnlyXML reportsare directedinto separatelogical files.

XML, ASCII orbinary reports

are sentover FTP

IPInterface toNetAct?

Report format is XML, ASCII orM11-level binary

ONLINEreporting?



The output format(s) of the trace report can be defined by theOBS_REPORT_FORMATS (050:0000) PRFILE parameter. The followingformats can be defined in every possible combination of one, two, or threeof them:

. ASCII

. binary

. XML

The figure below describes the connection between the logical files wherethe trace reports are output by the report forming service and the physicaldevices. For the on-line XML report transfer a new logical file and a newphysical device name is introduced. If on-line transfer is used for XMLreports, the reports are output to their own logical file, which is immediatelyclosed after the report is written to the file. After the file is closed, anotification is sent to Nokia NetAct indicating that the file can betransferred. The transfer method is the same as for off-line reporting.However, in the case of on-line transfer, the reports can be transmitted toNokia NetAct as soon as the event has happened.

Figure 5. Connection between logical files where trace reports are output bythe report forming services and the physical devices

Nokia NetActQ3 (CMIS)Binary reports online

GSMME1MXO

OBXOFL

VDS-4

Online XML reports

GSMME1MX

OBXFIL

VDS-2

Offline XML reports

GSMME1MG

OBSFIL

VDS-0

Offline binary reports

Files fetched byFTAM/FTP




The MGW trace records are sent to NEMU which converts binary tracedata to CORBA structure (XML) and sends the report to NetAct by usingNWI3 notification. NetAct sends a DATA RECEIVED OKacknowledgement when the trace record is received. After this message,the NEMU removes the records from its trace buffer. If the NEMU does notreceive the DATA RECEIVED OK acknowledgement from NetAct in time(that is, NEMU’s timer expires), the trace record is sent again.

If the NWI3 interface is broken between NEMU and Nokia's NetAct NMSproduct, all trace reports are lost after the trace report sending buffer in theNEMU becomes full. However, the MGW reports can be viewed in NEMUwith NEMU trace viewer.

For more information on the related PRFILE parameters, see sectionTrace-related files and PRFILE parameters.

If there are problems with the trace report transfer to the OMC, seeinstructions and descriptions on OSI services.

Note

Priority parameters are not used in the MGW. There is only one type ofreport transfer from the MGW (in CORBA structure using NWI3notification).

Logical files for trace reports

With logical files and connections, you can define the devices to whichoutputs are directed from the DX 200 system. Change the connectionswith MML commands. Application programs output data to logical files thatcan be connected to the desired targets, which can be logical files or I/Odevices. When the system is delivered, it has a default I/O deviceconfiguration which is defined by the device supplier. You can use logicalfiles to direct, copy, and back up outputs of the exchange and of theoperation and maintenance network. Outputs include, for example, alarms,reports, and charging data.

The logical output files of the reports on HLR subscriber observation are:

. GSMME1PR: ASCII reports

. GSMME1MG: binary reports

. GSMME1MX: XML reports for off-line transfer



. GSMME1MXO: XML reports for on-line transfer

. GSMME1MXM: XML reports for XML printer

The logical output files related to the MSC/VLR are:

. GSMME1PR: subscriber and equipment trace ASCII reports

. GSMME1MG: subscriber and equipment trace binary reports

. GSMME1MX: subscriber and equipment trace XML reports for off-line transfer

. GSMME1MXO: subscriber and equipment trace XML reports for on-line transfer

. GSMME1MM: XML printer's file for subscriber and equipment tracein MSC/VLR

. OBSEIRGA: EIR gray list trace ASCII reports EIR(G)

. OBSEIRGB: EIR gray list trace binary reports EIR(G)

. OBSEIRGX: EIR gray list trace XML reports EIR(G) for off-linetransfer

. OBSEIRGXO: the EIR gray list trace XML reports EIR(G) for on-linetransfer

. OBSEIRGXM: XML printer's file for EIR(G) gray list trace

. OBSEIRBA: EIR black list trace ASCII reports EIR(B)

. OBSEIRBB: EIR black list trace binary reports EIR(B)

. OBSEIRBX: EIR black list trace XML reports EIR(B) for off-linetransfer

. OBSEIRBXO: the EIR black list trace XML reports EIR(B) for on-linetransfer

. OBSEIRBXM: XML printer's file for EIR(B) black list trace

. OBSEIRUA: EIR unknown list trace ASCII reports EIR(U)

. OBSEIRUB: EIR unknown list trace binary reports EIR(U)

. OBSEIRUX: EIR unknown list trace XML reports EIR(U) for off-linetransfer

. OBSEIRUXO: the EIR unknown list trace XML reports EIR(U)reports for on-line transfer

. OBSEIRUXM: XML printer's file for EIR(U) unknown list trace




. TSTCOBSA: test call observation ASCII reports

. TSTCOBSB: test call observation binary reports

. TSTCOBSX: test call observation XML reports

Logical files have one to four connections to I/O devices or to other logicalfiles. Logical files can also be connected to a byte basket, which meansthat the outputs are not directed anywhere. For more information on logicalfiles, see the instructions and descriptions on I/O system.

The manufacturer has defined initial settings for connections betweenlogical files and devices. You can change these settings. To interrogateexisting connections, use the IID and IIL commands of the I/OConfiguration Handling (II) command group.

There are some other measurements that produce reports to the samelogical files. The binary reports of the traffic observation (numberdestination observation, clear code observation, circuit observation, andthe statistical observation) are directed to the logical file GSMME1MG.However, this is not the case in XML: only trace reports are directed to theGSMME1MX logical file.

For more information on transferring logical files, see section Integratingthe MSC/MSS, CDS, and the HLR with Nokia NetAct in NSS Statistics.

1.7 Trace-related protocols

BSSAP

A trace is invoked in the BSS by sending a BSSMAP MSC-INVOKE-TRACE message from the MSC to the BSS at the beginning of the call, inconnection with a handover, or when a location update occurs. The MSCsends an MSC-INVOKE-TRACE message to the BSS if the BSSAPversion in question supports trace. When the BSC receives this message,the BSC statistics starts trace.

The trace invocation command is not sent to the BSC if the BSSAPversion does not support trace. The MSC has a list of all network elementsconnected to the A-interface. The list has a parameter that specifieswhether the BSSAP version supports trace. The BSS-specific tracefeature support parameters can be interrogated with the IED command.

In the case of intra-BSC handovers, in a successful case the BSC notifiesthe MSC with the HANDOVER_PERFORMED operation message and theBSSAP service block sends the handover occurrence to statistics.



In the case of inter-BSC handovers, in a successful case the BSSAPservice block receives the HANDOVER_COMPLETE operation messagefrom the target BSC, the MSC gives the CLEAR command, and theBSSAP service block sends a message to statistics.

MAP - D

If the MSC and VLR receive a 'trace activate map operation' of GSM phase1 from the HLR (because HLR supports only MAP v1), the trace typeparameter is in the phase 1 format, and the MAP-D interface programshave to convert the trace type to GSM phase 2 trace type format.

If the HLR or the MSC/VLR supports MAP v1, the following conversionfrom/to phase 1 trace type values are used:

Table 3. Trace type conversion table for the HLR-MSC/VLR interface (inbinary format)

Trace type (phase 1) Trace type (phase 2) Description

0000 0000 => 0000 0000 all

0000 0001 => 0000 0001 only calls

1000 0000 => 0000 0011 OLCM rec (operator-defined value)

1000 0001 => 0000 0111 OLCM rec rep (operator-defined)

MAP - E

If the subsequent MSC supports the phase 2 trace, the trace data is sent tothe MSC-B in a MAP-PREPARE-HANDOVER operation in a BSS_APDUparameter. The BSS_APDU parameter contains the trace controlattributes of MSC_INVOKE_TRACE (the same that is used in the A-interface).

If the subsequent MSC supports MAP v1, the trace data is sent to theMSC-B in a MAP-TRACE-SUBSCRIBER-ACTIVITY operation.

The trace type conversion table for the MSC-A in an MSC-MSC handoverMAP-TRACE-SUBSCRIBER-ACTIVITY operation is presented below:




Table 4. Trace type conversion table for MSC-MSC handover (in binaryformat)

Trace type (phase 2) Trace type (phase1)

Description

X000 0000 => 0000 0000 all

X000 0001 => 0000 0001 only calls

X000 0010 => 0000 0000 LU and IMSI attach/detach (in phase 2)**

X0YY YY11 => not supported operator-specific types

X bit can be set to 1 or to 0.

** The LU and IMSI attach/detach events of phase 2 are included in all events of phase 1 trace type.

MEGACO

The MSC Server (MSS) can invoke the trace to the MGW through theMEGACO protocol by including the Nokia proprietary trace package intothe ADD or the MODIFY command if the MGW in question supports thetrace package. The MGW informs the MSS if the trace activation hasfailed.

RANAP

A trace is invoked in the RNS by sending a RANAP CN_INVOKE_TRACEmessage from the MSS or from the R99 MGW to the RNS at the beginningof the call. The MSS sends a CN_INVOKE_TRACE message to the RNConly if the trace type's BSS record type has a value other than 'No BSSTrace'. When the RNC receives the RANAP CN_INVOKE_TRACEmessage, it can start trace the connection. Note that the CS core networkdoes not send a CN_DEACTIVATE_TRACE RANAP message to theRNC. The trace is deactivated in the RNS when the call is released.

Q3

The trace reports generated by the HLR and the MSC can be transferredon-line.

XML over HTTP/FTP

The trace reports generated by the HLR, MSC, or MSS can be transferredto the OSS with FTP. The notification which indicates that the file is readyis sent over HTTP. The reports are in XML format. For more information,see the feature description of Feature 1275: New IP Interfaces for O&M.

For more information, see section Trace report transfer.



1.8 Trace-related network elements

Base Station Controller (BSC)

Trace can be set into the BSC in connection with call setup, locationupdate, and inter-BSC handover (see 1.7.1 BSSAP).

Operations and Maintenance Centre (OMC)

The observation reports generated in the HLR, MSC/VLR, and BSS aresent to the OSS either as on-line notifications or by using off-line bulktransfer in case of OSI protocol stack. In case of O&M IP interfaces, FTP isused for file transfer, and the trace reports are sent in XML format, exceptthose coming from the BSS (see the feature description of Feature 1275:New IP Interfaces for O&M). See sections Trace report transfer and Trace-related files and PRFILE parameters for more information.

Reports from the MGW are sent in CORBA structure using NWI3notification.

Serving General Packet Radio Service Support Node (SGSN)

In the trace activation operation, the HLR sends the same trace type to theSGSN as it sends to the MSC. The HLR includes the OMC ID to the traceactivation operation. See section Trace activation from the HLR to theGPRS network for details.

Radio Network Controller (RNC)

Trace can be set in the RNC in connection with call setup, location update,and handover (see 1.7.1 RANAP).

R99 Multimedia Gateway (R99 MGW)

MGW always gets the BSSMAP MSC_INVOKE_TRACE message fromthe MSC and it translates this message to CN_INVOKE_TRACEmessage, which is then sent to the RNC if the BSS record type has a valueother than 'No BSS trace'. In the case of RNC relocation, the MGWtranslates all RANAP messages to BSSMAP messages and vice versa.

Multimedia Gateway (MGW)

Trace can be set by the MSS in the Multimedia Gateway in connection withcall set-up, see section MEGACO for more information.




1.9 Trace-related files and PRFILE parameters

Files containing trace information

In the HLR, the Home Subscriber Database (HOSTEL) contains thefollowing trace information:

. IMSI

. trace activated in VLR

. trace activated in SGSN

. trace reference

. MSC & BSS trace type

. HLR trace type

. OMC identifier

. SGSN trace type

In the VLR, the Visiting Subscriber Data File (VISION) contains the activetrace data:

. IMSI/IMEI

. trace reference

. MSC & BSS trace type

. OMC identifier

In the VLR, the PLMN-specific Parameter File (VICTOR) contains thefollowing data that stores the trace activation restriction for each PLMN:

. Trace restriction

PRFILE parameters used in trace

The General Parameter File (PRFILE) contains the following parameterswhich are used in subscriber and equipment trace:

. TRACE_TRANSFER_MODE (parameter 002:0386) controls whattrace report models can be supported in the network element. Withthis parameter, you can define what trace type priority values aresupported.

The parameter can have the following values:



Value Explanation

0 Trace reports are not transferred.

1 on-line transfer: trace reports are transferred immediately after the event. Theycan be transferred by FTP using Feature 1275: New IP Interfaces for O&M, orthrough the Q3 interface using Feature 715: Application for CMIS: Event BasedReport Transfer.

2 off-line transfer: trace reports are collected in the network element, and after acertain time they are transferred to the OMC off-line or using FTP.

3 Both: trace reports are transferred according to the method stated by thepriority in the trace type. on-line or off-line can be used.

. REPORT_IN_CALL_PHASE (parameter 009:0036) defines in whichphase of a call the report is output. The default value is 3FH (binary0000 00111111). The allowed values are 0...1FFH. This parameter isused to control subscriber and equipment trace.

The following figure shows the structure of theREPORT_IN_CALL_PHASE PRFILE parameter.

Figure 6. The bit structure of the parameter REPORT_IN_CALL_PHASE

The CALL SETUP bit indicates the setup phase of the A subscriber.

The OUTGOING CIRCUIT SEIZED bit indicates the setup phase ofthe B subscriber.

The B ANSWERS bit indicates the conversation phase.

The RELEASE bit indicates the release phase of the call.

1 1 1 1 1 1 1 111

CALL SETUPOUTGOING CIRCUIT SEIZEDB ANSWERSRELEASE (CHARGING ENDS)INTERRUPT (in setup, circuit seizure or speech)SERVICE USAGEHANDOVERINTERMEDIATE CHARGINGFRAUDCAMELRATE CHANGEMGW SELECTIONROUTE SELECTION

111




The INTERRUPT bit indicates that the call is interrupted.

If the SERVICE USAGE and the CAMEL bits are not set to 1, onlycalls are traced. The TRACE TYPE USED invoking event is CALLSONLY if the requested TRACE TYPE invoking event is ALL (allrecordable events).

The HANDOVER bit indicates that a handover has happened.

Reports about intermediate charging are made only if a subscriber istraced and the INTERMEDIATE CHARGING bit is set.

If the FRAUD bit is set to 1, a subscriber is traced, and the fraudulentcall duration or the maximum number of simultaneous call transfersis exceeded, an additional MSC observation report indicating fraudis generated.

If the CAMEL bit is set, an MSC observation report is generatedabout the CAMEL modification flags, if statistics receives it from thegsmSCF. This bit can also be used to control the report generationfrom CPH.

If the RATE RANGE bit is set, there is an ongoing UMTS CS datacall, and there is a rate change during the call, an additional tracereport is generated.

If the MGW SELECTION bit is set and there is a call where the userplane is connected to the MGW, a report is printed for the resourcereservation attempt in the MGW (both successful and unsuccessfulones for the incoming and outgoing direction). The MGWSELECTION report can show whether the trace activation to theMGW was successful or not.

If the ROUTE SELECTION bit is set, a report about the routeselection is triggered when the call reaches alerting phase, it isinterrupted, or a new destination is choosen.

. MAX_TRACE_FILE_SIZE (parameter 011:0012) defines themaximum size of the physical file connected to the logical file wherethe trace notifications are stored in RANAP Trace. Using thisparameter, you can modify the size of a physical trace file. The valuerange is 10 to 5120 Kb. The default value is 1024 Kb.



. MGW_TRACE_MAX (parameter 012:0109) controls the amount ofactivated trace events in the MGW. The operator can limit themaximum number of active trace events with this parameter toreduce the capacity need. The parameter has computer unit (ISU)-based limitation. Thus, the complete limitation of trace events in theMGW is multiplied by the number of ISUs.

. OBS_REPORT_FORMATS (parameter 050:0000) defines theoutput format of trace reports. The format can be ASCII, binary, orXML, or every possible combination of two or three of them.






2 Checking the settings for subscriber andequipment trace

Before you activate subscriber and equipment trace, check and set up theoutput I/O device for the trace reports, define the call phases that producea report, set up the report transfer method, and in VLR trace cases, checkthat the BSC and the subsequent MSC support trace.

2.1 Setting up the output I/O device

Steps

1. Check the output I/O device (IID)

Check the I/O device where the reports are output in each networkelement.

The logical files for subscriber and equipment trace reports are:. GSMME1PR: ASCII reports. GSMME1MG: binary reports. GSMME1MX: XML reports for off-line transfer. GSMME1MXO: XML reports for on-line transfer

The logical files for EIR list category trace are the following:. OBSEIRGA: EIR grey list trace ASCII reports. OBSEIRGB: EIR grey list trace binary reports. OBSEIRGX: EIR gray list trace XML reports for off-line transfer. OBSEIRBXO: EIR gray list trace XML reports for on-line

transfer. OBSEIRBA: EIR black list trace ASCII reports. OBSEIRBB: EIR black list trace binary reports. OBSEIRBX: EIR black list trace XML reports for off-line

transfer



Checking the settings for subscriber and equipment trace

. OBSEIRBXO: EIR black list trace XML reports for on-linetransfer

. OBSEIRUA: EIR unknown list trace ASCII reports

. OBSEIRUB: EIR unknown list trace binary reports

. OBSEIRUX: EIR unknown list trace XML reports for off-linetransfer

. OBSEIRUXO: EIR unknown list trace XML reports for on-linetransfer

ZIID::<logical file name>;

2. Change the output I/O device if necessary (IIS)

You only need to define the I/O devices once in each networkelement for the trace functions.

ZIIS::<logical file name>:DEV=<current I/O device>:DEV=<new I/O device>;

2.2 Defining the call phases that produce a report

For more information, see section PRFILE parameters used in trace.

Steps

1. Check PRFILE parameter 9:36 (WOI)

Check PRFILE parameter 9:36. This parameter defines the callphases that produce a report.

ZWOI:9;

2. Change the parameter value (WOC)

Change the value of the parameter so that a report is produced whenrequired.

You only need to define this parameter once in each networkelement for the trace functions.

ZWOC:9,36,<parameter value>;



2.3 Setting up the trace report transfer method andreport format

For more information, see section PRFILE parameters used in trace.

Steps

1. Check PRFILE parameters 2:386 and 50:0 (WOI)

Check PRFILE parameter 2:386 to see the transfer method for tracereports.

ZWOI:2,386;

Check PRFILE parameter 50:0 to see the trace report format.

ZWOI:50,0;

2. Change the parameter values (WOC)

Change the value of parameter 2:386 to allow transfer of the reportson-line or off-line according to the parameter.


Change the value of parameter 50:0 to change the trace reportformat.


2.4 Setting up trace support in other network elements

Steps

1. Check if the BSC supports trace (EDB)

Check if the BSC supports trace in case you want to set the <BSStrace record type> parameter to a value other than 'no BSS trace'.

ZEDB:NAME=<BSC name>:<information group>;

2. Change the BSS parameter to support trace (EDT)



Checking the settings for subscriber and equipment trace

Change the BSS parameter to support trace if trace reports are to begenerated in the BSC.

You only need to define this parameter once in every MSC/VLR forthe trace functions.

ZEDT:VER=<BSSAP version>:<parameter type>,<parameter index>,<parameter value>;

3. Check if the subsequent MSC supports trace (EIO)

Check if the subsequent MSC supports trace in inter-MSC handover.

ZEIO:<location area code>;

4. Change the location area parameters (EIM)

Change the location area parameters so that in inter-MSC handoverthe subsequent MSC supports trace.

You only need to define this parameter once in every MSC/VLR forthe trace functions.

ZEIM:<location area code>:TRA=<call trace allowed>;



3 Activating and deactivating subscribertrace in HLR

Use the trace in the HLR to trace home subscribers.

Trace activated in the HLR overrides the trace activated in the VLR.

. Use the MTT command to activate trace for a single subscriber. Thiscommand cannot be used to modify trace settings.

. If you need to modify the trace settings of an existing trace case, firstdeactivate the trace case with the trace deactivation command MTU,using either IMSI or one of the subscriber's MSISDN numbers. Thenactivate trace again using new trace settings.

. To display trace-activated subscribers in HLR, use the MTIcommand.

. To interrogate the trace settings of subscribers in HLR, use the MTOcommand.

For background information, see section Subscriber and equipment trace.

Note

If you want the trace to be active in a certain PLMN, you can check thePLMN's information with the MJP command (Output PLMN Record) tomake sure that neither TRACE nor TSGSN are listed as values for the<not allowed supplementary service> parameter. You can delete thesewith the MJT command (Delete Not Allowed Service Code) of the HLRand PLMN Parameter Handling (MJ) command group.

Trace can be activated in the HLR separately for the Packet-Switched(PS) and Circuit-Switched (CS) domain, or to both domains withdifferent trace types. This can be set on a subscriber basis.



Activating and deactivating subscriber trace in HLR

Before you start

For instructions, see section Setting up the output I/O device.

Steps

1. Set up the report transfer method

See section Setting up the trace report transfer method.

2. Activate subscriber trace (MTT)

Activate trace for a single subscriber:

ZMTT:IMSI=<international mobile subscriberidentity>:REF=<trace reference>,HTYPE=<HLR tracerecord type>,HPRI=<priority of trace in HLR>,MEVENT=<trace invoking event in MSC and BSS>,MTYPE=<MSC trace record type>,BTYPE=<BSS trace recordtype>,MPRI=<priority of trace in MSC and BSS>,SEVENT=<trace invoking event in SGSN and BSS>,STYPE=<SGSN trace record type>,GTYPE=<BSS tracerecord type in SGSN>,SPRI=<priority of trace in SGSNand BSS>;

Further information

Example Activating subscriber trace in the HLR

1. Check the I/O device where the reports are output in each MSC/VLRand the HLR in question.

ZIID::GSMME1PR;

ZIID::GSMME1MG;

2. Change the I/O device where the reports are output. The current I/Odevice is virtual display unit. Change the ASCII reports to be outputon the line printer, and the binary reports on the WDU.

ZIIS::GSMME1PR:DEV=VDU-0:DEV=LPT-0;

ZIIS::GSMME1MG:DEV=VDU-0:DEV=WDU-0;

3. Check the PRFILE parameters 2:386 and 50:0.

ZWOI:2,386;

ZWOI:50,0;



4. Change the value of the PRFILE parameter 2:386 to allow transfer ofthe reports on-line or off-line according to the parameter <priority oftrace in HLR>.

ZWOC:2,386,3;

5. Change the value of the PRFILE parameter 50:0 to define the outputformat of trace reports (ASCII and XML in this example):

ZWOC:50,0,5;

6. Check the trace settings with the MTO command in the HLR. If youneed to modify an existing trace case, first you have to firstdeactivate the case with the MTU command. Then you can modifythe settings with the MTT command.

Activate trace for a subscriber.. In the CS domain, use the following values:

. the subscriber's IMSI is 244051112345

. trace reference is 100

. the HLR trace record type is BASIC record type

. the HLR trace records are transferred to the OMC off-line

. the trace invoking event in the MSC and the BSS isCALL

. the MSC trace record type is basic record type

. the BSS trace record type is no BSS trace

. trace records are transferred to the OMC on-line

ZMTT:IMSI=244051112345:REF=100,MEVENT=CALL,BTYPE=N,MPRI=Y;

. In the PS domain, use the following values:. the subscriber's IMSI is 244051112345. trace reference is 101. trace invoking event in SGSN and BSS is ALL. SGSN trace record type is BASIC. BSS trace record type in SGSN is BASIC. priority of trace in SGSN and BSS is unprior

ZMTT:IMSI=244051112345:REF=101;



Activating and deactivating subscriber trace in HLR



4 Activating and deactivating subscriber,equipment, and EIR list trace in VLR

You can activate trace of a subscriber in the VLR instead of activating it inthe HLR.

The trace is effective only in the VLR where it has been activated. If youwant a subscriber to be traced in the whole network, activate trace in theHLR. The trace activated in the HLR overrides the trace activated in theVLR.

Note

You are recommended to activate trace for home subscribers in theHLR and for visiting subscribers in the VLR.

You can activate trace in the HLR, in which case the HLR sends the tracesettings to the appropriate MSC. You must activate trace in all the MSC/VLRs where the reports are requested from.

When you place a subscriber under trace, a report is output automaticallywhen the subscriber, for example, makes a call or uses supplementaryservices.

You can activate trace of a mobile equipment in the VLR. When theequipment is used, a report is output automatically.

The trace settings activated with the MWC command are permanentlystored in the VLR. The trace becomes active immediately if the subscriberor mobile equipment to be traced is registered in the VLR. If the subscriberor mobile equipment is not registered in the VLR at the moment, the tracecase is set in the active pending state. This means that the trace settingsare kept in the VLR waiting for the subscriber or mobile equipment toregister.



Activating and deactivating subscriber, equipment, and EIR list tracein VLR

If you activate trace and would like to prevent that in case of an inter-PLMNhandover the trace is transferred to the visited PLMN, you can use the MJScommand to define this setting.

With PLMN-based trace activation control in the MSC, the operator cancontrol whether to accept trace activation coming from foreign networks ornot. This provides trace activation restriction from different PLMNs.

If you want to make sure that equipment trace works properly and notraced equipment is missed, you need to switch on IMEI checking with theMXN command.

For background information, see section Subscriber and equipment trace.

4.1 Activating and deactivating subscriber trace in VLR

Activate subscriber trace in VLR with the MWC command. To display trace-activated subscribers and equipment in the VLR, use the MWL command.

To check the trace settings of an individual subscriber, use the MWIcommand. The command displays both the locally activated trace casesand the subscriber trace cases activated in the HLR. The tracedsubscriber is identified with IMSI, MSISDN, or Alternate Line ServiceMSISDN number (if available).

To deactivate subscriber trace in VLR, use the MWE command. Use theIMSI of the subscriber whose trace you want to deactivate. Trace isstopped only in the VLR where the deactivation is performed. If you needto deactivate a trace case in several MSC/VLRs, you must do it separatelyin each of them.

Before you start

See section Setting up the output I/O device.

Steps

1. Define the call phases that produce a report

See section Defining the call phases that produce a report.

2. Set up the trace report transfer method




Note

You have to check the PRFILE parameter 2:386 setting and change it totransfer on-line in this case. Otherwise, the setting in the PRFILEoverrides the parameter <priority of trace in MSC and BSS>.

The report transfer method (on-line or off-line) is controlled by bothparameter <priority of trace in MSC and BSS> and the 2:386PRFILE parameter. For more information see section Trace reporttransfer.

3. Check and set up trace support in other network elements

See section Setting up trace support in other network elements.

4. Check the trace setting in the VLR (MWI)

Check the trace setting with the MWI command in the VLR. If youneed to modify an existing trace case, first you have to deactivatethe case with the MWE command. Then you can then modify thesettings with the MWC command.

5. Activate subscriber trace in VLR (MWC)

ZMWC:IMSI=<international mobile subscriberidentity>:REF=<trace reference>,OMC=<operation andmaintenance centre address>,MEVENT=<trace invokingevent in MSC and BSS>,MTYPE=<MSC trace record type>,BTYPE=<BSS trace record type>,PRI=<priority of tracein MSC and BSS>;

Further information

Example Activating subscriber trace in VLR

1. Check the I/O device where the reports are output in each MSC/VLR.

ZIID::GSMME1PR;

ZIID::GSMME1MG;

2. Change the I/O devices. The current I/O device is a virtual displayunit. Change the ASCII reports to be output in the line printer, andthe binary reports in the WDU.






3. Check the PRFILE parameter 9:36, which defines the call phaseswhen a report is produced.

ZWOI:9;

4. Change the value of the parameter so that the report is producedwhen the called subscriber answers, charging ends, and a service isused. The binary number for the example is 000101100 which is 2Chexadecimal.

ZWOC:9,36,2C;


ZWOI:2,386;

ZWOI:50,0;

6. Change the value of the PRFILE parameter 2:386 to allow transfer ofthe reports on-line or off-line according to the parameter <priority oftrace in MSC and BSS>.

ZWOC:2,386,3;

7. Change the value of the PRFILE parameter 50:0 to define the outputformat of trace reports (ASCII and XML in this example).

ZWOC:50,0,5;

8. Check if the BSS supports trace in the case of a BSC with the nameABERDEEN.

ZEDB:NAME=ABERDEEN:FUN;

9. Change the BSS parameter for the BSSAP version 9 to supporttrace if trace reports are to be generated in the BSC.

ZEDT:VER=9:F,34,1;

10. Check if the subsequent MSC supports trace in inter-MSC handoverand in all location areas.

ZEIO;

11. Change the location area parameters so that in inter-MSC handoverthe MSC supports trace in the case of a location area with the code45531.

ZEIM:45531:TRA=Y;



12. Activate local subscriber trace of the subscriber whose IMSI numberis 244041297264491. The trace reference is 100, there is no OMCaddress, the trace invoking events in the MSC and the BSS are allevents, the MSC trace record type is basic, the BSS record type isbasic, and the trace records are transferred to the OMC on-line.

ZMWC:IMSI=244041297264491:REF=100,PRI=Y;

4.2 Activating and deactivating equipment trace in VLR

Activate equipment trace in VLR with the MWC command.

To display trace-activated subscribers and equipment in the VLR, use theMWL command.

To check the trace settings of individual equipment, use the MWIcommand. The traced equipment is identified with its IMEI.

To deactivate equipment trace in VLR, use the MWE command.

Before you start


Steps

1. Define the call phases that produce a report

See section Defining the call phases that produce a report.



Note

You have to check the PRFILE parameter 2:386 and change it totransfer on-line in this case. Otherwise, the setting in the PRFILEoverrides the parameter <priority of trace in MSC and BSS>.

The report transfer method (on-line or off-line) is controlled by bothparameter <priority of trace in MSC and BSS> and the 2:386 PRFILEparameter. For more information see section Trace report transfer.




3. Set up trace support in other network elements

See section Setting up trace support in other network elements.

4. Check the trace settings (MWI)

Check the trace setting with the MWI command in the VLR. If youneed to modify an existing trace case, first you have to deactivatethe case with the MWE command. Then you can modify the settingswith the MWC command.

5. Check the PLMN parameters (MXP)

ZMXP:NAME=<PLMN name>;

The execution printout of the command contains the TRACEparameter value (whether trace activation from other PLMNs isaccepted or not).

6. Modify the PLMN parameters (MXN)

Modify the PLMN parameter TRACE to define whether traceactivation from other PLMNs is accepted or not.

ZMXN:NAME=<PLMN name>::::::TRACE=<Yes/No>;

7. Activate equipment trace (MWC)

ZMWC:IMEI=<international mobile station equipmentidentity>:REF=<trace reference>,OMC=<operation andmaintenance centre address>,MEVENT=<trace invokingevent in MSC and BSS>,MTYPE=<MSC trace record type>,BTYPE=<BSS trace record type>,PRI=<priority of tracein MSC and BSS>;

Further information

Example Activating equipment trace in VLR


ZIID::GSMME1PR;

ZIID::GSMME1MG;



2. Change the I/O devices. The current I/O device is a virtual displayunit. Change the ASCII reports to be output in the line printer, andthe binary reports in the WDU.



3. Check the PRFILE parameter 9:36, which defines the call phaseswhen a report is produced.

ZWOI:9;

4. Change the value of the parameter so that the report is producedwhen the called subscriber answers, charging ends, and a service isused. The binary number for the example is 000101100, which is 2Chexadecimal.

ZWOC:9,36,2C;


ZWOI:2,386;

ZWOI:50,0;

6. Change the value of the PRFILE parameter 2:386 to allow transfer ofthe reports on-line or off-line according to the parameter priority oftrace in MSC and BSS.

ZWOC:2,386,3;


ZWOC:50,0,5;

8. Check the parameters of the PLMN called MIDDLEEARTH. In theexecution printout, look for the TRACE parameter value to seewhether trace activation is accepted from this PLMN or not.

ZMXP:NAME=MIDDLEEARTH;

9. Modify the PLMN parameters so that trace activation is not acceptedfrom the PLMN called MIDDLEEARTH.

ZMXN:NAME=MIDDLEEARTH::::::TRACE=N;

10. Check if the BSS supports trace in the case of a BSC with the nameABERDEEN.

ZEDB:NAME=ABERDEEN:FUN;

11. Change the BSS parameter for the BSSAP version 9 to supporttrace if trace reports are to be generated in the BSC.




ZEDT:VER=9:F,34,1;

12. Check if the subsequent MSC supports trace in inter-MSC handoverand in all location areas.

ZEIO;

13. Change the location area parameters so that in inter-MSC handoverthe MSC supports trace in the case of a location area whose with thecode 45531.

ZEIM:45531:TRA=Y;

14. Activate local trace for a mobile equipment whose IMEI number is49010261587090. The trace reference is 333, the OMC address is134767922, the trace invoking events in the MSC and the BSS arelocation updates and IMSI attach/detach, the MSC trace record typeis basic, no BSS trace, and the trace records are transferred to theOMC on-line.

ZMWC:IMEI=49010261587090:REF=333,OMC=134767922,MEVENT=LU,BTYPE=N,PRI=Y;

4.3 Activating and deactivating EIR list category tracein VLR

To display trace-activated EIR list categories in a given PLMN, use the MXPcommand. The PLMN index of the subscriber is included in the commandexecution printout.

The execution printout of the MWIcommand includes the EIR list status ofthe equipment in question.

If you want to check if a single IMEI or IMEI series are put either to theblack or grey EIR list (and consequently, if they are affected by the EIR listtrace settings), use the MEO command.

If you want to check which IMEIs are on the black, grey, or white lists (and,consequently, which are affected by the EIR list trace settings), use theMEI command.

To deactivate EIR list category trace in VLR, use the MXN command andchange the appropriate PLMN parameter value to other than TR.



Note

EIR list category trace can cause substantial load in your system.

Before you start


Steps


See section Setting up the report transfer method.

2. Activate EIR list trace

Steps

a. Check the PLMN parameters (MXP)

ZMXP:NAME=<PLMN name>;

The execution printout of the command contains the followingEIR list related blocks:. black list effect (BLOCK, TRACED or ALLOW). grey list effect (BLOCK, TRACED or ALLOW). unknown IMEI effect (BLOCK, TRACED or ALLOW). TRACE parameter value (whether trace activation from

other PLMNs is accepted or not)

b. Modify the PLMN parameters (MXN)

Modify the PLMN parameters so that trace is activated onentities found in the black, grey or unknown list of IMEIs in theEIR. Whether trace activation from other PLMNs is acceptedor not can also be defined.

ZMXN:NAME=<PLMN name>:BLE=<black list effect>,GLE=<grey list effect>,UIE=<effect of unknownIMEI>:::::TRACE=<Yes/No>;

c. Add new IMEI to the EIR list, if necessary (MEB, MEG)

Add a new equipment identity (IMEI) to the EIR black or greylist, if necessary.




Use the MEB command for black list handling, and the MEGcommand for grey list handling.

ZMEB:IMEI=<international mobile equipmentidentity>,PSNR=<part of serial number>,REASON=<reason code>,CD=<check digit>,VISIB=<visibility>;

ZMEG:IMEI=<international mobile equipmentidentity>,PSNR=<part of serial number>,REASON=<reason code>,CD=<check digit>,VISIB=<visibility>;

Further information

Example Activating EIR list category trace in VLR

Activate trace on the EIR grey list and add the IMEI series53728252100001 - 53728252100100 to the grey list with a reason code of'not properly working equipment'. The PLMN name is MIDDLEEARTH.


ZIID::OBSEIR%;

2. Change the I/O devices if necessary.

The current I/O device is a virtual display unit. Change the ASCIIreports to be output in the line printer, and the binary reports in theWDU.

ZIIS::OBSEIRGA:DEV=VDU-0:DEV=LPT-0;

ZIIS::OBSEIRGB:DEV=VDU-0:DEV=WDU-0;

3. Check the PRFILE parameters 2:386 and 50:0 to see the transfermethod for trace reports and the report output format.

ZWOI:2,386;

ZWOI:50,0;

4. Change the value of the parameter to allow the transfer of thereports on-line or off-line according to the parameter <priority of tracein MSC and BSS>.

ZWOC:2,386,3;




ZWOC:50,0,5;

6. Check the parameters of the PLMN called MIDDLEEARTH andexamine the block of 'grey list effect' in the execution printout. Also,check the value of the TRACE parameter in the printout to seewhether trace activation is accepted from this PLMN.

ZMXP:NAME=MIDDLEEARTH;

7. Modify the PLMN parameters so that trace is activated on entitiesfound in the grey list, if the value of 'grey list effect' is other than TR(trace).

ZMXN:NAME=MIDDLEEARTH:GLE=TR;

8. Modify the PLMN parameters so that trace activation is not acceptedfrom the PLMN called MIDDLEEARTH.

ZMXN:NAME=MIDDLEEARTH::::::TRACE=N;

9. Add the IMEI series 53728252100001 - 53728252100100 to thegrey list with a reason code of 'not properly working equipment'.

ZMEG:IMEI=53728252100001,PSNR=100,REASON=NW;




Subscriber and Equipment Trace

Documents

nokiasiemens networks

trace activationdeactivation

trace priorities

trace reports

tracerelated protocols

tracerelated files

product documentation

trace invoking events