baseband - edatop.com · part b baseband test suite structure (tss) and test purposes (tp) system...

Core System Package
Part B
BasebandTest Suite Structure (TSS) andTest Purposes (TP)System Specification 2.0 + EDR

This document defines the TSS and TPs for the Bluetooth® Wireless Technology Baseband layer.

BB.TS/2.0.E.4Document No

14 October 2005Issued

2.0.E.4Revision

BLUETOOTH TEST SPECIFICATION Ver. 2.0 + EDR [vol 2] page 2 of 228

Baseband

CONTENTS

1 1 .................................................................................................. Scope92 Normative References ....................................................................... 113 Definitions and Abbreviations ..........................................................13

3.1 Definitions ..................................................................................133.2 Abbreviations .............................................................................133.3 Overview....................................................................................133.4 Test suite structure (TSS) ..........................................................133.5 Test groups ................................................................................14

3.5.1 Protocol groups .............................................................143.5.1.1 Frequency Hopping/Signalling........................143.5.1.2 TX/RX Timing .................................................143.5.1.3 Coding/Decoding ............................................153.5.1.4 Automatic Repeat Request.............................153.5.1.5 Inquiry.............................................................163.5.1.6 Paging ............................................................163.5.1.7 Connection .....................................................163.5.1.8 Piconet............................................................16

3.5.2 Main test group .............................................................163.5.2.1 Valid Behavior (BV) tests ................................163.5.2.2 Invalid Behavior (BI) tests...............................16

4 Test Purposes (TP).............................................................................174.1 Introduction ................................................................................17

4.1.1 TP definition conventions..............................................174.1.2 TP naming conventions.................................................174.1.3 General Test Conditions................................................174.1.4 Lower Layer assumptions .............................................184.1.5 Upper Layer assumptions .............................................184.1.6 Implicit testing ...............................................................184.1.7 Conventions for mathematical notations .......................18

4.1.7.1 Mathematical signs.........................................184.1.7.2 Power of the base 10......................................18

4.1.8 Representation of parameter values .............................194.1.9 Advertisement of features for test cases.......................19

4.2 Frequency Hopping Procedures ................................................194.2.1 Frequency Hopping.......................................................19

4.2.1.1 BV test purposes ............................................194.2.1.2 TP/PHYS/FRE/BV-01-C

(79 channel hop seq)20

2 14 October 2005


Baseband

4.2.1.3 TP/PHYS/FRE/BV-02-C (AFH Hop Seq)21

4.2.1.4 TP/PHYS/FRE/BV-03-C (AFH Hop Seq after Master Slave Switch)24

4.2.1.5 BI test purposes..............................................264.3 TX/RX Timing.............................................................................26

4.3.1 TX Timing ......................................................................264.3.1.1 BV test purposes ............................................264.3.1.2 TP/PHYS/TRX/BV-01-C (master TX timing) ...274.3.1.3 BI test purposes..............................................28

4.3.2 RX Timing......................................................................284.3.2.1 EDR Guard Time ............................................284.3.2.2 BV test purposes ............................................284.3.2.3 TP/PHYS/TRX/BV-03-C

(master RX/TX timing)284.3.2.4 TP/PHYS/TRX/BV-04-C

(slave RX/ TX timing)304.3.2.5 TP/PHYS/TRX/BV-05-C (Symbol rate) ...........31

4.3.3 Enhanced Data Rate Guard Time .................................324.3.3.1 BV test purposes ............................................324.3.3.2 TP/PHYS/TRX/BV-06-E (EDR Guard Time) ...324.3.3.3 BI test purposes..............................................36

4.3.4 Synchronization Sequence and Trailer .........................364.3.4.1 BV test purposes ............................................364.3.4.2 TP/PHYS/TRX/BV-07-E (EDR Synchronization

Sequence and Trailer)364.3.4.3 BI test purposes..............................................37

4.4 Coding/Decoding .......................................................................384.4.1 Packet Types.................................................................38

4.4.1.1 BV test purposes ............................................384.4.1.2 TP/PROT/COD/BV-01-C (HV1 packet type) ...384.4.1.3 TP/PROT/COD/BV-02-C (HV2 packet type) ...404.4.1.4 TP/PROT/COD/BV-03-C (HV3 packet type) ...424.4.1.5 TP/PROT/COD/BV-04-C (DV packet type) .....444.4.1.6 TP/PROT/COD/BV-05-C (DH1 packet type)...464.4.1.7 TP/PROT/COD/BV-06-C (DM3 packet type) ..494.4.1.8 TP/PROT/COD/BV-07-C (DH3 packet type)...514.4.1.9 TP/PROT/COD/BV-08-C (DM5 packet type) ..534.4.1.10 TP/PROT/COD/BV-09-C (DH5 packet type)...564.4.1.11 TP/PROT/COD/BV-10-C

(AUX1 packet type)584.4.1.12 TP/PROT/COD/BV-11-C

(Erroneous slave address)604.4.1.13 TP/PROT/COD/BV-17-C

(EV3 packet type)624.4.1.14 TP/PROT/COD/BV18-C (EV4 packet type) ....64

14 October 2005 3


Baseband

4.4.1.15 TP/PROT/COD/BV19-C (EV5 packet type) ....664.4.1.16 TP/PROT/COD/BV-20-C (2-EV3 packet type)...

684.4.1.17 TP/PROT/COD/BV-21-C (2-EV5 packet type)...



744.4.1.20 TP/PROT/COD/BV-24-C (2-DH1 packet type) ..






894.4.1.26 BI test purposes..............................................91

4.4.2 FEC (R=1/3)..................................................................914.4.2.1 BV test purposes ............................................914.4.2.2 TP/PROT/COD/BV-12-C

(Correctable packet header)914.4.2.3 TP/PROT/COD/BV-14-C

(Correctable error HV1 payload)944.4.2.4 BI test purposes..............................................96

4.4.3 FEC (R=2/3)..................................................................964.4.3.1 BV test purposes ............................................964.4.3.2 TP/PROT/COD/BV-16-C

(Correctable error DM1 payload)974.4.3.3 BI test purposes..............................................99

4.5 ARQ ...........................................................................................994.5.1 ARQ Procedures - Master.............................................99

4.5.1.1 BV test purposes ............................................994.5.1.2 TP/PROT/ARQ/BV-01-C (Explicit NAK) .......1004.5.1.3 TP/PROT/ARQ/BV-02-C (Implicit NAK)........1024.5.1.4 TP/PROT/ARQ/BV-03-C

(Uncorrectable packet header)1044.5.1.5 TP/PROT/ARQ/BV-04-C

(Uncorrectable payload)1074.5.1.6 TP/PROT/ARQ/BV-05-C (SEQN) ................. 1104.5.1.7 TP/PROT/ARQ/BV-06-C (FLOW control) ..... 1134.5.1.8 TP/PROT/ARQ/BV-08-C (Implicit GO) ......... 116

4 14 October 2005


Baseband

4.5.1.9 TP/PROT/ARQ/BV-10-C (Same SEQN value)119

4.5.1.10 TP/PROT/ARQ/BV-27-C (Explicit NAK – eSCO Master)121

4.5.1.11 TP/PROT/ARQ/BV-28-C (Implicit NAK – eSCO Master)124

4.5.1.12 TP/PROT/ARQ/BV-30-C (Uncorrectable header – eSCO Master)127

4.5.1.13 BI test purposes............................................1304.5.2 ARQ Procedures - Slave .............................................131

4.5.2.1 BV test purposes ..........................................1314.5.2.2 TP/PROT/ARQ/BV-14-C

(Uncorrectable packet header)1314.5.2.3 TP/PROT/ARQ/BV-15-C

(Uncorrectable payload)1344.5.2.4 TP/PROT/ARQ/BV-16-C (Explicit NAK)........1374.5.2.5 TP/PROT/ARQ/BV-18-C (SEQN) .................1384.5.2.6 TP/PROT/ARQ/BV-19-C (FLOW control) .....1414.5.2.7 TP/PROT/ARQ/BV-23-C

(Same SEQN value)1444.5.2.8 TP/PROT/ARQ/BV-25-C

(Retransmission of DV packet)1464.5.2.9 TP/PROT/ARQ/BV-26-C

(Uncorrectable DV packet)1494.5.2.10 TP/PROT/ARQ/BV-29-C (Explicit NAK –

eSCO Slave)1514.5.2.11 TP/PROT/ARQ/BV-31-C (Uncorrectable

header original transmission – eSCO Slave)1554.5.2.12 TP/PROT/ARQ/BV-32-C (Uncorrectable

header re-transmission – eSCO Slave)1584.5.2.13 BI test purposes............................................162

4.6 Inquiry ......................................................................................1624.6.1 Inquiry Procedures - Master ........................................162

4.6.1.1 BV test purposes ..........................................1624.6.1.2 TP/PHYS/INQ/BV-01-C (Inq hop seq) ..........1634.6.1.3 TP/PHYS/INQ/BV-03-C (Inquiry proc) ..........1654.6.1.4 BI test purposes............................................166

4.6.2 Inquiry Procedures - Slave ..........................................1674.6.2.1 BV test purposes ..........................................1674.6.2.2 TP/PHYS/INQ/BV-10-C

(Inquiry response)1674.6.2.3 TP/PHYS/INQ/BV-14-C (Inquiry scan

window and interval)1684.6.2.4 TP/PHYS/INQ/BV-15-C (Interlaced Inquiry

scan window and interval)1704.7 Paging......................................................................................172

4.7.1 Paging Procedures - Master........................................172

14 October 2005 5


Baseband

4.7.1.1 BV test purposes ..........................................1724.7.1.2 TP/PHYS/PAG/BV-01-C (Page hop seq)......1724.7.1.3 TP/PHYS/PAG/BV-03-C

(Page resp to 1st msg)1754.7.1.4 TP/PHYS/PAG/BV-05-C

(Page resp to 2nd msg)1774.7.2 Paging Procedures - Slave .........................................180

4.7.2.1 BV test purposes ..........................................1804.7.2.2 TP/PHYS/PAG/BV-10-C

(Page resp 1/1 slot)1814.7.2.3 TP/PHYS/PAG/BV-12-C

(Page resp 1/2 slot)1834.7.2.4 TP/PHYS/PAG/BV-14-C (

Page scan interval R0)1854.7.2.5 TP/PHYS/PAG/BV-16-C

(Page scan interval R1)1874.7.2.6 TP/PHYS/PAG/BV-17-C (Page scan

interval R1 with Interlaced Scan)1894.7.2.7 TP/PHYS/PAG/BV-18-C

(Page scan interval R2)1914.7.2.8 TP/PHYS/PAG/BV-19-C (Page scan

interval R2 and interlaced scan)1924.8 Connection...............................................................................193

4.8.1 Connection State - Master...........................................1934.8.1.1 BV test purposes ..........................................1944.8.1.2 TP/PROT/CON/BV-01-C (POLL at start up) .1944.8.1.3 TP/PROT/CON/BV-02-C (Polling slave).......1974.8.1.4 TP/PROT/CON/BV-03-C (Wrong UAP) ........1994.8.1.5 TP/PROT/CON/BV-04-C

(Change from DV to HV1)2014.8.1.6 BI test purposes............................................203

4.8.2 Connection State - Slave.............................................2044.8.2.1 BV test purposes ..........................................2044.8.2.2 TP/PROT/CON/BV-05-C (POLL at start up) .2044.8.2.3 TP/PROT/CON/BV-08-C (Wrong UAP) ........2084.8.2.4 TP/PROT/CON/BV-09-C

(Change from DV to HV1)2104.8.2.5 BI test purposes............................................212

4.9 Piconet.....................................................................................2134.9.1 Piconet - Master ..........................................................213

4.9.1.1 BV test purposes ..........................................2134.9.1.2 TP/PROT/PIC/BV-03-C (Broadcast packets)2134.9.1.3 BI test purposes............................................216

4.9.2 Piconet - Slave............................................................2164.9.2.1 BV test purposes ..........................................2164.9.2.2 TP/PROT/PIC/BV-04-C (Broadcast NAK) ....216

6 14 October 2005


Baseband

4.9.2.3 BI test purposes............................................219

5 Test Case Mapping...........................................................................2216 Provisional Baseband Testing (EDR) .............................................227

14 October 2005 7


Baseband

8 14 October 2005


Baseband

1 SCOPE

This Bluetooth document contains the Test Suite Structure (TSS) and Test Pur-poses (TP) to test the Bluetooth Baseband layer. The objective of this Test Specification is to provide a basis for conformance tests for Bluetooth devices giving a high probability of air interface inter-operability between different man-ufacturer's Bluetooth devices. The general concepts and conformance testing principles as defined in ISO/IEC 9646-1 and OSI Conformance Testing Meth-odology and Framework (CTMF) are used as a basis for the testing of Blue-tooth protocol and profile implementation.

The following revisions are applicable to this document.

Revision Date Description

D5r3 2003-11-05 Original Release

D10R00 2004-03-03 Re-partitioned to match Main Specification Volume/Part partitioning. TSE 479, 487, 495, 496, 497, 498, 501, 509, 510, 513, 527, 535, 536, and 556 incorporated

D10R01 2004-03-15 Editorial changes

D12r02 2004-03-18 Editorial changes. Changed reference and document num-bering to D12 to reflect applicable Bluetooth version.

1.2.1 2004-03-25 Editorial changes.Changed document numbering and revi-sion number to conform with legacy system.

1.2.2 2004-07-01 Changed page numbering to begin part with page 1 and made editorial changes to accommodate Vol. 1, Part A.

2.0.E.0 2004-10-19 Incorporated changes for V2.0 + EDRIncorporated TSE 581 for TP/PROT/PIC/BV-03-CIncorporated TSE 645 for TP/PROT/ARQ/BV-06-C.Incorporated TSE 666 for TP/PROT/COD/BV-18-C and TP/PROT/COD/BV-19-C

2.0.E.1 2004-10-20 Editorial change to TP/PHYS/TRX/BV

2.0.E.2 2004-11-01 Add EDR Guard Time Measurement procedure to TP/PHYS/TRX/BV-06-E

2.0.E.3 2004-11-04 Editorial change and repagination. First version for 1.2/2.0/2.0 + EDR available for qualifica-tion

BB.TS.2.0.1r0 2005-08-03 Incorporate TSE 723 to TP/PROT/CON/BV-01-CIncorporate TSE 735 for TP/PHYS/TRX/BV-06-E

2.0.4r1 2005-09-19 Removed spec version 1.2 from title cover pageCorrected version #, revision number #, & file name, Replaced outer parens in TP/PHYS/TRX/BV-06-E for start of symbol0

2.0.4 2005-10-14 Prepare for publication.

Scope 14 October 2005 9


Baseband

10 14 October 2005 Scope


Baseband

2 NORMATIVE REFERENCES

These normative references are cited at the appropriate places in the text.

The normative references listed below represent the most current versions as of the date of publication of this document. The most current version of a listed reference should be used unless a specific version is noted in the list.

[1] Specification of the Bluetooth System, Core System Package, Volume 2, Part B

[2] ISO/IEC 9646-1: "Conformance testing methodology and framework / General con-cepts", http://www.etsi.org

[3] ISO/IEC 9646-2: "Conformance testing methodology and framework / Abstract Test Suite specification", http://www.etsi.org

[4] ETSI ETR 266: "Methods for Testing and Specification (MTS); Test Purpose style guide", http://www.etsi.org

[5] Specification of the Bluetooth System, Core System Package, Volume 2, Part A, Radio Frequency (RF)

[6} PICS Proforma for Baseband (BB)

[7] Specification of the Bluetooth System, Core System Package, Volume 3, Part D

Normative References 14 October 2005 11

http://www.etsi.org

http://www.etsi.org

http://www.etsi.org

http://www.etsi.org

http://www.etsi.org

http://www.etsi.org


Baseband

12 14 October 2005 Normative References


Baseband

3 DEFINITIONS AND ABBREVIATIONS

3.1 DEFINITIONS

For the purpose of this Bluetooth document, the definitions given in Specifica-tion of the Bluetooth System, Volume 2, Part B and "ISO/IEC 9646-1" [2] apply.

Additional definitions in this Test Specification are given in Volume 1, Part A, Test Strategy and Terminology Overview.

Mathematical conventions used in this document comply with the definitions of Test Strategy & Terminology Overview, Volume 1 Part A

3.2 ABBREVIATIONS

For the purpose of this Bluetooth document, the abbreviations given in Test Strategy & Terminology Overview Volume 1 Part A are applicable.

3.3 OVERVIEW

The Baseband is layer 2 of the Bluetooth protocol stack.

Figure 3.1: Bluetooth protocol stack, Basic Layers

3.4 TEST SUITE STRUCTURE (TSS)

The test suite structure is structured as a tree with a first level defined as BB representing the protocol group "BB for Master and Slave".

Bluetooth RF

Baseband

Link Manager

L2CAP Audio

HCI

Definitions and Abbreviations 14 October 2005 13


Baseband

Figure 3.2: Test suite structure for the Baseband Part.

The test suite structure is structured as a tree with a first level defined as BB representing the protocol group "BB for Master and Slave".

3.5 TEST GROUPS

The test groups are organized in 3 levels. The first level defines the protocol groups representing the protocol services. The second level, separates the protocol services in functional modules. The last level in each branch contains the standard ISO subgroups BV.

3.5.1 Protocol groups

The protocol groups identify the Bluetooth Baseband services: Frequency Hop-ping, TX/RX Timing, Coding/Decoding, Automatic Repeat Request, Inquiry, Paging, Connection, and Piconet defined in Specification of the Bluetooth Sys-tem, Volume 2, Part A .

3.5.1.1 Frequency Hopping/Signalling

With the functional module:

• Frequency Hopping

3.5.1.2 TX/RX Timing

With the functional module:

• TX Timing

• RX Timing

Baseband Test Suite Structure

Frequency hopping procedures

TX/RX timing

Coding/Decoding

ARQ

Inquiry

Paging

Connection

Piconet

14 14 October 2005 Definitions and Abbreviations


Baseband

• Enhanced Data Rate Guard Time

• Enhanced Data Rate Synchronization Sequence and Trailer

3.5.1.3 Coding/Decoding

With the functional modules:

• Packet Types

• FEC (R=1/3)

• FEC (R=2/3)

3.5.1.4 Automatic Repeat Request


• ARQ Procedures - Master

• ARQ Procedures - Slave

Definitions and Abbreviations 14 October 2005 15


Baseband

3.5.1.5 Inquiry


• Inquiry Procedures - Master

• Inquiry Procedures - Slave

3.5.1.6 Paging


• Paging Procedures - Master

• Paging Procedures - Slave

3.5.1.7 Connection


• Connection - Master

• Connection - Slave

3.5.1.8 Piconet


• Piconet - Master

• Piconet - Slave

3.5.2 Main test group

The main test groups are valid behavior group and the invalid behavior group.

3.5.2.1 Valid Behavior (BV) tests

This sub group provides testing to verify that the IUT reacts in conformity with the dynamic conformance requirements of the Bluetooth standard, after receipt or exchange of a valid Protocol Data Units (PDUs). Valid PDUs means that the exchange of messages and the content of the exchanged messages are con-sidered as valid.

3.5.2.2 Invalid Behavior (BI) tests

This sub group provides testing to verify that the IUT reacts in conformity with the dynamic conformance requirements of the Bluetooth standard, after receipt of a syntactically or semantically invalid PDU.

16 14 October 2005 Definitions and Abbreviations


Baseband

4 TEST PURPOSES (TP)

4.1 INTRODUCTION

4.1.1 TP definition conventions

The TPs are defined following the particular rules of TP Definition Conventions in Test Strategy & Terminology Overview, Volume 1 Part A.

4.1.2 TP naming conventions

The identifier of the TP: TP/<class>/<feat>/<xx>-<nn>-<y> is built according to the standard defined by "TP Naming Conventions" in Test Strategy & Terminol-ogy Overview, Volume 1 Part A

Features/ functions tested for this specification are:.

4.1.3 General Test Conditions

For the purpose of the test procedures defined in this Bluetooth document it is assumed that propagation delay on the air interface and runtime of the tester and of the IUT can be neglected.

The test purposes defined in this Test Specification represent only the behavior that is important to create the final verdict. Additional behavior that provides BB and LM is not presented. E.g. the Master polls the slave in order to synchronize the slave to the channel. Further LM has 30s of time to response to LMP requests, between this 30s a possible behavior is not stated in the test proce-dure of the test purposes.

Identifier: Class Identifier <class>

Physical test for formal testingProtocol test for formal testing

PHYSPROT

Identifier: Feature Identifier <feat>

Frequency HoppingTX/RX TimingCoding/DecodingAutomatic repeat requestInquiryPagingConnectionPiconet

FRETRXCODARQINQPAGCONPIC

Table 4.1: TP Naming Conventions

Test Purposes (TP) 14 October 2005 17


Baseband

For the definition of Nominal Test Conditions and Extreme Test Conditions, see sections 5.1 and 5.2 of Specification of the Bluetooth System, Core System Package, Volume 2, Part A, Radio Frequency (RF). Unless otherwise speci-fied, tests shall be performed under normal conditions.

4.1.4 Lower Layer assumptions

For conformance testing of the Baseband layer it is necessary to have working lower layers in conformance with the lower layer Test Specification.

4.1.5 Upper Layer assumptions

For conformance testing of the Baseband layer it is necessary to have a Test Control Interface as described in Specification of the Bluetooth System, Vol-ume 3, Part A . HCI commands can be sent and HCI events can be received via this TCI to stimulate the IUT respectively to get information from the IUT. This interface builds the UT.

4.1.6 Implicit testing

For some subjects to be validated, conformance is not verified explicitly. This does not imply that correct functioning of these subjects is not essential, but that these are implicitly tested to a sufficient degree in other tests.

For example tests relating to Data Whitening are implicitly covered by other TP.

4.1.7 Conventions for mathematical notations

For the purpose of this Bluetooth document mathematical terms used through-out this document are given in this subclause.

4.1.7.1 Mathematical signs

The "plus or minus" sign is expressed by "+/-".

The sign "multiplied by" is expressed by "*".

The sign "divided by" is expressed by "/".

The sign "greater than or equal to" is expressed by ">=".

The sign "less than or equal to" is expressed by "<=".

4.1.7.2 Power of the base 10

Powers of the base 10 are expressed by "10Ex", where x is the exponent, e.g. 10E-3, 10E9.

18 14 October 2005 Test Purposes (TP)


Baseband

4.1.8 Representation of parameter values

It is important to indicate explicitly the numeric system which forms the basis of the value of a parameter. For the purpose of this Bluetooth document the fol-lowing indicators are used:

Values of binary represented parameters are enclosed in ' and 'B, e.g. binary 1011 is represented by '1011'B.

Values of hexadecimal represented parameters are enclosed in ' and 'H, e.g. hexadecimal A5F3 is represented by 'A5F3'H.

Values of octal represented parameters are enclosed in ' and 'O, e.g. octal A5F3 is represented by 'A5F3'O.

Values of decimal represented parameters are enclosed in ' and 'D, e.g. deci-mal 255 is represented by '255'D.

Values not enclosed according to the previous defined scheme are to be inter-preted as decimal represented values.

4.1.9 Advertisement of features for test cases

It is favorable to avoid LMP traffic that could create situations in which a test case is not designed to be executed or which may add complexity to the test system implementation. This can be achieved by proper selection of which fea-tures are advertised by the tester. In some test cases this is exactly specified in the test specification but in most cases it is not. As a general rule, for each test case the tester should not advertise more features than necessary to facilitate execution of the test purpose. Specifically, with the introduction of Enhanced Data Rate, this feature shall only be advertised by the tester in those test cases where it is necessary for the test purpose.

4.2 FREQUENCY HOPPING PROCEDURES

Test group objectives:

• To verify the correct implementation of the Frequency hopping procedure and the signalling rate.

4.2.1 Frequency Hopping

Test subgroup objectives:

• To verify the frequency hopping procedure.

4.2.1.1 BV test purposes




Baseband

• To test the behavior of the IUT in relation to syntactically and contextual cor-rect behavior of the test system.

4.2.1.2 TP/PHYS/FRE/BV-01-C (79 channel hop seq)

Verify that the hopping sequences in connection state are correct for the 79 channel hopping scheme.

• Reference[Vol. 2, Part B] Section 2.2.2 on page 59.

• Initial ConditionThe tester pages the IUT to become the master.The tester and IUT are in normal connection state. The Bluetooth clock of the tester is chosen to include clock wrap-around (227-1 to 0) during the test procedure.

• Test Procedurea) The tester transmits POLL packets in all master-to-slave slots. To

verify the sequence for every 32-hop-segment, 2600 packets are checked.

b) The tester records the clock values for which a response from the IUT is received. It is not necessary to check the content of the ACK packets sent by the IUT. Every signal sent back in the correct slot is taken as a criterion that the correct hop frequency was used.

c) The BT clock of the tester is reinitialized to the value used in the initial conditions. The IUT is paged again and test steps a) to b) are repeated.

d) Step c) is repeated so that the same clock values are tested three times in total.

e) The BT clock of the tester is initialized to a value randomly chosen such that the new clock value range used does not overlap with the previous range.in the initial conditions.

f) A new page procedure is performed and steps a) to d) are repeated.

• Test ConditionThe test is performed at normal conditions.

• Expected Outcome



Baseband

Pass verdict:

For each of the 5200 clock values the tester has recorded at least one response.

Fail verdict:

At least one of the 5200 clock values does not have any response.

• UncertaintiesN/A.

• Notesa) A standardized cable interface can be used for the baseband

connection.b) If the IUT responds with an LMP command the tester uses its own

LMP response as a trigger packet.c) In steps c) and d) of the test procedure, the test is repeated with

the same BT clock to detect any systematical errors.

4.2.1.3 TP/PHYS/FRE/BV-02-C (AFH Hop Seq)

Verify that the slave correctly implements the AFH hopping sequence for the following cases: 79 channel AFH, even channels bad, odd channels bad, and three “random” cases where one tests the minimum number of channels (20). IUT is slave and tester is master.

• Reference[Vol. 2, Part B] Section 2.3 on page 63.



Baseband

• Initial Conditiona) The tester pages the IUT to become the master.b) The tester and IUT are in normal connection state.c) Adaptive frequency hopping is enabled by the tester using all

channels: AHS(79).d) The Bluetooth clock of the master is chosen to include clock wrap-

around (227 – 1 to 0) during the test procedure.

• Test Procedurea) The tester transmits POLL packets in all master-to-slave slots. To

verify the sequence for every 32-hop-segment, 2600 packets are checked.

b) The tester records the clock values for which a response from the IUT is received. It is not necessary to check the content of the ACK packets sent by the IUT. Every signal sent back in the correct slot is taken as a criterion that the correct hop frequency was used.

c) The BT clock of the tester is reinitialized to the value used in the initial conditions. The IUT is paged again and test steps a) and b) are repeated again.

d) Step c) is repeated so that the same clock values are used three times in total.



Baseband

e) The BT clock of the tester is initialized to a value randomly chosen such that the new clock range used does not overlap with the previous range in the initial conditions.

f) A new page procedure is performed and steps a) to d) are repeated.

g) The Bluetooth clock of the master is re-initialized to include clock wrap-around (227 – 1 to 0) during the test procedure.

h) The tester changes the set of used channels to all odd channels and repeats steps a) to f).

i) The Bluetooth clock of the master is re-initialized to include clock wrap-around (227 – 1 to 0) during the test procedure.

j) The tester changes the set of used channels to all even channels and repeats steps a) to f).

k) The Bluetooth clock of the master is re-initialized to include clock wrap-around (227 – 1 to 0) during the test procedure.

l) The tester changes the set of used channels to a random set of channels with at least 20 used and repeats steps a) to f).

m)The Bluetooth clock of the master is re-initialized to include clock wrap-around (227 – 1 to 0) during the test procedure.

n) The tester changes the set of used channels to a second random set of channels with at least 20 used and repeats steps a) to f).

o) The Bluetooth clock of the master is re-initialized to include clock wrap-around (227 – 1 to 0) during the test procedure.

p) The tester changes the set of used channels to a third random set of channels with at least 20 used and repeats steps a) to f).


• Expected OutcomePass verdict:

For each hop set, the tester has recorded at least one response on each of the 5200 clock values.

Fail verdict:

For at least one hop set, the tester has not recorded a response on at least one of the 5200 clock values.



Baseband



connection.b) If the IUT responds with an LMP command the tester uses its own

LMP response as a trigger packet.c) In steps c) and d) of the test procedure, the test is repeated with

the same BT clock to detect systematic errors.

4.2.1.4 TP/PHYS/FRE/BV-03-C (AFH Hop Seq after Master Slave Switch)

Verify that the IUT correctly disables AFH after a successful master slave switch. IUT is master and tester is slave.

Only for IUTs supporting AFH as master and master slave switch.


• Initial Conditiona) The IUT pages the tester to become the master.b) The tester and IUT are in normal connection state.c) Adaptive frequency hopping is enabled by the IUT using any

channel map.



Baseband

• Test Procedure

Figure 4.1: TP/PHYS/FRE/BV-03-C (AFH Hop Seq after Master Slave Switch)

a) The upper tester initiates a role switch.b) Upon successful completion of the role switch the upper tester

reads the channel map of the IUT using HCI.c) The lower tester sends 10 POLL packets and checks that the IUT

replies each packet correctly. In this way is tested that AFH mode is disabled.

Master

IUT

Slave

Lower Tester Upper Tester

LMP_switch_req

(switch_instant)

LMP_slot_offset

(slot_offset, BDADD)

NULL, POLL or ACL

ACL connection established, AFH enabled.

HCI_Switch_Role

(BDADDR, Role=Slave)

HCI_Read_AFH_Channel_Map

LMP_accepted

(Opcode LMP_switch_req)

FHS

Page response (ID)

Poll (BB)

Any type of BB packet

HCI Command Status event

(Status=0x00, Num_HCI_Comm,

Opcode=0x000B)

HCI Role Change event

(Status=0x00, BDADDR,

New_Role=Slave)

HCI Command Complete event

(Status, Connection_Handle, AFH_Mode,

AFH_channel_map)



Baseband



The AFH Mode parameter in the HCI Command Complete Event is set to 0x00 (AFH disabled).

Fail verdict:

The AFH Mode parameter in the HCI Command Complete Event is set to ‘01’H (AFH enabled).



connection.

4.2.1.5 BI test purposes


• To check the behavior of the IUT in response to invalid messages.

4.3 TX/RX TIMING


• To verify the TX and RX timing.

4.3.1 TX Timing


• To verify the TX timing.






Baseband

4.3.1.2 TP/PHYS/TRX/BV-01-C (master TX timing)

Verify that the IUT as master keeps an exact timing interval of M x 1250 µs dur-ing the existence of a piconet.


• Initial Conditiona) The IUT pages the tester to become the master of the piconet.b) IUT and Tester are in connection state.c) Tester uses LMP_quality_of service_req to negotiate the

maximum poll interval accepted by the master.

• Test Procedurea) The tester identifies the Position of Bit p0 in the Access code of a

Poll packet sent by the master and sets a timestamp. As clock reference the tester reference is used instead of the BT clock.

b) Timing drift is measured by setting a timestamp upon reception of a Poll packet, counting 5000 master slots and setting a second timestamp upon reception of the next Poll packet sent by the master.

c) Steps a) and b) are repeated 4 times. The overall drift is calculated as the average of the 5 measurement values.

• Test ConditionThis test case is performed at normal and extreme test conditions.


The measured timing drift tdrift of the IUT over 5000 slots is ≤ 125 µs.

Fail verdict:

The measured timing drift tdrift of the IUT over 5000 slots is > 125 µs.




Baseband

• NotesIn step c) of the initial conditions, the maximum accepted POLL interval is negotiated to allow the IUT to use a low power mode.




4.3.2 RX Timing


• To verify the RX timing.

• Verification of the timing and correctness of the guard time, synchronization sequence and trailer symbols that are transmitted in Enhanced Data Rate packets

4.3.2.1 EDR Guard Time


• Verification of the duration of the guard time between the basic rate header and the Enhanced Data Rate synchronization sequence




4.3.2.3 TP/PHYS/TRX/BV-03-C (master RX/TX timing)

Verify that the master's RX timing is based on its TX timing with a shift of 625 µs. Verify that the master uses a ±10 µs uncertainty window in the RX slot to allow for slave misalignments.




Baseband

• Initial Conditiona) The IUT pages the tester to become the master of the piconet.b) IUT and tester are in connection state.c) The tester uses LMP_quality_of service_req to negotiate the

minimum poll interval accepted by the master.

• Test Procedurea) The tester transmits a DM1 packet with a payload header

indicating zero length L2CAP continuation fragment in every slave TX slot following a master to slave transmission.

b) The tester's TX timing is varied from the nominal 625 µs slave RX/TX timing. Variation values are 0 and ±9.5 µs with equal probability.

c) The start of the IUT's TX burst is identified in the tester by setting a timestamp at bit position p0. The tester uses the burst received from the IUT as reference to calculate the variation for the next tester TX burst.

d) The number of ACKs returned by the IUT for at least 1000 transmitted tester burst is counted.

• Test ConditionThe test is performed at normal test conditions.

• Expected OutcomePass Verdict:

The measured ratio of returned ACKs to transmitted tester packets is ≥0.95.

Fail Verdict:

The measured ratio of returned ACKs to transmitted tester packets is <0.95.


• NotesThe test requirement of 95% returned ACKs is to take into account the imperfect radio path but not to allow any errors due to the size of the IUT’s RX detection window width. It also requires the tester’s TX jitter to be less than ±0.5 µs.



Baseband

4.3.2.4 TP/PHYS/TRX/BV-04-C (slave RX/ TX timing)

Verify that the slave's transmission starts N x 625 µs after receiving a burst.

Verify the slave’s RX detection window width and turn around timing jitter.


• Initial Conditiona) The tester pages the IUT to become the master of the piconet.b) IUT and Tester are in connection state.

• Test Procedurea) The tester transmits DM1 packets with a payload header indicating

zero length L2CAP continuation fragments in all master TX slots.b) The IUT’s estimate of the tester’s timing is varied by adding a

variation to the nominal 1250 µs tester TX timing. Variation values are 0 ±4 and ±8 µs in the following repeating sequence (referenced to the nominal Master transmit timing): 0, 0, +4, 0, +8, 0, +4, 0, 0, 0, 0, –4, 0, -8, 0, –4, 0, 0.

c) The start of the slave's TX burst is identified in the tester by setting a timestamp at bit position p0.

d) The slave's RX / TX timing is calculated by comparing the start of the slave's TX burst to the start of the tester's TX burst.

e) The number of bursts returned by the slave for at least 1000 transmitted master bursts is counted.

• Test ConditionThe test is performed at normal test conditions.



Baseband

• Expected OutcomePass Verdict:

The measured ratio of returned IUT TX bursts to transmitted tester bursts is ≥ 0.95.The measured time between the tester’s and IUT’s TX bursts is 625 ±3 µs for all bursts received by the tester.

Fail Verdict:

The measured ratio of returned IUT TX bursts to transmitted tester bursts is < 0.95.The measured time between the tester’s and IUT’s TX bursts is < 622 µs or > 628 µs for all bursts received by the tester.


• NotesThe test requirement of 95% returned burst is to take into account the imper-fect radio path but not to allow any errors due to the size of the IUT’s RX detection window width. The ±3 µs allowance is to cope with jitter and mea-surement uncertainties in both test equipment and IUT.

4.3.2.5 TP/PHYS/TRX/BV-05-C (Symbol rate)

Verify that the IUT uses the correct symbol rate of 1 Ms/s ±20 ppm.

• Reference[Vol. 2, Part A] Section 3.1 on page 34.

• Initial ConditionThe IUT is in test mode TX test.

• Test Procedurea) The IUT is polled by the tester. The IUT transmits packets with a

1010 pattern as payload. The longest supported packet type (DH1/3/5) with the longest supported payload length is used.

b) The tester records the time interval from the first bit of the preamble to the last bit of the payload. The number of bits received by the tester is divided by the time interval. The average value over 1000 packets is taken.



Baseband

• Test ConditionThe test is performed at normal and extreme temperature conditions.


The IUT symbol rate as measured by the tester is 1 Ms/s ±20 ppm.

Fail verdict:

The IUT symbol rate as measured by the tester is outside the range 1 Ms/s ±20 ppm.

• UncertaintiesThe test procedure can only be applied to IUT’s where access to BB signals is possible and with dedicated test equipment. Manufacturers may use their own test method to ensure compliance with the test case verdict. Because implementation of the test method is architecture dependent the test case must remain at Category C (or lower).

• NotesN/A.

4.3.3 Enhanced Data Rate Guard Time


• Verification of the synchronization sequence and trailer symbols that are transmitted in Enhanced Data Rate packets



• To test the behavior of the IUT in relation to syntactically and contextual cor-rect behavior of the test system

4.3.3.2 TP/PHYS/TRX/BV-06-E (EDR Guard Time)

Verification of the duration of the guard time between the basic rate packet header and the Enhanced Data Rate synchronization sequence.

• Reference[1] (Section 6.6.1)



Baseband

• Initial Conditiona) IUT is connected to tester via a 50 ohm connector or a temporary

50 ohm connector or if there is no antenna connector via a suitable coupling device.

b) IUT in test mode loop back or TX mode (or manual configuration if loopback is not available), whitening off.

c) Hopping off.d) IUT transmits at maximum output power back to the tester

• Test Procedurea) IUT transmits maximum length 2-DH1 or 2-EV3 packets

containing PRBS9.b) Tester demodulates a packet.c) Tester determines the start time of the first preamble bit p0 using

the measurement method defined in section 6.6 of the Radio Frequency Test Specification.

d) Tester determines the start time of the reference symbol of the Enhanced Data Rate portion of the packet from the Enhanced Data Rate synchronization sequence. The start time of the reference symbol is defined as 1 µs before the time when the symbol following the reference symbol becomes the dominant contributor to the transmitter’s instantaneous phase. The required method of determining the start time of the reference symbol is provided in the Notes section.

e) Tester determines the guard time, that is the time difference between the end of the last header symbol (defined as 126 microseconds after p0) and the start of the reference symbol of the Enhanced Data Rate portion, referenced to the output of the IUT transmitter.

f) Repeat steps b) to e) for 100 packetsg) If Enhanced Data Rate 3 Mbps payload data rate is supported by

the IUT, repeat steps b) to f) using maximum length 3-DH1 or 3-EV3 packets containing PRBS9 data.

• Test ConditionsThis test is carried out under normal test conditions.


The expected outcome of this test is:

95% of the measured guard times of the packets must fall within the range 4.75 - ε µs < guard time < 5.25 + ε µs, where ε = 0.15 µs is the allowed uncertainty due to the measurement process.

• Uncertainties



Baseband

• NotesThe tester should use all the symbols in the synchronization sequence to determine the timing of the reference symbol.Background of Method of MeasurementThe method of determining the start time of the reference symbol is based on the following observation.According to the Volume 2, Part A, Section 3.2.1.3 of the Bluetooth Core Specification, the lowpass equivalent information bearing signal v(t) is given by:

Symbol K becomes the dominant contributor to the transmitter phase when:

The instantaneous frequency of the signal will be:

It can be shown that:

At the point where symbol K becomes the dominant contributor then the instantaneous frequency will have an extreme value.The position of the start of the reference symbol, s0, is calculated using an averaging based on the position of all the frequency extremes in the sync word.

v t( ) Sk p t kT–( )k∑=

p t KT–( ) p t kT–( )k∑⎝ ⎠⎜ ⎟⎛ ⎞

> pt KT–

2p t KT–( ) v t( )>

–

f fc ddt----- -1 v t( )( )imag

v t( )( )real---------------------------⎝ ⎠⎛ ⎞tan+=

2p t KT–( ) vt= dfdt-----⇒ 0=



Baseband

Required Measurement MethodThe required method of measuring the start of the reference symbol and thus the guard time is defined below.Set the test equipment to vector analyzer mode and turn on FM demodula-tion with symbol rate 1 MHz. Trigger by any means to achieve reliable view-ing of the guard period. Look for and identify the synchronization sequence. The start of the reference symbol is defined to be one micro-second preced-ing the first frequency extreme of the synchronization sequence.For the 10 frequency extreme values in the sync word, the i’th frequency extreme value time is t(i) in µsec, this is the start of symbol i.

The start of symbol s0 is then

where symbol time is 1 µsec.Figure 4.2 is a plot of how the instantaneous frequency will look during the last bits of the header and the EDR sync word:

Figure 4.2: Instantaneous Frequency of Signal about the Guard Time

1 i 10≤ ≤

t0110------ t i( ) i symbol time×–( )

i 1=

10

∑=

6µs 6µs 5µs 1µs 10µs

6 Header-Bits

Guard-space

Reference-symbol

Syncword

The last 6Header-

Bits



Baseband




4.3.4 Synchronization Sequence and Trailer


• Verification of the synchronization sequence and trailer symbols that are transmitted in Enhanced Data Rate packets



• To test the behavior of the IUT in relation to syntactically and contextual cor-rect behavior of the test system

4.3.4.2 TP/PHYS/TRX/BV-07-E (EDR Synchronization Sequence and Trailer)

Verification of the synchronization sequence and trailer symbols that are trans-mitted in Enhanced Data Rate packets.

• Reference[1] (Section 6.6.1)



Baseband

• Initial Conditiona) IUT is connected to tester via a 50 ohm connector or a temporary

50 ohm connector or if there is no antenna connector via a suitable coupling device.

b) IUT in test mode loop back or TX mode (or manual configuration if loopback is not available), whitening off.

c) Hopping off.d) IUT transmits at maximum output power back to the tester

• Test Procedurea) IUT transmits maximum length 2-DH1 or 2-EV3 packets

containing PRBS9 data.b) Tester demodulates a packet, including the synchronization

sequence and the two trailer symbols. c) Tester compares the demodulated bits corresponding to the

synchronization sequence with the correct bit sequence defined in [1] and compares the demodulated trailer bits with zeros.

d) Repeat step b) to c) for 50 packets.e) If Enhanced Data Rate 3 Mbps payload data rate is supported by

the IUT, repeat steps b) to d) with maximum length 3-DH1 or 3-EV3 packets containing PRBS9 data.

• Test ConditionThis test is carried out under normal test conditions.

• Expected OutcomeFor each modulation, the expected outcome over all 50 tested packets is zero bit errors in the synchronization sequences and no more than one bit error in all the trailer symbols.

• Uncertainties

• Notes






Baseband

4.4 CODING/DECODING


• To verify that correct coding and decoding is used.

4.4.1 Packet Types


• To verify that the different packet types are correctly coded and decoded.

Because it can be assumed that coding and decoding is independent of the role of the IUT this TP are only specified for IUT configured as slave in Test Mode (Loopback). Besides, tests relating to coding and decoding of packets in case of IUT configured as master is implicitly covered by other TP.




4.4.1.2 TP/PROT/COD/BV-01-C (HV1 packet type)

Verify that the IUT, upon reception of a HV1 packet, decodes and encodes the packet correctly.

Only for IUTs supporting the HV1 packet type.

• Reference[Vol. 2, Part B] Section 6.5.2.1 on page 109.

• Initial ConditionTester:

Configured as Master in state CONNECTION.

IUT:Configured as Slave in state CONNECTION with Test Mode (Loopback, Synchronous packets) active.

• Test Procedure



Baseband

Figure 4.3: TP/PROT/COD/BV-01-C (HV1 packet type)

The tester transmits a HV1 packet.HV1Access code:

Preamble: 1010 or 0101 sequence, depending on whether the LSB of the following sync word is 1 or 0, respectively.Sync word: derived from the 24 bit address (LAP) of the master (CAC).Trailer: 1010 or 0101 sequence, depending on whether the MSB of the sync word is 1 or 0, respectively.

Packet Header:

LT_ADDR: Logical Transport Address of the slave.TYPE: '0101'B.FLOW: Any value.ARQN: Any value.SEQN: Any value.HEC: Generated by the polynom '647'O in respect to the UAP of the master.Payload: 10 Bytes PRBS.

The tester verifies that the IUT transmits the packet correctly coded back to the tester.

Slave

IUT

Master


Tester: configured as Master in state CONNECTION.

IUT: configured as Slave in state CONNECTION with Test Mode

(normal Loopback, Synchronous packets) active.

HV1

HV1

(Access Code, LT_ADDR, TYPE,

ARQN, SEQN, FLOW, HEC, Payload)





Baseband

• Test ConditionN/A.


The IUT transmits the packet correctly coded back to the tester.

Fail verdict:

The IUT does not transmit the packet correctly coded back to the tester.


• NotesThe payload is protected by FEC 1/3 but is not CRC coded.










Baseband

• Test Procedure




Packet Header:

LT_ADDR: Logical Transport Address of the slave.TYPE: '0110'B.FLOW: Any value.ARQN: Any value.SEQN: Any value.HEC: Generated by the polynom '647'O in respect to the UAP of the master.Payload: 20 Bytes PRBS.


Slave

IUT

Master





HV2



HV2





Baseband




Fail verdict:



• NotesThe payload is protected by FEC 2/3 but is not CRC coded.








• Test Procedure



Baseband




Packet Header:

LT_ADDR: Logical Transport Address of the slaveTYPE: '0111'B.FLOW: Any value.ARQN: Any value.SEQN: Any value.HEC: Generated by the polynom '647'O in respect to the UAP of the master.Payload: 30 Bytes PRBS.


• Test Condition

Slave

IUT

Master




(normal Loopback, Snychronous packets) active.

HV3



HV3





Baseband

N/A.



Fail verdict:



• NotesThe payload is not protected by FEC and is not CRC coded.

4.4.1.5 TP/PROT/COD/BV-04-C (DV packet type)

Verify that the IUT, upon reception of a DV packet, decodes and encodes the packet correctly.

Only for IUTs supporting the DV packet type.





• Test Procedure



Baseband

Figure 4.6: TP/PROT/COD/BV-04-C (DV packet type)

The tester transmits a DV packet.DVAccess code:


Packet Header:

LT_ADDR: Logical Transport Address of the slaveTYPE: '1000'B.FLOW: '1'B.ARQN: '1'B.SEQN: Depends on the former transmission of the tester.HEC: Generated by the polynom '647'O in respect to the UAP of the master.Voice Field: 10 Bytes PRBS.

Slave

IUT

Master





DV


ARQN, SEQN, FLOW, HEC,

Voice Field, LLID, FLOW, LENGTH,

Data payload body)

DV


ARQN, SEQN, FLOW, HEC,

Voice Field, LLID, FLOW, LENGTH,

Data payload body)



Baseband

Data payload header:

LLID: '10'B.FLOW: '1'B.LENGTH: '01001'B = '9'D.Data payload body: 9 Bytes PRBS plus 16 bit CRC.





Fail verdict:



• NotesThe voice payload is not protected by FEC. The data payload is protected with FEC 2/3 and is CRC coded.This test is only mandatory for devices that support DV packets.

4.4.1.6 TP/PROT/COD/BV-05-C (DH1 packet type)

Verify that the IUT, upon reception of a DH1 packet, decodes and encodes the packet correctly.

Only for IUTs supporting the DH1 packet type.


• Initial Condition



Baseband

Tester:Configured as Master in state CONNECTION.

IUT:Configured as Slave in state CONNECTION with Test Mode (Loopback, ACL packets) active.

• Test Procedure

Figure 4.7: TP/PROT/COD/BV-05-C (DH1 packet type)

The tester transmits a DH1 packet.DH1Access code:


Slave

IUT

Master



IUT: configured as Slave in state CONNECTION with Test Mode (normal Loopback, ACL packets) active.

DH1


ARQN, SEQN, FLOW, HEC, LLID,

LENGTH, Payload body)

DH1






Baseband

Packet Header:

LT_ADDR: Logical Transport Address of the slaveTYPE: '0100'B.FLOW: '1'B.ARQN: '1'B.SEQN: depends on the former transmission of the tester.HEC: Generated by the polynom '647'O in respect to the UAP of the master.

Payload header:

LLID: '10'B.FLOW: '1'B.LENGTH: '11011'B = '27'D.Payload body: 27 Bytes PRBS plus 16 bit CRC.





Fail verdict:



• NotesThe payload is not protected by FEC but is CRC coded.



Baseband

4.4.1.7 TP/PROT/COD/BV-06-C (DM3 packet type)

Verify that the IUT, upon reception of a DM3 packet, decodes and encodes the packet correctly.

Only for IUTs supporting the DM3 packet type.





• Test Procedure

Figure 4.8: TP/PROT/COD/BV-06-C (DM3 packet type)

The tester transmits a DM3 packet.DM3

Slave

IUT

Master




DM3

Access Code, LT_ADDR, TYPE,


FLOW, LENGTH, UNDEFINED,

Payload body)

DM3

Access Code, LT_ADDR, TYPE,



Payload body)



Baseband

Access code:

Preamble: 1010 or 0101 sequence, depending on whether the LSB of the following sync word is 1 or 0, respectively.Sync word: Derived from the 24 bit address (LAP) of the master (CAC).Trailer: 1010 or 0101 sequence, depending on whether the MSB of the sync word is 1 or 0, respectively.

Packet Header:

LT_ADDR: Logical Transport Address of the IUT.TYPE: '1010'B.FLOW: '1'B.ARQN: '1'B.SEQN: Depends on the former transmission of the tester.HEC: Generated by the polynom '647'O in respect to the UAP of the master.

Payload header:

LLID: '10'B.FLOW: '1'B.LENGTH: '001111001'B = '121'D.UNDEFINED: '0000'B.Payload body: 121 Bytes PRBS plus 16 bit CRC.





Fail verdict:




Baseband


• NotesThe payload is protected by FEC 2/3 and is CRC coded.This packet covers three time slots.This test is only mandatory for devices that support DM3 packets.








• Test Procedure



Baseband


The tester transmits a DH3 packet.DH3Access code:


Packet Header:

LT_ADDR: Logical Transport Address of the slave.TYPE: '1011'B.FLOW: '1'B.ARQN: '1'B.SEQN: Depends on the former transmission of the tester.HEC: Generated by the polynom '647'O in respect to the UAP of the master.



Slave

IUT

Master


DH3




Payload body)

DH3




Payload body)



Baseband

Payload header:

LLID: '10'B.FLOW: '1'B.LENGTH: '010110111'B = '183'D.UNDEFINED: '0000'B = any value.Payload body: 183 Bytes PRBS plus 16 bit CRC.





Fail verdict:



• NotesThe payload is not protected by FEC but is CRC coded.This packet covers three timeslots.This test is only mandatory for devices that support DH3 packets.

4.4.1.9 TP/PROT/COD/BV-08-C (DM5 packet type)

Verify that the IUT, upon reception of a DM5 packet, decodes and encodes the packet correctly.

Only for IUTs supporting the DM5 packet type.




Baseband




• Test Procedure

Figure 4.10: TP/PROT/COD/BV-08-C (DM5 packet type)

The tester transmits a DM5 packet.DM5Access code:




Slave

IUT

Master


DM5




Payload body)

DM5




Payload body)



Baseband

Packet Header:


Payload header:






Fail verdict:



• NotesThe payload is protected by FEC 2/3 and is CRC coded.The packet used in this Test Case covers five timeslots.This test is only mandatory for devices that support DM5 packets.



Baseband








• Test Procedure


The tester transmits a DH5 packet.DH5



Slave

IUT

Master


DH5

DH5




Payload body)




Payload body)



Baseband

Access code:


Packet Header:


Payload header:



• Test Condition

• N/A.



Fail verdict:




Baseband


• NotesThe payload is not protected by FEC but is CRC coded.This packet in this Test Case covers five timeslots.This test is only mandatory for devices that support DH5 packets.

4.4.1.11 TP/PROT/COD/BV-10-C (AUX1 packet type)

Verify that the IUT, upon reception of an AUX1 packet, decodes and encodes the packet correctly.

Only for IUTs supporting the AUX1 packet type.





• Test Procedure



Baseband

Figure 4.12: TP/PROT/COD/BV-10-C (AUX1 packet type)

The tester transmits an AUX1 packet.AUX1Access code:


Packet Header:




Slave

IUT

Master


AUX1




Payload body)

AUX1




Payload body)



Baseband

Payload header:

LLID: '00'B.FLOW: '1'B.LENGTH: '11101'B = '29'D.Payload body: 29 Bytes PRBS.





Fail verdict:



• NotesThis test is only mandatory for devices that support AUX1 packets.

4.4.1.12 TP/PROT/COD/BV-11-C (Erroneous slave address)

Verify that the IUT configured as slave upon reception of a packet containing a logical transport address not belonging to the slave does not transmit any packet.





Baseband

Tester:Configured as Master in state CONNECTION (active mode ACL link).

IUT:Configured as Slave in state CONNECTION (active mode, ACL link).

• Test Procedure

Figure 4.13: TP/PROT/COD/BV-11-C (Erroneous slave address)

The tester transmits a POLL packet with an logical transport address not belonging to the Slave.POLLAccess code:



IUT: configured as Slave in state CONNECTION (active mode, ACL packets.)

Slave

IUT

Master


POLL

(Access Code, LT_ADDR, TYPE, FLOW,

ARQN, SEQN, HEC)

LT_ADDR not belonging

to the slave.

IUT does not respond

in the following slave

to master slot.

Does nothing



Baseband

Packet Header:

LT_ADDR: Logical Transport Address not belonging to the slave.TYPE: '0001'B.FLOW: '1'B.ARQN: '1'B.SEQN: Depends on the former transmission of the tester.HEC: Generated by the polynom '647'O in respect to the UAP of the master.

The tester verifies that the IUT does not transmit any packet back to the tester.The procedure is repeated to test all LT_ADDR not belonging to the IUT (six addresses). For each address one POLL packet is transmitted to make sure that the IUT does not respond to the POLL packet.



The IUT does not transmit any packet in the slave to master slot.

Fail verdict:

The IUT responds to a POLL packet.


• NotesN/A.

4.4.1.13 TP/PROT/COD/BV-17-C (EV3 packet type)

Verify that the IUT, upon reception of an EV3 packet, decodes and encodes the packet correctly.

Only for IUTs supporting the EV3 packet type.



Baseband




IUT:Configured as Slave in state CONNCTION with Test Mode (Loopback, Synchronous packets) active.

• Test ProcedureThe tester transmits an EV3 packet.EV3Access code:


Packet Header:

LT_ADDR: Logical Transport Address of the slave.TYPE: ‘0111’B.FLOW: ‘1’B.ARQN: ‘1’B.SEQN: Depends on the former transmission of the tester.HEC: Generated by the polynomial ‘647’O in respect to the UAP of the master.

Payload header:

N/A.

Payload:

30 bytes PRBS plus 16 bit CRC.



Baseband





Fail verdict:


• UncertaintiesNone.

• NotesThe payload is not protected by FEC but is CRC coded.There is no payload header.This test is only mandatory for devices that support eSCO.

4.4.1.14 TP/PROT/COD/BV18-C (EV4 packet type)









Baseband

• Test ProcedureThe tester transmits an EV4 packet.EV4Access code:


Packet Header:

LT_ADDR: Logical Transport Address of the slave.TYPE: ‘1100’B.FLOW: ‘1’B.ARQN: ‘1’B.SEQN: Depends on the former transmission of the tester.HEC: Generated by the polynomial ‘647’O in respect to the UAP of the master.

Payload header:

N/A.

Payload:








Baseband

Fail verdict:



• NotesThe payload is protected by FEC 2/3 and is CRC coded.There is no payload header.The packet covers three time slots.This test is only mandatory for devices that support EV4 packets.

4.4.1.15 TP/PROT/COD/BV19-C (EV5 packet type)



• Reference[Vol. 2, Part B] Section 6.5.3.3 on page 110




• Test ProcedureThe tester transmits an EV5 packet.EV5



Baseband

Access code:


Packet Header:

LT_ADDR: Logical Transport Address of the slave.TYPE: ‘1101’B.FLOW: ‘1’B.ARQN: ‘1’B.SEQN: depends on the former transmission of the tester.HEC: Generated by the polynomial ‘647’O in respect to the UAP of the master.

Payload header:

N/A.

Payload:






Fail verdict:




Baseband


• NotesThe payload is not protected by FEC 2/3 but is CRC coded.There is no payload header.The packet covers three time slots.This test is only mandatory for devices that support EV5 packets.

4.4.1.16 TP/PROT/COD/BV-20-C (2-EV3 packet type)

Verify that the IUT, upon reception of a 2-EV3 packet, decodes and encodes the packet correctly.

Only for IUTs supporting the 2-EV3 packet type.

• Reference[1] (Section 6.5.3.4)

• Initial ConditionTester: configured as Master in state CONNECTION.

IUT: configured as Slave in state CONNECTION and with Test Mode (Loop-back, eSCO packets) active.

Whitening on

• Test Procedure

Figure 4.14: TP/PROT/COD/BV-20-C (2-EV3 packet type)

The tester transmits a 2-EV3 packet.

Lower Tester IUT Upper Tester

Tester: Configured as a master in state CONNECTIONIUT: Configured as a slave in state CONNECTION with Test Mode (normal Loopback, eSCO packets) active

Master Slave

Access code, LT_ADDR, TYPE: ARQN, SEQN, FLOW, HEC, Payload

2-EV3

2-EV3




Baseband

Access code

Preamble: ‘1010’B or ‘0101’B sequence, depending on whether the LSB of the following sync word is 1 or 0, respectively.

sync word: derived from the 24 bit address (LAP) of the master (CAC).

trailer: ‘1010’B or ‘0101’B sequence, depending on whether the MSB of the sync word is 1 or 0, respectively.

Packet Header

LT_ADDR:Logical Transport Address.

TYPE:'0110'B

FLOW:'1'B

ARQN:'1'B

SEQN:depends on the former transmission of the tester

HEC:Generated by the polynom '647'O in respect to the UAPof the master.

Guard time:As defined in [1].

Sync sequence:As defined in [1]

Payload header:N/A

Payload body: 60 Bytes PRBS9 plus 16 bit CRC.

Trailer: As defined in [1].


• Test Condition This test is carried out under normal test conditions.




Baseband

Pass verdict:The IUT transmits the 2-EV3 packet correctly coded back to the tester.Fail verdict:The IUT does not transmit the packet correctly coded back to the tester.

• UncertaintiesN/A






• Initial ConditionTester: configured as Master in state CONNECTION.

IUT: configured as Slave in state CONNECTION and with Test Mode (Loop-back, eSCO packets) active.

Whitening on

• Test Procedure




Master Slave


2-EV5

2-EV5Access code, LT_ADDR, TYPE: ARQN, SEQN, FLOW, HEC, Payload



Baseband

The tester transmits a 2-EV5 packet.Access code

Preamble:‘1010’B or ‘0101’B sequence, depending on whether the LSB of the following sync word is 1 or 0, respectively.

sync word:derived from the 24 bit address (LAP) of the master (CAC).

trailer:‘1010’B or ‘0101’B sequence, depending on whether the MSB of the sync word is 1 or 0, respectively.

Packet Header


TYPE:'1100'B

FLOW:'1'B

ARQN:'1'B


HEC:Generated by the polynom '647'O in respect to the UAPof the mas-ter.

Guard time:As defined in [1].

Sync sequence:As defined in [1]

Payload headerN/A

Payload body: 360 Bytes PRBS9 plus 16 bit CRC.






Baseband

• Expected OutcomePass verdict:The IUT transmits the packet correctly coded back to the tester.Fail verdict:The IUT does not transmit the packet correctly coded back to the tester.







• Initial ConditionTester:configured as Master in state CONNECTION.

IUT:configured as Slave in state CONNECTION and with Test Mode (Loop-back, eSCO packets) active.

Whitening on

• Test Procedure




Master Slave


3-EV3

3-EV3




Baseband





Packet Header


TYPE:'0111'B

FLOW:'1'B

ARQN:'1'B



Guard time:As defined in [1]. Sync sequence:As defined in [1] Payload headerN/A

Payload body:90 Bytes PRBS9 plus 16 bit CRC.






Baseband








• Initial ConditionTester:configured as Master in state CONNECTION.

IUT:configured as Slave in state CONNECTION and with Test Mode (Loop-back, eSCO packets) active.

Whitening on

• Test Procedure




Master Slave


3-EV5

3-EV5




Baseband





Packet Header


TYPE:'1101'B

FLOW:'1'B

ARQN:'1'B



Guard time:As defined in [1]. Sync sequence:As defined in [1] Payload headerN/A







Baseband




4.4.1.20 TP/PROT/COD/BV-24-C (2-DH1 packet type)

Verify that the IUT, upon reception of a 2-DH1 packet, decodes and encodes the packet correctly.

Only for IUTs supporting the 2-DH1 packet type.


• Initial ConditionTester:configured as Master in state CONNECTION with ptt = 1.

IUT:configured as Slave in state CONNECTION with ptt = 1 and with Test Mode (Loopback, ACL packets) active.

Whitening on

• Test Procedure

Figure 4.18: TP/PROT/COD/BV-24-C (2-DH1 packet type)


Tester: Configured as a master in state CONNECTIONIUT: Configured as a slave in state CONNECTION with Test Mode (normal Loopback, ACL packets) active

Master Slave


2-DH1

2-DH1




Baseband

The tester transmits a 2-DH1 packet.Access code



trailer:‘1010’B or ‘0101’B sequence, depending on whether the MSB of the sync word is 1 or 0, respectively.Packet Header


TYPE:'0100'B

FLOW:'1'B

ARQN:'1'B



Guard time:As defined in [1]. Sync sequence:As defined in [1] Payload header

L_CH:'10'B

FLOW:'1'B

LENGTH:'0000110110'B = '54'D




Baseband













Whitening on



Baseband

• Test Procedure






Packet Header


TYPE:'1010'B

FLOW:'1'B

ARQN:'1'B




Master Slave


2-DH3

2-DH3




Baseband



L_CH:'10'B

FLOW:'1'B

LENGTH:'0101101111'B = '367'D













Baseband




Whitening on

• Test Procedure








Master Slave


2-DH5

2-DH5




Baseband

Packet Header


TYPE:'1110'B

FLOW:'1'B

ARQN:'1'B




L_CH:'10'B

FLOW:'1'B

LENGTH:' 1010100111'B = '679'D







Baseband










Whitening on



Baseband

• Test Procedure








Master Slave


3-DH1

3-DH1




Baseband

Packet Header


TYPE:'1000'B

FLOW:'1'B

ARQN:'1'B




L_CH:'10'B

FLOW:'1'B

LENGTH:' 0001010011'B = '83’D







Baseband










Whitening on



Baseband

• Test Procedure








Master Slave


3-DH3

3-DH3




Baseband

Packet Header


TYPE:'1011'B

FLOW:'1'B

ARQN:'1'B




L_CH:'10'BFLOW:'1'BLENGTH:' 1000101000'B = '552’D








Baseband









Whitening on

• Test Procedure


The tester transmits a 3-DH5 packet.



Master Slave


3-DH5

3-DH5




Baseband

Access code




Packet Header


TYPE:'1111'B

FLOW:'1'B

ARQN:'1'B



Guard time:As defined in [1]. Sync sequence:As defined in [1][1] Payload header

L_CH:'10'B

FLOW:'1'B

LENGTH:' 1111111101'B = '1021’D




Baseband










4.4.2 FEC (R=1/3)


• To verify that the Forward Error Correction, Rate = 1/3, is correctly imple-mented.




4.4.2.2 TP/PROT/COD/BV-12-C (Correctable packet header)

Verify that the IUT, upon reception of a DM1 packet with a correctable error in the packet header, decodes and encodes the packet correctly.



Baseband





• Test Procedure

Figure 4.24: TP/PROT/COD/BV-12-C (Correctable packet header)

The tester transmits a DM1 packet with a correctable error in the packet header.DM1Access code:




Slave

IUT

Master


DM1


FLOW, ARQN, SEQN, HEC)

DM1



With correctable errors in the

packet header.

ARQN bit set to ACK.



Baseband

Packet Header:


Payload header:

LLID: '10'B indicating no fragmentation.FLOW: '1'B.LENGTH: '00000'B = '0'D.Payload body: 0 Bytes.

The packet header is FEC 1/3 coded. After the coding procedure has suc-cessfully performed errors have to be inserted. In packets of three bits one bit will be changed.The tester verifies that the IUT transmits the same packet back to the tester with the ARQN bit set to ACK.This test procedure is repeated 100 times. The inserted correctable errors must be distributed in all possible bit error positions in the 100 packets, with only one error per packet.



The IUT transmits the same packet with the ARQN bit set to ACK for at least or equal than 95% of the repetitions.

Fail verdict:

The IUT transmits a NULL packet with the ARQN bit set to NAK (or sends nothing) for more than 5% of the repetitions.




Baseband

• NotesN/A.

4.4.2.3 TP/PROT/COD/BV-14-C (Correctable error HV1 payload)

Verify that the IUT, upon reception of a HV1 packet with a correctable error in the payload, decodes and encodes the packet correctly.





• Test Procedure

Figure 4.25: TP/PROT/COD/BV-14-C (Correctable error HV1 payload)

Slave

IUT

Master




(normal Loopback, Synchronous packets) active.)

HV1

(Access Code, Header, Voice field)

HV1


With correctable errors

in the voice payload.




Baseband

The tester transmits a HV1 packet with a correctable error in the payload.HV1Access code:


Packet Header:

LT_ADDR: Logical Transport Address of the slave.TYPE: '0101'B.FLOW: '1'B.ARQN: '1'B.SEQN: Any value because data without CRC information is used.HEC: Generated by the polynom '647'O in respect to the UAP of the master.Payload body: 10 Byte user payload.

The payload body is FEC 1/3 coded. After the coding procedure has been successfully performed errors have to be inserted. In blocks of three bits one bit will be changed.The tester verifies that the IUT sends the packet correctly coded back to the tester with the ARQN bit set to ACK.This test procedure is repeated 240 times to cover all bit positions after FEC is applied. The inserted correctable errors must be distributed in all 240 pos-sible bit positions in the 240 packets, with only one error per packet.






Baseband

Fail verdict:

The IUT transmits a NULL packet with the ARQN bit set to NAK (or send nothing) for more than 5% of the repetitions.


• NotesN/A.




4.4.3 FEC (R=2/3)


• To verify that the Forward Error Correction, Rate = 2/3, is correctly imple-mented.






Baseband

4.4.3.2 TP/PROT/COD/BV-16-C (Correctable error DM1 payload)

Verify that the IUT, upon reception of a DM1 packet with a correctable error in the payload, decodes and encodes the packet correctly.





• Test Procedure

Figure 4.26: TP/PROT/COD/BV-16-C (Correctable error DM1 payload)

Slave

IUT

Master




DM1


ARQN, SEQN, HEC, LLID, FLOW,


DM1


ARQN, SEQN, HEC, LLID, FLOW,


With correctable errors

in the payload.




Baseband

The tester transmits a DM1 packet with a correctable error in the payload.DM1Access code:


Packet Header:


Payload header:

LLID: '10'B indicating no fragmentation.FLOW: '1'B.LENGTH: '01001'B = '9'D.Payload body: 9 Bytes PRBS.

This corresponds to 100 bits payload contents (1 Byte packet header 9 Bytes payload body and 2 Bytes CRC corresponds to 96 bits plus 4 zero bits for FEC coding) before FEC 2/3 coding. After FEC 2/3 coding the payload consists of 150 bits. In blocks of 15 bits one bit will be changed.The tester verifies that the IUT transmits the packet correctly coded back to the tester with the ARQN bit set to ACK.This test procedure is repeated 150 times to cover all bits positions after FEC is applied. The inserted correctable errors must be distributed in all 150 possible bit positions in the 150 packets, with only one error per packet.




Baseband



Fail verdict:

The IUT transmits a NULL packet with the ARQN bit set to NAK (or send nothing) for more than 5% of the repetitions.


• NotesN/A.




4.5 ARQ


• To verify that correct Automatic Repeat Request scheme is used.

4.5.1 ARQ Procedures - Master


• To verify that the ARQ scheme used by the Master is correct.






Baseband

4.5.1.2 TP/PROT/ARQ/BV-01-C (Explicit NAK)

Verify that the IUT configured as Master, upon reception of a packet with its ARQN bit set to NAK (explicit NAK), retransmits the packet again.

• Reference[Vol. 2, Part B] Section 6.4.4 on page 104.[Vol. 2, Part B] Section 7.6 on page 124.[Vol. 2, Part B] Section 7.6.2 on page 127.


Configured as Slave in state CONNECTION (active mode, ACL link).

IUT:Configured as Master in state CONNECTION (active mode, ACL link).



Baseband

• Test Procedure

Figure 4.27: TP/PROT/ARQ/BV-01-C (Explicit NAK)

The tester transmits an LMP_features_req message.The tester verifies that the IUT transmits a DM1 packet containing LMP_features_res.The tester acknowledges the packet with a NULL packet with ARQN bit set to NAK.NULLAccess code:


Master

IUT

Slave


DM1

(LMP_features_res (features))

NULL

DM1


NULL

(LT_ADDR, TYPE, FLOW, ARQN,

SEQN, HEC)


SEQN, HEC)

DM1

(LMP_features_req (features))

ARQN bit set to NAK.


Tester: configured as Slave in state CONNECTION (active mode, ACL link.)

IUT: configured as Master in state CONNECTION (active mode, ACL link.)



Baseband

Packet Header:


The tester verifies that the IUT retransmits the packet.



The IUT retransmits the packet after receiving the NULL packet with the ARQN bit set to NAK.

Fail verdict:

The IUT does not retransmit the packet.


• NotesN/A.

4.5.1.3 TP/PROT/ARQ/BV-02-C (Implicit NAK)

Verify that the IUT configured as Master, when the acknowledgement is left out (implicit NAK), retransmits the packet again.

• Reference[Vol. 2, Part B] Section 7.6 on page 124.[Vol. 2, Part B] Section 6.4.4 on page 104.



Baseband




• Test Procedure

Figure 4.28: TP/PROT/ARQ/BV-02-C (Implicit NAK)

The tester transmits an LMP_features_req message.The tester verifies that the IUT transmits a DM1 packet containing LMP_features_res.The tester does not send any packet.The tester verifies that the IUT retransmits the packet.

Master

IUT

Slave


Tester: configuredas Slave in state CONNECTION (active mode, ACL link.)


DM1


DM1

Does Nothing

DM1

NULL


SEQN, HEC)



End of Test Purpose.




Baseband



The IUT retransmits the packet after not receiving any response from the tester.

Fail verdict:



• NotesN/A.

4.5.1.4 TP/PROT/ARQ/BV-03-C (Uncorrectable packet header)

Verify that the IUT configured as Master, upon reception of a packet with uncor-rectable errors in the packet header, transmits the next packet addressing the same slave with the ARQN bit set to NAK.

• Reference[Vol. 2, Part B] Section 6.4.4 on page 104.[Vol. 2, Part B] Section 7.6 on page 124.






Baseband

• Test Procedure

Figure 4.29: TP/PROT/ARQ/BV-03-C (Uncorrectable packet header)

The tester transmits a DM1 packet containing the LMP_features_req mes-sage with an uncorrectable error in the packet header.DM1Access code:


Master

IUT

Slave




any_ACL_packet

(LT_ADDR, TYPE, ARQN, SEQN,

FLOW, HEC)

DM1


any_ACL_packet

DM1 packet with uncorrectable

errors in the packet header.




Baseband

Packet Header:

LT_ADDR: Logical Transport Address of the slave.TYPE: '0011'B.FLOW: '1'B.ARQN: '1'B.SEQN: Depends on the previous transmission from the tester and ACK or NACK from the IUT.HEC: Generated by the polynom '647'O in respect to the UAP of the master.

The packet header is FEC 1/3 coded. After the coding procedure has suc-cessfully performed errors have to be inserted. The maximum number of inserted errors depends on the Hamming distance provided by the HEC.

Payload header:

LLID: '11'B indicating a LMP message.FLOW: '1'B.LENGTH: '01001'B = '9'D.Payload body: 9 Bytes.

1. Byte = '4F'H Transaction ID and OpCode.2. to 9. Byte = '00'H.

The tester verifies that the IUT transmits an ACL packet with the ARQN bit set to NAK in the next master to slavetransmission.This test procedure is repeated 100 times. The inserted uncorrectable errors must be statistically distributed.




Baseband


For at least 99% of the repetitions the IUT transmits a packet with the ARQN bit set to NAK in the next transmission to the slave.

Fail verdict:

For more than 1% of the repetitions the IUT transmits a packet with the ARQN bit set to ACK in the next transmission to the slave.


• NotesThis test should lead to the tester transmitting 100 consecutive packets with uncorrectable errors.

4.5.1.5 TP/PROT/ARQ/BV-04-C (Uncorrectable payload)

Verify that the IUT configured as Master, upon reception of a DM1 packet with uncorrectable errors in the payload transmits a packet with the ARQN bit set to NAK.







Baseband

• Test Procedure

Figure 4.30: TP/PROT/ARQ/BV-04-C (Uncorrectable payload)

The tester transmits a DM1 packet containing the LMP_features_req mes-sage with an uncorrectable error in the payload.DM1Access code:


Master

IUT

Slave



IUT: configured as Master in State CONNECTION (active mode, ACL link.)

any packet


FLOW, HEC)

DM1


any packet

DM1


DM1



FLOW, HEC)

DM1 packet with uncorrectable

errors in the payload.

ARQN bit set to NAK End of

Test Purpose.

Several packets might be

exchanged before

LMP_features_res

is transmitted.



Baseband

Packet Header:


Payload header:

LLID: '11'B indicating a LMP message.FLOW: '1'B.LENGTH: '01001'B = '9'D.Payload body: 9 Bytes.

1. Byte = ‘4F’H Transaction ID and OpCode.2. to 9. Byte = '00'H.

This corresponds to 90 bits payload contents (1 Byte packet header 8 Bytes payload body and 2 Bytes CRC corresponds to 88 bits plus 2 zero bits for FEC coding) before FEC 2/3 coding. After FEC 2/3 coding the payload con-sists of 135 bits. The maximum number of inserted errors depends on the Hamming distance provided by the CRC.Then the tester verifies that the IUT transmits any packet with the ARQN bit set to NAK.This test procedure is repeated 100 times. The inserted uncorrectable errors must be statistically distributed.




Baseband


For at least 99% of the repetitions the IUT transmits a packet with the ARQN bit set to NAK in the next transmission to the slave.

Fail verdict:

For more than 1% of the repetitions the IUT transmits a packet with the ARQN bit set to ACK in the next transmission to the slave.


• NotesN/A.

4.5.1.6 TP/PROT/ARQ/BV-05-C (SEQN)

Verify that the IUT configured as Master, respects SEQN values in the transmit case.




IUT:Configured as Master in state CONNECTION (active mode, ACL link).The tester does not support any feature.



Baseband

• Test Procedure

Figure 4.31: TP/PROT/ARQ/BV-05-C (SEQN)

The tester transmits LMP_features_req. The tester verifies that the IUT transmits a DM1 packet containing LMP_features_ res. The tester has to store the SEQN value (first SEQN value) contained in the packet header.The tester acknowledges the packet with a NULL packet with the ARQN bit set to NAK.

,

Master

IUT

Slave




DM1

(LMP_version_req (Vers, Comp, SubVers))

(LMP_version_res (Vers, Comp, SubVers))

DM1

(LMP_features_req

(features=0x0000000000000000))

DM1


DM1


SEQN, HEC)

NULL


DM1

(LMP_features_req

(features=0x0000000000000000))

DM1


DM1


LMP_version_req together

with no features in the tester

minimalizes the risk the IUT

initiates LMP signaling, still the

IUT might transmit something

else before LMP_features_res.

ARQ bit set to ACK.

Different SEQN as in previous

CRC transmission.

End of test purpose.

The IUT might transmit other

LMP signaling before

LMP_features_res.



Baseband

NULLAccess code:


Packet Header:


The tester verifies that the IUT retransmits the DM1 packet containing LMP_features_res with the same SEQN value (second SEQN value) as in the previous transmission. The tester has to store the SEQN value con-tained in the packet header.The tester transmits a DM1 packet containing the LMP_features_req again with the ARQN bit set to ACK.The tester verifies that the IUT transmits a DM1 packet with a different SEQN value (third SEQN value) compared to the previous transmissions.



The second SEQN value is the same as the first SEQN value The third SEQN value is not the same as the second SEQN value.

Fail verdict:

The second SEQN value is not the same as the first SEQN value The third SEQN value is the same as the second SEQN value.



Baseband

• UncertaintiesThe IUT might transmit unsolicited LMP signaling changing the intended test procedure. This risk is minimized by having the tester transmit LMP_version_req immediately after connection establishment and always indicate no feature is supported.

• NotesN/A.

4.5.1.7 TP/PROT/ARQ/BV-06-C (FLOW control)

Verify that the IUT configured as Master, stops transmitting upon receiving STOP indication, switch to default packet types and resumes to transmit when GO indication is received.







Baseband

• Test Procedure

Figure 4.32: TP/PROT/ARQ/BV-06-C (FLOW control)

5 s

Master

IUT

Slave




DM1


DM1


NULL


FLOW, HEC)

NULL or POLL


FLOW, HEC)

NULL


FLOW, HEC)

NULL or POLL


FLOW, HEC)

NULL


FLOW, HEC)

DM1


NULL


FLOW, HEC)

FLOW bit set to STOP.

ARQN bit set to NACK.

Default packet.



Default packet.

FLOW bit set to GO.





Baseband

The tester transmits LMP_features_req. The tester verifies that the IUT transmits a DM1 packet containing LMP_features_res. The tester responds the next 5 s with NULL packets with the FLOW bit set to '0'B indicating STOP and the ARQN bits set to NAK to guarantee a retransmission after indicating GO.The tester verifies that the IUT stops transmission and switches to the default packet type (NULL or POLL).The tester sends a NULL packet with FLOW bit set to '1'B indicating GO after the 5 s.NULLAccess code:


Packet Header:


The tester verifies that the IUT transmits a DM1 packet containing an LMP_features_res.



The IUT stops transmitting upon receiving STOP, switch to the default packet type and resumes to transmit when the GO indication is received. Maximum 5% of the NULL packets sent by the tester with the FLOW bit indicating STOP is answered by the IUT sending



Baseband

LMP_features_res.

Fail verdict:

The IUT does not stop transmitting upon receiving STOP.The IUT does not switch to the default packet type.The IUT does not resume to transmit when the GO indication is received.

• UncertaintiesIf the IUT misses a packet from the tester, it might interpret this as implicit GO and transmit the LMP_features_res even though the tester did not remove the stop indication. This would result in a false failure so the IUT is allowed to send the response for 5% of the given STOP indications.

• NotesN/A.

4.5.1.8 TP/PROT/ARQ/BV-08-C (Implicit GO)

Verify that the IUT configured as Master, goes back to normal transmission mode when the tester sends implicit GO.







Baseband

• Test Procedure

Figure 4.33: TP/PROT/ARQ/BV-08-C (Implicit GO)

5 s

Master

IUT

Slave




DM1


DM1


NULL


FLOW, HEC)

NULL or POLL


FLOW, HEC)

NULL


FLOW, HEC)

NULL or POLL


FLOW, HEC)

DM1


NULL


FLOW, HEC)

Implicit GO.

Does Nothing



Default packet.



Default packet.




Baseband

The tester transmits LMP_features_req. The tester verifies that the IUT transmits a DM1 packet containing LMP_features_res. The tester responds the next 5 s with NULL packets with the FLOW bit set to '0'B indicating STOP and the ARQN bits set to NAK to guarantee a retransmission after indicating GO.The tester verifies that the IUT stops transmission and switches to the default packet type (NULL or POLL).The tester verifies that the IUT transmits a DM1 packet containing LMP_features_res.



The IUT goes back to normal transmission mode upon reception of an implicit GO. Maximum 5% of the NULL packets sent by the tester with the FLOW bit indicating STOP is answered by the IUT sending LMP_features_res.

Fail verdict:

The IUT does not go back to normal transmission mode upon reception of an implicit GO.

• UncertaintiesIf the IUT misses a packet from the tester, it might interpret this as implicit GO and transmit the LMP_features_res even though the tester did not remove the stop indication. This would result in a false failure so the IUT is allowed to send the response for 5% of the given STOP indications.

• NotesN/A.



Baseband

4.5.1.9 TP/PROT/ARQ/BV-10-C (Same SEQN value)

Verify that the ARQN bit is set to ACK and the data are disregarded if a packet with CRC information with a correct header is received that has the same SEQN value as in the previous reception.







Baseband

• Test Procedure

Figure 4.34: TP/PROT/ARQ/BV-10-C (Same SEQN value)

The tester sends a DM1 packet containing LMP_features_req message.The tester verifies that the IUT sends a DM1 packet containing a LMP_features_res message.The tester repeats the former DM1 packet containing the LMP_features_req message (same SEQN value).The tester verifies that the IUT sends a packet with the ARQN bit set to ACK and verifies that the IUT does not respond to the 2nd LMP_features_req message with a LMP_features_res the next 30s.


30s

Master

IUT

Slave




DM1

(LMP_features_req)

DM1

DM1

(LMP_features_req)

any_ACL_packet


FLOW, HEC)

(LMP_features_res)

IUT does not send a

LMP_features_res.

Same SEQN value as in

the previous transmission.




Baseband


The IUT acknowledges with a packet with the ARQN bit set ACK and does not respond to the 2nd LMP_features_req message with a LMP_features_res for the next 30s.

Fail verdict:

The IUT does not acknowledge with a packet with the ARQN bit set ACK or responds to the 2nd LMP_features_req message with a LMP_features_res for the next 30s.


• NotesN/A.

4.5.1.10 TP/PROT/ARQ/BV-27-C (Explicit NAK – eSCO Master)

Verify that the IUT when configured as master, upon reception of an eSCO packet with its ARQN bit set to NAK (explicit NAK) prior to the end of the retransmission window, transmits the packet again.

Only for IUTs supporting eSCO links.




IUT:Configured as Master in state CONNCTION (active mode, ACL link).



Baseband

• Test Procedure

Figure 4.35: TP/PROT/ARQ/BV-27-C (Explicit NAK – eSCO Master)

Master

IUT

Slave




NULL

(LT_ADDR, Type, FLOW, ARQN,

SEQN, HEC)

EV3


SEQN, HEC)

EV3


SEQN, HEC)

EV3


SEQN, HEC)


An eSCO link is established.





Baseband

The tester sets up an eSCO link with the following parameters:

eSCO handle: Any valid number.eSCO LT_ADDR: Set by IUT.Timing control flags: Derived from IUT master clock.Desco: Set by IUT.Tesco: 6 slots.Wesco: 2 slots.Packet type M→S: EV3.Packet type S→M: EV3.Packet length M→S: 30 bytes.Packet length S→M: 30 bytes.Air mode: Any supported air mode.Negotiation Flag: Initiate Negotiation.

The tester verifies that the IUT transmits an EV3 packet at the eSCO instant.The tester transmits an EV3 packet in the following slot:EV3Access code:


Packet Header:

LT_ADDR: Logical Transport Address of the eSCO link.TYPE: ‘0111’B.FLOW: ‘1’B.ARQN: ‘0’B.SEQN: Depends on the former transmission of the tester.HEC: Generated by the polynomial ‘647’O in respect to the UAP of the master.

Payload header:

N/A.



Baseband

Payload:


The tester verifies that the IUT retransmits the EV3 packet.



The IUT retransmits the packet after receiving the EV3 packet with the ARQN bit set to NAK.

Fail verdict:



• NotesThis test is only mandatory for devices that support eSCO links.A PIXIT statement is used to distinguish between IUTs requiring HCI interac-tion to generate EV packets and IUTs transmitting the packets without HCI interaction. Optionally the IUT might send HCI eSCO packets to the upper tester.

4.5.1.11 TP/PROT/ARQ/BV-28-C (Implicit NAK – eSCO Master)

Verify that the IUT when configured as master, when the acknowledgement is left out (implicit NAK) prior to the end of the retransmission window, transmits the packet again.





Baseband




• Test Procedure

Figure 4.36: TP/PROT/ARQ/BV-28-C (Implicit NAK – eSCO Master)

Master

IUT

Slave




NULL


SEQN, HEC)

EV3


SEQN, HEC)

EV3


SEQN, HEC)




Does Nothing.



Baseband



The tester verifies that the IUT transmits an EV3 packet at the eSCO instant.The tester transmits nothing in the following slot.The tester verifies that the IUT retransmits the EV3 packet.



The IUT retransmits the packet.

Fail verdict:






Baseband

4.5.1.12 TP/PROT/ARQ/BV-30-C (Uncorrectable header – eSCO Master)

Verify that the IUT when configured as master, upon reception of a packet with uncorrectable errors in the packet header of an eSCO transmission prior to the end of the retransmission window, will transmit the next packet addressing the same slave with the ARQN bit set to NAK.








Baseband

• Test Procedure

Figure 4.37: TP/PROT/ARQ/BV-30-C (Uncorrectable header – eSCO Master)

Master

IUT

Slave




EV3

(LT_ADDR, TYPE, ARQN,

SEQN, FLOW, HEC)

EV3


SEQN, FLOW, HEC)

EV3


SEQN, FLOW, HEC)



EV3 packet with uncorrectable

errors in the packet header.



Baseband



The tester verifies that the IUT transmits an EV3 packet at the eSCO instant.The tester transmits an EV3 packet in the following slot:EV3Access code:


Packet Header:

LT_ADDR: Logical Transport Address of the eSCO link.TYPE: ‘0111’B.FLOW: ‘1’B.ARQN: ‘1’B.SEQN Depends on the former transmission of the tester.HEC: Generated by the polynomial ‘647’O in respect to the UAP of the master. The packet header is FEC 1/3 encoded. After the coding procedure the tester shall insert uncorrectable errors in the header in a random way.

Payload header:

N/A.



Baseband

Payload:


The tester verifies that the IUT retransmits the EV3 packet with the ARQN bit set to NAK.The test procedure is repeated 100 times with randomly drawn uncorrect-able error patterns.



The IUT retransmits the packet inside the retransmission window, with the ARQN bit set to NAK, for at least 99% of the repetitions excluding responses using the ACL LT_ADDR.

Fail verdict:

The IUT does not retransmit the packet, or retransmits the packet with the ARQN bit set to ACK, for more than 1% of the repetitions excluding responses using the ACL LT_ADDR.

• UncertaintiesPOLL packets have higher priority than eSCO retransmissions so the IUT might use the ACL LT_ADDR in the retransmission window.







Baseband

4.5.2 ARQ Procedures - Slave


• To verify that the ARQ scheme used by the Slave is correct.




4.5.2.2 TP/PROT/ARQ/BV-14-C (Uncorrectable packet header)

Verify that the IUT configured as Slave, upon reception of a packet with uncor-rectable errors in the packet header, does not transmit any packet.



Configured as Master in state CONNECTION (active mode, ACL link).




Baseband

• Test Procedure

Figure 4.38: TP/PROT/ARQ/BV-14-C (Uncorrectable packet header)

The tester transmits a DM1 packet with an uncorrectable error in the packet header.DM1Access code:


Slave

IUT

Master


Tester: configured as Master in state CONNECTION (active mode, ACL link.)

IUT: configured as Slave in state CONNECTION (active mode, ACL link.)

With uncorrectable errors

in the packet header.

DM1

(any_value)

POLL

any_ACL_packet

IUT does not transmit


to master slot.




Baseband

Packet Header:


The packet header is FEC 1/3 coded. After the coding procedure has suc-cessfully performed errors have to be inserted. The maximum number of inserted errors depends on the Hamming distance provided by the HEC.

Payload header:

LLID: '11'B indicating LMP message.FLOW: '1'B.LENGTH: '10001'B = '17'D.Payload body: 17 Bytes PRBS plus 2 bytes CRC.

The tester verifies that the IUT does not transmit any packet in the following slave to master slot.The tester verifies that the IUT transmits an ACL packet with the ARQN bit set to NAK after the next POLL interval of the tester.This test procedure is repeated 100 times. The inserted uncorrectable errors must be statistically distributed.



For at least 99% of the repetitions the IUT does not transmit any packet in the next slave to master slot. After the next POLL the IUT sets the ARQN bit to NAK.

Fail verdict:

For more than 1% of the repetitions the IUT transmits a packet in the next slave to master slot. After the next POLL the IUT sets the ARQN bit to ACK.



Baseband


• NotesN/A.

4.5.2.3 TP/PROT/ARQ/BV-15-C (Uncorrectable payload)

Verify that the IUT configured as Slave, upon reception of a DM1 packet with uncorrectable errors in the payload, either transmits a packet with ARQN bit set to NAK or does not answer.







Baseband

• Test Procedure

Figure 4.39: TP/PROT/ARQ/BV-15-C (Uncorrectable payload)

The tester transmits a DM1 packet with an uncorrectable error in the pay-load.DM1Access code:


Packet Header:


OPT

Slave

IUT

Master




DM1

(any value)

any_ACL_packet


FLOW, HEC)


in the payload.




Baseband

Payload header:

LLID: '11'B indicating LMP message.FLOW: '1'B.LENGTH: '10001'B = '17'D.Payload body: 17 Bytes PBRS plus 2 bytes CRC.

This corresponds to 160 bits payload contents (1 Byte packet header 17 Bytes payload body and 2 Bytes CRC) before FEC 2/3 coding. After FEC 2/3 coding the payload consists of 240 bits. The maximum number of inserted errors depends on the Hamming distance provided by the CRC.The tester verifies that the IUT transmits any ACL packet with the ARQN bit set to NAK, or no packet at all.This test procedure is repeated 100 times. The inserted uncorrectable errors must be statistically distributed.



In at least 99% of the repetitions the IUT sends a packet with the ARQN bit set to NAK or no packet at all in the next slave to master slot.

Fail verdict:

In more than 1% of the repetitions the IUT sends a packet with the ARQN bit set to ACK in the next slave to master slot.


• NotesThis test should lead to the tester transmitting 100 consecutive packets with uncorrectable errors.



Baseband

4.5.2.4 TP/PROT/ARQ/BV-16-C (Explicit NAK)

Verify that the IUT configured as Slave, upon reception of a packet with its ARQN bit set to NAK (explicit NAK), retransmits the packet again.

• Reference[Vol. 2, Part B] Section 6.4.4 on page 104.[Vol. 2, Part B] Section 7.6 on page 124.[Vol. 2, Part B] Section 7.6.2 on page 127.




• Test Procedure

Figure 4.40: TP/PROT/ARQ/BV-16-C (Explicit NAK)

Slave

IUT

Master




DM1

(LMP_features_req (features)

DM1

(LMP_features_res (features)

NULL


FLOW, HEC)

DM1

(LMP_features_res (features)

With ARQN bit set to NAK.



Baseband

The tester sends a DM1 packet containing a LMP_features_req message.The tester verifies that the IUT responds with the LMP_features_res mes-sage by using a DM1 packet.The tester acknowledges the packet with a NULL packet with the ARQN bit set to NAK.The tester verifies that the IUT retransmits the DM1 packet again containing the LMP_features_res message.



The IUT retransmits the packet after receiving the NULL packet with the ARQN bit set to NAK.

Fail verdict:



• NotesN/A.

4.5.2.5 TP/PROT/ARQ/BV-18-C (SEQN)

Verify that the IUT configured as Slave, respects SEQN values in the transmit case.






Baseband

IUT:Configured as Slave in state CONNECTION (active mode, ACL link).The tester does not support any feature.

• Test Procedure

Figure 4.41: TP/PROT/ARQ/BV-18-C (SEQN)

The tester transmits a DM1 packet containing LMP_features_req message.

Slave

IUT

Master




DM1

(LMP_version_req (Vers, Comp, SubVers))

DM1

(LMP_version_res (Vers, Comp, SubVers))

DM1

(LMP_features_req

(features=0x0000000000000000))DM1


NULL or POLL


FLOW, HEC)

DM1


DM1

(LMP_features_req

(features=0x0000000000000000))

DM1


LMP_version_req together

with no features in the tester

minimizes the risk the IUT

initiates LMP signaling, still

the IUT might transmit

something else before

LMP_features_res.



Same SEQN as in previous

CRC transmission.

Different SEQN as in previous

CRC transmission.


The IUT might transmit other

LMP signaling before

LMP_features_res.



Baseband

DM1Access code:


Packet Header:


Payload header:

LLID: 11'B indicating LMP message.FLOW: '1'B.LENGTH: '01001'B = '9'D.Payload body: 9 Bytes.

1. Byte = '4E'H Transaction ID and OpCode.2. to 9. Byte = '00'H.

The tester verifies that the IUT transmits a DM1 packet containing LMP_features_res message. The tester has to store the SEQN value (first SEQN value) contained in the packet header.The tester acknowledges the packet with NULL or POLL packets with the ARQN bit set to NAK.The tester verifies that the IUT retransmits the DM1 packet containing LMP_features_res message with the same SEQN value (second SEQN value) as in the previous transmission. The tester has to store the SEQN value contained in the packet header.The tester transmits a DM1 packet containing LMP_features_req message again with the ARQN bit set to ACK.The tester verifies that the IUT transmits a DM1 packet with a different SEQN value (third SEQN value) compared to the previous transmissions.



Baseband



The second SEQN value is the same as the first SEQN value The third SEQN value is not the same as the second SEQN value.

Fail verdict:

The second SEQN value is not the same as the first SEQN value The third SEQN value is the same as the second SEQN value.

• UncertaintiesThe IUT might transmit unsolicited LMP signaling changing the intended test procedure. This risk is minimized by having the tester transmit LMP_version_req immediately after connection establishment and always indicate no feature is supported.

• NotesN/A.

4.5.2.6 TP/PROT/ARQ/BV-19-C (FLOW control)

Verify that the IUT configured as Slave, stops transmitting upon receiving STOP indication, switch to the default packet type and resumes to transmit when GO indication is received.







Baseband

• Test Procedure

Figure 4.42: TP/PROT/ARQ/BV-19-C (FLOW control)

20s

Slave

IUT

Master




DM1


NULL


FLOW, HEC)

POLL


FLOW, HEC)

NULL


FLOW, HEC)

POLL


FLOW, HEC)

NULL


FLOW, HEC)

POLL


FLOW, HEC)

DM1


FLOW bit indicating STOP.



FLOW bit indicating GO.



Baseband

The tester sends a DM1 packet containing a LMP_features_req message with the FLOW bit set to '0'B indicating STOP.The tester verifies that the IUT stops transmission and switches to the default packet type (NULL). Since LM does not work in real time a value of 20 seconds was chosen to ensure that the LMP_features_res message is ready before the GO indication will be sent from the tester. In this 20 s the tester sends POLL packets with the FLOW bit set to STOP.After expiration of the 20 seconds the tester sends a POLL packet with the FLOW bit set to GO.The tester verifies that the IUT responds with the LMP_features_res mes-sage by using a DM1 packet.



The IUT stops transmitting upon receiving STOP for at least 20 seconds.The IUT switch to the default packet type for at least 20 seconds.The IUT resumes to transmit when GO indication is received.

Fail verdict:

The IUT does not stop transmitting upon receiving STOP for at least 20 seconds.The IUT does not switch to the default packet type for at least 20 seconds.The IUT does not resume to transmit (LMP_features_req message) when the GO indication is received.


• NotesN/A.



Baseband

4.5.2.7 TP/PROT/ARQ/BV-23-C (Same SEQN value)

Verify that the ARQN bit is set to ACK and the data is disregarded if a packet with CRC information with a correct header is received that has the same SEQN value as in the previous reception.







Baseband

• Test Procedure

Figure 4.43: TP/PROT/ARQ/BV-23-C (Same SEQN value)

The tester sends a DM1 packet containing a LMP_features_req message.The tester verifies that the IUT transmits a DM1 packet containing a LMP_features_res message.The tester sends a DM1 packet containing a LMP_features_req message again with the same SEQN bit as set in the previous transmission.The tester verifies that the IUT sends a packet with the ARQN bit set to ACK and discards the payload.Since LM does not work in real time the tester waits for 30 seconds to ensure that the LMP_feature_res is not sent from the IUT.

30s

Slave

IUT

Master




DM1


DM1


DM1


any_ACL_packet


SEQN, HEC)

30s no response upon

LMP_features_req.

Same SEQN value as in

previous transmission.




Baseband



The IUT sends a packet with the ARQN bit set to ACK and the IUT disregards the new data.

Fail verdict:

The IUT does not send a packet with the ARQN bit set to ACK and the IUT does not disregarded the new data.


• NotesN/A.

4.5.2.8 TP/PROT/ARQ/BV-25-C (Retransmission of DV packet)

Verify that the data payload of a DV packet is retransmitted upon reception of the ARQN bit set to NAK.

Only for IUTs supporting SCO packets.



Configured as Master.

IUT:Configured as Slave.An SCO connection is established.



Baseband

• Test Procedure

Figure 4.44: TP/PROT/ARQ/BV-25-C (Retransmission of DV packet)

Slave

IUT

Master


SCO connection established.

DV

(Access Code, Header, Voice field,

LMP_features_res (features)))

HV1


DV


LMP_features_res (features)))

DV


LMP_features_req (features)))

HV1


HV1


OPTIONAL

OPTIONAL

HCI_Host_Buffer_Size

(Host_ACL_Data_Packet_Length,

Host_Synchronous_Data_Packet_Length,

Host_Total_Num_ACL_Data_Packets,

Host_Total_Num_Synchronous_Data_Packets)


(Num_HCI_Comm, Com_OpCode=0x0C33,

Status=0x00)

HCI_Read_Buffer_Size


(Num_HCI_Comm, Com_OpCode=0x1005,

Status=0x00, Host_ACL_Data_Packet_Length,




HCI_Synchronous_Data_Packets


(Conn_Handle, Data_total_length, Data)


The IUT might replace DV packets

with DM1 packets, also in

retransmissions.


Same data as in the previous DV

transmission.

New voice information.

Several HV1 packets might be

exchanged before the DV packet

is transmitted.



Baseband

The tester transmits a DV packet containing LMP_features_req to the IUT in order to force the IUT to transmit LMP_features_res.The tester verifies that the IUT transmits a DV packet containing the LMP_features_res message.The tester responds with an HV1 packet with the ARQN bit set to NAK.The tester verifies that the IUT retransmits the DV packet containing the LMP_features_res message.With PIXIT is selected if the IUT needs HCI Synchronous Data packets to transmit HV1/DV packets. If HCI Synchronous Data packets are used the upper tester fills them with a pseudo random bit pattern and the lower tester checks each HV1/DV packet has a new voice field.



The IUT transmits a DV packet again containing the same data field.If HCI Synchronous Data packets are used the new DV packet contains a new voice field.

Fail verdict:

The IUT transmits a DV packet again containing a new data field.If HCI Synchronous Data packets are used the new DV packet contains the previous voice field.

• UncertaintiesThere is no possibility written in the core specification to force the IUT to send a DV packet. For IUTs using DV packets it can be checked whether they are received If no DV packet is returned the IUT must return a DM1 packet.

• NotesA PIXIT statement is used to distinguish between IUTs requiring HCI interac-tion to transmit HV1/DV packets and IUTs transmitting the packets without HCI interaction. Optionally the IUT might send HCI Synchronous packets to the upper tester.



Baseband

4.5.2.9 TP/PROT/ARQ/BV-26-C (Uncorrectable DV packet)

Verify that the IUT configured as Slave, upon reception of a DV packet with uncorrectable errors in the data payload, transmits a packet with the ARQN bit set to NAK.




IUT:Configured as Slave.An SCO connection using HV1 packets is established.



Baseband

• Test Procedure

Figure 4.45: TP/PROT/ARQ/BV-26-C (Uncorrectable DV packet)

The tester transmits a DV packet with uncorrectable errors in the data pay-load.

Slave

IUT

Master


SCO connection established using HV1 packets.

OPTIONAL

OPTIONAL

HV1


HV1


DV


Data field)

HV1









Status=0x00)












Uncorrectable errors in the

data payload.

ARQN bit set to NAK, could

be DM1 or DV packet too.



Baseband

The tester verifies that the IUT transmits a DM1, DV or HV1 packets with the ARQN bit set to NAK.



The IUT transmits a DM1, DV or HV1 packet with the ARQN bit set to NAK.

Fail verdict:

The IUT transmits a DM1, DV or HV1 packet with the ARQN bit set to ACK.



4.5.2.10 TP/PROT/ARQ/BV-29-C (Explicit NAK – eSCO Slave)

Verify that the IUT when configured as slave, upon reception of an eSCO packet with its ARQN bit set to NAK, transmits the packet again.





Baseband



IUT:Configured as Slave in state CONNCTION (active mode, ACL link).

• Test Procedure

Figure 4.46: TP/PROT/ARQ/BV-29-C (Explicit NAK – eSCO Slave)

Slave

IUT

Master




POLL


SEQN, FLOW, HEC)

EV3


SEQN, FLOW, HEC)

EV3


SEQN, FLOW, HEC)

EV3


SEQN, FLOW, HEC)


With ARQN bit set to NAK.



Baseband


eSCO handle: Any valid number.eSCO LT_ADDR: Any valid number.Timing control flags: Derived from tester’s master clock.Desco: Any number in the range [0,Tesco-1].Tesco: 6 slots.Wesco: 2 slots.Packet type M→S: EV3.Packet type S→M: EV3.Packet length M→S: 30 bytes.Packet length S→M: 30 bytes.Air mode: Any supported air mode.Negotiation Flag: Initiate Negotiation.

The tester transmits an EV3 packet at the eSCO instant.

EV3Access code:


Packet Header:


Payload header:

N/A.



Baseband

Payload:


The tester verifies that the IUT transmits an EV3 packet in the following slot.The tester transmits a POLL packet in the following slot:

POLLAccess code:


Packet Header:


The tester verifies that the IUT retransmits the EV3 packet in the following slot.



The IUT retransmits the packet after receiving the EV3 packet with the ARQN bit set to NAK.

Fail verdict:




Baseband



4.5.2.11 TP/PROT/ARQ/BV-31-C (Uncorrectable header original transmission – eSCO Slave)

Verify that the IUT when configured as slave, upon reception of a packet with uncorrectable errors in the packet header of an eSCO original transmission, will transmit the packet with the ARQN bit set to NAK.








Baseband

• Test Procedure

Figure 4.47: TP/PROT/ARQ/BV-31-C (Uncorrectable header original transmission – eSCO Slave)



Slave

IUT

Master




EV3

EV3








Baseband


EV3Access code:


Packet Header:

LT_ADDR: Logical Transport Address of the eSCO link.TYPE: ‘0111’B.FLOW: ‘1’B.ARQN: ‘1’B.SEQN: Depends on the former transmission of the tester.HEC: Generated by the polynomial ‘647’O in respect to the UAP of the master. The packet header is FEC 1/3 encoded. After the coding procedure the tester shall insert uncorrectable errors in the header in a random way.

Payload header:

N/A.

Payload:


The tester verifies that the IUT transmits an EV3 packet in the next slot with the ARQN bit set to NAK.The test procedure is repeated 100 times with randomly drawn uncorrect-able error patterns.




Baseband


The IUT transmits the packet with the ARQN bit set to NAK for at least 99% of the repetitions excluding responses using the ACL LT_ADDR.

Fail verdict:

The IUT does not transmit the packet, or transmits the packet with the ARQN bit set to ACK, for more than 1% of the repetitions excluding responses using the ACL LT_ADDRs.

• UncertaintiesThe tester might POLL the IUT forcing the IUT to acknowledge the POLL rather than retransmit eSCO.


4.5.2.12 TP/PROT/ARQ/BV-32-C (Uncorrectable header re-transmission – eSCO Slave)

Verify that the IUT when configured as slave, upon reception of a packet with uncorrectable errors in the packet header of an eSCO re-transmission, does not transmit.







Baseband


• Test Procedure

Figure 4.48: TP/PROT/ARQ/BV-32-C (Uncorrectable header re-transmission – eSCO Slave)

Slave

IUT

Master




EV3

EV3




IUT does not transmit


to master slot.

POLL



Baseband




EV3Access code:


Packet Header:


Payload header:

N/A.



Baseband

Payload:


The tester verifies that the IUT transmits an EV3 packet in the next slot.The tester transmits a POLL packet in the following slot:POLLAccess code:


Packet Header:


The packet header is FEC 1/3 encoded. After the coding procedure the tester shall insert uncorrectable errors in the header in a random way.The tester verifies that the IUT does not transmit again inside the retrans-mission window.The test procedure is repeated 100 times with randomly drawn uncorrect-able error patterns.



The IUT does not transmit in response to the second packet from the tester, in at least 99% of the repetitions.



Baseband

Fail verdict:

The IUT transmits a packet in response to the second packet from the tester, in more than 1% of the repetitions.






4.6 INQUIRY


• To verify the Inquiry procedures.

4.6.1 Inquiry Procedures - Master


• To verify that the Inquiry procedures for the Master is correct.






Baseband

4.6.1.2 TP/PHYS/INQ/BV-01-C (Inq hop seq)

Verify that the IUT as master uses the correct inquiry hopping sequence when discovering which other Bluetooth devices are in range.

Only for IUTs supporting inquiry and using the 79-channel hopping scheme.

Verify that:

a) the master uses the general inquiry access code (GIAC) and its native clock CLKN to determine the inquiry hopping sequence.

b) the master sequentially transmits on 2 different hop frequencies during each TX slot.

c) 2 10 ms inquiry trains A and B with 16 hops each are used.d) the inquiry trains A and B are repeated at least Ninquiry = 256

times.e) at least 4 trains are transmitted subsequently.f) One inquiry instance is stopped latest when inquiryTO is reached.


• Initial Conditiona) The tester has performed an inquiry procedure as master before

to get the clock CLK of the IUT.b) The IUT is configured as master.c) Both IUT and tester are in standby mode.

• Test ProcedureTo verify the inquiry hopping sequence the tester must not follow the normal inquiry scan procedure. For the RX slots, the inquiry hopping sequence of the master is used as well instead.

a) In the HCI_Inquiry command the general inquiry LAP is used.b) The tester listens for inquiry packets from the IUT using an

algorithm derived from its BT clock and enabling it to receive a packet within the IUT´s first repetition of the first A-Train. The tester´s correlator is matched to the inquiry access code.

c) The tester monitors the train A during one train (16 frequencies). If no inquiry packet is received, the tester switches to scan train B during one train.

d) Switching trains will continue until first ID packet is received by the tester



Baseband

e) After successfully receiving the first IAC packet, the tester adjusts its RX window and phase (clock bits 0-1) to get the remaining hops of train. The tester never responds to the inquiry.

f) The IUT repeats its first train for at least Ninquiry=256 times.g) The tester records the first inquiry train for 255 times only because

the first train is known to be incomplete.h) The tester immediately starts listening on the other train

frequencies.i) The IUT sends the other inquiry train for Ninquiry times starting at

an unknown point of time.j) The tester records this inquiry train for 256 times.k) Steps f) to j) are repeated until the inquiry instance is finished but

with the difference that the tester always monitors 256 repetitions for each train from now on (also in step g).

l) One of the reserved LAPs for dedicated inquiry is randomly chosen and steps b) to k) are repeated.

• Test ConditionNone.


Requirements a) to f) are fulfilled.Requirement a) is checked in steps d), j) and l)Requirement b) is checked in steps d) and j)Requirement c) is checked in steps d) and j)Requirement d) is checked in steps f) and j)Requirement e) is checked in step k)Requirement f) is checked in step k).The tester records at least 95% of the expected ID packets.

Fail verdict:

Otherwise.

• UncertaintiesAs it is not possible to completely record all packets of the first most train after inquiry starts, violations of requirements cannot be checked on the first A train repetition. A cable connection is recommended to create an undisturbed RF path.



Baseband

• NotesN/A.

4.6.1.3 TP/PHYS/INQ/BV-03-C (Inquiry proc)

Verify that the IUT as master uses the correct procedure when performing inquiry.

Verify that:

a) the master transmits the inquiry access code in the ID packet when starting the inquiry procedure.

b) that the master continuously transmits inquiry messages after receiving a response (FHS packet).

c) the inquiry substate is left after a sufficient number of responses.

• Reference[Vol. 2, Part B] Section 8.4.2 on page 145.[Vol. 2, Part B] Section 8.4.3 on page 147.

• Initial Conditiona) IUT must be configured as master.b) The IUT is in STANDBY mode.

• Test Procedurea) The tester sends a HCI_Inquiry command to carry out Inquiry and

sets the values for the LAP, and the Inquiry_Length and Num_Responses as follows:

LAP: LAP for GIAC ‘9E8B33’H.Inquiry_Length: 0x30 = 61,44 sec.Num_Responses: 2.

b) The tester verifies that the master sends an ID packet containing the general inquiry access code (GIAC).



Baseband

c) The tester sends a FHS packet after receiving the first ID packet.d) The tester verifies that the master sends continuously ID packets

containing the general inquiry access code (GIAC).e) After a random number (between 0 and 1023) of time slots the

tester sends one more FHS packet (different BD_ADDR from that sent the first time in step c)).

f) The tester waits 30 seconds and verifies that no more ID packet is sent by the IUT (i.e. the IUT has left inquiry substate).



Requirements a) to c) are fulfilled.Requirement a) is checked after step b.Requirement b) is checked after step d.Requirement c) is checked after step f.

Fail verdict:

Otherwise.


• NotesNone.






Baseband

4.6.2 Inquiry Procedures - Slave


• To verify that the Inquiry procedures for the slave are correct.




4.6.2.2 TP/PHYS/INQ/BV-10-C (Inquiry response)

Verify that the IUT as slave uses the correct inquiry response procedure.

Only for IUTs supporting inquiry scan with first FHS.

Verify that:a) the IUT transmits the inquiry response (FHS packet) 625 µs after

receiving the inquiry message.b) the IUT transmits a FHS packet with the slave's device address

after receiving an inquiry message.c) the IUT (if it does receive an inquiry message and returns a FHS

packet) adds an offset of 1 to the phase in the inquiry hop sequence (the phase has a 1.28s resolution) and enters the inquiry scan substate again.



To ensure that the tester can follow the inquiry scan sequence of the slave an inquiry procedure has been performed before to get the estimate CLKE of the slave’s BT clock. The IUT uses default values for inquiry scan interval and inquiry scan window:

Inquiry scan interval = 4096 slots.Inquiry scan window = 18 slots.Scan_Type = Normal Scan.

The inquiry scan of the IUT is started before the tester starts inquiry.



Baseband

• Test Procedurea) The tester starts inquiry using A trains, f(k) corresponding to the

estimate of the IUT's scan frequency at the beginning of a 1.28 s phase (CLK 2-11 = 0). The tester sends ID packets continuously until the IUT responds with the FHS packet.

b) After receiving the FHS packet from the IUT the tester increases its phase and sends ID packets again until the next FHS packet is received.

c) Step b) will be repeated until 10 FHS packets have been received. The time distance between the FHS packets will be recorded and shall be randomly. After the 10th FHS packet the tester shall stop sending the packets for at least 1023 slots.

d) Step a) to c) are performed 10 times.



Requirements a) to d) are fulfilled.In step d) of the test procedure, the tester receives at least 99 FHS packets from the IUT.Requirement a) is checked after step b).Requirement b) is checked after step b).Requirement c) is checked in step d).

Fail verdict:

Otherwise.


• NotesN/A.

4.6.2.3 TP/PHYS/INQ/BV-14-C (Inquiry scan window and interval)

Verify that the IUT as slave uses the correct inquiry scan window and interval.



Baseband

Only for IUTs supporting inquiry scan with first FHS.

To verify that:a) the receiver scans for the inquiry access code long enough to

completely scan for 16 inquiry frequencies.b) the phase changes every 1.28 s.


• Initial Conditiona) The tester uses the 79 hop scheme according to the IUT

capabilities.b) The IUT is in STAND BY mode.

HCI_Write_Scan_Enable = 01’H (Inquiry Scan enabled; Page Scan disabled).

c) Default values are used for:InquiryScan_Interval = 4096 slots (2.56 s) andInquiryScan_Window = 18 slotsScan_Type = Normal Scan



Baseband

• Test Procedurea) The tester continuously transmits inquiry messages until a

response FHS packet is received.b) The tester waits for 1023 slots plus 18 slots.c) Steps a) and b) are performed 100 times.



In step b) of the test procedure, the tester receives a response FHS packet within 5.12 s after starting to transmit inquiries for more than 95% of the inquiry procedures.

Fail verdict:

In step b) of the test procedure, the tester receives a response FHS packet within 5.12 s after starting to transmit inquiries for less than 95% of the inquiry procedures.


• NotesIn test procedure step b) the additional 18 slots is required for the tester to avoid receiving FHS at the first inquiry scan after test procedure step a) even if the RAND is 1023 slots.

4.6.2.4 TP/PHYS/INQ/BV-15-C (Interlaced Inquiry scan window and interval)

Verify that the IUT as slave uses the correct inquiry scan window and interval.

Only for IUTs supporting inquiry scan with first FHS and interlaced scan.

To verify that:a) the receiver scans for the inquiry access code long enough to

completely scan for 16 inquiry frequencies.b) the phase changes every 1.28 s.



Baseband


• Initial Conditiona) The tester uses the 79 channel hop scheme.b) The IUT is in STAND BY mode.

HCI_Write_Scan_Enable = ‘01’H (Inquiry Scan enabled; Page Scan disabled).

c) Default values are used for:InquiryScan_Interval = 4096 slots (2.56 s) andInquiryScan_Window = 18 slotsScan_Type = Interlaced Scan

• Test Procedurea) The tester continuously transmits inquiry messages until a

response FHS packet is received.b) The tester waits for 1023 slots plus 128 slots.c) Steps a) and b) are performed 100 times.



In step b) of the test procedure, the tester receives a response FHS packet within 2.56 s after starting to transmit inquiry messages for more than 95% of the inquiry procedures.

Fail verdict:

In step b) of the test procedure, the tester receives a response FHS packet within 2.56 s after starting to transmit inquiry messages for less than 95% of the inquiry procedures.




Baseband

• NotesIn test procedure step b) since there may be some switching time between two back to back scans, the tester should wait for 1023 slots + 18 slots + (switching time) + 18 slots. It is assumed that no implementation would have the switching time larger than 128-18-18=92 slots.

4.7 PAGING


• To verify the Paging procedures.

4.7.1 Paging Procedures - Master


• To verify that the Paging procedures for the Master, i.e. the unit establishing the connection, is correct.




4.7.1.2 TP/PHYS/PAG/BV-01-C (Page hop seq)

Verify that the IUT as master uses the correct paging hopping sequence when paging the Slave (tester).

Only for IUTs supporting paging and using the 79-channel hopping scheme.

Verify that:

a) the master uses the slave's device address to determine the page hopping sequence.

b) the master sequentially transmits on 2 different hop frequencies during each TX slot.

c) the master uses the estimate CLKE of the slave's BT clock to build the page trains A and B (only applicable if IUT supports Inquiry).

d) the page trains A and B are repeated Npage times, depending on the scan interval R0/R1/R2.

e) the page is aborted after pageTO if no response is received.

• Reference



Baseband

[Vol. 2, Part B] Section 8.3.2 on page 136.

• Initial Conditiona) If the IUT supports inquiry:

The IUT pages the tester to become the master of the piconet. An inquiry procedure has been performed before to get back the clock offset between master and slave clock in the inquiry result event. The clock offset is used in the HCI_Create_Connection command to the IUT in step b) of the test procedure.If the IUT does not support Inquiry:The IUT pages the tester to become the master of the piconet. The clock offset between master and slave clock is calculated in the tester. The clock offset is used in the HCI_Create_Connection command to the IUT in step b) of the test procedure.

b) If Inquiry is supported SR mode R0 is used.



Baseband

• Test ProcedureTo verify the page hopping sequence the tester must not follow the normal page scan procedure. For the RX slots, the page hopping sequence is used as well instead.

a) The tester listens for paging packets from the IUT using an algorithm derived from its BT clock and enabling it to receive a packet within the IUT´s first repetition of the first A-Train. The tester´s correlator is matched to its device address.

b) The IUT starts the page at some point not exactly known to the tester.

c) After successfully receiving the first ID packet, the tester adjusts its RX window and phase (clock bits 0-1) to get the remaining hops of train A. The tester never responds to the page.

d) The IUT repeats train A for at least Npage times.e) The tester records inquiry train A for Npage-1 times only because

the first train is known to be incomplete. As the number of repetitions is not known, only the minimum required number (i.e. 1, 128 or 256) is recorded to avoid missing the change to train B. If Npage is 1, to assure, that the first B train can be completely monitored, the tester shall switch to step f) after exactly one ID packet of train A was received.

f) The tester immediately starts listening on train B frequencies.g) The IUT sends page train B for Npage times starting at an

unknown point of time.h) The tester records page train B for Npage times. As the number of

repetitions is not known, only the minimum required number (i.e. 1, 128 or 256) is recorded to avoid missing the change to train A.

i) Steps d) to h) are repeated until the timeout page TO is reached but with the difference that the tester always monitors Npage repetitions for each train from now on (also in step e).

j) Steps a) to i) are repeated with SR mode R1 and R2.k) The tester changes its device address. A new inquiry procedure is

performed to get the new DAC (if the IUT supports inquiry).l) Steps a) to i) are repeated.




Baseband


Requirements a) to e) are fulfilled.Requirement a) is checked in steps a), c) and j).Requirement b) is checked in steps a) and c).Requirement c) is checked in steps a) and c).Requirement d) is checked in steps e) and h).Requirement e) is checked in step i).The tester records at least 95% of the expected ID packets.

Fail verdict:

Otherwise.


• NotesDue to the limited resolution of the CLK value used for CLKE calculation the tester can miss hops of the first page train A.

4.7.1.3 TP/PHYS/PAG/BV-03-C (Page resp to 1st msg)

Verify that the IUT as master uses the correct page response procedure when paging the slave (tester).

The slave responds to the first page message.

Verify that:

a) the IUT (master) enters the master response routine, freezes the current clock input to the page hop selection scheme and transmits a FHS packet containing the master’s real time Bluetooth clock.

b) the IUT (master) transmits the FHS packet 1250 µs after transmitting the first page packet if a response is received from the slave (step 3).

c) the IUT (master) updates the clock in each new FHS packet if no response is received.

d) the IUT (master) changes to the master parameter submitted in the FHS packet (step 3, channel access code and master clock) after the FHS packet has been acknowledged by the slave (step5).



Baseband

e) after a successful page attempt the IUT enters the CONNECTION state (step 5).

f) the IUT (master) sends first a POLL packet within newconnectionTO number of slots after reception of the FHS packet acknowledgement (step 5).


• Initial Conditiona) The IUT is in STANDBY mode.b) The tester know the BD_ADDR of the IUT.c) A Page procedure is initiated by the IUT (master, step 1).

• Test Procedurea) The tester (slave) responds to the first page message.b) After receiving the first FHS packet (step 3) the tester records the

CLK27-2 field in the FHS packet and does not send a response.c) After receiving the second FHS packet (step 3) the tester

compares the clock value CLK27-2 field of the first FHS packet with that received in the second FHS packet (the CLK value is increased by 1) and sends a response.

d) After receiving the fist traffic packet (POLL packet) from the IUT the tester checks that the first POLL packet was sent within newconnectionTO after the FHS packet acknowledgement.

e) The tester checks that the IUT uses the master channel access code, the master clock and the rules for the 79 hopping system (master BD_ADDR) to change from ‘master response substate’ to CONNECTION state (step 5).

• Test ConditionIt must be possible to instruct the IUT to start the page procedure and also which unit to page, the DAC for the Slave (tester).



Baseband


Requirement a) to f) are fulfilled.Requirement a) is checked after step b.Requirement b) is checked after step b.Requirement c) is checked after step c.Requirement d) is checked after step d.Requirement e) is checked after step e, f.Requirement f) is checked after step d.

Fail verdict:

Otherwise.


• NotesN/A.

4.7.1.4 TP/PHYS/PAG/BV-05-C (Page resp to 2nd msg)

Verify that the IUT as master uses the correct page response procedure when paging the slave (tester).

The slave responds to the second page message.

Verify that:

a) the IUT (master) enters the master response routine, freeze the current clock input to the page hop selection scheme and transmits a FHS packet containing the master’s real time Bluetooth clock.

b) the IUT (master) transmits the FHS packet 1250 µs after transmitting the first page packet if a response is received from the slave (step 3).

c) the IUT (master) updates the clock in each new FHS packet if no response is received.

d) the IUT (master) changes to the master parameter submitted in the FHS packet (step 3, channel access code and master clock) after the FHS packet has been acknowledged by the slave (step5).



Baseband

e) after a successful page attempt the IUT enters the CONNECTION state (step 5).

f) the IUT (master) sends first a POLL packet within newconnectionTO number of slots after reception of the FHS packet acknowledgement (step 5).


• Initial Conditiona) The IUT is in STANDBY mode.b) The tester know the BD_ADDR of the IUT.c) A Page procedure is initiated by the IUT (master, step 1).

• Test Procedurea) The tester (Slave) responds to the second page message.b) After receiving the first FHS packet (step 3) the tester records the

CLK27-2 field in the FHS packet and does not send a response.c) After receiving the second FHS packet (step 3) the tester

compares the clock value CLK27-2 field of the first FHS packet with that received in the second FHS packet and send an response.

d) After receiving the fist traffic packet (POLL packet) from the IUT the tester checks that the first POLL packet was sent within newconnectionTO after the FHS packet acknowledgement.



Baseband

e) The tester checks that the IUT uses the master channel access code, the master clock and the rules for the 79 hopping system (master BD_ADDR) to change from ‘master response substate’ to CONNECTION state (step 5).

Figure 4.49: Messaging at initial connection when slave responds to second page message.



Requirement a) to f) are fulfilled.Requirement a) is checked after step b.Requirement b) is checked after step b.Requirement c) is checked after step c.Requirement d) is checked after step d.Requirement e) is checked after step e, f.Requirement f) is checked after step d.

Fail verdict:

Otherwise.


• NotesN/A.

step 1 step 2 step 3 step 4 step 5 step 6

f(k) f(k+1) f(k+2) g(m)

f'(k+2)f'(k+1) g(m+1)

PAGE FHS 1st TRAFFIC

1st TRAFFICRESPONSERESPONSE

page hopping sequence channel hopping sequence

MASTER

SLAVE



Baseband

4.7.2 Paging Procedures - Slave


• To verify that the Paging procedures for the Slave is correct.






Baseband

4.7.2.2 TP/PHYS/PAG/BV-10-C (Page resp 1/1 slot)

Verify that the IUT as slave uses the correct page response procedure when receiving the page message in the first half of the RX time slot.

Only for IUTs supporting page scan

Verify that:a) the slave enters the slave response routine and freezes the

current clock input to the page and page response hop selection.b) the slave transmits a response message after receiving his own

device access code with the slave’s device access code 625 µs after the beginning of the received page message.

c) the slave uses the slave response sequence for transmission during initial messaging.

d) the IUT returns back to the page scan substate for one scan period if nothing was received after pagerespTO.

e) the slave return to the state it was in prior to the first page scan if pagerespTO is exceeded and no page message is received during the additional scan period.

f) the IUT returns to page scan substate when not receiving a POLL packet within newconnectionTO after acknowledging the FHS packet.

g) the slave changes to the master parameter submitted in the FHS packet (BT address and master clock) after the FHS packet has been acknowledged.

h) the slave enters the CONNECTION state after acknowledging the received FHS packet in the slave response packet.


• Initial Conditiona) The IUT is in STANDBY mode.b) Default values are used for:

Page Scan_Window = 18 slots andPage Scan_Interval = 1.28 sec.Scan_Type = Normal Scan



Baseband

• Test Procedurea) The tester pages the slave in the first half of the TX time slot only

by using the slave’s device access code.b) After receiving a response message consisting of the IUT’s device

access code the tester does not send a FHS packet.c) After the pagerespTO timer (in the slave) has expired the tester

does not page the IUT within the following scan period (11,25 ms). The slave returns to the state it was in prior to the first page scan state (STAND BY mode).

d) Step a) and b) shall be repeated.e) After the pagerespTO timer (in the slave) has expired the tester

pages the IUT within the following scan period (11,25 ms).f) After receiving a response message consisting of the IUT’s device

access code the tester sends a FHS packet.g) After receiving the acknowledge of the FHS packet the tester waits

until the newconnectionTO timer has expired.The IUT returns to page scan substate.

h) The tester pages the IUT.i) After receiving a response message the tester sends a FHS

packet.j) After receiving the acknowledgement of the FHS packet the tester

sends a POLL packet.k) The tester receives the confirmation from the slave.



Requirement a) to h) are fulfilled.Requirement a) is checked after step b.Requirement b) is checked after step b.Requirement c) is checked after step g.Requirement d) is checked after step e.Requirement e) is checked after step c.Requirement f) is checked after step i.Requirement g) is checked after step k.Requirement h) is checked after step k.



Baseband

Fail verdict:

Otherwise.

• UncertaintiesThe tester may need to transmit the FHS and POLL packets more than once within pageresTO and newconnectionTO number of slots, respectively.

• NotesN/A.

4.7.2.3 TP/PHYS/PAG/BV-12-C (Page resp 1/2 slot)

Verify that the IUT as slave uses the correct page response procedure when receiving the page message in the second half of the RX time slot.

Only for IUTs supporting page scan:

a) the slave enters the slave response routine and freezes the current clock input to the page and page response hop selection.

b) the slave transmits a response message after receiving his own device access code within the slave’s device access code 625 µs after the beginning of the received page message.

c) the slave uses the slave response sequence for transmission during initial messaging.

d) the slave returns back to the page scan substate for one scan period if nothing was received after pagerespTO.

e) the slave return to the state it was in prior to the first page scan if pagerespTO is exceeded and no page message is received during the additional scan period.

f) the IUT returns to page scan substate when not receiving a POLL packet within newconnectionTO after acknowledging the FHS packet.

g) the slave changes to the master parameter submitted in the FHS packet (BT address and master clock) after the FHS packet has been acknowledged.

h) the slave enters the CONNECTION state after acknowledging the received FHS packet in the slave response packet.




Baseband

• Initial ConditionThe IUT is in STANDBY mode.

• Test Procedurea) The tester page the slave 312,5 µs after the Master TX time slot

has been started (second half of the TX time slot) by using the slave’s device access code.

b) After receiving a response message consisting of the SLAVE’s device access code the tester does not send a FHS packet.

c) After the pagerespTO timer (in the slave) has expired the tester do not pages the IUT within the following scan period (11,25 ms). The slave returns to the state it was in prior to the first page scan state (STAND BY mode).

d) Step a) and b) shall be repeated.e) After the pagerespTO timer (in the slave) has expired the tester

pages the IUT within the following scan period (11,25 ms).f) After receiving a response message consisting of the IUT’s device

access code the tester sends a FHS packet.g) After receiving the acknowledge of the FHS packet the tester waits

until the newconnectionTO timer has expired.The IUT returns to page scan substate.

h) The tester pages the IUT.i) After receiving a response message the tester sends a FHS

packet.j) After receiving the acknowledgement of the FHS packet the tester

sends a POLL packet.k) The tester receives the confirmation from the slave.




Baseband


Requirement a) to h) are fulfilled.Requirement a) is checked after step b.Requirement b) is checked after step b.Requirement c) is checked after step g.Requirement d) is checked after step e.Requirement e) is checked after step c.Requirement f) is checked after step i.Requirement g) is checked after step k.Requirement h) is checked after step k.

Fail verdict:

Otherwise.

• UncertaintiesThe tester may need to transmit the FHS and POLL packets more than once within pageresTO and newconnectionTO number of slots, respectively.

• NotesN/A.

4.7.2.4 TP/PHYS/PAG/BV-14-C (Page scan interval R0)

Verify that the IUT as slave uses the correct page scan interval for paging mode R0 (continuous).

Only for IUTs supporting page scan repetition mode R0.




Baseband

• Initial Conditiona) The tester uses the 79 channel hop scheme.b) The IUT is configured as slave using page scan mode R0.c) If the IUT supports inquiry:

To ensure that the tester can follow the page scan sequence of the slave a procedure has been performed before to get the estimate CLKE of the slave’s BT clock.

If the IUT does not support Inquiry:The tester is paged by the IUT. The clock offset between master and slave clock is calculated in the tester. The clock offset is used in step a) of the test procedure.

d) The IUT is in STAND BY mode. Periodic scan is enabled with HCI_Write_Scan_Enable.

• Test Procedurea) The tester pages the IUT continuously until a response ID packet

is received. The number of pages and the position in the page hop sequence are recorded.

b) The tester does not respond with a FHS packet but waits for one scan period (18 slots) + pagerespTO (8 slots) plus a randomly chosen number of slots between 0 and 1023.

c) Steps a) and b) are performed 100 times.



In step a) of the test procedure, the tester receives a response ID packet on the first page train A in at least 95% of the page procedures.

Fail verdict:

In step a) of the test procedure, the tester receives a response ID packet on the first page train A in less than 95% of the page procedures.




Baseband

LowerTesterSlave

UpperTesterIUT

Master

ACL connection establishedHost Controller data buffers have been checked

ACL packet

BC retransmissions

NULL

(LT_ADDR, Type, FLOW, ARQN, SEQN, HEC)

HCI_ACL_Data_Packet(Conn_Handle, PB = 0b10, BC = 0b01,Data_Total_Length, Data)


HCI_ACL_Data_Packet(Conn_Handle, PB = 0b10, BC = 0b00,Data_Total_Length = 15, Data)




BC retransmissions

LT_ADDR=0, SEQN,LLID=0b10, NBC retransmissions

(SEQN depends on previoustransmitted broadcast packet)

ACL packet

ACL packet

ACL packet

OPTIONAL:Depends on data total lengthin relation to buffer size

HCI Number Of Completed Packets event

(Number_of_Handles, Conn_Handle[i], HC_Num_Of_Completed_Packets[i]





LowerTesterSlave

UpperTesterIUT

Master


ACL packet


LT_ADDR=0, SEQN=1,LLID=0b10, NBC retransmissions

NULL




LT_ADDR=0, SEQN=0,LLID=0b01, N

BC retransmissions

BC retransmissions(SEQN depends on previoustransmitted broadcast packet)

ACL packet

ACL packet

ACL packet








LowerTesterSlave

UpperTesterIUT

Master


ACL packet

BC retransmissions

NULL








BC retransmissions



ACL packet

ACL packet

ACL packet








LowerTesterSlave

UpperTesterIUT

Master


ACL packet



NULL





BC retransmissions


ACL packet

ACL packet

ACL packet








• Notes

None.


Verify that the IUT as slave uses the correct page scan interval for paging mode R1 (≤ 1.28s).

Only for IUTs supporting page scan.




Baseband

[Vol. 2, Part B] Section 8.3.2 on page 136.







b) The tester does not respond with a FHS packet but waits for one scan period (18 slots), pagerespTO (8 slots) and a randomly chosen number of slots between 0 and 2048.




In step a) of the test procedure, the tester receives a response ID packet within 1.28 s after the start of the page for more than 95% of the page procedures.

Fail verdict:

In step a) of the test procedure, the tester receives a response ID packet within 1.28 s after the start of the page for less than 95% of the page procedures.

• Uncertainties



Baseband

N/A.

• NotesNone.

4.7.2.6 TP/PHYS/PAG/BV-17-C (Page scan interval R1 with Interlaced Scan)

Verify that the IUT as slave uses the correct page scan interval for paging mode R1 (≤ 1.28s) when interlaced scan is used during page scanning.

Only for IUTs supporting page scan and interlaced scan.


• Initial Conditiona) The tester uses the 79 channel hop scheme.b) The IUT is configured as slave using page scan mode R1.c) Scan_type = Interlaced Scand) The IUT is in STAND BY mode. Periodic scan is enabled with

HCI_Write_Scan_Enable.



Baseband








Fail verdict:



• NotesIn test procedure step b) since there may be some switching time between two back to back scans, the tester should wait for scan period (18 slots + switching time + 18 slots), pagerespTO (8 slots) and a randomly chosen number of slots between 0 and 2048. It is assumed that no implementation would have the switching time larger than 128-18-18=92 slots.



Baseband


Verify that the IUT as slave uses the correct page scan interval for paging mode R2 (≤ 2.56 s).

Only for IUTs supporting page scan repetition mode R2.













Baseband



Fail verdict:



• NotesNone.

4.7.2.8 TP/PHYS/PAG/BV-19-C (Page scan interval R2 and interlaced scan)

Verify that the IUT as slave uses the correct page scan interval for paging mode R2 (≤ 2.56 s) when interlaced scan is used during page scanning.

Only for IUTs supporting page scan repetition mode R2 and interlaced scan.


• Initial Conditiona) The tester uses the 79 channel hop scheme.b) The IUT is configured as slave using page scan mode R2.c) Scan_type = Interlaced Scan.d) The IUT is in STAND BY mode. Periodic scan is enabled with

HCI_Write_Scan_Enable.



Baseband








Fail verdict:



• NotesIn test procedure step b) since there may be some switching time between two back to back scans, the tester should wait for scan period (18 slots + switching time + 18 slots), pagerespTO (8 slots) and a randomly chosen number of slots between 0 and 2048. It is assumed that no implementation would have the switching time larger than 128-18-18=92 slots.

4.8 CONNECTION


• To verify that the behavior in the connection state is correct.

4.8.1 Connection State - Master




Baseband

• To verify that the master works correctly in the connection state.




4.8.1.2 TP/PROT/CON/BV-01-C (POLL at start up)

Verify that the IUT configured as master sends a POLL packet at the start of a new connection and initializes the ARQN bit set to NAK.

Further verify that the master initializes the SEQN bit of the first CRC data packet to 1.

• Reference[Vol. 2, Part B] Section 7.6.1 on page 124.[Vol. 2, Part B] Section 7.6.2 on page 127.[Vol. 2, Part B] Section 8.3.3.1 on page 140.[Vol. 2, Part B] Section 8.5 on page 148.


Configured as Slave in state STANDBY.

IUT:Configured as Master in state STANDBY.



Baseband

• Test Procedure

Figure 4.50: TP/PROT/CON/BV-01-C (POLL at start up)

The tester sends an HCI command via the UT to instruct the IUT to carry out page.

Master

IUT

Slave


Tester: configured as Slave in state STANDBY.

IUT: configured as Master in state STANDBY.

ID

(Slaves device access code)

ID


ID


FHS


FLOW, HEC, Parity bits, LAP, Undefined,

SR, SP='10'B, UAP, NAP, Class of device,

LT_ADDR, CLK27-2, Page Scan Mode)

ID


POLL

(Access code, LT_ADDR, TYPE,


NULL



DM1

HCI_Create_Connection

(BD_ADDR, Packet_Type,

Page_Scan_Repetition_Mode, Reserved,

Clock_Offset, Allow_Role_Switch)

Command Status event

(Status, Num_HCI_Command_Packets,

Command_Opcode)

Start of paging.



SEQN bit set to 1.




Baseband

HCI_Create_Connection:

BD_ADDR: BD_ADDR of the tester.Packet_Type: '330E'H.Page_Scan_Repetition_Mode: '01'H.Reserved: '00'H.Clock_Offset: As required.Allow_Role_Switch: As required by the IUT.

Then the tester verifies that the IUT sends an ID packet containing the slave's device access code.Upon reception of an ID packet the tester transmits an ID packet back also containing the slave's device access code.Then the tester verifies that the IUT transmits a FHS packet.After having received the FHS packet from the IUT the tester transmits an ID packet (slave's devices access code) again to indicate the reception from the former FHS packet.The tester verifies that the IUT sends a POLL packet with the ARQN bit set to NAK.The tester confirms the reception with a NULL packet.The tester verifies that the IUT sends a DM1 packet with the SEQN bit set to 1.



The IUT sends at the start of a new connection a POLL packet with the ARQN bit set to NAK.The IUT initializes the SEQN bit of the first CRC data packet to 1.

Fail verdict:

The IUT does not send at the start of a new connection a POLL packet.The IUT sends at the start of a new connection a POLL packet with the ARQN bit set to ACK.The IUT does not initialize the SEQN bit of the first CRC data packet to 1.



Baseband


• NotesA FHS packet can already arrive 312,5 µs after the arrival of the page mes-sage, and not 625 µs as is usually the case in the RX/TX timing.

4.8.1.3 TP/PROT/CON/BV-02-C (Polling slave)

Verify that the IUT configured as master transmits periodical to keep the slave synchronized on the channel.







Baseband

• Test Procedure

Figure 4.51: TP/PROT/CON/BV-02-C (Polling slave)

The tester verifies that the IUT periodically transmits with an interval of max-imum 40 slots (default value for POLL interval as stated in LMP Specification in Table 5.5).The test is carried out for a time of 10 seconds.



The master transmits periodically with an interval of maximum 40 slots for a time of 10 seconds.

Master

IUT

Slave




POLL



NULL



POLL



NULL



10 seconds duration for

Test Purpose.



Baseband

Fail verdict:

The master does not transmit periodically with an interval of maximum 40 slots for a time of 10 seconds.


• NotesIt is assumed that the IUT does not exceed the default poll interval of 40 slots.

4.8.1.4 TP/PROT/CON/BV-03-C (Wrong UAP)

Verify that the IUT configured as master upon reception of a packet with the same access code - i.e., an access code of a device owning the same LAP but different UAP - passes the access code test, it will disregard the packet after HEC and CRC tests when the UAP do not match.




IUT:Configured as Master state CONNECTION (active mode, ACL link).



Baseband

• Test Procedure

Figure 4.52: TP/PROT/CON/BV-03-C (Wrong UAP)

Upon reception of a POLL packet the tester sends a DM1 packet containing a LMP_features_req message with a wrong UAP.The tester verifies that the IUT discards the packet and does not response to the LMP_features_req message for the next 30s.



The IUT discards the packet and does not response to the LMP_features_req message.

30s

Master

IUT

Slave




POLL


FLOW, ARQN, SEQN, FLOW, HEC)

Upper Tester

DM1


any_ACL_packet


FLOW, HEC)

IUR discards packet.

With wrong UAP.



Baseband

Fail verdict:

The IUT does not discard the packet or responses to the LMP_features_req message.


• NotesN/A.

4.8.1.5 TP/PROT/CON/BV-04-C (Change from DV to HV1)

Verify that the IUT automatically change from DV packet type to HV1 packet type used before the mixed data/voice transmission when there is no data to be sent.




Configured as Slave.

IUT:Configured as Master.An SCO link is established. The only features supported by the tester are SCO-link, µ-law, A-law, CVSD and transparent data.



Baseband

• Test Procedure

Figure 4.53: TP/PROT/CON/BV-04-C (Change from DV to HV1)

Master

IUT

Slave


LMP features and version info have been exchanged.


OPTIONAL

OPTIONAL

HV1


HV1


DV


LMP_features_req (features=0x09C800))

DV


LMP_features_res (features))

HV1


HV1









Status=0x00)












Several HV1 packets might

be exchanged before the DV

packet is transmitted.

The IUT might replace DV

packets with DM1 packets.

There might be other DV or

DM1 packets sent from the

IUT but HV1 packets shall

be sent frequently.



Baseband

The tester verifies that the IUT transmits HV1 packets to the tester.The tester responds with HV1 packets in the slave to master slots.The tester transmits a DV packet containing LMP_features_req to the IUT in order to force the IUT to send a DV packet containing LMP_features_ res.Upon reception of a DV packet the tester responds with a HV1 packet.The tester verifies that the IUT automatically changes from DV packet type to HV1 packet type.



The IUT changes automatically from DV packet type to HV1 packet type.

Fail verdict:

The IUT does not change automatically from DV packet type to HV1 packet type.

• UncertaintiesThere is no possibility written in the core specification to force the IUT to send a DV packet. For IUTs using DV packets it can be checked whether they are received. If no DV packet is returned the IUT must return a DM1 packet. The IUT might transmit unsolicited LMP signaling changing the intended test procedure. This risk is minimized by having the tester transmit LMP_features_req and LMP_version_req immediately after ACL connection establishment and only indicate support for the minimum number of features required to make the test case work.







Baseband

4.8.2 Connection State - Slave


• To verify that the slave works correctly in the connection state.




4.8.2.2 TP/PROT/CON/BV-05-C (POLL at start up)

Verify that the IUT configured as slave confirms the reception of the first POLL packet sent by the master after start up of a new connection and initializes the ARQN bit set to NAK.

Further verify that the IUT initializes the SEQN bit of the first CRC data packet set to 1.

• Reference[Vol. 2, Part B] Section 6.5.1.3 on page 106.[Vol. 2, Part B] Section 7.6.1 on page 124.[Vol. 2, Part B] Section 7.6.2 on page 127.[Vol. 2, Part B] Section 8.5 on page 148.


Configured as Master in state STANDBY. Inquiry is performed successfully.

IUT:Configured as Slave in state STANDBY. Inquiry scan is performed successfully.



Baseband

• Test Procedure

Figure 4.54: TP/PROT/CON/BV-05-C (POLL at start up)

Slave

IUT

Master


Tester: configured as Master in state STANDBY. Inquiry is performed successfully.

IUT: configured as Slave in state STANDBY. Inquiry scan is performed successfully.

ID

(slaves device access code)

ID


ID


FHS

(Parity bits, LAP, Undefined, SR,

SP='10'B,UAP, NAP, Class of device,

LT_ADDR,CLK27-2, Page scan mode)

ID


POLL



any_ACL_packet

DM1

(LMP_host_connection_req)

DM1

(LMP_accepted or LMP_not_accepted)

HCI_Write_Scan_Enable

(Scan_Enable)

HCI_Command_Complete_event

(Num_HCI_Command_Packets,

Command_Opcode,

return_Parameters)

Start Page scan.

Start paging.

Page response.

ARQN bit set to NAK

Confirmation of former

POLL packet.

ARQN bit set to to NAK.

SEQN bit set to 1.

SEQN bit set to 1.




Baseband

The tester sends a HCI command via the UT to instruct the IUT to carry out page scan.HCI_Write_Scan_Enable:

Scan_Enable: 0x02.

The tester repeatedly transmits an ID packet (slave's device access code) in different hop channels to page the slave.Then the tester verifies that the IUT sends an ID packet containing the slave's device access code.Upon reception of the ID packet the tester transmits a FHS packet.FHS:Access code:

Preamble: 1010 or 0101 sequence, depending on whether the LSB of the following sync word is 1 or 0, respectively.Sync word: Derived from the 24 bit address (LAP) of the slave (DAC).Trailer: 1010 or 0101 sequence, depending on whether the MSB of the sync word is 1 or 0, respectively.

Packet Header:

LT_ADDR: Set to all-zero.TYPE: '0010'B.FLOW: '1'B.ARQN: '1'B.SEQN: Any value because contents of the SEQN bit in the FHS packet should not be checked.HEC: Generated by the polynom '647'O in respect to the UAP of the master.



Baseband

FHS Payload:

Parity bits: First 34-bit of the sync word of the access code.LAP: LAP of the tester.Undefined: Any value.SR: '00'B.SP: ‘10'B.UAP: UAP of the tester.NAP: NAP of the tester.Class of device: Not define yet; any value.LT_ADDR: Logical Transport Address the IUT shall use.CLK27-2: Current value of the system clock of the tester.Page Scan Mode: '000'B.

After having received the FHS packet of the tester the IUT transmits an ID packet (slave's device access code only) again to indicate the reception of the former FHS packet.The tester sends a POLL packet in the next master to slave slot.

POLL packet:

LT_ADDR: Logical Transport Address of the IUT.TYPE: '0001'B.FLOW: '1'B.ARQN: Depends on the reception of the former packet.SEQN: Any value.HEC: UAP of the master device address.

Then the tester verifies that the IUT confirms the reception of the former POLL packet with any ACL packet with the ARQN bit set to NAK.The tester sends a DM1 packet containing a LMP_host_connection_req message with the SEQN bit set to 1.The tester verifies that the IUT sends a DM1 packet with the SEQN bit set to 1.




Baseband


The IUT confirms the reception of the POLL packet after start up with the ARQN bit set to NAK.The IUT initializes the SEQN bit of the first CRC data packet to 1.

Fail verdict:

The IUT does not confirm the reception of the POLL packet after start up.The IUT sets the ARQN bit to ACK after the reception of the first POLL packet.The IUT does not initialize the SEQN bit of the first CRC data packet to 1.


• NotesN/A.

4.8.2.3 TP/PROT/CON/BV-08-C (Wrong UAP)

Verify that when a packet with the same access code - i.e., an access code of a device owning the same LAP but different UAP - passes the access code test, it will disregard the packet after HEC and CRC tests when the UAP do not match.







Baseband

• Test Procedure

Figure 4.55: TP/PROT/CON/BV-08-C (Wrong UAP)

The tester sends a DM1 packet containing a LMP_features_req message with a wrong UAP to the IUT.The tester verifies that the IUT discards the packet and verifies that the IUT does not response to the LMP_features_req message.



The IUT discards the packet and does not response to the LMP_features_req message.

Fail verdict:

The IUT does not discard the packet or responses to the LMP_features_req message.

30s

Slave

IUT

Master




DM1


IUT discards packet.

With wrong UAP.



Baseband


• NotesN/A.

4.8.2.4 TP/PROT/CON/BV-09-C (Change from DV to HV1)

Verify that the IUT automatically changes from DV packet type to HV1 packet type used before the mixed data/voice transmission when there is no data to be sent.





IUT:Configured as Slave.An SCO connection is established. The only features supported by the tester are SCO-link, µ-law, A-law, CVSD and transparent data.



Baseband

• Test Procedure

Figure 4.56: TP/PROT/CON/BV-09-C (Change from DV to HV1)

Slave

IUT

Master


OPTIONAL

OPTIONAL

HV1


HV1


DV


LMP_features_req (features=0x09C800))

DV


LMP_features_res (features))

HV1


HV1


LMP features and version info have been exchanged.






Host_Total_Num_Synchronous_Data_Packets,



Status=0x00)





HC_Synchronous_Data_Packet_Length,

HC_Total_Num_ACL_Data_Packets,

HC_Total_Num_Synchronous_Data_Packets,





Several HV1 packets might be

exchanged before the DV packet

is transmitted. The IUT might

replace DV packets with DM1

packets.

There might be other DV or DM1

packets sent from the IUT but HV1

packets shall be sent frequently.



Baseband

The tester transmits a HV1 packet to the IUT.The tester verifies that the IUT responds with a HV1 packet in the following slave to master slot.The tester sends transmits LMP_features_req to the IUT in order to force the IUT to transmit a DV packet containing LMP_Features_ res.The tester verifies that the IUT transmits a DV packet.The tester verifies that the IUT automatically changes from DV packet type to HV1 packet type.



The IUT changes automatically from DV packet type to HV1 packet type.

Fail verdict:

The IUT does not change automatically from DV packet type to HV1 packet type.

• UncertaintiesThere is no possibility written in the core specification to force the IUT to send a DV packet. For IUTs using DV packets it can be checked whether they are received. If no DV packet is returned the IUT must return a DM1 packet. The IUT might transmit unsolicited LMP signaling changing the intended test procedure. This risk is minimized by having the tester transmit LMP_features_req and LMP_version_req immediately after ACL connection establishment and only indicate support for the minimum number of features required to make the test case work.







Baseband

4.9 PICONET


• To verify the behavior in a piconet.

4.9.1 Piconet - Master


• To verify that the Master works correctly in the piconet.




4.9.1.2 TP/PROT/PIC/BV-03-C (Broadcast packets)

Verify that broadcast packets are repeated a fixed number of times.

Verify that broadcast packets carrying L2CAP start packets use the indication LLID = 0b10.Verify that broadcast packets have a separate sequence number-ing.

Only applicable for IUTs supporting broadcast messages.


• Initial ConditionThe IUT is master and the tester is slave. An ACL connection is established using only 1-slot packets. The Host Controller data buffers have been checked. The number of retransmissions (NBC) shall be declared as PIXIT.The tester does not support any features (features= 0x0000000000000000).



Baseband

• Test Procedure

Figure 4.57: TP/PROT/PIC/BV-03-C (Broadcast packets)

The tester sends HCI_ACL_Data packets alternating broadcast and point-to-point. The tester sends the first broadcast HCI ACL Data packet with payload length 28 bytes to force the IUT to split the data over at least 2 BB packets. The remaining packets are sent with payload size 15 bytes. If the IUT buffer size is less than 28 bytes the upper tester uses the longest possible data payload that fits for the first packet and the IUT might not split the data over several BB packets. After each HCI_ACL_Data packet the upper tester waits for the HCI Number Of Completed Packets Event before sending the next HCI_ACL_Data

LowerTesterSlave

UpperTesterIUT

Master


ACL packet

BC retransmissions

NULL








BC retransmissions



ACL packet

ACL packet

ACL packet








LowerTesterSlave

UpperTesterIUT

Master


ACL packet



NULL





BC retransmissions


ACL packet

ACL packet

ACL packet








LowerTesterSlave

UpperTesterIUT

Master


ACL packet

BC retransmissions

NULL








BC retransmissions



ACL packet

ACL packet

ACL packet








LowerTesterSlave

UpperTesterIUT

Master


ACL packet



NULL





BC retransmissions


ACL packet

ACL packet

ACL packet










Baseband

packet..


Expected OutcomePass verdict:

The tester receives the broadcast packets repeated maximum NBC times as specified in PIXIT.Broadcast packets have a sequence numbering separate from point-to-point packets.The transmitted broadcast packets have correct values for LLID.

Fail verdict:

The tester detects NBC larger than the value given in PIXIT.Broadcast packets have wrong sequence numbering or LLID or LT_ADDR.

• UncertaintiesThe Host Controller might not split HCI ACL Data packets in several BB packets if the max buffer size is less than 28 bytes. The tester might miss a packet so the number of repetitions recorded might be less than NBC.

• Notes

ACL SEQN

Broad- cast SEQN

ACL SEQN

Broad- cast SEQN

ACL SEQN

Broad- cast SEQN

ACL SEQN

Broad- cast SEQN

Last ACL SEQN

0 0 1 1

First broad-cast

1 10

1 10

ACL data

1 1 0 0

Broad-cast

0 1 0 1

Table 4.2: Sequence Numbers



Baseband

The connection handle used by the upper tester for broadcast data is differ-ent from the connection handle used for point-to-point PDUs. The host con-troller can only use DM1 and DH1 packets for broadcast ACL data because the tester does not support longer packets. It is unlikely an IUT has a max buffer less than 28 bytes so most IUTs will split the first broadcast packet into multiple BB packets. A broadcast packet from the IUT may be transmit-ted once more than specified in the HCI command.




4.9.2 Piconet - Slave


• To verify that the slave works correctly in the piconet.




4.9.2.2 TP/PROT/PIC/BV-04-C (Broadcast NAK)

Verify that broadcast messages are not acknowledged. Only applicable for IUTs supporting broadcast messages.


• Initial ConditionThe IUT is slave and the tester is master. ACL connection established using only DM1 packets. The tester does not support any features (features = 0x0000000000000000).



Baseband

• Test Procedure

Figure 4.58: TP/PROT/PIC/BV-04-C

The tester transmits LMP_quality_of_service to notify the IUT of poll interval and NBC.

The tester transmits a POLL packet and stores the received ARQN bit (ARQN1).

Slave

IUT

Master


ACL connection established using only DM1 packets.

DM1

(LMP_quality_of_service (poll interval=2,

NBC

=1))

NULL or DM1


SEQN, HEC)

DM1

POLL


SEQN, HEC)

NULL or DM1


SEQN, HEC)

POLL


SEQN, HEC)

NULL or DM1


SEQN, HEC)

DM1

HCI ACL Data packet

(Conn_Handle, PB=0b10, BC=0b01,

Data_total_length, Data)

Broadcast packet with 15 bytes

payload, LLID=0b10.

POLL


SEQN, HEC)

NULL or DM1


SEQN, HEC)

POLL


SEQN, HEC)

NULL or DM1


SEQN, HEC)

Broadcast packet with

uncorrectable errors in the

payload, LLID=0b10.



Baseband

The tester transmits a broadcast packet NBC times with data payload cor-rectly inserted.The tester transmits a POLL packet and stores the received ARQN bit (ARQN2).The tester transmits a POLL packet again and stores the received ARQN bit (ARQN3).The tester transmits a broadcast packet NBC times with uncorrectable errors in the data payload.The tester transmits a POLL packet and stores the received ARQN bit (ARQN4).



ARQN1=ARQN2 and ARQN3=ARQN4. The IUT does not respond to the broadcast packets.

Fail verdict:

ARQN1 not equal to ARQN2 or ARQN3 not equal to ARQN4. The IUT responds to the broadcast packets.

Inconclusive Verdict:If the IUT misses any of the POLL packets, the tester will not receive a response in the following slot. If the IUT does not receive the correct broadcast packet, the packet will not be received at the upper tester. If either of these events occur, the test case is inconclusive.

• UncertaintiesThe tester might transmit a DM1 packet instead of POLL affecting the acknowledgment mechanism. Packets might get lost. If a fail verdict is set the test case should be repeated a few times to possibly get a test session without lost or unintentional DM1 packets. An IUT with a very high packet error rate might result in a fail verdict.

• NotesN/A.



Baseband






Baseband

5 TEST CASE MAPPING

1. Fill out the column "Support".

2. If the Baseband feature BB, y/x (see in "Item") is supported, mark it in the "Support" field, where y corresponds to the table and x corresponds to the feature number in the Baseband's ICS table.

3. If a feature is supported corresponding to the logical connection under "Item", the corresponding test case(s) are applicable.

For Baseband features refer to the PICS proforma for Baseband (BB) docu-ment.

For purpose and structure of the PICS/PIXIT proforma and instructions for completing the PICS/PIXIT proforma refer to the Bluetooth ICS and IXIT pro-forma document.

Test Case Mapping 14 October 2005 221


Baseband

Selection Expression Feature Baseband Support Test Case

Test Case Applicable

Basic requirements

BB, 1/1 TP/PHYS/FRE/BV-01-CTP/PHYS/TRX/BV-01-CTP/PHYS/TRX/BV-03-CTP/PHYS/TRX/BV-04-CTP/PHYS/TRX/BV-05-CTP/PROT/COD/BV-11-CTP/PROT/COD/BV-12-CTP/PROT/COD/BV-16-CTP/PROT/ARQ/BV-01-CTP/PROT/ARQ/BV-02-CTP/PROT/ARQ/BV-03-CTP/PROT/ARQ/BV-04-CTP/PROT/ARQ/BV-05-CTP/PROT/ARQ/BV-06-CTP/PROT/ARQ/BV-08-CTP/PROT/ARQ/BV-10-CTP/PROT/ARQ/BV-14-CTP/PROT/ARQ/BV-15-CTP/PROT/ARQ/BV-16-CTP/PROT/ARQ/BV-18-CTP/PROT/ARQ/BV-19-CTP/PROT/ARQ/BV-23-CTP/PROT/CON/BV-01-CTP/PROT/CON/BV-02-CTP/PROT/CON/BV-03-CTP/PROT/CON/BV-05-CTP/PROT/CON/BV-08-C

AFH

BB, 1/2 Adaptive frequency hopping

TP/PHYS/FRE/BV-02-C

BB, 1/2 AND LM, 2/6 AND LM, 26/1

AFH and M/S switch TP/PHYS/FRE/BV-03-C

Table 5.1: Test Case Mapping

222 14 October 2005 Test Case Mapping


Baseband

Link Types

BB, 2/1 Support of ACL link N/A

BB, 2/2 Support of SCO link TP/PROT/COD/BV-01-CTP/PROT/COD/BV-04-CTP/PROT/COD/BV-14-CTP/PROT/ARQ/BV-25-CTP/PROT/ARQ/BV-26-CTP/PROT/CON/BV-04-CTP/PROT/CON/BV-09-C

SCO link support

BB, 3/1 SCO links to same Slave

N/A

BB, 3/2 SCO links to different Slaves

N/A

BB, 3/4 SCO links from dif-ferent Masters

N/A

Common packet types

BB, 4/1 Support of ID packet type

N/A

BB, 4/2 Support of NULL packet type

N/A

BB, 4/3 Support of POLL packet type

N/A

BB, 4/4 Support of FHS packet type

N/A

BB, 4/5 Support of DM1 packet type

N/A

ACL packet types

BB, 5/1 Support of DH1 packet type

TP/PROT/COD/BV-05-C


TP/PROT/COD/BV-06-C


TP/PROT/COD/BV-07-C


TP/PROT/COD/BV-08-C






Baseband


TP/PROT/COD/BV-09-C

BB, 5/6 Support of AUX1 packet type

TP/PROT/COD/BV-10-C

SCO packet types

BB, 6/1 Support of HV1 packet type

N/A

BB, 6/2 AND BB, 2/2

Support of HV2 packet type

TP/PROT/COD/BV-02-C

BB, 6/3 AND BB, 2/2

Support of HV3 packet type

TP/PROT/COD/BV-03-C

BB, 6/4 Support of DV packet type

N/A

eSCO packet types

BB, 6/5 EV3 packet TP/PROT/COD/BV-17-CTP/PROT/ARQ/BV-27-CTP/PROT/ARQ/BV-28-CTP/PROT/ARQ/BV-29-CTP/PROT/ARQ/BV-30-CTP/PROT/ARQ/BV-31-CTP/PROT/ARQ/BV-32-C

BB, 6/6 EV4 packet TP/PROT/COD/BV-18-C

BB, 6/7 EV5 packet TP/PROT/COD/BV-19-C

Page procedures

BB, 7/1 Supports paging TP/PHYS/PAG/BV-01-CTP/PHYS/PAG/BV-03-CTP/PHYS/PAG/BV-05-C

BB, 7/2 Supports page scan TP/PHYS/PAG/BV-10-CTP/PHYS/PAG/BV-12-C

BB, 9/2 AND BB, 7/5

Page scan interval R1 with interlaced scan

TP/PHYS/PAG/BV-17-C

BB, 9/3 AND BB, 7/5

Page scan interval R2 and interlaced scan

TP/PHYS/PAG/BV-19-C






Baseband

Paging modes

BB, 9/1 Supports paging mode R0

TP/PHYS/PAG/BV-14-C


TP/PHYS/PAG/BV-16-C


TP/PHYS/PAG/BV-18-C

Inquiry procedures

BB, 10/1 Supports inquiry TP/PHYS/INQ/BV-03-C

BB, 10/2 Supports inquiry scan

TP/PHYS/INQ/BV-10-CTP/PHYS/INQ/BV-14-C

BB, 10/2 AND BB, 10/6

Interlaced inquiry scan

TP/PHYS/INQ/BV-15-C

BB, 10/5 AND BB, 10/1

Supports the dedi-cated inquiry access code

TP/PHYS/INQ/BV-01-C

Piconet capabilities

BB, 11/1 Broadcast messages TP/PROT/PIC/BV-03-CTP/PROT/PIC/BV-04-C

Enhanced Data Rate

BB:1a/2 OR BB:1a/3

Enhanced Data Rate guard time

TP/PHYS/TRX/BV-06-E

BB:1a/2 OR BB:1a/3

Enhanced Data Rate synchronization sequence and trailer

TP/PHYS/TRX/BV-07-E

eSCO packet types (2 Mbps)

BB:6a/1 Support of 2-EV3 packet type

TP/PROT/COD/BV-20-C


TP/PROT/COD/BV-21-C

eSCO packet types (3 Mbps)


TP/PROT/COD/BV-22-C


TP/PROT/COD/BV-23-C






Baseband

ACL packet types (2 Mbps)

BB:5a/1 Support of 2-DH1 packet type

TP/PROT/COD/BV-24-C


TP/PROT/COD/BV-25-C


TP/PROT/COD/BV-26-C

ACL packet types (3 Mbps)


TP/PROT/COD/BV-27-C


TP/PROT/COD/BV-28-C


TP/PROT/COD/BV-29-C






Baseband

6 PROVISIONAL BASEBAND TESTING (EDR)

Measurement of baseband performance in accordance with the baseband test cases may not be possible until dedicated test equipment is available. There-fore, certain deviations from the specified test procedures are permitted for an interim period. These deviations cease to be permitted for a particular test case when this test case is made active in Category A as indicated in a released TCRL.

The permitted test procedure deviations during the interim period are as:

• Non loop back testing may be used.

• The EUT may be configured for a test case by any suitable means.

• Frequency hopping may be disabled.

For each test case, all deviations from the specified test procedure shall be documented by the manufacturer.

Provisional Baseband Testing (EDR) 14 October 2005 227


Baseband

228 14 October 2005 Provisional Baseband Testing (EDR)

专注于微波、射频、天线设计人才的培养易迪拓培训网址：http://www.edatop.com

射频和天线设计培训课程推荐

易迪拓培训(www.edatop.com)由数名来自于研发第一线的资深工程师发起成立，致力并专注于微

波、射频、天线设计研发人才的培养；我们于 2006 年整合合并微波 EDA 网(www.mweda.com)，现

已发展成为国内最大的微波射频和天线设计人才培养基地，成功推出多套微波射频以及天线设计经典

培训课程和 ADS、HFSS 等专业软件使用培训课程，广受客户好评；并先后与人民邮电出版社、电子

工业出版社合作出版了多本专业图书，帮助数万名工程师提升了专业技术能力。客户遍布中兴通讯、

研通高频、埃威航电、国人通信等多家国内知名公司，以及台湾工业技术研究院、永业科技、全一电

子等多家台湾地区企业。

易迪拓培训推荐课程列表： http://www.edatop.com/peixun/tuijian/

射频工程师养成培训课程套装

该套装精选了射频专业基础培训课程、射频仿真设计培训课程和射频电

路测量培训课程三个类别共 30 门视频培训课程和 3 本图书教材；旨在

引领学员全面学习一个射频工程师需要熟悉、理解和掌握的专业知识和

研发设计能力。通过套装的学习，能够让学员完全达到和胜任一个合格

的射频工程师的要求…

课程网址：http://www.edatop.com/peixun/rfe/110.html

手机天线设计培训视频课程

该套课程全面讲授了当前手机天线相关设计技术，内容涵盖了早期的

外置螺旋手机天线设计，最常用的几种手机内置天线类型——如

monopole 天线、PIFA 天线、Loop 天线和 FICA 天线的设计，以及当前

高端智能手机中较常用的金属边框和全金属外壳手机天线的设计；通

过该套课程的学习，可以帮助您快速、全面、系统地学习、了解和掌

握各种类型的手机天线设计，以及天线及其匹配电路的设计和调试...

课程网址： http://www.edatop.com/peixun/antenna/133.html

WiFi 和蓝牙天线设计培训课程

该套课程是李明洋老师应邀给惠普 (HP)公司工程师讲授的 3 天员工内

训课程录像，课程内容是李明洋老师十多年工作经验积累和总结，主要

讲解了 WiFi 天线设计、HFSS 天线设计软件的使用，匹配电路设计调

试、矢量网络分析仪的使用操作、WiFi 射频电路和 PCB Layout 知识，

以及 EMC 问题的分析解决思路等内容。对于正在从事射频设计和天线

设计领域工作的您，绝对值得拥有和学习！…

课程网址：http://www.edatop.com/peixun/antenna/134.html

`

专注于微波、射频、天线设计人才的培养易迪拓培训网址：http://www.edatop.com

CST 学习培训课程套装

该培训套装由易迪拓培训联合微波 EDA 网共同推出，是最全面、系统、

专业的 CST 微波工作室培训课程套装，所有课程都由经验丰富的专家授

课，视频教学，可以帮助您从零开始，全面系统地学习 CST 微波工作的

各项功能及其在微波射频、天线设计等领域的设计应用。且购买该套装，

还可超值赠送 3 个月免费学习答疑…

课程网址：http://www.edatop.com/peixun/cst/24.html

HFSS 学习培训课程套装

该套课程套装包含了本站全部 HFSS 培训课程，是迄今国内最全面、最

专业的 HFSS 培训教程套装，可以帮助您从零开始，全面深入学习 HFSS

的各项功能和在多个方面的工程应用。购买套装，更可超值赠送 3 个月

免费学习答疑，随时解答您学习过程中遇到的棘手问题，让您的 HFSS

学习更加轻松顺畅…

课程网址：http://www.edatop.com/peixun/hfss/11.html

ADS 学习培训课程套装

该套装是迄今国内最全面、最权威的 ADS 培训教程，共包含 10 门 ADS

学习培训课程。课程是由具有多年 ADS 使用经验的微波射频与通信系统

设计领域资深专家讲解，并多结合设计实例，由浅入深、详细而又全面

地讲解了 ADS 在微波射频电路设计、通信系统设计和电磁仿真设计方面

的内容。能让您在最短的时间内学会使用 ADS，迅速提升个人技术能力，

把 ADS 真正应用到实际研发工作中去，成为 ADS 设计专家...

课程网址： http://www.edatop.com/peixun/ads/13.html

我们的课程优势：

※ 成立于 2004 年，10 多年丰富的行业经验，

※ 一直致力并专注于微波射频和天线设计工程师的培养，更了解该行业对人才的要求

※ 经验丰富的一线资深工程师讲授，结合实际工程案例，直观、实用、易学

联系我们：

※ 易迪拓培训官网：http://www.edatop.com

※ 微波 EDA 网：http://www.mweda.com

※ 官方淘宝店：http://shop36920890.taobao.com

专注于微波、射频、天线设计人才的培养

官方网址：http://www.edatop.com 易迪拓培训淘宝网店：http://shop36920890.taobao.com

baseband - edatop.com · part b baseband test suite structure (tss) and test purposes (tp) system...

Documents