PDF
HistoryRoadmap
- 1 Implementation Status
- 1.1 Reader Core Proxy (Uses Licensed Fosstrak modules as Codebase)
- 1.2 ALE Server (Uses Licensed Fosstrak modules as Codebase)
- 1.3 Business Event Generator
- 1.4 EPCIS (Uses Licensed Fosstrak modules as Codebase)
- 1.5 Tooling (Eclipse)
- 1.6 Connector
- 1.7 ONS
- 1.8 TDT (Uses Fosstrak Library for EPC TDT)
- 1.9 Applications and Demos
- 2 Tasks
The ASPIRE Middleware RoadMap includes implementation of the following modules:
- Filtering and Collection (F&C) Server implementing core features of the EPC-ALE 1.1 Specification
- Business Event Generation (BEG) Server Translating Reports from F&C to Business Events
- Information Sharing Repository implementing core features of the EPC-IS 1.0.1 Specification
- JMX Applications for End-to-End Management of the ASPIRE Middleware
- Connector applications for Databases and Legacy IT systems (ERPs / WMS)
- Integrated Development Environment for RFID Solution Descriptions and RFID Business Process Management
- Reading API
- Writing API
- Logical Readers API
- Access Control API
- Tag Memory API
- BEG to F&C bindings (HTTP)
- BEG to information sharing repository bindings
- Authentication and Authorization
- Configurable Processing of Reports from F&C (e.g., ALE ECReports)
- Information Sharing Data Model (according to EPC-IS)
- Capture Operations
- Query Operations
- Bindings for Capture Operations
- Bindings for Query Operations
Implementation Status
Note that modules noted in “Red” are not implemented yetReader Core Proxy (Uses Licensed Fosstrak modules as Codebase)
- Implemented as an OSGi bundle that runs within Apache Felix
- Provides JMX management interface
- Provides EPC Reader Management (not currently enabled and used)
- Uses EPC Reader Protocol to communicate with ALE
- Provides Interfaces with readers ( Implemented as an OSGi bundle):
- For Intermec(BRI)
- For FossTrack’s Simulator reader
- For Impinj (Mach1) (no OSGi implementation yet)
- HAL Wrapper for new readers
- FEIG ID ISC.LRU1000 (Ethernet, TPC/IP) (supported by Fosstrak not tested yet, no OSGi implementation yet)
- FEIG ID ISC.MR101-A (RS232/485, COM) (supported by Fosstrak not tested yet, no OSGi implementation yet)
- Standardization for Reader Management (RM) based on JMX
- Authentication/Access mechanisms
ALE Server (Uses Licensed Fosstrak modules as Codebase)
- EPC F&C 1.1 standard compliant (not all Standards Implemented).
- Check if AspireRFID fully supports Tag Memory Specification API (Section 7 of ALE 1.1 specifications)
- ALETM – Main API class (Section 7.1 of ALE1.1 specifications) and implement it if it doesn’t.
- Check if AspireRFID fully supports Tag Memory Specification API (Section 7 of ALE 1.1 specifications)
- Runs on Apache tomcat 6.0
- Provides Standard EPC Control Interface Based on SOAP messages
- Uses CXF and spring to implement JaxWS for the control interface.
- Supports Maven.
- Supports RP and LLRP for the communication with the readers.
- Supports TCP/HTTP protocol to deliver EC reports
- Extension Model for Captured sensor data from semi-passive Tags, active-Tags, Sensor Networks, actuators… (Need to propose the supported model and implement it) sensors input planed to be supported:
- Humidity
- Temperature
- Accelerometer
- GPS coordinates
- Interface for connecting/supporting Sensor Networks (e.g. Zigbee)
- Interface for connecting/supporting Active Tags
- Middleware anti-collision solution implementation for multi-vendor RFID readers
- Partial implementation of the EPC Writing API for supporting Label generation and printing (including 1D and 2D barcodes)
- Integration of TDT to support multiple types of Tags/Barcodes
- Implemented as an OSGi bundle that can be deployed in JOnAS Application Server (not implemented yet)
- Authentication/Access mechanisms
Business Event Generator
- Runs on Apache tomcat 6.0
- Uses CXF and Spring to implement JaxWS for the control interface.
- Provides TCP/HTTP interface to capture the ECReports
- Uses EPCIS Master Data Capture Client using AspireRFID MDC API Based on SOAP messages
- Uses EPCIS Capture Client using the standard EPC Control Interface Based on SOAP messages
- Uses EPCIS Query Client using the standard EPC Control Interface Based on SOAP messages
- Supports Quantity, Aggregation, Transaction and Object Events (needs to be tested)
- Interface for connecting/supporting (this feature can be implemented at the Connector also)
- Actuators
- To give feedback to various devises (e.g. Account machines, delivery Information at the gates/handheld devises …)
- Implemented as an OSGi bundle that can be deployed in JOnAS Application Server (not implemented yet)
- Authentication/Access mechanisms
EPCIS (Uses Licensed Fosstrak modules as Codebase)
- EPC 1.0.1 standard compliant
- Provides Extension Mechanisms
- For every Event the following data are supported from the repository (check Section 6.3 and 9.1 of the EPCIS specifications):
- Provides Extension Mechanisms
| Column Name | Type Name |
|---|---|
| event_id | BIGINT |
| fieldname | VARCHAR |
| prefix | VARCHAR |
| intValue | INT |
| floatValue | FLOAT |
| dateValue | TIMESTAMP |
| strValue | VARCHAR |
- Runs on Apache tomcat 6.0
- Provides standard EPC Query and Capture Interface Based on SOAP messages.
- Provides Query and Capture Interfaces
- Uses CXF and Spring to implement JaxWS for the standard EPC Query and Capture interface.
- Provides AspireRFID’s Master Data Capture Interface Based on SOAP messages.
- Uses CXF and Spring to implement JaxWS for the standard EPC Query and Capture interface.
- Uses SQL for the Query interface and Hibernate for the Capture interface.
- Supports MySQL 5.0 (Can Support more Databases with some modifications)
- Probably a New Field extensions may be required for the existing Event Types extensions in the Data Definition Layer (Useful to store e.g. GPS coordinates, Security check …).
- Implement EPCIS Repo as an OSGi bundle that can be deployed in JOnAS Application Server
- Authentication/Access mechanisms
Tooling (Eclipse)
ASPIRE IDE has been designed as an Eclipse RCP (Rich Client Platform) application that will run over Equinox OSGI server. It uses the command API to define menus, pop-up menu items and toolbars so as to support easily plug-ins and provide more control. Every tool will be an eclipse plug-in/bundle that will be able to be installed or removed as needed.- AspireRfidIDE Core (required for the other plug-ins to run)
- ALE Server Configurator Plug-in
- Business Event Generator Plug-in
- Physical Reader Configuration & Management Plug-in
- EC-Spec Editor Plug-in
- LR-Spec Editor Plug-in
- Master Data Editor Plug-in
- Business Process Management and Workflow Editor Plug-in
- Possible candidates to use as codebase:
- Eclipse JWT Workflow Editor
- OW2 Bonita
- OW2 Enhydra JaWE
- Possible candidates to use as codebase:
- Connector Configurator Plug-in
- Business Location Designer. Will be used to “build” the company (Master Data: Business Location) using a design editor.
- ASPIRE Programmability Engine Plug-in. Will be used to translate the AspireRFID specification Language prodused from the BPMWE Plug-in to the AspireRFID middleware.
- End-to-End management for all the AspireRFID middleware’s modules
- Probably use Jasmine (eclipse plug-in) as codebase (note: should find appropriate open source JMX enabled plug-in as codebase)
- Concurrent innovation engineering framework
- Authentication/Access mechanisms for the AspireRFID IDE
Connector
- Runs on Apache tomcat 6.0
- Uses CXF and Spring to implement JaxWS for the control interface.
- Uses EPCIS Query Client using the standard EPC Control Interface Based on SOAP messages.
- ERP/WMS Support:
- Singular Logic’s Enterprise ERP
- Microsoft’s Dynamics NAV
- MyWMS
- UJF’s Object tracking
- UJF’s Supply chain management
- UJF’s Sonding Balloon tracking
- Implemented as an OSGi bundle that can be deployed in JOnAS Application Server (not implemented yet)
- Authentication/Access mechanisms
ONS
- Under Construction
TDT (Uses Fosstrak Library for EPC TDT)
| Tag Data Standards | Supported |
|---|---|
| Bar Code Tags (GS1 System) | Yes |
| EAN/UPC | Yes |
| ITF-14 | Yes |
| GS1 DataMatrix | Yes |
| GS1 DAtaBar | Yes |
| GS1-128 | Yes |
| EPC Global Tags | Yes (Using Fosstrak) |
| SSCC | Yes |
| GTIN | Yes |
| GTIN | Yes |
| GLN | Yes |
| GRAI | Yes |
| GIAI | Yes |
| GLN | Yes |
| ISO Tags | To be supported |
| 14443 | To be supported |
| 15693 | To be supported |
| 15962 | To be supported |
| uCode Tags | To be supported |
Applications and Demos
- Simple F&C Test
- Warehouse Packet Delivery (3 Tier Use)
- AIT’s Warehouse Packet Delivery (6 Tier Use)
- UJF’s Object tracking (Connector Interface should be build to be supported)
- UJF’s Supply chain management (Connector Interface should be build to be supported)
- UJF’s Sonding Balloon tracking (Connector Interface should be build to be supported)
- Demo Packs for all available demos and Middleware modules.
Tasks
At the Implementation sequence column below we can find what should be done first. At the Priority column below we can find the task’s implementation priority degree from 1 to 9 with 9 defining higher priority.| C/N | Task Summary | First Version Deadline | Impl. Seq. | Priority (1-->9) |
|---|---|---|---|---|
| 1 | Reader Core Module | |||
| 1.1 | Reader Core HAL for TagSys Medio | 3 | ||
| 1.2 | Reader Core HAL for Tikitag | 3 | ||
| 1.3 | Reader Core HAL for Bluetooth | ? | 3 | |
| 1.4 | Reader Core HAL for NFC Phones | 3 | ||
| 1.5 | Reader Core Authentication/Access mechanisms | ? | 5 | |
| 1.6 | Standardization for Reader Management (RM) based on JMX | ? | ||
| 2 | Filtering & Collection Module | |||
| 2.1 | Extension Model for F&C Captured sensor data from semi-passive Tags | ? | 2 | 9 |
| 2.2 | Extension Model for F&C Captured sensor data from Sensor Networks | asap | 2 | 8 |
| 2.3 | Extension Model for F&C Captured data from actuators | ? | 7 | |
| 2.4 | Interface for F&C (or Reader Core) connecting/supporting Active Tags | ? | 7 | |
| 2.5 | Interface for F&C (or Reader Core) connecting/supporting Sensor Networks | asap | 2 | 8 |
| 2.6 | Partial implementation of the EPC Writing API for supporting Label generation and printing | ? | 4 | |
| 2.7 | Integration of TDT to F&C for supporting multiple types of Tags/Barcodes | ? | 6 | |
| 2.8 | Anti-collision protocol for multi-vendor RFID readers reside on middleware | ? | 7 | |
| 2.9 | Anti-collision protocol for multi-vendor RFID readers reside on Mac layer | ? | 7 | |
| 2.10 | Middleware anti-collision solution implementation for multi-vendor RFID readers | ? | 7 | |
| 2.11 | F&C Bundlization for OSGi deployment within JOnAS Application Server | ? | 2or8 ? | |
| 2.12 | Filtering & Collection Authentication/Access mechanisms | ? | 5 | |
| 2.13 | Management and automatic configuration of multiple RFID readers | ? | 6 | |
| 2.14 | Specifications of different kinds of low level filtering | ? | 7 | |
| 2.15 | Design of light ALE modules to be embedded in the readers, customizable based on the application | ? | 7 | |
| 2.16 | HAL for TagSys Medio | asap | 1 | 9 |
| 2.17 | HAL for Tikitag | asap | 1 | 8 |
| 2.18 | HAL for Bluetooth | ? | 1 | 7 |
| 2.6 | Reader Core HAL for NFC Phones | asap | 1 | 8 |
| 3 | Business Event Generator Module | |||
| 3.1 | BEG Interface for connecting/supporting Actuators | ? | 6 | |
| 3.2 | BEG Interface for connecting/supporting feedback to various devises (e.g. Account machines, delivery Information at the gates/handheld devises …) | ? | 4 | |
| 3.3 | BEG Bundlization for OSGi deployment within JOnAS Application Server | ? | 2or8 ? | |
| 3.4 | BEG Authentication/Access mechanisms | ? | 5 | |
| 4 | EPCIS Repository Module | |||
| 4.1 | EPCIS new Field extensions for the existing Event Types extensions in the Data Definition Layer | asap | 3 | 9 |
| 4.2 | EPCIS deployment within JOnAS Application Server | ? | 2or8 ? | |
| 4.3 | EPCIS Authentication/Access mechanisms | ? | 5 | |
| 5 | Connector Module | |||
| 5.1 | Connector Singular Logic’s Enterprise ERP support | ? | 4 | |
| 5.2 | Connector Microsoft’s Dynamics NAV ERP support | ? | 3 | |
| 5.3 | Connector MyWMS WMS support | ? | 3 | |
| 5.4 | Connector UJF’s Object tracking support | asap | 4 | 8 |
| 5.5 | Connector UJF’s Supply chain management support | asap | 4 | 8 |
| 5.6 | Connector UJF’s Sonding Balloon tracking support | ? | 3 | |
| 5.7 | Connector Bundlization for OSGi deployment within JOnAS Application Server | ? | 2or8 ? | |
| 5.8 | Connector Authentication/Access mechanisms | ? | 5 | |
| 6 | ONS Module | |||
| 6.1 | ONS | ? | 1 | |
| 7 | IDE/Tooling Module | |||
| 7.1 | RFID Specification Language | ? | 8 | |
| 7.2 | Programmable Engine Plug-in | ? | 7 | |
| 7.3 | Business Process Workflow Management Editor Plug-in | ? | 7 | |
| 7.4 | Concurrent innovation engineering framework (as an Eclipse plug-in?) | ? | 6 | |
| 7.5 | Connector Configurator Plug-in | ? | ||
| 7.6 | Business Location Designer plug-in | ? | 2 | |
| 7.7 | End-to-End management plug-in for all the AspireRFID middleware’s modules | 5 | 7 | |
| 7.8 | Authentication/Access mechanisms for the AspireRFID IDE | ? | 5 | |
| 8 | TDT Module | |||
| 8.1 | TDT extended support | ? | 6 | |
| 9 | Packaging Module | |||
| 9.1 | Demo Packs for all available demos and Middleware modules | ? | 4 |
