1、ETSI GSM*L2.08 94 3400855 00040b5 404 Released: October, 1994 GSM 12.08 Version: 4.0.0 Date: October 7, I994 Source: ETSI TC-SMG Reference: DE/SMG-O61208P UDC: 621.396.21 Key words: European digital cellular telecommunications system, Global System for Mobile communications (GSM) European digital ce
2、llular telecommunications system (Phase 2); Subscriber and Equipment Trace (GSM 12.08) ETSI European Telecommunications Standards Institute ETSI Secretariat Postal address: 06921 Sophia Antipolis Cedex - FRANCE Office address: Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE Tel.: + 33 92 9
3、4 42 O0 - Fax: + 33 93 65 47 16 0 European Telecommunications Standards Institute 1994. All rights reserved. No part may be reproduced except as authorised by written permission. The copyright and the foregoing restriction on reproduction extend to all media in which the information may be embodied.
4、 Page 3 GSM 12.08 version 4.0.0 Contents Foreword . 7 Introduction 7 1 Scope 9 2 (Normative) references . 9 3 Definitions. symbols and abbreviations . 10 3.1 Definitions . 10 3.3 Abbreviations . 10 3.2 Symbols 10 4 Trace overview . 10 5 Trace activation and deactivation 12 5.1 5.2 5.3 5.4 5.5 5.6 Ge
5、neral . 12 Subscriber Tracing (Tracing of 1MS1) . 13 5.2.1 General 13 5.2.2 HPLMN Operator Traces Home Subscriber within the HPLMN 13 5.2.3 PLMN Operator traces the HLR activities of own IMSI roaming in a VPLMN 14 5.2.4 PLMN Operator wishes to trace foreign subscribers (IMSII in own PLMN 14 Equipmen
6、t Tracing (Tracing of IMEI) 15 5.3.1 General 15 5.3.2 Tracing of IMEI via VLR 15 TMN Management Functions for Activation/Deactivation 16 5.4.1 List of Functions 16 5.4.1.1 HLR 16 5.4.1.2 MSCNLR . 16 5.4.2 Activate Home Subscriber Trace 16 5.4.3 Deactivate Home Subscriber Trace . 17 5.4.4 Activate Fo
7、reign Subscriber Trace 17 5.4.5 Deactivate Foreign Subscriber Trace . 18 5.4.6 Activate Equipment Trace . 19 5.4.7 Deactivate Equipment Trace 19 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 tracedHomeSubscrib
8、erInHlr . 20 5.5.1.3 Notifications 22 VLR Functional Entities 22 5.6.1 Managed Object Classes in VLR . 22 5.6.1.1 tracedForeignSubscriberlnVlr 22 5.6.1.2 tracedEquipmentlnVir 22 5.6.1.3 Attributes . 23 5.6.1.3.2 tracedEquipmentlnVlr . 23 5.6.1 .3. 1. tracedForeignSubscriberlnVlr 23 Previous page is
9、blank ETSI GSM*L2.08 94 = 3400855 00040b7 287 H Page 4 GSM 12.08 version 4.0.0 5.6.1.4 Notifications 24 6 7 8 9 10 Trace Types . 24 6.1 MSCIBSS Trace Type 24 6.2 HLR Trace Type 26 Trace Record Contents . 27 7.1 General . 27 7.2 MSC Trace Record Content 29 7.3 BSS Trace Record Content . 31 7.4 HLR Tr
10、ace Record Content . 33 7.5 Trace Record fields . 34 7.5.1 Radio channel information . 34 Creation of Trace Records and Partial Trace Records 35 8.1 General . 35 8.2 Trace Record Control 35 8.2.1 General 35 8.2.2 Attributes . 36 8.2.3 Other Partial Record Criteria 37 Partial Record Structure . 37 8.
11、3.1 Header 37 8.3.2 Record 38 8.3 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 . 40 9.2.3 Log access 40 9.2.4 Event Reporting . 40 Event Forwarding Discriminators . 40 Direct Transfer by Trace Control Function . 40 9.2.4.1 9.2.4
12、.2 Managed Object Model . 41 1 O . 1 Naming Hierarchy . 41 10.2 Inheritance . 41 1 0.3 Object Classes . 42 10.3.1 tracedHomeSubscriberlnHlr . 42 10.3.2 tracedForeignSubscriberlnVlr . 42 10.3.3 tracedEquipmentlnVlr . 43 10.3.4 Trace control . 44 1 0.3.5 Trace log entry 44 1 O . 3.6 Log 45 1 0.3.7 Eve
13、nt Forwarding Discriminators 45 10.4 Attributes 45 10.4.1 traceActivatedlnVlr 45 10.4.2 foreignSubscriberRegisteredInVIr 45 10.4.3 equipmentRegisteredlnVlr 45 10.4.4 mapErrorOnTrace . 46 10.4.5 IMEI 46 10.4.6 IMSI 46 10.4.7 Trace record content 46 10.4.8 Trace control id . 46 10.4.9 Trace record typ
14、e 47 10.4.1 O Trace reference . 47 10.4.11 Trace type 47 ETSI GSM*I2.08 94 3400855 0004068 113 Page 5 GSM 12.08 version 4.0.0 10.4.12 10.4.1 3 10.4.14 10.4.1 5 10.4.1 6 Partial record criteria 47 Timer value . 47 Event type i . 48 Number of events 48 10.4.17 Operational State . 48 10.4.18 Administra
15、tive State 48 1 0.5 Notifications 48 10.5.1 General 48 10.5.2 Trace report 48 tracedHomeSubscriberInHlr-hlrfunction Name Binding . 49 tracedEquipmentlnVlr-vlrfunction Name Binding . 49 traceLogEntry-Log Name Binding . 50 tracecontrol-hlrfunction Name Binding . 50 tracecontrol-mscfunction Name Bindin
16、g . 50 tracecontrol-bssfunction Name Binding 50 Operation system ID 48 10.6 Name Bindings . 49 tracedForeignSubscriberlnVlr-vlrfunction Name Binding 49 10.6.1 10.6.2 10.6.3 10.6.4 10.6.5 10.6.6 10.6.7 11 Syntax . 50 12 . History . 61 ETSI GSMJL2.08 74 = 3400855 O004067 05T Page 7 GSM 12.08 version 4
17、.0.0 Foreword To be drafted by the ElSl Secretariat. Introduction The trace facility enables customer administration and network management to trace the activities of various entities which result in events occurring within the PLMN. This facility should also enable the tracing of all the informatio
18、n 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 0 The identity of the incoming and outgoing circuits of the
19、 nodes involved 0 Supplementary Services invoked 0 All A-lnterface 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“, t
20、he network integrity and also the network 00s 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
21、 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 until the load is decreased or by only producing a sub-set of the information required. Previous page is b
22、lank ETSI GSM*L2.08 94 3400855 0004070 87L Page 9 GSM 12.08 version 4.0.0 1 Scope This ETS specifies the Trace facility for GSM where it refers to: - Subscriber tracing (tracing of IMSI); - Equipment tracing (tracing of IMEI). It does not cover: 0 Types of trace which relate more to network elements
23、 than to individual subscribers e.g. tracing events within a BSS, and so on. 0 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 MMI. 2 (Normative) references This ETS incorporates by dated or
24、 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 incorpora
25、ted in it by amendment or revision. For undated references the latest edition of the publication referred to applies. i11 i21 i31 i41 i51 i61 i71 i81 191 i101 i111 CCITT X227 - IS0 8650: CCITT Rec. X721 - IS0 DIS 101 65-1 : System Management Information Model. CCITT X734 - IS0 DIS 1 O1 64-5: Event R
26、eport Management Function. CCITT X735 - IS0 DIS 1 O1 64-6: Log Control Function. TS GSM 04.08 European digital cellular telecommunication system (Phase 2): Mobile radio interface layer 3 specification. TS GSM 08.06 European digital cellular telecommunication system: Signalling Transport Mechanism sp
27、ecification for the Base Station System - Mobile-services Switching Centre (BSS-MSC) interface. TS GSM 08.08 European digital cellular telecommunication system: Mobile-services Switching Centre - Base Station System (MSC-BSS) interface. TS GSM 08.58 European digital cellular telecommunication system
28、 (Phase 2) : Base Station Controller (BSC) to Base Transceiver Station (BTS) Interface: layer 3 specification. TS GSM 09.02 European digital cellular telecommunication system (Phase 2): Mobile Application Part specification. TS GSM 12.00 European digital cellular telecommunication system (Phase 2):
29、Objectives and Structure of Network Management (NM). TS GSM 12.01 European digital cellular telecommunication system (Phase 2): Common Aspects of GSM Network Management (NM) Previous page is blank ETSI GSM+12.08 94 9 3400855 0004071 708 Page 10 GSM 12.08 version 4.0.0 121 TS GSM 12.02 European digit
30、al cellular telecommunication system (Phase 2): Subscriber, Mobile Equipment (ME) and Services Data Administration. 11 31 TS GSM 12.05 European digital cellular telecommunication system (Phase 2): Subscriber related event and call data. 11 41 TS GSM 12.20 European digital cellular telecommunication
31、system (Phase 2): Network Management (NM) procedures and messages. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of this ETS standard, the following definitions apply: Activation of a Trace: an action taken at the OSF through MMI commands 3 allow a trace record to be prod
32、uced for a particular IMSI or IMEI when an Invocation Event occurs. This equates to “activation of a trace“ in TS GSM 09.02. Invocation of a Trace: an event relating to a particular IMSI or IMEI that occurs in the network that causes a trace record to be created in circumstances where trace has been
33、 activated for that IMSI or IMEI. This equates to “tracing subscriber activity“ in TS GSM 09.02, Active Pending: the state of ;I- activated trace is called Active Pending in a particular NE when the subscriber or equipment being rrciced is not registered in that NE. 3.2 Symbols None. 3.3 Abbreviatio
34、ns For all abbreviations used in this specification refer to TS GSM 01.04. 4 Trace overview Fig 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. ETSI GSM*12.08 94 m 3400855 0004072 64
35、4 m Page 11 GSM 12.08 version 4.0.0 MSC A r Il- 12.08 Tm 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
36、 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
37、; c) d) Trace Type; e) HLR Trace Type. OMC-Id of the destination OMC; 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 m
38、essage (MAP-ACTIVATE-TRACE-MODE). When the HPLMN subscriber trace is activated, a trace record will be created by MSC A , MSC BI, HLR or BSS when certain invoking events occur .e. MOC, MTC, SS-Action, SMS-MO, SMS-MT, Location Update, IMSI attach and detach. The trace action and record layout is defi
39、ned by the trace type parameters. 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 th
40、e 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
41、active in the HPLMN VLRs. All trace records created in the HLR, VLR, BSS and MSC are forwarded to the OSF either as notifications and/or with bulk transfer, as defined in the trace type parameters. The trace is deactivated by using the management function Deactivate Home Subscriber Trace in the HLR.
42、 This request includes the trace parameters in the following list: ETSI GSM*L2-08 94 3400855 0004075 353 Page 14 GSM 12.08 version 4.0.0 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 registered vi
43、a 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 This scenario is identical to the previous scenario with the exception that the only records generated come from the HLR
44、. 5.2.4 In order to trace the IMSls of roaming subscribers in own PLMN, a list of those IMSls plus the associated subscriber trace parameters must be stored in the VLR. The operator may activate a trace for any foreign roaming IMSI from an OSF by invoking the management function Activate Foreign Sub
45、scriber 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: PLMN Operator traces the HLR activities of own IMS
46、I roaming in a VPLMN. PLMN Operator wishes to trace foreign subscribers (IMSI) in own PLMN a) IMSI to be traced; b) Trace Reference; c) dl Trace Type. OMC-Id of the destination OMC; The trace request is stored in an object in the VLR. If VLR area the VPLMN subscriber trace will be activated. For eac
47、h IMSI only one foreign subscriber trace can requests being rejected. All trace records created in the HLR, MSC A, MSC B the subscriber subsequently roams into the be active in a particular VLR, subsequent and BSS are forwarded to the OSF either as notifications andlor with bulk transfer, as defined
48、 in the trace parameters. 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-INVOKETRACE message from the MSC to
49、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 trace type is “No BSS Trace“, the MSC does not send a BSSMAP MSC-INVOKE-TRACE to the BSC. 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: al IMSI; b) Trace Reference. ETSI GSM*L2*08 94 3400855 000Y07b 29T Page 15 GSM 12.08 version 4.0.0 TMN Management Functions required for trace activation (in VL
