Link Type: Short Range Wireless

Intermodal Terminal --> Freight Equipment:
container identification request

Definitions

container identification request (Information Flow): Request to a container to provide its identification information; may require the requestor to authenticate their identity.

Intermodal Terminal (Source 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.

Freight Equipment (Destination 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.

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:

Communication Solutions

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

(None-Data) - Local Unicast Wireless (1609.2)

Solution Description

This solution is used within the U.S.. It combines standards associated with (None-Data) with those for V-X: Local Unicast Wireless (1609.2). The (None-Data) standards include an unspecified set of standards at the upper layers. The V-X: Local Unicast Wireless (1609.2) standards include lower-layer standards that support local-area unicast wireless solutions applicable to North America, such as WAVE DSRC, LTE-V2X, LTE, Wi-Fi, etc.

ITS Application Entity
Mind the gap

Development needed
Click gap icons for more info.

Mgmt

Addressed Elsewhere
Facilities

Development needed
Security
Mind the gap
TransNet

IEEE 1609.3
Access
Mind the gapMind the gapMind the gap
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

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 Source
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 Moderate Low
Basis Probably no need to obfuscate the request, though if any unique or proprietary information is requested this could change to MODERATE. If the request gets ignored or incorrectly perceived the related application will not work optimally. There should be other ways to get this data. In an intermodal terminal dependent on this information flow with less use of other mechanisms, this may increase to MODERATE.


Security Characteristics Value
Authenticable True
Encrypt False