| 18 |
3.1.2.5 |
cooperative ITS |
subset of ITS where information is shared among physical objects based on mutual security agreements with a credentialing system |
| 18 |
3.1.2.4 |
intelligent transport system |
technology system that is designed to benefit a surface transport system
|
| 18 |
3.1.3.11 |
stakeholder |
<system> individual, team, organization, or classes thereof, having an interest in a system |
| 18 |
3.1.5.1 |
access layer |
<ITS-S> part of the data plane that provides the functionality related to the physical and data link layers of the open systems interconnect (OSI) reference model |
| 18 |
3.1.5.2 |
application entity |
<ITS-S> part of the ITS station reference architecture that is responsible for providing ITS-related functionality |
| 18 |
3.1.5.3 |
data plane |
<ITS-S> part of the ITS station reference architecture that is responsible for handling communications with other physical objects
|
| 18 |
3.1.5.4 |
facilities layer |
<ITS-S> part of the data plane that provides the functionality related to the session, presentation, and application layers of the open systems interconnect (OSI) reference model |
| 18 |
3.1.5.5 |
management entity |
<ITS-S> part of the ITS station reference architecture that is responsible for management of communications and configuration information for the local physical object and possibly remote physical objects |
| 18 |
3.1.5.6 |
security entity |
<ITS-S> part of the ITS station reference architecture that is responsible for providing privacy, communication security, and system security |
| 18 |
3.1.5.7 |
transnet layer |
<ITS-S> part of the data plane that provides the functionality related to the network and transport layers of the open systems interconnect (OSI) reference model |
| 18 |
3.1.11.2 |
data element |
data concept represented by a specific value domain and that describes a single atomic property about an object class. |
| 18 |
3.1.11.3 |
data frame |
data concept represented by a specific aggregate domain and that describes information of interest through a useful grouping of more atomic properties about one or more object classes. |
| 18 |
3.1.12.1 |
scenario |
<use case> a description of the sequence of events from the user's perspective to perform a task in a specified context |
| 18 |
3.2.3.3 |
roadside equipment |
field system used to send electronic messages to and receive messages from nearby vehicle systems and traveller systems via wireless technologies |
| 18 |
3.2.3.4 |
roadside unit |
component of roadside equipment that performs the logical control functions |
| 18 |
3.2.5.2 |
cooperative ITS credentials management system |
support system that enables trusted communications among ITS components and protects data from unauthorized access |
| 18 |
3.2.6.1 |
vehicle onboard equipment |
vehicle system that provides the onboard functions necessary to support the ITS services supported by the vehicle |
| 18 |
3.2.7.2 |
ITS station |
portion of an ITS component that provides a bounded secured managed domain and conforms to the ITS-S reference architecture
|
| 18 |
3.2.7.3 |
ITS-S unit |
instantiation of an ITS station
|
| 18 |
3.2.8.6 |
application template |
<ITS> executable technical pattern of an ITS application specification
|
| 18 |
3.2.8.2 |
interoperability design |
characteristics necessary to fully define how various physical objects interoperate to provide a service
|
| 18 |
3.2.8.1 |
ITS application |
interoperability design for an ITS service
|
| 18 |
3.2.8.3 |
ITS application specification |
one or more documents that detail all necessary requirements for an ITS application
|
| 18 |
3.2.8.5 |
ITS deployment |
installation capable of implementing one or more ITS applications
|
| 18 |
3.2.8.4 |
ITS implementation |
integration of each physical object necessary to implement one or more ITS applications
|
| 18 |
3.2.9.9 |
ITS application role |
ITS-S user need expressed as a formal set of interoperability requirements that need to be fulfilled to satisfy a portion of functionality of an ITS application
|
| 18 |
3.2.9.5 |
ITS-S application |
ITS-S application process residing in the application entity
|
| 18 |
3.2.9.6 |
ITS-S application implementation |
ITS-S application process implementation within the application entity
|
| 18 |
3.2.9.7 |
ITS-S application installation |
ITS-S application process installation within the application entity
|
| 18 |
3.2.9.8 |
ITS-S application instance |
ITS-S application process instance within the application entity
|
| 18 |
3.2.9.1 |
ITS-S application process |
element in an ITS station that performs information processing for an ITS-S service
|
| 18 |
3.2.9.2 |
ITS-S application process implementation |
implementation of an ITS-S application process
|
| 18 |
3.2.9.3 |
ITS-S application process installation |
installation of an ITS-S application process implementation
|
| 18 |
3.2.9.4 |
ITS-S application process instance |
run-time instance of an ITS-S application process installation
|
| 18 |
3.4.2.2 |
location reference |
specification of a location according to a specific set of rules |
| 18 |
3.5.3.1 |
service |
<ITS> performance of one or more tasks to fulfil an ITS user need for an ITS user
|
| 18 |
3.5.4.5 |
bounded, secured, managed domain |
controlled processing environment that adheres to a minimum set of management and security principles and procedures so as to establish a level of trust between itself and other similar ITS stations with which it might communicate |
| 18 |
3.5.5.1 |
communication service |
<ITS-S> performance of one or more tasks to fulfil an ITS-S communication need for an ITS-S communication user
|
| 18 |
3.7.1.1 |
vehicle |
material entity used to transport people or physical goods
|
| 18 |
3.7.4.1 |
connected vehicle |
vehicle that is equipped with vehicle onboard equipment that is active and operational |
| 18 |
3.7.4.4 |
disconnected vehicle |
off-grid vehicle that is or was equipped with vehicle onboard equipment that is sufficiently physically disconnected such that the vehicle no longer sends or receives any connected vehicle communications |
| 18 |
3.7.4.2 |
off-grid vehicle |
vehicle that is currently unable to send or receive any connected vehicle communications |
| 18 |
3.7.4.3 |
unconnected vehicle |
off-grid vehicle that is equipped with vehicle onboard equipment that is not active or is otherwise unable to send or receive any connected vehicle communications\r\n
|
| 18 |
3.7.4.5 |
unequipped vehicle |
off-grid vehicle that is not and has never been equipped with vehicle onboard equipment
|