ITU-T M 1537-1997 Definition of Maintenance Information to be Exchanged at Customer Contact Point (MICC) - Series M TMN and Network Maintenance International Transmission Systems T.pdf

1、STD=ITU-T RECMN M.1537-ENGL I 48b2591i Ob42270 TOT I INTERNATIONAL TELECOMMUNICATION UNION ITU=T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU MA537 (I 0197) SERIES M: TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Des

2、ignations and information exchange Definition of maintenance information to be exchanged at customer contact point (MICC) ITU-T Recommendation M. 1537 (Previously CCITT Recommendation) STD-ITU-T RECMN M.3537-ENGL 4862593 ObYi1273 94b I ITU-T M-SERI ES RECOMMENDATIONS TMN AND NETWORK MAINTENANCE: INT

3、ERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS Introduction and general principles of maintenance and maintenance organization International transmission systems International telephone circuits Common channel signalling systems International telegraph

4、 systems and phototelegraph transmission International leased group and supergroup links International leased circuits Mobile telecommunication systems and services International public telephone network International data transmission systems M. 10-M.299 M.300-M.559 M. 560-M.759 M.760-M.799 M.800-M

5、.899 M.900-M.999 M. 1000-M. 1 O99 M.1100-M.1199 M. 1200-M.1299 M. 1300-M.1399 Designations and informati M.140-M.1999 International transport network M.2000-M.2999 Telecommunications management network Integrated services digital networks Common channel signalling systems M.3000-M.3599 M.3600-M.3999

6、 M.4000-M.4999 For further details, please refer to ITU-T List of Recommendations. STD-ITU-T RECMN M-L537-ENGL .1 48b259L Ob42272 882 ITU-T RECOMMENDATION M.1537 DEFINITION OF MAINTENANCE INFORMATION TO BE EXCHANGED AT CUSTOMER CONTACT POINT (MICC) Source ITU-T Recommendation M.1537 was prepared by

7、ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 24th of October 1997. FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (

8、ITU-T) is a permanent organ of the ITU. The 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 Conference (WTSC), which meets

9、 every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1. In some areas of information techno

10、logy which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECT

11、UAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights

12、, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implement

13、ors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. o ITU 1998 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photoco

14、pying and microfilm, without permission in writing fiom the ITU. Recommendation M.1537 (10/97) 11 1 2 3 3.1 4 5 5.1 5.2 5.3 5.4 6 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 7 7.1 7.2 7.3 STD=ITU-T RECMN M-1537-ENGL sl 48b2591 0642274 655 CONTENTS Page Scope 1 References Terms and definitions . Terminology . Ab

15、breviations . Defmition of maintenance information Information basic structure . Generic information part Specific information part Reference information part . Examples of maintenance processes . Bringing-into-service process . Fault report process (customer to service provider) . Network fault rep

16、ort process (service provider to customer) . Fault localization process . Service restoration process . Network repair process . Fault follow-up process Planned outage process . . Information classification . Utility value of information Timing of information Standardization levels . Annex A . Examp

17、les of maintenance process . 2 2 2 6 6 6 7 7 7 7 7 7 8 Recommendation M.1537 (10/97) iii STD-ITU-T RECMN M-1537-ENGL = 48b2591 Ob42275 591 Recommendation M.1537 DEFINITION OF MAINTENANCE INFORMATION TO BE EXCHANGED AT CUSTOMER CONTACT POINT (MICC) (Geneva, I99 7) 1 Scope This Recommendation describe

18、s the definition for the maintenance information exchange between a customer and a service providers customer care staff at customer contact point under the environment of multiple service providers. A customer contact point is a conceptual point at which a service provider can interact with any cus

19、tomer of the offered service for the purpose of maintaining communication services. 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 i

20、ndicated were valid. All Recommendations and other references are subject to revision; all 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

21、ITU-T Recommendations is regularly published. ITU-T Recommendation E.440 (1 996), Customer satisfaction point. ITU-T Recommendation E.800 (1994), Terms and dejnition related to quality of service and network performance including dependability. CCITT Recommendation M.2 1 (1 992), Maintenance philoso

22、phy for telecommunication services. ITU-T Recommendation M.60 (1 993), Maintenance terminology and dejnitions. ITU-T Recommendation M. 1400 (1 997), Designations for international networks. CCITT Recommendation M. 15 1 O (1992), Exchange of contact point information for the maintenance of internatio

23、nal services and the international network. CCITT Recommendation M. 1520 (1992), Standardized information exchange between Administrations. CCITT Recommendation M. 1530 (1 992), Network maintenance information. ITU-T Recommendation M. 1535 (1996), Principles for Maintenance Information to be exchang

24、ed at Customer Contact point (MICC). ITU-T Recommendation M. 1540 (1994), Exchange of information for planned outages of transmission systems. ITU-T Recommendation M.301 O (1 996), Principles for a Telecommunications Management Network. ITU-T Recommendation M.3200 (1 997), Tm management services and

25、 telecommunications managed areas: overview. Recommendation M.1537 (10/97) 1 STD-ITU-T RECMN M.1537-ENGL M 48625%L 0642276 428 I ITU-T Recommendation X. 160 (1 996), Architecture for customer network management service for public data networks. ITU-T Recommendation X. 1 6 1 (1 999, DeJinition of cus

26、tomer network management services for public data networks. ITU-T Recommendation X. 162 (1 995), DeJinition of management information for customer network management service for public data networks to be used with the CNMc Interface. ITU-T Recommendation X. 163 (1995), DeJinition of management info

27、rmation for customer network management service for public data networks to be used with the CNMe Interface. Terms and definitions Terminology Recommendation M. 1535 provides principles for Maintenance Information to be exchanged at Customer Contact point (MICC). Terminology and definitions relating

28、 to this Recommendation are provided in Recommendation M.60. Further terms and definitions can be found in other ITU-T Recommendations (e.g. M.21, M.1400, M.1510, M.1520, M.1530, M.1540, M.3010, M.3200, E.800, E.440, X.160, X.161, X.162 and X. 163). 4 Abbreviations This Recommendation uses the follo

29、wing abbreviations ISDN Integrated Services Digital Network MICC Maintenance Information to be exchanged at Customer Contact point TMN Telecommunications Management Network 5 Definition of maintenance information 5.1 Information basic structure Maintenance Information to be exchanged at Customer Con

30、tact point (MICC) consists of “Generic information part“, “Specific information part“ and “Reference information part“. All this information contains items and/or sub-items of maintenance information (see Figure 1). 2 Recommendation M.1537 (10/97) STD-ITU-T RECMN M.3537-ENGL S 4862593 Ob42277 3b4 E

31、Generic information part Specific Reference information information part part MICC - Generic information part Specific information part - - Reference information part - “f Bringing-into-service information I - Fault Reporting information - - Network fault Reporting information - Fault localization i

32、nformation Service restoration information - Network repair information - Follow-up - information Planned outage information Contact information Service agreement information - L itemq -I- item L I I I I l I I I I I I I I I I I I I I I I I I I I l l I I I I I TO407320-97 Figure 1M.1537 - MICC basic

33、structure 5.2 Generic information part Generic information part is independent from the maintenance sub-process type (see Recommendation M.1535), and it is normally used during a sequence of procedure in order to identi the circuit and event concerned. Generic information items are shown in Table 1.

34、 Recommendation M.1537 (10/97) 3 STD-ITU-T RECMN M.3537-ENGL 48b259L Ob42278 2TO = Telephone services (Note 1) Leased Circuit ISDN Data services services transmission services 5.3 Specific information part Specific information part is dependent on individual maintenance sub-process. Therefore, appro

35、priate maintenance information items are used for each of the following eight maintenance sub-processes (see Recommendation M. 1535): - bringing-into-service; - - - fault localization; - service restoration ; - network repair; - fault follow-up; - planned outage. Specific information items are shown

36、 in Table 2. fault report (customer to service provider); network fault report (service provider to customer); Generic information I , 4 Recommendation M.1537 (10/97) Information items - Contact time (Note 2) - Customer identification - Customer care staff identification - Circuit identification (No

37、te 3) STDmITU-T RECMN M-1537-ENGL 4862593 Ob42279 I137 I Telephone Leased Circuit ISDN services services services (Note) Managed -elated process Data transmission services 3ringing-into-service ?auk report Vetwork fault report Fault localization Service restoration Network repair Fault follow-up Pla

38、nned outage - Transmission route - Transmission media - Ready for service date - Testing date - Circuit designation - Reference to the appropriate ITU-T Recommendations - Fault start time (based on fault occurrence andor its detection) - Faultstatus - Permission for testing - Fault related data log

39、- Fault detection time - Fault status - Permission for testing - Expected restoration time - Cause(s) - Fault related data log - Localization result by customer - Localization result by service provider - Requirementhapability for service restoration - Expected service restoration time - Means for s

40、ervice restoration - Confirmation of service restoration - Expected network repair time - Means for network repair - Confirmation of network repair - Restoration schedule - Progress - Planned outage schedule (starilend time) - Reason - Affected area - Normality confirmation test result by both custo

41、mer and service provider NOTE - For telephone services, the above information items are used for special telephone services only, for example sound-program transmission on fixed (non-switched) public circuits. Recommendation M.1537 (10/97) 5 STD-ITU-T RECMN M.LS37-ENGL M 48b259L Ob42280 959 M 5.4 Re

42、ference information part Reference information part is used in case of necessity to proceed maintenance efficiently in collaboration with the customer, and it can be mainly classified into contract information (Note 1) and service agreement information (Note 2). Typical maintenance information items

43、 which are related to the maintenance service contract or maintenance service agreement are: - contract identifier (e.g. contract number); - contact identifier (e.g. authentication identification and password); - service starting date; - service hours (for normal and particular days of the year); -

44、type of contract; - access network type (e.g. mobile, ISDN, leased circuit); - network configuration (e.g. transmission routes, transmission media, automatic restoration); - traffic volume; - fault status and occurrence; - testing status; - call connectivity quality; - transmission quality; - conges

45、tion status; - service availability. NOTE 1 - A contract represents a formal business agreement between service provider and customer for its maintenance service. NOTE 2 - A maintenance service agreement may not be formal nor has a legal binding as maintenance service contract. It is to be noted tha

46、t for this information part the maintenance information items depend on the managed area. 6 Examples of maintenance processes An example of each maintenance process is described in Annex A to help understanding the “Generic part and the Specific part“ of MICC based on maintenance process reference m

47、odel (see Recommendation M. 1535). 6.1 Bringing-into-service process An example of bringing-into-service process is given in Figure A. 1. 6.2 A customer detects malfunction in the service by receiving report from end-user or alarm report from its own communication facilities. Then he can confirm the

48、 status of this malfunction by notifying the end-user for the detail of test results and type of alarm on the facilities. The customer tries to specify where the cause of malfunction is located (at his own premises, customer side or at the service provider side). Then he accesses a customer contact

49、point to report the malfunction to the service provider. An example of fault report process is given in Figure A.2. Fault report process (customer to service provider) 6 Recommendation M.1537 (10/97) STD=ITU-T RECMN MmL537-ENGL I 48b259L Ob42281 895 W 6.3 An example of network fault report process is given in Figure A.3. Network fault report process (service provider to customer) 6.4 Fault localization process An example of fault localization process is given in Figure A;4. 6.5 Service restoration process An example of service restoration process is given i