Protocols are a certain set of rules that govern the exchange of data through a communication connection. Most widely used protocols define small data exchanges that occur millions of times a day like the Hypertext Transfer Protocol (HTTP) or File Transfer Protocol (FTP). It is fair to say that most people use protocols on a daily basis. Because RFID is built on communication exchange, there are multiple protocols specific to RFID systems. Some higher-level, complex protocols are constructed of component protocols; a common example of that is the EPC Gen2 protocol.
The EPC Gen2 protocol is comprised of other protocols like anti-collision protocols, air interface protocols, and authorization protocols – just to name a few. Each exchange of data must be defined in a protocol in order to not only comply with rules set by the FCC and other regulatory bodies, but also to gain widespread acceptance and usage. Protocols can be created by a company a manufacturer, or a committee, but must be approved by a governing body to be used.
Industry Specific Protocols
Because the popularity of RFID tracking is becoming more widespread, industries as a whole are starting to use RFID and are invested in creating standards and protocols specific to their use cases. They also have broad applications which will foster easier data exchange between diverse entities who do business with each other. Two common examples of this are the ATA protocol created for the transportation industry, and the AAR protocol created for the railway industry.
The ATA protocol was created for the transportation industry; it was set by the American Trucking Association or (ATA) who created a standard to define and set protocols for using RFID in the industry. The ATA protocol defines the way that the communication will take place between tag and reader, while the standard defines items like memory allocation and security methods.
Industries like these create standards and protocols in order to create specifications to work toward universal adoption. This allows users from all across the industry to read RFID tags and find tracking information in the same uniform way, and, in this case, there is the added benefit of cost competition between RFID vendors.
Added Benefit: Ease of use, and Potential Widespread Adoption
TransCore’s eGo & SeGo Protocols
TransCore, an RFID manufacturer that specializes in Automatic Vehicle Identification (AVI) and tolling applications, owns two specific protocols that can provide benefits to automotive applications. eGo and SeGo are two protocols under ISO 18000-6B that are currently used in applications like access control, tolling, and AVI. SeGo – also known as “SuperEgoTM”, differs from eGo in that it has higher tag-to-reader data exchange rates.
Both of these protocols provide advanced security procedures to customers that ensure a tag’s authenticity while preventing data corruption and/or alteration. In addition, tag cloning, spoofing, copying, or duplicating is prevented1. Because vehicles are high-cost assets, these advanced security techniques are valued in AVI applications. In addition, these tags offer 3x the amount of read/write memory than standard RFID tags – up to 2048 bits.
Added Benefit: Advanced Security Measures, and Increased Memory
The Wiegand Protocol is another example of a custom protocol that can be used for added benefits. Wiegand is built upon the Wiegand effect, discovered by John R. Wiegand, which uses wires and magnetic properties to encode and decode cards. Because this can be used with RFID, and not just magnetic key cards – a protocol was created to describe the communication between tag and reader with Wiegand capabilities. The most common use for a Wiegand system is in electronic access systems to enter gates or buildings.
In order to setup an electronic access system using RFID with doors, locks, and gates, the readers most likely will need to have Wiegand output capabilities. Wiegand output capabilities on RFID readers are similar to GPIO abilities in that they provide information to other Weigand protocol compatible accessories like control systems for gates or magnetic locks for door entry. The RFID tags used in the system will also have to be programmed with Wiegand specific coding.
Added Benefit: Enable Use with Wiegand systems/devices
Reader manufacturers usually offer software Application Program Interfaces (APIs) for RFID readers so that custom software can be developed by end users to integrate the reader into their business processes. Reader manufacturers may also provide Software Development Kits (SDKs) which provide sample code examples and other helpful documentation to speed up the development and integration process of RFID readers into their environment.
Two Gen2 interfaces exist that can help users integrate directly with RFID readers and start reading and writing as well as building custom applications.
API – Application programming interfaces are provided by reader manufacturers and the functions of each may vary. The primary disadvantage to using an API to build custom software is if the application changes to a reader made by another manufacturer. If this occurs, then the code will need to be modified using the new manufacturer’s API commands.
ALE – Application level events specifies an interface that is basically a starting point for creating and writing custom software. It gives users filtered and consolidated data capture information for physical events and other related data.2
Other custom interfaces exist on the market that provide added benefits, such as Kathrein’s KRAI Interface.
Kathrein’s KRAI Interface
Kathrein is one of the few companies that created an interface that works through the reader to manipulate connected, smart RFID antennas. The KRAI, or Kathrein RFID Antenna Interface, is a selectable option when purchasing certain Kathrein manufactured antennas and readers. The KRAI interface actually takes the place of choosing a polarization – whether RHCP, LHCP, or linear polarization that can be horizontal or vertical.
This configurable reader deployment is due to the innovative way that the reader and antenna modules communicate. Working together, a KRAI reader and antenna toggle between the four different polarization methods and then choose (through internal testing) which is best suited for the read area. This unique feature allows for the optimum antenna polarization and changes depending on the site performance requirements.
On one specific KRAI antenna, the Wide Range UHF RFID Antenna, the interface allows the antenna to switch between three read fields in order to enable coverage in specific areas. This antenna is typically used for logistics, AVI, and general portal applications. This vendor specific interface provides abilities that can greatly increase the success of an application.
Added Benefits: Optimized Antenna Polarization / Optimized Read Field
For more information on RFID Protocols and Interfaces, please comment below or contact us.
1 www.transcore.com. In reference to their eGo and SeGo products
2 http://www.gs1.org/ale . Application Level Events