FOTA (Firmware Over-The-Air) -NOT ready yet

 What is FOTA?

FOTA is a mobile software management technology that enables the updating of a mobile device’s operating system.
The download process for FOTA-capable phones is typically less than 10 minutes.
(Not anymore)

FOTA simplifies the process of updating mobile device firmware by allowing manufacturers to provide it through a single, secure and fast method. This eliminates the need for manual downloads and simplifies the process of keeping devices up to date.

Bugfix allows manufacturers to repair faulty units and remotely update software updates. This method typically involves the consumer downloading and updating mobile device firmware through a manufacturer’s website or server. FOTA updates are generally accessible through the device menu or software or firmware update

Device management protocols

LwM2M (OMA Lightweight M2M), 
built by the Open Mobile Alliance, is a light, fast and structured protocol, ideal for low-capacity device.

OMA-DM (OMA Device Management),
built by Open Mobile Alliance, but more oriented to mobile applications. Ideal for things in movement (changing IP address for instance). More complex and structured tan LwM2M.

TR-069,(CPE WAN Management Protocol, remote device deployment)
created by the Broadband Form and used in hundreds of thousand of devices all over the world, being a protocol widely used by telecommunication operators to provision their routers, etc.

MQTT, (Message Queuing Telemetry Transport)
MQTT is an OASIS standard. The standard protocol with the most impact in IoT is MQTT. since is light, robust and overhead-less. It works with in a subscription-publish model, very similar in concept as a lot of chat tools. This protocol is oriented to communication, but it lacks of a native IoT Device Management feature.

Firmware and Software Upgrade Process

• To Determine Firmware Versions
  Automatic update check
  Manual update check
• To Obtain Newer Firmware Versions
  Unicast transport protocols : HTTP / HTTPS (TR-069 mandatory), FTP, SFTP and TFTP
  Multicast protocols : FLUTE and DSM-CC 
• To Upgrade the Firmware
  Conventional FOTA (without Secure Boot) ?
  Secure Boot Mechanism for Secure FOTA ?
• To Validating the upgrades

TR-069 Software Update

• Setup the Software update test environment
• Server (TR-69 ACS) / 
• Client (CPE or CWMP Endpoints)
• Requirements (Inform RPC method )
• The CPE MAY at any time initiate a connection to the ACS via a CWMP Endpoint using the pre-determined ACS address.
• The ACS MAY at any time request that a CWMP Endpoint initiate a connection to the ACS using the Connection Request mechanism. 
• File Transfers
• The CPE MAY send the HTTP/GET/PUT over the already established connection.
• The CPE MUST use TLS when the file location is specified as an HTTPS URL.
• The Response message
• A Download response / A Transfer complete message(successful download)
• A Transfer Complete message sent in a subsequent Session(apply the downloaded file)

Open Mobile Alliance (OMA)

The Open Mobile Alliance (OMA) is a standards organization which develops open, international technical standards for the mobile phone industry. It’s a nonprofit Non-governmental organization(NGO), a forum for industry stakeholders to agree on common specifications for products and services.

Formation :  June 2002 (19 years ago.)Merger of IPSO Alliance : March 2018 (3 years ago)

• Standard specifications:
• OMA SyncML Common Specifications V1.1.2
• OMA Device Management (OMA DM) specification for mobile device management using  SyncML V1.1.2The OMA DM (based on SyncML DM) specifications define the protocols and mechanisms for how configuration parameters can be delivered to an OMA client from a SyncML DM server that is part of the overall architecture 
• Device Management Conformance Requirements, Version 1.1.2.file name: OMA-SyncML-DMConReqs-V1_1_2-20030613-A.pdf

Reference : 

A Firmware Update Architecture for Internet of Things https://tools.ietf.org/id/draft-ietf-suit-architecture-08.html

Applicable Protocol for Updating Firmware of Automotive HVAC Electronic Control Units (ECUs) Over the Airhttps://ieeexplore.ieee.org/document/8726718

Research of the systems for Firmware Over The Air (FOTA) and Wireless Diagnostic in the new vehicleshttps://ieeexplore.ieee.org/document/9238345/

Secure FOTA Object for IoThttps://ieeexplore.ieee.org/document/8110218

Research Firmware Update Over the Air from the Cloudhttps://ieeexplore.ieee.org/document/8549628

OMA Specifications (Open Mobile Alliance)https://technical.openmobilealliance.org/index.html

MT7697 API Reference

https://www.ibm.com/docs/en/zos/2.4.0?topic=task-types-software-updates

https://www.muutech.com/en/iot-device-management-protocols-lwm2m-oma-dm-and-tr-069/

CDRouter OD-128 tests.

The test cases in this module are based on the DSL forum's OD-128 Rev 4 January 2011.
Test Name: od128_test_1.1(same as 8.3.1 of CTC)
Purpose:
The purpose of this test is to validate that a CPE can establish an authenticated HTTP session with the ACS using basic authentication.  This test should be performed only if the ACS uses or can be configured to use basic authentication.

這個測試的目的是為了驗證一個用戶端設備可以建立一個 HTTP會話認證與 ACS使用基本身份驗證。這個測試應該執行僅當 ACS的使用，也可以配置為使用基本身份驗證。


Procedure:
1. If necessary, configure the ACS to use basic HTTP authentication.

2. The CPE is stimulated to initiate an HTTP session with the ACS. Possible methods involve various TR-069 specific mechanisms, or stimulating the CPE  directly if such a mechanism exists through a non-standard interface.
3. The ACS issues a "401 Unauthorized" HTTP challenge and HTTP authentication proceeds normally.



Success Metric

1. The CPE and ACS are able to successfully establish an authenticated HTTP session.

TR069 Overview.

TR-069定義：

TR-069 = CPE WAN Management Protocol (CWMP), which was created by the Broadband Forum (http://www.broadband-forum.org/).

TR-069為 DSL Forum所定義的CPE WAN端的管理協定CPE WAN Management Protocol（CWMP），透過網路遠端管理客戶端設備的協定。

TR-069為Device和Auto Configuration Servers (ACS)之間共同的溝通方式，使用SOAP透過HTTP傳輸，包函了一個安全的自動設定和控制等管理的完整架構。ACS是一種裝置，可以管理終端設備、trouble shoot、設定、昇級等功能。

Protocol stack

TR-069的目的:
服務提供商(Service Providers)現在可以使用一個共同的管理平台,通過網路以使用TR-069的CPE及ACS完成廣大及覆雜的自動設定、管理所有客戶設備（像是modems, routers, gateways, Set-top box, paddles, VoIP-phones等等…）











TR-069 End-to-End Architecture 主要的功能:
自動設定及動態的服務更新。
軟體及韌體的管理。
狀態及效能的監控。
故障診斷。
TR-069相關延伸協定:
TR-098-Internet Gateway Device Data Model for TR-069(之前定義在TR-069的參數，現今全部移至TR-098)
TR-104-Provisioning Parameters for VoIP CPE(VoIP的參數)
TR-106-Data Model Template for TR-069 Enabled Devices
TR-110-Reference Models for VoIP Configurations in the DSL Home
TR-111-Remote. Management of Home Networking Devices
其餘WT階段文件不在此篇提出。


The CPE establishes a connection to the server on a number of occasions:

• The first time it is installed/connected
• On startup
• Periodically
• When requested by the server
• Whenever particular parameter values change (via Connection Request)
• When a file transfer is complete (e.g. after firmware upgrade)
• When a diagnostics test is complete