ITU-T Q 834 4 AMD 1-2004 A CORBA interface specification for Broadband Passive Optical Networks based on UML interface requirements Amendment 1 SERIES Q SWITCHING AND SIGNALLING Q3.pdf

《ITU-T Q 834 4 AMD 1-2004 A CORBA interface specification for Broadband Passive Optical Networks based on UML interface requirements Amendment 1 SERIES Q SWITCHING AND SIGNALLING Q3.pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 834 4 AMD 1-2004 A CORBA interface specification for Broadband Passive Optical Networks based on UML interface requirements Amendment 1 SERIES Q SWITCHING AND SIGNALLING Q3.pdf（30页珍藏版）》请在麦多课文档分享上搜索。

1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T Q.834.4TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Amendment 1(01/2004) SERIES Q: SWITCHING AND SIGNALLING Q3 interface A CORBA interface specification for Broadband Passive Optical Networks based on UML interface requirements Amendment 1 ITU-T Recomm

2、endation Q.834.4 (2003) Amendment 1 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3 INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59 FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN Q.60Q.99 CLAUSES APPLICABLE TO ITU-T S

3、TANDARD SYSTEMS Q.100Q.119 SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4, 5, 6, R1 AND R2 Q.120Q.499 DIGITAL EXCHANGES Q.500Q.599 INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699 SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.799 Q3 INTERFACE Q.800Q.849 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.

4、999 PUBLIC LAND MOBILE NETWORK Q.1000Q.1099 INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199 INTELLIGENT NETWORK Q.1200Q.1699 SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799 SPECIFICATIONS OF SIGNALLING RELATED TO BEARER INDEPENDENT CALL CONTROL (BICC) Q.1900Q.1999 BROADBAND I

5、SDN Q.2000Q.2999 For further details, please refer to the list of ITU-T Recommendations. ITU-T Rec. Q.834.4 (2003)/Amd.1 (01/2004) i ITU-T Recommendation Q.834.4 A CORBA interface specification for Broadband Passive Optical Networks based on UML interface requirements Amendment 1 Summary This amendm

6、ent provides several enhancements to the CORBA interface specification for the management interface between a Supplier Management System and an Operator Management System managing Broadband Passive Optical Networks (BPONs). In includes changes needed for management of dynamic bandwidth allocation an

7、d automatic ranging of Optical Network Units (ONUs) and Optical Network Terminals (ONTs). It also includes additions required to adequately support testing of telephony and data services, software activity notification, and capacity management. Source Amendment 1 to ITU-T Recommendation Q.834.4 (200

8、3) was approved on 13 January 2004 by ITU-T Study Group 4 (2001-2004) under the ITU-T Recommendation A.8 procedure. ii ITU-T Rec. Q.834.4 (2003)/Amd.1 (01/2004) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The I

9、TU 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 to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardi

10、zation 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 Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information tec

11、hnology 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 conciseness to indicate both a telecommunication administration and a recognized operating agency. Compli

12、ance 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 is achieved when all of these mandatory provisions are met. The words “shall“ or some other oblig

13、atory 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. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementatio

14、n 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, whether asserted by ITU members or others outside of the Recommendation development process. As of

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

16、consult the TSB patent database. ITU 2004 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. Q.834.4 (2003)/Amd.1 (01/2004) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Terms and definitions . 1 3.1 Te

17、rms imported from ITU-T Rec. G.983.4 1 3.2 New terms. 2 4 Abbreviations 2 5 Conventions 2 6 Enhancements to Build and Common interfaces 2 6.1 Modifications to clause 9.2.1.1, “buildNode“ 2 6.2 Modifications to clause 9.2.1.2, “assignUserLabelsToNE“ . 3 6.3 Modifications to clause 9.2.1.3, “modifyNod

18、e“ . 3 6.4 buildTCONT. 4 6.5 modifyTCONTParameters . 4 6.6 deleteTCONT . 4 6.7 Modifications to clause 9.2.1.20, “Exceptions“ 5 7 Enhancements to Test interface 5 7.1 metallicDropTest 5 7.2 scheduleMetallicDropTest 6 7.3 mACLayerTest . 6 7.4 scheduleMACLayerTest. 7 7.5 drawDialToneBreakTest. 7 7.6 s

19、cheduleDrawDialToneBreakTest 7 7.7 Modifications to clause 9.15.1.5, “modifyResourceSelfTestSchedule“. 8 7.8 Modifications to clause 9.15.1.6, “cancelScheduledResourceSelfTest“ 8 7.9 Modifications to clause 9.15.1.7, “conductResourceSelfTest“ 9 8 Enhancements to Event Supplier interface. 9 8.1 Activ

20、ityCompletionEventSupplier . 9 8.2 Table 1, “q834_4 module organization“. 10 9 Enhancements to Common Interface for Capacity Management . 10 10 Enhancements to Annex A, “Data dictionary“ . 10 11 Enhancements to Annex B, “Exceptions“ 11 iv ITU-T Rec. Q.834.4 (2003)/Amd.1 (01/2004) Page 12 Enhancement

21、s to Annex C, “IDL files“ 11 12.1 Enhancements to clause C.2, “Q834Build.idl“. 11 12.2 Enhancements to clause C.3, “Q834Common.idl“. 15 12.3 Enhancements to clause C.6, “Q834Eventpublisher.idl“ . 18 12.4 Enhancements to clause C.15, “Q834Test.idl“. 19 13 Enhancements to Annex D, “Example endpoint te

22、mplates“ 22 ITU-T Rec. Q.834.4 (2003)/Amd.1 (01/2004) 1 ITU-T Recommendation Q.834.4 A CORBA interface specification for Broadband Passive Optical Networks based on UML interface requirements Amendment 1 1 Scope This amendment provides several enhancements to the CORBA interface specification for th

23、e management interface between a Supplier Management System and an Operator Management System managing Broadband Passive Optical Networks (BPONs). In includes changes needed for management of dynamic bandwidth allocation and automatic ranging of Optical Network Units (ONUs) and Optical Network Termi

24、nals (ONTs). It also includes additions required to adequately support testing of telephony and data services, software activity notification, and capacity management. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, cons

25、titute provisions of 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 R

26、ecommendations and other 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. 1 ITU-T Recommendation G.983.4 (2001), A b

27、roadband optical access system with increase service capability using dynamic bandwidth assignment (DBA). 2 ITU-T Recommendation G.983.7 (2001), ONT Management and Control Interface specification for Dynamic Bandwidth Assignment (DBA) B-PON system. 3 ITU-T Recommendation G.983.4 (2001)/Amd.1 (2003),

28、 A broadband optical access system with increased service capability using dynamic bandwidth assignment (DBA), Amendment 1: New Annex A Performance monitoring parameters. 4 ITU-T Recommendation G.983.1 (1998), Broadband optical access systems based on Passive Optical Networks (PON). 3 Terms and defi

29、nitions For the purposes of this amendment, the following definitions apply: 3.1 Terms imported from ITU-T Rec. G.983.4 The following terms from ITU-T Rec. G.983.4 1 are used in this amendment. Dynamic Bandwidth assignment; T-CONT; Guaranteed Bandwidth; Fixed Bandwidth; Assured Bandwidth; Maximum Ba

30、ndwidth. 2 ITU-T Rec. Q.834.4 (2003)/Amd.1 (01/2004) 3.2 New terms This amendment defines no new terms. 4 Abbreviations This amendment uses no new abbreviations in addition to those found in the main Recommendation. 5 Conventions This amendment has no new conventions in addition to those found in th

31、e main Recommendation. 6 Enhancements to Build and Common interfaces This clause describes changes to Q834:Build and Q834:Common interface required to support the management of dynamic bandwidth allocation as well as the automatic ranging of ONTs or ONUs following one of the ranging mechanisms defin

32、ed in ITU-T Rec. G.983.1. First, operations used to construct or modify attributes for ONT or ONU network elements are modified to include input parameters required to properly characterize such network elements supporting dynamic bandwidth allocation and automatic ranging. Second, new operations ar

33、e added to provide the capability of construction of TCONTs, a partitioning of bandwidth intended for use at an ONT or ONU in conjunction with the dynamic bandwidth allocation protocol mechanisms. These operations are called buildTCONT, modifyTCONTParameters, and deleteTCONT. The new operations crea

34、te the need for a new exception called UnsupportedTCONTType, the enhancement of the definition of ParameterViolation exception, and the new use of an existing exception, InsufficientPONBW, by Q834:Build interface. Third, the data structures used to characterize ONTs and ONUs in Q834:Common are modif

35、ied to include these new attributes. Finally, new HistoryData record types are added to Q834:Common in order to allow for the performance monitoring of the dynamic bandwidth allocation function. They are called DBAFairnessPMHistoryDataType and TCONTTEPMHistoryDataType. All changes to Q834:Common and

36、 associated changes to Annexes A and B are combined with other enhancements and presented in clauses 12.2 , 10, and 11, respectively. 6.1 Modifications to clause 9.2.1.1, “buildNode“ a) Replace: “ in AdministrationDomainType administrationDomain) raises (UnrecognisedVersion, InvalidSerialNumSyntax,

37、DuplicateSerialNumber, UnknownProfiles,“ with: “ in RegistrationIdType registrationId, in boolean sRInd, in AdministrationDomainType administrationDomain) raises (UnrecognisedVersion, InvalidSerialNumSyntax, DuplicateSerialNumber, UnknownProfiles, ParameterViolation,“ ITU-T Rec. Q.834.4 (2003)/Amd.1

38、 (01/2004) 3 b) Replace: “The input administrationDomain identifies the domain to which the NE belongs.“ with: “The input registrationId provides the logical key to associate this provisioning data with an installed NE. The input sRInd specifies whether or not the NE should be status reporting if th

39、e NE constructed is an ONT or ONU and dynamic bandwidth allocation is supported. The input administrationDomain identifies the domain to which the NE belongs.“ 6.2 Modifications to clause 9.2.1.2, “assignUserLabelsToNE“ a) Replace: “ in AdministrationDomainType administrationDomain)“ with: “ in Regi

40、strationIdType registrationId, in AdministrationDomainType administrationDomain)“ b) Replace: “The input administrationDomain identifies the domain to which the NE is assigned.“ with: “The input registrationId provides the logical key to associate this provisioning data with an installed NE. The inp

41、ut administrationDomain identifies the domain to which the NE belongs.“ 6.3 Modifications to clause 9.2.1.3, “modifyNode“ a) Replace: “ in AdministrationDomainType administrationDomain) raises (UnknownManagedEntity, UnknownNE, InvalidSlotAssignmentList, UnknownProfiles, DuplicateUserLabel, AccessDen

42、ied, InvalidExternalTime, ProfileSuspended);“ with: “ in RegistrationIdType registrationId, in boolean sRInd, in AdministrationDomainType administrationDomain) raises (UnknownManagedEntity, UnknownNE, InvalidSlotAssignmentList, UnknownProfiles, DuplicateUserLabel, AccessDenied, InvalidExternalTime,

43、ProfileSuspended, ParameterViolation);“ b) Replace: “The input administrationDomain identifies the domain to which the NE is reassigned.“ with: “The input registrationId provides the logical key to associate this provisioning data with an installed NE. The input sRInd specifies the new value for the

44、 status reporting characteristic of the ONT or ONU. The input administrationDomain identifies the domain to which the NE belongs.“ 4 ITU-T Rec. Q.834.4 (2003)/Amd.1 (01/2004) 6.4 buildTCONT This operation builds a TCONT in the Supplier Management System. The ONT or ONU associated with the TCONT must

45、 be provisioned prior to this operation. The operation signature for buildTCONT is shown below: ManagedEntityIdType buildTCONT ( in ManagedEntityIdType nEId, in TCONTType typeOFTCONT, in BWType maxBW, in BWType fixedBW, in BWType guaranteedBW, in UserLabelType userLabel) raises (UnknownNE, AccessDen

46、ied, InsufficientPONBW, UnsupportedTCONTType, DuplicateUserLabel); The input nEId identifies the ONT or ONU where the TCONT is to be terminated. The input parameter typeOFTCONT identifies which of the five TCONT types is to be constructed. The input parameters maxBW, fixedBW, and guaranteedBW identi

47、fy the bandwidth attributes that characterize the logical link end. The input userLabel provides a unique operator designation for the constructed TCONT, if such identification is desired. The return value of type ManagedEntityIdType provides unique identifier for the constructed TCONT. 6.5 modifyTC

48、ONTParameters This operation modifies the parameters associated with an existing TCONT in the Supplier Management System. The operation signature for modifyTCONTParameters is shown below: void modifyTCONTParameters ( in ManagedEntityIdType tCONTId, in BWType maxBW, in BWType fixedBW, in BWType guara

49、nteedBW, in UserLabelType userLabel) raises (UnknownManagedEntity, AccessDenied, InsufficientPONBW, DuplicateUserLabel); The input tCONTId identifies the TCONT whose characteristics are to be modified. The input parameters maxBW, fixedBW, and guaranteedBW identify the new bandwidth attributes that should characterize the logical link end. The input userLabel provides a unique operator designation for the constructed TCONT, if such identification is desired. The return value is of type void. 6.6 deleteTCONT This operation deletes a TCONT