TS-3GA-32.690(Rel10)v10.0.0 Telecommunication management; Inventory Management (IM); Requirements



Similar documents
TS-3GA (Rel7)v7.0.0 Telecommunication management; File Transfer (FT) Integration Reference Point (IRP): Requirements

Mobile Device Manager Admin Guide. Reports and Alerts

Nuance Healthcare Services Project Delivery Methodology

expertise hp services valupack consulting description security review service for Linux

Document Management Versioning Strategy

Customer no.: enter customer no. Contract no.: enter contract no.

9 ITS Standards Specification Catalog and Testing Framework

Information paper Reference Data Management Service

Version: Modified By: Date: Approved By: Date: 1.0 Michael Hawkins October 29, 2013 Dan Bowden November 2013

Request for Resume (RFR) CATS II Master Contract. All Master Contract Provisions Apply

Firewall Protection Profile

A96 CALA Policy on the use of Computers in Accredited Laboratories Revision 1.5 August 4, 2015

Chorus UFB Services Agreement Bitstream Services: Service Description for UFB Handover Connection

SBClient and Microsoft Windows Terminal Server (Including Citrix Server)

Wireless Nurse Calling System Technical Document

Guidelines on Data Management in Horizon 2020

LINCOLNSHIRE POLICE Policy Document

CERTIFICATION CRITERIA

HP ValuPack Consulting Description OpenVMS Engineering Change Order (ECO) Patch List

Service Level Agreement (SLA) Hosted Products. Netop Business Solutions A/S

Knowledge Base Article

Managed Firewall Service Definition. SD007v1.1

HP ExpertOne. HP2-T21: Administering HP Server Solutions. Table of Contents

NC3A SOA Techwatch Day Call for Presentations

CS 360 Software Development Spring 2008 Tuesdays and Thursdays 3:30 p.m. 4:45 p.m.

HP ValuPack Consulting Description Red Hat Linux System Performance Monitoring & Tuning

Importance and Contribution of Software Engineering to the Education of Informatics Professionals

How To Manage Aio Cms

Loss Share Data Specifications Change Management Plan

CORE 8 to 9 Data Migration Guide

Datasheet. PV4E Management Software Features

Internet Service Definition. SD012v1.1

MaaS360 Cloud Extender

WinFlex Web Single Sign-On (EbixLife XML Format) Version: 1.5

This guide is intended for administrators, who want to install, configure, and manage SAP Lumira, server for BI Platform

Appendix A Page 1 of 5 DATABASE TECHNICAL REQUIREMENTS AND PRICING INFORMATION. Welcome Baby and Select Home Visitation Programs Database

Schedule 2b. additional terms for Managed Video Service 1. SERVICE DESCRIPTION

THOMSON REUTERS C-TRACK CASE MANAGEMENT SYSTEM SOFTWARE AS A SERVICE SERVICE DEFINITION FOR G-CLOUD 6

HP Point of Sale FAQ Warranty, Care Pack Service & Support. Limited warranty... 2 HP Care Pack Services... 3 Support... 3

CHANGE MANAGEMENT STANDARD

Regions File Transmission

Customer Service Description

4394 Gazzetta tal-gvern ta Malta MINISTRY OF FINANCE. Value Added Tax Department. Fiscal Cash Register Specifications

IMT Standards. Standard number A GoA IMT Standards. Effective Date: Scheduled Review: Last Reviewed: Type: Technical

Improved Data Center Power Consumption and Streamlining Management in Windows Server 2008 R2 with SP1

UNIVERSITY OF CALIFORNIA MERCED PERFORMANCE MANAGEMENT GUIDELINES

ROSS RepliWeb Operations Suite for SharePoint. SSL User Guide

Data Warehouse Scope Recommendations

SPECIFICATION. Hospital Report Manager Connectivity Requirements. Electronic Medical Records DRAFT. OntarioMD Inc. Date: September 30, 2010

G-CLOUD FRAMEWORK SERVICE DEFINITION. Solution Architecture for Cloud Service. Copyright: point6 Ltd

Systems Support - Extended

The actions discussed below in this Appendix assume that the firm has already taken three foundation steps:

Newborn Blood Spot Failsafe Solution (NBSFS) Operational Level Agreements. Part B: Child Health Record Department (CHRD) Users

FUJITSU Software ServerView Suite ServerView PrimeCollect

Support Services. v1.19 /

3GPP TS V8.0.0 ( )

STIOffice Integration Installation, FAQ and Troubleshooting

BRILL s Editorial Manager (EM) Manual for Authors Table of Contents

ITIL Release Control & Validation (RCV) Certification Program - 5 Days

BackupAssist SQL Add-on

Pexip Infinity and Cisco UCM Deployment Guide

Solving the Patch Management Dilemma Using SCCM 2007

Wireless Light-Level Monitoring

Overview of ETS in Committee T1

Implementing SQL Manage Quick Guide

Template on written coordination and cooperation arrangements of the supervisory college established for the <XY> Group/<A> Institution

1.2 Supporting References For information relating to the Company Hardware Request project, see the SharePoint web site.

Projects Director Report Guidelines. IPMA Level A

BES12 Jumpstart Program Description ( Jumpstart Program Description )

LeadStreet Broker Guide

Service Level Agreement

Government of Malta. Reference: GMICT X :2014 Version: 7.0. Effective: 07 January 2014

Software and Hardware Change Management Policy for CDes Computer Labs

Traffic monitoring on ProCurve switches with sflow and InMon Traffic Sentinel

April 29, 2013 INTRODUCTION ORGANIZATIONAL OVERVIEW PROJECT OVERVIEW

1)What hardware is available for installing/configuring MOSS 2010?

Software Quality Assurance Plan

BME Smart-Colo. Smart-Colo is a solution optimized for colocating trading applications, built and managed by BME.

HOWTO: How to configure SSL VPN tunnel gateway (office) to gateway

ScaleIO Security Configuration Guide

HP ValuPack Consulting Description Storage Library System Disaster Recovery Audit ValuPack

Information Services Hosting Arrangements

edoc Lite Recruitment Guidelines

HP ValuPack Consulting Description ABS Media/Device Management Server Install

LogMeIn Rescue Web SSO via SAML 2.0 Configuration Guide

CSC IT practix Recommendations

TS-3GB-S.R v1.0 VoIP Supplementary Services Descriptions: Call Forwarding - Unconditional

Design for securability Applying engineering principles to the design of security architectures

Implementing an electronic document and records management system using SharePoint 7

White Paper for Mobile Workforce Management and Monitoring Copyright 2014 by Patrol-IT Inc.

Restricted Document. Pulsant Technical Specification

Annex 3. Specification of requirement. Surveillance of sulphur-emissions from ships in Danish waters

The Whole of Government Approach: Models and Tools for EGOV Strategy & Alignment

WatchDox Server. Administrator's Guide. Version 3.8.5

TELE GREENLAND A/S (Referred to as TELE-POST) Wholesale Data Services. Annex C6. National IP Service. Service Description

Adobe Sign. Enabling Single Sign-On with SAML Reference Guide

FINRA Regulation Filing Application Batch Submissions

Health Care Solution

Symantec User Authentication Service Level Agreement

Transcription:

TS-3GA-32.690(Rel10)v10.0.0 Telecmmunicatin management; Inventry Management (IM); Requirements 2011 年 6 月 22 日 制 定 一 般 社 団 法 人 情 報 通 信 技 術 委 員 会 THE TELECOMMUNICATION TECHNOLOGY COMMITTEE

本 書 は 一 般 社 団 法 人 情 報 通 信 技 術 委 員 会 が 著 作 権 を 保 有 しています 内 容 の 一 部 又 は 全 部 を 一 般 社 団 法 人 情 報 通 信 技 術 委 員 会 の 許 諾 を 得 ることなく 複 製 転 載 改 変 転 用 及 びネットワーク 上 での 送 信 配 布 を 行 うことを 禁 止 します

TS-3GA-32.690(Rel10)v10.0.0 Telecmmunicatin management; Inventry Management (IM); Requirements < 参 考 > [Remarks] 1. 英 文 記 述 の 適 用 レベル [Applicatin level f English descriptin] 適 用 レベル [Applicatin level]:e2 本 標 準 の 本 文 付 属 資 料 および 付 録 の 文 章 および 図 に 英 文 記 述 を 含 んでいる [English descriptin is included in the text and figures f main bdy, annexes and appendices.] 2. 国 際 勧 告 等 の 関 連 [Relatinship with internatinal recmmendatins and standards] 本 標 準 は で 承 認 された Technical Specificatin 32.690 (Versin 10.0.0) に 準 拠 している [This standard is standardized based n the Technical Specificatin 32.690 (Versin 10.0.0) apprved by.] 3. 上 記 国 際 勧 告 等 に 対 する 追 加 項 目 等 [Departures frm internatinal recmmendatins] 原 標 準 に 対 する 変 更 項 目 [Changes t riginal standard] 原 標 準 が 参 照 する 標 準 のうち TTC 標 準 に 置 き 換 える 項 目 [Standards referred t in the riginal standard, which are replaced by TTC standards.] 原 標 準 が 参 照 する 標 準 のうち それらに 準 拠 した TTC 標 準 等 が 制 定 されている 場 合 は 自 動 的 に 最 新 版 TTC 標 準 等 に 置 き 換 え 参 照 するものとする [Standards referred t in the riginal standard shuld be replaced by derived TTC standards.] 4. 工 業 所 有 権 [IPR] 本 標 準 に 関 わる 工 業 所 有 権 等 の 実 施 の 権 利 に 係 る 確 認 書 の 提 出 状 況 は TTCホームページによる [Status f Cnfirmatin f IPR Licensing Cnditin submitted is prvided in the TTC web site.] 5. 作 成 専 門 委 員 会 [Wrking Grup] 専 門 委 員 会 [ Wrking Grup] i

TS 32.690 V10.0.0 (2011-03) Technical Specificatin 3rd Generatin Partnership Prject; Technical Specificatin Grup Services and System Aspects; Telecmmunicatin management; Inventry Management (IM); Requirements (Release 10) The present dcument has been develped within the 3 rd Generatin Partnership Prject ( TM ) and may be further elabrated fr the purpses f. The present dcument has nt been subject t any apprval prcess by the Organizatinal Partners and shall nt be implemented. This Specificatin is prvided fr future develpment wrk within nly. The Organizatinal Partners accept n liability fr any use f this Specificatin. Specificatins and reprts fr implementatin f the TM system shuld be btained via the Organizatinal Partners' Publicatins Offices.

2 TS 32.690 V10.0.0 (2011-03) Keywrds UMTS, management Pstal address supprt ffice address 650 Rute des Luciles - Sphia Antiplis Valbnne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Internet http://www.3gpp.rg Cpyright Ntificatin N part may be reprduced except as authrized by written permissin. The cpyright and the freging restrictin extend t reprductin in all media. 2011, Organizatinal Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved. UMTS is a Trade Mark f ETSI registered fr the benefit f its members is a Trade Mark f ETSI registered fr the benefit f its Members and f the Organizatinal Partners LTE is a Trade Mark f ETSI currently being registered fr the benefit f its Members and f the Organizatinal Partners GSM and the GSM lg are registered and wned by the GSM Assciatin

3 TS 32.690 V10.0.0 (2011-03) Cntents Frewrd... 4 Intrductin... 4 1 Scpe... 5 2 References... 5 3 Definitins and abbreviatins... 5 3.1 Definitins... 5 3.2 Abbreviatins... 6 4 Inventry Management (IM) cncepts... 7 5 Requirements... 8 5.1 General requirements... 8 5.2 Inventry Management (IM) requirements... 8 Annex A (Infrmative): Examples f Inventry Data... 9 Annex B (Infrmative): Examples f Inventry Infrmatin... 10 Annex C (infrmative): Change histry... 11

4 TS 32.690 V10.0.0 (2011-03) Frewrd This Technical Specificatin has been prduced by the 3 rd Generatin Partnership Prject (). The cntents f the present dcument are subject t cntinuing wrk within the TSG and may change fllwing frmal TSG apprval. Shuld the TSG mdify the cntents f the present dcument, it will be re-released by the TSG with an identifying change f release date and an increase in versin number as fllws: Versin x.y.z where: x the first digit: 1 presented t TSG fr infrmatin; 2 presented t TSG fr apprval; 3 r greater indicates TSG apprved dcument under change cntrl. y the secnd digit is incremented fr all changes f substance, i.e. technical enhancements, crrectins, updates, etc. z the third digit is incremented when editrial nly changes have been incrprated in the dcument. Intrductin The present dcument is part f a TS-family cvering the 3 rd Generatin Partnership Prject; Technical Specificatin Grup Services and System Aspects; Telecmmunicatin management; as identified belw: 32.690: Inventry Management (IM); Requirements 32.691: Inventry Management (IM) netwrk resurces Integratin Reference Pint (IRP); Requirements 32.692: Inventry Management (IM) netwrk resurces Integratin Reference Pint (IRP); Netwrk Resurce Mdel (NRM) 32.696: Inventry Management (IM) netwrk resurces Integratin Reference Pint (IRP); Slutin Set (SS) definitins Inventry Management (IM), in general, prvides the peratr with the ability t assure crrect and effective peratin f the 3G netwrk as it evlves. IM actins have the bjective t cntrl and mnitr the actual equipment cnfiguratin n the Netwrk Elements (NEs) and Netwrk Resurces (NRs), and they may be initiated by the peratr r by functins in the Operatins Systems (OSs) r NEs. IM actins may be requested as part f an implementatin prgramme (e.g. additins and deletins), as part f an ptimisatin prgramme (e.g. mdificatins), and t maintain the verall Quality f Service (QS). The IM actins are initiated either as single actins n single NEs f the 3G netwrk, r as part f a cmplex prcedure invlving actins n many resurces/bjects in ne r several NEs.

5 TS 32.690 V10.0.0 (2011-03) 1 Scpe The present dcument defines, in additin t the requirements defined in [1], [2] and [3], the requirements fr the present IRP: Inventry Management IRP. 2 References The fllwing dcuments cntain prvisins which, thrugh reference in this text, cnstitute prvisins f the present dcument. References are either specific (identified by date f publicatin, editin number, versin number, etc.) r nn-specific. Fr a specific reference, subsequent revisins d nt apply. Fr a nn-specific reference, the latest versin applies. In the case f a reference t a dcument (including a GSM dcument), a nn-specific reference implicitly refers t the latest versin f that dcument in the same Release as the present dcument. [1] TS 32.101: "Telecmmunicatin Management, Principles and high level requirements". [2] TS 32.102: "Telecmmunicatin management; Architecture". [3] TS 32.600: "Telecmmunicatin management; Cnfiguratin Management (CM); Cncept and high-level requirements". [4] TS 32.692: "Telecmmunicatin management; Inventry Management (IM) netwrk resurces Integratin Reference Pint (IRP): Netwrk Resurce Mdel (NRM)". 3 Definitins and abbreviatins 3.1 Definitins Fr the purpses f the present dcument, the fllwing terms and definitins apply. data: any infrmatin r set f infrmatin required t give sftware r equipment r cmbinatins theref a specific state f functinality Element Manager (EM): prvides a package f end-user functins fr management f a set f clsely related types f Netwrk Elements (NEs). These functins can be divided int tw main categries: Element Management Functins fr management f NEs n an individual basis. These are basically the same functins as supprted by the crrespnding lcal terminals. Sub-Netwrk Management Functins that are related t a netwrk mdel fr a set f NEs cnstituting a clearly defined sub-netwrk, which may include relatins between the NEs. This mdel enables additinal functins n the sub-netwrk level (typically in the areas f netwrk tplgy presentatin, alarm crrelatin, service impact analysis and circuit prvisining). Field Replaceable Unit (FRU): An FRU is defined t be a spare part r cmpnent that can be substituted / supplanted r be used t substitute / supplant an existing part r cmpnent in rder t rectify a fault r any ther issue which is identified by the user r technician r a diagnstic prgram. IRP: see TS 32.101 [1]. IRP Infrmatin Mdel: see TS 32.101 [1]. IRP Infrmatin Service: see TS 32.101 [1]. IRP Slutin Set: see TS 32.101 [1].

6 TS 32.690 V10.0.0 (2011-03) Infrmatin Object Class (IOC): Within the cntext f all IRP IS specificatins, IOC is the term used instead f MOC fr a managed bject class. MOC is used n the SS level. See als the definitin f Managed Object. Managed Element (ME): An instance f the Managed Object Class ManagedElement. Managed Object (MO): In the cntext f the present dcument, a Managed Object (MO) is a sftware bject that encapsulates the manageable characteristics and behaviur f a particular Netwrk Resurce. See als the def. f MO in TS 32.101 [1]. The MO is instance f a MO class (MOC) defined in a MIM/NRM. This class, within the cntext f this Infrmatin Service specificatin called Infrmatin Object Class (IOC), has attributes that prvide infrmatin used t characterize the bjects that belng t the class (the term "attribute" is taken frm TMN and crrespnds t a "prperty" accrding t CIM). Furthermre, an MO class can have peratins that represent the behaviur relevant fr that class (the term "peratin" is taken frm TMN and crrespnds t a "methd" accrding t CIM). An MO class may supprt ntificatins that prvide infrmatin abut an event ccurrence within a netwrk resurce. Management Infrmatin Base (MIB): the set f existing managed bjects in a management dmain, tgether with their attributes, cnstitutes that management dmain's MIB. The MIB may be distributed ver several OS/NEs. Management Infrmatin Mdel (MIM): als referred t as NRM - see the definitin belw. There is a slight difference between the meaning f MIM and NRM - the term MIM is generic and can be used t dente any type f management mdel, while NRM dentes the mdel f the actual managed telecmmunicatins Netwrk Resurces (NRs). Netwrk Element (NE): is a discrete telecmmunicatins entity, which can be, managed ver a specific interface e.g. the RNC. Netwrk Manager (NM): prvides a package f end-user functins with the respnsibility fr the management f a netwrk, mainly as supprted by the EM(s) but it may als invlve direct access t the NEs. All cmmunicatin with the netwrk is based n pen and well-standardised interfaces supprting management f multi-vendr and multitechnlgy NEs. Netwrk Resurce Mdel (NRM): a mdel representing the actual managed telecmmunicatins Netwrk Resurces (NRs) that a System is prviding thrugh the subject IRP. An NRM describes Managed Object Classes (MOC), their assciatins, attributes and peratins. The NRM is als referred t as "MIM" (see abve) which riginates frm the ITU-T TMN. 3.2 Abbreviatins Fr the purpses f the present dcument, the fllwing abbreviatins apply: CM Cnfiguratin Management EM Element Manager FM Fault Management IOC Infrmatin Object Class IRP Integratin Reference Pint IS Infrmatin Service (see [1]) ITU-T Internatinal Telecmmunicatin Unin, Telecmmunicatin Standardisatin Sectr MIB Management Infrmatin Base MIM Management Infrmatin Mdel MOC Managed Object Class MOI Managed Object Instance NE Netwrk Element NM Netwrk Manager NR Netwrk Resurce NRM Netwrk Resurce Mdel OMG Object Management Grup OS Operatins System TM Telecm Management TMN Telecmmunicatins Management Netwrk UML Unified Mdelling Language (OMG) UMTS Universal Mbile Telecmmunicatins System

7 TS 32.690 V10.0.0 (2011-03) 4 Inventry Management (IM) cncepts The main task f the 3G netwrk inventry management is t manage netwrk inventry infrmatin abut the varius static resurces f a 3G mbile telecmmunicatin netwrk. It prvides supprt t netwrk planning, t netwrk peratin and maintenance and t wrking craft management. Inventry management functins are distributed ver different layers f a Telecmmunicatins Management Netwrk (TMN). The main task f the inventry management functin at Itf-N is t prvide an efficient access fr netwrk management systems t the static inventry data f all related managed netwrk elements. The basic tasks f the Inventry Management IRP f this release is: t prvide an efficient mechanism enabling IRPManagers t uplad inventry data as fllws: request an IRPAgent t prepare inventry data f a certain part f the current netwrk fr uplading; t check the status f data preparatin in the IRPAgent; t request the IRPAgent t alert the IRPManager when the data preparatin is cmpleted; and t uplad the prepared inventry data; t prvide a standard data frmat s that all IRPManagers and IRPAgents invlved have a cmmn understanding f the upladed inventry data. The inventry data: is static data abut the hardware equipment and firmware units (e.g. line cards, prcessing units, pwer supplies) cnstructing the netwrk elements managed by the cncerned element manager. Static data is the data which: is usually prvided by vendrs and is basically vendr-specific; is basically independent f the peratin status f the related equipment/units; is nt changed frequently during the nrmal peratin; cannt be changed thrugh Itf-N interface; and is basically independent f cnfiguratin management; may either be integrated in the related equipment/units r be assigned t the related equipment/units during the installatin r during peratin; may include data shwing static physical relatins between equipment r units, e.g. card A is in slt B.

8 TS 32.690 V10.0.0 (2011-03) 5 Requirements 5.1 General requirements The present dcument defines requirements fr the IS fr this IRP. As such, capabilities specified here as being required in the IS are nt necessarily required in the prduct implementatin. That which is required in the prduct implementatin will be specified in the IS itself. The fllwing general and high-level requirements apply fr the present IRP: A. IRP-related requirements in TS 32.101 [1]; B. IRP-related requirements in TS 32.102 [2]; C. IRP-related requirements in TS 32.600 [3]. 5.2 Inventry Management (IM) requirements The fllwing requirements shall apply fr Inventry Management ver Itf-N. 1. Inventry data is defined as infrmatin pertaining t Field Replaceable Unit (FRU) hardware, firmware and ptinally sftware units f 3G Netwrks, and shall be manageable. The management f sftware unit infrmatin shuld be similar t the management f hardware and firmware infrmatin. Examples f inventry data and attributes are described in Annex A and Annex B and standardised inventry data fr Itf-N is defined in TS 32.692 [4]. Examples f inventry hardware units may be rack, shelf, slt, circuit pack and physical prt, as lng as they are FRUs. 2. The Inventry hardware infrmatin can be captured as a hierarchy r a flat mdel. In a hierarchical mdel, an inventry unit is cntained by anther inventry unit, thereby creating a cntainment relatinship. 3. It shall be pssible fr the IRPManager t initiate the uplad (IRPAgent t IRPManager) f inventry data ver Itf-N. 4. It shall be pssible t scpe the inventry data t be upladed frm the IRPAgent, e.g. inventry data fr a NdeB, an RNC, r all the NEs managed by the IRPAgent. 5. It shall be pssible t filter the inventry data t be upladed frm the IRPAgent, e.g. HW units f a certain type in the netwrk. 6. It shall be pssible t check the status f an Inventry Management peratin. 7. Interface-N shall supprt a file-based mechanism fr transferring inventry data. 8. The file frmat used fr transferring f bulk inventry data shall include a standard part and shall als allw fr vendr specific representatin f inventry data. The meaning, syntax, units, etc. f the standard part f inventry infrmatin will be specified, e.g. standard fields fr HW bard identity (including versin number f HW/SW/FW), bard type and serial number. 9. A Netwrk Resurce Mdel shall be defined fr the standard part f inventry data. 10. As the files are transferred via a machine-machine interface, the file frmat shall be machine-readable using industry standard tls, e.g. XML r ASN.1 parsers. 11. The file frmat shall be specified by using a standardised language, e.g. the Extensible Mark-up Language (XML). 12. The file frmat shall be independent f the data transfer prtcl used t carry the file frm ne system t anther. 13. The file transfer facility shall be implemented using a file transfer prtcl as defined in TS 32.101 [1]. 14. The identificatin f IOC instances shall be cnsistent with Alarm Reprting and the Netwrk Resurce Mdels used fr Cnfiguratin Management. 15. All inventry units shall be uniquely identifiable.

9 TS 32.690 V10.0.0 (2011-03) Annex A (Infrmative): Examples f Inventry Data Examples f inventry data are described in the fllwing table. The actual standardised inventry data fr Itf-N is defined in TS 32.692 [4]. A Managed Element is als referred t as a Netwrk Element (NE). Inventry data item Descriptin f item Additinal Infrmatin n what an peratr will d with this item Managed Element data Managed Element id Crrespnds t the Managed Element MOC in CM NRM. Managed Element type Crrespnds t the Managed Element MOC attribute in CM NRM. User label Crrespnds t the Managed Element MOC attribute in CM NRM. Vendr name Crrespnds t the Managed Element MOC attribute in CM NRM. SW Versin Crrespnds t the Managed Element MOC attribute in CM NRM. Lcatin name Lcatin f site cntaining Managed Element. Crrespnds t the Managed Useful fr maintenance activity, asset lcatin. Element MOC attribute in CM NRM. HW Versin Infrmatin HW versin infrmatin f all hardware supprting this Managed Element. Serial number Serial number f all hardware supprting this Managed Element. HW unit data HW unit id Uniquely identifies the HW unit (e.g. bard). The HW unit id shall be used fr administering and lcating a unit unambiguusly in an peratr's netwrk HW unit type The type f the HW unit in descriptive frm, e.g. mnemnic. Managed Element id The Managed Element cntaining the HW unit. Crrespnds t the Managed Element MOC in CM NRM. Managed Element type Crrespnds t the Managed Element MOC attribute in CM NRM. User label Crrespnds t the Managed Element MOC attribute in CM NRM. Vendr name Manufacturer/Vendr f HW unit. Serial number Serial number f HW unit. Versin number Versin number f HW unit. Date f Manufacture Date f manufacture f HW unit. Date f last service Date f the last service by the vendr. Unit psitin Psitin f HW unit with reference t rack, shelf and slt id. Useful fr maintenance activity, asset lcatin. FW infrmatin Infrmatin related t FW in HW unit. Tplgy infrmatin Remte unit cnnected t HW unit (e.g. prt infrmatin). Allws an peratr t build up the physical tplgy (cnnectin list) based n prt infrmatin. Crrespnding MOCs in CM NRM Mapping f HW unit t crrespnding MOC(s) in CM NRM. Manufacturer specific data Manufacturer specific prprietary infrmatin fr HW unit. Vendr unit type number Vendr r manufacturer specific number f the HW unit which uniquely identifies the unit type and versin. Shall be used fr maintenance, repair and lgistic purpses and identifies, fr example, replacement units. SW unit data SW unit id Uniquely identifies the SW package The SW unit id shall be used fr administering the SW running in NEs. Vendr name Manufacturer/Vendr f SW unit. Versin number Versin number f SW unit. Manufacturer specific data Manufacturer specific prprietary infrmatin fr SW unit.

10 TS 32.690 V10.0.0 (2011-03) Annex B (Infrmative): Examples f Inventry Infrmatin Examples f inventry data, which represents hardware units, are described in figure B.1. The actual standardised inventry data fr Itf-N is defined in TS 32.692 [4]. Rack Shelf Slt Circuit pack Physical prt Figure B.1: Examples f inventry data that represents hardware unit(s) NOTE: Whether hardware is mdelled as an inventry unit r nt is dependent n such hardware being field replaceable (FRU). Fr example, physical prt and slts are hardware units that shuld be defined as Inventry Units if they are FRUs. If they are nt FRUs, then these shuld be captured as attributes f inventry unit that is field replaceable.

11 TS 32.690 V10.0.0 (2011-03) Annex C (infrmative): Change histry Change histry Date TSG # TSG Dc. CR Rev Subject/Cmment Cat Old New Dec SA_26 SP-040815 -- -- Submitted t SA#26 fr Apprval -- 1.0.0 6.0.0 2004 Nte: The cntent was submitted t SA#21 as 32.681-100 fr Infrmatin. This new TS des nt have the IRP part. Sep SA_29 SP-050461 0001 -- Clarify the inventry data descriptin F 6.0.0 6.1.0 2005 Jun 2007 SA_36 -- -- -- Autmatic upgrade t Rel-7 (n CR) at freeze f Rel-7. Deleted reference -- 6.1.0 7.0.0 t CMIP SS, discntinued frm R7 nwards. Dec SA_42 -- -- -- Upgrade t Release 8 -- 7.0.0 8.0.0 2008 Dec - - - - Update t Rel-9 versin -- 8.0.0 9.0.0 2009 2011-03 - - - - Update t Rel-10 versin (MCC) 9.0.0 10.0.0