1、 ETSI TS 132 152 V13.1.0 (2016-04) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire (3GPP TS 32.152
2、 version 13.1.0 Release 13) TECHNICAL SPECIFICATION ETSI ETSI TS 132 152 V13.1.0 (2016-04)13GPP TS 32.152 version 13.1.0 Release 13Reference RTS/TSGS-0532152vd10 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 S
3、iret N 348 623 562 00017 - NAF 742 C Association but non 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.
4、 The content of any electronic and/or print versions of 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 Port
5、able Document Format (PDF) version kept on a specific 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 https:/porta
6、l.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the 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
7、 or mechanical, including photocopying and microfilm except as authorized 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 Telecommu
8、nications Standards Institute 2016. 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 t
9、he GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 132 152 V13.1.0 (2016-04)23GPP TS 32.152 version 13.1.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertain
10、ing to these 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 Secretari
11、at. Latest updates are available on the ETSI Web server (https:/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 th
12、e ETSI Web server) 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
13、, UMTS identities 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. Modal verbs terminology In the present document “sh
14、all“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “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 use
15、d in direct citation. ETSI ETSI TS 132 152 V13.1.0 (2016-04)33GPP TS 32.152 version 13.1.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2
16、Abbreviations . 7g34 Requirements 7g35 Model Elements and Notations 8g35.1 Basic model elements . 8g35.1.1 attribute . 8g35.1.2 aggregation . 8g35.1.3 operation . 8g35.1.4 association and association name 8g35.1.5 realization relationship 9g35.1.6 generalization relationship 9g35.1.7 dependency rela
17、tionship . 9g35.1.8 note . 9g35.1.9 multiplicity, a.k.a. cardinality . 10g35.1.10 rolename . 10g35.1.11 Xor constraint . 10g35.2 Stereotype . 11g35.2.1 . 11g35.2.1.1 Sample. 11g35.2.2 Void 12g35.2.3 . 12g35.2.3.1 Sample . 12g35.2.4 . 12g35.2.4.1 Sample . 12g35.2.5 . 13g35.2.5.1 Sample . 13g35.2.6 an
18、d 13g35.2.6.1 Sample for target . 14g35.2.6.2 Sample for target 14g35.2.7 . 15g35.2.7.1 Sample . 15g35.2.8 Void 15g35.2.9 . 15g35.2.9.1 Sample. 15g35.2.10 15g35.2.10.1 Sample. 16g35.2.11 16g35.2.11.1 Sample . 16g35.2.12 . 16g35.2.12.1 Sample . 16g35.2.13 . 17g35.2.13.1 Sample . 17g35.3 Void 17g35.4
19、Association classes . 17g35.4 Association classes . 18g3ETSI ETSI TS 132 152 V13.1.0 (2016-04)43GPP TS 32.152 version 13.1.0 Release 135.5 Abstract Class . 19g35.5.1 Sample 19g3Annex A (informative): Samples of using to model Link related IOCs . 20g3A.1 First Sample 20g3A.2 Second Sample . 21g3X.Y.1
20、 AsFunction 21g3X.Y.1.1 Definition 21g3Annex B (normative): Application of and . 22g3Annex C (informative): Change history . 23g3History 24g3ETSI ETSI TS 132 152 V13.1.0 (2016-04)53GPP TS 32.152 version 13.1.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Par
21、tnership 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 the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an in
22、crease 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 approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancem
23、ents, 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 of a TS-family covering the 3rdGeneration Partnership Project; Technical Specification Group Services and System Aspects; Te
24、lecommunication management; as identified below: TS 32.150: Integration Reference Point (IRP) Concept and definitions TS 32.151: Integration Reference Point (IRP) Information Service (IS) template TS 32.152: Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML)
25、repertoire TS 32.153 Integration Reference Point (IRP) technology specific templates TS 32.154 Backward and Forward Compatibility (BFC); Concept and definitions TS 32.155 Requirements template ETSI ETSI TS 132 152 V13.1.0 (2016-04)63GPP TS 32.152 version 13.1.0 Release 131 Scope 3GPP SA5 has chosen
26、UML to capture systems behaviour in the IRP IS context. UML provides a rich set of concepts, notations and model elements to model distributive systems. Usage of all UML notations and model elements is not necessary for the purpose of IRP IS specifications. This TS documents the necessary and suffic
27、ient set of UML notations and model elements, including the ones built by the UML extension mechanism , for use by 3GPP IRP IS authors. Collectively, this set of notations and model elements is called the 3GPP IRP IS modelling repertoire. The selection of the UML notations and model elements in this
28、 repertoire is based on the needs of the existing 3GPP IRP IS specifications. Future IRP IS releases may require the use of additional UML notations or model elements. IRP IS specifications shall employ the UML notation and model elements of this repertoire and may also employ other UML notation and
29、 model elements considered necessary. However, before any other UML notation and model elements may be employed in an approved 3GPP IRP specification, the other notation and model elements should be agreed for inclusion first in this repertoire. 2 References The following documents contain provision
30、s 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. For a non-specific reference,
31、 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 management; Principles and high l
32、evel requirements“. 2 3GPP TS 32.102: “Telecommunication management; Architecture“. 3 3GPP TS 32.150: “Telecommunication management; Integration Reference Point (IRP) Concept and definitions“. 4 3GPP TS 32.151: “Telecommunication management; Integration Reference Point (IRP) Information Service (IS)
33、 template“. 5 OMG: “Unified Modelling Language Specification, Version 1.5“. http:/www.omg.org/spec/UML/1.5/ 6 3GPP TS 32.602 “Telecommunication management; Configuration Management (CM); Basic CM Integration Reference Point (IRP): Information Service (IS)“. 7 3GPP TS 32.612: “Telecommunication manag
34、ement; Configuration Management (CM); Bulk CM Integration Reference Point (IRP): Information Service (IS)“. 8 3GPP TS 32.302: “Telecommunication management; Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)“. 9 3GPP TS 32.404: “Telecommunication
35、management; Performance Management (PM); Performance measurements - Definitions and template“. 10 3GPP TS 32.300: “Name convention for Managed Objects”. ETSI ETSI TS 132 152 V13.1.0 (2016-04)73GPP TS 32.152 version 13.1.0 Release 133 Definitions and abbreviations 3.1 Definitions For the purposes of
36、the present document, the terms and definitions given in 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.150 3 and the following apply: Distinguished Name: See 3GPP TS 32.300 10. IRPAgent: See 3GPP TS 32.150 3. IRPManager: See 3GPP TS 32.150 3. Naming attribute: See 3GPP TS 32.300 10. Notification: S
37、ee 3GPP TS 32.302 8. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TS 32.101 1, 3GPP TS 32.102 2, 3GPP TS 32.150 3 and the following apply: CM Configuration Management DN Distinguished NameGERAN GSM/EDGE Radio Access Network IRP Integration Reference Poi
38、nt IS Information Service NRM Network Resource Model OMG Object Management Group UML Unified Modelling Language (OMG) 4 Requirements IRPAgent can be characterized by several different but related models. The models can be exterior or interior to the IRPAgent. Exterior models are use case models and
39、interior models are object models. Current version of this TS focuses on the interior model aspects of IRPAgents. The notation elements captured in this repertoire shall be used to model all aspects of NRM IRP IS (such as GERAN NRM IRP: IS) and (interface) IRP (such as Alarm IRP: IS). All quotes are
40、 from 5. Capitalized words are defined by various 3GPP IRP IS specifications or the reference 5. ETSI ETSI TS 132 152 V13.1.0 (2016-04)83GPP TS 32.152 version 13.1.0 Release 135 Model Elements and Notations 5.1 Basic model elements UML defined a number of basic model elements. This subclause lists t
41、he selected subset for use in the repertoire. The semantics of the selected ones are defined in 5. 5.1.1 attribute See subclause 3.25 of 5. This sample shows someattributes, listed as strings in the attribute compartment of the class AlarmInformation. 5.1.2 aggregation See subclause 3.43.2.5 of 5. T
42、his sample shows a hollow diamond attached to the end of a path to indicate aggregation. The diamond is attached to the class that is the aggregate. 5.1.3 operation See subclause 3.26 of 5. This sample shows two operations, shown as strings in the operation compartment of class NotificationIRPManage
43、ment, that the instance of NotificationIRPManagement may be requested to perform. The operation has a name, e.g. subscribe and a list of arguments (not shown). 5.1.4 association and association name See subclause 3.41 of 5. These two samples show a binary association between exactly two model elemen
44、ts. The association can include the possibility of relating a model element to itself. The first sample shows a bi-directional association in that each model element is aware of the other. The second sample shows a unidirectional association (shown with an open arrow at the target model element end)
45、 in that only the source model element is aware of the target model element and not vice-versa. Association can be named, such as abcd and label6 in the following samples. AlarmInformationalarmIdnotificationIdclearUserIdother attributes .MscFunctionManagedElementNotificationIRPManagementsubscribe()u
46、nsubscribe()ETSI ETSI TS 132 152 V13.1.0 (2016-04)93GPP TS 32.152 version 13.1.0 Release 135.1.5 realization relationship See subclause 2.5.2.1 of 5. This sample shows the realization relationship between a model element AlarmIRPOperations_1 and another model element, AlarmIRP. The latter (the targe
47、t model element) implements the former. The target model element must be a . 5.1.6 generalization relationship See subclause 3.50 of 5. This sample shows a generalization relationship between a more general element (the IRPAgent) and a more specific element (the IRPAgent_vendor_A) that is fully cons
48、istent with the first element and that adds additional information. 5.1.7 dependency relationship See subclause 3.51 of 5. This sample shows that BClass instances have a semantic relationship with AClass instances. It indicates a situation in which a change to the target element will require a chang
49、e to the source element in the dependency. 5.1.8 note See subclause 3.11 of 5. This sample shows a note, as a rectangle with a “bent corner“ in the upper right corner. The note contains arbitrary text. It appears on a particular diagram and may be attached to zero or more modelling elements by dashed lines. XClas sYClassabcdAClassBClasslabel6AlarmIRPAlarmIRPOperations_1getAlarmList()acknowledgeAlarms()IRPAgentIRPAgent_vendor_AAClassBClassETSI ETSI TS 132 152 V13.1.0 (2016-04)103GPP TS 32.152 version 1
