Java telematics system preferences

• US 20030182360A1
• Filed: 03/22/2002
• Published: 09/25/2003
• Est. Priority Date: 03/22/2002
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Petrovsky, Sergey, Grigoriev, Nikolay Georgievich, Mocek, Darryl J.
• Application Number:
  US10/104,246
• Publication Number:
  US 20030182360A1
• Time in Patent Office: Days
• US Class Current: 709/203
• 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/306 User profiles
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system for storing preferences on a telematics client is provided. The system includes a telematics server configured to receive a request containing modification data for preferences. The modification data for the preferences is stored on a preference server of the telematics server. The telematics server includes a server side communications framework in communication with the preference server. The telematics control unit (TCU) has a preference manger for storing the preferences. The TCU includes a client side communications framework in communication with the preference manager, wherein the preference manager and the preference server are configured to synchronize over a network connection to allow the modification data to be communicated between the preference server and the preference manager.

Claims

1. A system for storing preferences on a telematics client, comprising:

a telematics server configured to receive a request containing modification data for preferences, the modification data for the preferences stored on a preference server of the telematics server, the telematics server including a server side communications framework in communication with the preference server;

a telematics control unit (TCU) having a preference manger for storing the preferences, the TCU including a client side communications framework in communication with the preference manager, wherein the preference manager and the preference server are configured to synchronize over a network connection to allow the modification data to be communicated between the preference server and the preference manager.

2. The system of claim 1, wherein the TCU includes a software stack having a hardware layer, an operating system layer, a Java virtual machine layer, an open services gateway initiative layer and a Java telematics client layer.

3. The system of claim 1, wherein the preferences are one of a system preference, an application preference and a user preference.

4. The system of claim 1, wherein synchronization between the client side and the server side is established through a connection object.

5. The system of claim 1, wherein a synchronization control enables communication between the client side communications framework, and the server side communications framework.

6. The system of claim 1, wherein the client side communications framework includes a data mutliplexer and a flow controller.

7. The system of claim 1, wherein the server side communications framework includes a data mutliplexer and a flow controller.

8. The system of claim 4, wherein the connection object of the client side has the ability to switch between channels available to the client side communication framework.

9. A telematics control unit (TCU), comprising

a software stack, the software stack including;

an operating system (OS) layer;

a Java virtual m a chine (JVM) layer;

a service gateway layer; and

a Java telematics client (JTC) layer, the JTC layer including;

a client side communication framework configured to communicate with a server side communication framework;

a user interface manager; and

a preference manager in communication with the client side communication framework, the preference manager configured to store at least one preference.

10. The TCU of claim 9, wherein the preference is one of a system preference, an application preference and a user preference.

11. The TCU of claim 9, wherein the JTC layer further includes:

carlets executed by the JTC layer, the carlets executing functionality specified by the preference.

12. The TCU of claim 9, wherein the client side communications framework further includes;

a message manager providing one way communication;

a stream manager providing two way communication, the stream manager configured to receive a request that a connection be established from a carlet; and

a data mutliplexer and a flow controller configured to receive a request from the stream manager for a connection object, wherein in response to the request, the data mutliplexer and the flow controller return a connection object to the carlet to establish a connection.

13. A method for storing preferences associated with a telematics system, comprising:

selecting a preference;

storing the selected preference in storage of a preference server;

synchronizing the preference server with a preference manager of a telematics control unit (TCU);

transmitting the preference to the preference manager; and

storing the preference in storage of the TCU.

14. The method of claim 13, wherein the method operation of synchronizing the preference server with a preference manager further includes:

requesting a connection object from a data multiplexer and flow controller; and

determining whether a desired channel is available.

15. The method of claim 13, wherein the preference is one of a system preference and a user preference.

16. The method of claim 13, wherein the system preference includes one of a vehicle identification number, a driver'"'"'s license number, a license plate number and a telephone number for connecting to a server.

17. The method of claim 13, wherein the user preference is an infotainment or convenience preference.

18. The method of claim 13, wherein the method operation of selecting a preference further includes;

accessing a distributed network in communication with the preference server; and

inputting the preference through a user interface.

19. The method of claim 18, wherein the user interface is a web page.

20. The method of claim 13, wherein the method operation of synchronizing the preference server with a preference manager of a TCU further includes:

initiating the synchronization upon power-up of the TCU.