Parent Service Package: SU06
< < SU05.3 : SU06.1 : SU07.1 > >

SU06.1: Object Registration and Discovery Implementation

This 'implementation' is a holistic view of the SU06 service package, including all Physical Objects, Functional Objects, and Triples associated with the service package. It distinguishes between items that are fundamental to the service and items that are optional. Your specific implementation is likely to include the fundamental items and selected optional items, based on your specific project requirements.

Relevant Regions:

Enterprise
Functional
Physical
Goals and Objectives
Needs and Requirements
Sources
Security
Standards
System Requirements

Enterprise

Development Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
ITS Object Developer	ITS Object	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
ITS Object Developer	Object Registration and Discovery System Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
ITS Object Developer	Vehicle Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Object Registration and Discovery System Developer	ITS Object Developer	Application Interface Specification (hide) The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Object Registration and Discovery System Developer	Object Registration and Discovery System	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Vehicle Developer	Vehicle	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.

Installation Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
ITS Object Installer	ITS Object	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
ITS Object Owner	ITS Object Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
ITS Object Owner	ITS Object Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Object Registration and Discovery System Installer	Object Registration and Discovery System	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Object Registration and Discovery System Owner	Object Registration and Discovery System Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Object Registration and Discovery System Owner	Object Registration and Discovery System Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Vehicle Installer	Vehicle	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Vehicle Owner	Vehicle Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Vehicle Owner	Vehicle Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.

Operations and Maintenance Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Driver	Vehicle	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
ITS Object Maintainer	ITS Object	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
ITS Object Manager	ITS Object	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
ITS Object Owner	Driver	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
ITS Object Owner	ITS Object Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
ITS Object Owner	ITS Object Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
ITS Object Owner	Object Registration and Discovery System Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
ITS Object Owner	Object Registration and Discovery System Owner	Expectation of Information Provision (hide) An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient.
ITS Object Owner	Object Registration and Discovery System User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
ITS Object Owner	ORDS Operator	Application Usage Agreement (hide) An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
ITS Object Owner	Vehicle Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
ITS Object Owner	Vehicle User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
ITS Object Supplier	ITS Object Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Object Registration and Discovery System Maintainer	Object Registration and Discovery System	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Object Registration and Discovery System Manager	Object Registration and Discovery System	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Object Registration and Discovery System Manager	ORDS Operator	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Object Registration and Discovery System Owner	ITS Object Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Object Registration and Discovery System Owner	ITS Object User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Object Registration and Discovery System Owner	Object Registration and Discovery System Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Object Registration and Discovery System Owner	Object Registration and Discovery System Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Object Registration and Discovery System Supplier	Object Registration and Discovery System Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
ORDS Operator	Object Registration and Discovery System	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Vehicle Maintainer	Vehicle	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Vehicle Manager	Driver	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Vehicle Manager	Vehicle	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Vehicle Owner	Vehicle Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Vehicle Owner	Vehicle Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Vehicle Supplier	Vehicle Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
ITS Object	ITS Management Support	10.6.4.2	Support ITS Object Management
Object Registration and Discovery System	Object Registration and Discovery	10.7.1	Support Object Registration and Discovery
Vehicle	Vehicle Support Services	10.6.3.1	Support Vehicle System Communications

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 (including motorcycles), 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

Associated Objective Categories

Objective Category

Associated Objectives and Performance Measures

Objective	Performance Measure

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

Related Sources

Document Name	Version	Publication Date
None

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
Object Registration and Discovery System
Vehicle

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
Source	Destination	Information Flow	Basis	Basis	Basis
ITS Object	Object Registration and Discovery System	object registration	Low	High	Moderate
ITS Object	Object Registration and Discovery System	object registration	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
ITS Object	Vehicle	service advertisement	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
Object Registration and Discovery System	ITS Object	object discovery	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
Object Registration and Discovery System	ORDS Operator	ORDS operations information presentation	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
ORDS Operator	Object Registration and Discovery System	ORDS operator input	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. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.

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

System Requirements

No System Requirements