MIFARE DESFire EV1 vs MIFARE DESFire Light
MIFARE DESFire EV1 offers 2-8 KB memory with 3DES + AES-128 security, making it ideal for transit, campus cards, access control. MIFARE DESFire Light provides 640 bytes with AES-128 + LRP security, suited for transit tickets, loyalty, micro-payment tokens.
MIFARE DESFire EV1
MIFARE DESFire Light
MIFARE DESFire EV1 vs MIFARE DESFire Light
DESFire Light is not a stripped-down EV1 — it is a deliberately simplified product aimed at a different deployment tier: disposable, single-application transit tickets where cost sensitivity is highest.
Overview
MIFARE DESFire EV1: Full DESFire feature set — multiple AIDs, multiple file types, ISO 14443ISO 14443Standard for contactless smart cards at 13.56 MHz (Types A and B)View full →-4, AES-128 / 3DES, 2–8 KB. Designed for multi-year, multi-application card credentials.
MIFARE DESFire Light: Simplified DESFire command set, single application, fixed file structure (3 standard files, 1 backup, 1 value, 1 cyclic record), AES-128 + LRP, 640 bytes, ISO 14443-4 partial implementation. Designed for disposable transit tickets, loyalty stamps, and single-purpose tokens.
Key Differences
- Multiple applications: EV1 supports multiple independent AIDs. DESFire Light supports exactly one application.
- File system flexibility: EV1 allows configuring any combination of file types up to memory limits. DESFire Light has a fixed file layout.
- Memory: EV1 offers 2–8 KB. DESFire Light offers 640 bytes.
- LRP authenticationauthenticationIdentity verification of NFC tags/readers via passwords or cryptographyView full →: DESFire Light supports AES-128 and LRP (Leakage Resilient Primitive) — an additional authentication mode. EV1 supports AES-128 and 3DES.
- Cost: DESFire Light is priced below EV1, closer to Classic 1K, enabling the AES security upgrade at disposable-ticket cost levels.
- ISO 14443-4: Both implement ISO 14443-4 (T=CL), but DESFire Light implements a reduced command subset.
Technical Comparison
| Parameter | MIFARE DESFire EV1 | MIFARE DESFire Light |
|---|---|---|
| Memory | 2 / 4 / 8 KB | 640 bytes |
| Security | AES-128, 3DES | AES-128, LRP |
| Applications | Multiple (AID-based) | Single |
| File types | Configurable | Fixed (3+1+1+1) |
| Protocol | Full ISO 14443-4 | ISO 14443-4 (subset) |
| Proximity Check | No | No |
| Target use case | Multi-year card credential | Disposable transit ticket |
| Typical cost (volume) | $0.40–$0.80 | $0.12–$0.28 |
Use Cases
DESFire EV1
Multi-application campus cards, transit cards with long service life, corporate access combined with cafeteria and printing, government ID with access and transit.
DESFire Light
- Single-journey or limited-period transit tickets
- Event wristbands with a single access application
- Loyalty stamp cards with a value file
- Micropayment tokens for transit micro-payments
Verdict
These chips target different deployment tiers. Use DESFire EV1 (or better, EV3) when the card credential needs multiple applications or a long service life. Use DESFire Light when the deployment is a disposable, single-application ticket where cost is the primary driver and only one application needs AES protection.
おすすめ
Choose MIFARE DESFire EV1 when you need flexible file system with strong encryption; choose MIFARE DESFire Light when you need DESFire security in a cost-optimized package.