ETSI TS 101 811-2-3-2003 Broadband Radio Access Networks (BRAN) HIPERLAN Type 2 Conformance testing for the packet based convergence layer Part 2 Ethernet Service Specific Converge.pdf

1、 ETSI TS 101 811-2-3 V1.2.1 (2003-07)Technical Specification Broadband Radio Access Networks (BRAN);HIPERLAN Type 2;Conformance testing for the packet based convergence layer;Part 2: Ethernet Service Specific Convergence Sublayer SSCS);Sub-part 3: Abstract Test Suite (ATS) specificationfloppy3 ETSI

2、ETSI TS 101 811-2-3 V1.2.1 (2003-07) 2 Reference RTS/BRAN-0024TA4-2-3 Keywords access, ATS, HIPERLAN, testing ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregist

3、re la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents

4、between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document ma

5、y be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editoretsi.org Copyright Notification No part may be reproduce

6、d except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members.

7、TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 101 811-2-3 V1.2.1 (2003-07) 3 Contents Intellectual Property

8、Rights5 Foreword.5 1 Scope 6 2 References 6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7 4 Abstract Test Method (ATM).8 4.1 Test architecture .8 4.2 Test Configurations 9 4.2.1 Test Configurations for MT9 4.2.2 Test Configurations for AP.9 5 Untestable Test Purposes (TP) .

9、10 6 ATS conventions10 6.1 Naming conventions.10 6.1.1 Declarations part.10 6.1.1.1 General10 6.1.1.2 Test suite operations definition .10 6.1.1.3 Test suite parameter declarations 10 6.1.1.4 Test case selection expression definition 11 6.1.1.5 Test suite constant declarations.11 6.1.1.6 Test suite

10、variable declarations .11 6.1.1.7 Test case variable declarations11 6.1.1.8 Timer declarations.11 6.1.1.9 ASP type definitions .11 6.1.1.10 PDU type definitions.12 6.1.1.11 CM type definitions.12 6.1.1.12 Alias definitions 12 6.1.2 Constraints part.12 6.1.2.1 General12 6.1.3 Dynamic part 12 6.1.3.1

11、General12 6.1.3.2 Test Case (TC) identifier.12 6.1.3.3 Test step identifier.13 6.1.3.4 Default identifier .13 6.1.3.5 Label identifier13 6.1.3.6 ATS abbreviations.13 6.2 Implementation conventions 14 6.2.1 Declaration part 14 6.2.2 Constraint part 14 6.2.3 Dynamic part 14 7 Abstract testing service

12、primitives .14 7.1 Tester primitives.14 7.2 RLC primitives.14 Annex A (normative): Abstract Test Suite (ATS) .15 A.1 The TTCN Graphical form (TTCN.GR) 15 A.2 The TTCN Machine Processable form (TTCN.MP)15 Annex B (normative): Partial PIXIT proforma for H/2 Ethernet SSCS MT .16 B.1 Identification summ

13、ary.16 ETSI ETSI TS 101 811-2-3 V1.2.1 (2003-07) 4 B.2 ATS summary 16 B.3 Test laboratory16 B.4 Client identification17 B.5 SUT 17 B.6 Protocol layer information17 B.6.1 Protocol identification 17 B.6.2 IUT information .18 Annex C (normative): Partial PIXIT proforma for H/2 Ethernet SSCS AP 28 C.1 I

14、dentification summary.28 C.2 ATS summary 28 C.3 Test laboratory28 C.4 Client identification29 C.5 SUT 29 C.6 Protocol layer information29 C.6.1 Protocol identification 29 C.6.2 IUT information .30 Annex D (normative): PCTR Proforma for H/2 Ethernet SSCS MT39 D.1 Identification summary.39 D.1.1 Proto

15、col conformance test report39 D.1.2 IUT identification.39 D.1.3 Testing environment.39 D.1.4 Limits and reservation40 D.1.5 Comments.40 D.2 IUT Conformance status 40 D.3 Static conformance summary .40 D.4 Dynamic conformance summary41 D.5 Static conformance review report.41 D.6 Test campaign report4

16、2 D.7 Observations.42 Annex E (normative): PCTR Proforma for H/2 Ethernet SSCS AP .43 E.1 Identification summary.43 E.1.1 Protocol conformance test report43 E.1.2 IUT identification.43 E.1.3 Testing environment.43 E.1.4 Limits and reservation44 E.1.5 Comments.44 E.2 IUT Conformance status 44 E.3 Sta

17、tic conformance summary .44 E.4 Dynamic conformance summary45 E.5 Static conformance review report.45 E.6 Test campaign report46 E.7 Observations.46 History 47 ETSI ETSI TS 101 811-2-3 V1.2.1 (2003-07) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may

18、 have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI st

19、andards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of

20、other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Project Broadband Radio Access Networks (BRAN). The present document is part 2,

21、 sub-part 3 of a multi-part deliverable. Full details of the entire series can be found in part 1, sub-part 1 10. ETSI ETSI TS 101 811-2-3 V1.2.1 (2003-07) 6 1 Scope The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to test TS 101 493-2 2. The objective of the prese

22、nt document is to provide a basis for conformance tests for BRAN, HIPERLAN Type 2 equipment giving a high probability of air interface inter-operability between different manufacturers BRAN, HIPERLAN Type 2 equipment. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 5 and

23、ISO/IEC 9646-2 6) as well as the ETSI rules for conformance testing (ETS 300 406 4) are used as a basis for the test methodology. Annex A provides the Tree and Tabular Combined Notation (TTCN) part of the ATS. Annex B provides the Partial Protocol Implementation Extra Information for Testing (PIXIT)

24、 Proforma of the MT side ATS. Annex C provides the Partial Protocol Implementation Extra Information for Testing (PIXIT) Proforma of the AP side ATS. Annex D provides the Protocol Conformance Test Report (PCTR) Proforma of the MT side ATS. Annex E provides the Protocol Conformance Test Report (PCTR)

25、 Proforma of the AP side ATS. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For

26、a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. 1 ETSI TS 101 493-1 (V1.1.1): “Broadband Ra

27、dio Access Networks (BRAN); HIPERLAN Type 2; Packet based Convergence Layer; Part 1: Common Part“. 2 ETSI TS 101 493-2 (V1.2.1): “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Packet based Convergence Layer; Part 2: Ethernet Service Specific Convergence Sublayer (SSCS)“. 3 ETSI TS 101 823

28、-2-3 (V1.3.1): “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Conformance Testing for the Data Link Control (DLC) Protocol; Part 2: Radio Link Control (RLC) Sublayer; Sub-part 3: Abstract Test Suite (ATS) specification“. 4 ETSI ETS 300 406: “Methods for Testing and Specification (MTS); Pr

29、otocol and profile conformance testing specifications; Standardization methodology“. 5 ISO/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. 6 ISO/IEC 9646-2: “Information technology - Open Systems Intercon

30、nection - Conformance testing methodology and framework - Part 2: Abstract test suite specification“. 7 ISO/IEC 9646-3: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The tree and tabular combined notation“. ETSI ETSI TS 101 811-2-3 V

31、1.2.1 (2003-07) 7 8 ISO/IEC 9646-6: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification“. 9 ISO/IEC 9646-7: “Information technology - Open Systems Interconnection - Conformance testing methodology and fr

32、amework - Part 7: Implementation conformance statement“. 10 ETSI TS 101 811-1-1: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Conformance testing for the packet based convergence layer; Part 1: Common part; Sub-part 1: Protocol Implementation Conformance Statement (PICS) proforma“. 11 E

33、TSI 101 811-2-2: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Conformance testing for the packet based convergence layer; Part 2: Ethernet Service Specific Convergence Sublayer (SSCS); Sub-part 2: Test Suite Structure and Test Purposes (TSS - The minimum value allowed, which will use th

34、e suffix “_min“; - The value actually implemented, with no suffix; EXAMPLE 1: T201_max, T201_min, and T201. 2) Not standardized: - Those not defined in the protocol standard, i.e. for execution use, e.g. a timer waiting for a response. These timers begin with the prefix “T_“, followed by a string in

35、 lowercase letters. EXAMPLE 2: T_resp represents a timer for controlling the response time of the IUT. 6.1.1.9 ASP type definitions The general conventions in clause 6.1.1.1 apply. The identifier of an ASP type uses the same name as the name defined in the protocol standard. ETSI ETSI TS 101 811-2-3

36、 V1.2.1 (2003-07) 126.1.1.10 PDU type definitions The general conventions in clause 6.1.1.1 apply. The PDU type identifier shall identify the related structure or type as defined in the protocol standard. 6.1.1.11 CM type definitions The CM types are defined as the ASP types without sub-fields. 6.1.

37、1.12 Alias definitions Alias definitions are not used. 6.1.2 Constraints part This clause describes the naming conventions chosen for the elements of the ATS constraints part. 6.1.2.1 General Constraints shall be written with the first letter in uppercase, and the rest in lowercase. The first part o

38、f the constraint declaration identifier name is equivalent to the corresponding type identifier used in the declaration part. The second part of the name describes the content of this constraint. EXAMPLE: Declaration part: HEADER_FIELD; Constraint part: Header_field_paging. 6.1.3 Dynamic part This c

39、lause describes the naming conventions used for the elements of the ATS dynamic part. 6.1.3.1 General All test cases shall be listed in the order in which they appear in TS 101 811-2-2 11. 6.1.3.2 Test Case (TC) identifier The identifier of the test case is built in the same way as for the test purp

40、ose described in TS 101 811-2-2 11, with the exception that “TP“ is replaced by “TC“. The identifier of a TC is built according to table 2. Table 2: TC naming convention Identifier: TC_ = side type AP Access Point MT Mobile Terminal = protocol group ESP Ethernet Service Specific procedures = functio

41、nal module AS Association DL DLC connection HN Handover ML Multicast x = Type of testing CA Capability Tests BV Valid Behaviour Tests BI Invalid Behaviour Tests BO Inopportune Behaviour Tests = sequential number (000 to 999) Test Purpose Number EXAMPLE: TP identifier: TP/MT/ESP/AS/BV-010; TC identif

42、ier: TC_MT_ESP_AS_BV_010. ETSI ETSI TS 101 811-2-3 V1.2.1 (2003-07) 136.1.3.3 Test step identifier The test step identifier is built of substrings in lowercase letters, preceded by a string of uppercase letters. Underscore characters join the substrings. The first substring indicates the main functi

43、on of the test step; e.g. PR for preamble, PO for postamble, LTS for local tree and STP for general test step. The second substring indicates the purpose of the step. EXAMPLE: PO_release_duc. 6.1.3.4 Default identifier The default identifiers begin with the prefix “DF_“, followed by a string in lowe

44、rcase letters. 6.1.3.5 Label identifier The identifiers in the label column is built according to table 3. Table 3: Naming convention for verdict assignment identifier Identifier: = type of table TB Test Body CS Check State test step DF DeFault PO POstamble PR PReamblTS TestStep = sequential number

45、(00 to 99) Label number 6.1.3.6 ATS abbreviations These abbreviations are used to shorten identifier names: addr address ack acknowledgement bear bearer cap capability cfm confirmchn channel con connection ctrl control est establish ext extensionid identification ind indicationinfo information max m

46、aximum min minimum par parameter prop proprietary rel release req request rsp responsestd standard sys systemETSI ETSI TS 101 811-2-3 V1.2.1 (2003-07) 146.2 Implementation conventions 6.2.1 Declaration part The comment line of single element TTCN tables (e.g. test suite constants) is used to give a

47、reference where the format and content of the element is described in the relevant protocol standards. Any particularity of the element format or content is described in the comment line. The comment line in the header of multi element TTCN tables (e.g. ASP) is used to reference to the protocol stan

48、dard. The detailed comments are used to describe any particularity of the table. In the ASP and PDU declarations the comment column is further used to give information about the parameter/field value, in particular if the parameter/field contains a fixed spare value. 6.2.2 Constraint part The ASPs a

49、nd PDUs are defined in a way that all relevant parameters/fields are parameterized. That improves the transparency of the constraints in the dynamic part, as all values, which are relevant for the test, are always present. Generally no modified constraints are used. This allows an easier reuse and adaptation of constraints if they are reused in other test specifications. The Comment line of a constraint always contains a reference to the relevant protocol standard. The detailed comment footer is used to describe any particulari