1、ETSI EN 301 81 1-1-2 1.1.1 (2001-01) European Standard (Telecommunications series) 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 and Test Purposes (TSS Essential, or potential
2、ly 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 ClattD:/www.etsP.c/iDr. Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No gua
3、rantee can be given as to the existence of other IPRs not referenced in ETSI SR O00 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This European Standard (Telecommunications series) has been produced by ETSI Project Broadb
4、and Radio Access Networks (BRAN). The present document is sub-part 2 of a multi-part deliverable covering Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Conformance testing for the packet based convergence layer; Part 1: Common part, as identified below: Sub-part 1: “Protocol Implementatio
5、n Conformance Statement (PICS) proforma“; Sub-part 2: “Test Suite Structure and Test Purposes (TSS Sub-part 3: “Abstract Test Suite (ATS) specification“. National transposition dates Date of adoption of this EN Date of latest announcement of this EN (doa): Date of latest publication of new National
6、Standard or endorsement of this EN (dop/e): Date of withdrawal of any conflicting National Standard (dow): 19 January 2001 30 April 2001 31 October 2001 31 October 2001 ETSI 5 ETSI EN 301 811-1-2 V1.l.l (2001-01) 1 Scope The present document contains the Test Suite Structure (TSS) and Test Purposes
7、(TP) to test the BRAN HIPERLAN Type 2; Conformance testing for the packet based convergence layer; Part 1: Common part. The objective of the present document is to provide a basis for conformance tests for HIPERLAN Type 2 equipment giving a high probability of air interface inter-operability between
8、 different manufacturers HIPERLAN Type 2 equipmen t. The IS0 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 document
9、s contain provisions which, through reference in this text, constitute provisions of the present documen t. References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non
10、-specific reference, the latest version applies. A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same number. u1 ETSI TS 101 493-1 (Vl.l.1): “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Packet based Convergence Layer; Part 1:
11、 Common Part“. ETSI ETS 300 406 (1995): “Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. ISO/IEC 9646-1 (1991): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework -
12、 Part 1: General concepts“. (See also ITU-T Recommendation X.290 (1991). ISO/IEC 9646-2 (1991): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“. (See also ITU-T Recommendation X.291 (1991). ISO/IEC 96
13、46-6 (1991): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification“. ISO/IEC 9646-7 (1991): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7:
14、Implementation Conformance Statements“. 121 131 141 151 161 3 Definitions and abbreviations 3.1 Def i n it ions For the purposes of the present document, the following terms and definitions apply: a) The terms defined in ISO/IEC 9646-7 6; and b) The definitions in TS 101 493-1 i. ETSI 6 Test Suite E
15、TSI EN 301 811-1-2 V1.l.l (2001-01) Protocol group I Protocol subgroup I Test group 3.2 PCL-AP/ PCL-MT I Common procedures Abbreviations Sender 1x1 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 and the abbreviations define
16、d in TS 101 493-1 i apply. In particular, the following abbreviations apply: BI BO BV CA IUT PDU PICS TSS TP AP BCH CL cc CPCS DCCH DLC DUC DCC EC MAC MT PBCL PDU sscs Invalid Behaviour Inopportune Behaviour Valid Behaviour Capability tests Implementation Under Test Protocol Data Unit Protocol Imple
17、mentation Conformance Statement Test Suite Structure Test Purposes Access Point Broadcast CHannel Convergence Layer Central Controller Common Part Convergence Layer Dedicated Control CHannel Data Link Control DLC User Connection DLC user Connection Control Error Control Medium Access Control Mobile
18、Terminal Packet Based Convergence Layer Protocol Data Unit Service Specific Convergence Sublayer 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. Figure 1 : TSS for Hiperlan 2 Common part PBCL
19、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 protocol group representing the prot
20、ocol services. The second level separates the protocol services in functional modules. The last level in each branch contains one or more of the standard IS0 subgroups CA, BV, BI and BO. 4.2.1 Protocol groups The protocol groups identify the common part procedures as defined in TS 101 493-1 i. ETSI
21、7 TP Id according to the TP naming conventions TP Id Reference Condition Stimulus Expected behaviour ETSI EN 301 811-1-2 V1.l.l (2001-01) Reference. Initial condition. Stimulus. Expected behaviour. The TP Id is a unique identifier it shall be specified according to the TP naming conventions defined
22、in the Subclause below. The reference should contain the references of the subject to be validated by the actual TP (specification reference, clause and paragraph). The condition defines in which initial state the IUT has to be to apply the actual TP. The stimulus defines the test event to which the
23、 TP is related. Definition of the events that are expected from the IUT to conform to the base soecification. 4.2.1 .I 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 functiona
24、l module identifies the procedures at the receiver side. 4.2.2 Main test groups The main test groups are the capability group, the valid behaviour group, the invalid behaviour group and the inopportune behaviour group. 4.2.2.1 Capability (CA) tests This test sub group shall provide limited testing o
25、f the major IUT capabilities aiming to ensure 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 the present document, after receipt or exchange of valid Protocol Dat
26、a Units (PDUs). Valid PDUs means that the exchange 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 the present document, after receipt of a syntactically invali
27、d PDU. 4.2.2.4 Inopportune Behaviour (BO) tests This test sub group shall verify that the IUT reacts in conformity with the present document, after receipt of a syntactically correct PDU not expected in the actual message exchange. 5 Test Purposes (TP) 5.1 I nt roduction 5.1 .I TP definition convent
28、ions The TPs are defined following particular rules as shown in Table 1. Table 1 : TP definition rules ETSI 8 ETSI EN 301 811-1-2 V1.l.l (2001-01) 5.1.2 TP naming conventions The identifier of the TP is built according to Table 2. Table 2: TP naming convention Example: TP/MT/CPP/RS/BV-OlO is the ten
29、th 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 i. 5.2 Test purposes for AP 5.2.1 Procedures at the sender T PIA PIC P PISSICA-O00 T PIA
30、PIC P PISSICA-00 1 T PIA PIC P PIS SICA- O O2 Reference: TS 1 O1 493-1 - 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
31、 send. Reference: TS 1 O1 493-1 - 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. Reference: TS 1 O1 493-1 - 5.3.
32、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 9 5.2.2 Procedures at the receiver ETSI EN 301 811-1-2 V1.l.l (2001-01
33、) T PIA PIC P PI RSICA-000 T PIA PIC P PI RSICA-O0 1 T PIA PIC P PI RSIC A- O 02 T PIA PIC P PI RSIC A- O 03 T PIA PIC P PI RSIC A- O 04 T PIA PIC P PI RSIC A- O 05 T PIA PIC P PI RSICA-006 Reference: TS 1 O1 493-1 - 5.3.4.3 Initial condition: DUC-established. IUT is the receiver. A loop back mechan
34、ism 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. Reference: TS 1 O1 493-1 - 5.3.4.3 Initial condition: DUC-established. IUT is the receiver. A loop back mechanism is imple
35、mented 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. Reference: TS 1 O1 493-1 - 5.3.4.3 Initial condition: DUC-established. IUT is the receiver. A loop back mechanism is implemented on top
36、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. Reference: TS 1 O1 493-1 - 5.3.4.3 Initial condition: DUC-established. IUT is the receiver. A loop back mechanism is
37、 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. Reference: TS 1 O1 493-1 - 5.3.4.3 Initial condition: DUC-established. IUT is the receiver. A loop back mechanism is implemented on top
38、of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly a continuous stream of received CPCS PDU. Reference: TS 1 O1 493-1 - 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 a
39、t the IUT. Check, that: the IUT manages correctly a discontinuous flow of received CPCS PDU. Reference: TS 1 O1 493-1 - 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 rea
40、ssembles correctly a large amount of received SAR-UNITDATA. 5.3 Test purposes for MT 5.3.1 Procedures at the sender TPIMTIC P PISSICA-000 TPIMTICP PISSICA-O0 1 TPIMTIC P PISSICA-002 Reference: TS 1 O1 493-1 - 5.3.4.2 Initial condition: DUC-established. IUT is the sender. A loop back mechanism is imp
41、lemented on top of either CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly a continuousstream of CPCS PDU to send. Reference: TS 1 O1 493-1 - 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
42、SSCS layer at the IUT. Check, that: the IUT manages correctly a discontinuous flow of CPCS PDU to send. Reference: TS 1 O1 493-1 - 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: th
43、e IUT segments correctly a large CPCS PDU (near the value). ETSI 10 5.3.2 Procedures at the receiver TP/MT/CPP/RS/CA-004 TP/MT/CPP/RS/CA-005 TP/MT/CPP/RS/CA-O06 TP/MT/CP P/RS/CA-000 higher layer. Reference: TS 1 O1 493-1 - 5.3.4.3 Initial condition: DUC-established. IUT is the receiver. A loop back
44、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. Reference: TS 1 O1 493-1 - 5.3.4.3 Initial condition: DUC-established. IUT is the receiver. A loop back mechanism is implemented on top of e
45、ither CPCS layer or SSCS layer at the IUT. Check, that: the IUT manages correctly a discontinuous flow of received CPCS PDU. Reference: TS 1 O1 493-1 - 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 t
46、he IUT. Check, that: the IUT reassembles correctly a large amount of received SAR-UNITDATA. ETSI EN 301 811-1-2 V1.l.l (2001-01) Reference: TS 1 O1 493-1 - 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
47、at the IUT. Check. that: the IUT discards a received CPCS PDU. if the calculated PAD field is I longerthan 47 octets. I Reference: TS 1 O1 493-1 - 5.3.4.3 TP/MT/CPP/RS/CA-001 TP/MT/CP P/RS/CA-002 Initial condition: DUC-established. IUT is the receiver. A loop back mechanism is implemented on top of
48、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. Reference: TS 1 O1 493-1 - 5.3.4.3 Initial condition: DUC-established. IUT is the receiver. A loop back mechanism is implemented on top of either CPCS la
49、yer or SSCS layer at the IUT. Check, that: the IUT discards a received CPCS PDU, if the value of the extracted I Length field is higher than the value of the parameter. I Reference: TS 1 O1 493-1 - 5.3.4.3 TP/MT/CPP/RS/CA-003 ETSI 11 ETSI EN 301 811-1-2 V1.l.l (2001-01) vl.l.l vl.l.l History September 2000 Publication as TS 101 811-1-1 September 2000 One-step Approval Procedure OAP 20010119: 2000-09-20 to 2001-01-19 I Document history I V1.l.l I January 2001 I Publication ETSI
