Many smartphone users are already familiar with LTE—or Long Term Evolution, typically referred to as a Fourth Generation (4G) mobile connectivity technology. Now, Internet of Things and machine-to-machine communications devices are getting onboard with LTE. In much of the world, this wireless standard has superseded the older, slower standards of 2G and 3G for mobile phones, with over 75% penetration across the US, Europe, and especially in Asia. LTE was designed to use a new protocol called Orthogonal Frequency Domain Multiple Access (OFDMA), and it has many advantages for IoT/M2M that are just now becoming apparent.
You may be familiar with SIM (subscriber identity module) cards found in cell phones, but did you know SIM cards are also used to serve a range of applications other than mobile phone usage and tracking? The purpose of SIM cards is to access wireless networks and transmit data, which makes them a cornerstone in the development of Internet of Things technology. Due to the elaborate and industrious nature of IoT, the applications an IoT SIM card must endure are much more rigorous and taxing than the abuse an average cell phone takes, presenting new challenges for the card itself.
Are you a new Neo customer? You may be wondering how to understand the monthly bill you receive for Neo’s self-serve IoT connectivity. It’s pretty simple, but it’s also worth taking a careful look at each line-item to make sure you know what each charge is. So let’s review.
A SIM card (subscriber identity module) is used to identify and allow users access to a wireless network. It is the gatekeeper for wireless networks and ensures every user on the network is authorized.
Most people are familiar with the SIM cards found in cell phones, but Internet of Things technology requires a different kind of SIM card, such as a Neo SIM, for hardware to transmit data. Any device’s access to a network is dependent on the SIM card state: Assigned, Provisioned, Active-Billed, Suspended, or Cancelled. Automatic and manual triggers allow Neo users to switch between each of these states. Manual triggers occur by using AerPort or programming an application using Aeris AerAdmin API, while automatic triggers occur when certain criteria or usage limits are met.