Getting Started

Getting Started with Monogoto's Private LTE Solution

Monogoto’s private LTE solution enables organizations to create stand-alone cellular networks, independent of public cellular operators.

The multi-tenant solution includes secure SIM cards, small cells (or bring your own) and connection to the Monogoto secure cloud. Monogoto’s connectivity management platform (CMP) facilitates full network configuration, device management and subscription control. It comes with roaming support enabling hybrid solutions where SIMs roam with public LTE networks outside of the private network's vicinity.

Data sent over Private LTE networks can be processed locally to reduce latency and to comply with data privacy regulation.

What is Private LTE?

Private LTE networks are becoming more and more popular due to the reduced complexity and operational costs. Running networks privately allows for improved quality of service, lower latency and better data security. It enables full control over the data flow and can be setup in a way that your data won't leave your servers or physical site.

Recently, the US opened a 150 MHz band for shared use, allowing companies to deploy private networks without the need to license spectrum. This shared spectrum is referred to as the Citizens Broadband Radio Service, or CBRS.

Citizens Broadband Radio Service (CBRS)

In 2015, the FCC (Federal Communications Commission) in the United States opened up the 150 MHz band ranging from 3550 to 3700 MHz, also referred to as 3.5 GHz band or CBRS

The CBRS band can be used commercially and doesn’t require heavy investments to license the specific frequencies, making it easier and cheaper to run networks privately. CBRS is perfectly suited for running private LTE networks, using the LTE Band 48.

The 3.5 GHz band it is still used by the US military as well as by satellite ground stations and entities which licensed parts of the spectrum through spectrum auctions. Hence radio traffic needs to be coordinated and prioritized. The radio coordination software which manages the use of the CBRS band is called SAS (Spectrum Access System). The SAS manages the band by coordinating data based on 3 priorities:

Tier 1 - Incumbent Access Federal users, fixed satellite service earth stations and official licensees.

Tier 2 - Priority Access Entities which licensed specific bands through spectrum auctions.

Tier 3 - General Authorized Access Any entity which registered their devices at a SAS.

Spectrum Access Administrators running SAS

Before using the LTE Band 48, the base stations (also called eNodeBs) need to be registered at the SAS. This can be done through one of the Spectrum Access Administrators, which are FCC approved companies that run the SAS. Spectrum Access Administrators are:

  • Amdocs

  • CommScope

  • Federated Wireless

  • Google

  • Sony

  • Key Bridge

For more information about CBRS, review the official FCC website:

Private LTE Architecture

There are 3 building blocks for a private LTE network:

  1. CPE (Customer Premise Equipment)

  2. eNodeB (evolved Node B)

  3. EPC (Evolved Packet Core)

CPE (Customer Premise Equipment) and UE (User Equipment)

Customer Premise Equipment and User Equipment are devices which contain a cellular modem which can communicate over the LTE band used in the Private LTE network. For example Telit’s modem: LM960A9-P

Learn more about CPE & UE

eNodeB - Evolved Node B

eNodeBs are also referred to as base stations, small cells or CBSDs when supporting CBRS. eNodeBs are hardware which form the bridge between wireless and wired communication. It sends and receives data to and from CPEs, forwards data to and from specific local or public endpoints, and it connects to the EPC to manage the network and devices.

Learn more about eNodeB

EPC - Evolved Packet Core

The Evolved Packet Core runs on Monogoto cloud and is responsible for controlling the network and the devices.

eNodeBs can be connected in 2 ways:

  1. Regular configuration - network control and data is routed to Monogoto’s cloud

  2. Local break out - network control and data are separated. Control messages are going to Monogoto’s cloud, user data is going straight to the (local) Internet via the router that is connected to the eNodeB.

Get in touch with Monogoto

Last updated