Skip to content

9.9 Patch the connected home

9.9.1 Description

This use case is to provide a solution to monitor and update the software of the different devices in a house. Many devices are connected to internet through the Home Gateway provided by the Operator. All these devices could be attacked and used to prepare some attacks (e.g. DDoS, cyber attack) if they are not protected and kept up to date against vulnerabilities. The patch could be also necessary to maintain the continutity with the service and the support of new functionalities within the Home.

9.9.2 Source

REQ-2018-0021R04- Use case patch the digital home.

9.9.3 Actors

IoT Device(s), Gateway, device manufacturer, and Operator (Internet Service Provider).

9.9.4 Pre-conditions

None

9.9.5 Triggers

None

9.9.6 Normal Flow

  • The Operator, through the Gateway, collects all the software/firmware versions of the devices in the Home network (object management inventory function).
  • For each device, the Operator, through the Updates' Coordinator, liaises with the manufacturer and collects information about the up-to-date software/firmware versions.
  • The Operator retrieves all the available updates from device manufacturer.
  • In accordance with the user consent and the criticity of the updates, the Operator launches software updates for the impacted devices.

9.9.7 Alternative Flow

  • The Operator, through the Gateway, collects all the software/firmware versions of the devices in the Home (object management inventory).
  • For each device, the Operator, through the Updates' Coordinator, liaises with the manufacturer and collects information about the up-to-date software/firmware versions.
  • The Operator retrieves all the available updates information from device manufacturer.
  • The Opeartor informs the end user about the necessary updates
  • In accordance with the user consent and the criticity of the updates, the deveice manufacturer launches software updates for the impacted devices.

9.9.8 Post-conditions

None

9.9.9 High Level Illustration

The figure below depicts high architecture. Herafter, the high level desctiption of all the steps in the figure:

  • (1) Scan the Home network ecosystem controlled by the GW to obtain metadata.
  • (2) All valid (i.e. not compromised) devices answer to the request from GW
  • (3) GW informs the Coordinator server on current situation
  • (4) Coordinator inform the concerned manufacturers and request action (e.g. Detected security breachs by the operator, ask for security patch, ask for update, etc)
  • (5) Manufacturer sends back up to date information and OS (e.g. new versions, new features, new)
  • (6) Coridinator retrieves the OS and sends it to all concerned GWs
  • (7) According to user consent, GW launchs secure installation to dedicated devices. GW could perform integrity and authenticity check of the SW on behalf the device (e.g. for Lightweight device).

Figure 9.9.9-1 Call flow for the connected home patch

Figure 9.9.9-1 Call flow for the connected home patch

9.9.10 Potential Requirements

  • The M2M System shall be able to dynamically obtain metadata (e.g. Firmware version, Manufacturer ID, HW version) from field devices (e.g. located behind a gateway).
  • The M2M System shall be able to authenticate metadata (e.g. Firmware version, Manufacturer ID, HW version) from field devices (e.g. located behind a gateway).
  • The M2M System shall be able to trigger the secure (e.g. authenticity, integrity, and confidentiality protected) Firmware/Software update of field devices.