Abstract: To control secondary devices of a subscriber whose primary device is subscribed to a mobile network, a secondary mobile directory number (“MDN”) and secondary device identifiers are employed. After the primary device is rung, an Authentication and Call Waiting Engine receives a request from a Telephony Gateway to retrieve identifiers of any secondary devices that are linked to a primary MDN of the primary device. Next, the Authentication and Call Waiting Engine retrieves a secondary device identifier for each secondary device that is paired with the primary device by searching a secondary device identifier database with the primary MDN to find all linked secondary device identifiers. A rules database may be applied to exclude secondary device identifiers based on time of day and day of the week. The Authentication and Call Waiting Engine transmits the list of qualified secondary device identifiers to the Telephony Gateway for ringing.

Abstract: Systems and methods for message timestamp re-alignment for message thread consistency across multiple devices are disclosed. In some implementations, an outbound message originating at a mobile phone is received at an integrated messaging server. The outbound message is associated with a messaging protocol. A timestamp representing a send time for the outbound message associated with the messaging protocol at the mobile phone is determined, at the integrated messaging server, by receiving an indication of the send time from the mobile phone. The outbound message and the timestamp are stored at the integrated messaging server. The outbound message and the timestamp representing the send time for the outbound message are provided from the integrated messaging server to a client computing device different from the mobile phone.

Abstract: An approach is provided for messaging gateway services. It is determined whether a user profile specifies opting to receive content. The content is selectively forwarded, according to a multimedia protocol, to a device of a user as a multimedia messaging service (MMS) message or a short messaging service (SMS) message based on the determination, wherein the multimedia protocol supports both MMS messaging and SMS messaging.

Abstract: To control secondary devices of a subscriber whose primary device is subscribed to a mobile network, a secondary mobile directory number (“MDN”) and secondary device identifiers are employed. After the primary device is rung, an Authentication and Call Waiting Engine receives a request from a Telephony Gateway to retrieve identifiers of any secondary devices that are linked to a primary MDN of the primary device. Next, the Authentication and Call Waiting Engine retrieves a secondary device identifier for each secondary device that is paired with the primary device by searching a secondary device identifier database with the primary MDN to find all linked secondary device identifiers. A rules database may be applied to exclude secondary device identifiers based on time of day and day of the week. The Authentication and Call Waiting Engine transmits the list of qualified secondary device identifiers to the Telephony Gateway for ringing.

Abstract: Systems and methods for message timestamp re-alignment for message thread consistency across multiple devices are disclosed. In some implementations, an outbound message originating at a mobile phone is received at an integrated messaging server. The outbound message is associated with a messaging protocol. A timestamp representing a send time for the outbound message associated with the messaging protocol at the mobile phone is determined, at the integrated messaging server, by receiving an indication of the send time from the mobile phone. The outbound message and the timestamp are stored at the integrated messaging server. The outbound message and the timestamp representing the send time for the outbound message are provided from the integrated messaging server to a client computing device different from the mobile phone.

Abstract: A server receives encrypted information for an intended recipient. The server determines, based on recipient information, whether the recipient's device is able to decrypt the encrypted information. If so, the encrypted information is provided to the device. Upon determining that the device is unable to decrypt the encrypted information, the server sends a notification message to the device. The notification message indicates that the encrypted message has been received. In response to the notification message, the server receives a response from the device. If the device is successfully authenticated, based on the response, the server decrypts the encrypted information and provides the decrypted information to the device for presentation to the recipient.

Abstract: A method includes receiving a message, determining at least one of a message importance level or a message delivery alert level based on one or more message characteristics associated with the message and generating metadata that indicates the at least one of the message importance level or the message delivery alert level with the message. The method further includes transmitting the message and the metadata toward a destination, receiving the message with the metadata, and providing notification and user interface indication corresponding to the at least one of the message importance level or the message delivery alert level or a storing of the message in an inbox folder corresponding to the at least one of the message importance level or the message delivery alert level.

Abstract: An approach is provided for messaging gateway services. It is determined whether a user profile specifies opting to receive content. The content is selectively forwarded, according to a multimedia protocol, to a device of a user as a multimedia messaging service (MMS) message or a short messaging service (SMS) message based on the determination, wherein the multimedia protocol supports both MMS messaging and SMS messaging.

Abstract: An approach is provided for messaging gateway services. It is determined whether a user profile specifies opting to receive content. The content is selectively forwarded, according to a multimedia protocol, to a device of a user as a multimedia messaging service (MMS) message or a short messaging service (SMS) message based on the determination, wherein the multimedia protocol supports both MMS messaging and SMS messaging.

Abstract: For a location-based broadcast messaging service, a broadcast server receives a broadcast request from a business application server. The broadcast request includes a message, at least one identifier for target mobile devices, and an identifier for a location. The broadcast server sends a location query including the identifier for the location to location agents associated with the target mobile devices. In response to receiving the location query, each location agent determines whether the location of the associated mobile device is within or otherwise satisfies a requirement related to the identified location. If the location of the device is within the identified location or satisfies the requirement, the location agent sends a query response to the broadcast server and receives, from the broadcast server, the message included in the broadcast request. The broadcast request can include a time-period identifier, such that the location agent determines the device location during the time-period.

Abstract: A method for a client and server based messaging system efficiently exchanges messages over an IP connection in a wireless network. Also included is an automated method by which a messaging client can request intelligent and efficient presence updates from the wireless network by utilizing timers and adapt such timers based on load conditions in the wireless network.

Abstract: For a location-based broadcast messaging service, a broadcast server receives a broadcast request from a business application server. The broadcast request includes a message, at least one identifier for target mobile devices, and an identifier for a location. The broadcast server sends a location query including the identifier for the location to location agents associated with the target mobile devices. In response to receiving the location query, each location agent determines whether the location of the associated mobile device is within or otherwise satisfies a requirement related to the identified location. If the location of the device is within the identified location or satisfies the requirement, the location agent sends a query response to the broadcast server and receives, from the broadcast server, the message included in the broadcast request. The broadcast request can include a time-period identifier, such that the location agent determines the device location during the time-period.

Abstract: A method that enables provisioning of mobile station messages to multiple devices associated with the sender and/or receiver includes receiving, at a mobile messaging service center, a mobile messaging service message; identifying a destination mobile station associated with the received message, the destination mobile station having a Mobile Directory Number and corresponding to a primary device of a customer of a mobile communication network provider; and delivering, through a mobile communication network, the received message to the primary device of the customer. The method also includes steps of determining whether the customer subscribes to a Messaging Anywhere (MA) service; upon determination that the customer subscribers to the MA service, delivering, from the mobile messaging service center, a copy of the received message to an MA server; and delivering, from the MA server, the message to a secondary device previously identified by the customer.

Abstract: Techniques and equipment are provided to allow Multimedia Message Service (MMS) communication between applications on a platform on a mobile station and third party websites or web servers by using a hybridized architectural design of MMS and BREW services. The following communications are provided: communication from a BREW application on a first mobile station to a BREW application on a second mobile station, communication from a BREW application on a mobile station to an application server or website, and communication from an application server or website to a BREW application on a mobile station.

Abstract: A method may include receiving a multimedia messaging service (MMS) message from a sending device, the MMS message being addressed to a terminating device. A notification may be sent to the terminating device that the MMS message is available. A user agent profile may be received from the terminating device, the user agent profile including a network indicator to indicate the type of network currently servicing the terminating device. It may then be determined if transcoding of the MMS message is required based on the type of network indicated in the user agent profile and attributes of the MMS message.

Abstract: A method for offloads SMS messages from a voice network of a wireless carrier to a data network. The method includes sending a mobile originated SMS using hypertext transfer protocol (HTTP) from a wireless handset to a short message service center (SMSC) over a wireless data network. The method further includes conducting a lookup at the SMSC to determine the home SMSC for the originating mobile handset and sending a redirect to the mobile handset as means to facilitate a dynamic update of the home SMSC location stored on the wireless handset.

Abstract: Techniques and equipment are provided to allow Multimedia Message Service (MMS) communication between applications on a platform on a mobile station and third party websites or web servers by using a hybridized architectural design of MMS and BREW services. The following communications are provided: communication from a BREW application on a first mobile station to a BREW application on a second mobile station, communication from a BREW application on a mobile station to an application server or website, and communication from an application server or website to a BREW application on a mobile station.

Abstract: Techniques and equipment are provided to allow Multimedia Message Service (MMS) communication between applications on a platform on a mobile station and third party websites or web servers by using a hybridized architectural design of MMS and BREW services. The following communications are provided: communication from a BREW application on a first mobile station to a BREW application on a second mobile station, communication from a BREW application on a mobile station to an application server or website, and communication from an application server or website to a BREW application on a mobile station.

Abstract: A disclosed enterprise instant messaging (IM) service aggregator enables validation of mobile stations and/or users for enterprise IM service through a wireless communication network; and in the examples, the enterprise IM service provides a secure messaging environment that allows IM traffic to/from wireless mobile stations. The security offered may be unique to and controlled by each enterprise, for example, by enabling each enterprise to generate its own encryption key for distribution through the aggregator and by allowing mobile stations to generate their own keys for distribution back through the aggregator to the enterprise IM servers. As disclosed, the login credentials are encrypted from the mobile station to the enterprise IM server. The use of standard encryption methods within the call flows allows a simple method of ensuring that only authorized users can access the enterprise servers and that the messages will be encrypted by the strongest possible means.

Abstract: An approach is provided for messaging gateway services. It is determined whether a user profile specifies opting to receive content. The content is selectively forwarded, according to a multimedia protocol, to a device of a user as a multimedia messaging service (MMS) message or a short messaging service (SMS) message based on the determination, wherein the multimedia protocol supports both MMS messaging and SMS messaging.