Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
BS ISO IEC 24791 — RFID Software System Infrastructure for Item Management
Information Technology — Radio Frequency Identification (RFID) for Item Management — Software System Infrastructure
📡 The BS ISO/IEC 24791 series is the British Standard adoption of the ISO/IEC 24791 international standards, focused on the software system infrastructure for radio frequency identification (RFID) item management. Working alongside ISO/IEC 18000 (air interface) and ISO/IEC 15963 (unique identification), it forms the middleware and platform layer that connects RFID readers to enterprise applications. BSI Technical Committee IST/34 (Automatic identification and data capture techniques) is responsible for UK participation in this work, classified under ICS 35.040. This article presents the series as a whole: its structure, key technical requirements, and engineering practice.
💡 In an RFID project, readers and tags are only the “sensing layer”; usability and maintainability are often determined by the software system infrastructure. ISO/IEC 24791 provides the common architecture and interfaces for this “invisible middle layer”.
1. Series Overview 📌
The ISO/IEC 24791 series is developed by ISO/IEC JTC 1/SC 31 (Automatic identification and data capture techniques) and adopted identically in the UK as BS ISO/IEC 24791. The series does not define the air interface between tags and readers (that is ISO/IEC 18000); instead it defines the software interfaces, data models, and system architecture needed between readers and applications, between devices, and for device management — so that readers, middleware, and enterprise applications from different vendors can interoperate.
The BS ISO/IEC 24791 series comprises the following parts:
| Part | Edition | Subject | Main Content |
|---|---|---|---|
| BS ISO/IEC 24791-1 | 2010 | Part 1: Architecture | Defines the overall architecture, components, and relationships of RFID software system infrastructure — the “blueprint” of the series. |
| BS ISO/IEC 24791-2 | 2011 | Part 2: Data management | Defines Application Level Events (ALE) and related data management interfaces, converting raw tag reads into business events. |
| BS ISO/IEC 24791-3 | 2014 | Part 3: Device management | Defines the Device Control Interface (DCI) and SNMP interface sets for managing reader device state and configuration. |
| BS ISO/IEC 24791-5 | 2012 | Part 5: Protocol test methods | Specifies testing and conformance verification for the software infrastructure interfaces (scan version; written from public domain knowledge). |
⚠️ Part 5 (24791-5:2012) is a scan-only file in the source material; its content is summarised from public domain knowledge. Always refer to the official BSI published version for actual use.
2. Architecture and Technical Points 🏗️
Part 1 (Architecture) is the foundation of the series. It divides the RFID software system infrastructure into logical layers and functional entities and defines the interfaces between them. A typical architecture includes: a device layer connecting reader hardware, a data management layer performing filtering and event aggregation, an application interface layer providing unified access to business systems, and a cross-cutting device management and configuration layer. The interfaces and data models are described using the Unified Modeling Language (UML) to keep implementations consistent.
Part 2 (Data management) defines the Application Level Events (ALE) interface. ALE aggregates tag reads from multiple readers into “events” according to time windows, filters (such as EPC prefix or tag type), and report triggers — reducing the volume of data forwarded upward and simplifying business logic. It also specifies the XML representation and querying of event data models.
Part 3 (Device management) defines two interface sets: the Device Control Interface (DCI) and the Simple Network Management Protocol (SNMP) interface set. DCI controls, configures, and queries reader status; the SNMP interface set lets network management platforms discover and monitor RFID devices through standard SNMP, integrating them with existing network management systems.
| Architecture Layer | Primary Standard Basis | Typical Function |
|---|---|---|
| Device layer (reader/tag) | ISO/IEC 18000, ISO/IEC 15963 | Air interface communication, unique tag identification |
| Data management layer | BS ISO/IEC 24791-2 (ALE) | Filtering, aggregation, event reporting |
| Device management layer | BS ISO/IEC 24791-3 (DCI/SNMP) | Device configuration, status monitoring, remote management |
| Application interface layer | BS ISO/IEC 24791-1 | Unified access and event subscription for business systems |
3. Key Technical Requirements 🔧
- Interoperability: standardized interfaces and data models allow readers and middleware from different vendors to be replaced and to interoperate, reducing integration and long-term maintenance cost.
- Event-driven operation: ALE outputs events as its basic unit; business systems subscribe to events of interest rather than polling devices, avoiding wasted resources and latency.
- Unified device management: DCI provides unified device control commands, while SNMP integrates readers into enterprise network management for centralised monitoring and alarms.
- Data modelling: interfaces and data models are expressed in UML to ensure implementation consistency and extensibility.
- Testing and conformance: Part 5 defines how interface implementations are tested and assessed for conformance — an important basis for procurement acceptance.
4. Engineering Practice 🛠️
An RFID project typically involves three parallel tracks: hardware selection, middleware selection, and business integration. Following BS ISO/IEC 24791 brings the following practical benefits:
- 🔍 Selection: when buying readers and middleware, require conformance to the interfaces defined by this series, ensuring future replaceability and extensibility.
- 🔗 Integration: using the standard ALE event interface and data model, business systems (WMS, MES, supply chain platforms) can be connected quickly with less custom development.
- 📊 Operations: integrate RFID devices into a unified network management platform via SNMP for centralised status, alarms, and configuration.
- 📋 Acceptance testing: perform conformance verification per Part 5 to ensure the delivered system meets the standard.
✅ Practice key: first define business events and data requirements, then choose standards-compliant middleware and readers, and finally integrate via standard interfaces; do not start with hardware selection, which may lock you into vendor-specific interfaces later.
5. Frequently Asked Questions ❓
❓ Q: What is the difference between ISO/IEC 24791 and ISO/IEC 18000?
A: ISO/IEC 18000 defines the air interface between tags and readers (physical layer and protocol of wireless communication), while ISO/IEC 24791 defines the software system infrastructure above readers (middleware interfaces, data management, and device management). They occupy different layers of the RFID stack and complement each other.
A: ISO/IEC 18000 defines the air interface between tags and readers (physical layer and protocol of wireless communication), while ISO/IEC 24791 defines the software system infrastructure above readers (middleware interfaces, data management, and device management). They occupy different layers of the RFID stack and complement each other.
❓ Q: Why is the ALE (Application Level Events) layer needed?
A: A single reader may read hundreds or thousands of tags per second; reporting them raw would overwhelm business systems. ALE filters and aggregates raw reads into meaningful events (e.g., “a pallet passed a gate”), greatly reducing data volume and simplifying business logic.
A: A single reader may read hundreds or thousands of tags per second; reporting them raw would overwhelm business systems. ALE filters and aggregates raw reads into meaningful events (e.g., “a pallet passed a gate”), greatly reducing data volume and simplifying business logic.
❓ Q: Does this series specify reader/tag performance?
A: Not directly. Performance and conformance are primarily defined by air interface standards (e.g., ISO/IEC 18000) and associated test methods; BS ISO/IEC 24791 concerns the software interfaces and architecture above them.
A: Not directly. Performance and conformance are primarily defined by air interface standards (e.g., ISO/IEC 18000) and associated test methods; BS ISO/IEC 24791 concerns the software interfaces and architecture above them.
❓ Q: What are the direct benefits of adopting this series?
A: The core benefits are interoperability and maintainability — products from different vendors can be interchanged and managed uniformly, and business systems connect through standard interfaces, reducing integration cost, avoiding vendor lock-in, and easing long-term operations and expansion.
A: The core benefits are interoperability and maintainability — products from different vendors can be interchanged and managed uniformly, and business systems connect through standard interfaces, reducing integration cost, avoiding vendor lock-in, and easing long-term operations and expansion.