This solution is used within Australia, the E.U. and the U.S.. It combines standards associated with TPEG2 with those for C–X: Wide Area Broadcast. The TPEG2 standards include upper–layer standards required to support multi–modal information services.. The C–X: Wide Area Broadcast standards include lower–layer standards that support one entity broadcasting information to all wireless devices over an area that covers at least a metropolitan area without any expectation of acknowledgement or response; security is provided by the upper–layers.
| Level | DocNum | FullName | Description |
|---|
| Mgmt | | Proprietary | A proprietary mechanism to provide services for this layer. |
|---|
| Mgmt | ISO 21219–6 | Intelligent transport systems – Traffic and travel information via transport protocol experts group, generation 2(TPEG2) –– Part 6: Message management container (TPEG2–MMC) | ISO 21219–6 adds a basic toolkit definition to the ISO 21219 series specifying the Message Management Container (MMC), which is used by all TPEG applications to provide information about the handling of messages on the TPEG client side. The MMC holds administrative information allowing a decoder to handle the message appropriately. This information is not aimed at the end user. The MMC is a toolkit and not a stand–alone application but is included in TPEG applications. |
|---|
| Security | | Proprietary | A proprietary mechanism to provide services for this layer. |
|---|
| Security | ISO 21219–24 | Intelligent transport systems – Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) –– Part 24: Light encryption (TPEG2–LTE) | ISO/TS 21219–24 defines the LTE encryption mechanism for TPEG Service Data Frames. It has been specifically designed for use with Business–to–Business (B2B) business models. The objective of this document is to provide a simple to use, yet effective Conditional Access mechanism for TPEG including encryption for use with both broadcast and/or point–to–point delivery. For both service providers and device manufacturers, a standardized conditional access mechanism is beneficial to avoid a proliferation of proprietary methods with multiplied implementation effort and lead times. |
|---|
| ITS Application Entity | ISO 21219–15 | Intelligent transport systems –– Traffic and travel information (TTI) via transport protocol experts group, generation 2 (TPEG2) –– Part 15: Traffic event compact (TPEG2–TEC) | ISO/TS 21219–15 specifies the TPEG application: Traffic Event Compact. This application has been specifically designed to support information about traffic events (e.g. road works, traffic jams). A specific form of traffic events are local hazard warnings which, being safety–related messages, are sent with high priority to warn a driver that may encounter dangerous situations (e.g. black–ice, accident beyond curves, obstacles on road, etc.) unexpectedly. |
|---|
| Facilities | No Standard Needed | No Standard Needed | The services related to this portion of the stack are not critical within the scope of this solution. |
|---|
| TransNet | | Proprietary | A proprietary mechanism to provide services for this layer. |
|---|
| Access | | Satellite Broadcast Alternatives | A set of alternative standards that includes all satellite–based wireless broadcast technologies. |
|---|
One significant or possibly a couple minor issues. For existing deployments, the chosen solution likely has identified security or management issues not addressed by the communications solution. Deployers should consider additional security measures, such as communications link and physical security as part of these solutions. They should also review the management issues to see if they are relevant to their deployment and would require mitigation. For new deployments, the deployment efforts should consider a path to addressing these issues as a part of their design activities. The solution does not by itself provide a fully secure implementation without additional work.
| Issue | Severity | Description | Associated Standard | Associated Triple |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | Summit County Engineer Website=>broadcast traveler information=>Commercial Vehicles |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | ODOT OHGO Traveler Information System=>broadcast traveler information=>Commercial Vehicles |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | OTIC Website=>road weather advisories=>OTIC Public Service Vehicles |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | OTIC Website=>broadcast traveler information=>OTIC Public Service Vehicles |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | OTIC Website=>broadcast traveler information=>Personal Information Device |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | City of Green Traffic Information Website=>broadcast traveler information=>Personal Information Device |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | City of Green Traffic Information Website=>broadcast traveler information=>Commercial Vehicles |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | City of Green Traffic Information Website=>broadcast traveler information=>Connected/Automated Vehicles |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | DriveAkron=>broadcast traveler information=>Personal Information Device |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | DriveAkron=>broadcast traveler information=>Commercial Vehicles |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | ODOT OHGO Traveler Information System=>broadcast traveler information=>Personal Information Device |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | Summit County Engineer Website=>broadcast traveler information=>Personal Information Device |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | Summit County Engineer Website=>broadcast traveler information=>Connected/Automated Vehicles |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | Portage County Website=>broadcast traveler information=>Personal Information Device |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | Portage County Website=>broadcast traveler information=>Commercial Vehicles |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | Portage County Website=>broadcast traveler information=>Connected/Automated Vehicles |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | Akron–Canton Airport=>broadcast traveler information=>Personal Information Device |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | Akron–Canton Airport=>broadcast traveler information=>Commercial Vehicles |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | Other City Traffic Information Websites=>broadcast traveler information=>Commercial Vehicles |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | Other City Traffic Information Websites=>broadcast traveler information=>Connected/Automated Vehicles |
|---|
| Overlap of standards | Medium | Multiple standards have been developed to address this information and it is unclear which standard should be used to address this specific information flow. | (None) | DriveAkron=>broadcast traveler information=>Connected/Automated Vehicles |
|---|
| Secure data access not provided | Medium | The solution does not define rules on how the application entity authenticates requests to accept or provide data. | (None) | (All) |
|---|
| Use case not considered in design (medium) | Medium | While the indicated standards nominally address the information flow, the design may not meet practical constraints because this particular use case was not the focus of the design effort. | (None) | OTIC Website=>road weather advisories=>OTIC Public Service Vehicles |
|---|
| Ubiquitous broadcast technology | Low | With the continual enhancement of broadcast technologies and a mixture of free and subscriber–based systems, it is difficult to identify any single technology that can be used to reliably reach the bulk of drivers in a timely manner. | (None) | (All) |
|---|
| Source | Destination | Flow |
|---|
| Akron–Canton Airport | Commercial Vehicles | broadcast traveler information |
|---|
| Akron–Canton Airport | Personal Information Device | broadcast traveler information |
|---|
| City of Green Traffic Information Website | Commercial Vehicles | broadcast traveler information |
|---|
| City of Green Traffic Information Website | Connected/Automated Vehicles | broadcast traveler information |
|---|
| City of Green Traffic Information Website | Personal Information Device | broadcast traveler information |
|---|
| DriveAkron | Commercial Vehicles | broadcast traveler information |
|---|
| DriveAkron | Connected/Automated Vehicles | broadcast traveler information |
|---|
| DriveAkron | Personal Information Device | broadcast traveler information |
|---|
| ODOT OHGO Traveler Information System | Commercial Vehicles | broadcast traveler information |
|---|
| ODOT OHGO Traveler Information System | Personal Information Device | broadcast traveler information |
|---|
| Other City Traffic Information Websites | Commercial Vehicles | broadcast traveler information |
|---|
| Other City Traffic Information Websites | Connected/Automated Vehicles | broadcast traveler information |
|---|
| OTIC Website | OTIC Public Service Vehicles | broadcast traveler information |
|---|
| OTIC Website | OTIC Public Service Vehicles | road weather advisories |
|---|
| OTIC Website | Personal Information Device | broadcast traveler information |
|---|
| Portage County Website | Commercial Vehicles | broadcast traveler information |
|---|
| Portage County Website | Connected/Automated Vehicles | broadcast traveler information |
|---|
| Portage County Website | Personal Information Device | broadcast traveler information |
|---|
| Summit County Engineer Website | Commercial Vehicles | broadcast traveler information |
|---|
| Summit County Engineer Website | Connected/Automated Vehicles | broadcast traveler information |
|---|
| Summit County Engineer Website | Personal Information Device | broadcast traveler information |
|---|