Preconfigured SyncML profile categories

• US 9,807,166 B2
• Filed: 01/04/2016
• Issued: 10/31/2017
• Est. Priority Date: 12/28/2006
• Status: Expired due to Fees

• Current Assignee: Conversant Wireless Licensing S.à.r.l. (f/k/a Core Wireless Licensing S.a.r.l.) (MOSAID Technologies Inc. (f/k/a Conversant Intellectual Property Management))
• Original Assignee: Conversant Wireless Licensing S.à.r.l. (f/k/a Core Wireless Licensing S.a.r.l.) (MOSAID Technologies Inc. (f/k/a Conversant Intellectual Property Management))
• Inventors: Vuori, Janne
• Primary Examiner(s): Bengzon, Greg C
• Application Number:
  US14/987,468
• Publication Number:
  US 20160197991A1
• Time in Patent Office: 666 Days
• Field of Search: None
• 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 comprising:

receiving, at a client, a synchronization request from a server in a synchronization session, the synchronization request including server information and based on a data synchronization protocol;

determining whether a specific profile for the server exists at the client;

responsive to determining that the specific profile exists at the client;

in the same synchronization session, performing data synchronization with the server according to the specific profile; and

responsive to determining that the specific profile does not exist at the client;

creating a new profile for the server on the client based on;

i) the server information included in the synchronization request, where the information includes a server ID item and a bearer item; and

ii) a default profile for new servers stored at the client; and

in the same synchronization session, performing data synchronization with the server according to the new profile.

2. The method of claim 1, further comprising:

authenticating a user to the client.

3. The method of claim 1, wherein the server is a remote server.

4. The method of claim 1, further comprising adding information to the new profile to be used with the server.

5. A client apparatus comprising:

at least one processor; and

at least one memory storing computer code, and the at least one memory and stored computer code being configured, with the at least one processor, to cause the apparatus to;

in a synchronization session, receive a server-originating synchronization request that includes server information and is based on a data synchronization protocol;

determine whether a specific profile for the server is stored on the client apparatus;

responsive to determining that the specific profile is stored at the client apparatus for the server;

in the same synchronization session, perform data synchronization with the server according to the specific profile; and

responsive to determining that the specific profile is not stored at the client apparatus for the server;

create a new profile for the server on the client apparatus based on;

i) the server information included in the synchronization request, where the information includes a server ID item and a bearer item; and

ii) default settings for new servers stored at the client apparatus; and

in the same synchronization session, perform data synchronization with the server according to the new profile.

6. The client apparatus of claim 5, wherein the at least one processor is configured to add information to the new profile based on the synchronization request.

7. The client apparatus of claim 6, wherein the information includes a profile name generated from information from the server.

8. The client apparatus of claim 6, wherein the information includes activated content types.

9. The client apparatus of claim 6, wherein the information includes an access point item.

10. The client apparatus of claim 6, wherein the information includes authentication information including a username and password.