Accessibility settings

Text size

100%

5 terms Reviewed

IoT and device software glossary

Terms you meet when software has to run on devices you do not hold in your hand: updates over the air, fleet management and control of network traffic.

Every entry is reviewed by a practitioner who builds these systems: Maciej Sułek.

What we build: IoT & Device Software Development Services

A

  • AOSP

    Android Open Source Project

    AOSP (Android Open Source Project) is the open-source code base of the Android operating system, published by Google. Device makers can build their own Android variants from it. Google apps and services (GMS) are not part of AOSP and are licensed separately.

D

  • Deep packet inspection

    Deep packet inspection (DPI) is a method of network traffic analysis that reads packet contents, not only IP addresses and ports, to identify the protocol or application behind a flow, extract fields such as host names, and allow, block or log the traffic by policy.

M

  • MDM

    Mobile device management

    Mobile device management (MDM) is software that lets an organization enroll, configure, monitor, lock and wipe phones, tablets and other devices from a central console, by sending policies to an agent or to the management interface of each device's operating system.

O

  • OTA update

    Over-the-air update

    An OTA (over-the-air) update is a software or firmware update that a device downloads and installs over a network, with no cable or service visit. FOTA is the firmware case. The package must be signed, verified on the device and recoverable when the installation fails.

S

  • Sideloading

    Sideloading is installing an app from a source other than the device's official app store, for example an APK file from a website, an email or a cable. Android asks for permission for each source, and a company that manages the device can block it with a device policy.

Free for buyers

Build your requirements checklist from this glossary

  1. Pick the terms

    Tap the plus on every term your project touches: protocols, regulations, market rules.

  2. Get it by e-mail

    For each term: the definition and what it requires from your software, written by our engineers.

  3. Use it in your RFP

    Paste the requirements into a request for proposal or use them to check what a vendor left out.

Commissioning software and the terms are piling up?

Talk to an engineer, not a salesperson. 30 minutes, we review your requirements and say what we would build first.

Talk to an engineer

Requirements checklist

For each term we send the definition and what it requires from your software. Free, no sales call needed.

Your checklist is empty. Use the plus next to a term to add it.

    Order Group sp. z o.o. (Warsaw) uses your e-mail to send the checklist (Art. 6(1)(b) GDPR) and keeps a record of the request (Art. 6(1)(f) GDPR). Marketing consent is optional and can be withdrawn at any time. Read the Privacy Policy