WO2011160341A1

WO2011160341A1 - Reader driver device, system and method based on llrp (low-level reader protocol)

Info

Publication number: WO2011160341A1
Application number: PCT/CN2010/076960
Authority: WO
Inventors: 陆娜; 刘万立; 朱睿
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-06-21
Filing date: 2010-09-15
Publication date: 2011-12-29
Also published as: CN102289636A; CN102289636B

Abstract

A reader driver device, a system and a method based on a LLRP (Low-level reader protocol) protocol are provided, wherein, the reader driver device based on LLRP protocol comprises a base interface, an extension interface and a communication interface. The base interface is configured to interact with upper layer application about LLRP base operation messages. The extension interface is configured to interact with upper layer application about LLRP extension operation messages. The communication interface is configured to implement the message interaction between the base interface or the extension interface and the reader. The device is convenient to re-develop the reader based on LLRP protocol, reduces the development cost obviously, and improves the development efficiency and flexibility.

Description

Reader driving device, system and method based on LLRP protocol

Technical field

The present invention relates to the field of RFID (Radio Frequency Identification), and more particularly to a reader driving device, system and method based on LLRP (Low-level reader protocol) protocol.

Background technique

RFID systems typically include a reader (Reader), an electronic tag (TAG), and an upper application. The reader is a radio frequency tag reading and writing device, which is an information control and processing center of the RFID system, and is used for transmitting read and write commands to the electronic tag through the spatial channel; the electronic tag receives the read/write command and then responds as necessary, and the reader is also from the upper layer. The application obtains the data written to the electronic tag, or reports the data read from the electronic tag to the upper application. In general, the reader interacts with the upper application through a specific command format or a contracted protocol, which is implemented by an API (Application Program Interface) between the reader and the upper application. The API interface between most readers and the upper application uses RID (Reader Interface Driver: Reader Interface Driver or Reader Driver) to implement link control of the reader and basic operations such as reading and writing. The RID will respond to the corresponding information. The format encapsulated into a DLL (Dynamic Link Library) is provided to the upper application for development. Since the communication protocol between the reader and the upper application is not completely unified, different reader vendors generally define their own APIs, so readers provided by different device vendors need to use a specific RID to implement the interface driver. Although these interface drivers provide device access, they may have incompatible control modules, command parameters, and even support different air interface protocols, so they cannot be used universally. Moreover, when the driver is updated, the upper application is also upgraded. If the system uses products from different vendors, it will obviously increase maintenance costs.

The introduction of the LLRP protocol provides a common interface for reader integration. It provides control over air interface operations and air interface protocol command parameters, enhances access to lower-level reader operations, and resolves the gap between readers and upper-layer applications. The communication protocol cannot be completely unified. In addition to the current support for the EPC (Electronic Product Code) protocol, the LLRP protocol has certain scalability to support other possible air interface protocols. However, the user performs the reader on the LLRP protocol. The premise of application development is to understand the LLRP protocol and the EPC protocol in depth, and the development complexity is high, which makes it difficult for users who need only simple secondary development of the reader. Summary of the invention

The main technical problem to be solved by the present invention is to provide a reader driving device, system and method based on LLRP protocol which are easy to realize secondary development of a reader.

In order to solve the above technical problem, the present invention provides a reader driving device based on the low-level reader/writer standard LLRP protocol, which comprises a basic interface, an extended interface and a communication unit;

The basic interface is configured to perform interaction with the upper layer application for the LLRP basic operation message; the extended interface is set to perform interaction with the upper layer application for the LLRP extended operation message; the communication unit is configured to implement the basic interface or the extended interface Information interaction between readers.

Further, the device further includes a message processing unit, where the message processing unit includes an encoding module and a decoding module;

The encoding module is configured to transmit an LLRP basic operation message from the base interface or an LLRP extended operation message from the extended interface into a bitstream format and transmit the format to the communication unit;

The decoding module is configured to convert the LLRP basic operation message or the LLRP extended operation message from the communication unit into a message format and transmit to the base interface or the extension interface accordingly.

Preferably, the message processing unit further includes a buffer area configured to store an LLRP basic operation message or an LLRP extended operation message from the communication unit, and provide an LLRP basic operation message or an LLRP extended operation message to the decoding module .

Preferably, the message processing unit further includes a queue processing module, which is configured to add the LLRP basic operation message or the LLRP extended operation message that is completely decoded by the decoding module to the message queue, and then provide the corresponding basic interface or extended interface.

The message processing unit further includes a message lookup module configured to: after finding a specific LLRP basic operation message or an LLRP extended operation message from the message queue, provide the corresponding basic interface or extended interface. Further, the extension interface includes a message reading module, a parsing module, and an extended operation module. The message reading module is configured to read an LLRP extended operation message in an extensible markup language XML format from an upper layer application, and send the message to the office. The parsing module; and the LLRP extended operation message in XML format forwarded by the parsing module is provided to the upper layer application;

The parsing module is configured to convert the LLRP extended operation message in the XML format into a message format, and forward the message to the corresponding extended operation module; and parse the LLRP extended operation message of the message format into an XML format, and forward the message to the Message reading module

The extended operation module is configured to forward the LLRP extended operation message of the message format to the communication unit; and receive an LLRP extended operation message from the message format of the communication unit, and forward the message to the parsing module.

The extended operation module includes at least one of a reader operation RO rule module, an access operation AO rule module, a configuration module, and a fourth notification module;

The RO rule module is configured to forward the RO rule message of the message format from the parsing module to the communication unit; and forward the RO rule message of the message format from the communication unit to the parsing module;

The AO rule module is configured to forward the AO rule message from the message format of the parsing module to the communication unit; and forward the AO rule message of the message format from the communication unit to the parsing module;

The configuration module is configured to forward the rule configuration message of the message format from the parsing module to the communication unit; and forward the rule configuration message of the message format from the communication unit to the parsing module;

The reporting module is configured to forward the reporting rule message of the message format from the parsing module to the communication unit; and forward the reporting rule message of the message format from the communication unit to the parsing module.

Further, the device further includes a reader management interface, and the reader management interface includes a reader open module and a reader close module;

The reader open module is configured to open the communication unit by setting a corresponding parameter object, and the reader close module is set to close the communication unit. And, the reader management interface further includes a link listening module configured to listen to the reader in a reader client mode.

The reader management interface also includes a link detection module configured to detect a link status of the reader.

The present invention also protects a reader control system based on the LLRP protocol, including a reader, an upper layer application, and a reader driver device based on the LLRP protocol, the reader driving device including a base interface, an expansion interface, and a communication unit;

The present invention also protects a reader-driven method based on the LLRP protocol, the method comprising: performing interaction between an LLRP basic operation message and an LLRP extended operation message between an upper layer application and a base interface and an extended interface of the reader driving device; as well as

The basic interface or the extended interface exchanges information with the reader through the communication unit of the reader driving device.

Further, before performing the interaction between the LLRP basic operation message and the LLRP extended operation message, the method further includes: the step of the reader driving device establishing a link with the reader in any one of the following manners:

In the serial port mode, the upper application calls the reader management interface, and sets the corresponding parameter object in the reader open module to the serial port parameter;

In the reader server mode, the upper application calls the reader management interface, and sets the corresponding parameter object in the reader open module to the IP information of the reader that needs to be linked;

In the reader client mode, the upper application calls the reader management interface, and listens to the reader through the link listening module, waiting for the reader to build a link.

Further, the specific manner of the interaction is:

In the downstream direction, the reader driver will perform the basic operation of the LLRP from the upper application. The LLRP extended operation message is converted into a format of the bit stream, and the bit stream is transmitted to the reader;

In the upstream direction, the reader driver converts the LLRP basic operation message or the LLRP extended operation message from the reader into a message format and provides it to the upper layer application.

The beneficial effects of the present invention are as follows: The RID and the driving method based on the LLRP protocol provided by the present invention enable the user to understand the complex LLRP protocol without having to deeply understand the complex LLRP protocol, and only need to invoke the corresponding interface to realize the extended service of the reader through simple information interaction. The basic operation business facilitates secondary development of the reader, which significantly reduces development costs and improves development efficiency and flexibility compared with the prior art.

The invention can also control the link state of the reader, and interact with the reader through various communication modes, and can be widely applied to various work scenarios. BRIEF abstract

1 is a schematic diagram of a reader control system based on the LLRP protocol according to an embodiment of the present invention; FIG. 2 is a flow chart of communication based on the LLRP protocol according to an embodiment of the present invention;

Figure 3 is a flow chart of the link of the reader as a client;

Figure 4 is a flow chart of the link of the reader as a server;

FIG. 5 is a flowchart of implementing queue processing of an uplink message according to the present invention;

6 is a flowchart of a process for finding a specific message according to the present invention;

Figure 7 is a decoding flowchart of the present invention;

8 is a flow chart of obtaining a complete frame message in a decoding process;

Figure 9 is a flow chart of the encoding of the present invention. Preferred embodiment of the invention

The present invention will be further described in detail below with reference to the accompanying drawings.

The invention provides a driving device and a method for realizing data interaction between a reader and an upper layer application through an LLRP protocol, which can support an LLRP basic operation message between a reader and an upper layer application. LLRP extends the transmission of operational messages.

Embodiment 1:

Referring to FIG. 1, the reader control system based on the LLRP protocol of the present invention includes an upper application 10, a reader 20, and a reader driving device (referred to as RID) 30.

Among them, the upper application 10 can call different interfaces in the reader driving device 30, thereby implementing reader link control, basic operation control, and extended operation control. For example, reader link control includes opening the reader, turning off the reader, detecting the link, and listening to the link in the reader server mode. The basic operation control includes controlling the reader to read, write, count, lock, and kill the electronic tag. Basic services such as dead, query basic configuration, update basic configuration, and acquisition capabilities; extended operational controls include RO (READER OPERATION) rules for controlling readers, AO (ACESS OPERATION) rules, configuration rules, reporting rules , rule management, etc., can be used to achieve secondary development of the reader 20.

The reader 20 includes an LLRP primitive interface 21 that supports the LLRP protocol, which is arranged to interact with the RID 30 for information.

The RID 30 includes a reader management interface 31, a base interface 32, an extension interface 33, a message processing unit 34, and a communication unit 35. The reader management interface 31, the base interface 32, and the extension interface 33 all implement corresponding operation control according to the call of the upper layer application 10; the communication unit 35 is configured to implement the basic operation of the LLRP between the base interface 32 or the extension interface 33 and the reader 20. Messages or LLRP extend the interaction of operational messages and other data information.

The reader management interface 31 is configured to manage the link status of the reader 20, including a reader open module 311, a reader close module 312, a link listening module 313, and a link detection module 314. When the upper application 10 interacts with the reader 20, the reader open module 311 or the reader close module 312 is respectively configured to receive the opening or closing of the communication unit 35 to establish a link or disconnect link with the reader 20.

The communication mode of the RID 30 includes a serial port mode or a network port mode. When the reader 20 and the RID 30 communicate in the serial port mode, the upper layer application 10 calls the reader management interface 31, and sets the corresponding parameter object in the reader open module 31. For the serial port parameter, the RID 30 can open the serial port of the communication unit 35 and establish a link with the reader 20. After the link is completed, the reader closes the module 312 to disconnect and read. A link to the reader 20.

The network port mode includes a reader server mode and a reader client mode. In the reader server mode, after the reader 20 is started, the upper application 10 calls the reader management interface 31 in the RID 30, and sets the corresponding parameter object in the reader open module 311 to the IP of the reader 20 that needs to be linked. The RID 30 can open the network port of the communication unit 35 to implement the link with the reader 20. After the link is completed, the upper application 10 can call the reader close module 312 to disconnect the link. In the reader client mode, the upper application 10 calls the reader management interface 31, listens to the reader 20 by the link monitoring module 313, and waits for the reader 20 to establish a chain. After the link is completed, the link monitoring disconnection and reading can be stopped. The link to the device 20.

The link detection module 314 is configured to detect the link status of the reader 20 in real time or periodically during the link process, thereby determining the number of readers 20 currently linked with the upper application 10, and whether each reader 20 is normally linked with the upper application 10. If a reader 20 has disconnected the link, the upper application 10 can be reported. Preferably, the heartbeat detection mode is used, that is, the link detection module 314 periodically returns the heartbeat information of the reader 20 during the link process, for example, the heartbeat interval time defaults to 5s, and if the heartbeat information cannot be received within 10 seconds, the reader 20 is considered to be disconnected. Linking, the link detection module 314 can also periodically send heartbeat information to the reader 20 and wait for a response.

The base interface 32 is configured to perform an interaction of the LLRP basic operation message with the upper layer application 10, thereby controlling the basic service of the reader 20. The LLRP basic operation message includes various messages based on the LLRP protocol, such as writing a label, reading a label, checking a label, locking a label, killing a label, querying a basic configuration, and updating a basic configuration interface, for example, including multiple RO rule messages, AO rule messages, and the like. . After receiving the call of the upper layer application 10, the basic interface 32 usually needs to perform several message interactions with the reader 20 to implement a basic service, and the basic interface 32 encapsulates the parameters in each message and provides the upper layer application 10 . At present, there are two main types of UHF tags: ISO18000-6B protocol tag and EPC C1G2 (ISO18000-6C) protocol tag. ISO18000-6B protocol is the communication protocol between UHF tag and reader introduced by ISO/IEC organization. The EPC C1G2 protocol differs in some key technologies such as physical layer data encoding, modulation mode, and anti-collision algorithm; depending on the tag type, the base interface 32 can implement basic service operations independently for the two tags.

The LLRP basic operation message is sent in the downlink direction mainly in the Message format, and after being encoded and converted into a bit (output) stream, the LLRP basic operation message is exchanged with the reader 20 through the communication unit 35; In the uplink direction, the LLRP basic operation message in the bit stream format is decoded, converted into a Message format, and the extracted result is output to the upper layer application 10.

The extension interface 33 is configured to perform an interaction of the LLRP extended operation message with the upper layer application 10, thereby controlling the extended service of the reader 20. The LLRP extended operation message includes controlling the RO rule, the AO rule, the configuration rule, the report rule, etc. based on the LLRP protocol. The various messages generally include only one RO rule message, AO rule message or other rule message. After receiving the call of the upper application 10, the extended interface 33 usually only needs to perform an information interaction with the reader 20 to implement an extended service, which is usually used to independently set a certain parameter, for example, for a certain RO rule. Add, delete, start, stop, activate, etc., report rule messages are used to obtain report messages returned by the reader 20, and the like. The LLRP extended operation message is sent in the downlink direction mainly in an XML (Extensible Markup Language) file format, first parsed into a Message format, and then encoded into a bit stream, and then transmitted to the reader 20 through the communication unit 35; The LLRP basic operation message in the bit stream format is decoded and converted into a Message format, and then the generated XML file is reported to the upper layer application 10.

The extension interface 33 includes a message reading module 331, a parsing module 332, and a plurality of extended operation modules.

333.

In the downlink direction, the message reading module 331 is configured to read the LLRP extended operation message in the XML format from the upper layer application 10 and send it to the parsing module 332. In the uplink direction, it is set to the XML format forwarded by the parsing module 332. The LLRP extended operation message is provided to the upper layer application 10.

In the downlink direction, the parsing module 332 is configured to convert the LLRP extended operation message in XML format into a Message format and forward it to the corresponding extended operation module 333. In the uplink direction, it is configured to parse the LLRP extended operation message in the message format. The format is XML and forwarded to the message reading module 331.

In the downlink direction, the extended operation module 333 is configured to forward the LLRP extended operation message in the Message format to the communication unit 35; in the uplink direction, it is further configured to receive the LLRP extended operation message in the Message format from the communication unit 35, and forward the message. The parsing module 332 is provided.

The extended operation module 333 includes at least one or more of an RO rule module, an AO rule module, a configuration module, and a report module, and controls RO rules, AO rules, configuration rules, report rules, and the like, respectively. Specifically, for the RO rule message, the AO rule message, and the allocation An LLRP extended operation message, such as a rule message, a report rule message, and the like, the RO rule module is configured to forward the message rule RO rule message from the parsing module 332 to the communication unit 35, and also set the message format RO from the communication unit 35. The rule message is forwarded to the parsing module 332; the AO rule module is configured to forward the AO rule message in the Message format from the parsing module 332 to the communication unit 35, and further set to forward the AO rule message in the Message format from the communication unit 35 to the parsing The module 332 is configured to forward the rule configuration message of the Message format from the parsing module 332 to the communication unit 35, and further set to forward the rule configuration message of the Message format from the communication unit 35 to the parsing module 332; The report rule message of the Message format from the parsing module 332 is forwarded to the communication unit 35, and is further configured to forward the report rule message of the Message format from the communication unit 35 to the parsing module 332.

The message processing unit 34 is configured to perform corresponding codec on the LLRP basic operation message or the LLRP extended operation message, including the encoding module 341, the decoding module 342, the buffer area 343, the queue processing module 344, the message lookup module 345, and the like.

In the downstream direction, the encoding module 341 is arranged to transmit the LLRP basic operation message from the Message format of the base interface 32 or the LLRP extended operation message of the Message format from the extended interface 33 into a bit stream format for transmission to the communication unit 35.

In the upstream direction, the decoding module 342 is arranged to convert the bit stream from the communication unit 35 into an LLRP basic operation message or an LLRP extended operation message in the message format and forward it to the base interface 32 or the extension interface 33 accordingly. The Message based on the LLRP protocol is mainly composed of a parameter and a field. The decoding process will be described in detail below with reference to FIGS. 6 to 8.

In the upstream direction, the buffer area 343 is set to store the LLRP basic operation message or the LLRP extended operation message from the bit stream format of the communication unit 35, and perform reception processing in accordance with the corresponding reception state and then transmit to the decoding module 342. The receiving status of the message in the buffer area 343 includes three states: READY, FRAME_ERROR, NEED_MORE, etc., which respectively represent the receipt of a complete frame message, receiving error, and need to continue receiving.

The queue processing module 344 is arranged to add the LLRP basic operation message or the LLRP extended operation message that is completely decoded by the decoding module 342 to the message queue, and to the base interface 32 or the extension interface 33 in the order of the message queue.

The message lookup module 345 is configured to look up a specific LLRP basic operation from the message queue. The message or LLRP extended the operation message and provides it to the corresponding base interface 32 or extension interface 33, which can be searched according to the message type or ID number, and the message is deleted from the message queue after the search is completed. For example, RID 30 sends an AddROSpec message to reader 20, and after receiving 20, it returns an AddROSpecResponse message, and RID 30 needs to find the AddROSpecResponse message from the message queue. If the ID number of the AddROSpecResponse message is the same as the ID number of the AddROSpec, it is judged that the response message of the AddROSpec is found, and after the AddROSpecResponse message is extracted to the base interface 32 or the extended interface 33, the message is deleted from the message queue.

The present invention also protects a reader-driven method based on the LLRP protocol. The upper layer application 10 and the reader 20 implement the interaction between the LLRP basic operation message and the LLRP extension operation message through the RID 30 described above. Specifically, after the reader 20 is linked with the RID 30, in the downlink direction, the upper layer application 10 calls the corresponding interface of the RID 30, converts the LLRP basic operation message or the LLRP extended operation message into a bit stream format, and transmits the bit stream to the bit stream. The reader 20; in the uplink direction, the RID 30 converts the LLRP basic operation message or the LLRP extended operation message from the bit stream format of the reader 20 into a Message format and provides it to the upper layer application 10 through a corresponding interface.

As shown in FIG. 2, an embodiment of the present invention is based on a communication flow of the LLRP protocol, and the RID 30 is used to control the reader 20 to implement an inventory operation by using an RO rule, including the following steps:

Step S201: The RID 30 establishes a link with the reader 20. During the linking process, the communication mode of the communication unit 35 can be set to the serial port mode or the network port mode, and the network port mode includes the reader server mode or the reader client mode. After the link is successful, the upper application 10 can also invoke the basic interface 32 of the RID 30 to query and update the basic configuration of the reader 20, including antenna power, antenna in-position detection, antenna status query, pre-reverse rate, coding type, modulation mode, Common parameters such as communication type parameters, protocol type, device code, and fixed frequency hopping. After the configuration of the protocol type, antenna power, etc. is completed, the interaction between the LLRP basic operation message or the LLRP extended operation message can be implemented with the reader 20.

Step S202: According to the LLRP protocol standard, the RID 30 is sent through the basic interface 32.

The AddROSpec message is sent to the reader 20, indicating the addition of the RO rule. The LLRP protocol typically uses various Spec (Spec) commands to declare various parameter objects of the reader 20, each Spec command representing a rule of operation or an operation itself.

Step S203: The base interface 32 receives the AddROSpecResponse message returned by the reader 20. (ie add a RO rule response) to determine that the AddROSpec operation was successful.

Step S204: The base interface 32 sends an EnableROSpec message to the reader 20 indicating that the RO rule is activated.

Step S205: The base interface 32 receives the EnableROSpecResponse message returned by the reader 20 to determine that the EnableROSpec operation is successful.

Step S206: The base interface 32 sends a StartROSpec message to the reader 20 instructing the reader 20 to begin performing an inventory operation based on the specific parameters in the RO rule.

Step S207: The base interface 32 receives the result of the inventory operation returned by the reader 20, and provides the result of the inventory operation to the upper layer application 10.

Step S208: The base interface 32 sends a StopROSpec message to the reader 20 indicating that the RO rule is stopped.

Step S209: The base interface 32 sends a DeleteROSpec message to the reader 20, indicating that the RO rule is deleted.

As shown in FIG. 3, when the RID 30 works in the reader client mode, the link process of the reader 20 as a client includes the following steps:

Step S301: The RID 30 starts the link monitoring module 313 to listen to the reader 20. The link monitoring module 313 first calls the Windows network programming interface WSAStart to initialize Winsock, thereby creating a socket function.

Step S302: Call the socket function to create a listener.

Step S303: Binding the interception to the communication object specified by the socket function.

Step S304: Calling a listener (listen) to wait for a link.

Step S305: Call accept (accept) to accept the link, and generate a session socket.

Step S306: The send function (send ( )) and the receive function (recv ( )) are called to talk with the reader 20.

Step S307: After the link is completed, the close socket is called to close the socket, and the reader 20 is stopped.

As shown in FIG. 4, when the RID 30 operates in the reader server mode, the reader 20 serves as a service. The link process of the end includes the following steps;

Step S401: RID 30 starts the reader to open the module 311, and the reader opens the module 311 to first call the Windows network programming interface WSAStart to initialize Winsock, thereby creating a socket function.

Step S402: Call a socket function to create a session.

Step S403: After the session is successfully created, a connection (connect) is invoked, and the corresponding parameter object is set to the IP information of the reader 20 that needs to be linked.

Step S403: Calling send ( ) and recv ( ) to make a conversation with the reader 20 through the communication unit 35.

Step S404: After the link is completed, the reader close module 311 calls the closesocket function to close the socket and stops the reader 20 from listening.

FIG. 5 is a flowchart of a process for implementing queue processing of an uplink message according to the present invention;

Step S501: The process starts.

Step S502: The communication unit 35 receives the bit stream format LLRP basic operation message or the LLRP extended operation message from the reader 20 through the serial port or the network port.

Step S503: The received bit stream is stored in the buffer area 343.

Step S504: Determine the status of the message. If the message status is NEED_MORE, the process proceeds to step S502 to continue receiving. If it is FRAME_ERROR, step S508 is performed, and if it is READY, step S505 is performed.

Step S505: Parsing the LLRP basic operation message in the bit stream format by the decoding module 342 or

LLRP extended the operation message, and the decoding process is shown in Figure 7.

Step S506: It is judged whether a complete message is obtained, and if yes, step S507 is performed, otherwise step S508 is performed.

Step S507: Add the parsed complete LLRP basic operation message or LLRP extended operation message to the message queue by the queue processing module 344; Go to step 502.

Step S508: Clear the buffer area 343, and proceed to step S502 to continue receiving the message.

FIG. 6 is a flowchart of a process for finding a specific message according to the present invention: Step S601: The process starts.

Step S602 The message lookup module 345 starts the exclusive message queue and searches for a message with a specific type or ID number from the message queue.

Step S603: If a corresponding specific message is found, go to step S604, otherwise go to step S606.

Step S604: Extract the corresponding specific message and correspondingly forward to the basic interface 32 or the extended interface 33, and delete the specific message from the message queue.

Step S605: Cancel the exclusive use of the message queue, and proceed to step S609.

Step S606: determining whether to traverse the entire message queue, if yes, proceeding to step S607, otherwise returning to step S602 to continue searching.

Step S607: Cancel the exclusive use of the message queue.

Step S608: The search operation may also be controlled by a certain timing mechanism. If the predetermined time is up, the process proceeds to step S609, otherwise, the process proceeds to step S602.

Step S609: The search process ends; for different services, such as inventory business, the process can also be cycled multiple times.

Figure 7 shows the decoding process of the present invention comprising the following steps:

Step S701: Start decoding.

Step S702: The decoding process of the present invention is used to convert the bit stream into a message object, and the decoding module 342 first obtains the complete data in a bit stream format. The specific acquisition process is as shown in FIG. 8.

Step S703: First parsing the frame header to obtain three parameters MessageType, MessageLength,

MessagelD, which refers to the message type, message length, and ID number of the message, respectively.

Step S704: Create a Message object according to the MessageType.

Step S705: Parse the field part of the Message object, and set the object attribute of the parameter to the corresponding value.

Step S706: Next, parse the Parameter part of the Message object. Since the Fields in the Parameter of the TLV type parameter may be a value or a sub-parameter, first determine whether the parameter type is a TLV type, if yes, go to step S707, otherwise go to step S708. Step S707: Traverse the sub-parameters, and then proceeds to step S708.

Step S708: Set an object attribute of the parameter to the corresponding value.

Step S709: Obtain a complete Parameter part of the Message object.

Step S710: The decoding process ends.

8 is a flow chart of obtaining a complete frame message in a decoding process;

Step S801: The process starts.

Step S802: After the RID 30 receives the binary bit stream, the encoding module 342 first parses the current stream length CurrentFrameLength »

Step S803: It is judged whether CurrentFrameLength is less than 10 bytes, if yes, go to step S804, otherwise, go to step S805.

Step S804: Continue to receive data until the CurrentFrameLength is greater than 10 bytes, and the process proceeds to step S805.

Step S805: When the CurrentFrameLength is greater than 10 bytes, it indicates that the frame header is received, and the analysis header obtains the total frame length TotalFrameLength.

Step S806: determining whether CurrentFrameLength<TotalFrameLength, if yes, proceeding to step S807, otherwise proceeding to step S808.

Step S807: Continue to receive until CurrentFrameLength=TotalFrameLength, and proceed to step S808.

Step S808: Obtain a complete one frame message.

Step S809: The receiving process ends.

Figure 9 is a flow chart of the encoding of the present invention.

Step S901: Encoding starts.

Step S902: The encoding module 341 first acquires a message object.

Step S903: The message header is generated according to the obtained message object.

Step S904: traverse all the message parameters to generate a binary bit stream.

Step S905: Processing the message byte stream length in the message header. Step S906: The encoding process ends.

The RID and driving method based on the LLRP protocol provided by the invention makes it unnecessary for the user to deeply understand the complex LLRP protocol, and only needs to invoke the corresponding interface, so that the extended service and the basic operation service of the reader can be realized through simple information interaction, which is convenient for the user to The secondary development of the reader significantly reduces development costs and improves development efficiency and flexibility compared to the prior art.

The invention can also control the link state of the reader, and interact with the reader through various communication modes, and can be widely applied to various work scenarios.

One of ordinary skill in the art will appreciate that all or a portion of the steps above may be accomplished by a program to instruct the associated hardware, such as a read-only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.

The above is a further detailed description of the present invention in connection with the specific embodiments, and it is not intended that the specific embodiments of the invention are limited to the description. It will be apparent to those skilled in the art that the present invention may be practiced without departing from the spirit and scope of the invention.

Industrial applicability

The LLRP protocol-based reader driving device, system and method provided by the invention enable the user to understand the complex LLRP protocol without having to deeply understand the complex LLRP protocol, and can realize the extended service and basic operation of the reader through simple information interaction. The business facilitates secondary development of the reader, significantly reducing development costs and improving development efficiency and flexibility. Moreover, the present invention can also control the link state of the reader, and perform data interaction with the reader through various communication modes, and can be widely applied to various work scenarios.

Claims

Claim

1. A reader driver device based on a low-level reader/writer standard LLRP protocol, comprising: a base interface, an expansion interface, and a communication unit;

2. The apparatus of claim 1, the apparatus further comprising a message processing unit, the message processing unit comprising an encoding module and a decoding module;

3. The apparatus according to claim 2, wherein the message processing unit further comprises a buffer area configured to store an LLRP basic operation message or an LLRP extended operation message from the communication unit, and to perform an LLRP basic operation message or An LLRP extended operation message is provided to the decoding module.

4. The apparatus according to claim 3, wherein the message processing unit further comprises a queue processing module configured to add an LLRP basic operation message or an LLRP extended operation message that is completely decoded by the decoding module to the message queue. Provided to the corresponding base interface or extended interface.

5. The apparatus according to claim 4, wherein the message processing unit further comprises a message lookup module configured to: after finding a specific LLRP basic operation message or an LLRP extended operation message from the message queue, providing the corresponding Basic interface or extended interface.

The apparatus according to any one of claims 2 to 5, wherein the extension interface comprises a message reading module, a parsing module and an extended operation module;

The message reading module is configured to: read an LLRP extended operation message in an extensible markup language XML format from an upper layer application, and send the LLRP extended operation message to the parsing module; and forward the XML forwarded by the parsing module The formatted LLRP extended operation message is provided to the upper layer application;

The extended operation module is configured to: forward the LLRP extended operation message of the message format to the communication unit; and receive an LLRP extended operation message from the message format of the communication unit, and forward the message to the parsing module.

The apparatus according to claim 6, wherein the extended operation module comprises at least one of a reader operation RO rule module, an access operation AO rule module, a configuration module, and a report module; and the RO rule module is configured to An RO rule message from a message format of the parsing module is forwarded to the communication unit; and an RO rule message of a message format from the communication unit is forwarded to the parsing module;

8. Apparatus according to any of claims 2 to 5, said apparatus further comprising a reader management interface, said reader management interface comprising a reader open module and a reader close module; the reader open module settings To open the communication unit by setting a corresponding parameter object, the reader close module is set to close the communication unit.

9. The apparatus of claim 8, wherein the reader management interface further comprises a link listening module configured to listen to the reader in a reader client mode.

10. The apparatus of claim 8, wherein the reader management interface further comprises a link A detection module configured to detect a link status of the reader.

11. A reader control system based on a low-level reader/writer standard LLRP protocol, comprising a reader, an upper layer application, and a reader driver device based on an LLRP protocol, the reader driving device comprising a base interface, an expansion interface, and a communication unit;

12. A reader driving method based on a low layer reader/writer standard LLRP protocol, the method comprising:

The upper layer application performs interaction between the LLRP basic operation message and the LLRP extended operation message respectively with the base interface and the extended interface of the reader driver;

13. The method of claim 12, wherein the LLRP basic operation message is performed and

Before the LLRP extends the interaction of the operation message, the method further comprises: the step of the reader driver establishing a link with the reader in any of the following ways:

14. The method according to claim 12, wherein the specific manner of the interaction is: in a downlink direction, the reader driving device converts an LLRP basic operation message or an LLRP extended operation message from the upper layer application into a bit stream. Formatting, and transmitting the bit stream to a reader; In the upstream direction, the reader driver converts the LLRP basic operation message or the LLRP extended operation message from the reader into a message format and provides it to the upper layer application.