ITU-T M 3347-2012 Requirements for the NGN service activation across the interface between the network management system and the element management system (Study Group 2)《通过网络管理系统和.pdf

1、 International Telecommunication Union ITU-T M.3347TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (05/2012) SERIES M: TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Telecommunications management network Requirements for the NGN service activation across the interface between th

2、e network management system and the element management system Recommendation ITU-T M.3347 ITU-T M-SERIES RECOMMENDATIONS TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Introduction and general principles of maintenance and maintenance organization M.10M.299 International transmi

3、ssion systems M.300M.559 International telephone circuits M.560M.759 Common channel signalling systems 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 te

4、lecommunication systems and services M.1100M.1199 International public telephone network M.1200M.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.359

5、9Integrated services digital networks M.3600M.3999 Common channel signalling systems M.4000M.4999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T M.3347 (05/2012) i Recommendation ITU-T M.3347 Requirements for the NGN service activation across the interface between

6、 the network management system and the element management system Summary Recommendation ITU-T M.3347 describes the requirements for the next generation network (NGN) service activation across the interface between the network management system (NMS) and the element management system (EMS) in the ser

7、vice provisioning business process. The requirements are provided using the telecommunications management network (TMN) interface specification methodology described in Recommendation ITU-T M.3020. The general requirements include subscriber configuration, user configuration, subscribed service conf

8、iguration, user service relation configuration, user service relation update notification and bulk configuration. This Recommendation defines the interface requirements for each configuration function. History Edition Recommendation Approval Study Group 1.0 ITU-T M.3347 2012-05-14 2 Keywords Agent,

9、manager, NGN, OS, requirements, service, service activation, service provider. ii Rec. ITU-T M.3347 (05/2012) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The I

10、TU 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 worldwide basis. The World Telecommunication Standardi

11、zation 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 WTSA Resolution 1. In some areas of information tec

12、hnology 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 administration and a recognized operating agency. Compli

13、ance 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 provisions are met. The words “shall“ or some other obl

14、igatory 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 the possibility that the practice or implementat

15、ion 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 of the Recommendation development process. As o

16、f 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 information and are therefore strongly urged t

17、o consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2013 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.3347 (05/2012) iii Table of Contents Page 1 Scope 1 2 References. 1 3 Def

18、initions 1 3.1 Terms defined elsewhere 1 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conventions 2 6 Concepts and background . 3 7 Requirements 4 7.1 Business level requirements . 4 7.2 Specification level requirements 10 iv Rec. ITU-T M.3347 (05/2012) Introduction

19、ITU-T has described the provisioning function set group which is contained in configuration management ITU-T M.3400. The provisioning function set group consists of procedures which are necessary to bring equipment into service, not including installation. However, the interface between the network

20、management system (NMS) and the element management system (EMS) of the service provisioning has not been defined. With the rapid growth of next generation networks (NGNs) and the expansion of new NGN services, it is more important for the service provider (SP) to improve the end-user experience. Con

21、sequently, it is necessary to define the NMS-EMS interface for service activation in order to improve the automation capability, effectiveness and quality of service provisioning. This Recommendation contains the requirements for the NGN service activation across the NMS-EMS interface. Rec. ITU-T M.

22、3347 (05/2012) 1 Recommendation ITU-T M.3347 Requirements for the NGN service activation across the interface between the network management system and the element management system 1 Scope This Recommendation contains the requirements for the NGN service activation across the interface between the

23、network management system (NMS) and the element management system (EMS) in the service provisioning business process. The requirements are provided using the telecommunications management network (TMN) interface specification methodology described in ITU-T M.3020. 2 References The following ITU-T Re

24、commendations and other 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

25、 therefore encouraged to 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

26、 stand-alone document, the status of a Recommendation. ITU-T F.500 Recommendation ITU-T F.500 (1992), International public directory services. ITU-T M.3010 Recommendation ITU-T M.3010 (2000), Principles for a telecommunications management network. ITU-T M.3020 Recommendation ITU-T M.3020 (2009), Man

27、agement interface specification methodology. ITU-T M.3050.1 Recommendation ITU-T M.3050.1 (2007), Enhanced Telecom Operations Map (eTOM) The business process framework. ITU-T M.3060 Recommendation ITU-T M.3060/Y.2401 (2006), Principles for the Management of Next Generation Networks. ITU-T M.3208.1 R

28、ecommendation ITU-T M.3208.1 (1997), TMN management services for dedicated and reconfigurable circuits network: Leased circuit services. ITU-T M.3400 Recommendation ITU-T M.3400 (2000), TMN management functions. ITU-T M.3702 Recommendation ITU-T M.3702 (2010), Common management services Notification

29、 management Protocol neutral requirement and analysis. ITU-T Y.2001 Recommendation ITU-T Y.2001 (2004), General overview of NGN. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 element management function (EMF) ITU-T M.3060 3.1.2 interf

30、ace ITU-T M.3010 3.1.3 network management function (NMF) ITU-T M.3060 3.1.4 next generation network (NGN) ITU-T Y.2001 2 Rec. ITU-T M.3347 (05/2012) 3.1.5 operations system ITU-T M.3010 3.1.6 Q interface ITU-T M.3010 3.1.7 service ITU-T M.3050.1 3.1.8 service provider ITU-T M.3208.1 3.1.9 subscriber

31、 ITU-T M.3050.1 3.1.10 user ITU-T F.500 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 service activation: The procedure of making a service ready for use, which processes information related to the telecommunications management for the purpose of con

32、figuration and activation of the resources reserved for supporting a specific service instance. 3.2.2 subscribed service: A service instance subscribed by the subscriber. 3.2.3 user service: A service instance configured by the subscriber and assigned to a user. 3.2.4 user service relation: The rela

33、tionship between a user and a user service, which contains the information including user identifier, the service instance identifier, and the user usage preference for the service instance. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: EMF Element M

34、anagement Function NGN Next Generation Network NMF Network Management Function OS Operations System OSF Operations Systems Function QoS Quality of Service RMF Resource Management Function SLA Service Level Agreement SMF Service Management Function SP Service Provider SRM Service Resource Management

35、SRMF Service Resource Management Function TMN Telecommunications Management Network TRMF Transport Resource Management Function 5 Conventions In this Recommendation, mandatory requirements are indicated by the use of the word “shall“. Desirable requirements are indicated by the use of the word “shou

36、ld“. Optional requirements are indicated by the use of the word “may“ or “can“. Rec. ITU-T M.3347 (05/2012) 3 6 Concepts and background The “service“ used in this Recommendation refers to “service instance“ in all the cases. In the NGN management functional view reference to ITU-T M.3060, the servic

37、e provisioning is supported by several operations systems functions (OSFs) laid in different management layers. The service management function (SMF) is dedicated to service management and manages the service life cycles and service profiles. Each service profile expresses the transport and service

38、resources requirements needed to activate the service and the underlying service resource management function (SRMF) and transport resource management function (TRMF) map these requirements into network parameters of the underlying network elements. The SMF also manages the service and transport res

39、ources required for enabling the activation of services according to the subscription contract, including the required connectivity and its associated characteristics: bandwidth, quality of service (QoS), and level of subscriber line access (SLA). All management functions in SMF are resource/technol

40、ogy independent and will not provide any technical knowledge on the underlying resources involved in the provisioning of services to the customers: no information about transport or service platforms is available through service management functions. The SMF relies on the SRMF and TRMF to map its se

41、rvice-oriented view and information to the required entities in the appropriate NGN resources. The network management function (NMF) interprets the requirements from the SMF into network parameters of the underlying network elements and performs service activation action through the element manageme

42、nt function (EMF) to activate the related resources for a specific service. Figure 1 shows the interface addressed in this Recommendation. The operations system (OS) (managing system) realizes the service activation related function of the NMF and the OS (managed system) realizes the service activat

43、ion related function of the EMF. The interface is a Q interface. Figure 1 The NMS-EMS interface addressed in this Recommendation This Recommendation defines the requirements for the NGN service activation across the NMS-EMS interface in the service provisioning business process. The subscriber is an

44、 entity that can subscribe some services for an SP. The subscribed service must be activated in the SPs network before it can be used; this process has been illustrated in the above paragraphs of this clause. A subscriber is associated with one or more users, who actually use the service. A subscrib

45、er needs to assign services to users, and a service assigned to a user is a user service. As users can have different usage preference for a service, the user service relationship is used to record this requirement. To support the service activation process, the information about the 4 Rec. ITU-T M.

46、3347 (05/2012) subscriber, user, subscribed service and user service need to be configured in the managed system through the interface addressed in this Recommendation. The service in the managed system can be configured by the user after activation for usage preference via the telecommunication net

47、work, and if the managing system wants to receive updated information on the user service relation, it can subscribe to the managed system for notification of updates of the user service relation. 7 Requirements 7.1 Business level requirements 7.1.1 Requirements The general requirements include: Sub

48、scriber configuration User configuration Subscribed service configuration User service relation configuration User service relation update notification Bulk configuration Non-functional requirements 7.1.1.1 Subscriber configuration REQ-SA-FUN-101 The managing system shall be able to request the mana

49、ged system to create a new subscriber with the subscribers identification. The managed system shall return the creation result. The subscribers identification cannot be modified after creation. The information of a specific subscriber includes subscriber ID, subscriber name, subscriber type (organization, individual), etc. REQ-SA-FUN-102 The managing system shall be able to request the managed system to modify the existing subscribers information identified by the subscribers identification. The in