Electronic Product Code ( EPC ) is designed as a universal identifier that provides a unique identity for every physical object anywhere in the world, for all time. The EPC structure is defined in the EPCglobal Data Tag Standard [1], which is an open standard available for free to download from the EPCglobal, Inc. website. The canonical representation of the EPC is a URI, the 'pure-identity URI' Representation intended to be used when referring to a particular physical object in communication about the EPC between the business information system and business software. Standard Data Tags EPCglobal also defines additional representations of EPC identifiers, such as the format of tag encoding URIs and compact binary formats that are suitable for efficiently storing EPC identifiers in RFID tags (for which RFID passive low cost RFID is usually limited memory capacity available for EPC memory banks/UII). The EPCglobal Data Tag Standard defines the URI syntax structure and binary format, as well as the encoding and decoding rules to allow the conversion between these representations. EPC is designed as a flexible framework that can support many existing coding schemes, including many coding schemes that are currently used with barcode technology. The current EPC identification supports 7 identification keys of the GS1 identifier system, as well as a common identifier and EPC identifier that can be used to encode supplies to the US Department of Defense.
EPC is not designed specifically for use with RFID data carriers. They can indeed be built based on readings of optical data carriers, such as linear barcodes and two-dimensional bar codes, such as the Data Matrix symbol. The canonical representation of 'true URI identity' of the EPC is agnostic to the data carrier technology used to attach a unique identifier to an individual physical object.
EPC is designed to meet the needs of various industries, while ensuring uniqueness for all tags that meet EPC. Some of the existing GS1 identification keys [2] (such as the Global Back Asset Identifier ( GRAI )) already provide a unique identification of individual objects. However, the Global Trade Goods Number ( GTIN ) only identifies the type of product or inventory storage unit (SKU ) rather than individual samples of a particular product type. To ensure that the EPC always uniquely identifies the individual physical object, in the case of GTIN, the EPC is built as Serialized Serialized Global Trade Item Number ( SGTIN ) by combining GTIN product identifiers with a unique serial number.
Both Universal Product Codes and EAN-13 identifiers still found on many trading items can be mapped to a 14-digit GTIN identifier, with padding to the left with zero digits to achieve a total of 14 digits. Therefore, the SGTIN EPC identifier can be constructed by combining the generated GTIN with a unique serial number and following the coding rules in the EPCglobal Data Tag Standard.
The EPC accommodates the existing coding scheme and defines the new schema if necessary. Each coding scheme in the EPC identifier framework is distinguished through the use of a separate namespace. In URI notation, this is indicated by using URI prefixes such as urn: epc: id: sgtin or jar: epc: id: sscc In a concise binary encoding of an EPC identifier, namespace instead shown using a compact binary header (usually the first 8 bits of the binary encoding of the EPC identifier). The EPCglobal Tag Data Standard provides precise URI prefix and binary header values.
Cheap passive RFID tags are designed to identify each uniquely manufactured item. By contrast, barcodes for trade goods and consumer products have limited capacity and usually only identify producers and product classes. While RFID tags are still more expensive than simple visual readable labels, they offer additional capabilities such as the ability to be read by radio waves, without requiring a 'line of sight' between readers or interrogators and tags; this allows each item in a large cardboard box (box) to read without first unpacking each item from the box. Some RFID tags offer additional read/write user memory that can be used for storage of additional information, such as expiration date or creation date.
EPC tags will never completely replace plain text and barcodes, because the obligation obligations for manufacturers require long-lasting and fairly fail-safe labels. Currently (2010) there are no applications where RFID tags completely replace conventional labels.
The EPC is the establishment of the MIT Auto-ID Center, a consortium of more than 120 global companies and university laboratories. The EPC identifier is designed to identify every manufactured item, not just the manufacturer and the product class, as the current bar code does. The EPC system is currently managed by EPCglobal, Inc., a subsidiary of GS1. Specifications for EPC identifiers can be found in EPCglobal, Inc. Standard Tag data, which is an open standard, is available for free for anyone to download.
The Electronic Product Code is one of the industry standards for global RFID use, and the core element of EPCglobal Network [3], an open standards architecture developed by the EPCglobal GS1 community. Most of the RFID EPCs used today comply with ISO/IEC 18000-6C for RFID air interface standards.
Video Electronic Product Code
Structure
The canonical representation of an EPC is a URI - a 'pure identity-identity' intended to be used when referring to a particular physical object in communication about the EPC between the business information system and business software.
Each coding scheme in the EPC identifier framework is distinguished through the use of a separate namespace. In URI notation, this is indicated by using URI prefixes such as urn: epc: id: sgtin or jar: epc: id: sscc In a concise binary encoding of an EPC identifier, namespace instead shown using a compact binary header (usually the first 8 bits of the binary encoding of the EPC identifier). The EPCglobal Tag Data Standard provides precise URI prefix and binary header values.
This namespace indicator (URI prefix or concise binary header value) in turn determines the length, type, and structure of the EPC. The EPC coding scheme is used to uniquely identify one object. Most EPCs incorporate elements within their structure that correspond to the serial number.
The EPC 1.3 version supports the following alternative encoding schemes:
- GID-96 General Identifier (GID)
- serial version of GS1 Global Goods Sale Number (GTIN) SGTIN-96 SGTIN-198
- SSC-96 Subscriber Mandatory Submit Code (SSCC) 96
- GS1 Global Location Number (GLN), SGLN-96 SGLN-195
- GS1 Global Asset Return Assets (GRAI) GRAI-96 GRAI-170
- GS1 Global Individual Asset Identifier (GIAI) GIAI-96 GIAI-202 and
- DOD Build DoD-96
From Version 1.4, this new coding scheme is also supported:
- Global Services Relation Number (GSRN) GSRN-96
- GDTI-96 Global Document Identifier (GDTI-96)
Starting January 2014, the current version of Standard Tag Data is v1.8, which also defines the formatting of the Tag Identifier (TID) memory bank and how to use Packaged Objects to format additional data within the user's memory bank.
Maps Electronic Product Code
See also
- Product code (disambiguation)
References
External links
- EPC/RFID on the GS1 website
- EPCglobal Tag Data Standard
- EPCglobal Standard Version Data Tag 1.10
- EPCglobal Standard Version Data Tag 1.9
- EPCglobal Standard Version Data Tag 1.8
- EPCglobal Standard Version Data Tag 1.6
- EPCglobal Standard Version Data Tag 1.5
- EPCglobal Standard Version Data Tag 1.4
- EPCglobal Standard Version 1.3 Data Tag
- Translation Data Standard Tag EPCglobal
- Global RFID. Value of EPCglobal Network for Supply Chain Management - Contains lots of information by some MIT people involved in EPC development.
Source of the article : Wikipedia
0 Comments