You are here: Resources > FIDIS Deliverables > Profiling > D7.7: RFID, Profiling, and AmI > 

D7.7: RFID, Profiling, and AmI

Selected Standards  Title:


Electronic Product Code (EPC) *

EPC* allows for unique identification and tracking of tagged objects via internet. 

EPCglobal Inc. is a non-profit organisation founded by GS1 (former EAN – European Article Numbering International) and UCC (Uniform Code Council), the two main barcode issueing associations.  

EPC*, the Electronic Product Code* standardised by EPCglobal, is intended to replace EAN or UPC (Universal Product Code) numbers when RFID tags* replace barcodes as identifiers on products. 

EPC* is a set of coding schemes for RFID tags*, originally developed by MIT AutoID Center. EPC* numbers start with a header identifying the encoding scheme used, which according to EPC Version 1.3 can be one of the following:


  • General Identifier (GID), GID-96, 

  • Serialized version of the GS1 Global Trade Item Number (GTIN), SGTIN-96, SGTIN-198, 

  • GS1 Serial Shipping Container Code (SSCC), SSCC-96, 

  • GS1 Global Location Number (GLN), SGLN-96, SGLN-195, 

  • GS1 Global Returnable Asset Identifier (GRAI), GRAI-96, GRAI-170, 

  • GS1 Global Individual Asset Identifier (GIAI), GIAI-96, GIAI-202,  

  • DoD Construct, DoD-96. 


The EPCglobal architecture allows the use of a variety of authentication technologies across its defined interfaces. It is expected, however, that the X.509 authentication framework will be widely employed within the EPCglobal network.

When an EPC* number is read, the reading device can identify the object via internet by accessing the Object Name Service within the EPCglobal network. The EPCglobal Networks aims at exchanging data in real time to allow tracking of products. An EPC* number contains:


  • Header, which identifies the length, type, structure, version and generation of EPC*,  

  • Manager Number, which identifies the company or company entity , 

  • Object Class, similar to a stock keeping unit, 

  • Serial Number, which is the specific instance of the Object Class being tagged.  


Additional fields may also be used as part of the EPC* in order to properly encode and decode information from different numbering systems into their native (human-readable) forms.

EPC* uses Object Name Service (technically based on DNS) to allow for unique identification of tagged objects (as opposed to identification of object class with barcodes).  



Selected Standards  fidis-wp7-del7.7.RFID_Profiling_AMI_02.sxw  References
Denis Royer 41 / 43