# Class B and Class C Functionalites

**URL:** <https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903>\
**Category:** Gateways\
**Created:** [December 26, 2015, 10:11am UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903 "2015-12-26T10:11:56Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![ffwali](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/ffwali/32/38203_2.png) [@ffwali](https://www.thethingsnetwork.org/forum/u/ffwali)\
**Post date:** [December 26, 2015, 10:11am UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/1 "2015-12-26T10:11:56Z")

</div>

Hi Everyone,

Has anyone achieved Class B and C Functionality of LoRaWAN Uptill now ??  
Which available gateway supports all LoRaWAN device classes ??

---

<div class="post-metadata">

**Author:** ![Arjan](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjan/32/180_2.png) [@Arjan](https://www.thethingsnetwork.org/forum/u/Arjan)\
**Post date:** [December 26, 2015, 11:24am UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/2 "2015-12-26T11:24:53Z")

</div>

I haven’t seen any device yet that supports B or C. Also, the current TTN testbed does not yet support this.

---

<div class="post-metadata">

**Author:** ![niels](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/n/ebca7d/32.png) [@niels](https://www.thethingsnetwork.org/forum/u/niels)\
**Post date:** [December 26, 2015, 12:23pm UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/3 "2015-12-26T12:23:26Z")

</div>

TTN doesn’t even fully support class-A yet

as far as I know the following is still missing:

- no confirmed sending (yet) meaning that the node gets an acknowledgement from the gateway the packet successfully arrived.
- no dynamic over the air pairing of nodes (yet), only static (activation by personalization)
- no sending back data to the node, in class-A each end-device’s uplink transmission is followed by two short downlink receive windows, in which the “network” can send back data to the node, this is not supported yet.

anyway… you can buy any gateway you like, even the D.I.Y. ones, because they all use semtech SX1301 boards … it’s just a matter of updating firmware to get new functionality, so all g/w hardware is OK

---

<div class="post-metadata">

**Author:** ![seppestas](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/seppestas/32/242_2.png) [@seppestas](https://www.thethingsnetwork.org/forum/u/seppestas)\
**Post date:** [January 3, 2016, 10:43pm UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/4 "2016-01-03T22:43:46Z")

</div>

Well, [Semtech’s reference implementation](https://github.com/Lora-net/LoRaMac-node) supports class C devices, and IBM’s LoRaWAN in C partially supports class B devices.

While Microchip’s [RN2483](http://www.microchip.com/wwwproducts/Devices.aspx?product=RN2483) only supports class A devices, there are plenty of modules available that give direct SPI access to the SX1272/SX1276 chip allowing you to run these stacks (or you can just build your own hardware).

As for the server; the loriot.io network server seems to support class C devices, however I have only tested class A devices on that platform.

---

<div class="post-metadata">

**Author:** ![asier](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/a/ecc23a/32.png) [@asier](https://www.thethingsnetwork.org/forum/u/asier)\
**Post date:** [March 7, 2017, 3:53am UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/5 "2017-03-07T03:53:30Z")

</div>

Hello,

It’s been one year already and I was wondering if there has been some progress on the implementation of Class B and C devices. I am particularly interested in implementing a Class B end-device. I don’t know if my inAir9B supports Class B directly or needs a firmware update. Also, where can I find the code for the node (arduino) that implements Class B?

Thanks,

Asier

---

<div class="post-metadata">

**Author:** ![robg66](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/r/e19adc/32.png) [@robg66](https://www.thethingsnetwork.org/forum/u/robg66)\
**Post date:** [March 7, 2017, 10:21am UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/6 "2017-03-07T10:21:45Z")

</div>

I don’t think class B and C will be implemented.

See:

> [@SWOT Analysis on TTN](https://www.thethingsnetwork.org/forum/t/swot-analysis-on-ttn/3023/6):
>
> Hi @hoonppark, I think your analysis is very accurate. It’s very helpful for us to see what we’re doing right and where we should improve. Some comments / background: TTN Production Server planned to be released in early 2017: I’m positive that it will be before 2017. We’re almost ready to start public testing with the new version of the backend slight_smile Class A only / no plan for Class B and C: Supporting Class B devices is unfortunately not easy in a network where you don’t own/contro…

---

<div class="post-metadata">

**Author:** ![htdvisser](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/htdvisser/32/45312_2.png) [@htdvisser](https://www.thethingsnetwork.org/forum/u/htdvisser)\
**Post date:** [March 7, 2017, 10:45am UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/7 "2017-03-07T10:45:01Z")

</div>

We are definitely going to implement Class B and C in our backend, but it’s not sure if we’ll be able to fully support this in the public community network.

---

<div class="post-metadata">

**Author:** ![TijnOnlijn](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/tijnonlijn/32/27494_2.png) [@TijnOnlijn](https://www.thethingsnetwork.org/forum/u/TijnOnlijn)\
**Post date:** [March 7, 2017, 10:48am UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/8 "2017-03-07T10:48:25Z")

</div>

Do you consider them as a pair or will class C be implemented separated from (before?) class B?

---

<div class="post-metadata">

**Author:** ![htdvisser](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/htdvisser/32/45312_2.png) [@htdvisser](https://www.thethingsnetwork.org/forum/u/htdvisser)\
**Post date:** [March 7, 2017, 11:46am UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/9 "2017-03-07T11:46:17Z")

</div>

We intend to implement Class C first.

---

<div class="post-metadata">

**Author:** ![Epyon](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/epyon/32/8479_2.png) [@Epyon](https://www.thethingsnetwork.org/forum/u/Epyon)\
**Post date:** [March 7, 2017, 10:50pm UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/10 "2017-03-07T22:50:44Z")

</div>

> [@htdvisser](#):
>
> We are definitely going to implement Class B and C in our backend, but it’s not sure if we’ll be able to fully support this in the public community network.

Why not class C? Because of the risk of air time violations?

---

<div class="post-metadata">

**Author:** ![Mirmit](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/mirmit/32/11119_2.png) [@Mirmit](https://www.thethingsnetwork.org/forum/u/Mirmit)\
**Post date:** [March 8, 2017, 9:24am UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/11 "2017-03-08T09:24:03Z")

</div>

Class B require a precise synchronisation across the gateways. As the TTN network is made of various type of GW and not all of them will have access to a reliable time source (GPS receiver), the proper time synchronisation required by Class B will probably not being available.

---

<div class="post-metadata">

**Author:** ![Sylvain\_M](https://www.thethingsnetwork.org/forum/letter_avatar_proxy/v4/letter/s/839c29/32.png) [@Sylvain\_M](https://www.thethingsnetwork.org/forum/u/Sylvain_M)\
**Post date:** [March 8, 2017, 10:12pm UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/12 "2017-03-08T22:12:56Z")

</div>

All gateways with basic packet forwarding abilities should support class C, if the network server enables it (no need for special sync). Class B is something else entirely.

The Multitech gateways with build-in network server support class C.

---

<div class="post-metadata">

**Author:** ![caferacer](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/caferacer/32/31404_2.png) [@caferacer](https://www.thethingsnetwork.org/forum/u/caferacer)\
**Post date:** [July 5, 2017, 11:37am UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/13 "2017-07-05T11:37:01Z")

</div>

Does TTN network server supports Class C now?

---

<div class="post-metadata">

**Author:** ![kersing](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/kersing/32/44777_2.png) [@kersing](https://www.thethingsnetwork.org/forum/u/kersing)\
**Post date:** [July 5, 2017, 10:25pm UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/14 "2017-07-05T22:25:07Z")

</div>

No. It is still in development.

---

<div class="post-metadata">

**Author:** ![Pyrog](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/pyrog/32/35697_2.png) [@Pyrog](https://www.thethingsnetwork.org/forum/u/Pyrog)\
**Post date:** [July 26, 2017, 5:05pm UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/15 "2017-07-26T17:05:33Z")

</div>

> [@Mirmit](#):
>
> not all of them will have access to a reliable time source (GPS receiver)

Does [Network Time Protocol](https://en.wikipedia.org/wiki/Network_Time_Protocol) could be used to synchronised gateways?

> NTP can usually maintain time to within **tens of milliseconds** over the public Internet,

---

<div class="post-metadata">

**Author:** ![Pyrog](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/pyrog/32/35697_2.png) [@Pyrog](https://www.thethingsnetwork.org/forum/u/Pyrog)\
**Post date:** [July 26, 2017, 6:41pm UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/16 "2017-07-26T18:41:19Z")

</div>

How many networks could I receive?  
How to know if some gateways are in range?  
Where are they?

**The simple way seem to receive class B beacons.**  
Does some TTN gateways support class B beaconing?  
Does other networks send beacons?

In France, Objenious will support class B in 2018 ([Source](http://msiot.insa-toulouse.fr/_attachments/iot-day-actualite/INSA_IoTDays_Fouille_Objenious.pdf?download=true))  
Is there an (official) list of networks providing class B?

**If there is no class B gateways, how to detect networks and gateways?**

Thanks!

---

<div class="post-metadata">

**Author:** ![BoRRoZ](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/borroz/32/44234_2.png) [@BoRRoZ](https://www.thethingsnetwork.org/forum/u/BoRRoZ)\
**Post date:** [July 2, 2018, 9:48am UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/17 "2018-07-02T09:48:39Z")

</div>

A post was merged into an existing topic: [Class C Status](https://www.thethingsnetwork.org/t/class-c-status/12139/3)

---

<div class="post-metadata">

**Author:** ![BoRRoZ](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/borroz/32/44234_2.png) [@BoRRoZ](https://www.thethingsnetwork.org/forum/u/BoRRoZ)\
**Post date:** [July 2, 2018, 9:48am UTC](https://www.thethingsnetwork.org/forum/t/class-b-and-class-c-functionalites/903/18 "2018-07-02T09:48:59Z")

</div>


