This topic presents frequently asked questions about COSA (Country and Operator Settings Asset), the new format MOs use in Windows 10 Version 1703 and later to provision Windows desktop devices for mobile broadband. The existing apndatabase.xml (APN database) from Windows 8, Windows 8.1, and Windows 10 versions before 1703 has been converted to COSA, which is ingestible by the new desktop provisioning framework. Note that these previous versions of Windows will continue to use the older APN database for provisioning.
For a more detailed description about COSA and the APN database, see COSA/APN database.
For more information about the submission process for COSA and the APN database, see COSA/APN database submission.
- What are the settings that MOs can specify in COSA?
- What events trigger the application of new MO settings?
- What SIM information from modems does COSA use?
- Is there an algorithm to make the best APN match?
- Where is the COSA database stored, and can it be visually inspected like apndatabase.xml?
- What happens when a device updates from Windows 10 Version 1607 (or earlier) to Windows 10 Version 1703? Are custom or manually created APNs migrated? Do they still have priority over the defaults from the database?
The settings are the same as what MOs configured in apndatabase.xml, with a few exceptions. For details, see the table in Planning your COSA/APN database submission.
Three events trigger the Windows provisioning engine to look for a change in settings:
- The insertion or removal of a physical SIM (change in ICCID)
- Reconfiguration of an eSIM (change in ICCID)
- When the device boots
For MO/MVNO discovery, Windows tries to make the best match for an available profile in the COSA database using SPN from the SIM in the modem.
In versions of Windows before Windows 10 Version 1703, MOs could specify an auto-connect order. Windows 10 Version 1703 and later continue to use a round-robin approach through all available APNs, but there is no longer a specific order that the algorithm uses.
COSA is in the format of a Windows 10 provisioning package (.ppkg). It is in the Windows\Provisioning\COSA\Microsoft folder. You can use a third-party tool, such as 7-Zip File Manager (www.7-Zip.org), to visually inspect its contents.
Note that OEM extensions to COSA, if specified in the device image, are in the COSA\OEM folder. For more information, see Customize the Country and Operator Settings Asset.
What happens when a device updates from Windows 10 Version 1607 (or earlier) to Windows 10 Version 1703? Are custom or manually created APNs migrated? Do they still have priority over the defaults from the database?
COSA replaces apndatabase.xml after the upgrade. If an APN was provisioned in the previous version, whether custom, manual, or device-provisioned via the database, it is migrated as a part of the upgrade to Version 1703 and the device continues to use it for connectivity without requiring any additional action. Manually provisioned APNs still have priority over the defaults from the database just as they did in Version 1607 and earlier.