Connected Vehicle Roadside Equipment --> Transit Vehicle OBE:
transit stop request

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

transit stop request (Information Flow): Notification that a transit stop has been requested by a transit user at a roadside stop. This flow identifies the route, stop, and the time of the request.

Connected Vehicle Roadside Equipment (Source Physical Object): 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.

Transit Vehicle OBE (Destination Physical Object): The 'Transit Vehicle On-Board Equipment' (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit vehicles.

Included In

This Triple is in the following Service Packages:

PT15: Transit Stop Request

This triple is associated with the following Functional Objects:

This Triple is described by the following Functional View Data Flows:

transit_stop_request_from_roadside

This Triple has the following triple relationships:

Relationship	Source	Destination	Flow
Interactive	Transit Vehicle OBE	Connected Vehicle Roadside Equipment	transit vehicle information

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) - G5 TCP

Solution Description

This solution is used within Australia and the E.U.. It combines standards associated with (None-Data) with those for V-X: G5 TCP. The (None-Data) standards include an unspecified set of standards at the upper layers. The V-X: G5 TCP standards include lower-layer standards that support broadcast, near constant, low latency vehicle-to-vehicle and vehicle-to-infrastructure communications using the ETSI GeoNetworking Bundle with TCP/IPv6 over the 5.9GHz spectrum.

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Bundle: G5 Congestion Control Management	Facilities Development needed	Security Bundle: ETSI ITS-S Security Architecture
	TransNet Bundle: GeoNetworking IPv6 IETF RFC 9293
	Access Bundle: ETSI ITS-G5

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	False
Cardinality	Unicast
Initiator	Source
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	Moderate	Moderate
Basis	Contains PII, including traveler identity, location and stop request information, which is predictive of traveler location.	If corrupted, stop request may not be received or acted upon, which would affect the originator of the request. Limited in scope to that request though.	If this flow is not available then stop requests won't be completed and the originator of the request is inconvenienced. Long term however, if this flow is generally not reliable then users are unlikely to use or rely on it. Should be MODERATE to instill confidence and encourage use.

Security Characteristics	Value
Authenticable	True
Encrypt	True

Connected Vehicle Roadside Equipment --> Transit Vehicle OBE:transit stop request