Tag formatting to connect Btooth device to 6131

[tdelazzari]

Hi there,
Do you know what is the exact tag format to connect a Btooth device to 6131 ?
See this video: http://www.nearfield.org/2007/03/blu...orporating-nfc
What exactly is in the Tag ? It certainly contains a Btooth ID. Is it a NDEF String ?

Thanks
Thomas

[geri-m]

yet there is no standardized NDEF Format for bluetooth. see http://www.nfc-forum.org/specs/. The Nokia demos rely on a proprietary implementation.

[glinskik]

Are there any nfc enabled btooth devices on the market?

[geri-m]

Too me it looks like all new devices featureing BT 2.1 and NFC (like the Nokia 6131) are capable of NFC Pairing over NFC ...

<http://www.intomobile.com/2007/03/30/bluetooth-21-gets-official.html>

[glinskik]

But how about bt headsets, picture frames, etc?

[geri-m]

I think in the picture frame thereis a tag with the BT-URI the picture frame. This enables the Nokia 6131 to establish the connection with this device. (same for the printer ...).

[glinskik]

But are any of those picture frame or printers available for me to go out and buy right now?

[tdelazzari]

Can someone from Nokia answer about the BT-URI ? What is the exact tag formatting to make this kind of demo ?
You can buy the Btooth picture frame from Parrot and stick a Tag on it That is what they are doing.

[samuuh]

Hi,

Here is the content of Bluetooth NDEF tag for Nokia 6131 NFC. Please note though that this is proprietary implementation for Nokia 6131 NFC so it might not work in any other phone!

The NDEF Record type must be EXTERNAL_RTD and the type name "urn:nfc:ext:nokia.com:bt"

For the payload you need to make following byte array:

Configuration type, 1 byte:
0x00 = Discovery only
0x01 = PIN
0x02 = Public key

Buetooth address, 6 bytes

Bluetooth Class of Device (CoD), 3 bytes
Only imaging tags are supported by Nokia 6131 NFC, so bytes should in following bit format: xxxxxxxx xxx00110 1xxxxxxx. For example 0x00 0x06 0x80

Authentication info, 16 bytes
Depends on the configuration type.

Short name length, 1 byte
Length of short name in bytes

Short name, n bytes
Displayed on screen upon discovery

There is an example for the topic:
http://wiki.forum.nokia.com/index.ph...tooth_NDEF_tag

[cde]

@glinskik: yes, there are already picture(s) frames and printer(s) available. HP has a printer and parrot has a picture frame with bluetooth support. So you have to issue a tag with BT info of the frame and then touch the tag with the phone. It works great!

[tdelazzari]

Many thanks samuuh

[TS-Tec]

Some further questions:
If I understand this thread right, the automatic bluetooth pairing via NFC is only possible with a passive tag containing proprietary code. So an automatic pairing between 2 active clients (two mobile phones, or a mobile and a pda) with a handshake is not possible yet. Am I right?
I want to implement an automatic pairing function between a 6131 an a PC with an Omnikey CardMan 5321. So the only way to do this is by emulating a passive tag with the CardMan?
Does anyone know how the further implementation with two active devices is planed? Will there be a own protocol for this action (Bluetooth 2.1 does not say how to do this)? Is it generally possible to emulate a tag with this kind of reader?

Thanks for your help!

[TS-Tec]

...nobody there to answer my questions?
Nokia experts, where are you? ;-)
I would be very grateful if some could help me...

[boraturan3]

Hi,

I believe only Discovery Type (00) works with Nokia 6131. Can anyone confirm this?

Configuration type, 1 byte:
0x00 = Discovery only
0x01 = PIN
0x02 = Public key

Can Nokia provide more details on how to construct NDEF body on different configuration (0x01, 0x02) modes?

Kind regards,

BT

[mkarger]

since 6131 does not support BT 2.1, mode 0x02 wont work. 0x01 could work..