The following table describes the seven possible types of synchronisation as presented in OMA DS specifications:

mode
200

Sync Scenario
Two-way synchronisation (Rapid Sync)

Description

201

202

A normal synchronisation type in which the client and the server exchange information about modified data in these devices. The client sends the modifications first. Slow synchronisation (Slow A form of two-way Sync) synchronisation in which all records are compared with each other on a field-by-field basis. In practice, this means that the client sends all its data from a database to the server and the server does the synchronisation analysis (field-by-field) for this data and the data in the server. One-way synchronisation A synchronisation type in from which the client client only (Rapid Export) sends its modifications to the server but the

203

Refresh synchronisation from client only (Slow Export)

204

One-way synchronisation from server only (Rapid Import)

server does not send its modifications back to the client. A synchronisation type in which the client sends all its data from a database to the server (i.e., exports). The server is expected to replace all data in the target database with the data sent by the client. Server does the synchronisation analysis just like the Slow synchronisation scenario and determines which information is kept, based on the conflict resolution to apply. In practice, Refresh synchronisation from client is like a Slow synchronisation without modification on client. A synchronisation type in which the client gets all modifications from the server but the client does not send its modifications to the server.

205

Refresh synchronisation from server only (Slow Import)

206

Server Alerted synchronisation.

A synchronisation type in which the server sends all its data from a database to the client. The client is expected to replace all data in the target database with the data sent by the server. In practice, Refresh synchronisation from server is like a Slow synchronisation without modification on server. Replacement process may differ on different manufacturer solutions. A sync type in which the server alerts the client to perform synchronisation. See [SAN]

TAGS: - SupportLargObjs [DEVINF] - MaxObjSize [META] - MaxMsgSize [META] - Size [META] - MoreData [REPPRO] [DSREPU] STATUS CODES AND ALERTS:

STATUS CODES
213 222 223 424 416 411

DESCRIPTION
Chunked item accepted and buffered [REPPRO] NEXT MESSAGE [DSPROTO] [DSREPU] End of Data for chunked object not received [SYNCPRO] [DSREPU] Size Mismatch [REPPRO] Request entity too large [REPPRO] Size REQUIRED. The requested command MUST be accompanied by byte size or length information in the Meta element type [REPPRO]

The following table summarizes the different Status and Alert codes that the server can potentially use in its answer to a Resume request sent by the client, as well as the expected client behaviour: Status code
200

Alert code
Same Sync type code as in the previous interrupted session Sync type code different from the previous interrupted session one Slow Sync type code 201

Meaning
The resumption of the session is accepted by both client and server NOT POSSIBLE The server is not OMA DS 1.2 compliant in that case The server refuses to resume the session and forces a Slow Sync. The server refuses to resume the session and indicates the new Sync type it wants to use. In an enterprise environment, there are times when the server would prefer a Refresh

Client behaviour
The client MUST resume the interrupted session.

200

508

The client MUST end the resumed session in failure with a relevant error status code The client MUST perform a Slow Sync

508

Sync type code 205

The client MAY accept the override or end the resumed session in failure with a relevant error status code

from Server type of Sync (Alert 205) rather than a full Slow Sync (Alert 201). The use case for this is when the client device type is known to corrupt data (eg. May use vcal only and may introduce oddities in representation of exceptions to recurring events which MUST NOT be propagated to the server datastore.)

Alert Codes
Here are listed all Alert codes and values, which are used in the Data element when the Alert command is sent.
Alert Codes used for user alerts

Alert Code Value

100

Name
DISPLAY

Description
Show. The Data element type contains content information that should be processed and displayed through the user agent. Reserved for future SyncML usage.

101-150

Alert Codes used at the synchronization initialization

Alert Code Value

200 201 202

Name
TWO-WAY SLOW SYNC ONE-WAY FROM CLIENT REFRESH FROM CLIENT

Description
Specifies a client-initiated, twoway sync. Specifies a client-initiated, twoway slow-sync. Specifies the client-initiated, one-way only sync from the client to the server. Specifies the client-initiated, refresh operation for the oneway only sync from the client to the server. Specifies the client-initiated, one-way only sync from the server to the client. Specifies the client-initiated,

203

204

ONE-WAY FROM SERVER REFRESH FROM

205

SERVER

refresh operation of the oneway only sync from the server to the client.

Alert Codes used by the server when alerting the sync. Alert Code Name Value
206 207 TWO-WAY BY SERVER ONE-WAY FROM CLIENT BY SERVER

Description
Specifies a server-initiated, two-way sync. Specifies the serverinitiated, one-way only sync from the client to the server. Specifies the serverinitiated, refresh operation for the one-way only sync from the client to the server. Specifies the serverinitiated, one-way only sync from the server to the client. Specifies the serverinitiated, refresh operation of the oneway only sync from the server to the client. Reserved for future SyncML usage.

208

REFRESH FROM CLIENT BY SERVER

209

ONE-WAY FROM SERVER BY SERVER

210

REFRESH FROM SERVER BY SERVER

211-220

Special Alert Codes Alert Code Value

221 222 223 224 225 226

Name
RESULT ALERT NEXT MESSAGE NO END OF DATA SUSPEND RESUME DATA MANAGEMENT

Description
Specifies a request for sync results. Specifies a request for the next message in the package. End of Data for chunked object not received. Suspend Synchronization session Resume Synchronization session Specifies a request for data management without synchronization. Reserved for future SyncML usage.

227-250