-
Notifications
You must be signed in to change notification settings - Fork 3
Terms for ISO TC 204 WG 18
Ken Vaughn edited this page Mar 6, 2019
·
2 revisions
WG | Clause | Term | Definition |
---|---|---|---|
18 | 3.1.1.11 | stakeholder | <system> individual, team, organization, or classes thereof, having an interest in a system |
18 | 3.1.11.1 | service | <ITS> performance of one or more tasks that fulfils an ITS user need for an ITS user |
18 | 3.1.12.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.1.13.2 | communication service | <ITS-S> performance of one or more tasks that fulfils an ITS-S communication need for an ITS-S communication user |
18 | 3.1.14.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.14.4 | intelligent transport system | technology system that is designed to benefit a surface transport system |
18 | 3.1.15.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.1.3.1 | access layer | 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.3.2 | application entity | part of the ITS station reference architecture that is responsible for providing ITS-related functionality |
18 | 3.1.3.3 | data plane | part of the ITS station reference architecture that is responsible for handling communications with other physical objects |
18 | 3.1.3.4 | facilities layer | 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.3.5 | management entity | 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.3.6 | security entity | part of the ITS station reference architecture that is responsible for providing privacy, communication security, and system security |
18 | 3.1.3.7 | transnet layer | 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.9.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.9.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.2.1.6 | application template | <ITS> executable technical pattern of an ITS application specification |
18 | 3.2.1.2 | interoperability design | characteristics necessary to fully define how various physical objects interoperate to provide a service |
18 | 3.2.1.1 | ITS application | interoperability design for an ITS service |
18 | 3.2.1.3 | ITS application specification | one or more documents that detail all necessary requirements for an ITS application |
18 | 3.2.1.5 | ITS deployment | installation capable of implementing one or more ITS applications |
18 | 3.2.1.4 | ITS implementation | integration of each physical object necessary to implement one or more ITS applications |
18 | 3.2.2.5 | ITS-S application | ITS-S application process within the application entity |
18 | 3.2.2.6 | ITS-S application implementation | ITS-S application process implementation within the application entity |
18 | 3.2.2.7 | ITS-S application installation | ITS-S application process installation within the application entity |
18 | 3.2.2.8 | ITS-S application instance | ITS-S application process instance within the application entity |
18 | 3.2.2.1 | ITS-S application process | element in an ITS station that performs information processing for an ITS-S service |
18 | 3.2.2.2 | ITS-S application process implementation | implementation of an ITS-S application process |
18 | 3.2.2.3 | ITS-S application process installation | installation of an ITS-S application process implementation |
18 | 3.2.2.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.7.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.7.3.4 | roadside unit | component of roadside equipment that performs the logical control functions |
18 | 3.7.4.2 | cooperative ITS credentials management system | support system that enables trusted communications among ITS components and protects data from unauthorized access |
18 | 3.7.6.1 | vehicle onboard equipment | vehicle system that provides the onboard functions necessary to support the C-ITS services supported by the vehicle |
18 | 3.7.7.2 | ITS station |
ITS component that provides a bounded secured managed domain and conforms to the ITS-S reference architecture\r\n EDITOR'S NOTE 1 As can be seen in a few examples, the phrase "network, comprised of applications" is ambiguous as it is unclear if the ITS-S is comprised of the items or if the network is comprised of the items.\r\n EDITOR'S NOTE 2 The proposed definition assumes that ITS-S are not required to have a wireless network interface. It is my understanding that any ITS device that conformed to the ITS-S architecture (which is almost a null requirement) and provides a BSMD (which is ill-defined) would be considered an ITS-S. Thus, at least at present, I see the term ITS-S to really mean any ITS physical entity that can claim to be secure (and it would be just a claim since there are no measurable requirements). And in fact, some definitions even make the BSMD optional - though I think this is wildly unwise.\r\n EDITOR'S NOTE 3 Logically, an ITS-S seldom (if ever) provides ITS services because an ITS-S is a component of an ITS network; the ITS service is provided by the ITS as a whole. The ITS-S logically should provide ITS-S services, or more specifically, the ITS-S is comprised of the ITS-S architectural components (i.e., applications entity, facilities layer, etc), which all provide ITS-S services. \r\n |
18 | 3.7.7.3 | ITS-S unit | implementation of an ITS station |
18 | 3.8.1.3 | motor vehicle | self-propelled vehicle designed to be propelled by an on-board motor providing a top design speed in excess of 50 km/hr and equipped to satisfy local regulations for the operation on the road network |
18 | 3.8.1.1 | vehicle | entity used to transport people or physical goods |
18 | 3.8.6.1 | connected vehicle | vehicle that includes vehicle onboard equipment |