DATA SYNCHRONIZATION AND INTEGRITY FOR INTERMITTENTLY CONNECTED SENSORS

• US 20070290803A1
• Filed: 05/30/2007
• Published: 12/20/2007
• Est. Priority Date: 06/09/2006
• Status: Active Grant

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: Matsen, Marc R., Ung, Kevin Y., Ayyagari, Arun, Johnson, Karl L., Blackwell, David B., Coop, William P.
• Granted Patent: US 8,723,645 B2
• Time in Patent Office: Days
• US Class Current: 340/10.1
• CPC Class Codes: G06K 7/0008 General problems related to the reading of electronic memory record carriers, independent of its reading method, e.g. power transfer
• CPC Class Codes: G06K 7/10356 using a plurality of antennas, e.g. configurations including means to resolve interference between the plurality of antennas
• CPC Class Codes: G06Q 10/00 Administration; Management

Abstract

A system for data synchronization of intermittently connected sensors may include an RFID system and an information management system. The system may also include an application to insure integrity of data retrieved or posted between the RFID system and the information management system.

Claims

1. A system for data synchronization of intermittently connected sensors, comprising:

an RFID system;

an information management system; and

an application to insure integrity of data retrieved or posted between the RFID system and the information management system.

2. The system of claim 1, wherein the RFID system comprises:

at least one RFID tag; and

a data schema associated with the at least one RFID tag, wherein the data schema is adapted to minimize an amount of data to be read from the RFID tag in response to a particular query.

3. The system of claim 1, further comprising:

an RFID reader; and

an event manager to manage interactions between the RFID reader and the information management system.

4. The system of claim 3, further comprising a data store-forward capability associated with at least one of the RFID reader and the event manger to ensure continued operation when the RFID system is disconnected from the information management system and to ensure there is no data loss during a disconnect period.

5. The system of claim 3, wherein the RFID reader comprises a context and event manager functionality to ensure contextual RFID tag read and write operation.

6. The system of claim 1, further comprising a data locking and synchronization mechanism between the information management system and the RFID system.

7. The system of claim 1, further comprising:

a plurality of RFID tags; and

a cryptographic hash on each RFID tag for writing data to ensure data validation for data read from the tag and that is stored on the information management system.

8. The system of claim 1, further comprising an integration broker to interface between the information management system and a front-end application.

9. The system of claim 1, further comprising a module for data synchronization and integrity between an RFID tag and the RFID system, wherein the module is adapted to perform a group of operations comprising:

establish a context for interactions with an event manager, RFID reader, and RFID tag;

perform RFID tag reads per the context and any predetermined specifications;

enable asynchronous operation when disconnected from the RFID system by providing a local store and data collection functions;

provide coordination with the RFID system to write lock appropriate information records that will potentially be updated;

support synchronization of information between RFID tags and the RFID system

enable filtering and eventing based on information retrieved from RFID tags per the context to minimize transactions;

validate integrity of information retrieved from the RFID tags based on the context and prior history record available from the local store; and

validate RFID tag write commands initiated locally or from the RFID system, perform the RFID tag write, and synchronize update status with the RFID system.

10. The system of claim 1, further comprising a module to perform a group of operations comprising:

establish a context for interactions with an event manager;

accept any queries from any applications via an integration broker and issue an appropriate request or requests to the event manager;

accept and respond to any queries from any applications via the integration broker with current information available at an RFID database or information retrieved from the event manager;

support a write lock functionality for appropriate information records per a request from the event manager or the applications;

support synchronization of information between an RFID tag and/or RFID reader or event manager local store and the RFID database;

validate integrity of information retrieved from the event manager based on the context and a prior history record available from the RFID database;

provide a service broker to asynchronously or synchronously access the information; and

provide query and capture interfaces to subscribers and applications in an asynchronous or synchronous manner.

11. The system of claim 1, further comprising validation means to validate data to and from an RFID tag.

12. The system of claim 11, wherein the validation means comprises a keyed cryptographic hash.

13. A method for data synchronization of intermittently connected sensors, comprising:

providing a data schema to minimize an amount of data to be read from an RFID tag; and

maintaining context and event manager functionality on an RFID reader to facilitate contextual RFID tag read/write operation.

14. The method of claim 13, further comprising providing a data store-forward capability within the RFID reader and an event manager for continued operation when disconnected from an information management system and to prevent loss of data during a disconnection.

15. The method of claim 13, further comprising providing a data locking mechanism and a synchronization mechanism between a front-end application and a data management system for proper operation of backend applications and decision support systems.

16. The method of claim 13, further comprising maintaining a cryptographic hash on the RFID tag for write operations to ensure data validation for data read from the RFID tag and stored on an information management system.

17. The method of claim 13, further comprising:

establishing a context for interactions with an event manager, RFID reader, and RFID tag;

performing RFID tag reads per the context and any predetermined specifications;

enabling asynchronous operation when disconnected with an RFID system by providing a local store and data collection function;

providing coordination with the RFID system to write lock appropriate information records that will potentially be updated;

supporting synchronization of information between the RFID tag and the RFID system;

enabling filtering and eventing based on information retrieved from the RFID tag per the context to minimize transactions;

validating integrity of information retrieved from the RFID tag based on context and a prior history record available from the local store; and

validating RFID tag write commands initiated locally or from the RFID system, perform the RFID tag write, and synchronize update status with the RFID system.

18. The method of claim 13, further comprising:

establishing a context for interactions with an event manager;

accepting queries from applications via an integration broker and issuing an appropriate request or requests to the event manager;

accepting and responding to queries from the applications via the integration broker with current information available at an RFID database or information retrieved from the event manager;

supporting write lock functionality for appropriate information records per request from the event manager or the applications;

supporting synchronization of information between an RFID tag and an RFID reader or event manager local store and an RFID database;

validating integrity of information retrieved from the event manager based on the context and a prior history record available from the RFID database;

providing service broker functionality to asynchronously or synchronously access information; and

providing query and capture interfaces to subscribers and applications in an asynchronous or synchronous manner.

19. The method of claim 13, further comprising validating data to and from the RFID tag.

20. The method of claim 19, further wherein validating data to and from the RFID tag comprises using a keyed cryptographic hash.

21. A system for maintaining an aircraft, comprising:

an RFID system for reading and writing information on an RFID tag associated with a component of the aircraft;

an information management system; and

an application to insure integrity of data retrieved or posted between the RFID system and the information management system.

22. The system of claim 21, further comprising a data schema associated with an RFID tag adapted to minimize an amount of data to be read from the RFID tag in response to a particular query.

23. The system of claim 21, further comprising:

an RFID reader; and

an event manager to manage interactions between the RFID reader and the information management system.

24. The system of claim 23, further comprising a data store-forward capability associated with at least one of the RFID reader and the event manger to ensure continued operation when the RFID system is disconnected from the information management system and to ensure there is no data loss during a disconnect period.

25. The system of claim 23, further comprising a context and event manager functionality on the RFID reader to ensure contextual RFID tag read and write operation.

26. The system of claim 21, further comprising:

a data locking mechanism between a front-end application and the information management system; and

a synchronization mechanism between the front-end application and the information management system, wherein the data locking mechanism and the synchronization mechanism ensure proper operation of any backend applications and decision support systems.

27. The system of claim 21, further comprising a cryptographic hash on the RFID tag for data validation.

28. A method for maintaining an aircraft, comprising:

associating an RFID tag with an aircraft component; and

providing security for data on the RFID tag.

29. The method of claim 28, wherein providing security for data on the RFID tag comprises providing a cryptographic hash for data validation.

30. The method of claim 28, further comprising providing a data schema to minimize an amount of data to be read from the RFID tag.

31. The method of claim 28, further comprising maintaining context and event manager functionality on an RFID reader to facilitate contextual RFID tag read/write operation.

32. The method of claim 28, further comprising providing a data store-forward capability within an RFID reader and an event manager for continued operation when disconnected from an information management system and to prevent loss of data during a disconnection.

33. The method of claim 28, further comprising providing a data locking mechanism between a front-end application and a data management system.

34. The method of claim 28, further comprising providing a synchronization mechanism for proper operation of any backend applications and decision support systems.

35. A method for maintaining an aircraft, comprising:

associating an RFID tag with an aircraft component;

ensuring validity of any data read from the RFID tag;

ensuring integrity of any data retrieved or posted between an RFID system and an information management system;

storing any data when the RFID system does not have access to the information management system; and

updating the information management system when the RFID system regains access to the information management system.

36. The method of claim 35, further comprising write locking at least some information associated with the aircraft component.

37. The method of claim 35, minimizing transactions by filtering and eventing based on information retrieved from the RFID tag and a context for interaction between components.

38. The method of claim 35, further comprising providing access to information associated with the aircraft component through an integrated broken mechanism.

39. The method of claim 35, further comprising synchronizing information between different components of a system for maintaining the aircraft.