ETSI TS 101 823-4-2-2004 Broadband Radio Access Networks (BRAN) HIPERLAN Type 2 Conformance testing for the Data Link Control (DLC) layer Part 4 Extension for Home Environment Sub-.pdf

《ETSI TS 101 823-4-2-2004 Broadband Radio Access Networks (BRAN) HIPERLAN Type 2 Conformance testing for the Data Link Control (DLC) layer Part 4 Extension for Home Environment Sub-.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 101 823-4-2-2004 Broadband Radio Access Networks (BRAN) HIPERLAN Type 2 Conformance testing for the Data Link Control (DLC) layer Part 4 Extension for Home Environment Sub-.pdf（19页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 101 823-4-2 V1.3.1 (2004-08)Technical Specification Broadband Radio Access Networks (BRAN);HIPERLAN Type 2;Conformance testing for the Data Link Control (DLC) layer;Part 4: Extension for Home Environment;Sub-part 2: Test Suite Structure andTest Purposes (TSS Essential, or potentially Essent

2、ial, 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, no investigation, including IPR searches, has been carried out by ETSI. N

3、o guarantee can be 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

4、Networks (BRAN). The present document is part 4, sub-part 2 of a multi-part deliverable. Full details of the entire series can be found in part 1, sub-part 1 4. ETSI ETSI TS 101 823-4-2 V1.3.1 (2004-08) 5 1 Scope The present document contains the Test Suite Structure (TSS) and Test Purposes (TP) to

5、test the BRAN HIPERLAN Type 2; Data Link Control (DLC) layer; Extension for Home Environment. The objective of the present 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 manufactur

6、ers BRAN HIPERLAN type 2 equipment. The ISO standard for the methodology of conformance testing (ISO/IEC 9646-1 13 and ISO/IEC 9646-2 14) as well as the ETSI rules for conformance testing (ETS 300 406 12) are used as a basis for the test methodology. 2 References The following documents contain prov

7、isions 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 apply. For a non-specific ref

8、erence, 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 Void. 2 ETSI TS 101 761-2 (V1.3.1): “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Data Link Control (DLC) la

9、yer; Part 2: Radio Link Control (RLC) Sublayer“. 3 ETSI TS 101 761-4 (V1.3.2): “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Data Link Control (DLC) layer; Part 4: Extension for Home Environment“. 4 ETSI TS 101 823-1-1: “Broadband Radio Access Networks (BRAN); HIPERLAN Type 2; Conformanc

10、e testing for the Data Link Control (DLC) layer; Part 1: Basic data transport functions; Sub-part 1: Protocol Implementation Conformance Statement (PICS) proforma“. 5 Void. 6 Void. 7 Void. 8 Void. 9 Void. 10 Void. 11 Void. 12 ETSI ETS 300 406: “Methods for Testing and Specification (MTS); Protocol a

11、nd profile conformance testing specifications; Standardization methodology“. 13 ISO/IEC 9646-1 (1994): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. (See also ITU-T Recommendation X.290 (1995). ETSI ETSI TS 101 823

12、-4-2 V1.3.1 (2004-08) 6 14 ISO/IEC 9646-2 (1994): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification“. (See also ITU-T Recommendation X.291 (1995). 15 Void. 16 Void. 17 Void. 18 ISO/IEC 9646-6 (1994): “In

13、formation technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification“. 19 ISO/IEC 9646-7 (1995): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementatio

14、n Conformance Statement“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 19, TS 101 761-2 2 and TS 101 761-4 3 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations defined in

15、ISO/IEC 9646-1 13, ISO/IEC 9646-6 18, ISO/IEC 9646-7 19, TS 101 761-2 2, TS 101 761-4 3 and the following apply: AP Access Point BI Invalid Behaviour BO Inopportune Behaviour BV Valid Behaviour CA Capability tests CC Central Controller CL Convergence Layer DLC Data Link Control DM Direct Mode DUC DL

16、C User Connection FEC Forward Error Correction HE Home Extention IUT Implementation Under Test LT Lower Tester MAC Medium Access Control MT Mobile Terminal PDU Protocol Data Unit PICS Protocol Implementation Conformance Statement RLC Radio Link Control TP Test Purposes TSS Test Suite Structure WT Wi

17、reless Terminal ETSI ETSI TS 101 823-4-2 V1.3.1 (2004-08) 7 4 Test suite structure 4.1 Structure Figure 1 shows the Data Link Control (DLC) layer; Extension for Home Environment Test Suite Structure (TSS) including its subgroups defined for the conformance testing. Test Suite Protocol group Protocol

18、 subgroup Test group CA BV BI BO TI XHE-AP/XHE-MT Link Control procedures Terminal association for multiple convergence layers x Power Control in Direct Link Phase x Link Quality Calibration for DM operation x DLC User Connection Control x Dynamic CC Selection x CC Responsibility Handover x Authenti

19、cation KeyManagement x U-plane Error Control procedures FEC error control procedures x Figure 1: TSS for HIPERLAN 2 DLC HE The test suite is structured as a tree with a first level defined as XHE-AP or XHE-MT representing the protocol group “DLC HE for AP and DLC HE for MT“. 4.2 Test groups The test

20、 groups are organized in three levels. The first level creates two protocol groups 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, BO and TI. 4.2.1

21、 Protocol groups The protocol groups identifie the DLC HE services: Link Control procedures, and U-plane Error Control procedures, as defined in TS 101 761-4 3. 4.2.1.1 Link Control procedures The Link Control procedures group is divided in seven functional modules. The first functional module ident

22、ifies the Terminal association for multiple convergence layers procedures. The second functional module identifies the Power Control in Direct Link Phase procedures. The third functional module distinguishes the Link Quality Calibration for DM operation procedures. The fourth functional module disti

23、nguishes the DLC User Connection Control procedures. The fith functional module distinguishes the Dynamic CC Selection procedures. The sixth functional module distinguishes the CC Responsibility Handover procedures. The last functional module identifies the Authentication Key Management procedures.

24、4.2.1.2 U-plane Error Control procedures The U-plane Error Control procedures group is divided in one functional module. The functional module is representing the FEC error control procedures. ETSI ETSI TS 101 823-4-2 V1.3.1 (2004-08) 8 4.2.2 Main test groups The main test groups are the capability

25、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 of the major IUT capabilities aiming to insure that the claimed capabilities are correctly supported, according to the PI

26、CS. 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 Data Units (PDUs). Valid PDUs means that the exchange of messages and the content of the exchanged messages are considered

27、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 invalid PDU. 4.2.2.4 Inopportune Behaviour (BO) tests This test sub group shall verify that the IUT reacts in conformity with

28、the present document, after receipt of a syntactically correct PDU not expected in the actual message exchange. 4.2.2.5 Timer (TI) tests This test sub group shall verify that the IUT reacts in conformity with the present document, after timer activity (start, stop, expiration, etc.). 5 Test Purposes

29、 (TP) 5.1 Introduction 5.1.1 TP definition conventions The TPs are defined following particular rules as shown in table 1. Table 1: TP definition rules TP Id according to the TP naming conventions Reference. Initial condition. Stimulus. Expected behaviour. TP Id The TP Id is a unique identifier it s

30、hall be specified according to the TP naming conventions defined in clause 5.1.2. Reference The reference should contain the references of the subject to be validated by the actual TP (specification reference, clause and paragraph). Condition The condition defines in which initial state the IUT has

31、to be to apply the actual TP. Stimulus The stimulus defines the test event to which the TP is related. Expected behaviour Definition of the events that are expected from the IUT to conform to the base specification. ETSI ETSI TS 101 823-4-2 V1.3.1 (2004-08) 9 5.1.2 TP naming conventions The identifi

32、er of the TP is built according to table 2. Table 2: TP naming convention Identifier: TP/- = side type AP Access Point MT Mobile Terminal = protocol group LCP Link Control procedures ECP U-plane Error Control procedures = functional module TC Terminal association for multiple convergence layers PC P

33、ower Control in Direct Link Phase LQ Link Quality Calibration for DM operation DC DLC User Connection Control DS Dynamic CC Selection procedures CH CC Responsibility Handover AK Authentication Key Management FP FEC error control procedures x = Type of testing CA Capability Tests BV Valid Behaviour T

34、ests BI Invalid Behaviour Tests BO Inopportune Behaviour Tests TI Timer Tests = sequential number (000-999) Test Purpose Number EXAMPLE: TP/MT/LCP/DS/BV-010 is the tenth purpose for the valid behaviour testing of the Dynamic CC Selection procedures of the Link Control procedures implemented at MT si

35、de. 5.1.3 Sources of TP definitions All TPs are specified according to TS 101 761-4 3. 5.2 Test purposes for AP/CC 5.2.1 Terminal association for multiple convergence layers TP/AP/LCP/TC/CA-000 Reference: TS 101 761-4, clause 6.2 Initial condition: Link_Agreed_or_Encryption_active_or_Authenticated O

36、nly for IUT that supports DLC home extensions. Check, that: after receiving the RLC_INFO message, the IUT replies to the LT with a RLC_INFO_ACK message for each selected CL and, after the last exchange, considers the WT (LT) as MT_Associated_to_AP. ETSI ETSI TS 101 823-4-2 V1.3.1 (2004-08) 105.2.2 L

37、ink Quality Calibration for DM operation TP/AP/LCP/LQ/CA-000 Reference: TS 101 761-4, clause 6.5.2 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. Only for IUT that supports DLC home extensions. Check, that: when the IUT wishes to start a calibration measurement phase for all WT

38、s, it sends a relevant RLC_CALIBRATION_MEASUREMENT_TRIGGER message without a Mac_Id liste. TP/AP/LCP/LQ/CA-001 Reference: TS 101 761-4, clause 6.5.2 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. Only for IUT that supports DLC home extensions. Check, that: when the IUT wishes t

39、o start a calibration measurement phase for a set of WTs, it sends a relevant RLC_CALIBRATION_MEASUREMENT_TRIGGER message containing a Mac_Id liste. TP/AP/LCP/LQ/CA-002 Reference: TS 101 761-4, clause 6.5.3 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. Only for IUT that suppor

40、ts DLC home extensions. Check, that: when the IUT wishes to start a calibration-reporting phase for all WTs, it sends a relevant RLC_CALIBRATION_REPORT_TRIGGER message without a Mac_Id liste. TP/AP/LCP/LQ/CA-003 Reference: TS 101 761-4, clause 6.5.3 Initial condition: IUT is the AP/CC. LT is acting

41、as WT1 and as WT2. Only for IUT that supports DLC home extensions. Check, that: when the IUT wishes to start a calibration-reporting phase for a set of WTs, it sends a relevant RLC_CALIBRATION_REPORT_TRIGGER message containing a Mac_Id liste. TP/AP/LCP/LQ/CA-004 Reference: TS 101 761-4, clause 6.5.4

42、 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. Only for IUT that supports DLC home extensions. Check, that: when the IUT wishes to distribute the map of connectivity, it sends a relevant RLC_CALIBRATION_LINKQUALITYMAP message. TP/AP/LCP/LQ/CA-005 Reference: TS 101 761-4, claus

43、e 6.5.4 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. Only for IUT that supports DLC home extensions. Check, that: after receiving a RLC_CALIBRATION_LINKQUALITYMAP_REQUEST message from the WT1, the IUT replies to the LT with a relevant RLC_CALIBRATION_LINKQUALITYMAP message. E

44、TSI ETSI TS 101 823-4-2 V1.3.1 (2004-08) 115.2.3 DLC User Connection Control TP/AP/LCP/DC/CA-000 Reference: TS 101 761-4, clause 6.6 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. WT1 and WT2 have joined the same multicast group. WT1 has sent a RLC_DM_MC_SETUP message to become

45、 the sender of the multicast group. Only for IUT that supports DLC home extensions. Check, that: after receiving the RLC_DM_MC_SETUP message from WT1, the IUT replies to the LT with a RLC_DM_MC_CONNECT message. TP/AP/LCP/DC/CA-001 Reference: TS 101 761-4, clause 6.6 Initial condition: IUT is the AP/

46、CC. LT is acting as WT1 and as WT2. WT1 and WT2 have joined the same multicast group. IUT has sent a RLC_DM_MC_CONNECT message to WT1 who needs to become the sender of the multicast group. Only for IUT that supports DLC home extensions. Check, that: after receiving the RLC_DM_MC_CONNECT_ACK message

47、from the WT1, the IUT sends a relevant RLC_DM_MC_SETUP message to the WT2. TP/AP/LCP/DC/CA-002 Reference: TS 101 761-4, clause 6.6 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. WT1 and WT2 have joined the same multicast group. IUT has sent a RLC_DM_MC_SETUP message to the WT2

48、to forward the direct link multicast setup to the receiver. Only for IUT that supports DLC home extensions. Check, that: after receiving the RLC_DM_MC_CONNECT message from the WT2, the IUT replies to the LT with a RLC_DM_MC_CONNECT_ACK message and sends a relevant RLC_DM_MC_CONNECT_COMPLETE message

49、to WT1. TP/AP/LCP/DC/CA-003 Reference: TS 101 761-4, clause 6.6 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. WT1 and WT2 have joined the same multicast group. IUT has sent a RLC_DM_MC_CONNECT_COMPLETE message to the WT1. Only for IUT that supports DLC home extensions. Check, that: after completion of the DM multicast setup procedure, the U-plane is established between the WT1 as sender and the WT2 as receiver. TP/AP/LCP/DC/CA-004 Reference: TS 101 761-4, clause 6.6 Initial