Preconfigured syncML profile categories

• US 10,419,535 B2
• Filed: 10/02/2017
• Issued: 09/17/2019
• Est. Priority Date: 12/28/2006
• Status: Active Grant

• 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:
  US15/722,541
• Publication Number:
  US 20180091592A1
• Time in Patent Office: 715 Days
• 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 between the client and the server, the synchronization request including server information and based on a data synchronization protocol;

determining that a specific profile for the server does not exist at the client;

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; and

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

in the same synchronization session, performing a slow data synchronization between the client and the server according to the new profile for limited content types as specified in the default profile;

wherein the server information in the synchronization request comprises a server ID and an IP address of the server retrieved from a packet header of the synchronization request.

6. The method of claim 1, further comprising:

in a next synchronization session, synchronizing at least one content type, other than the limited content types, that was not synchronized in the slow data synchronization.

7. The method of claim 6, wherein the next synchronization session is initiated by the client.

8. The method of claim 6, wherein the next synchronization session is initiated by the server.

2. 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 client 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 that a specific profile for the server is not stored on the client apparatus;

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; and

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

in the same synchronization session, perform a slow data synchronization between the client the server according to the new profile for limited content types as specified in the default profile; and

wherein the server information in the synchronization request comprises a server ID and an IP address of the server retrieved from a packet header of the synchronization request.

3. The client apparatus of claim 2, wherein the computer code is configured, with the at least one processor, to cause the client apparatus to also:

in a next synchronization session, synchronize at least one content type, other than the limited content types, that was not synchronized in the slow data synchronization.

4. The client apparatus of claim 3, wherein the computer code is configured, with the at least one processor, to cause the client apparatus to also:

initiate the next synchronization session.

5. The client apparatus of claim 3, wherein the next synchronization session is server-initiated.