Você está na página 1de 16

BT.

5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification

BT.1001_ LTE1702_ BlueTooth Pairing, PAN Establishment and Connection


Verification
Purpose:

The purpose of this test is to verify Bluetooth pairing, PAN


establishment and active connection on a Windows based laptop
that can be locally connected to Flexi Zone Micro (FZM) small cell
via Bluetooth interface. This test will cover the procedure on how to
pair and connect to FZM small cell using Legacy Pairing via
passcode, then confirm the link with the FZM (using a laptop running
Windows OS) by navigating to the FTM/TRS Webserver and
enabling SSH access.

Abstract:

This software-only feature will enable site service technician wirelessly


connect to a specific site locally for initial site deployment, reactive site
maintenance and proactive site service and auditing. Purpose of this
test is to check whether Bluetooth interface can be properly enabled and
disabled. After Bluetooth interface is enabled, we will verify if we can
connect to FZM via Bluetooth with Legacy Pairing authorization method
by enabling SSH access to the FZM. Part of verification is to check if
FZM correctly raises Bluetooth Paired and Bluetooth Network
Connected alarms are correctly displayed in BTSSM and/or NetAct.

Related
Features
or CRLs:

1702 FZM Bluetooth Support

Related
<List here specifications related to this test case>
specifications: BLUETOOTH SPECIFICATION Version 2.1 + EDR
Related
documents:

<Add here precise information on where a customer can find more


information on feature(s) and subject(s) mentioned in this TC>
<List here also the names of related ATMN documents if
applicable>
Test cases and other:

Prerequisites:

Required Network Elements/ Equipment


LTE Flexi zone Micro eNB (FZM)
Application PC (UE side, core side)
BTSSM supports LTE1702
Class 1 BlueTooth USB Dongle

Amount
1
2
1
1

BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 1 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification

Additional
information:

Assume that FZM has been pre-loaded with software that is


reachable via BTSSM and has a legacy pairing default password in
place or customer has NSN BlueTooth password generation tool to
access the unit for the first time (from factory). The test is preferred
to be conducted with the FZM fully integrated into the network,
however, this test can be performed on an FZM without an S1 link.

Document change history:


Version
<1.0> where:
- Minor versioning
(1.1, 1.2, etc.) for
changes within
release (e.g.
RL40)
- Major versioning
for changes in
new release (2.0
for RL50, 3.0 for
RL60, etc.)

Date
30.01.14

Author
Sbenes

Changes
Initial draft on BTSSM v20 and SW
87_00

<leave the rest of this page empty>

BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 2 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification

1. Test Configuration
Network elements, instrumentation and terminals configuration

Figure 1. Basic FlexiZone Micro eNB Network

BlueTooth Client
BTSCSite
Manager

Bluetooth
Link

Client PC

BlueTooth
Radio
FZM O&M
FZM

Figure 2. Basic Connectivity between Client and FZM over BlueTooth

BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 3 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification

2. Setup / Test Preparation & Background Information


2.1

Background Information

In actual deployment, it is expected that most Flexi Zone Micro (FZM) BTS units will
not be physically accessible once mounted without special access equipment. Use of
a specialty truck every time site access is needed for maintenance and
troubleshooting can be costly and time consuming for the operator. In addition, it is
expected that many deployments will not allow for a physical Ethernet cable to be run
from the Flexi Zone BTS to an easily accessible location. As a result, BlueTooth has
been added to the Flexi Zone Micro BTS to allow the operator a way to access the
unit wirelessly from street level. This feature enhances the basic Bluetooth
functionality to improve performance, operability, and security.
Key Feature Functionality

Ability to quickly transfer data over the Bluetooth link


Locally push data to the FZM (example: load configuration files)
Locally pull data from the FZM (example: collect logs)
Configuration Management capabilities including but not limited to:
Status, reset, and disable FZM devices (example: status GPS, reset radio, disable
transmit)
Configuration changes (example: configure IP address)
Display data (example: hardware serial number)
Secure the Bluetooth link to address Bluetooth security concerns with improved
processes, alarms, and parameters

Note that the FZM will include information from the factory to facilitate first time
Bluetooth access to the unit (new commissioning). This procedure assumes that the
FZM has already been through the initial commissioning steps and is able to accept
the parameters specified in this test.
2.2

2.3

Setup / Test Preparation


Factory software is required to be preinstalled
Laptop computer with pre-installed BTS site manager software
BTOOTH:actBluetooth is set to ENABLED
BTOOTH: allowInqScanResp is set to ENABLED
BTOOTH: allowLegacyPairing flag is set to ENABLED
BTOOTH:legacyPairingOPTMode is set to -2
BTOOTH:legacyPairingSecret is set to LEGACYOTP (4c45474143594f5450)
BTOOTH:allowSspPairing flag is set to DISABLED
BTOOTH:actBluetoothAlarm is set to ENABLED

Setting O&M Parameters

BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 4 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification
There is a list of new configurable O&M parameters that can be customized by
operator and site technician.

Parameter Name

Description

actBluetooth

Allow operator to enable/disable


Bluetooth

Range and step


Enabled: Bluetooth enabled
Disabled: Bluetooth disabled
Auto: Bluetooth enabled
automatically upon loss of
connection to NetAct

Allow additional control over


legacy pairing protocol
implementation.

legacyPairingOPTMode

If "Legacy Pairing OTP Mode" =


-2 (configured PIN mode), the
initial bytes of the configured
legacyPairingSecret (up to 16
bytes in all after hex unencoding)
is used as a fixed legacy PIN;
Otherwise, counter-based logic
adapted from RFC
6238/RFC4226 uses secret B1
derived from legacyPairingSecret
as a key for generating a series of
site-specific, one time 16 byte
PINs based on
RFC6238/RFC4226.

Default
value
Enabled

-1

-2..214748264, step 1

If "Legacy Pairing OTP Mode" is


set to -1 (rotating PIN mode), the
applicable counter advances
based on internal BTS logic.

legacyPairingSecret

If "Legacy Pairing OTP Mode" is


set between 0 and 214748264
(generated static PIN mode), the
applicable counter is fixed to the
specified data value of Legacy
Pairing OTP Mode.
Configures site-specific secrets
associated with Bluetooth legacy
pairing . The configured secret
must be entered as a hex
encoded string. For example,
binary string 1mA is represented
by hex encoding 316D41.

0..256 Characters

Empty

With Legacy Pairing OTP Mode =


-2 (configured PIN mode),
legacyPairingSecret can be used
to explicitly configure a fixed
legacy pairing PIN. For this case,
the operator should carefully
consider the limitations of any
BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 5 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification
expected Bluetooth peers. A
complex PIN is more secure.
However, a PIN containing only
digits is mostly widely compatible.

allowInqScanResp

allowLegacyPairing

With Legacy Pairing OTP Mode


>= -1 (rotating PIN mode or
generated static PIN mode),
legacyPairingSecret can be used
to assign a custom legacy pairing
secret B1 for the legacy OTP
algorithm. If legacyPairingSecret
is left empty in these modes,
secret B1 is set to a default value
known to all sites and all NSN
customers.
Allow the site to respond to
inquiry scans to provide device
name and other info before
pairing. A site that does not
respond to inquiry requests will be
less visible to casual scans.
Allow legacy pairing (as defined
by BT protocol) and set PIN
and/or seed for rotating PIN

Disabled
Enabled: FZm responds to
Bluetooth inquiry requests.
Disabled: Requires site
operator to know Bluetooth
device address

Enabled
Disabled: legacy pairing
required by BT 2.1 compliance

Enabled

allowSspPairing

Allow Bluetooth secure simple


pairing

Enabled
Disabled

Disabled

pairingRelationTimer

Allow user to timeout pairing


relationship after the configured
number of hours.

0..169 h, step 1 h

3h

If it is set to 0: Immediately clear


all pairing relationships and
connections at time of
configuration change; no
subsequent pairing or
connections allowed until Pairing
Relationshio Timout changed to a
non-zero value.
If it is set to 169 : Do not
automatically timeout pairing
relationships;
If it is set to the value between 1
and 168, the value is the timeout
in hours. Once the age of a
pairing relationship reaches the
timeout, BTS will automatically
timeout the pairing relationship.
If the device is connected at the
time of pairing timeout, the device
is not forcibly disconnected by the
pairing timeout. However,
BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 6 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification
subsequent connection after
expired pairing relationship will
require a fresh pairing.
Allow operator to configure a
persistent Bluetooth device
whitelist and blacklist.
pairingRelationships

sspSecret

actBluetoothAlarm

If the list contains at least one


whitelisted device, only whitelisted
devices may connect to or pair
with the BTS. Otherwise, if the list
contains blacklisted devices, the
blacklisted devices can NOT
connect to or pair with the BTS.
Configure site-specific secret for
Bluetooth secure simple pairing.
The configured secret must be
entered as a hex encoded string.
For example, binary string 1mA is
represented by hex encoding
316D41.
If sspSecret is an empty string, a
site-specific key, as derived from
NSN's default algorithm, will be
used as the key for counter-based
generation of a series of one time
6 digit passkey per
RFC6238/RFC4226;
If sspSecret is an non-empty
string, Secure Simple Pairing
Secret will be used as a key for
counter-based generation of a
series of one time 6 digit passkey
per RFC6238/RFC4226.
Activate Bluetooth alarm
capability to generate notification
to operator if Bluetooth has been
enabled or disabled at a site.

None
Structure:
deviceAddress,
deviceStatus,
outOfBandData,
pairingOrderNum

Empty

0..256 characters

Enabled: an alarm is
generated notifying the
operator
Disabled: Do not ever
generate the alarm.

Enabled

Table 1: O&M parameters related to LTE1702 feature

BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 7 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification

3. Test execution / Implementation


Step1: Enable Bluetooth interface by setting Bluetooth parameters
Action / Input
1. Bluetooth interface should be defaulted to enabled, FZM should look for
pairing element starting from cold start.
a. Ensure Legacy default values match setup parameters in figure 3

Figure 3. Legacy Pairing Settings

2. Make sure BlueTooth interface is enabled on BTS site manager laptop.


a. This step is based on a Windows operating system. Note, different
BlueTooth clients may have slightly different screens for the pairing
process. However, the steps outlined in this document will remain true.
3. Select the BlueTooth name of the FZM you wish to pair to.
4. Select the LEGACY pairing mechanism requires the manual entry of a
pairing code, as shown in figure 4.
a. Enter LEGACYOTP as pairing code, shown in figure 5.

BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 8 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification

Figure 4. Pairing options, use "Enter Device Pairing Code"

BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 9 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification

Figure 5. Entering the Legacy Pairing Code

5. The operating system will proceed through the pairing process and the FZM
will be shown in the BlueTooth Devices screen. Once paired, establish
connection by selecting Network Connect to establish full connection.

BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 10 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification

Figure 6. Establishing PAN Connection

Expected Result / Output


1. FZM Bluetooth interface is successfully paired with laptop computer which is
running BlueTooth client, shown in figure 7.

Figure 7. Successful PAN Established


BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 11 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification

If you are monitoring the progress on a BTS Site Manager (BTSSM) connected via
M-plane or LMT, you will see BlueTooth alerts indicating that BlueTooth is enabled
and that a Bluetooth connection has been established, similar to the figure below.

Figure 8. LMT BTSSM Displaying Successful BlueTooth Connection Alert

Step2: Assign IP to establish PAN network


Action / Input
1. Assign one of the IP (192.168.255.243/29) to the PAN network interface on the
"laptop computer" using the proper technique for your OS (for example, on
Windows it is under network interface). Assign the netmask value of
255.255.255.248. A DNS IP address is not required. See figure 9 for an
example.

BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 12 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification

Figure 9. Assigning IP for Windows Client

2. Ping IP 192.168.255.245 from laptop.


Expected Result / Output
1. IP assigned successfully.
2. No failure alarms observed on LMT connected BTS Site Manager. Minor alerts
of "Bluetooth Enabled" and "Bluetooth Network Connected observed if other
instance of BTSSM or NetAct is attached to FZM.
3. "ping" to 192.168.255.245 succeeds.

Step3: Navigate to FTM/TRS Web Page on FZM via BlueTooth PAN


Action / Input
Start web browser application on BlueTooth client laptop (example: Internet
Explorer). Enter URL:
https://192.168.255.245
Expected Result / Output
The FTM/TRS webserver page will be displayed. See figure 10 for an example.

BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 13 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification

Figure 10. Transport Module Webpage on FZM

Step4: Enable SSH via FTM/TRS Web Page


Action / Input
Select SSH Service on left side menu. A login window will open, enter:
User Name: Nemuadmin
Password: nemuuser

Expected Result / Output


You will be on the SSH page. Select Enable SSH. A SSH status change will indicate
you have successfully completed the test.

BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 14 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification
Step5: Verify SSH connectivity
Action / Input
Using a SSH tool (such as PuTTY) open an SSH session to IP address
192.168.255.245 with the following login credentials:
Login name: toor4nsn
Password: (available to NSN customers)

Expected Result / Output


A SSH session will open and you will logged to the linux system on the FZM.

4. Impacted KPI/Counters
No KPIs or Counters Impacted

5. Related Message Flow


No message flow applicable.

6. Epilogue

PAN connection can remain open, or user can quit the SSH session, close the web
browser and select Disconnect Network Service to close the connection.

Copyright Nokia Solutions and Networks GmbH & Co KG 2008. All rights reserved.
The information in this document is subject to change without notice and describes only the product defined in the
introduction of this documentation. This document is intended for the use of Nokia Solutions and Networks
customers only for the purposes of the agreement under which the document is submitted, and no part of it may
be reproduced or transmitted in any form or means without the prior written permission of Nokia Solutions and
Networks. The document has been prepared to be used by professional and properly trained personnel, and the
customer assumes full responsibility when using it. Nokia Solutions and Networks welcomes customer comments
as part of the process of continuous development and improvement of the documentation.

BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 15 of 16

BT.5001
BT.5001_LTE1702_ BlueTooth Pairing, PAN Establishment and Connection
Verification
Nokia Solutions and Networks liability for any errors in the document is limited to the documentary correction of
errors. NOKIA SOLUTIONS AND NETWORKS WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN
THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY
LOSSES), that might arise from the use of this document or the information in it.
This document and the product it describes are considered protected by copyright according to the applicable
laws.
Technical specifications, performance values and features are binding only insofar as they are specifically and
expressly agreed upon in a written contract.
NOKIA Solutions and Networks logo is a registered trademark of Nokia Solutions and Networks GmbH & Co KG.
Other product names mentioned in this document may be trademarks of their respective companies, and they are
mentioned for identification purposes only.

BT.5001_LTE1702_BlueTooth Pairing, PAN Establishment and Connection Verification

Page 16 of 16