1、 ETSI TS 102 148-2-3 V1.2.1 (2004-04)Technical Specification Broadband Radio Access Networks (BRAN);HIPERACCESS;Conformance testing for the Packet based Convergence Layer;Part 2: Ethernet Service SpecificConvergence Sublayer (SSCS);Sub-part 3: Abstract Test Suite (ATS)ETSI ETSI TS 102 148-2-3 V1.2.1
2、 (2004-04) 2 Reference RTS/BRAN-0034T04-2-3R1 Keywords access, ATS, broadband, ethernet, hiperaccess, radio, 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 e
3、nregistre 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 co
4、ntents 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 docu
5、ment may 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 re
6、produced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2004. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Me
7、mbers. 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 102 148-2-3 V1.2.1 (2004-04) 3 Contents Intellectual Pr
8、operty Rights6 Foreword.6 1 Scope 7 2 References 7 3 Definitions and abbreviations.8 3.1 Definitions8 3.2 Abbreviations .8 4 Abstract Test Method (ATM).9 4.1 Test architecture .9 4.2 Test Configurations 10 4.2.1 Test Configurations for AT.10 4.2.2 Test configurations for AP10 5 Untestable Test Purpo
9、ses (TP) .10 6 ATS conventions11 6.1 Naming conventions.11 6.1.1 Declarations part.11 6.1.1.1 General11 6.1.1.2 Test suite operations definition .11 6.1.1.3 Test suite parameter declarations 11 6.1.1.4 Test case selection expression definition 11 6.1.1.5 Test suite constant declarations.12 6.1.1.6 T
10、est suite variable declarations .12 6.1.1.7 Test case variable declarations12 6.1.1.8 Timer declarations.12 6.1.1.9 ASP type definitions .12 6.1.1.10 PDU type definitions.12 6.1.1.11 CM type definitions.12 6.1.1.12 Alias definitions 13 6.1.2 Constraints part.13 6.1.2.1 General13 6.1.3 Dynamic part 1
11、3 6.1.3.1 General13 6.1.3.2 Test Case (TC) identifier.13 6.1.3.3 Test step identifier.13 6.1.3.4 Default identifier .13 6.1.3.5 Label identifier14 6.1.3.6 ATS abbreviations.14 6.2 Implementation conventions 14 6.2.1 Declaration part 14 6.2.2 Constraint part 15 6.2.3 Dynamic part 15 7 Abstract testin
12、g service primitives .15 7.1 Tester primitives.15 7.2 RLC primitives.15 Annex A (normative): Abstract Test Suite (ATS) .16 A.1 The TTCN Graphical form (TTCN.GR) 16 A.2 The TTCN Machine Processable form (TTCN.MP)16 Annex B (normative): Partial PIXIT proforma for HIPERACCESS Ethernet SSCS AT17 ETSI ET
13、SI TS 102 148-2-3 V1.2.1 (2004-04) 4 B.1 Identification summary.17 B.2 ATS summary 17 B.3 Test laboratory17 B.4 Client identification18 B.5 SUT 18 B.6 Protocol layer information18 B.6.1 Protocol identification 18 B.6.2 IUT information .19 Annex C (normative): Partial PIXIT proforma for HIPERACCESS E
14、thernet SSCS AP26 C.1 Identification summary.26 C.2 ATS summary 26 C.3 Test laboratory26 C.4 Client identification27 C.5 SUT 27 C.6 Protocol layer information27 C.6.1 Protocol identification 27 C.6.2 IUT information .28 Annex D (normative): PCTR Proforma for HIPERACCESS Ethernet SSCS AT 35 D.1 Ident
15、ification summary.35 D.1.1 Protocol conformance test report35 D.1.2 IUT identification.35 D.1.3 Testing environment.35 D.1.4 Limits and reservation36 D.1.5 Comments.36 D.2 IUT Conformance status 36 D.3 Static conformance summary .36 D.4 Dynamic conformance summary36 D.5 Static conformance review rep
16、ort.37 D.6 Test campaign report37 D.7 Observations.37 Annex E (normative): PCTR Proforma for HIPERACCESS Ethernet SSCS AP.38 E.1 Identification summary.38 E.1.1 Protocol conformance test report38 E.1.2 IUT identification.38 E.1.3 Testing environment.38 E.1.4 Limits and reservation39 E.1.5 Comments.3
17、9 E.2 IUT Conformance status 39 E.3 Static conformance summary .39 E.4 Dynamic conformance summary39 E.5 Static conformance review report.40 E.6 Test campaign report40 E.7 Observations.40 ETSI ETSI TS 102 148-2-3 V1.2.1 (2004-04) 5 Annex F (informative): Bibliography.41 History 42 ETSI ETSI TS 102 1
18、48-2-3 V1.2.1 (2004-04) 6 Intellectual Property Rights IPRs essential or potentially essential to the present document may 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 3
19、14: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, 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,
20、 no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI 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 Technic
21、al Specification (TS) has been produced by ETSI Project Broadband Radio Access Networks (BRAN). The present document is part 2, sub-part 3 of a multi-part covering the testing specification for Ethernet Service Specific Convergence Sublayer (SSCS), of the BRAN HIPERACCESS system, as identified below
22、: Part 1: “Common part“; Part 2: Ethernet Service Specific Convergence Sublayer (SSCS). Sub-part 1: “Protocol Implementation Conformance Statement (PICS) proforma“; Sub-part 2: “Test Suite Structure and Test Purposes (TSS Sub-part 3: “Abstract Test Suite (ATS)“. ETSI ETSI TS 102 148-2-3 V1.2.1 (2004
23、-04) 7 1 Scope The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to test the BRAN HIPERACCESS; Packet based Convergence Layer; Part 2: Ethernet Service Specific Convergence Sublayer (SSCS). The objective of the present document is to provide a basis for conformance
24、tests for BRAN HIPERACCESS equipment giving a high probability of air interface inter-operability between different manufacturers BRAN HIPERACCESS equipment. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 5 and ISO/IEC 9646-2 6) as well as the ETSI rules for conformance
25、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) Proforma of the AT side ATS. - Annex C provides the Par
26、tial 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 AT side ATS. - Annex E provides the Protocol Conformance Test Report (PCTR) Proforma of the AP side ATS. 2 References The fol
27、lowing 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 a specific reference, subsequent revisions do not
28、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 102 117-1: “Broadband Radio Access Networks (BRAN); HIPERACCESS; Packet based Conve
29、rgence Layer; Part 1: Common Part“. 2 ETSI TS 102 117-2: “Broadband Radio Access Networks (BRAN); HIPERACCESS; Packet based Convergence Layer; Part 2: Ethernet Service Specific Convergence Sublayer“. 3 ETSI TS 102 149-3 V1.2.1: “Broadband Radio Access Networks (BRAN); HIPERACCESS; Conformance Testin
30、g for the Data Link Control (DLC) layer; Sub-part 3: Abstract Test Suite (ATS) specification“. 4 ETSI ETS 300 406: “Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 5 ISO/IEC 9646-1: “Information technology - Open Sys
31、tems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. 6 ISO/IEC 9646-2: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract test suite specification“. 7 ISO/IEC 9646-3: “Information tech
32、nology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The tree and tabular combined notation“. ETSI ETSI TS 102 148-2-3 V1.2.1 (2004-04) 8 8 ISO/IEC 9646-6: “Information technology - Open Systems Interconnection - Conformance testing methodology and framewor
33、k - Part 6: Protocol profile test specification“. 9 ISO/IEC 9646-7: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation conformance statement“. 10 ETSI TS 102 148-2-2: “ Broadband Radio Access Networks (BRAN); HIPERACCESS; C
34、onformance 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 the suffix “_min“; - The value actually implemented, with no suffix; EXAMPLE 1
35、: 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 lowercase letters. EXAMPLE 2: T_resp represents a timer for controlling the
36、 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. 6.1.1.10 PDU type definitions The general conventions in clause 6.1.1.1 apply. The PDU type identifi
37、er 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. ETSI ETSI TS 102 148-2-3 V1.2.1 (2004-04) 136.1.1.12 Alias definitions Alias definitions are not used. 6.1.2 Constraints par
38、t 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 of the constraint declaration identifier name is equivalent to the correspond
39、ing 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 clause describes the naming conventions used for the elements of the ATS dynami
40、c part. 6.1.3.1 General All test cases shall be listed in the order in which they appear in the Test Suite Structure (TSS) and TP document. 6.1.3.2 Test Case (TC) identifier The identifier of the test case is built in the same way as for the test purpose described TS 102 148-2-2 10, with the excepti
41、on 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 AT Access Terminal = protocole group ESP Ethernet Service Specific Procedures = functional module RF RFC 2684 x = Type of testing CA CApab
42、ility tests BV Valid Behaviour tests BI Invalid Behaviour tests BO Inoportune Behaviour tests = sequential number (000-999) Test Purpose number EXAMPLE: TP identifier: TP/AT/ESP/RF/BV-010. TC identifier: TC_AT_ESP_RF_BV_010. 6.1.3.3 Test step identifier The test step identifier is built of substring
43、s in lowercase letters, preceded by a string of uppercase letters. Underscore characters join the substrings. The first substring indicates the main function of the test step; e.g. PR for preamble, PO for postamble, Local Tree (LTS) for local tree and general test STeP (STP) for general test step. T
44、he 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 lowercase letters. ETSI ETSI TS 102 148-2-3 V1.2.1 (2004-04) 146.1.3.5 Label identifier The identifiers in the label
45、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 (00-99) Label number 6.1.3.6 ATS abbreviations These abbreviations ar
46、e 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 maximum min minimum par parameter prop proprietary rel release req reques
47、t rsp responsestd standard sys system6.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 reference where the format and content of the element is described in the relevant protocol standards. Any particula
48、rity 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 standard. The detailed comments are used to describe any particularity of the table. In the ASP and PDU declarations the
49、 comment column is further used to give information about the parameter/field value, in particular if the parameter/field contains a fixed spare value. ETSI ETSI TS 102 148-2-3 V1.2.1 (2004-04) 156.2.2 Constraint part The ASPs and 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
