SIST ETS 300 836-4 E1:2006
(Main)Broadband Radio Access Networks (BRAN); HIgh PErformance Radio Local Area Network (HIPERLAN) Type 1; Conformance testing specification; Part 4: Abstract Test Suite (ATS) specification
Broadband Radio Access Networks (BRAN); HIgh PErformance Radio Local Area Network (HIPERLAN) Type 1; Conformance testing specification; Part 4: Abstract Test Suite (ATS) specification
This European Telecommunication Standard (ETS) specifies the Abstract Test Suite (ATS) for the Medium Access Control (MAC) and Channel Access Control (CAC) protocol parts of the HIgh PErformance Radio Local Area Network (HIPERLAN) Type 1 functional specification as specified in ETS 300 652 [1]. ETS 300 836-3 [8] specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this ATS specification. In this ETS, the term "HIPERLAN" is used to refer to HIPERLAN, Type 1.
Širokopasovna radijska dostopovna omrežja (BRAN) – Zelo zmogljivo radijsko lokalno omrežje (HIPERLAN), tip 1 – Specifikacija za preskušanje skladnosti – 4. del: Abstraktni preskušalni niz (ATS) – Specifikacija
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
01-februar-2006
Širokopasovna radijska dostopovna omrežja (BRAN) – Zelo zmogljivo radijsko
lokalno omrežje (HIPERLAN), tip 1 – Specifikacija za preskušanje skladnosti – 4.
del: Abstraktni preskušalni niz (ATS) – Specifikacija
Broadband Radio Access Networks (BRAN); HIgh PErformance Radio Local Area
Network (HIPERLAN) Type 1; Conformance testing specification; Part 4: Abstract Test
Suite (ATS) specification
Ta slovenski standard je istoveten z: ETS 300 836-4 Edition 1
ICS:
33.060.01 Radijske komunikacije na Radiocommunications in
splošno general
35.110 Omreževanje Networking
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
EUROPEAN ETS 300 836-4
TELECOMMUNICATION May 1998
STANDARD
Source: BRAN Reference: DE/BRAN-10-02C
ICS: 33.020
Key words: HIPERLAN, LAN, radio, testing
Broadband Radio Access Networks (BRAN);
HIgh PErformance Radio Local Area Network (HIPERLAN)
Type 1;
Conformance testing specification;
Part 4: Abstract Test Suite (ATS) specification
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Internet: secretariat@etsi.fr - http://www.etsi.fr - http://www.etsi.org
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1998. All rights reserved.
Page 2
ETS 300 836-4: May 1998
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.
Page 3
ETS 300 836-4: May 1998
Contents
Foreword .7
1 Scope .9
2 Normative references.9
3 Definitions and abbreviations .10
3.1 Definitions .10
3.2 Abbreviations .10
4 Abstract Test Method (ATM).11
4.1 ATM for MAC protocol .11
4.1.1 Co-ordinated test method.11
4.1.2 Remote test method.11
4.1.3 Choice of MAC ATM.12
4.2 ATM for CAC protocol.12
5 Requirements on underlying layers for testing .13
5.1 MAC testing .13
5.1.1 CAC service for MAC testing.13
5.1.2 CAC protocol for MAC testing .13
5.1.3 PHY protocol for MAC testing .15
5.2 CAC testing.15
5.2.1 PHY service interface for CAC testing .15
5.2.1.1 PHY service primitives.15
5.2.1.1.1 PH-UNITDATA-request (PH-UD-RQ).15
5.2.1.1.2 PH-UNITDATA-confirm (PH-UD-CO).15
5.2.1.1.3 PH-UNITDATA-indication (PH-UD-IN).15
5.2.1.1.4 PH-START-request (PH-ST-RQ).16
5.2.1.1.5 PH-START-indication (PH-ST-IN) .16
5.2.1.1.6 PH-END-request (PH-EN-RQ).16
5.2.1.1.7 PH-END-indication (PH-EN-IN) .16
5.2.1.1.8 PH-RESET (PH-REST) .16
5.2.1.1.9 PH-CHANNEL (PH-CHAN).16
5.2.1.2 Sequence of primitives .17
6 Untestable test purposes.19
6.1 MAC protocol .19
6.2 CAC protocol.20
7 ATS conventions .20
7.1 MAC ATS.20
7.1.1 Naming conventions.20
7.1.1.1 General.20
7.1.1.2 Timers.20
7.1.1.3 ASPs.20
7.1.1.3.1 Aliases for ASPs .21
7.1.1.4 PDUs .21
7.1.1.5 Constraints.21
7.1.1.5.1 ASPs.22
7.1.1.5.2 PDUs.22
7.1.2 Test steps and defaults .22
7.1.3 Use of ASN.1.22
7.1.3.1 ASN.1 types.23
7.1.3.2 ASN.1 encoding.23
7.2 CAC ATS .23
7.2.1 Description (in test suite overview).23
Page 4
ETS 300 836-4: May 1998
7.2.2 Declarations. 23
7.2.2.1 Type definitions. 23
7.2.2.2 Test suite operations. 23
7.2.2.3 Test suite parameters . 23
7.2.2.4 Selection expressions . 23
7.2.2.5 Test suite constants. 23
7.2.2.6 Test suite variables . 24
7.2.2.7 Test case variables . 24
7.2.2.8 PCOs. 24
7.2.2.9 Timers . 24
7.2.2.10 ASPs . 24
7.2.2.11 PDUs. 24
7.2.2.12 Aliases. 24
7.2.3 Constraints. 24
7.2.3.1 ASPs containing PDUs, PDUs and fields of PDUs. 24
7.2.3.2 Other ASP constraints . 25
7.2.4 Dynamic part. 25
7.2.4.1 Labels. 25
7.2.4.2 Test steps . 26
8 ATS to TP map . 26
8.1 Combined TPs . 26
9 Conformance . 26
9.1 PCTR conformance. 26
9.2 PIXIT conformance . 26
9.3 ATS conformance . 27
Annex A (normative): Test Management Protocol (TMP) specification. 28
A.1 TMP . 28
A.1.1 Receipt of LR-TMPDU . 28
A.1.2 Receipt of DT-TMPDU . 28
A.1.3 Receipt of CL-TMPDU . 28
A.1.4 Generation of LC-TMPDU. 29
A.1.5 Generation of DT-TMPDU. 29
A.1.6 TMPDU transmission . 29
A.2 Test Management PDUs (TMPDUs) .30
A.2.1 TMPDUs received by the UT. 30
A.2.1.1 LR-TMPDU . 30
A.2.1.2 DT-TMPDU. 30
A.2.1.3 CL-TMPDU . 30
A.2.2 TMPDUs transmitted by the UT . 31
A.2.2.1 LC-TMPDU . 31
A.2.2.2 DT-TMPDU. 31
Annex B (normative): MAC Protocol Conformance Test Report (PCTR) proforma . 32
B.1 Identification summary. 32
B.1.1 Protocol conformance test report. 32
B.1.2 IUT identification. 32
B.1.3 Testing environment. 32
B.1.4 Limits and reservations . 33
B.1.5 Comments. 33
B.2 IUT conformance status . 33
B.3 Static conformance summary. 33
B.4 Dynamic conformance summary. 33
B.5 Static conformance review report . 34
Page 5
ETS 300 836-4: May 1998
B.6 Test campaign report .34
B.7 Observations .38
Annex C (normative): Partial PIXIT proforma for MAC.39
C.1 Identification summary .39
C.2 Abstract test suite summary.39
C.3 Test laboratory .40
C.4 Client (of the Test Laboratory).40
C.5 SUT .41
C.6 Protocol information .41
C.6.1 Protocol identification.41
C.6.2 Addresses.42
C.6.3 Parameter values.43
C.6.4 Sending of PDUs by IUT.44
Annex D (normative): CAC PCTR proforma.45
D.1 Identification summary .45
D.1.1 Protocol conformance test report.45
D.1.2 IUT identification .45
D.1.3 Testing environment .45
D.1.4 Limits and reservations.46
D.1.5 Comments .46
D.2 IUT conformance status.46
D.3 Static conformance summary.46
D.4 Dynamic conformance summary.46
D.5 Static conformance review report.47
D.6 Test campaign report .47
D.7 Observations .50
Annex E (normative): Partial PIXIT proforma for CAC.51
E.1 Identification summary .51
E.2 Abstract test suite summary.51
E.3 Test laboratory .52
E.4 Client (of the Test Laboratory).52
E.5 SUT .53
E.6 Protocol information .53
E.6.1 Protocol identification.53
E.6.2 Addresses.54
E.6.3 Parameter values.54
E.6.4 Sending of PDUs by IUT.54
Annex F (normative): Graphical Representation (GR) format of ATS .55
Page 6
ETS 300 836-4: May 1998
F.1 GR for MAC ATS . 55
F.2 GR for CAC ATS . 55
Annex G (normative): Machine Processable (MP) format of ATS . 56
G.1 MP for MAC ATS . 56
G.2 MP for CAC ATS. 56
History. 57
Page 7
ETS 300 836-4: May 1998
Foreword
This European Telecommunication Standard (ETS) has been produced by the ETSI Project Broadband
Radio Access Networks (BRAN) of the European Telecommunications Standards Institute (ETSI).
This ETS consists of 4 parts as follows:
Part 1: "Radio type approval and Radio Frequency (RF) conformance test specification";
Part 2: "Protocol Implementation Conformance Statement (PICS) proforma specification";
Part 3: "Test Suite Structure and Test Purposes (TSS&TP) specification";
Part 4: "Abstract Test Suite (ATS) specification".
Transposition dates
Date of adoption of this ETS: 1 May 1998
Date of latest announcement of this ETS (doa): 31 August 1998
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 28 February 1999
Date of withdrawal of any conflicting National Standard (dow): 28 February 1999
Page 8
ETS 300 836-4: May 1998
Blank page
Page 9
ETS 300 836-4: May 1998
1 Scope
This European Telecommunication Standard (ETS) specifies the Abstract Test Suite (ATS) for the
Medium Access Control (MAC) and Channel Access Control (CAC) protocol parts of the HIgh
PErformance Radio Local Area Network (HIPERLAN) Type 1 functional specification as specified in
ETS 300 652 [1].
ETS 300 836-3 [8] specifies the Test Suite Structure and Test Purposes (TSS&TP) related to this ATS
specification.
In this ETS, the term "HIPERLAN" is used to refer to HIPERLAN, Type 1.
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ETS 300 652 (1996) + prA1 (1996): "Radio Equipment and Systems (RES);
HIgh PErformance Radio Local Area Network (HIPERLAN); Type 1; Functional
specification".
[2] ISO/IEC 9646-1 (1994): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 1:
General concepts".
[3] ISO/IEC 9646-2 (1994): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 2:
Abstract Test Suite specification".
[4] ISO/IEC 9646-3 (1992): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 3:
The Tree and Tabular Combined Notation (TTCN)" (including Amendment 1 and
Amendment 2).
[5] ISO/IEC 9646-4 (1994): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 4:
Test realization".
[6] ISO/IEC 9646-5 (1994): "Information technology - Open Systems
Interconnection - Conformance testing methodology and framework - Part 5:
Requirements on test laboratories and clients for the conformance assessment
process".
[7] ETS 300 836-2: "Radio Equipment and Systems (RES); HIgh PErformance
Radio Local Area Network (HIPERLAN) Type 1; Conformance testing
specification; Part 2: Protocol Implementation Conformance Statement (PICS)
proforma specification".
[8] ETS 300 836-3: "Radio Equipment and Systems (RES); HIgh PErformance
Radio Local Area Network (HIPERLAN) Type 1; Conformance testing
specification; Part 3: Test Suite Structure and Test Purposes (TSS&TP)
specification".
Page 10
ETS 300 836-4: May 1998
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply, in addition to those given in ETS 300 652 [1]:
Abstract Test Suite (ATS): See ISO/IEC 9646-1 [2].
Implementation Under Test (IUT): See ISO/IEC 9646-1 [2].
Lower Tester (LT): See ISO/IEC 9646-1 [2].
Protocol Implementation Conformance Statement (PICS) proforma: See ISO/IEC 9646-1 [2].
Protocol Implementation eXtra Information for Testing (PIXIT) proforma: See ISO/IEC 9646-1 [2].
Point of Control and Observation (PCO): See ISO/IEC 9646-1 [2].
Protocol Implementation Conformance Statement (PICS): See ISO/IEC 9646-1 [2].
Protocol Implementation Extra Information For Testing (PIXIT): See ISO/IEC 9646-1 [2].
System Under Test (SUT): See ISO/IEC 9646-1 [2].
Upper Tester (UT): See ISO/IEC 9646-1 [2].
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply, in addition to those given in
ETS 300 652 [1]:
ASP Abstract Service Primitive
ATM Abstract Test Method
ATS Abstract Test Suite
CAC Channel Access Control
ExTS Executable Test Suite
HCPDU HIPERLAN CAC Protocol Data Unit
HEU HIPERLAN Enhancement Unit
HIPERLAN HIgh PErformance Radio Local Area Network
IUT Implementation Under Test
LT Lower Tester
MAC Medium Access Control
MOT Means of Testing
PCO Point of Control and Observation
PDU Protocol Data Unit
PICS Protocol Implementation Conformance Statement
PIXIT Protocol Implementation eXtra Information for Testing
SUT System Under Test
TMP Test Management Protocol
TMPDU Test Management Protocol Data Unit
TP Test Purpose
TSS&TP Test Suite Structure and Test Purposes
TTCN Tree and Tabular Combined Notation
UT Upper Tester
Page 11
ETS 300 836-4: May 1998
4 Abstract Test Method (ATM)
4.1 ATM for MAC protocol
There are two different ATMs supported by the MAC ATS:
- co-ordinated test method;
- remote test method.
4.1.1 Co-ordinated test method
In this ATM there is an UT which communicates with the LT by means of a Test Management Protocol
(TMP). The UT can send Protocol and Data Units (PDU) and examine the content of received PDUs.
There is one Point of Control and Observation (PCO). This is in the test system at the upper boundary of
the CAC (PCO-L) above which is the LT. The boundary between the IUT and the UT is not considered a
PCO.
The test events at PCO-L are specified in terms of HCS-primitives, HMPDUs and Test Management
PDUs (TMPDUs). The behaviour at the upper boundary of the IUT is not explicitly described in test cases;
it is defined in the definition of the TMP which is implemented in the upper tester. The TMP is specified in
annex A.
Test system SUT
Lower Upper
Tester TM-PDUs Tester
HM-PDUs MAC (IUT)
PCO L
CAC CAC
PHY
Figure 1: Co-ordinated test method
4.1.2 Remote test method
In this ATM there is no special UT, the layer(s) in the SUT above the IUT may be considered as a notional
upper tester. There is only one PCO. This is at the upper boundary of the CAC in the test system (PCO-L)
above which is the lower tester. There is no PCO at the upper boundary of the IUT and no observation is
possible at that point. It is however possible to control the IUT although this is specified by informal means
(i.e. implicit sends).
The test events at PCO-L are specified in terms of HCS-primitives and HMPDUs. The behaviour at the
upper boundary of the IUT is not explicitly specified. It is only possible to specify actions at the upper
boundary in terms of the resulting events at PCO-L.
Page 12
ETS 300 836-4: May 1998
Test system SUT
Notional
Manage-
Lower Informal
Upper
ment
Control
Tester Tester
entity
HM-PDUs MAC (IUT)
PCO L
CAC CAC
PHY
Figure 2: Remote test method
In this ATM the ATS uses implicit sends where the sending of a PDU requires an action at the upper
boundary of the IUT. The use of an implicit send means "take whatever action is required to cause the IUT
to send the specified PDU". Questions are included in the PIXIT regarding if, and how, such PDUs can be
sent.
There are some disadvantages with this ATM:
- tests need to be deselected if the specified implicit sends are not possible according to the PIXIT;
- it is not possible to test what happens on reception of a PDU beyond detection of PDUs which are
sent in response;
- it is not possible to test the correct implementation of functions such as encryption and decryption
because the PDU at the upper boundary of the IUT cannot be specified or examined.
The main advantage of this ATM is that it imposes no additional requirements on the IUT beyond those in
the protocol specification.
4.1.3 Choice of MAC ATM
The ATM used is selected via a test suite parameter whose value is assigned in the PIXIT.
The choice of ATM will have an effect on the coverage of the ATS. See subclause 6.2 for an indication of
which test cases become untestable for particular ATMs. The co-ordinated test method gives the greater
coverage because many test cases can only be tested using this ATM. On the other hand, there are no
test cases which can only be tested using the remote test method.
4.2 ATM for CAC protocol
There are three different ATMs supported by the CAC ATS:
- co-ordinated embedded test method - for normal HIPERLAN implementations;
- remote embedded test method - for normal HIPERLAN implementations;
- remote test method - for HIPERLAN enhancement units.
In the embedded test methods the IUT is embedded under the HIPERLAN MAC layer and in the
co-ordinated embedded test method the same upper tester as for the MAC ATS is used. Where the MAC
layer can act as a forwarder the upper tester is never used and there are no implicit sends, therefore there
is no difference between the Co-ordinated Embedded and Remote Embedded test methods.
Page 13
ETS 300 836-4: May 1998
The test method used depends on the test suite parameters HEU (HIPERLAN Enhancement Unit), U_T
(Upper Tester) and forwarder:
-if HEU is true then the remote test method is used (in this case U_T and forwarder should be false
as there is no CAC interface);
- otherwise if forwarder is true then the remote embedded test method (identical to co-ordinated
embedded) is used;
- otherwise if U_T is true the co-ordinated embedded test method is used;
- otherwise the remote embedded test method is used.
5 Requirements on underlying layers for testing
5.1 MAC testing
5.1.1 CAC service for MAC testing
The underlying layers used for MAC testing shall provide the HIPERLAN CAC service as defined in
ETS 300 652 [1] clause 7 with the following modifications:
a) all HC-UNITDATA-request primitives issued by the IUT shall result in a HC-UNITDATA-indication
primitive at the tester, except in the following situations:
- there are simultaneous attempts to transmit by the IUT and the tester in which case the
normal contention situation applies;
- this is prevented due to errors in the physical layer.
In particular an HC-UNITDATA-indication primitive shall be invoked at the tester side even if the
tester is not identified by the destination address parameter of an HC-UNITDATA-request primitive
invoked by the IUT, although this would be contrary to ETS 300 652 [1] subclause 7.7;
b) all HC-UNITDATA-request primitives issued by the IUT with the destination address being an
individual HCSAP address not in the range 00 00 00 00 00 00 to 00 00 00 FF FF FF shall be
considered successful and result in an HC-STATUS (successful) primitive issued unless the
exceptions described in (a) above apply;
c) there shall be a condition, the "busy condition", which can be controlled by the lower tester in which
no HC-SYNC or HC-FREE primitives may be issued to the IUT. It shall be possible to terminate this
condition with either an HC-SYNC or HC-FREE primitive being issued to the IUT (unless the CAC in
the SUT does not support the synchronized channel access cycle in which case the HC-FREE is
issued in both situations);
d) there shall be a facility to measure and report the channel access priority used by the IUT when
transmitting a DT-HCPDU following the termination of the busy condition.
NOTE: The busy condition is controlled by means of test suite operations.
5.1.2 CAC protocol for MAC testing
If the underlying layers in the SUT are according to ETS 300 652 [1] then the CAC protocol implemented
in the tester shall conform to ETS 300 652 [1] clause 8 with the following modifications to support the
modifications to the CAC service described above:
a) the procedure in ETS 300 652 [1] subclause 8.4.6 (user data delivery) is executed on receipt of all
DT-HCPDUs (irrespective of destination HCSAP address);
Page 14
ETS 300 836-4: May 1998
b) the procedure in ETS 300 652 [1] subclause 8.5.5 (HCPDU reception) shall be modified such that
an AK-HCPDU is generated and transmitted in all cases where an LBR-HBR HCPDU is received
and not rejected, where DA is an individual HCSAP address not in the range 00 00 00 00 00 00 to
00 00 00 FF FF FF;
c) the tester HC-entity shall transmit a busy condition burst in each of the following circumstances:
- on entering the busy condition if in the channel free condition at that time;
- immediately following transmission or reception of a multicast DT-HMPDU in the busy
condition;
- immediately following transmission or reception of an AK-HCPDU in the busy condition;
- on detection that an expected AK-HCPDU has not been received when in the busy condition;
- when in the busy condition and a time i has elapsed since the last transmission by the
BC
tester, except when awaiting an AK-HCPDU;
The minimum duration of a busy condition burst shall be 256 high bit-rate periods, there is no
maximum duration specified. The burst shall not contain a DT-HCPDU addressed to the IUT
(including a multicast DT-HCPDU) or an AK-HCPDU but is otherwise unspecified. The maximum
duration of i is 1 900 High bit-rate periods, no minimum duration is specified. For the purposes of
BC
determining the channel free condition the channel shall be considered idle during the transmission
of these bursts.
d) when the tester HC-entity is instructed to terminate the busy condition with an HC-SYNC primitive
by means of a test suite operation it shall:
- if a channel access cycle is in progress transmit no further busy condition bursts. The test
suite operation shall return at the time when HC-SYNC would normally be issued following
that cycle (whether or not HC-SYNC is actually issued);
- if in the channel free condition a multicast DT-HCPDU with an HCSAP destination address of
All_Neighbours and an HCSDU field of length 1 octet is transmitted. An HC-STATUS
(unsuccessful) is issued at the start of transmission of this HCPDU and the test suite
operation returns following transmission of this HCPDU, no HC-SYNC or HC-STATUS
(successful) is issued;
- otherwise at the next time the channel free condition occurs no HC-FREE is issued but a
multicast DT-HCPDU with an HCSAP destination address of All_Neighbours and an HCSDU
field of length 1 octet is transmitted. The test suite operation returns following transmission of
this HCPDU, no primitive is issued;
e) if a DT-HCPDU is received in the channel access cycle following termination of the busy condition
as described in d) then its channel access priority shall be determined and passed to the lower
tester;
f) when the tester HC-entity is instructed to terminate the busy condition with an HC-FREE primitive it
shall:
- if a channel access cycle is in progress, transmit one busy condition burst at the end of that
cycle (as when in the busy condition) and no further busy condition bursts. No HC-SYNC
primitive shall be issued at the end of that channel access cycle. The test suite operation
shall return i following the end of that busy condition burst;
MF
- otherwise no further busy condition bursts are transmitted and the test suite operation shall
return i following the end of the last transmission by the tester.
MF
Page 15
ETS 300 836-4: May 1998
5.1.3 PHY protocol for MAC testing
The PHY protocol used in the tester shall support the provision of the testing CAC service and, where
applicable, the testing CAC protocol defined above. There are no further requirements defined.
NOTE: The PHY protocol in the tester may be according to ETS 300 652 [1], however
modifications to facilitate testing are not excluded by this ETS.
5.2 CAC testing
5.2.1 PHY service interface for CAC testing
This PHY service interface is defined for the purposes of CAC testing only. It is purely abstract for the
purpose of relating the Tree and Tabular Combined Notation (TTCN) test cases for the CAC with activity
on the channel and is therefore defined in terms of the relationship between primitives at the PH-SAP with
signals transmitted and received by the PHY of the test system. It does not define the overall PHY service
provided between the PH-SAP in the test system and the PH-SAP in the SUT.
The model of the PHY service used here assumes that the tester PHY is able to detect transmissions
from the IUT while it is transmitting, however it does not rely on it being able to demodulate such
transmissions.
It is not intended to describe the mechanism by which a lower tester communicates with the PHY in a real
test system. The timing of primitives are defined in relation to activity on the channel, so that such timings
can be referred to within test cases. It is recognized that this prevents the primitives being generated in
real time because it may not be possible to determine the time of an event such as the first bit of a burst
until a finite time after the event occurs.
5.2.1.1 PHY service primitives
Table 1: PHY service primitives
Facility Service Primitive Parameters
Data transfer PHSDU transfer PH-UNITDATA-request (LBR_part, HBR_part)
PH-UNITDATA-confirm -
PH-UNITDATA-indication (LBR_part, HBR_part)
Channel access Access control PH-START-request -
PH-START-indication -
PH-END-request -
PH-END-indication -
Initialization Initialization PH-RESET -
Channel selection Channel control PH-CHANNEL (Channel_no)
5.2.1.1.1 PH-UNITDATA-request (PH-UD-RQ)
This Abstract Service Primitive (ASP) is used to initiate transmission of an LBR or LBR-HBR HCPDU. The
parameters contain the PDU to be transmitted, in the case of an LBR HCPDU HBR_part is null. The start
of the burst (i.e. the first bit) is transmitted at the time of the primitive.
5.2.1.1.2 PH-UNITDATA-confirm (PH-UD-CO)
This ASP is issued by the PHY on completion of transmission of an HCPDU. The time of the primitive is at
the end of the burst (i.e. the last bit).
5.2.1.1.3 PH-UNITDATA-indication (PH-UD-IN)
This ASP is issued by the PHY on completion of reception of an HCPDU. The parameters contain the
received HCPDU, in the case of an LBR HCPDU HBR_part is null. The time of the primitive is at the end
of the burst (i.e. the last bit).
Page 16
ETS 300 836-4: May 1998
5.2.1.1.4 PH-START-request (PH-ST-RQ)
This ASP is used to initiate the transmission of a channel access burst. The start of the burst (i.e. the first
bit) is transmitted at the time of the primitive. The burst continues until a further primitive is received.
5.2.1.1.5 PH-START-indication (PH-ST-IN)
This ASP is issued by the PHY to indicate that it has detected the start of a transmission from the IUT. In
the case of an LBR or LBR-HBR burst the time of the primitive is that of the start of the burst (i.e. the first
bit). In other cases (e.g. channel access bursts) it may be the time when power is detected if it is not
possible to accurately determine the start of the bit.
5.2.1.1.6 PH-END-request (PH-EN-RQ)
This ASP is used to stop the transmission of a channel access burst. The end of the burst (i.e. the last bit)
is transmitted at the time of the primitive.
5.2.1.1.7 PH-END-indication (PH-EN-IN)
This ASP is issued by the PHY to indicate that it has detected the end of a transmission from the IUT,
other than an HCPDU. It may also be issued at the end of an HCPDU if transmissions from the tester
prevented its reception. The time of the primitive may be the time of the end of the burst (i.e. the last bit)
or the time that power ceased to be detected.
5.2.1.1.8 PH-RESET (PH-REST)
This ASP is used to reset the state of the physical layer in the tester. When this primitive is received by the
PHY any transmission in progress is terminated. If the receiver detects a signal at the time of the primitive
then a PH-START-indication is issued, otherwise no primitive is issued in response.
5.2.1.1.9 PH-CHANNEL (PH-CHAN)
This ASP is used to request the tester to change channel. The parameter channel_no indicates the new
channel to be used. Where the parameter is null any channel that the SUT is configured for operation on
may be chosen.
NOTE: In practice it may not be necessary to implement this primitive because manual
reconfiguration of the SUT between test cases is likely to be necessary for operation
on different channels and manual re-configuration of the tester could be carried out at
the same time.
Page 17
ETS 300 836-4: May 1998
5.2.1.2 Sequence of primitives
The possible sequences of primitives at the tester PHY interface are defined by figure 3 and table 2.
1 4
PH-UD-CO
TX: Burst TX: HCPDU
Idle
RX: Idle RX: Idle
PH-ST-IN
PH-ST-IN
PH-ST-IN
PH-UD-IN
915 7011
8 PH-EN-IN
PH-EN-IN 6
PH-EN-IN
12 15
PH-CO-IN
TX: Burst TX: Idle TX: HCPDU
RX: Active RX: Active RX: Active
PH-ST-IN PH-ST-IN
18 20
12 13
PH-ST-IN
PH-UD-IN
PH-ST-IN
Figure 3: State transitions
Page 18
ETS 300 836-4: May 1998
Table 2: State transitions
TX state Idle Idle Burst Burst HCPDU HCPDU
RX state Idle Active Idle Active Idle Active
Abbreviation II IA BI BA HI HA
Action None None Transmit Transmit Transmit Transmit
(TX) Channel channel HCPDU HCPDU
access burst access burst
Events RX_start RX_end RX_start RX_end TX_end TX_end
possible RX_HCPDU RX_HCPDU RX_start RX_end
RX_end_HC (note 1) RX_HCPDU
RX_start_HC (note 1)
PH-ST-RQ 1 BI 12 BA XXXX
PH-EN-RQ X X 2 II 13 IA X X
PH-UD-RQ 3 HI 14 HA XXXX
PH-REST 17 II 21 PH-ST-IN 2 II 18 PH-ST-IN 19 II 20 PH-ST-IN
IA IA IA
PH-CHAN 16 II 16 IA 16 BI 16 BA 16 HI 16 HA
TX_end----4 PH-UD-CO 15 PH-UD-CO
II IA
RX_start 5 PH-ST-IN IA - 8 PH-ST-IN - 10 PH-ST-IN -
BA HA
RX_end - 6 PH-EN-IN II - 9 PH-EN-IN BI - 11 PH-EN-IN
HI
RX_HCPDU - 7 PH-UD-IN II - 9 PH-EN-IN BI - 11 PH-EN-IN
HI
RX_end_HC - 22 PH-UD-IN----
PH-ST-IN IA
RX_start_HC - 21 PH-ST-IN----
IA
NOTE 1: In these states RX_end and RX_HCPDU cannot be distinguished.
NOTE 2: Explanation of symbols:
n SS Transition number n to state SS
n PP-PP-PP SS Transition number n to state SS issuing primitive PP-PP-PP
n PP-PP-PP SS Transition number n to state SS issuing primitive PP-PP-PP
(can only occur in case of error)
X Invalid primitive for state
- Impossible event for state
The events referred to in table 2 are defined in table 3.
Table 3: Descriptions of events
Event Description
TX_end Completion of transmission of a HCPDU (i.e. sending of last bit).
RX_start Detection of start of signal from IUT.
RX_end Detection of end of signal from the IUT, but not the end of an HCPDU (see note).
RX_HCPDU Detection of the end of an HCPDU and the signal from the IUT (see note).
RX_end_HC Detection of the end of an HCPDU, but not the end of the signal from the IUT.
RX_start_HC Detection of the start of an HCPDU, but not the start of the signal from the IUT.
NOTE: While the tester is transmitting, RX_end and RX_HCPDU are considered indistinguishable. If
the tester transmitted at any time while receiving a burst from the IUT RX_end may be
generated instead of RX_HCPDU even if that burst contained an HCPDU.
Page 19
ETS 300 836-4: May 1998
6 Untestable test purposes
ETS 300 836-3 [8] specifies the Test Suite Structure and Test Purposes (TSS&TP) for HIPERLAN. Some
Test Purposes (TP) cannot be tested with the specific test methods associated with this ATS specification;
some of these cannot be tested with any standardized tes
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...