U.S. patent application number 10/698665 was filed with the patent office on 2005-05-05 for open update framework for mobile handsets capable of processing firmware and software update packages based on mime-types.
Invention is credited to Chia, Teck, Qumei, Iyad.
Application Number | 20050096025 10/698665 |
Document ID | / |
Family ID | 34550715 |
Filed Date | 2005-05-05 |
United States Patent
Application |
20050096025 |
Kind Code |
A1 |
Qumei, Iyad ; et
al. |
May 5, 2005 |
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.
Inventors: |
Qumei, Iyad; (Huntington
Beach, CA) ; Chia, Teck; (Aliso Viejo, CA) |
Correspondence
Address: |
Christopher, C. Winslade
McAndrews, Held & Malloy, Ltd.
34th Floor
500 West Madison Street
Chicago
IL
60661
US
|
Family ID: |
34550715 |
Appl. No.: |
10/698665 |
Filed: |
October 30, 2003 |
Current U.S.
Class: |
455/418 |
Current CPC
Class: |
G06F 8/65 20130101; H04M
1/72406 20210101; H04M 3/42178 20130101 |
Class at
Publication: |
455/418 |
International
Class: |
H04M 003/00 |
Claims
What is claimed is:
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.
Description
CROSS-REFERENCE TO OTHER APPLICATIONS
[0001] The present application hereby incorporates herein by
reference the complete subject matter of the following U.S.
Provisional patent applications Ser. No. 60/249,606 filed on Nov.
17, 2000, and hereby incorporates herein by reference the complete
subject matter thereof in its entirety.
[0002] The present application also hereby incorporates herein by
reference the complete subject matter of PCT application having
publication number WO/02/41147 A1, and having application number
PCT/US01/44034, filed on Nov. 19, 2001, in its entirety.
FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT
[0003] [Not Applicable]
MICROFICHE/COPYRIGHT REFERENCE
[0004] [Not Applicable]
BACKGROUND OF THE INVENTION
[0005] Electronic devices, such as mobile phones and personal
digital assistants (PDA's), often contain firmware and application
software that are either provided by the manufacturers of the
electronic devices, by telecommunication carriers, or by third
parties. These firmware and application software often contain
software bugs. New versions of the firmware and software are
periodically released to fix the bugs, introduce new features, or
both.
[0006] A generator in a manufacturing environment of an electronic
device such as a mobile handset, or in other software development
environments, generates update packages that are used to update the
firmware of software components. These update packages are
deposited into repository. Unfortunately, several different
generators will be generating different kinds of information. There
is no easy way to process these different kinds of update packages
in mobile handsets without first determining what these update
packages contain, or which application or component in the mobile
handset is capable of handling them. There is no easy way to
distinguish between these update packages that are generated by
different vendors or manufacturers. Mobile handsets that receive
them cannot easily distinguish them from each other in order to
process them appropriately.
[0007] A telecom carrier or a wireless carrier will have to support
storing update packages received from several different sources,
each source potentially employing various different formats for
data to be transferred to the carrier network/wireless network.
Thus, there is currently no easy way to distinguish update packages
delivered to the server environments from other types of
information.
[0008] Other problems and deficiencies of the prior art will become
apparent to one skilled in the art after referencing such art in
view of the reminder of this specification and drawings.
SUMMARY OF THE INVENTION
[0009] Aspects of the present invention may be found in a method
for updating a mobile handset. The method may comprise using a
mime-type associated with the update package to determine if the
update package received is appropriate for updating the mobile
handset. The method may also comprise invoking an appropriate
update agent, based on the mime-type, for updating the mobile
handset.
[0010] In an embodiment of the present invention, invoking an
appropriate update agent comprises determining which of a 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.
[0011] In a further embodiment of the present invention, the mobile
handset comprises firmware, software or configuration and 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.
[0012] In a related embodiment 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.
[0013] In another embodiment of the present invention, the method
further comprises 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.
[0014] In an embodiment of the method, 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.
[0015] In a related embodiment, 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.
[0016] Aspects of the present invention may also be found in an
open update framework with producers and consumers of update
packages wherein the open update framework comprises delivery means
for the delivery of update packages and consumption means for
consuming update packages. The open update framework provides the
consumers of update packages access to a large variety of update
packages in an interoperable manner.
[0017] In an embodiment of the open update framework, the producers
of update packages designate a mime-type with the update packages
and the consumers of update packages employ the mime-type to
determine how to consume the update packages.
[0018] In another embodiment of the open update framework, 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.
[0019] In another embodiment of the open update framework, the
consumers of update packages are update agents in mobile
handsets.
[0020] In another embodiment of the open update framework, the
consumers of update packages are download agents or browsers in
mobile handsets.
[0021] In another embodiment of the open update framework, the
consumers of update packages are handoff agents in mobile
handsets.
[0022] In another embodiment of the open update framework, a
generator 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.
[0023] In another embodiment of the open update framework, a
content server serves as a repository of update packages for
distribution to the mobile handsets and a mime-type is associated
with the update package container created by the generator. In
addition, the content server process the update package container
based upon the mime-type associated update package container.
[0024] Aspects of the present invention may be found in 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. The mobile handset also
comprises 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 and 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.
[0025] In one embodiment of the mobile handset, the update agent is
selected from a plurality of available agents based on the
mime-type of the update package.
[0026] In one embodiment of the mobile handset, the handoff agent
is selected from a plurality of available agents based on the
mime-type of the update package.
[0027] In one embodiment of the mobile handset, the download agent
is selected from a plurality of available agents based on the
mime-type of the update package.
[0028] In one embodiment of the mobile handset, the mime-type of
the update package has an associated magic number that is included
in the update package.
[0029] These and various other advantages and features of novelty
which may characterize the invention are pointed out with
particularity in the claims annexed hereto and that form a part
hereof. However, for a better understanding of the invention, its
advantages, and the objects obtained by its use, reference should
be made to the drawings which form a further part hereof, and to
accompanying descriptive matter, in which there are illustrated and
described specific examples of an apparatus in accordance with the
invention.
BRIEF DESCRIPTION OF THE DIAGRAMS
[0030] FIG. 1 is a perspective diagram of an open update framework
for mobile handsets that is used in a network, such as a carrier
network, that can download update packages employing over-the-air
(OTA) or other techniques and update its firmware and software,
etc., each of the update packages being associated with a
corresponding mime-type; and
[0031] APPENDIX A--New Access Types for Firmware, Software and
Configuration Update Packages.
DETAILED DESCRIPTION OF THE DIAGRAMS
[0032] FIG. 1 is a perspective diagram of an open update framework
105 for mobile handsets 107 that is used in a network, such as a
carrier network, that can download update packages employing
over-the-air (OTA) or other techniques and update its firmware 117
and software 119, 121, etc., each of the update packages being
associated with a corresponding mime-type. In the open update
framework, the mobile handset 107 employs the mime-type to
determine an appropriate agent, such as the update agent 113, that
is capable of processing the update packages 123.
[0033] Typically, an update package is generated by an update
packager/generator 131 and is transferred, employing an update
package container (UPC) format, to a content server/update store
129 that is communicatively coupled to the mobile handset 129,
either directly or via a DM server/delivery server 127. The UPC has
an associated mime-type and, in one embodiment, the content
server/update store 129 processes the UPC based upon its
mime-type.
[0034] In general, the mobile handset 107 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 a
mime-type to determine where the downloaded object 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.
[0035] In one embodiment, the mobile handset employs a mime-type of
an update package and associated parameters (processor, binary
layout, etc.) to determine what type of agent needs to be to
invoked, where to save update package, etc.
[0036] In one embodiment, a plurality of download agents and
handoff agents are available in the mobile handset 107 and the
mobile handset employs the appropriate one of the plurality of
download agents and hand-off agents based upon the mime-type
associated with the update package.
[0037] In one embodiment, a plurality of handoff agents 115 are
available in the mobile handset 107 and the mobile handset employs
the appropriate one of the plurality of handoff agents 115 for
storing the download update package at appropriate locations in
non-volatile or volatile memory of the mobile handset, for
selectively processing or storing the metadata associated with the
update package, and to set flags and other parameters, based upon
the mime-type associated with the downloaded update package.
[0038] In one embodiment, a plurality of update agents are
available in the mobile handset 107 and the mobile handset employs
an appropriate one of the plurality of update agents for processing
the download update package based upon the mime-type associated
with the downloaded update package.
[0039] In one embodiment, the update package 123 is saved in a
pre-determined location by the handoff agent 115 after it has been
downloaded by a download agent or a browser, the pre-determined
location being based on the mime-type associated with the update
package 123.
[0040] In one embodiment, a browser application 121 in the mobile
handset 107 has several update agent plug-ins 113 registered with
it, each update agent plug-in 113 associated with a different
mime-type. The browser invokes the right update agent plug-in 113
based on the mime-type associated with the update package
downloaded from a server or URL.
[0041] The update packager/generator 131 creates one or more update
packages, determines the metadata, associates a mime-type with the
update package generated, populates the metadata with the
mime-type, determines or computes security information such as
signatures and incorporates them into an update package
container/catalog (UPC) that is then communicated to the content
server/update store 129 that serves as a repository for the network
105. The UPC itself has an appropriate mime-type associated with
it. The content server/update store 129 is capable of parsing the
update package container of that mime-type, and is capable of
selectively retrieving all or a subset of the available update
packages, selectively verifying the authenticity of the update
package catalog as well as that of the update packages themselves,
and saving information in a storage, and, in general, behaving as a
repository of update packages and associated metadata.
[0042] Update packages from one or more manufacturers with
generators 131 is sent to the content server/update store 129 for
storage and subsequent dissemination to mobile handsets 107 via the
DM Server/Delivery server 127. The mime-type of the UPC are used by
the content server/update store 129 to process the UPC
appropriately employing the corresponding parsers, security
mechanisms and other utilities.
[0043] In general, the network 105 comprises a generator that is
communicatively coupled to an update store (or some repository) and
employs an UPC that can be used to save information, using an XML
format, the UPC having an associated mime-type. The UPC comprising
one or more update packages for one or more devices and one or more
transitions of versions for each device, is created by the
generator and transferred to the update store/repository, where it
is processed based on its mime-type by the appropriate processing
components. The UPC also comprises metadata information, security
information, etc.
[0044] The present invention is also aimed at defining an open
update framework for the delivery and consumption (for example, by
the client-side agents) in the delivery and consumption chain, a
chain that might include server-side consumers as well as
client-side consumers. This open framework will provide content
creators, producers, distributors and service providers with equal
opportunities in the firmware and software update market. This will
also be to the benefit of the content consumer providing them
access to a large variety of content in an interoperable
manner.
[0045] The present invention is based on two essential concepts:
the definition of a fundamental unit of distribution and
transaction (the update package) and the concept of agents
interacting with the update packages. The update packages can be
considered the "what" of the update framework (e.g., a firmware
update, software update, configuration update) and the user
devices, specifically the agents (download agents, handoff agents,
update agents, etc.) can be considered the "who" of the update
framework.
[0046] The goal of the present invention can thus extended to
include defining the technology needed to support mobile handsets
to exchange, access, consume, trade and otherwise manipulate update
packages in an efficient, transparent and interoperable way.
[0047] Thus, the present invention provides for the standardization
of the process of manipulating update packages for firmware,
software, configuration, etc. by appropriate client-side agents in
the mobile handsets.
[0048] The suggested update framework and associated mime-types
identifies and defines the mechanisms and elements needed to
support the update package delivery chain as described above as
well as the relationships between and the operations supported by
them. Within the parts of the suggested mime-types, these elements
are elaborated by defining the syntax and semantics of their
characteristics, such as interfaces to the functional elements.
[0049] One aspect of the update framework is the definition of
associated security and access control mechanisms. The update
framework provides for the specification of various types of access
rights, such rights can be used to express the agreements between
the update package provider and the end user.
[0050] Although a system and method according to the present
invention has been described in connection with a preferred
embodiment, the invention is not intended to be limited to the
specific form set forth herein, but on the contrary, is intended to
cover such alternative modifications and equivalents, as can be
reasonably included within the spirit and scope of the invention,
as defined by this disclosure and the appended diagrams. It is
intended that the scope of the invention be limited not with this
detailed description, but rather by the claims appended hereto.
[0051] 1 APPENDIX A--New Access Types for Firmware, Software and
Configuration Update Packages
[0052] 1.1 Introduction
[0053] Bitfone would like to seek the registration of new access
types (MIME media types) to facilitate the download and subsequent
update of firmware, software, configuration parameters, etc. in
mobile handsets.
[0054] The content to be downloaded may be:
[0055] a) Firmware update packages
[0056] b) Software update packages
[0057] c) Configuration update packages
[0058] where the term "update packages" refers to a compressed
format (perhaps proprietary) employed for the packaging of
"difference information" and associated metadata, the generation of
which is targeted towards the update of specific devices. Such
update packages may be generated by "Generators" that implement
various proprietary or non-proprietary "differencing algorithms",
etc. and output them into a format that is understood by
corresponding agents (client components) in a mobile handset.
[0059] The dissemination of update packages is typically performed
by web-sites, portals, device management servers in a carrier
network, etc. Mobile handsets or other client devices request
and/or receive the update packages and process them to update the
firmware, software and/or configuration parameters.
[0060] Typically, more than one agents may reside in a mobile
handset (or other similar client devices) that can act upon the
appropriate mime-type to:
[0061] a) field the incoming data of that mime-type
[0062] b) process/render the incoming data of that mime-type
[0063] 1.2 Proposed Mime-Types
[0064] The proposed mime types are of two kinds, vendor specific
(proprietary) and generic.
[0065] 1.2.1 Encoding Considerations
[0066] Update packages, in general, are binary embedded in XML.
Some portions of update packages may be quite readable but many
include within them some digital signature information and many
have large portions encrypted or compressed. This signature and/or
encrypted information is essentially binary and may be base 64
encoded in certain fields. In the future, Content-Transfer-Encoding
may be required.
[0067] 1.2.2 General Security Considerations
[0068] The update packages are interpreted by client-side agents,
such as Bitfone's mProve update agent. The update packages
themselves contain certain security-related information that may be
employed for authentication and integrity checks. However, in
general, update packages from unknown sources should never be
considered as trustable.
[0069] In general, the update packages do not include macros or
code directly executable on the user's system.
[0070] The proposed system is designed so that a secure channel is
not required other than for privacy reasons. Someone observing the
proposed messages may be able to tell who is transferring the
update packages to whom and for what reason but they will not be
able to misuse the update packages or decipher what it contains
based on these messages unless they can break the compression and
cryptosystems employed. Use of the proposed update packages within
a secure envelope will usually eliminate all privacy concerns other
than basic traffic analysis. No currently defined update packages
has any "executable" material.
[0071] 1.2.3 Published Specification
[0072] The specifications for this content-type may be proprietary,
especially the ones that are vendor-specific. For example, mProve
specification are specified by Bitfone, Corp. The registration of
these content-type is intended only to provide a convention for
labeling such proprietary/non-proprietary data type within the
MIME/HTTP environment and does not specify any details about the
content format or semantics, except to refer to the software and
specifications provided by Bitfone, Corp.
[0073] 1.3 New Generic Mime-Types
[0074] The following three generic mime types are recommended:
[0075] `application/firmware-update`
[0076] `application/software-update`
[0077] `application/configuration-update`
[0078] Although these mime-types have not been provided with
parameters, it is conceivable that vendor names or some
vendor-specific information may be provided as a parameter.
[0079] 1.3.1 Application/Firmware-Update
[0080] MIME type name: application
[0081] MIME subtype name: firmware-update
[0082] Required parameters: none
[0083] Optional parameters: none
[0084] Encoding considerations: See section 1.2.1 above
[0085] Security considerations: See section 1.2.2 above
[0086] Published specification: See section 1.2.3 above
[0087] Person & email address to contact for further
information:
[0088] Bindu Rama Rao
[0089] Senior Engineer
[0090] Bitfone Corp.
[0091] (949) 234-7000
[0092] email: brao@bitfone.com
[0093] 1.3.2 Application/Software-Update
[0094] MIME type name: application
[0095] MIME subtype name: software-update
[0096] Required parameters: none
[0097] Optional parameters: none
[0098] Encoding considerations: See section 1.2.1 above.
[0099] Security considerations: See section 1.2.2 above.
[0100] Published specification: See section 1.2.3 above.
[0101] Person & email address to contact for further
information:
[0102] Bindu Rama Rao
[0103] Senior Engineer
[0104] Bitfone Corp.
[0105] (949) 234-7000
[0106] email: brao@bitfone.com
[0107] 1.3.3 Application/Configuration-Update
[0108] MIME type name: application
[0109] MIME subtype name: configuration-update
[0110] Required parameters: none
[0111] Optional parameters: none
[0112] Encoding considerations: See section 1.2.1 above.
[0113] Security considerations: See section 1.2.2 above.
[0114] Published specification: See section 1.2.3 above.
[0115] Person & email address to contact for further
information:
[0116] Bindu Rama Rao
[0117] Senior Engineer
[0118] Bitfone Corp.
[0119] (949) 234-7000
[0120] email: brao@bitfone.com
[0121] 1.4 New Vendor Specific Mime-Types
[0122] The following three vendor-specific mime types are
recommended:
[0123] `application/vnd.bitfone.firmware-update`
[0124] `application/vnd.bitfone.software-update`
[0125] `application/vnd.bitfone.configuration-update`
[0126] 1.4.1 Application/vnd.bitfone.firmware-update
[0127] MIME type name: application
[0128] MIME subtype name: vnd.mprove-firmware-update
[0129] Required parameters: none
[0130] Optional parameters: none
[0131] Encoding considerations: See section 1.2.1 above.
[0132] Security considerations: See section 1.2.2 above.
[0133] Published specification: See section 1.2.3 above.
[0134] Person & email address to contact for further
information:
[0135] Bindu Rama Rao
[0136] Senior Engineer
[0137] Bitfone Corp.
[0138] (949) 234-7000
[0139] email: brao@bitfone.com
[0140] 1.4.2 Application/vnd.bitfone.software-update
[0141] MIME type name: application
[0142] MIME subtype name: vnd.mprove-software-update
[0143] Required parameters: none
[0144] Optional parameters: none
[0145] Encoding considerations: See section 1.2.1 above.
[0146] Security considerations: See section 1.2.2 above.
[0147] Published specification: See section 1.2.3 above.
[0148] Person & email address to contact for further
information:
[0149] Bindu Rama Rao
[0150] Senior Engineer
[0151] Bitfone Corp.
[0152] (949) 234-7000
[0153] email: brao@bitfone.com
[0154] 1.4.3 Application/vnd.bitfone.configuration-update
[0155] MIME type name: application
[0156] MIME subtype name: vnd.mprove-configuration-update
[0157] Required parameters: none
[0158] Optional parameters: none
[0159] Encoding considerations: See section 1.2.1 above.
[0160] Security considerations: See section 1.2.2 above.
[0161] Published specification: See section 1.2.3 above.
[0162] Person & email address to contact for further
information:
[0163] Bindu Rama Rao
[0164] Senior Engineer
[0165] Bitfone Corp.
[0166] (949) 234-7000
[0167] email: brao@bitfone.com
[0168] 1.5 Mime-type For a Container of Update Packages
[0169] A container of update packages, called Update Package
Container (UPC), that contains one or more update packages,
requires a mime-type to enable its automated processing by servers.
The following generic mime-type is proposed:
[0170] Application/Update Package Container
[0171] MIME type name: application
[0172] MIME subtype name: update package container
[0173] Required parameters: none
[0174] Optional parameters: none
[0175] Encoding considerations: See section 1.2.1 above.
[0176] Security considerations: See section 1.2.2 above.
[0177] Published specification: See section 1.2.3 above.
[0178] Person & email address to contact for further
information:
[0179] Bindu Rama Rao
[0180] Senior Engineer
[0181] Bitfone Corp.
[0182] (949) 234-7000
[0183] email: brao@bitfone.com
* * * * *