Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Abstraction

This chapter provides requirements for backup management functions.

In order to prevent data corruption due to malfunction, it is necessary to take measures such as securing the data safety within the product. Backing up the necessary data on a regular basis will help maintain the reliability of the product.

In this way, we focus on the function of performing data backup on the product and describe the use case requirements.

Use case

In the following table, use cases which need the backup management for services are described.

#ItemUser

1

A user changes the language display of the IVI from English to Japanese. By backing up the configuration data in the system, the user does not have to set the language display to Japanese every time the user uses IVI.

Driver

2

If a user wants to delete the data backed up in the IVI, the user uses the system reset function.

Driver

3

Developers check during development if the backup data can be saved correctly.

OEM/Developer(Before product shipment)

Discussion Space for additional use cases(Freely write please) ~

#

Item

1

Data persistency vs Backup

  • They have different requirement and functionality
2
  • identify the location of the storage / app specific storage area
  • status of the persistent storage (wear leveling)
3data access restriction
4

what kind of data?

  • Frequently used Destination
  • User specific info 
5
  • infrastructure code
  • app property, version control
  • regional setting
  • original setting
  • Database from App
  • logging
  • GPS
    • compressed, secured form

Functional Requirements

This table includes the functional requirements of Persistent notification and backup management module.

#Item

1

IVI needs the ability to back up the data it needs, when it needs it.

2

The required data in #1 includes, for example, the following, but each data is specified by each OEM.

(e.g., time display method, Bluetooth pairing information, IVI screen theme color settings, etc.)

3

The following are examples of required timing for #1, but each data shall be specified by each OEM.
(e.g., when IVI is turned off, periodic backups, etc.)

Backup management in Basesystem

Reference implementation in Basesystem

Backup manager

  • No labels