JP6443452B2 - Distribution of branding content and customized information to mobile communication devices - Google Patents

Description

  Mobile communication devices can be purchased at service provider retail stores, consumer electronics retailers, and / or general retail stores. Various activities can be performed to provide services to a new mobile phone. To use a mobile communication device in a cellular network, a mobile phone can first be provisioned. Provisioning a mobile communication device (eg, a mobile phone) to operate in a wireless network involves defining and / or adjusting the settings of the mobile communication device stored in the device and the settings stored in the network, Allows the mobile communication device to properly access communication services and / or execute one or more desired applications, and the network allows the mobile communication device to receive services for those applications Can be recognized as authorized.

  For example, mobile phones can be provisioned for simple voice services, voice and data services, special corporate data services, Internet access, email, voice mail, GP related services, location monitoring, and the like. Provisioning can also include a preferred roaming list, user zone list, language settings, browser settings, display settings, operating system version, security settings, access restrictions, geographic settings, and the like. Mobile communication devices and cellular networks may jointly provide access to these services.

  In one embodiment, a method for provisioning a mobile device is disclosed. The method wirelessly distributes a provisioning payload to a mobile device, the payload having one or more file locators, and the mobile device is preloaded in a system memory partition of the mobile device. A mobile device carrier having a customized content item, accessing at least a portion of the preloaded customized content based on the file locator, and a copy of the preloaded customized content referenced by the file locator Storing in a memory partition and completing customization process for a mobile device using customized content stored in a carrier memory partition; Provided.

  In one embodiment, a method for customizing a mobile device is disclosed. The method wirelessly receives a provisioning payload at a mobile device, the payload having a string of one or more uniform resource identifiers and preloaded based on the uniform resource identifier strings. Accessing the customized content, wherein the string of uniform resource identifiers is stored in the system memory partition, pointing to at least a portion of the preloaded customized content stored in the system memory partition of the mobile device; Using the customized content to complete a customization process for the mobile device.

  In one embodiment, a method for customizing a mobile device is disclosed. The method wirelessly receives a provisioning payload at a mobile device, the payload having customized content and one or more file locators, and accessing additional customized content based on the file locator. Storing customized content in a system memory partition on the mobile device and using the customized content to complete a customization process for the mobile device.

  In one embodiment, a method for provisioning a mobile device is disclosed. The method wirelessly receives a provisioning payload at a mobile device, the payload having one or more file locators, and accessing a remotely hosted location based on the file locators; Downloading customized content from a remotely hosted location to the mobile device and using the downloaded customized content to complete a customization process for the mobile device.

  In one embodiment, a method for customizing a mobile device is disclosed. The method wirelessly receives a provisioning payload at a mobile device, the payload comprising customized content and a string of one or more uniform resource locators, inspecting the provisioning payload, a uniform resource locator, Accessing a remotely hosted location based on the string of the user and downloading additional customized content from the remotely hosted location to the carrier memory partition of the mobile device, the carrier memory partition comprising: The mobile device operating system where the mobile device operating system restricts write access based on one of the keys or passwords. Comprising a part of Li, and are used to store the branding information includes the steps, and completing stage customization process for mobile devices using customized content and.

  In one embodiment, a method for customizing a mobile device is disclosed. The method wirelessly receives a provisioning payload at a mobile device, the payload having a first file locator and a second file locator, and pre-loading based on the first file locator. Accessing the customized content, wherein the first file locator points to one or more pre-loaded customized content items on the mobile device and based on the second file locator, the remote Accessing customized hosted locations, downloading customized content from a remotely hosted location to a mobile device, preloaded customized content and downloaded customized content Use tools, and a completing step customization process for the mobile device.

  These and other features will be more clearly understood from the following detailed description considered in conjunction with the accompanying drawings and claims.

  For a more complete understanding of the present disclosure, reference will now be made to the accompanying drawings and the following brief description that is considered in connection with the detailed description. Like reference numbers represent like parts.

1 is an example of a communication system according to an embodiment of the present disclosure.

6 is a flowchart illustrating a method according to an embodiment of the present disclosure.

5 is a flowchart illustrating another method according to an embodiment of the present disclosure.

6 is a flowchart illustrating a method according to an embodiment of the present disclosure.

5 is a flowchart illustrating another method according to an embodiment of the present disclosure.

1 is an example of a mobile communication device according to an embodiment of the present disclosure.

1 is a block diagram of a mobile communication device according to an embodiment of the present disclosure. FIG.

2 is a block diagram of a software architecture of a mobile communication device according to an embodiment of the present disclosure. FIG.

FIG. 6 is a block diagram of another software architecture of a mobile communication device according to an embodiment of the present disclosure.

1 illustrates an exemplary computer system suitable for implementing some embodiments of the present disclosure.

  Several exemplary implementations of one or more embodiments are set forth below, but the disclosed systems and methods use any number of techniques, whether currently known or not yet present. It should be understood first that it can be implemented. The present disclosure should in no way be limited to the exemplary implementations, drawings, and techniques set forth below, but within the scope of the appended claims and their equivalents. Can be changed.

  Embodiments of the present disclosure relate to a plurality of methods and systems for mobile device provisioning and / or customization. After the mobile device is purchased by the user, custom settings and information (or customized content) can be delivered to or accessed at the mobile device. The customized content may include multiple graphics, multiple images, multiple audio files, multiple splash screens, multiple startup screens, multiple backgrounds, and multiple tones. The customized content may also include multiple customer service numbers, multiple messaging platforms, multiple IP addresses and port numbers, client identification information, and multiple market catalogs. The customized content can be used to complete the provisioning and / or activation process on the mobile device. Here, the customized content may be installed, downloaded, and / or otherwise accessed during the provisioning process. In some cases, the provisioning and / or activation process may be completed by an application on the mobile device, such as a provisioning application, an activation application, and / or a customization client. In some cases, the provisioning process may be initiated when the provisioning payload is delivered to the mobile device. The provisioning payload may comprise a plurality of instructions for completing the provisioning process. The launch process instructs the user to perform various launch phases, such as entering user preferences, migrating contacts from another mobile device, installing multiple third party applications on the mobile device, etc. You can prepare for that. If provisioning is thought to focus on setting up mobile devices and wireless service provider networks to facilitate basic communication services for mobile devices, the activation process may be performed after provisioning is complete. Alternatively, the provisioning process may be considered to further comprise the stages characterized above as part of the activation process.

  In some cases, the provisioning payload may include one or more file locators, and at least some of the customized content may be accessed by referring to the file locators. Accessing customized content through a file locator can reduce the amount of content included in the provisioning payload, and thus the size of the provisioning payload. In addition, the provisioning payload transfer time may be reduced. In some cases, some of the customized content may be delivered to the mobile device in a provisioning payload. Here, the part delivered with the payload may have a small file or data.

  In some cases, at least a portion of the customized content may be preloaded on the device. The file locator delivered in the provisioning payload may reference or identify pre-loaded customized content. In some cases, the file locator may comprise a string of uniform resource identifiers (ie, URIs), and the provisioning application may access pre-loaded customized content based on the URI string. In some cases, the URI string may only point to a portion of the preloaded customization content. Here, the pre-loaded content may include multiple sets of customized content, and each set of customized content may be associated with a different wireless service brand.

  In some cases, the file locator may comprise a string of uniform resource locators (ie URLs), and the provisioning application may access customized content from a remotely hosted location based on the URL string. The customized content can be downloaded from a remotely hosted location to the mobile device and then used to complete the provisioning process. In some cases, some of the customization content can be obtained from preloaded content, some of the customization content can be downloaded from a remotely hosted location, or some of the customization content can be in the provisioning payload It can be delivered or any combination of the above.

  In some cases, mobile devices are suitable to be provisioned for use under multiple different brands. Each of those different brands may be characterized by different brand specific content and / or customized content. For example, the brand content associated with each brand may comprise multiple sets of content, at least some of which vary from brand to brand. For example, a first brand may be associated with a first background theme, a first power-on splash screen, a provisioned first customer care number, and a provisioned first voice mail number, The second brand may be associated with a second background theme, a second power-on splash screen, a provisioned second customer care number, and a provisioned second voice mail number. This is a simple example. In certain cases, a set of branded content may be more extensive.

  Further, the device may access multiple sets of customized content based on the URL. The sets of content are associated with a plurality of different brands. In some cases, the mobile device may be able to be associated with the second brand after the initial provisioning process is complete. For example, a user may wish to use the same device with different brands, carriers, or services. Alternatively, the device may be restored and reset. In this case, the mobile device may complete the second provisioning process, and the customized content accessed during the second provisioning process is different (or to a different brand) than the content accessed during the first provisioning process. Associated). In other words, the device may have multiple branding options (such as access to multiple sets of customized content), the first branding option may be selected in the first provisioning process, and then in the second provisioning process A second branding option is selected, and so on.

  The ability to easily and easily change the brand of a mobile communication device can drive various desirable business goals. For example, bulk orders for a single model of a handset can be priced by an original equipment manufacturer at a volume discount, after which those models can be branded into three or more different brands. If those handsets were branded by an original equipment manufacturer, they would probably be treated as three different products, priced based on the purchase quantity of each different product, and at least some of the volume discounts could be lost There would have been sex. Further, multiple devices may be rebranded at various stages of the mobile device life cycle. For example, the user may return the phone as having a problem that is repaired during the warranty period. The repair center may ship different physical devices to the user and repair the failed phone. After repair of the failed phone, the phone can be rebranded to a different brand--for example, a brand that is currently experiencing increased customer demand-and provided to the distribution center for resale. The multiple innovations and methods of the present disclosure contribute to the ease and functionality of performing such branding, rebranding and customization activities.

  The mobile communication device may have memory established as a system memory partition and a user memory partition. The operating system of the mobile communication device may restrict write access to the system memory partition so that the contents of the system memory partition are erased during multiple reset operations, for example reset to factory defaults Can prevent. For example, a user may be prevented from writing to a system memory partition and / or causing a write to a system memory partition. On the other hand, the operating system of the mobile communication device may allow unrestricted write access to the user memory partition. For example, a user of a mobile communication device exercises user interface control choices, for example by entering personal contacts, installing third party applications, downloading ring tones, etc. at least indirectly by a user memory partition May be allowed by the operating system to write information into the. During reset, for example, during factory reset, information in the user memory partition may be deleted by the operating system. The ANDROID® operating system used by some mobile communication devices may establish a system memory partition and a user memory partition.

  The operating system may further provide write access to the carrier memory partition for multiple privileged users or multiple automated processes. For example, an individual providing a carrier memory partition key or password, eg, an employee or contractor associated with a wireless communication service provider, may be allowed to write to the carrier memory partition by the operating system. Alternatively, the instructions executed on the mobile communication device may be granted privileges for writing to the carrier memory partition by the operating system based on the instructions providing a key or password. In one embodiment, the key or password is unavailable and unknown to the user of the mobile communication device, for example, the key or password may be known only to the wireless service provider and / or carrier. In one embodiment, the plurality of instructions may invoke an application programming interface (API) provided by the operating system to write to the carrier memory partition, where the API call is a key or password associated with the carrier memory partition. You may need to provide In some contexts this may be referred to as a carrier memory partition key or carrier memory partition password. An automated procedure or function performed on the mobile communication device that presents the carrier memory partition key or password, eg, a script that is transmitted wirelessly to the mobile communication device, may be allowed to write to the carrier memory partition. The carrier memory partition can be used to store branding information. The carrier memory partition may also be used to store other information unrelated to branding and / or customized content. For more details on the carrier memory partition, see Brandon C. et al. See US patent application Ser. No. 13 / 763,428, filed Feb. 8, 2013, by Annan et al., Entitled “System and Method of Storage Service Brand Packages On a Mobile Device”. The patent application is hereby incorporated by reference in its entirety.

  Referring now to FIG. 1, a communication system 100 is described. In one embodiment, the communication system 100 comprises a mobile device 102 having a cellular radio transceiver 120, a plurality of communication applications 108, and an optional user interface 118. Mobile device 102 may be involved in various communication exchanges. Mobile device 102 may have a variety of devices such as mobile phones, personal digital assistants (PDAs), media players, laptop computers, tablet computers, and other electronic devices including macro cellular radio transceivers.

  In one embodiment, the system 100 includes a network 131. The network 131 can be a private network, a public network, or a combination thereof. Network 131 may facilitate voice and data communications. Multiple portions of the network 131 may provide an IP Multimedia Subsystem (IMS) network. The mobile device 102 can be coupled to the network 131 by various communication paths. The mobile device 102 includes, but is not limited to, code division multiple access (CDMA), long term evolution (LTE), global interoperability for microwave access (WiMAX), pan-European digital mobile communication system (GSM ( (Registered trademark)), or other wireless communication protocols, and may communicate with a base station (BTS) 132 via a wireless link according to any of a variety of wireless communication protocols. In some embodiments, the mobile device 102 may communicate with a base station (BTS) 132 via the mobile device's 102 cellular radio transceiver 120. A wireless link between mobile device 102 and base station 132 may couple mobile device 102 to network 131. Further, the base station 132 may also be known as a cell tower. In some embodiments, the network 131 may provide communication between the mobile device 102 and the network server 134. Network server 134 may also communicate with network database 136.

  It will be appreciated that the system 100 may comprise any number of mobile devices 102 and any number of base stations 132. A collection of base stations 132 may be said to include a radio access network in that these base stations 132 may provide a wireless communication link to the mobile device 102 to provide access to the network 131. The radio access network may be abstracted in various ways and in addition to the base station 132, multiple home location registers (HLR) or multiple home location register functions, multiple server locations, multiple visitor locations Multiple servers and data stores, such as multiple servers that implement register (VLR) or multiple visitor location register functions, base station controller (BSC), mobile switching center (MSC), and especially mobile device 102 It may include other network nodes associated with providing wireless access and connectivity.

  The plurality of communication applications 108 include voice communication applications, data communication applications, web browser applications, email applications, short message system (SMS) or text messaging applications, multimedia message system (MMS) applications, and other Multiple communication applications may be included. The plurality of communication applications 108 may be a plurality of standard communication applications distributed by an original equipment manufacturer (OEM) that assembles the mobile communication device 102. The plurality of communication applications 108 may be stored as firmware or software in the trusted memory area of the mobile communication device 102. The plurality of communication applications 108 may expose a plurality of application programming interfaces (APIs) accessible to a plurality of other applications to provide wireless communication functions to the plurality of other applications.

  The plurality of communication applications 108 can be any of a variety of applications. One of the plurality of communication applications 108 receives a plurality of dialed digits and attempts to place a voice call—for example, a voice over IP (VoIP) call—to a called phone. Can be a phone application to try. One of the plurality of communication applications 108 may be a web browser application that requests content from the network 131, for example, by sending a hypertext transfer protocol (HTTP) message that embeds a universal reference locator (URL). One of the plurality of communication applications 108 may be a media player that requests streaming or downloading of media from the network 131. Many of the plurality of communication applications 108 may rely on communication services provided by the IMS network to deliver their functionality to the end user of the mobile device 102. One of the plurality of communication applications 108 may include a mobile transaction interface. The user can complete the purchase using the application, and secure information such as credit card information can be communicated through the application. In some embodiments, multiple communication applications 108 may be stored in the system memory partition 104 of the memory of the mobile device 102.

  The user interface 118 of the mobile device 102 may include a display, input system, speaker system, and / or microphone in some embodiments. In some embodiments, the display can include a screen and the input system can include, for example, a keypad and / or a touch screen. The speaker system may communicate audio (such as media, messages, ring tones, or telephone audio) to a user of the mobile device 102. The microphone may receive voice and / or audio from the user and / or communicate audio to the user. In one embodiment, the user may use the user interface 118 to communicate with the mobile device 102 and may initiate execution of one or more of the plurality of communication applications 108, for example. In addition, the user may receive communications from the mobile device 102 via the user interface 118, for example, phone calls, text messages, messages, emails, contact information, caller ID, call history, Internet access, and the like. The user may further use a user interface 118 for viewing and / or listening to media such as music, movies, shows, videos, photos, games, and the like.

  In some embodiments, the mobile device 102 may include a memory system that is divided into one or more partitions. The plurality of partitions may include a system memory partition 104, a carrier memory partition 106, and a user memory partition 105. In some embodiments, content may be stored and / or executed in one or more partitions. In some embodiments, the content stored in the memory of the mobile device 102 may be associated with the device manufacturer or may be content pre-loaded on the device. In some embodiments, the term “preloaded” may describe content that is loaded onto the device 102 before the device 102 is activated by the user. In some embodiments, multiple communication applications 108 may be stored in the system memory partition 104. Further, the customization client 114 (or provisioning application) can be stored and / or executed in the system memory partition 104. The customization client 114 may be operable to complete a customization or provisioning process for the mobile device 102. In some embodiments, one or more of the plurality of storage locations may include non-volatile or permanent memory.

  In some embodiments, preloaded content 112 may be downloaded to mobile device 102. The pre-loaded content 112 may include provisioning content or customized content. In some embodiments, the preloaded content 112 may be downloaded (or stored) to the system memory partition 104 of the mobile device 102. In some embodiments, preloaded content 112 may be used by mobile device 102 (or an application on mobile device 102) to complete a provisioning process or a customization process. In some embodiments, preloaded content 112 may have at least three sets of customized content. Each set of customized content is associated with a different wireless service brand. For example, each set of pre-loaded content 112 may include branding for a particular wireless service brand, such as a Sprint service brand, a Boost Mobile service brand, and / or a Virgin Mobile service brand. Customization information as well as settings may be included. In some embodiments, the preloaded content 112 may include at least a set of preloaded content 112 that includes general or mass sales branding and customization information. In some embodiments, when the mobile device 102 is branded by a mobile virtual network operator (MVNO), a common set of preloaded content 112 may be used. In some embodiments, the pre-loaded content 112 is one or more of multiple graphics, multiple images, multiple audio files, multiple splash screens, startup screens, multiple backgrounds, and multiple tones. Can be included.

  In some embodiments, the provisioning payload 113 is sent to the device 102 during initial setup of the device or during a subsequent setup procedure, such as when the device 102 is reset or returned to factory settings. Can be delivered. The provisioning payload 113 may include information and / or instructions for completing the provisioning process. In some embodiments, the provisioning payload 113 may be delivered according to an OMA DM (Open Mobile Alliance Device Management) protocol or framework. In other words, the provisioning payload 113 can be delivered as an OMA DM payload. In some embodiments, provisioning payload 113 may be stored in carrier memory partition 106 of mobile device 102. In some embodiments, at least a portion of the provisioning payload may be stored on a SIM (Subscriber Identity Module) card or an SD (Secure Digital) card on the mobile device. A SIM card or SD card may provide removable memory to the mobile device.

  Provisioning payload 113 may communicate with customization client 114. The customization client 114 may use the provisioning payload 113 data to complete the provisioning process. In some embodiments, the provisioning payload 113 may include one or more file locators that point to one or more of the plurality of preloaded content items 112. In some embodiments, the customization client 114 may access a portion of the preloaded content 112 based on the file locator. In some embodiments, the file locator may include a string of uniform resource identifiers (ie, URIs). In some embodiments, the file locator may point to only one of the multiple wireless service brands. Each set of preloaded content 112 may be associated with a different wireless service brand.

  In some embodiments, it may be desirable to store customized content outside the system memory partition 104, such as the carrier memory partition 106 and / or the user memory partition 105. In some embodiments, a pre-loaded copy of content 112 may be downloaded from system memory partition 104 to carrier memory partition 106. The content can be stored as customized content 110. In some embodiments, customized content 110 stored in the carrier memory partition 106 may persist if the mobile device 102 is returned to factory settings. In some embodiments, customized content 110 may be stored on a SIM card or SD card on the mobile device. In some embodiments, some or all of the unused content may be removed from the device 102 if there is unused preloaded content 112 on the device 102 after the provisioning process is complete. In other embodiments, preloaded content 112 may persist in system memory partition 104, whether or not it is accessed by customization client 114.

  In some embodiments, provisioning payload 113 may include customized content. The customized content is distributed together with the provisioning payload 113 in a wireless or wired manner. In some embodiments, the content delivered in provisioning payload 113 may be stored as customized content 110 in carrier memory partition 106. In other embodiments, the customized content delivered with the provisioning payload can be stored on a SIM card or SD card on the mobile device. In some embodiments, customized content 110 stored in the carrier memory partition 106 may persist if the mobile device 102 is returned to factory settings. In some embodiments, the customized content delivered in the provisioning payload 113 may include only a portion of the total content necessary to complete the provisioning process. For example, the provisioning payload 113 may include only a plurality of smaller files (eg, approximately 256 bytes or smaller) of the customized content 110, and the provisioning payload 113 may be preloaded content on the device 102. A file locator for remaining customization content 110, which may be 112, may also be included. In some embodiments, customized content 110 delivered with provisioning payload 113 may include one or more of customer service numbers, messaging platforms, IP addresses and port numbers, client identification information, and multiple market catalogs. .

  In some embodiments, the provisioning payload 113 may include one or more file locators. The at least one file locator can be a string of uniform resource locators (ie URLs). In some embodiments, the URL string may point to a remotely hosted location 140. Mobile device 102 may access remotely hosted location 140 wirelessly (or via network 131). During the provisioning process by the customization client 114, the device 102 may access the remotely hosted location 140 based on the file locator (or URL string). In some embodiments, the remotely hosted location 140 may provide customized content 110 that can be downloaded to the device 102 via the network 131. In some embodiments, the download of customized content 110 may be completed gradually. The content to be downloaded is prioritized and can be downloaded according to the priority. In other embodiments, customized content 110 may be downloaded all at once or in a single transaction. In some embodiments, the remotely hosted location 140 may be provided or hosted by a third party (separate from the service provider and / or manufacturer of the device 102). Branding content or customization content specific to the third party may be provided in the downloaded customization content 110.

  In some embodiments, provisioning payload 113 may include temporary customized content. In some embodiments, the temporary customized content may include one or more placeholders. Placeholders may be replaced during the provisioning process with customized content 110 pointed to by the file locator (as described above). The file locator can be a URI string that points to pre-loaded content 112, the file locator can be a URL string that points to a remotely hosted location 140, or the combination of URI string and URL string can be: Can be used to obtain customized content 110.

  In some embodiments, downloading customized content 110 from remotely hosted location 140 may be completed incrementally. For example, content to be downloaded to the device 102 can be prioritized according to the importance for completing the provisioning process, and if not all content can be downloaded simultaneously, the content can be downloaded according to the priority. For example, when the download is initiated, the device 102 may have a weak connection or roaming connection to the network 131, which may prevent a complete content download. In some embodiments, the downloading of content to the device 102 may be partially completed and then postponed until the device has a better connection with the network 131 before completion. In other embodiments, the download of customized content 110 may be postponed until a better connection is obtained. In some embodiments, placeholder content may be used on device 102 before the download is complete. Placeholder content can be already loaded on the device, delivered in the provisioning payload 113, or downloaded to the device 102. In some embodiments, the user may be charged or charged for data used to download provisioning payload 113 and / or customized content 110 from remotely hosted location 140.

  In some embodiments, all of the customized content 110 that is used to complete the provisioning process may be provided by preloaded content 112. In other embodiments, all of the customized content 110 used to complete the provisioning process can be downloaded from the remotely hosted location 140. In other embodiments, a portion of customized content 110 used to complete the provisioning process may be downloaded from a remotely hosted location 140 and another portion of the customized content may be provisioned payload 113 Together with the device 102. In other embodiments, a portion of customized content 110 used to complete the provisioning process may be provided by pre-loaded content 112, and another portion of the customized content along with provisioning payload 113. It can be delivered to the device 102. In yet other embodiments, a portion of the customized content used to complete the provisioning process may be downloaded from the remotely hosted location 140, and another portion of the customized content is preloaded. Content 112 may be provided.

  In some embodiments, it may be useful to access customized content 110 from multiple sources as described above. For example, a portion of the customized content 110 may be delivered and maintained by the remotely hosted site 140, while another portion of the customized content 110 is pre-loaded on, for example, the provisioning payload 113 or the device 102. Through loading, it can be delivered and maintained by the telephone service provider. Next, if customized content 110 accessed from remotely hosted location 140 requires any updates or changes, this will not affect any content accessed from the service provider of device 102. I will. That is because those changes and updates are probably done on the remotely hosted site 140. Similarly, if the content 110 held on the device 102 or through the provisioning payload 113 (by the service provider of the device 102) requests any updates or changes, the remotely accessed content and the retention of that content is Will not be affected.

  With reference now to FIG. 2, a method 200 for provisioning a mobile device is described. The method 200 comprises preloading a plurality of customized content items in a system memory partition of the mobile device at block 202. In some embodiments, the pre-loaded customization content is one or more of multiple graphics, multiple images, multiple audio files, multiple splash screens, startup screens, multiple backgrounds, and multiple tones. Can have. At block 204, the method 200 comprises wirelessly delivering the provisioning payload to the mobile device. The payload may have one or more file locators. In some embodiments, the file locator may include a uniform resource identifier (URI) string. At block 206, the method 200 comprises accessing at least a portion of the preloaded customized content based on the file locator.

  At block 208, the method 200 comprises storing a copy of the preloaded customized content referenced by the file locator in the carrier memory partition of the mobile device. At block 210, the method 200 comprises completing a customization process for the mobile device using the customized content stored in the carrier memory partition. In some embodiments, following the file locator, storing a copy of the content, and completing the customization process may be completed by the customization client of the mobile device. In some embodiments, the pre-loaded customization content has at least three sets of customization content. Each set of customized content is associated with a different wireless service brand, and the file locator is associated with only one set of those sets of customized content, eg, customized content associated with only one of a plurality of wireless service brands, Point to. In some embodiments, the method 200 may optionally comprise removing unused pre-loaded customized content from the system memory partition at block 212.

  In some embodiments, a portion of the total customization content may be delivered in the provisioning payload. The portion of the customized content delivered in the provisioning payload may have one or more of a customer service number, messaging platform, IP address and port number, client identification information, and multiple market catalogs. In other embodiments, the entire customization content can be preloaded on the mobile device and referenced by a file locator. In some embodiments, the provisioning payload size may be reduced. This is because at least some of the customized content is preloaded on the mobile device.

  With reference now to FIG. 3, a method 300 for customizing a mobile device is described. The method 300 comprises wirelessly receiving a provisioning payload at a mobile device at block 302. The payload has one or more file locators. In some embodiments, the file locator may have a uniform resource identifier (URI) string. At block 304, the method 300 may comprise accessing pre-loaded customized content based on the file locator (or URI string). The file locator points to at least a portion of preloaded customized content stored in the system memory partition of the mobile device. At block 306, the method 300 may optionally comprise storing a pre-loaded copy of customized content from the mobile device system memory partition in the mobile device carrier memory partition.

  At block 308, the method 300 may comprise completing the mobile device customization process using the customized content stored in the system memory partition. In some embodiments, the method 300 may optionally comprise returning the mobile device to factory default settings at block 310. Throughout the factory default settings, the customized content remains in the mobile device's carrier memory partition. In some embodiments, a portion of the total customization content may be delivered in the provisioning payload. In some embodiments, the customization process is completed by a provisioning application on the mobile device. In some embodiments, the file locator may have one of a uniform resource identifier (URI) string or a uniform resource locator (URL) string. In some embodiments, the customized content may be brand or company specific.

  With reference now to FIG. 4, a method 400 for provisioning a mobile device is described. The method 400 comprises, at block 402, wirelessly receiving a provisioning payload at the mobile device. The payload has one or more file locators and optionally customized content. In some embodiments, the file locator may include a string of uniform resource locators (ie URLs). At block 404, the method 400 optionally comprises examining the provisioning payload. At block 406, the method 400 comprises accessing a remotely hosted location based on the file locator. At block 408, the method 400 comprises downloading customized content from a remotely hosted location to the mobile device. In some embodiments, the downloading step can be completed based on a hypertext transfer protocol (HTTP) request. In some embodiments, the downloading step can be completed incrementally and the customized content is prioritized and downloaded according to the priority. In some embodiments, the downloading step can only be partially completed if the mobile device is connected to the network by a roaming connection (or if the mobile device is under a roaming connection). In some embodiments, mobile device users may not be charged for data usage that occurs for downloading customized content.

  In some embodiments, the downloaded customized content may have multiple graphics, multiple images, multiple audio files, multiple splash screens, startup screens, multiple backgrounds, and multiple tones. In some embodiments, the entire customization content can be downloaded from a remotely hosted location. In other embodiments, a portion of the customized content may be delivered in the provisioning payload, and the portion of the customized content delivered in the provisioning payload may include a customer service number, a messaging platform, an IP address and port number, a client identification Information as well as one or more of a plurality of market catalogs may be included. At block 410, the method 400 comprises completing the customization process for the mobile device using the customization content. In some embodiments, the method 400 may optionally comprise returning the mobile device to factory default settings at block 412. Throughout the factory default settings, customized content persists in the mobile device's carrier memory partition. In some embodiments, one or more of the steps of the method may be completed by a customization client or provisioning application on the mobile device. In some embodiments, the customized content downloaded from a remotely hosted location and / or received in the provisioning payload can be brand and / or company specific content.

  Referring now to FIG. 5, a method 500 for customizing a mobile device is described. The method 500 comprises wirelessly receiving a provisioning payload at the mobile device at block 502. The payload has two or more file locators. At block 504, the method 500 may comprise accessing pre-loaded customized content based on the first file locator. The first file locator points to one or more preloaded customized content items on the mobile device. In some embodiments, the preloaded customization content has up to four different versions of branding content. At block 506, the method 500 may comprise accessing a remotely hosted location based on the second file locator. At block 508, the method 500 may comprise downloading customized content from a remotely hosted location to the mobile device. In some embodiments, the second file locator may point to the fifth version of the branding content. In some embodiments, the second file locator may point to company specific content. At block 510, the method 500 may comprise completing a customization process for a mobile device using pre-loaded customization content and downloaded customization content.

  FIG. 6 depicts a mobile device 600. Although the mobile device 600 is operable to implement aspects of the present disclosure, the present disclosure should not be limited to these implementations. Although shown as a mobile phone, the mobile device 600 may take various forms including a wireless handset, pager, personal digital assistant (PDA), game console, or media player. Mobile device 600 includes a display 602 and a touch-sensitive surface and / or a plurality of keys 604 for input by a user. Mobile device 600 may present multiple options for the user to select, multiple controls for the user to activate, and / or multiple cursors or other indicators for the user to indicate. The mobile device 600 may further accept data input from the user, including multiple numbers to dial or various parameter values for setting the operation of the handset. The mobile device 600 may further execute one or more software or firmware applications in response to a plurality of user instructions. These applications may configure the mobile device 600 to perform various customized functions in response to user interaction. Further, mobile device 600 can be programmed and / or configured wirelessly from, for example, a wireless base station, wireless access point, or peer mobile device 600. Mobile device 600 may execute a web browser application that allows display 602 to display a web page. The web page may be obtained by wireless communication with a base station, wireless network access node, peer mobile device 600, or any other wireless communication network or system.

  FIG. 7 shows a block diagram of a mobile device 600. While various known components of the handset are depicted, in one embodiment, the mobile device 600 may include a subset of the listed components and / or additional components not listed. . Mobile device 600 includes a digital signal processor (DSP) 702 and memory 704. As shown, mobile device 600 includes antenna and front end unit 706, radio frequency (RF) transceiver 708, baseband processing unit 710, microphone 712, earphone speaker 714, headset port 716, input / output interface 718, removable memory. Card 720, universal serial bus (USB) port 722, infrared port 724, vibrator 726, keypad 728, touch screen liquid crystal display (LCD) 730 having a touch sensor surface, touch screen / LCD controller 732, camera 734, camera controller 736 , And a global positioning system (GPS) receiver 738. In one embodiment, the mobile device 600 may include another type of display that does not provide a touch sensor screen. In one embodiment, the DSP 702 can communicate directly with the memory 704 without going through the input / output interface 718. Further, in one embodiment, the mobile device 600 may include other peripheral devices that provide other functions.

  The DSP 702, or some other form of controller or central processing unit, can control the various components of the mobile device 600 according to embedded software or firmware stored in the memory 704 or stored in the memory contained within the DSP 702 itself. Operates to control. In addition to the embedded software or firmware, the DSP 702 is stored in the memory 704 or via an information carrying medium such as a portable data storage medium such as a removable memory card 720 or via wired or wireless network communication. A plurality of other applications that can be used in the future can be executed. The application software may comprise a compiled set of machine readable instructions that configure the DSP 702 to provide the desired functionality, or the application software may be processed by an interpreter or compiler to indirectly configure the DSP 702 Can be a plurality of high level software instructions.

  The DSP 702 may communicate with the wireless network via the analog baseband processing unit 710. In some embodiments, the communication may provide an Internet connection, allowing a user to gain access to content on the Internet and send and receive email or text messages. The input / output interface 718 interconnects the DSP 702 with various memories and interfaces. Memory 704 and removable memory card 720 may provide software and data to configure the operation of DSP 702. Among the plurality of interfaces may be a USB port 722 and an infrared port 724. USB port 722 may allow mobile device 600 to function as a peripheral and exchange information with a personal computer or other computer system. Other optional ports, such as an infrared port 724 and a Bluetooth® interface or an IEEE 802.11 compliant wireless interface, may include the mobile device 600, other nearby handsets and / or multiple wireless base stations. It may be possible to communicate with the radio.

  Keypad 728 is coupled to DSP 702 via interface 718 and provides a mechanism for a user to make selections, enter information, and otherwise provide input to mobile device 600. Another input mechanism may be a touch screen LCD 730 that may also display text and / or graphics to the user. Touch screen LCD controller 732 couples DSP 702 to touch screen LCD 730. The GPS receiver 738 is coupled to the DSP 702 to decode a plurality of global positioning system signals, thereby allowing the mobile device 600 to determine its location.

  FIG. 8A shows a software environment 802 that may be implemented by the DSP 702. The DSP 702 executes operating system software 804 that provides a platform on which the rest of the software runs. The operating system software 804 may provide various drivers for handset hardware that has multiple standardized interfaces that are accessible to application software. Operating system software 804 is coupled to and can exchange information with an application management service (AMS) 806 that transfers control between multiple applications running on the mobile device 600. A web browser application 808, media player application 810, and JAVA applet 812 are also shown in FIG. 8A. Web browser application 808 can be executed by mobile device 600 to browse content and / or the Internet, for example, when mobile device 600 is coupled to a network via a wireless link. Web browser application 808 may allow a user to enter information into multiple forms and select multiple links to search and browse multiple web pages. Media player application 810 may be executed by mobile device 600 to play audio or audiovisual media. The JAVA applet 812 may be executed by the mobile device 600 to provide various functions including games, utilities, and other functions.

  FIG. 8B shows an alternative software environment 820 that may be implemented by the DSP 702. The DSP 702 executes operating system software 828 (eg, an operating system kernel) and an execution runtime 830. The DSP 702 executes an application 822 that may execute at the execution runtime 830 and may use multiple services provided by the application framework 824. Application 822 and application framework 824 may use the functionality provided by library 826.

  FIG. 9 illustrates a computer system 900 suitable for implementing one or more embodiments disclosed herein. Computer system 900 communicates with secondary storage device 904, memory devices including read only memory (ROM) 906, random access memory (RAM) 908, input / output (I / O) devices 910, and network connectivity devices 912. , Including a processor 902 (which may be referred to as a central processing unit or CPU). The processor 902 can be implemented as one or more CPU chips.

  By programming and / or loading a plurality of executable instructions on computer system 900, at least one of CPU 902, RAM 908, and ROM 906 is modified to provide a specific machine with the novel functionality taught by this disclosure. Alternatively, it is understood that the computer system 900 is partially converted into an apparatus. It is fundamental in the electrical and software engineering arts that functions that can be implemented by loading executable software into a computer can be converted into hardware implementations by a number of well-known design rules. The decision between implementing the concept in software and that in hardware usually depends on considerations of design stability and the number of units generated, rather than any issues involved in the software domain to hardware domain transformation. To do. In general, designs that still change frequently will preferably be implemented in software. This is because hardware implementation respins are more expensive than software design respins. In general, a stable and mass-produced design will preferably be implemented in hardware, for example in an application specific integrated circuit (ASIC). This is because hardware implementation costs less than software implementation for mass production. The design can often be developed and tested in software form and later converted to an equivalent hardware implementation by well-known design rules in an application specific integrated circuit that hardwires multiple software instructions. Just as a machine controlled by a new ASIC is a specific machine or device, a computer loaded with multiple executable instructions and / or loaded can similarly be considered a specific machine or device.

  Secondary storage 904 typically consists of one or more disk drives or tape drives and overflows to store data in a nonvolatile manner and if RAM 908 is not large enough to hold all the working data Used as a data storage device. The secondary storage device 904 can be used to store a plurality of programs. Multiple programs are loaded into RAM 908 when such multiple programs are selected to be executed. ROM 906 is used to store a plurality of instructions and possibly data read during program execution. ROM 906 is typically a non-volatile memory device having a small memory capacity relative to the larger memory capacity of secondary storage device 904. The RAM 908 is used to store volatile data and in some cases to store multiple instructions. Access to both ROM 906 and RAM 908 is typically faster than access to secondary storage device 904. Secondary storage device 904, RAM 908, and / or ROM 906 may be referred to as computer-readable storage media and / or non-transitory computer-readable media in some contexts.

  The I / O device 910 can be a printer, video monitor, liquid crystal display (LCD), touch screen display, keyboard, keypad, switch, dial, mouse, tracking ball, voice recognition device, card reader, paper tape reader, or other Well known input devices may be included.

  The network connectivity device 912 includes a modem, a modem bank, an Ethernet card, a universal serial bus (USB) interface card, a serial interface, a token ring card, a fiber optic distributed data interface (FDDI) card, a wireless local area network ( WLAN) cards such as code division multiple access (CDMA), pan-European digital mobile communication system (GSM), long term evolution (LTE), global interoperability for microwave access (WiMAX) And / or may take the form of wireless transceiver cards, such as wireless transceiver cards of other wireless interface protocols, and other well-known network devices. These network connectivity devices 912 may allow the processor 902 to communicate with the Internet or one or more intranets. With such a network connection, it is expected that the processor 902 may receive information from the network or output information to the network in the course of performing the steps of the method described above. Such information, often represented as a sequence of instructions to be executed using processor 902, is received from and output to a network, for example, in the form of a computer data signal embodied in a carrier wave. obtain.

  Such information, which may include, for example, data to be executed using processor 902 or instructions, is received from a network in the form of, for example, a computer database band signal, or a signal embodied in a carrier wave, and the network Can be output. Baseband signals currently used or developed in the future or embedded in a carrier wave, or other types of signals may be generated according to several methods well known to those skilled in the art. The baseband signal and / or the signal embedded in the carrier wave may be referred to as a transient signal in some contexts.

  The processor 902 may include a hard disk, a floppy disk, an optical disk (these various disk-based systems may all be considered secondary storage devices 904), a ROM 906, a RAM 908, or a network connectivity device 912. Multiple instructions, multiple codes, multiple computer programs, multiple scripts to access may be executed. Although only one processor 902 is shown, there may be multiple processors. Thus, although it may be stated that multiple instructions are executed by one processor, the instructions may be executed by one or more processors simultaneously, sequentially, or otherwise. For example, multiple instructions, multiple codes, multiple computer programs that may be accessed from secondary storage device 904, ROM 906, and / or RAM 908 such as a hard drive, floppy disk, optical disk, and / or other device. The plurality of scripts and / or data may be referred to as non-temporary instructions and / or non-temporary information in some contexts.

  In one embodiment, the computer system 900 may include two or more computers that communicate with each other to perform tasks in coordination. For example, an application may be partitioned to allow simultaneous and / or parallel processing of multiple instructions of the application, but is not so limited. Alternatively, data processed by an application may be partitioned to allow simultaneous and / or parallel processing of multiple different portions of the data set by two or more computers. In one embodiment, virtualization software may be used by computer system 900 to provide the functionality of multiple servers that are not directly coupled to multiple computers in computer system 900. For example, the virtualization software may provide 20 virtual servers on 4 physical computers. In one embodiment, the above disclosed functionality may be provided by running one application and / or multiple applications in a cloud computing environment. Cloud computing can include providing a plurality of computing services over a network connection using a plurality of dynamically scalable computing resources. Cloud computing may be supported at least in part by virtualization software. The cloud computing environment can be established by the enterprise and / or employed as needed from a third party provider. Some cloud computing environments may comprise multiple cloud computing resources owned and operated by an enterprise, as well as multiple cloud computing resources employed and / or leased from third party providers.

  In one embodiment, some or all of the above disclosed functions may be provided as a computer program product. The computer program product includes one or more computer readable storage media that contain computer usable program code and may perform the functions disclosed above. The computer program product may include a plurality of data structures, a plurality of executable instructions, and other computer usable program code. The computer program product may be stored on a removable computer storage medium and / or a non-removable computer storage medium. Removable computer-readable storage media include, for example, analog magnetic tape, compact disk read only memory (CD-ROM) disk, floppy (registered trademark) disk, jump drive, digital card, multimedia card, etc., paper tape, magnetic tape, magnetic disk , Optical disks, solid state memory chips, but not limited to. The computer program product can be stored in the secondary storage device 904 of the computer system 900, in the ROM 906, in the RAM 908, and / or in other non-volatile memory and volatile memory, at least a plurality of portions of the content of the computer program product. System 900 may be suitable for loading. The processor 902 may execute a plurality of executable instructions and / or by partially accessing the computer program product, for example, by reading from a CD-ROM disk inserted into a disk drive peripheral of the computer system 900. Or multiple data structures may be processed. Alternatively, the processor 902 can execute multiple by accessing the computer program product remotely, for example, by downloading multiple executable instructions and / or multiple data structures from a remote server through the network connectivity device 912. Instructions and / or multiple data structures may be processed. The computer program product may include data, multiple data structures, multiple files, secondary storage 904 of computer system 900, ROM 906, RAM 908, and / or other non-volatile and volatile memory, and There may be multiple instructions that facilitate loading and / or copying multiple executable instructions.

  In some contexts, secondary storage device 904, ROM 906, and RAM 908 may be referred to as non-transitory computer readable media or computer readable storage media. The dynamic RAM embodiment of the RAM 908 stores the information written to it while the dynamic RAM receives power and is operated according to its design, for example, while the computer system 900 is turned on and operational. In that regard, it may also be referred to as a non-transitory computer readable medium. Similarly, processor 902 may include internal RAM, internal ROM, cache memory, and / or other internal non-transitory storage blocks that may be referred to as non-transitory computer readable media or computer readable storage media in some contexts. , Sections, or components.

  Although several embodiments have been provided in the present disclosure, the disclosed systems and methods can be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. Should be understood. The embodiments are to be regarded as illustrative and not restrictive, and the intent is not limited to the details given herein. For example, the various elements or components may be combined or integrated in another system, or multiple specific features may be omitted or not implemented.

  Also, in various embodiments, multiple techniques, multiple systems, multiple subsystems, and multiple methods described and shown as separate or separate may be used without departing from the scope of this disclosure. Can be combined or integrated with multiple systems, multiple modules, multiple technologies, or multiple methods. Other items shown or described as being directly coupled or communicating with each other may be electrically, mechanically, or otherwise through some interface, device, or intermediate component. Rather, they can be indirectly connected or communicate. Other examples of alterations, substitutions, and modifications will be identified by those skilled in the art and may be made without departing from the spirit and scope disclosed herein.

Claims (11)

A method for provisioning a mobile device, comprising:
Wirelessly delivering a provisioning payload to the mobile device, the payload having one or more file locators, and the mobile device includes a plurality of customizations preloaded in a system memory partition of the mobile device Having a content item, and
Accessing at least a portion of the pre-loaded customization content based on the file locator;
Storing a copy of the preloaded customized content referenced by the file locator in a carrier memory partition of the mobile device;
Completing the customization process for the mobile device using the customization content stored in the carrier memory partition. The method of claim 1, wherein the file locator includes a string of uniform resource identifiers. The method according to claim 1 or 2, wherein the step of following the file locator, storing the copy of the content, and completing the customization process are completed by a customization client on the mobile device. The pre-loaded customized content includes at least three sets of customized content, each set of customized content is associated with a different wireless service brand, and the file locator is only one set of the at least three sets of customized content. A method according to any one of claims 1 to 3. The method of claim 4, further comprising removing unused preloaded customized content from the system memory partition. The method according to any one of claims 1 to 5, wherein a part of the whole of the customized content is delivered in the provisioning payload. 7. The portion of the customized content delivered in the provisioning payload includes one or more of a customer service number, messaging platform, IP address and port number, client identification information, and multiple market catalogs. The method described. The method according to any one of claims 1 to 7, wherein the entire customized content is pre-loaded on the mobile device and referenced by the file locator. The preloaded customization content includes one or more of a plurality of graphics, a plurality of images, a plurality of audio files, a plurality of splash screens, a startup screen, a plurality of backgrounds, and a plurality of tones. 9. The method according to any one of items 8. The method according to any one of claims 1 to 9, wherein the size of the provisioning payload is reduced because at least some of the customized content is preloaded on the mobile device. On mobile devices ,
A procedure for receiving a provisioned payload distributed over the air, wherein the payload has one or more file locators, and the mobile device has a plurality of customized content preloaded in a system memory partition of the mobile device Having an item, a procedure;
Accessing at least a portion of the pre-loaded customization content based on the file locator;
Storing a copy of the preloaded customized content referenced by the file locator in a carrier memory partition of the mobile device;
Procedures for completing a customization process for the mobile device using the customization content stored in the carrier memory partition;
Program for the execution.

Images