Tech.co – August 11, 2016 – When new technology hits the market, early adopters often find themselves carrying the burden of high development costs. But over time, industries mature, technologies evolve, and more players enter the fray. And once variety and competition rise, costs drop drastically. The internet of things (IoT) is no exception to this inevitable trend. Read more>>
Purpose-built IoT network to enable access to a host of applications for smart energy, agriculture and other sustainability solutions
SAN DIEGO – August 10, 2016 – Ingenu Inc.™, the pioneer in delivering connectivity exclusively to machines, today announced availability of its Machine Network™ in Phoenix. With a coverage area of more than 1,850 square miles, the network provides Internet of Things (IoT) connectivity to the sixth-largest city in the United States, serving a population of over 3.1 million.
Ingenu’s Machine Network is powered by the company’s patented RPMA® (Random Phase Multiple Access) communication technology, which provides robust, reliable connectivity across a variety of operating environments. Although the topology of Phoenix is vast, the urban and remote areas are served by only 10 RPMA access points, which is significantly less infrastructure than would be required with comparable cellular coverage.
“Adding this type of smart city technology is a real advantage for our economy,” said Greg Stanton, Mayor of Phoenix. “Private networks and machine-to-machine connectivity will help Phoenix, and other cities working to become more sustainable, to find new efficiencies and cost savings.”
“Ingenu is laying the groundwork for development of smart applications and devices to serve the needs of the Phoenix metropolitan area,” said Tom Gregor, Ingenu’s president and GM, Machine Network. “The company’s proven expertise in delivering smart city solutions and the immediate availability of Machine Network connectivity in the area will support the city’s IoT initiatives for many years to come.”
The Machine Network build-out is now underway across the United States, and will serve more than 30 major metropolitan areas by the end of 2016. The Machine Network currently provides more than 100,000 square miles of wireless coverage for a host of IoT applications. For specific information on the Phoenix Machine Network, visit www.ingenu.com/technology/machine-network/cities/phoenix/.
Ingenu will be collaborating with the developer community in the Phoenix area through its sponsorship of Phoenix Mobile and IoT Festival 2016, taking place September 24, 2016. For detailed information on the event, visit www.meetup.com/phxmobi/events/233021842/.
About RPMA
Utilizing globally available spectrum, Ingenu’s RPMA® (Random Phase Multiple Access) technology is purpose-built for M2M/IoT connectivity, offering unparalleled range, coverage and capacity with extremely low power requirements and longer-lasting battery life. It uniquely enables devices to connect more efficiently and cost-effectively in both the uplink and downlink. Requiring fewer towers to provide coverage to large areas (1:10 to 1:30 radio towers needed for RPMA vs. cellular), RPMA is rapidly becoming a global standard for IoT communication. For more information on RPMA technology, visit www.ingenu.com/technology/rpma/
About Ingenu Inc.
Ingenu™ is building the first wireless Machine Network™, the world’s largest IoT network dedicated to LPWA (low-power, wide-area) connectivity for machines only. Operating on universal spectrum, the company’s RPMA® technology is a proven standard for connecting Internet of Things (IoT) and machine-to-machine (M2M) devices around the world, with 38 private networks deployed over seven years. The Machine Network will have further reach, global range and longer lasting battery life than any existing network. It is also future-proof: enabling technology solution providers to maximize their product’s efficiency and longevity, with unparalleled control and visibility. Ingenu is led by a highly experienced team and backed by one of the strongest boards in the industry, including veterans from Verizon and Qualcomm. Information about Ingenu can be found at www.ingenu.com, or follow us on Twitter @ingenunetworks.
5G cellular is touted to be a great many things and can be anything, but without actual specifications being written, it is nothing. However, some common themes have emerged from various participants. With the announcement of a US-focused 5G consortium, there is at least a bit more clarity. That announcement coupled with this one by the FCC where they released “nearly 11 gigahertz of high-frequency spectrum for mobile, flexible and fixed-use wireless broadband”, shows that 5G will continue the cellular world’s chase after greater amounts of throughput. This makes sense, as their primary customers today are high-throughput devices like smartphones. And, from the way things look, they intend to expand into replacing our cable box wires with wireless cable boxes. If you think that the importance of spectrum for high-throughput uses was intense today, then tomorrow’s devices will leave you floored.
IoT Agenda – August 3, 2016 – Wireless connectivity is inherent to IoT, and while most IoT solutions rely on local, personal and proximity-based connectivity (e.g., Zigbee, Bluetooth, Wi-Fi and RFID), there are currently over 300 million IoT devices that use wireless wide area networks (WWAN), provided primarily by mobile operators. Tolaga Research forecasts that the number of connections will increase from 300 million to 1.45 billion by 2020, and 4.63 billion 2025. Read more>>
Business2Community – August 3, 2016 – With economies of scale, small businesses face an inherent uphill battle. To compete with large, well-oiled machines of mass production, these humbler entities need to leverage every advantage they can get. Read more>>
If you ever make it out to an IoT conference and look at the speaking agenda, you will invariably find at least a couple of panels or keynotes that will discuss the impending boom of the IoT. I’ve been in the industry for enough time that I no longer ask when that boom is coming, but when we’re actually going to stop talking about it. The fact is, the overused “hockey stick” term has become quite passé (and even I, being from Canada, love hockey). It’s time for the marketplace as a whole to start talking about the growth that is happening; no longer the growth that will happen.
So, let’s start fresh here and put the future in the past. We all know there are going to be a lot of devices that make their way online. Done.
The IoT does not need to be related to a hockey stick anymore
The topic that we should be discussing is how our infrastructure will need to be designed to support the long-term viability of those gazillions of devices. We’re so excited to flood the IoT with all kinds of things that we tend to overlook the ability of technologies to support those things.
When it comes down to it, we really should be talking about one critical question: how are our networks going to be able to handle all of these things?
Up to this point, all of the fanning of flames around the growth that’s quickly coming at us is just something that analysts use to draw in eyeballs. The fact is that our connected infrastructure is like a fire that starts to grow in size only to have a network sunset or new standard come along to throw a nice big bucket of water on those growing flames.
Times are changing and technologies have emerged that give priority to this blaze of IoT growth. This is critical to the boom that has been forecasted for years. Now, solution developers can put business plans in place that will have maturity dates of more than just a couple of years.
So, now that those technologies are budding, it’s time to ask the right questions. Those questions are centered on capacity, coverage, and longevity.
Many new technologies, while dedicated to machines, do not have the ability to support more than just a couple thousand devices per access point. This is a big problem when we’re talking about a flood of connected things. It’s critical that the industry start looking a little closer at the capacity component.
When it comes to coverage, the things that make up the IoT are not always where people are. That’s what makes the IoT so valuable: remote devices can be where people don’t have to be. Coverage, especially around cellular-based technologies, is often designed and built for people. The IoT needs affordable coverage in all kinds of places.
Lastly, as an industry we need to shift the conversation to network longevity. This is that bucket of water that keeps on dashing the flames of IoT growth. It should be part of the conversation every time a solution provider evaluates a network technology. How long is that technology going to be around? If history is any indicator, most cellular standards only last a handful of years. This isn’t going to cut it as the world becomes more and more connected.
So, let’s put away the hockey sticks for a season and just focus on the things that will get us there.
I would like to address an aspect of Low-Power, Wide-Area (LPWA) networking that is extremely important yet receives little attention: capacity. Capacity is a measure of how many devices a piece of networking infrastructure may support and/or how rich of a data model a network can provide to those devices.
Below are LPWA technology comparisons that either ignore capacity entirely, or use unjustified vendor claims that are often simply based on the amount of addressing space supported.
http://frankrayal.com/2016/06/11/comparative-look-at-lpwa-performance/
http://lora.multitech.com/white-papers/lpwa_white_paper_86003000_2016-06-13.pdf
http://www.eejournal.com/archives/articles/20150907-lpwa/
http://www.eetimes.com/document.asp?doc_id=1328365&page_number=3
These comparisons spend much of their attention on supported link data rates, thus missing the point fundamentally on what a wide area network (WAN) is supposed to do. A WAN in general is not about delivering data rates to a single endpoint, rather, it is fundamentally about providing high-capacity connectivity to a large number of endpoints.
Here’s an analogy. When you order a pizza, would you be comfortable understanding a range of size of individual pizza slices you might receive (analogous to range of data rates), but giving the pizza parlor full control of the number of slices that they will deliver as well as the sizes of those slices (as long as they are within the stated pizza slice range)? If this pizza slice scenario makes perfect sense, then these “data rate centric” frameworks are for you. But, if you’re like me, and prefer ordering a pizza based on the size of the pizza, then you would likely be more comfortable with a different measure – one that examines the “capacity” of the system. Just as the size of a pizza is indicative of the number of hungry family members that can be satiated (or often over-satiated), capacity is a measure of how many IoT devices may be served by a network based on their data needs. We should probably have colored the circles more pizza-colored for clarity. As you can imagine, insufficient capacity means not being able to build a profitable network…or analogously, whether that pizza parlor can stay in business.
If you would like to understand the details behind these calculations, please check out Appendix A through C of How RPMA Works: The Making of RPMA.
On a side-note, I was surprised to see RPMA represented as inferior coverage in this framework. We work through the link budget calculations in Section 2.3 of the same document (How RPMA Works: The Making of RPMA) and make the point that RPMA has a massive coverage advantage.
A common misconception among those investigating RPMA for the first time is that the 2.4GHz band is too crowded. The Big Bad Wolf, Wi-Fi rules this domain, along with his evil minions, Bluetooth baby monitors – pretty scary, right? The perception is that this space must be riddled with interference, however, this is false.
We have all been there. It’s a Saturday night at Wal-Mart. It’s the last minute grocery run for milk and a cartoon of eggs. You hustle through the store, and are ready to check out two minutes later. You get to the checkout lanes and realize the whole town has decided to check out at the same time. All twenty lanes are jam packed. You slump your shoulders and are resigned to wait a half hour to get through the line. Then, voila! Magically, 80 checkout lanes are suddenly fully staffed and open to receive you. You bypass big bad Wi-Fi with his two carts full of groceries and move to a lane near the edge of the store. There is no line and you are out of the store a couple minutes later.
So it is with the 2.4GHz spectrum. As it turns out, the 2.4GHz spectrum is composed of 80 distinct 1MHz channels. This provides an enormous amount of flexibility, especially given that an RPMA network can reside in a single 1MHz channel. It is well documented where the Wi-Fi bands lay, and Ingenu has wisely chosen to deploy RPMA outside of those channels. In fact, there are eleven 1MHz channels completely clear of Wi-Fi on which RPMA can operate.
While choosing a channel that is free and clear of Wi-Fi resolves the majority of inquiries regarding RPMA’s handling of interference, it is but one of the many methods RPMA employs to overcome interference. Physical layer mechanisms of the network like direct-sequence spread spectrum, and forward error correction have been essential in rolling out over 30 private RPMA networks across five continents over the past eight years. RPMA is a globally proven and available technology, and from the onset has been prepared to wisely navigate the interference concerns of the 2.4GHz spectrum.
We have asserted textbook style categories for Low-Power, Wide-Area (LPWA) connectivity Blog 1: Categories of LPWA Modulation Schemes. Then we went back to basics to get some framework and vocabulary in place to discuss these various schemes in Blog 2: Back to Basics – The Shannon Hartley Theorem, where we introduced the critical concepts of spectral efficiency (η), Eb/No, and how a point of diminishing returns can be reached in the quest to reach the Shannon Limit. In Blog 3: Chirp Spread Spectrum (CSS): The Jell-O of Non-Coherent M-ary Modulation, I confirmed that CSS can be treated more generally as Non-Coherent M-ary Modulation (NC-MM).
And then in Blog 4: “Spreading” – A Shannon-Hartley Loophole?, we discussed in more detail technologies that use links with very low spectral efficiency (η << 0.1) and the capacity implications with three concrete examples: the Sigfox® technology, LoRa™, and Ingenu’s RPMA®.
In this blog, we will set the stage with a description of a public network business model including how the fundamentals of coverage and capacity fit into building that business. Given that framework, I will then go onto discuss how the three technologies highlighted below (the Sigfox technology, LoRa, and RPMA) compare on the economics of coverage (building the network), capacity (monetizing the network), and capacity scalability or cell splitting (growing a successful network.)
| Category | Local Area Network | Wide Area Network |
| Ultra Narrow Band
(UNB) |
Sigfox
Telensa N-Wave WaveIOT |
|
| Non-Coherent M-ary Modulation (NC-MM) | Bluetooth
802.11b LoRa (CSS) Sensus (7-FSK) |
GSM/GPRS
EC-GSM
|
| Direct Sequence Spread Spectrum (DSSS) | 802.11
Zigbee
|
W-CDMA
RPMA |
| Orthogonal Frequency Division Multiplexing
(OFDM) |
802.11a/g | LTE
WiMax NB-IOT |
Setting the Stage: The Public Network Business
The public network business requires two general components: a carrier, and applications that may benefit from that network. Let’s define these roles and look at a public LPWA network from these points of view:
The LPWA business begins with the carrier. Typically, the carrier must invest in building the network prior to revenue being realized. Let’s introduce a few key terms to bridge the LPWA economics to the LPWA technology:
From a carrier’s point of view, investment in coverage is a slight “dip in the road” in terms of outward cash-flow; capacity represents that “road up the mountain” in turns of how profitable that network may be based on number of devices supported.
Coverage
To build a network economically means that each piece of infrastructure must cover large amounts of area with high probability. This means that the range of the link must be as high as possible, which, in turn, means the receiver sensitivity must be a good as possible.
In the figure below, we show the amount of typical reliable coverage that can be expected with the three approaches based on the analysis in Section 2.3 of How RPMA Works: The Making of RPMA. Naturally, the cost of a carrier covering a large region is far lower if each tower is capable of covering the large area shown for RPMA.
Capacity
It is important for a technology to allow for connection of a sufficient number of endpoints per piece of networking equipment to make long-term economic sense. There are costs to delivering LPWA connectivity including the infrastructure cost, the deployment cost, and any maintenance costs. These costs need to be shared among a tremendous number of devices such that each device’s share of the burden is very low. Keep in mind, these are typically low-value devices that can only bear minimal networking expense. If you take a look at the figure below, you will see that RPMA supports a factor of 60x to 1300x more data per piece of networking infrastructure (which equate to more 60x to 1300x more devices) relative to LoRa (exactly where in that range depends whether we are talking uplink/downlink and the particular regulatory domain). The Sigfox technology numbers are similar. Not surprisingly, the 60x to 1300x reduction in the per device connectivity cost is the difference between making the economics of the network work at all, and being able to make the economics of the network work easily.
The Sigfox technology is argued to serve only very low-bandwidth devices and thus, capacity is not an important attribute for the low-end devices they serve. There are two main problems with this argument:
Note the number of devices supported on average per piece of network infrastructure as shown below and imagine the amount of revenue per endpoint for the Sigfox technology and LoRa. In our opinion, these numbers will not support a profitable carrier business model if you assume reasonable connectivity cost per endpoint as revenue.
An additional headwind LoRa in particular faces is the lack of selectivity (discussed in more depth in Section 2.10 of How RPMA Works: The Making of RPMA.) where endpoints that are deployed on private LoRa networks actually consume capacity on overlapping public networks – far more capacity, as a matter of fact, than had they actually been connected to the public LoRa network.
Capacity Scaling (Cell Splitting)
What happens when a tower is at capacity based on the number of devices shown above? As a carrier, you would probably like to add more tower locations to continue offering robust connectivity. The cellular industry has a term for this called “cell splitting” and it can be done effectively. However, not all technologies allow for offloading capacity by adding towers. All the technologies in the LAN category share this aspect including the Sigfox technology and LoRa. Due to lack of support for transmit power control (among other things), once a critical density of endpoints is reached, the system simply ceases to work robustly.
By contrast, RPMA has been built from the ground up as an LPWAN solution. It was not easy or fast to do this. It took considerable investment because a new technology had to be developed from scratch, along with a whole new type of chip to inexpensively implement the new technology with minimal cost and power. The most important thing now is that RPMA is done, commercialized, and networks and endpoints are rapidly being deployed! We believed (and we still strongly believe) that with LPWA device counts in the 10s of billions or more, an investment in a purpose-built technology was well worth it.
In future blogs, we will explore additional topics such as sunsetting, NB-IOT looming technical issues, standardization, RPMA commercial progress, and development of RPMA technology. If you would like an advanced peek into many of these topics please take a look at the document How RPMA Works: The Making of RPMA.
We have asserted textbook style categories for Low-Power, Wide-Area (LPWA) connectivity Blog 1: Categories of LPWA Modulation Schemes. Then we went back to basics to get some framework and vocabulary in place to discuss these various schemes in Blog 2: Back to Basics – The Shannon-Hartley Theorem, where we introduced the critical concepts of spectral efficiency (η), Eb/No, and how a point of diminishing returns can be reached in the quest to reach the Shannon Limit. In Blog 3: Chirp Spread Spectrum (CSS): The Jell-O of Non-Coherent M-ary Modulation, I confirmed that CSS can be treated more generally as Non Coherent M-ary Modulation (NC-MM).
So, what is “spreading”? From the most generic perspective, it is increasing receive sensitivity (thus, a longer range and more robust link) by reducing the data rate and keeping the same channel bandwidth. That underlined part is very important and represents a potential looming problem: the link data rate is becoming a trickle, and yet that link takes the same amount of valuable spectrum. The result is that the capacity could become vanishingly small. But the capacity does not have to – and therein lays the loophole.
Let’s use what we’ve learned to determine the capacity of a few well-known Low-Power, Wide-Area (LPWA) “spreading-based” connectivity technologies [LoRa™ (CSS) and RPMA®] highlighted in the table below and additionally, a well-marketed Ultra-Narrow Band (UNB) approach used as the Sigfox™ technology for comparison purposes.
| Category | Local Area Network | Wide Area Network |
| Ultra Narrow Band
(UNB) |
Sigfox
Telensa N-Wave WaveIOT |
|
| Non-Coherent M-ary Modulation (NC-MM) | Bluetooth
802.11b LoRa (CSS) Sensus (7-FSK) |
GSM/GPRS
EC-GSM
|
| Direct Sequence Spread Spectrum (DSSS) | 802.11
Zigbee
|
W-CDMA
RPMA |
| Orthogonal Frequency Division Multiplexing
(OFDM) |
802.11a/g | LTE
WiMax NB-IOT |
Recall from Blog 3: Chirp Spread Spectrum (CSS): The Jell-O of Non-Coherent M-ary Modulation, we introduced the calculation of the individual link spectral efficiency (η) for LoRa. Let’s take that information and insert the Sigfox technology and RPMA for comparison. The Sigfox technology looks great and RPMA looks worse than even the meager spectral efficiency of LoRa. Uh oh…Looks like RPMA is off to a rough start.
But wait, this analysis is far from complete in terms of a capacity calculation. RPMA is a WAN that allows for simultaneous transmission of overlapping waveforms. That is the loophole. Recall that the Shannon-Hartley Theorem is applicable only to a single link.
The result is that for RPMA, there is no capacity benefit for an individual link being extremely spectrally inefficient. RPMA can use extreme variable spreading (or processing gain), result in an extremely sensitive modem (-145 dBm is best in the world), and not be hit with any capacity penalty.
RPMA can demodulate 1,000 signals simultaneously for a couple of fundamental reasons:
RPMA satisfies both of these requirements; LoRa only partially satisfies the second criteria. LoRa signals at different data rates have a chance of both being resolvable which results in incremental capacity benefit (<30%), not the game-changing 1000x advantage that RPMA enables. Note that RPMA satisfies these requirements without the need for protocol overhead. This is a big differentiator from cellular technologies such as LTE (and the LPWA offshoots like NB-IOT) and I will discuss this in more depth in a future blog.
As detailed in Appendix A-C of How RPMA Works: The Making of RPMA, there are other significant factors that influence the total amount of data that can be pushed through the spectrum (ηgoodput )
| Technology | Spectral Efficiency Single Link
η link |
Spectral Efficiency
Multiple Access η MA |
Spectral Efficiency
Goodput η goodput |
| RPMA | 0.00006 to 0.008 | 0.03 | 0.0026 |
| Sigfox | 1 | 0.013 | 0.00019 |
| LoRa (US) | 0.0049 to 0.047 | 0.00057 | 0.000013 |
| LoRa (Europe) | 0.0049 to 0.0015 | 0.00017 | 0.000019 |
And that’s not all! ηgoodput is a per Hertz of bandwidth number, it still needs to be multiplied by the amount of spectrum available! Since RPMA is at 2.4 GHz where 80 MHz is available, we can use significantly more spectrum that the fractured, regional subGHz bands that the Sigfox technology and LoRa use.
| Technology | Spectral Efficiency Goodput
η goodput |
Available Spectrum (MHz)
BW |
Total Goodput
(bps) η goodput xBW |
| RPMA | 0.0026 | 16 | 41,000 |
| Sigfox | 0.00019 | 0.2 | 37 |
| Lora (US) | 0.000013 | 12.8 | 170 |
| Lora (Europe) | 0.000019 | 1.6 | 30 |
As you can see, RPMA has a massive advantage in the resultant goodput. That means a piece of RPMA network infrastructure (typically on a tower or rooftop) will be capable of servicing orders of magnitude more devices and devices with far greater data needs. We’ll crunch some numbers on this in Blog 5 – The Economics of Receiver Sensitivity and Spectral Efficiency.
At any point, if you’re interested in a more in-depth treatment of these topics, please download, How RPMA Works: The Making of RPMA.