# Patent

## Title
System and method of storing service brand packages on a mobile device

## Abstract

A method of providing wireless communication service to a mobile device is provided. The method comprises providing a system memory partition and a carrier memory partition on the mobile device. The method further comprising protecting two or more service brand packages from deletion by a mobile device reset. The method further comprises provisioning the mobile device with a first service brand network. The method further comprising resetting the mobile device, wherein resetting the mobile device comprises removing the mobile device from the first service brand network and deleting unprotected data stored on the mobile device. The method further comprising provisioning the mobile device with a second service brand network without re-installing previously installed data associated with the second service brand package.

## Background
CROSS-REFERENCE TO RELATED APPLICATIONS
None.
STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT
Not applicable.
REFERENCE TO A MICROFICHE APPENDIX
Not applicable.
BACKGROUND
Mobile telephones are electronic devices used for mobile voice or data communication based on network connectivity provided by base stations known as cell towers or sites. Electronic devices may have a system memory partition which stores an operating system package and fundamental communication applications for operating the electronic device. The operating system protects the system partition by restricting read/write access. Electronic devices may also have a user memory partition which provides storage for vendor packages and data packages downloaded by an electronic device user. The operating system may permit read/write access to virtually anyone desiring to access the user memory partition.
SUMMARY
In an embodiment, a method of branding a mobile device is disclosed. The method comprises providing a system memory partition and a carrier memory partition on the mobile device, wherein the carrier memory partition is a partitioned segment of a mobile device operating system with a set of carrier memory partition rules comprising immunity from deletion of data stored on the carrier memory partition during a mobile device reset. The method further comprises protecting two or more service brand packages from deletion by a mobile device reset, wherein service brand packages are employed by service brands and wherein service brand packages are configured to provision the mobile device with service brand networks, and wherein protecting two or more service brand packages comprises storing the two or more service brand packages on the carrier memory partition. The method further comprises provisioning the mobile device with a first service brand network, wherein provisioning the mobile device with the first service brand network comprises activating the first service brand package and receiving mobile service on the mobile device using the first service brand network. The method further resetting the mobile device, wherein resetting the mobile device comprises removing the mobile device from the first service brand network and deleting unprotected data stored on the mobile device. The method further comprises provisioning the mobile device with a second service brand network without re-installing previously installed data associated with the second service brand package, wherein provisioning the mobile device with the second service brand network comprises activating the second service brand package and receiving mobile service on the mobile device using the second service brand network.
In an embodiment, a method of branding a mobile device is disclosed. The method comprises providing a system memory partition and a carrier memory partition on the mobile device, wherein the carrier memory partition is a partitioned segment of a mobile device operating system with a set of carrier memory partition rules comprising immunity from deletion of data stored on the carrier memory partition during a mobile device reset. The method further comprising storing one or more applications on the carrier memory partition, wherein applications are configured to execute one or more functions on the mobile device, and wherein storing one or more applications comprise protecting one or more applications from deletion during a mobile device reset. The method further comprises installing one or more applications updates on the carrier memory partition without accessing the system memory partition. The method further comprises resetting the mobile device, wherein resetting the mobile device comprises deleting unprotected data stored on the mobile device. The method further comprises executing one or more applications stored on the carrier partition without re-installing application updates previously installed with the one or more applications on the carrier partition.
In an embodiment, a mobile device apparatus is disclosed. The apparatus comprises a radio transceiver. The apparatus further comprises at least one processor. The apparatus further comprises a mobile device operating system. The apparatus further comprises a carrier partition comprising a set of carrier partition rules, wherein the carrier partition rules comprise providing control over access to the carrier partition to the service brands with service brand packages stored on the carrier partition and protecting at least a first service brand package and a second service brand package stored on the carrier partition during a reset of the mobile device. The apparatus further comprises a system partition comprising a set of system partition rules, wherein the system partition rules comprises providing control over access to the system partition to the manufacturer of the mobile device and protecting data stored on the system partition during a reset of the mobile device.
These and other features will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.



BRIEF DESCRIPTION OF THE DRAWINGS
For a more complete understanding of the present disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.
FIG. 1 is a block diagram of a provisioning system according to an embodiment of the disclosure.
FIG. 2 is a flow chart of a method according to an embodiment of the disclosure.
FIG. 3 is a flow chart of a method according to an embodiment of the disclosure.
FIG. 4 is an illustration of a mobile device according to an embodiment of the disclosure.
FIG. 5 is a block diagram of a mobile device according to an embodiment of the disclosure.
FIGS. 6A and 6B are block diagrams of software architecture for a mobile device according to an embodiment of the disclosure.
FIG. 7 is a block diagram of a computer system according to an embodiment of the disclosure.



DETAILED DESCRIPTION
It should be understood at the outset that although illustrative implementations of one or more embodiments are illustrated below, the disclosed systems and methods may be implemented using any number of techniques, whether currently known or not yet in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, but may be modified within the scope of the appended claims along with their full scope of equivalents.
An apparatus and methods for branding and rebranding a mobile device with two or more service brand networks is described. Unique service brand packages for the same mobile device lead to separate stock keeping units (SKUs) for the same mobile device configured for different service brand networks, introducing complexity to inventory management and distribution. A single unique service brand package stored on a mobile device may limit or stop mobile communication service when the mobile device no longer has access or is no longer in range of the service brand network the device was provisioned with. Furthermore, a service brand package may be stored with the mobile device's operating system package so that in order for a service brand to update their service brand package the service brand must coordinate with a manufacturer's update.
As a remedy, a carrier partition is created on the mobile device. The carrier partition has rules (i.e. carrier partition rules) enforced by the operating system protecting data from deletion during a reset of the mobile device and giving certain parties control over read/write access. A reset of a mobile device may generally remove a mobile device from a mobile service network (i.e. so that the mobile device is not provisioned with a mobile service network) as well as delete unprotected data installed on the mobile device (e.g. music installed by a user on a user partition of the mobile device). A system partition may also be created on the mobile device. Generally, the system partition may store a mobile device operating system package and fundamental communication applications configured to provide functionality to the mobile device. The system partition may protect the mobile device's operating system package so that when a reset of the mobile device is implemented, the operating system package is not deleted from the mobile device. Read/write access to the system partition may be controlled by the operating system so that the manufacturer of the mobile device may have exclusive read/write access to the system partition, for example by providing access keys or tokens known only to the manufacturer. Additionally, a user partition may also be created on the mobile device. Generally, the user partition may store vendor data and/or data uploaded to the mobile device by a user. The rules of the user partition may also be controlled by the operating system. In an embodiment, the operating system may provide read/write access to the user partition to virtually anyone.
The carrier partition may generally store at least one service brand package configured to provision the mobile device with a service brand network. The carrier partition may protect service brand packages so that when a reset of the mobile device is implemented, the service brand packages are not deleted from the mobile device. This feature may allow the mobile device to change from operating on a first service brand network to operating on a second service brand network without reinstalling the second service brand package. Thus, a mobile device operating on a first service brand network may lose service when their mobile device is moved out of range from a first service brand network, but then may regain service when their mobile device comes into range of a second service brand network. For example, a mobile device may be located in the United States with a United States service brand network. The user of the mobile device may decide to leave the United States and the United States service brand network for Japan with a Japanese service brand network. The carrier partition of the mobile device may store both a United States service brand package associated with the United States service brand network and a Japanese service brand package associated with a Japanese service brand network so that when the mobile device moves from the United States to Japan, the mobile device may continue to receive mobile service. Additionally, this feature may allow the manufacturer of the mobile device as well as multi-service brand retailers to utilize economies of scale and reduce inventory costs by providing one mobile device associated with a single SKU configured for operation on two or more service brand networks. Furthermore, this feature may allow for updates to the service brand packages as well as vendor package updates stored on the carrier partition to be protected when the mobile device changes from operating on the first service brand network to operating on the second service brand network.
Access to the carrier partition is controlled by one or more carriers so that if updates to the first service brand package and/or the second service brand package are desired, only the carrier may access, provide access, and grant access to the carrier partition to make those updates. This feature may provide the carriers freedom to access to their service brand packages whenever they desire without having to coordinate for example with either another service brand or the mobile device manufacturer. Additionally, this feature may allow carriers to update their service brand packages even though the mobile device is operating on another service brand network. Furthermore, this feature may provide control to a carrier to permit only select vendors to install selected vendor packages or update selected vendor packages on the carrier partition.
Turning now to FIG. 1, a communication system 100 is described. The system 100 comprises a mobile device 112, a base transceiver station (BTS) 114, a network 116, and a server 140. The mobile device 112 may be a mobile phone, a personal digital assistant (PDA), a media player, or other communication enabled portable electronic device. In an embodiment, the mobile device 112 may be implemented as a handset. Details of handsets are discussed further hereinafter. The base transceiver station 114 provides a wireless communication link to the mobile device 112 and couples the mobile device 112 to the network 116. In an embodiment, the base transceiver station 114 provides a wireless communication link to the mobile device 112 according to one or more of a code division multiple access (CDMA) wireless protocol, a global system for mobile communications (GSM) wireless protocol, a long term evolution (LTE) wireless protocol, a worldwide interoperability for microwave access (WiMAX) wireless protocol, or another wireless protocol. While a single base transceiver station 114 is illustrated in FIG. 1, it is understood that the communication system 100 may comprise any number of base transceiver stations 114 and any number of mobile devices 112. The network 116 may be a public communication network, a private communication network, or a combination thereof.
The mobile device 112 may comprise a radio transceiver 122, a first user interface 124, a system partition 126, a user partition 130, and a carrier partition 128. Alternatively, the mobile device 112 may comprise two or more radio transceivers 122. The system partition 126 may store at least an operating system package and the carrier partition 128 may store one or more service brand packages. The carrier server 140 may comprise a processor 142, a memory 144, and an application 146 stored in the memory 144. The carrier server 140 may be implemented as a computer system. Computers are discussed in more detail hereinafter.
The application 146, when executed by a processor 142 of the carrier server 140, may receive an activation message from the mobile device 112, the mobile device 112 having two or more service brand packages stored on the carrier partition 128, wherein one of the service brand packages is configured to provision the mobile device with the service brand network associated with the carrier server 140. In response to an activation message from the mobile device 112, the application 146 identifies the particular service brand package stored on the carrier partition of the mobile device 112 associated with the carrier server 140, and writes a reference over-the-air to enable the particular service brand package on the carrier partition to provision the mobile device 112 with the particular service brand network.
The carrier server 140 may also reside in a distribution center or warehouse, and that some or all initial provisioning events may be completed in the distribution center. This would allow branding and customization to be accomplished prior to sending a plurality of mobile devices 112 to a retail point of sale or a large enterprise customer, whom all want to sell and/or use the mobile device on a particular service brand network, for example.
In FIG. 2, a method 200 is described. At block 202, a system partition may be provided, for example, by the manufacturer of a mobile device. The system partition may comprise a set of system partition rules. In an embodiment, the system partition rules may comprise requirements for accessing the system partition. For example, access to the system partition may be controlled only by the manufacturer of the mobile device and thus access to the system partition requires permission from the manufacturer of the mobile device. In an embodiment, the system partition rules may comprise protecting data stored on the system partition. For example, protecting data stored on the system partition may comprise protecting data from deletion during a reset of the mobile device to factory settings. Additionally, in an embodiment, the system partition rules may comprise regulation of the size (i.e. the memory capacity) of the system partition. For example, the size of the system partition may be a fixed size, such as a size predetermined by the manufacturer. Conversely, the size of the system partition may be varied depending on the total available memory space on the mobile device.
Additionally at block 202, one or more carrier partitions may be provided and/or installed on the mobile device, for example by the manufacturer of a mobile device. In an embodiment, the carrier partition may be a memory partition which is distinct from the system partition and/or any other memory partition on the mobile device (e.g. a user partition). For example, the carrier partition may be physically distinct from the system partition and/or any other partition such that a physical barrier physically separates the partitions. Alternatively, the operating system may virtually separate the partitions by restricting access to the different partitions, for example, based on user ID and/or secure passwords or keys.
The carrier partition may also comprise a set of carrier partition rules. In an embodiment, the carrier partition rules may comprise requirements for accessing the carrier partition. For example, access to the carrier partition may be controlled by service brands which store their service brand packages on the carrier partition. Each service brand may access the carrier partition to install updates to their service brand packages. Additionally, each service brand may permit access to a third party vendor to install vendor packages (e.g. applications) and/or vendor package updates (e.g. application updates) compatible with their own service brand package.
In an embodiment, the carrier partition rules may comprise protecting data stored on the carrier partition. In an embodiment, the carrier partition rules may be enforced or applied by the operating system. For example, the operating system may enforce carrier partition rules protecting data stored on the carrier partition, wherein protecting data (e.g. a service brand package) comprises protecting data from deletion during a reset of the mobile device to factory settings. The carrier partition rules may also permit a service brand and/or the manufacturer to selectively protect data and/or data packages from deletion during a reset of the mobile device. For example, logic instructions may be installed on the carrier partition for each service brand package. Flags may be installed with the logic instructions to switch each service brand package on or off. The carrier partition may be configured to protect the logic instructions from deletion during a reset of the mobile device, but may not be configured to protect the flags. Furthermore, the carrier partition may also be configured to protect service brand packages and vendor packages from deletion during a reset of the mobile device. Additionally, in an embodiment, the carrier partition rules may comprise regulation of the size (i.e. the memory capacity) of the carrier partition. For example, the size of the carrier partition may be a fixed size, such as a size predetermined by the manufacturer. Conversely, the size of the carrier partition may be varied depending on the total available memory space on the mobile device. The carrier partition is sized to store two or more service brand packages. Generally, the carrier partition rules are less restrictive than the system partition rules.
In an embodiment, the mobile device may comprise two or more carrier memory partitions, wherein each of the carrier memory partitions is designated for a particular service brand package. For example, a first service brand package may be stored on a first carrier memory partition and a second service brand package may be stored on a second carrier memory partition. The first carrier memory partition may protect the first service brand package from deletion during a mobile device reset and allow the first service brand to control access to the first carrier memory partition. Additionally, the second carrier memory partition may protect the second service brand package from deletion during a mobile device reset and allow the second service brand to control access to the second carrier memory partition.
In an embodiment, the one or more carrier memory partitions may comprise one or more sub-partitions. For example, a carrier memory partition storing a first service brand package may have one or more sub-partitions which the first service brand package may designated to one or more other data packages and/or one or more vendors providing applications packages. The sub-partition may protect data packages and/or data package updates from a deletion during a mobile device reset, for example. The first service brand may also allow designated data packages and/or designated to vendors access to one or more sub-partitions to install new data packages and/or data package updates.
In an embodiment, a user partition may be provided and installed, for example, by the manufacturer of a mobile device. The user partition may comprise a set of user partition rules. In an embodiment, the user partition rules may comprise requirements for accessing the user partition. For example, access to the user partition may be provided to virtually anyone who desires to download data on to the mobile device.
At block 204, an operating system package may be provided and install on the system partition of the mobile device. The operating system package may be configured to provide the basic factory operating functions for the mobile device. The rules governing the system partition may be used to protect the operating system for deletion from a mobile device reset and/or restrict access to the operating system.
At block 206, at least a first service brand package employed by a first service brand and a second service brand package employed by a second service brand may be protected from deletion by a mobile device reset. The first service brand package and the second service brand package may be protected from deletion by a mobile device reset by being installed on the carrier partition of the mobile device. In an embodiment, the manufacturer of the mobile device may be instructed, for example by a specification, to install a first service brand package employed by a first service brand on the carrier partition of the mobile device. The first service brand package may be configured to provision the mobile device to a first service brand network. A second service brand package employed by a second service brand may be installed on a carrier partition of the mobile device. In an embodiment, the manufacturer may be optionally instructed, for example by a specification, to install the second service brand package employed by a second service brand on a carrier partition of the mobile device. In an embodiment, the second service brand package may be installed on the same carrier partition as the first service brand package. Conversely, the first service brand package may installed a carrier partition dedicated the first service brand package while the second service brand package may be installed on a different carrier partition, for example a carrier partition dedicated for the second service brand package, than the first service brand package. The second service brand package is configured to provision the mobile device to a second service brand network. In an embodiment, the first service brand and the second service brand may be different brands. Furthermore, in an embodiment, the first service brand network and the second service brand network may be different networks. Conversely, the first service brand and the second service brand may be the same brand, but the first service brand may employ a first service brand package which provisions a mobile device to a first service brand network and the second service brand may employ a second service brand package which provisions a mobile device to second service brand network, wherein the first service brand network and the second service brand network are different networks. For example, Brand A may provide a first service brand employing a first service brand package as well as a second service brand employing a second service brand package, wherein the first service brand package provisions a mobile device to a first service brand network which, for example, operates in a first area, and the second service brand package provisions a mobile device to a second service brand network which, for example, operates in a second and different area. Furthermore, the first service brand and the second service brand may be different brands, but the first service brand network and the second service brand network may be the same network. For example, a first prepaid phone service and a second prepaid phone service may be different service brands, and thus, for example may have different rate packages, but the first and second prepaid phone services may be provisioned on the same prepaid mobile device network.
In an embodiment, a third, fourth, and/or fifth service brand package may be installed on a carrier partition of the mobile device. In an embodiment, the manufacturer of the mobile device may be instructed to install a third, fourth, and/or fifth service brand package employed by a third, fourth, and/or fifth service brand. One of ordinary skill in the art will appreciate after reading this disclosure the quantity of additional service brand packages which may be installed on the carrier partition of the mobile device.
Additionally, in an embodiment, logic instructions may be installed on the carrier partition of the mobile device, wherein the logic instruction comprise flags assigned to each of the service brand packages. In an embodiment, the manufacturer of the mobile device may be instructed to install logic instructions on the carrier partition of the mobile device. In an embodiment, the flags may be modulated in response to receiving a signal, for example, a wireless signal, enabling the first service brand package to transmit a signal to the first server. In an embodiment, only one set of flags (e.g. comprising one or more flags) assigned to one service brand package may be enabled at any one time.
At block 208, the mobile device is provisioned with the first service brand network associated with first service brand package stored on the carrier partition. For example, a first, second, and third service brand package may be stored on the carrier partition of the mobile device, wherein each service brand package is associated with a different service brand network. The mobile device may be provisioned with one service brand network, for example the first service brand network, by activating the first service brand package employed by the first service brand associated with the first service brand network. In an embodiment, activating a service brand package may comprise transmitting an activation signal to the mobile device through a short range wireless signal, an infrared signal, wire line, USB port, or the like. One of ordinary skill in the art will appreciate after reading this disclosure the various embodiments by which an activation signal may be transmitted to a mobile device. In an embodiment, activating the mobile device may comprise permitting a distributor and/or retailer to install pre-set logic instructions on the carrier partition which activates a particular service brand package and directs that particular service brand package to request provisioning data. In an embodiment, the activation signal may modulate one or more logic instruction switches associated with the first service brand package to activate the first service brand package and direct the first service brand package to request provisioning data. In an embodiment provisioning the mobile device with first service brand network may comprise sending a request to a server by the activated service brand package requesting provisioning data. The mobile device may then receive, install, and/or protect the provisioning data with the associated service brand package from the associated carrier server. Once provisioning data is installed with the particular service brand package, the mobile device may then operate on the particular service brand network.
Regardless of how the mobile device may be provisioned on a service brand network, the mobile device may be provisioned on only one service brand network at any one time. Thus, for example, if a mobile device is provisioned on the first service brand network, then the mobile device may not also be provisioned on the second service brand network while the mobile device is provisioned on the first service brand network. Furthermore, if the mobile device is to be moved from a first service brand network to a second service brand network, the mobile device may require removal from the first service brand network before being provisioned on the second service brand network.
At block 210, the mobile device is reset, wherein resetting the mobile device comprises removing the mobile device from the first service brand network (thus, the mobile device is no longer a branded mobile device with the first service brand, but a generic mobile device not branded with any brand). A reset of the mobile device may be performed by installing a code into the mobile device. For example, a reset of the mobile device may be performed by installing a “##RTN” code into the mobile device. A reset of the mobile device may also be performed by sending a signal to the mobile device. One of ordinary skill in the art will appreciate after reading this disclosure the various embodiments by which resetting a mobile device may be carried out.
In an embodiment, removing the mobile device from the first service brand network may comprise deactivating the first service brand package on the carrier partition of the mobile device by deleting data stored on the carrier partition, but unprotected by the carrier partition. For example, carrier partition rules may protect a first service brand package and a second service brand from deletion during a reset of the mobile device. Additionally, in an embodiment, carrier partition rules may protect provisioning data received from the first carrier server. Carrier partition rules may not protect pre-set logic instructions stored on the carrier partition of the mobile device activating the first service brand package. Thus, removing the mobile device from the first service brand network may comprise deleting the pre-set logic instructions on the carrier partition thereby deactivating the first service brand package on the carrier partition of the mobile device.
In an embodiment, removing the mobile device from the first service brand network may comprise deactivating the first service brand package on the carrier partition of the mobile device by modulating flags with the logic instructions assigned to each service brand package, wherein the flags may be switched on or off to activate or deactivate the service brand packages. For example, carrier partition rules may protect a first service brand package, a second service brand, and logic instructions from deletion during a reset of the mobile device. However, carrier partition rules may allow the flags to modulate into the off position during a reset of the mobile device deactivating any activated service brand packages on the carrier partition. Thus, in an embodiment, removing the mobile device from the first service brand network may comprise modulating one or more flags from the “on” position to the “off” position deactivating first service brand package.
In an embodiment, resetting the mobile device may comprise deleting data stored on a user partition of the mobile device and/or unprotected by the carrier partition. For example, video files and/or vendor packages stored on the user partition may be deleted during a reset of the mobile device, thereby losing any data previously installed and/or updated on the user partition when the device is provisioned again with another service brand network.
At block 212, the mobile device is provisioned with the second service brand network without re-installing previously installed data associated with the second service brand package. In an embodiment, the mobile device may be provisioned with second service brand network by activating the second service brand package employed by the second service brand. In an embodiment, activating the second service brand package may comprise transmitting an activation signal to the mobile device through a short range wireless signal, an infrared signal, wire line, USB port, or the like. One of ordinary skill in the art will appreciate after reading this disclosure the various embodiments by which an activation signal may be transmitted to a mobile device. For example, the activation signal may modulate one or more logic instruction switches associated with the second service brand package to activate the second service brand package and direct the second service brand package to request provisioning data. In an embodiment, activating the mobile device may comprise permitting a distributor and/or retailer to install pre-set logic instructions on the carrier partition which activates a particular service brand package and directs that particular service brand package to request provisioning data. In an embodiment provisioning the mobile device with the second service brand network may comprise that the activated second service brand package sends a request to the second carrier server for provisioning data. The mobile device may then receive and install the provisioning data with the second service brand package from the second carrier server. Once provisioning data is installed with the second service brand package, the mobile device may be provisioned with the second service brand network.
In an embodiment, because the first service brand package (i.e. with all of the first service brand updates) is still stored in the carrier partition while the mobile device is provisioned on the second service brand network, another reset of the mobile device may be carried out and the mobile device may again be provisioned on the first service brand network without downloading the first service brand package. In this embodiment, the carrier partition rules may protect the provisioning data installed with the first service brand package during the reset of the mobile device. Therefore, reactivation of the mobile device with the first service brand network does not require the re-installation of provisioning data associated with the first service brand package. Additionally, a manufacturer may have been instructed to install a third service brand package on the carrier partition of the mobile device when the first and second service brand packages were installed. In this case, another reset of the mobile device may be carried out so that the mobile device is provisioned on a third service brand network. It should be understood, that because the first, second, and third service brand packages are stored on the carrier partition, the carrier partition rules may allow updates to each of the packages to be retained after each reset of the mobile device regardless of whether the package was provisioning the mobile device during the update.
Furthermore, if vendors are permitted access to the carrier partition to install and/or update vendor packages on the mobile device, it should be understood that the carrier partition rules may allow installations and/or updates to the vendor packages installed on the carrier partition to be retained after each reset of the mobile device regardless of whether the vendor package was associated with a service brand package provisioning the mobile device during the installation and/or update.
In an embodiment, the method may further comprise installing and/or protecting a service brand package update on the carrier partition with one or more service brand packages while the mobile device is provisioned on a service brand network. For example, first service brand package updates may be installed and/or protected on the carrier partition which increase data rates with the service brand network or install new first service brand package features for the mobile device. One of ordinary skill in the art will appreciate the various types of updates which may be installed and/or protected with a service brand package.
A service brand package update for a particular service brand package may be installed on the carrier partition and/or protected by the carrier partition while the mobile device is provisioned on the service brand network associated with the service brand package update. For example, a service brand package update for a first service brand package may be installed on the carrier partition while the mobile device is provisioned on the first service brand network. A service brand package update for a particular service brand package may be installed on the carrier partition while the mobile device is provisioned on the service brand network unassociated with the service brand package update. For example, a service brand package update for a second service brand package may be installed on the carrier partition and protected by the carrier partition while the mobile device is provisioned on the first service brand network.
In an embodiment, service brand package updates may be installed without obtaining permission from a third party such as a manufacturer or another service brand. For example, a first service brand package update may be required for the first service brand package stored on the carrier partition. Because the first service brand package is stored on the carrier partition, the carrier partition rules may give the first service brand control over access to the carrier partition to update the first service brand package. Thus, the first service brand does not have to obtain permission from a manufacturer to install the first service brand package update. Additionally, because of the carrier partition rules, the first service brand would not have to obtain permission from a second service brand, for example, which also has a service brand package (i.e. second service brand package) stored on the carrier partition. In this example, even though the second service brand also controls access to the carrier partition, the first service brand would not have to obtain permission from the second service brand to access the carrier partition, unless the first service brand sought to access the area of the carrier partition storing data associated with the second service brand. Thus, in an embodiment, carrier partition rules may comprise that a service brand package only controls access to one more sections of the carrier partition where the service brand's data is stored.
In an embodiment, the method may further comprise that one or more service brands storing service brand package(s) on the carrier partition of the mobile device permit a vendor to install and/or update a vendor package on the carrier partition while the mobile device is provisioned on a service brand network. In an embodiment, a vendor package may comprise a data package which is not installed or created by the manufacturer of the mobile device and/or is not created by a service brand storing a service brand package on the mobile device. For example, vendor packages may be installed on the carrier partition for gaming applications, navigating applications, news outlet applications, or the like. One of ordinary skill in the art will appreciate the various types of vendor packages which may be installed and/or updated on the carrier partition.
A service brand with a service brand package stored on the carrier partition may permit a vendor to install and/or update a vendor package on the carrier partition while the mobile device is provisioned on the service brand network associated with the service brand granting permission. For example, a first service brand storing a first service brand package on the carrier partition may permit a vendor to install and/or update a vendor package on the carrier partition while the mobile device is provisioned on the first service brand network. A service brand with a service brand package stored on the carrier partition may also permit a vendor to install and/or update a vendor package on the carrier partition while the mobile device is provisioned on a service brand network not associated with the service brand granting permission. For example, a second service brand storing a second service brand package may permit a vendor to install and/or update a vendor package on the carrier partition while the mobile device is provisioned on the first service brand network.
In an embodiment, the service brand may permit a vendor package to be installed and/or updated based on one or more vendor identifications. A service brand with a service brand package stored on the carrier partition may permit all vendor packages from a particular vendor to install and/or update vendor packages on the carrier partition. For example, a first service brand may permit all vendor packages from vendor “A” to be installed and/or updated on the carrier partition. Additionally, a service brand with a service brand package stored on the carrier partition may permit only approved vendor packages from one or more vendors to install and/or update vendor packages on the carrier partition. For example, a first service brand may permit only gaming vendor packages from one or more vendors to be installed and/or updated on the carrier partition.
In an embodiment, a service brand may permit a vendor to access the carrier partition to install and/or update vendor packages without obtaining permission from a third party such as a manufacturer or another service brand. Because of the carrier partition rules, a service brand may not have to obtain permission from another service brand which also has a service brand package stored on the carrier partition to permit a vendor to access to the carrier partition to install and/or update a vendor package. For example, a first service brand may permit vendor “A” to access the carrier partition to install and/or update vendor “A's” vendor package on the carrier partition, even though a second service brand does not permit vendor “A” to access the carrier partition. In this example, even though the second service brand also controls access to the carrier partition, the first service brand may not have to obtain permission from the second service brand to permit Vendor “A” to access to the carrier partition to install and/or update the package of vendor “A”, unless the first service brand sought to permit vendor “A” access to the area of the carrier partition storing data associated with the second service brand. Similarly, because of the carrier partition rules, a service brand may not have to obtain permission from the manufacturer to permit a vendor access to the carrier partition to install and/or update vendor packages.
Turning now to FIG. 3, a method 300 is described. At block 302, a system memory partition and a carrier memory partition may be provided on the mobile device, wherein the carrier memory partition is a partitioned segment of a mobile device operating system with a set of carrier memory partition rules comprising immunity from deletion of data stored on the carrier memory partition during a mobile device reset. The system partition may comprise an operating system package, while the one or more carrier partitions may comprise two or more service brand packages. The service brand packages may be employed by different brands (e.g. a first service brand and a second service brand). In an embodiment, the first service brand package employed by the first service brand may be activated on the mobile device, while the second service brand package employed by the second service brand may be not be activated.
At block 304, one or more applications and/or data packages are stored on the carrier memory partition, wherein the applications and/or data packages are configured to execute one or more functions on the mobile device. In an embodiment, storing one or more applications and/or data packages on the mobile device may comprise protecting one or more applications from deletion during a mobile device reset. For example, a text messaging application may be stored on the carrier memory partition of the mobile device. The mobile device may be reset, thereby deleting all unprotected data packages on the mobile device. The mobile device may still retain the text message application because it was stored on the carrier memory partition protecting the text messaging application from the mobile device reset.
At block 306, one or more application updates and/or data package updates may be installed and/or stored on the carrier memory partition of the mobile device. In an embodiment, because access to the carrier memory partition is controlled by one or more service brands the one or more application updates and/or data package updates may be installed without accessing the system partition. For example, the text messaging application may require updates to accommodate new picture and/or video software which may be sent via text message. These updates may be installed on the carrier memory partition of the mobile device with the permission of one or more service brands. Because the service brands control access to the carrier memory partition, the vendor supplying the text message application and/or the text messaging application updates does not have to coordinate with a manufacturer, for example, in order install applications and/or updates on the mobile device.
At block 308, the mobile device is reset. A mobile device reset comprises deleting unprotected data, such as application packages and/or application package updates, stored on the mobile device. For example, data packages, application packages, updates for data packages, and/or updates for applications packages may be stored on a user memory partition of the mobile device. Thus, when a mobile device reset is executed, all the data packages, application packages, updates for data packages, and/or updates for applications packages stored on the user memory partition may be deleted. Conversely, if the same data packages, application packages, updates for data packages, and/or updates for applications packages are stored on the carrier memory partition for example, they may not be deleted by a mobile device reset.
At block 310, one or more applications stored on the carrier memory partition are executed without re-installing application updates previously installed with the one or more applications on the carrier memory partition. For example, the one or more updates to the text message application may have been installed and/or stored on the carrier memory partition before the mobile device was reset. Because the one or more updates where installed and/or stored on the carrier memory partition before the mobile device reset, the updates previously installed may not require re-installing after the mobile device reset to execute the updates and/or the applications with the updates. Conversely, if the one or more applications were stored on, for example, the user memory partition, the one or more updates may require re-installation after the mobile device is reset.
FIG. 4 depicts the mobile device 400, which is operable for implementing aspects of the present disclosure, but the present disclosure should not be limited to these implementations. Though illustrated as a mobile phone, the mobile device 400 may take various forms including a wireless handset, a pager, a personal digital assistant (PDA), a gaming device, or a media player. The mobile device 400 includes a display 402 and a touch-sensitive surface and/or keys 404 for input by a user. The mobile device 400 may present options for the user to select, controls for the user to actuate, and/or cursors or other indicators for the user to direct. The mobile device 400 may further accept data entry from the user, including numbers to dial or various parameter values for configuring the operation of the handset. The mobile device 400 may further execute one or more software or firmware applications in response to user commands. These applications may configure the mobile device 400 to perform various customized functions in response to user interaction. Additionally, the mobile device 400 may be programmed and/or configured over-the-air, for example from a wireless base station, a wireless access point, or a peer mobile device 400. The mobile device 400 may execute a web browser application which enables the display 402 to show a web page. The web page may be obtained via wireless communications with a base transceiver station, a wireless network access node, a peer mobile device 400 or any other wireless communication network or system.
FIG. 5 shows a block diagram of the mobile device 500. While a variety of known components of handsets are depicted, in an embodiment a subset of the listed components and/or additional components not listed may be included in the mobile device 400. The mobile device 400 includes a digital signal processor (DSP) 502 and a memory 504. As shown, the mobile device 400 may further include an antenna and front end unit 506, a radio frequency (RF) transceiver 508, a baseband processing unit 510, a microphone 512, an earpiece speaker 514, a headset port 516, an input/output interface 518, a removable memory card 520, a universal serial bus (USB) port 522, an infrared port 524, a vibrator 526, a keypad 528, a touch screen liquid crystal display (LCD) with a touch sensitive surface 530, a touch screen/LCD controller 532, a camera 534, a camera controller 536, and a global positioning system (GPS) receiver 538. In an embodiment, the mobile device 400 may include another kind of display that does not provide a touch sensitive screen. In an embodiment, the DSP 502 may communicate directly with the memory 504 without passing through the input/output interface 518. Additionally, in an embodiment, the mobile device 400 may comprise other peripheral devices that provide other functionality.
The DSP 502 or some other form of controller or central processing unit operates to control the various components of the mobile device 400 in accordance with embedded software or firmware stored in memory 504 or stored in memory contained within the DSP 502 itself. In addition to the embedded software or firmware, the DSP 502 may execute other applications stored in the memory 504 or made available via information carrier media such as portable data storage media like the removable memory card 520 or via wired or wireless network communications. The application software may comprise a compiled set of machine-readable instructions that configure the DSP 502 to provide the desired functionality, or the application software may be high-level software instructions to be processed by an interpreter or compiler to indirectly configure the DSP 502.
The DSP 502 may communicate with a wireless network via the analog baseband processing unit 510. In some embodiments, the communication may provide Internet connectivity, enabling a user to gain access to content on the Internet and to send and receive e-mail or text messages. The input/output interface 518 interconnects the DSP 502 and various memories and interfaces. The memory 504 and the removable memory card 520 may provide software and data to configure the operation of the DSP 502. Among the interfaces may be the USB port 522 and the infrared port 524. The USB port 522 may enable the mobile device 400 to function as a peripheral device to exchange information with a personal computer or other computer system. The infrared port 524 and other optional ports such as a Bluetooth® interface or an IEEE 802.11 compliant wireless interface may enable the mobile device 400 to communicate wirelessly with other nearby handsets and/or wireless base stations.
The keypad 528 couples to the DSP 502 via the interface 518 to provide one mechanism for the user to make selections, enter information, and otherwise provide input to the mobile device 400. Another input mechanism may be the touch screen LCD 530, which may also display text and/or graphics to the user. The touch screen LCD controller 532 couples the DSP 502 to the touch screen LCD 530. The GPS receiver 538 is coupled to the DSP 502 to decode global positioning system signals, thereby enabling the mobile device 400 to determine its position.
FIG. 6A illustrates a software environment 602 that may be implemented by the DSP 502. The DSP 502 executes operating system software 604 that provides a platform from which the rest of the software operates. The operating system software 604 may provide a variety of drivers for the handset hardware with standardized interfaces that are accessible to application software. The operating system software 604 may be coupled to and interact with application management services (AMS) 606 that transfer control between applications running on the mobile device 400. Also shown in FIG. 6A are a web browser application 608, a media player application 610, and JAVA applets 612. The web browser application 608 may be executed by the mobile device 400 to browse content and/or the Internet, for example when the mobile device 400 is coupled to a network via a wireless link. The web browser application 608 may permit a user to enter information into forms and select links to retrieve and view web pages. The media player application 610 may be executed by the mobile device 400 to play audio or audiovisual media. The JAVA applets 612 may be executed by the mobile device 400 to provide a variety of functionality including games, utilities, and other functionality.
FIG. 6B illustrates an alternative software environment 620 that may be implemented by the DSP 502. The DSP 502 executes operating system software 628 (for example an operating system kernel) and an execution runtime 630. The DSP 502 executes applications 622 that may execute in the execution runtime 630 and may rely upon services provided by the application framework 624. Applications 622 and the application framework 624 may rely upon functionality provided via the libraries 626.
FIG. 7 illustrates a computer system 380 suitable for implementing one or more embodiments disclosed herein. The computer system 380 includes a processor 382 (which may be referred to as a central processor unit or CPU) that is in communication with memory devices including secondary storage 384, read only memory (ROM) 386, random access memory (RAM) 388, input/output (I/O) devices 390, and network connectivity devices 392. The processor 382 may be implemented as one or more CPU chips.
It is understood that by programming and/or loading executable instructions onto the computer system 380, at least one of the CPU 382, the RAM 388, and the ROM 386 are changed, transforming the computer system 380 in part into a particular machine or apparatus having the novel functionality taught by the present disclosure. It is fundamental to the electrical engineering and software engineering arts that functionality that can be implemented by loading executable software into a computer can be converted to a hardware implementation by well known design rules. Decisions between implementing a concept in software versus hardware typically hinge on considerations of stability of the design and numbers of units to be produced rather than any issues involved in translating from the software domain to the hardware domain. Generally, a design that is still subject to frequent change may be preferred to be implemented in software, because re-spinning a hardware implementation is more expensive than re-spinning a software design. Generally, a design that is stable that will be produced in large volume may be preferred to be implemented in hardware, for example in an application specific integrated circuit (ASIC), because for large production runs the hardware implementation may be less expensive than the software implementation. Often a design may be developed and tested in a software form and later transformed, by well known design rules, to an equivalent hardware implementation in an application specific integrated circuit that hardwires the instructions of the software. In the same manner as a machine controlled by a new ASIC is a particular machine or apparatus, likewise a computer that has been programmed and/or loaded with executable instructions may be viewed as a particular machine or apparatus.
The secondary storage 384 is typically comprised of one or more disk drives or tape drives and is used for non-volatile storage of data and as an over-flow data storage device if RAM 388 is not large enough to hold all working data. Secondary storage 384 may be used to store programs which are loaded into RAM 388 when such programs are selected for execution. The ROM 386 is used to store instructions and perhaps data which are read during program execution. ROM 386 is a non-volatile memory device which typically has a small memory capacity relative to the larger memory capacity of secondary storage 384. The RAM 388 is used to store volatile data and perhaps to store instructions. Access to both ROM 386 and RAM 388 is typically faster than to secondary storage 384. The secondary storage 384, the RAM 388, and/or the ROM 386 may be referred to in some contexts as computer readable storage media and/or non-transitory computer readable media.
I/O devices 390 may include printers, video monitors, liquid crystal displays (LCDs), touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, or other well-known input devices.
The network connectivity devices 392 may take the form of modems, modem banks, Ethernet cards, universal serial bus (USB) interface cards, serial interfaces, token ring cards, fiber distributed data interface (FDDI) cards, wireless local area network (WLAN) cards, radio transceiver cards such as code division multiple access (CDMA), global system for mobile communications (GSM), long-term evolution (LTE), worldwide interoperability for microwave access (WiMAX), and/or other air interface protocol radio transceiver cards, and other well-known network devices. These network connectivity devices 392 may enable the processor 382 to communicate with the Internet or one or more intranets. With such a network connection, it is contemplated that the processor 382 might receive information from the network, or might output information to the network in the course of performing the above-described method steps. Such information, which is often represented as a sequence of instructions to be executed using processor 382, may be received from and outputted to the network, for example, in the form of a computer data signal embodied in a carrier wave.
Such information, which may include data or instructions to be executed using processor 382 for example, may be received from and outputted to the network, for example, in the form of a computer data baseband signal or signal embodied in a carrier wave. The baseband signal or signal embedded in the carrier wave, or other types of signals currently used or hereafter developed, may be generated according to several methods well known to one skilled in the art. The baseband signal and/or signal embedded in the carrier wave may be referred to in some contexts as a transitory signal.
The processor 382 executes instructions, codes, computer programs, scripts which it accesses from hard disk, floppy disk, optical disk (these various disk based systems may all be considered secondary storage 384), ROM 386, RAM 388, or the network connectivity devices 392. While only one processor 382 is shown, multiple processors may be present. Thus, while instructions may be discussed as executed by a processor, the instructions may be executed simultaneously, serially, or otherwise executed by one or multiple processors. Instructions, codes, computer programs, scripts, and/or data that may be accessed from the secondary storage 384, for example, hard drives, floppy disks, optical disks, and/or other device, the ROM 386, and/or the RAM 388 may be referred to in some contexts as non-transitory instructions and/or non-transitory information.
In an embodiment, the computer system 380 may comprise two or more computers in communication with each other that collaborate to perform a task. For example, but not by way of limitation, an application may be partitioned in such a way as to permit concurrent and/or parallel processing of the instructions of the application. Alternatively, the data processed by the application may be partitioned in such a way as to permit concurrent and/or parallel processing of different portions of a data set by the two or more computers. In an embodiment, virtualization software may be employed by the computer system 380 to provide the functionality of a number of servers that is not directly bound to the number of computers in the computer system 380. For example, virtualization software may provide twenty virtual servers on four physical computers. In an embodiment, the functionality disclosed above may be provided by executing the application and/or applications in a cloud computing environment. Cloud computing may comprise providing computing services via a network connection using dynamically scalable computing resources. Cloud computing may be supported, at least in part, by virtualization software. A cloud computing environment may be established by an enterprise and/or may be hired on an as-needed basis from a third party provider. Some cloud computing environments may comprise cloud computing resources owned and operated by the enterprise as well as cloud computing resources hired and/or leased from a third party provider.
In an embodiment, some or all of the functionality disclosed above may be provided as a computer program product. The computer program product may comprise one or more computer readable storage medium having computer usable program code embodied therein to implement the functionality disclosed above. The computer program product may comprise data structures, executable instructions, and other computer usable program code. The computer program product may be embodied in removable computer storage media and/or non-removable computer storage media. The removable computer readable storage medium may comprise, without limitation, a paper tape, a magnetic tape, magnetic disk, an optical disk, a solid state memory chip, for example analog magnetic tape, compact disk read only memory (CD-ROM) disks, floppy disks, jump drives, digital cards, multimedia cards, and others. The computer program product may be suitable for loading, by the computer system 380, at least portions of the contents of the computer program product to the secondary storage 384, to the ROM 386, to the RAM 388, and/or to other non-volatile memory and volatile memory of the computer system 380. The processor 382 may process the executable instructions and/or data structures in part by directly accessing the computer program product, for example by reading from a CD-ROM disk inserted into a disk drive peripheral of the computer system 380. Alternatively, the processor 382 may process the executable instructions and/or data structures by remotely accessing the computer program product, for example by downloading the executable instructions and/or data structures from a remote server through the network connectivity devices 392. The computer program product may comprise instructions that promote the loading and/or copying of data, data structures, files, and/or executable instructions to the secondary storage 384, to the ROM 386, to the RAM 388, and/or to other non-volatile memory and volatile memory of the computer system 380.
In some contexts, the secondary storage 384, the ROM 386, and the RAM 388 may be referred to as a non-transitory computer readable medium or a computer readable storage media. A dynamic RAM embodiment of the RAM 388, likewise, may be referred to as a non-transitory computer readable medium in that while the dynamic RAM receives electrical power and is operated in accordance with its design, for example during a period of time during which the computer 380 is turned on and operational, the dynamic RAM stores information that is written to it. Similarly, the processor 382 may comprise an internal RAM, an internal ROM, a cache memory, and/or other internal non-transitory storage blocks, sections, or components that may be referred to in some contexts as non-transitory computer readable media or computer readable storage media.
While several embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted or not implemented.
Also, techniques, systems, subsystems, and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component, whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein.

## Claims

1. A method of branding a mobile device, comprising:
providing a system memory partition and a carrier memory partition on the mobile device, wherein the carrier memory partition includes a partitioned segment of a mobile device operating system with a set of carrier memory partition rules comprising immunity, during a mobile device reset, from deletion of data stored on the carrier memory partition, and wherein the data of the carrier memory partition comprises two or more service brand packages;
protecting the two or more service brand packages from deletion responsive to the mobile device reset, wherein the two or more service brand packages are employed by service brands and are configured to provision the mobile device with one or more networks, and wherein protecting the two or more service brand packages comprises storing the two or more service brand packages on the carrier memory partition and providing control of access to the carrier memory partition to a carrier associated with one of the two or more service brand packages;

provisioning the mobile device with a first service brand network, wherein provisioning the mobile device with the first service brand network comprises activating the first service brand package and receiving mobile service on the mobile device using the first service brand network;
resetting the mobile device, wherein resetting the mobile device comprises removing the mobile device from the first service brand network, deleting unprotected data stored on the mobile device, and immunizing the carrier memory partition from deletion of data by providing the control of access to the carrier memory partition to the carrier associated with one of the two or more service brand packages; and
provisioning the mobile device with a second service brand network without re-installing previously installed data associated with the second service brand package from the carrier memory partition, wherein provisioning the mobile device with the second service brand network comprises activating the second service brand package from the carrier memory partition and receiving mobile service on the mobile device using the second service brand network, and wherein the first and second service brand networks comprise the same network or different networks.

2. The method of claim 1, wherein provisioning comprises accessing a service brand package stored on the carrier memory partition without accessing the system memory partition.

3. The method of claim 1, wherein the system memory partition comprises a partitioned segment of the mobile device operating system distinct from the carrier partition and a set of system memory partition rules.

4. The method of claim 3, wherein the set of system partition rules comprise providing control over access to the system memory partition to the manufacturer of the mobile device.

5. The method of claim 1, the method further comprising providing a user memory partition on the mobile device, wherein the user memory partition is governed by a set of user memory partition rules.

6. The method of claim 1, wherein the set of carrier memory partition rules comprise providing control over access to the carrier partition to the one or more carriers with service brand packages stored on the carrier memory partition.

7. The method of claim 1, the method further comprising updating the first service brand package on the carrier memory partition while the mobile device is provisioned on the first service brand network, wherein updates on the carrier memory partition are installed independently of any other updates.

8. The method of claim 1, the method further comprising installing logic instructions comprising flags on the carrier memory partition, wherein the flags are modulated to activate the first service brand package.

9. The method of claim 1, wherein the carrier memory partition rules further comprise permitting a vendor to access the carrier memory partition to install vendor packages on the carrier memory partition.

10. The method of claim 1, wherein the carrier memory partition rules further comprise permitting a vendor to access the carrier memory partition to install vendor package updates to vendor packages on the carrier memory partition.

11. A method of branding a mobile device, comprising:
providing a system memory partition and a carrier memory partition on the mobile device, wherein the carrier memory partition includes a partitioned segment of a mobile device operating system with a set of carrier memory partition rules comprising immunity, during a mobile device reset, from deletion of data stored on the carrier memory partition, and wherein the data of the carrier memory partition comprises two or more service brand packages;
storing one or more applications on the carrier memory partition, wherein applications are configured to execute one or more functions on the mobile device, and wherein storing the one or more applications comprises protecting the one or more applications from deletion during the mobile device reset by providing control of access to the carrier memory partition to a carrier associated with one of a plurality of service brand packages of the carrier memory partition;
installing one or more applications updates on the carrier memory partition without accessing the system memory partition;
resetting the mobile device, wherein resetting the mobile device comprises deleting unprotected data stored on the mobile device and immunizing the carrier memory partition from deletion of data by providing the control of access to the carrier memory partition to the carrier associated with one of the plurality of service brand packages; and
executing the one or more applications stored on the carrier partition without re-installing application updates previously installed with the one or more applications on the carrier partition.

12. The method of claim 11, wherein the system memory partition comprises a set of system memory partition access rules different from the carrier memory partition rules and an operating system package.

13. The method of claim 11, wherein resetting the mobile device further comprises deactivating a first service brand package on the carrier memory partition without deleting provisioning data installed with the first service brand package.

14. The method of claim 11, wherein installing the one or more application updates comprises installing application updates associated with at least an activated service brand package.

15. The method of claim 11, wherein installing the one or more application updates comprises installing application updates associated with at least a deactivated service brand package.

16. The method of claim 11, wherein resetting the mobile device comprises protecting data stored on at least the carrier memory partition that is at least associated with a previously activated service brand package or at least a previously deactivated service brand package.

17. A mobile device, comprising:
a radio transceiver that communicatively couples with a wireless network of a carrier;
an at least one processor;
a mobile device operating system;
a carrier memory partition comprising a set of carrier partition rules, wherein the carrier memory partition rules:
provide control of access to the carrier partition to the carrier associated with at least one of a plurality of service brand packages stored on the carrier memory partition,
immunize the carrier memory partition from deletion of data by providing the control of access to the carrier memory partition to the carrier, and
protect at least a first service brand package and a second service brand package of the plurality of service brand packages stored on the carrier memory partition during a reset of the mobile device; and

a system memory partition comprising a set of system memory partition rules, wherein the system memory partition rules:
provide control over access to the system partition to the manufacturer of the mobile device, and
provide data stored on the system memory partition that is unprotected from deletion during the reset of the mobile device.

18. The apparatus of claim 17, wherein the mobile device comprises two or more carrier memory partitions, wherein each of the carrier memory partitions is designated for a particular service brand package.

19. The apparatus of claim 18, wherein the two or more carrier memory partitions comprise at least a first carrier memory partition and a second carrier memory partition, wherein the first carrier memory partition protects the first service brand package and access to the first carrier memory partition is controlled by the first service brand and the second carrier memory partition protects the second service brand package and access to the second carrier memory partition is controlled by the second service brand.

20. The apparatus of claim 17, wherein the carrier memory partition further comprises one or more sub-partitions.