IP Library Granted Patent US 7,822,828
Granted Patent B2
US 7,822,828 · App. 11/856,536 · Granted Oct 26, 2010

System for using non-standard transfer protocol from software received at in-vehicle communications gateway for exchanging data with client device

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,822,828
App. No.
11/856,536
Granted
Oct 26, 2010
Kind
B2
Abstract

Methods and apparatus are provided for transmitting data to a client device from a computer module in a vehicle. Data is transmitted from the computer module over an in-vehicle network to an in-vehicle communications gateway module. The data from the computer module is destined for the client device. A request for a software component is transmitted to the client device from a standard port of the in-vehicle communications gateway module. The software component comprises a non-standard transfer protocol module. The in-vehicle communications gateway module loads the non-standard transfer protocol module, and the data is exchanged between the in-vehicle communications gateway module and the client device according to the non-standard transfer protocol.

Claims (54)

1. A method for transmitting data to a client device from a computer module in a vehicle, the method comprising:

transmitting data from the computer module over an in-vehicle network to an in-vehicle communications gateway module, wherein the data from the computer module is destined for the client device;

transmitting, in accordance with a standard transfer protocol from a standard port of the in-vehicle communications gateway module in response to receiving the data from the computer module, a request for a software component to the client device, wherein the software component comprises a non-standard transfer protocol module that enables the in-vehicle communications gateway module to communicate the data to the client device;

sending, in response to the request, the software component from the client device to the standard port of in-vehicle communications gateway module;

loading the non-standard transfer protocol module at the in-vehicle communications gateway module so that the in-vehicle communications gateway module is capable of communicating with the client device according to the non-standard transfer protocol; and

after the in-vehicle communications gateway module has loaded the non-standard transfer protocol, exchanging the data between the in-vehicle communications gateway module and the client device according to the non-standard transfer protocol.

2. A method according to claim 1 , further comprising:

delaying transmission of the data to the client device at the in-vehicle communications gateway module until the in-vehicle communications gateway module has loaded the non-standard transfer protocol.

3. A method according to claim 1 , further comprising:

establishing a connection between the in-vehicle communications gateway module and the client device according to the non-standard transfer protocol.

4. A method according to claim 3 , further comprising:

closing the connection between the in-vehicle communications gateway module and the client device according to the non-standard transfer protocol after exchanging the data between the in-vehicle communications gateway module to the client device according to the non-standard transfer protocol.

5. A method according to claim 1 , further comprising:

closing the standard port of the in-vehicle communications gateway module and a standard port of the client device before exchanging the data between the in-vehicle communications gateway module to the client device according to the non-standard transfer protocol.

6. A method according to claim 5 , wherein the step of closing the standard port of the in-vehicle communications gateway module and a standard port of the client device, comprises:

closing the standard port at the in-vehicle communications gateway module and the client device before exchanging the data between the in-vehicle communications gateway module to the client device according to the non-standard transfer protocol so that standard internet protocols are not used for the subsequent exchange of information between the server application hosted at the in-vehicle communications gateway module and the browser application hosted at the remote client device.

7. A method according to claim 1 , wherein the software component is used to establish the non-standard transfer protocol module for communications between a server application hosted at the in-vehicle communications gateway module and a browser application hosted at the remote client device, and wherein the software component comprises:

an executable program which includes the non-standard transfer protocol module which allows the browser application hosted at the remote client device to communicate with the server application hosted at the in-vehicle communications gateway module according to the non-standard transfer protocol module.

8. A method according to claim 7 , wherein the browser application executes the executable program to enable communication between the browser application hosted at the remote client device and the server application hosted at the in-vehicle communications gateway module in accordance with the non-standard transfer protocol module.

9. A method according to claim 7 , wherein the software component comprises at least one of:

a compiled program;

a Java applet; and

an active X control.

10. A vehicle, comprising:

a computer module designed to generate data;

an in-vehicle network; and

an in-vehicle communications gateway module designed to:

receive the data from the computer module over the in-vehicle network, wherein the data from the computer module is destined for a remote client device, and

transmit, in accordance with a standard transfer protocol from a standard port of the in-vehicle communications gateway module in response to receiving the data from the computer module, a request for a software component to the client device, wherein the software component comprises a non-standard transfer protocol module that enables the in-vehicle communications gateway module to communicate the data to the client device;

receive the software component from the client device;

load the non-standard transfer protocol module at the in-vehicle communications gateway module so that the in-vehicle communications gateway module is capable of communicating with the client device according to the non-standard transfer protocol; and

exchange the data with the client device according to the non-standard transfer protocol after the in-vehicle communications gateway module has loaded the non-standard transfer protocol.

11. A vehicle according to claim 10 , wherein the in-vehicle communications gateway module is further designed to: delay transmission of the data to the client device until the in-vehicle communications gateway module has loaded the non-standard transfer protocol.

12. A vehicle according to claim 10 , wherein the in-vehicle communications gateway module is further designed to: establish a connection with the client device according to the non-standard transfer protocol.

13. A vehicle according to claim 12 , wherein the in-vehicle communications gateway module is further designed to: close the connection between the in-vehicle communications gateway module and the client device according to the non-standard transfer protocol after exchanging the data with the client device according to the non-standard transfer protocol.

14. A vehicle according to claim 10 , wherein the in-vehicle communications gateway module is further designed to: close the standard port before exchanging the data with the client device according to the non-standard transfer protocol.

15. A vehicle according to claim 14 , wherein the in-vehicle communications gateway module is further designed to: close the standard port before exchanging the data with the client device according to the non-standard transfer protocol so that standard internet protocols are not used for the subsequent exchange of the data between a server application hosted at the in-vehicle communications gateway module and a browser application hosted at the remote client device.

16. A vehicle according to claim 10 , wherein the software component is used to establish the non-standard transfer protocol module for communications between a server application hosted at the in-vehicle communications gateway module and a browser application hosted at the remote client device, and wherein the software component comprises:

an executable program which includes the non-standard transfer protocol module which allows the server application hosted at the in-vehicle communications gateway module to communicate with the browser application hosted at the remote client device according to the non-standard transfer protocol.

17. A vehicle according to claim 16 , wherein the browser application executes the executable program to enable communication between the browser application hosted at the remote client device and the server application hosted at the in-vehicle communications gateway module in accordance with the non-standard transfer protocol.

18. A vehicle according to claim 16 , wherein the software component comprises at least one of:

a compiled program;

a Java applet; and

an active X control.

19. An in-vehicle communications gateway module according to claim 10 , wherein the software component is used to establish the non-standard transfer protocol module for communications between a server application hosted at the in-vehicle communications gateway module and a browser application hosted at the remote client device, and wherein the software component comprises:

an executable program which includes the non-standard transfer protocol module which allows the server application hosted at the in-vehicle communications gateway module to communicate with the browser application hosted at the remote client device according to the non-standard transfer protocol, wherein the browser application executes the executable program to enable communication between the browser application hosted at the remote client device and the server application hosted at the in-vehicle communications gateway module in accordance with the non-standard transfer protocol.

20. An in-vehicle communications gateway module designed to receive data from a computer module over an in-vehicle network, wherein the data from the computer module is destined for a remote client device, comprising:

a server designed to:

transmit, in accordance with a standard transfer protocol from a standard port of the in-vehicle communications gateway module, a request for a software component to the client device in response to receiving the data from the computer module, wherein the software component comprises a non-standard transfer protocol module that enables the in-vehicle communications gateway module to communicate the data to the client device;

receive the software component from the client device;

close the standard port before exchanging the data with the client device so that standard transfer protocols are not used for the subsequent exchange of the data between the server and a browser application hosted at the client device;

load the non-standard transfer protocol module so that the in-vehicle communications gateway module is capable of communicating with the client device according to the non-standard transfer protocol;

establish a connection with the client device according to the non-standard transfer protocol;

exchange the data with the client device according to the non-standard transfer protocol after the in-vehicle communications gateway module has loaded the non-standard transfer protocol.

Assignments (12)
RELEASE OF SECURITY INTEREST Recorded Nov 7, 2014
From: WILMINGTON TRUST COMPANY
To: GM GLOBAL TECHNOLOGY OPERATIONS LLC
Reel/Frame 034185/0587 →
CHANGE OF NAME Recorded Feb 10, 2011
From: GM GLOBAL TECHNOLOGY OPERATIONS, INC.
To: GM GLOBAL TECHNOLOGY OPERATIONS LLC
Reel/Frame 025781/0035 →
SECURITY AGREEMENT Recorded Nov 8, 2010
From: GM GLOBAL TECHNOLOGY OPERATIONS, INC.
To: WILMINGTON TRUST COMPANY
Reel/Frame 025324/0057 →
RELEASE OF SECURITY INTEREST Recorded Nov 5, 2010
From: UAW RETIREE MEDICAL BENEFITS TRUST
To: GM GLOBAL TECHNOLOGY OPERATIONS, INC.
Reel/Frame 025314/0946 →
RELEASE OF SECURITY INTEREST Recorded Nov 4, 2010
From: UNITED STATES DEPARTMENT OF THE TREASURY
To: GM GLOBAL TECHNOLOGY OPERATIONS, INC.
Reel/Frame 025245/0780 →
SECURITY AGREEMENT Recorded Aug 28, 2009
From: GM GLOBAL TECHNOLOGY OPERATIONS, INC.
To: UAW RETIREE MEDICAL BENEFITS TRUST
Reel/Frame 023162/0187 →
SECURITY AGREEMENT Recorded Aug 27, 2009
From: GM GLOBAL TECHNOLOGY OPERATIONS, INC.
To: UNITED STATES DEPARTMENT OF THE TREASURY
Reel/Frame 023156/0215 →
RELEASE OF SECURITY INTEREST Recorded Aug 21, 2009
From: CITICORP USA, INC. AS AGENT FOR BANK PRIORITY SECURED PARTIES; CITICORP USA, INC. AS AGENT FOR HEDGE PRIORITY SECURED PARTIES
To: GM GLOBAL TECHNOLOGY OPERATIONS, INC.
Reel/Frame 023155/0880 →
RELEASE OF SECURITY INTEREST Recorded Aug 20, 2009
From: UNITED STATES DEPARTMENT OF THE TREASURY
To: GM GLOBAL TECHNOLOGY OPERATIONS, INC.
Reel/Frame 023124/0670 →
SECURITY AGREEMENT Recorded Apr 16, 2009
From: GM GLOBAL TECHNOLOGY OPERATIONS, INC.
To: CITICORP USA, INC. AS AGENT FOR BANK PRIORITY SECURED PARTIES; CITICORP USA, INC. AS AGENT FOR HEDGE PRIORITY SECURED PARTIES
Reel/Frame 022554/0479 →
SECURITY AGREEMENT Recorded Feb 3, 2009
From: GM GLOBAL TECHNOLOGY OPERATIONS, INC.
To: UNITED STATES DEPARTMENT OF THE TREASURY
Reel/Frame 022195/0334 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 17, 2007
From: ALRABADY, ANSAF I.; CATSBURG, THOMAS M. P.
To: GM GLOBAL TECHNOLOGY OPERATIONS, INC.
Reel/Frame 019836/0807 →