MobileID Solutions for Public Safety
In the early 2000s, the law enforcement community witnessed a remarkable surge in the adoption of Biometric MobileID (or RapidID) technology. This cutting-edge tool revolutionized the way officers operated in the field by swiftly comparing biometric data—ranging from fingerprints to facial features, latents, and/or irises—against various databases spanning local, state, and federal/national levels. The result? A rapid identification process that empowered law enforcement to make crucial decisions on the spot.
MobileID's applications are as diverse as they are impactful. From aiding officer field investigations to facilitating quick identifications from patrol cars, assisting medical examiner services, managing inmate bookings and transports, screening at special events, enforcing border control and immigration policies, to supporting military missions, MobileID has become indispensable in the arsenal of modern law enforcement.
MobileID has proven itself a powerful tool to enhance both officer and subject safety. While simple in concept, MobileID is much like an iceberg: not all the challenges are easily visible. As a result, these solutions require meticulous planning to integrate effectively with other public safety applications and databases. This article sheds light on the intricacies of MobileID infrastructure. It also explores some of the device technology, selection criteria, and design factors agencies must navigate to ensure the effective upgrade and/or deployment of this ever-evolving technology.
Please sign up on BCP’s website to receive a free copy of our upcoming White Paper on Mobile ID. Discover how the latest generation of MobileID is reshaping identification and paving the way for safer, more efficient public safety operations.
MobileID Infrastructure
Understanding that any MobileID solution is more than just the hardware device is an essential first step. MobileID implementations require an infrastructure to support devices in the field. While each vendor handles these tasks differently, certain building blocks are a necessary part of any MobileID solution. They include the following:
MobileID Server – Residing at the agency’s data center, this server(s) is responsible for collecting and often reporting key audit information, device activity, application authentication and permissions, and interfaces to search biometric databases.
Mobile Device Management (MDM) – A critical component of any MobileID solution deployment, an MDM can be supplied by a COTS provider or in some cases can be part of the MobileID Server. MDM is an advanced IT tool that allows an agency to manage the security of the devices and provide expedited support. Each agency can create policies in its MDM to enforce things like encryption, multi-factor authentication, and security updates.
MobileID Application – This user-facing application resides on the hardware devices (Android, iOS, Windows, Linux, etc.) and is responsible for initiating each MobileID biometric transaction.
MobileID Hardware Devices – Agencies can choose one or more hardware devices depending on their use case needs.
MobileID Device Types
Depending on the functionality they require, agencies can choose from four main types of MobileID device technologies:
All-in-One Handheld – A dedicated custom hardware device with a modified operating system focused on specific tasks, with the hardware profile of a large phone or tablet. Some of them are ruggedized or even MIL-SPEC certified. Some of these devices are also MDM software capable but, given their customized operating system, future security patches may be a challenge.
Mobile Phone/Tablet Integrated – Built on commercial of the shelf (COTS) hardware like a Samsung Galaxy or iPhone, usually with MIL-STD/SPEC tested cases. Agencies can choose among sled-style cases (designed for a specific model phone, adding one or more biometric scanners that connect to the charge port of the phone/tablet). These integrated devices are compatible with most MDM solutions and can be used alongside other applications, but they also have a higher chance of compatibility issues, and some cases are less rugged and resilient than typical All-in-One devices.
Bluetooth Capture Device connected to a Computer/Mobile Data Computer (MDC) – Laptop or notebook computers already installed for jails, courts, and in patrol cars (usually MDC), can also be equipped to perform MobileID searches. To achieve this capability, a Bluetooth or USB biometric capture device is attached to the computer, which then works with a web client (Google Chome, Microsoft Edge, etc.) or thick client (an application installed on the computer). This option is compatible with most MDM solutions, but its link to a computer limits the device’s biometric scanner connection range and portability.
Mobile Phone Contactless Fingerprint – This developing technology does not yet have an industry standard, but a few companies now offer contactless fingerprint capabilities using COTS smartphones with advanced cameras. The FBI currently notes “Not for use with CJIS systems” on the devices they have tested. Both accuracy and cross-vendor applications still need further development and testing, so this technology requires significant refinement to be ready for federal certification (Appendix F). However, this technology has promise and would be a good candidate for test implementation, integrated with ABIS in a large agency.
MobileID Solution Considerations
MobileID has become such an important law enforcement tool that agencies are now moving to a new generation of technology, which means they have even more choices to make. Optimizing the advantages of new applications is much more than just buying hardware.
BCP’s upcoming White Paper on MobileID goes into all of the following device selection issues in much greater detail, but in summary, solution selection includes:
FBI Certification – To date, the FBI has certified 277 MobileID products, ranging from Fingerprint Acquisition Profile (FAP) 10 to FAP 45 rating. FAP reflects the size of the sensor, which must be large enough, and have high enough resolution, to capture fingerprint(s).
Usability (UI and UX) -- Great technology must work effectively in the field to ensure wholehearted adoption by officers. Therefore, User Interface (UI) and User Experience (UX) really matter. MobileID tools need to be easy to use and reliable for your particular agency’s needs.
Quality Feedback – Immediate quality feedback is a critical part of MobileID success. Your chosen device should use nationally recognized biometric standards to analyze image quality on the device, providing feedback that allows the user to easily and quickly capture and/or recapture high quality images.
CJIS and Security – Any MobileID solution must comply with the most recent CJIS standards, many of which can be implemented via the agency’s MDM and datacenter protocols. This includes considerations such as data encryption, multi-factor authentication, audit trails, and requiring a reason for fingerprinting.
Hardware Ruggedness – These units travel with officers into all kinds of situations, so they are exposed to many environmental challenges. In addition to ruggedized cases, choose devices that have passed water, dust, and drop tests and, optimally, with IP (Ingress Protection) ratings of IP65-IP68 and MIL-STD or MIL-SPEC certification.
Accessory and Tracking Issues – Who gets which MobileID device, tracking device location and usage, appropriate accessories for field use and secure storage/charging, updating software and security through the agency’s MDM, and lifecycle planning are all considerations for these critical tools.
Service Level Agreements (SLAs) – MobileID SLAs also present many options. Do you want 24/7/365 1-hour support, a required response time <3 minutes, a False Positive or False Negative requirement, an accuracy requirement based on number of minutiae points (for latents)? With so many possibilities, SLAs require careful attention when building an RFP or negotiating contract terms,
Lifecycle Management – Keeping future-proofing in mind is extremely important. Device hardware, applications software, MobileID servers for the biometric and transaction data from mobile operations, updatability, support, and usability are all part of this equation. Furthermore, agencies should consider both current maintenance and next-generation replacement technology paths.
Cost – Cost versus functionality considerations are particularly relevant with MobileID devices, since agencies often add tens or hundreds of these devices for multiple use cases. In addition, planning must address recurring expenses and less tangible costs such as how much time officers spend using the tool. BCP’s upcoming MobileID white paper addresses cost issues in more detail.
MobileID Design Factors
MobileID must function effectively within law enforcement’s large, complex identification ecosystem. Design specifications must consider the impact of MobileID on other connected systems. For example:
Network Design – MobileID networks are more complicated because agencies have multiple choices for connection. Devices may be connected to a cellular provider’s mobile data network (i.e. Verizon, AT&T) or to a Wi-Fi hotspot. If agencies do use a cellular provider, the next question is: public or private network? Private cellular networks offer benefits such as increased security, greater monitoring, and administrative control over your devices. Of course, those benefits come at a premium cost. Public networks cost less and offer tools like a VPN to improve security.
Workflow Design – Workflows (the steps/rules each type of transaction follows) can include validation rules, conditional statements, user decision points, and other additional complexity. Each workflow should be based on a clearly understood, well-defined use case. Designing the right workflows helps your agency maintain CJIS compliance, operate more efficiently, and get the most timely and accurate results.
Multiple Databases and Search Types – MobileID devices can support three different types of database access for searches: on-board/device-specific databases, local ABIS databases, and remote databases (state, federal, or inter-agency). Furthermore, MobileID solutions allow different types of searches: one to one (1:1), one to few (1:F), and one to many (1:N or 1:M); also, multiple biometrics are selectable (1-2 prints, faces, irises).
Throughput and Response Time – MobileID is part of your agency’s overall public safety ecosystem. Therefore, data packet size, peak load, throughput, and response time for MobileID will impact networked systems such as ABIS, records management, and criminal history. If not done correctly, changing the number of devices in the field, the number of searches per time period, or the database(s) accessed can have a drastic impact on tenprint and/or latent performance.
Today’s MobileID Challenges
BCP has highlighted some of the many decisions needed when your agency decides to initially implement or upgrade your MobileID solution. Selecting the right MobileID solution involves considerations such as product(s) selection, design, workflow, funding, security, agency policies, user adoption, public scrutiny, and more. It is imperative to think of your MobileID project holistically, rather than solely relying on demonstrations of device or product capabilities. Subject matter experts can provide important guidance to support more informed decision-making.
This article underscores the complexity of MobileID deployments, which closely resemble an iceberg…there is a lot beneath the surface! Expert guidance can help streamline your project, avoiding unnecessary delays, cost overruns, and confusion by tailoring a “best fit” MobileID solution. BCP understands this powerful tool, our upcoming White Paper on MobileID will address many of its challenges in more detail.
