Proprietary Data - Proprietary Comm
Description
This solution is used within Australia, Canada, the E.U. and the U.S.. It combines standards associated with Proprietary Data with those for Proprietary Comm. The Proprietary Data standards include upper–layer technologies that do not necessarily follow standards. The Proprietary Comm standards include lower–layer technologies that do not necessarily follow standards.
Includes Standards
| Level | DocNum | FullName | Description |
|---|
| Mgmt | | Proprietary | A proprietary mechanism to provide services for this layer. |
|---|
| Security | | Proprietary | A proprietary mechanism to provide services for this layer. |
|---|
| ITS Application Entity | | Proprietary | A proprietary mechanism to provide services for this layer. |
|---|
| Facilities | | Proprietary | A proprietary mechanism to provide services for this layer. |
|---|
| TransNet | | Proprietary | A proprietary mechanism to provide services for this layer. |
|---|
| Access | | Proprietary | A proprietary mechanism to provide services for this layer. |
|---|
Readiness: Low
Readiness Description
One serious or several significant issues. This category often includes proprietary or partial solutions. The communications solution may fail to provide even a base level of interoperability and security. Consider alternative solutions, or define specific revisions or upgrades that would provide a level of interoperability or security that are needed for the deployment.
Issues
| Issue | Severity | Description | Associated Standard | Associated Triple |
|---|
| Proprietary Solution | High | The profile is not defined in a standard and represents a proprietary design | (None) | (All) |
|---|
Supports Interfaces
| Source | Destination | Flow |
|---|
| PennDOT Field Devices – State | Commercial Vehicles | request tag data |
|---|