PROTOCOL AGNOSTIC DYNAMIC MESSAGING PLATFORM AND A SYSTEM AND A METHOD THEREOF

• US 20140006528A1
• Filed: 05/06/2013
• Published: 01/02/2014
• Est. Priority Date: 06/27/2012
• Status: Abandoned Application

• Current Assignee: Synchronoss Technologies Incorporated
• Original Assignee: Synchronoss Technologies Incorporated
• Inventors: Allen, Aristotle B., Kowalchuck, Dan, Smyth, Jeffrey, Negandhi, Priyesh, Powell, Tony
• Application Number:
  US13/888,230
• Publication Number:
  US 20140006528A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression

Abstract

Embodiments of the present invention relates to a protocol agnostic dynamic messaging platform. Typically, the platform dynamically creates a message based on a transactional state associated with a first external entity. The platform automatically generates content, determines content format, and chooses a transmission protocol for the message to be sent to a second external entity. The platform is advantageously flexible to allow a message of any content type to be transmitted via any transmission protocol.

Claims

1. A messaging platform comprising:

a. a receiver component configured to handle a request from a first external entity;

b. a qualifier component is configured to determine whether the request requires a message to be sent to a second external entity and to define a rule for the message, wherein the rule specifies content, an appropriate content format, and an appropriate transmission protocol;

c. an assembler component is configured to create the message based on the rule; and

d. a sender component configured to affix the transmission protocol for the message and to send the message to the second external entity.

2. The messaging platform of claim 1, wherein the request is one of event driven and state driven.

3. The messaging platform of claim 1, wherein the first external entity is the second external entity.

4. The messaging platform of claim 1, wherein the content is customized for the second external entity.

5. The messaging platform of claim 1, wherein the assembler component is associated with the content format.

6. The messaging platform of claim 1, wherein the content format is plain text, media, HTML, or binary type.

7. The messaging platform of claim 1, wherein the sender component is associated with the transmission protocol.

8. The messaging platform of claim 1, wherein the transmission protocol is SMS, FTP, SCP, SMTP, HTTPS, MMS, or HTTP.

9. The messaging platform of claim 1, wherein the determination made by the qualifier component is based on configuration data.

10. The messaging platform of claim 1, further comprising a qualifier factory including at least one qualifier component, wherein the at least one qualifier component includes the qualifier component.

11. The messaging platform of claim 1, further comprising an assembler factory including at least one assembler component, wherein the at least one assembler component includes the assembler component.

12. The messaging platform of claim 1, further comprising a sender factory including at least one sender component, wherein the at least one sender component includes the sender component.

13. The messaging platform of claim 1, further comprising a controller configured to select the assembler component and the sender component based on the rule.

14. The messaging platform of claim 13, wherein the controller is a part of the assembler component.

15. The messaging platform of claim 1, further comprising an auditor component configured to audit all actions within the messaging platform.

16. A non-transitory computer-readable medium storing instructions that, when executed by a computing device, cause the computing device to perform a method comprising:

a. receiving a request from a first external entity;

b. qualifying the request received from the first external entity as one of a first type and a second type; and

c. automatically performing a first procedure in response to the request being qualified as the first type, and automatically performing a second procedure in response to the request being qualified as the second type.

17. The non-transitory computer-readable medium of claim 16, wherein the first type does not require a message to be sent to a second external entity, and the second type does require a message to be sent to the second external entity.

18. The non-transitory computer-readable medium of claim 16, wherein the request is qualified based on a state associated with the request.

19. The non-transitory computer-readable medium of claim 16, wherein the first procedure includes returning a response to the first external entity indicating that no messages were sent to a second external entity.

20. The non-transitory computer-readable medium of claim 16, wherein the second procedure includes:

a. creating a message including content; and

b. sending the message to a second external entity.

21. The non-transitory computer-readable medium of claim 20, wherein the second procedure includes, prior to creating a message, defining a rule for the message.

22. The non-transitory computer-readable medium of claim 20, wherein creating a message includes referencing configuration data to determine how to create the message.

23. The non-transitory computer-readable medium of claim 20, wherein creating a message includes customizing the message tailored to a second external entity.

24. The non-transitory computer-readable medium of claim 20, wherein format of the content is plain text, media, html, or binary data.

25. The non-transitory computer-readable medium of claim 20, wherein sending the message includes affixing an appropriate transmission protocol.

26. The non-transitory computer-readable medium of claim 20, wherein the second procedure further includes auditing all actions associated with the request.

27. The non-transitory computer-readable medium of claim 26, wherein the second procedure further includes relaying information regarding the sent message to the first external entity.

28. A system comprising:

a. a first external entity; and

b. a messaging platform communicatively coupled with the first external entity, wherein the messaging platform is configured to dynamically create a message based on a transactional state associated with the first external entity.

29. The system of claim 28, wherein the messaging platform is configured to automatically generate content, automatically determine content format, and automatically choose a transmission protocol for the message.

30. The system of claim 28, wherein the messaging platform is configured to audit all actions within the messaging platform, and to provide the first external entity information regarding an audit associated with a request made by the first external entity.

31. The system of claim 28, wherein the messaging platform includes modular components, wherein the modular components includes a receiver component, a qualifier component, an assembler component, a sender component and an auditor component.

32. The system of claim 28, further comprising a second external entity communicatively coupled with the messaging platform, wherein the second external entity is configured to receive the message.

33. The system of claim 28, further comprising a data store communicatively coupled with the messaging platform, wherein the data store is configured to store configuration data.

34. The system of claim 28, further comprising administration tools configured to alter the system.