-2-
FIELD OF THE INVENTION
The present invention relates to Bluetooth scatternet network manager system (BSNMS).
BACKGROUND OF THE INVENTION
Bluetooth wireless technology is a short-range communications technology intended to
replace the cables connecting portable and / or fixed devices while maintaining high
levels of security. The key features of Bluetooth technology are robustness, low power,
and low cost. The Bluetooth specification defines a uniform structure for a wide range of
devices to connect and communicate with each other.
Bluetooth technology has achieved global acceptance such that any Bluetooth enabled
device, almost everywhere in the world, can connect to other Bluetooth enabled devices
in proximity. Bluetooth enabled electronic devices can be connected for wireless
communication through short-range, ad hoc networks known as piconets. Each device
can simultaneously communicate with up to seven other devices within a single piconet.
Each device can also belong to several piconets simultaneously. Piconets are established
dynamically and automatically as Bluetooth enabled devices enter and leave radio
proximity.

-3-
A fundamental Bluetooth wireless technology strength is the ability to simultaneously
handle both data and voice transmissions. This enables users to enjoy variety of
innovative solutions such as a hands-free headset for voice calls, printing and fax
capabilities, and synchronizing PDA, laptop, and mobile phone applications to name a
few.
A piconet comprises a collection of such digital devices which are connected by using
Bluetooth technology in an ad-hoc manner. A scatternet comprises a number of
independent piconets.
Document US 2002 0044549 discloses a method of routing information in an ad hoc
network. Two separated scatternets are provided - one maximum connectivity scatternet
(MCS) and the other, traffic scatternet (TS). An overall scatternet according to this
document comprises one maximum connectivity scatternet and a number of traffic
scatternets.
Information on all the nodes in the scatternet are maintained by the maximum
connectivity scatternet MCS so that a quick path can be established in case of a
destination node search. When new nodes enter the scatternet and other existing nodes
exit, the MCS is maintained in an autonomous form. A traffic scatternet is established

-4-
between two nodes in the scatternet on a per session basis. The object of the traffic
scatternet is to achieve best possible data flow between the concerned nodes. Besides
establishing dedicated TS piconets and / or dedicated TS links, when supported, this may
involve switching to Bluetooth high speed mode on traffic scatternet links.
The above mentioned US document 0044549 describes a scatternet with one maximum
connectivity scatternet (MCS) and two traffic scatternets (TS). The MCS includes three
piconets. One piconet has a master node and seven slave nodes. Another piconet has a
master node and six slave nodes. The third piconet has one master node and five slave
nodes. The MCS maximizes the number of nodes in each piconet so that it can spread
and maintain information with minimum number of inter-piconet connections.
The MCS can be considered as an efficient scatternet containing information about all of
the nodes therein, unlike the conventional scatternets, thereby establishing a quick path
during a search perform for a destination node. A record for each slave in the piconet is
stored in a piconet information database by the master of each piconet in the MCS.
In another aspect the document mentioned above describes a slave record containing
information about the traffic load on the slave node, the available capacity, number of
piconets where the slave node is a member, information regarding the slave node also

-5-
being a master node in some other piconets, and so on. The piconet database
information may be shared among the members and stored by all forwarding slave nodes
for providing information on request received by neighbouring piconets. For establishing
an efficient scatternet like the MCS, the nodes are to be interconnected such that densely
connected structures can be avoided. The number of interconnections between two
adjacent piconet is kept at 1 or 2 for limiting the number of inter-piconet nodes. Also,
the scatternet ID can be used by a node in order to find out whether or not a detected
node is part of the scatternet. The scatternet ID is stored in the piconet information
database. A common scatternet ID is used when the scattemets merge.
The master nodes of the piconets can share information between themselves besides the
master nodes and slave nodes exchanging information for the maintenance of MCS. The
master nodes for instance can exchange information on the number of nodes and IDs
(BD_ADDR) of the nodes in each piconet, which information can be stored in the piconet
information database by each master node.
Only a part of the piconet information database contents are shared between the
piconets so that the amount of traffic can be limited. A master node can find out when it
reaches an overlap of nodes with another master node on the basis of the information
exchanged between them. Upon determining this the master nodes may perform a
pcioconet merge so as to minimize the number of inter-piconet nodes like MCS gateway
nodes between MCSs.

-6-
The internet protocol (IP) addresses and their mapping to BD_ADDRs of the nodes in the
piconet is stored in the piconet data base information for limiting the spread of the
address resolution request. Thus the master nodes of each piconet can resolve the
address resolution request and it can be further limited if the piconet information
database of each piconet of the MCS are stored by the MCS gateways. A mapping of
domain name server (DNS) and service lookup may be performed with the MCS path
finding. Such mapping will need additional information to be stored in the piconet
information database.
In prior art systems features like supporting protocols and profiles about the devices
present in the scatternet cannot be known. When a new device enters the scatternet no
other device present in the scatternet, apart from the master or server, have the
information about the newly joined device. These other devices in the scatternet will be
called upon to do individually device discovery and service search for finding out the
required information. The present invention overcomes these disadvantages in prior art
system.

-7-
SUMMARY OF THE INVENTION
The main object of the present invention therefore, is to provide a standard for Bluetooth
scattemet network manager system (BSNMS) so that each slave or client device in the
scatternet can easily get information like support services, device status and security
mode about all other members in the scatternet by using BSNMS client profile.
The BSNM Server contains a database, BSNM Server profile, Bluetooth radio and
Bluetooth stack. The BSNMS master database contains all information about the BSNM
clients. The Bluetooth core stack having an upper and a lower stack allow the BSNMS
server and clients to share the database. The Bluetooth devices contain radio as well as
baseband firware. The Bluetooth radio can transmit and receive information sent by
BSNMS clients and server via the upper Bluetooth stack(L2CAP layer...).
In the present invention a standard for BSNMS profile is provided so that each slave or
client device in the scatternet can easily get the information like supported services
(Phone Book access profile, printer, Hands free, ftp, serial access profile etc.), device
status (Active/Low power Mode), BD-address's, pin key, link key, security related issues
about all other members in the scattemet by using BSNMS client. In this network, one
device will act as BSNMS master or server and it will maintain a database about all
members in the scatternet. It updates the database whenever there is new Bd client
detected in the network or there is change in the services of the already available Bd

-8-
In a preferred embodiment the present invention provides a Bluetooth scatternet network
manager system (BSNMS) comprising: a scatternet with piconets each having a master to
act as (BSNMS) server and a plurality of slaves to act as BSNMS clients; a master or
server database designed to contain all information about slaves or clients of the
scatternet; a Bluetooth core stack configured for allowing BSNMS server and clients to
share said database information with each other; and BSNM server and clients containing
radio and baseband firmware and upper Bluetooth stack for transmitting and receiving
information .
BREIF DESCRIPTION OF THE ACCOMPANYING DRAWING
The invention can now be described in detail with the help of the figure of the
accompanying drawing in which
Figure 1 shows the scatternet where the present invention has been applied.
Figure 2 shows BSNMS server and BSNM client comprising upper and lower stacks.

-9-
DETAILED DESCRIPTION
As shown in Figure 1 two piconets are there. Each one have one master and four slaves.
As shown in Figure 1 the shared slave can act as a BSNM server and all other devices in
two piconets will act as a BSN clients. When any BSNM slave enter into piconet it checks
for BSNM server. If it is there it will establish a BSNM profile level connection and share
its services information and bd address and pin key etc with BSNM server and disconnect
the BSNM profile level connection. And BSNM server stores this information in its
database and share with any other BSNM client if required. Suppose any slave requires a
Bluetooth printer in the vicinity to connect, generally it has to do device discovery then
establish a hci & I2cap level connection to that device. Then it do service discovery by
establishing SDP level connection to that device. If that required service is not supported
by that device then it has to do service discovery for another device this procedure
repeats till it found a device with required service. Which is time-consuming job. With
this BSNM standard any BSNM client wants to connect to a Bluetooth printer then it will
establish BSNM connection to BSNM server and fetches the database information from
BSNM server. From that database it comes to know that which device supporting that
service (for example). And then simply it will try to establish that service level connection
to that device without doing any sdp service discovery. If in case that remote device
doesn't accept the connection due to some authentication issues then it will try
connection to the next available device in the database.

-10-
The basic structure of the Bluetooth scatternet network manager system (BSNMS) of the
present invention comprises a database for the server (master: BSNM Server). This
database is designed to contain all the information about slaves or clients (BSNM Clients)
of the scatternet like:
1) Supported services (Example: Phone Book access profile, printer, Hands free, ftp,
serial access profile etc.)
2) Device status (Active/Low power Mode).
3) BD-address's.
4) pin key.
5) link key.
6) Protocols.
7) security related issues.
BSNMS clients will share their respective information with the master (BSNM Server).
As shown in Figure 2, the BSNM Server and BSNM Client includes Bluetooth core stack
comprising a lower stack (radio + baseband firmaware + Link manager protocol) and an
upper stack (l_2cap and above layers). The Bluetooth core stack allows the BSNMS server
and clients to share the database information with each other via Bluetooth technology.

-11-
Bluetooth devices are provided which contain a radio as well as base-band firmware as a
part of lower stack. The radio provides the digital signal processing component of the
system and uses the adaptive frequency hopping techniques to minimize the interference
level, and the baseband processes these signals. The link controller handles all the
baseband functions and supports the link manager. It sends and receives data, identifies
the sending device, performs authentication, and determines the type of frame to use for
sending transmissions. The link controller also directs how devices listen for transmissions
from other devices and can move devices into power-saving modes.
The link manager, located on top of the link controller, controls setup, authentication, link
Configuration and other low-level protocols. Together, the baseband and the link
manager establish connections for the network. By using Bluetooth functionalities
BSNMS clients and server will exchange the data.
In the Bluetooth scattemet manager system (BSNMS) of the present invention one device
will act as BSNMS server and it will maintain a database about all members in the
scatternet. It updates the database whenever any change in the service of the BSNM
client or any new BSNM client enters in to network.

-12-
As already mentioned earlier in the prior art system when any other device in the
scatternet wants to know about the information on newly joined devices or existing
devices, it is required to do so by device discovery and service search requests for finding
the information in the present invention a standard for BSNMS profile is provided.
Service discovery has to be done individually to each Bluetooth device for knowing
whether the device is supporting the required service or not (ex: Suppose a Bluetooth
device requires the Bluetooth Printer then it will do service search for all available
Bluetooth devices in the vicinity one by one, and all devices will respond with their
provided services. From that response it selects the Bluetooth printer and it connect to
that device) In case it is not supported the service search has to be repeated for all other
available devices in the vicinity. In Pairing process device will trust with each other by
generating link Key. So in the present invention a standard for Bluetooth scatternet
network manager system is defined in which master will act as a BSNM server and other
slaves act as a BSNM clients.
Whenever a Bluetooth device (BSNM Client) enters into a particular piconet or scatternet
First it establish a profile level connection to BSNM server it updates its features and
services with master database (BSNMS server) (ex: what are the services it supports, pin
key, bdaddress,device status etc) .Master(BSNM Server)

-13-
stores all these BSNM client services information in its database and share this
information with any BSNM slaves in the scatternet when it receives request from BSNM
client, so that any slave can connect to any other Bluetooth device for required services
just by browsing master database without performing any sdp service discovery. This
database consists of all relevant information of all available Bluetooth devices such as
supported services (Phone Book access profile, printer, Hands free, ftp, serial access
profile etc.), device status (Active/Low power Mode), BD-address's, pin key, link key,
protocols, security related issues.
It is commercially good for office environment where multiple Bluetooth accessories are
in use. For example if there are multiple Bluetooth printer devices available in an office.
If any Bluetooth device wants the printer service then it will directly browse the master
database for the available printer devices and get the service from the required Bluetooth
printer. In case the Bluetooth printer does not accept the connection for being busy or
for any authentication issues then it can try connection to another available Bluetooth
printer in the vicinity without doing any sdp service discovery.

-14-
As already stated, in the present invention a standard is provided for BSNMS. For
Bluetooth technology no network manager system (NMS) technology has so far been
used in Bluetooth devices. Using the technology of the present invention service
discovery process can be avoided by directly browsing the NMS database present in the
BSNMS server in the scatternet for the required Bluetooth service like file transfer profile
(FTP), printer, etc.
The advantages of (BSNMS) system of the present invention are: It speeds up the
discovery time. It also allows fast switchover from one device to another. Complete
information on scatternet devices are available with master which are sharable with
slaves.

-15-
WE CLAIM
1. A Bluetooth scatternet network manager system (BSNMS) comprising:
- a scatternet with piconets each having a master to act as (BSNMS) server
and a plurality of slaves to act as BSNMS clients;
- a master or server database designed to contain all information about
slaves or clients of the scattemet;
- a Bluetooth core stack configured for allowing BSNMS server and clients to
share said database information with each other; and
- BSNM server and clients containing radio and baseband firmware and upper
Bluetooth stack for transmitting and receiving information.
2. The system as claimed in claim 1, wherein the master or server database is
designed to contain information about slaves or clients like supported services,
device status, BD-addresses, pin key, link key protocols and security related
issues.

-16-
3. The system as claimed in claim 1, wherein said bluetooth core stack comprises a
lower stack and an upper stack.
4. The system as claimed in claim 3, wherein said lower stack comprises radio and
baseband firmware for providing digital signal processing component of the system
and minimizing the interference level with the aid of adaptive frequency hopping
technique.
5. The system as claimed in claim 4, said lower stack is provided with a link controller
for handling the baseband functions and supporting a link manager for receiving
data, identifying the sending device, performing authentication and determining
the type of frame to use for sending transmission.
6. The system as claimed in claim 5, wherein said link controller is adapted to direct
as to how devices listen for transmission from other devices and for moving
devices into power-saving modes.
7. A Bluetooth scatternet network manager system, substantially as herein described
and illustrated in the accompanying drawings.

The main object of the present invention therefore, is to provide a standard for Bluetooth
scatternet network manager system (BSNMS) so that each slave or client device in the
scatternet can easily get information like support services, device status and security
mode about all other members in the scatternet by using BSNMS client profile.
The BSNM Server contains a database, BSNM Server profile, Bluetooth radio and Bluetooth stack. The BSNMS master database contains all information about the BSNM clients. The Bluetooth core stack having an upper and a lower stack allow the BSNMS server and clients to share the database. The Bluetooth devices contain radio as well as baseband firware. The Bluetooth radio can transmit and receive information sent by BSNMS clients and server via the upper Bluetooth stack(L2CAP layer...).
In the present invention a standard for BSNMS profile is provided so that each slave or
client device in the scatternet can easily get the information like supported services
(Phone Book access profile, printer, Hands free, ftp, serial access profile etc.), device
status (Active/Low power Mode), BD-address's, pin key, link key, security related issues
about all other members in the scatternet by using BSNMS client. In this network, one
device will act as BSNMS master or server and it will maintain a database about all members in the scatternet. It updates the database whenever there is new Bd client detected in the network or there is change in the services of the already available Bd Client.
In a preferred embodiment the present invention provides a Bluetooth scatternet network
manager system (BSNMS) comprising: a scatternet with piconets each having a master to act as (BSNMS) server and a plurality of slaves to act as BSNMS clients; a master or server database designed to contain all information about slaves or clients of the scatternet; a Bluetooth core stack configured for allowing BSNMS server and clients to share said database information with each other; and BSNM server and clients containing radio and baseband firmware and upper Bluetooth stack for transmitting and receiving
information .