SIST ETS 300 627 E2:2003
(Main)Digital cellular telecommunications system (Phase 2) (GSM); Subscriber and equipment trace (GSM 12.08 version 4.5.1)
Digital cellular telecommunications system (Phase 2) (GSM); Subscriber and equipment trace (GSM 12.08 version 4.5.1)
Specification of the Trace facility in GSM for Subscriber tracing and Equipment tracing for O&M purposes.
Digitalni celični telekomunikacijski sistem (faza 2) ¬– Popis podatkov o naročniku in opremi (GSM 12.08, različica 4.5.1)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-december-2003
'LJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHP ID]D ¤±3RSLVSRGDWNRYRQDURþQLNX
LQRSUHPL *60UD]OLþLFD
Digital cellular telecommunications system (Phase 2) (GSM); Subscriber and equipment
trace (GSM 12.08 version 4.5.1)
Ta slovenski standard je istoveten z: ETS 300 627 Edition 2
ICS:
33.070.50 Globalni sistem za mobilno Global System for Mobile
telekomunikacijo (GSM) Communication (GSM)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN ETS 300 627
TELECOMMUNICATION February 1998
STANDARD Second Edition
Source: SMG Reference: RE/SMG-061208PR1
ICS: 33.020
Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM)
R
GLOBAL SYSTEM FOR
MOBILE COMMUNICATIONS
Digital cellular telecommunications system (Phase 2);
Subscriber and equipment trace
(GSM 12.08 version 4.5.1)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1998. All rights reserved.
Page 2
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.
Page 3
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
Contents
Foreword .7
Introduction.7
1 Scope .9
2 Normative references.9
3 Definitions and abbreviations .10
3.1 Definitions .10
3.2 Abbreviations .10
4 Trace overview.11
5 Trace activation and deactivation.13
5.1 General .13
5.2 Subscriber Tracing (Tracing of IMSI).13
5.2.1 General.13
5.2.2 HPLMN Operator Traces Home Subscriber within the HPLMN.13
5.2.3 HPLMN Operator traces the HLR activities of own IMSI roaming in a
VPLMN .14
5.2.4 PLMN Operator wishes to trace foreign subscribers (IMSI) in own PLMN .14
5.3 Equipment Tracing (Tracing of IMEI).15
5.3.1 General.15
5.3.2 Tracing of IMEI via VLR .15
5.4 TMN Management Functions for Activation/Deactivation.16
5.4.1 List of Functions .16
5.4.1.1 HLR.16
5.4.1.2 MSC/VLR.16
5.4.2 Activate Home Subscriber Trace .16
5.4.3 Deactivate Home Subscriber Trace .17
5.4.4 Activate Foreign Subscriber Trace.17
5.4.5 Deactivate Foreign Subscriber Trace.18
5.4.6 Activate Equipment Trace .18
5.4.7 Deactivate Equipment Trace.19
5.5 HLR Functional Entities .20
5.5.1 Managed Object Classes in HLR .20
5.5.1.1 tracedHomeSubscriberInHlr .20
5.5.1.2 Attributes.20
5.5.1.2.1 tracedHomeSubscriberInHlr .20
5.5.1.3 Notifications .21
5.6 VLR Functional Entities.22
5.6.1 Managed Object Classes in VLR .22
5.6.1.1 tracedForeignSubscriberInVlr.22
5.6.1.2 tracedEquipmentInVlr .22
5.6.1.3 Attributes.23
5.6.1.3.1 tracedForeignSubscriberInVlr .23
5.6.1.3.2 tracedEquipmentInVlr .23
5.6.1.4 Notifications .24
6 Trace Types .25
6.1 MSC/BSS Trace Type.25
6.2 HLR Trace Type.26
7 Trace record contents .28
7.1 General .28
Page 4
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
7.2 MSC Trace Record Content. 30
7.3 BSS Trace Record Content. 32
7.4 HLR Trace Record Content. 34
7.5 Trace Record fields. 35
7.5.1 Radio channel information. 35
8 Creation of Trace Records . 36
8.1 General. 36
8.2 Trace Record Control. 36
8.2.1 General . 36
8.2.2 Attributes. 37
8.2.3 Other Trace Record Criteria . 37
9 Trace Record Transfer . 38
9.1 General. 38
9.2 Transfer of Records .39
9.2.1 Bulk record transfer . 39
9.2.2 Log control . 39
9.2.3 Log access. 39
9.2.4 Event Reporting . 39
9.2.4.1 Event Forwarding Discriminators . 39
9.2.4.2 Direct Transfer by Trace Control Function. 40
10 Managed Object Model. 41
10.1 Naming Hierarchy. 41
10.2 Inheritance. 41
10.3 Object Classes . 42
10.3.1 tracedHomeSubscriberInHlr . 42
10.3.2 tracedForeignSubscriberInVlr. 42
10.3.3 tracedEquipmentInVlr . 43
10.3.4 Trace control. 44
10.3.5 Trace log record. 44
10.3.6 Log. 46
10.3.7 Event Forwarding Discriminators. 46
10.4 Attributes . 46
10.4.1 traceActivatedInVlr. 46
10.4.2 foreignSubscriberRegisteredInVlr. 46
10.4.3 equipmentRegisteredInVlr . 47
10.4.4 mapErrorOnTrace. 47
10.4.5 IMEI . 47
10.4.6 IMSI . 47
10.4.7 Trace record content . 48
10.4.8 Trace control id. 48
10.4.9 HLR Trace type. 48
10.4.10 Trace reference . 48
10.4.11 Trace type. 48
10.4.12 Record criteria . 48
10.4.13 Event types . 49
10.4.14 Operation system ID. 49
10.4.15 Operational State. 49
10.4.16 Administrative State. 49
10.4.17 MSC BSS trace type used . 49
10.4.18 HLR trace type used . 49
10.4.19 MSC BSS trace type. 49
10.5 Notifications. 49
10.5.1 General . 49
10.5.2 Trace report . 50
10.6 Name Bindings. 50
10.6.1 tracedHomeSubscriberInHlr-hlrFunction Name Binding. 50
10.6.2 tracedForeignSubscriberInVlr-vlrFunction Name Binding . 50
10.6.3 tracedEquipmentInVlr-vlrFunction Name Binding. 51
10.6.4 traceLogRecord-Log Name Binding . 51
10.6.5 traceControl-hlrFunction Name Binding. 51
Page 5
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
10.6.6 traceControl-mscFunction Name Binding .51
10.6.7 traceControl-bssFunction Name Binding .51
11 Syntax.52
History.63
Page 6
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
Blank page
Page 7
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
Foreword
This European Telecommunication Standard (ETS) has been produced by the Special Mobile Group
(SMG) of the European Telecommunications Standards Institute (ETSI).
This ETS specifies trace facilities for the Digital cellular telecommunications system.
The specification from which this ETS has been derived was originally based on CEPT documentation,
hence the presentation of this ETS may not be entirely in accordance with the ETSI/PNE rules.
Transposition dates
Date of adoption of this ETS: 23 January 1998
Date of latest announcement of this ETS (doa): 31 May 1998
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 30 November 1998
Date of withdrawal of any conflicting National Standard (dow): 30 November 1998
Introduction
The trace facility enables customer administration and network management to trace the activities of
various entities when specific events occur within the PLMN. This facility should also enable the tracing of
all the information that is available to the PLMN concerning the call path used by the associated entity.
Examples of information that could be in a trace record are:
- the identity of the originating and terminating equipment of the mobile or fixed subscriber;
- the identity of the incoming and outgoing circuits of the nodes involved;
- supplementary Services invoked;
- all A-Interface messages.
The trace facility is a useful maintenance aid and development tool which can be used during system
testing and proving. In particular it may be used in conjunction with test-MSs to ascertain the digital cell
"footprint", the network integrity and also the network QOS as perceived by the PLMN customers.
The facility may be used by subscriber administration and network management for subscriber
observation, e.g. following a customer complaint or on suspicion of equipment malfunction by the operator
or at the request of the police.
As the amount of information that can be collected for a single call is very large, Network Elements can
limit the number of simultaneous traces by either rejecting a trace request or by only producing a sub-set
of the information required.
Page 8
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
Blank page
Page 9
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
1 Scope
This European Telecommunication Standard (ETS) specifies the Trace facility for GSM where it refers to:
- subscriber tracing (tracing of International Mobile Subscriber Identity (IMSI));
- equipment tracing (tracing of International Mobile station Equipment Identity (IMEI)).
It does not cover:
- types of trace which relate more to network elements than to individual subscribers e.g. tracing
events within a Base Station System (BSS), and so on;
- tracing of all possible parties in e.g. a multi-party call.
It also refers only to tracing activated from the OSF and not to that activated by means of local Man
Machine Interface (MMI).
2 Normative references
This ETS incorporates by dated or undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] GSM 01.04 (ETR 100): "Digital cellular telecommunications system (Phase 2);
Abbreviations and acronyms".
[2] GSM 04.08 (ETS 300 557): "Digital cellular telecommunications system
(Phase 2); Mobile radio interface layer 3 specification".
[3] GSM 08.06 (ETS 300 589): "Digital cellular telecommunications system
(Phase 2); Signalling transport mechanism specification for the Base Station
System - Mobile-services Switching Centre (BSS - MSC) interface".
[4] GSM 08.08 (ETS 300 590): "Digital cellular telecommunications system
(Phase 2); Mobile Switching Centre - Base Station System (MSC - BSS)
interface Layer 3 specification".
[5] GSM 08.58 (ETS 300 596): "Digital cellular telecommunications system
(Phase 2); Base Station Controller - Base Transceiver Station (BSC - BTS)
interface Layer 3 specification".
[6] GSM 09.02 (ETS 300 599): "Digital cellular telecommunications system
(Phase 2); Mobile Application Part (MAP) specification".
[7] GSM 12.00 (ETS 300 612-1): "Digital cellular telecommunications system
(Phase 2); Objectives and structure of Network Management (NM)".
[8] GSM 12.01 (ETS 300 612-2): "Digital cellular telecommunications system
(Phase 2); Common Aspects of GSM Network Management (NM)".
[9] GSM 12.02 (ETS 300 613): "Digital cellular telecommunications system
(Phase 2); Subscriber, Mobile Equipment (ME) and services data
administration".
[10] GSM 12.05 (ETS 300 616): "Digital cellular telecommunications system
(Phase 2); Subscriber related event and call data".
[11] GSM 12.20 (ETS 300 622): "Digital cellular telecommunications system
(Phase 2); BSS Management Information".
Page 10
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
[12] CCITT Recommendation X.227 - ISO 8650: "Information technology - Open
Systems Interconnection - Connection-oriented protocol for the association
control service element: Protocol specification".
[13] CCITT Recommendation X.721 (ITU-T | ISO/IEC 10165-1): "Information
technology - Open Systems Interconnection - Structure of management
information: Definition of management information".
[14] CCITT Recommendation X.734 (ITU-T | ISO/IEC 10164-5): "Information
technology - Open Systems Interconnection - Systems Management: Event
report management function".
[15] CCITT Recommendation X.735 (ITU-T | ISO/IEC 10164-6): "Information
technology - Open Systems Interconnection - Systems Management: Log
control function".
[16] CCITT Recommendation X.731 (ITU-T | ISO/IEC 10164-2): "Information
technology - Open Systems Interconnection - Systems Management: State
management function".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
activation of a trace: An action taken at the OSF through MMI commands to allow a trace record to be
produced for a particular IMSI or IMEI when an Invocation Event occurs. This equates to "activation of a
trace" in GSM 09.02 [6].
active pending: The state of an activated trace is called Active Pending in a particular NE when the
subscriber or equipment being traced is not registered in that NE.
invocation of a trace: An event relating to a particular IMSI or IMEI that occurs in the network that
causes data to be collected in a trace record in circumstances where trace has been activated for that
IMSI or IMEI. This equates to "tracing subscriber activity" in GSM 09.02 [6] and "Trace Invocation" in
GSM 08.08 [4]. It is possible that an event relating to the IMSI/IMEI may still be active when another event
or events relating to the same IMSI/IMEI occurs which requires additional information to be collected.
These additional events are termed parallel events. This additional trace information for parallel events is
collected in the same trace record as the first event.
trace record: In the NEF a trace record is a set of traceable data collected as determined by the trace
type. The trace record is collected under the trace record criteria specified by the OSF and transferred to
the OSF.
3.2 Abbreviations
For all abbreviations used in this ETS, refer to GSM 01.04 [1].
Page 11
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
4 Trace overview
Figure 1 gives an outline of the subscriber and equipment tracing and shows the relationship between the
inputs on activation and deactivation and the trace record outputs.
OMC1 OMCx
12.08
Trace Activation
a) IMSI.
b) Trace Reference.
c) OMC Destination.
12.08
d) Trace Type.
Trace Activation
a) IMSI.
12.08
b) Trace Reference.
Trace Activation
c) OMC Destination.
a) IMEI.
d) Trace Type.
b) Trace Reference.
e) HLR Trace Type.
c) OMC Destination.
d) Trace Type.
Equipment Foreign Sub. Home Sub.
12.08
HLR
Trace Record Generation
a) Trace Record Header.
b) HLR Trace Record.
09.02
MAP-ACTIVATE-TRACE-MODE MAP-DEACTIVATE-TRACE-MODE
a) IMSI
a) IMSI
b) Trace Reference b) Trace Reference
c) omc-id
d) Trace Type
MSC 'A' MSC 'B'
09.02
MSC/VLR MSC/VLR
MAP_PREPARE_HANDOVER
(Contains
MSC_INVOKE_TRACE message)
12.08
08.08
12.08
Trace Record Generation
a) Trace Record Header. MSC-INVOKE-TRACE
Trace Record Generation
b) MSC Trace Record.
a) Message Type a) Trace Record Header.
b) IMSI or IMEI
b) MSC Trace Record.
c) Trace Reference
d) Trigger Id
e) OMC Id
f) Trace Type
g) TransactionId
12.08
Trace Record Generation
a) Trace Record Header.
b) BSS Trace Record.
BSS BSS BSS BSS
Figure 1: Subscriber and Equipment Trace for 12.08
Trace Activation and Deactivation are described in clause 5.
The Trace Types are defined in clause 6.
The Trace Records are defined in clause 7.
Page 12
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
The following events may invoke a MSC or BSS trace:
- Call set-up within MSC (MOC, MTC) (incl. attempts);
- SS-Action;
- Location Update (Normal and Periodic);
- SMS-MO;
- SMS-MT;
- IMSI attach and detach.
Additionally, the following event may invoke a BSS trace:
- Handover.
An HLR Trace may be invoked by one of the following:
- Location updates/cancellations;
- Insert/delete subscriber data;
- Routing enquiry (speech and SM);
- Provide roaming number;
- SS activity;
- SMS: Alert service centre/Ready for SM;
Trace records are generated within the managed elements by the trace control function according to the
trace type. Once a trace has been invoked and a trace record is being compiled, subsequent invoking
events relating to that IMSI (parallel events) will not cause new records to be compiled simultaneously but
will be contained in the same trace record as the first event.
For operator defined trace types the events on which trace records are generated and their contents are
defined within the trace record generation control.
These records are then transferred to the OSF (as defined by OMC-Id of the Destination OMC or
forwarded by the EFD) either as notifications (CMISE), or with bulk transfer (FTAM).
Page 13
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
5 Trace activation and deactivation
5.1 General
This document is only concerned with the activation of a trace from an OSF (OMC), and the OSF shall
keep a log of all trace activations and their deactivations. All entries in the log shall be date and time
stamped.
In the case of an OSF (OMC) failure, it may be possible to activate and deactivate the trace at a particular
network element by means of local MMI, but the procedures for doing this are not covered by this ETS.
Facilities shall exist to allow unsolicited trace data to be received by an OSF. This permits the collection of
trace data if the triggering entity (i.e. OSF or network element) is different to the collecting OSF.
5.2 Subscriber Tracing (Tracing of IMSI)
5.2.1 General
The tracing of both home and foreign roaming subscribers can be handled with this function.
If implemented, then the way the trace facility is used and organized, including restrictions due to national
laws and regulations, will be a matter for the PLMN Operator.
All trace records created in the HLR, MSC "A", MSC "B" and BSS are forwarded to the OSF either as
notifications and/or with bulk transfer, as defined in the trace parameters.
The following scenarios are identified from the HPLMN operation viewpoint:
a) HPLMN Operator traces its own (home) IMSI within the HPLMN;
b) HPLMN Operator traces the HLR activities of its own (home) IMSI while they are roaming in a
VPLMN;
c) HPLMN Operator wishes to trace foreign roaming subscribers (IMSI) within its own HPLMN.
5.2.2 HPLMN Operator Traces Home Subscriber within the HPLMN
The Operator may activate a trace for a home subscriber (IMSI) from any OSF by invoking the
management function Activate Home Subscriber Trace in the HLR where the IMSI is contained. This
request includes the trace parameters in the following list:
a) IMSI to be traced;
b) Trace Reference;
c) OMC-Id of the destination OMC;
d) Trace Type;
e) HLR Trace Type.
For each IMSI, only one HPLMN subscriber trace can be active, subsequent requests being rejected.
If the IMSI is roaming within its HPLMN, then the trace request is forwarded to the VLR where the
subscriber is registered via a MAP message (MAP-ACTIVATE-TRACE-MODE).
When the HPLMN subscriber trace is activated, a trace record will be created by MSC "A" , MSC "B", HLR
or BSS when certain invoking events occur i.e. MOC, MTC, SS-Action, SMS-MO, SMS-MT, Location
Update, IMSI attach and detach. The trace action and record layout is defined by the trace type
parameters.
Page 14
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
A trace may be invoked in the BSS when an Invoking Event, specified in the Invoking Event sub-field in
the Trace Type, occurs and the BSS Record Type is set to a value other than "No BSS Trace". A Trace is
invoked by sending a BSSMAP MSC_INVOKE_TRACE message from the MSC to the BSS. When the
BSS receives this message it starts tracing the necessary fields as specified in the BSS Record
associated with the specified BSS Record Type.
If the subscriber is roaming in a foreign PLMN then the HPLMN subscriber trace request is stored in the
HLR, but the trace is not active in the HPLMN VLRs.
The trace is deactivated by using the management function Deactivate Home Subscriber Trace in the
HLR. This request includes the trace parameters in the following list:
a) IMSI;
b) Trace Reference.
If the IMSI is roaming within its HPLMN then the trace deactivation request is forwarded to the VLR where
the subscriber is registered via a MAP message (MAP-DEACTIVATE-TRACE-MODE).
TMN Management Functions required for trace activation (in HLR):
Activate Home Subscriber Trace
Deactivate Home Subscriber Trace
5.2.3 HPLMN Operator traces the HLR activities of own IMSI roaming in a VPLMN
This scenario is identical to the previous scenario with the exception that the only records generated come
from the HLR.
5.2.4 PLMN Operator wishes to trace foreign subscribers (IMSI) in own PLMN
In order to trace the IMSIs of roaming subscribers in own PLMN, a list of those IMSIs plus the associated
subscriber trace parameters must be stored in the VLR. No HLR trace records are produced for foreign
subscriber traces.
The operator may activate a trace for any foreign roaming IMSI from an OSF by invoking the management
function Activate Foreign Subscriber Trace in one or more VLRs within their own PLMN. If the location
of the subscriber is not known it is necessary to activate the trace in all VLRs where the subscriber may be
located.
The following trace parameters are sent with this request:
a) IMSI to be traced;
b) Trace Reference;
c) OMC-Id of the destination OMC;
d) Trace Type.
The trace request is stored in the VLR. If the subscriber subsequently roams into the VLR area the
VPLMN subscriber trace will be activated.
For each IMSI only one foreign subscriber trace can be active in a particular VLR, subsequent requests
being rejected.
A trace may be invoked in the BSS when an Invoking Event, specified in the Invoking Event sub-field in
the Trace Type, occurs and the BSS Record Type is set to a value other than "No BSS Trace". A Trace is
invoked by sending a BSSMAP MSC_INVOKE_TRACE message from the MSC to the BSS. When the
BSS receives this message it starts tracing the necessary fields as specified in the BSS Record
associated with the specified BSS Record Type.
Page 15
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
The VPLMN subscriber trace is deactivated by invoking Deactivate Foreign Subscriber Trace in the
VLR. This request includes the trace parameters in the following list:
a) IMSI;
b) Trace Reference.
TMN Management Functions required for trace activation (in VLR):
Activate Foreign Subscriber Trace
Deactivate Foreign Subscriber Trace
5.3 Equipment Tracing (Tracing of IMEI)
5.3.1 General
If the tracing of IMEIs is implemented then the way the trace facility is used and organized, including
restrictions due to national laws and regulations, will be a matter for the PLMN Operator.
An IMEI may be traced in order to find out the current IMSI, or the location or behaviour of faulty or stolen
equipment reported via the EIR.
The ETS describes one method of handling IMEI tracing i.e. tracing of IMEI via the VLR.
5.3.2 Tracing of IMEI via VLR
The operator may activate an equipment trace for any subscriber's equipment (IMEI) from an OSF by
invoking the management function Activate Equipment Trace in one or more VLR in the HPLMN. The
trace must be activated in all VLRs controlling areas where it is required to trace the target IMEI. The trace
parameters are transmitted with the activation request.
The following trace parameters are sent with this request:
a) IMEI to be traced;
b) Trace reference;
c) OMC-Id of the destination OMC;
d) Trace Type.
For GSM Phase 2 Mobile Stations the IMEI will be available to the Network as it can be included in the
BSS-MAP message CIPHER-MODE-COMPLETE. If IMEI trace is required, it is the responsibility of the
network operator to specify that CIPHER-MODE-COMPLETE contains IMEIs, or optionally the IMEI is
called for in connection with MOC, location update etc. Alternatively the network can ask the MS for the
IMEI by sending a GSM 04.08 [2] IDENTITY REQUEST message to the MS, indicating that the IMEI is
required.
When a subscriber arrives at a VLR using an equipment with an IMEI for which trace has been activated
(but is in pending state) at that VLR then the IMEI trace will become.
For each IMEI only one equipment trace can be active in a particular VLR at any one time, subsequent
requests being rejected, although both the IMSI trace (home subscriber tracing and foreign subscriber
tracing) and the IMEI trace can be active at the same time.
This equipment trace is deactivated by invoking the management function Deactivate Equipment Trace
in the VLR. This request includes the trace parameters in the following list:
a) IMEI;
b) Trace Reference.
Page 16
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
TMN Management Functions required for trace activation (in VLR):
Activate Equipment Trace
Deactivate Equipment Trace
5.4 TMN Management Functions for Activation/Deactivation
5.4.1 List of Functions
5.4.1.1 HLR
Activate Home Subscriber Trace
Deactivate Home Subscriber Trace
5.4.1.2 MSC/VLR
Activate Foreign Subscriber Trace
Deactivate Foreign Subscriber Trace
Activate Equipment Trace
Deactivate Equipment Trace
5.4.2 Activate Home Subscriber Trace
This function is equivalent to the OM_Subscriber_Tracing_Activation_req in GSM 09.02 [6].
The subscriber tracing procedures are used for the management of the trace status and the type of trace.
The subscriber tracing activation procedure operates as follows:
a) The OSF creates a tracedHomeSubscriberInHlr object instance in the HLR of the subscriber to be
traced.
b) If the subscriber is roaming outside of the HPLMN or not currently registered, then the trace is in
active pending state. The home subscriber trace for the subscriber is activated in the HLR on a
subsequent location update. This activation is shown as an attribute value change in the attribute
traceActivatedInVlr.
c) If the subscriber is already registered then the home subscriber trace becomes immediately active
in the HLR (after positive confirmation from the VLR).
When the trace is first activated then the status of the trace indicator attribute traceActivatedInVlr in the
tracedHomeSubscriberInHlr object instance is set to False.
If the subscriber is registered and is roaming in the home PLMN area then the HLR will initiate the
MAP-ACTIVATE-TRACE-MODE request primitive and the trace indicator status will be set to True only in
the case of a positive confirmation of the MAP-ACTIVATE-TRACE-MODE. In case of an error, the trace
indicator status remains False.
If the MAP-ACTIVATE-TRACE-MODE confirm primitive is received indicating an error situation then this is
recorded in an error attribute in the tracedHomeSubscriberInHlr object instance.
If the subscriber roams to an area outside that where tracing is possible then the status in the
tracedHomeSubscriberInHlr object instance is updated to False.
Page 17
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
The trace records are sent from the recording NEF to the OSF by the deployed event reporting
mechanism (see chapter Trace Record Transfer). The Trace Type attribute indicates the type of trace
records to be produced and the way in which they will be reported i.e. each event record being either
directly sent to the OSF in real-time, or being collected in a file for later transfer.
All attribute value changes will be reported with a notification to the OSF.
System management functions:
Create tracedHomeSubscriberInHlr
Get Attribute
Notifications:
objectCreation
attributeValueChange
5.4.3 Deactivate Home Subscriber Trace
This function is equivalent to the OM_Subscriber_Tracing_Deactivation_req in GSM 09.02 [6].
The subscriber trace is deactivated by the OSF deleting the tracedHomeSubscriberInHlr object instance in
the HLR.
If the trace status is True then the HLR will send the MAP-DEACTIVATE-TRACE-MODE message to
VLR.
If the MAP-DEACTIVATE-TRACE-MODE confirm primitive is received indicating an error situation then
this is indicated to the OSF via an error attribute in the tracedHomeSubscriberInHlr object instance and
the object is not deleted.
The home subscriber trace deactivation can be indicated with a notification to the initiating OSF.
System management functions:
Delete tracedHomeSubscriberInHlr
Get Attribute
Notifications:
objectDeletion
attributeValueChange
5.4.4 Activate Foreign Subscriber Trace
This function is analogous to the OM_Subscriber_Tracing_Activation_req in GSM 09.02 [6], but the trace
activation is performed directly in the VLR.
The foreign subscriber trace is activated by the OSF executing the system management function Create
tracedForeignSubscriberInVlr in the VLR.
THE OSF creates a tracedForeignSubscriberInVlr object instance in the VLR(s) in which the network
operator wishes to trace the subscriber.
The tracing continues as follows:
a) If the subscriber is not currently registered, then the foreign subscriber trace for the subscriber is
active pending. It is activated (i.e. status attribute value is set to True) in the VLR on a subsequent
location update. The activation is notified to the OSF as an attribute value change in the attribute
foreignSubscriberRegisteredInVlr.
Page 18
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
b) If the subscriber is already registered then the foreign subscriber trace becomes immediately active
in the VLR.
When the trace is first activated then the status of the attribute foreignSubscriberRegisteredInVlr is set to
False. When the traced subscriber registers in the VLR the attribute status of
foreignSubscriberRegisteredInVlr is set to True.
All attribute value changes will be reported with a notification to the OSF.
The trace records are sent from the corresponding MSC to the OSF by the deployed event reporting
mechanism (see chapter Trace Record Transfer). The Trace Type attribute indicates the type of trace
records to be produced and the method by which they will be reported.
System management functions:
Create tracedForeignSubscriberInVlr
Get Attribute
Notifications:
objectCreation
attributeValueChange
5.4.5 Deactivate Foreign Subscriber Trace
This function is analogous to the OM_Subscriber_Tracing_Deactivation_req in GSM 09.02 [6], but the
trace deactivation is performed.
The OSF deactivates subscriber trace by deleting the tracedForeignSubscriberInVlr object instance in the
VLR(s) in which the object instance had previously been created.
The foreign subscriber trace is deactivated by the OSF executing the system management function Delete
tracedForeignSubscriberInVlr in the VLR.
System management functions required:
Delete tracedForeignSubscriberInVlr
Notifications required:
objectDeletion
attributeValueChange
5.4.6 Activate Equipment Trace
This function is analogous to the OM_Subscriber_Tracing_Activation_req in GSM 09.02 [6], but the trace
activation is performed directly in the VLR.
The equipment trace is activated by the OSF executing the system management function Create
tracedEquipmentInVlr.
The OSF creates a traceEquipmentInVlr object instance in the VLR(s) for the areas to be monitored.
Page 19
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
The tracing continues as follows:
a) If the equipment is not currently registered, then the equipment trace for the equipment is active
pending. It is activated (i.e. status attribute value is set to True) in the VLR on a subsequent
location update or IMSI attach. The activation is notified to the OSF as an attribute value change in
the attribute equipmentRegisteredInVlr.
b) If the equipment is already registered then the equipment trace becomes immediately active in the
VLR.
When the trace is first activated then the status of the attribute equipmentRegisteredInVlr is set to False.
When the equipment registers in the VLR the attribute status of equipmentRegisteredInVlr is set to True.
All attribute value changes will be reported with a notification to the OSF.
The trace records are sent from the corresponding MSC to the OSF by the deployed event reporting
mechanism (see chapter Trace Record Transfer). The Trace Type attribute indicates the type of trace
records to be produced and the method by which they will be reported.
System management functions:
Create tracedForeignSubscriberInVlr
Get Attribute
Notifications:
objectCreation
attributeValueChange
5.4.7 Deactivate Equipment Trace
This function is analogous to the OM_Subscriber_Tracing_Deactivation_req in GSM 09.02 [6], but the
trace deactivation is performed in the VLR.
The equipment trace is deactivated by the OSF executing the system management function Delete
tracedEquipmentInVlr.
The OSF deactivates equipment trace by deleting the tracedEquipmentInVlr object instance in the VLR(s)
in which the object instance had previously been created.
System management functions:
Delete tracedEquipmentInVlr
Notifications:
objectDeletion
attributeValueChange
Page 20
ETS 300 627 (GSM 12.08 version 4.5.1): February 1998
5.5 HLR Functional Entities
Figure 2 shows that part of the Subscriber Administration Containment Tree for the HLR relevant to Trace
activation and deactivation.
hlrFunction
tracedHomeSubscriberInHlr
Figure 2: Subscriber Trace Containment Tree for the HLR
5.5.1 Managed Object Classes in HLR
5.5.1.1 tracedHomeSubscriberInHlr
This object class controls the home subscriber trace facility. Each instance of this object represents an
IMSI of a home subscriber to be traced i.e. if an instance for an IMSI exists then that means that the trace
has been activated for that IMSI.
Name M/O Value-Set
IMSI RDN Single
traceActivatedInVlr M Single
traceReference M Single
traceType M Single
hlrTraceType M Single
operationSystemId O Single
mapErrorOnTrace M Single
5.5.1.2 Attributes
5.5.1.2.1 tracedHomeSubscriberInHlr
IMSI
This attribute is the RDN of the object tracedHomeSubscriberInHlr and defines an IMSI to be traced. It will
be an IMSI of a home subscriber for whom tracing is required.
The syntax is defined in MAP-CommonDataTypes IMSI.
traceActivatedInVlr
This attribute is single valued and gives an indication of the status of the Trace. Possible values of this
attribute are True and False.
On creation this attribute is set to False.
If the subscriber is register
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...