11.01.2015 Views

[MS-ASCMD]: ActiveSync Command Reference Protocol Specification

[MS-ASCMD]: ActiveSync Command Reference Protocol Specification

[MS-ASCMD]: ActiveSync Command Reference Protocol Specification

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

1.4 Relationship to Other <strong>Protocol</strong>s<br />

The <strong>ActiveSync</strong> commands described in this document are sent and received over a Hypertext<br />

Transfer <strong>Protocol</strong> (HTTP) connection, as described in [RFC2616] in an HTTP POST method. The<br />

information contained in the HTTP POST header is described in [<strong>MS</strong>-ASHTTP]. The information<br />

contained in the HTTP message is sent and received in Wireless Application <strong>Protocol</strong> (WAP)<br />

Binary XML (WBXML) format, as described in [<strong>MS</strong>-ASWBXML], where the content of the WBXML<br />

adheres to the commands described in this document.<br />

Some of the <strong>ActiveSync</strong> commands described in this document are used to synchronize or retrieve<br />

more than one class of content. For example, the Ping command (section 2.2.2.11) can be used to<br />

monitor changes to the e-mail, note, contact, calendar, or task classes. The elements included in the<br />

Ping command change depending on which content class is being monitored. Because each content<br />

class is used by multiple commands, each content class is described by an individual protocol. The<br />

content class protocols are described in [<strong>MS</strong>-ASEMAIL], [<strong>MS</strong>-ASCNTC], [<strong>MS</strong>-ASDOC], [<strong>MS</strong>-ASCAL],<br />

[<strong>MS</strong>-ASNOTE], [<strong>MS</strong>-AS<strong>MS</strong>], and [<strong>MS</strong>-ASTASK].<br />

Another protocol that contains elements used by multiple commands is [<strong>MS</strong>-ASAIRS]. [<strong>MS</strong>-ASAIRS]<br />

describes the AirSyncBase namespace, which is used by multiple commands to specify the<br />

formatting preference of body content, truncation sizes, and other commonly used elements.<br />

This document describes all of the <strong>ActiveSync</strong> commands except for the Provision command, which<br />

is described in [<strong>MS</strong>-ASPROV] section 2.2.2.43.<br />

The Autodiscover command (section 2.2.2.1) is described in this document, but more information<br />

about Autodiscover publishing and lookup are available in [<strong>MS</strong>-OXDSCLI].<br />

All simple data types in this document conform to the data type definitions in [<strong>MS</strong>-ASDTYPE].<br />

For information about how to control the view of related e-mail messages or conversations, see<br />

[<strong>MS</strong>-ASCON].<br />

For information about how outbound Short Message Service (S<strong>MS</strong>) e-mail messages are sent from<br />

mobile devices, see [<strong>MS</strong>-AS<strong>MS</strong>].<br />

1.5 Prerequisites/Preconditions<br />

This protocol assumes that authentication has been performed by the underlying protocols.<br />

1.6 Applicability Statement<br />

This protocol is applicable in scenarios where a client has to synchronize its messages and files with<br />

a server.<br />

1.7 Versioning and Capability Negotiation<br />

None.<br />

1.8 Vendor-Extensible Fields<br />

None.<br />

1.9 Standards Assignments<br />

None.<br />

[<strong>MS</strong>-<strong>ASCMD</strong>] — v20110315<br />

<strong>ActiveSync</strong> <strong>Command</strong> <strong>Reference</strong> <strong>Protocol</strong> <strong>Specification</strong><br />

Copyright © 2011 Microsoft Corporation.<br />

Release: Tuesday, March 15, 2011<br />

19 / 369

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!