ETSI EN 301 251 V4.1.2 (1997-12)

Digital cellular telecommunications system (Phase 2) (GSM); Fault management of the Base Station System (BSS) (GSM 12.11 version 4.1.2)

DEN/SMG-061211P

Digitalni celični telekomunikacijski sistem (faza 2) – Upravljanje okvar za sisteme baznih postaj (BSS) (GSM 12.11, različica 4.1.2)

General Information

• Status: Published
• Publication Date: 30-Dec-1997
• Technical Committee: SMG 6 - Operations & Maintenance
• Current Stage: 12 - Completion
• Due Date: 26-Dec-1997
• Completion Date: 31-Dec-1997
• Ref Project: SIST EN 301 251 V4.1.2:2003 - Digital cellular telecommunications system (Phase 2) (GSM); Fault management of the Base Station System (BSS) (GSM 12.11 version 4.1.2)

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digital cellular telecommunications system (Phase 2) (GSM); Fault management of the Base Station System (BSS) (GSM 12.11 version 4.1.2)33.070.50Globalni sistem za mobilno telekomunikacijo (GSM)Global System for Mobile Communication (GSM)ICS:Ta slovenski standard je istoveten z:EN 301 251 Version 4.1.2SIST EN 301 251 V4.1.2:2003en01-december-2003SIST EN 301 251 V4.1.2:2003SLOVENSKI
STANDARD



SIST EN 301 251 V4.1.2:2003



European Telecommunications Standards InstituteEN 301 251 V4.1.2 (1997-12)European Standard (Telecommunications series)Digital cellular telecommunications system (Phase 2);Fault management of the Base Station System (BSS)(GSM 12.11 version 4.1.2)GLOBAL SYSTEM
FOR MOBILE COMMUNICATIONSRSIST EN 301 251 V4.1.2:2003



EN 301 251 V4.1.2 (1997-12)2GSM 12.11 version 4.1.2ReferenceDEN/SMG-061211P (bl0020dc.pdf)KeywordsDigital cellular telecommunications system,Global System for Mobile communications(GSM), TMNETSI SecretariatPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: [phone]
Fax: [phone]Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88X.400c= fr; a=atlas; p=etsi; s=[e-mail]://www.etsi.frCopyright NotificationNo 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 1997.All rights reserved.SIST EN 301 251 V4.1.2:2003



EN 301 251 V4.1.2 (1997-12)3GSM 12.11 version 4.1.2ContentsIntellectual Property Rights.5Foreword.5Introduction.51Scope.62References.62.1Normative references.72.2Informative references.83Definitions and abbreviations.83.1Definitions.83.2Abbreviations.104General requirements on fault management.114.1Overview of the service components.124.1.1Alarm Surveillance service component.124.1.2Fault Localisation service component.124.1.3Fault Correction service component.124.1.4Testing service component.125Fault management service components.125.1Alarm surveillance.125.1.1The model.145.1.2Threshold Management.155.1.2.1General.155.1.2.2Counter Thresholds.165.1.2.3Gauge thresholds.175.1.2.4Operations.185.1.3Alarm Reporting.185.1.4Log control.195.1.5Alarm summary.205.2Fault localisation.215.3Fault correction.215.4Testing.235.4.1The model.235.4.2Testing requirements.245.4.3Test Categories.255.4.3.1Resource Self Test.255.4.3.2Resource Boundary Test.255.4.3.3Connection Test.255.4.3.4Data Integrity Test.265.4.3.5Loopback Test.265.4.3.6Protocol Integrity Test.265.4.3.7Test-Infrastructure Test.266Fault management functions.266.1Alarm surveillance functions.276.1.1Threshold Management functions.276.1.2Alarm Reporting functions.286.1.3Log control functions.296.1.4Alarm summary functions.306.1.5Alarm surveillance related basic services.306.2Fault localisation functions.326.2.1Alarm report function.326.2.2Test management functions.326.3Fault correction functions.326.4Test management functions.33SIST EN 301 251 V4.1.2:2003



EN 301 251 V4.1.2 (1997-12)4GSM 12.11 version 4.1.26.4.1Functions.336.4.1.1Controlled Test Request function.336.4.1.2Uncontrolled Test Request function.336.4.1.3Resume/suspend Test function.336.4.1.4Terminate Test function.346.4.1.5Test Result function.346.4.1.6Scheduling Conflict Report function.346.4.2Test management related basic functions.347BSS specific fault management functions.347.1BSS specific alarm surveillance functions.357.2BSS specific fault localisation functions.357.3BSS specific fault correction functions.357.4BSS specific testing function.367.5BSS-OS communication failure.36Annex A (normative):BSS specific probable causes.37A.1BSS specific probable causes.37A.2ASN.1 syntax for BSS specific probable cause definitions.40History.43SIST EN 301 251 V4.1.2:2003



EN 301 251 V4.1.2 (1997-12)5GSM 12.11 version 4.1.2Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin ETR 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect ofETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the ETSIWeb server (http://www.etsi.fr/ipr).Pursuant to the ETSI Interim IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. Noguarantee can be given as to the existence of other IPRs not referenced in ETR 314 (or the updates onhttp://www.etsi.fr/ipr) which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) (EN) has been produced by ETSI Special Mobile Group (SMG).National transposition datesDate of adoption of this EN:5 December 1997Date of latest announcement of this EN (doa):31 March 1998Date of latest publication of new National Standardor endorsement of this EN (dop/e):30 September 1998Date of withdrawal of any conflicting National Standard (dow):30 September 1998IntroductionThis EN specifies the requirements and model necessary for the standardised fault management (FM) aspects ofoperation, administration and maintenance (OAM) of a multivendor GSM PLMN.The management of a GSM PLMN follows the systems management model outlined in ITU-T X.701 [5] whichstructures systems management into various aspects. This EN addresses the functional aspects of fault management.Fault management provides the following facilities during the operation and maintenance phases of the PLMN undernormal and failure conditions:-installation and acceptance testing;-putting into service;-keeping the network operational.The structure of this document has been defined taking into consideration two aspects:1)The structured, top-down process of the standardization. A general description of the 'Fault Management' of aNetwork Element (NE) is presented in clause 4. In clause 5, there is a specification of the four fault management'Service Components' and, in clauses 6 and 7, the specification of the 'Functions' which the above servicecomponents are based on.2)The reusability of this specification for other NEs of the PLMN. The requirements in clauses 4, 5 and 6 havebeen specified in a generic way (referring to a generic NE instead of a specific Base Station System) and all BSSspecific management functions are specified separately in clause 7.SIST EN 301 251 V4.1.2:2003



EN 301 251 V4.1.2 (1997-12)6GSM 12.11 version 4.1.2GSM fault management is based upon the context set by GSM 12.00. Principles, concepts and definitions are based onthe M-series of the ITU-T standards (with the exception of the Alarm Surveillance management functions based onQ.821). Where the M-series of standards is not applicable, then the X-series is used as far as possible.1ScopeThis EN describes the fault management of any NE of a GSM PLMN through the Q3 interface, with focus on the BaseStation System (BSS).The OAM of the GSM Public Land Mobile Network (PLMN) is organised and described in terms of TMN ManagementServices. GSM 12.00 describes the architecture and gives a general overview of the OAM services, while the rest of theGSM 12 series gives the detailed specification for each service and other aspects of the OAM.Among all the TMN Management Services listed in GSM 12.00, the following are addressed by this specification:-Management of the BSS (also covered by GSM 12.20).-Restoration and Recovery (also covered by GSM 12.06).This Phase 2 version of GSM 12.11 deals with "Fault Management" aspects of the above services.For the TMN Management Services covered, the following "TMN Management Service Components" have been defined inclause 5:-Alarm surveillance.-Fault localisation.-Fault correction.-Testing.The above TMN Management Service Components are based on several "Management Functions", some of which aredefined in other ITU-T documents (e.g. State Management Functions, Alarm Reporting Functions, etc.), and others whichare specifically defined here, in clauses 6 and 7.For some management functions, the Management Information Model is already provided by some ITU-Trecommendations, GSM 12.00 and GSM 12.20.This EN does not include the GDMO definition of the information model.Although sometimes considered as part of fault management, various administrative policies and procedures such astrouble ticketing and tracking, parts inventory, etc. are not included in this EN. Such aspects may be considered to be theresponsibility of the operator and thus outside the scope of the EN.2ReferencesReferences may be made to:a)specific versions of publications (identified by date of publication, edition number, version number, etc.), inwhich case, subsequent revisions to the referenced document do not apply; orb)all versions up to and including the identified version (identified by "up to and including" before the versionidentity); orc)all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); ord)publications without mention of a specific version, in which case the latest version applies.SIST EN 301 251 V4.1.2:2003



EN 301 251 V4.1.2 (1997-12)7GSM 12.11 version 4.1.2A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.2.1Normative referencesThis EN incorporates, by dated or undated reference, provisions from other publications. These normative references arecited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequentamendments to, or revisions of, any of these publications apply to this EN only when incorporated in it by amendment orrevision. For undated references the latest edition of the publication referred to applies.[1]ITU-T Recommendation M.20: (1992) "Maintenance Philosophy for TelecommunicationNetworks".[2]ITU-T Recommendation M.3100: (1995) "Generic Network information Model".[3]ITU-T Recommendation M.3200: (1992) "TMN Management Services: Overview".[4]ITU-T Recommendation M.3400: (1992) "TMN Management Functions".[5]ITU-T Recommendation X.701 (1992) ½ ISO/IEC 10 040: " Information technology - OpenSystems Interconnection - Systems Management Overview ".[6]ITU-T Recommendation X.721 (1992) ½ ISO/IEC 10 165-2: " Information technology - OpenSystems Interconnection - Structure of management information: Definition of ManagementInformation ".[7]ITU-T Recommendation X.722 (1992) ½ ISO/IEC 10 165-4: "Information technology - OpenSystems Interconnection - Structure of management information: Guidelines for the Definition ofManaged Objects".[8]ITU-T Recommendation X.732 (1992) ½ ISO/IEC 10 164-3: "Information technology - OpenSystems Interconnection - Systems Management: Attributes for representing relationships".[9]ITU-T Recommendation X.733 (1992) ½ ISO/IEC 10 164-4: "Information technology - OpenSystems Interconnection - Systems Management: Alarm Reporting Function".[10]ITU-T Recommendation X.734 (1992) ½ ISO/IEC 10 164-5: "Information technology - OpenSystems Interconnection - Systems Management: Event Report Management Function".[11]ITU-T Recommendation X.735 (1992) ½ ISO/IEC 10 164-6: "Information technology - OpenSystems Interconnection - Systems Management: Log Control Function".[12]ITU-T Recommendation X.737 (1995) ½ (ISO/IEC 10 164-14): "Information technology - OpenSystems Interconnection - Systems Management: Confidence and Diagnostic Test Categories".[13]ITU-T Recommendation X.745 (1994) ½ ISO/IEC 10 164-12: "Information technology - OpenSystems Interconnection - Test Management Function".[14]ITU-T Recommendation X.751 (1995) ½ (ISO/IEC 10 164-17): "Information technology - OpenSystems Interconnection - Change Over Function".[15]ITU-T Recommendation Q.821: (1993) "Q3 Interface for Alarm Surveillance".[16]ETR 100 (GSM 01.04): "Digital cellular telecommunications system (Phase 2); Abbreviations andacronyms".[17]ETS 300 590 (GSM 08.08): "Digital cellular telecommunications system (Phase 2);Mobile-services
Switching Centre Base Station System (MSC-BSS) interface Layer 3specification".[18]ETS 300 612-1 (GSM 12.00): "Digital cellular telecommunications system (Phase 2); Objectivesand Structure of GSM PLMN Management".SIST EN 301 251 V4.1.2:2003



EN 301 251 V4.1.2 (1997-12)8GSM 12.11 version 4.1.2[19]ETS 300 612-2 (GSM 12.01): "Digital cellular telecommunications system (Phase 2); NetworkManagement (NM); Part 2: Common aspects of GSM/DCS 1 800 Network
Management".[20]ETS 300 615 (GSM 12.04): "Digital cellular telecommunications system (Phase 2); Performancedata measurements".[21]ETS 300 617 (GSM 12.06): "Digital cellular telecommunications system (Phase 2); GSM NetworkConfiguration Management".[22]ETS 300 622 (GSM 12.20): "Digital cellular telecommunications system (Phase 2); Base StationSystem (BSS) Management Information".2.2Informative references1)ITU-T Recommendation M.3010 (1992): "Principles for a Telecommunications ManagementNetwork".2)ITU-T Recommendation X.710 (1991): "Common management information service definition forCCITT applications". ISO/IEC 9 595: "Information technology - Open Systems Interconnection -Common management information service definition" is technically aligned with ITU-T X.710.3)ITU-T Recommendation X.711 (1991): "Common management information protocol specificationfor CCITT applications" ISO/IEC 9 596: "Information technology - Open Systems Interconnection- Common management information protocol specification " is technically aligned with ITU-TX.711.4)ITU-T Recommendation X.725 (1995):½ ISO/IEC 10 165-7: "Information technology - OpenSystems Interconnection - Structure of management information: General Relationship Model".5)ITU-T Recommendation X.731 (1992): ½ ISO/IEC 10 164-2: "Information technology - OpenSystems Interconnection - Systems Management: State Management Function".6)ETS 300 593 (GSM 08.52): "Digital cellular telecommunications system (Phase 2); Base StationController Base Transceiver Station (BSC - BTS) interface; principles".7)ETS 300 596 (GSM 08.58): "Digital cellular telecommunications system (Phase 2); Base StationController - Base Transceiver Station (BSC-BTS) interface Layer 3 specification".8)ETS 300 597 (GSM 08.60): "Digital cellular telecommunications system (Phase 2); Inband controlof remote transcoders and rate adapters for full rate traffic channels".9)ETS 300 623 (GSM 12.21): "Digital cellular telecommunications system (Phase 2); NetworkManagement (NM) procedures and messages on the A-bis interface".10)ETS 300 624 (GSM 12.22): "Digital cellular telecommunications system (Phase 2); Interworkingof GSM Network Management (NM) procedures and messages at the Base Station Controller(BSC)".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following definitions apply:alarm: A notification, of the form defined by the alarm reporting function (ITU-T X.733 [9]), of a specific event.active resource: An active resource in the context of redundancy is equivalent to a primary resource.alarm report: A specific type of event report used to convey alarm information.SIST EN 301 251 V4.1.2:2003



EN 301 251 V4.1.2 (1997-12)9GSM 12.11 version 4.1.2outstanding alarm condition: The state in which the conditions that originated an alarm are still present in the system.anomaly: An anomaly is a discrepancy between the actual and desired characteristics of an item (ITU-T M.20 [1]). Inthe context of this specification, the item may also be external to the NE (e.g.: environmental alarm detector).asymmetric redundancy: A redundancy where the primary and secondary resources have different capabilities, andtherefore cannot exchange their roles (where the secondary may take the primary role, but the primary may not take thesecondary role). Once the faulty primary resource is repaired and restored to service a change back needs to beperformed.back up: A back up resource is a secondary resource providing redundancy to a primary resource.backed up: A backed up resource is a primary resource which has a secondary resource providing redundancy.change-back: A change back is the reverse change over in an asymmetric redundancy to restore the resources into theiroriginal roles.change-over: Change over is the action within a system capable of supporting redundancy which results in a secondaryresource taking over the primary role. In a symmetric redundancy, the primary resource may take the secondary role.cleared Alarm: An alarm notification with the perceived severity set to cleared.cold standby: A secondary resource that requires initialisation activity before it can provide backup capability isdefined as being in a cold standby state (ITU-T X.751 [14]).counter: Counters are a management abstraction of an underlying process, which may be associated with a definedinternal event in management information. The current value of a counter is incremented when this event occurs (seenote). It can take any values in its range. When a counter reaches its maximum value, it wraps around and countsupwards from 0; overflow information is not in general retained. An additional notification may be defined for counterswith wrap behaviour.NOTE:The rule that a counter value can increase only in single increments is a descriptive convention thatsimplifies the description of a counter threshold. It does not imply that it will always be possible toobserve each increment in the counter's range, since the events counted may occur in rapid succession.counter threshold: A counter threshold is the application of the thresholding mechanism to a counter.defect: A defect is a limited interruption in the ability of an item to perform a required function. It may or may not leadto maintenance action depending on the results of additional analysis (M.20 [1]). In the context of this specification, theitem may also be external to the NE (e.g.: environmental alarm detector).duplex redundancy: A duplex redundancy is a redundancy in which a given function can be performed by tworesources: a primary resource and secondary resource (also known as active and standby resources respectively).failure: A failure is the termination of the ability of an item to perform a required function (M.20 [1]). In the context ofthis specification, the item may also be external to the NE (e.g.: environmental alarm detector).NOTE: After a failure, the item has a fault (M.20 [1]).fault: A fault is the inability of an item to perform a required function, excluding that inability due to preventivemaintenance, lack of external resources or planned actions.NOTE: A fault is often the result of a failure of the item itself, but may exist without prior failure (M.20 [1]).gauge: The gauge is the management abstraction of the value of a dynamic variable, such as the number of connectionscurrently operated by a protocol machine or the rate of change of a traffic counter. There is no restriction on what thedynamic variable may represent, within the constraints set out below. The value of the gauge is subject to change ineither direction. The value of the increment or decrement is unconstrained, except that a change that would take thegauge beyond its minimum or maximum value, will leave the gauge value at its minimum or maximum valuerespectively, until it is subsequently again within the gauge range values.gauge threshold: A gauge threshold is the application of the thresholding mechanism to a gauge.hot standby: A secondary resource that is able to provide backup capability for a primary resource without the need forinitialisation activity is defined as being in a hot standby state (X.751 [14]).SIST EN 301 251 V4.1.2:2003



EN 301 251 V4.1.2 (1997-12)10GSM 12.11 version 4.1.2Least Replaceable Unit (LRU): The smallest piece of equipment that can be replaced by field service personnel.N+K redundancy: A redundancy where a given function can be performed by N primary resources and K secondaryresources. When a failure occurs on one of the N primary resources, one of the K secondary resources may take over therole of that faulty primary resource.primary resource: A primary resource (in a system capable of supporting redundancy) is a resource that is performinga given function. On failure of a primary resource a secondary resource may take over the role of the faulty primaryresource. A primary resource may also be referred to as an "active" or "backed up" resource.redundancy: The capability of a system to perform fault tolerant functionality by means of spare resources (or groupsof resources).secondary resource: A secondary resource (in a system capable of supporting redundancy) is a resource that may backup a primary resource. A secondary resource may take over the role of a primary resource on failure of that resource. Asecondary resource may also be referred to as a "standby" or "back up" resource.standby resource: A standby resource in the context of redundancy is equivalent to a secondary resource.symmetric redundancy: A redundancy where the primary and secondary resources have th
...