Windows Mobile 6.5 Network Configuration Tools

Windows Mobile 6.5 featured specialized network operator auto-configuration utilities designed to eliminate manual setup for mobile data, multimedia messaging (MMS), and dial-up connections. This article examines the primary built-in tools and protocols—specifically the native Connection Setup application and Open Mobile Alliance provisioning standards—that automated cellular configuration upon detecting a subscriber identity module (SIM) card.

Connection Setup

The primary user-facing auto-configuration utility in Windows Mobile 6.5 was Connection Setup (often located under Settings > Connections > Connection Setup). Originally introduced in Windows Mobile 6 and refined in 6.5, this utility streamlined the process of configuring data connections.

When a user inserted a SIM card or booted the device for the first time, Connection Setup performed the following actions:

  • SIM Identification: It read the International Mobile Subscriber Identity (IMSI) from the SIM card to extract the Mobile Country Code (MCC) and Mobile Network Code (MNC).
  • Database Matching: It matched the MCC/MNC against an internal database containing network profiles for hundreds of mobile network operators worldwide.
  • Automatic Provisioning: It configured Access Point Names (APNs), proxy settings, WAP gateways, and MMS server URLs without requiring manual data entry from the user.

If a SIM card belonged to a Mobile Virtual Network Operator (MVNO) or a country with multiple matching operator profiles, Connection Setup prompted the user to select their specific carrier from a narrowed-down list.

OMA Client Provisioning (OMA CP)

Windows Mobile 6.5 natively supported the Open Mobile Alliance Client Provisioning (OMA CP) standard. This utility operated in the background to handle Over-The-Air (OTA) configuration messages sent directly by network operators.

When a subscriber joined a network or updated their plan, the operator transmitted binary SMS messages containing signed configuration XML (WAP Provisioning Documents). The Windows Mobile provisioning engine parsed these messages to:

  • Update APN settings for high-speed packet access (HSDPA/UMTS/EDGE).
  • Configure multimedia messaging service centers (MMSCs).
  • Update browser homepage bookmarks and carrier-specific security certificates.

OMA Device Management (OMA DM)

For CDMA networks (such as Verizon and Sprint) and select GSM carriers, Windows Mobile 6.5 included an OMA Device Management (OMA DM) client. This framework managed carrier-specific provisioning sessions, allowing operators to automatically update roaming lists (PRL), firmware settings, and data profiles over an active IP connection.

OEM Variations and Extensibility

While Microsoft provided the base APIs and the standard Connection Setup utility, device manufacturers often supplied enhanced versions. For example, HTC integrated its own "HTC Connection Setup" (also referred to as the Network Wizard) on Windows Mobile 6.5 devices. These OEM utilities relied on an updated local database of XML files (signed_config.xml) that could be refreshed independently of full operating system updates, ensuring compatibility with new network operators and MVNOs.