ISO 15638-22:2019 高度道路交通システム—規制された商用貨物車両（TARV）の共同テレマティクスアプリケーションのフレームワーク—パート22：貨物車両の安定性の監視 | ページ 6

3.1

access methods

procedures and protocols to provision and retrieve data

3.2

app

small (usually) software applets, organized as software bundles, that support application services (3.3) by keeping the data pantry (3.18) provisioned with up to date data

3.3

application service

service provided by a service provider (3.36) enabled by accessing data from the IVS (3.23) of a regulated vehicle (3.33) via a wireless communications network

3.4

application service provider

ASP

party that provides an application service (3.3)

3.5

app library

separately secure area of memory in IVS (3.23) where apps are stored with different access controls to data pantry (3.18)

3.6

application service data file

ASD file

file held in the data pantry (3.18) of the IVS (3.23) containing data specific to an application service (3.3)

3.7

architecture

formalised description of the design of the structure of TARV and its framework (3.21)

3.8

audit

auditing

review of a party’s capacity to meet, or continue to meet, the initial and ongoing certification agreements as a service provider (3.36)

3.9

authentication

function intended to establish and verify a claimed identity

3.10

basic vehicle data

data maintained/provided by all IVS (3.23) [regardless of jurisdiction (3.27)]

3.11

certification

formal affirmation that an applicant has satisfied all the requirements for appointment as an application service provider (3.4) or that an application service delivers the required service levels

3.12

certification authority

<digital> organization which issues digital certificates for use by other parties (specifically in the context of communications security)

3.13

certification authority

<regulatory> organization (usually independent) which conducts certification (3.11) and ongoing audit (3.8) for service providers (3.36) on behalf of a jurisdiction (3.27)

3.14

commercial application(s)

ITS applications in regulated vehicles (3.33) for commercial (unregulated) purposes

3.15

consignment

shipment of goods/cargo to a destination

3.16

conveyance

vehicle or trailer used to transport from one place to another

3.17

cooperative ITS

C-ITS

ITS applications for both regulatory and commercial purposes that require the exchange of data between uncontracted parties using multiple ITS-stations (3.25) communicating with each other and sharing data with other parties with whom they have no direct contractual relationship to provide one or more ITS services (3.24)

3.18

data pantry

secure area of memory in IVS (3.23) where data values are stored [with different access controls to app library (3.5)

3.19

driver

person driving the regulated vehicle (3.33) at any specific point in time

3.20

facilities

layer that sits on top of the communication stack and helps to provide data interoperability and reuse, and to manage applications and enable dynamic real time loading of new applications

3.21

framework

particular set of beliefs and ideas referred to in order to describe a scenario or solve a problem

3.22

global navigation satellite system

GNSS

several networks of satellites that transmit radio signals containing time and distance data that can be picked up by a receiver, allowing the user to identify the location of its receiver anywhere around the globe

3.23

in-vehicle system

IVS

ITS-station (3.25) and connected equipment on board a vehicle

3.24

ITS service

communication functionality offered by an ITS-station (3.25) to an ITS-station application

3.25

ITS-station

ITS-s

entity in a communication network, comprised of application, facilities (3.20) , networking and access layer components specified in ISO 21217 that operate within a bounded secure management domain

3.26

Java™

object oriented open source operating language developed by SUN systems

3.27

jurisdiction

government, road or traffic authority which owns the r egulatory applications (3.31)

3.28

local data tree

LDT

frequently updated data concepts stored in the on-board data pantry (3.18) containing a collection of data values deemed essential for either a) TARV regulated application service, or b) cooperative intelligent transport systems (3.17)

3.29

operator

fleet manager of a regulated vehicle (3.33)

3.30

prime service provider

service provider (3.36) who is the first contractor to provide regulated application services (3.32) to the regulated vehicle (3.33) , or a nominated successor on termination of that initial contract

Note 1 to entry: The prime service provider is also responsible to maintain the installed IVS (3.23) . If the IVS was not installed during the manufacture of the vehicle the prime service provider is also responsible to install and commission the IVS.

3.31

regulated/regulatory application

application arrangement using TARV utilised by jurisdictions (3.27) for granting certain categories of commercial vehicles rights to operate in regulated circumstances subject to certain conditionsor to permit a vehicle to operate within the jurisdiction

Note 1 to entry: It may be mandatory or voluntary at the discretion of the jurisdiction.

3.32

regulated application service

TARV application service to meet the requirements of a regulated application that is mandated by a regulation imposed by a jurisdiction (3.27) , or is an option supported by a jurisdiction

3.33

regulated vehicle

vehicle that is subject to regulations determined by the jurisdiction (3.27) as to its use on the road system of the jurisdiction in regulated circumstances, subject to certain conditions, and in compliance with specific regulations for that class of regulated vehicle

Note 1 to entry: At the option of jurisdictions, this may require the provision of information via TARV or provide the option to do so.

3.34

regime for open application management

ROAM

facilities (3.20) layer for TARV, within the ISO 15638 series of standards, providing an open access, yet secure runtime environment for TARV and other applications, including cooperative vehicle applications, on top of the CALM communications environment

3.35

roadside sensor

3.36

service provider

party which is certified by a c ertification authority (regulatory) (3.12) as suitable to provide regulated or commercial ITS application services (3.3)

3.37

session

wireless communication exchange between the ITS-station (3.25) of an IVS (3.23) and the ITS-station of its application service provider (3.4) to achieve data update, data provision, upload apps, or otherwise manage the provision of the application service (3.3) , or a wireless communication provision of data to the ITS-station of an IVS from any other ITS-station

3.38

specification

explicit and detailed description of the nature and functional requirements and minimum performance of equipment, service or a combination of both

3.39

tamper

tampering

conduct towards IVS (3.23) or a service provider’s (3.36) system which is intended to prevent the IVS or the service provider’s system from functioning correctly

3.40

telematics

use of wireless media to obtain and transmit (data) from a distant source

3.41

Unified Modeling Language

UML

graphical language for visualizing, specifying, constructing, and documenting the artifacts of a software-intensive system

Note 1 to entry:UML offers a standard way to write a system's blueprints, including conceptual things such as business processes and system functions as well as concrete things such as programming language statements, database schemas, and reusable software components, and is standardised as ISO/IEC 19501 [Unified Modeling Language (UML)].

3.42

user

individual or party that enrols in and operates within a regulated or commercial application (3.14) service