VEHICLE TELEMATICS DATA EXCHANGE

• US 20150288636A1
• Filed: 04/02/2014
• Published: 10/08/2015
• Est. Priority Date: 04/02/2014
• Status: Active Grant

• Current Assignee: Ford Global Technologies, LLC (Ford Motor Company)
• Original Assignee: Ford Global Technologies, LLC (Ford Motor Company)
• Inventors: YALAVARTY, Praveen, ELLIS, John Thomas
• Granted Patent: US 9,325,650 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads

Abstract

A system may include a message publisher and a message recipient. The message publisher may be configured to identify a message to be published to a topic of a topic tree maintained by a message broker, the topic being associated with a type of the message identified to be published and an intended recipient of the message; pack data elements into the message according to a name/value pair message schema of the system; and publish the message via the message broker to the topic.

Claims

1. A system comprising:

a message publisher configured to

identify a message to be published to a topic of a topic tree maintained by a message broker, the topic being associated with a type of the message identified to be published and an intended recipient of the message;

pack data elements into the message according to a name/value pair message schema of the system; and

publish the message via the message broker to the topic.

2. The system of claim 1, wherein the message publisher is a service delivery network, and the intended recipient of the message is at least one vehicle.

3. The system of claim 2, wherein the intended recipient of the message includes a plurality of vehicles subscribed to the topic of the topic tree, the topic being associated with vehicles at least one of a particular firmware version and a particular firmware configuration version.

4. The system of claim 2, wherein the intended recipient of the message is a single vehicle, and the topic is associated with a unique identifier of the single vehicle targeted to receive the message.

5. The system of claim 1, wherein the message publisher is a vehicle, and the intended recipient of the message is a service delivery network.

6. The system of claim 5, wherein the message is a response to a command published to the vehicle by the service delivery network, and the message includes a correlation identifier specified by the command to allow the service delivery network to link the response to the command.

7. The system of claim 5, wherein the message is an alert published in response to a condition identified by the vehicle.

8. The system of claim 5, wherein the message is a connection alert published by the vehicle to inform the message broker that the vehicle is still connected to the message broker.

9. The system of claim 1, wherein the name/value pair message schema defines at least one message structure defining a plurality of common data elements to be included in a plurality of types of message, the at least one message structure including at least one of:

a set of common data elements to be included in messages from a vehicle to a service delivery network, and a set of common data elements to be included in messages from the service delivery network to the vehicle.

10. The system of claim 1, wherein each of the data elements is associated with a unique identifier, and to pack the data elements into the message includes to pack the unique identifier of each data element into the message accompanying a value for the respective data element.

11. A system comprising:

a message recipient configured to

identify a message published by a message publisher to a topic of a topic tree maintained by a message broker, the topic being associated with a type of the message identified to be published and subscribed to by the message recipient;

unpack data elements from the message according to a name/value pair message schema of the system; and

process the message according to the type of the message.

12. The system of claim 11, wherein the message publisher is a service delivery network, and the message recipient is a vehicle.

13. The system of claim 12, wherein the message recipient is one of a plurality of vehicles subscribed to the topic of the topic tree, the topic being associated with vehicles at least one of a particular firmware version and a particular firmware configuration version.

14. The system of claim 12, wherein the message recipient is a single vehicle, and the topic is associated with a unique identifier of the single vehicle targeted to receive the message.

15. The system of claim 11, wherein the message publisher is a vehicle, and the message recipient is a service delivery network.

16. The system of claim 15, wherein the message is a response to a command published to the vehicle by the service delivery network, and the message includes a correlation identifier specified by the command to allow the service delivery network to link the response to the command.

17. The system of claim 15, wherein the message is an alert published in response to a condition identified by the vehicle.

18. The system of claim 15, wherein the message is a connection alert published by the vehicle to inform the message broker that the vehicle is still connected to the message broker.

19. The system of claim 11, wherein the name/value pair message schema defines at least one message structure defining a plurality of common data elements to be included in a plurality of types of message, the at least one message structure including at least one of:

a set of common data elements to be included in messages from a vehicle to a service delivery network, and a set of common data elements to be included in messages from the service delivery network to the vehicle.

20. The system of claim 11, wherein each of the data elements is associated with a unique identifier, and to pack the data elements into the message includes to pack the unique identifier of each data element into the message accompanying a value for the respective data element.