ITU-T G 852 1-1996 Management of the Transport Network - Enterprise Viewpoint for Simple Subnetwork Connection Management - Series G Transmission Systems and Media Digital Systems ig.pdf

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU G.852.1 (I 1/96) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Digital transmission systems - Digital networks - SDH network characteristics Management of the transport network - Ente

2、rprise viewpoint for simple subnetwork connection management ITU-T Recommendation G.852.1 (Previously CCITT Recommendation) ITU-T G-SERIES RECOMMENDATIONS TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS INTERNATIONAL ANALOGUE CARRIER SYST

3、EM TRANSMISSION SYSTEMS INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE WITH METALLIC LINES COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY TRANSMISSION MEDIA CHARACTERISTICS DIGITAL TRANSMISSION SYS

4、TEMS TERMINAL EQUIPMENTS YENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER- SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION General Coding of analogue signals by pulse code modulation Coding of analogue signals by methods other than PCM Principal characteristics of primary multipl

5、ex equipment Principal characteristics of second order multiplex equipment Principal characteristics of higher order multiplex equipment Principal characteristics of transcoder and digital multiplication equipment Operations, administration and maintenance features of transmission equipment Principa

6、l characteristics of multiplexing equipment for the synchronous digital hierarchy Other terminal equipment General aspects Design objectives for digital networks Quality and availability targets Network capabilities and functions DIGITAL NETWORKS DIGITAL SECTIONS AND DIGITAL LINE SYSTEM General Para

7、meters for optical fibre cable systems Digital sections at hierarchical bit rates based on a bit rate of 2048 kbis Digital line transmission systems on cable at non-hierarchical bit rates Digital line systems provided by FDM transmission bearers Digital line systems Digital section and digital trans

8、mission systems for customer access to ISDN Optical fibre submarine cable systems Optical line systems for local and access networks G. 1 OO-G. I99 G.200-G.299 G.300-G.399 G .400-G .449 G.450-G.499 G.600-G.699 G. 700-G . 799 G. 700-G. 709 G.710-G.719 G.720-G.729 G .730-G. 739 G .740-G. 749 G.750-G.7

9、59 G .760-G.769 G.770-G.779 G. 780-G. 789 G ,790-G . 799 G.800-G.899 G.800-G.809 G.810-G.819 G. 820-G. 829 G ,830-G .839 G ,840-G 399 G.900-G.999 G .900-G. 909 G.910-G.919 G.920-G. 929 G.930-G.939 G.940-G .949 G. 950-G. 959 G. 960-G. 969 G. 970-G. 979 G.980-G.999 For further details, please refer to

10、 ITU-T List of Recommendations. ITU-T RECOMMENDATION G.852.1 MANAGEMENT OF THE TRANSPORT NETWORK - ENTERPRISE VIEWPOINT FOR SIMPLE SUBNETWORK CONNECTION MANAGEMENT Summary This Recommendation contains the enterprise viewpoint specification for managing a transport network from a network viewpoint. I

11、n particular this Recommendation details the enterprise viewpoint for Subnetwork Connection Management. The specification was written in accordance with G.85 1.1 Management of the Transport Network - Application of the RM-ODP Framework. Source ITU-T Recommendation G.852.1 was prepared by ITU-T Study

12、 Group 15 (1993-1996) and was approved under the WTSC Resolution No. 1 procedure on the 8th of November 1996. STD-ITU-T RECMN G-852-L-ENGL L99b D 48b257L Ob3b932 233 9 FOREWORD IT (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The

13、 ITU Telecommunication Standardization Sector (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

14、 Standardization Conference (WTSC), which meets 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 Resolu

15、tion No. 1. In some areas of information technology 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 administrati

16、on and a recognized operating agency. INTELLECTUAL 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 IT takes no position concerning the evidence, validity or applica

17、bility 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, the ITU had/had not received notice of intellectual property, protected by patents, which may be required to

18、 implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database. O ITU 1997 All rights reserved. No part of this publication may be reproduced or utilized in any form or by any

19、means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. 11 Recommendation G.852.1 (11/96) CONTENTS Page 1 Scope 2 References 3 4 Definitions Abbreviations . 5 Enterprise viewpoint . Annex A - COMMUNITY sscc “Simple Subnetwork Connection Conf

20、iguration“ . A.1 PURPOSE . A.2 ROLE (See Figure A.l) A.3 POLICY A.4 ACTION . ssccl “Setup Point-to-Point SNC“ sscc2 “Release Point-to-Point SNC“ . AS ACTIVITY . A.6 CONTRACT . Annex B - COMMUNITY sfm “Simple Failure Monitoring“ A.4.1 A.4.2 B . 1 B.2 B.3 B . 4 B.5 B.6 PURPOSE . ROLE (See Figure B.l)

21、POLICY ACTION . B.4.1 sfml “Report Failure“ . B.4.2 sfm2 “Report Recovery“ . B.4.3 sfm3 “Suspend Monitor Reporting“ B.4.4 sfm4 “Resume Monitor Reporting“ . ACTIVITY . CONTRACT . Annex C . COMMUNITY smscc “Simple Monitored Subnetwork Connection C.1 PURPOSE . C.2 ROLE (see Figure C.1) . c.3 POLICY C.4

22、 ACTION . C.4.1 ssccl “Setup Point-to-Point SNC“ C.4.2 sfml “Report Failure“ . Configuration“ Recommendation G.852.1 (11/96) 1 1 1 1 2 2 4 4 4 4 4 5 5 5 5 5 6 6 6 . 111 STD-ITU-T RECMN G-852*L-ENGL L77b = 48bZ.571 Ob3b734 OOb Page . C.4.3 sfm2 “Report Recovery“ 9 C.4.4 sfm3 “Suspend Monitor Reportin

23、g“ 10 C.4.5 sfm4 “Resume Monitor Reporting“ 10 C.4.6 sscc2 “Release Point-to-Point SNC“ 10 C.5 ACTIVITY 11 C.6 CONTRACT 11 . . . . iv Recommendation G.852.1 (11/96) Recommendation G.852.1 MANAGEMENT OF THE TRANSPORT NETWORK - ENTERPRISE VIEWPOINT FOR SIMPLE SUBNETWORK CONNECTION MANAGEMENT (Geneva,

24、1996) 1 Scope This Recommendation describes the enterprise viewpoint specification for Simple Subnetwork Connection Management of a transport network. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions

25、 of this Recommendation. At the time of publication, the editions indicated 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 Recommendation

26、s and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. - ITU-T Recommendation G.805 (1 995), Generic functional architecture of transport - ITU-T Recommendation G.85 1.1 (1 996), Management of the transport network - networks. Application of

27、the RM-ODP fiamework. 3 Definitions None. 4 Abbreviations This Recommendation uses the following abbreviations: ITU-T RM-ODP International Telecommunication Union - Telecommunication Standardization Sector Reference Model for Open Distributed Processing 5 Enterprise viewpoint The enterprise specific

28、ations contained in the annexes were written in accordance with Recommendation G.85 1.1 that defines the FW-ODP methodology employed to generate enterprise specifications in regard to the management of transport networks. The enterprise specifications assume the existence of G.805 network resources

29、and are thus written from a Network View of managing a transport network, as opposed to network management based upon a Network Element View. Recommendation G.852.1 (1 1/96) 1 ANNEX A COMMUNITY sscc “Simple Subnetwork Connection Configuration“ A.l PURPOSE “The objective of the community is to config

30、ure point-to-point subnetwork connections between pairs of ports, which have been previously populated on the boundary of a subnetwork.“ A.2 ROLE (See Figure A.l) caller “This role reflects the client of the actions defined in this community. One and only one caller role occurrences may exist in the

31、 community.“ provider “This role reflects the server of the actions defined in this community. One and only one provider role occurrence must exist in the community.“ port “This role reflects the G.805 port resource used in the actions defined in this community. Zero or more port role occurrences ma

32、y exist in the community.“ sn “This role reflects the G.805 subnetwork resource used in the actions defined in this community. One and only one sn role occurrence must exist in the community.“ snc “This role reflects the G.805 subnetwork connection resource used in the actions defined in this commun

33、ity. Zero or more snc role occurrences may exist in the community.“ Subnetwork Connection Community T1527720-97 Figure A.UG.852.1- ROLE in the Simple Subnetwork Connection Community A.3 POLICY OBLIGATION OBLG-1 “The provider shall support such viewing of the resource properties and relationships whi

34、ch have been identified and allowed in the service contract with the caller.“ 2 Recommendation G.852.1 (11/96) A.4 ACTION A.4.1 ssccl “Setup Point-to-Point SNC“ “This action sets up a point-to-point subnetwork connection between two ports on the same subnetwork.“ ACTION-POLICY OBLIGATION OBLG-1 “Thi

35、s action must be provided in respect to all the action policies or it fails, In the event the action fails, the provider shall report to the caller which action policy has been violated.“ OB LIGATION OBLG-2 “The caller shall identi and other features which are for future study.“ ANNEX B COMMUNITY sf

36、m “Simple Failure Monitoring“ B.l PURPOSE “The objective of the community is to allow monitoring for a failure condition in a managed resource that makes it incapable of performing its normal function.“ B.2 ROLE (See Figure B.1) caller “This role reflects the client of the actions defined in this co

37、mmunity. One or more caller role occurrences can exist in the community.“ provider “This role reflects the server of the actions defined in this community. One and only one provider role occurrence must exist in the community. monitored entity “This role reflects the resource in the actions defined

38、in this community subject to simple failure monitoring. Zero or more monitored-entity role occurrences can exist in the community.“ I 4 Recommendation G.852.1 (11/96) STD-ITU-T RECMN G-852-1-ENGL 177b 48b2571 Ob3b739 b9 m Failure Monitoring T1527730-97 Figure B.UG.852.1- ROLE in the Failure Monitori

39、ng Community B.3 POLICY OBLIGATION OBLG-1 “The provider shall support such viewing of the resource properties and relationships which have been identified and allowed the service contract with the caller.“ OBLIGATION OBLG-2 “The provider shall have a unique identity for each Monitored-entity in the

40、community.“ B.4 ACTION B.4.1 sfm “Report Failure“ “This action is used by the provider to report on the failure of the monitored - entity to perform its function. I ACTION-POLICY OBLIGATION OBLG-1 “The caller will be informed by the provider of the identity of a monitored-entity if a failure conditi

41、on in a resource supporting that monitored - entity results in the inability of the monitored-entity to provide its function.“ B.4.2 sfm2 “Report Recovery“ “This action is used by the provider to report on the recovery of the monitored-entity to perform its function.“ ACTION-POLICY OBLIGATION OBLG-1

42、 “The caller will be informed by the provider of the identity of a monitored-entity if a failure condition in a resource supporting that monitored-entity disappears and its function is re-established.“ B.4.3 sfm3 “Suspend Monitor Reporting“ “This action is used to suspend failure and recovery report

43、ing of the monitored-entity.“ Recommendation G.852.1 (1 1/96) 5 ACTION-POLICY OBLIGAT1 ON OBLG-1 “This action must be provided in respect to all the action policies or it fails. In the event the action fails, the provider shall report to the caller which action policy has been violated.“ OBLIGATION

44、OBLG-2 “The caller shall identi the monitored-entity for which monitor reporting is requested to be suspended. II OBLIGATION OBLG-3 “If OBLG-2, then the provider shall suspend monitor reporting.“ B.4.4 sfm4 “Resume Monitor Reporting“ “This action is used to resume failure and recovery reporting of t

45、he Monitored-entity.“ ACTIONPOLICY OBLIGATION OBLG-1 “This action must be provided in respect to all the action policies or it fails. In the event the action fails, the provider shall report to the caller which action policy has been violated.“ OBLIGATION OBLG-2 “The caller shall identify the monito

46、red-entity for which monitor reporting is requested to be resumed.“ OBLIGATION OBLG-3 “If OBLG-2 then the provider shall resume monitor reporting.“ B.5 ACTIVITY “None.“ B.6 CONTRACT “Service features subject to negotiation as part of a service contract shall include: - - degree of visibility of reso

47、urce (their properties and relationships); and other features which are for future study.“ ANNEX C COMMUNITY smscc “Simple Monitored Subnetwork Connection Configuration“1 C.l PURPOSE “The objective of the community is to configure point-to-point subnetwork connections and to monitor them for failure

48、. This annex presents a combination of communities. While the objective for the combined community is agreed, the general method of combining and representation of combination is for further study. 6 Recommendation G.852.1 (11/96) The following communities are used by this community: - - Simple Fail

49、ure Monitoring Community. Rules concerning the use of these communities are detailed in the community policies and action policies of this community.“ Simple Subnetwork Connection Configuration Community; and C.2 ROLE (see Figure C.1) caller “This role reflects the client of the actions defined in this community and assumes the role of the caller in other communities used by this community. One and only one caller role occurrences may exist in the community.“ provider “This role reflects the server of the actions defined in this community and assumes the role of t