LIT Middleware: Design and Implementation of RFID Middleware based on the EPC Network Architecture

Transcription

1 LIT Middleware: Design and Implementation of RFID Middleware based on the EPC Network Architecture Ashad Kabir, Bonghee Hong, Wooseok Ryu, Sungwoo Ahn Dept. of Computer Engineering Pusan National University, Republic of Korea

2 Introduction RFID Middleware needed for Track & Trace item automatically throughout the supply chain. Safe & Secure supply chain. Fast & Accurate data collection. Business process automation. Application Domains Supply Chain Management (SCM) in transportation e-government e-health Waste management Documents identification & tracking 2

3 Introduction RFID Middleware Process real time event data Data filtering and aggregation ERP Manufacture Process Management Reader Coordination CRM SCM Distribution center Data routing and integration WMS Retail Environments Tags Readers RFID Middleware Enterprise Applications 3

4 Requirements of RFID Middleware Data Management Data Filtering Redundant data removing Sending data to right destination Extensibility Support new RFID Readers Support new event data Support global standard High Performance Application Integration Need to process enormous event data Have to serve a lot of applications RFID Middleware Device Management Dynamic configuration Monitor and control Reader Deployment Support heterogeneous applications Support standard and widely used technology such as JMS, XML, and SOAP Reliable connectivity 4

5 Standard for RFID Middleware EPCglobal Standard Joint venture between EAN international and UCC Inc. Developed by Auto-ID center Objectives Achieving worldwide adoption and standardization of EPC technology Suggests EPC network architecture for RFID technology Standard for RFID Middleware Roles and Interfaces Standard Data format Benefits True visibility of items in supply chain More accurate and immediate information 5

6 Standard for RFID Middleware Overview of EPC Network Architecture * Enterprise Apps Local ONS Partner Apps EPCIS Query Interface EPCIS Repository EPCIS Capture Interface EPCIS Capturing Apps ALE Interface SW / HW Role Standard Interface Filtering & Collection (ALE) Reader Protocol READER READER READER READER RFID Tag * EPCglobal Architecture Framework, EPCglobal Inc. 6

7 Standard for RFID Middleware Roles of Application Level Events (ALE) Receiving EPCs from one or more data sources Accumulating, filtering and grouping EPCs Reporting in various forms Roles of EPC Information Services (EPCIS) Store biz events Respond queries from various clients Provides a uniform programmatic interface to various clients 7

8 Overview of LIT Middleware Objectives of LIT Middleware To provide highest level of extensibility To provide fast & accurate data collection To support heterogeneous applications To support diverse logistics devices Layered Architecture Physical Layer RFID tag & Reader Logical Layer ALE Manager Business Layer Standard reader interface and reader integration module Smoothing filter & Continuous Query Processor EPCIS Manager Data Source Access Component Continuous query processor Track & Trace query module 8

9 Overview of LIT Middleware Top level Architecture of LIT Middleware Enterprise Applications Business Layer EPCIS Manager Business Event Time 3:14pm 1/1/2005 epc: bizlocation = Dist. Center #2 inbound bizstep = Receiving Business Rules Logical Layer ALE Manager Logical Event LogicalReader = DockDoor#1 epc: Addition Physical Layer READER READER READER READER Physical Event epc: epc: epc: RFID Tag 9

10 Design concepts of LIT Middleware Features from Requirements Analyzed Requirements of Middleware Analyzed EPCglobal Standard Deduced Features of Middleware Requirements High Performance Scalability Application Abstraction Reader Abstraction Extensibility Features Continuous Query Process Duplicate Data Removal Technique Track & Trace query module State-based execution Standard Application Interface Commercial legacy DB support Common Reader Management Interface Logical Reader mapping module Integration of new Readers New Event adaptation 10

11 Features of ALE Manager High performance Continuous Query Process RFID data are gathered continuously by many readers EPCglobal mentions standard specification (ECSpec( ECSpec) ) for filtering and collecting data during fixed time interval Query Index representing query using spatial data structure 5 3 Query insert Query evaluation 2 Register Continuous Query CQ Manager results Register ECSpec ECReport Query Index 4 Reader Interface Data Insert User Application Reader 11

12 Features of ALE Manager High performance Duplicate data removal technique Time duration of each query called event cycle. During event cycle reader may read same tag many times User/App. User/App. Duplicate Data Remove duplicate data Remove duplicate data Duplicate Data Continuous Query Processor T2 Remove duplicate data Duplicate Data RFID Readers T1 T2 T2 T1 T3 T3 12

13 Features of ALE Manager Scalability Thread-based execution VS. State-based execution * Thread-based execution model incurs significant overhead due to Cache misses Lock contention Switching State-based execution model Single scheduler Avoids the limitation of thread-based model Applications Applications Applications Applications ALE Manager ALE Manager Query Processor Thread-I Query Processor Thread-II Query Processor Thread-III... Query Scheduler Processor State RFID Readers RFID Readers RFID Readers RFID Readers * Operator Scheduling in a Data Stream Manager.. 29 th VLDB Conference, Berlin, Germany, pp

14 Features of ALE Manager Application Abstraction Provides independence from different types of applications EPCglobal proposed extensible application interface API for Management API for Reader Management API for Middleware Management API for Query Define, Undefine,, Subscribe, Unsubscribe Immediate, Poll Common Application Query & Response (by EPCglobal) ECSpec, ECReports 14

15 Features of ALE Manager Reader Abstraction Common Reader Management Interface Manage heterogeneous RFID Reader Using EPCglobal Reader Protocol standard Logical Reader Mapping Independent from Number of RFID Readers Arrangement of RFID Readers Warehouse_a DockDoor_a DockDoor_b 15

16 Features of ALE Manager Reader Extensibility To support different types of RFID Readers from various vendors UNIX Device Driver, Jini architecture Adaptor look-up table Adaptor Applications Applications Adaptor C look-up table Adaptor A Adaptor B Filtering & Collection Adaptor C Adapter Manager Adaptor A Adaptor A Adaptor B Physical Reader Manager Reader A Reader A Reader B Reader C 16

17 Features of EPCIS Manager High performance and scalability Efficient Subscribe operation (using CQ Index technique) Reduce processing time Only first time access repository Transaction Event : Object Event : Aggregation Event : Method Call : Query Results : subscribe Working scheduler Logger Transaction Event Repository Aggregation Event Repository Object Event Repository CQIndex & Buffer Event Data Component Capture Interface 17

18 Features of EPCIS Manager High performance Spatial index query for track & trace RFID tag object Example of query Where is the product #1? (present query) Which products left warehouse B two hours ago? (past query) Extended query interface Fixed Interval R-treeR * Extended EPCIS Query Interface Tracking & Tracing Query Interface Index Track & Trace Component * Design and Implementation of an Index Structure Using Fixed Intervals for Tracing of RFID Tags.. ICCSA, LNCS 3981, pp

19 Features of EPCIS Manager Application Abstraction Independent from types of applications Persistent & compatible to store different types of EPCIS event. Standard Query Interface (proposed by EPCglobal) Standard data format XML Standard communication protocols : Query/Capture Service HTTP TCP Web Service (wsdl( wsdl) Warehouse Management System Enterprise Information Systems Other Legacy Systems Trading Partners... Standard Query Interface EPCIS Repository Capture Interface 19

20 Features of EPCIS Manager Application Abstraction To support commercial legacy DB (Oracle, MSSQL ), XML DB and File system We designed Data Source Access Component Service Provider Event Data Component Track & Trace Component Master Data Component Data Provider Data Source Schema Access Module Data Source Access Interface (Open API) Query Language Convert Module Query Result Access Module Repository Manager Data Source MetaData Repository JDBC Embedded SQL Driver XPATH Driver Local API Driver ( App.conf, Web.conf ) ORACLE Or MSSQL Or Sybase XML DB File System 20

21 Features of EPCIS Manager Extensibility To support new EPCIS Event Ex: Sensor Event, e-seal e Event etc. XSD, WSDL file extension. Repository Management Module Schema registry of each event data Data Source Access Component Repository Manager Schema Registry (xsd) Object Event Schema Tran. Event Schema Event Data Repository (Data Source) Agg. Event Schema e-seal Event Schema Object Event Transaction Event Aggregation Event e-seal Event Sensor Event Sensor Event Schema ( App.conf, Web.conf ) 21

22 Software Architecture of ALE Manager Application Abstraction Layer State-based Execution Layer Continuous Query Layer Reader Abstraction Layer 22

23 Software Architecture of ALE Manager Reader Abstraction Layer Support different types of Readers from various vendors Can integrate new Readers at runtime State-based based execution and Continuous Query Layer Control and manage ALE CQ processor is implemented using query index To support query defined by application Query manager stores and manages query information Reader manager keeps information of logical and physical reader mapping Smoothing filter is used to remove duplicate data Application Abstraction Layer Provides RFID data access by Standard Interface Used standard protocol TCP, HTTP, FTP, WSDL. Support standard format (XML) 23

24 Software Architecture of EPCIS Manager Controller Model Controller QueryService Layer Repository Layer Query Processing Layer Data Access Layer DataBase Layer CaptureService Layer Abstraction Detailed Architecture WS Wrapper SessionBean JNDI JNDI SessionBean Main Memory Index Entity Bean JDBC File System Message driven Bean JMS Implementation Technique 24

25 Software Architecture of EPCIS Manager Capture Service Layer Provides standard interface To capture events from EPCIS capturing application Support standard format (XML) Repository Layer Continuous Query processor for efficient subscribe operation Implemented using query index Implemented Fixed Interval R-tree R for Track & Trace query Implemented Data Source Access component To support File system, Legacy DB and XML DB. Query Service Layer Control and manage query processing Provides Standard query interface Used standard protocol HTTP, WSDL 25

26 Implementation Environment CPU: Pentium IV 2.66 GHz. RAM: 1 GB. OS: Windows XP Pro. SP2 Language: JAVA (JDK 5.0). Web server: SUN Application server. RFID Reader, Antenna and Tag: Alien, Intermec, Kiscomm,, KPC, LIT, Thingmagic. 26

27 Implementation Implemented software RFID middleware RFID Reader Management Tool Manages physical RFID readers Manages logical readers GUI for ALE Manager Client Common Application Interface 27

28 Implementation Implemented software RFID Middleware Monitor Monitor RFID tag data Monitor RFID middleware interface call RFID Readers Smoot hing Filt er DROP Pattern Fil t e r DROP Application 28

29 Implementation Implemented Software GUI for EPCIS Manager Client 29

30 Conclusion & Future work Conclusion Studied EPCglobal Network Architecture. Analyzed requirements of RFID Middleware Design Middleware based on EPCglobal standard Layered Architecture Provides important features such as High performance, Scalability, Abstraction and Extensibility Implement Middleware with features User friendly GUI Real time monitoring Future work Requirements analysis and implementation of Middleware to support RFID, RTLS (Real Time Locating System) and Sensor data 30

31 Thanks for your attention Questions? Ashad Kabir 31