Method and system for mobile device activation

CROSS-REFERENCE TO OTHER APPLICATIONS

p-0002This application claims priority benefit of U.S. Provisional Patent Application No. 60/879,318, filed Jan. 7, 2007, and entitled “METHOD SYSTEM AND GRAPHICAL USER INTERFACE FOR MOBILE DEVICE ACTIVATION,” which is hereby incorporated by reference herein.

p-0003This application also references and/or incorporates: (1) U.S. patent application No. 11/650,859, filed Jan. 7, 2007, and entitled “MOBILE DEVICE ACTIVATION,” which is hereby incorporated by reference herein; (2) U.S. patent application No. 11//767,447, filed Jun. 22, 2007, and entitled “DEVICE ACTIVATION AND ACCESS,” which is hereby incorporated by reference herein; and (3) U.S. patent application No. 11/821,597, filed Jun. 22, 2007, and entitled “GRAPHICAL USER INTERFACE AND METHOD FOR MOBILE DEVICE ACTIVATION,” which is hereby incorporated by reference herein.

COPYRIGHT NOTICE

p-0004A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the U.S. Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND OF THE INVENTION

p-00051. Field of the Invention

p-0006The present invention relates to mobile electronic devices and, more particularly, to activation of mobile electronic devices having wireless communication capabilities.

p-00072. Description of the Related Art

p-0008Mobile phones are often used by individuals on a personal basis. When a mobile phone is newly acquired, the wireless network infrastructure (e.g., cellular phone network) of the appropriate wireless carrier or service provider needs to be setup to work with the mobile phone. Mobile phone setup is principally done at retail establishments that sell mobile phones and wireless service plans. Alternatively, mobile phones can be configured at a manufacturing or distribution site or at a service center. Unfortunately, however, mobile phone setup is time consuming and restrictive to consumers. Additionally, once a mobile phone and service plan have been setup for a consumer, the wireless network needs to be informed of the mobile phone and the mobile phone thereafter needs to register with the wireless network whenever being used. Registration requires a location update request be sent from the mobile phone to the wireless network. In the case of initial phone setup, since location update is triggered on power-up, typically the person configuring the mobile phone would be required to power-off and then power-on the mobile phone to render it active on the wireless network. There is thus a need to avoid the various inconveniences and inefficiencies of conventional mobile phone setup.

SUMMARY OF THE INVENTION

p-0009The invention pertains to methods, systems and graphical user interfaces that facilitate setup or activation of mobile devices, such as communication devices or multi-function devices, via computers. According to one embodiment, activation of a mobile device with respect to a wireless service provider can be performed by users through use of a computer (e.g., personal computer) that communicate with a remotely located activation server. According to another embodiment, graphical user interfaces can be presented to users so as to enable end users to easily activate mobile devices.

p-0010The invention can be implemented in numerous ways, including as a method, system, device, apparatus, graphical user interface, or computer readable medium. Several embodiments of the invention are discussed below.

p-0011As a computer-implemented method for activating wireless network service for an electronic device through use of a host device, where the electronic device is associated with a customer for wireless network service provided by a wireless network service provider, one embodiment can, for example, include at least the acts of: receiving device information from the electronic device when the electronic device is attached to the host device; acquiring customer information pertaining to the customer; receiving a service plan selection from the customer; receiving billing information for payment of the service plan; and initiating activation of a wireless service account for use of the electronic device with the wireless network service provided by the wireless network service provider. The wireless service account being activated can be based on the customer information, the service plan and the billing information.

p-0012As a computer-implemented method for activating an electronic device for wireless network service through use of a host device, where the electronic device is associated with a customer for wireless network service provided by a wireless network service provider, one embodiment can, for example, include at least the acts of: receiving device information from the electronic device while the electronic device is attached to the host device; acquiring customer information pertaining to the customer; offering the user one or more service plans; receiving a user selection of one of the service plans; and receiving billing information for payment of the selected service plan.

p-0013As a computer-implemented method for activating an electronic device for wireless network service from a host device, where the electronic device is associated with a customer for wireless network service provided by a wireless network service provider, one embodiment can, for example, include at least the acts of: receiving device information from the electronic device when the electronic device is attached to the host device; determining whether the electronic device has already been activated based on the device information; and automatically initiating activation of the electronic device when it is determined that the electronic device has not already been activated.

p-0014As a graphical user interface to assist an end user in activating an account for an electronic device having wireless communication capabilities, where the account is with respect to a wireless service provider providing wireless network service, one embodiment of the invention can, for example, include at least a plurality of displayable pages that are presented on a display device associated with a host computer. The displayable pages can, for example, include: an end user status page to facilitate selection of a type of activation; a service plan selection page to facilitate selection of a service plan for the wireless network service; a media account page for a media account associated with an online media store so that a user can create a new media account or login to an existing media account; an end user information entry page to facilitate entry of end user information; a billing information page to facilitate entry of billing information for one or both the user media account and a wireless account; a terms and conditions page regarding legal agreements with the online media store and with the wireless service provider; and/or an activation page to inform the end user of activation information.

p-0015As a computer-implemented method for activating an electronic device for wireless network service, where the electronic device is associated with a customer of a wireless service provider associated with the wireless network service, one embodiment can, for example, include at least the acts of: informing an activation server of an electronic device having wireless communication device that is to be activated for wireless network service; displaying a customer status page to facilitate selection of a type of activation; specifying to the activation server a type of activation desired by the customer; displaying a service plan selection page to facilitate selection of a service plan for the wireless network service; informing the activation server of a selected service plan; displaying a customer account page to facilitate login to or creation of a user media account with an online media store; providing account information for the user media account for the customer; displaying a customer information entry page; providing customer information to the activation server; displaying a billing information page to facilitate entry of billing information for one or both the user media account and a wireless account; informing the activation server of the billing information; displaying a terms and conditions page regarding legal agreements with the online media store and with the wireless service provider; informing the activation server of acceptance of the legal agreements; displaying an information review page; informing the activation server of approval of the information provided on the information review page; displaying an activation completion page; and displaying a device preference page to assist the customer with setting one or more preferences or options to be applied to the operation of the electronic device.

p-0016As a computer readable medium including at least computer executable program code tangibly embodied therein for activating wireless network service for an electronic device through use of a client computing device, the electronic device being associated with a customer for wireless network service provided by a wireless network service provider, one embodiment can, for example, include at least: computer program code for receiving device information from the electronic device when the electronic device is attached to the host device; computer program code for acquiring customer information pertaining to the customer; computer program code for receiving a service plan selection from the customer; computer program code for receiving billing information for payment of the service plan; and computer program code for initiating activation of a wireless service account for use of the electronic device with the wireless network service provided by the wireless network service provider.

p-0017Other aspects and advantages of the invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

p-0018The invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which:

p-0019<figref idrefs="DRAWINGS">FIG. 1</figref> is a block diagram of an activation system according to one embodiment of the invention.

p-0020<figref idrefs="DRAWINGS">FIG. 2A</figref> is a flow diagram of a system activation process according to one embodiment of the invention.

p-0021<figref idrefs="DRAWINGS">FIG. 2B</figref> is a flow diagram of a setup process according to one embodiment of the invention.

p-0022<figref idrefs="DRAWINGS">FIG. 3</figref> is a flow diagram of a device operational process according to one embodiment of the invention.

p-0023<figref idrefs="DRAWINGS">FIG. 4</figref> is a flow diagram of a device operation process according to another embodiment of the invention.

p-0024<figref idrefs="DRAWINGS">FIG. 5</figref> is a system state diagram according to one embodiment of the invention.

p-0025<figref idrefs="DRAWINGS">FIGS. 6A-6C</figref> are flow diagrams of a network service setup process according to one embodiment of the invention.

p-0026<figref idrefs="DRAWINGS">FIG. 6D</figref> is a flow diagram of an alternative portion of the network service setup process according to one embodiment of the invention.

p-0027<figref idrefs="DRAWINGS">FIG. 7</figref> is a flow diagram of a network service setup process according to one embodiment of the invention.

p-0028<figref idrefs="DRAWINGS">FIGS. 8A-8C</figref> are flow diagrams of an activation process according to one embodiment of the invention.

p-0029<figref idrefs="DRAWINGS">FIG. 9</figref> is a flow diagram of an activation process according to another embodiment of the invention.

p-0030<figref idrefs="DRAWINGS">FIG. 10</figref> is a flow diagram of an activation process according to another embodiment of the invention.

p-0031<figref idrefs="DRAWINGS">FIG. 11</figref> is a flow diagram of an activation process according to another embodiment of the invention.

p-0032<figref idrefs="DRAWINGS">FIGS. 12A-12C</figref> are flow diagrams of a mobile device provisioning process according to one embodiment of the invention.

p-0033<figref idrefs="DRAWINGS">FIG. 13</figref> is a screen shot of an exemplary initial registration page according to one embodiment of the invention.

p-0034<figref idrefs="DRAWINGS">FIG. 14</figref> is a screen shot of an exemplary customer status page according to one embodiment of the invention.

p-0035<figref idrefs="DRAWINGS">FIG. 15</figref> is a screen shot of an exemplary screen shot of a mobile number transfer page.

p-0036<figref idrefs="DRAWINGS">FIG. 16</figref> is a screen shot of an exemplary screen shot of a landline number transfer page.

p-0037<figref idrefs="DRAWINGS">FIGS. 17A and 17B</figref> are screen shots of an exemplary service plan selection page according to one embodiment of the invention.

p-0038<figref idrefs="DRAWINGS">FIG. 18</figref> is a screen shot of an exemplary customer account page according to one embodiment of the invention.

p-0039<figref idrefs="DRAWINGS">FIG. 19</figref> is a screen shot of a customer information entry page according to one embodiment of the invention.

p-0040<figref idrefs="DRAWINGS">FIG. 20</figref> illustrates an exemplary billing information page according to one embodiment of the invention.

p-0041<figref idrefs="DRAWINGS">FIG. 21A</figref> is an exemplary screen shot of a first terms and conditions page according to one embodiment of the invention.

p-0042<figref idrefs="DRAWINGS">FIG. 21B</figref> is an exemplary screen shot of a second terms and conditions page according to one embodiment of the invention.

p-0043<figref idrefs="DRAWINGS">FIG. 22</figref> is a screen shot of an exemplary review information page according to one embodiment of the invention.

p-0044<figref idrefs="DRAWINGS">FIG. 23</figref> is an exemplary screen shot of a setup completion page according to one embodiment of the invention.

p-0045<figref idrefs="DRAWINGS">FIG. 24A</figref> is an exemplary screen shot of a setup completion page according to another embodiment of the invention.

p-0046<figref idrefs="DRAWINGS">FIG. 24B</figref> is an exemplary screen shot of a setup completion page according to still another embodiment of the invention.

p-0047<figref idrefs="DRAWINGS">FIG. 25</figref> is an exemplary screen shot of a device preference page according to one embodiment of the invention.

p-0048<figref idrefs="DRAWINGS">FIG. 26</figref> is a screen shot of an exemplary customer status page according to one embodiment of the invention.

p-0049<figref idrefs="DRAWINGS">FIG. 27</figref> is a screen shot of an exemplary account information page according to one embodiment of the invention.

p-0050<figref idrefs="DRAWINGS">FIG. 28</figref> is a screen shot of an exemplary customer status page according to one embodiment of the invention.

p-0051<figref idrefs="DRAWINGS">FIG. 29</figref> is a screen shot of an exemplary account information page according to one embodiment of the invention.

p-0052<figref idrefs="DRAWINGS">FIG. 30</figref> is a screen shot of an exemplary account type selection page according to one embodiment of the invention.

p-0053<figref idrefs="DRAWINGS">FIG. 31</figref> is a screen shot of an exemplary customer status page according to one embodiment of the invention.

p-0054<figref idrefs="DRAWINGS">FIG. 32</figref> is a screen shot of an exemplary account type selection page according to one embodiment of the invention.

p-0055<figref idrefs="DRAWINGS">FIG. 33</figref> is a screen shot of an exemplary prepayment requirement page.

p-0056<figref idrefs="DRAWINGS">FIG. 34</figref> is a block diagram of a mobile multi-function device according to one embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

p-0057The invention pertains to methods, systems and graphical user interfaces that facilitate setup or activation of mobile devices, such as communication devices or multi-function devices, via computers. According to one embodiment, activation of a mobile device with respect to a wireless service provider can be performed by users through use of a computer (e.g., personal computer) that communicate with a remotely located activation server. According to another embodiment, graphical user interfaces can be presented to users so as to enable end users to easily activate mobile devices.

p-0058Embodiments of the invention are discussed below with reference to <figref idrefs="DRAWINGS">FIGS. 1-34</figref>. However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the invention extends beyond these limited embodiments.

p-0059<figref idrefs="DRAWINGS">FIG. 1</figref> is a block diagram of an activation system <b>100</b> according to one embodiment of the invention. The activation system <b>100</b> includes a client machine <b>102</b>. The client machine <b>102</b> is, for example, a computing device, such as a personal computer. The client machine <b>102</b> can also be referred to as a host device. A mobile multi-function device <b>104</b> can be connected (e.g., temporarily connected) to the client machine <b>102</b>. In one implementation, the mobile multi-function device <b>104</b> can be connected to the client machine <b>102</b> over a cable <b>106</b>. As an example, the cable <b>106</b> can pertain to a peripheral bus (e.g., USB) connection. In another implementation, the mobile multi-function device <b>104</b> can connect to the client machine <b>102</b> over a wireless connection. The mobile multi-function device <b>104</b> operates to support a plurality of different functions. For example, the mobile multi-function device <b>104</b> can operate as a media playback device, such as an MP3 player, video player, game player, etc. In addition, the mobile multi-function device <b>104</b> can support wireless voice communications through a wireless network <b>108</b>. The wireless voice communications through the wireless network <b>108</b> can enable a user of the mobile multi-function device to communicate with users of other mobile multi-function devices or other communication devices. Similarly, the mobile multi-function device <b>104</b> can support wireless data exchange (e.g., SMS messages) through the wireless network <b>108</b>. Although <figref idrefs="DRAWINGS">FIG. 1</figref> illustrates one client machine <b>102</b> and one mobile multi-function device <b>104</b>, it should be noted that the activation system <b>100</b> can have multiple client machines <b>102</b> and multiple mobile multi-function devices <b>104</b>. In addition, one or more of the mobile multi-function devices can connect to one or more client machines. In one implementation, the wireless network <b>108</b> can represent a cellular telephone network. In another implementation, the wireless network <b>108</b> can represent a local or regional wireless network (e.g., WiFi, WiMax). In still another implementation, the wireless network <b>108</b> can represent multiple wireless networks.

p-0060The activation system <b>100</b> also illustrates a data network <b>110</b>. The data network is, for example, a local area network, a wide area network, or a global network, such as the Internet. The client machine <b>102</b> can couple to the data network <b>110</b>. In addition, the activation system <b>100</b> includes an activation server <b>112</b> and a wireless communication provider server <b>114</b>. In order to activate the mobile multi-function device <b>104</b>, the mobile multi-function device <b>104</b> interacts with the activation server <b>112</b>. To do so, the mobile multi-function device <b>104</b> communicates with the client machine <b>102</b> and the client machine <b>102</b> in turn communicates with the activation server <b>112</b> through the data network <b>110</b>. In this regard, the activation server <b>112</b> can coordinate and control activation of the mobile multi-function device <b>104</b>. In addition, the activation server <b>112</b> can communicate with the wireless communication provider server <b>114</b> so that an appropriate account to be utilized by the mobile multi-function device <b>104</b> can be established by the wireless communication provider that is operating on the wireless network <b>108</b>.

p-0061<figref idrefs="DRAWINGS">FIG. 2A</figref> is a flow diagram of a system activation process <b>200</b> according to one embodiment of the invention. The system activation process <b>200</b> concerns activation of a mobile multi-function device (MMD). The system activation process <b>200</b> begins with a mobile multi-function device being obtained <b>202</b>. For example, a user can obtain <b>202</b> a mobile multi-function device at a retail location or by mail order. In this embodiment, when the mobile multi-function device is obtained <b>202</b>, it is not activated for use with any wireless network. As a result, the mobile multi-function device needs to go through an activation process in order to operate. In this regard, after the mobile multi-function device is obtained <b>202</b>, a service plan and a payment arrangement need to be setup <b>204</b>. After the service plan and payment arrangement have been successfully setup <b>204</b>, the mobile multi-function device can be enabled <b>206</b>. In addition, the mobile multi-function device can be registered with a network, namely, a wireless network. Here, the registration <b>208</b> with the network is performed to permit the mobile multi-function device to be utilized on the network.

p-0062Following successful enabling <b>206</b> and registration <b>208</b>, the mobile multi-function device can operate <b>210</b> with or without utilization of the network. In this regard, since the mobile multi-function device supports multiple functions, the mobile multi-function device can be utilized in a non-network manner, such as playing local games, displaying local data, playing music from local storage, viewing local pictures, viewing locally stored electronic mail, etc. However, if the user of the mobile multi-function device desires to utilize the network (e.g., make or receive voice calls or electronic messages), network access is permitted in accordance with the service plan that has been setup <b>204</b>, provided that the registration <b>208</b> was successful and provided that the network is available.

p-0063Once the mobile multi-function device is enabled <b>206</b> some or all of the functions or operations supported by the mobile multi-function device can be utilized. In one embodiment, once enabled <b>206</b>, the mobile multi-function device can be utilized for all non-network functions or operations available from the mobile multi-function device, with network functions or operations becoming available following registration at block <b>208</b>. In another embodiment, functions or operations of the mobile multi-function device can be prevented or restricted until completion of initial (i.e., first time) registration at block <b>208</b> at which point all functions or operations available from the mobile multi-function device can be utilized. In still another embodiment, certain, non-network functions or operations of the mobile multi-function device can be available even prior to the mobile multi-function device being enabled <b>206</b>.

p-0064<figref idrefs="DRAWINGS">FIG. 2B</figref> is a flow diagram of a setup process <b>250</b> according to one embodiment of the invention. The setup process <b>250</b> operates to setup a service plan and/or payment arrangement with respect to one or more service providers. The setup process <b>250</b> is, for example, suitable for use as the setup <b>204</b> of a service plan and payment arrangement illustrated in <figref idrefs="DRAWINGS">FIG. 2A</figref>.

p-0065The setup process <b>250</b> retrieves <b>252</b> device information. Typically, the device information is retrieved <b>252</b> from the device itself. For example, the device can be referred to as a mobile multi-function device. Customer information can also be acquired <b>254</b>, such as from the customer. The customer information can be acquired <b>254</b> so that the service provider can receive information regarding the customer that seeks to activate the mobile multi-function device. A service plan for the device is also set <b>256</b>. The customer can be offered one or more service plans depending upon various different criteria, including customer's location, customer's credit history, customer's current service provider, etc. A service plan as used herein can also be referred to as a rate plan. Once a service plan to be utilized with the customer has been set <b>256</b>, a billing account can be setup <b>258</b>. The billing account serves to facilitate billing the customer for the services provided by the service plan. Typically, the customer is billed monthly for the service plan. The setup <b>258</b> of the billing account acquires all the necessary information for billing the customer. As one example, the billing account can utilize a credit card whereby the customer is billed monthly via the credit card for the service plan. Subsequently, the customer account can be activated <b>260</b>. In this regard, the setup process <b>250</b> can communicate with a computing device (e.g., activation server <b>112</b>) associated with a service provider to activate a customer account so that the customer can utilize the mobile multi-function device with the at least one service provider in accordance with the service plan. The service provider is, for example, a wireless (communications) service provider. Additionally, an account with another service provider, such as an online media store, can be established. Following the block <b>260</b>, the setup process <b>250</b> ends and subsequent processing can continue at block <b>206</b> of the system activation process <b>200</b> illustrated in <figref idrefs="DRAWINGS">FIG. 2A</figref>.

p-0066<figref idrefs="DRAWINGS">FIG. 3</figref> is a flow diagram of a device operational process <b>300</b> according to one embodiment of the invention. The device operational process <b>300</b> is, for example, processing associated with a mobile multi-function device, such as the mobile multi-function device <b>104</b> illustrated in <figref idrefs="DRAWINGS">FIG. 1</figref>.

p-0067The device operational process <b>300</b> can begin when the mobile multi-function device is powered on. Hence, a decision <b>302</b> determines whether the mobile multi-function device has been powered on. When the mobile multi-function device has not been powered on, the device operational process <b>300</b> is not performed. On the other hand, when the decision <b>302</b> determines that the mobile multi-function device has been powered on, a decision <b>304</b> can determine whether the mobile multi-function device has been enabled. Here, it is assumed that the mobile multi-function device performing the device operational process <b>300</b> may or may not have been enabled to operate. Hence, when the decision <b>304</b> determines that the mobile multi-function device has not been enabled, the mobile multi-function device is eligible to operate <b>306</b> in a limited use mode. As an example, in the limited use mode, the mobile multi-function device can permit emergency communications (e.g., emergency telephone calls). However, the limited use mode may prevent other operations of the mobile multi-function device. For example, if the mobile multi-function device provides media playback or network browsing, then when in the limited use mode, media playback and/or network browsing can be prevented (or limited). In one implementation, while in the limited use mode, the mobile multi-function device can prevent all other operational uses except emergency communications.

p-0068On the other hand, when the decision <b>304</b> determines that the mobile multi-function device is enabled, the mobile multi-function device can operate in a full use mode. Following the blocks <b>306</b> and <b>308</b>, a decision <b>312</b> can determine whether the mobile multi-function device is to be powered off. When the decision <b>312</b> determines that the mobile multi-function device should not be powered off, the mobile multi-function device continues to operate in the previously established operational mode (e.g., limited use mode or full use mode). On the other hand, when the decision <b>312</b> determines that the mobile multi-function device should be powered off, the mobile multi-functional device is powered down <b>314</b>. Following the block <b>314</b>, the device operational process <b>300</b> can end.

p-0069<figref idrefs="DRAWINGS">FIG. 4</figref> is a flow diagram of a device operation process <b>400</b> according to another embodiment of the invention. The device operational process <b>400</b> is, for example, processing associated with a mobile multi-function device, such as the mobile multi-function device <b>104</b> illustrated in <figref idrefs="DRAWINGS">FIG. 1</figref>.

p-0070The device operational process <b>400</b> begins with a decision <b>402</b>. The decision <b>402</b> determines whether the mobile multi-function device has been powered on. When the decision <b>402</b> determines that the mobile multi-function device has not been powered on, the device operational process <b>402</b> awaits power on of the mobile multi-function device. Once the decision <b>402</b> determines that the mobile multi-function device has been powered on, the device operational process <b>400</b> is effectively invoked. Once the decision <b>402</b> determines that the mobile multi-function device has been powered on, a decision <b>404</b> determines whether the mobile multi-function device has been enabled.

p-0071When the decision <b>404</b> determines that the mobile multi-function device has not yet been enabled, the device operational process <b>400</b> places <b>406</b> the mobile multi-function device in an emergency mode. In the emergency mode, the mobile multi-function device is permitted to make emergency calls only. Next, a decision <b>408</b> determines whether the mobile multi-function device is to be powered off. When the decision <b>408</b> determines that the mobile multi-function device is not to be powered off, the device operational process <b>400</b> returns to repeat the decision <b>404</b> to again evaluate whether the mobile multi-function device has been enabled. In an alternative embodiment, when the decision <b>408</b> determines that the mobile multi-function device is not to be powered off, the device operation process <b>400</b> can remain in the emergency mode and simply repeat the decision <b>404</b> until powered off.

p-0072Alternatively, when the decision <b>404</b> determines that the mobile multi-function device has been enabled, the mobile multi-function device is placed <b>410</b> in an active mode. Registration with a wireless network can also be requested <b>412</b>. In one embodiment, a location update request can be used to request <b>412</b> registration with the wireless network. A decision <b>414</b> determines whether the registration with the wireless network has been successful. When the decision <b>414</b> determines that the registration has been successful, the device operational process <b>400</b> permits <b>416</b> the mobile multi-function device to perform network and/or non-network operations. Next, a decision <b>418</b> determines whether the mobile multi-function device is to be powered off. When the decision <b>418</b> determines that the mobile multi-function device has not been powered off, the device operational process <b>400</b> returns to repeat the block <b>416</b> so that the mobile multi-function device can continue to perform <b>416</b> network and/or non-network operations.

p-0073On the other hand, when the decision <b>414</b> determines that registration with the wireless network has not been successful, then the user of the multi-function device can be notified <b>422</b> that the network is unavailable. In one implementation, the notification <b>422</b> can be displayed on a display screen for one or both of the multi-function device or a client device connected thereto. Further, the mobile multi-function device can be operated to permit <b>424</b> non-network operations. A decision <b>426</b> can then determine whether the mobile multi-function device is to be powered off. When the decision <b>426</b> determines that the mobile multi-function device is not to be powered off, the device operational process <b>400</b> returns to repeat the block <b>424</b> so that non-network operations can continue to be performed <b>424</b>.

p-0074When any of the decisions <b>408</b>, <b>418</b> or <b>426</b> determine that the mobile multi-function device is to be powered off, the mobile multi-function device can be powered down <b>420</b>. After the mobile multi-function device has been powered down, the device operational process <b>400</b> ends.

p-0075<figref idrefs="DRAWINGS">FIG. 5</figref> is a system state diagram <b>500</b> according to one embodiment of the invention. The system state diagram <b>500</b> illustrates a plurality of states associated with system activation of a mobile multi-function device (MMD) according to one embodiment. At state <b>502</b>, a mobile multi-function device is obtained. At state <b>504</b>, following the state <b>502</b>, the mobile multi-function device is powered-on. Next, at state <b>506</b>, the mobile multi-function device is connected to a computer, (e.g., personal computer). Thereafter, at state <b>508</b>, one or more accounts can be arranged. These accounts can pertain to an account with an online media store and/or an account with a wireless service provider. Next, at state <b>510</b>, a service plan can be selected. Typically, the service plans are associated with a wireless service provider that is providing wireless network access for the mobile multi-function device. In addition, payment can be arranged at state <b>512</b>. It should also be noted that states <b>510</b> and/or <b>512</b> could be part of the state <b>508</b>.

p-0076Following state <b>512</b>, at state <b>514</b>, the mobile multi-function device can be enabled. Once enabled, the mobile multi-function device is able to be fully utilized. Subsequently, the mobile multi-function device can be registered with a network (e.g., wireless network) at state <b>516</b>. The registration with the network enables the mobile multi-function device to send and receive calls with respect to the network. Optionally, it should be noted that following the state <b>504</b>, in the event that the mobile multi-function device was previously enabled, the mobile multi-function device can transition directly to state <b>516</b>. In any case, once the mobile multi-function device has been registered with the network at state <b>516</b>, the mobile multi-function device can be utilized with the network at state <b>518</b>. Following the state <b>518</b>, the mobile multi-function device can be powered off at state <b>520</b>. Also, following the state <b>514</b>, the mobile multi-function device can be disconnected from the computer at state <b>522</b> or the mobile multi-function device can be powered off at state <b>524</b>.

p-0077In an alternative embodiment, at state <b>514</b>, the mobile multi-function device can be enabled for only certain functions or operations. In this manner, the mobile multi-function device can have its available functions or operations controlled such that available functions or operations can be available (and others restricted) at (i) pre-enablement, (ii) post-enablement, and (iii) post-registration.

p-0078As such, activation can include one or more of account activation, device activation (i.e., enablement), and network activation (i.e., network setup). In one embodiment, the states <b>508</b>, <b>510</b> and <b>512</b> can be considered account activation, and the state <b>514</b> can be considered device activation. Following state <b>512</b> or state <b>514</b> and prior to <b>516</b>, the network can be setup (i.e., network activation) to support the account for the mobile multi-function device being activated.

p-0079<figref idrefs="DRAWINGS">FIGS. 6A-6C</figref> are flow diagrams of a network service setup process <b>600</b> according to one embodiment of the invention. For example, with reference to <figref idrefs="DRAWINGS">FIG. 1</figref>, the network service setup process <b>600</b> is processing performed when the mobile multi-function device <b>104</b> is connected to the client machine <b>102</b> illustrated in <figref idrefs="DRAWINGS">FIG. 1</figref> so that interaction with the activation server <b>112</b> can be performed to setup service for the mobile multi-function device <b>104</b>.

p-0080The network service setup process <b>600</b> can begin with a decision <b>602</b> that determines whether the mobile multi-function device is attached to the client machine (e.g., personal computer). When the decision <b>602</b> determines that the mobile multi-function device is not attached, then the network service setup process <b>600</b> is not performed. On the other hand, when the decision <b>602</b> determines that the mobile multi-function device is attached, the network service setup process <b>600</b> can be performed. In one embodiment, the network setup process <b>600</b> can be automatically initiated where the mobile multi-function device is attached to the client machine.

p-0081When the network setup process <b>600</b> is performed, mobile multi-function device (MMD) information is received <b>604</b> from the mobile multi-function device. Next, a decision <b>605</b> determines whether a user activation request has been received. When the decision <b>605</b> determines that a user activation request has not been received, the network service setup process <b>600</b> can await a user activation request. A user can request activation of the mobile multi-function device. In one example, the user can specify whether the activation of the mobile multi-function device is to be associated with a new account or an existing account. On the other hand, when the decision <b>605</b> determines that a user activation request has been received, a decision <b>606</b> can then determine whether the mobile multi-function device is to be subject to an existing account. The decision <b>606</b> can be based on the user activation request which can indicate whether the activation of the mobile multi-function device is to be associated with a new account or an existing account. When the decision <b>606</b> determines that the mobile multi-function device is not subject to an existing account, account setup information is requested <b>608</b>. The account setup information is information used to setup a new account. The account setup information can, for example, be provided by user. A decision <b>610</b> then determines whether the account setup information has been received. When the decision <b>610</b> determines that the account setup information has not yet been received, the network service setup process <b>600</b> awaits such information. Once the decision <b>610</b> determines that the account setup information has been received, a user account can be setup <b>612</b>. The user account can pertains to a user account with a wireless service provider, an online media store, and/or some other account. The user account contains information concerning the user and often includes personal information and financial information.

p-0082On the other hand, when the decision <b>606</b> determines that an existing account is associated with the mobile multi-function device, authentication information can be requested <b>614</b>. A decision <b>616</b> can then determine whether the authentication information has been received. When the decision <b>616</b> determines that the authentication information has not yet been received, the network service setup process <b>600</b> can await such information. Alternatively, when the decision <b>616</b> determines that the authentication information has been received, a decision <b>618</b> can determine whether the user is authenticated for access to the existing account. When the decision <b>618</b> determines that the user has not been authenticated, an error indication <b>620</b> can be provided. Following the block <b>620</b>, the network service setup process <b>600</b> can end with network setup not being completed.

p-0083Following the block <b>612</b> or following the decision <b>618</b> when the user has been properly authenticated, the user can be offered <b>622</b> one or more service plans. In one embodiment, the one or more service plans being offered <b>622</b> can depending on a credit evaluation (e.g., credit score) for the user. For example, a user having poor credit can be only offered service plans that require prepayment. A decision <b>624</b> then determines whether a plan has been selected but the user. When the decision <b>624</b> determines that a plan has not yet been selected, the network service setup process <b>600</b> awaits such a selection. Once the decision <b>624</b> determines that a plan has been selected, a decision <b>628</b> determines whether a new account is being processed. When the decision <b>628</b> determines that a new account is being processed, setup of a billing account can be requested <b>630</b>. However, when the decision <b>628</b> determines that an existing account is being processed, the block <b>630</b> can be bypassed. The request <b>630</b> can include payment information, such as payment information provided by the user. In one embodiment, the network setup process <b>600</b> already received or has access to the payment information to be used for the account. As one example, the account setup information can include the billing account information. In another embodiment, the network setup process <b>600</b> can request and receive the payment information prior to the request <b>630</b>. When the decision <b>628</b> determines that payment information has not yet been received, the network service setup process <b>600</b> can await receipt of the payment information. Once the decision <b>628</b> determines that the payment information has been received, setup of a billing account can be requested <b>630</b>.

p-0084Thereafter, activation of the account for the user can be requested <b>631</b>. A decision <b>632</b> can then determine whether activation confirmation and phone number for the account being established have been received. When the activation confirmation and phone number have not been received, the network service setup process <b>600</b> can await such information. Alternatively, when the decision <b>632</b> determines that the activation confirmation and phone number have been received, the user can be informed <b>634</b> of successful account setup and the appropriate phone number.

p-0085Following the block <b>634</b>, the mobile multi-function device is enabled <b>636</b>. In one implementation, the client machine <b>102</b> can write certain information into data storage on the mobile multi-function device <b>104</b> to inform the mobile multi-function device <b>104</b> that the device is now enabled. The mobile multi-function device can then self-determine whether the device is enabled by reading the stored information. Following the block <b>636</b> the mobile multi-function device can be disconnected from the client machine.

p-0086In any case, following the block <b>636</b>, a decision <b>638</b> determines whether network setup has been completed. When the decision <b>638</b> determines that network setup has been completed, the user can be notified <b>640</b> that network setup has completed. The notification can alert the user to perform an action with respect to the mobile multi-function device so that the mobile multi-function device can register with the network and thereafter be utilized thereon. As an example, the notification can be provided to the user by displaying an indication or by sending an electronic message (e.g., email or text message) to the associated client machine. For example, the user can be instructed by the notification to power cycle the mobile multi-function device or connect the mobile multi-function device to the client machine. Following the block <b>640</b>, the network service setup process <b>600</b> ends.

p-0087On the other hand, when the decision <b>638</b> determines that the network setup is not complete, the network service setup process <b>600</b> can perform other processing <b>642</b> unassociated with the network setup. For example, the other processing <b>642</b> can pertain to the synchronization of data between the client machine <b>102</b> and the mobile multi-function device <b>104</b>. The other processing <b>642</b> can also pertain to media playback at the mobile multi-function device, setting of preferences at the mobile multi-function device or at the client machine, etc. Following the block <b>642</b>, a decision <b>644</b> can determine whether completion of the network setup for the mobile multi-function device should be re-checked. In one embodiment, the completion of the network setup can be re-checked periodically (e.g., every 2 minutes). Typically, if the network setup has not properly completed after a number of attempts or period of time, the network service setup process <b>600</b> could end and inform the use that the network service was not able to be setup. In any case, when the decision <b>644</b> determines that the network setup should be re-checked, the network service setup process <b>600</b> can repeat the decision <b>638</b> and subsequent blocks to again determine whether network setup has completed. Alternatively, when the decision <b>644</b> determines that the network setup should not be re-checked, the network service setup process <b>600</b> can repeat the block <b>642</b> so that other processing can optionally be performed.

p-0088<figref idrefs="DRAWINGS">FIG. 6D</figref> is a flow diagram of an alternative portion of the network service setup process <b>600</b> according to one embodiment of the invention. In particular, the blocks <b>646</b>-<b>660</b> illustrated in <figref idrefs="DRAWINGS">FIG. 6D</figref> represent an alternative embodiment for the portion of the network service setup process <b>600</b> illustrated in <figref idrefs="DRAWINGS">FIG. 6C</figref>, namely, blocks <b>636</b>-<b>644</b>. Following the block <b>634</b>, the mobile multi-function device is enabled <b>646</b>. In one implementation, the client machine <b>102</b> can write certain information into data storage on the mobile multi-function device <b>104</b> to inform the mobile multi-function device <b>104</b> that the device is now enabled. The mobile multi-function device can then self-determine whether the device is enabled by reading the stored information. In any case, following the block <b>646</b>, a decision <b>648</b> determines whether network setup has been completed. When the decision <b>648</b> determines that network setup has been completed, the mobile multi-function device can be instructed <b>650</b> to register with the network. The mobile multi-function device can be instructed <b>650</b> to register with the network by causing a location update to be issued from the mobile multi-function device. In one implementation, the client machine <b>102</b> can send a command to the mobile multi-function device <b>104</b> to initiate the location update. In another implementation, the client machine <b>102</b> can cause the mobile multi-function device <b>104</b> to reset its radio transmitter/receiver (i.e., a portion of its hardware) so as to trigger a location update.

p-0089On the other hand, when the decision <b>648</b> determines that the network setup is not complete, a decision <b>652</b> determines whether the mobile multi-function device has been disconnected from the client machine. When the decision <b>652</b> determines that the mobile multi-function device has not been disconnected, the network service setup process <b>600</b> can perform other processing <b>654</b> unassociated with the network setup. For example, the other processing <b>654</b> can pertain to the synchronization of data between the client machine <b>102</b> and the mobile multi-function device <b>104</b>. The other processing can also pertain to media playback at the mobile multi-function device, setting of preferences at the mobile multi-function device or at the client machine, etc. Following the block <b>654</b>, the network service setup process <b>600</b> returns to repeat the decision <b>648</b> to again determine whether network setup has completed.

p-0090Alternatively, when the decision <b>652</b> determines that the mobile multi-function device has been disconnected from the client machine, a decision <b>656</b> determines whether network setup has completed. When the decision <b>656</b> determines that network setup has not completed, other processing <b>658</b> can be performed until the network setup has completed. Alternatively, when the decision <b>656</b> determines that network setup has completed, the user can be notified <b>660</b> that network setup has completed. The notification can alert the user to perform an action with respect to the mobile multi-function device so that the mobile multi-function device can register with the network and thereafter be utilized thereon. As an example, the notification can be provided to the user by displaying an indication or by sending an electronic message (e.g., email or text message) to the user. The electronic message can, for example, be sent to the mobile multi-function device or the associated client machine. For example, the user can be instructed by the notification to power cycle the mobile multi-function device or connect the mobile multi-function device to the client machine. Following the blocks <b>650</b> and <b>660</b>, the network service setup process <b>600</b> ends.

p-0091In one embodiment, the mobile multi-function device can store information that can be used to determine whether the mobile multi-function device is enabled. For example, the mobile multi-function device can stored an identifier (e.g., activation identifier) that is provided by a client machine once the mobile multi-function device is to be enabled. In one embodiment, the identifier is stored in a secured manner, such as through use of encryption, digital certificate or other cryptographic technique. The identifier can include or be based on a Subscriber Identity Module (SIM) that is included in the mobile multi-function device while activated. In one implementation, a SIM value, such as a SIM card identifier (e.g., ICCID), read from the SIM card itself within the mobile multi-function device is compared to the identifier stored in a data store (e.g., Flash memory) within the mobile multi-function device. If the identifier matches the read SIM value, then the mobile multi-function device has previously been enabled. As such, the mobile multi-function device can self-determine whether it has been enabled. This enablement verification can, for example, prevent different SIM cards from being used with a mobile multi-function device that has been previously activated while using a different SIM card. An alternative to a SIM is a Universal Subscriber Identity Module (USIM). SIM cards are used with GSM type wireless networks. Other types of networks, such as CMDA, can use other identifiers. Often the identifiers in other networks are not removable from the multi-function device by users. In such cases, the identifier is stored within the device itself such that the identifier is not removable from the device. In such cases, the mobile multi-function device can simply store a flag that indicates whether or not the mobile multi-function device is enabled.

p-0092<figref idrefs="DRAWINGS">FIG. 7</figref> is a flow diagram of a network service setup process <b>700</b> according to one embodiment of the invention. The network service setup process <b>700</b> is, for example, processing performed when activating a Mobile Multi-function Device (MMD). For example, the network service setup process <b>700</b> can be associated with processing performed when the mobile multi-function device <b>104</b> is connected to the client machine <b>102</b> illustrated in <figref idrefs="DRAWINGS">FIG. 1</figref> so that interaction with the activation server <b>112</b> can be performed via the client machine <b>102</b> to setup service for the mobile multi-function device <b>104</b>.

p-0093The network service setup process <b>700</b> can begin with a decision <b>702</b> that determines whether the mobile multi-function device is attached to the client machine (e.g., personal computer). When the decision <b>702</b> determines that the mobile multi-function device is not attached, the network service setup process <b>700</b> is not performed. On the other hand, when the decision <b>702</b> determines that the mobile multi-function device is attached, the network service setup process <b>700</b> can be performed. Once the decision <b>702</b> determines that the mobile multi-function device is attached, Mobile Multi-function Device (MMD) information can be read <b>704</b> from the multi-function device. In one embodiment, the MMD information can be encrypted so as to prevent unauthorized access. For additional details on preventing unauthorized access to device information, such as the MMD information, see, for example, U.S. pat. application Ser. No. 11/767,447, filed Jun. 22, 2007, and entitled “DEVICE ACTIVATION AND ACCESS,” which is hereby incorporated by reference herein. After the MMD information has been read <b>704</b>, a decision <b>706</b> determines whether the mobile multi-function device has already been activated. When the decision <b>706</b> determines that the mobile multi-function device has already been activated, then other processing <b>708</b> can be performed In other words, in one embodiment, the mobile multi-function device can perform various other processing <b>708</b> supported by the device given that the device has been activated. In this regard, the mobile multi-function device can utilize network service. Following the block <b>708</b>, since the mobile multi-function device has already been activated, the network service setup process <b>700</b> can end.

p-0094When the decision <b>706</b> determines that the mobile multi-function device has not already been activated, a decision <b>710</b> determines that a user activation request has been received. When the decision <b>710</b> determines that a user activation request has not been received, the network service setup process <b>700</b> awaits a user activation request. Alternatively, when the decision <b>710</b> determines that a user activation request has been received, a decision <b>712</b> determines whether the user is a new customer. When the decision <b>712</b> determines that the user is a new customer, a decision <b>714</b> determines whether the customer desires an individual plan or a family plan. When the decision <b>714</b> determines that the customer desires an individual plan, processing proceeds to <figref idrefs="DRAWINGS">FIGS. 8A-8C</figref> where an activation process for an individual plan is described. On the other hand, when the decision <b>714</b> determines that the customer desires a family plan, processing proceeds to <figref idrefs="DRAWINGS">FIG. 9</figref> where an activation process for a family plan is described.

p-0095On the other hand, when the decision <b>712</b> determines that the user is not a new customer, but is instead an existing customer, then a decision <b>716</b> determines whether the mobile multi-function device is a new device being substituted for a previously activated device. When the decision <b>716</b> determines that the mobile multi-function device is a new device, then processing proceeds to <figref idrefs="DRAWINGS">FIG. 10</figref> where an activation process for an existing account is described. Alternatively, when the decision <b>716</b> determines that the mobile multi-function device is not new, a decision <b>718</b> can determine whether a new line is to be added to an existing account. When the decision <b>718</b> determines that a new line is to be added to an existing account, then processing proceeds to <figref idrefs="DRAWINGS">FIG. 11</figref> where an activation process for a new line is described. Alternatively, when the decision <b>718</b> determines that a new line is not to be provided, then activation can be deemed <b>720</b> unavailable. Following the block <b>720</b>, the network service setup process <b>700</b> can end.

p-0096<figref idrefs="DRAWINGS">FIGS. 8A-8C</figref> are flow diagrams of an activation process <b>800</b> according to one embodiment of the invention. The activation process <b>800</b> corresponds to activation of a mobile multi-function device with respect to an individual user plan.

p-0097The activation process <b>800</b> can begin with a decision <b>802</b> that determines whether a phone number is to be transferred. A phone number that can be transferred can be associated with another service provider. Typically, the phone number eligible to be transferred is from another wireless service provider. However, more generally, the phone number eligible to be transferred can correspond to either a wireless account or a land line account. In any case, when the decision <b>802</b> determines that a phone number is to be transferred, an existing phone number and account information for another service provider are provided <b>804</b>. Typically, the customer will interact with a graphical user interface to provide the information regarding the existing phone number and account information.

p-0098Following the block <b>804</b> as well as directly following the decision <b>802</b> when a phone number is not to be transferred, customer information can be requested <b>806</b>. The customer information can include name, address, date of birth, security question(s), e-mail address, account identifier, etc. The customer information can be utilized for one or more accounts that are to be established with one or more service providers. A decision <b>808</b> determines whether the customer information has been received. When the decision <b>808</b> determines that the customer information has not been received, the activation process <b>800</b> can await the customer information.

p-0099After the decision <b>808</b> determines that the customer information has been received, a decision <b>810</b> can determine whether the location of the customer is supported. Here, the service provider typically only supports specific geographical locations. Hence, the customer location can be examined to determine whether it is within a geographical location supported by the system. Hence, when the decision <b>810</b> determines that the customer location is not supported by the system of the service provider, the customer can be informed <b>812</b> that activation is unavailable. Following the block <b>812</b>, the activation process <b>800</b> can end without activating the mobile multi-function device.

p-0100On the other hand, when the decision <b>810</b> determines that the customer location is supported by the system of the service provider, one or more service plans to be offered to the customer can be determined <b>814</b>. Next, the one or more service plans are offered <b>816</b> to the customer. A decision <b>818</b> then determines whether the customer has selected one of the service plans. When the decision <b>818</b> determines that a service plan has not yet been selected, the activation process <b>800</b> can await a plan selection. Alternatively, when the decision <b>818</b> determines that a service plan has been selected, billing information can be requested <b>820</b>. The billing information can be utilized by one or more service providers. A decision <b>822</b> determines whether the billing information has been received. When the decision <b>822</b> determines that the requested billing information has not been received, the activation process <b>800</b> can await the billing information. Once the decision <b>822</b> determines that the billing information has been received, account information approval is requested <b>824</b>. The account information approval can pertain to approval of the customer for the account to be activated. In one example, the account information would be presented to the customer for review and approval. A decision <b>826</b> determines whether the account information has been approved. When the decision <b>826</b> determines that the account information has not yet been approved, the activation process <b>800</b> can await such approval.

p-0101Once the decision <b>826</b> determines that the account information has been approved, the activation process <b>800</b> requests <b>828</b> approval of one or more service agreements. In one example, the one or more service agreements would be presented to the customer for review and acceptance. A decision <b>830</b> then determines whether the one or more service agreements had been approved. When the decision <b>830</b> determines that the one or more service agreements have not been approved, then the activation process <b>800</b> can await such approval. Once the decision <b>830</b> determines that the one or more service agreements have been approved, setup of a billing account can be requested <b>832</b>. A remote server associated with a service provider can receive and process the request to setup a billing account for the customer. The setup of the billing account can utilize the customer information and/or the billing information that has been previously obtained by the activation process <b>800</b>. Billing accounts can be setup in this manner for one or more service providers.

p-0102Additionally, the activation process <b>800</b> can request activation of an account. In other words, the activation being requested <b>834</b> can correspond to an account activation process. The account activation can be perform by a remote server, e.g., activation server, associated with a service provider. Following the request <b>834</b> for activation of an account, a decision <b>836</b> can determines whether the account has been activated. When the decision <b>836</b> determines that the account has not yet been activated, a decision <b>838</b> can determine whether the account activation has failed. When the decision <b>838</b> determines that the account activation has not failed, the activation process <b>800</b> can return to repeat the decision <b>836</b>. Alternatively, when the decision <b>838</b> determines that the account information has failed, the customer can be informed <b>840</b> of unsuccessful activation. Following the block <b>840</b>, the activation process <b>800</b> ends.

p-0103On the other hand, when the decision <b>836</b> determines that the account associated with the customer has been activated, the customer can be informed <b>842</b> of the successful activation. Thereafter, the mobile multi-function device can be activated <b>844</b>. The activation <b>844</b> of the mobile multi-function device can, for example, be processing described above with reference to <figref idrefs="DRAWINGS">FIGS. 6C</figref> or <b>6</b>D.

p-0104<figref idrefs="DRAWINGS">FIG. 9</figref> is a flow diagram of an activation process <b>900</b> according to another embodiment of the invention. The activation process <b>900</b> is, for example, processing associated with activating a mobile multi-function device for use on a family plan.

p-0105The activation process <b>900</b> can begin with a decision <b>902</b> that determines whether the mobile multi-function device is to be activated as a family plan. When the decision <b>902</b> determines that the mobile multi-function device is not to be activated as a family plan then the mobile multi-function device can alternatively be activated <b>904</b> on an individual plan basis. When the decision <b>902</b> determines that the mobile multi-function device is to be activated as a family plan, an activation process <b>906</b> can be carried out for a family plan. The activation process for a family plan is generally similar to the processing illustrated in <figref idrefs="DRAWINGS">FIGS. 8A-8C</figref>; however, the account being established is a family account not an individual account and also the service plans normally differ because they pertain to family plans. Following the blocks <b>904</b> and <b>906</b>, the activation process <b>900</b> for a family plan is complete.

p-0106<figref idrefs="DRAWINGS">FIG. 10</figref> is a flow diagram of an activation process <b>1000</b> according to another embodiment of the invention. The activation process <b>1000</b> is, for example, processing associated with activation of a new mobile multi-function device by an existing customer of the service provider.

p-0107The activation process <b>1000</b> can request <b>1002</b> current account information. Typically, the current account information would be requested <b>1002</b> from a customer attempting to activate a mobile multi-function device. A decision <b>1004</b> then determines whether the current account information has been received. In one embodiment, the current account information is received from the customer through interaction with a graphical user interface. The current account information is requested so that the customer's current account can be identified. When the decision <b>1004</b> determines that the current account information has not been received, the activation process <b>1000</b> can await the current account information.

p-0108Once the decision <b>1004</b> determines that the current account information has been received, a decision <b>1006</b> determines whether the user is authenticated. The authentication of the customer (user) can be achieved in a variety of different ways, including use of a user name, password, and/or a security question, etc. Hence, authenticating the user typically requires user data entry. When the decision <b>1006</b> determines that the customer (user) is authorized with respect to the current account, a subscriber status for the current account can be checked <b>1008</b>. A decision <b>1010</b> can then determine whether the account for the subscriber is active. When the decision <b>1010</b> determines that the account for the subscriber is active, then processing associated with blocks <b>814</b>-<b>844</b> are the activation process <b>800</b> illustrated in <figref idrefs="DRAWINGS">FIG. 8A-8C</figref> can be performed <b>1012</b> to activate an account (new or update to existing account) and also activate the mobile multi-function device. On the other hand, when the decision <b>1006</b> determines that the user is not authenticated or when the decision <b>1010</b> determines that the account is not active, an error indication can be presented <b>1014</b>. As an example, the error indication can be presented <b>1014</b> by a graphical user interface that informs the customer that activation is not available. Following the block <b>1012</b> or the block <b>1014</b>, the activation process <b>1000</b> can end.

p-0109<figref idrefs="DRAWINGS">FIG. 11</figref> is a flow diagram of an activation process <b>1100</b> according to another embodiment of the invention. The activation process <b>1100</b> is concerned with adding an additional line to an existing account with a network service provider.

p-0110The activation process <b>1000</b> can request <b>1102</b> current account information. Typically, the current account information would be requested <b>1102</b> from a customer attempting to activate a mobile multi-function device. A decision <b>1104</b> determines whether the current account information associated with the customer has been received. In one embodiment, the current account information is received from the customer through interaction with a graphical user interface. When the decision <b>1104</b> determines that the current account information has not been received, the activation process <b>1100</b> can await the current account information. Alternatively, when the decision <b>1104</b> determines that the current account information has been received, a decision <b>1106</b> can determine whether the customer (user) is authorized to access the client account (or its information). When the decision <b>1106</b> determines that the customer (user) is authenticated and able to access the account, a subscriber status for the account is checked <b>1108</b>. A decision <b>1110</b> can then determine whether the account associated with the subscriber (customer) is active. When the decision <b>1110</b> determines that the account associated with the subscriber is inactive (i.e., not active), an error indication can be presented <b>1112</b>. In the event that the account associated with the subscriber is inactive, the error indication being presented <b>1112</b> can inform the customer that they are unable to add a new line to an existing account because the account is inactive.

p-0111On the other hand, when the decision <b>1110</b> determines that the account associated with the subscriber is active, the activation process <b>1100</b> can determine <b>1114</b> whether an additional line is available to the subscriber. In one embodiment, a subscriber can be allocated up to a determined of number lines for which they may activate. The number of lines available to the subscriber can be determined based on the subscriber's credit history, service plan, anticipated or actual use, etc. When the decision <b>1116</b> determines that an additional line is not available to the subscriber, then the subscriber can be informed <b>1118</b> that the additional line is not available. In one implementation, such as illustrated in <figref idrefs="DRAWINGS">FIG. 11</figref>, when an additional line can still be available if the subscriber provides a deposit (e.g., security deposit), the subscriber can be so informed <b>1118</b>. Alternatively, when the decision <b>1116</b> determines that the additional line is available, the activation process <b>1100</b> can perform various previously described operations to activate the mobile multi-function device at block <b>1120</b>. In one embodiment, the activation operations are associated with blocks <b>802</b>, <b>804</b> and <b>810</b>-<b>844</b> of the activation process <b>800</b> illustrated in <figref idrefs="DRAWINGS">FIGS. 8A-8C</figref>. Following the blocks <b>1112</b>, <b>1118</b> and <b>1120</b>, the activation process <b>1100</b> can end.

p-0112Another aspect of the invention pertains to online provisioning methods and graphical user interfaces therefore. The provisioning methods enable an end user to activate a mobile communication device (e.g., mobile phone). In one embodiment, an end user can connect a mobile communication device to a computing device, such as a personal computer, and then perform an online activation process with a wireless service provider. The invention can provide automation and flexibility to activation of wireless communication devices.

p-0113<figref idrefs="DRAWINGS">FIGS. 12A-12C</figref> are flow diagrams of a mobile device provisioning process <b>1200</b> according to one embodiment of the invention. The mobile device provisioning process <b>1200</b> is, for example, performed by a server, such as the activation server <b>112</b> of the activation system <b>100</b> illustrated in <figref idrefs="DRAWINGS">FIG. 1</figref>.

p-0114The mobile device provisioning process <b>1200</b> can begin with a decision <b>1202</b>. The decision <b>1202</b> can determine whether a new mobile device needs to be provisioned (or activated). The new mobile device, for example, can refer to a mobile device that requires provisioning in order to utilize a wireless network for voice (and/or data) communications. The new mobile device can, for example, be recognized by a client machine, such as the client machine <b>102</b> illustrated in <figref idrefs="DRAWINGS">FIG. 1</figref>, when the mobile device connects with the client machine. The client machine can then in turn interact with the activation server to present suitable graphical user interfaces that assist the user of the mobile device in provisioning (or activating) the mobile device. Hence, when the decision <b>1202</b> determines that a new mobile device is not present, then the mobile device provisioning process <b>1200</b> awaits the presence of a new mobile device. In other words, until a new mobile device is present, the mobile device provisioning process <b>1200</b> simply waits to recognize a new mobile device. On the other hand, once the decision <b>1202</b> determines that a new mobile device has been recognized, an initial registration page is displayed <b>1204</b>. The initial registration page can provide initial information to a user regarding registration of a mobile device.

p-0115<figref idrefs="DRAWINGS">FIG. 13</figref> is a screen shot of an exemplary initial registration page <b>1300</b> according to one embodiment of the invention. The initial registration page <b>1300</b> illustrated in <figref idrefs="DRAWINGS">FIG. 13</figref> provides initial registration information regarding a device entitled “Debbie's iphone” which in this example pertains to a mobile phone. In one embodiment, the mobile phone is a multi-function device. After the initial registration page is displayed <b>1204</b>, a decision <b>1206</b> can determine whether a user continues with the mobile device provisioning process <b>1200</b>. When the decision <b>1206</b> determines that the user has not yet elected to continue, the mobile device provisioning process <b>1200</b> can await such a request. Alternatively, the user could instead request to cancel the mobile device provisioning process <b>1200</b>, in which case the mobile device provisioning process <b>1200</b> could end.

p-0116On the other hand, when the decision <b>1206</b> determines that the user has requested to continue with the mobile device provisioning process <b>1200</b>, a customer status page can be displayed <b>1208</b>. In general, the customer status page can allow a customer (user) to specify whether or not they are an existing customer to the wireless network provider, in this example, AT&amp;T Wireless. Additionally, the customer status page may enable the customer to specify whether they are activating on an individual plan or a group plan, or whether they wish to keep their current phone number (i.e., transferring the phone number) or create a new phone number.

p-0117<figref idrefs="DRAWINGS">FIG. 14</figref> is a screen shot of an exemplary customer status page <b>1400</b> according to one embodiment of the invention. The customer status page <b>1400</b> allows a new wireless network service customer to activate a new phone on an individual plan. Here, the customer may or may not desire to transfer their current mobile phone number. Further, the customer status page <b>1400</b> can allow an existing wireless network service customer to either keep their current phone number or create a new phone number for the particular mobile device being provisioned.

p-0118After the customer status page is displayed <b>1208</b>, a decision <b>1210</b> determines whether the customer is a new customer. As an example, this determination can be made following submission of the customer status page <b>1400</b> which enables the user to indicate whether or not they are an existing customer.

p-0119Although not illustrated in <figref idrefs="DRAWINGS">FIGS. 12A-12C</figref>, the mobile device provisioning process <b>1200</b> can further display a number transfer page. The number transfer page can assist a user in transferring an existing number from another service provider to be used with the particular mobile device being provisioned.

p-0120<figref idrefs="DRAWINGS">FIG. 15</figref> is a screen shot of an exemplary screen shot of a mobile number transfer page <b>1500</b>. The mobile number transfer page <b>1500</b> includes a data entry region <b>1502</b> that enables a user to provide existing account information in the case where an existing mobile number is to be transferred. <figref idrefs="DRAWINGS">FIG. 16</figref> is a screen shot of an exemplary screen shot of a landline number transfer page <b>1600</b>. The landline number transfer page <b>1600</b> includes a data entry region <b>1602</b> that enables a user to provide existing account information in the case where an existing landline number is to be transferred.

p-0121When the decision <b>1210</b> determines that the user is a new customer, a service plan selection page can be displayed <b>1212</b>. In general, the service plan selection page provides one or more available service plans to the customer. A customer can then select one of the available service plans.

p-0122<figref idrefs="DRAWINGS">FIGS. 17A and 17B</figref> are screen shots of an exemplary service plan selection page <b>1700</b> according to one embodiment of the invention. The service plan selection page <b>1000</b> allows the customer to select from one of six service plans <b>1702</b>-<b>1712</b>, each of which can offer a different package of services at different rates. A first three of the service plans are illustrated in <figref idrefs="DRAWINGS">FIG. 17A</figref>, and a second three of the service plans are illustrated in <figref idrefs="DRAWINGS">FIG. 17B</figref>.

p-0123Following the display <b>1212</b> of the service plan selection page, a decision <b>1214</b> can determine whether a service plan has been selected. When the decision <b>1214</b> determines that a service plan has not yet been selected, the mobile device provisioning process <b>1200</b> can await such a selection. On the other hand, once the decision <b>1214</b> determines that a service plan has been selected, as well as following the decision <b>1210</b> when the customer is not a new customer, a customer account page can be displayed <b>1216</b>. The customer account page can allow an existing customer to login to their account. The account is, for example, associated with an on-line media store, such as the iTunes® media store.

p-0124<figref idrefs="DRAWINGS">FIG. 18</figref> is a screen shot of an exemplary customer account page <b>1100</b> according to one embodiment of the invention. The customer account page <b>1100</b> includes a sign-in section <b>1802</b> that allows an existing account holder to sign-in, with an identifier (e.g., Apple ID) and password.

p-0125After the customer account page has been displayed <b>1216</b>, a decision <b>1218</b> can determine whether the customer is an existing account holder. When the decision <b>1218</b> determines that the customer has an existing account, the customer can login <b>1220</b> to the account. Alternatively, when the decision <b>1218</b> determines that the customer does not have an existing account, or following the block <b>1220</b> after a successful login to an account, a customer information entry page is displayed <b>1222</b>. The customer information entry page can facilitate a user in entering customer information that is to be utilized by either the wireless network service provider or the media asset provider (e.g., on-line media store). For a customer with an existing account, the customer information can be pre-entered and/or the certain subsequent portions of the remaining processing for the mobile device provisioning process <b>1200</b> could be simplified or eliminated. For a customer without an existing account with the on-line media store, the customer information entry page can also allow the customer to create a new account with the on-line media store.

p-0126<figref idrefs="DRAWINGS">FIG. 19</figref> is a screen shot of a customer information entry page <b>1900</b> according to one embodiment of the invention. The customer information entry page <b>1900</b> allows entry of basic customer information to be utilized in creating one or more accounts. The customer information can, for example, include information pertaining to the customer, such as e-mail address, password, security question and answer, and date of birth.

p-0127Once the customer has entered the requested customer information, the mobile device provisioning process <b>1200</b> can continue. A decision <b>1224</b> determines whether customer information has been received. When the decision <b>1224</b> determines that the customer information has been received, such as by completion of the customer information entry page, a billing information page can be displayed <b>1226</b>. The billing information page enables a customer to provide billing information to be utilized to pay for the service plan that was previously selected by the customer. The billing information can also be used by another service provider, such as an online media store. It should be noted that sharing of customer information and/or billing information between two or more service providers provides an efficient and user friendly system is provided.

p-0128<figref idrefs="DRAWINGS">FIG. 20</figref> illustrates an exemplary billing information page <b>2000</b> according to one embodiment of the invention. The billing information page <b>2000</b> provides a means for the customer to enter various billing information, such as name, billing address, phone number, social security number, credit card number, security code, and expiration date. The billing information can be used by one or more service providers, in this example, AT&amp;T Wireless as the wireless service provider and iTunes® media store as an online media service provider.

p-0129After the billing information page is displayed <b>1226</b>, a decision <b>1228</b> determines whether billing information has been received. When the decision <b>1228</b> determines that billing information has not been received, then the mobile device provisioning process <b>1200</b> awaits such billing information. On the other hand, when the decision <b>1228</b> determines that billing information has been received, a terms and condition page can be displayed <b>1230</b>. The terms and conditions page can provide the customer with the terms and conditions of the one or more legal agreements that are being established with the customer.

p-0130<figref idrefs="DRAWINGS">FIG. 21A</figref> is an exemplary screen shot of a first terms and conditions page <b>2100</b> according to one embodiment of the invention. In this example, the customer is required to read and agree to a software license/usage agreement <b>2102</b> with respect to Apple Computer, Inc. for use of the iTunes® media store. <figref idrefs="DRAWINGS">FIG. 21B</figref> is an exemplary screen shot of a second terms and conditions page <b>2150</b> according to one embodiment of the invention. In this example, the customer is required to read and agree to a wireless service agreement <b>2502</b> with a wireless service provider. The terms and conditions pages <b>2100</b> and <b>2150</b> require that the user accept the respective terms and conditions of these agreements in order to continue.

p-0131Following the display <b>1230</b> of the terms and conditions page, a decision <b>1232</b> determines whether the customer has accepted the various terms and conditions. When the decision <b>1232</b> determines that the customer has not accepted the terms and conditions, then the mobile device provisioning process <b>1200</b> awaits such acceptance. Once the decision <b>1232</b> determines that the customer has accepted the various terms and conditions, a review information page can be displayed <b>1234</b>. The review information page allows a user to finally review the information regarding the service plan (i.e., wireless network service) being established for the mobile device for the customer information, and the associated billing information.

p-0132<figref idrefs="DRAWINGS">FIG. 22</figref> is a screen shot of an exemplary review information page <b>2200</b> according to one embodiment of the invention. The review information page <b>2200</b> summarizes the billing and plan information concerning the mobile device being activated. For example, as shown in <figref idrefs="DRAWINGS">FIG. 22</figref>, the review information page <b>2200</b> can specify the billing amount and the manner in which the customer is to be billed, a service plan and a brief description thereof, additional fees and explanation of additional costs.

p-0133After the review information page has been displayed, a decision <b>1236</b> can determine whether the mobile device provisioning process <b>1200</b> should continue. When the decision <b>1236</b> determines that the customer has decided to continue the mobile device provisioning process <b>1200</b>, one or more setup completion pages can be displayed <b>1238</b>. The one or more setup completion pages can inform the customer that the setup (or activation) of their mobile device is processing and/or has successfully completed. The setup completion page may also provide a phone number for the mobile device to the customer or indicate that the existing phone number is being transferred. The setup completion page may also permit the customer to provide a name for the mobile device.

p-0134<figref idrefs="DRAWINGS">FIG. 23</figref> is an exemplary screen shot of a setup completion page <b>2300</b> according to one embodiment of the invention. The setup completion page <b>2300</b> informs the customer that activation of the mobile device is being processed. <figref idrefs="DRAWINGS">FIG. 24A</figref> is an exemplary screen shot of a setup completion page <b>2400</b> according to another embodiment of the invention. The setup completion page <b>2400</b> provides the customer with a phone number <b>2402</b>. <figref idrefs="DRAWINGS">FIG. 24B</figref> is an exemplary screen shot of a setup completion page <b>2450</b> according to still another embodiment of the invention. The setup completion page <b>2450</b> informs the customer that transfer of the existing phone number is ongoing. In one embodiment, the setup completion page <b>2400</b> and the setup completion page <b>2450</b> are alternative pages that are chosen dependent on whether a new phone number is being assigned or whether an existing phone number is being transferred.

p-0135After the setup completion page has been displayed <b>1238</b>, a decision <b>1240</b> determines whether the customer desires to continue on with the mobile device provisioning process <b>1200</b>. When the decision <b>1240</b> determines that the customer has not yet decided to continue, the mobile device provisioning process <b>1200</b> awaits the request to continue. Once the decision <b>1240</b> determines that the customer has requested to continue, a device preference page is displayed <b>1242</b>. The device preference page can, for example, be provided by a media management application. In this regard, the media management application can assist the customer with the setting of one or more preferences concerning the mobile device that has just been provisioned (or activated). Alternatively, the customer can choose not to continue to the device preference page and instead end the mobile device provisioning process <b>1200</b>. In any case, following the block <b>1242</b> (or alternatively following the block <b>1238</b>), the mobile device provisioning process <b>1200</b> can end as the provisioning of the mobile device has been initiated and perhaps completed. Following the mobile device provisioning process <b>1200</b>, the mobile device can thereafter be controlled or managed by the media management application. To the extent that the customer has set one or more preferences concerning the mobile device, the media management application can thereafter operate in accordance with the one or more preferences when interacting with or on behalf of the mobile device.

p-0136<figref idrefs="DRAWINGS">FIG. 25</figref> is an exemplary screen shot of a device preference page <b>2500</b> according to one embodiment of the invention. The device preference page <b>2500</b> includes a source region <b>2501</b> and a preference information region <b>2502</b>. A visual selector <b>2503</b> indicates selection of a device referred to as “Debbie's iphone”. For this selected device, the preference information area <b>2502</b> displays information <b>2506</b> regarding preferences associated with the particular device. In this specific example, a summary tab <b>2504</b> is active so that a summary preference window is displayed in the preference information area <b>2502</b>. The summary preference window includes information describing the particular device, such as name, size, software version and serial number. The summary preference window also provides version information <b>2508</b> indicating whether or not an updated version of any software components might be available. Further, the summary preference window includes an options section <b>2510</b> that allows a customer to select one or more predetermined options regarding the mobile device. Device preferences can be set by a user for a plurality of different types of media. The device preferences can also be set differently for different types of media. The device preference page <b>2500</b> includes other tabs for distinct media types, including music, movies, TV shows, podcasts, photos, personal and games. These device preferences can be synchronization preferences used when synchronizing the media device with the client machine. For additional information on synchronization and synchronization preferences see (i) U.S. Provisional Patent Application No. 60/879,319, filed Jan. 7, 2007, and entitled “MULTI-DEVICE DATA SYNCHRONIZATION OR BACKUP VIA A HOST DEVICE,” which is hereby incorporated herein by reference; and (ii) U.S. patent application Ser. No. 11/679,082, filed Feb. 26, 2007, and entitled “DATA SYNCHRONIZATION WITH HOST DEVICE IN ACCORDANCE WITH SYNCHRONIZATION PREFERENCES,” which is hereby incorporated herein by reference.

p-0137As noted above, the provisioning method can also be used by existing customers. For example, an existing customer may get a new wireless communication device (e.g., mobile phone, multi-function device, etc.) that they want to use in place of their current wireless communication device. In one embodiment, the service plan (or rate plan) offered to the end user can have a predetermined minimum term (e.g., 2 years) or cancellation penalty duration. In one implementation, the user's new service plan will reset such minimum period(s) regardless of whether the user has already exceed the minimum period(s) for the user's existing plan.

p-0138<figref idrefs="DRAWINGS">FIG. 26</figref> is a screen shot of an exemplary customer status page <b>2600</b> according to one embodiment of the invention. The customer status page <b>2600</b> allows a new wireless network service customer to activate a new mobile phone (i.e., mobile device) on pre-existing account in place of an existing mobile phone, whereby the phone number for the new mobile phone is the same as the phone number previously used for the existing mobile phone. Since the customer is an existing customer, an account information page can also be displayed. The account information page can permit the user to enter account information concerning their account with the wireless service provider. The account information serves to identify the pre-existing account of the user. As such, an activation server can locate the user account and associate the new mobile phone with the pre-existing account. <figref idrefs="DRAWINGS">FIG. 27</figref> is a screen shot of an exemplary account information page <b>2700</b> according to one embodiment of the invention. The account information page <b>2700</b> includes an account information entry area <b>2702</b> allows a user to enter account information.

p-0139An existing customer can also use the computer-assisted provisioning process to add an additional line to an existing account. <figref idrefs="DRAWINGS">FIG. 28</figref> is a screen shot of an exemplary customer status page <b>2800</b> according to one embodiment of the invention. The customer status page <b>2800</b> allows an existing wireless network service customer to activate a new mobile phone on pre-existing account. Since the customer is an existing customer, an account information page can also be displayed. The account information page can permit the user to enter account information concerning their account with the wireless service provider. The account information serves to identify the pre-existing account of the user. As such, an activation server can locate the user account and associate the new mobile phone with the pre-existing account. <figref idrefs="DRAWINGS">FIG. 29</figref> is a screen shot of an exemplary account information page <b>2900</b> according to one embodiment of the invention. The account information page <b>2900</b> includes an account information entry area <b>2902</b> allows a user to enter account information. Still further, in this scenario the pre-existing account is assumed to be an individual account. Hence, in one embodiment, an account type selection page can be displayed. <figref idrefs="DRAWINGS">FIG. 30</figref> is a screen shot of an exemplary account type selection page <b>3000</b> according to one embodiment of the invention. The account type selection page <b>3000</b> allows the customer to choose to activate the new mobile phone on an individual plan or to instead convert to a family plan. Typically, with a family plan, the various mobile phones within the group can share service time (e.g., share plan minutes).

p-0140A new customer can also use the computer-assisted provisioning process to activate multiple mobile devices. <figref idrefs="DRAWINGS">FIG. 31</figref> is a screen shot of an exemplary customer status page <b>3100</b> according to one embodiment of the invention. The customer status page <b>3100</b> allows a new customer for wireless network service to activate one mobile phone or multiple mobile phones. In one embodiment, when two or more mobile phones are to be activated an account type selection page can be displayed to enable the customer to choose between individual plans or family plans. <figref idrefs="DRAWINGS">FIG. 32</figref> is a screen shot of an exemplary account type selection page <b>3200</b> according to one embodiment of the invention. The account type selection page <b>3200</b> allows the customer to choose to activate each of the multiple new mobile phones on individual plans or to instead activate all of the multiple new mobile phones on a family plan. Typically, with a family plan, the various mobile phones within the group can share service time (e.g., share plan minutes). In this example, the conversion to a family plan requires calling customer support; however, in other embodiments such can be part of the computer-assisted provisioning.

p-0141Mobile device provisioning can also enable remote provisioning of multiple wireless communication devices. For example, wireless service providers often refer to multiple devices on a primary account as a “family plan”. Activation of multiple devices for such a primary account can require additional operations. In one embodiment, a first mobile device is connected to the host computer, such as using a USB connection, and then for the subsequent one or more mobile device to be also activated for the primary account can be identified to the provisioning server by having an end-user manually enter an identifier that is provided with another mobile device. For example, the identifier can be provided on or within a package containing the another mobile device. Hence, in would be possible for an end-user to activate a mobile device without it being present.

p-0142In one embodiment, the activation process uses two identifiers, IMEI and ICCID, when activating a mobile device. However, neither of these identifiers have built-in error correct or validation. Hence, manual entry of these identifiers by end-users could lead to failed or improper activation. One embodiment to enhance activation in such situations is to provide end-users with a computed identifier that uniquely maps to the needed IMEI and ICCID identifiers. The computed identifier can be more compact (i.e., less digits) and thus easier for manual entry. Moreover, the computed identifier can include error correction to guard against improper entry of the computed identifier.

p-0143Mobile device provisioning can also restrict payment options to those consumers that have low credit scores. For example, a wireless service provider may not desire to activate a wireless service plan to those customers that have poor credit. Hence, in one embodiment, the wireless service provider can offer different payment options to different customers dependent on at least credit information (e.g., credit score). For example, customers with poor credit can be required to pay a deposit or to pre-pay for such service.

p-0144In some cases, a new customer can be limited to service plans that require prepayment. In one embodiment, the provisioning process can decide whether prepayment is required based on the credit history of the customer. The credit history can, for example, result from a credit report on the customer. <figref idrefs="DRAWINGS">FIG. 33</figref> is a screen shot of an exemplary prepayment requirement page <b>3300</b>. The exemplary prepayment requirement page <b>3300</b> can present the customer with one or more option on activating wireless service. The exemplary prepayment requirement page <b>3300</b> allows the customer to (i) provide a pre-approval credit check code and continue activation, (ii) agree to a prepaid plan (e.g., with advance monthly payment via credit or debit card) and continue activation, or (iii) restart/cancel the activation process.

p-0145As noted above, the provisioning method can also be used by existing customers. For example, an existing customer may get a new wireless communication device (e.g., mobile phone, multi-function device, etc.) that they want to use it in place of their current wireless communication device. In one embodiment, the service plan offered to the end user can have a predetermined minimum term (e.g., 2 years) or cancellation penalty duration. In one implementation, the user's new service plan will reset such minimum period regardless of whether the user has already exceed the minimum period for the user's existing plan.

p-0146<figref idrefs="DRAWINGS">FIG. 34</figref> is a block diagram of a mobile multi-function device <b>3400</b> according to one embodiment of the invention. The mobile multi-function device <b>3400</b> can include the circuitry of the mobile multi-function device <b>104</b> illustrated in <figref idrefs="DRAWINGS">FIG. 1</figref> and/or can perform the operations described with reference to <figref idrefs="DRAWINGS">FIGS. 3 and 4</figref>. The mobile multi-function device <b>3400</b> includes hardware and software components to provide at least two functions, namely, a media playback function and a wireless voice communications function. When providing media playback, the mobile multi-function device <b>3400</b> can operate as a media player capable of playing (including displaying) media items. The media items can, for example, pertain to audio items (e.g., audio files or songs), videos (e.g., movies) or images (e.g., photos). When providing wireless voice communications, the mobile multi-function device <b>3400</b> can operate a mobile telephone (e.g., cellular phone).

p-0147The mobile multi-function device <b>3400</b> includes a processor <b>3402</b> that pertains to a microprocessor or controller for controlling the overall operation of the mobile multi-function device <b>3400</b>. The mobile multi-function device <b>3400</b> stores media data pertaining to media items in a file system <b>3404</b> and a cache <b>3406</b>. In one embodiment, the file system <b>3404</b> is implemented by a storage disk or a plurality of disks. In another embodiment, the file system <b>3404</b> is implemented by EEPROM or Flash type memory. The file system <b>3404</b> typically provides high capacity storage capability for the mobile multi-function device <b>3400</b>. However, since the access time to the file system <b>3404</b> is relatively slow, the mobile multi-function device <b>3400</b> can also include a cache <b>3406</b>. The cache <b>3406</b> is, for example, Random-Access Memory (RAM) provided by semiconductor memory. The relative access time to the cache <b>3406</b> is substantially shorter than for the file system <b>3404</b>. However, the cache <b>3406</b> does not have the large storage capacity of the file system <b>3404</b>. Further, the file system <b>3404</b>, when active, consumes more power than does the cache <b>3406</b>. The power consumption is often a concern when the mobile multi-function device <b>3400</b> is a portable mobile multi-function device that is powered by a battery <b>3424</b>. The mobile multi-function device <b>3400</b> also includes a RAM <b>3420</b> and a Read-Only Memory (ROM) <b>3422</b>. The ROM <b>3422</b> can store programs, utilities or processes to be executed in a non-volatile manner. The ROM <b>3422</b> can be implemented by an EEPROM or Flash type memory so as to provide writable non-volatile data storage. The RAM <b>3420</b> provides volatile data storage, such as for the cache <b>3406</b>.

p-0148In one embodiment, to support wireless voice communications, the mobile multi-function device <b>3400</b> includes a transceiver <b>3426</b> and a SIM card <b>3428</b>. The transceiver <b>3426</b> supports wireless communication with a wireless network (such as a wireless cellular network). The SIM card <b>3428</b> includes an identifier (e.g., SIM identifier) can be used by the mobile multi-function device <b>3400</b> to gain access and utilize the wireless network. In other embodiments, a SIM card <b>3428</b> is not utilized.

p-0149The mobile multi-function device <b>3400</b> also includes a user input device <b>3408</b> that allows a user of the mobile multi-function device <b>3400</b> to interact with the mobile multi-function device <b>3400</b>. For example, the user input device <b>3408</b> can take a variety of forms, such as a button, keypad, dial, etc. Still further, the mobile multi-function device <b>3400</b> includes a display <b>3410</b> (screen display) that can be controlled by the processor <b>3402</b> to display information to the user. A data bus <b>3411</b> can facilitate data transfer between at least the file system <b>3404</b>, the cache <b>3406</b>, the processor <b>3402</b>, and the CODEC <b>3412</b>.

p-0150In one embodiment, the mobile multi-function device <b>3400</b> serves to store a plurality of media items (e.g., songs) in the file system <b>3404</b>. When a user desires to have the mobile multi-function device play a particular media item, a list of available media items is displayed on the display <b>3410</b>. Then, using the user input device <b>3408</b>, a user can select one of the available media items. The processor <b>3402</b>, upon receiving a selection of a particular media item, supplies the media data (e.g., audio file) for the particular media item to a coder/decoder (CODEC) <b>3412</b>. The CODEC <b>3412</b> then produces analog output signals for a speaker <b>3414</b>. The speaker <b>3414</b> can be a speaker internal to the mobile multi-function device <b>3400</b> or external to the mobile multi-function device <b>3400</b>. For example, headphones or earphones that connect to the mobile multi-function device <b>3400</b> would be considered an external speaker.

p-0151The mobile multi-function device <b>3400</b> also includes a bus interface <b>3416</b> that couples to a data link <b>3418</b>. The data link <b>3418</b> allows the mobile multi-function device <b>3400</b> to couple to a host device (e.g., host computer or power source). The data link <b>3418</b> can also provide power to the mobile multi-function device <b>3400</b>.

p-0152The various aspects, embodiments, implementations or features of the invention can be used separately or in any combination.

p-0153The invention can be implemented by software, hardware or a combination of hardware and software. The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data which can thereafter be read by a computing device (e.g., computer system). Examples of the computer readable medium include read-only memory, random-access memory, CD-ROMs, DVDs, magnetic tape, and optical data storage devices. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

p-0154The advantages of the invention are numerous. Different aspects, embodiments or implementations may, but need not, yield one or more of the following advantages. One advantage of the invention is that mobile devices can be setup or activated to operate on wireless networks by end users. Another advantage of the invention is that setup or activation can be substantially automated and controlled by a computer-implemented system to facilitate setup or activation with a service provider (e.g., wireless service provider). Another advantage of the invention is that graphical user interfaces can be presented to users so as to enable end users to easily activate mobile devices. Still another advantage of the invention is that more than one account for different service providers can be concurrently arranged in an efficient and user friendly manner. Yet still another advantage of the invention is that mobile devices can be largely disabled until properly activated with a service provider.

p-0155The many features and advantages of the present invention are apparent from the written description. Further, since numerous modifications and changes will readily occur to those skilled in the art, the invention should not be limited to the exact construction and operation as illustrated and described. Hence, all suitable modifications and equivalents may be resorted to as falling within the scope of the invention.