CVRIA Glossary

• A
• B
• C
• D
• E
• F
• G
• H
• I
• J
• K
• L
• M
• N
• O
• P
• Q
• R
• S
• T
• U
• V
• W
• X
• Y
• Z

Access Control

Refers to mechanisms and policies that restrict access to computer resources. An access control list (ACL), for example, specifies what operations different users can perform on specific files and directories.

Adjacent

One of the values for the Spatial Context Flow Characteristic. Data that is hyper local (relevant to a geographic area within ~1 minute travel distance). Also known as "Hyper Local" in some connected vehicle projects.

Administrator

These are the operators that set control parameters, implement system policies, monitor system configuration, and make changes to the system as needed.

Aftermarket Safety Device

A connected device in a vehicle that operates while the vehicle is mobile, but which is not connected to the data bus of the vehicle.

Aggregation

The process of combining data elements of similar format into a single data element that is a statistical representation of the original elements.

Allowed Movements

In the context of connected vehicle, the directions of movement that are legally allowed at a specific point in time based upon the state of the intersection signals.

Analysis

The process of studying a system by partitioning the system into parts (functions, components, or objects) and determining how the parts relate to each other.

Anonymity

Lacking individuality, distinction, and "recognizability" within message exchanges.

Anonymous Certificate

A certificate which contains a pseudonym of the System User instead of his real identity in the subject of the certificate and thus prevents other System Users from identifying the certificate owner when the certificate is used to sign or encrypt a message in the connected vehicle program. The real identity of the anonymous certificates can be traced by Authorized System Operators by using the services of Registration Authority and Certification Authority.

Application

One or more pieces of software designed to perform some specific function; it is a configuration of interacting Engineering Objects. For example, a software program with an interface, enabling people to use a computer as a tool to accomplish a specific task. The connected vehicle Applications provide an accessible, service-oriented perspective to the Connected Vehicle Reference Implementation Architecture (CVRIA). They are tailored to address, separately or in combination, real world transportation problems and needs. The Applications have been defined by various connected vehicle and Cooperative ITS programs. The source for the application descriptions ranges from Concepts of Operations (ConOps), Requirements Specifications, or existing Standards and Architectures. There are five types of Connected Vehicle Applications: Environmental, Mobility, Safety, Support, and Convenience. Each type is comprised of groups of applications (no Convenience applications are currently defined in the CVRIA, but this type of application may access some of the same Support Services as other Applications). The Application pages include a description of the application, its source references, and the subset of the CVRIA that pertains to that application, including sub-tabs for each view (enterprise, functional, physical, and communications).

Application Object

The building blocks of the physical objects of the physical view. Application objects group similar processes of a particular physical object together into an "implementable" package. The grouping also takes into account the need to accommodate various levels of functionality. Since application objects are both the most detailed components of the physical view and tied to specific applications, they provide the common link between the interface-oriented architecture definition and the deployment-oriented applications.
In CVRIA, Application Objects provide functionality defined by PSpecs in the Functional View.

Application Protocol Data Unit

Application Protocol Data Unit (APDU) is a defined data structure that is transferred at a peer level between two applications.

Application User

A user who interfaces with Application Layer software for a desired function or feature.

Architecture

A framework within which a system can be built. Requirements dictate what functionality the architecture must satisfy. An architecture functionally defines what the pieces of the system are and the information that is exchanged between them. An architecture is functionally oriented and not technology-specific which allows the architecture to remain effective over time. It defines "what must be done," not "how it will be done."

Assumption

A judgment about unknown factors and the future which is made in analyzing alternative courses of action.

Authenticate

The process of ensuring that an APDU originated from a source identified within the message.

Authentication

The process of determining the identity of a user that is attempting to access a network.

Authenticity

The quality of being genuine or authentic; which is to have the origin supported by unquestionable evidence; authenticated; verified. This includes whether the software or hardware came from an authorized source.

Authorization

The process of determining what types of activities or access are permitted on a network. Usually used in the context of authentication: once you have authenticated a user, they may be authorized to have access to a specific service.

Available

Ready or able to be used.