<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Joey Padden on Medium]]></title>
        <description><![CDATA[Stories by Joey Padden on Medium]]></description>
        <link>https://medium.com/@jpadden?source=rss-b1a847d001be------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ttoEsq278gjInX5XVBgc_w.jpeg</url>
            <title>Stories by Joey Padden on Medium</title>
            <link>https://medium.com/@jpadden?source=rss-b1a847d001be------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 17:21:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jpadden/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[WISP Special: Baicells, Magma, and Mikrotik platter with a side of Dual APN goodness]]></title>
            <link>https://medium.com/open5g/wisp-special-baicells-magma-and-mikrotik-platter-with-a-side-of-dual-apn-goodness-7462a7cf7729?source=rss-b1a847d001be------2</link>
            <guid isPermaLink="false">https://medium.com/p/7462a7cf7729</guid>
            <category><![CDATA[etl]]></category>
            <category><![CDATA[mikrotik]]></category>
            <category><![CDATA[5g]]></category>
            <category><![CDATA[small-cells]]></category>
            <category><![CDATA[broadband]]></category>
            <dc:creator><![CDATA[Joey Padden]]></dc:creator>
            <pubDate>Thu, 05 Nov 2020 21:19:10 GMT</pubDate>
            <atom:updated>2020-11-05T21:41:46.501Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3fxeIsb6qQCdPTOMePHOfQ.png" /></figure><p>At FreedomFi, some of our initial customers and deployments have been with WISPs doing Fixed Wireless Access (FWA) type deployments. Other customers are looking at more traditional mobility centric deployments. One universal need we saw was for bridged networks with multi-APN support. So we worked with the Magma team and the open source community and I’m excited to share that customers are going live this week with this new feature. To share the excitement, in this blog I’m going to detail the steps and configuration needed to set this up yourself.</p><blockquote>Note: Please read through once before attempting to follow along.</blockquote><p>If you want to play along, you need the following popular WISP gear:</p><ul><li>Magma Core v1.3.0 (or later)</li><li>Baicells 436Q CBRS eNodeB</li><li>Baicells Atom OD04 (or 6) CPE radio</li><li>MikroTik Router</li></ul><h3>Multi-APNs!</h3><p>APNs, or Access Point Names, are a name that 4G/5G systems use to identify a set of networking parameters. APNs are linked to a particular network interface (called the SGi interface) that provides access to particular a packet data network (or PDN). APNs have unique rate limits, QoS settings, and their own radio bearers. All of this configurability allows the operator to use APNs to segment traffic in and out of each client, based on APNs configured on the client.</p><p>Two classic examples of how you’d use dual APNs:</p><h4>Public vs Private Data</h4><p>In the Public vs Private Data example, a WISP wants to have the customer traffic and network separate from their internal management traffic. Moreover they may wish to keep the management data internal to their network for added security. This makes billing more accurate for the customer, allows specific security and QoS policy to be easily applied to each traffic type, and allows for things like IP passthrough so the WISP can allocate a public IP to the customer APN, but keep their management traffic in private IP space.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*7qAndBUSIAAhakPA5xTTig.png" /><figcaption>Dual APN Traffic Flow</figcaption></figure><h4>Data vs Voice</h4><p>The other classic dual APN scenario is data vs voice traffic separation. Now that voice is just another IP service with <a href="https://moniem-tech.com/2019/08/16/what-is-the-value-of-volte/">VoLTE </a>and <a href="https://moniem-tech.com/2020/05/27/5g-voice-over-new-radio-vonr/">VoNR</a>, in this scenario voice and data traffic are routed via different APNs allowing (again) different networking, billing, QoS, and security policy to be applied to each traffic flow. Often you’ll see an “internet” and an “IMS” APN configured in devices using this architecture.</p><p>In theory, you can have more than 2 APNs, seems like most UEs support at least 4 APNs.</p><h3>Bridge Network / IP Passthrough</h3><p>Another big part of this configuration for WISPs is the ability to set the UE and the 4G/5G packet core to bridge traffic and relay DHCP messages from the UE up to a WISP DHCP server. This can be called bridge or IP Passthrough mode. It gives the WISP the ability to distribute public IPs from a common pool across all their sites. This is a premium service more commonly asked for by business customers, which are usually obliged to pay for a static public IP.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/781/1*gjZobAdU_qatZM3s8IflxQ.png" /><figcaption>Bridged UE + Bridge Packet Core</figcaption></figure><h3>Network Requirements</h3><p>The first step is to prepare your SGi and bridge networks. For this setup we will need 3 VLANs and a bridge created on the MikroTik router.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*FbxrLiy0OFQlR5y1ITBvnw.png" /><figcaption>Network Setup for Magma Dual APN on Mikrotik</figcaption></figure><h4>Port 1</h4><p>This is your WAN port on the FreedomFi Gateway. This single physical port will have 3 VLAN sub-interfaces.</p><p>VLAN 2 is used for the FreedomFi Gateway management, it provides the connection to the orchestrator in the cloud and is used for all control and management traffic. The address on the FreedomFi Gateway can be obtained via DHCP or statically assigned in the orchestrator. The VLAN ID will assigned via the orchestrator either way.</p><p>VLAN 3 is used for your UE management APN network. This VLAN/subnet will most likely be an internal subnet using RFC 1918 address space (e.g. 10.x.x.x. or 192.168.x.x or 172.16.x.x). The addresses in this APN need to be obtained via DHCP at this time. The VLAN ID will be assigned to the APN resource in the orchestrator.</p><p>VLAN 4 is used in bridge mode on the UE to allow for full IP passthrough down to your customers edge device. This VLAN/subnet can be publicly routable or private address space. But if you want to do public IPs, this is the network for it.</p><p>In the above discussion, I used VLAN ID 2,3,4, they can be any value in the valid VLAN range from 2–4095.</p><h4>Port 2</h4><p>Port 2 is used to connect FreedomFi Gateway LAN port to the eNB via the router. We do this for failover safety. If anything happens to your FreedomFi Gateway, having a direct connection to the eNB from the router will likely save you trip to your deployment site. In MikroTik world, we simply create a new Bridge entity we call “AGW LAN to eNB Network” and add Port 2 to the bridge.</p><p>Port 2 is connected to the FreedomFi LAN port (labeled eNB1).</p><h4>Port 3</h4><p>Port 3 is configured exactly like port 2, just add it to the bridge we just made.</p><p>Port 3 is connected to the eNB WAN port.</p><p>In the end, we have a network that looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/380/1*tfAnY0pabjEZuuUl0Cpf1w.png" /><figcaption>Wiring Diagram: MikroTik + FreedomFi Gateway + eNB</figcaption></figure><h4>Other Networky Bits</h4><p>A couple of gotchas to lookout for:</p><ul><li>Jumbo frames: Because of VLAN headers and GTP headers, we need jumbo frames enabled on 3 interfaces: FreedomFi GW LAN port (eth1), the eNB WAN port, and Port 1 on the MikroTik. We use MTU = 1600 and all is happy. This avoids the customer having to set their MTU on their edge device.</li><li>DHCP options: Magma AGW code uses DHCP options to learn the gateway for each APN subnet. It sees these options when it performs DHCP on behalf of the UE at the time of attach. While possible to configure around, life is better if you ensure Option 3 (router IP) is enabled.</li></ul><h3>Magma Configuration</h3><p>OK, now that the network is ready, we need to configure Magma. Magma has always supported assigning multiple APNs to a subscriber. But, for extra fun, in v1.3 we now see three new options all built to enable a bridged multi-APN configuration. First is IP Allocation Mode, the second is Multi-APN IP Allocation, and the third is APN Resources.</p><h4>IP Allocation Mode and Multi-APN IP Allocation</h4><p>When you configure a network starting in v1.3, you see expanded options in the EPC modal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/1*l1SaM7lICTYiw7uWz540KA.png" /><figcaption>Magma Network -&gt; EPC Modal (v1.3)</figcaption></figure><p>Now we have the option to choose between NAT and DHCP_Broadcast for IP Allocation Mode. By choosing DHCP_Broadcast, you are setting the whole network to bridge mode (i.e. all AGWs in this network).</p><p>When you chose DHCP_Broadcast for IP Allocation Mode, you see the toggle for Multi-APN IP Allocation become available, toggle that on as well.</p><p>With these two settings in place, you have configured Magma to fetch a DHCP address from an upstream server for each UE, for each configured APN assigned to that subscriber. In addition, you have configured Magma to setup the OVS magic (<a href="https://oswalt.dev/2013/10/introduction-to-open-vswitch/">for more on OVS see here</a>) that makes the bridged traffic forwarding work.</p><h4>APN Resources</h4><p>The final key new element is called an APN Resource. Prior to v1.3, Magma had a single static configuration for the SGi interface, and it was a physical NIC. Now, you still keep that physical NIC configuration (found in /etc/magma/spgw.yml as <em>s1u_iface_name</em>) but you also get the option to configure VLAN IDs for specific APNs. When you do, the DHCP request, and all user plane traffic for that APN will now get VLAN tagged.</p><p>APN Resources get configured via a new modal in the Gateway configuration screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/957/1*AnCPgKjxE-kBjYv1Ane6yQ.png" /><figcaption>APN Resource Modal</figcaption></figure><h4>Other Magma Configurations:</h4><p>A couple more configurations are needed to ensure we have a working config:</p><ul><li>When adding your gateway, be sure to disable the <em>NAT Enabled</em> toggle in the EPC modal. While we disabled it at the Network level, we still need to make sure our Gateway configuration matches.</li><li>Be sure to set the Gateway management VLAN. Do to this you need to add your Gateway, then go into the JSON and edit it directly. There are good instruction for this <a href="https://magma.github.io/magma/docs/howtos/config_agw_bridged#agw-management-traffic">at the bottom of this Magma documentation page.</a></li><li>If you decide to use a static IP for your Gateway management IP, <strong><em>BE CAREFUL</em></strong> to add the /24 (or whatever length) subnet mask in the JSON element. Failing to do so causes Magma to assume a /32 and you will lose your AGWs connection to the world. Not unrecoverable, but annoying, I’ve done it twice when going too fast.</li></ul><h4>Port Forwarding</h4><p>At this point we have Magma set to work with your eNB. However, because of how Magma networking is configured, you’ll need some port forwarding rules if you want the eNB to be reachable for non-user plane traffic, things like SNMP, access to the webUI, and your SAS connection.</p><p>You’ll need to 2 port forwarding setups to make things work, one inbound and one outbound.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/599/1*_0vAH6ZZ4Osh9_Xsn9Hsrg.png" /><figcaption>Outbound NAT rule for TR-069 connection to OMC</figcaption></figure><p>The first rule we want to install will make sure the eNB can connect to Baicells OMC. OMC is where the domain proxy lives for interacting with the SAS to get you legal access to CBRS spectrum. Legal is good. So we want to make sure that connection is working.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*x1Cc1k6-iPWN55FpakHQ9Q.png" /><figcaption>Inbound forwarding rules creation script</figcaption></figure><p>The second script we have is for configuring inbound port forwarding to enable management and monitoring of the eNB. In general we forward the following proto/port pairs:</p><ol><li>TCP — 80 &amp; 443 (WebUI)</li><li>UDP — 161 (SNMP)</li><li>TCP — 27149 (Baicells SSH port)</li></ol><p>Similar to the outbound rule, we want to use the <em>uplink_br0</em> interface as our target for these rules.</p><h3>eNB Configuration</h3><p>Next we configure the eNB. We have been using the Baicells 436Q which we find performs well and has been easy to configure.</p><p>Below is a list of the key settings we use:</p><ol><li>Network -&gt; WAN -&gt; Set MTU = 1600</li><li>Network -&gt; IPsec/MME Pool -&gt; Disable MME pool, then disable IPsec (order matters)</li><li>Network -&gt; LGW -&gt; Off (<strong>this is crucial</strong>, forces S1-U to go through Magma SPGW)</li><li>BTS Info -&gt; Quick Setting -&gt; MME IP = 10.0.2.1 (remove any other MME entries)</li><li>BTS Info -&gt; Quick Setting -&gt; configure your PLMN, channel, etc. per your desired cell configuration.</li><li>OPTIONAL: BTS Setting -&gt; Management Server -&gt; SNMP Enable = On</li><li>Reboot to apply all changes in 1–6 above</li><li>Watch BTS Info -&gt; Status page and confirm your eNB can connect to both MME and OMC.</li></ol><blockquote>NOTE: We have been testing with eNB FW 2.3.6 and 2.4.4 and this setup works with both. Other versions, YMMV.</blockquote><h3>UE Configuration</h3><p>Finally, our last step, configuring the UE. We have been using the Baicells Atom OD 04, a CAT 4 LTE UE in an outdoor friendly enclosure. It uses POE for power and has some good configurability.</p><p>Our key settings here are:</p><ol><li>Network -&gt; LAN Settings -&gt; Disable DHCP (uncheck “Enable” box)</li><li>Network -&gt; WAN Settings -&gt; Network Mode -&gt; Bridged</li><li>LTE -&gt; APN Management -&gt; #1 -&gt; Mode = NAT, Name = management (all else accept defaults)</li><li>LTE -&gt; APN Management -&gt; #2 -&gt; Mode = Bridge, Name = internet, Enable = checked</li><li>OPTIONAL: System -&gt; SNMP -&gt; Enabled = checked</li></ol><blockquote>NOTE 1: The APN order matters. If you flip which APN is #1 and #2, you will run into problems with some FW versions.</blockquote><blockquote>NOTE 2: We have been testing with UE FW 2.1.4, 2.2.1, and 2.4.5 and this setup works with all three. Other versions, YMMV.</blockquote><h3>You’re done!</h3><p>The only thing left now is to put in your SIM card and have at it. You should see a couple things in your setup:</p><ul><li>A host plugged into the LAN ethernet port on your UE POE power injector should get an IP address from your “internet” VLAN as configured above. This validates that the IP is getting passed all the way down to the customer device.</li><li>Also, both inbound and outbound connections should work to the host connected to your UE. As there is no NAT, no port forwarding should be needed to get to that host, the “customer edge device” in a WISP scenario.</li><li>A host from your core network should be able to ping, SSH, access the web UI, and do SNMP get/sets on both the eNB and the UE.</li></ul><p>Special thanks to Dave @ <a href="https://wicw.net/">WiConnect Wireless</a>, the FreedomFi engineering team, Jesse @ <a href="https://na.baicells.com/">Baicells</a>, and the Magma Dev community for helping to get this new feature working.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7462a7cf7729" width="1" height="1" alt=""><hr><p><a href="https://medium.com/open5g/wisp-special-baicells-magma-and-mikrotik-platter-with-a-side-of-dual-apn-goodness-7462a7cf7729">WISP Special: Baicells, Magma, and Mikrotik platter with a side of Dual APN goodness</a> was originally published in <a href="https://medium.com/open5g">open5g</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building an Open and Private LTE Network]]></title>
            <link>https://medium.com/open5g/building-an-open-and-private-lte-network-f6acde216749?source=rss-b1a847d001be------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6acde216749</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[private-network]]></category>
            <category><![CDATA[freedomfi]]></category>
            <category><![CDATA[etl]]></category>
            <category><![CDATA[5g]]></category>
            <dc:creator><![CDATA[Joey Padden]]></dc:creator>
            <pubDate>Mon, 19 Oct 2020 03:19:43 GMT</pubDate>
            <atom:updated>2021-08-06T19:34:45.325Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*31UA3dldBM_jRXfmUZN4OA.png" /></figure><p>A couple of years ago I wrote a <a href="https://www.cablelabs.com/a-little-lte-for-you-me-build-your-own-lte-network-budget">blog about building your own LTE network</a> while I was working at CableLabs. At the time, I was focused on building a lab grade network for doing research. It didn’t have requirements for availability, scalability, or need any fancy features. Using all open source software for such a network made sense and fit the maturity of the open source options at the time.</p><p>As I reprise that post 3 years later, a lot has changed. Private networks, no matter who you ask (see: <a href="https://www.rcrwireless.com/20191023/5g/private-lte-5g-network-market-2023">here</a>, <a href="https://www.abiresearch.com/press/private-lte-will-be-us163-billion-opportunity-2025-and-foundation-5g-services-end-vertical-markets/?utm_source=Triggermail&amp;utm_medium=email&amp;utm_campaign=Post%20Blast%20bii-connectivity-and-tech:%20New%20York%20Power%20Authority%20extends%20private%20LTE%20network%20request%20%7C%20Apple%20blocks%20coronavirus%20apps%20from%20less%20reputable%20developers%20%7C%20Nvidia%20buys%20SwiftStack%20to%20enhance%20data%20management%20tools&amp;utm_term=BII%20List%20Connectivity%20ALL">here</a>, or <a href="https://www.thefastmode.com/technology-and-solution-trends/16474-private-lte-and-5g-market-to-triple-to-10b-by-2025-says-mobile-experts">here</a>) have transitioned from lab toys to a multi-billion dollar industry. Open source too has left the lab and solutions from the likes of <a href="https://www.redhat.com/en">RedHat</a>, <a href="https://www.openstack.org/">OpenStack</a>, <a href="https://www.o-ran.org/">O-RAN Alliance</a>, and the <a href="https://telecominfraproject.com/">Telecom Infra Project</a> are a growing presence in operators networks globally. As the footprint of open source grows, and network operators see the benefits of deploying open source, the industry is responding by developing open source solutions moving up the stack. Now with the introduction of the <a href="https://www.magmacore.org/">Magma project</a>, open source is moving into complex network functions like the core of the 4G and 5G mobile network.</p><p>Dumping gas on the open and private network fire, the FCC has made available commercially deployable <a href="https://www.fiercewireless.com/regulatory/cbrs-3-5-ghz-auction-concludes-raising-4-58b">CBRS spectrum that we see taking off</a> in the recent auction and as Spectrum Access Systems (SASs) go live. With it’s 3 tier access, CBRS means anyone can get a meaningful chunk of airwaves with 25 times (or more) the power of most Wi-Fi networks to deliver high quality wireless services.</p><p>In light of these changes, in this version of the build your own network how-to, I will move our target from a lab network to a commercial grade LTE network deployment. Let’s get started.</p><h4>The Ingredients</h4><p>There are 6 key components to an open and private LTE network:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eJ3m9UBDqGuruSV-PU90IA.png" /></figure><p>The marketplace for these components has changed significantly in the last few years. Today an individual or small enterprise has the ability to get a hold of commercial grade LTE components at achievable price points. That’s new, so let’s look closer.</p><h4>The Core</h4><p>Perhaps the biggest shift has come recently with the Magma Core project. Previously your only option for a commercial grade LTE core was to go to a traditional mobile vendor and pay healthily. But now, you can deploy your own instance of an open source multi-access core network from the Magma Core project. Magma provides unified core functions for 4G LTE, 5G SA, and Enterprise Wi-Fi networks, built as a set of cloud native microservices. FreedomFi has taken the Magma project and developed a curated and hardened version we sell for as little as $300 for a single Gateway network (good for up to about 5 radios). But it’s open source, if you don’t mind a little elbow grease, you can buy your own hardware/AWS machines and create your own Magma core <a href="https://magma.github.io/magma/versions">by going here</a> and pulling the latest release.</p><h4>Radios</h4><p>Next you need a radio to plug into your new core. Until recently LTE radios were tough to come buy if you weren’t a mobile network operator. And even if you could buy one, they were all built for specific licensed spectrum bands you likely weren’t allowed to radiate on. BUT! CBRS is changing all of that by creating a growing market of off the shelf radios, with varying capabilities (indoor, outdoor, low power, high power, multi-sector, multi-carrier, etc) all built for spectrum you can actually use. Vendors like <a href="https://na.baicells.com/">Baicells</a>, <a href="https://www.accelleran.com/">Accelleran</a>, <a href="https://blinqnetworks.com/">Blinq Networks</a>, and <a href="https://www.airspan.com/cbrs/">Airspan</a> all have CBRS radio portfolios. Better yet, they are available for anyone to order off websites like <a href="https://www.doubleradius.com/">DoubleRadius</a>, <a href="https://www.ispsupplies.com/">ISPSupplies</a>, and <a href="http://www.winncom.com/">WinnComm</a>. All of these offerings are giant steps ahead of a BYO radio based on a mini-pc and an SDR in terms of power output, performance, and environmental hardening; these are radios you can deploy. For a full list of devices you can hunt down, go to the <a href="https://www.cbrsalliance.org/certification/">OnGo certification</a> page and you can see a list of all the FCC approved devices.</p><p>At FreedomFi, we’ve had good luck with the Baicells 436Q and the Accelleran E1000 products in our early deployments.</p><p>A couple of gotchas to watch out for when ordering an LTE radio:</p><ol><li>LTE radios often don’t come with integrated antennas. You’ll need to chose between an omnidirectional (think donut shape coverage) or a sector antenna (more directional, focused energy) when ordering an antenna.</li><li>Features vary significantly, so looks closely. In these early days of CBRS, many products are focused at fixed wireless deployments and don’t support the common mobility features you might be expecting (e.g. seamless handover). So read the spec sheets and ask questions to make sure you are getting a radio that does what you need.</li><li>Most of these modern small cells are heavily software driven. Because of this, the same HW package can have really different functionality based on the license you purchase with it. Here again your best bet is to read the fine print and ask questions about things like carrier aggregation, split cell modes, number of UEs supported, and number of carriers.</li><li>SAS interoperability is another topic to double check. We’ll talk more about this next, but as CBRS and SAS integration is still new, not all radios play nice with all SASs yet, so ask.</li></ol><h4>Spectrum</h4><p>The spectrum game changed in 2017 when CBRS left the rule making phase and entered the market. This band is a whole new approach to sharing the valuable airwaves bouncing around the nation. <a href="https://medium.com/@freedomfi">Boris made this point clearly before</a>, so I won’t belabor it. The point here is, to get access to CBRS spectrum you need a commercial relationship with a SAS operator and most likely a Certified Professional Installer (CPI) to perform / approve your installation. As of today you have 5 choices for SAS operators (in alphabetical order) <a href="https://www.amdocs.com/spectrumONE">Amdocs</a>, <a href="http://www.commscope.com/">CommScope</a>, <a href="https://federatedwireless.com/">Federated Wireless</a>, <a href="http://g.co/sharedspectrum">Google</a>, and Sony.</p><p>At FreedomFi we’ve had good initial success testing with Federated Wireless and Google. Depending on what package you select when buying a FreedomFi Gateway, we can also provide you a SAS connection and CPI services. Or for about $600 you can take an online course from <a href="https://www.coursera.org/learn/google-cbrs-cpi-training">Google</a>, <a href="https://federatedwireless.com/certified-professional-installer/">Federated Wireless</a> or others and become a CPI yourself.</p><p>Once you have your SAS connection, the SAS will periodically make sure your radio power and channel selection aren’t going to cause interference, and configure your radio to ensure it stays that way. In this way, the SASs keep the CBRS spectrum clean and interference free, making your private network more performant.</p><p>The one gotcha I can share for SAS configuration is the units. Some power values are in dBm / MHz, others are in dBm / 10 MHz, and others can be in total power, just dBm. If you have configuration issues (e.g. keep getting error code 103 responses from SAS) triple check you haven’t mixed your units.</p><h4>SIM Cards</h4><p>I’m gonna be honest, I’ve been programming SIM cards for lab and private networks for 10 years, and they still baffle me. They are so powerful, they can do so much, but configuration and management of SIM cards is a Byzantine affair. To make things more fun, some UEs honor SIM fields strictly, others ignore various settings in favor of values stored in a black box somewhere. But as SIM cards are the literal key to LTE security, you gotta have them.</p><p>There are a handful of options on how to get SIM cards: you can talk to <a href="https://www.thalesgroup.com/en/markets/digital-identity-and-security/technology/sim">ThalesGroup</a> for tier one service, you can go to Alibaba and try your luck, or you can work with <a href="https://www.smartjac.biz/">SmartJac</a>. At FreedomFi we have always used SmartJac for their quick service and great support. Alternatively many radio providers (e.g. Baicells) will also sell you SIMs along with your radios.</p><p>For most basic private network operators, here are the important items you need to worry about, and some suggestions on how to handle them:</p><ol><li>Ki — This is the private key for each subscriber. For a lab setup, handy to have all your SIMs match. For any production network, ask your SIM provider to randomize these per card.</li><li>OP/OPc — OP is your operator secret key. OPc is a munge of Ki and OP you store in your HSS. You should pick an OP and keep it somewhere real safe. You can then provide OP to your SIM provider and they will calculate OPc using the random Ki they chose and put these in your SIMs.</li><li>IMSI — This is the subscriber identity. It is made of your PLMN + a unique number for each subscriber. More on this in the next section.</li><li>SPN — This a fun one, the Service Provider Name field in the SIM is what makes your phone say “Bob’s Wireless” of whatever name you choose for your network. Android tends to honor it and display the name, iOS phones less reliably.</li><li>PINs — Some SIMs have security PINs to enable/disable them. You can chose how secure you want your SIMs. Keep in mind the subscriber you give the SIM card to has to remember the SIM and plug it into their phone to activate the SIM. So, SIM PINs can also be a source of trouble calls.</li></ol><p>One last note on SIMs. They come in many sizes e.g. standard, micro, mini, nano. When you order SIMs, you have to select your size or chose a multi form factor card. In a multi form factor SIM, you can pop out a nano, from a mini, from a micro… etc. They are handy if you don’t know the exact set of devices you plan to support and what their SIM needs are.</p><h4>PLMN/SHMI/IMSIs</h4><p>Yeah, I know, PL-what? These fun acronyms are the way LTE/5G networks identify themselves to UEs and vice a versa. You can kinda think of PLMN like an SSID for Wi-Fi, though I’m sure many 3GPP people just cringed reading that. To deploy a private network, you need the right to use a PLMN and your SIM cards need configuration to match it.</p><p>In the case of CBRS, the CBRS Alliance has developed a shared PLMN, or Shared Home Network Indicator (SHMI) that can be used by many private network operators. There is a registration process and a bunch more detail I’ll get into in a future post. For now, <a href="https://ongoalliance.org/resource/">CBRS Alliance</a> has a good page with some specifications at the top to help understand these needed values are and how you get them. Also be sure to watch the linked webinar, it too contains good information.</p><p>Some radio vendors also have registered PLMNs that can be used with the purchase of their gear. Baicells for example provides its customers with a PLMN they can use.</p><p>Last note on identifiers, unlike SSID in Wi-Fi, they are controlled in the LTE/5G world, so be sure to use something you have the right to use. Broadcasting on someone else&#39;s PLMN is a pretty bad idea.</p><h4>UEs</h4><p>Last but not least, the User Equipment, or UE in 3GPP nerd speak, is the name for a smartphone, a dumb phone, an ethernet to LTE bridge, a USB 5G dongle, really any LTE/5G client device. There are myriad LTE and now 5G capable devices on the market. And while the air interface for LTE and 5G are well standardized, there is a lot of room in other layers of the stack for device specific behavior when it comes to getting a UE attached to and passing data on your network.</p><p>Below are some suggestions that will help you keep from draining hours fighting UE compatibility problems:</p><ol><li>In general Android will act differently than Apple products. Even within an OS ecosystem, a Samsung phone will act differently than a Google Pixel. Even the same device, with a SW update may use a different attach call flow and start or stop working with your network. So always test your SIM and your network with the device and SW version you plan to use. It is never safe to assume “it worked with X, so it will work with Y” so always test.</li><li>Some UEs are “Locked” to a carrier network. A carrier locked UE will only join that particular carriers PLMN (or set of approved PLMNs). As you shouldn’t be using someone else’s PLMN, that means the phone won’t work on your network. This may even manifest as the phone displaying an error when you put your SIM card in, or saying “no SIM” when you put your SIM in.</li><li>All UEs support a finite set of frequency bands. The cheaper the UE, the small the list usually. If the UE doesn’t support the band you are using (e.g. CBRS Band 48) there is nothing SW can do to make it. There is a great website called <a href="https://www.gsmarena.com/">gmsarena.com</a> that you can use to lookup the band support of many many smartphone UEs. For other device types be sure to check the spec sheets. If you can’t explicitly confirm a device supports your band, probably not safe to assume it does.</li></ol><h4>Let’s Do It!</h4><p>Ok, there you have it, you are armed with knowledge and links galore. If this blog made you excited to go it alone, great, get after it.</p><p>If on the other hand it made you feel like you want someone to handle all the details for you, that’s great too, contact us at <a href="https://freedomfi.com/">FreedomFi.com</a>. At FreedomFi we’re all about building private networks using open source software. We think you should do it too. If your Wi-Fi network isn’t delivering the service you need, the reach you need, the security you need, let us help build you a open and private LTE or 5G network.</p><p>Check back here, I’ll be posting more tips and explainers about open private LTE and 5G networks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6acde216749" width="1" height="1" alt=""><hr><p><a href="https://medium.com/open5g/building-an-open-and-private-lte-network-f6acde216749">Building an Open and Private LTE Network</a> was originally published in <a href="https://medium.com/open5g">open5g</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>