• 中文
  • 日本の
  • 한국어
  • España
  • American
收缩
Home » News & Knowledge» RFID & IOT Knowledge
News & Knowledge
RFID & IOT Knowledge
What is RFID middleware
4/18/2018 1:38:42 AM / Editor - yoyo / Source - rfid4u

RFID middleware is a radio frequency identification (RFID) software, between readers and business/business applications. Middleware has several functions that play a major role in the operation and management of RFID systems. This middleware not only manages RFID readers and printers, communicates between these devices and your business applications, but also manages, filters, summarizes, and understands data from RFID tags.


Due to the large amount of data from RFID tags (think thousands or thousands of tags are read almost simultaneously at thousands of times), radio frequency identification (RFID) systems require a new kind of middleware and traditional integrated middleware. Traditional middleware is mainly used to connect different applications (internal and external) to the enterprise in order to:

  • Use different transport protocols to route data

  • Translate data to different formats

  • Web Services


RFID-middleware.jpg


RFID middleware functional requirements

There are several requirements for RFID middleware, such as:

  • Effective ability to interact with various databases

  • Whether manufacturers include RFID readers, RFID printers/encoders, sensors and other devices, any AIDC device can be integrated.

  • It must manage devices from central and distributed locations and/or through the cloud and must be manageable regardless of the location of the system.

  • The most important is interface with various enterprise application programs such as Supply Chain Management (SCM), Warehouse Management System (WMS), and Enterprise Resource Planning (ERP).

  • Modular architecture, scalable and easy to upgrade

  • Provide platform transparency to mask the heterogeneity, to achieve the exchange between different platforms (such as different hardware (PC, Mac, Solaris, etc.) and operating system (Linux, Unix, Windows, Apple)). One

  • Supports Radio Frequency Identification (RFID) standards and provides future standards.


RFID middleware EPCGLOBAL specification

The EPCglobal community, which includes many technology vendors and end-users who design and deploy RFID technology and develop RFID middleware, has developed specifications for the interface between standardized RFID tags, RFID readers, and enterprise systems. There are four main criteria: Low-Level Reader Protocol (LLRP), Discovery Configuration and Initialization (DCI), Reader Management (RM), and Application-Level Event (ALE) standards.


LLRP

The LLRP standard specifies the interface between the RFID reader and the client. This protocol is called a low-level protocol because it controls RFID air protocol operation timing and access to air protocol command parameters.


DCI

The DCI standard specifies the interface between the RFID reader and the access controller and its operating network. The standard is designed to specify the operation of the reader and the client so that the reader and the client can use the network to which they are connected to communicate with other devices, exchange configuration information and initialize the operation of each reader.


RM

The current RM standard describes the wired protocol used by the management software to monitor the operating status and health of RFID readers that comply with EPCglobal standards. The reader management protocol specifies the interaction between the device that can interface with the tag and the management software.


ALE

The ALE standard states that for customers to specify, in a high-level, declarative way, what kind of electronic product code (a means of EPC) data they are interested in is that there is no governing implementation. It provides a standardized format for reporting cumulative, filtered EPC data that is largely independent of the source or processing of EPC data.


RFID middleware has an irreplaceable position in RFID systems. Even if its functionality is sometimes taken over by the system application, the middleware ends and the user application is not explicitly described when it starts. All tasks are still part of the system and data flow is still handled internally.



You May Like - News video:
You May Like - News:

Product Related With This News
Application Related With This News