LIGHTWEIGHT PROTOCOL FOR USE IN A TCP/IP COMMUNICATIONS NETWORK
First Claim
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 lightweight protocol.
14 Assignments
0 Petitions
Accused Products
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.
-
Citations
18 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 lightweight protocol. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 11, 12, 13, 14, 15, 16)
-
-
10. 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 lightweight protocol; (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.
-
-
17. 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, but can provide for other arbitrary, non-SOAP MIME content by including entity-headers. - View Dependent Claims (18)
-
Specification