Identifiers for enterprise messages

• US 9,973,906 B2
• Filed: 02/22/2017
• Issued: 05/15/2018
• Est. Priority Date: 07/01/2015
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Prabhune, Rohini, Sanjeev, Kumar, Khanna, Radhika, Steinbach, Lodema M.
• Primary Examiner(s): Taylor, Nathan
• Application Number:
  US15/439,356
• Publication Number:
  US 20170164170A1
• Time in Patent Office: 447 Days
• Field of Search: 455466
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements

Abstract

A device of a first party may receive a message from a second party. The device may obtain mapping information. The mapping information may be associated with a third party verification that the enterprise identifier was assigned to the second party. The mapping information may be associated with mapping the enterprise identifier to a media identifier selected by the second party or the third party to represent the enterprise sender. The device may map the enterprise identifier to the media identifier based on the mapping information. The device may provide the media identifier with the message.

Claims

1. A device, comprising:

one or more processors to;

receive an enterprise message from a sender identified by an enterprise identifier of a set of enterprise identifiers;

determine that an identifier associated with the enterprise message is the enterprise identifier based on mapping the identifier to the enterprise identifier using mapping information stored on the device,

the mapping information representing a third party verification, for the device, that each enterprise identifier, of the set of enterprise identifiers, corresponds to a respective media identifier of a set of media identifiers, and

the mapping information being part of a messaging application downloaded or installed on the device;

map the enterprise identifier to a particular media identifier, of the set of media identifiers, based on the mapping information;

provide the particular media identifier with the enterprise message via a user interface based on mapping the enterprise identifier to the particular media identifier;

request, based on a threshold period of time elapsing, updated mapping information from a messaging application server;

receive another enterprise message from another sender identified by another enterprise identifier;

map the other enterprise identifier to another media identifier based on the updated mapping information; and

provide the other media identifier with the other enterprise message for display based on mapping the other enterprise identifier to the other media identifier.

2. The device of claim 1, where the one or more processors, when determining that the identifier associated with the enterprise message is the enterprise identifier, are to:

parse the enterprise message to identify at least one of a short code or a long code associated with the enterprise identifier.

3. The device of claim 1, where the particular media identifier includes at least one of:

an icon,

a logo,

an image,

a name,

a video, or

a sound.

4. The device of claim 1, where the one or more processors are further to:

consolidate a plurality of messages associated with the particular media identifier into a thread of messages identified by the particular media identifier.

5. The device of claim 1, where the one or more processors, when providing the particular media identifier, are to:

provide the particular media identifier via the user interface without providing the enterprise identifier via the user interface.

6. The device of claim 1, where the one or more processors, when receiving the enterprise message from the sender, are to:

receive the enterprise message from the sender via a short message service (SMS) message or a multimedia message service (MMS) message.

7. The device of claim 1, where the messaging application is verified by a third party.

8. A computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more processors of a device, cause the one or more processors to;

receive an enterprise message from a sender identified by an enterprise identifier of a set of enterprise identifiers;

determine that an identifier associated with the enterprise message is the enterprise identifier based on mapping the identifier to the enterprise identifier using mapping information stored on the device,

the mapping information representing a third party verification, for the device, that each enterprise identifier, of the set of enterprise identifiers, corresponds to a respective media identifier of a set of media identifiers, and

the mapping information being part of a messaging application downloaded or installed on the device;

map the enterprise identifier to a particular media identifier, of the set of media identifiers, based on the mapping information;

provide the particular media identifier with the enterprise message via a user interface based on mapping the enterprise identifier to the particular media identifier;

request, based on a threshold period of time elapsing, updated mapping information from a messaging application server;

receive another enterprise message from another sender identified by another enterprise identifier;

map the other enterprise identifier to another media identifier based on the updated mapping information; and

provide the other media identifier with the other enterprise message for display based on mapping the other enterprise identifier to the other media identifier.

9. The computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to determine that the identifier associated with the enterprise message is the enterprise identifier, cause the one or more processors to:

parse the enterprise message to identify at least one of a short code or a long code associated with the enterprise identifier.

10. The computer-readable medium of claim 8, where the particular media identifier includes at least one of:

an icon,

a logo,

an image,

a name,

a video, or

a sound.

11. The computer-readable medium of claim 8, where the one or more instructions further cause the one or more processors to:

consolidate a plurality of messages associated with the particular media identifier into a thread of messages identified by the particular media identifier.

12. The computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to provide the particular media identifier, cause the one or more processors to:

provide the particular media identifier via the user interface without providing the enterprise identifier via the user interface.

13. The computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to receive the enterprise message from the sender, cause the one or more processors to:

receive the enterprise message from the sender via a short message service (SMS) message or a multimedia message service (MMS) message.

14. The computer-readable medium of claim 8, where the messaging application is verified by a third party.

15. A method, comprising:

receiving, by a device, an enterprise message from a sender identified by an enterprise identifier of a set of enterprise identifiers;

determining, by the device, that an identifier associated with the enterprise message is the enterprise identifier based on mapping the identifier to the enterprise identifier using mapping information stored on the device,

the mapping information representing a third party verification, for the device, that each enterprise identifier, of the set of enterprise identifiers, corresponds to a respective media identifier of a set of media identifiers, and

the mapping information being part of a messaging application downloaded or installed on the device;

mapping, by the device, the enterprise identifier to a particular media identifier, of the set of media identifiers, based on the mapping information;

providing, by the device, the particular media identifier with the enterprise message via a user interface based on mapping the enterprise identifier to the particular media identifier;

requesting, by the device and based on a threshold period of time elapsing, updated mapping information from a messaging application server;

receiving, by the device, another enterprise message from another sender identified by another enterprise identifier;

mapping, by the device, the other enterprise identifier to another media identifier based on the updated mapping information; and

providing, by the device, the other media identifier with the other enterprise message for display based on mapping the other enterprise identifier to the other media identifier.

16. The method of claim 15, where determining that the identifier associated with the enterprise message is the enterprise identifier comprises:

parsing the enterprise message to identify at least one of a short code or a long code associated with the enterprise identifier.

17. The method of claim 15, further comprising:

consolidating a plurality of messages associated with the particular media identifier into a thread of messages identified by the particular media identifier.

18. The method of claim 15, where providing the particular media identifier comprises:

providing the particular media identifier via the user interface without providing the enterprise identifier via the user interface.

19. The method of claim 15, where receiving the enterprise message from the sender comprises:

receiving the enterprise message from the sender via a short message service (SMS) message or a multimedia message service (MMS) message.

20. The method of claim 15, where the messaging application is verified by a third party.