Message
Message
One of
Option 1
Properties
| Name | Type | Required | Description |
|---|---|---|---|
isPrivate | boolean | Yes | Defines whether the message is private or public. Private messages are published under the Vendor ID defined in the configuration and only visible to devices of selected vendors. Public messages are published under the Public vendor and are visible to all the users. |
roadUserType | array | Yes | Type of the Road User. |
triggerConditions | array | Yes | Trigger conditions that define on which road user action the message will be sent. If multiple Trigger Conditions are defined any of them will trigger the message. |
limits | array | No | List of limitations. These limitations can be used for making the trigger condition more precise by defining speed and motion direction requirements to be met before the messages are sent out. |
distributionType | array | No | Type of the distribution. |
distributionSchedule | object | No | The distribution schedule parameters for broadcast messages. |
generic | object | Yes | Custom message which is defined by the user and can support "any" message type or format. Note: ETX prefers the j2735 or the j2735_gr encoding and only vendor specific message types are allowed to be published in different message formats. |
Option 2
Properties
| Name | Type | Required | Description |
|---|---|---|---|
isPrivate | boolean | Yes | Defines whether the message is private or public. Private messages are published under the Vendor ID defined in the configuration and only visible to devices of selected vendors. Public messages are published under the Public vendor and are visible to all the users. |
roadUserType | array | Yes | Type of the Road User. |
triggerConditions | array | Yes | Trigger conditions that define on which road user action the message will be sent. If multiple Trigger Conditions are defined any of them will trigger the message. |
limits | array | No | List of limitations. These limitations can be used for making the trigger condition more precise by defining speed and motion direction requirements to be met before the messages are sent out. |
distributionType | array | No | Type of the distribution. |
distributionSchedule | object | No | The distribution schedule parameters for broadcast messages. |
saeAlert | object | Yes | Road Side Alert (RSA) message payload as defined in SAE J2735. |
Option 3
Properties
| Name | Type | Required | Description |
|---|---|---|---|
isPrivate | boolean | Yes | Defines whether the message is private or public. Private messages are published under the Vendor ID defined in the configuration and only visible to devices of selected vendors. Public messages are published under the Public vendor and are visible to all the users. |
roadUserType | array | Yes | Type of the Road User. |
triggerConditions | array | Yes | Trigger conditions that define on which road user action the message will be sent. If multiple Trigger Conditions are defined any of them will trigger the message. |
limits | array | No | List of limitations. These limitations can be used for making the trigger condition more precise by defining speed and motion direction requirements to be met before the messages are sent out. |
distributionType | array | No | Type of the distribution. |
distributionSchedule | object | No | The distribution schedule parameters for broadcast messages. |
saeInfo | object | Yes | Traveler Information Message (TIM) payload as defined in SAE J2735. |
Option 4
Properties
| Name | Type | Required | Description |
|---|---|---|---|
isPrivate | boolean | Yes | Defines whether the message is private or public. Private messages are published under the Vendor ID defined in the configuration and only visible to devices of selected vendors. Public messages are published under the Public vendor and are visible to all the users. |
roadUserType | array | Yes | Type of the Road User. |
triggerConditions | array | Yes | Trigger conditions that define on which road user action the message will be sent. If multiple Trigger Conditions are defined any of them will trigger the message. |
limits | array | No | List of limitations. These limitations can be used for making the trigger condition more precise by defining speed and motion direction requirements to be met before the messages are sent out. |
distributionType | array | No | Type of the distribution. |
distributionSchedule | object | No | The distribution schedule parameters for broadcast messages. |
etsiAlert | object | Yes | DENM (Decentralized Environmental Notification Message) payload as defined in ETSI. |