1、 ETSI TS 101 811-1-2 V1.3.1 (2003-07)Technical Specification Broadband Radio Access Networks (BRAN);HIPERLAN Type 2;Conformance testing for the packet based convergence layer;Part 1: Common part;Sub-part 2: Test Suite Structure andTest Purposes (TSS Essential, or potentially Essential, IPRs notified
2、 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, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be
3、 given as to the existence of 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). T
4、he present document is part 1, sub-part 2 of a multi-part deliverable. Full details of the entire series can be found in part 1, sub-part 1 7. ETSI ETSI TS 101 811-1-2 V1.3.1 (2003-07) 5 1 Scope The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to TS 101 493-1 1. Th
5、e objective of this test specification is to provide a basis for conformance tests for Broadband Radio Access Networks (BRAN), HIPERLAN Type 2 equipment giving a high probability of air interface inter-operability between different manufacturers Broadband Radio Access Networks (BRAN), HIPERLAN Type
6、2 equipment. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 3 and ISO/IEC 9646-2 4) as well as the ETSI rules for conformance testing (ETS 300 406 2) are used as a basis for the test methodology. 2 References The following documents contain provisions which, through refe
7、rence 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 apply. For a non-specific reference, the latest version
8、 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 Radio Access Networks (BRAN); HIPERLAN Type 2; Packet based Convergence Layer; Part 1: Common Part“. 2 ETSI
9、 ETS 300 406: “Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 3 ISO/IEC 9646-1: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. 4 I
10、SO/IEC 9646-2: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“. 5 ISO/IEC 9646-6: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Proto
11、col profile test specification“. 6 ISO/IEC 9646-7: “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation conformance statements“. 7 ETSI TS 101 811-1-1: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Conformance tes
12、ting for the packet based convergence layer; Part 1: Common part; Sub-part 1: Protocol Implementation Conformance Statement (PICS) proforma“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 6 and TS 101 493-1
13、 1 apply. ETSI ETSI TS 101 811-1-2 V1.3.1 (2003-07) 6 3.2 Abbreviations For the purposes of the present document, the abbreviations defined in ISO/IEC 9646-1 3, ISO/IEC 9646-6 5, ISO/IEC 9646-7 6, TS 101 493-1 1 and the following apply: AP Access Point BI Invalid Behaviour BO Inopportune Behaviour B
14、V Valid Behaviour CA Capability tests DLC Data Link Control DUC DLC User Connection IUT Implementation Under Test MAC Medium Access Control MT Mobile Terminal PBCL Packet Based Convergence Layer PDU Protocol Data Unit PICS Protocol Implementation Conformance Statement TP Test Purposes TSS Test Suite
15、 Structure 4 Test Suite Structure 4.1 Structure Figure 1 shows the Common PBCL Test Suite Structure (TSS) including its subgroups defined for the conformance testing. Test Suite Protocol group Protocol subgroup Test group CA BV BI BO PCL-AP/ PCL-MT Common procedures Sender x Receiver x Figure 1: TSS
16、 for HIPERLAN 2 Common part PBCL The test suite is structured as a tree with a first level defined as PCL-AP or PCL-MT representing the protocol group “Common part PBCL for AP and Common part PBCL for MT“. 4.2 Test groups The test groups are organized in three levels. The first level creates one pro
17、tocol group representing the protocol services. The second level separates the protocol services in functional modules. The last level in each branch contains one or more of the standard ISO subgroups CA, BV, BI and BO. 4.2.1 Protocol groups The protocol groups identifies the common part procedures
18、as defined in TS 101 493-1 1. 4.2.1.1 Common procedures The common part procedures group is divided in two functional modules. The first functional module identifies the procedures at the sender side. The last functional module identifies the procedures at the receiver side. 4.2.2 Main test groups T
19、he main test groups are the capability group, the valid behaviour group, the invalid behaviour group and the inopportune behaviour group. ETSI ETSI TS 101 811-1-2 V1.3.1 (2003-07) 7 4.2.2.1 Capability (CA) tests This test sub group shall provide limited testing of the major IUT capabilities aiming t
20、o insure that the claimed capabilities are correctly supported, according to the PICS. 4.2.2.2 Valid Behaviour (BV) tests This test sub group shall verify that the IUT reacts in conformity with TS 101 493-1 1, after receipt or exchange of valid Protocol Data Units (PDUs). Valid PDUs means that the e
21、xchange of messages and the content of the exchanged messages are considered as valid. 4.2.2.3 Invalid Behaviour (BI) tests This test sub group shall verify that the IUT reacts in conformity with TS 101 493-1 1, after receipt of a syntactically invalid PDU. 4.2.2.4 Inopportune Behaviour (BO) tests T
22、his test sub group shall verify that the IUT reacts in conformity with TS 101 493-1 1, after receipt of a syntactically correct PDU not expected in the actual message exchange. 5 Test Purposes (TP) 5.1 Introduction 5.1.1 TP definition conventions The TPs are defined following particular rules as sho
23、wn in table 1. Table 1: TP definition rules TP Id Reference. Initial condition. Stimulus. Expected behaviour. TP Id The TP Id is a unique identifier it shall be specified according to the TP naming conventions defined in clause 5.1.2. Reference The reference should contain the references of the subj
24、ect to be validated by the actual TP (specification reference, clause, and paragraph). Initial condition The condition defines in which initial state the IUT has to be to apply the actual TP. Stimulus The stimulus defines the test event to which the TP is related. Expected behaviour Definition of th
25、e events that are expected from the IUT to conform to the base specification. ETSI ETSI TS 101 811-1-2 V1.3.1 (2003-07) 8 5.1.2 TP naming conventions The identifier of the TP is built according to table 2. Table 2: TP naming convention Identifier: TP/- = side type AP Access Point MT Mobile Terminal
26、= protocol group CPP Common Part Procedures = functional module SS Sender Side RS Receiver Side 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/MT/CPP/RS/BV-010
27、 is the tenth purpose for the valid behaviour testing of the procedures at the receiver of the common part procedures implemented at MT side. 5.1.3 Sources of TP definitions All TPs are specified according to TS 101 493-1 1. 5.2 Test purposes for AP 5.2.1 Procedures at the sender TP/AP/CPP/SS/CA-000
28、 Reference: TS 101 493-1 1, clause 5.3.4.2 Initial condition: DUC established. IUT is the sender. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly a continuous stream of CPCS PDU to send. TP/AP/CPP/SS/CA-001 Reference:
29、TS 101 493-1 1, clause 5.3.4.2 Initial condition: DUC established. IUT is the sender. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly a discontinuous flow of CPCS PDU to send. TP/AP/CPP/SS/CA-002 Reference: TS 101 493-
30、1 1, clause 5.3.4.2 Initial condition: DUC established. IUT is the sender. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT segments correctly a large CPCS PDU (near the value). ETSI ETSI TS 101 811-1-2 V1.3.1 (2003-07) 9 5.2.2 Procedure
31、s at the receiver TP/AP/CPP/RS/CA-000 Reference: TS 101 493-1 1, clause 5.3.4.3 Initial condition: DUC established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT discards a received CPCS PDU, if the calculated PAD
32、 field is longer than 47 octets. TP/AP/CPP/RS/CA-001 Reference: TS 101 493-1 1, clause 5.3.4.3 Initial condition: DUC established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT discards a received CPCS PDU, if the
33、 value of the extracted Length field is zero. TP/AP/CPP/RS/CA-002 Reference: TS 101 493-1 1, clause 5.3.4.3 Initial condition: DUC established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT discards a received CPC
34、S PDU, if the value of the extracted Length field is higher than the value of the parameter. TP/AP/CPP/RS/CA-003 Reference: TS 101 493-1 1, clause 5.3.4.3 Initial condition: DUC established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IU
35、T. Check, that: the IUT delivers the payload of a correctly received CPCS PDU to SSCS higher layer. TP/AP/CPP/RS/CA-004 Reference: TS 101 493-1 1, clause 5.3.4.3 Initial condition: DUC established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at
36、 the IUT. Check, that: the IUT manages correctly a continuous stream of received CPCS PDU. TP/AP/CPP/RS/CA-005 Reference: TS 101 493-1 1, clause 5.3.4.3 Initial condition: DUC established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT.
37、 Check, that: the IUT manages correctly a discontinuous flow of received CPCS PDU. TP/AP/CPP/RS/CA-006 Reference: TS 101 493-1 1, clause 5.3.4.3 Initial condition: DUC established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check,
38、that: the IUT reassembles correctly a large amount of received SAR_UNITDATA. 5.3 Test purposes for MT 5.3.1 Procedures at the sender TP/MT/CPP/SS/CA-000 Reference: TS 101 493-1 1, clause 5.3.4.2 Initial condition: DUC established. IUT is the sender. A loop back mechanism is implemented on top of eit
39、her CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly a continuous stream of CPCS PDU to send. TP/MT/CPP/SS/CA-001 Reference: TS 101 493-1 1, clause 5.3.4.2 Initial condition: DUC established. IUT is the sender. A loop back mechanism is implemented on top of either CPCS lay
40、er or SSCS layer at the IUT. Check, that: the IUT manages correctly a discontinuous flow of CPCS PDU to send. TP/MT/CPP/SS/CA-002 Reference: TS 101 493-1 1, clause 5.3.4.2 Initial condition: DUC established. IUT is the sender. A loop back mechanism is implemented on top of either CPCS layer or SSCS
41、layer at the IUT. Check, that: the IUT segments correctly a large CPCS PDU (near the value). ETSI ETSI TS 101 811-1-2 V1.3.1 (2003-07) 105.3.2 Procedures at the receiver TP/MT/CPP/RS/CA-000 Reference: TS 101 493-1 1, clause 5.3.4.3 Initial condition: DUC established. IUT is the receiver. A loop back
42、 mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT discards a received CPCS PDU, if the calculated PAD field is longer than 47 octets. TP/MT/CPP/RS/CA-001 Reference: TS 101 493-1 1, clause 5.3.4.3 Initial condition: DUC established. IUT is the receiv
43、er. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT discards a received CPCS PDU, if the value of the extracted Length field is zero. TP/MT/CPP/RS/CA-002 Reference: TS 101 493-1 1, clause 5.3.4.3 Initial condition: DUC established. IUT
44、is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT discards a received CPCS PDU, if the value of the extracted Length field is higher than the value of the parameter. TP/MT/CPP/RS/CA-003 Reference: TS 101 493-1 1, clause 5
45、.3.4.3 Initial condition: DUC established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT delivers the payload of a correctly received CPCS PDU to SSCS higher layer. TP/MT/CPP/RS/CA-004 Reference: TS 101 493-1 1, c
46、lause 5.3.4.3 Initial condition: DUC established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly a continuous stream of received CPCS PDU. TP/MT/CPP/RS/CA-005 Reference: TS 101 493-1 1, clause 5.3
47、.4.3 Initial condition: DUC established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly a discontinuous flow of received CPCS PDU. TP/MT/CPP/RS/CA-006 Reference: TS 101 493-1 1, clause 5.3.4.3 Ini
48、tial condition: DUC established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT reassembles correctly a large amount of received SAR_UNITDATA. ETSI ETSI TS 101 811-1-2 V1.3.1 (2003-07) 11History Document history V1.1.1 September 2000 Publication V1.1.1 January 2001 Publication as EN 301 811-1-2 V1.2.1 December 2001 Publication V1.3.1 July 2003 Publication
