ITU-T M 3343-2007 Requirements and analysis for NGN trouble administration across B2B and C2B interfaces (Study Group 4)《B2B和C2B接口NGN故障管理的要求和分析研究组4》.pdf

1、 International Telecommunication Union ITU-T M.3343TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2007) SERIES M: TELECOMMUNICATION MANAGEMENT, INCLUDING TMN AND NETWORK MAINTENANCE Telecommunications management network Requirements and analysis for NGN trouble administration across B2B and C2B

2、 interfaces ITU-T Recommendation M.3343 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 c

3、ircuits 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.1100M.1199

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

5、9 Common channel signalling systems M.4000M.4999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. M.3343 (01/2007) i ITU-T Recommendation M.3343 Requirements and analysis for NGN trouble administration across B2B and C2B interfaces Summary ITU-T Recommendation M.334

6、3 contains the requirements and analysis for trouble administration functions for the business-to-business and customer-to-business interfaces in support of NGN. The requirements and analysis are provided using the TMN interface specification methodology described in ITU-T Recommendation M.3020. Thi

7、s Recommendation differs from existing approved Recommendations on trouble management in that NGN requires product and service flexibility and extensions introduced by new technology for NGN. Trouble type is also configurable and extensible by either the service provider or service customer to suppo

8、rt new products and services. These extensions are introduced to support peer-wise, local, national and regional requirements introduced and described in ITU-T Recommendation M.3050.2 for supplier/partner relationship management introduced by the NGN value-chain. This is needed to support regulatory

9、 and international trade needs. Source ITU-T Recommendation M.3343 was approved on 13 January 2007 by ITU-T Study Group 4 (2005-2008) under the ITU-T Recommendation A.8 procedure. Keywords Analysis, B2B/C2B interface, NGN, requirements, service customer, service provider, trouble report. ii ITU-T Re

10、c. M.3343 (01/2007) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and t

11、ariff 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 four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Reco

12、mmendations 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, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recomm

13、endation, the expression “Administration“ is used for conciseness 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., interoperab

14、ility 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 negative equivalents are used to express requirements. The use of such words does not suggest that com

15、pliance 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 the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validi

16、ty 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 Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be requir

17、ed 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:/www.itu.int/ITU-T/ipr/. ITU 2008 All rights reserved. No part of this publication may be reproduced

18、, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. M.3343 (01/2007) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation. 3 4 Abbreviations and acronyms 4 5 Conventions 4 6 Functional requir

19、ements . 5 6.1 Requirements framework . 5 6.2 Business level requirements . 9 6.3 Specification level requirements 23 7 Analysis 42 7.1 Scope 42 7.2 Use cases 42 7.3 Interface definition . 43 7.4 Information object classes 63 Appendix I ITU-T example of trouble type 84 I.1 Trouble type 84 iv ITU-T R

20、ec. M.3343 (01/2007) Introduction This Recommendation contains the requirements and analysis for the trouble administration function for the business-to-business (B2B) and customer-to-business (C2B) interfaces. From time to time all systems, including communications networks, develop problems or mal

21、functions, referred to in this Recommendation as “troubles“. A “trouble“ in a communications network is a problem that has an adverse effect on the quality of service perceived by network users. When a trouble is detected, possibly as a result of an alarm report, a trouble report may be entered by a

22、 user or the system may raise a report automatically. Management of that trouble report is necessary to ensure that it receives attention and that the trouble is cleared to restore the service to its previous level of capability. At the time of a trouble, a network may have been interworking with an

23、other network to provide a service and the problem or malfunction may be due to the other network. Therefore, it may be necessary to exchange trouble management information between management systems across interfaces which may be client-to-service provider or service provider-to-service provider in

24、terfaces and may represent inter-jurisdictional, as well as intra-jurisdictional, boundaries. In addition to exchanging information on trouble that has already been detected, advance information on service inaccessibility may also need to be exchanged. Thus, a service provider may need to inform a c

25、ustomer of future service inaccessibility (because of planned maintenance, for example). The scope of this Recommendation includes all of the above processes for exchange of management information for NGN to support the B2B and C2B interfaces. The NGN introduces the requirements for the extensibilit

26、y and configurability of the trouble types to address new and evolving IMS services, the definition of these extensions is for further study. ITU-T Rec. M.3343 (01/2007) 1 ITU-T Recommendation M.3343 Requirements and analysis for NGN trouble administration across B2B and C2B interfaces 1 Scope This

27、Recommendation contains the requirements and analysis for the business-to-business (B2B) and customer-to-business (C2B) interfaces of trouble administration for NGN. It assumes a multi-service provider environment and is aimed at trouble administration functions to support the deployment of NGN and

28、includes both the B2B and C2B interfaces. B2B/C2B interface is a synonymous term to X Interface. Figure 1-1 shows the relationship of this Recommendation to existing and as yet undefined documents for service assurance management. It shows the architecture for NGN service assurance management. M.334

29、3(07)_F1-1Recommendation on management interfacearchitecture of service assurance/trouble administration M.33xxTrouble reportmanagementTesting management Appointment management SLA/QoS managementX.790 X.745M.3343 M.33xx M.33xx M.3341Figure 1-1 Illustration of document architecture for NGN service as

30、surance/trouble management Trouble administration consists of processes utilizing trouble report management, testing management, appointment management and SLA management. This Recommendation and the current ITU-T X.790 are specific to trouble report. Functions for testing of the service or transpor

31、t stratum, appointment management and SLA management are outside the scope of this Recommendation. Trouble administration will require all the functions defined in this Recommendation and the other three Recommendations to provide a complete set of functions. Third-party request/response operations

32、are dependent upon the privacy business rules defined in the SC/SPs contract and consequently are considered out of scope for this Recommendation. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of

33、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 to investigate the possibility of applying the most recent edition of the Recommendations and ot

34、her 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, the status of a Recommendation. 2 ITU-T Rec. M.3343 (01/2007) ITU-T G.805 ITU-T Recommendation

35、G.805 (2000), Generic functional architecture of transport networks. ITU-T M.3010 ITU-T Recommendation M.3010 (2000), Principles for a telecommunications management network. ITU-T M.3016.x ITU-T Recommendation M.3016.x (2005), Security for the management plane. ITU-T M.3020 ITU-T Recommendation M.30

36、20 (2007), Management interface specification methodology. ITU-T M.3050.x ITU-T Recommendation M.3050.x (2004), Enhanced telecommunications operations map (eTOM). ITU-T M.3060 ITU-T Recommendation M.3060/Y.2401 (2006), Principles for the management of next generation networks. ITU-T M.3200 ITU-T Rec

37、ommendation M.3200 (1997), TMN management services and telecommunications managed areas: Overview. ITU-T M.3208.1 ITU-T Recommendation M.3208.1 (1997), TMN management services for dedicated and reconfigurable circuits network: Leased circuit services. ITU-T M.3400 ITU-T Recommendation M.3400 (2000),

38、 TMN management functions. ITU-T Q.1290 ITU-T Recommendation Q.1290 (1998), Glossary of terms used in the definition of intelligent networks. ITU-T X.720 ITU-T Recommendation X.720 (1992), Information technology Open Systems Interconnection Structure of management information: Management information

39、 model. ITU-T X.721 ITU-T Recommendation X.721 (1992), Information technology Open Systems Interconnection Structure of management Information: Definition of management information. ITU-T X.790 ITU-T Recommendation X.790 (1995), Trouble management function for ITU-T applications. ITU-T Y.2001 ITU-T

40、Recommendation Y.2001 (2004), General overview of NGN. ETSI TS 122 228 ETSI TS 122 228 (2006), UMTS: Service requirements for the IP multimedia core network subsystem (IMS); Stage 1. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 admin

41、istrative domain: ITU-T G.805. 3.1.2 b2b/c2b reference point: ITU-T M.3060. 3.1.3 interface: ITU-T M.3010. 3.1.4 IP multimedia application ETSI TS 122 228: An application that handles one or more media simultaneously, such as speech, audio, video and data (e.g., chat text, shared whiteboard) in a sy

42、nchronized way from the users point of view. A multimedia application may involve multiple parties, multiple connections and the addition or deletion of resources within a single IP multimedia session. A user may invoke concurrent IP multimedia applications in an IP multimedia session. ITU-T Rec. M.

43、3343 (01/2007) 3 3.1.5 IP multimedia subsystem (IMS) ETSI TS 122 228: An IP multimedia service is the user experience provided by one or more IP multimedia applications. 3.1.6 managed resource: ITU-T M.3010. 3.1.7 management domain: ITU-T M.3010. 3.1.8 management function: ITU-T M.3010. 3.1.9 market

44、, product and customer management function (MPCMF): ITU-T M.3060. 3.1.10 next generation network (NGN): ITU-T Y.2001. 3.1.11 operations system (OS): ITU-T M.3010. 3.1.12 operations systems function (OSF): ITU-T M.3010. 3.1.13 Q interface: ITU-T M.3010. 3.1.14 service customer: ITU-T M.3208.1. 3.1.15

45、 service provider: ITU-T M.3208.1. 3.1.16 service resource management function (SRMF): ITU-T M.3060. 3.1.17 service user: ITU-T Q.1290. 3.1.18 supplier/partner relationship management function (SPRMF): ITU-T M.3060. 3.1.19 X interface: ITU-T M.3010. 3.1.20 x reference point: ITU-T M.3010. NOTE 1 The

46、 definitions of SPRMF, MPCMF and SRMF are for further study. NOTE 2 SP and SC used in this Recommendation means SP role and SC role. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 B2B/C2B interface: The B2B/C2B interface in this Recommendation is used

47、 to interconnect two administrative domains or to interconnect a compliant environment with other networks or systems which accommodate a compliant interface, across which trouble administration information can be exchanged. 3.2.2 clearing trouble report: An assertion by an agent that actions which

48、are identified in the trouble report or the repair activity object instances have been satisfactorily performed to resolve the trouble, or that such actions are no longer necessary, such that in either case the trouble report is a candidate for closure. 3.2.3 closing trouble report: An assertion by

49、an agent that the trouble is resolved such that the cleared trouble report may only be processed further to generate a trouble history record and/or be deleted. 3.2.4 network operator: An organization that operates a NGN transport stratum. A network operator may offer both transport stratum and service stratum. A NGN network operator may or may not provide NGN service stratum services. 3.2.5 open trouble report: An assertion by the manager that a trouble exists in the quality of service