{"id":16462,"date":"2025-08-17T23:19:44","date_gmt":"2025-08-18T06:19:44","guid":{"rendered":"https:\/\/www.lansitec.com\/?p=16462"},"modified":"2025-09-02T04:59:40","modified_gmt":"2025-09-02T11:59:40","slug":"ultimate-macro-bluetooth-gateway-connectivity-guide-lorawan-nb-iot-lte-m-cat-1","status":"publish","type":"post","link":"https:\/\/www.lansitec.com\/ko\/blogs\/\uad81\uadf9\uc758-\ub9e4\ud06c\ub85c-\ube14\ub8e8\ud22c\uc2a4-\uac8c\uc774\ud2b8\uc6e8\uc774-\uc5f0\uacb0-\uac00\uc774\ub4dc-\ub85c\/","title":{"rendered":"\uad81\uadf9\uc758 \ub9e4\ud06c\ub85c \ube14\ub8e8\ud22c\uc2a4 \uac8c\uc774\ud2b8\uc6e8\uc774 \uc5f0\uacb0 \uac00\uc774\ub4dc: LoRaWAN, NB-IoT\/LTE-M, Cat-1"},"content":{"rendered":"\n

When customers first skim the data sheet of the Lansitec\u2019s Macro Bluetooth Gateway<\/a><\/strong>, they often stumble over an apparent paradox. The device is called a gateway, yet the LoRaWAN<\/a> version seems to rely on another<\/strong> LoRaWAN<\/a> gateway in the vicinity. The moment you understand why, the rest of the product range falls neatly into place.<\/p>\n\n\n\n

\"Macro<\/figure>
\n

The Lansitec Macro Bluetooth Gateway always performs the same local job: it listens to nearby BLE beacons<\/a>, reshapes the payload, and sends it northbound. What changes between the three SKUs is how that uplink reaches the internet.<\/p>\n<\/div><\/div>\n\n\n\n

\n
\n
\n
LoRaWAN Macro Bluetooth Gateway<\/a><\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
NB-IoT & LTE-M<\/strong> Macro Bluetooth Gateway<\/a><\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
LTE Cat-1<\/strong> Macro Bluetooth Gateway<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

What is a Macro Bluetooth Gateway?<\/h2>\n\n\n\n

In the LoRaWAN<\/a> ecosystem, the Macro Bluetooth Gateway plays the role of a LoRaWAN<\/a> end-device, not a base-station. But this does not mean it is not a gateway.<\/p>\n\n\n\n

How a Macro Bluetooth Gateway Works<\/h3>\n\n\n\n

It scans nearby BLE beacons<\/a>, repackages their data, and then emits that data over its own LoRa radio. The catalog phrases this clearly: the Macro \u201cforwards it to LoRaWAN<\/a> gateways<\/a> for real-time monitoring\u201d and \u201ctransmit \u2026 BLE sensor readings to LoRaWAN<\/a> gateways\u201d.<\/p>\n\n\n\n

How LoRaWAN Bluetooth Gateway Work<\/h3>\n\n\n\n

LoRaWAN<\/a> uses a star-of-stars<\/strong> topology:<\/p>\n\n\n\n

    \n
  1. End-devices<\/strong> (sensors<\/a>, trackers\u2026 or this Macro) talk via LoRa.<\/li>\n\n\n\n
  2. One or more LoRaWAN<\/a> gateways<\/a><\/strong> (a.k.a. base stations) simply listen, de-duplicate, and relay those RF packets over IP (Ethernet, cellular, Wi-Fi) to a Network Server<\/strong>.<\/li>\n\n\n\n
  3. The server handles security, deduplication, and forwards the data to your application.<\/li>\n<\/ol>\n\n\n\n

    End-devices cannot forward each other\u2019s traffic and have no IP backhaul of their own, so at least one true LoRaWAN<\/a> gateway must be within RF range to pass the macros\u2019 uplinks onward.<\/p>\n\n\n\n

    Why is the Bluetooth Gateway Naming Confusing?<\/h3>\n\n\n\n

    Lansitec calls the product a \u201cBluetooth Gateway\u201d because it bridges Bluetooth \u279c LoRaWAN<\/a><\/strong>. In LoRaWAN<\/a> terminology, though, it\u2019s just another node<\/strong>. The \u201creal\u201d LoRaWAN<\/a> gateway is the larger box (often on a mast or rooftop) with both a LoRa concentrator and an IP connection.<\/p>\n\n\n\n

    When You Don\u2019t Need a Separate LoRaWAN Gateway<\/h3>\n\n\n\n

    If your site already sits under public LoRaWAN coverage<\/a><\/strong> (e.g., a Helium hotspot <\/a>or a carrier-operated gateway) and the Macro\u2019s 22\u201330 dBm radio can reach it, you\u2019re done. Otherwise, you\u2019ll deploy an indoor\/outdoor LoRaWAN<\/a> gateway of your own and point it at The Things Stack, ChirpStack, etc.<\/p>\n\n\n\n

    Think of the Macro as a talkative sensor: fantastic at gathering BLE traffic, but it still needs a \u201ctower\u201d to shout to the cloud for it.<\/p>\n\n\n\n

    Bluetooth Gateway Network Topologies: LoRaWAN vs Cellular<\/h2>\n\n\n\n

    So, the beacons<\/a> talk to the gateway via BLE, then the gateway talks to another gateway via LoRaWAN<\/a>, and then that other gateway connects the data to the network server where it can be used, correct? And for the other variants, can they directly transmit the data to the NS? Don’t they also need a device in the middle?<\/p>\n\n\n\n

    LoRaWAN vs NB-IoT\/LTE-M vs Cat-1: The Short Answer<\/h3>\n\n\n\n