1、 ETSI TS 101 811-3-2 V1.3.1 (2004-08)Technical Specification Broadband Radio Access Networks (BRAN);HIPERLAN Type 2;Conformance testing for the packet based convergence layer;Part 3: IEEE 1394 Service Specific Convergence Sublayer (SSCS);Sub-part 2: Test Suite Structure and Test Purposes (TSS Essent
2、ial, 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, no investigation, including IPR searches, has b
3、een carried out by ETSI. No 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 Proje
4、ct Broadband Radio Access Networks (BRAN). The present document is part 3, sub-part 2 of a multi-part deliverable. Full details of the entire series can be found in part 1, sub-part 1 (see bibliography). ETSI ETSI TS 101 811-3-2 V1.3.1 (2004-08) 6 1 Scope The present document contains the Test Suite
5、 Structure (TSS) and Test Purposes (TP) to test the BRAN HIPERLAN type 2; Packet based Convergence Layer; Part 3: IEEE 1394 Service Specific Convergence Sublayer (SSCS). The objective of the present document is to provide a basis for conformance tests for BRAN HIPERLAN type 2 equipment giving a high
6、 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 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 fo
7、r the test methodology. 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 a spec
8、ific 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-3 (V1.3.1): “Broadband Radio Ac
9、cess Networks (BRAN); HIPERLAN Type 2; Packet based Convergence Layer; Part 3: IEEE 1394 Service Specific Convergence Sublayer (SSCS)“. 2 ETSI ETS 300 406: “Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; Standardization methodology“. 3 ISO/IEC 9
10、646-1 (1994): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts“. (See also ITU-T Recommendation X.290 (1995). 4 ISO/IEC 9646-2 (1994): “Information technology - Open Systems Interconnection - Conformance testing methodo
11、logy and framework - Part 2: Abstract test suite specification“. (See also ITU-T Recommendation X.291 (1995). 5 ISO/IEC 9646-6 (1994): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification“. 6 ISO/IEC 9646
12、-7 (1995): “Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation 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
13、-7 6 and TS 101 493-3 1 apply. ETSI ETSI TS 101 811-3-2 V1.3.1 (2004-08) 7 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-3 1 and the following apply: AP Access Point BI Invalid Behaviour BO In
14、opportune Behaviour BV Valid Behaviour CA Capability tests CC Central Controller CL Convergence Layer DLC Data Link Control DM Direct Mode HARP HIPERLAN/2 Address Resolution Protocol IUT Implementation Under Test LCH Long CHannel MAC Medium Access Control MT Mobile Terminal PBCL Packet Based Converg
15、ence Layer PDU Protocol Data Unit PICS Protocol Implementation Conformance Statement RLC Radio Link Control TP Test Purposes TSS Test Suite Structure 4 Test suite structure 4.1 Structure Figure 1 shows the IEEE 1394 Service Specific PBCL Test Suite Structure (TSS) including its subgroups defined for
16、 the conformance testing. Test Suite Protocol group Protocol subgroup Test group CA BV BI BO IEE-AP/ IEE-MT/ IEE-HS User plane procedures Clock synchronization x Asynchronous transaction x Isochronous Stream x Asynchronous Stream xControl plane procedures Association - Initialization x Bus reset x C
17、lock information connection x CL responsibilityhandover x HL2 Address Resolution service x Asynchronous transaction x Isochronous stream x Asynchronous stream x Figure 1: TSS for Hiperlan 2 IEEE 1394 Service Specific PBCL The test suite is structured as a tree with a first level defined as IEE-AP, I
18、EE-MT or IEE-HS representing the protocol group “IEEE 1394 Service Specific PBCL for AP“, “IEEE 1394 Service Specific PBCL for MT“ and “IEEE 1394 Service Specific PBCL for HL2 Bus system“. ETSI ETSI TS 101 811-3-2 V1.3.1 (2004-08) 8 4.2 Test groups The test groups are organized in three levels. The
19、first level creates one protocol 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 group identifies t
20、he User plane procedures and the Control plane procedures as defined in TS 101 493-3 1. 4.2.1.1 User plane procedures The User plane procedures group is divided in four functional modules. The first functional module distinguishes the Clock synchronization service. The second functional module disti
21、nguishes the Asynchronous transaction data transport service. The third functional module distinguishes the isochronous stream data transport service. The last functional module distinguishes the Asynchronous stream data transport service. 4.2.1.2 Control plane procedures The Control plane procedure
22、s group is divided in eight functional modules. The first functional module distinguishes the Association - Initialization service. The second functional module distinguishes the Bus reset service. The third functional module distinguishes the Clock information connection control service. The fourth
23、 functional module identifies the CL responsibility handover service. The fifth functional module distinguishes the HL2 Address Resolution service (HARP). The sixth functional module distinguishes Asynchronous transaction connection control service. The seventh functional module distinguishes the is
24、ochronous stream connection control service. The last functional module distinguishes the Asynchronous streams connection control service. 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.
25、 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 PICS. 4.2.2.2 Valid Behaviour (BV) tests This test sub group shall verify that the IUT reacts in con
26、formity 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 as valid. 4.2.2.3 Invalid Behaviour (BI) tests This test sub group shall verify that the IUT react
27、s 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 the present document, after receipt of a syntactically correct PDU not expected in the actual mess
28、age exchange. ETSI ETSI TS 101 811-3-2 V1.3.1 (2004-08) 9 5 Test Purposes (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.
29、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 subject to be validated by the actual TP (specification reference, clause and paragr
30、aph). 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 the events that are expected from the IUT to conform to the base specification. 5.1.2 TP na
31、ming 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 HS HL2 Bus system = Protocol group UPP User plane procedures CPP Control plane procedures = Functional module CS Clock synchronizatio
32、n AT Asynchronous transaction IS Isochronous Stream AS Asynchronous StreamAI Association - Initialization BR Bus reset CI Clock information connection RH CL responsibility handover HA HL2 Address Resolution service x = Type of testing CA Capability Tests BV Valid Behaviour Tests BI Invalid Behaviour
33、 Tests BO Inopportune Behaviour Tests = Sequential number (000-999) Test Purpose Number EXAMPLE: TP/MT/CPP/RH/BV-010 is the tenth purpose for the valid behaviour testing the Control plane CL responsibility handover procedures of the IEEE 1394 Service Specific layer implemented at MT side. 5.1.3 Sour
34、ces of TP definitions All TPs are specified according to TS 101 493-3 1. ETSI ETSI TS 101 811-3-2 V1.3.1 (2004-08) 105.2 Test purposes for AP 5.2.1 Association - Initialization TP/AP/CPP/AI/CA-000 Reference: TS 101 493-3 1, clause 6.3.1 Initial condition: IUT is the AP/CC. LT is acting as WT. Only f
35、or IUT that supports 1394 SSCS. Check, that: after receiving an RLC_INFO message containing the EUI_64 information element, the CC sends an RLC_INFO_ACK message. TP/AP/CPP/AI/CA-001 Reference: TS 101 493-3 1, clause 6.3.2 Initial condition: IUT is the AP/CC. LT is acting as WT. Only for IUT that sup
36、ports 1394 SSCS. Check, that: after receiving an RLC_GROUP_JOIN message for the main multicast group of the 1394 broadcast channel, the CC sends an RLC_GROUP_JOIN_ACK message. TP/AP/CPP/AI/CA-002 Reference: TS 101 493-3 1, clause 6.3.1 Initial condition: IUT is the AP/CC. LT is acting as WT. Only fo
37、r IUT that supports 1394 SSCS. Check, that: when the CC sends an RLC_INFO_ACK message in answer to an RLC_INFO message containing the EUI_64 information element, the field of the RLC_INFO_ACK message contains the received EUI_64 information element. TP/AP/CPP/AI/CA-003 Reference: TS 101 493-3 1, cla
38、use 6.3.2 Initial condition: IUT is the AP/CC. LT is acting as WT. Only for IUT that supports 1394 SSCS. Check, that: when the CC sends an RLC_GROUP_JOIN_ACK message in answer to an RLC_GROUP_JOIN message for the main multicast group of the 1394 broadcast channel, the field of the RLC_GROUP_JOIN_ACK
39、 message contains the received CHANNEL information element. ETSI ETSI TS 101 811-3-2 V1.3.1 (2004-08) 115.2.2 Bus reset service TP/AP/CPP/BR/CA-000 Reference: TS 101 493-3 1, clause 6.4.1 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. WT1 has joined the clock multicast group. W
40、T2 joins the clock multicast group. Only for IUT that supports 1394 SSCS. Check, that: the CC initiates a bus-reset procedure when a wireless node joins the HL2 Bus. TP/AP/CPP/BR/CA-001 Reference: TS 101 493-3 1, clause 6.4.1 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. WT1 h
41、as joined the clock multicast group. WT2 leaves the clock multicast group and disassociates from CC. Only for IUT that supports 1394 SSCS. Check, that: the CC initiates a bus-reset procedure when a wireless node leaves the HL2 Bus. TP/AP/CPP/BR/CA-002 Reference: TS 101 493-3 1, clause 6.4.2.1 Initia
42、l condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. WT1 and WT2 have joined the clock multicast group. WT1 has sent a BUS_RESET. Only for IUT that supports 1394 SSCS. Check, that: when the CC receives an RLC_INFO message containing a BUS_RESET information element, it acknowledges the WT b
43、y sending an RLC_INFO_ACK message. TP/AP/CPP/BR/CA-003 Reference: TS 101 493-3 1, clause 6.4.2.3 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. WT1 and WT2 have joined the clock multicast group. Only for IUT that supports 1394 SSCS. Check, that: the CC starts the BUS_RESET proc
44、edure by sending an RLC_INFO message containing a BUS_SUSPEND information element in the field to all associated WTs TP/AP/CPP/BR/CA-004 Reference: TS 101 493-3 1, clause 6.4.2.3 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. WT1 and WT2 have joined the clock multicast group. W
45、T1 and WT2 have sent a BUS_SUSPEND response. Only for IUT that supports 1394 SSCS. Check, that: after having received an RLC_INFO_ACK message containing the BUS_SUSPEND information element from all associated WTs, the CC sends an RLC_INFO message containing a BUS_RESUME information element in the fi
46、eld to all associated WTs TP/AP/CPP/BR/CA-005 Reference: TS 101 493-3 1, clause 6.4.2.3 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. WT1 and WT2 have joined the clock multicast group. WT1 and WT2 have not sent the BUS_RESUME response within the T_reset timer. Only for IUT tha
47、t supports 1394 SSCS. Check, that: if the CC cannot complete the BUS_RESET procedure within the T_reset timer, it starts another BUS_RESET procedure. TP/AP/CPP/BR/CA-006 Reference: TS 101 493-3 1, clause 6.4.2.3 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. WT1 and WT2 have jo
48、ined the clock multicast group. WT1 has sent the BUS_SUSPEND response and WT2 has not. Only for IUT that supports 1394 SSCS. Check, that: if the CC did not receive the RLC_INFO_ACK message containing the BUS_SUSPEND information element response from all associated WTs, it retransmits the RLC_INFO me
49、ssage containing the BUS_SUSPEND information element in the field to only those WTs that did not acknowledge it. TP/AP/CPP/BR/CA-007 Reference: TS 101 493-3 1, clause 6.4.2.3 Initial condition: IUT is the AP/CC. LT is acting as WT1 and as WT2. WT1 and WT2 have joined the clock multicast group. WT1 has sent the BUS_RESUME response and WT2 has not. Only for IUT that supports 1394 SSCS. Check, that: if the CC did not receive the RLC_INFO_ACK message containing the BUS_RESUME information element response from all assoc
