Link Type: Center to Center
Traffic Regulatory Authority Center --> Map Update System:
traffic-related regulations
Definitions
traffic-related regulations (Information Flow): Traffic rules, regulations, ordinances and statutes that have official status and must be understood by all motor vehicle operators and intelligent vehicles that operate at higher automation levels. The flow includes the regulations and the associated locations, effective date and time periods, and applicable vehicle classes. This flow supports bulk transfer of regulations, rules, statutes, and related attributes between back office systems.
Traffic Regulatory Authority Center (Source Physical Object): The 'Traffic Regulatory Authority Center' is the authoritative source for traffic rules, regulations, ordinances and statutes that have official status and must be understood by all motor vehicle operators and intelligent vehicles that operate at higher automation levels. This center may represent multiple authorities that operate at local, regional, state, and national levels and represents organizations that establish, manage, and enact the traffic code.
Map Update System (Destination Physical Object): The 'Map Update System' represents a provider of map databases used to support ITS services. It supports the provision of the map data that are used directly by vehicles (e.g., roadway and intersection geometry data sets), travelers (e.g., navigable maps used for route guidance and display maps used at traveler information points), system operators (e.g., map data used by Traffic Operators to monitor and manage the road network, and map data used by Fleet Managers to manage a vehicle fleet). It may represent a third-party provider or an internal organization that produces map data for agency use. In the latter case, the 'Map Update System' is typically included as part of the center (e.g., a Traffic Management Center) of the infrastructure owner/operator that manages map data. Products may include simple display maps, map data sets that define detailed road network topology and geometry, or full geographic information system databases that are used to support planning and operations.
Included In
This Triple is in the following Service Packages:
This Triple is in the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
None |
Communication Solutions
-
(None-Data) - Secure Internet (ITS) (32)
-
(None-Data) - Apache Kafka (36)
-
(None-Data) - OMG DDS (36)
-
(None-Data) - OASIS MQTT (42)
-
(None-Data) - OASIS AMQP (45)
Selected Solution

Solution Description
ITS Application Entity
![]() Development needed ![]() |
Click gap icons for more info.
|
||
Mgmt
OMG DDS ![]() |
Facilities
![]() ![]() Development needed ![]() OMG DDS ![]() OMG DDS-RPC ![]() OMG DDSI-RTPS ![]() |
Security
OMG DDS-Security ![]() |
|
TransNet
|
|||
Access
Internet Subnet Alternatives ![]() |
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Destination |
Authenticable | True |
Encrypt | False |
Interoperability | Description |
---|---|
National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Low | High | Moderate | |
Basis | Regulations should be publicly accessible, so observation of this flow gains no information that could not be obtained legitimately. | Regulations may be used to guide operations, particularly for automated vehicles. As such, inaccurate regulations imply the vehicle operator (human or otherwise) may inadvertently violate regulations, possibly endangering the safety of others expecting the operator or vehicle to follow the rules of the road. | Regulations will be used to guide the operator, which may be an autonomous vehicle. As such the regulations need to be kept up to date to avoid conflict with regulations, penalties or of course safety of life. Availability is not considered HIGH as it is unlikely that such regulations that affect safety would change very often. In environments where it is envisioned that safety-impacting regulations change quickly, HIGH would be justified. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |