 |
 |
 |
 |
|
 |
 |
SAE J2735-Draft-Rev29 [issued: 12-11-08]
-
230 -
This is an SAE Motor Vehicle Council draft document of the DSRC committee, subject to change.
11.3
URLs used in the standard
The standard makes use of URL strings in various places to link to other information. At times the data
elements used to convey the full URL break the string up into component parts. This is done to save
payload bytes in the transmitted message. The data element URL-Short must be combined with the contents
of the data element URL-Base to create a valid URL string in such cases.
Annex A Message Framework
Introduction
This annex is intended as a guide for message framework issues.
Message Common Header
A message common header element is a data element in a message that is common to all messages. It is
part of the transmitted message, is not changed by any lower levels and is required and used by a receiving
application or applications. The only identified message common header element in this standard is the
message ID included as the first word of content in all messages.
Application Programming Interface
An Application Programming Interface (API) is required to process common management information not
included in a message (Application Protocol Data Unit). This message related information is not
transmitted as part of the message set. An API for J2735 purposes is either information provided by an
application which is required by the application’s lower layers or is information required by an application
and provided by the application’s lower layers. The mechanism of communication is not considered in
scope for J2735 and may or may not be provided by other standards. Any J2735 API should include the
transmitted power level and the message priority.
Temporary ID
The Temporary ID, an element of the Basic Safety Message, might occasionally need to be changed for
purposes of privacy. The Temporary ID value should be chosen randomly and is separate from any other
identifier in the vehicle. Thus any relationship it might have with any other identifier is out of scope for the
J2735 standard. A vehicle should refrain from changing the temporary vehicle ID when event flags are
set. A mechanism for when and how the Temporary ID changes and how the changes are coordinated
between layers is yet to be determined. The change mechanism itself is considered out of scope for the
J2735 standard.
PSC/PSID
The PSC/PSID is an example of information shared by application and its lower layers. It is considered out
of scope for the J2735 standard.
Message Priority