Different names often point to the same radio interface
EPC Class 1 Gen2 originated in the EPCglobal and GS1 ecosystem. The same family of technical behavior is standardized internationally as ISO/IEC 18000-63, historically also described in product literature as ISO 18000-6C.
Compliance with the air interface is necessary, but a working project also depends on the regional frequency plan, reader configuration, antenna system, tag chip features, memory, form factor and application software.
Protocol
What the standard defines
The air interface controls radio communication between a reader and many passive tags.
Reader commands
How a reader starts an inventory round, selects tags and requests data.
Tag replies
How a passive tag harvests energy and backscatters a response.
Anti-collision
How many tags share the same radio field without all replying at once.
Memory operations
Reading and writing EPC, TID, User and Reserved memory where supported.
Session behavior
How tag state can be managed across repeated inventory rounds.
Access controls
Optional passwords, locking and security functions depending on the tag and generation.
Gen2, Gen2v2 and Gen2v3
Later versions preserve the core interface while adding or clarifying capabilities.
Gen2
The widely deployed base for passive UHF tag inventory and memory operations.
Gen2v2
Adds security and privacy functions used by compatible chips and readers.
Gen2v3
Further evolves the GS1 specification while retaining the interoperability goal.
EPC memory
Typically stores the identifier used by the application.
TID memory
Identifies the tag chip or tag model characteristics; behavior depends on the chip.
User memory
Optional application data with capacity defined by the selected chip.
Reserved memory
Access and kill passwords where the tag supports them.
Regional rules
Frequency, power and channel requirements must match the country of operation.
Compatibility is more than a logo
Check the complete operating chain before procurement.
Tag and reader
Confirm the reader supports the required region, commands and optional chip features.
How to choose an RFID tagReader and application
Confirm the device interface, SDK or LLRP support and how reads reach the business system.
How to choose an RFID readerWhat to check in a specification
A statement such as “ISO 18000-6C compatible” is only the starting point.
- Operating frequency range and regional configuration.
- Supported Gen2 version and optional commands.
- EPC, TID and User memory size required by the application.
- Read and write operations needed in the process.
- Password, locking or security requirements.
- Tag sensitivity, form factor and behavior on the real surface.
- Reader antenna ports, power and device interface.
- Software support, event filtering and integration.
Standards enable interoperability; testing proves the application
Two compliant products can still perform differently because antenna design, chip sensitivity, tag placement and the surrounding material affect the link budget.
Select compatible equipment first, then compare candidate tags and reader settings on representative objects and in the intended control zone.
FAQ
EPC Gen2 and ISO/IEC 18000-63 questions
Are EPC Gen2 and RAIN RFID the same thing?
RAIN RFID is the industry name for passive UHF RFID systems based on the EPC Gen2 and ISO/IEC 18000-63 family.
Will older Gen2 tags work with a newer reader?
The standards are designed for interoperability, but required commands, regional configuration and optional chip features should still be confirmed.
Should all product data be written to the tag?
Usually no. The EPC acts as an identifier; detailed business data is commonly stored in the connected database.
Is “ISO 18000-6C” enough in a product card?
No. Also verify frequency region, supported commands, memory, form factor, environmental rating and the device integration interface.
Are LLRP and EPC Gen2 the same?
No. EPC Gen2 is the tag-reader air interface. LLRP is a protocol used by software to control compatible readers.
