ETSI TS 132 672-2012 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Telecommunication management Configuration Manageme.pdf

1、 ETSI TS 132 672 V11.0.0 (2012-11) Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Information Service (IS) (3GPP TS 32.672

2、version 11.0.0 Release 11) Technical Specification ETSI ETSI TS 132 672 V11.0.0 (2012-11)13GPP TS 32.672 version 11.0.0 Release 11Reference RTS/TSGS-0532672vb00 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 Si

3、ret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version

4、or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secret

5、ariat. 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 the present document, please send

6、 your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp 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 St

7、andards Institute 2012. All rights reserved. DECTTM, 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

8、are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 672 V11.0.0 (2012-11)23GPP TS 32.672 version 11.0.0 Release 11Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these

9、 essential IPRs, if any, is publicly available for ETSI 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 u

10、pdates are available on the ETSI Web server (http:/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 ser

11、ver) which are, or may be, or may become, essential 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 identit

12、ies or GSM identities. These should be interpreted 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. ETSI ETSI TS 132 672 V11.0.0 (2012-11)33GPP TS 32.672 version 11.

13、0.0 Release 11Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Void 6g35 Information Object Classes (IOCs) 6g35.1 Information entities imported and local la

14、bels . 6g35.2 Class diagram . 6g35.2.1 Attributes and relationships 6g35.2.2 Inheritance 7g35.3 Information object classes definition 7g35.3.1 StateManagementEntity 7g35.3.1.1 Definition 7g35.3.1.2 Attributes . 7g35.4 Information attributes definition . 8g35.4.1 Definition and legal values . 8g3Anne

15、x A (informative): Change history . 9g3History 10g3ETSI ETSI TS 132 672 V11.0.0 (2012-11)43GPP TS 32.672 version 11.0.0 Release 11Foreword This Technical Specification (TS) has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continui

16、ng work within the TSG and may change following formal TSG approval. Should the TSG modify 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 presen

17、ted to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved 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

18、 changes have been incorporated in the document. Introduction The present document is part of a TS-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; as identified below: 32.671: Configuration Management (CM

19、); State Management Integration Reference Point (IRP); Requirements 32.672: Configuration Management (CM); State Management Integration Reference Point (IRP); Information Service (IS) 32.676: Configuration Management (CM); State Management Integration Reference Point (IRP); Solution Set (SS) definit

20、ions Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the 3G network as it evolves. CM actions have the objective to control and monitor the actual configuration on the Network Elements (NEs) and Network Resources (NRs), a

21、nd they may be initiated by the operator or by functions in the Operations Systems (OSs) or NEs. CM actions may be requested as part of a deployment program (e.g. additions and deletions), as part of an optimisation program (e.g. modifications), and to maintain the overall Quality of Service (QoS).

22、The CM actions are initiated either 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 672 V11.0.0 (2012-11)53GPP TS 32.672 version 11.0.0 Release 111 Scope The present document defi

23、nes the Information Service (IS) part of the State Management IRP. It specifies the semantics of the network resource state and status information visible across the Itf-N. It also specifies the interaction required for the management of the state and status information. The state and status attribu

24、tes specified in this document shall be used, where applicable, as attributes in Information Object Class (IOC) definitions of other 3GPP IRPs. When used by the IOC definition, the semantics of the state and status attributes can be qualified and enhanced if deemed necessary. 2 References The follow

25、ing documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply

26、. 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 latest version of that document in the same Release as the present document. 1 3GPP TS 32.101: “Telecommunication ma

27、nagement; Principles and high level requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.300: “Telecommunication management; Configuration Management (CM); Name convention for Managed Objects“. 4 3GPP TS 32.302: “Telecommunication management; Configuration Mana

28、gement (CM); Notification Integration Reference Point (IRP): Information Service (IS)“. 5 3GPP TS 32.312: “Telecommunication management; Generic Integration Reference Point (IRP) management; Information Service (IS)“. 6 3GPP TS 32.600: “Telecommunication management; Configuration Management (CM); Co

29、ncept and high-level requirements“. 7 ITU-T Recommendation X.731: “Information technology - Open Systems Interconnection - Systems Management: State management function“. 8 ITU-T Recommendation X.733: “Information technology - Open Systems Interconnection - Systems Management: Alarm reporting functi

30、on“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TS 32.101 1, 3GPP TS 32.102 2 and 3GPP TS 32.600 6 apply. ETSI ETSI TS 132 672 V11.0.0 (2012-11)63GPP TS 32.672 version 11.0.0 Release 113.2 Abbreviations For the pu

31、rposes of the present document, the following abbreviations apply: CM Configuration Management EM Element Manager IOC Information Object Class IRP Integration Reference Point IS Information Service (see 3GPP TS 32.101 1) M Mandatory NE Network Element NM Network ManagerNR Network Resource O Optional

32、OMG Object Management Group OS Operations System QoS Quality of Service UML Unified Modelling Language (OMG) 4 Void 5 Information Object Classes (IOCs) 5.1 Information entities imported and local labels Label reference Local label There are no information entities imported. 5.2 Class diagram 5.2.1 A

33、ttributes and relationships This subclause depicts the set of information object classes (IOCs) that encapsulate information within the Generic State Management IRP. The intent is to identify the information required for the State Management IRP implementation of its operations and notification emis

34、sion. This subclause provides the overview of all information object classes in UML. Subsequent subclauses provide more detailed specification of various aspects of these information object classes. ETSI ETSI TS 132 672 V11.0.0 (2012-11)73GPP TS 32.672 version 11.0.0 Release 11StateManagementEntity

35、# operationalState # usageState # administrativeState # alarmStatus # proceduralStatus # availabilityStatus # controlStatus # standbyStatus # unknownStatus 5.2.2 Inheritance There are no inheritance relationships. 5.3 Information object classes definition 5.3.1 StateManagementEntity 5.3.1.1 Definiti

36、on StateManagementEntity is a Archetype, that may represent any IOC defined in the Network Resource Models, e.g. Generic Network Resource Model, Core Network Resource Model, UTRAN Network Resource Model or GERAN Network Resource Model. The attributes defined for this Archetype can be imported and us

37、ed in any IOC of the Network Resource Models, where such attributes are needed. These attributes shall be used in the same way as defined in the ITU-T Recommendation X.731 7 and ITU-T Recommendation X.733 8, unless otherwise stated. That document gives also examples of state diagrams, defining possi

38、ble state transitions when one or more of the state attributes defined here are used in a class. 5.3.1.2 Attributes The following attributes are defined for this information object class. Attribute name Support Qualifier operationalState N/A usageState /administrativeState N/A alarmStatus N/procedur

39、alStatus N/A availabilityStatus /controlStatus N/A standbyStatus /unknownStatus N/A ETSI ETSI TS 132 672 V11.0.0 (2012-11)83GPP TS 32.672 version 11.0.0 Release 115.4 Information attributes definition 5.4.1 Definition and legal values The following table gives the definition and legal values for eac

40、h attribute. Attribute Name Definition Legal Values operationalState It indicates the operational state of the object instance. “It describes whether or not the resource is physically installed and working.“ 7 This attribute is READ-ONLY. “Enabled“, “Disabled“ The meaning of these values is as defin

41、ed in ITU-T Recommendation X.731 7. usageState It indicates the usage state of the object instance. “It describes whether or not the resource is actively in use at a specific instant, and if so, whether or not it has spare capacity for additional users at that instant.“ 7 This attribute is READ-ONLY

42、. “Idle“, “Active“, “Busy“ The meaning of these values is as defined in ITU-T Recommendation X.731 7. administrativeState It indicates the administrative state of the object instance. “It describes the permission to use or prohibition against using the resource, imposed through the management servic

43、es.“ 7 “Locked“, “Shutting down“, “Unlocked“ The meaning of these values is as defined in ITU-T Recommendation X.731 7. alarmStatus It indicates the alarm status of the object instance. This is mapped to the perceived severity of the most severe active alarm associated to the object instance. “Clear

44、ed“, “Indeterminate“, “Warning“, “Minor“, “Major“, “Critical“, The meaning of these values is as defined for the attribute perceived severity in ITU-T Recommendation X.733 8. proceduralStatus It indicates the procedural status of the object instance. A set consisting of zero or more of the following

45、 values: “Initialisation required“, “Not initialised“, “Initialising“, “Reporting“, “Terminating“. The meaning of these values is as defined in ITU-T Recommendation X.731 7. availabilityStatus It indicates the availability status of the object instance. A set consisting of zero or more of the follow

46、ing values: “In test“, “Failed“, “Power off“, “Off line“, “Off duty“, “Dependency“, “Degraded“, “Not installed“, “Log full“ The meaning of these values is as defined in ITU-T Recommendation X.731 7. controlStatus It indicates the control status of the object instance. A set consisting of zero or mor

47、e of the following values: “Subject to test“, “Part of services locked“, “Reserved for test“, “Suspended“ . The meaning of these values is as defined in ITU-T Recommendation X.731 7. standbyStatus It indicates the standby status of the object instance. “Hot standby“, “Cold standby“, “Providing servi

48、ce“, . The meaning of these values is as defined in ITU-T Recommendation X.731 7. UnknownStatus It indicates whether the state of the resource represented by the managed object is unknown. “True“ (state is unknown, the values of the state attributes may not reflect the actual state of the resource);

49、 “False“ (state is known, the values of the state attributes reflect the actual state of the resource). ETSI ETSI TS 132 672 V11.0.0 (2012-11)93GPP TS 32.672 version 11.0.0 Release 11Annex A (informative): Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New Jun 2002 SA_16 SP-020329 - - Submitted to TSG SA #16 for Information 1.0.0 Sep 2002 SA_17 SP-020469 - - Submitted to TSG SA #17 for Approval 2.0.0 5.0.0 Mar 2004 SA_23 SP-040105 - - Automatic upgrade to Rel-6 (no CR) 5.0.0 6.0.0 Mar