{"id":3599,"date":"2017-06-09T23:00:05","date_gmt":"2017-06-09T23:00:05","guid":{"rendered":"\/kb\/?post_type=ht_kb&#038;p=3599"},"modified":"2021-03-05T15:46:18","modified_gmt":"2021-03-05T15:46:18","slug":"sae-j2735-dsrc-message-list","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/sae-j2735-dsrc-message-list\/","title":{"rendered":"SAE J2735 DSRC Message List"},"content":{"rendered":"<p><strong>A complete list of all adopted SAE DSRC J2735 Messages with brief commentary.<\/strong><\/p>\n<p>The official release of the standard at this time is called:<br \/>\n<em><strong>SAE J2735 Dedicated Short Range Communications (DSRC) Message Set Dictionary&#x2122; (Revised: 2016-03-30)<\/strong><\/em><\/p>\n<p>Buy a complete copy, including the ASN.1 source specification\u00a0 <a href=\"https:\/\/www.sae.org\/standardsdev\/dsrc\/\" target=\"_blank\" rel=\"noopener noreferrer\">here<\/a>.<\/p>\n<h3>Comments<\/h3>\n<p>The DSRC message set is used in Intelligence Transportation Systems (or <strong>ITS<\/strong>, as in ITSware.net) as the primary means by which vehicles communicate with each other (vehicle-to-vehicle, or V2V) and the with the roadway infrastructure (vehicle-to-infrastructure, or V2I or V2x).\u00a0 Conceptually all DSRC equipped vehicles in the US and much of the rest of the world will be sending their position, velocity and acceleration data to nearby vehicles at a 10Hz rate.\u00a0 In order to do this with more accuracy, differential corrections are of great value, although they are not required to be present all of the time.\u00a0 The DSRC message set reuses stock RTCM messages wrapped in an outer ASN message which is defined in the SAE standard J2735.\u00a0 <span style=\"color: #0000ff;\"><strong>SNIP<\/strong><\/span> provides these messages (using the <a href=\"https:\/\/www.use-snip.com\/downloads\/sae-dsrc-j2735-v2x\/\" target=\"_blank\" rel=\"noopener\">DSRC Plug-In<\/a>) and that is why this list appears on a web site which is otherwise devoted the NTRIP Caster issues.<\/p>\n<p>Your rover (or OBU, or vehicle reference receiver) can obtain these messages from the <span style=\"color: #0000ff;\"><strong>SNIP<\/strong> <\/span>Caster by way of any TCP\/IP connection (typically a cell phone in the test vehicle) or by way of the the Roadside Unit (RSU).\u00a0 The precise details will vary depending on needs.<\/p>\n<p>If you are interested in the RTCM type messages you are likely to encounter in the real world, here is an article with our popular <a href=\"\/kb\/knowledge-base\/an-rtcm-message-cheat-sheet\/\">RTCM 3 cheat sheet<\/a> summary.<\/p>\n<p>The <span style=\"color: #0000ff;\"><strong>SNIP<\/strong> <\/span>Caster (when using the <a href=\"https:\/\/www.use-snip.com\/downloads\/sae-dsrc-j2735-v2x\/\" target=\"_blank\" rel=\"noopener\">DSRC Plug-In<\/a>) has several unique abilities with regards to DSRC.\u00a0 The key item of interest to most readers is that a <span style=\"color: #0000ff;\"><strong>SNIP<\/strong> <\/span>Caster is unique in its ability to create properly formatted DSRC message from RTCM corrections streams.\u00a0 This ability is required in order to send RTCM content over the DSRC message set and the DSRC Wave Short Message (WSM) channel defined by IEEE 1609.\u00a0\u00a0 The local <span style=\"color: #0000ff;\"><strong>SNIP<\/strong> <\/span>Caster provides well formed messages to a local DOT operation center which in turn distributes them to the roadside units (DSRC transmitters) located along the roadside.\u00a0 In this configuration, the rover device is typically a passing automobile which recovers the DSRC messages, decodes the ASN and strips out the RTCM connections, and feeds that to the GNSS device in the vehicle to be used in the normal way.<\/p>\n<p>The text below summarizes the tool tips that <span style=\"color: #0000ff;\"><strong>SNIP<\/strong><\/span> will display when decoding various J2735 messages from an NTRIP stream.\u00a0 Unlike other <a href=\"\/kb\/knowledge-base\/question-what-is-an-ntrip-caster\/\">NTRIP Casters<\/a>, <span style=\"color: #0000ff;\"><strong>SNIP<\/strong> <\/span>has the ability to decode and process both the DSRC and the RTCM messages to provide additional functionality.<\/p>\n<h3>The Message List<\/h3>\n<h4>Current Messages<\/h4>\n<p>All must be encoded in ASN.1 UPER format (unaligned packed encoding rules).\u00a0\u00a0 Like RTCM messages, the SAE DSRC messages have a unique assigned number and a formal name.\u00a0\u00a0 The formal name (e.g. &#8220;mapData&#8221;) comes from an ASN type definition value but each message is more often referred to by a short acronym\u00a0 (e.g. &#8220;MAP&#8221;).<\/p>\n<table>\n<tbody>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>Msg#<\/strong><\/span><\/td>\n<td width=\"542\"><span style=\"color: #0000ff;\"><strong>Message Name &amp; Usage Commentary<\/strong><\/span><\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#18<\/strong><\/span><\/td>\n<td width=\"542\"><strong><span style=\"color: #0000ff;\">mapData<\/span><br \/>\n<\/strong>The <strong>MAP<\/strong> message is used to provide intersection and roadway lane geometry data for one or more locations (e.g. intersections and fragments of maps).\u00a0 Almost all roadway geometry information as well as roadway attributes (such as where a do not block region exists, or what maneuvers are legally allowed at a given point) is contained in the \u201cgeneric lane\u201d details of this message.\u00a0 MAP messages are used in intersections to number and describe lane level details of each lane, while the SPAT message provides the current state of each signal head controlling the ability to stop\/pass a given lane.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#19<\/strong><\/span><\/td>\n<td width=\"542\"><strong><u><span style=\"color: #0000ff;\">signalPhaseAndTimingMessage<\/span><br \/>\n<\/u><\/strong>The <strong>SPAT<\/strong> message is used to provide the current signal \/ phase timing data (times at which signals will change) for one or more signalized intersections, as well as other time of day status details.\u00a0\u00a0 All SPAT messages link to MAP messages to convey the roadway details and to link the signal controller phases to the correct set of lanes.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#20<\/strong><\/span><\/td>\n<td width=\"542\"><strong><span style=\"color: #0000ff;\">basicSafetyMessage<\/span><br \/>\n<\/strong>The all-purpose <strong>BSM<\/strong> message used by both light duty vehicles and other types with various Part II content present depending on the applications being supported.\u00a0 See the different J2945\/x documents for further details.\u00a0 In simple terms, all equipped vehicles broadcast a stream of BSM messages at a 10Hz rate. Nearly all application exchanges (V2V, V2I, V2X) make use of the presence of BSMs as a prerequisite for operation.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#21<\/strong><\/span><\/td>\n<td width=\"542\"><strong><span style=\"color: #0000ff;\">commonSafetyRequest<\/span><br \/>\n<\/strong>The <strong>CSR<\/strong> message is not deployed in any known use at this time.\u00a0 Its original design intent was to allow a per vehicle request for supporting data elements in V2V safety exchanges. It has not been developed further since the 2009 edition of the standard.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#22<\/strong><\/span><\/td>\n<td width=\"542\"><strong><span style=\"color: #0000ff;\">emergencyVehicleAlert<\/span><br \/>\n<\/strong>The <strong>EVA<\/strong> message is not deployed in any known use at this time.\u00a0 Its original design intent (to announce the presence of emergency vehicles in the area).\u00a0 It has largely been replaced with the additional content now sent in the Part II section of the BSM message (See J2945\/2 for further details). It is not recommended for use in new development.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#23<\/strong><\/span><\/td>\n<td width=\"542\"><strong><span style=\"color: #0000ff;\">intersectionCollision<\/span><br \/>\n<\/strong>The <strong>ICA<\/strong> message (intersection collision announcement in this context) and is intended to\u00a0 inform other nearby users that a dangerous condition exists, or is likely to exist, in the immediate future (e.g., it can be used to detect a red light \/ stop line violation and inform others).\u00a0 It can be sourced by both vehicles and by the infrastructure.\u00a0 The ICA message wraps a BSM message (real or virtual) with additional details to reflect the estimated path of the offending vehicle.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#24<\/strong><\/span><\/td>\n<td width=\"542\"><strong><span style=\"color: #0000ff;\">nmeaCorrections<\/span><br \/>\n<\/strong>The <strong>NMEA<\/strong> message is not deployed in any known use at this time.\u00a0 Its original design intent was to provide a way to \u201cwrap\u201d NMEA-183 formatted messages for sending over the DSRC channel used in early testing.\u00a0 As these message lack the level of accuracy expected for DSRC in the BSM message (as well as other key data), there is little practical use for this message at this point.\u00a0 It is not recommended for use in new development. As with all \u201cwrapped\u201d messages, the internal content of the message is defined by another SDO (in this case NMEA, not to be confused with NEMA).<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#25<\/strong><\/span><\/td>\n<td width=\"542\"><strong><span style=\"color: #0000ff;\">probeDataManagement<\/span><br \/>\n<\/strong>The <strong>PDM<\/strong> message is used to control the details of the probe data that the vehicle will collect and then report back to RSU devices using the PVD message. In the DSRC environment vehicles can act as anonymous probes to collect traffic flow data, local weather data, and other conditions.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#26<\/strong><\/span><\/td>\n<td width=\"542\"><strong><span style=\"color: #0000ff;\">probeVehicleData<\/span><br \/>\n<\/strong>The <strong>PVD<\/strong> message is used to report details of collected probe data (meeting the data needs established by other PDM messages) to Road Side Units (RSU) devices in V2I exchanges.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#27<\/strong><\/span><\/td>\n<td width=\"542\"><strong><span style=\"color: #0000ff;\">roadSideAlert<\/span><br \/>\n<\/strong>The <strong>RSA<\/strong> message is a more primitive version of the TIM message. Its original design intent was to support the creation of simple, quick, ad hoc messages for ATIS-like informational use from public safety vehicles by a responder in the field (such as a DOT vehicle which has parked to remove a roadway obstruction) without the need for coordination with others.\u00a0 By contrast, the TIM message was intended to support more complex pre-planned incident and work zone uses.\u00a0 This distinction has blurred in more recent times, but the simplicity of deploying the RSA message is still considered of value.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#28<\/strong><\/span><\/td>\n<td width=\"542\"><strong><span style=\"color: #0000ff;\">rtcmCorrections<\/span><br \/>\n<\/strong>The <strong>RTCM<\/strong> messages are used to \u201cwrap\u201d RTCM corrections messages for sending over the DSRC channel. Corrections data allows the GNSS of each DSRC device to maintain lane level accuracy under various conditions.\u00a0 The type\/content of these messages varies with the precise kind of corrections data needed by local deployments.\u00a0 As with all \u201cwrapped\u201d messages, the internal content of the message is defined by another SDO (in this case RTCM).<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#29<\/strong><\/span><\/td>\n<td width=\"542\"><strong><span style=\"color: #0000ff;\">signalRequestMessage<\/span><br \/>\n<\/strong>The <strong>SRM<\/strong> messages are used by authorized parties to request services from an intersection signal controller.\u00a0 Vehicles approaching an intersection use this message to affect the signal operation.\u00a0 This is how traditional preemption and priority requests are handled for intersection safety in DSRC.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#30<\/strong><\/span><\/td>\n<td width=\"542\"><strong><span style=\"color: #0000ff;\">signalStatusMessage<\/span><br \/>\n<\/strong>The <strong>SSM<\/strong> messages, which are sent by the local DSRC \/ Signal Controller, are used to reflect the current operational state of the intersection signal control.\u00a0 Any prior request services (SRM messages) and their outcomes are reflected here as well.\u00a0 This message therefore serves as a means to acknowledge signal requests.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#31<\/strong><\/span><\/td>\n<td width=\"542\"><strong><span style=\"color: #0000ff;\">travelerInformation<\/span><br \/>\n<\/strong>The <strong>TIM<\/strong> message is used to contain a variety of traffic condition and \u201cadvanced traveler\u201d messages.\u00a0 It provides the means to inform the public about both incidents (traffic accidents) and pre-planned roadwork events. The TIM message can be used to alert the public to severe weather conditions and other local or regional emergencies.\u00a0\u00a0 It can also be used for a variety of speed warnings, traffic signage, road conditions and other general information.\u00a0 The ITIS codes (J2540) are prominently used in this message.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><strong><span style=\"color: #0000ff;\">#32<\/span> <\/strong><\/td>\n<td width=\"542\"><strong><span style=\"color: #0000ff;\">personalSafetyMessage<\/span><br \/>\n<\/strong>The <strong>PSM<\/strong> message is used to convey similar BSM-like information for at-risk pedestrian users (rather than being vehicle mounted). The PSM message is described in further detail in the J2945\/9 standard.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#33<\/strong><\/span><\/td>\n<td width=\"542\"><strong>Not Assigned<\/strong> at this time<br \/>\nThe next message developed would be assigned this value as per normal SAE DSRC practices.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#240~#255<\/strong><\/span><\/td>\n<td width=\"542\"><span style=\"color: #0000ff;\"><strong>testMessage00<\/strong> ~ <\/span><strong><span style=\"color: #0000ff;\">testMessage15<\/span><br \/>\n<\/strong>These sixteen messages are be used by regional deployments in any way they see fit (the definition and use of the associated message us up to the deployment).<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h4>Outdated Messages<\/h4>\n<p>All these message must be encoded in ASN.1 BER-DER format (distinguished encoding rules).\u00a0 The format of these messages reflects an earlier standard and style of encoding (published in 2009).\u00a0 These message are no longer recommended for new work.<\/p>\n<table>\n<tbody>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>Msg#<\/strong><\/span><\/td>\n<td width=\"542\"><span style=\"color: #0000ff;\"><strong>Message Name &amp; Usage Commentary<\/strong><\/span><\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#0<\/strong><\/span><\/td>\n<td width=\"542\">Reserved by SAE DSRC TC for use<br \/>\nA placeholder message value in the outdated DER encoding.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#1<\/strong><\/span><\/td>\n<td width=\"542\"><strong>alaCarteMessage-D<\/strong> (retired)<br \/>\nA retired message value in the outdated DER encoding.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#2<\/strong><\/span><\/td>\n<td width=\"542\"><strong>basicSafetyMessage-D<br \/>\n<\/strong>The older BSM msg, in the outdated DER encoding, not recommended for new use.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#3<\/strong><\/span><\/td>\n<td width=\"542\"><strong>basicSafetyMessageVerbose-D<\/strong><br \/>\nThe older BSM msg in its verbose format (allowing optional content), in the outdated DER encoding.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#4<\/strong><\/span><\/td>\n<td width=\"542\"><strong>commonSafetyRequest-D<\/strong><br \/>\nA rarely used msg in the outdated DER encoding, not recommended for new use.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#5<\/strong><\/span><\/td>\n<td width=\"542\"><strong>emergencyVehicleAlert-D<\/strong><br \/>\nA rarely used msg in the outdated DER encoding, not recommended for new use.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#6<\/strong><\/span><\/td>\n<td width=\"542\"><strong>intersectionCollision-D<\/strong><br \/>\nA rarely used msg in the outdated DER encoding, not recommended for use.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#7<\/strong><\/span><\/td>\n<td width=\"542\"><strong>mapData-D<\/strong><br \/>\nThe MSP msg in the outdated DER encoding, not recommended for new use.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#8<\/strong><\/span><\/td>\n<td width=\"542\"><strong>nmeaCorrections-D<\/strong><br \/>\nA rarely used msg in the outdated DER encoding, not recommended for new use.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#9<\/strong><\/span><\/td>\n<td width=\"542\"><strong>probeDataManagement-D<\/strong><br \/>\nA rarely used msg in the outdated DER encoding, not recommended for new use.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#10<\/strong><\/span><\/td>\n<td width=\"542\"><strong>probeVehicleData-D<\/strong><br \/>\nA rarely used msg in the outdated DER encoding, not recommended for new use.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#11<\/strong><\/span><\/td>\n<td width=\"542\"><strong>roadSideAlert-D<\/strong><br \/>\nA simple form of the TIM msg,\u00a0 in the outdated DER encoding, not recommended for new use.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#12<\/strong><\/span><\/td>\n<td width=\"542\"><strong>rtcmCorrections-D<\/strong><br \/>\nThe msg used to send RTCM data, in the outdated DER encoding, not recommended for new use.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#13<\/strong><\/span><\/td>\n<td width=\"542\"><strong>signalPhaseAndTimingMessage-D<\/strong><br \/>\nThe SPAT, a signal safety msg in the outdated DER encoding, not recommended for new use.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#14<\/strong><\/span><\/td>\n<td width=\"542\"><strong>signalRequestMessage-D<\/strong><br \/>\nA signal safety msg in the outdated DER encoding, not recommended for new use.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#15<\/strong><\/span><\/td>\n<td width=\"542\"><strong>signalStatusMessage-D<\/strong><br \/>\nA signal safety msg in the outdated DER encoding, not recommended for new use.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#16<\/strong><\/span><\/td>\n<td width=\"542\"><strong>travelerInformation-D<\/strong><br \/>\nThe TIM msg in the outdated DER encoding, not recommended for new use.<\/td>\n<\/tr>\n<tr>\n<td width=\"96\"><span style=\"color: #0000ff;\"><strong>#17<\/strong><\/span><\/td>\n<td width=\"542\"><strong>uperFrame-D<\/strong><br \/>\nA frame msg in the outdated DER encoding to hold other content, not recommended for new use.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>See Also<\/h3>\n<p>These related message sets may also be of interest to you.<\/p>\n<p style=\"padding-left: 30px;\"><a href=\"\/kb\/knowledge-base\/an-rtcm-message-cheat-sheet\/\">A <em>cheat sheet<\/em> of the most popular <strong>RTCM 3 Messages<\/strong><\/a>.<\/p>\n<p style=\"padding-left: 30px;\">A complete list of all adopted <strong>RTCM 3 Messages<\/strong> with commentary.<\/p>\n<p style=\"padding-left: 30px;\">A complete list of all adopted <a href=\"\/kb\/knowledge-base\/rtcm-2-message-list\/\"><strong>RTCM 2 Messages<\/strong><\/a> with commentary.<\/p>\n<p style=\"padding-left: 30px;\">Common <a href=\"\/kb\/knowledge-base\/nmea-gga-strings-in-ntrip-clients\/\">NMEA-183 messages<\/a> of interest to GNSS NTRIP users\u00a0 <a href=\"http:\/\/home.mira.net\/~gnb\/gps\/nmea.html\">Site-1<\/a>\u00a0 and <a href=\"http:\/\/www.gpsinformation.org\/dale\/nmea.htm\">Site-2.<\/a><\/p>\n<p>The only way to truly understand the details of the SAE DSRC message set is to purchase a copy for yourself from SAE, please do so if you have interest.\u00a0 Here is the <a href=\"https:\/\/www.sae.org\/standardsdev\/dsrc\/\">web page <\/a>with some of the SAE standards you would need to do DSRC development work.<\/p>\n<hr \/>\n<p><span style=\"color: #0000ff;\"><strong>SNIP<\/strong> <\/span>is a robust <a href=\"\/kb\/knowledge-base\/question-what-is-an-ntrip-caster\/\"><strong>NTRIP Caster<\/strong><\/a>, but it also has built in utilities useful for message decoding<\/p>\n<p style=\"padding-left: 30px;\">Need to see the internal contents of these messages?\u00a0 Use <span style=\"color: #0000ff;\"><strong>SNIP<\/strong><\/span>&#8216;s <a href=\"\/kb\/knowledge-base\/using-the-rtcm3-decoder-dialog\/\">RTCM3 Decoder<\/a> feature.<\/p>\n<p style=\"padding-left: 30px;\">Need to use these messages in a navigation solution?\u00a0 Use <span style=\"color: #0000ff;\"><strong>SNIP<\/strong><\/span>&#8216;s <a href=\"\/kb\/knowledge-base\/graphical-monitoring\/\">Graphical Display<\/a> feature<\/p>\n<p style=\"padding-left: 30px;\">Need to quickly plot the <a href=\"\/kb\/knowledge-base\/converting-ecef-to-llh-and-back\/\">ECEF<\/a> location of a base station?\u00a0 Use <span style=\"color: #0000ff;\"><strong>SNIP<\/strong><\/span>&#8216;s <a href=\"\/kb\/knowledge-base\/support-for-basic-mapping\/\">Mapping<\/a> feature.<\/p>\n<p style=\"text-align: center;\"><a href=\"https:\/\/www.use-snip.com\/download\/\" target=\"_blank\" rel=\"noopener noreferrer\"><strong>Download your own copy of SNIP today<\/strong><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A complete list of all adopted SAE DSRC J2735 Messages with brief commentary. The official release of the standard at this time is called: SAE J2735 Dedicated Short Range Communications (DSRC) Message Set Dictionary&#x2122; (Revised: 2016-03-30) Buy a complete copy, including the ASN.1 source specification\u00a0 here. Comments The DSRC message [&hellip;]<\/p>\n","protected":false},"author":13,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"ht-kb-category":[341],"ht-kb-tag":[295,338,294,504],"class_list":["post-3599","ht_kb","type-ht_kb","status-publish","format-standard","hentry","ht_kb_category-message-decoding","ht_kb_tag-decoder","ht_kb_tag-dsrc","ht_kb_tag-message-types","ht_kb_tag-v2x"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.3 (Yoast SEO v27.3) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>SAE J2735 DSRC Message List - SNIP Support<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.use-snip.com\/kb\/knowledge-base\/sae-j2735-dsrc-message-list\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SAE J2735 DSRC Message List\" \/>\n<meta property=\"og:description\" content=\"A complete list of all adopted SAE DSRC J2735 Messages with brief commentary. The official release of the standard at this time is called: SAE J2735 Dedicated Short Range Communications (DSRC) Message Set Dictionary&#x2122; (Revised: 2016-03-30) Buy a complete copy, including the ASN.1 source specification\u00a0 here. Comments The DSRC message [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.use-snip.com\/kb\/knowledge-base\/sae-j2735-dsrc-message-list\/\" \/>\n<meta property=\"og:site_name\" content=\"SNIP Support\" \/>\n<meta property=\"article:modified_time\" content=\"2021-03-05T15:46:18+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/knowledge-base\\\/sae-j2735-dsrc-message-list\\\/\",\"url\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/knowledge-base\\\/sae-j2735-dsrc-message-list\\\/\",\"name\":\"SAE J2735 DSRC Message List - SNIP Support\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/#website\"},\"datePublished\":\"2017-06-09T23:00:05+00:00\",\"dateModified\":\"2021-03-05T15:46:18+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/knowledge-base\\\/sae-j2735-dsrc-message-list\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/knowledge-base\\\/sae-j2735-dsrc-message-list\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/knowledge-base\\\/sae-j2735-dsrc-message-list\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SAE J2735 DSRC Message List\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/#website\",\"url\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/\",\"name\":\"SNIP NTRIP Caster Support\",\"description\":\"SNIP NTRIP Caster Support\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/#organization\",\"name\":\"SNIP Support\",\"alternateName\":\"NTRIP Caster\",\"url\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/wp-content\\\/uploads\\\/2016\\\/08\\\/SNIPwStreamUsers.png\",\"contentUrl\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/wp-content\\\/uploads\\\/2016\\\/08\\\/SNIPwStreamUsers.png\",\"width\":1132,\"height\":723,\"caption\":\"SNIP Support\"},\"image\":{\"@id\":\"https:\\\/\\\/www.use-snip.com\\\/kb\\\/#\\\/schema\\\/logo\\\/image\\\/\"}}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"SAE J2735 DSRC Message List - SNIP Support","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/sae-j2735-dsrc-message-list\/","og_locale":"en_US","og_type":"article","og_title":"SAE J2735 DSRC Message List","og_description":"A complete list of all adopted SAE DSRC J2735 Messages with brief commentary. The official release of the standard at this time is called: SAE J2735 Dedicated Short Range Communications (DSRC) Message Set Dictionary&#x2122; (Revised: 2016-03-30) Buy a complete copy, including the ASN.1 source specification\u00a0 here. Comments The DSRC message [&hellip;]","og_url":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/sae-j2735-dsrc-message-list\/","og_site_name":"SNIP Support","article_modified_time":"2021-03-05T15:46:18+00:00","twitter_card":"summary_large_image","twitter_misc":{"Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/sae-j2735-dsrc-message-list\/","url":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/sae-j2735-dsrc-message-list\/","name":"SAE J2735 DSRC Message List - SNIP Support","isPartOf":{"@id":"https:\/\/www.use-snip.com\/kb\/#website"},"datePublished":"2017-06-09T23:00:05+00:00","dateModified":"2021-03-05T15:46:18+00:00","breadcrumb":{"@id":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/sae-j2735-dsrc-message-list\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.use-snip.com\/kb\/knowledge-base\/sae-j2735-dsrc-message-list\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/sae-j2735-dsrc-message-list\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.use-snip.com\/kb\/"},{"@type":"ListItem","position":2,"name":"SAE J2735 DSRC Message List"}]},{"@type":"WebSite","@id":"https:\/\/www.use-snip.com\/kb\/#website","url":"https:\/\/www.use-snip.com\/kb\/","name":"SNIP NTRIP Caster Support","description":"SNIP NTRIP Caster Support","publisher":{"@id":"https:\/\/www.use-snip.com\/kb\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.use-snip.com\/kb\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.use-snip.com\/kb\/#organization","name":"SNIP Support","alternateName":"NTRIP Caster","url":"https:\/\/www.use-snip.com\/kb\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.use-snip.com\/kb\/#\/schema\/logo\/image\/","url":"https:\/\/www.use-snip.com\/kb\/wp-content\/uploads\/2016\/08\/SNIPwStreamUsers.png","contentUrl":"https:\/\/www.use-snip.com\/kb\/wp-content\/uploads\/2016\/08\/SNIPwStreamUsers.png","width":1132,"height":723,"caption":"SNIP Support"},"image":{"@id":"https:\/\/www.use-snip.com\/kb\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/3599","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb"}],"about":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/types\/ht_kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/comments?post=3599"}],"version-history":[{"count":40,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/3599\/revisions"}],"predecessor-version":[{"id":7584,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb\/3599\/revisions\/7584"}],"wp:attachment":[{"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/media?parent=3599"}],"wp:term":[{"taxonomy":"ht_kb_category","embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb-category?post=3599"},{"taxonomy":"ht_kb_tag","embeddable":true,"href":"https:\/\/www.use-snip.com\/kb\/wp-json\/wp\/v2\/ht-kb-tag?post=3599"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}