ITU-T M 3349-2013 Requirements for service and product lifecycle management across business to business interfaces (Study Group 2)《业务到业务接口的服务和产品生命周期管理的要求研究组2》.pdf

《ITU-T M 3349-2013 Requirements for service and product lifecycle management across business to business interfaces (Study Group 2)《业务到业务接口的服务和产品生命周期管理的要求研究组2》.pdf》由会员分享，可在线阅读，更多相关《ITU-T M 3349-2013 Requirements for service and product lifecycle management across business to business interfaces (Study Group 2)《业务到业务接口的服务和产品生命周期管理的要求研究组2》.pdf（52页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T M.3349TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (03/2013) SERIES M: TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Telecommunications management network Requirements for service and product lifecycle management across business t

2、o business interfaces Recommendation ITU-T M.3349 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 t

3、elephone 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 telecommunication systems and services M.1

4、100M.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.3599Integrated services digital networks M.

5、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.3349 (03/2013) i Recommendation ITU-T M.3349 Requirements for service and product lifecycle management across business to business interfaces Summary Recomme

6、ndation ITU-T M.3349 describes the requirements for service and product lifecycle management across business to business interfaces in support of next generation networks. The requirements are provided using the TMN interface specification methodology described in Recommendation ITU-T M.3020. Histor

7、y Edition Recommendation Approval Study Group 1.0 ITU-T M.3349 2013-03-16 2 Keywords NGN, product, requirement, service, service customer, service provider, supplier/partner. ii Rec. ITU-T M.3349 (03/2013) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized age

8、ncy in the field of telecommunications, information 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

9、 to standardizing telecommunications on a worldwide 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 Recommendati

10、ons is covered by the procedure laid down in WTSA 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 concisene

11、ss to indicate both a telecommunication administration 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

12、 is achieved when all of these mandatory provisions 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. INTE

13、LLECTUAL PROPERTY RIGHTS ITU draws attention to the 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, w

14、hether asserted by ITU members or others outside 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

15、 cautioned that this may not represent the latest information and are therefore strongly urged to 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 permissio

16、n of ITU. Rec. ITU-T M.3349 (03/2013) iii Table of Contents 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 and acronyms 2 5 Conventions 2 6 Concepts and background . 2 7 Requirements 3 7.1 Business level requi

17、rements . 3 7.2 Specification level requirements 13 iv Rec. ITU-T M.3349 (03/2013) Introduction ITU-T has defined the architecture and general principles of next generation networks (NGN). Next generation networks are essentially about delivering new services. The open architecture of NGNs will enab

18、le the creation of new services to be easier and quicker. The service provider can either provide services and products by itself, or assemble services and products provided by its suppliers and partners. The supply chain will become more complex in an NGN environment. During service and product lif

19、ecycle management, the interaction between the service provider and its suppliers and partners will be more frequent and more important. This Recommendation contains the requirements for service and product lifecycle management across business to business interfaces in support of NGNs Rec. ITU-T M.3

20、349 (03/2013) 1 Recommendation ITU-T M.3349 Requirements for service and product lifecycle management across business to business interfaces 1 Scope This Recommendation contains the requirements for service and product lifecycle management across business to business interfaces in support of NGNs. I

21、n general, the lifecycle of services and products includes development, negotiation and sales, implementation, execution, assessment, and decommission phases (See ITU-T M.3050.3). In this Recommendation, the interface focuses only on the interactions between a service provider and its suppliers and

22、partners. In each phase, the exchange of service and product information is required between the service provider and its suppliers and partners across business to business (B2B) interfaces. This Recommendation focuses on the requirements of B2B interfaces which cover all of these phases. The requir

23、ements are provided using the TMN interface specification methodology described in ITU-T M.3020. 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, t

24、he editions 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 current

25、ly valid ITU-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.

26、3020 Recommendation ITU-T M.3020 (2011), 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.3050.3 Recommendation ITU-T M.3050.3 (2007), Enhanced Telecom Operations Map (e

27、TOM) Representative process flows. ITU-T M.3060 Recommendation ITU-T M.3060/Y.2401 (2006), Principles for the Management of Next Generation Networks. ITU-T M.3190 Recommendation ITU-T M.3190 (2008), Shared information and data model (SID). ITU-T M.3320 Recommendation ITU-T M.3320 (1997), Management

28、requirements framework for the TMN X-Interface. ITU-T M.3343 Recommendation ITU-T M.3343 (2007), Requirements and analysis for NGN trouble administration across B2B and C2B interfaces. ITU-T M.3400 Recommendation ITU-T M.3400 (2000), TMN management functions. ITU-T Y.2001 Recommendation ITU-T Y.2001

29、 (2004), General overview of NGN. 2 Rec. ITU-T M.3349 (03/2013) 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 interface ITU-T M.3010 3.1.2 network operator ITU-T M.3343 3.1.3 next generation network (NGN) ITU-T Y.2001 3.1.4 partner IT

30、U-T M.3050.1 3.1.5 product ITU-T M.3050.1 3.1.6 service ITU-T M.3050.1 3.1.7 service customer ITU-T M.3320 3.1.8 service provider ITU-T M.3320 3.1.9 supplier ITU-T M.3050.1 3.2 Terms defined in this Recommendation None. 4 Abbreviations and acronyms This Recommendation uses the following abbreviation

31、s and acronyms: B2B Business to Business NGN Next Generation Network SC Service Customer SLA Service Level Agreement SP Service Provider P/S Partner/Supplier TMN Telecommunications Management Network 5 Conventions In this Recommendation, mandatory requirements are indicated by use of the word “shall

32、“. 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 Concepts and background The open architecture of NGNs will enable the creation of new services to be easier and quicker. Services are developed by a s

33、ervice provider (SP) or its partners/suppliers (P/S), for sale within products. A product is what an SP offers or provides to service customers (SC); a product ALWAYS includes a service component. The same service may be included in multiple products, packaged differently, and have different prices

34、for different products, etc. The supply chain will become more complex and more role types will be involved, e.g., network operators, service customers, service providers, content providers, content aggregators, device manufacturers, etc. The SP can either provide services and products by itself, or

35、 assemble services Rec. ITU-T M.3349 (03/2013) 3 and products provided by its P/Ss. Assembling services refers to when an SP implements a service based on the chosen set of services provided by its P/Ss. An assembled service can be composed of a single service provided by a P/S, with or without any

36、changes, or it can be composed of multiple services provided by different P/Ss. The assembling of products refers to the implementation of an assembly of one or more existing service specifications by an SP. The implementation of a product specification or the creation of a new product is done eithe

37、r from scratch or by creating a new version of an existing one. In this case the P/S may only provide services for an SP, and then the SP assembles them as a product and delivers them to the SC. In another case, an SP may assemble products provided by other P/Ss through contractual agreements where

38、the P/S is the owner and SP takes the role of the customer. The SP may do a combination of the above two cases. In an NGN environment, it will become more common for SPs to assemble services and products provided by its P/S(s), to deliver to its customers. The B2B interfaces for service and product

39、lifecycle management between an SP and its P/S(s) are becoming more frequent and important. This introduces increasing requirements to identify the core interfaces that need to be standardized to enable an SP and its P/S(s) to collaborate with regard to the phases of service and product lifecycle ma

40、nagement. Figure 1 illustrates the roles of B2B interfaces in this Recommendation. M.3349(13)_F01SPPartner/SupplierPartner/SupplierB2B interfaceSCFigure 1 Roles of B2B interfaces for service and product lifecycle management This Recommendation contains the requirements for service and product lifecy

41、cle management across B2B interfaces in support of NGNs. In general, the service and product lifecycle includes the development, negotiation, implementation, execution, assessment and decommissioning phases. In each phase, service and product information needs to be exchanged between an SP and its P

42、/S(s) across B2B interfaces. These open interfaces will permit the interoperability across an SP and its P/S(s). Clear and well understood interfaces can provide a means for creating common practices for service and product lifecycle management across an SP and its P/S(s). The P/S(s) that wish to pa

43、rticipate in the phases of the service and product lifecycle management can enable their service and product by complying with all of the interfaces that are appropriate to the offer that they make. 7 Requirements 7.1 Business level requirements 7.1.1 Requirements The general requirements include: s

44、ervice development service negotiation service implementation service execution service assessment service decommission 4 Rec. ITU-T M.3349 (03/2013) product development product negotiation product implementation product execution product assessment product decommission. 7.1.1.1 Service development

45、REQ-SP-FUN-0101 The SP may send service requirements requests, including service functionalities and features to the P/S(s), so that the P/S(s) can provide appropriate services, or develop new services based on these service requirements. The service requirements information includes service functio

46、n descriptions, service characteristics, etc. REQ-SP-FUN-0102 The P/S shall be able to send service requirements responses to the SP; these contain information of the services available in the P/S that meet the SPs service requirements. The information of service requirements responses includes the

47、service ID, service name, service function description, service version, service owner, etc. REQ-SP-FUN-0103 The SP shall be able to provide the service introduction approval result to the P/S. The resulting information includes the service ID, service name, approval status, approval time, etc. If t

48、he requested service introduction has not been approved, the reason should be indicated. REQ-SP-FUN-0104 The SP shall be able to notify the P/S to test an assembled service (that is, to set up an appointment with its P/S for the service test). The information of service test notification includes th

49、e service ID, test plan description, test start time, etc. REQ-SP-FUN-0105 The SP shall be able to notify the P/S of the service test result. The information of the service test result notification includes the service ID, test result, test completed time, etc. 7.1.1.2 Service negotiation REQ-SP-FUN-0201 If the service has passed the test, the SP shall be able to initiate a request to the P/S for service contract establishment, including commercial and SLA aspects. The SP shall offer contract info