Multi-zone devices with Monarch
28 August, 2019 by
Multi-zone devices with Monarch
Natalia Vavilina

Because of global regulations, Sigfox currently uses 7 different radio configurations.

A Sigfox device will transmit properly only in the RC zone it is currently set up for. When leaving one RC zone and entering another, it would make sense for Sigfox devices created for global tracking to be able to switch the radio configuration they transmit in.

In order to do so, these features have to be enabled:

  • The antenna needs to be able to transmit in the desired RC zones

  • Switching between the RC zones has to be supported

  • A trigger for RC (radio configuration) zone switch has to be defined

There are several ways the RC zone change can be triggered:

Manual – through a switch/button, human action that’s not remote in general

Time – the easiest one, if you know that the device is leaving a port you can tell the device to switch to another radio zone within 2 days

GPS – if the device has a GPS module, you can program the device to switch the zones when it reaches a zone border

World Time Code emitter – you can listen to it and switch the RCZ based on location

WiFi beacons – if you have a predefined trajectory and are able to put managed WiFi beacons at transition points, you can use them to switch the zones

Monarch – a system of beacons provided by Sigfox that transmit a Monarch RCZ zone information every 5 minutes and are located at maritime ports and airports and also at the final destination – factories, warehouses, etc.

Beacons are integrated into all types of regular base stations. The major issue with Monarch is that the beacon is only available at ports and not anywhere else. So it’s necessary to somehow detect that the device is at the port and start Monarch listening. Otherwise, you must be listening all the time, which can be configured based on the knowledge of how long the device stays around the beacon/port/airport.

If the device stays there for at least one day it is enough to listen only once a day. In case it stays around the airport for at least two hours it is enough to listen to every two hours.

With SimplePack, each Monarch listening consumes roughly the same energy as 40 messages. (So we can listen once a day for 1000 days)

Also, if you know that the device will be traveling overseas for extended time periods you have an option to start listening only after a certain period of time.

If you miss the beacon port the device does not switch zones and is lost so to prevent this you must have a backup beacon in the final destination point.

If you enable Monarch listening only at ports/airports you can detect them by:

  • GPS boundary/position

  • barometric trigger landing/taking off of the airplane

  • barometric trigger lifting by few meters and loading/unloading the containers

  • accelerometer detecting the taking off and landing of the airplane

Monarch is NOT an automatic worldwide trigger and needs complete Discovery or a very use case-specific approach.

Interested to see this webinar in a recording and see slides? Find more about Sigfox technologies here.

See Monarch support in different versions of SimplePack here.