Abstract: A communications system may include a content provider device having an instant message (IM) content provider contact associated therewith and may be configured to store content. The communications system may include an IM contact server configured to register the content provider device and thereafter allow subscriber access to the IM content provider contact. The communications system may further include a communications server configured to communicate with the content provider device, and a subscriber device configured to access the IM content provider contact from the IM contact server, and download content from the content provider device via the communications server and based upon the IM content provider contact.

Abstract: A method is set forth of displaying a document identified by a URL on a mobile browser, comprising registering an attachment viewer plug-in to the mobile browser for a predetermined data stream content type, registering a mobile data service transcoder for predetermined document types, sending a request for the document of one of the predetermined document types from the mobile browser to the mobile service transcoder, retrieving and converting the document to the predetermined data stream content type, and forwarding the converted document from the mobile data service transcoder to the mobile browser for display via the attachment viewer plug-in.

Abstract: A generic IM device/server protocol permits a single implementation of a IM application on client devices for communicating with different enterprise IM servers types. The protocol defines a server maintained tag to identify the currency of a contact list it is managing for a client device. The client device receives and persists the tag and provides it at login. The server automatically sends a contact list update only if the tag indicates the client devices contact list instance is not current. Presence updates may also be sent automatically at login and the client device need not separately request contact list or presence updates at login. The client device may be pre-provisioned with respective graphics, text and server capabilities for multiple server types. A specific IM configuration may be selected in response to service information.

Abstract: Automatic identification and authentication of a user of a mobile application entails receiving from the wireless communications device a unique device identifier and an e-mail address corresponding to the wireless communications device, associating a registration identifier with the unique device identifier and the e-mail address, generating an authentication token, and communicating the authentication token and the registration identifier to the wireless communications device. This technology obviates the need for the user to remember and enter a user ID and password to access backed-up application data on a server. This is particularly useful for instant messaging applications, e.g. PIN messaging, in which the unique device identifier is used to identify the user and is also the transport address. Once registered, the user who has switched to a new device or has wiped his existing device, can restore contacts or other application data from the server based on the registration identifier.

Abstract: A method is set forth of displaying a document identified by a URL on a mobile browser, comprising registering an attachment viewer plug-in to the mobile browser for a predetermined data stream content type, registering a mobile data service transcoder for predetermined document types, sending a request for the document of one of the predetermined document types from the mobile browser to the mobile service transcoder, retrieving and converting the document to the predetermined data stream content type, and forwarding the converted document from the mobile data service transcoder to the mobile browser for display via the attachment viewer plug-in.

Abstract: A communications system may include a control device having an instant message (IM) device contact associated therewith. The communications system may also include a control gateway having an IM gateway contact associated therewith and may be configured to communicate with a controllable device over a network. The control gateway may be configured to validate the IM device contact. The control device may be configured to communicate with the controllable device through the control gateway after validation and based upon the IM device contact and the IM gateway contact.

Abstract: To promote efficient transmission of presence update information to a presence service client associated or integrated with a communication client such as an instant messaging (IM) client, a separate computing device may be notified when the communication client becomes dormant. The separate device may buffer presence updates destined for the communication client, each presence update containing information regarding availability of at least one of a set of contacts for intercommunication via said communication client. When the separate device learns that either the communication client has ceased being dormant or that an event has occurred which shall cause the communication client to cease being dormant, the buffered presence updates may be sent to the presence service client. Presence updates within the buffered set may be reconciled to eliminate obsolete information. The result may be a conservation of wireless connection bandwidth or reduction in device power consumption.

Abstract: A communications system may include a content provider device having an instant message (IM) content provider contact associated therewith and may be configured to store content. The communications system may include an IM contact server configured to register the content provider device and thereafter allow subscriber access to the IM content provider contact. The communications system may further include a communications server configured to communicate with the content provider device, and a subscriber device configured to access the IM content provider contact from the IM contact server, and download content from the content provider device via the communications server and based upon the IM content provider contact.

Abstract: A method is set forth of displaying a document identified by a URL on a mobile browser, comprising registering an attachment viewer plug-in to the mobile browser for a predetermined data stream content type, registering a mobile data service transcoder for predetermined document types, sending a request for the document of one of the predetermined document types from the mobile browser to the mobile service transcoder, retrieving and converting the document to the predetermined data stream content type, and forwarding the converted document from the mobile data service transcoder to the mobile browser for display via the attachment viewer plug-in.

Abstract: To promote efficient transmission of presence update information to a presence service client associated or integrated with a communication client such as an instant messaging (IM) client, a separate computing device may be notified when the communication client becomes dormant. The separate device may buffer presence updates destined for the communication client, each presence update containing information regarding availability of at least one of a set of contacts for intercommunication via said communication client. When the separate device learns that either the communication client has ceased being dormant or that an event has occurred which shall cause the communication client to cease being dormant, the buffered presence updates may be sent to the presence service client. Presence updates within the buffered set may be reconciled to eliminate obsolete information. The result may be a conservation of wireless connection bandwidth or reduction in device power consumption.

Abstract: A generic IM device/server protocol permits a single implementation of a IM application on client devices for communicating with different enterprise IM servers types. The protocol defines a server maintained tag to identify the currency of a contact list it is managing for a client device. The client device receives and persists the tag and provides it at login. The server automatically sends a contact list update only if the tag indicates the client devices contact list instance is not current. Presence updates may also be sent automatically at login and the client device need not separately request contact list or presence updates at login. The client device may be pre-provisioned with respective graphics, text and server capabilities for multiple server types. A specific IM configuration may be selected in response to service information.

Abstract: Automatic identification and authentication of a user of a mobile application entails receiving from the wireless communications device a unique device identifier and an e-mail address corresponding to the wireless communications device, associating a registration identifier with the unique device identifier and the e-mail address, generating an authentication token, and communicating the authentication token and the registration identifier to the wireless communications device. This technology obviates the need for the user to remember and enter a user ID and password to access backed-up application data on a server. This is particularly useful for instant messaging applications, e.g. PIN messaging, in which the unique device identifier is used to identify the user and is also the transport address. Once registered, the user who has switched to a new device or has wiped his existing device, can restore contacts or other application data from the server based on the registration identifier.

Abstract: A generic IM device/server protocol permits a single implementation of a IM application on client devices for communicating with different enterprise IM servers types. The protocol defines a server maintained tag to identify the currency of a contact list it is managing for a client device. The client device receives and persists the tag and provides it at login. The server automatically sends a contact list update only if the tag indicates the client devices contact list instance is not current. Presence updates may also be sent automatically at login and the client device need not separately request contact list or presence updates at login. The client device may be pre-provisioned with respective graphics, text and server capabilities for multiple server types. A specific IM configuration may be selected in response to service information.

Abstract: To promote efficient transmission of presence update information to a presence service client associated or integrated with a communication client such as an instant messaging (IM) client, a separate computing device may be notified when the communication client becomes dormant. The separate device may buffer presence updates destined for the communication client, each presence update containing information regarding availability of at least one of a set of contacts for intercommunication via said communication client. When the separate device learns that either the communication client has ceased being dormant or that an event has occurred which shall cause the communication client to cease being dormant, the buffered presence updates may be sent to the presence service client. Presence updates within the buffered set may be reconciled to eliminate obsolete information. The result may be a conservation of wireless connection bandwidth or reduction in device power consumption.

Abstract: A method is set forth of displaying a document identified by a URL on a mobile browser, comprising registering an attachment viewer plug-in to the mobile browser for a predetermined data stream content type, registering a mobile data service transcoder for predetermined document types, sending a request for the document of one of the predetermined document types from the mobile browser to the mobile service transcoder, retrieving and converting the document to the predetermined data stream content type, and forwarding the converted document from the mobile data service transcoder to the mobile browser for display via the attachment viewer plug-in.

Abstract: A generic IM device/server protocol permits a single implementation of a IM application on client devices for communicating with different enterprise IM servers types. The protocol defines a server maintained tag to identify the currency of a contact list it is managing for a client device. The client device receives and persists the tag and provides it at login. The server automatically sends a contact list update only if the tag indicates the client devices contact list instance is not current. Presence updates may also be sent automatically at login and the client device need not separately request contact list or presence updates at login. The client device may be pre-provisioned with respective graphics, text and server capabilities for multiple server types. A specific IM configuration may be selected in response to service information.