ANSI INCITS 245-1995 Information Technology - Fiber Distributed Data Interface (FDDI) - Token Ring Media Access Control Conformance Testing (FDDI MAC ATS).pdf

《ANSI INCITS 245-1995 Information Technology - Fiber Distributed Data Interface (FDDI) - Token Ring Media Access Control Conformance Testing (FDDI MAC ATS).pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS 245-1995 Information Technology - Fiber Distributed Data Interface (FDDI) - Token Ring Media Access Control Conformance Testing (FDDI MAC ATS).pdf（73页珍藏版）》请在麦多课文档分享上搜索。

1、ANSI INCITS 245-1995 (R2001)(formerly ANSI X3.245-1995 (R2001)for Information Technology Fiber Distributed Data Interface (FDDI) Token Ring Media Access ControlConformance Testing (FDDI MAC ATS)ANSIX3.245-1995SecretariatInformation Technology Industry CouncilApproved October 27, 1995American Nationa

2、l Standards Institute, Inc.AbstractConformance tests are specified to test the Media Access Control (MAC) functions of an FDDIpath. FDDI is a set of standards which define a 100 Mbps token ring architecture and uses fiberoptics as the transmission medium over distances of several km in extent.Americ

3、an National Standardfor Information Technology Fiber Distributed Data Interface (FDDI) Token Ring Media Access Control Conformance Testing (FDDI MAC ATS)AmericanNationalStandardApproval of an American National Standard requires review by ANSI that therequirements for due process, consensus, and othe

4、r criteria for approval havebeen met by the standards developer.Consensus is established when, in the judgment of the ANSI Board of StandardsReview, substantial agreement has been reached by directly and materiallyaffected interests. Substantial agreement means much more than a simplemajority, but n

5、ot necessarily unanimity. Consensus requires that all views andobjections be considered, and that a concerted effort be made toward theirresolution.The use of American National Standards is completely voluntary; their existencedoes not in any respect preclude anyone, whether he has approved the stan

6、dardsor not, from manufacturing, marketing, purchasing, or using products, processes,or procedures not conforming to the standards.The American National Standards Institute does not develop standards and will inno circumstances give an interpretation of any American National Standard.Moreover, no pe

7、rson shall have the right or authority to issue an interpretation ofan American National Standard in the name of the American National StandardsInstitute. Requests for interpretations should be addressed to the secretariat orsponsor whose name appears on the title page of this standard.CAUTION NOTIC

8、E: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, or withdrawthis standard. Purchasers of American National Standards may receive currentinformation on a

9、ll standards by calling or writing the American National StandardsInstitute.CAUTION: The developers of this standard have requested that holders of patents that may be required for theimplementation of the standard disclose such patents to the publisher. However, neither the developers nor the publi

10、sherhave undertaken a patent search in order to identify which, if any, patents may apply to this standard. As of the date ofpublication of this standard and following calls for the identification of patents that may be required for the implementationof the standard, no such claims have been made. N

11、o further patent search is conducted by the developer or publisher inrespect to any standard it processes. No representation is made or implied that licenses are not required to avoidinfringement in the use of this standard.Published byAmerican National Standards Institute11 West 42nd Street, New Yo

12、rk, New York 10036Copyright 1996 by Information Technology Industry Council (ITI)All rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of ITI, 1250 Eye Street NW,Washington, DC 20005.Printed in th

13、e United States of AmericaiForeword ii1 Scope12 Normative references.13 Abbreviations 24 Organization of test suite25 Timer definitions 36 Tester implementation37 PICS and PIXIT information38 Test specification in TTCN .4Figure1 MAC test configuration.1AnnexesA PIXIT Proforma for Fiber Distributed D

14、ata Interface (FDDI) Token Ring Media Access Control Protocol (MAC) 61B Bibliography 65ContentsPageiiThe Fiber Distributed Data Interface (FDDI) is intended for use in a high-performance general-purpose multi-station network and is designed for effi-cient operation with a peak data rate of 100 Mbit/

15、s. It uses a Token RingArchitecture with optical fiber as the transmission medium. FDDI providesfor hundreds of stations operating over an extent of tens of kilometers.FDDI Media Access Control (MAC) specifies the lower sublayer of the DataLink Layer for FDDI. It specifies access to the medium, incl

16、uding address-ing, data checking and data framing. MAC also specifies the receiver andtransmitter state machines. This Abstract Test Suite (ATS) provides a con-formance test for FDDI MAC. Since MAC is a protocol that deals primarilywith complete PDUs, the Tree and Tabular Combined Notation TTCN lan-

17、guage specified in ISO 9646 is used to specify MAC protocol tests. Four other standards are under development which, when complete, willprovide a complete conformance test of an FDDI station:a) An ATS for FDDI Physical Medium Dependent (PMD) that provides aconformance test for FDDI PMD. PMD specifie

18、s the optical interface ofFDDI stations. PMD is not a protocol standard and this ATS requires themeasurement of physical quantities such as optical power, wavelength,and signal jitter. The PMD ATS differs from the methodology of higherlevel protocol conformance tests written using the TTCN, because

19、theTTCN notation does not provide a suitable vehicle for Physical Layertesting, where there is no concept of a protocol data unit and wherephysical quantities must be measured;b) An ATS for the FDDI Physical Layer Protocol (PHY) that provides aconformance test for FDDI PHY. PHY specifies the upper s

20、ublayer ofthe Physical Layer for the FDDI, including the data encode/decode,framing and clocking, as well as the elasticity buffer, smoothing andrepeat filter functions. FDDI PHY, however, does contain several statemachines and implements a protocol at the level of FDDI code symbols.The only physica

21、l quantity that must be measured in this conformancetest is frequency. The PHY ATS cannot use the TTCN notation and anotation is developed in the PHY ATS for specifying test patterns andexpected results in terms of FDDI code symbol strings;c) An ATS for FDDI Station Management (SMT) that provides a

22、confor-mance test for FDDI SMT. SMT specifies the local portion of the systemmanagement application process for FDDI, including the control requiredfor proper operation of an FDDI station in an FDDI ring. SMT providesservices such as connection management, station insertion and removal,station initi

23、alization, configuration management and fault recovery, com-munications protocol for external authority, scheduling policies, and thecollection of statistics. SMT interacts with PMD, PHY, and MAC.Therefore, an ATS for portions of SMT that use MAC PDUs can be speci-fied in TTCN, while other portions

24、require other approaches;d) A Protocol Implementation Conformance Statement (PICS) proformafor FDDI that provides a statement of the mandatory and optionalrequirements of each of the four FDDI base standards. The PICS profor-ma is used to identify requirements for conformance testing and tospecify o

25、ptional functionality requirements, particularly by workshops forfunctional standards and profiles.Foreword (This foreword is not part of American National Standard X3.245-1995.)iiiThis standard was developed by Task Group X3T9.3 of AccreditedStandards Committee X3 during 1990, 1991, and 1992. The s

26、tandardsapproval process started in 1992.This standard contains two annexes, both of which are informative and notconsidered part of this standard.Requests for interpretations, suggestions for improvement or addenda, ordefect reports are welcome. They should be sent to the X3 Secretariat,Information

27、 Technology Industry Council, 1250 Eye Street, NW,Washington, DC 20005.This standard was processed and approved for submittal to ANSI byAccredited Standards Committee on Information Technology, X3.Committee approval of the standard does not imply that all committeemembers voted for the standard. At

28、the time it approved this standard, theX3 Committee had the following members:James D. Converse, ChairDonald C. Loughry, Vice-ChairJoanne Flanagan, SecretaryOrganization Represented Name of RepresentativeAMP, Inc. Edward KellyCharles Brill (Alt.)American Nuclear SocietyGeraldine C. MainSally Hartzel

29、l (Alt.)Apple Computer, IncDavid K. MichaelATF: Fail (when used in the verdict column of the Dynamic Behavior tables);I: Inconclusive (when used in the verdict column of the Dynamic Behavior tables);IUT: Implementation Under Test;P: Pass (when used in the verdict column of the Dynamic Behavior table

30、s);PDU: Protocol Data Unit defined in terms of MAC frames;PHY: Physical Layer Protocol;PICS: Protocol Implementation Conformance Statement;PIXIT: Protocol Implementation eXtra Information for Testing;TTCN: Tree and Tabular Combined Notation.4 Organization of test suiteThe test cases are divided into

31、 six major groups:Basic: Tests the ability of the IUT to transmit, receive, repeat, and strip frames. The transmission testsare further divided into asynchronous and synchronous transmission. In order to test the synchronoustransmission, the IUT must be able to be configured and forced to transmit d

32、ata at test operatorscontrol; otherwise, these tests should not be selected for testing.Claim Token: Tests the ability of the IUT to participate in the Claim Token process used to initializethe network. The test includes test cases where the IUT should win the claim and cases where itshould lose.Bea

33、coning: Tests IUTs participation in the Beacon process.Addressing: Tests the IUTs ability to handle short and long addresses, and broadcasting.Timer: Tests the IUTs response to the expiration of timers TRT and TVX._1)Available from the American National Standards Institute, 11 West 42nd Street, New

34、York, NY 10036.ANSI X3.245-19953Frame Error: Tests the ability of the IUT to detect errors in frames and tokens.This test suite is applicable only to equipment using 48-bit addresses. The IUT is expected to processand repeat some frames with short addresses it receives, but it will not generate any

35、short addressframes.5 Timer definitionsA set of timers, as described below, is used in the test suite; their values must be initialized prior to thebeginning of testing unless a default value is specified. Even though the minimum timer unit is inmicroseconds, an actual implementation of the test sui

36、te may require a hardware timer with higherresolutions.T_Req: The target token rotation timer configured in the IUT in unit of microseconds. This value will beconverted to units of 80 nanoseconds for the claim process.TVX: The Valid-Transmission Timer configured in the IUT, in microseconds.T_Max: Th

37、e maximum token rotation time in microseconds.D_Max: The maximum ring latency. The default value is 1617 microseconds.T_Pri: The threshold value of the highest priority level implemented on the IUT. If priority is notsupported, then the value of the negotiated TRT is used.Topr: Time required for a t

38、est operator to initiate operations on the IUT, for example, startingsynchronous mode transmission. This is used in conjunction with the TTCN Implicit Send event for testcoordination. The test suite uses a default value of 3 minutes.Aux_30: Maximum time allowed for SMT to produce a response, per SMT

39、 specification, the value of30 seconds is used.6 Tester implementationSince the abstract test suite specifies the test sequences at the MAC frame level the implementationof the MAC tester must provide the following functions: Support of the MAC and PHY layer interface; Translation of 5-bit symbols r

40、eceived from PHY into 4-bit units and assembly of these units intoMAC frames. Note that the PDU fields in this ATS are defined in a mixture of 5-bit symbols and 4-bitdata, as appropriate, it is up to the tester implementation to select the internal desirablerepresentations; Transmission of frames as

41、 specified in the TTCN sequence, including translation of symbols, andgeneration of preambles of proper length; Automatic transmission of IDLE symbols when there is nothing to transmit from the TTCNsequence; Generation of Frame Check Sequences (FCS), and when requested, insertion of incorrect FCS.7

42、PICS and PIXIT informationAdditional information about the IUT must be provided in order to perform tests based on thisAmerican National Standard. Information is needed to: (1) configure the tester and the FDDI ring, (2)select applicable test cases for the IUT, and (3) perform the test cases selecte

43、d. They are obtainedfrom answers to the Protocol Implementation Conformance Statements (PICS) and ProtocolImplementation Extra Information for Testing (PIXIT) proforma. The PICS proforma for the FDDI MACis specified in ANSI X3.262, FDDI PICS. The PIXIT proforma for this ATS is specified in annex A.A

44、NSI X3.245-199548 Test specification in TTCN8.1 Test Suite OverviewTest Suite OverviewSuite Name : FDDI_MACStandards ref : ANSI X3.139-1987 or ISO 9314-2:1989PICS proforma ref : X3T9.5/92-098PIXIT proforma ref : Clause 7 of this standardPICS/PIXIT use : Test case selection and test suite parametersT

45、est Method(s) : Remote Single LayerComments :Test Case Identifier Test Case Reference Page DescriptionUsable_asynch FDDI_MAC/BASIC/TRANSMIT/Usable_asynch39 Verifies that the IUT sends frames when itcaptures an unrestricted and usable TOKEN,and there is asynchronous data to transmit.Release_Token FDD

46、I_MAC/BASIC/TRANSMIT/Release_Token39 Verifies that the IUT, after sending dataframes, will release and transmit the token.Unusable_asynch_lateTKFDDI_MAC/BASIC/TRANSMIT/Unusable_asynch_lateTK40 Verify that the IUT does not capture anunrestricted and late TOKEN (LATE_CT=1),when it has only asynchronou

47、s data totransmit.Unusable_asynch_restrictTKFDDI_MAC/BASIC/TRANSMIT/Unusable_asynch_restrictTK41 Verify that the IUT does not capture arestricted TOKEN not intended for it, whenthere is asynchronous data to transmit.Unusable_asynch_priorityFDDI_MAC/BASIC/TRANSMIT/Unusable_asynch_priority42 Verify th

48、at the IUT does not capture anunrestricted TOKEN, when IUT does nothave a priority to use it and there isasynchronous data to transmit.Unusable_asynch_nodataFDDI_MAC/BASIC/TRANSMIT/Unusable_asynch_nodata43 Verify that the IUT does not capture anunrestricted TOKEN when there is no data totransmit.Usa

49、ble_synch_earlyrestrictTKFDDI_MAC/BASIC/TRANSMIT/Usable_synch_earlyrestrictTK43 Verify that IUT captures a restricted earlyTOKEN (LATE_CT=0) and sends a frame,when there is synchronous data to transmit.Usable_synch_lateTK FDDI_MAC/BASIC/TRANSMIT/Usable_synch_lateTK44 Verify that IUT captures a restricted lateTOKEN (LATE_CT=1) and sends a frame,when there is synchrounous data to transmit.Unusable_synch_restrictTKnodataFDDI_MAC/BASIC/TRANSMIT/Unusable_synch_restrictTKnodata45 Verify that IUT does not capture a restrictedTOKEN, when there is no synchronous datato tr