Lightweight protocol for use in a TCP/IP communications network

• US 7,881,251 B2
• Filed: 08/18/2006
• Issued: 02/01/2011
• Est. Priority Date: 08/18/2006
• Status: Active Grant

• Current Assignee: General Motors LLC (General Motors Company)
• Original Assignee: General Motors LLC (General Motors Company)
• Inventors: Hovey, Matthew N.
• Primary Examiner(s): Jagannathan; Melanie
• Application Number:
  US11/465,614
• Publication Number:
  US 20080043684A1
• Time in Patent Office: 1,628 Days
• Field of Search: 370/338
• US Class Current: 370/328
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
• CPC Class Codes: H04L 69/163 In-band adaptation of TCP data exchange; In-band control procedures
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence

Abstract

A lightweight communications protocol optimized for wireless transfer of data across a TCP/IP network that connects a vehicle communications device to a remote entity, such as a call center. The lightweight protocol utilizes messages that include header, trailer, and payload elements, where the payload element is optimized for the transmission of SOAP content as a default content type, but is capable of transmitting other types of non-SOAP MIME content as well. The lightweight protocol also reduces session overhead and thus data traffic by maintaining sessions in an open status so that numerous messages can be transferred within a single session, without having to shut the session down and rebuild it each time.

Claims

1. A communications system for providing wireless communication between a vehicle and one or more remote entities, comprising:

a vehicle communications device located on the vehicle;

a remote entity located some distance from the vehicle; and

a wireless carrier system that communicates with both said vehicle communications device and said remote entity so that information can be wirelessly exchanged therebetween;

wherein said vehicle communications device, said remote entity, and said wireless carrier system communicate over a network configured with a TCP/IP protocol stack having a data link layer, a network layer, a transport layer, and an application layer, said application layer includes a first sub-layer utilizing a SOAP protocol, a second sub-layer utilizing a MIME protocol, and a third sub-layer utilizing a non-HTTP lightweight protocol that maintains an established session in an open status while a plurality of request and response messages are transmitted between said vehicle communications device and said remote entity without closing said established session down.

2. The communications system of claim 1, wherein said lightweight protocol provides for the transmission of arbitrary MIME content, but recognizes SOAP as a default protocol for said first sub-layer.

3. The communications system of claim 1, wherein said lightweight protocol is built on the semantics of synchronous request-reply messaging.

4. The communications system of claim 1, wherein said lightweight protocol provides for the establishment of a session by utilizing a TCP 3-way handshake.

5. The communications system of claim 1, wherein said lightweight protocol provides for the closure of said session if either of the following events occurs:

an initiator peer closes said session, or an idle session timeout occurs.

6. The communications system of claim 5, wherein an elapsed time associated with said idle session timeout is reset by a listener peer each time a request message is received from an initiator peer.

7. The communications system of claim 1, wherein said lightweight protocol provides for the closure of a session by utilizing a TCP 4-way handshake.

8. The communications system of claim 1, wherein said system is used to transmit at least one of the following types of information between said vehicle communications device and said remote entity:

navigation information, infotainment information, and diagnostic information.

9. A method for communicating with a vehicle communications device over a wireless network, comprising the steps of:

(a) establishing a session between an initiator peer and a listener peer, wherein said session is established over a wireless network configured with a TCP/IP protocol stack having an application layer that includes a first sub-layer utilizing a SOAP protocol, a second sub-layer utilizing a MIME protocol, and a third sub-layer utilizing a non-HTTP lightweight protocol, wherein said non-HTTP lightweight protocol reduces overhead by establishing SOAP as the default protocol for said first sub-layer and establishing MIME as the default protocol for said second sub-layer so that certain control data that would otherwise be required to establish the SOAP and MIME protocols can be omitted from one or more entity-headers;

(b) sending a request message from said initiator peer to said listener peer;

(c) sending a response message from said listener peer to said initiator peer; and

(d) closing said session.

10. The method of claim 9, wherein step (a) further includes utilizing a TCP 3-way handshake to establish said session.

11. The method of claim 9, wherein said method further includes maintaining said session in an open status so that a plurality of said request and response messages can be transmitted without closing said session down.

12. The method of claim 11, wherein step (d) further includes closing said session down if either of the following events occurs:

said initiator peer closes said session, or an idle session timeout occurs.

13. The method of claim 12, wherein step (d) further includes resetting an elapsed time associated with said idle session timeout each time said listener peer receives said request message from said initiator peer.

14. The method of claim 9, wherein step (d) further includes utilizing a TCP 4-way handshake to close said session.

15. The method of claim 9, wherein said method is used to transmit at least one of the following types of information over the wireless network:

navigation information, infotainment information, and diagnostic information.

16. A communications system for providing wireless communication between a vehicle and one or more remote entities, comprising:

a vehicle communications device located on the vehicle;

a remote entity located some distance from the vehicle; and

a wireless carrier system that communicates with both said vehicle communications device and said remote entity so that information can be wirelessly exchanged therebetween;

said vehicle communications device, said remote entity, and said wireless carrier system communicate over a network configured with a TCP/IP protocol stack having a data link layer utilizing a CDMA protocol, a network layer utilizing an IP protocol, a transport layer utilizing a TCP protocol, and an application layer, said application layer includes a first sub-layer utilizing a SOAP protocol, a second sub-layer utilizing a MIME protocol, and a third sub-layer utilizing a lightweight protocol,

wherein said lightweight protocol provides for messages, comprising;

a header element containing a size indicator;

a trailer element indicating the end of the message; and

a payload element located between said header and trailer elements, said payload element is optimized for SOAP content as a default content type so that certain control data that would otherwise be required for SOAP content can be omitted from one or more entity-headers, but can provide for other arbitrary, non-SOAP MIME content by including such control data in one or more entity-headers.

17. The communications system of claim 16, wherein said lightweight protocol provides for extension points that allow directives to be added to or deleted from a protocol specification.