Open update framework for mobile handsets capable of processing firmware and software update packages based on mime-types

Abstract

Disclosed herein is a mobile handset, part of an open update framework, that uses a mime-type to determine if an update package received is appropriate for an update activity, or is currently supported. In addition, it uses the mime-type to determine where the downloaded update package needs to be stored in non-volatile memory, such as Flash. It also uses the mime-type to invoke an appropriate firmware, software or configuration update agent.

1 . A method for updating a mobile handset using an update package, the method comprising: 
 using a mime-type associated with the update package to determine if the update package received is appropriate for updating the mobile handset; and    invoking an appropriate update agent, based on the mime-type, for updating the mobile handset.    
     
     
         2 . The method of  claim 1  wherein the mobile handset comprises a plurality of update agents and the invoking an appropriate update agent comprises determining which of the plurality of update agents are capable of processing the update package and invoking one of the plurality of update agents that is determined to be capable of processing the update package.  
     
     
         3 . The method of  claim 2  wherein the mobile handset comprises firmware, software or configuration and wherein the invoking one of the plurality of update agents comprises invoking an appropriate one of the plurality of update agents to perform an update of the firmware, software or configuration of the mobile handset.  
     
     
         4 . The method of  claim 3  wherein a different mime-type is associated with update packages that are used to update firmware, update packages that are used to update software and update packages that are used to update configuration in the mobile handset.  
     
     
         5 . The method of  claim 4  further comprising: 
 registering the update agent and associated mime-types such that the mobile handset is able to determine the mime-types supported or processed by the update agent.    
     
     
         6 . The method of  claim 1  wherein the method further comprises using the mime-type associated with the update package to determine where the update package needs to be stored in non-volatile memory.  
     
     
         7 . The method of  claim 1  wherein the method further comprises using the mime-type associated with the update package to determine where the status is stored in the mobile handset following the invoking of an appropriate update agent.  
     
     
         8 . An open update framework with producers and consumers of update packages, the open update framework comprising: 
 delivery means for the delivery of update packages;    consumption means for consuming update packages;    the open update framework that provides the consumers of update packages access to a large variety of update packages in an interoperable manner.    
     
     
         9 . The open update framework of  claim 8  further comprising: 
 the producers of update packages designating a mime-type with the update packages; and    the consumers of update packages employing the mime-type to determine how to consume the update packages.    
     
     
         10 . The open update framework of  claim 9  further comprising: 
 the producers of update packages wherein the producers of update packages are update package generators capable of generating update packages based on an old version of firmware or software and a new version of the firmware and software and associating a mime-type with the update packages.    
     
     
         11 . The open update framework of  claim 9  further comprising: 
 the consumers of update packages wherein the consumers of update packages are update agents in mobile handsets.    
     
     
         12 . The open update framework of  claim 9  further comprising: 
 the consumers of update packages wherein the consumers of update packages are download agents or browsers in mobile handsets.    
     
     
         13 . The open update framework of  claim 9  further comprising: 
 the consumers of update packages wherein the consumers of update packages are handoff agents in mobile handsets.    
     
     
         14 . The open update framework of  claim 9  further comprising a generator that creates one or more update packages, determines the metadata, associates an appropriate mime-type with each of the update packages generated, populates the metadata with the mime-type, determines or computes security information such as signatures, and incorporates them into an update package container.  
     
     
         15 . The open update framework of  claim 11  further comprising 
 a content server that serves as a repository of update packages for distribution to the mobile handsets;    a mime-type associated with the update package container created by the generator;    the content server processing the update package container based upon the mime-type associated update package container.    
     
     
         16 . A mobile handset with non-volatile memory that is capable of processing an update package, the mobile handset comprising: 
 a download agent or a browser that uses a mime-type associated with the update package to determine if the update package received is appropriate for an update activity or is currently supported;    a handoff agent that determines where the update package with an associated mime-type must be stored in non-volatile memory when it is downloaded;    an update agent that uses the mime-type related information to determine if the update package is appropriate for the firmware, software or configuration of the mobile handset.    
     
     
         17 . The mobile handset of  claim 16  wherein the update agent is selected from a plurality of available agents based on the mime-type of the update package.  
     
     
         18 . The mobile handset of  claim 16  wherein the handoff agent is selected from a plurality of available agents based on the mime-type of the update package.  
     
     
         19 . The mobile handset of  claim 16  wherein the download agent is selected from a plurality of available agents based on the mime-type of the update package.  
     
     
         20 . The mobile handset of  claim 16  wherein the mime-type of the update package has an associated magic number that is included in the update package.