[MS-OMS]:
Office Mobile Service Protocol
Intellectual Property Rights Notice for Open Specifications Documentation
Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions.
Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation.
No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting .
Trademarks. The names of companies and products contained in this documentation might be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit
Fictitious Names. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events that are depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.
Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than as specifically described above, whether by implication, estoppel, or otherwise.
Tools. The Open Specifications documentation does not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments, you are free to take advantage of them. Certain Open Specifications documents are intended for use in conjunction with publicly available standards specifications and network programming art and, as such, assume that the reader either is familiar with the aforementioned material or has immediate access to it.
Revision Summary
Date / Revision History / Revision Class / Comments7/13/2009 / 0.1 / Major / Initial Availability
8/28/2009 / 0.2 / Editorial / Revised and edited the technical content
11/6/2009 / 0.3 / Editorial / Revised and edited the technical content
2/19/2010 / 1.0 / Editorial / Revised and edited the technical content
3/31/2010 / 1.01 / Editorial / Revised and edited the technical content
4/30/2010 / 1.02 / Editorial / Revised and edited the technical content
6/7/2010 / 1.03 / Editorial / Revised and edited the technical content
6/29/2010 / 1.04 / Editorial / Changed language and formatting in the technical content.
7/23/2010 / 1.05 / Major / Significantly changed the technical content.
9/27/2010 / 1.05 / None / No changes to the meaning, language, or formatting of the technical content.
11/15/2010 / 1.05 / None / No changes to the meaning, language, or formatting of the technical content.
12/17/2010 / 1.05 / None / No changes to the meaning, language, or formatting of the technical content.
3/18/2011 / 1.05 / None / No changes to the meaning, language, or formatting of the technical content.
6/10/2011 / 1.05 / None / No changes to the meaning, language, or formatting of the technical content.
1/20/2012 / 2.0 / Major / Significantly changed the technical content.
4/11/2012 / 2.0 / None / No changes to the meaning, language, or formatting of the technical content.
7/16/2012 / 2.0 / None / No changes to the meaning, language, or formatting of the technical content.
9/12/2012 / 2.0 / None / No changes to the meaning, language, or formatting of the technical content.
10/8/2012 / 2.1 / Minor / Clarified the meaning of the technical content.
2/11/2013 / 2.1 / None / No changes to the meaning, language, or formatting of the technical content.
7/30/2013 / 2.2 / Minor / Clarified the meaning of the technical content.
11/18/2013 / 2.2 / None / No changes to the meaning, language, or formatting of the technical content.
2/10/2014 / 2.2 / None / No changes to the meaning, language, or formatting of the technical content.
4/30/2014 / 2.2 / None / No changes to the meaning, language, or formatting of the technical content.
7/31/2014 / 2.2 / None / No changes to the meaning, language, or formatting of the technical content.
10/30/2014 / 2.2 / None / No changes to the meaning, language, or formatting of the technical content.
3/16/2015 / 3.0 / Major / Significantly changed the technical content.
6/23/2016 / 3.0 / None / No changes to the meaning, language, or formatting of the technical content.
9/14/2016 / 3.0 / None / No changes to the meaning, language, or formatting of the technical content.
Table of Contents
1Introduction
1.1Glossary
1.2References
1.2.1Normative References
1.2.2Informative References
1.3Overview
1.3.1Roles
1.3.1.1Protocol Server
1.3.1.2Protocol Clients
1.3.2Scenarios
1.3.2.1Obtaining Information from the Protocol Server
1.3.2.2Obtaining Information from an Authenticated User
1.3.2.3Data Communication
1.4Relationship to Other Protocols
1.5Prerequisites/Preconditions
1.6Applicability Statement
1.7Versioning and Capability Negotiation
1.8Vendor-Extensible Fields
1.9Standards Assignments
2Messages
2.1Transport
2.2Common Message Syntax
2.2.1Namespaces
2.2.2Messages
2.2.2.1Mobile message packaged as MIME formatted e-mail message
2.2.2.1.1Message Headers
2.2.2.1.1.1Content-Class
2.2.2.1.1.2X-MS-Reply-To-Mobile
2.2.2.1.1.3To
2.2.2.1.1.4From
2.2.2.1.1.5Subject
2.2.2.1.2Message Body
2.2.2.1.2.1Incoming Text Message
2.2.2.1.2.2Incoming Multimedia Message
2.2.3Elements
2.2.4Complex Types
2.2.4.1tAudio
2.2.4.2tBody
2.2.4.3tContent
2.2.4.4tDeliveryError
2.2.4.5tHeader
2.2.4.6tImg
2.2.4.7tLayout
2.2.4.8tMeta
2.2.4.9tMmsSlides
2.2.4.10tPar
2.2.4.11tRegion
2.2.4.12tRoot-layout
2.2.4.13tText
2.2.4.14tTo
2.2.4.15tUser
2.2.4.16tXmsBody
2.2.4.17tXmsData
2.2.4.18tXmsHeader
2.2.4.19tXmsResponse
2.2.5Simple Types
2.2.5.1tRequiredServiceTypeEnum
2.2.6Attributes
2.2.6.1client
2.2.7Groups
2.2.8Attribute Groups
2.2.9Common Data Structures
3Protocol Details
3.1Server Details
3.1.1Abstract Data Model
3.1.2Timers
3.1.3Initialization
3.1.4Message Processing Events and Sequencing Rules
3.1.4.1GetServiceInfo
3.1.4.1.1Messages
3.1.4.1.1.1GetServiceInfoSoapIn
3.1.4.1.1.2GetServiceInfoSoapOut
3.1.4.1.2Elements
3.1.4.1.2.1GetServiceInfo
3.1.4.1.2.2GetServiceInfoResponse
3.1.4.1.2.3serviceInfo
3.1.4.1.3Complex Types
3.1.4.1.3.1tServiceInfo
3.1.4.1.3.2tSupportedService
3.1.4.1.3.3tSMS_SENDER
3.1.4.1.3.4tLONG_SMS_SENDER
3.1.4.1.3.5tMMS_SENDER
3.1.4.1.4Simple Types
3.1.4.1.4.1tAuthenticationTypeEnum
3.1.4.1.5Attributes
3.1.4.1.6Groups
3.1.4.1.7Attribute Groups
3.1.4.2GetUserInfo
3.1.4.2.1Messages
3.1.4.2.1.1GetUserInfoSoapIn
3.1.4.2.1.2GetUserInfoSoapOut
3.1.4.2.2Elements
3.1.4.2.2.1GetUserInfo
3.1.4.2.2.2GetUserInfoResponse
3.1.4.2.2.3xmsUser
3.1.4.2.2.4userInfo
3.1.4.2.3Complex Types
3.1.4.2.3.1tXmsUser
3.1.4.2.3.2tUserInfo
3.1.4.2.3.3tUserError
3.1.4.2.4Simple Types
3.1.4.2.5Attributes
3.1.4.2.6Groups
3.1.4.2.7Attribute Groups
3.1.4.3DeliverXms
3.1.4.3.1Messages
3.1.4.3.1.1DeliverXmsSoapIn
3.1.4.3.1.2DeliverXmsSoapOut
3.1.4.3.2Elements
3.1.4.3.2.1DeliverXms
3.1.4.3.2.2DeliverXmsResponse
3.1.4.3.2.3xmsData
3.1.4.3.2.4xmsResponse
3.1.4.3.3Complex Types
3.1.4.3.4Simple Types
3.1.4.3.5Attributes
3.1.4.3.6Groups
3.1.4.3.7Attribute Groups
3.1.4.4DeliverXmsBatch
3.1.4.4.1Messages
3.1.4.4.1.1DeliverXmsBatchSoapIn
3.1.4.4.1.2DeliverXmsBatchSoapOut
3.1.4.4.2Elements
3.1.4.4.2.1DeliverXmsBatch
3.1.4.4.2.2DeliverXmsBatchResponse
3.1.4.4.2.3xmsBatch
3.1.4.4.2.4xmsResponses
3.1.4.4.3Complex Types
3.1.4.4.3.1tXmsBatch
3.1.4.4.3.2tXmsDataInBatch
3.1.4.4.3.3tXmsResponseWithId
3.1.4.4.4Simple Types
3.1.4.4.5Attributes
3.1.4.4.6Groups
3.1.4.4.7Attribute Groups
3.1.4.5Send reply message to client after collecting them from the recipient’s phone
3.1.5Timer Events
3.1.6Other Local Events
3.2Client Details
3.2.1Abstract Data Model
3.2.2Timers
3.2.3Initialization
3.2.4Message Processing Events and Sequencing Rules
3.2.5Timer Events
3.2.6Other Local Events
4Protocol Examples
4.1GetServiceInfo
4.2GetUserInfo
4.3DeliverXms
4.4DeliverXmsBatch
4.5Send Reply Message from Server to Client after Server Collects the Mobile Message from Recipient’s Phone
5Security
5.1Security Considerations for Implementers
5.2Index of Security Parameters
6Appendix A: Full WSDL
7Appendix B: Product Behavior
8Change Tracking
9Index
1Introduction
The Office Mobile Service Protocol specifies the protocol used to transmit mobile messages between a protocol client and a protocol server.
Sections 1.5, 1.8, 1.9, 2, and 3 of this specification are normative. All other sections and examples in this specification are informative.
1.1Glossary
This document uses the following terms:
alert: A message that is passed to a protocol client to notify it when specific criteria are met.
ASCII: The American Standard Code for Information Interchange (ASCII) is an 8-bit character-encoding scheme based on the English alphabet. ASCII codes represent text in computers, communications equipment, and other devices that work with text. ASCII refers to a single 8-bit ASCII character or an array of 8-bit ASCII characters with the high bit of each character set to zero.
authenticated user: A built-in security group specified in [MS-WSO] whose members include all users that can be authenticated by a computer.
authentication: The act of proving an identity to a server while providing key material that binds the identity to subsequent communications.
certificate: A certificate is a collection of attributes (1) and extensions that can be stored persistently. The set of attributes in a certificate can vary depending on the intended usage of the certificate. A certificate securely binds a public key to the entity that holds the corresponding private key. A certificate is commonly used for authentication and secure exchange of information on open networks, such as the Internet, extranets, and intranets. Certificates are digitally signed by the issuing certification authority (CA) and can be issued for a user, a computer, or a service. The most widely accepted format for certificates is defined by the ITU-T X.509 version 3 international standards. For more information about attributes and extensions, see [RFC3280] and [X509] sections 7 and 8.
Hypertext Markup Language (HTML): An application of the Standard Generalized Markup Language (SGML) that uses tags to mark elements in a document, as described in [HTML].
language code identifier (LCID): A 32-bit number that identifies the user interface human language dialect or variation that is supported by an application or a client computer.
Multipurpose Internet Mail Extensions (MIME): A set of extensions that redefines and expands support for various types of content in email messages, as described in [RFC2045], [RFC2046], and [RFC2047].
Simple Mail Transfer Protocol (SMTP): A member of the TCP/IP suite of protocols that is used to transport Internet messages, as described in [RFC5321].
site: A group of related webpages that is hosted by a server on the World Wide Web or an intranet. Each website has its own entry points, metadata, administration settings, and workflows. Also referred to as web site.
SOAP action: The HTTP request header field used to indicate the intent of the SOAP request, using a URI value. See [SOAP1.1] section 6.1.1 for more information.
SOAP body: A container for the payload data being delivered by a SOAP message to its recipient. See [SOAP1.2-1/2007] section 5.3 for more information.
SOAP fault: A container for error and status information within a SOAP message. See [SOAP1.2-1/2007] section 5.4 for more information.
Synchronized Multimedia Integration Language (SMIL): An XML-based language that enables a data stream to be divided, transmitted as separate streams, and then recombined as a single stream, as described in [W3C-SMIL3.0].
Uniform Resource Identifier (URI): A string that identifies a resource. The URI is an addressing mechanism defined in Internet Engineering Task Force (IETF) Uniform Resource Identifier (URI): Generic Syntax [RFC3986].
Uniform Resource Locator (URL): A string of characters in a standardized format that identifies a document or resource on the World Wide Web. The format is as specified in [RFC1738].
web service: A unit of application logic that provides data and services to other applications and can be called by using standard Internet transport protocols such as HTTP, Simple Mail Transfer Protocol (SMTP), or File Transfer Protocol (FTP). Web services can perform functions that range from simple requests to complicated business processes.
XML fragment: Lines of text that adhere to XML tag rules, as described in [XML], but do not have a Document Type Definition (DTD) or schema, processing instructions, or any other header information.
XML namespace: A collection of names that is used to identify elements, types, and attributes in XML documents identified in a URI reference [RFC3986]. A combination of XML namespace and local name allows XML documents to use elements, types, and attributes that have the same names but come from different sources. For more information, see [XMLNS-2ED].
XML namespace prefix: An abbreviated form of an XML namespace, as described in [XML].
XML schema: A description of a type of XML document that is typically expressed in terms of constraints on the structure and content of documents of that type, in addition to the basic syntax constraints that are imposed by XML itself. An XML schema provides a view of a document type at a relatively high level of abstraction.
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.
1.2References
Links to a document in the Microsoft Open Specifications library point to the correct section in the most recently published version of the referenced document. However, because individual documents in the library are not updated at the same time, the section numbers in the documents may not match. You can confirm the correct section numbering by checking the Errata.
1.2.1Normative References
We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact . We will assist you in finding the relevant information.
[GIF89a] CompuServe Incorporated, "Graphics Interchange Format(sm)", Graphics Interchange Format Programming Reference, July 1990,
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997,
[RFC2616] Fielding, R., Gettys, J., Mogul, J., et al., "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999,
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000,
[RFC5321] Klensin, J., "Simple Mail Transfer Protocol", RFC 5321, October 2008,
[SOAP1.1] Box, D., Ehnebuske, D., Kakivaya, G., et al., "Simple Object Access Protocol (SOAP) 1.1", May 2000,
[SOAP1.2/1] Gudgin, M., Hadley, M., Mendelsohn, N., Moreau, J., and Nielsen, H.F., "SOAP Version 1.2 Part 1: Messaging Framework", W3C Recommendation, June 2003,
[WSDL] Christensen, E., Curbera, F., Meredith, G., and Weerawarana, S., "Web Services Description Language (WSDL) 1.1", W3C Note, March 2001,
[XMLNS] Bray, T., Hollander, D., Layman, A., et al., Eds., "Namespaces in XML 1.0 (Third Edition)", W3C Recommendation, December 2009,
1.2.2Informative References
[IANA-CharSets] IANA, "Character Sets", Last Updated 2010-11-04,
[MS-LCID] Microsoft Corporation, "Windows Language Code Identifier (LCID) Reference".
1.3Overview
This protocol allows a client to remotely send mobile messages to a server that processes and delivers these messages to a recipient’s phone. The protocol of data communication from a protocol server to a phone is not in the scope of this document.
A typical scenario for using this protocol is a data communication application between software in a computer with a phone. The software, as a protocol client, sends the data as specified in this document to a protocol server, and the protocol server will deliver the data to the phone. The phone can reply to the protocol server and the protocol server delivers the message to the protocol client via SMTP protocol.
Another scenario for using this protocol is an alert application sent from software in a computer to a phone. The software, as a protocol client, sends the data as specified in this document to a protocol server, and the protocol server will deliver the data to the phone. Such an application could use this protocol to provide user a notification on the phone when user has no access to the computer or Internet.
1.3.1Roles
Two roles are always being played whenever this protocol is used. There is always a protocol client issuing request to a protocol server, and there is always a protocol server to receive, process and respond to the requests of protocol clients.
1.3.1.1Protocol Server
The protocol server implements the Web service described by this protocol. It also maintains the database of authenticated users who can send a valid request to this server, as well as delivers the data sent from these users to the recipients’ phones according to the request. It also collects the replies from the phones and delivers to the protocol clients accordingly.
1.3.1.2Protocol Clients
Protocol clients issue commands to the protocol server via the Web service methods described in this protocol.
The client is required to implement the message delivery mechanism from client to server.
The client can also accept replies to the messages from a server, if two-way communication is required between the client and the recipient’s phone. If the application does not require a reply (such as an alert application), the client need not implement the interpretation mechanism in receiving the reply message.
1.3.2Scenarios
The methods described by this service enable several types of data communication operations.
1.3.2.1Obtaining Information from the Protocol Server
Protocol clients can send a request to understand what the protocol server can offer. A common usage is for the protocol clients to configure the behavior of itself according to the server’s information.
Figure 1: Obtaining information from a protocol server
1.3.2.2Obtaining Information from an Authenticated User
Protocol clients can obtain more detailed information from an authenticated user from the server. A common usage is for the protocol clients to obtain user’s phone number as the recipient of an alert.
Figure 2: Obtaining information from an authenticated user
Prior to the initiation of this request, the client is configured with the user’s authenticated information.
1.3.2.3Data Communication
Protocol clients can initiate communications with the protocol server by sending a SOAP message. The protocol server will send a response to the client. If the protocol server receives a mobile message as a reply, this will be delivered to the protocol client via SMTP.
Figure 3: Data communication
Prior to the initiation of sending messages to server, the client is configured with the user’s authenticated information.
1.4Relationship to Other Protocols
This protocol uses the SOAP message protocol for formatting request and response messages, as described in [SOAP1.1], [SOAP1.2/1] and [SOAP1.2/2]. It transmits those messages by using HTTPS, as described in [RFC2818].
The following diagram shows the underlying messaging and transport stack used by the protocol:
Figure 4: This protocol in relation to other protocols
This protocol has no interactions with parallel protocols, nor are there other protocols that substitute for it.
1.5Prerequisites/Preconditions
This protocol operates against a site that is identified by a URL that is known by protocol clients. The protocol client also knows the user’s authentication information for sending a request to retrieve user information or deliver message to the server. The protocol requires that SOAP data transferring under HTTPS to protect the user’s authentication information.
The protocol server maintains records of known protocol clients. For each client the server will store the information needed to authenticate messages sent from the client, and the e-mail addresses needed to deliver messages to the client.
1.6Applicability Statement
The protocol is designed to allow protocol clients to send mobile messages to the protocol server.
1.7Versioning and Capability Negotiation
None.
1.8Vendor-Extensible Fields
None.
1.9Standards Assignments
None.
2Messages
In the following sections, the schema definition might differ from the processing rules imposed by the protocol. The WSDL in this specification matches the WSDL that shipped with the product and provides a base description of the schema. The text that introduces the WSDL might specify differences that reflect actual Microsoft product behavior. For example, the schema definition might allow for an element to be empty, null, or not present but the behavior of the protocol as specified restricts the same elements to being non-empty, not null, and present.
2.1Transport
Protocol servers MUST support SOAP over HTTPS, as specified in [RFC2818], for securing communication with clients.
Protocol messages, including service discovery and mobile messages from protocol client to protocol server MUST be formatted as specified either in [SOAP1.1] section 4 or in [SOAP1.2/1] section 5. Protocol server faults MUST be returned either using HTTP status codes as specified in [RFC2616] section 10 or using SOAP faults as specified either in [SOAP1.1] section 4.4 or in [SOAP1.2/1] section 5.4.