Mesh Profile (MESH) / Test Suite
Bluetooth SIG Proprietary Page 19 of 439
In any case, where a member finds an issue with the test plan generated by Launch Studio, the test case
as described in the test suite, or with the test system utilized, the member is required to notify the
responsible party via an erratum request such that the issue may be addressed.
4.1.3 Pass/Fail verdict conventions
Each test case has an Expected Outcome section. The IUT is granted the Pass verdict when all the
detailed pass criteria conditions within the Expected Outcome section are met.
The convention in this test suite is that, unless there is a specific set of fail conditions outlined in the test
case, the IUT fails the test case as soon as one of the pass criteria conditions cannot be met. If this
occurs, the outcome of the test is a Fail verdict.
4.2 Setup preambles
4.2.1 State: Node PB-ADV Link Established
1. The IUT is induced to send Unprovisioned Device beacons with the Beacon Type set to 0x00
(Unprovisioned Device), the Device UUID value set to the IUT’s Device UUID, and the OOB
Information field has the bit set to a non-RFU value supported by the manufacturer.
2. The Lower Tester scans for Unprovisioned Device beacons until it receives a beacon matching
the Device UUID of the IUT.
3. The Lower Tester begins to periodically advertise PB-ADV PDU containing a Link Open
message. The mesh packet containing the PB-ADV PDU has the Length field set to the length of
the AD Type and Contents, the AD Type set to «Mesh Provisioning», and the Contents set to the
PB-ADV PDU. The PB-ADV PDU containing the Link Open message has the Link ID value set to
a newly allocated random Link ID, the Transaction Number set to 0, and the Generic Provisioning
PDU containing the Link Open message. The Generic Provisioning PDU has a BearerOpcode
value of 0x00, the GPCF field is set to 0b11, and the Link Open message parameters contain the
Device UUID field equal to the Device UUID of the IUT.
4. The Lower Tester receives a Link Ack message from the IUT before the link establishment
timeout. The mesh packet containing the PB-ADV PDU has the Length field set to the length of
the AD Type and Contents and the AD Type set to «Mesh Provisioning». The PB-ADV PDU
containing the Link Ack message has a BearerOpcode value of 0x01, the GPCF field is set to
0b11, the Generic Provisioning Payload is zero length, the Link ID is set to the value sent in the
Link Open message, the Transaction Number value is set to 0x00, and the Link Ack message has
no parameters.
4.2.2 State: Provisioner PB-ADV Link Established
1. The IUT is induced to periodically advertise a PB-ADV PDU containing a Link Open message.
The mesh packet containing the PB-ADV PDU has the Length field set to the length of the AD
Type and Contents and the AD Type set to «Mesh Provisioning». The PB-ADV PDU containing
the Link Open message has a Link ID value set to a newly allocated random Link ID, the
Transaction Number set to 0, and the Generic Provisioning PDU containing the Link Open
message. The Generic Provisioning PDU has a BearerOpcode value of 0x00, the GPCF field is
set to 0b11, and the Link Open message parameters contain the Device UUID field equal to the
Device UUID of the Lower Tester as supplied in the IXIT [6].
2. The Lower Tester detects the PB-ADV PDU advertised by the IUT.
3. The Lower Tester periodically advertises a Link Ack message containing the newly allocated Link
ID sent in step 1. The Lower Tester continues to advertise for at least 5 seconds to ensure the
message is received by the IUT.