ISO 24089:2023 道路車両 — ソフトウェア更新エンジニアリング | ページ 6

3.1.1

compatibility

capability of software (3.1.15) to be executable on vehicle systems (3.1.25) without conflicts

Note 1 to entry: Compatibility can be checked by vehicle configuration information (3.1.24) .

3.1.2

condition

criteria required for a software update operation (3.1.19) to be completed successfully

Note 1 to entry: Conditions can include compatibility (3.1.1) , safe vehicle state (3.1.13) , in-vehicle resources (3.1.11) , and external resources.

3.1.3

corrective action

action to eliminate or contain a problem or failure

3.1.4

cybersecurity

road vehicle cybersecurity

context in which assets are sufficiently protected against threat scenarios to vehicle systems (3.1.25) of road vehicles and infrastructure (3.1.10) required to support software update engineering (3.1.18)

Note 1 to entry: In this document, for the sake of brevity, the term cybersecurity is used instead of road vehicle cybersecurity.

[SOURCE:ISO/SAE 21434:2021, 3.1.9, modified — “to items of road vehicles, their functions and their electrical or electronic components” has been replaced by “to vehicle systems of road vehicles and infrastructure required to support software update engineering” and the Note 1 to entry has been modified.]

3.1.5

cybersecurity risk

effect of uncertainty on cybersecurity (3.1.4) expressed in terms of attack feasibility and impact

[SOURCE:ISO/SAE 21434:2021, 3.1.29]

3.1.6

dependency

effect of software (3.1.15) for one vehicle system (3.1.25) on the same or other vehicle systems (3.1.25)

Note 1 to entry: A dependency can generate a condition (3.1.2) in the metadata of a software update package (3.1.20) .

3.1.7

ECU

electronic control unit

embedded device in a vehicle whose software (3.1.15) can be updated

3.1.8

functional safety

absence of unreasonable risk due to hazards caused by malfunctioning behaviour of vehicle systems (3.1.25)

[SOURCE:ISO 26262-1:2018, 3.67, modified — “E/E” was replaced by “vehicle”.]

3.1.9

functional safety risk

combination of the probability of occurrence of harm and the severity of that harm

[SOURCE:ISO 26262-1:2018, 3.128, modified — The term has been modified from “risk” to “functional safety risk” for the scope of this document.]

3.1.10

infrastructure

processes and information systems managing any combination of software update operations (3.1.19) , software update campaigns (3.1.16) , documentation, and vehicle configuration information (3.1.24) , including both digital and manual activities

Note 1 to entry: Infrastructure can include any combination of servers, tools, and manual activities used in the software update operation.

3.1.11

in-vehicle resource

vehicle or electronic control unit (ECU) (3.1.7) available properties relevant for software update engineering (3.1.18)

3.1.12

recipient

individual instance of a vehicle, vehicle system (3.1.25) , or electronic control unit (ECU) (3.1.7) that receives a software update package (3.1.20) during a software update campaign (3.1.16)

3.1.13

safe vehicle state

vehicle operating mode based on conditions (3.1.2) for performing software update operations (3.1.19) without an unreasonable level of risk

Note 1 to entry: Safe vehicle state can be different depending on the conditions (3.1.2) required for the software update package (3.1.20) .

Note 2 to entry: Safe vehicle state can vary based on the software update operation step being performed.

3.1.14

skilled person

individual with relevant technical education, training or experience to execute software update operations (3.1.19)

Note 1 to entry: A skilled person can be a mechanic in a workshop.

Note 2 to entry: A skilled person can be authorized or certified for their specialized training or be a skilled vehicle user (3.1.26) .

[SOURCE:ISO 10209:2022, 3.14.36, modified — The phrase “to enable them to perceive risks and avoid hazards occurring during use of a product” has been replaced by “to execute software update operations”.]

3.1.15

software

computer programs and associated data intended for installation (3.2.2) on vehicles, vehicle systems (3.1.25) , or electronic control units (ECUs) (3.1.7) , that may be dynamically written or modified during execution

[SOURCE:NIST SP 800-53, modified — The phrase “intended for installation on vehicles, vehicle systems, or electronic control units(ECUs)” was added.]

3.1.16

software update campaign

sequence of identifying targets (3.1.23) and resolving recipients (3.1.12) ; distributing software update packages (3.1.20) ; and monitoring and documenting results of software update operations (3.1.19)

3.1.17

software update distribution method

mechanism for delivery of a software update package (3.1.20) during a software update campaign (3.1.16)

Note 1 to entry: The software update distribution method can be wired (e.g. tool, USB flash drive), wireless (e.g. cellular or Wi-Fi) or hardware replacement.

Note 2 to entry: Hardware replacement can be replacing an electronic control unit (ECU) (3.1.7) with the effect of software (3.1.15) version replacement.

3.1.18

software update engineering

application of a systematic and managed approach to the processes of planning, development, and deployment of software update packages (3.1.20)

[SOURCE:ISO/IEC/IEEE 24765:2017, 3.3810, modified — “disciplined, quantifiable” was replaced by “and managed”, and “development, operation and maintenance of software” was replaced by “processes of development, planning, and deployment of software update packages”.]

3.1.19

software update operation

steps involved in receipt (3.2.1) , installation (3.2.2) and activation (3.2.3) of software update packages (3.1.20) in a vehicle, vehicle systems (3.1.25) , or electronic control units (ECUs) (3.1.7)

3.1.20

software update package

set of software (3.1.15) and associated metadata that is intended to be deployed to one or more vehicles, vehicle systems (3.1.25) , or electronic control units (ECUs) (3.1.7)

3.1.21

software update project

set of software update engineering (3.1.18) activities for one or more targets (3.1.23)

Note 1 to entry: Activities can include developing or adapting the infrastructure (3.1.10) , vehicle capabilities, or processes described in this document.

Note 2 to entry: A software update project can encompass multiple software update campaigns (3.1.16) .

3.1.22

tailor

to omit or perform an activity in a different manner compared to its description in this document

[SOURCE:ISO/SAE 21434:2021, 3.1.32]

3.1.23

target

one or more classes of vehicles, vehicle systems (3.1.25) , or electronic control units (ECUs) (3.1.7) determined by vehicle configuration information (3.1.24)

3.1.24

vehicle configuration information

comprehensive accounting of hardware versions, software (3.1.15) versions and configuration parameters in a vehicle

3.1.25

vehicle system

functional group of one or more electronic control units (ECUs) (3.1.7) and attached hardware

Note 1 to entry: Attached hardware can be, for example, a sensor, actuator or light, that is not an ECU.

3.1.26

vehicle user

person operating, driving, owning or managing a vehicle

Note 1 to entry: A vehicle user can be a skilled person (3.1.14) .