ATIS 0300003-2017 XML Schema Interface for Fault Management (Trouble Administration).pdf

1、ATIS-0300003.2017 Revision of ATIS-0300003.2015 American National Standard for Telecommunications XML Schema Interface for Fault Management (Trouble Administration) Alliance for Telecommunications Industry Solutions Approved November 16, 2016 American National Standards Institute, Inc. Abstract This

2、 standard provides an XML schema information model for Trouble Administration and an XML schema interface for Trouble Administration functions and services. Additional information from the original CMIP-based Trouble Administration standards ATIS-0300227.2008 and ATIS-0300228.2011 can be found in in

3、formative annexes to this document. It is the intention that this document be used for current implementations of Electronic Bonding, which to this Committees knowledge are all implemented using XML. The informative annexes have been included here so as not to lose context information that may still

4、 prove to be of value. ATIS-0300003.2017 ii Foreword The information contained in this Foreword is not part of this American National Standard (ANS) and has not been processed in accordance with ANSIs requirements for an ANS. As such, this Foreword may contain material that has not been subjected to

5、 public review or a consensus process. In addition, it does not contain requirements necessary for conformance to the Standard. The Alliance for Telecommunication Industry Solutions (ATIS) serves the public through improved understanding between carriers, customers, and manufacturers. The Telecom Ma

6、nagement and Operations Committee (TMOC) - formerly T1M1 -develops operations, administration, maintenance and provisioning standards, and other documentation related to Operations Support System (OSS) and Network Element (NE) functions and interfaces for communications networks with an emphasis on

7、standards development related to U.S.A. communication networks in coordination with the development of international standards. ANSI guidelines specify two categories of requirements: mandatory and recommendation. The mandatory requirements are designated by the word shall and recommendations by the

8、 word should. Where both a mandatory requirement and a recommendation are specified for the same criterion, the recommendation represents a goal currently identifiable as having distinct compatibility or performance advantages. Suggestions for improvement of this document are welcome. They should be

9、 sent to the Alliance for Telecommunications Industry Solutions, TMOC, 1200 G Street NW, Suite 500, Washington, DC 20005. At the time it approved this document, TMOC, which is responsible for the development of this Standard, had the following leadership: M. Usry, TMOC Chair (iconectiv) T. Barrett,

10、Technical Editor (AT each value of the choice type is derived from the value of one of the component types. 3.8.14 component type: One of the types referenced when defining a CHOICE, SET, SEQUENCE, SET OF, or SEQUENCE OF. Schema Data Structure Diagram Act ivityCodeValueTypeApproved : 0Assign : 1Canc

11、el : 2Clear : 3Close : 4Defer : 5Dispatch : 6Refer : 7Release : 8Reopen : 9Repair : 10Test : 11Transfer : 12ActivityCodeTypeNumber : ActivityCodeValueTypeIdent ifier : Object IdentifierTypeATIS-0300003.2017 9 Table 3.5 CHOICE: Case 2 ASN.1 Definition UML Model Schema TroubleDetectionTime:=CHOICE NUL

12、L, GeneralizedTime, GeneralizedTimeTypeTroubleDetectionTimeTypeNullStringTypeATIS-0300003.2017 10 Table 3.6 CHOICE: Case 3 ASN.1 Definition UML Model Schema OutageDuration:=CHOICE NULL, TimeInterval, . Schema Data Structure Diagram OutageDurationTypeTimeIntervalType Day : DateType Hour : HourType Mi

13、nute : MinuteType Second : SecondType Msec : MsecTypeNullObjectTypeATIS-0300003.2017 11 Table 3.7 Artificial “CHOICE“ Creation for Accommodating Two Definitions ASN.1 Definition UML Model Schema (a) Abstract Syntax 1 AccessControl := SEQUENCE entityIdentifier 0 IMPLICIT GraphicString (SIZE (164), en

14、cryptedString 1 IMPLICIT OCTET STRING (SIZE (164) (b) Abstract Syntax 2 AccessControl := SEQUENCE entityIdentifier 0 IMPLICIT GraphicString (SIZE 164), initializationVector1IMPLICIT OCTET STRING (SIZE (8), keyIdentifier 2 IMPLICIT INTEGER, encryptedString 3 IMPLICIT OCTET STRING (SIZE (864) Schema D

15、ata Structure Diagram AccessControl1Type EntityIdentifier : EntityIdentifierType EncrytedString : EncrytedStringTypeAccessControl2Type EntityIdentifier : EntityIdentifierType InitializationVector : OctetStringType KeyIdentifier : Integer EncryptedString : EncrytedStringTypeAccessControlTypeAccessCon

16、trol1 : AccessControl1TypeAccessControl2 : AccessControl2TypeATIS-0300003.2017 12 Table 3.8 BIT STRING ASN.1 Definition UML Model Schema ActivityType:= BIT STRING after-hours-repair (0), standby (1), after-hours-standby (2), test (3), manager-initiated-test (4), dispatch (5), no-access (6), delayed-

17、maintenance (7), release (8), deregulatedWork (9), authorize-to-work (10), Excerpt from X.680 3.8.6 bitstring type: A simple type whose distinguished values are an ordered sequence of zero, one, or more bits. Schema Data Structure Diagram ATIS-0300003.2017 13 Table 3.9 SEQUENCE: Case 1 ASN.1 Definit

18、ion Schema PersonReach:= SEQUENCE number 0 PersonNumber DEFAULT “, name 1 PersonName DEFAULT “, phone 2 PersonPhone OPTIONAL, loc 3 PersonLocation OPTIONAL, email 4 PersonEmail OPTIONAL, fax 5 PersonFax OPTIONAL, respon 6 PersonRespon OPTIONAL, pager 7 PersonPhone OPTIONAL, The reason for mapping Nu

19、mber field as optional is that no one in the industry is using this field. Excerpt from X.680 3.8.56 sequence types: Types defined by referencing an ordered list of types (some of which may be declared to be optional); each value of the sequence type is an ordered list of values, one from each compo

20、nent type. ATIS-0300003.2017 14 UML Model Schema Data Structure Diagram PersonReachType Number : PersonNumberType Name : PersonNameType Phone : PersonPhoneType Loc : PersonLocationType Email : PersonEmailType Fax : PersonFaxType Respon : PersonResponType Pager : PersonPhoneTypeATIS-0300003.2017 15 T

21、able 3.10 SEQUENCE: Case 2 ASN.1 Definition UML Model Schema WeekMask:=SEQUENCE daysOfWeek BIT STRING sunday (0), monday (1), tuesday (2), wednesday (3), thursday (4), friday (5), saturday (6), . DEFAULT 1111111B, intervalsOfDay SET OF SEQUENCE intervalStart Time24, intervalEnd Time24, . DEFAULT 0,0

22、,23,59, . Schema Data Structure Diagram WeekMaskType DaysOfWeek : DaysOfWeekType IntervalsOfDay : IntervalsOfDayTypeDaysOfWeekType Sunday : Boolean Monday : Boolean Tuesday : Boolean Wednesday : Boolean Thursday : Boolean Friday : Boolean Saturday : Boolean IntervalStart : Time24Type IntervalEnd : T

23、ime24TypeIntervalsOfDayType0n1ATIS-0300003.2017 16 Table 3.11 SET ASN.1 Definition (X.680) UML Model Schema CustomerRecord := SET name 0 VisibleString, mailingAddress 1 VisibleString, accountNumber 2 INTEGER, balanceDue 3 INTEGER OPTIONAL, Excerpt from X.680 3.8.58 set types: Types defined by refere

24、ncing a fixed, unordered, list of distinct types (some of which may be declared to be optional); each value in the set type is an unordered list of values, one from each of the component types. Schema Data Structure Diagram CustomerRecordType Name : VisibleStringType MailingAddress : VisibleStringTy

25、pe AccountNumber : Integer BalanceDue : IntegerATIS-0300003.2017 17 Table 3.12 SET OF SEQUENCE ASN.1 Definition UML Model Schema ActivityDuration:=SET OF SEQUENCE duration 0 TimeInterval, billable 1 BOOLEAN DEFAULT TRUE, type 2 ActivityType OPTIONAL, Excerpt from X.680 3.8.59 set-of types: Types def

26、ined by referencing a single component type; each value in the set-of type is an unordered list of zero, one, or more values of the component type. Schema Data Structure Diagram Duration : TimeIntervalType Billable : Boolean Type : ActivityTypeTypeActivityDurationType0n1ATIS-0300003.2017 18 Table 3.

27、13 SET OF CHOICE ASN.1 Definition UML Model Schema CallBackInfoList:=SET OF CHOICE escalation 0PersonReach, beforeAutoTest 1PersonReach, afterCleared 2PersonReach, . Excerpt from X.680 3.8.59 set-of types: Types defined by referencing a single component type; each value in the set-of type is an unor

28、dered list of zero, one, or more values of the component type. Schema Data Structure Diagram CallBackInfoListTypeEscalation : PersonReachTypeBeforeAutoTest : PersonReachTypeAfterCleared : PersonReachType0n1ATIS-0300003.2017 19 Table 3.14 SET OF with SIZE ASN.1 Definition UML Model Schema ElectronicM

29、ailAddressRange:= SET SIZE (064) OF GraphicString(SIZE(064) Schema Data Structure Diagram Table 3.15 OCTET STRING Excerpt from X.680 UML Model Schema 3.8.48 octetstring type: A simple type whose distinguished values are an ordered sequence of zero, one, or more octets, each octet being an ordered se

30、quence of eight bits. C.2.6 Octet string C.2.6.1 Use an octet string type to model binary data whose format and length are unspecified, or specified elsewhere, and whose length in bits is a multiple of eight. EXAMPLE G4FacsimileImage := OCTET STRING - a sequence of octets conforming to - Recommendat

31、ions T.5 and T.6. image G4FacsimilePage := 3FE2EBAD471005H ElectronicMailAddressRangeTypeGraphicStringType0641OctetStringTypeATIS-0300003.2017 20 Table 3.16 SEQUENCE OF ASN.1 Definition (X.711) UML Model Schema AttributeValueAssertion := SEQUENCE type AttributeType, assertion AttributeValue Relative

32、DistinguishedName := SET OF AttributeValueAssertion RDNSequence := SEQUENCE OF RelativeDistinguishedName DistinguishedName:= RDNSequence Excerpt from X.680 3.8.57 sequence-of types: Types defined by referencing a single component type; each value in the sequence-of type is an ordered list of zero, o

33、ne, or more values of the component type. Schema Data Structure Diagram RDNSequenceTypeAttributeValueAssertionType Type : AttributeTypeType Assertion : AttributeValueType0n1ATIS-0300003.2017 21 Table 3.17 Restricted Inheritance Based on CMIP Specification (see Annexes A through H) ASN.1 Definition (

34、X.711) UML Model Schema ObjectInstance:= CHOICE distinguishedName 2 IMPLICIT DistinguishedName, nonSpecificForm 3 IMPLICIT OCTET STRING, localDistinguishedName 4 IMPLICIT RDNSequence ASN.1 Definition (Annexes A through H) ManagedObjectInstance:= ObjectInstance Excerpt from Annexes A through H 7.5 Su

35、pporting Productions . AttributeId, ObjectClass, ObjectInstance FROM CMIP-1 joint-iso-ccitt(2) ms(9) cmip(1) modules(0) protocol(3); Only the Distinguished Name and Local Distinguished Name forms are supported. Schema Data Structure Diagram ManagedObjectInstanceTypeDistinguishedName : DistinguishedN

36、ameTypeLocalDistinguishedName : RDNSequenceTypeATIS-0300003.2017 22 Table 3.18 Simple “typedef“ ASN.1 Definition UML Model Schema HandOffLocation:= GraphicString(SIZE(064) Excerpt from Annexes A through H 5.1 Use of GraphicString syntax Within North America, the character set for GraphicString shoul

37、d be the same as the set of characters defined for ASCII printableString. Excerpt from X.680 Table 5 PrintableString Name GraphicCapital letters A, B, . ZSmall letters a, b, . zDigits 0, 1, . 9Space (space)Apostrophe Left Parenthesis (Right Parenthesis )Plus sign +Comma ,Hyphen -Full stop .Solidus /

38、Colon :Equal sign =Question mark ?GraphicStringTypeHandOffLocationTypeATIS-0300003.2017 23 Table 3.19 Complex “typedef“: Case 1 ASN.1 Definition UML Model Schema AdditionalTroubleInfoList:= SET OF GraphicString GDMO Definition 7.2.8 Additional Trouble Information List The Additional Trouble Informat

39、ion List attribute further describes the selected Trouble Type. A minimum of 256 octets shall be supported, regardless of the number of values in the set. The manager can only add information, but not remove it. It is possible that the oldest information may be lost if an implementation has restrictions on the maximum size. additionalTroubleInfoList ATTRIBUTE WITH ATTRIBUTE SYNTAX GNMTA.AdditionalTroubleInfoList; MATCHES FOR EQUALITY, SET-INTERSECTION, SET-COMPARISON; REGISTERED AS trAttribute 8; Schema Data Structure Diagram GraphicStringTypeAdditionalTroubleInfoListType1n1