Messaging protocol

• US 20060095511A1
• Filed: 12/12/2005
• Published: 05/04/2006
• Est. Priority Date: 12/19/2000
• Status: Abandoned Application

• Current Assignee: Andrew Amadeo Munarriz, Marco Santulli
• Original Assignee: Andrew Amadeo Munarriz, Marco Santulli
• Inventors: Santulli, Marco, Munarriz, Andrew Amadeo
• Application Number:
  US11/299,405
• Publication Number:
  US 20060095511A1
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database

Abstract

A messaging system transfers messages between server and client in XML format. The transfer of messages is by HTTP. The server and client store messages in the XML format. The server can collect messages from various sources, convert those into the XML format and supply them to the client. The XML message may include an instruction to the client or server as to how the message is to be processed, for example sent, stored or deleted. The XML messages can be converted to WML format for display on devices such as mobile phones.

Claims

1-68. -68. (canceled)

69. A server comprising:

a process receiving email messages in SMTP format and instant messaging messages;

the server converting the email messages to an XML format having one or more fields and converting the instant messaging messages to the XML format; and

the server transmitting the XML format email messages and instant messaging messages to a client.

70. The server as claimed in claim 69 retrieving email messages and instant messaging messages stored on another server which were addressed to that other server, or a user account on that server, and transmitting the retrieved email messages and instant messaging messages to the client in the XML format.

71. The server as claimed in claim 69 converting the email messages and instant messaging messages in the XML format to a format including display layout information.

72. The server as claimed in claim 71 wherein the conversion is to a format including display layout information using Extensible Stylesheet Language (XSL).

73. The server as claimed in claim 71 wherein the conversion is to Wireless Mark-up Language (WML).

74. The server as claimed claim 69 comprising a message store wherein the server stores the email messages or the instant messaging messages for the client between sessions for that client.

75. The server as claimed claim 69 wherein the server is stores the email messages or the instant messaging messages for the client between sessions for that client.

76. The server as claimed in claim 69, transferring messages in said format using a HTTP protocol.

77. The server as claimed in claim 76 wherein the HTTP protocol is HTTPS.

78. The server as claimed in claim 69 performing an action on the email messages or the instant messaging messages, that action being indicated in one of the fields of the email messages and the instant messaging messages in the XML format.

79. The server as claimed in claim 78 wherein the field indicating the action indicates that the email message or the instant messaging message is to be sent and the server is responsive to that field to send the email message or the instant messaging message.

80. The server as claimed in claim 78 wherein the field indicating the action indicates that the email message or the instant messaging message is to be stored and the server is responsive to that field to store the message.

81. The server as claimed in claim 78 wherein the field indicating the action indicates that the email message or the instant messaging message is to be deleted and the server is responsive to that field to delete the message.

82. The server as claimed in claim 69 comprising a file defining which said XML fields the email messages or the instant messaging messages can contain.

83. The server as claimed in claim 82 interpreting the email messages or the instant messaging messages using the file defining the XML fields.

84. The server as claimed in claim 83 wherein the file defining the XML fields is in an XML format.

85. A method of transmitting messages comprising:

receiving email messages in an SMTP format with a server;

receiving instant messages with the server;

converting the email messages to an XML format;

converting the instant messaging messages to the XML format;

transmitting the converted email messages to a client; and

transmitting the converted instant messaging messages to the client.

86. A client comprising:

a process receiving an email message in an SMTP format;

the process converting the email message in the SMTP format to an XML format message; and

the process transmitting the XML format message to a server

87. The client as claimed in claim 86 comprising a message store, wherein the client stores the email messages between sessions with the server.

88. The client as claimed in claim 86 wherein the client does not store the email messages between sessions with the server.

89. The client as claimed in claim 86 comprising a file defining one or more delimited fields of the XML message format.

90. The client as claimed in claim 89 interpreting the email messages in the SMTP format using the file defining the delimited fields of the XML message format.

91. The client as claimed in claim 89 wherein said file defining the delimited fields is in XML format.

94. The client as claimed in claim 86 arranged to carry out an action on the email message, the action being indicated in a field of the email message.

92. The client as claimed 86, arranged to transfer XML format messages using an HTTP protocol.

93. The client as claimed in claim 92 wherein the HTTP protocol is HTTPS.

95. A system comprising:

a client and a server;

the client receiving an email message in SMTP format;

the client transmitting the email message to the server in an XML format; and

wherein the message sent to the server in the XML format includes a field indicating an action to be carried out on the message.

96. The client as claimed in claim 95 wherein the field indicating the action to be carried out on the message indicates that the message is to be sent and the server is responsive to that field to send the message.

97. The client as claimed in claim 95 wherein the field indicating the action to be carried out on the message indicates that it is to be stored and the server is responsive to that field to store the message.

98. The client as claimed in claim 95 wherein the field indicating the action to be carried out on the message indicates that it is to be deleted and the server is responsive to that field to delete the message.