Other Border Inspection Systems --> Border Inspection System:
border field equipment data

This triple is bi-directional. See also Border Inspection System --> Other Border Inspection Systems: border field equipment data

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

border field equipment data (Information Flow): Data such as camera images and radiation sensor data.

Other Border Inspection Systems (Source Physical Object): Representing another set of Border Inspection Systems, 'Other Border Inspection Systems' is intended to provide a source and destination for information exchange between international border inspection functions. It enables traffic management activities to be coordinated across international borders..

Border Inspection System (Destination Physical Object): 'Border Inspection System' represents data systems used at the border for the inspection of people or goods. It supports immigration, customs (trade), agricultural, and FDA inspections as applicable. It includes sensors and surveillance systems to identify and classify drivers and their cargo as they approach a border crossing, the systems used to interface with the back-office administration systems and provide information on status of the crossing or events.

Included In

This Triple is in the following Service Packages:

CVO22: International Border Coordination

This triple is associated with the following Functional Objects:

Border Inspection

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)

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) - Apache Kafka

Solution Description

This solution is used within the U.S.. It combines standards associated with (None-Data) with those for Apache Kafka. The (None-Data) standards include an unspecified set of standards at the upper layers. The Apache Kafka standards include lower-layer open source code that supports data distribution of specific types of data.

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Apache Zookeeper	Facilities Development needed Apache Kafka Apache Zookeeper	Security IETF RFC 8446
	TransNet IP Alternatives IETF RFC 9293
	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	Adjacent
Acknowledgement	True
Cardinality	Unicast
Initiator	Destination
Authenticable	True
Encrypt	True

Interoperability	Description
Local	In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides.

Security

Information Flow Security
	Confidentiality	Integrity	Availability
Rating	Moderate	Moderate	Moderate
Basis	Could be used as remote monitoring feed for the border, and so should be obfuscated to prevent unauthorized remote viewing of border circumstances. Also, some of the data reported here may not be casually observable.	Used to coordinate border operations; if incorrect, unavailable or manipulated could lead to an error in border crossing.	Used to coordinate border operations; if incorrect, unavailable or manipulated could lead to an error in border crossing.

Security Characteristics	Value
Authenticable	True
Encrypt	True

Other Border Inspection Systems --> Border Inspection System:border field equipment data