Parking Management Center --> Personal Information Device:
registered secureIDs

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

registered secureIDs (Information Flow): Cryptographically protected identifier indicating that the user associated with the identifier is entitled to use a particular service.

Parking Management Center (Source Physical Object): The 'Parking Management Center' manages one or more parking lots by providing configuration and control of field infrastructure, user account management and interfaces with financial systems to manage payment. This p-object takes the back office portion of the Parking Management System's functionality as it was defined in ARC-IT 8.3 and prior.

Personal Information Device (Destination Physical Object): The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help.

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:

traveler_authorized_secure_id

This Triple has the following triple relationships:

None

Communication Solutions

(None-Data) - Secure Wireless Internet (EU) (43)
(None-Data) - Secure Wireless Internet (ITS) (43)

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) - Secure Wireless Internet (EU)

Solution Description

This solution is used within Australia and the E.U.. It combines standards associated with (None-Data) with those for I-M: Secure Wireless Internet (EU). The (None-Data) standards include an unspecified set of standards at the upper layers. The I-M: Secure Wireless Internet (EU) standards include lower-layer standards that support secure communications between two entities, either or both of which may be mobile devices, but they must be stationary or only moving within wireless range of a single wireless access point (e.g., a parked car). Security is based on X.509 certificates. A non-mobile (if any) endpoint may connect to the service provider using any Internet connection method.

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Bundle: SNMPv3 MIB	Facilities Development needed	Security Secure Session Alternatives
	TransNet IP Alternatives Internet Transport Alternatives
	Access Wireless Internet Alternatives (EU)

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	Local
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	High	High	Moderate
Basis	These IDs are used to secure individual user's rights to use transportation assets. Compromising one of these would be a significant inconvenience but only for the user of that secureID. However, compromise of the algorithm securing all IDs would be catastrophic to the system that uses this mechanism as a means to pay for transportation services.	Individual tokens should be correct or the user will not be able to use this method to pay for transport. A systemic integrity flaw would compromise the system similar to how an encryption flaw would however, which justifies HIGH.	Should be relatively infrequently used by any one user, but over the sum of all transport users sees significant use. If the flow is not available, new or re-applying users will not be able to use this method to pay for transport.

Security Characteristics	Value
Authenticable	True
Encrypt	True

Parking Management Center --> Personal Information Device:registered secureIDs