Method of building a data integration environment

• US 8,311,972 B2
• Filed: 10/31/2007
• Issued: 11/13/2012
• Est. Priority Date: 11/02/2006
• Status: Active Grant

• Current Assignee: BAE Systems Plc
• Original Assignee: BAE Systems Plc
• Inventors: Barker, Sean Michael
• Primary Examiner(s): Vincent, David
• Assistant Examiner(s): Traktovenko, Ilya
• Application Number:
  US12/447,980
• Publication Number:
  US 20100070450A1
• Time in Patent Office: 1,840 Days
• Field of Search: 706/55, 706/47, 706/62
• US Class Current: 706/55
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

A method of building a data integration environment is provided. According to one embodiment of the invention as applied to a computer network, the method comprising: identifying the data integration environment and the policies that apply to it 200, negotiating with the environment 202, and generating a new interface rule set enabling information to be passed in dependence thereon between the system which is made part of the integration environment and the integration environment. The method can be usefully applied in UAV networks, robot networks as well as in networks of fixed sensors. The invention finds utility in various important applications such as in network-enabled capability and in rapid integration of systems.

Claims

1. In a collection of enterprises which uses a data communication systems network comprising a plurality of disparate data communication systems, a method of building a data integration environment, the method comprising the steps of:

(a) establishing a predetermined set of rules about data based upon a data framework, a set of hierarchical classification (or ontology) rules and attribute rules for each disparate data communication system of the network;

(b) replicating at least one set of rules representative of one of the systems and transferring said replicated set of rules to one or more other said systems of the network;

(c) negotiating, based on processing capabilities of the systems to and from which the at least one set of rules were replicated, a common rules set between the integration environment and the systems, by merging the rules about the data associated with the systems;

(d) loading the merged rules into the integration environment rule base and selectively populating the datastore implementing the data integration environment with rules data from each of the systems; and

(e) effecting data exchange between each of said systems and the integration environment in accordance with the newly-established rule set so as to allow the disparate systems to interoperate with each other.

2. A method of building a data integration environment as claimed in claim 1, including a step of linking the attribute rules to the hierarchical classification rules in such a way as to permit the set of rules to be used to define the meaning of attributes, the form of attributes and/or the use of attributes.

3. A method of building a data integration environment as claimed in claim 2, wherein the hierarchical classification rules are used by means of their hierarchical structure to define the meaning of attribute rules particular to one or more of said systems, which attribute rules describe attribute types, attribute values and/or a combination of attribute types and attribute values.

4. A method of building a data integration environment as claimed in claim 3, wherein the hierarchical classification rules are used by means of their hierarchical structure to define the meaning of behaviour rules particular to one or more of said systems, which behaviour rules are used with the attribute types, the attribute values and/or a combination of the attribute types and the attribute values.

5. A method of building a data integration environment as claimed in claim 1, wherein the hierarchical classification rules are used by means of their hierarchical structure to define the meaning of attribute rules particular to one or more of said systems, which attribute rules describe attribute types, attribute values and/or a combination of attribute types and attribute values.

6. A method of building a data integration environment as claimed in claim 5, wherein the hierarchical classification rules are used by means of their hierarchical structure to define the meaning of behaviour rules particular to one or more of said systems, which behaviour rules are used with the attribute types, the attribute values and/or a combination of the attribute types and the attribute values.

7. A computer program comprising program code means stored on a non-transitory computer readable medium for performing the method steps of claim 1 when the program is run on a computer.

8. A computer program product comprising program code means stored on a non-transitory computer readable medium for performing the method steps of claim 1 when the program is run on a computer.

9. A method as claimed in claim 1 applied in a UAV network.

10. A method as claimed in claim 1 applied in a robot network.

11. A method as claimed in claim 1 applied in a network of fixed sensors.

12. A method of building an agile data model comprising the steps of:

(a) establishing a framework data model representation of a set of states, each one of the states being associated with a concept variable describing the model;

(b) establishing a set of states corresponding to attributes and attribute roles which are applicable to the model;

(c) defining a hierarchical classification of states corresponding to the concept variables of (a), the attributes and the attribute roles; and

(d) constructing said data model based upon the established set of states of aforesaid steps (a), (b) and (c), and by creating therefrom a set of rules which associate particular attributes to particular framework concepts in particular attribute roles.