Bluetooth Network Encapsulation (BNEP) Protocol Test Cases - Rev0.95a

BNEP Test Cases
Bluetooth Network Encapsulation

Protocol (BNEP) Test Cases
Abstract:
The Bluetooth Networking Encapsulation Protocol (BNEP) test cases document
contains all of the test cases for testing conformance to the BNEP specification.
Introduction
June 26, 2001
Page 1
Bluetooth Network Encapsulation Protocol (BNEP) Test Cases
Page 2 of 2
Revision 0.95a
Disclaimer and copyright notice

The copyright in these specifications is owned by the Promoter Members of Bluetooth
SIG, Inc. (Bluetooth SIG). Use of these specifications and any related intellectual
property (collectively, the Specification), is governed by the Promoters Membership
Agreement among the Promoter Members and Bluetooth SIG (the Promoters
Agreement), certain membership agreements between Bluetooth SIG and its Adopter
and Associate Members (the Membership Agreements) and the Bluetooth
Specification Early Adopters Agreements (1.2 Early Adopters Agreements) among
Early Adopter members of the unincorporated Bluetooth special interest group and the
Promoter Members (the Early Adopters Agreement). Certain rights and obligations
of the Promoter Members under the Early Adopters Agreements have been assigned to
Bluetooth SIG by the Promoter Members.
Use of the Specification by anyone who is not a member of Bluetooth SIG or a party
to an Early Adopters Agreement (each such person or party, a Member), is
prohibited. The legal rights and obligations of each Member are governed by their
applicable Membership Agreement, Early Adopters Agreement or Promoters
Agreement.
No license, express or implied, by estoppel or otherwise, to any
intellectual property rights are granted herein.
Any use of the Specification not in compliance with the terms of the applicable
Membership Agreement, Early Adopters Agreement or Promoters Agreement is
prohibited and any such prohibited use may result in termination of the applicable
Membership Agreement or Early Adopters Agreement and other liability permitted
by the applicable agreement or by applicable law to Bluetooth SIG or any of its
members for patent, copyright and/or trademark infringement.
THE SPECIFICATION IS PROVIDED AS IS WITH NO WARRANTIES
WHATSOEVER, INCLUDING ANY WARRANTY OF MERCHANTABILITY,
NONINFRINGEMENT, FITNESS FOR ANY PARTICULAR PURPOSE,
SATISFACTORY QUALITY, OR REASONABLE SKILL OR CARE, OR ANY
WARRANTY ARISING OUT OF ANY COURSE OF DEALING, USAGE,
TRADE PRACTICE, PROPOSAL, SPECIFICATION OR SAMPLE.
Each Member hereby acknowledges that products equipped with the Bluetooth
technology ("Bluetooth Products") may be subject to various regulatory controls
under the laws and regulations of various governments worldwide. Such laws and
regulatory controls may govern, among other things, the combination, operation, use,
implementation and distribution of Bluetooth Products. Examples of such laws and
regulatory controls include, but are not limited to, airline regulatory controls,
telecommunications regulations, technology transfer controls and health and safety
regulations. Each Member is solely responsible for the compliance by their
Bluetooth Products with any such laws and regulations and for obtaining any and all
required authorizations, permits, or licenses for their Bluetooth Products related to
such regulations within the applicable jurisdictions. Each Member acknowledges that
nothing in the Specification provides any information or assistance in connection with
securing such compliance, authorizations or licenses.
NOTHING IN THE
SPECIFICATION CREATES ANY WARRANTIES, EITHER EXPRESS OR
IMPLIED, REGARDING SUCH LAWS OR REGULATIONS.
Introduction
June 26, 2001
Page 2
Page 3 of 3
Revision 0.95a
ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF ANY

INTELLECTUAL PROPERTY RIGHTS OR FOR NONCOMPLIANCE WITH
LAWS, RELATING TO USE OF THE SPECIFICATION IS EXPRESSLY
DISCLAIMED.
BY USE OF THE SPECIFICATION, EACH MEMBER
EXPRESSLY WAIVES ANY CLAIM AGAINST BLUETOOTH SIG AND ITS
PROMOTER MEMBERS RELATED TO USE OF THE SPECIFICATION.
Bluetooth SIG reserve the right to adopt any changes or alterations to the
Specification as it deems necessary or appropriate and to adopt a process for adding
new Bluetooth profiles after the release of the Specification.
Copyright
Introduction
2001.
Bluetooth
June 26, 2001
SIG,
Inc.
Page 3
Bluetooth Network Encapsulation Protoc ol (BNEP) Test Cases
Page 4 of 4
Revision 0.95a
Contents
1
2
4
5
6
7
8
Introduction............................................................................................................ 8
Profile Testing........................................................................................................ 9
2.1
Overview ........................................................................................................ 9
2.2
Testing Topology ........................................................................................... 9
2.3
Test Purposes (TP)......................................................................................... 9
2.3.1
Introduction............................................................................................ 9
BNEP Conformance Tests ....................................................................................12
3.1.1
TP/ BNEP/TX-TYPE-0/BV-01-C (BNEP Test Case 1 -- TX for BNEP
Type 0x00) ............................................................................................................12
3.1.2
TP/ BNEP/TX-C/BV-02-C (BNEP Test Case 2 -- TX BNEP Type
0x02)
14
3.1.3
TP/ BNEP/TX-C-S/BV-03-C (BNEP Test Case 3 -- TX for BNEP
Type 0x03) ............................................................................................................16
3.1.4
TP/ BNEP/TX-C-D/BV-04-C (BNEP Test Case 4 -- TX for BNEP
Type 0x04) ............................................................................................................18
3.1.5
TP/BNEP/CTRL/BV-05-C (BNEP Test Case 5 Unknown Control
Message) 20
3.1.6
TP/BNEP/CTRL/BV-06-C (BNEP Test Case 6 Setup Connection
Message) 22
3.1.7
TP/BNEP/CTRL/BV-07-C (BNEP Test Case 7 Setup Connection
Message Lost) .......................................................................................................24
3.1.8
TP/BNEP/CTRL/BV-08-C (BNEP Test Case 8 Network Protocol
Filter Message) ......................................................................................................26
3.1.9
TP/BNEP/CTRL/BV-09-C (BNEP Test Case 9 Network Protocol
Filter Message Lost) ..............................................................................................29
3.1.10
TP/BNEP/CTRL/BV-10-C (BNEP Test Case 10 Multicast Address
Filter Message) ......................................................................................................31
3.1.11
TP/BNEP/CTRL/BV-11-C (BNEP Test Case 11 Multicast Address
Filter Message Lost) ..............................................................................................34
References .............................................................................................................36
Acronyms and Abbreviations ................................................................................37
List of Figures .......................................................................................................38
List of Tables .........................................................................................................39
Annex ....................................................................................................................40
8.1
Test Case Mapping ........................................................................................40
8.1.1
PAN Profile Test Cases Mappings........................................................40
Introduction
June 26, 2001
Page 4
Page 5 of 5
Revision 0.95a
Revision History
Revision
Date
Comments
0.0
April 4, 2000
Original Document Started
0.1
May 11, 2000
Added various sections and added useful part of the Ethernet bridge
profile proposal
0.2
July 10, 2000
Added Monte Carlo F2F feedback
0.3
July 17, 2000
Fixed formatting errors
0.4
July 24, 2000
Added Addressing
0.5
September 26,
2000
Various structure and editorial changes
October 12, 2000
Editorial changes
0.6
Released to Adopters
Clarify Required Security

PAN User Service Record
Moved Testing Section to Appendix
0.7
November 27,
2000
Editorial changes
0.9
February 6, 2001
Separated PICS and Test Case from the PAN Profile document into
two separate document
0.95
June 12, 2001
Separated the BNEP test cases from the PAN Profile test cases.
Editorial changes and changes based on BARB, BTI, BQRB, BTAB
feedback.
0.95a
June 26, 2001
Editorial changes and changes based on BARB & BTI adoption

review.
Introduction
Added Test Cases
June 26, 2001
Page 5
Page 6 of 6
Revision 0.95a
Contributors
Name
Company
David Moore
3COM Corporation
Tom Scribner
3COM Corporation
Barry Corlett
Agere Systems
Willy Sagefalk
Axis Communications
Dan Willey
Certicom Corporation
Horia Balog
Classwave Wireless Inc.
Conrad Maxwell
Conexant Systems
Allan Bogeskov
Telefonaktiebolaget LM Ericsson
Theo Borst
Per Johansson
Tero Kauppinen
Martin Kitchen
Jesper Krogh
Tony Larsson
Johan Sorensen
Dave Suvak
Extended Systems Inc.
Jean Tourrilhes
Hewlett Packard Corporation
Toru Aihara
International Business Machines Corporation
Chatschik Bisdikian
International Business Machines Corporation
Kris Fleming (Editor)
Intel Corporation
Robert Hunter
Intel Corporation
Jon Inouye
Intel Corporation
Diego Melpignano
Philips Inc.
Eiji Kato
Matsushita Electric Industrial
Mike Foley
Microsoft Corporation
Billy Brackenridge
Microsoft
Dale Farnsworth
Motorola Inc.
Carmen Kuhl
Nokia Corporation
Introduction
June 26, 2001
Page 6
Jaakko Lipasti
Nokia Corporation
James Scales
Nokia Corporation
Markus Schetelig
Nokia Corporation
Sander
Valkenburg
van Nokia Corporation
Steven Kenny
Norwood Systems
Rebecca Ostergaard
Norwood Systems
Graeme Reid
Norwood Systems
Darrell Goff
Rappore
Daniel Shaw
Red-M Inc.
Pravin Bhagwat
ReefEdge, Inc.
Daryl Hlasny
Sharp Laboratories of America Inc.
Leonard Ott
Socket Communications Inc.
Johannes Lobbert
Sony Corporation
Wilhelm Hagg
Sony Corporation
Mike Blackstock
Synchropoint Wireless, Inc.
Yosuke Tajika
Toshiba Corporation
Tatuya Junmei
Tos hiba Corporation
Kazuo Nogami
Toshiba Corporation
Jim Hobza
Widcomm Inc.
Introduction
Page 7 of 7
Revision 0.95a
June 26, 2001
Page 7
Page 8 of 8
Revision 0.95a
1 Introduction
Bluetooth is a short-range wireless technology operating in the 2.4 GHz ISM
band. Many devices such as notebook computers, phones, PDAs, and other
computing devices will incorporate Bluetooth wireless technology. Using
Bluetooth wireless technology, devices will have the ability to form networks
and exchange information. For these devices to interoperate and exchange
information, a common packet format must be defined to encapsulate layer 3
network protocols.
The document contains the test cases for the Bluetooth Networking
Encapsulation Protocol (BNEP) specification.
Introduction
June 26, 2001
Page 8
Page 9 of 9
Revision 0.95a
2 Profile Testing
2.1 Overview
The test strategy will consist of only conformance testing. The conformance
testing will focus on testing the Bluetooth Networking Encapsulation Protocol
(BNEP) specification.
2.2 Testing Topology

For the testing of the Bluetooth Network Encapsulation Protocol one topology will be
used. The topology that is used for BNEP testing consist of two Bluetooth devices
connected to each other. While this topology does not represent the complete set of
topologies that are possible in an environments using BNEP, they are representative of
the most typical topologies and suitable for testing. The topology used for testing
BNEP is the simple network as shown in Figure 1. The network contains one master
(either Device A or B) and a single slave (either Device A or B).
Master
Slave
Figure 1 BNEP Testing Topology
2.3 Test Purposes (TP)

2.3.1 Introduction
The profiles, which use the BNEP specification, are dependent on the
successful validation of the required BNEP stack components and the BNEP
application functionality. TPs are also intended to verify the device
conformance and compatibility to the BNEP specification. TP definition and
naming conventions are stated below.
Profile Testing
June 26, 2001
Page 9
Page 10 of 10
Revision 0.95a
2.3.1.1 TP Definition Conventions

The TPs are defined following the particular rules show in the following table.
TP Id
Reference
Initial Condition
Test Procedure
Test Condition
Expected Outcome
The TP Id is a unique identifier. It is specified

according to the TP naming convention defined in the
sub clauses below
The reference contains the references of the subject to
be validated by the actual TP (Bluetooth Core
specification reference, verified requirements(s))
The initial condition specifies in which state the
Implementation Under Test (IUT) has to be in to
apply to the actual TP
Describes the steps to be performed for this TP
Describes the conditions which shall be maintained
during the test procedure
Describes the expected outcome of the TP
A Pass verdict is given if all test results are
successfully fulfilled
Uncertainties
Notes
A Fail verdict is given if all test results are

unsuccessfully fulfilled
If there exits any uncertainties for this TP, they are
stated here
Extra information for this TP
Table 1: Test Definition Conventions
Profile Testing
June 26, 2001
Page 10
Page 11 of 11
Revision 0.95a
2.3.1.2 TP Naming Conventions

The identifier of the TP is built according to the table below.
Identifier
<func> = Function
<xx> = Type of testing
<nn> = Sequential number
<y> = Test platform
TP/BNEP/<func>/<xx>-<nn> -<y>
TX =
TX_C = TX CompressedCTRL = Control
Valid Behavior (BV) tests
Invalid Behavior (BI) tests
(00-99) Test purpose number
I = Interoperability testing performed as product Vs.
product testing
C = Conformance testing performed with dedicated
Bluetooth test equipment
Table 2: Test Naming Convention
Profile Testing
June 26, 2001
Page 11
Page 12 of 12
Revision 0.95a
3 BNEP Conformance Tests

3.1.1 TP/ BNEP/TX-TYPE-0/BV-01-C (BNEP Test Case 1 -- TX for BNEP
T ype 0x00)
This test involves two Bluetooth devices, with one of the Bluetooth devices
sending a BNEP Packet to the other device. The test cases will verify the use
of the BNEP_GENERAL_ETHERNET (0x00) for sending Ethernet packets to
another device.
3.1.1.1 Reference
BNEP[1] and L2CAP in [2].
3.1.1.2 Initial Condition
Device A
Device B
L2CAP channel is open and configuration is completed
Data TX( Pattern # 0)
Both the Device A and Device B must be switched on and initialized.

Initialization may require a PIN if there are any security restrictions already in
place on the Bluetooth link. Device A and Device B must have valid Bluetooth
device addresses.
3.1.1.3 Test Procedure
Device B transmits a packet to Device A.
3.1.1.4 Test Condition
Device A must be in radio range of the Device B and successfully receive the
packet. Device A and Device B must be capable of maintaining an open
L2CAP connection.
BNEP Conformance Tests
June 26, 2001
Page 12
Page 13 of 13
Revision 0.95a
3.1.1.5 Expected Outcome

Pass verdict:
Device B is successful if Device B sent the correct data as defined below.
Pattern #0
Value
L2CAP Length 0x5EB
BNEP Type
Extension
Destination
Address
Source
Address
Network
Protocol Type
Dependent
Header or
other payload
information
Data
0x00
0x0
Device As
Bluetooth
Address
Device Bs
Bluetooth
Address
0x0800
Or
0x86DD
Or
0xXXXX
48 Bytes
Description
Length of the BNEP packet contained in the
L2CAP packet.
BNEP Type field is BNEP_GENERAL _ETHERNET
BNEP Extension flag = 0x0 = no extension header
The 48 bit Bluetooth Address of Device A
The 48 bit Bluetooth Address of Device B
The Network Protocol Type Internet IP (IPv4)

Or
Or
Other
48 bytes of Data to be ignored
0x5AC bytes are:{0x00, 0x01,,0xFF} *5 + {0x00,

0x01 , , 0xAB, 0xAC4}
Fail verdict:
Device B is unsuccessful, if Device B sends incorrect data.
3.1.1.6 Uncertainties
N/A
3.1.1.7 Notes
N/A
June 26, 2001
Page 13
Page 14 of 14
Revision 0.95a
3.1.2 TP/ BNEP/TX-C/BV-02-C (BNEP Test Case 2 -- TX BNEP Type 0x02)

This test involves two Blueto oth devices, with one of the Bluetooth devices
transmitting a BNEP Packet to the other device. The test cases will verify the
use of the BNEP_COMPRESSED_ETHERNET (0x02) for transmitting
Ethernet packets to another device.
3.1.2.1 Reference
Device A
Device B

device addresses.
L2CAP connection.
Pass verdict:
Pattern #0
Value
L2CAP Length 0x5DF
Description
L2CAP packet.
June 26, 2001
Page 14

BNEP Type
0x02
Extension
0x0
Network
Protocol Type
0x0800
Or
0x86DD
Or
0xXXXX
48 Bytes
Dependent
Header or
other payload
information
Data
Page 15 of 15
Revision 0.95a
BNEP Typ e field is

BNEP_COMPRESSED_ETHERNET
BNEP Extension flag = 0x0 = no extension
header
Or
Or
Other
0x5AC bytes are:{0x00, 0x01,,0xFF} *5 +

{0x00, 0x01 , , 0xAB, 0xAC4}
Fail verdict:
N/A
3.1.2.7 Notes
N/A
June 26, 2001
Page 15
Page 16 of 16
Revision 0.95a
3.1.3 TP/ BNEP/TX-C-S/BV-03-C (BNEP Test Case 3 -- TX for BNEP Type

0x03)
This test involves two Bluetooth devices, with one of the Bluetoothdevices
use of the BNEP_COMPRESSED_ETHERNET_SOURCE_ONLY (0x03) for
receiving Ethernet packets from another device.
3.1.3.1 Reference
Device A
Device B

device addresses.
L2CAP connection.
Pass verdict:
Pattern #0
Value
L2CAP Length 0x5E5
Description
June 26, 2001
Page 16
BNEP Type
0x03
Extension
0x0
Source
Address
Device Bs
Bluetooth
Address
0x0800
Or
0x86DD
Or
0xXXXX
48 Bytes
Network
Protocol Type
Dependent
Header or
other payload
information
Data
Page 17 of 17
Revision 0.95a
L2CAP packet.
BNEP Type field is
BNEP_COMPRESSED_ETHERNET_SOURCE_
ONLY
header
The 48 bit Bluetooth Address of Device B
Or
Or
Other
0x5AC bytes are:{0x00, 0x01,,0xFF} *5 +

{0x00, 0x01 , , 0xAB, 0xAC4}
Fail verdict:
N/A
3.1.3.7 Notes
N/A
June 26, 2001
Page 17
Page 18 of 18
Revision 0.95a
3.1.4 TP/ BNEP/TX-C-D/BV-04-C (BNEP Test Case 4 -- TX for BNEP Type

0x04)
use of the BNEP_COMPRESSED_ETHERNET_DEST_ONLY (0x04) for
transmitting Ethernet packets to another device.
3.1.4.1 Reference
Device A
Device B

device addresses.
L2CAP connection.
Pass verdict:
Pattern #0
Value
L2CAP Length 0x5E5
Description
Length of the BNEP packet contained in the L2CAP
June 26, 2001
Page 18
BNEP Type
0x04
Extension
Destination
Address
0x0
Device As
Bluetooth
Address
0x0800
Or
0x86DD
Or
0xXXXX
48 Bytes
Network
Protocol Type
Dependent
Header or
other payload
information
Data
Page 19 of 19
Revision 0.95a
packet.
BNEP Type field is
BNEP_COMPRESSED_ETHERNET_DEST_ONLY
The 48 bit Bluetooth Address of Device A

Or
Or
Other
0x5AC bytes are:{0x00, 0x01,,0xFF} *5 + {0x00,

0x01 , , 0xAB, 0xAC4}
Fail verdict:
N/A
3.1.4.7 Notes
N/A
June 26, 2001
Page 19
Page 20 of 20
Revision 0.95a
3.1.5 TP/BNEP/CTRL/BV-05-C (BNEP Test Case 5 Unknown Control

Message)
transmitting an unknown BNEP control message to the other device. The test
case will verify the use of the BNEP_CONTROL (0x02) for transmitting control
packets to another device.
3.1.5.1 Reference
Device A
Device B
CTRL Msg
CTRL Response Msg

device addresses.
Device A transmits the following BNEP unknown control message to Device
B.
CTRL Msg
Value
L2CAP Length 0x0002
BNEP Type
Extension
BNEP Control
Type
0x01
0x0
0xFF
Description
L2CAP packet.
BNEP Type field is BNEP_CONTROL
Unknown control command
June 26, 2001
Page 20
Page 21 of 21
Revision 0.95a

L2CAP connection.
Pass verdict:
CTRL
Value
Response
Msg
L2CAP Length 0x0003
BNEP Type
Extension
BNEP Control
Type
Unknown
Control Type
0x01
0x0
0x00
0xFF
Description
L2CAP packet.
BNEP_CONTROL_COMMAND_NOT_UNDERST
OOD
BNEP control type that was received and not
understood.
Fail verdict:
Device B is unsuccessful, if Device B does not send the above control
Response Message.
N/A
3.1.5.7 Notes
N/A
June 26, 2001
Page 21
Page 22 of 22
Revision 0.95a
3.1.6 TP/BNEP/CTRL/BV-06-C (BNEP Test Case 6 Setup Connection

Message)
transmitting a BNEP control message, which is setting up the connection, to
the other device. The test case will verify the use of the BNEP_CONTROL
(0x02) for transmitting control packets to another device. In addition, this test
verifies the proper response for a setup connection request message.
3.1.6.1 Reference
Device A
Device B
CTRL Msg
CTRL Response Msg

device addresses.
Device A transmits the following BNEP control message to Device B.
CTRL Msg
Value
L2CAP Length 0x0007
BNEP Type
Extension
0x01
0x0
BNEP Control
Type
UUID Size
Destination
0x01
0x04
0x1116
Description
L2CAP packet.
header
BNEP_SETUP_CONNECTION_REQUEST_MS
G
UUID Size = 4 bytes [3]
NAP Service UUID* [3]
June 26, 2001
Page 22

Service UUID
Source Service 0x1115
UUID
Page 23 of 23
Revision 0.95a
PANU Service UUID* [3]
* Note: Both the destination and source service UUID may be change to
match the supported services for each device under test. Also, in the future
addition profile may use BNEP and therefore other UUID [3] values are valid.
L2CAP connection.
Pass verdict:
CTRL
Value
Response
Msg
L2CAP Length 0x0002
BNEP Type
Extension
BNEP Control
Type
Response
Message
Description
0x01
0x0
0x02

packet.
BNEP_SETUP_ CONNECTION_RESPONSE_MSG
0x0000
Operation Successful
Fail verdict:
Device B is unsuccessful, if Device B does not send either of the above
control Response Message.
N/A
3.1.6.7 Notes
N/A
BNEP Confor mance Tests
June 26, 2001
Page 23
Page 24 of 24
Revision 0.95a
3.1.7 TP/BNEP/CTRL/BV-07-C (BNEP Test Case 7 Setup Connection

Message Lost)
transmitting a BNEP control message, which is setting up the connection, to
the other device. The test case will verify the use of the BNEP_CONTROL
(0x02) for transmitting control packets to another devic e. In this test case the
first control message is lost and is used to verify that the device A will resend
the control message again, after the message has timed out.
3.1.7.1 Reference
Device A
Device B
CTRL Msg
Time <=
30 sec.
CTRL Msg

device addresses.
CTRL Msg
Value
L2CAP Length 0x0007
BNEP Type
Extension
BNEP Control
Type
0x01
0x0
0x01
Description
L2CAP packet.
BNEP_SETUP_CONNECTION_REQUEST_MSG
June 26, 2001
Page 24

UUID Size
0x04
Destination
0x1116
Service UUID
Source Service 0x1115
UUID
Page 25 of 25
Revision 0.95a

PANU Service UUID* [3]
* Note: Both the destination and source service UUID may be change to
match the supported services for each device under test. Also, in the future
addition profile may use BNEP and therefore other UUID [3] values are valid.
Device B will intentionally drop the first control message.

L2CAP connection.
Pass verdict:
Device A is successful if Device A resends the original connection setup
control message as defined below within 30 seconds.
CTRL Msg
Value
L2CAP Length 0x0007
BNEP Type
Extension
BNEP Control
Type
UUID Size
Destination
Service UUID
0x01
0x0
0x01
Description
L2CAP packet.
BNEP_SETUP_CONNECTION_REQUEST_MSG
0x04
0x1116

Fail verdict:
Device A is unsuccessful, if Device A does not sends the above control
Response Message within 30 seconds.
N/A
3.1.7.7 Notes
June 26, 2001
Page 25
Page 26 of 26
Revision 0.95a
3.1.8 TP/BNEP/CTRL/BV-08-C (BNEP Test Case 8 Network Protocol

Filter Message)
transmitting a BNEP control message, which sets filters for all networking
protocol types excepted IPv6, to the other device. The test cases will verify
the use of the BNEP_CONTROL (0x02) for transmitting control packets to
another device. In addition, this test verifies the proper response for a
network protocol type filter message.
3.1.8.1 Reference
Device A
Device B
CTRL Msg
CTRL Response Msg

device addresses.
CTRL Msg
Value
L2CAP Length 0x0008
BNEP Type
Extension
BNEP Control
Type
List Length
0x01
0x0
0x03
0x0004
Description
L2CAP packet.
BNEP_FILTER_NET_TYPE_SET_MSG
Length of the list, in bytes, of the network protocols
not to be filtered
June 26, 2001
Page 26

Network
0x86DD
Protocol Type
Range Start #1
Network
0x86DD
Protocol Type
Range End #1
Page 27 of 27
Revision 0.95a
Network protocol type range starting at 0x86DD

Network protocol type range ending at 0x86DD

L2CAP connection.
Pass verdict:
Device B is successful if Device B supports networking filtering and sent the
correct data as defined below.
CTRL Msg
Value
L2CAP Length 0x0003
BNEP Type
Extension
BNEP Control
Type
Response
0x01
0x0
0x04
Description
L2CAP packet.
BNEP_FILTER_ NET_TYPE_RESPONSE_MSG
0x0000
Device B is also successful if Device B does not support networking filtering

and sent the correct data as defined below.
CTRL Msg
Value
L2CAP Length 0x0003
BNEP Type
Extension
BNEP Control
Type
Response
0x01
0x0
0x04
Description
L2CAP packet.
BNEP_FILTER_ NE T_TYPE_RESPONSE_MSG
0x0001
Unsupported Request
Fail verdict:
Device B is unsuccessful, if Device B does not send either of the above
control Response Messages.
N/A
June 26, 2001
Page 27
Page 28 of 28
Revision 0.95a
3.1.8.7 Notes
N/A
June 26, 2001
Page 28
Page 29 of 29
Revision 0.95a
3.1.9 TP/BNEP/CTRL/BV-09-C (BNEP Test Case 9 Network Protocol

Filter Message Lost)
transmitting a BNEP control message, which sets filters for all networking
protocol types excepted IPv6, to the other device. The test cases will verify
the use of the BNEP_CONTROL (0x02) for transmitting control packets to
another device, is retransmitted if the message is lost.
3.1.9.1 Reference
Device A
Device B
CTRL Msg
Time <=
30 sec.
CTRL Msg

device addresses.
CTRL Msg
Value
L2CAP Length 0x0008
BNEP Type
Extension
BNEP Contro l
Type
List Length
0x01
0x0
0x03
Network
Protocol Type
0x86DD
0x0004
Description
L2CAP packet.
not to be filtered
June 26, 2001
Page 29

Range Start #1
Network
0x86DD
Protocol Type
Range End #1
Page 30 of 30
Revision 0.95a

L2CAP connection.
Pass verdict:
Device A is successful if Device A resends the original filter control message
as defined below within 30 seconds.
CTRL Msg
Value
L2CAP Length 0x0008
BNEP Type
Extension
BNEP Control
Type
List Length
0x01
0x0
0x03
0x0004
Network
0x86DD
Protocol Type
Range Start #1
Network
0x86DD
Protocol Type
Range End #1
Description
L2CAP packet.
not to be filtered
Fail verdict:
Device A is successful if Device A does not resend the original filter control
message as defined below within 30 seconds.
N/A
3.1.9.7 Notes
N/A
June 26, 2001
Page 30
Page 31 of 31
Revision 0.95a
3.1.10 TP/BNEP/CTRL/BV-10-C (BNEP Test Case 10 Multicast Address

Filter Message)
This test involves two Bluetooth devices, w ith one of the Bluetooth devices
transmitting a BNEP control message, which sets filters for all multicast
address excepted IPv4, to the other device. The test cases will verify the use
of the BNEP_CONTROL (0x02) for transmitting control packets to another
device. In addition, this test verifies the proper response for a multicast
address type filter message.
3.1.10.1
Reference

3.1.10.2
Initial Condition
Device A
Device B
CTRL Msg
CTRL Response Msg

device addresses.
3.1.10.3
Test Procedure

CTRL Msg
Value
L2CAP Length 0x0010
BNEP Type
Extension
BNEP Control
Type
List Length
0x01
0x0
0x05
0x000C
Description
packet.
BNEP_FILTER_MULTI_ADDR_SET_MSG
Length of the list, in bytes, of the multicast address
not to be filtered
June 26, 2001
Page 31

Multicast
Address
Range Start #1
Multicast
Address
Range End #1
3.1.10.4
Page 32 of 32
Revision 0.95a
0x03000020 Multicast address range starting at 0x030000200000

0000
0x03000020 Multicast address range ending at 0x030000200000
0000
Test Condition
L2CAP connection.
3.1.10.5
Expected Outcome
Pass verdict:
Device B is successful if Device B supports networking filtering for multicast
addresses and sent the correct data as defined below.
CTRL Msg
Value
L2CAP Length 0x0003
BNEP Type
Extension
BNEP Control
Type
Response
0x01
0x0
0x06
Description
packet.
BNEP_FILTER_MULTI_ADDR_RESPONSE_MSG
0x0000
Device B is also successful if Device B does n ot support networking filtering

for multicast addresses and sent the correct data as defined below.
CTRL Msg
Value
L2CAP Length 0x0003
BNEP Type
Extension
BNEP Control
Type
Response
0x01
0x0
0x06
Description
packet.
BNEP_FILTER_MULTI_ADDR_RESPONSE_MSG
0x0001
Unsupported Request
Fail verdict:
Device B is unsuccessful, if Device B does not sends either the above control
Response Messages.
3.1.10.6
Uncertainties
N/A
June 26, 2001
Page 32

3.1.10.7
Page 33 of 33
Revision 0.95a
Notes
N/A
June 26, 2001
Page 33
Page 34 of 34
Revision 0.95a
3.1.11 TP/BNEP/CTRL/BV-11-C (BNEP Test Case 11 Multicast Address

Filter Message Lost)
transmitting a BNEP control message, which sets filters for all multicast
address excepted IPv4, to the other device. The test cases will verify the use
of the BNEP_CONTROL (0x02) for transmitting control packets to another
device, is retransmitted if the message is lost.
3.1.11.1
Reference

3.1.11.2
Initial Condition
Device A
Device B
CTRL Msg
Time <=
30 sec.
CTRL Msg

device addresses.
3.1.11.3
Test Procedure

CTRL Msg
Value
L2CAP Length 0x0010
BNEP Type
Extension
BNEP Control
Type
List Length
Multicast
Address
Range Start #1
0x01
0x0
0x05
Description
packet.
0x000C

not to be filtered
0000
June 26, 2001
Page 34
Page 35 of 35
Revision 0.95a
Range Start #1
Multicast
Address
0000
Range End #1

3.1.11.4
Test Condition
L2CAP connection.
3.1.11.5
Expected Outcome
Pass verdict:
Device A is successful if Device A resends the original filter control message
as defined below within 30 seconds.
CTRL Msg
Value
L2CAP Length 0x0010
BNEP Type
Extension
BNEP Control
Type
List Length
0x01
0x0
0x05
Description
packet.
0x000C

not to be filtered
0000
Multicast
Address
Range Start #1
Multicast
Address
0000
Range End #1
Fail verdict:
Device A is unsuccessful, if Device A does not resend the original filter control
message as defined below within 30 seconds.
3.1.11.6
Uncertainties
N/A
3.1.11.7
Notes
N/A
June 26, 2001
Page 35
Page 36 of 36
Revision 0.95a
References
[1]
Bluetooth Special Interest Group, Bluetooth Network Encapsulation

Protocol (BNEP) Specification, Specification of the Bluetooth System,
Version 0.95, June 12, 2001
[2]
Bluetooth Special Interest Group, Bluetooth Core, Specification of the

Bluetooth System, Version 1.1, February 22, 2001
[3]
Bluetooth Special Interest Group, Bluetooth Assigned Number,

Specification of the Bluetooth System, Version 1.1 December 1, 2000
References
June 26, 2001
Page 36
Page 37 of 37
Revision 0.95a
5 Acronyms and Abbreviations

List of abbreviations necessary for the understanding BNEP test cases.
Abbreviation or
Acronym
Meaning
BNEP
Bluetooth Network Encapsulation Protocol
IP
Internet Protocol
L2CAP
Logical Link Control and Adaptation Protocol
MTU
Maximum Transmission Unit
Acronyms and Abbreviations
June 26, 2001
Page 37
Page 38 of 38
Revision 0.95a
6 List of Figures
Figure 1 BNEP Testing Topology............................................................................................................................9
List of Figures
June 26, 2001
Page 38
Page 39 of 39
Revision 0.95a
7 List of Tables
Table 1: Test Definition Conventions ...................................................................................................................10
Table 2: Test Naming Convention ........................................................................................................................11
List of Tables
June 26, 2001
Page 39
Bluetooth Network Encaps ulation Protocol (BNEP) Test Cases
Page 40 of 40
Revision 0.95a
8 Annex
8.1 Test Case Mapping
8.1.1 PAN Profile Test Cases Mappings
Fill out the columns "Support" in the following way
If the BNEP feature is supported, mark it in the "Support" field, where x
corresponds to the feature number in the PAN's ICS tables.
For PAN features refer to the BT ICS/IXIT Proforma document, Table 1, 2, and 3.
Selection
Expression
1/0 AND
2/0 AND
3/0
Feature
Supported
Supports BNEP
Test Case(s)
Test Case
Applicable
TP/BNEP/TX
-TYPE-0/BV01-C
TP/BNEP/TX
-C/BV-02-C
TP/BNEP/TX
-C-S/BV-03C
TP/BNEP/TX
-C-D/BV-04C
TP/BNEP/CT
RL/BV-05-C
TP/BNEP/CT
RL/BV-06-C
TP/BNEP/CT
RL/BV-07-C
TP/BNEP/CT
RL/BV-08-C
Annex
June 26, 2001
Page 40

Selection
Expression
Feature
Supported
Page 41 of 41
Revision 0.95a
Test Case(s)
Test Case
Applicable
TP/BNEP/CT
RL/BV-09-C
TP/BNEP/CT
RL/BV-10-C
TP/BNEP/CT
RL/BV-11-C
Annex
June 26, 2001
Page 41

Bluetooth Network Encapsulation (BNEP) Protocol Test Cases - Rev0.95a

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Bluetooth Network Encapsulation (BNEP) Protocol Test Cases - Rev0.95a

Загружено:

Авторское право:

Доступные форматы

BNEP Test Cases

Bluetooth Network Encapsulation

June 26, 2001

Bluetooth Network Encapsulation Protocol (BNEP) Test Cases

Disclaimer and copyright notice

June 26, 2001

Bluetooth Network Encapsulation Protocol (BNEP) Test Cases

ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF ANY

June 26, 2001

Bluetooth Network Encapsulation Protoc ol (BNEP) Test Cases

June 26, 2001

Bluetooth Network Encapsulation Protocol (BNEP) Test Cases

Original Document Started

May 11, 2000

July 10, 2000

Added Monte Carlo F2F feedback

July 17, 2000

Fixed formatting errors

July 24, 2000

Various structure and editorial changes

October 12, 2000

Clarify Required Security

June 12, 2001

June 26, 2001

Editorial changes and changes based on BARB & BTI adoption

Added Test Cases

June 26, 2001

Bluetooth Network Encapsulation Protocol (BNEP) Test Cases

Classwave Wireless Inc.

Extended Systems Inc.

Hewlett Packard Corporation

International Business Machines Corporation

International Business Machines Corporation

Kris Fleming (Editor)

Matsushita Electric Industrial

June 26, 2001

Bluetooth Network Encapsulation Protocol (BNEP) Test Cases

van Nokia Corporation

Sharp Laboratories of America Inc.

Socket Communications Inc.

Synchropoint Wireless, Inc.

Tos hiba Corporation

June 26, 2001

Bluetooth Network Encapsulation Protocol (BNEP) Test Cases

June 26, 2001

Bluetooth Network Encapsulation Protocol (BNEP) Test Cases

2.2 Testing Topology

Figure 1 BNEP Testing Topology

2.3 Test Purposes (TP)

June 26, 2001

Bluetooth Network Encapsulation Protocol (BNEP) Test Cases

2.3.1.1 TP Definition Conventions

The TP Id is a unique identifier. It is specified

A Fail verdict is given if all test results are

Table 1: Test Definition Conventions

June 26, 2001

Bluetooth Network Encapsulation Protocol (BNEP) Test Cases

2.3.1.2 TP Naming Conventions

Table 2: Test Naming Convention

June 26, 2001

Bluetooth Network Encapsulation Protocol (BNEP) Test Cases

3 BNEP Conformance Tests

L2CAP channel is open and configuration is completed