METHOD AND APPARATUS FOR IMPLEMENTING A MOBILE SERVER

• US 20090077240A1
• Filed: 09/17/2007
• Published: 03/19/2009
• Est. Priority Date: 09/17/2007
• Status: Active Grant

• Current Assignee: GM Global Technology Operations LLC (General Motors Company)
• Original Assignee: GM Global Technology Operations Incorporated (Motors Liquidation Co. GUC Trust)
• Inventors: CATSBURG, THOMAS M. P., ALRABADY, ANSAF I.
• Granted Patent: US 7,822,828 B2
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

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

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, from a standard port of the in-vehicle communications gateway module, a request for a software component to the client device, wherein the software component comprises a non-standard transfer protocol module;

loading the non-standard transfer protocol module at the in-vehicle communications gateway module; and

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:

sending, in response to the request, the software component from the client device to the in-vehicle communications gateway module.

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 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.

5. A method according to claim 4, 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.

6. 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.

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, from a standard port of the in-vehicle communications gateway module, a request for a software component to the client device, wherein the software component comprises a non-standard transfer protocol module;

load the non-standard transfer protocol module at the in-vehicle communications gateway module; and

exchange the data with the client device according to the non-standard transfer protocol

11. A vehicle according to claim 10, wherein the in-vehicle communications gateway module is further designed to:

receive the software component from the client device.

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 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.

14. A vehicle according to claim 13, 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.

15. 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.

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.

20. 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.

19. 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, from a standard port of the in-vehicle communications gateway module, a request for a software component to the client device, wherein the software component comprises a non-standard transfer protocol module;

receive the software component from the client device;

close the standard port before exchanging the data with the client device so that standard internet 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;

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.