Abstract: A system is configured to receive account information associated with a subscriber and a set of user devices, and receive user input, from a device associated with the subscriber, indicating that a feature is to be activated for the set of user devices. The device is configured to determine an association between the set of user devices and a feature code associated with the feature. The device is configured to receive a request to activate the feature from a user device, of the set of user devices, and determine that the user device is eligible to receive the feature based on the association between the set of user devices and the feature code. The device is configured to activate the feature for the user device based on determining that the user device is eligible to receive the feature.

Abstract: A user device may be configured to generate a multipart message (e.g., a multimedia messaging service (“MMS”) message). A message part of the multipart message may include conversation metadata that includes information regarding a messaging conversation between the user device and at least one other user device. The message part may include a multipart type indicator (e.g., a Multipurpose Internet Mail Extensions (“MIME”) type indicator) that indicates that a type of the at least one part is a type associated with conversation metadata. The user device may output the multipart message to the other user device.

Abstract: A messaging device receives configuration information from a configuration device. The messaging device identifies application configuration information, associated with a first user device, based on the configuration information and sends the application configuration information to the first user device for configuring a messaging application on the first user device. The messaging device receives an incoming message, including message information, from the messaging application on the first user device. The messaging device identifies, based on the message information and the configuration information, a second user device and a message format associated with the second user device. The messaging device sends, in the message format associated with the second user device, an outgoing message, based on the message information and the configuration information, to the second user device.

Abstract: A messaging device receives configuration information from a configuration device. The messaging device identifies application configuration information, associated with a first user device, based on the configuration information and sends the application configuration information to the first user device for configuring a messaging application on the first user device. The messaging device receives an incoming message, including message information, from the messaging application on the first user device. The messaging device identifies, based on the message information and the configuration information, a second user device and a message format associated with the second user device. The messaging device sends, in the message format associated with the second user device, an outgoing message, based on the message information and the configuration information, to the second user device.

Abstract: Systems and methods for creating gift messages for sending to individuals via an existing messaging infrastructure are described. A gift provider system may receive a request for a gift catalog from a first user device. The gift provider system may provide an interactive gift catalog to the first user device that includes one or more gift cards available for purchase. The user of the first user device may select the amount of the gift card, create a personalized message for the gift card, select a recipient, and select graphics that may accompany the gift card. The gift provider system may create a gift message based on the purchased gift card and send the gift message to the recipient. The gift message may be sent as an MMS message and may include one or more codes that the recipient can use to redeem the gift card with a providing merchant.

Abstract: A conversion device may receive a first message in a Telelocator Alphanumeric Protocol (TAP) format. The first message may include information that identifies a user device as an intended recipient of the first message. The first message may not be transmissible over a wireless connection. The conversion device may convert the first message into a second message in a first format capable of being transmitted over the wireless connection. The second message may include information that identifies the user device. The conversion device may provide the second message, using the wireless connection, to a messaging device. The wireless message may cause the messaging device to convert the second message into a third message in a second format that is capable of being delivered to the identified user device. The wireless message may further cause the messaging device to provide the third message to the user device.

Abstract: A conversion device may receive a first message in a Telelocator Alphanumeric Protocol (TAP) format. The first message may include information that identifies a user device as an intended recipient of the first message. The first message may not be transmissible over a wireless connection. The conversion device may convert the first message into a second message in a first format capable of being transmitted over the wireless connection. The second message may include information that identifies the user device. The conversion device may provide the second message, using the wireless connection, to a messaging device. The wireless message may cause the messaging device to convert the second message into a third message in a second format that is capable of being delivered to the identified user device. The wireless message may further cause the messaging device to provide the third message to the user device.

Abstract: A user device may be configured to generate a multipart message (e.g., a multimedia messaging service (“MMS”) message). A message part of the multipart message may include conversation metadata that includes information regarding a messaging conversation between the user device and at least one other user device. The message part may include a multipart type indicator (e.g., a Multipurpose Internet Mail Extensions (“MIME”) type indicator) that indicates that a type of the at least one part is a type associated with conversation metadata. The user device may output the multipart message to the other user device.

Abstract: A system is configured to receive account information associated with a subscriber and a set of user devices, and receive user input, from a device associated with the subscriber, indicating that a feature is to be activated for the set of user devices. The device is configured to determine an association between the set of user devices and a feature code associated with the feature. The device is configured to receive a request to activate the feature from a user device, of the set of user devices, and determine that the user device is eligible to receive the feature based on the association between the set of user devices and the feature code. The device is configured to activate the feature for the user device based on determining that the user device is eligible to receive the feature.