ODOT Object Registration and Discovery System
Status: Planned
Description
The 'Object Registration and Discovery System' represents one or more center–based applications that provide registration and lookup services necessary to allow objects to locate (for communications purposes) other objects operating within the Connected Vehicle Environment. These registration and discovery services are support services that enable other applications.
Stakeholders
| Stakeholder | Role | Role Status |
|---|
| ODOT | Owns | Planned |
|---|
Physical Objects
Functional Objects
| Functional Object | Description | User Defined |
|---|
| Object Registration and Discovery | 'Object Registration and Discovery' facilitates the registration of services by the respective service providers and the subsequent query–based discovery of these registered services. Many of the services offered by roadside or center–based service providers operating within the project geographic boundary will require an advertisement of their existence and cyber location to potential users; which consist primarily of PIDs and vehicles, but could include roadside or other center based services. | False |
|---|
Physical Standards
| Document Number | Title | Description |
|---|
| ISO 21217 | Intelligent transport systems –– Communications access for land mobiles (CALM) –– Architecture | ISO 21217 describes the communications reference architecture of nodes called "ITS station units" designed for deployment in ITS communication networks. While it describes a number of ITS station elements, whether or not a particular element is implemented in an ITS station unit depends on the specific communication requirements of the implementation. It also describes the various communication modes for peer–to–peer communications over various networks between ITS communication nodes. These nodes may be ITS station units as described in the document or any other reachable nodes. ISO 21217 specifies the minimum set of normative requirements for a physical instantiation of the ITS station based on the principles of a bounded secured managed domain. |
|---|
| NIST FIPS PUB 140–2 | Security Requirements for Cryptographic Modules | This Federal Information Processing Standard (140–2) specifies the security requirements that will be satisfied by a cryptographic module, providing four increasing, qualitative levels intended to cover a wide range of potential applications and environments. The areas covered, related to the secure design and implementation of a cryptographic module, include specification; ports and interfaces; roles, services, and authentication; finite state model; physical security; operational environment; cryptographic key management; electromagnetic interference/electromagnetic compatibility (EMI/EMC); self–tests; design assurance; and mitigation of other attacks. |
|---|
Interfaces To
(View Context Diagram)