Shared Use Transportation Center --> Transportation Information Center:
shared use status
Definitions
shared use status (Information Flow): Status of usage by shared use providers. Includes asset inventory and status. Could also include information on specific travelers to support multimodal trip planning.
Shared Use Transportation Center (Source Physical Object): The 'Shared Use Transportation Center' manages shared use vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the shared use fleet. It spans contract-driven and centralized dispatch vehicle services such as taxis and ride-hail services, first/last mile automated vehicles as well as personal mobility fleets such as shared-use cars, bicycles, and scooters.
Transportation Information Center (Destination Physical Object): The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.
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
- EU: SIRI - Secure Internet (ITS) (3)
- GBFS - Secure Internet (ITS) (3)
- US: MDS - Secure Internet (ITS) (3)
- Data for Distribution (TBD) - Apache Kafka (36)
- Data for Distribution (TBD) - OMG DDS (36)
- Data for Distribution (TBD) - OASIS MQTT (42)
- Data for Distribution (TBD) - OASIS AMQP (45)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
Apache Zookeeper |
Facilities
Apache Kafka Apache Zookeeper |
Security
IETF RFC 8446 |
|
TransNet
|
|||
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 | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | True |
Interoperability | Description |
---|---|
Regional | Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Moderate | Moderate | Moderate | |
Basis | Contains information for a specific traveler. If no specific traveler data is included, this could be LOW. | If this is corrupted or modified the initiator may not receive his shared use booking. | If this service is not available then the shared use item may not be reserved, lessening its utility and failing to provide the service the (PID) user needs. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |