Patent Grant
10021240
None.
Not applicable.
Not applicable.
Mobile phones, also known as user equipment (UEs) in some contexts, are a common item of consumer electronic gear. On average, users replace their UEs about every two years. To distinguish over competitors and to attract the interest of customers, original equipment manufacturers (OEMs) of UEs produce a wide variety of different models of UEs. UEs may differ by operating system that is installed on the UE. UEs may differ by display size. UEs may differ by a brand name associated with the UE. It is understood that different brands may promote or support different user visible functions or applications on the UE. UEs may differ by quality and features of an electronic camera built into the UE.
In an embodiment, a method of customizing a user equipment (UE) is disclosed. The method comprises receiving by the UE a definition of a group identity (GID) of the UE that comprises a UE model identity and a wireless communication service brand identity and receiving by the UE a customization manifest, where the customization manifest identifies a plurality of feature customization policies and a plurality of user feature customization override policies, where each feature customization policy defines which of a predefined number of feature customizations are to be active for a UE, and each user feature customization override policy defines which of the predefined number of feature customizations are to mandatorily be applied notwithstanding preexisting user customizations of the associated feature, whereby the customization manifest defines different feature customization policies to be applied to different UE models and for different wireless communication service brand identities and one of overrides or permits retaining preexisting user customizations of features. The method further comprises searching in the customization manifest by a customization client application executing on the UE using the GID of the UE as a search key, where the customization client application is triggered to execute by one of a UE activation process, a UE rebranding process, or a UE change of service provider, finding and selecting a feature customization policy in the customization manifest that matches the GID of the UE by the customization client application, and reading the selected feature customization policy from the customization manifest by the customization client application. The method further comprises finding and selecting a user feature customization override policy from the customization manifest that matches the GID of the UE by the customization client application, reading the selected user feature customization override policy from the customization manifest by the customization client application, identifying preexisting user feature customizations on the UE by the customization client application, and based on reading the selected feature customization policy, based on reading the selected user feature customization override policy, and based on identifying preexisting user feature customizations on the UE, customizing one or more features of the UE by the customization client application and not customizing one or more features of the UE that is identified for customization in the selected feature customization policy for which a preexisting user customization is identified and for which the selected user feature customization override policy allows retaining a preexisting user customization, where the customizing takes place as part of one of a UE activation process, a UE rebranding process, or a UE change of service provider.
In another embodiment, a user equipment (UE) is disclosed. The UE comprises a radio transceiver, a processor, a non-transitory memory, and a customization client application stored in the non-transitory memory. When executed by the processor, the customization client application determines a group identity (GID) of the UE during activation of the UE that comprises a UE model identity and a wireless communication service brand identity, identifies preexisting user feature customizations on the UE, and reads a customization manifest received by the UE via the radio transceiver, wherein the customization manifest identifies a plurality of feature customization policies and a plurality of user feature customization override policies, where each feature customization policy defines which of a predefined number of feature customizations are to be active for a UE, and each user feature customization override policy defines which of the predefined number of feature customizations are to mandatorily be applied notwithstanding preexisting user customizations of the associated feature. When executed, the customization client application further selects at least one of the plurality of feature customization policies from the customization manifest based on the GID of the UE, selects a feature customization override policy from the customization manifest based on the GID of the UE, and customizes the UE during one of activation of the UE, rebranding of the UE, or changing a provisioning of the UE to a different wireless communication service provider based on the selected at least one feature customization policies, the selected feature customization override policy, and based on identified preexisting user feature customizations on the UE, whereby some of the predefined number of feature customizations are customized in accordance with the customization manifest and some of the predefined number of feature customizations are not customized leaving corresponding preexisting user customizations in place based on the selected feature customization override policy allowing retaining the user customization.
In yet another embodiment, a user equipment (UE) is disclosed. The UE comprises a radio transceiver, a processor, a non-transitory memory, and a customization client application stored in the non-transitory memory. When executed by the processor in response to one of an activation of the UE, a rebranding of the UE, or a provisioning of the UE to a different service provider, the customization client application determines a group identity (GID) of the UE that comprises a UE model identity and a wireless communication service brand identity and reads a customization manifest received by the UE via the radio transceiver, wherein the customization manifest comprises a plurality of feature customization policies, a plurality of user feature customization override policies, a plurality of feature configuration policies, and a compressed file comprising a plurality of feature customization inputs where each feature customization policy defines which of a predefined number of feature customizations are to be active for a UE, each user feature customization override policy defines which of the predefined number of feature customizations are to mandatorily be applied notwithstanding preexisting user customizations of the associated feature, each feature configuration policy defines which of optional feature configurations of the predefined number of feature customizations is to be configured on the UE, and the feature customization inputs of the compressed file support activation of feature customization on UEs. The customization client application further identifies preexisting user feature customizations on the UE, selects at least one of the plurality of feature customization policies from the customization manifest based on the GID of the UE, selects a user feature customization override policy from the customization manifest based on the GID of the UE, selects at least one of the plurality of feature configuration policies from the customization manifest based on the GID of the UE, and uncompresses the file of feature customization inputs. The customization client application further customizes the UE by customizing at least one feature identified as active based on the uncompressed feature customization inputs, leaves at least one preexisting user feature customization in place for which the selected user feature customization override policy allows retaining the preexisting user feature customization, and configures at least one of the customization features identified as active based on the selected at least one of the feature configuration policies based on the uncompressed feature customization inputs.
These and other features will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.
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.
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.
A wireless telecommunication service provider may support a large number of different models of mobile phone or user equipment (UE) for use by its subscribers in its wireless network. In the United States, the current business paradigm is that a service provider may subsidize at least a part of the cost of a UE in exchange for a subscription contract with the subscriber, for example a two year contract. A different UE is associated with a different stock keeping unit (SKU) identity. Each different SKU entails separate and different testing which entails costs. It is desirable to buy a limited number of different SKU UEs from original equipment manufacturers and increase diversity of features and brands post-manufacturing, whereby the number of different SKUs can be reduced and the costs associated with testing the different SKUs is likewise reduced. The UEs may be shipped as quasi-generic UEs and customized later to different brands and different feature installations and different service plans after the OEMs ship the devices to the service provider.
As used herein, ‘customization,’ as performed by the customization framework and customization client described below, is a process that is controlled not by a user or subscriber but instead is controlled by a wireless communication service provider and by system-level applications (e.g., by a customization client application described further hereinafter) on the UE that are inaccessible to the user or subscriber. Additionally, ‘customization,’ as used herein, comprises in part configuring basic functionality associated with the UE such as brand specific logos, brand specific ring tones, brand specific customer care speed dial numbers or buttons, brand specific voice mail box configuration. Some configuration performed during this ‘customization’, as used herein, changes memory partitions that are restricted from user modifications by an operating system of the UE. In an embodiment, ‘customization’ can comprise, for example during an initial activation, configuring a phone number into the UE, configuring a mobile network code (MNC) into the UE, and other configuration actions that are preconditions for establishing ordinary wireless communication links with a radio access network (RAN), e.g., a cellular network.
The ‘customization’ described herein takes place in the context of specific and delimited duration processes mediated by the wireless service provider and/or the wireless network infrastructure core, for example pursuant and/or during initial activation of the UE, reactivation of the UE, rebranding of the UE, and/or provisioning the UE to a different wireless service provider. Said in other words, ‘customization’, as used herein occurs in a special operation mode and not during normal operation mode of the UE. The term ‘customization’, as used herein, does not refer to personalization of the UE by a user or subscriber, for example installing custom ringtones, selecting ringtone preferences by a user, setting a lock screen or ‘swipe’ screen image file for the UE, setting a background image file for the UE. The term ‘user customization’ or ‘user feature customization’ may be used herein to refer to customizations that a user may perform. In some cases, the features that a ‘user customization’ affects may be the same features that ‘customization’ accomplished by the customization framework and/or customization client affects. The two terms ‘customization’ and ‘user customization’ (or ‘user feature customization’) are used to distinguish customizations performed by the customization framework and/or customization client without user intervention and during special operation modes of the UE (i.e., during activation or reactivation or rebranding of the UE) from customizations performed by a user or subscriber (i.e., with user intervention) during normal operation modes of the UE.
The present disclosure teaches a universal framework for customizing UEs after shipping by OEMs. This new system and method frees the customization process from the open mobile alliance device management (OMA-DM) framework which has been used in the past for limited customization activities. Specifically a universal customization manifest is sent to all UEs, irrespective of model of UE, that are engaged in the customization process, for example during an activation of the UE. The same universal customization manifest comprises the information used by a first UE of a first model and first brand to customize itself as well as the information used by a second UE of a second model and second brand to customize itself. In some cases, the first UE and the second UE may have different operating systems installed and yet be able to self-customize themselves with the same universal customization manifest.
The creation of a single customization framework using a universal customization manifest can provide the benefit of a more easily maintained and updated customization system. That is, information technology (IT) staff do not need to learn and master a number of different customization systems and methods, for example different customization systems and methods for different operating systems or different models of UEs. Additionally, the single customization framework using a universal customization manifest provides support for a true single SKU UE inventory for a wireless communication service provider. In this forward-looking vision, a service provider would purchase a true generic UE device that is capable of customizing to support any feature set, any brand, and possibly even any operating system. Such a single SKU UE would provide many benefits to a service provider.
After being shipped by the OEM, the UE of the present disclosure may be brought into service through an activation process. As is understood by those of skill in the art, activation of a mobile phone or UE may comprise one or more steps of configuring or provisioning information into the wireless communication network infrastructure to support authentication of the UE into the wireless network to receive communication connectivity as well as one or more steps of configuring features and applications on the UE. Activation may proceed in a series of actions or steps. During an early phase of activation, the UE may be provided with identity information such as a brand identity (recalling that this may be a quasi-generic UE that is customizable to any of a plurality of different brands) and carrier identifying information such as a mobile network code (MNC) or other. This identity information may be provided by insertion into the UE of a subscriber identity module (SIM) card or a universal integrated circuit card (UICC) that is provisioned with this information. This identity information may be electronically transmitted to the UE, for example over-the-air wirelessly or via a wired connection, and stored in a secure memory (similar to an embedded, non-removable SIM card or UICC) of the UE.
During activation, the UE may receive a universal customization manifest. In an embodiment, the manifest comprises a plurality of definitions of customization actions to be taken for a plurality of different UEs as well as customization logic, customization scripts, references, and/or configuration data that can be used by the UE to customize itself as mandated by the definitions of customization actions. A customization client application on the UE determines its group identity (GID) based on the information present in the SIM, UICC, or secure memory area. This GID can be an aggregation of UE model identity and brand identity. The GID can be an aggregation of UE model identity, carrier network identity, and brand identity. The GID can be an aggregation of other information as well. The customization client then searches the plurality of definitions of customization actions in the customization manifest using the GID it has determined as a search key. The customization client parses each set of customization definitions that are referenced by its GID. The customization client then performs the customization actions identified by the definitions, using the customization logic, customization scripts, references, configuration data, configuration scripts, and/or configuration logic also included in the customization manifest to perform those customization actions.
The universal customization framework taught herein replaces an earlier customization paradigm that may involve exchanges of multiple messages to complete the same customization, a process which may be sensitive to communication link interruptions. Said in other words, the universal customization framework reduces network traffic and reduces the vulnerability of the customization process to transient communications outages. Additionally, this framework delegates to the UE itself the decision making process of choosing, based on parsing and analyzing the universal customization manifest, the customizations for the subject UE, for example based on self-identification of the UE by reading its GID. This allows the server application that sends the customization manifest to the UE to be much simpler. The server application does not need to conduct a lengthy dialog with the UEs to complete customization; the server application does not need to incorporate complicated branching logic to provide for special cases related to different models of UEs and even different maintenance releases (MRs) of the same model of UEs. This framework may simplify and hence streamline and accelerate the process of deploying new UEs to the network—for example new models being deployed to customers. The network operator can publish specifications defining the customization framework and structure of the customization manifest and delegate to original equipment manufacturers of UEs both the development of customization overlays and customization supporting artifacts (customization logic, customization scripts, references to content sites, configuration data, configuration scripts, and/or configuration logic) and the testing of the same, thereby considerably reducing the labor burden on the wireless communication service provider of providing this service as in the prior customization paradigm.
Again, this framework redistributes much of the “intelligence” involved in determining what customization is to be performed on the UE from the network side to the device side—for example to a customization client application, thereby reducing the processing burden on the core network and making network operations (e.g., core computing functions) more efficient. One way of seeing this is to understand that powerful processors on the UEs will be recruited to perform the heavy lifting of analyzing and decision making rather than having the same processing performed for tens of millions of UEs through processing on servers in the core network. This innovation recruits tens of millions of UEs for performing this processing—which does not diminish or reduce the function of those UEs as those processors were not fully loaded in any case. This can result in considerable savings of capital equipment in reduced number of server computing resources needed to provide the desired customization processing.
In an embodiment, the definitions are different policies that define which of a plurality of feature customizations are to be performed for the UE having the subject GID. For some UEs a feature may not be customizable but instead may be hard coded and/or preconfigured in firmware by the OEM. For other UEs, by contrast, the same feature may be customizable during activation by the wireless service provider and possibly yet later by the customer. These differences—a feature is customizable on one UE model while the same feature is uncustomizable on a second UE model—can be defined in the policies, for example a feature customization policy overlay as discussed further hereinafter.
In an embodiment, the definitions are coded as a bit map of ones and zeros, each bit position associated with one feature customization. If a bit position holds a ‘1’ value, the corresponding feature customization is to be performed (i.e., the corresponding UE feature is to be customized); if the bit position holds a ‘0’ value, the corresponding feature customization is NOT to be performed (i.e., the corresponding UE feature is NOT to be customized). The bit map may be referred to as a feature customization policy overlay. By crafting the universal customization manifest, for example by an IT worker, the customization actions desired for each of a plurality of different GIDs can be defined and stored in the single universal customization manifest, along with all the different customization scripts, remote references (IP addresses, URLs, etc.), or data that allows each of the possible features to be enabled and/or activated on the UE. In an embodiment, the customization logic, customization scripts, references, and data may be provided in a compressed file container, for example in a ZIP file.
It is noted that the UE can be activated not only on the occasion of a first use when first delivered from an OEM. The UE can be reactivated on the occasion, for example, of migration of a subscription account from a first wireless communication service provider to a second wireless communication service provider. The UE can be reactivated on the occasion, for example, of migrating from a first brand associated with a carrier network to a second brand associated with the same carrier network. The same customization process described above can apply in these circumstances as well. It is contemplated that this customization framework can extend the concept of the GID to include additional identification information, for example maintenance release (MR) identities. Thus, a UE could undergo the customization process and apply a different customization overlay based on a changed GID resulting from an MR update of the UE.
In the circumstance that the UE is being reactivated or re-customized, user feature customizations may be present on the UE. ‘User feature customizations’ may affect some of the same features, settings, or configurations set during activation customization but may be performed by users and may be performed at times unrelated to activation, reactivation, rebranding, and changing of wireless service provider. Depending on the feature, the wireless service provider may consent to retaining the user feature customization for the feature on the UE but for other features may not retain the user feature customization but may instead replace the user feature customization with a preferred customization.
In an embodiment, the willingness to retain user feature customizations versus replace user feature customizations may be indicated in a user feature customization override overlay in the definitions of customization actions in the manifest, where the override overlay is referenced by the same GID that references the feature overlay. Each feature customization field of the feature customization policy is likewise represented in the feature customization override overlay. In an embodiment, the feature customization override overlay is a bit map such that each bit position of the feature customization override overlay relates to the same customization feature associated with the corresponding bit position in the feature customization policy. In an embodiment, the feature customization policy overlay associated with the GID is analyzed to determine feature customizations to perform. Then the user feature customization override overlay associated with the GID is analyzed to determine whether user feature customizations are overridden for specific features (override being active means that a user feature customization for the subject feature will be overridden and the feature customization preferred by the carrier will be activated). If a feature customization is not overridden and the user has customized the subject feature, the user customization is left in place and the carrier customization of that feature is not applied. If a feature customization is not overridden but the user has not customized the subject feature, the customization client may then activate or install the feature customization preferred by the carrier. The customization client may determine if a user customization has been provided by making a call to an operating system of the UE or by itself providing a monitoring function to track and log such user customization actions.
In an embodiment, the definitions of customization actions may further comprise a plurality of feature configuration overlays. Generally speaking, these feature configuration overlays can be used to define which of two or more alternative configurations is to be established for a corresponding customization feature. For example, for a customization feature that controls whether or not a specific messaging application is to be enabled or disabled for use on the UE, the feature customization policy overlay selected by the GID of the UE may indicate the messaging application is to be enabled but not indicate which of a plurality of different message length restrictions is to be configured for the subject messaging application. One or more feature configuration overlays may be referenced by the same GID to provide this further configuration information. For example, a single feature configuration overlay may have a single bit position of a bit map associated to the subject messaging application feature and a ‘0’ value may indicate a maximum message length of 200 characters while a ‘1’ value may indicate a maximum message length of 300 characters. Alternatively, two feature configuration overlays may have two bit positions—one in each feature configuration overlay—that are associated to the subject messaging application feature. In this case, the feature configuration overlays can indicate which of four different maximum message lengths may be configured. For example a ‘00’ value may correspond to a 150 character maximum message length, a ‘01’ value may correspond to a 200 character maximum message length, a ‘10’ value may correspond to a 300 character maximum message length, and a ‘11’ value may correspond to a 450 character maximum message length.
Different GIDs may reference different definitions of customization actions that comprise different numbers of feature configuration overlays. A first definition may have two feature configuration overlays, a second definition may have one feature configuration overlay, a third definition may have four feature configuration overlays. The significance of the encoding of the feature configuration overlays can be defined in the universal customization manifest, for example as part of configuration data. The encoding of the feature configuration overlays may select different operational modes of the corresponding features that are to be made active on the UE. The encoding of the feature configuration overlays, may in part map to different configuration scripts or configuration logic that are to be executed for customization of an associated feature. Configuring the feature may comprise executing the selected or mapped to configuration scripts and/or configuration logic.
For further details on a customization client, see U.S. patent application Ser. No. 15/265,833, filed Sep. 14, 2016, entitled “System and Method of Mobile Phone Customization Based on Universal Manifest,” by Jagannath Ghoshal, et al., which is incorporated herein by reference in its entirety.
Turning now to
The network 112 may comprise one or more private networks, one or more public networks, and/or a combination thereof. The UE 102 may be a mobile phone, a smart phone, a personal digital assistant (PDA), a media player, a headset computer, a wearable computer, a laptop computer, a notebook computer, or a tablet computer. The cell site 110 may establish communication links with the UE 102 according to a wireless communication protocol such as one or more of a long term evolution (LTE), a code division multiple access (CDMA), a global system for mobile communication (GSM), and/or a worldwide interoperability for microwave access (WiMAX) wireless communication protocol. The cell site 110 may communicatively couple the UE 102 to the network 112 so the UE 102 may perform voice calls with other UEs 122 via other cell sites 120 or may perform data communication sessions with servers coupled to the network, for example with content servers (not shown).
The UE 102 may undergo a customization process at one or more different phases in a life cycle of the device, for example upon initial activation (when first brought into service after shipping by the OEM) or upon reactivation for use on a different carrier network or for use under a different brand. The customization client application 106 may request a customization manifest 118a from the customization server application 116 executing on the customization server 114. The customization manifest 118a may comprise feature customization policy definitions and customization inputs for a wide variety of different UEs, for example different models of UE, UEs having different operating systems, UEs associated with different wireless service provider brands, UEs having subscriptions with different wireless carrier networks. A workstation 124 may be used, for example by an information technology (IT) worker, to create and extend the customization manifest 118a. For example, as new models of UEs are conceived of and released, new feature customization policy definitions and customization inputs associated with these new models of UEs may be added to the customization manifest 118a.
The customization manifest 118a may be referred to as a universal customization manifest because the same manifest is intended to contain feature customization policies, user feature customization override information, feature configuration definitions, and customization inputs for a universal set of different models of UEs (with the possible exclusion of iOS operating system based UEs). It is understood that the term “universal customization manifest” does not mean the manifest does not change over time—as new models of UEs are conceived and deployed to the customer market—but that at any given time, the same manifest is used by an extensive variety of UE models.
Upon request by the UE 102, the customization server application 116 may send a copy of the customization manifest 118a to the UE 102 as customization manifest 118b. The UE 102 receives the customization manifest 118b wirelessly via the cellular radio transceiver 104 or alternatively via a short range radio transceiver (not shown) such as a WiFi transceiver, a Bluetooth® transceiver, or another short range radio transceiver. The only difference between the manifest 118a and the manifest 118b, at least at the time that the UE 102 receives the manifest 118b, is that manifest 118b is stored on the UE 102 and manifest 118a is stored on the server 114. The customization client application 106 then searches in the customization manifest 118b using the GID 108 stored in the UE 102 for relevant feature customization policies, user feature customization override information, and feature configuration definitions that it applies or configures on the UE 102, as discussed herein.
Turning now to
The customization directives block 130 comprises a plurality of customization directives 132. Each customization directive 132 comprises a group identity (GID) key 134 or reference and a feature customization policy overlay 136. In an embodiment, each customization directive 132 further comprises a user feature customization override overlay 138. Alternatively, some customization directives 132 may comprise a user feature customization override overlay 138 and other customization directives 132 may not comprise a user feature customization override overlay 138.
With reference again to
It can be the case that the aggregated identities in the GID 108 match to a plurality of GID keys 134. The GID keys 134 may comprise portions of the full GID 108. Recall that the GID 108 is an aggregate of multiple identities of the UE 102, for example one or more of a mobile network code (MNC), a brand identity, a maintenance release (MR) identity, and possibly other identity components. The MNC of the GID 108 may match a GID key 134 comprising only the MNC. Thus, the searching performed by the customization client application 106 can search the GID keys 134 using any portion of combination or portions of the aggregate identity represented by the GID 108.
Turning now to
Some customization directives 132 of the second universal customization manifest 118B may not comprise feature configuration overlays 144 while other customization directives 132 of the fourth universal customization manifest 118d do comprise feature configuration overlays 144. The feature configuration overlays 144 may be used by the customization client application 106 to configure features that are indicated as enabled by the customization policy overlay 136, for example to configure a maximum number of characters of a particular messaging service that is enabled. It is noted that the feature configuration overlays 144, as part of customization directives 132, are also identified or referenced by an associated GID 134. The feature configuration overlays 144 may identify configuration scripts and/or configuration logic to execute to configure an associated feature of the UE 102. The feature configuration overlays 144 may identify operation modes of the associated feature or features on the UE 102.
Turning now to
In an embodiment, the feature customizations contemplated by the customization policy overlay 136 may be partitioned into feature customizations associated with voice mail customization, branding customization, messaging customization, browser customization, network parameters customization, contacts and dialers customization, and application management customization. In an embodiment, the feature customizations contemplated may be categorized differently. The voicemail customization category may comprise a voicemail speed dial feature customization. The branding customization category may comprise a branded startup animation feature customization, a branded startup sound feature customization, a branded shutdown animation feature customization, a branded shutdown sound feature customization, and a brand name feature customization. The messaging customization category may comprise feature customizations for IP address, port, URL, email signature, email synchronization schedule, and other feature customizations. The browser customization category may comprise feature customizations for homepage, bookmarks, search engine, and other feature customizations.
The network parameters customization category may comprise feature customizations for roaming menu, roaming preference, USB tetherings, Bluetooth® tetherings, and other feature customizations. The contacts and dialers customization category may comprise feature customizations for customer care contact, carrier contacts, dialer call intercepts, and other feature customizations. Other feature customizations may include customization of hardware diagnostics, customization of GPS. It is understood that the list of feature customizations in different embodiments may vary from that described above.
Turning now to
Turning now to
Turning now to
Turning now to
At block 204, the UE receives a customization manifest, where the customization manifest identifies a plurality of feature customization policies and a plurality of user feature customization override policies, where each feature customization policy defines which of a predefined number of feature customizations are to be active for a UE, and each user feature customization override policy defines which of the predefined number of feature customizations are to mandatorily be applied notwithstanding preexisting user customizations of the associated feature, whereby the customization manifest defines different feature customization policies to be applied to different UE models and for different wireless communication service brand identities and one of overrides or permits retaining preexisting user customizations of features. For example, the UE 102 receives the customization manifest 118.
The customization manifest received by the UE may correspond substantially with the customization manifest 118 described with reference to
At block 206, a customization client application executing on the UE searches in the customization manifest using the GID of the UE as a search key. The customization client application is triggered to execute by one of a UE activation process, a UE rebranding process, or a UE change of service provider. For example, the customization client application 106 searches in the customization manifest using the GID or a portion of the GID. For example, the customization client application 106 may deem a match of any single component of multiple components of the GID as a search match. The customization client application 106 may deem a match of any combination of two or more components of the multiple components of the GID as a search match. At block 208, the customization client application finds and selects a feature customization policy in the customization manifest that matches the GID of the UE. In some embodiments, the processing of block 206 and block 208 may be combined as a single step. It is understood, however, that the processing of block 208 may be repeated more than one time. Said in other words, the search of block 206 may result in two or more matches to the GID or partial matches to the GID. At block 210, the customization client application reads the selected feature customization policy from the customization manifest.
At block 212, the customization client application finds and selects a user feature customization override policy from the customization manifest that matches the GID of the UE. In some embodiments, the processing of block 206 and block 212 may be combined in a single step. At block 214, the customization client application reads the selected user feature customization override policy from the customization manifest. At block 216, the customization client application identifies preexisting user feature customizations on the UE. For example, the customization client 106 executes an operating system call on the UE 102 to determine previous customizations that have been performed by a user of the UE 102. Such user customizations may be discriminated from both system customizations (i.e., maintenance release (MR) types of changes that may be mediated by an original equipment manufacturer (OEM) of the UE) and carrier customizations (i.e., customizations initiated on the UE by the wireless communication service provider or carrier) by the operating system.
At block 218, based on reading the selected feature customization policy, based on reading the selected user feature customization override policy, and based on identifying preexisting user feature customizations on the UE, the customization client customizes one or more features of the UE and does not customize one or more features of the UE that is identified for customization in the selected feature customization policy for which a preexisting user customization is identified and for which the selected user feature customization override policy allows retaining a preexisting user customization, where the customizing takes place as part of one of a UE activation process, a UE rebranding process, or a UE change of service provider.
The processing of block 218 may be repeated for each of a plurality of feature customization opportunities or positions of the customization policy overlay of the customization manifest 118. For example, the customization client 106 executing on the UE 102 may read the first feature customization bit 150 of the customization policy overlay 136, determine that the value is “1,” and accordingly perform a customization of the feature associated with the first feature customization bit 150 on the UE 102, based on one or more of feature customization inputs 142 stored in the compressed file container 140. These feature customization inputs 142 comprise one or more of a corresponding customization logic, customization script, Internet protocol (IP) address, uniform resource locator (URL), and configuration data. This may, for example, involve customizing or configuring a voicemail speed dial number for the UE 102. Notwithstanding this description, if the first override bit 160 had a ‘0’ value (in the example in
Next, the customization client 106 may read the second feature customization bit 151 of the feature customization policy overlay 136, determine that the value is “1,” and accordingly perform a customization of the feature associated with the second feature customization bit 151 on the UE 102 based on one or more of a corresponding customization logic, customization script, reference, and data stored in the compressed file container 140 of the customization manifest 118 (provided the second override bit 161 did not have a ‘0’ value and/or a preexisting user customization did not exist). Next the customization client 106 may read the third feature customization bit 152 of the feature customization policy overlay 136, determine that the value is “0,” and accordingly perform no customization of the feature associated with the third feature customization bit 152 on the UE 102. The customization client 106 may continue reading and customizing or not customizing the remainder of UE features based on the contents of the feature customization policy overlay 136 found at block 208 and based on the user feature customization override overlay 138 found at block 212.
After completion of the processing of block 212, the processing may return to repeat the processing of blocks 206, 208, 210, 212, 214, 216, 218. Said in other words, additional customization directives blocks 130 may be found in the searching of blocks 206 and 208 to at least partially match the GID 108 stored in the UE 102. These additional successful searches would result in repeating the processing of blocks 210, 212, 214, 216, 218. It is understood that at least some of the processing of the blocks in method 200 may be performed in different orders. For example, the processing of block 216 may be performed at any point before the processing of block 218, for example before the processing of block 202, before the processing of block 204, before the processing of block 206, or at other places. The processing of blocks 212 and 214 may be performed the processing of blocks 208 and 210. Yet other rearrangements of processing blocks may be feasible and desirable.
In an embodiment, the processing of each feature customization bit read from the feature customization policy overlay 136 of the selected customization directives block 130 may further be based on the value contained in a corresponding user feature customization override bit read from the associated user feature customization override overlay 138. If the corresponding override bit has a value of “1,” the customization of the subject feature is performed if the associated feature customization bit. If, however, the corresponding override bit has a value of “0,” the customization of the subject feature is performed if the associated feature customization bit is “1” and if there has been no user feature customization of the associated feature. If, in this case, there is a user feature customization of the associated feature, this user feature customization is retained.
It is understood that the method 200 may comprise other actions and/or other processing blocks not illustrated in
The DSP 502 or some other form of controller or central processing unit operates to control the various components of the UE 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 UE 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 UE 400 to communicate wirelessly with other nearby handsets and/or wireless base stations. In an embodiment, the UE 400 may comprise a near field communication (NFC) transceiver. The NFC transceiver may be used to complete payment transactions with point-of-sale terminals or other communications exchanges. In an embodiment, the UE 400 may comprise a radio frequency identify (RFID) reader and/or writer device.
The switches 528 may couple to the DSP 502 via the input/output interface 518 to provide one mechanism for the user to provide input to the UE 400. Alternatively, one or more of the switches 528 may be coupled to a motherboard of the UE 400 and/or to components of the UE 400 via a different path (e.g., not via the input/output interface 518), for example coupled to a power control circuit (power button) of the UE 400. The touch screen display 530 is another input mechanism, which further displays text and/or graphics to the user. The touch screen LCD controller 532 couples the DSP 502 to the touch screen display 530. The GPS receiver 538 is coupled to the DSP 502 to decode global positioning system signals, thereby enabling the UE 400 to determine its position.
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.
Additionally, after the system 380 is turned on or booted, the CPU 382 may execute a computer program or application. For example, the CPU 382 may execute software or firmware stored in the ROM 386 or stored in the RAM 388. In some cases, on boot and/or when the application is initiated, the CPU 382 may copy the application or portions of the application from the secondary storage 384 to the RAM 388 or to memory space within the CPU 382 itself, and the CPU 382 may then execute instructions that the application is comprised of. In some cases, the CPU 382 may copy the application or portions of the application from memory accessed via the network connectivity devices 392 or via the I/O devices 390 to the RAM 388 or to memory space within the CPU 382, and the CPU 382 may then execute instructions that the application is comprised of. During execution, an application may load instructions into the CPU 382, for example load some of the instructions of the application into a cache of the CPU 382. In some contexts, an application that is executed may be said to configure the CPU 382 to do something, e.g., to configure the CPU 382 to perform the function or functions promoted by the subject application. When the CPU 382 is configured in this way by the application, the CPU 382 becomes a specific purpose computer or a specific purpose machine.
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 that promote radio communications using protocols such as code division multiple access (CDMA), global system for mobile communications (GSM), long-term evolution (LTE), worldwide interoperability for microwave access (WiMAX), near field communications (NFC), radio frequency identity (RFID), 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), flash drive, 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 system 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.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6131024 | Boltz | Oct 2000 | A |
| 6445914 | Findikli et al. | Sep 2002 | B1 |
| 6753887 | Carolan et al. | Jun 2004 | B2 |
| 6889040 | Koo | May 2005 | B1 |
| 7027773 | McMillin | Apr 2006 | B1 |
| 7165191 | Vakrat | Jan 2007 | B1 |
| 7260382 | Lamb et al. | Aug 2007 | B1 |
| 7266371 | Amin et al. | Sep 2007 | B1 |
| 7409208 | Clare et al. | Aug 2008 | B1 |
| 7493111 | Knowles | Feb 2009 | B2 |
| 7530079 | Stubbs et al. | May 2009 | B2 |
| 7817988 | Kruis et al. | Oct 2010 | B2 |
| 7904895 | Cassapakis et al. | Mar 2011 | B1 |
| 7991988 | Chen | Aug 2011 | B2 |
| 8107926 | Goto | Jan 2012 | B2 |
| 8185097 | Vanderlinden et al. | May 2012 | B2 |
| 8185101 | Wiseman et al. | May 2012 | B1 |
| 8249654 | Zhu | Aug 2012 | B1 |
| 8260281 | Urbanek | Sep 2012 | B2 |
| 8401538 | Urbanek | Mar 2013 | B2 |
| 8401595 | Zhu et al. | Mar 2013 | B2 |
| 8433953 | Gaudette et al. | Apr 2013 | B1 |
| 8442521 | Fleischman et al. | May 2013 | B2 |
| 8468164 | Paleja et al. | Jun 2013 | B1 |
| 8522343 | Hernacki | Aug 2013 | B2 |
| 8571536 | Urbanek | Oct 2013 | B2 |
| 8612967 | Delker | Dec 2013 | B1 |
| 8626165 | Narasimhan et al. | Jan 2014 | B1 |
| 8639245 | Shi et al. | Jan 2014 | B2 |
| 8666383 | Mauer et al. | Mar 2014 | B1 |
| 8699377 | Veillette | Apr 2014 | B2 |
| 8819188 | Blatherwick et al. | Aug 2014 | B2 |
| 8825039 | Mizuguchi | Sep 2014 | B2 |
| 8855012 | Suri | Oct 2014 | B1 |
| 8909211 | Huq et al. | Dec 2014 | B2 |
| 8909291 | Spanel et al. | Dec 2014 | B1 |
| 8938436 | Kozempel | Jan 2015 | B2 |
| 8965366 | Somayajula et al. | Feb 2015 | B1 |
| 9020479 | Somayajula et al. | Apr 2015 | B1 |
| 9026105 | Shipley et al. | May 2015 | B2 |
| 9042877 | Ghoshal et al. | May 2015 | B1 |
| 9098368 | Delker | Aug 2015 | B1 |
| 9100769 | Annan et al. | Aug 2015 | B2 |
| 9100819 | Annan et al. | Aug 2015 | B2 |
| 9124719 | Inlow et al. | Sep 2015 | B2 |
| 9125037 | Masterson et al. | Sep 2015 | B2 |
| 9143924 | Abou-El-Ella et al. | Sep 2015 | B1 |
| 9161209 | Ghoshal et al. | Oct 2015 | B1 |
| 9161325 | Urbanek | Oct 2015 | B1 |
| 9170870 | Masterson et al. | Oct 2015 | B1 |
| 9198027 | Urbanek | Nov 2015 | B2 |
| 9204239 | Sumner | Dec 2015 | B1 |
| 9204286 | Annan et al. | Dec 2015 | B1 |
| 9208513 | Mauer et al. | Dec 2015 | B1 |
| 9226133 | Spanel et al. | Dec 2015 | B1 |
| 9280483 | Ghoshal et al. | Mar 2016 | B1 |
| 9301081 | Callan et al. | Mar 2016 | B1 |
| 9304668 | Rezende et al. | Apr 2016 | B2 |
| 9307400 | Blinn et al. | Apr 2016 | B1 |
| 9313643 | Ghoshal et al. | Apr 2016 | B1 |
| 9319270 | Bestmann et al. | Apr 2016 | B2 |
| 9357378 | Delker et al. | May 2016 | B1 |
| 9363622 | Ahn et al. | Jun 2016 | B1 |
| 9392395 | Indurkar | Jul 2016 | B1 |
| 9398462 | Delker et al. | Jul 2016 | B1 |
| 9420399 | Urbanek | Aug 2016 | B2 |
| 9420496 | Indurkar | Aug 2016 | B1 |
| 9426641 | Ghoshal et al. | Aug 2016 | B1 |
| 9439025 | Ghoshal et al. | Sep 2016 | B1 |
| 9451446 | Spanel et al. | Sep 2016 | B2 |
| 9532211 | Sumner | Dec 2016 | B1 |
| 9549009 | Annan et al. | Jan 2017 | B1 |
| 9603009 | Indurkar | Mar 2017 | B1 |
| 9681251 | Ahn et al. | Jun 2017 | B1 |
| 9743271 | Urbanek | Aug 2017 | B2 |
| 9794727 | Delker et al. | Oct 2017 | B1 |
| 9913132 | Ghoshal et al. | Mar 2018 | B1 |
| 20020091931 | Quick, Jr. et al. | Jul 2002 | A1 |
| 20020142783 | Yoldi et al. | Oct 2002 | A1 |
| 20030023514 | Adler et al. | Jan 2003 | A1 |
| 20030031235 | Kim et al. | Feb 2003 | A1 |
| 20030188160 | Sunder et al. | Oct 2003 | A1 |
| 20030217145 | Leung et al. | Nov 2003 | A1 |
| 20040033798 | Robin et al. | Feb 2004 | A1 |
| 20040092248 | Kelkar et al. | May 2004 | A1 |
| 20040093109 | O'Connor et al. | May 2004 | A1 |
| 20040116163 | Kim et al. | Jun 2004 | A1 |
| 20040137890 | Kalke | Jul 2004 | A1 |
| 20040137891 | Clark et al. | Jul 2004 | A1 |
| 20040254975 | Teh et al. | Dec 2004 | A1 |
| 20040261041 | Parakkuth et al. | Dec 2004 | A1 |
| 20050020308 | Lai | Jan 2005 | A1 |
| 20050079855 | Jethi et al. | Apr 2005 | A1 |
| 20050079863 | Macaluso | Apr 2005 | A1 |
| 20050085222 | Przybilski et al. | Apr 2005 | A1 |
| 20050114114 | Rudolph | May 2005 | A1 |
| 20050119001 | Watanabe | Jun 2005 | A1 |
| 20050164737 | Brown | Jul 2005 | A1 |
| 20050188262 | Rosenman et al. | Aug 2005 | A1 |
| 20050197098 | Trossen | Sep 2005 | A1 |
| 20050203703 | Chang | Sep 2005 | A1 |
| 20060025151 | Karaoguz et al. | Feb 2006 | A1 |
| 20060121894 | Ganesan | Jun 2006 | A1 |
| 20060126620 | Bonar et al. | Jun 2006 | A1 |
| 20060135144 | Jothipragasam | Jun 2006 | A1 |
| 20060154651 | Knowles | Jul 2006 | A1 |
| 20060203722 | Oommen | Sep 2006 | A1 |
| 20060208071 | Chang et al. | Sep 2006 | A1 |
| 20060235944 | Haslam | Oct 2006 | A1 |
| 20060236325 | Rao et al. | Oct 2006 | A1 |
| 20060242150 | Jogand-Coulomb et al. | Oct 2006 | A1 |
| 20060246949 | Gupta et al. | Nov 2006 | A1 |
| 20070004404 | Buckley et al. | Jan 2007 | A1 |
| 20070015538 | Wang | Jan 2007 | A1 |
| 20070043667 | Qawami et al. | Feb 2007 | A1 |
| 20070082655 | Link et al. | Apr 2007 | A1 |
| 20070099599 | Smith et al. | May 2007 | A1 |
| 20070129057 | Xu et al. | Jun 2007 | A1 |
| 20070130156 | U. Tenhunen et al. | Jun 2007 | A1 |
| 20070165654 | Chai et al. | Jul 2007 | A1 |
| 20070169084 | Frank et al. | Jul 2007 | A1 |
| 20070190939 | Abel | Aug 2007 | A1 |
| 20070192854 | Kelley et al. | Aug 2007 | A1 |
| 20070197234 | Gill et al. | Aug 2007 | A1 |
| 20070250645 | Meadows et al. | Oct 2007 | A1 |
| 20070254635 | Montelius | Nov 2007 | A1 |
| 20080022395 | Holtzman et al. | Jan 2008 | A1 |
| 20080039114 | Phatak et al. | Feb 2008 | A1 |
| 20080046583 | Rao | Feb 2008 | A1 |
| 20080046880 | Jun et al. | Feb 2008 | A1 |
| 20080046997 | Wang | Feb 2008 | A1 |
| 20080051076 | OShaughnessy et al. | Feb 2008 | A1 |
| 20080057957 | Altbaum et al. | Mar 2008 | A1 |
| 20080062900 | Rao | Mar 2008 | A1 |
| 20080065753 | Rao | Mar 2008 | A1 |
| 20080109662 | Natarajan et al. | May 2008 | A1 |
| 20080146280 | Sasse et al. | Jun 2008 | A1 |
| 20080155275 | Natarajan et al. | Jun 2008 | A1 |
| 20080160970 | Srinivas Reddy et al. | Jul 2008 | A1 |
| 20080167027 | Gautier et al. | Jul 2008 | A1 |
| 20080171532 | Shieh et al. | Jul 2008 | A1 |
| 20080188210 | Choi et al. | Aug 2008 | A1 |
| 20080225806 | Arian et al. | Sep 2008 | A1 |
| 20080281511 | Miyata | Nov 2008 | A1 |
| 20080298559 | Nanjundaswamy | Dec 2008 | A1 |
| 20080300967 | Buckley et al. | Dec 2008 | A1 |
| 20080318547 | Ballou, Jr. et al. | Dec 2008 | A1 |
| 20090036165 | Brede | Feb 2009 | A1 |
| 20090061840 | Fleischman et al. | Mar 2009 | A1 |
| 20090075592 | Nystrom et al. | Mar 2009 | A1 |
| 20090093242 | Bhalekar et al. | Apr 2009 | A1 |
| 20090094350 | Rive et al. | Apr 2009 | A1 |
| 20090106200 | Salinas et al. | Apr 2009 | A1 |
| 20090124250 | Topaltzas et al. | May 2009 | A1 |
| 20090156190 | Fisher | Jun 2009 | A1 |
| 20090156209 | Franklin et al. | Jun 2009 | A1 |
| 20090217385 | Teow et al. | Aug 2009 | A1 |
| 20090239518 | Feuillette | Sep 2009 | A1 |
| 20090247124 | de Atley et al. | Oct 2009 | A1 |
| 20090259974 | Lin | Oct 2009 | A1 |
| 20090260004 | Datta et al. | Oct 2009 | A1 |
| 20090307763 | Rawlins et al. | Dec 2009 | A1 |
| 20100048193 | Ortion et al. | Feb 2010 | A1 |
| 20100060456 | Forster | Mar 2010 | A1 |
| 20100075669 | Sparks et al. | Mar 2010 | A1 |
| 20100080143 | Topaltzas et al. | Apr 2010 | A1 |
| 20100133335 | Maguid et al. | Jun 2010 | A1 |
| 20100136960 | Knezevic | Jun 2010 | A1 |
| 20100138652 | Sela et al. | Jun 2010 | A1 |
| 20100159876 | Brown et al. | Jun 2010 | A1 |
| 20100159954 | Rahman et al. | Jun 2010 | A1 |
| 20100161724 | Sathyan et al. | Jun 2010 | A1 |
| 20100161928 | Sela et al. | Jun 2010 | A1 |
| 20100167696 | Smith et al. | Jul 2010 | A1 |
| 20100185434 | Burvall et al. | Jul 2010 | A1 |
| 20100190479 | Scott et al. | Jul 2010 | A1 |
| 20100192120 | Raleigh | Jul 2010 | A1 |
| 20100194632 | Raento et al. | Aug 2010 | A1 |
| 20100198939 | Raleigh | Aug 2010 | A1 |
| 20100203864 | Howard | Aug 2010 | A1 |
| 20100207742 | Buhot et al. | Aug 2010 | A1 |
| 20100222031 | Carolan et al. | Sep 2010 | A1 |
| 20100222047 | Vanderlinden et al. | Sep 2010 | A1 |
| 20100250368 | Porco | Sep 2010 | A1 |
| 20100262638 | Fitzgerald | Oct 2010 | A1 |
| 20100291898 | Sanding et al. | Nov 2010 | A1 |
| 20100311391 | Siu et al. | Dec 2010 | A1 |
| 20100311404 | Shi et al. | Dec 2010 | A1 |
| 20100311468 | Shi et al. | Dec 2010 | A1 |
| 20100312794 | Liu | Dec 2010 | A1 |
| 20100325622 | Morton | Dec 2010 | A1 |
| 20100332639 | Diaz et al. | Dec 2010 | A1 |
| 20110003590 | Yoon et al. | Jan 2011 | A1 |
| 20110014913 | Yoon et al. | Jan 2011 | A1 |
| 20110026501 | Sharaga et al. | Feb 2011 | A1 |
| 20110028138 | Davies-Moore et al. | Feb 2011 | A1 |
| 20110030062 | Hsu et al. | Feb 2011 | A1 |
| 20110035421 | Laird-McConnell et al. | Feb 2011 | A1 |
| 20110069702 | Oktay et al. | Mar 2011 | A1 |
| 20110081885 | Sennett et al. | Apr 2011 | A1 |
| 20110086611 | Klein et al. | Apr 2011 | A1 |
| 20110119716 | Coleman, Sr. | May 2011 | A1 |
| 20110136482 | Kaliner | Jun 2011 | A1 |
| 20110138074 | Onda et al. | Jun 2011 | A1 |
| 20110161659 | Himawan et al. | Jun 2011 | A1 |
| 20110165836 | Dixon et al. | Jul 2011 | A1 |
| 20110173685 | Chai et al. | Jul 2011 | A1 |
| 20110202233 | Hatton | Aug 2011 | A1 |
| 20110202680 | Bells et al. | Aug 2011 | A1 |
| 20110202976 | Chow et al. | Aug 2011 | A1 |
| 20110208338 | Eteminan et al. | Aug 2011 | A1 |
| 20110208865 | Knowles et al. | Aug 2011 | A1 |
| 20110222404 | Watson et al. | Sep 2011 | A1 |
| 20110230136 | Washiro | Sep 2011 | A1 |
| 20110258249 | Biggs et al. | Oct 2011 | A1 |
| 20110263294 | Kim et al. | Oct 2011 | A1 |
| 20110294484 | Martin et al. | Dec 2011 | A1 |
| 20110296399 | Tugnawat et al. | Dec 2011 | A1 |
| 20110306318 | Rodgers et al. | Dec 2011 | A1 |
| 20110314129 | Rezaiifar et al. | Dec 2011 | A1 |
| 20120027059 | Zhao et al. | Feb 2012 | A1 |
| 20120030512 | Wadhwa et al. | Feb 2012 | A1 |
| 20120035989 | Abel et al. | Feb 2012 | A1 |
| 20120036282 | Chen et al. | Feb 2012 | A1 |
| 20120046022 | Kalke et al. | Feb 2012 | A1 |
| 20120047227 | Haggerty et al. | Feb 2012 | A1 |
| 20120054022 | Kosashvili | Mar 2012 | A1 |
| 20120077546 | Kawa et al. | Mar 2012 | A1 |
| 20120094684 | Reddy | Apr 2012 | A1 |
| 20120106509 | Klingenbrunn et al. | May 2012 | A1 |
| 20120129513 | van der Laak | May 2012 | A1 |
| 20120129572 | Johnstone et al. | May 2012 | A1 |
| 20120135733 | Cormier et al. | May 2012 | A1 |
| 20120142314 | Mohammed | Jun 2012 | A1 |
| 20120151199 | Shriver | Jun 2012 | A1 |
| 20120158580 | Eram et al. | Jun 2012 | A1 |
| 20120203824 | Oommen | Aug 2012 | A1 |
| 20120208511 | Vanderlinden et al. | Aug 2012 | A1 |
| 20120230587 | Arseneau | Sep 2012 | A1 |
| 20120260095 | Von Hauck et al. | Oct 2012 | A1 |
| 20120276872 | Knauth et al. | Nov 2012 | A1 |
| 20120282891 | Mohammed et al. | Nov 2012 | A1 |
| 20120282924 | Tagg et al. | Nov 2012 | A1 |
| 20120309377 | De Atley et al. | Dec 2012 | A1 |
| 20130010641 | Dinan | Jan 2013 | A1 |
| 20130013671 | Relan et al. | Jan 2013 | A1 |
| 20130023235 | Fan et al. | Jan 2013 | A1 |
| 20130031191 | Bott | Jan 2013 | A1 |
| 20130031234 | Alfano et al. | Jan 2013 | A1 |
| 20130031541 | Wilks et al. | Jan 2013 | A1 |
| 20130041988 | Rodermund et al. | Feb 2013 | A1 |
| 20130046951 | Jones | Feb 2013 | A1 |
| 20130065557 | Zhang et al. | Mar 2013 | A1 |
| 20130065578 | Raleigh et al. | Mar 2013 | A1 |
| 20130072168 | Colucciello et al. | Mar 2013 | A1 |
| 20130080911 | Klemm | Mar 2013 | A1 |
| 20130085914 | McPherson et al. | Apr 2013 | A1 |
| 20130111461 | Zubas et al. | May 2013 | A1 |
| 20130124186 | Donabedian et al. | May 2013 | A1 |
| 20130184029 | Lim et al. | Jul 2013 | A1 |
| 20130196647 | Raleigh et al. | Aug 2013 | A1 |
| 20130198567 | Ahmed et al. | Aug 2013 | A1 |
| 20130222395 | Bias, Jr. | Aug 2013 | A1 |
| 20130275560 | Bestmann et al. | Oct 2013 | A1 |
| 20130281085 | Sen et al. | Oct 2013 | A1 |
| 20130295902 | Justen et al. | Nov 2013 | A1 |
| 20130303142 | Burcham et al. | Nov 2013 | A1 |
| 20130310003 | Sadhvani et al. | Nov 2013 | A1 |
| 20130311836 | Hurst et al. | Nov 2013 | A1 |
| 20130318518 | Paalanen et al. | Nov 2013 | A1 |
| 20130326359 | Beckert et al. | Dec 2013 | A1 |
| 20140024332 | Droste et al. | Jan 2014 | A1 |
| 20140045483 | Whidden | Feb 2014 | A1 |
| 20140068779 | Tan et al. | Mar 2014 | A1 |
| 20140075567 | Raleigh et al. | Mar 2014 | A1 |
| 20140099916 | Mallikarjunan et al. | Apr 2014 | A1 |
| 20140113610 | Ramprasad et al. | Apr 2014 | A1 |
| 20140122563 | Singh et al. | May 2014 | A1 |
| 20140134981 | Park et al. | May 2014 | A1 |
| 20140140507 | Park et al. | May 2014 | A1 |
| 20140342715 | Gu et al. | Nov 2014 | A1 |
| 20140373184 | Mahaffey et al. | Dec 2014 | A1 |
| 20150011311 | Relan et al. | Jan 2015 | A1 |
| 20150017962 | Howard et al. | Jan 2015 | A1 |
| 20150033291 | Nicolau | Jan 2015 | A1 |
| 20150040246 | Yuen et al. | Feb 2015 | A1 |
| 20150071268 | Kennedy et al. | Mar 2015 | A1 |
| 20150094041 | Jung et al. | Apr 2015 | A1 |
| 20150111564 | Urbanek | Apr 2015 | A1 |
| 20150111565 | Urbanek | Apr 2015 | A1 |
| 20150133094 | Lindeman et al. | May 2015 | A1 |
| 20150193217 | Xiang et al. | Jul 2015 | A1 |
| 20150220245 | Wojcik et al. | Aug 2015 | A1 |
| 20150242336 | Loreskar et al. | Aug 2015 | A1 |
| 20150271662 | Lhamon et al. | Sep 2015 | A1 |
| 20150304506 | Zhu et al. | Oct 2015 | A1 |
| 20150312873 | Cormier et al. | Oct 2015 | A1 |
| 20150319178 | Desai et al. | Nov 2015 | A1 |
| 20150331590 | Yasui | Nov 2015 | A1 |
| 20150370428 | Chan et al. | Dec 2015 | A1 |
| 20160029204 | Lalwaney | Jan 2016 | A1 |
| 20160044091 | Doumet | Feb 2016 | A1 |
| 20160105843 | Xue et al. | Apr 2016 | A1 |
| 20160234675 | Ghoshal et al. | Aug 2016 | A1 |
| 20160239317 | Cuddihy et al. | Aug 2016 | A1 |
| 20160255493 | Lihosit | Sep 2016 | A1 |
| 20170150435 | Tagg et al. | May 2017 | A1 |
| 20170295450 | Urbanek | Oct 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 112016000711 | Nov 2017 | DE |
| 2079256 | Jul 2009 | EP |
| 2461613 | Jun 2012 | EP |
| 2292047 | Feb 1996 | GB |
| 201285272 | Apr 2012 | JP |
| 2015505190 | Feb 2015 | JP |
| 5924347 | Apr 2016 | JP |
| 6270066 | Jan 2018 | JP |
| 6273585 | Jan 2018 | JP |
| 6277455 | Jan 2018 | JP |
| 2006039974 | Feb 1996 | KR |
| WO2010135257 | Nov 2010 | WO |
| WO2012078753 | Jun 2012 | WO |
| WO2013169983 | Nov 2013 | WO |
| WO2014020237 | Feb 2014 | WO |
| WO2014046814 | Mar 2014 | WO |
| WO2014113128 | Jul 2014 | WO |
| WO2014123758 | Aug 2014 | WO |
| WO2014123759 | Aug 2014 | WO |
| WO2014158430 | Oct 2014 | WO |
| WO2015030945 | Mar 2015 | WO |
| WO2015060965 | Apr 2015 | WO |
| WO2016130266 | Aug 2016 | WO |
| Entry |
|---|
| FAIPP Pre-Interview Communication dated Mar. 12, 2015, U.S. Appl. No. 13/972,827, filed Aug. 21, 2013. |
| Notice of Allowance dated May 7, 2015, U.S. Appl. No. 13/972,827, filed Aug. 21, 2013. |
| FAIPP Pre-Interview Communication dated Feb. 25, 2016, U.S. Appl. No. 14/820,522, filed Aug. 6, 2015. |
| Notice of Allowance dated May 6, 2016, U.S. Appl. No. 14/820,522, filed Aug. 6, 2015. |
| FAIPP Pre-Interview Communication dated Nov. 20, 2014, U.S. Appl. No. 13/899,566, filed May 21, 2013. |
| Notice of Allowance dated Jan. 22, 2015, U.S. Appl. No. 13/899,566, filed May 21, 2013. |
| FAIPP Pre-Interview Communication dated Oct. 16, 2015, U.S. Appl. No. 14/060,712, filed Oct. 23, 2013. |
| Final Office Action dated Mar. 9, 2016, U.S. Appl. No. 14/060,712, filed Oct. 23, 2013. |
| Advisory Action dated May 3, 2016, U.S. Appl. No. 14/060,712, filed Oct. 23, 2013. |
| FAIPP Pre-Interview Communication dated Nov. 2, 2015, U.S. Appl. No. 14/060,719, filed Oct. 23, 2013. |
| First Action Interview Office Action dated Dec. 14, 2015, U.S. Appl. No. 14/060,719, filed Oct. 23, 2013. |
| Final Office Action dated Feb. 24, 2016, U.S. Appl. No. 14/060,719, filed Oct. 23, 2013. |
| Advisory Action dated Apr. 20, 2016, U.S. Appl. No. 14/060,719, filed Oct. 23, 2013. |
| Office Action dated Jun. 6, 2016, U.S. Appl. No. 14/060,719, filed Oct. 23, 2013. |
| FAIPP Pre-Interview Communication dated Apr. 15, 2015, U.S. Appl. No. 14/085,474 (U.S. Appl. No. 14/060,712), filed Nov. 20, 2013. |
| Notice of Allowance dated May 29, 2015, U.S. Appl. No. 14/085,474, filed Nov. 20, 2013. |
| FAIPP Pre-Interview Communication dated Sep. 29, 2015, U.S. Appl. No. 14/163,035, filed Jan. 24, 2014. |
| Final Office Action dated Feb. 16, 2016, U.S. Appl. No. 14/163,035, filed Jan. 24, 2014. |
| Office Action dated May 10, 2016, U.S. Appl. No. 14/163,035, filed Jan. 24, 2014. |
| FAIPP Pre-Interview Communication dated Mar. 16, 2016, U.S. Appl. No. 13/968,259, filed Aug. 15, 2013. |
| Final Office Action dated Jun. 14, 2016, U.S. Appl. No. 13/968,259, filed Aug. 15, 2013. |
| Notice of Allowance dated Aug. 18, 2016, U.S. Appl. No. 13/968,259, filed Aug. 15, 2013. |
| FAIPP Pre-Interview Communication dated Mar. 4, 2015, U.S. Appl. No. 14/010,518, filed Aug. 27, 2013. |
| Notice of Allowance dated May 8, 2015, U.S. Appl. No. 14/010,518, filed Aug. 27, 2013. |
| FAIPP Pre-Interview Communication dated Apr. 1, 2015, U.S. Appl. No. 14/010,522, filed Aug. 27, 2013. |
| Notice of Allowance dated Jul. 8, 2015, U.S. Appl. No. 14/010,522, filed Aug. 27, 2013. |
| FAIPP Pre-Interview Communication dated Apr. 3, 2015, U.S. Appl. No. 14/010,523, filed Aug. 27, 2013. |
| Notice of Allowance dated Jun. 26, 2015, U.S. Appl. No. 14/010,523, filed Aug. 27, 2013. |
| FAIPP Pre-Interview Communication dated Mar. 10, 2015, U.S. Appl. No. 14/010,524, filed Aug. 27, 2013. |
| Notice of Allowance dated Apr. 28, 2015, U.S. Appl. No. 14/010,524, filed Aug. 27, 2013. |
| Restriction Requirement dated May 21, 2015, U.S. Appl. No. 14/073,321, filed Nov. 6, 2013. |
| FAIPP Pre-Interview Communication dated Aug. 20, 2015, U.S. Appl. No. 14/073,321, filed Nov. 6, 2013. |
| Notice of Allowance dated Nov. 4, 2015, U.S. Appl. No. 14/073,321, filed Nov. 6, 2013. |
| FAIPP Pre-Interview Communication dated Apr. 8, 2015, U.S. Appl. No. 14/157,507, filed Jan. 16, 2014. |
| First Action Interview Office Action dated Oct. 16, 2015, U.S. Appl. No. 14/157,507, filed Jan. 16, 2014. |
| Notice of Allowance dated Feb. 25, 2016, U.S. Appl. No. 14/157,507, filed Jan. 16, 2014. |
| FAIPP Pre-Interview Communication dated Oct. 7, 2015, U.S. Appl. No. 14/075,687, filed Nov. 8, 2013. |
| Notice of Allowance dated Jan. 27, 2016, U.S. Appl. No. 14/075,687, filed Nov. 8, 2013. |
| FAIPP Pre-Interview Communication dated Nov. 19, 2015, U.S. Appl. No. 14/297,429, filed Jun. 5, 2014. |
| First Action Interview Office Action dated Feb. 2, 2016, U.S. Appl. No. 14/297,429, filed Jun. 5, 2014. |
| Notice of Allowance dated Apr. 20, 2016, U.S. Appl. No. 14/297,429, filed Jun. 5, 2014. |
| FAIPP Pre-Interview Communication dated Jul. 15, 2015, U.S. Appl. No. 14/163,041, filed Jan. 24, 2014. |
| Final Office Action dated Jan. 12, 2016, U.S. Appl. No. 14/163,041, filed Jan. 24, 2014. |
| Notice of Allowance dated Apr. 13, 2016, U.S. Appl. No. 14/163,041, filed Jan. 24, 2014. |
| FAIPP Pre-Interview Communication dated Sep. 21, 2015, U.S. Appl. No. 14/231,718, filed Mar. 31, 2014. |
| First Action Interview Office Action dated Jan. 19, 2016, U.S. Appl. No. 14/231,718, filed Mar. 31, 2014. |
| Final Office Action dated Apr. 19, 2016, U.S. Appl. No. 14/231,718, filed Mar. 31, 2014. |
| Advisory Action dated Jun. 28, 2016, U.S. Appl. No. 14/231,718, filed Mar. 31, 2014. |
| Office Action dated Oct. 6, 2016, U.S. Appl. No. 14/231,718, filed Mar. 31, 2014. |
| FAIPP Pre-Interview Communication dated Jul. 8, 2015, U.S. Appl. No. 14/475,399, filed Sep. 2, 2014. |
| Notice of Allowance dated Dec. 4, 2015, U.S. Appl. No. 14/475,399, filed Sep. 2, 2014. |
| Supplemental Notice of Allowability dated Dec. 14, 2015, U.S. Appl. No. 14/475,399, filed Sep. 2, 2014. |
| FAIPP Pre-Interview Communication dated Nov. 4, 2015, U.S. Appl. No. 14/619,677, filed Feb. 11, 2015. |
| Notice of Allowance dated Dec. 11, 2015, U.S. Appl. No. 14/619,677, filed Feb. 11, 2015. |
| Notice of Allowance dated Feb. 3, 2016, U.S. Appl. No. 14/639,056, filed Mar. 4, 2015. |
| Notice of Allowance dated Mar. 11, 2016, U.S. Appl. No. 14/639,060, filed Mar. 4, 2015. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Feb. 29, 2012, PCT/US2011/063736, filed on Dec. 7, 2011. |
| Foreign Communication from a Related Counterpart Application, “Preliminary Report on Patentability”, dated Jun. 20, 2013, PCT/US2011/063736, filed on Dec. 7, 2011. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Jul. 24, 2013, PCT/US13/40278, filed on May 9, 2013. |
| Foreign Communication from a Related Counterpart Application, “Preliminary Report on Patentability,” dated Nov. 20, 2014, PCT/US13/40278, filed on May 9, 2013. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Nov. 14, 2013, PCT/US13/55023, filed on Aug. 15, 2013. |
| Foreign Communication from a Related Counterpart—International Preliminary Report on Patentability, dated Apr. 2, 2015, PCT/US13/55023, filed on Aug. 15, 2013. |
| Foreign Communication from a Related Counterpart Application, International Search Report and Written Opinion dated Jan. 24, 2014, PCT/US13/68981, filed on Nov. 7, 2013. |
| Foreign Communication From a Related Counterpart Application, International Preliminary Report on Patentability dated Jul. 30, 2015, PCT/US13/68981, filed on Nov. 7, 2013. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated May 19, 2014, PCT/US14/13936, filed on Jan. 30, 2014. |
| Foreign Communication from a Related Counterpart Application, International Preliminary Report on Patentability dated Aug. 20, 2015, PCT/US14/13936, filed on Jan. 30, 2014. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated May 14, 2014, PCT/US14/13939, filed on Jan. 30, 2014. |
| Foreign Communication from a Related Counterpart Application, International Preliminary Report on Patentability dated Aug. 20, 2015, PCT/US14/13939, filed on Jan. 30, 2014. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Jun. 3, 2014, PCT/US14/16650, filed on Feb. 16, 2014. |
| Foreign Communication from a Related Counterpart Application, International Preliminary Report on Patentability dated Sep. 24, 2015, PCT/US14/16650, filed on Feb. 16, 2014. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Dec. 17, 2014, PCT/US14/46773, filed on Jul. 16, 2014. |
| Foreign Communication from a Related Counterpart—International Preliminary Report on Patentability, dated Mar. 10, 2016, PCT/US14/46773, filed on Jul. 16, 2014. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Dec. 30, 2014, PCT/US14/56778, filed on Sep. 22, 2014. |
| Foreign Communication from a Related Counterpart—International Search Report and Written Opinion, dated Apr. 4, 2016, PCT/US16/13272, filed on Jan. 13, 2016. |
| Amazon Kindle e-book reader, on public sale 2007, http://en.wikipedia.org/wiki/Amazon_Kindle. last accessed on Apr. 13, 2015. |
| Dummies, “Power Modes on Your Kindle Paperwhite”, http://dummies.com/how-to/content/power-modes-on-your-kindle-paperwhite.html, last accessed on Jul. 31, 2015. |
| Cushings, “Buy Your Kindle At Waterstones? You're Now Locked Into One Sceensaver . . . The Waterstones Logo”, https://www.techdirt.com/articles/20121206/16014421285/buy-your-kindle-waterstones-youre-now-locked-into-one-screensaver-waterstones-logo.shtml, last accessed Aug. 3, 2015. |
| Wikipedia, Extended Display Identification Data, https://en.wikipedia.org/wiki/Extended_Display_Identification_Data, last accessed Aug. 5, 2015. |
| Benjamin, Jeff, “How to change your iPhone carrier logo without jailbreaking,” idownloadblog.com, Dec. 31, 2012. |
| Wikipedia, “Motorola Fone,” Mar. 21, 2016. |
| Mobile Gazette, “Motorola FONE F3 Review,” www.mobilegazette.com, Sep. 16, 2007. |
| Yota Devices, “Hands-on with the YotaPhone: the e-ink Android phone that nobody expected,” New York Times, 2010. |
| Annan, Brandon C., et al., “Electronic Fixed Brand Labeling,” filed Feb. 8, 2013, U.S. Appl. No. 13/763,443. |
| Indurkar, Dhananjay, “System and Method of Branding a Device Independent of Device Activation,” filed Jan. 24, 2014, U.S. Appl. No. 14/163,035. |
| Sumner, Bret D., “Directing Server Connection Based on Location Identifier,” filed Aug. 15, 2013, U.S. Appl. No. 13/968,259. |
| Ahn, Chul Jin, et al., “Customization for Preloaded Applications,” filed Mar. 31, 2014, U.S. Appl. No. 14/231,718. |
| Koller, Gary D., et al., “Out of the Box Experience (OOBE) Country Choice Using Wi-Fi Layer Transmission,” filed Oct. 31, 2014, U.S. Appl. No. 14/530,666. |
| Delker, Jason R., et al. “Network Access Tiered Based on Application Launcher Installation,” filed May 25, 2016, U.S. Appl. No. 15/164,530. |
| Ghoshal, Jagannath, et al., “System and Method of Mobile Phone Customization Based on Universal Manifest,” filed Sep. 14, 2016, U.S. Appl. No. 15/265,833. |
| Notice of Allowance dated Apr. 26, 2012, U.S. Appl. No. 12/962,620, filed Dec. 7, 2010. |
| Notice of Allowance dated Nov. 2, 2012, U.S. Appl. No. 13/556,202, filed Jul. 24, 2012. |
| Notice of Allowance dated Jun. 11, 2013, U.S. Appl. No. 13/752,386, filed Jan. 28, 2013. |
| Foreign Office Action dated Jul. 7, 2015, Japanese Application Serial No. 2013-543310, filed Jul. 7, 2015. |
| Foreign Notice of Allowance dated Mar. 21, 2016, Japanese Application Serial No. 2013-543310, filed Jul. 7, 2015. |
| FAIPP Pre-Interview Communication dated Feb. 25, 2013, U.S. Appl. No. 13/149,505, filed May 31, 2013. |
| First Action Interview Office Action dated May 8, 2013, U.S. Appl. No. 13/149,505, filed May 31, 2013. |
| Notice of Allowance dated Aug. 9, 2013, U.S. Appl. No. 13/149,505, filed May 31, 2013. |
| FAIPP Pre-Interview Communication dated Sep. 22, 2014, U.S. Appl. No. 13/468,028, filed May 9, 2012. |
| First Action Interview Office Action dated Mar. 16, 2015, U.S. Appl. No. 13/468,028, filed May 9, 2012. |
| Final Office Action dated Nov. 4, 2015, U.S. Appl. No. 13/468,028, filed May 9, 2012. |
| Advisory Action dated Jan. 29, 2016, U.S. Appl. No. 13/468,028, filed May 9, 2012. |
| Office Action dated Apr. 4, 2016, U.S. Appl. No. 13/468,028, filed May 9, 2012. |
| FAIPP Pre-Interview Communication dated Aug. 13, 2013, U.S. Appl. No. 13/335,941, filed Dec. 23, 2011. |
| Notice of Allowance dated Oct. 9, 2013, U.S. Appl. No. 13/335,941, filed Dec. 23, 2011. |
| FAIPP Pre-Interview Communication dated Jun. 2, 2015, U.S. Appl. No. 14/152,627, filed Jan. 10, 2013. |
| Notice of Allowance dated Aug. 6, 2015, U.S. Appl. No. 14/152,627, filed Jan. 10, 2013. |
| FAIPP Pre-Interview Communication dated Apr. 23, 2014, U.S. Appl. No. 13/622,234, filed Sep. 18, 2012. |
| Final Office Action dated Sep. 19, 2014, U.S. Appl. No. 13/622,234, filed Sep. 18, 2012. |
| Advisory Action dated Dec. 17, 2014, U.S. Appl. No. 13/622,234, filed Sep. 18, 2012. |
| Office Action dated Mar. 2, 2015, U.S. Appl. No. 13/622,234, filed Sep. 18, 2012. |
| Notice of Allowance dated Jul. 15, 2015, U.S. Appl. No. 13/622,234, filed Sep. 18, 2012. |
| FAIPP Pre-Interview Communication dated Jan. 11, 2016, U.S. Appl. No. 14/877,215, filed Oct. 7, 2015. |
| Notice of Allowance dated Apr. 13, 2016, U.S. Appl. No. 14/877,215, filed Oct. 7, 2015. |
| FAIPP Pre-Interview Communication dated Mar. 19, 2014, U.S. Appl. No. 13/744,847, filed Jan. 18, 2013. |
| Notice of Allowance dated Aug. 4, 2014, U.S. Appl. No. 13/744,847, filed Jan. 18, 2013. |
| FAIPP Pre-Interview Communication dated Mar. 26, 2015, U.S. Appl. No. 14/522,586, filed Oct. 24, 2014. |
| Notice of Allowance dated Jul. 7, 2015, U.S. Appl. No. 14/522,586, filed Oct. 24, 2014. |
| FAIPP Pre-Interview Communication dated Jul. 16, 2014, U.S. Appl. No. 13/744,861, filed Jan. 18, 2013. |
| Notice of Allowance dated Nov. 20, 2014, U.S. Appl. No. 13/744,861, filed Jan. 18, 2013. |
| EP Search Report dated Jul. 7, 2016, European Application Serial No. 13871478.7 filed on Jan. 18, 2013. |
| FAIPP Pre-Interview Communication dated Apr. 8, 2015, U.S. Appl. No. 13/844,104, filed Mar. 15, 2013. |
| Notice of Allowance dated Jul. 16, 2015, U.S. Appl. No. 13/844,104, filed Mar. 15, 2013. |
| FAIPP Pre-Interview Communication dated Oct. 22, 2014, U.S. Appl. No. 13/763,428, filed Feb. 8, 2013. |
| Notice of Allowance dated Mar. 20, 2015, U.S. Appl. No. 13/763,428, filed Feb. 8, 2013. |
| EP Search Report dated May 17, 2016, European Application No. 14749499.1, filed on Feb. 8, 2013. |
| FAIPP Pre-Interview Communication dated Apr. 3, 2014, U.S. Appl. No. 13/763,434, filed Feb. 8, 2013. |
| Final Office Action dated Aug. 19, 2014, U.S. Appl. No. 13/763,434, filed Feb. 8, 2013. |
| Notice of Allowance dated Mar. 26, 2015, U.S. Appl. No. 13/763,434, filed Feb. 8, 2013. |
| EP Search Report dated Aug. 24, 2015, European Application Serial No. 14749462.9, filed on Feb. 8, 2013. |
| FAIPP Pre-Interview Communication dated Apr. 23, 2014, U.S. Appl. No. 13/763,443, filed Feb. 8, 2013. |
| First Action Interview Office Action dated Jun. 16, 2015, U.S. Appl. No. 13/763,443, filed Feb. 8, 2013. |
| Final Office Action dated Aug. 10, 2015, U.S. Appl. No. 13/763,443, filed Feb. 8, 2013. |
| Advisory Action dated Nov. 3, 2015, U.S. Appl. No. 13/763,443, filed Feb. 8, 2013. |
| Office Action dated May 3, 2016, U.S. Appl. No. 13/763,443, filed Feb. 8, 2013. |
| Notice of Allowance dated Sep. 12, 2016, U.S. Appl. No. 13/763,443, filed Feb. 8, 2013. |
| Office Action dated Aug. 7, 2014, U.S. Appl. No. 13/831,504, filed Mar. 14, 2013. |
| Notice of Allowance dated Dec. 29, 2014, U.S. Appl. No. 13/831,504, filed Mar. 14, 2013. |
| Office Action dated Jun. 16, 2015, U.S. Appl. No. 13/899,567, filed May 22, 2013. |
| Notice of Allowance dated Oct. 26, 2015, U.S. Appl. No. 13/899,567, filed May 22, 2013. |
| Japanese Final Office Action dated Aug. 23, 2017, JP Application Serial No. 2015-531933; filed on Feb. 16, 2015. |
| Japanese Office Action dated Sep. 6, 2017, Japanese Application Serial No. 2015-553721, filed on Jan. 18, 2013. |
| Examiners Answer dated Aug. 28, 2017, U.S. Appl. No. 14/060,719, filed Oct. 23, 2013. |
| Office Action dated Oct. 5, 2017, U.S. Appl. No. 14/530,666, filed Oct. 31, 2014. |
| FAIPP Pre-Interview Communication dated Sep. 6, 2017, U.S. Appl. No. 15/063,383, filed Mar. 7, 2016. |
| FAIPP Office Action dated Oct. 16, 2017, U.S. Appl. No. 15/063,383, filed Mar. 7, 2016. |
| Notice of Allowance dated Oct. 27, 2017, U.S. Appl. No. 15/265,833, filed Sep. 14, 2016. |
| Foreign Communication from a Related Counterpart—International Preliminary Report on Patentability, dated Aug. 24, 2017, PCT/US16/13272, filed on Jan. 13, 2016. |
| Japanese Office Action dated Apr. 13, 2017, JP Application Serial No. 2015-531933; filed on Feb. 16, 2015. |
| Notice of Allowance dated Apr. 17, 2017, U.S. Appl. No. 14/060,712, filed Oct. 23, 2013. |
| Final Office Action dated Jan. 26, 2017, U.S. Appl. No. 14/060,719, filed Oct. 23, 2013. |
| Advisory Action dated Mar. 24, 2017, U.S. Appl. No. 14/060,719, filed Oct. 23, 2013. |
| Notice of Allowance dated Feb. 21, 2017, U.S. Appl. No. 14/231,718, filed Mar. 31, 2014. |
| FAIPP Office Action dated Jan. 31, 2017, U.S. Appl. No. 14/530,666, filed Oct. 31, 2014. |
| FAIPP Pre-Interview Communication dated Apr. 10, 2017, U.S. Appl. No. 15/164,530, filed May 25, 2016. |
| EP Search Report dated Oct. 12, 2016, EP International Application No. 11847301.6, filed on Jun. 20, 2013. |
| Final Office Action dated Oct. 26, 2016, U.S. Appl. No. 13/468,028, filed May 9, 2012. |
| Office Action dated Dec. 29, 2016, U.S. Appl. No. 14/060,712, filed Oct. 23, 2013. |
| Notice of Allowance dated Nov. 2, 2016, U.S. Appl. No. 14/163,035, filed Jan. 24, 2014. |
| FAIPP Pre-Interview Communication dated Nov. 4, 2016, U.S. Appl. No. 14/530,666, filed Oct. 31, 2014. |
| Examiner's Answer dated Aug. 14, 2017, U.S. Appl. No. 13/468,028, filed May 9, 2012. |
| EP Notice of Intention to Grant dated May 26, 2017, European Application No. 14749499.1, filed on Feb. 8, 2013. |
| Final Office Action dated May 30, 2017, U.S. Appl. No. 14/530,666, filed Oct. 31, 2014. |
| Advisory Action dated Aug. 10, 2017, U.S. Appl. No. 14/530,666, filed Oct. 31, 2014. |
| Notice of Allowance dated Jun. 14, 2017, U.S. Appl. No. 15/164,530, filed May 25, 2016. |
| Office Action dated May 31, 2017, U.S. Appl. No. 15/265,833, filed Sep. 14, 2016. |
| Urbanek, Robert E., “Delivery of Branding Content and Customizations to a Mobile Communication Device,” filed Jun. 26, 2017, U.S. Appl. No. 15/633,737. |
| Indurkar, Dhananjay, “Mobile Phone Differentiated Set-Up,” filed May 1, 2017, U.S. Appl. No. 15/584,001. |
| Japanese Decision for Grant dated Jan. 9, 2018, Japanese Application Serial No. 2015-553721; filed on Jan. 18, 2013. |
| Japanese Decision for Grant dated Dec. 19, 2017, Japanese Application Serial No. 2015-556971; filed on Jun. 24, 2015. |
| Final Office Action dated Jan. 18, 2018, U.S. Appl. No. 15/063,383, filed Mar. 7, 2016. |
| Notice of Allowance dated Feb. 13, 2018, U.S. Appl. No. 14/530,666, filed Oct. 31, 2014. |
| Japanese Office Action dated Feb. 28, 2018, Japanese Application Serial No. 2015-556972; filed on Jun. 25, 2015. |
| Office Action dated Mar. 13, 2018, U.S. Appl. No. 15/584,001, filed May 1, 2017. |
