01 · The Problem
MNO subsidy economics depend on one assumption: the subsidized device stays with the subsidizing carrier through the contractual lock period, or the subsidy is recovered. In practice, the assumption breaks on multiple fronts. Factory reset clears software-level subsidy locks within minutes. SIM swap defeats phone-number-based enforcement. Recovery mode bypasses any DPC installed as profile owner rather than device owner. Subsidy clawback collection through legacy MDMs requires manual intervention per device and rarely succeeds at scale.
For a Tier-1 LATAM carrier subsidizing several million handsets per year, even a single-digit percentage of failed subsidy recovery translates to nine-figure annual losses. The math improves only if the device control is reset-resistant, the SIM lock survives operator transitions, and the integration with the carrier's billing and CRM systems supports automated recovery workflows rather than case-by-case manual enforcement.
02 · Lockia's Approach
Reset-resistant SIM control. Cipher Protocol enforces SIM lock state at the TEE layer rather than at the software-only baseband level. Factory reset, SIM swap, and recovery-mode attempts do not clear the carrier lock. The subsidy survives the device-state transitions that defeat conventional approaches.
Multi-operator transition handling. Subsidies frequently outlive the customer's relationship with the original carrier. Lockia's policy plane supports operator-to-operator handoff workflows where one carrier's subsidy lock persists across MVNO transitions, secondary-market resale, and cross-border roaming — without requiring the device to come offline.
Billing and CRM integration. Lock state is driven by your billing system, not by Lockia's. Webhook integrations with major carrier billing platforms (Amdocs, Netcracker, Oracle BRM) update lock state when the subscriber's subsidy contract status changes. CRM integrations route subsidy clawback escalations into the carrier's existing collections workflow.
For iOS, Lockia operates a self-hosted MDM server (Lockia Cipher MDM) integrated with each carrier's Apple Business Manager tenant via Apple's published MDM protocol. APNs is mandatory infrastructure for any iOS MDM; what is removed is the additional layer of third-party MDM SaaS between the carrier and Apple. For Android, Cipher DPC runs on any Android Enterprise–capable handset, including the entry-level smartphones that dominate prepaid subsidy programs.
03 · How It Works
For carriers running zero-touch provisioning at the OEM partner stage, no QR enrollment or end-user setup is required. The customer receives a sealed device that is already Cipher-enrolled and subsidy-locked — important for entry-level prepaid segments where customer self-service capacity is limited.
Pre-provisioning
Cipher Protocol activates at the OEM partner channel or carrier distribution warehouse, before the device reaches retail. No QR enrollment required at the point of sale.
Subsidy contract creation
Carrier billing system creates the subsidy contract. Webhook to Lockia backend establishes subsidy lock policy bound to subscriber identity.
Customer activation
Customer activates the device. Cipher Protocol authenticates against the assigned carrier identity and enforces subsidy lock state per contract terms.
Lifecycle sync
Payment status, plan changes, and operator transitions sync via webhook throughout the subsidy term. Lock state adjusts automatically without manual intervention.
Contract resolution
Contract complete: subsidy unlock command. Contract breached: progressive escalation through enforcement levels. Propagation globally within 200ms.
04 · Compared To
Architectural facts, not marketing claims. Trustonic is a Google DLC certified integrator focused on Android. Knox Configure is Samsung-only, Samsung-operated. Google DLC is Google's certified-partner program. The comparison reflects what each vendor builds, not how each vendor positions.
| Lockia | Trustonic | Knox Configure | Google DLC | |
|---|---|---|---|---|
| Architecture | Sovereign UEM (AOSP DPC + Lockia-hosted MDM, MNO-integrated) | Google DLC certified integrator | Samsung Knox (Samsung-only) | Google partner program |
| OEM coverage | All Android Enterprise OEMs + iOS via ABM | Google DLC partner-certified devices | Samsung handsets only | Google-certified devices only |
| Reset resistance | Multi-layer AOSP + TEE (patent-pending) | TEE-anchored (Trustonic TEE) | Samsung Knox (TEE-anchored) | Google DPC (varies by partner) |
| SIM control | TEE-anchored SIM lock | TEE-anchored | Samsung Knox (TEE-anchored) | Software-level (varies) |
| Billing integration | Webhook + REST API to Amdocs / Netcracker / Oracle BRM | Limited (Trustonic-managed) | Limited (Samsung-managed) | Per integrator |
| Customer data path | Lockia-hosted, carrier-region | Trustonic cloud + Google | Samsung cloud | Google + certified integrator cloud |
05 · Deployment Patterns
Anonymized patterns from MNO deployments. Specific carrier names, subscriber counts, and confidential clawback metrics are omitted; the patterns are detailed enough to be credible without identifying the operator.
A Tier-1 LATAM carrier with millions of subscribers across prepaid and postpaid segments. The carrier subsidizes entry-level handsets at high volume; subsidy recovery on defaulted contracts had historically required manual case-by-case enforcement. After deploying Lockia, recovery moved to a webhook-driven workflow tied to the existing billing system, with reset-resistant device control eliminating the most common bypass paths — factory reset and SIM swap — that had defeated the prior MDM implementation.
A Brazilian MNO with subsidy clawback enforcement in retail-financed segments. Brazilian consumer-protection law constrains the subsidy clawback mechanisms operators can deploy. Lockia's progressive enforcement levels — Notice, Warning, Soft Lock, Hard Lock — allow the operator to escalate within legal limits while maintaining ongoing communication with the subscriber. A workflow that conventional binary "lock/unlock" tools cannot support, because the regulatory requirement is for graduated, traceable enforcement rather than instant deactivation.
A Caribbean operator with a multi-country roaming subsidy model. Devices subsidized in one country routinely roam to others within the operator's regional footprint. Lockia's policy plane handles cross-border lock state without requiring the device to come online in the original subsidizing country — important for operators serving migrant and seasonal-worker subscriber segments, who would otherwise lose subsidy enforcement the moment the device crossed a border.
06 · One of Many
Carrier subsidy protection is one policy configuration of Lockia's enforcement layer. The same Cipher Protocol, the same Lockia-hosted MDM, the same AOSP DPC. What differs is the integration partner (carrier billing and CRM rather than retail BNPL platforms) and the policy granularity (subsidy lifecycle states rather than installment payment states).
For an operator considering the platform: the architectural commitment is the same whether you start with subsidy protection, expand into device financing for postpaid contracts, or integrate with OEM pre-configuration for direct-to-distribution programs. One platform, multiple operational workflows. The expansion path does not require a second vendor procurement, a second integration cycle, or a second policy plane.