Methods and apparatus for enabling a dynamic network of interactors according to personal trust levels between interactors

• US 20060031510A1
• Filed: 09/27/2005
• Published: 02/09/2006
• Est. Priority Date: 01/26/2004
• Status: Abandoned Application

• Current Assignee: Forte Internet Software, Inc.
• Original Assignee: Forte Internet Software, Inc.
• Inventors: Beck, Christopher Clemmett Macleod, Sidell, Mark Franklin, Powers, James Karl, Knuff, Charles Dazler, Gold, Thomas Knox
• Application Number:
  US11/237,269
• Publication Number:
  US 20060031510A1
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A system for causing routing of a communication event includes a sending platform for initiating and sending the communication event, a communications network for carrying the communication event, a receiving platform for receiving the communication event for final routing, and a router resident at least in the receiving platform for preparing and executing or forwarding for execution a routing instruction for handling the incoming communication event or notification thereof, the routing instruction thus executed, overriding a default routing instruction, the overriding routing instruction initiated upon discovery by the router of some level of trust metric between the sender and intended recipient of the event.

Claims

1. A system for causing routing of a communication event comprising;

a sending platform for initiating and sending the communication event;

a communications network for carrying the communication event;

a receiving platform for receiving the communication event for final routing; and

a router resident at least in the receiving platform for preparing and executing or forwarding for execution a routing instruction for handling the incoming communication event or notification thereof, the routing instruction thus executed, overriding a default routing instruction, the overriding routing instruction initiated upon discovery by the router of some level of trust metric between the sender and intended recipient of the event.

2. The system of claim 1, wherein the sending platform is one of a computer station, a telephone system, a cellular telephone, a personal digital assistant, a pager, a voice over Internet protocol phone, an Internet protocol telephone, or a video teleconferencing system.

3. The system of claim 1, wherein the receiving platform is one of a computer station, a telephone system, a cellular telephone, a personal digital assistant, a pager, a voice over Internet protocol phone, an Internet protocol telephone, or a video teleconferencing system.

4. The system of claim 1, wherein the communications network is the Internet network.

5. The system of claim 1, wherein the network is the Internet network and a telephone network integrated for communication through a bridging facility.

6. The system of claim 5, wherein the Internet network includes connected sub-networks and the telephone network includes wireless carrier networks.

7. The system of claim 1, wherein the communication event is one of an email, a voice mail, a telephone call notification, a video call notification, an instant message, a page, an Internet protocol telephony call notification, a file transfer request, or an invitation message to engage in a communication sequence.

8. The system of claim 1, wherein the receiving platform is a central routing facility.

9. The system of claim 1, wherein the receiving platform is an interactive voice response system connected to a routing system.

10. The system of claim 1, wherein the router is a software application having a graphic user interface including a portion thereof for providing system recommendations about trust plausibility associated with received events and for providing system recommendations of trust related to contacts available in a network directory.

11. The system of claim 1, wherein the router is a routine integrated with a firewall or other message filtering system.

12. The system of claim 1, wherein a router is resident in the sending platform and in the receiving platform.

13. The system of claim 1, wherein the router generates an extensible markup language-based trust interaction markup language from stored interaction history and contact parameters.

14. The system of claim 12, wherein the routers generate an extensible markup language-based trust interaction markup language from stored interaction history and contact parameters.

15. The system of claim 1, wherein the level of trust for a contact is configurable to extend trust beyond direct trust of the contact to users who are trusted by the contact.

16. The system of claim 1, wherein the level of trust for a contact and trusted users of the contact is configurable to a granularity of trusting or not trusting communications event types, and file types of attachments associated with those events.

17. A router for preparing and executing or forwarding for execution a routing instruction comprising:

a data conversion module for generating metadata from stored data;

a data communication module for sending and receiving metadata generated from stored data;

a data processing module for processing metadata sets, such processing sequence resulting in a positive or a negative determination of a trust relationship; and

, an instruction generation module for generating a routing instruction useable by an associated routing system.

18. The router of claim 17 resident in and operable on a network-capable communications device as a software application including a portion thereof for providing system recommendations about trust plausibility associated with received events and for providing system recommendations of trust related to contacts available in a network directory.

19. The router of claim 18, wherein the network-capable communications device is one of a desktop computer, a personal digital assistant, a laptop computer, an IP telephone, a cellular telephone, or an interactive media server.

20. The router of claim 17 resident in and operable on a telephony switch.

21. The router of claim 17 embedded in an interactive voice response system.

22. The router of claim 17, wherein the metadata is extensible markup language-based trust interaction markup language and the stored data is communication history data and contact parameters.

23. The router of claim 17, wherein metadata data is sent by attaching the metadata to a communications event for sending and wherein metadata is received by stripping it from an incoming communications event.

24. The router of claim 17, wherein data is sent over a communications link to another router, the communication link established by the sending router, and wherein data is received over a communications link established by a sending router, the data received at a receiving router.

25. The router of claim 17 further comprising:

a graphic user interface for registering the router on a network and for configuring the router functions including a portion thereof for providing system recommendations about trust plausibility associated with received events and for providing system recommendations of trust related to contacts available in a network directory.

26. The router of claim 17, wherein the metadata is trust interaction markup language extensible from social group description language, the trust interaction markup language transported using simple object access protocol over transfer control protocol/ Internet protocol, user data gram protocol, news network transfer protocol, or computer telephony integration protocols.

27. The router of claim 17, wherein the trust interaction markup language is an extension of contact center extensible markup language.

28. A method for routing a communication event or notification thereof based on an implied level of trust using a trust-based router at a receiving platform including steps for;

(a) pre-configuring the router to trust at least one contact and at least one user that the contact trusts;

(b) receiving a communication event or notification thereof at the receiving platform;

(c) notifying the router of the received communication event or notification thereof;

(d) launching the router, the router accessing local data and receiving any data attached to the communication event or sent directly thereto from a sending router;

(e) comparing the data sets and discovering some indication of a trust relationship between the sender and receiver of the communications event or notification thereof;

(f) preparing a routing instruction for handling the communications event or notification thereof according to the trust relationship discovered; and

(g) causing execution of the routing instruction according to the trust relationship discovered.

29. The method of claim 28 wherein in step (a), the identity of the at least one user is not known to the host platform of the router configured for trust.

30. The method of claim 28 wherein in step (b), the communication event is one of an email, a voice mail, a telephone call notification, a video call notification, an instant message, a page, an Internet protocol telephony call notification, a file transfer request, or an invitation message to engage in a communication sequence.

31. The method of claim 28 wherein in step (b), the receiving platform is one of a computer station, a telephone system, a cellular telephone, a personal digital assistant, a pager, a voice over Internet protocol phone, an Internet protocol telephone, or a video teleconferencing system.

32. The method of claim 28 wherein in step (d), the data received is extensible markup language-base trust interaction markup language.

33. The method of claim 28 wherein in step (d), the data accessed is interaction history and contact identity information, including trust metrics, if any set for those identities.

34. The method of claim 28 wherein in step (e), the trust relationship is implied or suggested by the system, but not necessarily approved by the operator of the receiving platform.

35. The method of claim 34 wherein in a step is provided between steps (e) and (f) for enabling the operator to approve or reject a suggested or implied trust relationship.

36. The method of claim 28 wherein in step (f), the routing instruction overrides an existing default instruction in place for routing the event or notification thereof.

37. The method of claim 28 wherein in step (g), the router causes execution of the routing instruction through an application program interface to the default routing system for the communications event type.

38. The method of claim 28 further including a step (h) for dynamically tuning trust metrics relevant to the discovered trust relationship.

39. The method of claim 38 wherein the tuning includes adding the identity of the sender to a trusted contact list for the type of communication of the event or notification thereof.

40. The method of claim 35 wherein the trust relationship discovered relates to one or more contacts included in a network-based directory the discovery communicated to the sender as an advisory before routing an outbound event to the one or more contacts.