1、 International Telecommunication Union ITU-T M.3348TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2011) SERIES M: TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Telecommunications management network Requirements of the NMS-EMS management interface for NGN service platforms
2、Recommendation ITU-T M.3348 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 transmission systems M.300M.559 International telephone circuits M.56
3、0M.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 telecommunication systems and services M.1100M.1199 Internationa
4、l 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.3599Integrated services digital networks M.3600M.3999 Common chan
5、nel signalling systems M.4000M.4999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T M.3348 (01/2011) i Recommendation ITU-T M.3348 Requirements of the NMS-EMS management interface for NGN service platforms Summary Recommendation ITU-T M.3348 describes the requireme
6、nts of the NMS-EMS management interface for NGN service platforms. The requirements are provided using the TMN interface specification methodology described in Recommendation ITU-T M.3020. History Edition Recommendation Approval Study Group 1.0 ITU-T M.3348 2011-01-13 2 Keywords EMS, interface, NGN,
7、 NMS, requirements, service platform. ii Rec. ITU-T M.3348 (01/2011) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sect
8、or (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 Standardization Assembly (WTSA), which meets every
9、 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 technology which fall within ITU-Ts purview,
10、 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. Compliance with this Recommendation is voluntar
11、y. 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 obligatory language such as “must“ and the n
12、egative 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 implementation of this Recommendation may involve th
13、e 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 of the date of approval of this Recommenda
14、tion, 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 to consult the TSB patent database at http
15、:/www.itu.int/ITU-T/ipr/. ITU 2011 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.3348 (01/2011) iii Table of Contents Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2
16、3.2 Terms defined in this Recommendation . 2 4 Abbreviations 2 5 Conventions 3 6 Requirements 3 6.1 Concepts and background . 3 6.2 Business-level requirements . 5 6.3 Specification-level requirements 8 iv Rec. ITU-T M.3348 (01/2011) Introduction The ITU-T M.370x series of Recommendations defines th
17、e management functions applicable in the network management system-element management system (NMS-EMS) interface which includes object management, state management, notification management, performance management and fault management. These common management functions are network independent. While
18、in NGN environment or in a mixed environment of NGN and non-NGN technologies, there are many kinds of service platforms to provide various services. The management and administration interface for controlling the service platform is proprietary to each vendor currently. The service platform consists
19、 of IT resources (including hardware and software aspects), service support applications and services. IETF has created detailed specifications related to the management of IT resources. Moreover, regarding service platforms, the management and administration to services and the service support appl
20、ications are more significant. The specification of the service support applications and services is seldom covered in the current Recommendations so, it is necessary to specify the NMS-EMS management interface for the NGN service platforms. Rec. ITU-T M.3348 (01/2011) 1 Recommendation ITU-T M.3348
21、Requirements of the NMS-EMS management interface for NGN service platforms 1 Scope This Recommendation defines the requirements for managing service platforms used to introduce new service types (e.g., multimedia service) in NGN. The management functions include monitoring and controlling service su
22、pport applications and services supported by service platforms. The purpose of this Recommendation is to provide a standardized interface to manage these services and service support applications. It is out of the scope of this Recommendation to manage the resources based on which the services are p
23、rovided. Management of service instances is out of the scope of this Recommendation. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions
24、indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are 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
25、-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T M.3010 Recommendation ITU-T M.3010 (2000), Principles for a telecommunications management network. ITU-T M.3020 Recomme
26、ndation ITU-T M.3020 (2010), Management 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 Gener
27、ation Networks. ITU-T M.3703 Recommendation ITU-T M.3703 (2010), Common management services Alarm management Protocol neutral requirements and analysis. ITU-T M.3704 Recommendation ITU-T M.3704 (2010), Common management service Performance management Protocol neutral requirements and analysis. ITU-T
28、 Y.110 Recommendation ITU-T Y.110 (1998), Global Information Infrastructure principles and framework architecture. ITU-T Y.2001 Recommendation ITU-T Y.2001 (2004), General overview of NGN. ITU-T Y.2011 Recommendation ITU-T Y.2011 (2004), General principles and general reference model for next genera
29、tion networks. 2 Rec. ITU-T M.3348 (01/2011) 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 application: ITU-T Y.110. 3.1.2 interface: ITU-T M.3010. 3.1.3 next generation network (NGN): ITU-T Y.2001. 3.1.4 NGN service stratum: ITU-T Y.
30、2011. 3.1.5 operations system (OS): 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 element management function (SEMF): ITU-T M.3060. 3.1.9 service network management function (SNMF): ITU-T M.3060. 3.2 Terms defined in this Recommendation This Recommendati
31、on defines the following terms: 3.2.1 service delivery platform (SDP): A complete environment or system architecture designed to enable rapid, cost efficient service creation, deployment, execution, orchestration and management. 3.2.2 service execution environment: The software and hardware which su
32、pport the execution of the service. The basic environment information of a service includes memory size, disk size, JDK (Java development kit) path, database URI (uniform resource identifier), process priority, etc. 3.2.3 service exposure: An interface provided by the service platform or SDP (servic
33、e delivery platform), through which the user (can be a system or an end user) can use the function of the service. The basic service exposure information includes service URI (service hostname, service port and service path), service access policies (permitted access user, permitted access time, etc
34、.), etc. 3.2.4 service platform: The collection of software and hardware on the server side, which is constructed by the service provider and used to deliver one or more specific services to end users. 3.2.5 service support application: The software which provides the function of the service using t
35、he resource of the service platform. 4 Abbreviations This Recommendation uses the following abbreviations: EMS Element Management System FM Fault Management ID Identifier IT Information Technology JDK Java Development Kit NGN Next Generation Network NMS Network Management System Rec. ITU-T M.3348 (0
36、1/2011) 3 OS Operations System PM Performance Management QoS Quality of Service SDP Service Delivery Platform SEMF Service Element Management Function SEMS Service Element Management System SNMF Service Network Management Function SNMS Service Network Management System URI Uniform Resource Identifie
37、r 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 “should“. Optional requirements are indicated by the use of the word “may“ or “can“. 6 Requirements 6.1 Concepts and background Fig
38、ure 1 indicates the interface addressed in this Recommendation. The interface is a Q interface, through which an agent (SEMS, which refers to the system providing the SEMF, or service platforms providing embedded SEMF) can communicate management information for its managed entities to a manager (SNM
39、S, which refers to the system providing the SNMF). M.3348(11)_F01OS (Managing system)SEMFNMS - EMS interfaceServices platformsSEFServices platformsSEF SEMFOS (Managed system)SNMFFigure 1 The NMS-EMS interface addressed in this Recommendation 4 Rec. ITU-T M.3348 (01/2011) As described in ITU-T Y.2011
40、, the service stratum may involve a complex set of geographically distributed service platforms or in the simple case just the service functions in two end-user sites. The service platforms provide the user services, such as a telephone service, a web service, etc. To provide these services, the app
41、lication support functions and service support functions and related control functions in NGN should be covered by the service platform. The dashed rectangle in Figure 2 shows the functions covered by the service platform in the NGN functional architecture. M.3348(11)_F02ApplicationsANITransport str
42、atumService stratumEnd-userfunctionsOthernetworksNNIUNIApplication support functions and service support functionsService controlfunctionsControl Media ManagementService userprofilesManagementfunctionsFigure 2 Functions covered by the service platform in the NGN functional architecture According to
43、the networks of telecom operators, there are two kinds of service platforms: traditional service platform and service delivery platform (SDP). (Both the service platform and the SDP are viewed as network elements in this Recommendation.) M.3348(11)_F03SEMS_1Serviceplatform_2Service 2Service platform
44、_1Service 1Service supportapplicationsResourcesServiceplatform_nResourcesSNMSService element management functionService networkmanagementfunctionService element management functionService supportapplicationsService nResourcesService element management functionService supportapplicationsFigure 3 Scen
45、ario 1 for management of service platforms Rec. ITU-T M.3348 (01/2011) 5 Figure 3 shows the traditional service platform scenario. Each service platform provides a specific service, and its service element management function (SEMF) is provided either by a dedicated SEMS or by itself. The service ne
46、twork management function (SNMF) is provided by a SNMS. This should be supported. Service platform consists of three aspects: Resources, service support applications and service. Resources are common IT infrastructures of the service platform, which consist of hardware and software. Hardware consist
47、s of network devices, storage devices and servers. Software consists of baseware (e.g., operating system, JAVA virtual machine) and middleware (e.g., database, web server, application server). Service support applications are the system procedures to support the services runtime environments, which
48、consist of service creation, service execution, service exposure, service management, security, etc. In Figure 4, the concept of SDP is introduced, so that multiple services can be provided or flexibly created through this. The SEMF is provided either by a dedicated SEMS or by the SDP itself, and th
49、e SNMF is provided by a SNMS. M.3348(11)_F04SEMS_1Service platform_2Service 2 Service nService platform_1Service 1Service support applicationsSNMSService element management functionService networkmanagementfunctionService delivery platformService x Service yService element management functionService deliveryplatformResourcesFigure 4 Scenario 2 for management of service platforms 6.2 Business-level requirements 6.2.1 Requirements This Recommendation only focuses on the management interface between the m
