ITU-T M 3190-2008 Shared information and data model (SID) (Study Group 4)《分享信息和数据模型(SID)》.pdf

1、 International Telecommunication Union ITU-T M.3190TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (07/2008) SERIES M: TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Telecommunications management network Shared information and data model (SID) Recommendation ITU-T M.3190 ITU-T M

2、-SERIES RECOMMENDATIONS TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Introduction and general principles of maintenance and maintenance organization M.10M.299 International transmission systems M.300M.559 International telephone circuits M.560M.759 Common channel signalling sy

3、stems M.760M.799 International telegraph systems and phototelegraph transmission M.800M.899 International leased group and supergroup links M.900M.999 International leased circuits M.1000M.1099 Mobile telecommunication systems and services M.1100M.1199 International public telephone network M.1200M.

4、1299 International data transmission systems M.1300M.1399 Designations and information exchange M.1400M.1999 International transport network M.2000M.2999 Telecommunications management network M.3000M.3599 Integrated services digital networks M.3600M.3999 Common channel signalling systems M.4000M.499

5、9 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T M.3190 (07/2008) i Recommendation ITU-T M.3190 Shared information and data model (SID) Summary Recommendation ITU-T M.3190 is an introduction to the TM Forum SID analysis model and a specification through reference

6、of the ITU-T subset of SID (the product and service business entities). The SID analysis model scope covers the information required to implement use cases based on the eTOM processes. The SID analysis model is implementation independent, focusing on what the information is and what its relationship

7、s are, not on how these are to be implemented. The SID applies primarily to service providers businesses and engaged stakeholders, e.g., system integrators, independent software vendors and network equipment providers. Source Recommendation ITU-T M.3190 was approved on 14 July 2008 by ITU-T Study Gr

8、oup 4 (2005-2008) under Recommendation ITU-T A.8 procedure. Keywords Data model, information model, methodology, TM Forum, UML. ii Rec. ITU-T M.3190 (07/2008) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, informa

9、tion and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a world

10、wide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WT

11、SA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication adminis

12、tration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisio

13、ns are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to t

14、he possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside

15、of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest

16、 information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2009 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T M.3190 (07/2008) iii CONTENT

17、S Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation. 2 4 Abbreviations 3 5 Conventions 3 6 SID introduction . 3 6.1 SID as an information model 3 6.2 Document structure 5 6.3 Relationship with other Recommendations 6 7 SID Framework

18、 7 7.1 SID framework Level 1 ABEs 8 7.2 ABE categorization 9 8 Product domain. 10 9 Service domain . 12 Appendix I Analysis patterns used in SID 16 I.1 Specification. 16 I.2 Abstract superclass . 16 I.3 Composite. 18 I.4 Role entity 18 I.5 Temporal state entity 19 I.6 Self-relationship . 20 I.7 Enti

19、ty specification characteristic/entity characteristic 21 Appendix II SID document structure 24 Appendix III SID use of UML 25 III.1 UML overview . 25 III.2 Goals of UML. 25 III.3 Why use UML? 25 III.4 UML diagrams 25 III.5 UML diagram classification Static, dynamic, and implementation 26 Appendix IV

20、 SID and the NGOSS views . 28 IV.1 SID life cycle 28 IV.2 SID logical and physical perspective . 30 Appendix V Positioning SID to the ITU-T M.1400-series Recommendations 31 Bibliography. 32 iv Rec. ITU-T M.3190 (07/2008) Rec. ITU-T M.3190 (07/2008) 1 Recommendation ITU-T M.3190 Shared information an

21、d data model (SID) 1 Scope This Recommendation is an introduction to the TM Forum SID analysis model and a specification through reference of the ITU-T subset of SID. The SID analysis model scope covers all of the information required to implement use cases based on the eTOM processes ITU-T M.3050.x

22、; in effect, this means that the SID covers a large proportion of the information needs for a service provider. However, the SID is still being developed and while the documents available today cover a substantial part of a service providers core information needs, they do not cover all of them. The

23、 SID analysis model is implementation independent, focusing on what the information is and what its relationships are, not on how these are to be implemented. The SID applies primarily to service providers businesses and engaged stakeholders: system integrators (SI), independent software vendors (IS

24、V) and network equipment providers (NEP). Parts of the SID may also apply directly to, or be adaptable to, other non-Telco service provider enterprise businesses. The focus of this Recommendation is the product and service business entities. 2 References The following ITU-T Recommendations and other

25、 references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged t

26、o investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document,

27、the status of a Recommendation. ITU-T M.3020 Recommendation ITU-T M.3020 (2007), Management interface specification methodology. ITU-T M.3050.x Recommendations ITU-T M.3050.x-series (2007), Enhanced Telecom Operations Map (eTOM). ITU-T M.3100 Recommendation ITU-T M.3100 (2005), Generic network infor

28、mation model. TMF GB922 TM Forum GB922, Shared Information/Data (SID) Model. Concepts, Principles, and Domains, Release 7.5. TMF GB922A3 TM Forum GB922, Shared Information/Data (SID) Model. Addendum 3 Product Business Entity Definitions, Release 7.5. TMF GB922A4SO TM Forum GB922, Shared Information/

29、Data (SID) Model. Addendum 4SO Service Overview Business Entity Definitions, Release 7.5. 2 Rec. ITU-T M.3190 (07/2008) OMG UML OMG, Unified Modelling Language Specification, Version 1.5. Additional non-normative references can be found in the Bibliography. 3 Definitions 3.1 Terms defined elsewhere

30、This Recommendation uses the following terms defined elsewhere: 3.1.1 aggregate business entity TMF GB922: An Aggregate Business Entity (ABE) is a well-defined set of information and operations that characterize a highly cohesive, loosely coupled set of business entities. 3.1.2 attribute TMF GB922:

31、An attribute is a fact that describes a business entity. 3.1.3 business entity TMF GB922: A Business Entity represents something of interest to the business that may be tangible things (such as a Customer), active things (such as a Customer Order), or conceptual things (such as a Customer Account).

32、Business entities are characterized by attributes and participate in relationships with other business entities. Business entity instances typically move through a well-defined life cycle. 3.1.4 domain TMF GB922: A Domain is a collection of Aggregate Business Entities associated with a specific mana

33、gement area. Domains that make up the SID Framework are consistent with eTOM level 0 concepts. 3.1.5 relationship TMF GB922: A relationship is an association of business interest between two business entities, or between a business entity and itself. 3.2 Terms defined in this Recommendation This Rec

34、ommendation defines the following terms: 3.2.1 information model: An information model for a problem space represents all relevant things, i.e., objects in that problem space along with all of their relevant attributes, and relationships. There may be a number of different relevant viewpoints repres

35、ented for different purposes. An information model is independent of implementation, i.e., independent of platform, language, protocol, etc. For example, it does not represent whether it is defined using CORBA IDL or a XML schema. Not all things (objects) in the information model will result in impl

36、ementation forms. For example, an information model view may be specified for the purpose of communication across management interfaces. However, not all things (objects, attributes, relationships) in that model will be visible across a management interface. The things to be encoded in an implementa

37、tion form will be identified in the information model. 3.2.2 data model: A data model is an encoded form of relevant parts of the information model for a specific platform, language and/or protocol, i.e., this is an implementation view. A data model adds no problem space specific properties, it only

38、 applies encoding and augments the information model with encoding directives. The relevant parts to be encoded for a specific application will be identified in the information model. Rec. ITU-T M.3190 (07/2008) 3 A single information model may give rise to one or more data models. Data models are t

39、ypically designed with respect to the characteristics of the platform, language or protocol. For example, an information model may be represented via a data model defined in CORBA IDL and also a data model defined using a XML schema. 4 Abbreviations This Recommendation uses the following abbreviatio

40、ns: ABE Aggregate Business Entity CMIP Common Management Information Protocol eTOM Enhanced Telecom Operations Map MISM Management Interface Specification Methodology (see ITU-T M.3020) NgOSS New Generation Operations Systems and Software QoS Quality of Service SID Shared Information and Data model

41、SLA Service Level Agreement UML Unified Modelling Language VPN Virtual Private Network 5 Conventions SID is described using UML OMG UML as described in Appendix III. An analysis pattern describes a problem which occurs over and over again, and describes the core of the solution to that problem. Key

42、analysis patterns that have been applied for the modelling of SID are described in Appendix I. 6 SID introduction 6.1 SID as an information model 6.1.1 What it is A common information model will streamline the processes associated with information exchange, both within an enterprise and between the

43、enterprise and its external stakeholders.Having a standard information model provides the following benefits: it allows for simplification of information management, by providing a common terminology and reducing unnecessary variation; it allows for unification of information both within an enterpri

44、se and between enterprises; it provides a bridge between the business and information technology groups by providing definitions that are understandable by the business, but are rigorous enough to be used for software development. These benefits then enable business benefits relating to cost, qualit

45、y, timeliness and adaptability of enterprise operations, allowing an enterprise to focus on value creation for their customers. An information model should model fundamental concepts and not be affected by minor business environment changes like organization restructures. 4 Rec. ITU-T M.3190 (07/200

46、8) The information model should be an enabler of change (new products, processes and ways of doing business), not a blocker to progress. An information model (as opposed to a data model) is an abstraction and only provides a high level view of things of interest to the business. It aids in understan

47、ding the scope and breadth of the business, rather than the depth. An information model is a way of representing and structuring information that has advantages over other common artifacts, as described in Table 1. Table 1 Information model comparison to other artifacts Artefact Artefact limitations

48、 Information model advantage Glossary Hard to understand how the concepts relate An information model links concepts together and provides a visual overview. Descriptive document Often rambling how they are related to one another (associations); key details about those things which help to define th

49、em unambiguously (domain-level attributes). An information model is useful: as a starting point for internal modelling work, applications and messages between software components or database schemas; to help in defining a common business terminology, e.g., for integration activities; to help in business transformation programs; to help in understanding business concepts and their relationships; as a source of inspiration for a new view on traditional practices. 6.1.2 What it is not A