No Display capability

Description

No Display (ND) capability is a parameter defined in 3GPP TS 31.111, which is part of the (U)SIM Application Toolkit (USAT/ SAT) specifications. It is a piece of terminal capability information that can be stored on the UICC (Universal Integrated Circuit Card, i.e., the SIM card) or determined by the Mobile Equipment (ME - the phone or device hardware). Its primary function is to explicitly indicate that the device in which the UICC is inserted does not possess a display screen for presenting visual information to the user.

Architecturally, this capability is communicated within the device's protocol stack. During initialization or when queried by an application on the UICC (like a proactive command), the ME provides its capability details, which include the display status. The UICC can store a default value for ND capability, but the ME's reported value typically takes precedence. This information is then available to the USAT runtime environment. When the network or a value-added service (VAS) provider sends a command that requires visual interaction—such as a "Display Text" proactive command, a menu selection request, or a request for user input—the USAT application on the UICC can check the ND flag.

If the ND flag is set to TRUE, the application logic can adapt its behavior. Instead of attempting to execute a command that requires a display (which would fail or cause an error), it can trigger an alternative action. This might involve sending a different command back to the network (like sending an error cause), using an audio-based method via "Play Tone" or "Set Up Call" commands to convey information, or simply ignoring the visual command. This mechanism ensures robust service operation across a wide range of device form factors, from smartphones to display-less Machine-to-Machine (M2M) communication modules.

Purpose & Motivation

The ND capability was introduced to address the growing diversity of devices connecting to cellular networks, particularly with the rise of M2M and IoT communications. Traditional mobile services were designed with the assumption of a human user interacting via a screen and keypad. Commands in the SIM Application Toolkit, such as displaying menus, text messages from the network, or request for user input (e.g., for mobile banking), are inherently visual. Sending such commands to a device without a display—like a smart meter, an asset tracker, or a wearable with only LED indicators—would be nonsensical and could cause the service to malfunction or the device to enter an error state.

The purpose of the ND flag is to enable service adaptability and backward compatibility. It allows service providers and network applications to design services that can gracefully degrade or offer alternative interaction modes based on device capabilities. This prevents service failures and improves the user experience (or machine experience) by ensuring that only appropriate commands are sent. Its creation was motivated by the need for a standardized, low-level signaling method to distinguish between devices with full user interfaces and those designed for autonomous, headless operation, thereby facilitating the reliable deployment of automated services across heterogeneous device ecosystems.

Key Features

• Defined as a terminal capability parameter in USAT/ SAT specifications (TS 31.111)
• Can be stored on the UICC (as a default) and reported by the Mobile Equipment
• Used by UICC applications to conditionally execute or reject display-dependent proactive commands
• Enables service adaptation for audio-only or non-interactive devices
• Critical for reliable operation of M2M and IoT devices lacking a user display
• Prevents errors and unnecessary signaling from failed display command attempts

Evolution Across Releases

Defining Specifications