RFID with two tier connectivity, RFID in the PLC rack, secure RFID tags and RFID multiplexer system

• US 20070143162A1
• Filed: 11/15/2006
• Published: 06/21/2007
• Est. Priority Date: 11/15/2005
• Status: Abandoned Application

• Current Assignee: ILS Technology LLC
• Original Assignee: ILS Technology LLC
• Inventors: Keever, John, De La Rosa, David, Bertelsen, Nils, Aupperlee, Eric, Wert, James, Wussow, Wendy
• Application Number:
  US11/599,771
• Publication Number:
  US 20070143162A1
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G05B 19/054 Input/output
• CPC Class Codes: G05B 2219/15038 Internet, tcp-ip, web server see under S05B219-40
• CPC Class Codes: G05B 2219/15117 Radio link, wireless
• CPC Class Codes: G05B 2219/25196 Radio link, transponder
• CPC Class Codes: G05B 2219/31205 Remote transmission of measured values from site, local to host
• CPC Class Codes: G06F 8/34 Graphical or visual programming
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders

Abstract

A device by which RFID data can pass from the RFID reader, or from the plant floor PLC and reader, to business applications at the enterprise level. The RFID tag date is easily integrated into a PLC for integration with other equipment. The security of the overall system is maintained by only allowing tag information to be available to authenticated users by means of active or passive tags and the use of certificates and encryption during the data transmission. Multiple RFID reader device drivers can be customized to support any number of readers available in the marketplace, with each RFID reader including its own data structure, protocol and handshaking methodology for communication. Additionally, a set of run time and configuration tools is provided which allow for an easier integration of RFID tag data into the enterprise architecture for use by other business applications.

Claims

1. A system for communicating RFID tag data from an RFID reader to an enterprise level business application, said system comprising:

an RFID reader having one or more RF antennas operably coupled thereto for detecting RFID tag data; and

software installed on the RFID reader, wherein the software can;

(a) process the RFID tag data, (b) decide if the RFID tag data is to be passed to an enterprise level business application and which enterprise level business application it should be passed to, and (c) transmit the RFID tag data directly to the enterprise level business application based on the decision in (b).

2. The system of claim 1, wherein the enterprise level business application comprises a PLC.

3. The system of claim 2, wherein the RFID data is pushed into the PLC memory via a PLC remote communication link.

4. The system of claim 1, wherein said software can decide to print a label (RFID or barcode) and send a signal to an attached printer with the RFID tag data to be printed.

5. The system of claim 1, wherein said software includes local business rules and/or logic installed thereon, and wherein said software processes the RFID tag data according to the local business rules and/or logic.

6. The system of claim 1, wherein the RFID tag data is sent to the enterprise level business application via a protocol selected from the group consisting of but not limited to ODBC, JDBC, CLI, Oracle, DB2, OPC, JMS and MQSeries.

7. The system of claim 1, where said software comprises:

a handler/scanner module receiving the RFID tag data;

a logic flow engine module receiving the RFID tag data from the handler/scanner and executing and applying local business rules and logic to the received RFID tag data; and

a transport server receiving the RFID data from the logic flow engine and transmitting the RFID tag data to the enterprise level business application.

8. The system of claim 7, wherein the logic flow engine decides if the RFID tag data is to be passed to an enterprise level business application and which enterprise level business application it should be passed to, and wherein the logic flow engine reformats the RFID tag data in accordance with its target enterprise level business application.

9. The system of claim 7, wherein the handler/scanner decides if the RFID tag data is to be passed to an enterprise level business application and which enterprise level business application it should be passed to, and wherein the handler/scanner reformats the RFID tag data in accordance with its target enterprise level business application.

10. The system of claim 7, wherein the handler/scanner includes a reader driver receiving RFID tag data from the RFID reader.

11. The system of claim 10, wherein the reader driver polls the RFID reader for RFID tag data.

12. The system of claim 7, wherein said software further comprises a logging server receiving and storing information in a database.

13. The system of claim 7, wherein the RFID reader includes means for providing an indication event of a successful read, wherein the logic flow engine instructs the handler/scanner to activate the indication means upon a successful RFID tag read.

14. The system of claim 13, wherein the indication means is selected from the group consisting of a visual indicator, an audio indicator, a PLC device status change, a screen update and a PLC device variable change.

15. The system of claim 7, wherein the handler/scanner includes a plurality of reader drivers receiving RFID tag data from a plurality of RFID readers.

16. The system of claim 15, wherein each reader driver is connected to one RFID reader and communicates using the protocol of the RFID reader to which it is connected.

17. The system of claim 7, wherein the RFID tag data is encrypted prior to transmission to the RFID reader, and wherein the logic flow engine decrypts the RFID tag data according to a decryption key.

18. The system of claim 17, wherein the RFID tag data includes a set number of bits that identify the tag source, and wherein the logic flow engine determines the appropriate decryption key based on the set number of bits identifying the tag source.

19. The system of claim 18, wherein the logic flow engine selects a decryption key from a key storage table based on the set number of bits identifying the tag source, wherein the key storage table includes a list of vendor ID numbers and corresponding key information for decryption.

20. The system of claim 7, wherein the software includes one or more configuration tools containing a record of all defined projects, transports and general setting, and wherein the software can reset itself to a previous setting using the configuration tools upon recovery from a power failure condition.

21. The system of claim 20, wherein the configuration tools provide information to a user in a tree format, wherein the user can drag and drop data elements or logic elements to create associations and rules between different elements.

22. The system of claim 20, wherein the configuration tools scan for active RFID connections at initialization and present a list of active readers to a user for configuration.

23. The system of claim 20, wherein the configuration tools allow a user to define a set of rules to apply before transmitting the RFID tag data.

24. The system of claim 23, wherein the set of rules includes not to take repeat reads, look for a range of acceptable information before reporting, and define a trigger to turn a reader on.

25. A system for communicating RFID tag data from an RFID reader to either an enterprise level business application or a PLC, said system comprising:

an RFID reader having one or more RF antennas operably coupled thereto for detecting RFID tag data;

a PLC in communication with the RFID reader and receiving RFID tag data from the RFID reader; and

software installed on the PLC, wherein the software can;

(a) process the RFID tag data, (b) decide if the RFID tag data is to be passed to an enterprise level business application and which enterprise level business application it should be passed to, (c) decide if the RFID tag data is to be pushed into a memory of the PLC, and (d) either transmit the RFID tag data directly to the enterprise level business application or push the RFID tag data into the PLC memory based on the decision in (b) and (c).

26. The system of claim 25, where the RFID data is pushed into the PLC memory via a PLC backplane API communication link.

27. The system of claim 25, wherein said software can decide to print a label (RFID or barcode) and send a signal to an attached printer with the RFID tag data to be printed.

28. The system of claim 25, wherein said software includes local business rules and/or logic installed thereon, and wherein said software processes the RFID tag data according to the local business rules and/or logic.

29. The system of claim 25, wherein the RFID tag data is sent to the enterprise level business application via a protocol selected from the group consisting of ODBC, JDBC, CLI, Oracle, DB2, OPC, JMS and MQSeries.

30. The system of claim 25, where said software comprises:

a handler/scanner module receiving the RFID tag data;

a logic flow engine module receiving the RFID tag data from the handler/scanner and executing and applying local business rules and logic to the received RFID tag data; and

a transport server receiving the RFID data from the logic flow engine and transmitting the RFID tag data to the enterprise level business application,

wherein the handler/scanner includes a PLC driver for sending the RFID tag data to the memory of the PLC.

31. The system of claim 30, wherein the PLC driver sends RFID tag data to the PLC memory via a PLC backplane communication link.

32. The system of claim 30, wherein the logic flow engine decides:

(a) if the RFID tag data is to be passed to an enterprise level business application and which enterprise level business application it should be passed to, and (b) if the RFID tag data is to be passed to the memory of the PLC.

33. The system of claim 32, wherein if the data is to be sent to an enterprise level business application the logic flow engine reformats the RFID tag data in accordance with its target enterprise level business application.

34. The system of claim 30, wherein the handler/scanner decides:

(a) if the RFID tag data is to be passed to an enterprise level business application and which enterprise level business application it should be passed to, and (b) if the RFID tag data is to be passed to the memory of the PLC.

35. The system of claim 34, wherein if the data is to be sent to an enterprise level business application the handler/scanner reformats the RFID tag data in accordance with its target enterprise level business application.

36. The system of claim 30, wherein the handler/scanner includes a reader driver receiving RFID tag data from the RFID reader.

37. The system of claim 30, wherein the reader driver polls the RFID reader for RFID tag data.

38. The system of claim 30, wherein said software further comprises a logging server receiving and storing information in a database.

39. The system of claim 30, wherein the RFID reader includes means for providing an indication event of a successful read, wherein the logic flow engine instructs the handler/scanner to activate the indication means upon a successful RFID tag read.

40. The system of claim 39, wherein the indication means is selected from the group consisting of a visual indicator, an audio indicator, a PLC device status change, a screen update and a PLC device variable change.

41. The system of claim 30, wherein the handler/scanner includes a plurality of reader drivers receiving RFID tag data from a plurality of RFID readers.

42. The system of claim 41, wherein each reader driver is connected to one RFID reader and communicates using the protocol of the RFID reader to which it is connected.

43. The system of claim 30, wherein the RFID tag data is encrypted prior to transmission to the RFID reader, and wherein the logic flow engine decrypts the RFID tag data according to a decryption key.

44. The system of claim 43, wherein the RFID tag data includes a set number of bits that identify the tag source, and wherein the logic flow engine determines the appropriate decryption key based on the set number of bits identifying the tag source.

45. The system of claim 44, wherein the logic flow engine selects a decryption key from a key storage table based on the set number of bits identifying the tag source, wherein the key storage table includes a list of vendor ID numbers and corresponding key information for decryption.

46. The system of claim 30, wherein the software includes one or more configuration tools containing a record of all defined projects, transports and general setting, and wherein the software can reset itself to a previous setting using the configuration tools upon recovery from a power failure condition.

47. The system of claim 46, wherein the configuration tools provide information to a user in a tree format, wherein the user can drag and drop data elements or logic elements to create associations and rules between different elements.

48. The system of claim 46, wherein the configuration tools scan for active RFID connections at initialization and present a list of active readers to a user for configuration.

49. The system of claim 46, wherein the configuration tools allow a user to define a set of rules to apply before transmitting the RFID tag data.

50. The system of claim 49, wherein the set of rules includes not to take repeat reads, look for a range of acceptable information before reporting, and define a trigger to turn a reader on.

51. A system for communicating RFID tag data from an RFID reader to an enterprise level business application, said system comprising:

an RFID reader having one or more RF antennas operably coupled thereto for detecting RFID tag data;

an edge controller in communication with the RFID reader and receiving RFID tag data from the RFID reader; and

software installed on the edge controller, wherein the software can;

(a) process the RFID tag data, (b) decide if the RFID tag data is to be passed to an enterprise level business application and which enterprise level business application it should be passed to, and (c) transmit the RFID tag data directly to the enterprise level business application based on the decision in (b).

52. The system of claim 51, wherein the enterprise level business application comprises a PLC.

53. The system of claim 52, wherein the RFID data is pushed into the PLC memory via a PLC remote communication link.

54. The system of claim 51, wherein said software can decide to print a label (RFID or barcode) and send a signal to an attached printer with the RFID tag data to be printed.

55. The system of claim 51, wherein said software includes local business rules and/or logic installed thereon, and wherein said software processes the RFID tag data according to the local business rules and/or logic.

56. The system of claim 51, wherein the RFID tag data is sent to the enterprise level business application via a protocol selected from the group consisting of ODBC, JDBC, CLI, Oracle, DB2, OPC, JMS and MQSeries.

57. The system of claim 51, where said software comprises:

a handler/scanner module receiving the RFID tag data;

a logic flow engine module receiving the RFID tag data from the handler/scanner and executing and applying local business rules and logic to the received RFID tag data; and

a transport server receiving the RFID data from the logic flow engine and transmitting the RFID tag data to the enterprise level business application.

58. The system of claim 57, wherein the logic flow engine decides if the RFID tag data is to be passed to an enterprise level business application and which enterprise level business application it should be passed to, and wherein the logic flow engine reformats the RFID tag data in accordance with its target enterprise level business application.

59. The system of claim 57, wherein the handler/scanner decides if the RFID tag data is to be passed to an enterprise level business application and which enterprise level business application it should be passed to, and wherein the handler/scanner reformats the RFID tag data in accordance with its target enterprise level business application.

60. The system of claim 51, wherein the handler/scanner includes a reader driver receiving RFID tag data from the RFID reader.

61. The system of claim 60, wherein the reader driver polls the RFID reader for RFID tag data.

62. The system of claim 51, wherein said software further comprises a logging server receiving and storing information in a database.

63. The system of claim 51, wherein the RFID reader includes means for providing an indication event of a successful read, wherein the logic flow engine instructs the handler/scanner to activate the indication means upon a successful RFID tag read.

64. The system of claim 63, wherein the indication means is selected from the group consisting of a visual indicator, an audio indicator, a PLC device status change, a screen update and a PLC device variable change.

65. The system of claim 51, wherein the handler/scanner includes a plurality of reader drivers receiving RFID tag data from a plurality of RFID readers.

66. The system of claim 65, wherein each reader driver is connected to one or more RFID reader(s) and communicates using the protocol of the RFID reader to which it is connected.

67. The system of claim 51, wherein the RFID tag data is encrypted prior to transmission to the RFID reader, and wherein the logic flow engine decrypts the RFID tag data according to a decryption key.

68. The system of claim 67, wherein the RFID tag data includes a set number of bits that identify the tag source, and wherein the logic flow engine determines the appropriate decryption key based on the set number of bits identifying the tag source.

69. The system of claim 68, wherein the logic flow engine selects a decryption key from a key storage table based on the set number of bits identifying the tag source, wherein the key storage table includes a list of vendor ID numbers and corresponding key information for decryption.

70. The system of claim 51, wherein the software includes one or more configuration tools containing a record of all defined projects, transports and general setting, and wherein the software can reset itself to a previous setting using the configuration tools upon recovery from a power failure condition.

71. The system of claim 70, wherein the configuration tools provide information to a user in a tree format, wherein the user can drag and drop data elements or logic elements to create associations and rules between different elements.

72. The system of claim 70, wherein the configuration tools scan for active RFID connections at initialization and present a list of active readers to a user for configuration.

73. The system of claim 70, wherein the configuration tools allow a user to define a set of rules to apply before transmitting the RFID tag data.

74. The system of claim 73, wherein the set of rules includes not to take repeat reads, look for a range of acceptable information before reporting, and define a trigger to turn a reader on.