Description
Million Operations Per Second (MOPS) is a unit of measurement representing a rate of one million operations completed per second. Within 3GPP specifications, this metric is primarily used to benchmark and specify the performance requirements of Subscriber Identity Module (SIM) cards, particularly in the context of the Universal Integrated Circuit Card (UICC) and embedded SIM (eSIM). The 'operations' referred to are typically cryptographic or processing tasks essential for network security and subscriber authentication, such as executing authentication algorithms (e.g., Milenage for 3G/4G/5G), generating cryptographic keys, or performing digital signatures.
The measurement is crucial for defining the minimum performance characteristics of UICC hardware to ensure it can support the required security procedures within acceptable time limits, especially as algorithms become more complex and authentication processes more frequent (e.g., in IoT devices with small data transmissions). Specifications like TS 26.952 (for USIM performance) detail test procedures and minimum MOPS ratings for different classes of UICC/USIM applications. For instance, a USIM intended for a high-end smartphone might have a higher MOPS requirement than one designed for a low-power IoT sensor, reflecting differences in expected usage patterns and authentication loads.
Beyond SIM cards, MOPS can be a general performance indicator for other network components involved in intensive processing, such as security gateways or network functions performing encryption/decryption at scale. It provides a standardized way to compare the computational throughput of different hardware implementations. In the evolution of mobile networks, increasing MOPS capabilities enable more robust security (through stronger, more computationally intensive algorithms), faster connection setup times, and the ability to handle massive numbers of simultaneous authentication requests from IoT devices, which is a key requirement for 5G massive Machine-Type Communication (mMTC) scenarios.
Purpose & Motivation
The specification of MOPS requirements arose from the need to guarantee a consistent user experience and network security performance across SIM cards from different manufacturers. Early SIM cards had varying processing speeds, which could lead to noticeable delays during network registration or call setup, or even cause failures in time-sensitive authentication procedures. Defining a minimum MOPS threshold ensured that all compliant SIM cards would meet a baseline performance level, preventing substandard components from degrading overall network performance.
As mobile services evolved, so did the computational demands on the SIM/UICC. The introduction of 3G and the Milenage algorithm, followed by 4G and 5G authentication, required more processing power. Furthermore, new use cases like IoT demanded SIM cards that were not only low-cost and low-power but also capable of handling authentication for a vast number of devices efficiently. The MOPS metric allows for the categorization of UICC performance classes tailored to different device types—from basic IoT modules to high-performance automotive or mobile broadband devices. It addresses the problem of ensuring that security, a foundational aspect of mobile networks, does not become a bottleneck for service accessibility or a point of failure under high load.
Key Features
- Standardized metric for UICC/USIM processing performance
- Benchmarks cryptographic operation throughput (e.g., authentications per second)
- Enables classification of SIM cards for different device categories
- Ensures consistent authentication times and user experience
- Supports scalability for massive IoT deployments
- Provides a basis for conformance testing and certification
Evolution Across Releases
Introduced performance requirements and test procedures for USIM application processing speed, establishing MOPS as a key metric. Defined initial benchmarks to ensure USIMs could handle 3G (UMTS) and emerging LTE authentication workloads within acceptable timeframes.
Defining Specifications
| Specification | Title |
|---|---|
| TS 26.952 | 3GPP TS 26.952 |
| TS 26.975 | 3GPP TS 26.975 |
| TS 26.976 | 3GPP TS 26.976 |
| TS 26.978 | 3GPP TS 26.978 |
| TS 46.055 | 3GPP TR 46.055 |