PRECONFIGURED SYNCML PROFILE CATEGORIES

• US 20070180127A1
• Filed: 12/28/2006
• Published: 08/02/2007
• Est. Priority Date: 12/28/2006
• Status: Abandoned Application

• Current Assignee: 2011 Intellectual Property Asset Trust (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Vuori, Janne
• Application Number:
  US11/617,253
• Publication Number:
  US 20070180127A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/30 Profiles
• CPC Class Codes: H04L 67/303 Terminal profiles

Abstract

A system and method for storing and retrieving preconfigured, hidden SyncML server profiles on a client is described. Conventionally, users of client devices need to manually configure the devices to allow for synchronization with new servers via SyncML. Preconfigured SyncML profiles allow a client to synchronize with a SyncML server without having to generate a new SyncML profile, thereby improving user experience. The preconfigured SyncML profiles may be hidden from a user or displayable to a user.

Claims

1. A method of initializing a connection between a client and a server using the SyncML protocol, comprising:

receiving at said client a synchronization request from said server;

determining that a specific profile for said server does not exist on said client;

retrieving a preconfigured profile on said client that allows said client to use said server for a SyncML data synchronization; and

performing SyncML data synchronization based on said profile.

2. The method according to claim 1, wherein said retrieving a preconfigured profile is performed by said client.

3. The method according to claim 1, wherein said performing SyncML data synchronization is after said server receives confirmation of said data synchronization from a user.

4. The method according to claim 1, further comprising:

authenticating a user to said client.

5. The method according to claim 1, wherein said server is a remote server.

6. The method according to claim 1, said generating further comprising adding information to said preconfigured profile to be used with said server.

7. The method according to claim 6, wherein said information includes a profile name generated from information from said server.

8. The method according to claim 6, wherein said information includes activated content types.

9. The method according to claim 7, wherein said information includes a default local database for each content type.

10. The method according to claim 6, wherein said information includes remote databases as defined by said server.

11. The method according to claim 6, wherein said information includes a host address, where the server is accessible through the host IP address or some other identifier.

12. The method according to claim 6, wherein said information includes a Server ID item.

13. The method according to claim 6, wherein said information includes a Bearer item.

14. The method according to claim 6, wherein said information includes an access point item.

15. The method according to claim 6, wherein said information includes authentication information including a username and password.

16. The method according to claim 6, wherein said information includes a port number for the server.

17. The method according to claim 1, wherein a user may view preconfigured profiles.

18. The method according to claim 1, wherein preconfigured profiles are hidden from a user.

19. A client comprising:

an input that receives a synchronization request from a SyncML server;

a processor that

     1) determines that a profile for said SyncML server does not exist on said client and

     2) creates a new profile for said SyncML server based on a preconfigured profile in said client; and

a storage that stores the new profile for the SyncML server.

20. The client according to claim 19, wherein said processor creates said profile based on information in the synchronization request.

21. The client according to claim 20, wherein said information includes a profile name generated from information from said server.

22. The client according to claim 20, wherein said information includes activated content types.

23. The client according to claim 20, wherein said information includes a host address, where the SyncML server is accessible through the host IP address address or some other identifier.

24. The client according to claim 19, wherein said information includes a server ID item.

25. The client according to claim 19, wherein said information includes a bearer item.

26. The client according to claim 19, wherein said information includes an access point item.

27. The client according to claim 19, wherein said information includes authentication information including a username and password.

28. The client according to claim 19, wherein a user may view preconfigured profiles.

29. The client according to claim 19, wherein preconfigured profiles are hidden from a user.

30. The client according to claim 19, where the preconfigured profile is provided in only a subset of all SyncML enabled devices for use by an enterprise partner.

31. The client according to claim 30, where the preconfigured profile from the enterprise partner is added to all or a subset of SyncML enabled devices.

32. A computer-readable medium having a program stored thereon, said program for initializing a connection between a client and a server using the SyncML protocol, said program comprising:

receiving at said client a synchronization request from said server;

determining that a specific profile for said server does not exist on said client;

retrieving a preconfigured profile on said client that allows said client to use said server for a SyncML data synchronization; and

performing SyncML data synchronization based on said profile.

33. The computer-readable medium according to claim 32, wherein preconfigured profiles are hidden from a user.

34. A client that initializes a connection between said client and a server using the SyncML protocol, comprising:

means for receiving at said client a synchronization request from said server;

means for determining that a specific profile for said server does not exist on said client;

means for retrieving a preconfigured profile on said client that allows said client to use said server for a SyncML data synchronization; and

means for performing SyncML data synchronization based on said profile.

35. The client according to claim 34, wherein said means for retrieving a preconfigured profile is performed by said client.