Federated system and methods and mechanisms of implementing and using such a system

• US 7,702,636 B1
• Filed: 07/31/2003
• Issued: 04/20/2010
• Est. Priority Date: 07/31/2002
• Status: Active Grant

• Current Assignee: Cadence Design Systems Incorporated (Cadence Group)
• Original Assignee: Cadence Design Systems Incorporated (Cadence Group)
• Inventors: Sholtis, Steven, Henderson, Kenneth Jerome, LeClair, Terry
• Primary Examiner(s): Fleurantin; Jean B
• Assistant Examiner(s): Ly; Anh
• Application Number:
  US10/633,338
• Time in Patent Office: 2,455 Days
• Field of Search: 707 1- 2, 707/10, 707100-102, 707/104.1
• US Class Current: 1/1
• CPC Class Codes: G06F 16/256 in federated or virtual databases

Abstract

A federated system and methods and mechanisms of implementing and using such a system is disclosed. In some embodiments, one or more mappings are created between a taxonomy view at a node and one or more taxonomies of one or more data sources. The one or more data sources can then be accessed via the taxonomy view. In other embodiments, one or more mappings are created between content from different data sources and content from those data sources are merged using the one or more mappings.

Claims

1. A federated system comprising:

a plurality of data sources configured across a distributed network, each data source being associated with a taxonomy; and

one or more nodes comprising at least one data server that hosts an organization'"'"'s data and user information, at least one of the one or more nodes comprising a taxonomy view, one or more of the plurality of data sources being defined on the at least one node, the at least one node further comprising one or more mappings between the taxonomy view of the at least one node and the taxonomy of at least one data source of the plurality of data sources defined on the at least one node, the at least one node being connectable to one or more clients, wherein the taxonomy view of the at least one node allows the at least one of the data source defined on the at least one node to be integrated into a standardized schema such that the one or more of the plurality of data sources is accessed via the taxonomy view of the at least one of the one or more nodes without requiring knowledge of each data source'"'"'s schema;

wherein the at least one node further comprises at least one other taxonomy view.

2. The system of claim 1, wherein the at least one node is connectable to at least one other node.

3. The system of claim 2, wherein the at least one other node is a portal.

4. The system of claim 1, wherein the at least one node is a private data interchange.

5. The system of claim 1, wherein one of the one or more nodes is configured to send replicated data to one or more other nodes.

6. The system of claim 1, wherein one of the one or more nodes is configured to synchronize with one or more other nodes.

7. The system of claim 1, wherein one of the one or more nodes is configured to host content and/or user information.

8. The system of claim 7, wherein the content comprises notifications, updates, security information, and/or links to other sources of content.

9. The system of claim 1, wherein one of the one or more nodes is configured to facilitate communication between a client connected to the node and one or more nodes disconnected from the client.

10. The system of claim 9, wherein the node facilitates communication by transmitting one or more requests for information from the client to the one or more disconnected nodes and conveying one or more responses to the one or more client requests from the one or more disconnected nodes to the client.

11. The system of claim 9, wherein the node facilitates communication by verifying the client has permission to communicate with the one or more disconnected nodes.

12. The system of claim 9, wherein the node facilitates communication by blending content from the one or more disconnected nodes before communicating the content to the client.

13. The system of claim 1, wherein one of the one or more nodes is configured to receive one or more requests from a client connected to the node.

14. The system of claim 13, wherein the one or more requests comprise one or more requests for content changes and/or for additional content.

15. The system of claim 1, wherein one or more applications are accessible through at least one of the one or more clients.

16. The system of claim 15, wherein the one or more applications are stored on the at least one client.

17. The system of claim 15, wherein the one or more applications are updated by the at least one client and/or one or more nodes connectable to the at least one client.

18. The system of claim 15, wherein access to the one or more applications is controlled by one or more nodes connectable to the at least one client.

19. The system of claim 15, wherein the one or more applications are utilized for design, filtering, validation, configuration, optimization, matching, mapping, administration, browsing, selection, procurement, and/or sourcing.

20. The system of claim 1, wherein the at least one node is part of an organization in which at least one other node is a part of.

21. The system of claim 20, wherein the at least one node and the at least one other node are in different divisions of the organization.

22. The system of claim 1, wherein at least one of the one or more data sources defined on the at least one node resides on the at least one node.

23. The system of claim 1, wherein at least one of the plurality of data sources does not reside on a node.

24. The system of claim 1, wherein access to each data source is controlled by one of the one or more nodes.

25. The system of claim 24, wherein access to a data source is controlled by restricting access to content in the data source.

26. The system of claim 25, wherein one or more IDs and/or passwords are used to restrict access to the content in the data source.

27. The system of claim 26, wherein the one or more IDs and/or passwords are stored on the node controlling access to the data source.

28. The system of claim 24, wherein access to a data source is controlled by regulating presentation of content from the data source.

29. The system of claim 28, wherein presentation of content from the data source is regulated by establishing one or more modes of presenting the content from the data source.

30. The system of claim 28, wherein presentation of content from the data source is regulated by dictating whether and to what extent content from the data source is presented.

31. The system of claim 28, wherein one or more filters and/or business rules are used to regulate the presentation of content from the data source.

32. The system of claim 31, wherein the one or more filters and/or business rules are stored on the node controlling access to the data source.

33. The system of claim 24, wherein access to a data source is controlled by altering content from the data source.

34. The system of claim 33, wherein content from the data source is altered by increasing one or more values in the content, decreasing one or more values in the content, and/or replacing one or values in the content with one or more other values.

35. The system of claim 33, wherein alteration of the content from the data source depends upon which client is seeking access to the content.

36. The system of claim 33, wherein one or more business rules are used to alter the content from the data source.

37. The system of claim 36, wherein the one or more business rules are stored on the node controlling access to the data source.

38. The system of claim 24, wherein access to a data source is controlled by managing how content from the data source can be used.

39. The system of claim 38, wherein one or more business rules are used to manage how the content from the data source is used.

40. The system of claim 39, wherein the one or more business rules are stored on the node controlling access to the data source.

41. The system of claim 24, wherein access to each data source is controlled by one or more other nodes.

42. The system of claim 1, wherein at least one other node is configured to control access to at least one of the one or more data sources defined on the at least one node.

43. The system of claim 1, wherein the at least one node is configured to control access to at least one of the one or more data sources defined on the at least one node.

44. The system of claim 1, wherein only a portion of the taxonomy of at least one of the one or more data sources defined on the at least one node is available for mapping.

45. The system of claim 1, wherein only a portion of the taxonomy of at least one of the one or more data sources defined on the at least one node is mapped to the taxonomy view of the at least one node.

46. The system of claim 1, wherein the taxonomy of at least one of the plurality of data sources is different from the taxonomy of at least one other data source.

47. The system of claim 1, wherein each data source comprises content and the content of at least one of the plurality of data sources is different from the content of at least one other data source.

48. The system of claim 1, wherein the taxonomy view of the at least one node is a snapshot of the taxonomy of at least one of the one or more data sources defined on the at least one node.

49. The system of claim 1, wherein a taxonomy is an organizational structure and/or classification scheme.

50. The system of claim 1, wherein a set of application programming interfaces are available to each node and/or each client.

51. The system of claim 50, wherein the at least one node communicates with a client connected to the at least one node and/or accesses at least one of the one or more data source defined on the at least one node via one or more application programming interfaces in the set of application programming interfaces.

52. The system of claim 51, wherein the at least one other taxonomy view is a personal view, a role-based view, a project view, or a company view.

53. The system of claim 1, wherein the at least one other taxonomy view is based on the taxonomy view.

54. A physical storage device containing instructions, the instructions being executable by a computer to cause the computer to perform a method, the method comprising:

mapping between the taxonomy view of at least one node of one or more nodes and a taxonomy of at least one data source of a plurality of data sources, wherein a taxonomy view of the at least one node allows the at least one data source defined on the at least one node to be integrated into a standardized schema such that the at least one data source is accessed via the taxonomy view of the at least one node without requiring knowledge of a schema of the at least one data source, wherein the at least one data source of the plurality of data sources configured across a distributed network is associated with the taxonomy and the at least one data source is defined on the at least one node, the at least one node comprising the taxonomy view;

wherein the at least one node further comprises at least one other taxonomy view.

55. The device of claim 54, further comprising facilitating communication between a client connected to the at least one node and one or more nodes disconnected from the client.

56. The device of claim 54, further comprising accessing one or more applications through at least one client.

57. The device of claim 54, further comprising controlling access to the at least one data source by one of the one or more nodes.

58. The device of claim 54, further comprising mapping a portion of the taxonomy of the at least one data source defined on the at least one node to the taxonomy view of the at least one node.

59. The device of claim 54, wherein the device is a cache or a hard drive.