{"id":6910,"date":"2020-02-24T12:42:10","date_gmt":"2020-02-24T12:42:10","guid":{"rendered":"https:\/\/rfid4u.com\/?page_id=6910"},"modified":"2020-09-19T04:09:42","modified_gmt":"2020-09-19T04:09:42","slug":"rfid-epc-gen2-memory","status":"publish","type":"page","link":"https:\/\/rfid4u.com\/rfid-epc-gen2-memory\/","title":{"rendered":"EPC Gen2 Memory"},"content":{"rendered":"

[vc_section full_width=”stretch_row” css=”.vc_custom_1600488574564{background: #ffffff url(https:\/\/rfid4u.com\/wp-content\/uploads\/2020\/05\/Rfid4uWebsite-Background-Image-1.jpg?id=11905) !important;background-position: center !important;background-repeat: no-repeat !important;background-size: cover !important;}”][vc_row][vc_column][vc_custom_heading text=”Explore \/ RFID Basics & Resources” font_container=”tag:h5|text_align:center|color:%23ffffff” use_theme_fonts=”yes”][vc_custom_heading text=”RFID Basics – EPC Gen2 Memory” font_container=”tag:h1|text_align:center|color:%23ffffff” use_theme_fonts=”yes”][\/vc_column][\/vc_row][\/vc_section][vc_section full_width=”stretch_row” css=”.vc_custom_1588939470806{background-color: #ffffff !important;background-position: 0 0 !important;background-repeat: no-repeat !important;}” el_class=”background-position-right-bottom”][vc_row][vc_column][vc_column_text]As per How to Select a Correct RFID Tag \u2013 Standards & Mandates<\/a>, this standard is officially called EPC Radio-Frequency Identity Protocols Class 1 Generation 2 UHF RFID protocol for communications at 860\u2013960 MHz. It was developed by EPCglobal, Inc. in 2004, which is now GS1, and was approved as ISO 18000-6C in July 2006. It defines air interface parameters for tags operating within the frequency range of 860\u2013960 MHz and allows for use of different frequencies in different regions from within this range.[\/vc_column_text]

<\/i>There are several versions of this standard and the latest version Gen2v2 (that was first introduced in 2013) 2.0.1. (ratified in 2015) introduces several new features to the protocol.<\/cite><\/blockquote><\/div>[vc_empty_space height=”30px”][vc_custom_heading text=”THE TABLE BELOW PROVIDES AN OVERVIEW OF GENERATION2 FEATURES:” font_container=”tag:h4|text_align:left|color:%23212121″ use_theme_fonts=”yes” css=”.vc_custom_1588940097997{margin-top: 0px !important;margin-bottom: 20px !important;}”][vc_row_inner][vc_column_inner width=”1\/2″][vc_custom_heading text=”EPC Gen2 Requirement” font_container=”tag:h4|text_align:left|color:%23424242″ use_theme_fonts=”yes” css=”.vc_custom_1588940111213{margin-top: 0px !important;margin-bottom: 20px !important;}”]
<\/div>
<\/div><\/div><\/div>[vc_column_text]Global regulatory compliance
\nMemory access control
\nRead speed
\nDense-reader operation
\nAnti-collision
\nKill security
\nMemory-write capability
\nBit-masked filtering
\nUser Memory
\nCost and availability
\nAuthentication
\nTraceability[\/vc_column_text][\/vc_column_inner][vc_column_inner width=”1\/2″][vc_custom_heading text=”EPC Gen2 (v2) Features” font_container=”tag:h4|text_align:left|color:%23424242″ use_theme_fonts=”yes” css=”.vc_custom_1588940122580{margin-top: 0px !important;margin-bottom: 20px !important;}”]
<\/div>
<\/div><\/div><\/div>[vc_column_text]Europe, North America, and others
\n32-bit Access password Memory locking
\nGreater than 1,000 tags per second
\nDense-reader operating mode
\nFlexible, changing based on environment
\n32-bit Kill password
\nGreater than seven tags per second write rate
\nFlexible Select command
\nSize based on vendor, enhanced for logging
\nMulti-vendor available, low cost
\nCryptographic authentication for anti-counterfeiting
\nFunctions for Untraceability[\/vc_column_text][\/vc_column_inner][\/vc_row_inner][vc_column_text]For more information, read How to Select a Correct RFID Tag \u2013 Standards & Mandates<\/a>.[\/vc_column_text][vc_empty_space height=”30px”][vc_custom_heading text=”TYPES OF DATA IN GEN2 TAG MEMORY” font_container=”tag:h4|text_align:left|color:%230f4996″ use_theme_fonts=”yes” el_class=”font-weight-bold text-uppercase” css=”.vc_custom_1588940150430{margin-top: 0px !important;margin-bottom: 20px !important;}”][vc_column_text el_class=”rfid4u-table”]<\/p>\n
\n\n\n\n\n\n\n\n
Information Type<\/th>\nDescription<\/th>\nWhere on Gen 2 Tag<\/th>\nWhere Typically Used<\/th>\nBar Code Equivalent<\/th>\n<\/tr>\n<\/thead>\n
Business Data<\/td>\nDescribes the physical object to which the tag is affixed.<\/td>\nEPC Bank (excluding PC and XPC bits, and filter value within EPC) User Memory Bank<\/td>\nData Capture layer and Business Application layer<\/td>\nYes: GS1 keys, Application Identifiers (AIs)<\/td>\n<\/tr>\n
Control Information<\/td>\nFacilitates efficient tag interaction MIC<\/td>\nReserved Bank EPC Bank: PC and XPC bits, and filter value within EPC<\/td>\nData Capture layer<\/td>\nNo<\/td>\n<\/tr>\n
Tag Manufacture Information<\/td>\nDescribes the tag itself, as opposed to the physical object to which the tag is affixed.<\/td>\nTID Bank<\/td>\nData Capture layer Unique tag manufacture serial number may reach Business Application layer<\/td>\nNo<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

[\/vc_column_text][vc_empty_space height=”30px”][vc_custom_heading text=”GENERATION 2 MEMORY LAYOUT” font_container=”tag:h4|text_align:left|color:%230f4996″ use_theme_fonts=”yes”][vc_column_text]The following graphic depicts the Generation 2 memory layout. Gen2 tags can four banks of non-volatile memory \u2013 Reserved Memory, EPC Memory, Tag Identification (TID) Memory and User Memory. Each memory region is accessed in parts, that are 16-bit long, called words, starting at word 0.[\/vc_column_text][vc_single_image image=”13998″ img_size=”full” alignment=”center” style=”vc_box_outline”][vc_empty_space height=”30px”][vc_custom_heading text=”RESERVED MEMORY (BANK 0)” font_container=”tag:h4|text_align:left|color:%230f4996″ use_theme_fonts=”yes”][vc_column_text]The reserved area of memory holds the tag\u2019s Access and Kill passwords, with a 32-bit \u201cKill\u201d password that allows a tag to be permanently silenced.
\n\u2022 The Kill command only executes if the password has been set (that is, is non-zero).
\n\u2022 The default Kill password value is zero.
\nA 32-bit Access password allows the Tag to transition to the Secured state. A tag in the Secured state can execute all Access commands, including writing to locked blocks.
\nKill and access passwords must be accepted prior to being used. The kill password is a 32-bit value stored in reserved memory 00h to 1Fh, MSB first. Remember that:<\/strong>
\n\u2022 A tag that does not implement a kill password acts as though it had a zero-valued kill password that is permanently read\/write locked.
\n\u2022 A tag does not execute a kill operation if its kill password is zero.
\n\u2022 An interrogator uses a tag\u2019s kill password once, to kill the tag and render it silent thereafter.
\n\u2022 The default (that is, un-programmed) value is zero.
\nThe access password is a 32-bit value stored in reserved memory 20h to 3Fh, MSB first. Remember that:<\/strong>
\n\u2022 Tags with a non-zero access password is required an interrogator to issue this password before transitioning to the secured state.
\n\u2022 The default (that is, un-programmed) value is be zero.
\nA tag that does not implement an access password acts as though it had a zero-valued access password that is permanently read\/write locked.[\/vc_column_text][vc_empty_space height=”30px”][vc_custom_heading text=”EPC MEMORY (BANK 1)” font_container=”tag:h4|text_align:left|color:%230f4996″ use_theme_fonts=”yes”][vc_column_text]EPC Memory consists of the 16-bit Cyclic Redundancy Check (CRC-16), which is an error detection code, a 16-bit Protocol Control (PC) and starting with Word 2, the EPC number (96 to 496 bits).[\/vc_column_text]

<\/i>The Protocol Control manages, how many bits of EPC are sent back to the reader, regardless the actual length of the EPC data in the bank. The standard is 96 bits but what if you need to send more? The length is defined in the PC. The total amount of words for EPC data in the memory depends on the chip manufacturer.<\/cite><\/blockquote><\/div>[vc_column_text]The PC is further subdivided:<\/strong>
\n\u2022 First 5 bits indicate the EPC memory length, next bit indicates whether the tag has or does not have user memory.
\n\u2022 The bit 6 identifies the existence of the Extended Protocol Control Word 1 (XPC_W1) in the word 21 of EPC Memory.
\n\u2022 The bit 7 identifies whether the data in the EPC data area conforms to a GS1 EPCGlobal™ (set to 0b) or an ISO\/IEC 15961 coding scheme (set to 1b). The actual coding scheme is identified in the Application Family Identifier (AFI) bit field.[\/vc_column_text][vc_column_text]<\/p>\n
\n\n\n\n\n\n\n\n\n\n\n
Bits<\/th>\nField<\/th>\nDescription<\/th>\nWhere Specified<\/th>\n<\/tr>\n<\/thead>\n
10h\u201314h<\/strong><\/td>\nLength<\/td>\nRepresents the number of 16-bit words comprising the PC field and the EPC field (below). See discussion in Section 15.1.1 for the encoding of this field.<\/td>\nUHFC1G2 Standard<\/td>\n<\/tr>\n
15h<\/strong><\/td>\nUser Memory Indicator (UMI)<\/td>\nIndicates whether the user memory bank is present and contains data.<\/td>\nUHFC1G2 Standard<\/td>\n<\/tr>\n
16h<\/strong><\/td>\nXPC Indicator (XI)<\/td>\nIndicates whether an XPC is present<\/td>\nUHFC1G2 Standard<\/td>\n<\/tr>\n
17h<\/strong><\/td>\nToggle<\/td>\nIf zero, indicates an EPCglobal application; in particular, indicates that bits 18h \u2013 1Fh contain the Attribute Bits and the remainder of the EPC bank contains a binary encoded EPC.
\nIf one, indicates a non-EPCglobal application; in particular, indicates that bits 18h \u2013 1Fh contain the ISO Application Family Identifier (AFI) as defined in [ISO15961] and the remainder of the EPC bank contains a Unique Item Identifier (UII) appropriate for that AFI.<\/td>\n		UHFC1G2 Standard<\/td>\n<\/tr>\n
18h\u20131Fh(if toggle = 0)<\/strong><\/td>\nAttribute Bits<\/td>\nBits that may guide the handling of the physical object to which the tag is affixed. (Applies to Gen2 v 1.x tags only.)<\/td>\nSection 11 of EPC C1G2 Tag Data Standard<\/td>\n<\/tr>\n
18h\u20131Fh(if toggle = 1)<\/strong><\/td>\nAFI<\/td>\nAn Application Family Identifier that specifies a non-EPCglobal application for which the remainder of the EPC bank is encoded<\/td>\nISO 15961<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

[\/vc_column_text][vc_empty_space height=”30px”][vc_custom_heading text=”USER MEMORY (BANK 3)” font_container=”tag:h4|text_align:left|color:%230f4996″ use_theme_fonts=”yes”][vc_column_text]User memory is optional and can have various sizes, usually 512 bits and up to 4 or 8K of memory in some tags. This memory is used for additional data that is not suitable or does not fit into the EPC memory, such as for instance temperature or maintenance logs, expiration dates and other data.
\nThe first few bits are a Data Storage Format Identifier (DSFID) as specified in ISO15961 and ISO15962. The DSFID specifies the format for the remainder of the user memory bank. The DSFID is usually eight bits in length, but may be extended as per ISO15961. When the DSFID specifies Access Method 2, the format of the remainder of user memory is \u201cpacked objects\u201d. This format is recommended for use in EPC applications.[\/vc_column_text][vc_empty_space height=”30px”][vc_custom_heading text=”TAG IDENTIFICATION (TID) MEMORY (BANK 2)” font_container=”tag:h4|text_align:left|color:%230f4996″ use_theme_fonts=”yes”][vc_column_text]TID Memory carries the unique tag identifier that cannot be changed or erased. This ID identifies the tag itself, rather than item it is applied to.[\/vc_column_text][vc_empty_space height=”30px”][vc_custom_heading text=”EPC TAG DATA STANDARDS, VERSION 1.9 (PUBLISHED JULY 2014)” font_container=”tag:h4|text_align:left|color:%230f4996″ use_theme_fonts=”yes”][vc_column_text]This standard defines EPC tag data formats for Generation 2 tags. It defines how the EPC is encoded on the tag and how it is encoded for use in the information systems layers of the EPC Systems Network. The standard includes specific encoding schemes for EPC General Identifier (GID).
\nextended as per ISO15961. When the DSFID specifies Access Method 2, the format of the remainder of user memory is \u201cpacked objects\u201d. This format is recommended for use in EPC applications.[\/vc_column_text][vc_empty_space height=”30px”][vc_custom_heading text=”GID FORMAT” font_container=”tag:h3|font_size:20px|text_align:left|color:%23212121|line_height:55px” use_theme_fonts=”yes” el_class=”font-weight-bold text-uppercase” css=”.vc_custom_1582617106483{margin-top: 0px !important;margin-bottom: 20px !important;}”][vc_column_text el_class=”rfid4u-table”]<\/p>\n

\n

Decimal capacity0011 0101(actual value)268,435,45516,777,21536 bits<\/p>\n\n\n\n\n\n
Information Type<\/th>\nHEADER<\/th>\nGENERAL MANAGER NUMBER<\/th>\nOBJECT CLASS NUMBER<\/th>\nSERIAL NUMBER<\/th>\n<\/tr>\n<\/thead>\n
GID-96<\/td>\n8 bits<\/td>\n28 bit<\/td>\n24bit<\/td>\n24 bits<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

The standard also defines encoding of other numbering systems for 96 bits used in global trade.<\/em>[\/vc_column_text][vc_empty_space height=”30px”][vc_custom_heading text=”OTHER EPC SCHEMES” font_container=”tag:h4|text_align:left|color:%230f4996″ use_theme_fonts=”yes”][vc_column_text]This standard defines EPC tag data formats for Generation 2 tags. It defines how the EPC is encoded on the tag and how it is encoded for use in the information systems layers of the EPC Systems Network. The standard includes specific encoding schemes for EPC General Identifier (GID).
\nextended as per ISO15961. When the DSFID specifies Access Method 2, the format of the remainder of user memory is \u201cpacked objects\u201d. This format is recommended for use in EPC applications.[\/vc_column_text][vc_empty_space height=”30px”][vc_custom_heading text=”GID FORMAT” font_container=”tag:h3|font_size:20px|text_align:left|color:%23212121|line_height:55px” use_theme_fonts=”yes” el_class=”font-weight-bold text-uppercase” css=”.vc_custom_1582617256724{margin-top: 0px !important;margin-bottom: 20px !important;}”]

<\/div>
<\/div><\/div><\/div>[vc_column_text el_class=”rfid4u-table”]<\/p>\n
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Information Type<\/th>\nHEADER<\/th>\nGENERAL MANAGER NUMBER<\/th>\n<\/tr>\n<\/thead>\n
SGTIN<\/td>\nSerialized Global Trade Item Number<\/td>\nUsed to assign a unique identity to an instance of a trade item, such as a specific instance of a product or SKU.<\/td>\n<\/tr>\n
SSCC<\/td>\nSerial Shipping Container Code<\/td>\nUsed to assign a unique identity to a logistics handling unit, such as the aggregate contents of a shipping container or a pallet load.<\/td>\n<\/tr>\n
SGLN*<\/td>\n\u00a0Global Location Number (with or without extension)<\/td>\nUsed to assign a unique identity to a
\nphysical location, such as a specific building or a specific unit of shelving within a warehouse.<\/td>\n<\/tr>\n
\u00a0GRAI<\/td>\n\u00a0Global Returnable Asset Identifier (serial number mandatory)<\/td>\n\u00a0Used to assign a unique identity to a specific returnable asset, such as a reusable shipping container or a pallet skid.<\/td>\n<\/tr>\n
GIAI<\/td>\nGlobal Individual Asset Identifier<\/td>\nUsed to assign a unique identity to a specific asset, such as a forklift or a computer.<\/td>\n<\/tr>\n
\u00a0GSRN<\/td>\nGlobal Service Relation Number (for Recipient)<\/td>\nUsed to assign a unique identity to a service recipient, i.e. a Hospital Patient or a Club Member.<\/td>\n<\/tr>\n
\u00a0GSRNP<\/td>\nGlobal Service Relation Number for Provider<\/td>\nUsed to assign a unique identity to a service provider, i.e. a hospital or a club.<\/td>\n<\/tr>\n
GDTI<\/td>\nGlobal Document Type Identifier<\/td>\nUsed to assign a unique identity to a specific document, such as land registration papers, an insurance policy, etc.<\/td>\n<\/tr>\n
CPI<\/td>\n\u00a0Component \/ Part Identifier<\/td>\n\u00a0Used by the technical industries (including the automotive sector) for the unique identification of parts or components.<\/td>\n<\/tr>\n
SGCN<\/td>\nSerialized Global Coupon Number<\/td>\nUsed to uniquely identify a coupon.<\/td>\n<\/tr>\n
GID<\/td>\nGeneral Identifier<\/td>\n\u00a0The GID EPC scheme is independent of any specifications or identity scheme outside the EPCglobal Tag Data Standard.<\/td>\n<\/tr>\n
DOD<\/td>\n\u00a0US Department of Defense Identifier<\/td>\nDefined by the United States Department of Defense. This tag data construct may be used to encode 96-bit Class 1 tags for shipping goods to the United States Department of Defense by a supplier who has already been assigned a CAGE (Commercial and Government Entity) code<\/td>\n<\/tr>\n
\u00a0ADI<\/td>\n\u00a0Aerospace and Defense Identifier<\/td>\n\u00a0Used by the aerospace and defense sector for the unique identification of parts or items.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

[\/vc_column_text][vc_column_text]*Explanation: Note that the letter \u201cS\u201d in the term \u201cSGLN\u201d does not stand for \u201cserialized\u201d as it does in SGTIN. This is because a GLN without an extension also identifies a unique location, as opposed to a class of locations, and so both GLN and GLN with extension may be considered as \u201cserialized\u201d identifiers. The term SGLN merely distinguishes the EPC form, which can be used either for a GLN by itself or GLN with extension, from the term GLN which always refers to the unextended GLN identifier. The letter \u201cS\u201d does not stand for anything. (Source GS1.org)<\/em>[\/vc_column_text][vc_empty_space height=”30px”]

<\/div>
<\/div><\/div><\/div>[vc_row_inner][vc_column_inner width=”1\/2″][vc_btn title=”RFID Regulations” style=”outline” shape=”square” color=”warning” align=”left” i_icon_fontawesome=”fas fa-arrow-left” add_icon=”true” link=”url:https%3A%2F%2Frfid4u.com%2Frfid-regulations%2F|title:RFID%20Regulations||”][\/vc_column_inner][vc_column_inner width=”1\/2″][vc_btn title=”EPC Gen2 Reader Commands and Q Parameter” style=”outline” shape=”square” color=”warning” align=”right” i_align=”right” i_icon_fontawesome=”fas fa-arrow-right” add_icon=”true” link=”url:https%3A%2F%2Frfid4u.com%2Fepc-gen2-reader-commands-and-q-parameter%2F|title:EPC%20Gen2%20Reader%20Commands%20and%20Q%20Parameter||”][\/vc_column_inner][\/vc_row_inner][\/vc_column][\/vc_row][\/vc_section]<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"

[vc_section full_width=”stretch_row” css=”.vc_custom_1600488574564{background: #ffffff url(https:\/\/rfid4u.com\/wp-content\/uploads\/2020\/05\/Rfid4uWebsite-Background-Image-1.jpg?id=11905) !important;background-position: center !important;background-repeat: no-repeat !important;background-size: cover !important;}”][vc_row][vc_column][vc_custom_heading text=”Explore \/ RFID Basics & Resources” font_container=”tag:h5|text_align:center|color:%23ffffff” use_theme_fonts=”yes”][vc_custom_heading text=”RFID Basics – EPC Gen2 Memory” font_container=”tag:h1|text_align:center|color:%23ffffff” use_theme_fonts=”yes”][\/vc_column][\/vc_row][\/vc_section][vc_section full_width=”stretch_row” css=”.vc_custom_1588939470806{background-color: #ffffff !important;background-position: 0 0 !important;background-repeat: no-repeat !important;}” el_class=”background-position-right-bottom”][vc_row][vc_column][vc_column_text]As per How to Select a Correct RFID Tag \u2013 Standards & Mandates, this standard is officially called […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"om_disable_all_campaigns":false,"inline_featured_image":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"class_list":["post-6910","page","type-page","status-publish","hentry"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/rfid4u.com\/wp-json\/wp\/v2\/pages\/6910","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rfid4u.com\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/rfid4u.com\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/rfid4u.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rfid4u.com\/wp-json\/wp\/v2\/comments?post=6910"}],"version-history":[{"count":0,"href":"https:\/\/rfid4u.com\/wp-json\/wp\/v2\/pages\/6910\/revisions"}],"wp:attachment":[{"href":"https:\/\/rfid4u.com\/wp-json\/wp\/v2\/media?parent=6910"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}