FirmwareOvertheAir教程资源-CSDN文库

共2个文件

pdf：2个

需积分: 20 157 浏览量 2014-02-26 10:27:41 上传评论收藏 471KB ZIP 举报

固件空中升级（Firmware Over The Air，简称FOTA）是一种通过无线网络为电子设备更新固件的方法。这种技术在移动通信设备，如智能手机、平板电脑以及物联网（IoT）设备中广泛应用，允许用户和制造商在不物理接触设备的情况下进行系统升级和修复。 Firmware Update Management Object（FUMO）是开放移动联盟（Open Mobile Alliance，简称OMA）提出的一种标准，它定义了如何管理和执行FOTA更新的过程。FUMO的主要目标是确保固件更新的安全、可靠和高效，同时提供了一种统一的框架，以便不同厂商的设备可以相互兼容，降低跨平台升级的复杂性。 OMA-TS-DM_FUMO-V1_0_2-20090828-A.pdf 和 OMA-AD-FUMO-V1_0-20070209-A.pdf 这两个文档分别详细阐述了FUMO的技术规范和应用指南。其中，"TS"通常代表"Technical Specification"，即技术规格，而"AD"可能代表"Application Document"，即应用文档。这两份资料将涵盖FUMO的各个方面，包括但不限于以下关键知识点： 1. **FUMO架构**：FUMO架构通常包含服务器端、网络和客户端三部分。服务器端负责生成、签名和分发更新包；网络提供传输通道；客户端则负责接收、验证和安装更新。 2. **更新流程**：FUMO定义了一个完整的更新流程，包括检测新版本、下载、验证、申请更新、执行更新和确认更新成功等步骤。 3. **安全机制**：为了确保固件更新的安全，FUMO使用数字签名来验证更新包的完整性和来源，防止恶意篡改。 4. **错误处理**：在更新过程中，可能会遇到各种问题，如网络中断、设备故障等。FUMO提供了错误恢复机制，保证在出现问题时能够妥善处理。 5. **资源管理**：考虑到无线网络的带宽限制和设备的电池寿命，FUMO在设计时会考虑资源优化，比如分段下载、后台更新等。 6. **互操作性**：FUMO标准保证不同设备和平台之间的兼容性，使得服务提供商能够为大量不同型号的设备提供一致的更新服务。 7. **状态管理**：FUMO支持设备状态的跟踪和报告，帮助管理员监控更新进度和结果。 8. **用户界面**：虽然FUMO主要关注后台的更新过程，但也会涉及到与用户的交互，比如通知用户何时有可用更新、询问用户是否同意安装等。通过深入学习这两份文档，开发者和管理员可以了解如何实施和管理FOTA更新，包括设置服务器、配置客户端、调试更新过程以及解决可能出现的问题。这些知识对于维护设备的最新状态、提高用户体验和增强设备安全性至关重要。

资源推荐

资源详情

资源评论

收起资源包目录

FOTA.zip （2个子文件）

OMA-AD-FUMO-V1_0-20070209-A.pdf 186KB

OMA-TS-DM_FUMO-V1_0_2-20090828-A.pdf 338KB





Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. [OMA-Template-Spec-20090101-I]

Firmware Update Management Object

Approved Version 1.0.2 – 28 Aug 2009

Open Mobile Alliance

OMA-TS-DM-FUMO-V1_0_2-20090828-A

OMA-TS-DM-FUMO-V1_0_2-20090828-A Page 2 (31)





Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. [OMA-Template-Spec-20090101-I]

Use of this document is subject to all of the terms and conditions of the Use Agreement located at

http://www.openmobilealliance.org/UseAgreement.html.

Unless this document is clearly designated as an approved specification, this document is a work in process, is not an

approved Open Mobile Alliance™ specification, and is subject to revision or removal without notice.

You may use this document or any part of the document for internal or educational purposes only, provided you do not

modify, edit or take out of context the information in this document in any manner. Information contained in this document

may be used, at your sole risk, for any purposes. You may not use this document in any other manner without the prior

written permission of the Open Mobile Alliance. The Open Mobile Alliance authorizes you to copy this document, provided

that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials

and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products

or services. The Open Mobile Alliance assumes no responsibility for errors or omissions in this document.

Each Open Mobile Alliance member has agreed to use reasonable endevors to inform the Open Mobile Alliance in a timely

manner of Essential IPR as it becomes aware that the Essential IPR is related to the prepared or published specification.

However, the members do not have an obligation to conduct IPR searches. The declared Essential IPR is publicly available

to members and non-members of the Open Mobile Alliance and may be found on the “OMA IPR Declarations” list at

http://www.openmobilealliance.org/ipr.html. The Open Mobile Alliance has not conducted an independent IPR review of

this document and the information contained herein, and makes no representations or warranties regarding third party IPR,

including without limitation patents, copyrights or trade secret rights. This document may contain inventions for which you

must obtain licenses from third parties before making, using or selling the inventions. Defined terms above are set forth in

the schedule to the Open Mobile Alliance Application Form.

NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE MADE BY THE OPEN

MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER OR ITS AFFILIATES REGARDING ANY OF

THE IPR’S REPRESENTED ON THE “OMA IPR DECLARATIONS” LIST, INCLUDING, BUT NOT LIMITED TO THE

ACCURACY, COMPLETENESS, VALIDITY OR RELEVANCE OF THE INFORMATION OR WHETHER OR NOT

SUCH RIGHTS ARE ESSENTIAL OR NON-ESSENTIAL.

THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY DIRECT, INDIRECT,

PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN

CONNECTION WITH THE USE OF DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS.

Used with the permission of the Open Mobile Alliance Ltd. Under the terms set forth above.

OMA-TS-DM-FUMO-V1_0_2-20090828-A Page 3 (31)





Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. [OMA-Template-Spec-20090101-I]

Contents

SCOPE ................................................................................................................................................................................ 5

REFERENCES .................................................................................................................................................................. 6

2.1

ORMATIVE

EFERENCES

.......................................................................................................................................... 6

2.2

NFORMATIVE

EFERENCES

....................................................................................................................................... 6

TERMINOLOGY AND CONVENTIONS ...................................................................................................................... 7

3.1

ONVENTIONS

............................................................................................................................................................. 7

3.2

EFINITIONS

................................................................................................................................................................ 7

3.3

BBREVIATIONS

.......................................................................................................................................................... 7

INTRODUCTION ............................................................................................................................................................. 8

FIRMWARE UPDATE MANAGEMENT OBJECT ..................................................................................................... 9

5.1

IRMWARE

PDATE

ANAGEMENT

BJECT

ARAMETERS

..................................................................................... 9

5.1.1

Node: x ................................................................................................................................................................. 9

5.1.2

Node: x/PkgName .............................................................................................................................................. 10

5.1.3

Node: x/PkgVersion ........................................................................................................................................... 10

5.1.4

Node: x/Download ............................................................................................................................................. 10

5.1.5

Node: x/Download/PkgURL .............................................................................................................................. 11

5.1.6

Node: x/Update .................................................................................................................................................. 11

5.1.7

Node: x/Update/PkgData.................................................................................................................................... 11

5.1.8

Node: x/DownloadAndUpdate ........................................................................................................................... 11

5.1.9

Node: x/DownloadAndUpdate/PkgURL ............................................................................................................ 12

5.1.10

Node: x/State ...................................................................................................................................................... 12

5.1.11

Node: x/Ext ........................................................................................................................................................ 13

BEHAVIOR ASSOCIATED WITH THE MANAGEMENT OBJECT ..................................................................... 14

6.1

‘E

XEC

’

OMMAND

.................................................................................................................................................... 16

6.1.1

‘Exec’ Command Semantics for Alternate Download ....................................................................................... 16

6.1.2

‘Exec’ Command Semantics for Update ............................................................................................................ 17

6.1.3

‘Exec’ Command Semantics for DownloadAndUpdate .................................................................................... 17

6.2

SE OF

ENERIC

LERT FOR

OTIFICATIONS

........................................................................................................ 18

6.2.1

URI of Firmware Update Management Object .................................................................................................. 18

6.2.2

Firmware Update Alert Types ............................................................................................................................ 18

6.2.3

Correlator ........................................................................................................................................................... 18

6.2.4

Result Code ........................................................................................................................................................ 19

6.3

UPPORT FOR

PDATE

ACKAGE

OWNLOAD AND

IRMWARE

PDATE

CTIVITIES

.......................................... 20

CLIENT INITIATED FIRMWARE UPDATE (NORMATIVE) ................................................................................ 21

7.1

ENERAL

................................................................................................................................................................... 21

7.1.1

Generic Alert ...................................................................................................................................................... 21

7.1.2

Alert Type .......................................................................................................................................................... 21

7.1.3

URI .................................................................................................................................................................... 21

7.1.4

Data .................................................................................................................................................................... 21

FUMO USAGE (INFORMATIVE) ............................................................................................................................... 22

8.1

IRMWARE

PDATE

ROTOCOL

VERVIEW

........................................................................................................... 22

8.1.1

Scenario 1: Firmware Update via OMA DM Download (Replace) ................................................................... 22

8.1.2

Scenario 2: Firmware Update through an Alternative Download Mechanism................................................... 22

8.2

ROTOCOL

EFINITION

............................................................................................................................................ 24

8.2.1

Firmware Update Step1: Firmware Update Initiation ........................................................................................ 24

8.2.2

Firmware Update Step 2: Device Information Exchange .................................................................................. 24

8.2.3

Firmware Update Step 3: Firmware Download ................................................................................................. 25

8.2.4

Firmware Update Step 4: Firmware Installation ................................................................................................ 25

8.2.5

Firmware Update Step 5: Notification of Firmware Update Status ................................................................... 25

OMA-TS-DM-FUMO-V1_0_2-20090828-A Page 4 (31)





Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document. [OMA-Template-Spec-20090101-I]

APPENDIX A.

CHANGE HISTORY (INFORMATIVE) .............................................................................................. 27

A.1

PPROVED

ERSION

ISTORY

................................................................................................................................. 27

APPENDIX B.

STATIC CONFORMANCE REQUIREMENTS (NORMATIVE) ..................................................... 28

B.1

SCR

FOR

FUMO

REE

TRUCTURE

........................................................................................................................ 28

B.2

SCR

FOR

FUMO

LIENT

......................................................................................................................................... 28

B.3

SCR

FOR

FUMO

ERVER

......................................................................................................................................... 30

APPENDIX C.

RECOMMENDATIONS (INFORMATIVE) ........................................................................................ 31

Figures

Figure 1: Firmware Update Management Object Structure (Informative) ......................................................................... 9

Figure 2: Firmware Update State Diagram ........................................................................................................................... 15

Figure 3: Firmware Update via OMA DM Download .......................................................................................................... 22

Figure 4: ‘Exec’ on x/Download and ‘Exec’ on x/Update..................................................................................................... 23

Figure 5: ‘Exec’ on x/DownloadAndUpdate .......................................................................................................................... 24

Tables

Table 1: Valid States ................................................................................................................................................................ 12

Table 2: Result Code .............................................................................................................................................................. 19