Universal personal information connector architecture

• US 20040193731A1
• Filed: 03/31/2003
• Published: 09/30/2004
• Est. Priority Date: 03/31/2003
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Mitchell, Larry
• Application Number:
  US10/403,617
• Publication Number:
  US 20040193731A1
• Time in Patent Office: Days
• US Class Current: 709/246
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• 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 and method for handling personal information management (PIM) data interactions with varied client devices. The system supports many devices, PIM data types, PIM communication protocols, and PIM data store configurations. The system may run on a telematics control unit and includes a data manager providing a client-side interface to PIM data that controls local presentation, manipulation, and storage of the client PIM data. A PIM connector manager discovers client devices in the system, determines what type of PIM interface to provide for the client devices, retrieves such PIM interfaces from a PIM interface registry, registers the PIM interfaces for use by the appropriate client devices, and enables the registered PIM interfaces for use by the client devices. The PIM connector provides data and protocol conversion between the client device and the data manager and/or data store storing the client device'"'"'s PIM data.

Claims

1. A computer-based system for allowing client devices to interface with personal information management (PIM) data from multiple PIM data stores, comprising:

a communication mechanism adapted for communicating with client devices;

a connector manager discovering a client device connected to the communication mechanism that is enabled for using a type of PIM data; and

a set of PIM connectors registered by the connector manager for a set of client devices including an implementation of a PIM connector interface selected and retrieved by the connector manager based on the type of PIM data determined for the discovered client device, wherein the PIM connectors provide data and protocol conversion between the set of client devices and data stores storing PIM data for the set of client devices.

2. The system of claim 1, wherein the connector manager further discovers loss of communication with the discovered client device at the communication port and in response, removes the implementation of the PIM connector interface selected for the discovered client device from the set of registered PIM connectors.

3. The system of claim 1, wherein the connector manager further discovers an additional client device linked to the communication mechanism that is enabled for using an additional type of PIM data differing from the type of PIM data used by the discovered client device and in response, selects and retrieves based on the additional type of PIM data an implementation of an additional PIM connector interface, the implementation of the additional PIM connector interface being added to the set of registered PIM connectors for later use by the additional client device.

4. The system of claim 1, further including a local data store including a local cache for the discovered client device storing a set of PIM data retrieved from the PIM data store for the discovered client device by the registered PIM connector corresponding to the implementation of the PIM connector interface corresponding to the discovered client device.

5. The system of claim 1, further including a connector implementation comprising the implementation of the PIM connector interface corresponding to the discovered client device that has been enabled by the connector manager for allowing the discovered client device to access the PIM data stored for the discovered client device.

6. The system of claim 1, further including a telematics control unit hosting the communication mechanism, the connector manager, and the set of registered PIM connectors.

7. The system of claim 1, further including an interface registry linked by a communication network with the connector manager, the interface registry storing a set of PIM interface connectors configured to support a set of PIM-enabled client device and PIM data store configurations.

8. The system of claim 7, wherein the connector manager creates the set of registered PIM connectors by discovering a set of client devices linked to the communication mechanism, retrieving one of the PIM interface connectors in the interface registry for each one of the set of client devices based on PIM enablement of the client devices, and registering the retrieved PIM interface connectors for use by the corresponding client devices.

9. A computer-based method for providing access connections for client devices to personal information management (PIM) data, comprising:

discovering a client device enabled for PIM data;

determining an interface to a PIM data source for the discovered client device;

registering a PIM connector for the discovered client device, wherein the PIM connector is an implementation of the determined interface; and

enabling the registered PIM connector for use by the discovered client device, whereby the enabled PIM connector controls access to PIM data on the PIM data source by the discovered client device.

10. The method of claim 9, further including:

discovering an additional client device enabled for PIM data,

determining an interface to an additional PIM data source for the additional client device;

registering a PIM connector for the additional client device, wherein the PIM connector for the additional client device is an implementation of the determined interface for the additional client device; and

enabling the PIM connector registered for the additional client device.

11. The method of claim 10, wherein the PIM data source and the additional PIM data source operate utilizing differing protocols to manage stored PIM data.

12. The method of claim 10, wherein the PIM connector for the discovered client device differs from the PIM connector for the additional client device.

13. The method of claim 9, further including creating a cache in a local data store corresponding to the discovered client device and the PIM data source storing a set of the PIM data accessed by the enabled PIM connector.

14. The method of claim 9, further including terminating the enabled PIM connector including determining loss of discovery of the discovered client device.

15. The method of claim 9, further including operating the enabled PIM connector to perform PIM data, PIM data function, and PIM data protocol conversion to allow the discovered client device to access the PIM data.

16. A method for linking client devices with personal information management (PIM) data sources, comprising:

establishing a communication link with a client device;

discovering the client device including determining whether the client device is enabled for a type of PIM data and determining PIM data sources storing PIM data for the client device;

for each of the PIM data sources, registering a connector configured to enable the client device to access the client device PIM data in one of the PIM data sources; and

enabling one of the registered connectors for use by the client device as an interface with a corresponding one of the PIM data sources.

17. The method of claim 16, further including:

establishing a communication link with an additional client device;

discovering the additional client device including determining a type of PIM data for which the additional client device is enabled and determining PIM data sources storing PIM data for the additional client device; and

for each of the PIM data sources for the additional client device, registering a connector configured to enable the additional client device to access the client device PIM data.

18. The method of claim 17, wherein the type of PIM data determined for the client device differs from the type of PIM data determined for the additional client device.

19. The method of claim 16, further including discovering loss of the client device and in response, terminating the enabled one of the registered connectors.

20. The method of claim 16, further including creating a local store including a cache for the client device for each of the PIM data sources storing PIM data retrieved by the connectors registered for use by the client device from the PIM data sources.