Freight Equipment --> Intermodal Terminal:
container identification
Definitions
container identification (Information Flow): A unique identification of a container that can be used to associate the container with a manifest and other important data.
Freight Equipment (Source Physical Object): 'Freight Equipment' represents a freight container, intermodal chassis, or trailer and provides sensory, processing, storage, and communications functions necessary to support safe, secure and efficient freight operations. It provides equipment safety data and status and can alert the appropriate systems of an incident, breach, or tamper event. It also provides accurate position information to support in-transit visibility of freight equipment.
Intermodal Terminal (Destination Physical Object): The 'Intermodal Terminal' represents the terminal areas corresponding to modal change points. This includes interfaces between roadway freight transportation and air, rail, and/or water shipping modes. The basic unit of cargo handled by the Intermodal Terminal physical object is the container; less-than-container load handling is typically handled at a different facility (i.e., Freight Consolidation Station). The Intermodal Terminal can include electronic gate control for entrance and exit from the facility, automated guidance of vehicles within the facility, alerting appropriate parties of container arrivals and departures, and inventory and location of temporarily stored containers.
Included In
This Triple is in the following Service Packages:
This triple is associated with 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
- ISO: Equipment Identification - Local Unicast Wireless (1609.2) (17)
- (None-Data) - Local Unicast Wireless (EU) (54)
Selected Solution
Solution Description
ITS Application Entity
ISO 14816 |
Click gap icons for more info.
|
||
Mgmt
Addressed Elsewhere |
Facilities
No Standard Needed |
Security
|
|
TransNet
IEEE 1609.3 |
|||
Access
|
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 | Adjacent |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Destination |
Authenticable | True |
Encrypt | True |
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 | Moderate | Moderate | Moderate | |
Basis | Possibly competetive information. Definitely has value, and if availble to actors with competing interests to the actors legitimately involved with the container, information as to where the container is and is projected to be at different times could be abused to the actor's advantage.For high value containers, this may be HIGH. | Possibly competetive, and also with legal and criminal implications. Container ID needs to be correct to deter fraudlence, smuggling and related activities.For high value containers, this may be HIGH. | There should be other means to identify the container, but without this flow accurate tracking becomes more difficult. For high value containers, this may be HIGH. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |