Reserved for future use.

The signal request message (SRM) is a message sent by a V2X-equipped entity (such as a vehicle) to the RSU in a signalized intersection. It is used for either a priority signal request or a preemption signal request depending on the way each request is set. Each request defines a path through the intersection which is desired in terms of lanes and approaches to be used. Each request can also contain the time of arrival and the expected duration of the service. Multiple requests to multiple intersections are supported. The requestor identifies itself in various ways (using methods supported by the RequestorDescription data frame), and its current speed, heading, and location can be placed in this structure as well. The specific request for service is typically based on previously decoding and examining the list of lanes and approaches for that intersection (sent in MAP messages). The outcome of all of the pending requests to a signal can be found in the signal status message (SSM) and may be reflected in the SPAT message contents if successful.

The signal status message is a message sent by an RSU in a signalized intersection. It is used to relate the current status of the signal and the collection of pending or active preemption or priority requests acknowledged by the controller. It is also used to send information about preemption or priority requests which were denied. This in turn allows a dialog acknowledgment mechanism between any requester and the signal controller. The data contained in this message allows other users to determine their “ranking” for any request they have made as well as to see the currently active events. When there have been no recently received requests for service messages, this message may not be sent. While the outcome of all pending requests to a signal can be found in the signal status message, the current active event (if any) will be reflected in the SPAT message contents.

The set of TestMessage messages are used to provide expandable messages for local and regional deployment use. This is intended to support the development new message and information exchanges of their own within the common framework of the overall V2X message set and this data dictionary. A few common data elements are provided for consistency, while the remainder of the message content can be defined by the developer using the normal regional methods. It is anticipated that over time the concepts developed in these messages will migrate into the data dictionary and message set itself.