1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelTelecommInvento(3GPP TS 32.6TECHNICAL SPECIFICATION132 690 V13.0.0 (2016communications system (Phaelecommunications System (LTE; munication management; ntory Management (IM); Requirements .690 version 13.0.0 Release 1316-02) hase 2+); (UMTS); ) ET
2、SI ETSI TS 132 690 V13.0.0 (2016-02)13GPP TS 32.690 version 13.0.0 Release 13Reference RTS/TSGS-0532690vd00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but n
3、on lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions o
4、f the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific
5、network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in t
6、he present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as a
7、uthorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM,
8、 PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Asso
9、ciation. ETSI ETSI TS 132 690 V13.0.0 (2016-02)23GPP TS 32.690 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for E
10、TSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/
11、ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essentia
12、l to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted
13、 as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “w
14、ill“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 132 690 V13.0.0 (2016-02)33GP
15、P TS 32.690 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Inventory Management (IM) concepts . 7g35 R
16、equirements 8g35.1 General requirements . 8g35.2 Inventory Management (IM) requirements 8g3Annex A (Informative): Examples of Inventory Data . 10g3Annex B (Informative): Examples of Inventory Information . 12g3Annex C (informative): Change history . 13g3History 14g3ETSI ETSI TS 132 690 V13.0.0 (2016
17、-02)43GPP TS 32.690 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify
18、 the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG ap
19、proved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part
20、 of a TS-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.690: Inventory Management (IM); Requirements 32.691: Inventory Management (IM) network resources Integration Reference Poin
21、t (IRP); Requirements 32.692: Inventory Management (IM) network resources Integration Reference Point (IRP); Network Resource Model (NRM) 32.696: Inventory Management (IM) network resources Integration Reference Point (IRP); Solution Set (SS) definitions Inventory Management (IM), in general, provid
22、es the operator with the ability to assure correct and effective operation of the 3G network as it evolves. IM actions have the objective to control and monitor the actual equipment configuration on the Network Elements (NEs) and Network Resources (NRs), and they may be initiated by the operator or
23、by functions in the Operations Systems (OSs) or NEs. IM actions may be requested as part of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (e.g. modifications), and to maintain the overall Quality of Service (QoS). The IM actions are initiated either
24、 as single actions on single NEs of the 3G network, or as part of a complex procedure involving actions on many resources/objects in one or several NEs. ETSI ETSI TS 132 690 V13.0.0 (2016-02)53GPP TS 32.690 version 13.0.0 Release 131 Scope The present document defines, in addition to the requirement
25、s defined in 1, 2 and 3, the requirements for the present IRP: Inventory Management IRP. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, ed
26、ition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the late
27、st version of that document in the same Release as the present document. 1 3GPP TS 32.101: “Telecommunication Management, Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.600: “Telecommunication management; Configuration Management
28、 (CM); Concept and high-level requirements“. 4 3GPP TS 32.692: “Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP): Network Resource Model (NRM)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the fo
29、llowing terms and definitions apply. data: any information or set of information required to give software or equipment or combinations thereof a specific state of functionality Element Manager (EM): provides a package of end-user functions for management of a set of closely related types of Network
30、 Elements (NEs). These functions can be divided into two main categories: Element Management Functions for management of NEs on an individual basis. These are basically the same functions as supported by the corresponding local terminals. Sub-Network Management Functions that are related to a networ
31、k model for a set of NEs constituting a clearly defined sub-network, which may include relations between the NEs. This model enables additional functions on the sub-network level (typically in the areas of network topology presentation, alarm correlation, service impact analysis and circuit provisio
32、ning). Field Replaceable Unit (FRU): An FRU is defined to be a spare part or component that can be substituted / supplanted or be used to substitute / supplant an existing part or component in order to rectify a fault or any other issue which is identified by the user or technician or a diagnostic p
33、rogram. IRP: see 3GPP TS 32.101 1. IRP Information Model: see 3GPP TS 32.101 1. IRP Information Service: see 3GPP TS 32.101 1. ETSI ETSI TS 132 690 V13.0.0 (2016-02)63GPP TS 32.690 version 13.0.0 Release 13IRP Solution Set: see 3GPP TS 32.101 1. Information Object Class (IOC): Within the context of
34、all IRP IS specifications, IOC is the term used instead of MOC for a managed object class. MOC is used on the SS level. See also the definition of Managed Object. Managed Element (ME): An instance of the Managed Object Class ManagedElement. Managed Object (MO): In the context of the present document
35、, a Managed Object (MO) is a software object that encapsulates the manageable characteristics and behaviour of a particular Network Resource. See also the def. of MO in TS 32.101 1. The MO is instance of a MO class (MOC) defined in a MIM/NRM. This class, within the context of this Information Servic
36、e specification called Information Object Class (IOC), has attributes that provide information used to characterize the objects that belong to the class (the term “attribute“ is taken from TMN and corresponds to a “property“ according to CIM). Furthermore, an MO class can have operations that repres
37、ent the behaviour relevant for that class (the term “operation“ is taken from TMN and corresponds to a “method“ according to CIM). An MO class may support notifications that provide information about an event occurrence within a network resource. Management Information Base (MIB): the set of existin
38、g managed objects in a management domain, together with their attributes, constitutes that management domains MIB. The MIB may be distributed over several OS/NEs. Management Information Model (MIM): also referred to as NRM - see the definition below. There is a slight difference between the meaning
39、of MIM and NRM - the term MIM is generic and can be used to denote any type of management model, while NRM denotes the model of the actual managed telecommunications Network Resources (NRs). Network Element (NE): is a discrete telecommunications entity, which can be, managed over a specific interfac
40、e e.g. the RNC. Network Manager (NM): provides a package of end-user functions with the responsibility for the management of a network, mainly as supported by the EM(s) but it may also involve direct access to the NEs. All communication with the network is based on open and well-standardised interfa
41、ces supporting management of multi-vendor and multi-technology NEs. Network Resource Model (NRM): a model representing the actual managed telecommunications Network Resources (NRs) that a System is providing through the subject IRP. An NRM describes Managed Object Classes (MOC), their associations,
42、attributes and operations. The NRM is also referred to as “MIM“ (see above) which originates from the ITU-T TMN. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management EM Element Manager FM Fault ManagementIOC Information Object Cla
43、ss IRP Integration Reference Point IS Information Service (see 1) ITU-T International Telecommunication Union, Telecommunication Standardisation Sector MIB Management Information Base MIM Management Information Model MOC Managed Object Class MOI Managed Object Instance NE Network Element NM Network
44、ManagerNR Network Resource NRM Network Resource Model OMG Object Management Group OS Operations System TM Telecom ManagementTMN Telecommunications Management Network UML Unified Modelling Language (OMG) UMTS Universal Mobile Telecommunications System ETSI ETSI TS 132 690 V13.0.0 (2016-02)73GPP TS 32
45、.690 version 13.0.0 Release 134 Inventory Management (IM) concepts The main task of the 3G network inventory management is to manage network inventory information about the various static resources of a 3G mobile telecommunication network. It provides support to network planning, to network operatio
46、n and maintenance and to working craft management. Inventory management functions are distributed over different layers of a Telecommunications Management Network (TMN). The main task of the inventory management function at Itf-N is to provide an efficient access for network management systems to th
47、e static inventory data of all related managed network elements. The basic tasks of the Inventory Management IRP of this release is: to provide an efficient mechanism enabling IRPManagers to upload inventory data as follows: o request an IRPAgent to prepare inventory data of a certain part of the cu
48、rrent network for uploading; o to check the status of data preparation in the IRPAgent; o to request the IRPAgent to alert the IRPManager when the data preparation is completed; and to o upload the prepared inventory data; to provide a standard data format so that all IRPManagers and IRPAgents invol
49、ved have a common understanding of the uploaded inventory data. The inventory data: is static data about the hardware equipment and firmware units (e.g. line cards, processing units, power supplies) constructing the network elements managed by the concerned element manager. Static data is the data which: o is usually provided by vendors and is basically vendor-specific; o is basically independent of the operation status of the related equipment/units; o is not changed frequently during the normal operation; o cannot be changed throug
