Skip to content
Search
Close this search box.

How Lansitec Bluetooth Gateway Works

Document Number: 990-00522
Product Part Number:
Rev. 1.0
contact@lansitec.com

LoRaWAN supports limited number of bytes in each uplink and downlink message. The user should identify and have the gateway send useful information only. The information must include ID and other parameters. ID can be UUID, or major and minor. Eventually, the gateway sends ID + parameters + RSSI to a LoRaWAN gateway and then to the cloud.

DR

EU868

US915

EU433

AU915

CN470

AS923

KR920

IN865

STE920

0

51

11

51

51

51

51

65

51

51

0

51

53

51

51

51

51

151

51

51

0

51

126

51

51

51

51

242

51

51

0

115

242

115

115

115

115

242

115

115

0

242

242

242

242

242

242

242

242

242

0

242

-

242

242

242

242

242

242

242

Lansitec LoRa Bluetooth gateway filters the data in a Bluetooth beacon payload and sends any data in the 31 bytes payload to the LoRaWAN gateway. It supports reporting a maximum of 3 types of beacons and caches a maximum of 105 beacons (all 3 types combined). It filters each beacon with 3 blocks of data (Payload Filter Block) maximum and reports 10 data blocks maximum in its payload. When corresponding data in a beacon’s payload match the ones define in the Payload Filter Block/Blocks, the gateway reports the data in the range of the Data Blocks. Refer to chapter 4.4.3 Rule Report in the datasheet for details in the datasheet (Doc. PN. 990-01201)

Taking the ibeacon protocol as an example, the user can select the yellow parts as filters, when a beacon’s data matched them, the gateway sends the green parts to the LoRaWAN gateway. The yellow and the green parts can be defined with downlink commands.

Byte Offset

Default Value

Description

Properties

Remark

0

0

0x02

Data length – 2 bytes

Constant Preamble

Payload

1

1

0x01

Data type – flags

Constant Preamble

Filter Block 1

2

2

0x06

LE and BR/EDR flag

Constant Preamble

Data Block 1

3

3

0x1A

Data length – 26 bytes

Constant Preamble

4

4

0xFF

Data type - Manufacturer
specific data

Constant Preamble

Payload
Filter Block 2

5

5

0x4C

Manufacturer data

Constant Preamble

Data Block 2

6

6

0x00

Manufacturer data

Constant Preamble

7

7

0x02

Manufacturer data

Constant Preamble

8

8

0x15

Manufacturer data

Constant Preamble

9

9

0xF2

Proximity UUID 1st byte

User UUID

Payload

10

10

0xA5

Proximity UUID 2nd byte

User UUID

Filter Block 3

11

11

0x2D

Proximity UUID 3rd byte

User UUID

12

12

0x43

Proximity UUID 4th byte

User UUID

13

13

0xE0

Proximity UUID 5th byte

User UUID

14

14

0xAB

Proximity UUID 6th byte

User UUID

15

15

0x48

Proximity UUID 7th byte

User UUID

16

16

0x9C

Proximity UUID 8th byte

User UUID

17

17

0xB6

Proximity UUID 9th byte

User UUID

18

18

0x4C

Proximity UUID 10th byte

User UUID

19

19

0x4A

Proximity UUID 11th byte

User UUID

20

20

0x83

Proximity UUID 12th byte

User UUID

21

21

0x00

Proximity UUID 13th byte

User UUID

22

22

0x14

Proximity UUID 14th byte

User UUID

23

23

0x67

Proximity UUID 15th byte

User UUID

24

24

0x20

Proximity UUID 16th byte

User UUID

25

25

AA

Major 1st byte

Major value

Data Block 3

26

26

BB

Major 2nd byte

Major value

27

27

CC

Minor 1st byte

Minor value

28

28

CC

Minor 2nd byte

Minor value

29

29

0xB3

Signal power (Calibrated SSI@1m)

Signal power value

Data Block 4

30

30

xx*

The gateway support ibeacon, Eddystone, and other protocol. Please make sure you have the payload information of the beacon so that you know how to configure the Bluetooth gateway. We’d like to configure it for you if you want.