What is the difference between private and public LoRaWAN networks?

What is the difference between private and public LoRaWAN networks?

[[331465]]

The low-power wide-area network (LPWAN) technology LoRaWAN was created to wirelessly connect battery-powered objects to the Internet. The protocol targets key Internet of Things (IoT) application requirements such as two-way communication, end-to-end security, mobility, and localized services.

LoRaWAN is a wireless transmission technology developed for applications and sensors that need to send and receive small amounts of data between devices over long distances several times an hour, or only once a day. Its network can be public (relying on the antennas of telecommunications operators) or private (where network elements such as gateways and servers are under the control of the user).

LoRaWAN, as a communication protocol, provides building managers with flexibility in implementing the Internet of Things.

LoRaWAN public or private network

To help you better understand this communication technology and choose the LoRaWAN network that best suits your needs, Oriane Poulat, IoT Manager at wireless products and solutions company Adeunis, explains the evolution of both networks.

Public LoRaWAN Network

In the context of LoRaWAN, public or operated networks are deployed and managed by telephone operators. For example, in France, Orange and Objenious (a subsidiary of Bouygues Telecom) have launched their own LoRaWAN networks and resell network access as a subscription service, just like they do for portable cell phone plans. So we are operating a network that is deployed nationwide for all users, and users subscribe to one or more plans to be able to connect their IoT sensor fleet.

According to Poulat, the user journey is as follows:

  • Purchase Subscription Services>
  • Declare the sensor on the operator platform>
  • Activate Sensor>
  • Data is retrieved on the operator platform and redirected (or not) to the data processing platform.

Subscribing to a public network is more appropriate when covering a larger geographical area and using fewer sensors. Users can benefit from the telecom operator's built-in IoT platform, managed network infrastructure, and roaming services.

However, if the user is looking for better indoor range, extended scale, multiple sensors with affordable battery consumption and still meet high security requirements, a private network can be used.

In the case of a public network to be shared and used by multiple users, the installation can be for use by a single entity. For a private network, users can manage their own IoT sensors and network infrastructure.

Although France and European countries generally offer high-quality public networks, many companies that use building IT infrastructure still prefer private networks. In a private network, a business can connect its internal systems to the network without using the Internet.

Poulat explained that for a private network, users take the following steps:

  1. Purchase one or more gateways as needed>
  2. Deploy them on their site>
  3. Declare the sensor in the gateway>
  4. Create a connection between the gateway and the data processing platform>
  5. Activate Sensor>

Users who wish to control buildings, factories, campuses, etc. should consider private networks. Reliance on carrier network coverage can present limitations, and economically speaking, telecom subscriptions can become very expensive if you deploy a large number of sensors.

Yes, in a private network the enterprise is responsible for the installation of the network infrastructure (devices, gateways, servers, business applications), but this can be cost-effective in terms of scalability (for example, in a building) with a large number of connected devices.

There is no absolute superiority or inferiority. Private and public networks are not incompatible, and the line between them can be blurred. Private networks can well complement public networks with nationwide coverage, and vice versa.

When choosing a network, the most important thing is the user's technical and budgetary needs. The basic criteria for selecting a LoRaWAN network are summarized as follows:

  • Network coverage quality.
  • Distribution of sensors (countries, cities, regions, buildings).
  • In buildings: indoor, outdoor or underground installation.
  • The number of sensors deployed and the communication frequency required.
  • Safety and service life of the sensor.
  • Subscription Fees

More and more industry players, such as PropTech, facility management companies, and property owners, are looking for affordable and simple ways to use LoRaWAN in large and small- to medium-sized buildings. For large commercial buildings, there is a pressing need to improve operational and management efficiency. For small multi-family residential projects, simple installation, maintenance, and monitoring capabilities are very attractive to building community members.

<<:  Digital transformation enters the "immersion period". Huawei helps government and enterprise industries embrace digitalization without blind spots.

>>:  The Role of WiFi in the Internet of Things

Recommend

6 tips to avoid automation disasters

Senior software engineer Benjamin Willenbring was...

5G technology and its impact on the Internet of Things

5G is the latest generation of cellular network t...

Thoroughly understand computer network communication equipment and protocols

【51CTO.com original article】 Table of contents 1....

Four perspectives to teach you to understand the Internet of Things

There is no doubt that it is very convenient to c...

Juniper Networks MIST AI network solution gives network engineers "superpowers"!

[51CTO.com original article] Under the night, the...

6 steps to effective real-time monitoring across hybrid IT

For data center operations, it can be difficult t...

Talk about IPv6 and Happy Eyeballs

[[256713]] Let's look at a picture first. Fro...

Huawei Software Development Cloud helps improve WeChat mini-program code quality

In the early morning of January 9, after more tha...