< < SU05 : SU06 : SU07 > >

SU06: Object Registration and Discovery

This service package provides registration and lookup services necessary to allow objects to locate other objects operating within the Connected Vehicle Environment.

An object registry is like a phone book for all the connected centers, systems, and equipment in the transportation system (the "objects"). In this service package, each object registers itself with the ORDS and tells the registry where it lives in the communication network (e.g., host, port, node name) and information about the services it provides - information that other objects can use to determine the type of service, the geographic scope of the service, and other information that helps users of the registry to make informed decisions about which object(s) support a needed service or information stream. This is the "Discovery" part of the service. Connected objects can use the registry to find (discover) objects that can be used to get needed information or services.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
ITS Object Maintainer ITS Object Maintains
ITS Object Manager ITS Object Manages
ITS Object Owner ITS Object Maintainer System Maintenance Agreement
ITS Object Owner ITS Object Manager Operations Agreement
ITS Object Owner Object Registration and Discovery System Maintainer Maintenance Data Exchange Agreement
ITS Object Owner Object Registration and Discovery System User Service Usage Agreement
ITS Object Owner ORDS Operator Application Usage Agreement
ITS Object Owner Vehicle Maintainer Maintenance Data Exchange Agreement
ITS Object Owner Vehicle User Service Usage Agreement
ITS Object Supplier ITS Object Owner Warranty
Object Registration and Discovery System Maintainer Object Registration and Discovery System Maintains
Object Registration and Discovery System Manager Object Registration and Discovery System Manages
Object Registration and Discovery System Manager ORDS Operator System Usage Agreement
Object Registration and Discovery System Owner ITS Object Maintainer Maintenance Data Exchange Agreement
Object Registration and Discovery System Owner ITS Object Owner Information Provision Agreement
Object Registration and Discovery System Owner ITS Object User Service Usage Agreement
Object Registration and Discovery System Owner Object Registration and Discovery System Maintainer System Maintenance Agreement
Object Registration and Discovery System Owner Object Registration and Discovery System Manager Operations Agreement
Object Registration and Discovery System Supplier Object Registration and Discovery System Owner Warranty
ORDS Operator Object Registration and Discovery System Operates
Vehicle Maintainer Vehicle Maintains
Vehicle Manager Vehicle Manages
Vehicle Owner Vehicle Maintainer System Maintenance Agreement
Vehicle Owner Vehicle Manager Operations Agreement
Vehicle Supplier Vehicle Owner Warranty

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
ITS Object ITS The general 'ITS Object' includes core capabilities common to any class of object.
Object Registration and Discovery System Support 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.
ORDS Operator Support The 'Object Registration and Discovery System Operator' represents the person or people that monitor and manage the Object Registration and Discovery System.
Vehicle Vehicle This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

Includes Functional Objects:

Functional Object Description Physical Object
ITS Management Support 'ITS Management Support' provides management of the ITS Object. This includes management of regulatory information and policies, management of application processes, management of communication system configuration and update management, communications interfaces, protocol-specific techniques to ensure interoperability such as service advertisements, communications congestion management and interference management, local device states and communications information, billing management, fault management, service level and performance monitoring. ITS Object
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. Object Registration and Discovery System
Vehicle Support Services 'Vehicle Support Services' provides foundational functions that support data collection, management, and distribution. It coordinates with Support subsystems to maintain necessary registrations with respect to location and scope. Vehicle

Includes Information Flows:

Information Flow Description
object discovery Represents the interactive discovery of network communications related information by any end entity, querying the ORDS. Information exchange could be as simple as a Domain Name Service (DNS) query, or it could include service and service metric information.
object registration Represents the provision of information related to communications, service and service metric information from a service provider end entity to the ORDS.
ORDS operations information presentation Presentation of information to the ORDS Operator including current operational status of the Object Registration and Discovery Service.
ORDS operator input User input from the ORDS operator including requests to monitor current system operation and inputs to affect system operation.
service advertisement An advertisement of available services and identification of how those services may be accessed (e.g., RF parameters, identifiers, etc.). Services include network services such as IPv6 routing, public roadside services such as intersection safety, back office services including situation data services and security credentials, or private services.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; Improve freight network
B. Increase the safety of the transportation system for motorized and nonmotorized users; Reduce fatalities and injuries
D. Increase the accessibility and mobility of people and for freight; Reduce congestion
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; Enhance integration and connectivity
G. Promote efficient system management and operation; Improve efficiency

Associated Objective Categories

Objective Category
Integration: Transportation Data Collection
Safety: Vehicle Crashes and Fatalities
System Efficiency: Delay

Associated Objectives and Performance Measures

Objective Performance Measure
Enhance planning with better data Amount of data gathered from ITS enhancements used in infrastructure and operations planning
Enhance planning with better data Number of planning activities using data from ITS systems
Enhance planning with better data Years of data in database that is easily searchable and extractable
Reduce crashes at intersections Number of crashes and fatalities at signalized intersections
Reduce crashes at intersections Number of crashes and fatalities at unsignalized intersections
Reduce crashes at intersections Number of crashes and fatalities related to red-light running
Reduce crashes at railroad crossings Number of crashes and fatalities at railroad crossings
Reduce crashes due to red-light running Number of crashes and fatalities related to red-light running
Reduce crashes due to road weather conditions Number of crashes and fatalities related to weather conditions
Reduce crashes due to unexpected congestion Number of crashes and fatalities related to unexpected congestion
Reduce hours of delay per driver by X percent by year Y. Hours of delay (person-hours).
Reduce hours of delay per driver by X percent by year Y. Hours of delay per driver.
Reduce lane departure crashes Number of crashes and fatalities related to inappropriate lane departure, crossing or merging
Reduce secondary crashes Number of secondary crashes
Reduce the number of motorcyclist fatalities by X percent by year Y. Number of motorcyclist fatalities
Reduce the number of pedestrian fatalities by X percent by year Y. Number of pedestrian fatalities
Reduce the rate fatalities in the region by X percent by year Y. Rate of fatalities (rate per vehicle miles travelled (VMT))
Reduce the rate of severe injuries in the region by X percent by year Y. Rate of serious injuries (rate per VMT)
Reduce the total number of crashes in the region by X percent by year Y. Total crashes per X VMT.
Reduce the total number of crashes involving bicyclists and pedestrians in the region by X percent by year Y. Total crashes involving bicycles.
Reduce the total number of crashes involving bicyclists and pedestrians in the region by X percent by year Y. Total crashes involving pedestrians.
Reduce the total number of fatalities and severe injuries in the region by X percent by year Y. Total fatalities per X VMT.
Reduce the total number of fatalities and severe injuries in the region by X percent by year Y. Total severe injuries per X VMT.
Reduce the total number of fatalities in the region by X percent by year Y. Number of fatalities
Reduce the total number of severe injuries in the region by X percent by year Y. Number of serious injuries

 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need Functional Object Requirement
01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services. ITS Management Support 01 The ITS Object shall provide its network address, service offerings and metrics characterizing those services to vehicles within the broadcast range of the ITS Object's short range communications equipment.
02 The ITS Object shall provide its network address, service offerings and metrics characterizing those services to the Object Registration and Discovery Service.
03 The ITS Object shall obtain network addresses from the Object Registration and Discovery Service.
04 The ITS Object shall make network address information available to onboard applications.
Object Registration and Discovery 01 The Center shall provide network addresses to Vehicles.
02 The Center shall provide network addresses to Personal devices.
03 The Center shall provide network addresses to Connected Vehicle Roadside Equipment.
04 The Center shall provide network addresses to other Centers.
05 The Center shall accept network address queries based on service type provided.
06 The Center shall accept network address queries based on service metric provided.
07 The Center shall maintain a registry of network address, services and service metrics.
08 The Center shall accept registration information from other Centers.
09 The Center shall accept registration information from other Connected Vehicle Roadside Equipment.
10 The Center shall provide the operator with a mechanism to monitor the status of its operations.
11 The Center shall provide the operator with a mechanism to modify registrations.
Vehicle Support Services 01 The Vehicle shall obtain network addresses from the Object Registration and Discovery Service.
02 The Vehicle shall make network address information available to onboard applications.

Related Sources

Document Name Version Publication Date
Southeast Michigan Test Bed 2014 Concept of Operation Draft 12/29/2014


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
ITS Object Low High Moderate Class 3
Object Registration and Discovery System Low High Moderate Class 3
Vehicle Not Applicable Low Moderate Class 1



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
ITS Object Object Registration and Discovery System object registration Low High Moderate
This information will be made public to C-ITS devices through the Object Registration and Discovery service. What is available where and to whom needs to be absolutely correct for the purpose of service management. Incorrect information here could lead to significant negative effects on communications utilization, which in turn could be disastrous to C-ITS services. Devices may need to change their offerings, which justifies MODERATE.
ITS Object Vehicle service advertisement Not Applicable Moderate Moderate
By definition broadcast and intended to be available to all receivers using the same media as the broadcaster Since this identifies the services made available by the object providing the service advertisement, if it is incorrect or unavailable then users may waste resources attempting to use unavailable services or more likely not be aware of what is available and not take advantage of service offerings. Since this identifies the services made available by the object providing the service advertisement, if it is incorrect or unavailable then users may waste resources attempting to use unavailable services or more likely not be aware of what is available and not take advantage of service offerings.
Object Registration and Discovery System ITS Object object discovery Low High Moderate
This information will be available to all C-ITS devices. C-ITS connectivity is predicated on device connectivity. The information contained within this flow is critical to that. Without correct and timely networking information, other C-ITS flows will fail, which is why this flow is so critical. C-ITS connectivity is predicated on device connectivity. The information contained within this flow is critical to that. Without correct and timely networking information, other C-ITS flows will fail, which is why this flow is so critical. Availability is considered MODERATE because this flow does not need to be instantiated every time a communication occurs; often the relevant information can be stored locally.
Object Registration and Discovery System ORDS Operator ORDS operations information presentation Not Applicable High High
System core flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over core equipment. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
ORDS Operator Object Registration and Discovery System ORDS operator input Not Applicable High High
System core flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over core equipment Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.

Name Title Physical Object
ISO 21217 Architecture Intelligent transport systems -- Communications access for land mobiles (CALM) -- Architecture ITS Object




System Requirements

System Requirement Need
001 The system shall provide its network address, service offerings and metrics characterizing those services to vehicles within the broadcast range of the ITS Object's short range communications equipment. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.
002 The system shall provide its network address, service offerings and metrics characterizing those services to the Object Registration and Discovery Service. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.
003 The system shall obtain network addresses from the Registration Center. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.
004 The system shall make network address information available to onboard applications. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.
005 The system shall provide network addresses to Vehicles. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.
006 The system shall provide network addresses to Personal devices. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.
007 The system shall provide network addresses to Connected Vehicle Roadside Equipment. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.
008 The system shall provide network addresses to other Centers. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.
009 The system shall accept network address queries based on service type provided. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.
010 The system shall accept network address queries based on service metric provided. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.
011 The system shall maintain a registry of network address, services and service metrics. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.
012 The system shall accept registration information from other Centers. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.
013 The system shall accept registration information from other Connected Vehicle Roadside Equipment. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.
014 The system shall provide the operator with a mechanism to monitor the status of its operations. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.
015 The system shall provide the operator with a mechanism to modify registrations. 01 System operators, vehicle operators, support system operators, PID users need to be able to identify the cyber addresses and services provided of other users. This is essentially a list of "what" services are supported, "who" provides each service and "where" to go to obtain these services.