Overview of Mobile Broadband in Windows 8

Partnering with Windows to improve the customer experience

September 28, 2012

Abstract

This paper provides an overview of the mobile Broadband experience for Windows 8. It provides guidelines for mobile operators to integrate with Windows 8 and offers their customers the richest possible experience. It assumes that the reader is familiar with basic mobile broadband scenarios. This information applies to the following operating systems: Windows 8 References and resources discussed here are listed at the end of this paper. The current version of this paper is maintained on the web at: Overview of Mobile Broadband in Windows 8

Disclaimer: This document is provided as-is. Information and views expressed in this document, including URL and other Internet website references, may change without notice. Some information relates to prereleased product which may be substantially modified before its commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here. You bear the risk of using it. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes. 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 2

Document History
Date September 28, 2012 August 15, 2012 May 31, 2012 Change Updates to reflect changes in branding Updated Key Scenario Providing Accurate Usage and Plan Data to Windows with link to API usage guidance. Updated with information about the Windows 8 opportunities to streamline the mobile broadband ecosystem, the integrated account experience, Windows connection manager, project planning roles, choices of engagement for operators, operator notifications and system events, providing accurate usage and plan data to Windows, authenticating to a wireless hotspot, displaying account information to the user, and Windows components. First publication

February 28, 2012

Contents
Improved Mobility Experience in Windows 8 ................................................................ 4 Supply-Chain Simplification ....................................................................................... 5 Integrated Account Experience ................................................................................. 6 Connecting Operators with Users .............................................................................. 8 Windows Connection Manager ................................................................................. 8 Project Planning ......................................................................................................... 9 Summary .................................................................................................................. 10 Choice of Engagement for Operators .......................................................................... 11 Level 0 - No Engagement ......................................................................................... 11 Level 1 - Provide APN database entries ................................................................... 11 Level 2 - Create an operator plan purchase/top-up website................................... 11 Level 3 Create service metadata and a mobile operator app............................... 12 Level 4 Wi-Fi Hotspot offloading and providing plan and data usage information to Windows .............................................................................................................. 12 Level 5 Premium services and complimentary apps ............................................. 12 Key Scenarios ............................................................................................................... 13 Plan Purchase ........................................................................................................... 13 Purchase when mobile operator app is already installed or an alternate Internet connection is available ........................................................................................ 13 Purchase when no mobile operator app is installed and no alternate Internet connectivity is available....................................................................................... 17 Connecting an Active Device ................................................................................... 20 Operator Notifications and System Events .............................................................. 21 Providing Accurate Usage and Plan Data to Windows ............................................ 23 Authenticating to a Wireless Hotspot...................................................................... 24 Setup.................................................................................................................... 24 Credential Generation ......................................................................................... 25 Authentication ..................................................................................................... 26 Displaying Account Information to the User ........................................................... 26 Enabling other devices and app scenarios ............................................................... 27 Privileged apps..................................................................................................... 27 Wireline Operators .............................................................................................. 28
September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 3

Technical Overview ...................................................................................................... 28 Windows Components............................................................................................. 29 Provisioning Agent ............................................................................................... 29 Data Usage & Subscription Manager................................................................... 29 Windows Connection Manager ........................................................................... 29 Local Data Counters............................................................................................. 30 Mobile Broadband Service .................................................................................. 30 Mobile Broadband Class Driver ........................................................................... 30 System Event Broker ........................................................................................... 31 Windows Metadata and Internet Services (WMIS) ............................................. 31 Windows Store .................................................................................................... 31 Operator Metadata .................................................................................................. 32 Windows APN Database ...................................................................................... 32 Service Metadata................................................................................................. 32 Provisioning Metadata ........................................................................................ 32 Operator Experiences .............................................................................................. 33 Mobile Operator App .......................................................................................... 33 Operator Website ................................................................................................ 33 Wi-Fi Hotspot....................................................................................................... 34 Resources ..................................................................................................................... 34

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 4

Improved Mobility Experience in Windows 8

Windows 8 was designed to work well on a variety of PC form factors, from desktop PCs to tablet PCs. Several areas of investment in Windows 8 make it an excellent operating system for lightweight portable computing. These include: A focus on extending battery life. Touch-optimized experience. Windows Store, which provides an integrated way for users to find and acquire apps. The ability to manage wireless (Wi-Fi and mobile broadband) connections from the Windows connection manager experience. Expected availability of a variety of hardware and form factors.

Users get the most out of Windows 8 PCs when those PCs are connected to the Internet. The Start screen comes alive with tile updates. Users will be able to glance at their Start screen and quickly get information about the people, topics, and things that they care about most. To take advantage of this, some users will want anywhere connectivity on their Windows 8 PCs. This involves using mobile broadband to connect in areas where there are no Wi-Fi or wired networks available. The mobility investments listed previously, plus the mobile broadband investments that have been made in Windows 8, means that mobile network operators should consider how to best offer and take advantage of Windows 8 PCs for their customers. Windows 8 simplifies mobile broadband connectivity for users, while offering new opportunities for mobile network operators. Users enjoy a streamlined, consistent connection flow. Operators continue to enjoy branding and the ability to highlight their value-added services, all while reducing their need to develop traditional connection management apps. Development resources can instead be focused on customer interaction, including account management and value-added services. This document outlines the opportunities for mobile network operators and how they can best integrate their brand and offerings with Windows 8. Opportunities Windows 8 presents an opportunity to reimagine and streamline the existing mobile broadband ecosystem. Earlier versions of Windows mobile broadband hardware required custom drivers. With the Windows 8 Mobile Broadband class driver, mobile broadband devices that are certified for Windows 8 have a consistent experience without the need to install custom drivers. This streamlining presents an opportunity to provide customers with a just works experience while possibly reducing support overhead. Customized connection management experiences duplicate Windows functionality and have different UX models than the rest of Windows. These

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 5

connection managers have to be deployed and maintained by the operator and their ISV partners. The need for a custom driver and for custom connection management software meant that USB- based mobile broadband devices need to also perform a USB storage function in order to deliver that custom software to the users PC. This dual-mode device concept often requires the user to switch between storage mode and modem mode, adding an extra task before the user can successfully connect to the network. There is a desire from operators to highlight unique services and capabilities that make their customer experience unique. Windows 8 provides the opportunity for operators to focus on the customer connection and to highlight their unique value-add through the mobile operator app.

These are the opportunities that inspired the mobile broadband investments in Windows 8.

Supply-Chain Simplification
The introduction of a Windows 8 class driver for mobile broadband modems means that Windows is reducing the complexity that is required for mobile broadband hardware to interact with Windows. Varying mobile broadband hardware now talks to Windows in a consistent way. Windows 8 certified modems conform to a single API specification, allowing certified hardware to integrate into the Windows connection manager and take advantage of the mobile broadband experience in Windows 8. There is no longer a need to have onboard storage, to emulate a CD install in order to show AutoPlay, or to maintain and ship Win32 software with the device. Windows 8 certified mobile broadband devices work on Windows RT (ARM-based platforms) and on Windows 8 PCs (x86, x64 based platforms). Because the driver and the connection management software are built in, the operator doesnt have to load them into the device prior to sale. Hardware vendors no longer need to expend resources to update and maintain drivers. To help ensure that devices are useful on previous versions of Windows, Microsoft has provided guidelines for modem vendors that enable their modems to automatically present the appropriate interfaces and functionality, whether theyre connected to a Windows 8 PC or to a previous version of Windows. Windows 8 can associate apps with a multitude of devices that are available through the Windows ecosystem. Operators can create a mobile operator app and deploy it on the Windows Store. When the mobile broadband device is connected, Windows 8 then automatically installs the operators app. The app appears on the Start screen automatically. The mobile operator app is tied not to the modem device identification, but to the network operators identification. For example, for Global System for Mobile communication (GSM)based networks, the subscriber identity module (SIM) identifies the operator, and that information is used to download the mobile operator app. Code Division Multiple-Access (CDMA) networks use similar network identification on the modem for this purpose.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 6

We encourage operators to work with original equipment manufacturers (OEMs) to help ensure that their mobile operator app and service metadata are preloaded onto the appropriate OEM image. If PCs have unlocked mobile broadband hardware and an operator SIM is later inserted into the PC, or if a USB-based mobile broadband modem is plugged into a PC, Windows will still detect the operator identifier and download the corresponding mobile operator app (provided that an Internet connection is available). If an Internet connection is not available, Windows has a built-in connectivity directorythe access point name (APN) databasethat allows Windows to connect to the operators network even without the operators app or metadata installed. After initial connection using the APN database, the operator app is then automatically installed once connectivity is established. Windows provides the following tools to help operators deliver a seamless experience: Native connection management for mobile broadband and Wi-Fi networks A rich platform to enable operators to highlight their brand and promote their value-added services from within Windows An in-box mobile broadband class driver to remove complexity in managing custom drivers and worrying about compatibility Technology to allow simplified deployment and software distribution by using the Windows Store The ability to manage Wi-Fi hotspots and offload mobile broadband network traffic when appropriate

Integrated Account Experience

The mobile operator app has privileged access to the Windows 8 Mobile Broadband APIs and can be started from the Start screen or from the Windows connection manager. Figure 1 shows an example, using the fictitious company Contoso, of how the mobile operator app integrates with the Windows 8 UI.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 7

Figure 1. An example of a mobile operator app is integrated into Windows

In addition to being automatically placed on the users Start screen at install time, the app can be started from the View my account link in the Windows connection manager network list. (If the user uninstalls the operators app, this link will lead the user to the store to reinstall the app.) The app is also started when the user tries to connect to the operators network without an active subscription, enabling the app to provide tailored point-of-sale functionality. The operator defines XML metadata, which along with the mobile operator app, can configure Windows 8 for the operators network, including hotspots for data offload. The app can also inform Windows about the users data limit, enabling Windows and other apps to behave intelligently on this metered network. Having the mobile operator app provide plan and usage information back to Windows is optional and depends upon the network operators capabilities. The Windows Store policies require that apps adjust their behavior based on the network state (that is, metered versus non-metered). By default all mobile broadband networks are set to be metered networks.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 8

Connecting Operators with Users

After the mobile broadband hardware has been detected and the corresponding mobile operator app is installed, the user will find several paths that lead him or her to interact with the operators app. The live tile on the Start screen provides the user a path into the app, as well as providing the operator a path to display important information to the user (for example, overdue payment or remaining data allotment). For more immediate interaction, the operator can choose for the app to provide notifications to the user by using the Windows notification framework. When the user touches the notification, the app will start. The user will also be led into the app when he or she attempts to use the Windows connection manager to connect to the operators network with an inactive account. The Windows connection manager also has a link to View my account within the operators network entry in Windows connection manager. This link provides a convenient way for the user to interact with the operator via the mobile operator app. Once the app launches, the operator controls each pixel on the screen to best present its brand, products, and services. The app is local, so the experience is fast and fluid, and can offer an offline experience if needed. The operator has the ability to present its full suite of products, including premium services, and can dynamically target promotional offers to particular users. Other value-added capabilities, such as a map of Wi-Fi hot-spot locations, can be provided within this experience. Development of these features is simpler than ever before, via the development tools that are available for developing Windows Store apps.

Windows Connection Manager

Windows 8 now provides native connection management functionality, taking care of all the industry-standard network connection control and freeing the operator to focus more on differentiated functionality. Connect/disconnect, device status, flight mode, and other standard wireless management capabilities are available directly from PC Settings or through the Windows connection manager and provide an interface that is consistent with the Windows 8 design. Because this functionality is now a part of Windows, there is no longer any confusion created by multiple connection management experiences. Users intrinsically understand where to go for connection management regardless of the type of connection that they are using. The Windows 8 connection manager also automatically manages Wi-Fi hot-spot credentials that are entered by the user or, for mobile broadband subscribers, supplied by their mobile network operator. The connection manager can offload network traffic from mobile broadband to the users preferred Wi-Fi networks when they are in range. There are still opportunities for operators to customize the connection settings for their network. They can: Provide a list of APNs and their connection order preference Apply new profiles Set connections as metered or non-metered
September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 9

Provide a logo and network name for the Windows connection manager Specify network order preferences Provide hotspot authentication information to offload data to preferred Wi-Fi networks, if they are within range Provide various other customizations that are described in Providing Mobile Broadband Metadata.

Project Planning
The following resources are an example of the skill sets that an operator can use to complete development of a mobile operator app: Technical architect Plan how the mobile operator app will interact with the operator back-end systems. Combine operator infrastructure with the Windows developer platform capabilities. Understand various types of metadata that must be created and submitted to enable the end-to-end mobile broadband experience. Design a metadata matching scheme that allows for MNO and MVNO experiences in Windows. Ensure a system is in place to provide updated service metadata submissions that describe the SIMs (or CDMA devices) that belong to the MNO/MVNOs. Business development contact Define the requirements for the mobile operator app and the key customer scenarios that the app will address. Create a spec document that the team can refer to while its coding and testing the app. Project manager Manage the project plan. Marketing contact Ensure agreement on the name of the mobile operator app, on how corporate branding and assets should be used, and on descriptions for the mobile operator app that appear in the Windows Store. UX designer Combine operator branding requirements with the new Windows user experience guidelines. Provide detailed designs for every page and UI in the mobile operator app. Provide cascading style sheets (CSS) and HTML layout assistance to the development team as needed. Software developer Provide UI expertise to lay out the Windows Store device app by using the new Windows user experience guidelines. Code the app. Software developer for device integration Understand the mobile broadband platform in Windows 8 and how metadata plugs into that. Generate required metadata packages and communicate with the Mobile Broadband APIs in Windows. Software tester Validate that the app and metadata are working correctly together. File bugs and ensure app quality.
September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 10

IT architect Provide business services and ensure operator backend systems are in place to take advantage of Windows 8 extensibility for operators. Design and deliver internet facing web services that the mobile operator app can access. Ensure content and dynamic updates are provided to the mobile operator app. Ensure integration with billing systems and account management and plan purchase infrastructure. Network architect Ensure integration between the mobile operator app and metadata and the operators mobile broadband network infrastructure. Ongoing deployment and maintenance An individual or team of people that is responsible for maintaining the APN database entries for the MNO/MVNO. They also need to keep track of new SIM ranges that are assigned to MNO/MVNO subscribers and describe these to Windows by submitting updated service metadata packages to the Windows Dev Center Hardware site. Manage the Windows Store listing for the operator and be able to submit app updates to the Store. Depending on other Windows Store apps that the operator chooses to develop for Windows 8 (for example, apps that highlight the operators premium service offerings such as a navigation app, a music app, or a video streaming app), there will be additional resources required for implementation.

Summary
New connectivity scenarios in Windows 8 will lead users to want always-on connectivity for their Windows-based PCs, driving demand for operator services. The mobile operator app provides an unprecedented capability for operators to connect with customers on any Windows 8 PC while simultaneously reducing the complexity of doing so. Windows 8 provides features that help operators provide rich, tailored experiences for their subscribers. Windows 8 also enables operators to highlight the value-added services that make them valuable and unique in the eyes of their customers. Windows 8 delivers the following for mobile operators: Drives new subscribers to mobile broadband by investing in mobility-oriented features and scenarios and providing an always-present APN database to make connectivity easy for potential subscribers. Simplifies the operators PC supply chain overhead by providing more inbox functionality including the Windows 8 mobile broadband class driver and improved Windows connection manager. Provides a unique ability to highlight operator value-added services through the mobile operator app and other operator value-added apps that are distributed through the Windows Store. Provides the potential for a variety of mobile broadband hardware and PC form factors that operators can source for sale to their subscribers.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 11

Choice of Engagement for Operators

Operators can choose what level of participation they want to have with the Windows 8 mobile broadband functionality. The following sections describe, from least to most integrated, the scenarios operators can expose by enabling their experience on Windows 8.

Level 0 - No Engagement
Customers who try to connect to your network using Windows 8 may need to enter custom APN strings to properly configure their profile and connect to your network. This is a less than ideal experience and the operator is not taking advantage of the mobile broadband extensibility opportunities that Windows 8 provides. Basic connectivity to mobile broadband can be achieved but may require additional help or documentation from the operator to their subscribers. Inline purchase experiences are not enabled.

Level 1 - Provide APN database entries

Operators submit APN connection information into the Windows APN database, an in-box database that is maintained through Windows Update. By providing your connection and purchase APN information for inclusion in the Windows APN database, customers will see a seamless connectivity experience without the need to install additional software. For more information, see the introduction to the APN database in Windows APN Database. Basic connectivity can be achieved, especially if the operator ships only modems or SIMs that already have an activated plan. However without an updated operator web site that works in a walled garden (described in Level 2), the operator may be missing opportunities to have customers activate and purchase data plans outside of a retail store environment.

Level 2 - Create an operator plan purchase/top-up website

The APN information the operator supplies can include a reference to an account experience website that is used to buy plans or top-up on data. If the operator enables the website to load in walled garden (or limited connectivity) scenarios, users can purchase plans without the need for any additional apps or software. The website can also make use of the Provisioning metadata to apply settings and configuration information to Windows after the subscriber has successfully purchased their plan. See the Operator Website section of this document for more details. Provisioning Metadata is described in the Provisioning Metadata section of this document. Level 1 + Level 2 allows the operator to enable basic connectivity scenarios and the operator to provide an account activation experience without the need for additional software or apps on the PC. This is useful for operators who sell Windows 8 certified USB-based mobile broadband devices with warm or non-activated SIMs. If the operator provides only activated SIMs to customers, then Level 2 is not needed.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 12

Level 3 Create service metadata and a mobile operator app

For operators who want to create a richer integrated experience in Windows 8 that takes advantage of a greater range of extensibility opportunities, they should create a service metadata package and mobile operator app. The mobile operator app is a Windows Store app that has access to privileged APIs, allowing the app to interact with mobile broadband APIs and SMS APIs. The service metadata package allows the operator to brand the Windows connection manager with a custom logo and to describe the name of the operator network that appears in the Windows connection manager. Building a mobile operator app enables the operator to create a richer set of functionality described in the next sections. More information about the mobile operator app can be found in Account Management Experience found later in this document. More information about service metadata is described in Service Metadata found later in this document. Level 1 + Level 2 (optional) + Level 3 provides a deeply integrated experience, allowing the operator to deliver a branded experience on Windows 8 that leverages the mobile broadband enhancements that are new for this release. This level is also required to enable SMS or operator notifications on the PC. This is the minimum recommended level of engagement that operators should target.

Level 4 Wi-Fi Hotspot offloading and providing plan and data usage information to Windows
Once the operator app and service metadata have been deployed, the operator can take advantage of provisioning metadata to implement more advanced scenarios, such as automatic Wi-Fi Hotspot offloading to reduce mobile broadband network traffic. Provisioning metadata can also be used to make Windows aware of the users plan and data limit. The Windows Store has a policy in place that directs third-party apps to respect and react to the customers data usage and plan information. Provisioning Metadata is described in Provisioning Metadata in this document. A variety of scenarios is available and can be implemented depending on the mobile operators capabilities. Level 1 + Level 2 (optional) + Level 3 + Level 4 allows operators to deliver a solution that meets their networks capabilities and interacts with Windows in a deeply integrated way.

Level 5 Premium services and complimentary apps

The operator can choose to create a variety of value-added services that are exposed to the subscriber in the form of apps that are available for download from the Windows Store. Using service metadata, the operator can describe a limited set of apps as being privileged, which also allows these apps to interact with the Mobile Broadband APIs or SMS APIs. The operator can use their mobile operator app to reference and highlight other apps that can be downloaded from the Windows Store that would be of interest to their subscribers. This allows operators to highlight their value-added services and make their unique offerings available to subscribers who are using Windows 8.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 13

Level 1 + Level 2 (optional) + Level 3 + Level 4 (optional) + Level 5 allows the operator to highlight their value-added services using the Windows 8 development platform and Windows Store distribution capabilities.

Key Scenarios
This section describes examples of the key scenarios that are part of the Windows 8 mobile broadband experience that the operator can choose to enable. Consider each of these scenarios in the context of your business models, and youll be able to plan which Windows components your app must interact with. You can also reference the Technical Overview section later in this paper for more details about each component that is involved in the flow. For more details about the user experience that is associated with each step, see the paper Designing User Experience of Mobile Operator Apps.

Plan Purchase
One of the activities that operators may want to enable in their mobile operator app is plan purchase or plan top-up. The operator provides their own unique plan purchase experience as part of the mobile operator app. A seamless plan purchase experience makes it easier for users to buy connectivity and enables the operator to accept new customers without the need for support or retail-store intervention. Two experiences for plan purchase are as follows: Plan purchase, where the mobile operator app and service metadata is already installed on the PC. This could happen for PCs that have embedded mobile broadband hardware where the OEM has preloaded the operator experience onto the Windows 8 image. Plan purchase for external devices (such as USB modems), where an alternate Internet connection is not available and the mobile operator app and service metadata is not installed.

Regardless of the plan purchase experience, there are various sub states of plan purchase based on the state of the SIM (or CDMA mobile broadband device). SIMs that are cold (having no plan), warm (being ready to accept a plan), or hot (already active with a plan) will likely present a different experience based on how the operator wants to structure their purchase flow.

Purchase when mobile operator app is already installed or an alternate Internet connection is available
An embedded device is likely to be in the PC with a SIM before the user attempts to activate service. Likely the mobile operator app and service metadata are already installed on the PC. Another possibility is that the user does not yet have the mobile operator app but has an alternate Internet connection that allows the app to be downloaded.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 14

The scenario includes two distinct stages. The following steps occur automatically to prepare the PC to connect to mobile broadband.

Mobile Broadband Service

Windows Metadata and Internet Services Service Metadata

Windows Store Mobile operator app

Figure 2. Steps that occur to prepare the PC to connect to mobile broadband

1. As soon as the SIM is inserted, the Mobile Broadband service reads the International Mobile Subscriber Identity (IMSI), the Integrated Circuit Card ID (ICCID, for GSM networks), the provider ID (also known as a SID, for Code-Division Multiple Access [CDMA] networks), or the provider name (for CDMA networks) and generates a set of hardware ID values (HWIDs). Note: If the OEM has already inserted the SIM and preloaded the mobile operator app and service metadata, this step will have already taken place. 2. When the PC is next connected to the Internet, these HWID values are sent to Windows Metadata and Internet Services (WMIS). WMIS identifies the operator and returns the appropriate service metadata package. Note: If the OEM has already inserted the SIM and preloaded the mobile operator app and service metadata, this step will have already taken place. 3. Windows uses the service metadata to identify and retrieve the operators app from the Windows Store. The app is installed automatically. Note: If the OEM has already inserted the SIM and preloaded the mobile operator app and service metadata, this step will have already taken place. 4. The PC is now ready for its first connection. The operators logo and name appear in Windows connection manager as a connection option. This is shown in Error! Reference source not found., which shows a Contoso branded network entry in the Windows connection manager. Contoso is a fictitious company that is frequently used in Microsoft documentation as an illustrative example.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 15

Figure 3. Operator branding in Windows connection manager

When the user clicks Connect, the following occurs:

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 16

Windows Connection Manager

Operator App Purchase Flow

Provisioning Agent
Provisioning Metadata

Figure 4. Steps that occur when Windows connection manager connects to the provisioning agent

5. Windows connection manager tries to connect by using the network profile configuration information in the service metadata. The next step depends on the result of the connection: If the initial connection is successful and Internet connectivity is available, nothing further happens. The user has previously purchased service and has an active account. If the initial connection is successful but Internet connectivity is not available, the mobile operator app is started to provide a purchase or top-up experience. If the initial connection fails and the error code indicates that network service has not yet been purchased, the mobile operator app is started. The app can determine the appropriate response. For example, due to lack of connectivity, the app may need to direct the user to complete the purchase by telephone or by connecting to an alternate Internet connection. If the initial connection fails with another error code, Windows connection manager notifies the user about the error. The mobile operator app is not started.

5. When the app opens the operator should write code to make a secure connection to the backend billing infrastructure so that the user can purchase a subscription. This process is proprietary for each operator and Microsoft is not involved in the purchase process this is code the mobile operator includes in their app in order to complete this scenario. The app establishes this connection through a limited mobile broadband connection (that the operator network needs to enable) or over an alternate Internet connection such as Wi-Fi. Figure shows an example of what the mobile operator app could present to users who are trying to purchase connectivity. Designing User Experience of Mobile Operator Apps provides best practices for building a user experience that aligns with the Windows Store design guidelines.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 17

Figure 5. Mobile operator app plan purchase example

6. When plan purchase is complete, the app generates a metadata provisioning file and passes it to the provisioning agent. This configures Windows with information about the plan that the user has purchased. This flow applies unchanged to an external device that is attached while the PC is connected to another Internet connection (such as Wi-Fi), and where enough time passes to permit the download and installation of the mobile operator app and service metadata.

Purchase when no mobile operator app is installed and no alternate Internet connectivity is available
An external mobile broadband device (such as a USB modem) can be inserted into PCs that may not have an alternate Internet connection available and may not have the mobile operator app installed. This scenario also applies if a PC has an unlocked embedded mobile broadband device where the user has inserted a SIM, with no alternate Internet connectivity. This section describes how a plan purchase experience can be built to work around the limitations in this scenario.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 18

Windows 8 features an in-box mobile broadband connectivity directory, the APN database, which allows Windows to connect to mobile broadband networks without the need for custom software. The APN database enables the partner to specify a URL that can be used to start a plan purchase experience in a web browser.

Mobile Broadband Service

Windows Connection Manager Windows APN Database

Operator Website

Provisioning Agent
Provisioning Metadata

Figure 6. Steps from mobile broadband service to provisioning agent

1. As soon as the mobile broadband hardware is detected, the Mobile Broadband service reads the IMSI, the ICCID (for GSM networks), the provider ID (or SID, for CDMA networks), or the provider name (for CDMA networks) and generates a set of encoded identifiers that represent the IMSI, ICCID, SID, or provider name read from the device. These encoded identifiers are referred to as Hardware IDs (HWIDs). The mobile broadband service in Windows listens for mobile broadband-related events that various parts of the Windows code base reacts to. 2. When the user clicks Connect, these HWID values are used to locate appropriate connection settings within the Windows APN database, as follows: If the initial connection is successful and Internet connectivity is available, nothing further happens. The user has previously purchased service and has an active account. If the initial connection is successful but Internet connectivity is not available, the default web browser is opened taking the user to the URL that is specified in the APN database for this HWID range. If the initial connection fails, Windows connection manager notifies the user about the error. The operators website assists the user in purchasing a plan.

3. After the user completes the plan purchase, the website generates a metadata provisioning file and passes it to the provisioning agent. This configures Windows with basic information about the plan that the user has purchased. Depending on the network structure, one of the following occurs: The user is granted Internet access on the current connection. The provisioning file includes instructions to disconnect and reconnect to the same network or a different network, which will provide Internet access.

At this point, the user is online. Now that an Internet connection is available, Windows detects the mobile broadband hardware and, in the background, downloads and installs the service metadata and the mobile operator app.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 19

Windows Metadata Service

Windows Store

Operator App - Background Events

Provisioning Agent Provisioning Metadata

Service Metadata Mobile operator app

Figure 7. Steps from Windows metadata service to provisioning agent

4. The HWID values that are calculated from the SIM or mobile broadband hardware are sent to WMIS. WMIS identifies the operator and returns the appropriate service metadata package. 5. Windows uses the service metadata to identify and retrieve the operators app from the Windows Store. The app is installed automatically and registered for background events. Registering for background events allows the app to react to local data usage counters, receive operator SMS messages, connect to Wi-Fi hotspots, and so on. More details about background tasks can be found in Introduction to Background Tasks. 6. When a background event occurs, the app generates a more complete provisioning file if needed and passes it to the provisioning agent. This configures Windows with information about the plan that the user has purchased.

Figure 8. Windows 8 Start screen showing an example Contoso app live tile after the Contoso mobile operator app has been installed.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 20

Connecting an Active Device

When a device with an active mobile broadband plan is attached to the Windowsbased PC, the flow is similar to that for purchase, except that the attempted connection leads to the Internet. Windows will not start the Windows Store device app for mobile broadband or the operator website. Instead, the app is installed in the background. Mobile Broadband Service Windows Connection Manager Windows APN Database
Figure 9. Steps from mobile broadband service to Windows connection manager

1. When the mobile broadband hardware is detected, the mobile broadband service reads the IMSI, the ICCID (for GSM networks), the provider ID (or SID, for CDMA networks), or the provider name (for CDMA networks) and generates HWIDs. 2. When the user clicks Connect, these HWID values are used to locate appropriate connection settings within the Windows APN database. For an active device, the connection is successful and Internet connectivity is available. At this point, the user is online. Now that an Internet connection is available, Windows will detect the mobile broadband hardware and in the background download and install the service metadata and the mobile operator app.

WMIS

Windows Store

Operator App - Background Events

Provisioning Agent Provisioning Metadata

Service Metadata Mobile operator app

Figure 10. Steps from WMIS to Windows connection manager

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 21

Operator Notifications and System Events

In order to keep the user informed about their account status, the mobile operator app needs to perform some activities even when the user is not interacting with it. These activities include responding to operator SMS or network-initiated USSD messages, notifying the user that they are approaching their data limit, notifying the user that their data plan has expired, and notifying the user of their roaming status. Incoming Short Message Service (SMS) messages are available to privileged apps that have been granted access to the SMS capabilities on the PC by the operators service metadata package. Some SMS messages come directly from the mobile network operator and should be displayed to the user via the mobile operator app. The mobile operator app can invoke a toast notification when it receives an operator SMS message. Figure shows what this could look like. Some operator messages are not intended for end-user consumption, and the mobile operator app can process these and act appropriately. The Windows Notification Service provides the most efficient direct-to-app notification channel, but Windows also supports the use of incoming SMS and Unstructured Supplementary Service Data (USSD) notifications from the mobile broadband network. More information about handling SMS messages can be found in Mobile Broadband SMS. More information about operator notifications can be found in Mobile Operator Notifications and System Events.

WMIS
Service Metadata

Provisioning Agent
Provisioning Metadata

Figure 11. Steps from mobile broadband service to Windows connection manager

1. The service metadata declares that the mobile operator app wants to access operator notifications. A private background event is created, and the app is registered for operator notification events at the time that it is installed. 2. Later, when the app applies provisioning metadata, it includes a description of all SMS and USSD messages that should be considered operator messages.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 22

Mobile Broadband Service

System Event Broker

Windows Store Device App Background Events

Figure 12. Steps from mobile broadband service to Windows Store device appbackground events

Upon receipt of an SMS or USSD message, the mobile broadband service compares to the description provided in the provisioning metadata. If parsing rules have been included, the Mobile Broadband service also interprets the message and updates the information about data usage. If the message is a match, the System Event Broker is notified to invoke the private background event for that operators app. If not, System Event Broker is notified to invoke the public SMS event. The app handles the incoming message as appropriate. Some examples of what the operator could code into the mobile operator app for responses to incoming SMS messages include the following: Immediately syncing current data usage Displaying a notification to the user, as shown in Figure

Figure 13. Example of a notification toast that the mobile operator app would display based on an operator SMS notification

Updating the apps live tile Retrieving and applying updated provisioning metadata

Note: Windows does not provide an inbox SMS app so the mobile operator app or a third-party SMS app to which the operator gives privileged access is needed in order to display SMS messages to the user. Note: Building a mobile operator app with SMS support is necessary to show notification UI to the end user when text messages are received, which may be required to conform to regulatory requirements or best practices in certain markets. SMS functionality is only available to mobile operator apps and Windows Store apps given privileged access by mobile network operators. Mobile network operators specify privileged apps through service metadata. For more information about service metadata, see Providing Mobile Broadband Metadata.
September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 23

Providing Accurate Usage and Plan Data to Windows

Windows provides Data Usage and Subscription Manager APIs that the mobile operator app can provide information to that describes the users data plan. The mobile operator app can update this API with information about the data plan size, metered vs. non-metered plan, and an updated data usage value from the operator backend. Windows will check the data usage information that has been set for the user via these APIs and change the behavior of core features. For example, Windows Update will only auto-download critical updates when the user is using a metered network. Usage information is also accessible to third-party apps via the Data Usage and Subscription Manager APIs; detailed usage guidelines are available at Managing connections on metered networks. The following is a walkthrough of the various features that the mobile operator app can choose to utilize in order to keep the user informed of their data usage.

Local Data Counters

Data Usage & Subscription Manager

System Event Broker

Windows Store Device App Background Event

Figure 14. Steps from local data counters to Windows Store device app background events

1. Local data counters estimate that usage on the profile has changed by more than 5 percent of the users data limit since the last update from the operator. This 5 percent increment is hard-coded and the mobile operator app can make use of background events to wake itself up and react to each 5 percent increment. 2. Data Usage and Subscription Manager is a Windows component that does this 5 percent usage increment tracking. It notifies the System Event Broker to trigger a background event for each 5 percent increment in the local estimated usage. 3. The System Event Broker invokes the mobile operator app to handle the background event. (Other triggers, such as an incoming notification, might cause this to occur.) The mobile operator app can choose what to do when it is invoked for this purpose. 4. A best practice is for the app to handle this event by retrieving the most current usage information from the operator backend to validate how much usage the user has actually gone through. This is likely an asynchronous operation over the network and the mobile operator app needs to be able to react to delays in getting this information from the backend.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 24

Operator App - Background Event

Provisioning Agent Provisioning Metadata

Data Usage & Subscription Manager

Third-Party Apps

Figure 15. Steps from local data counters to Windows Store device app background events

5. When the web query to the operators billing infrastructure completes, the app can apply updated provisioning metadata that describes the most up-to-date usage information available back to Windows. 6. The app publishes the updated information through the Data Usage and Subscription Manager APIs. 7. Windows components and third-party apps on the PC can access this usage information via the Windows.Networking.Connectivity.ConnectionProfile class. Apps can adjust their behavior accordingly (for example using a lower quality video stream on metered networks).

Authenticating to a Wireless Hotspot

As part of the provisioning metadata, the mobile operator app can describe the hotspots to which the user can authenticate using their operator-supplied credentials. These may include WISPr 1.0 hotspots or encrypted hotspots using EAPSIM, EAP-AKA, or other supported EAP methods. Windows will then automatically offload data traffic onto these hotspots when in range. Operators may want to do this in order to offload network traffic from their cellular data networks and onto land-line based Wi-Fi locations. In some cases the Wi-Fi hotspot may have increased speeds or better coverage than the cellular data network for that location. Operators may also choose to make a hotspot less preferred than the mobile network, making it available for Windows to use when mobile broadband is not available but not used for data offload.

Setup

Windows Store Device App

Provisioning Agent
Provisioning Metadata

Windows Connection Manager

Figure 16. Steps from Windows Store device app to Windows connection manager
September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 25

1. The mobile operator app generates a provisioning file that contains the service set identifiers (SSIDs) and authentication mechanism for hotspots to which the user may authenticate. By doing this, it avoids the user having to manually enter this information. 2. The provisioning agent parses the provisioning file and provides the necessary information to the Windows connection manager. Windows automatically connects to these networks when they are available.

Credential Generation
If the mobile operator app generates or retrieves WISPr credentials in a proprietary manner during the connection, the provisioning metadata includes a reference to the app, rather than providing specific credentials. If specific credentials are included, this phase is skipped.

Wi-Fi Hotspot

Windows Connection Manager

System Event Broker

Mobile operator app Background Event

Figure 17. Steps from Wi-Fi hotspot to mobile operator app - background event

1. The captive portal website in the Wi-Fi hotspot includes a challenge from the Wireless Internet Service Provider roaming (WISPr) protocol. 2. If static credentials were not provided, Windows connection manager notifies System Event Broker that hotspot authentication is occurring. Otherwise, Connection Manager proceeds directly to authentication. 3. For proprietary authentication schemes, the System Event Broker invokes the mobile operator app to generate credentials. 4. The app generates credentials via its proprietary mechanisms. These may or may not involve interaction with network resources, or with the mobile broadband interface. The app ultimately takes one of the following actions: Provide Credentials. The app can generate credentials for this network, and then return them to the Windows connection manager. The Windows connection manager authenticates to the hotspot using WISPr. Cancel Connection. The PC should not be connected to this network. The Windows connection manager will terminate the connection. Cancel Authentication. The app has been authenticated via an alternate method. The Windows connection manager will neither authenticate nor disconnect. Interact with User. The app will be brought to the foreground. This is selected when user confirmation is needed, such as a pay-per-connection

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 26

hotspot. The app should ultimately take one of the previously listed actions after consulting the user.

Authentication
When credentials are supplied by the operator app (dynamic WISPr credentials) or statically defined as part of provisioning (static WISPr credentials, EAP credentials), Windows handles delivering these credentials to the Wi-Fi hotspot. The configuration information provided by the operator app to the Windows connection managers connection profile determines how credentials are obtained and delivered. The delivery is outlined in the next steps:

Windows Connection Manager

Wi-Fi Hotspot

Figure 18. Steps from Windows connection manager to Wi-Fi hotspot

1. When the user is in range of the Wi-Fi hotspot then the Windows connection manager replies with credentials that are statically defined via provisioning metadata. This data can be generated by the mobile operator app or can come through a trusted website. 2. The hotspot verifies the credentials with the operator, and then permits the PC to access the Internet.

Displaying Account Information to the User

The best way for an operator to interact with their subscribers in Windows 8 is via the mobile operator app. This app is coded by the operator to meet their key scenarios around subscriber interaction. The operator app is a Windows Store app that is developed using the Windows 8 development tools and processes. Additionally it is a privileged app having access to the mobile broadband and SMS APIs.

WMIS
Service Metadata

Windows Connection Manager

Mobile operator app

Local Data Counters

Figure 19. Steps from WMIS to local data counters

1. Windows determines which MNO or MVNO the subscriber belongs to when mobile broadband hardware is detected on the PC. The operators service metadata is matched and downloaded using WMIS.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 27

2. The service metadata links the mobile operator app to the corresponding network entry in the Windows connection manager. 3. The Windows connection manager shows the operators logo and a View my account link. 4. When the user clicks the link, the operators app is launched. The app can be coded to retrieve the most up-to-date information available from the operators billing system. 5. Optionally, the app may query the local data counters for an estimate of usage since the billing system was last updated. The app can use this data to display a near-real-time approximation of the users usage. 6. Many more scenarios can be coded into the mobile operator app by the MNO or MVNO. The document Designing User Experience of Mobile Operator Apps gives detailed examples and UX guidelines of key scenarios the mobile operator app can enable.

Figure 20. An example of the landing page for a mobile operator app for the fictional company Contoso

Enabling other devices and app scenarios

Windows 8 provides a rich set of development tools and a flexible development platform that operators can choose to take advantage of by creating apps that highlight the value added services that make them unique.

Privileged apps
Mobile Broadband APIs and interfaces (including Account Provisioning and SMS) are restricted and only available to mobile operator apps. A list of privileged apps that have access to these privileged APIs can be specified in the service metadata package.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 28

Operators should consider which apps they wish to gain these privileges and must be declared in the operator service metadata package that is submitted to the Windows Dev Center - Hardware Dashboard.

Wireline Operators
For operators that wish to expose other devices (non-mobile broadband related) and have those appear in Windows 8 via a Windows Store device app, they can make use of PnP-X as described in this document about Specialized Devices. Devices such as DVRs, gateway routers, mobile hotspots, and phones can (while connected to the same Wi-Fi or LAN network as the Windows 8 PC) use PnP-X to make Windows 8 aware of their presence. Device metadata is then downloaded for those devices based on their device properties and a Windows Store device app that the operator has coded is automatically downloaded as well. If the operator chooses, they can reference the mobile operator app as the Windows Store device app for these devices so that a single mobile operator app can manage mobile broadband as well as these additional devices.

Technical Overview
This section provides a high-level overview of the components that are involved in presenting the preceding scenarios. They are divided between those that are part of the Windows operating system and those that are part of the service metadata or mobile operator app, which the operator authors.
PC

Operator Purchase Website

Provisioning Agent Third party apps Provisioning Metadata

Mobile operator app

Purchase Experience Background Event Handling

Wi-Fi Hotspot
Windows Store

Account Management Experience

Data Usage & Subscription Manager

Windows Connection Manager Mobile operator app

System Event Broker

Windows Metadata and Internet Services (WMIS)

Mobile Broadband Service

Local Data Counters

Service Metadata

APN Database

Mobile Broadband Class Driver

Figure 21. Technical components for providing an operator experience in Windows 8

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 29

Windows Components
Provisioning Agent
The provisioning agent provides an interface for a mobile operator to configure Windows with the network settings that are appropriate to its network. The provisioning agent accepts an XML file that describes the desired configuration. This XML file can be supplied in either of the following ways: As a signed XML file that a website provides to the window.external.msConfigureNetworks() function for Windows Internet Explorer 10+ (or another supporting browser) on a client running Windows 8 As a signed or unsigned XML file that an app provides to the Windows.Networking.NetworkOperators.ProvisioningAgent.ProvisionFromXml Async() function

For more details about the format and content of the provisioning file, see Providing Mobile Broadband Metadata.

Data Usage & Subscription Manager

The Data Usage & Subscription Manager tracks details about the users accounts. The stored cost information about the currently connected network is available to all Windows Store apps. The mobile network operator updates this information by using the provisioning XML. If the carrier requests it, Data Usage & Subscription Manager uses the local data counters to trigger a background event when 5 percent of the data limit has been used. System Event Broker delivers this background event, and the mobile operator app can use the event as a trigger to update billable usage.

Windows Connection Manager

The Windows connection manager monitors available networks across Wi-Fi, mobile broadband, and Ethernet. It makes automatic connect and disconnect decisions based on the available networks. The provisioning XML enables an operator to define the relative priority between networks that the operator owns. However, the user can manually connect to any network that he or she chooses. The Windows connection manager will use the users manual actions to influence future automatic connection choices. The Windows connection manager also manages post-connect authentication with Wi-Fi hotspots that support WISPr 1.0. If static credentials have been stored for the Wi-Fi hotspot, the Windows connection manager will authenticate automatically. If dynamic credentials are required, the Windows connection manager will trigger a background event via System Event Broker. The mobile operator app should then generate appropriate credentials and deliver them to the Windows connection manager in order to complete the authentication process. For more details, see Windows 8 Integration for Wireless Hotspot Operators.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 30

Local Data Counters

The local data counters track the amount of data that is sent and received on a network interface over time. This information appears in multiple locations: The App History tab of Task Manager The Windows.Networking.Connectivity.ConnectionProfile.GetLocalUsage() function (Optionally) In the Windows connection manager, in the expanded view of the Wi-Fi or mobile broadband network. Users have control over whether to show or hide this estimated for a particular network. By default it is shown for mobile broadband networks and is hidden for Wi-Fi networks. However, if Windows detects that a mobile operator app is installed, it will hide estimated data usage in the Windows connection manager for the corresponding mobile broadband network. This is because there is an assumption that if the operator has created a mobile operator app, they will want to control the data usage value that gets displayed to the user. The best place to do that is inside the mobile operator app. Users can choose to override this behavior and show estimated usage for the network at any time.

Local data usage information serves as an estimate and a guide for the user. Windows cannot account for unbilled traffic or for usage on other devices that share the same data limits (for example, family plans and using the same SIM on different devices). Operator apps should use local data counters only to approximate usage since the last sync with the operators own billing system. For data usage that has already been processed, the billing system should be considered authoritative.

Mobile Broadband Service

The mobile broadband service manages communication between the Mobile Broadband APIs and a mobile broadband device. The service can interact with any mobile broadband device whose driver conforms to the Windows mobile broadband driver model. The service also reads the SIM of a newly inserted device and initiates the process that retrieves the service metadata and the mobile operator app that correspond to the attached mobile broadband device.

Mobile Broadband Class Driver

The mobile broadband class driver reduces the burden on device manufacturers to deliver a custom driver for their specific mobile broadband device. Any mobile broadband interface that manifests as a USB device and complies with the USB Implementers Forum (USB-IF) Network Control Model (NCM) 2.0 specification will be managed via the mobile broadband class driver and does not require additional drivers to be downloaded or installed. The mobile broadband class driver conforms to the Windows mobile broadband driver model and provides full functionality to the mobile broadband service. It also supports custom extensions, which will be exposed directly to the mobile operator app. For more information, see Mobile Operator Hardware Guidelines for Windows 8.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 31

System Event Broker

The System Event Broker manages background events. Apps, including the mobile operator app, can register to receive background events in order to respond to changes in system state. Events that could be of interest to the mobile operator app include: Network status change network connected/disconnected, Internet connectivity changed on a network Account status change end of billing cycle, or 5 percent estimated data usage increments. These 5 percent increments invoke an event that the app can react to. Wi-Fi hot-spot authentication attempting to connect to a public hotspot, and credentials are needed Incoming operator notification SMS/USSD message that matches certain parsing rules that describe the SMS/USSD as coming from the operator Incoming SMS message received that does not match operator defined parsing rules Incoming USSD message received that does not match operator-defined parsing rules

Developers should be aware that a strict limit is placed on the amount of CPU time that an app may consume while it is not active. Although these limits are relaxed for some events, apps must always minimize the resources that they consume while the system is in a low-power state or while another app is running. For more information about background events in Windows 8, see Introduction to Background Tasks.

Windows Metadata and Internet Services (WMIS)

WMIS is a cloud-based Windows service that delivers customizations to Windows from third parties that participate in the Windows device ecosystem. For a mobile broadband device, WMIS delivers the service metadata package. This provides the basic information that Windows needs in order to retrieve the mobile operator app from the Windows Store, allow connectivity to the network for the first time, and display appropriate branding elements in the Windows connection manager.

Windows Store
The Windows Store is the primary way that Windows Store apps are delivered to Windows 8 PCs. For a mobile operator app, the app package is retrieved from the Windows Store whenever Internet connectivity is available after the device is connected. The app package is automatically installed and available to the user at that point. For more information about Windows Store device apps, see Windows 8 Device Experience: Windows Store Device Apps and Windows Store Device App Lifecycle. Note: Enterprises can side load Windows Store apps under certain conditions, these will not be covered in this document.

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 32

Operator Metadata
Metadata about operators is provided in three different ways for Windows 8 as described below. Each of the metadata options targets a different set of customers. Understanding how the three types of metadata are delivered and what information is used in each will help you better address your customers. For more information about the operator metadata, see Providing Mobile Broadband Metadata.

Windows APN Database

The Windows APN database is present on all Windows 8 PCs. The database is periodically updated via Windows Update to help ensure accuracy of the connectivity information that it contains. These updates are invoked via servicing requests from mobile operators themselves. This database provides key information to Windows about how to connect to the network if it encounters a mobile broadband device. This includes the APNs to which it should attempt a connection, as well as the URL to which the user should be directed if no Internet connectivity is available. This information is intended to get customers online within seconds of connecting a mobile broadband device. It should enable them to purchase service immediately via a web browser or get online immediately if they have already purchased service. Windows gets APN information from operators and it is kept up to date with a servicing process based on Windows Update.

Service Metadata
Service metadata is delivered to any user after he or she connects a mobile broadband device. Service metadata is always automatically downloaded (and eventually the mobile operator app is automatically downloaded) as long as the user has any form of Internet connectivity (including being connected to metered mobile broadband and even roaming networks). This information enables customers to have a richer experiencebranding elements for the Windows connection manager, a reference to the mobile operator app that is automatically acquired from the Windows Store, and the most current mobile broadband settings for getting online for purchase or Internet connectivity. Windows will periodically check that it has the latest service metadata package from WMIS. The service metadata package is delivered to customers only when mobile broadband hardware from that operator is detected on the PC. Information in this package overrides the content of the APN database whenever its present. For more information about the service metadata package schema, see Service Metadata Package Schema Reference for Windows 8.

Provisioning Metadata
Provisioning metadata is delivered to the PC by either the operators website or the mobile operator app after the subscriber has purchased service. Provisioning metadata is packaged as an XML file, is signed in certain cases, and is processed by Windows to modify the network settings of the PC.
September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 33

Provisioning metadata can be specified for each subscribers individual requirements if the operator chooses to do so. The provisioning metadata may also be updated with much higher frequency, generally via the mobile operator app. Information in provisioning metadata overrides the contents of the APN database and the service metadata. This is because it tends to be the most specific and tailored information about the subscriber.

Operator Experiences
Mobile Operator App
A customers primary experience with the operators offerings and brand will be through the mobile operator app. This app is not expected to provide primary connection management functions, but to provide an account management experience and highlight the value-added services that the operator provides. What follows are fundamentals that the operator can choose to include in their mobile operator app. The operator controls the design of its mobile operator app and can deliver additional functionality to differentiate its services and increase customer loyalty. For more information about how to design a great user experience for the mobile operator app, see Designing User Experience of Mobile Operator Apps.
Purchase Flow

If the app is already installed when the user attempts to purchase service, the app is started when the user clicks Connect. At this point, the PC will generally be connected to your mobile broadband network, but may be on a limited network connection. Your app should use resources available over this connection to help the user sign up for service, pay, and get online. At the end of this flow, your app can generate or retrieve the provisioning metadata package that is appropriate for the user.
Background Events

To deliver the best possible experience, your app may need to perform some activities when the user is not interacting with it. For example, your app may choose to periodically reconcile the users usage with your billing system, giving the user (and Windows) an accurate indication of the usage state.
Account Management Experience

A users most fundamental expectation of your app is likely to be the ability to check their usage and perhaps manage his or her account. The user may want to be able to quickly see his or her usage information, balance, and other information. You can make use of your apps live tile on the Start screen to display relevant information to the user.

Operator Website
For many users, your purchase website will be their first experience of your brand on Windows 8. Your website should be touch-friendly and render well in plugin-free web browsers. To deliver a seamless Windows 8 experience, the website can deliver a provisioning metadata file to the user at the end of the purchase experience. By using

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 34

the content of this file, Windows can connect to the Internet and get the user online immediately after purchase. For more information, see Creating a Website for Mobile Broadband Setup.

Wi-Fi Hotspot
Due to the increased demand on operator data networks, Wi-Fi hotspots have become a valuable asset to manage data offload. They may allow users greater speed, freedom from usage caps, or access in areas of poor coverage. They are also a source of incremental revenue from walk-up customers and roaming agreements. For more information about interacting with public hotspots, see Windows 8 Integration for Wireless Hotspot Operators.

Resources
Overview of Mobile Broadband in Windows 8 http://go.microsoft.com/fwlink/?linkid=242052 Preparing to Develop Mobile Operator Apps http://go.microsoft.com/fwlink/?linkid=242057 Development Guide to Creating Mobile Operator Apps http://go.microsoft.com/fwlink/?linkid=242058 Mobile Operator Hardware Guidelines http://go.microsoft.com/fwlink/?linkid=242059 Designing User Experience of Mobile Operator Apps http://go.microsoft.com/fwlink/?linkid=242066 Overview of Mobile Broadband Windows Runtime API http://go.microsoft.com/fwlink/?linkid=242060 Providing Mobile Broadband Metadata http://go.microsoft.com/fwlink/?linkid=242064 Service Metadata Package Schema Reference for Windows 8 http://go.microsoft.com/fwlink/?linkid=242065 Mobile Operator Notifications and System Events http://go.microsoft.com/fwlink/?linkid=242062 Mobile Broadband SMS http://go.microsoft.com/fwlink/?linkid=242061 Submitting a Mobile Operator App http://go.microsoft.com/fwlink/?linkid=242069 Submit a Bulk Metadata Package http://msdn.microsoft.com/library/c8e248d4-a419-48e1-839d-1bbb9adda382 Submit a Mobile Broadband Experience Metadata Package http://msdn.microsoft.com/library/windows/hardware/080c3f4a-400f-426c8296-1cd0bdfb0828 Introduction to Background Tasks http://go.microsoft.com/fwlink/?LinkID=227329&clcid=0x409

September 28, 2012 2012 Microsoft. All rights reserved.

Overview of Mobile Broadband in Windows 8 - 35

Building Portable Hotspots for Windows 8 http://go.microsoft.com/fwlink/?linkid=242071 Managing connections on metered networks http://msdn.microsoft.com/en-us/library/windows/apps/Hh750310.aspx

September 28, 2012 2012 Microsoft. All rights reserved.