JP2010287962A - Information processor, method of processing information, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information processor for decoding reception data, where start positions of parameters are undecided. <P>SOLUTION: A decoding determination section 106 determines whether reception data received by a communication section 108 are data, with which the start position of a parameter to be extracted coincides with a position defined by a prescribed rule and index decoding following the definition is possible, or data, with which the start position of the parameter differs from the defined position and the index decoding is not possible. When the index decoding is possible, a decoding section 105 performs decoding from the defined start position of the parameter to extract the parameter. When the index decoding is not possible, a detailed decoding section 102 determines the length of a data length identifier by a value of the start bit of the data length identifier disposed directly before the parameter, derives the start position of the parameter, and performs decoding from the derived start position to extract the parameter. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a technique for decoding encoded data.

The command interface of the UHF band reader / writer is defined by ISO15961.
In ISO 15961, ASN. 1 is used.
ASN. Reference numeral 1 denotes a data structure of “data type / data length / data” (further hierarchical structure in the data), and the data length and data are variable length.

On the other hand, there is OSGi as a Java (registered trademark) -based service platform capable of remotely managing embedded devices.
In order to use a device such as an RFID (Radio Frequency IDentification) tag from software compliant with OSGi, software that is controlled by specifications defined by OSGi is required.
Equinox is an Eclipse plug-in that provides a runtime and tools for implementing the OSGi specification.
In Equinox, an index is used for decoding encoded data transmitted by a reader.
This is a parameter definition for received data in advance, and the decoding module performs decoding according to the parameter definition when data is received (hereinafter, decoding based on the parameter definition is referred to as index decoding).
The parameter definition is defined by the position (index) from the beginning of the received data of the parameter data to be extracted, the length to be extracted, and the parameter type.

FIG. 3 shows an example of character string type received data.
It is assumed that data after “ID =” is parameter data (hereinafter also referred to as a parameter).
The parameter definition in this case is the definition of the fourth character from the beginning of the received data, the character string type, and an indefinite length parameter. Index decoding that decodes the data after the fourth character from the beginning of the received data and extracts the parameters. Is done.

  When implementing control software for a reader / writer conforming to ISO 15961 using Equinox, ASN. It is necessary to decode the data encoded by 1 using an index.

FIG. It is an example of the data showing the execution result of the read command of tag ID in the RFID reader which employ | adopts 1 encoding system.
The data has two parameters, the number of tags and the tag list. The number of tags is 99 and the length of the tag list data is 357 (the length of the tag list data: 357 is the lower 2 bytes of the index = 8-10 portion) "0165" in decimal notation).
Only the index = 6 of the tag number portion and the index = 10 portion of the tag ID list should be acquired as parameters.
Here, each element of FIG. 2 is as follows.
index = 0: “type” identifier representing the entire data index = 1: “data length” identifier of the entire data index = 4: “type” identifier of the tag number parameter index = 5: “data length” identifier of the tag number parameter index = 6: “Data” (parameter data) of the tag number parameter
index = 7: “Type” identifier of the tag ID list parameter index = 8: “Data length” identifier of the tag ID list parameter index = 10: “Data” (parameter data) of the tag ID list parameter
The “type” identifier is fixed to 1 byte, the “data length” identifier and the “data” are variable length.

  If there are a plurality of parameters, the list is also defined as data (index = 0 is the type of the list, index = 1 is the length of the list data, and the whole after index = 4 is the parameter).

If the index decoding is to be applied to the data shown in FIG. 2, the decoding parameter is defined as a tag number parameter from index = 6 to 1 byte as a numerical type, and from index = 10 to the end of the data as a character string type. To do.
However, as in this example, when there is a possibility that the data length included in the list becomes large, the “data length” identifier (index = 8 to 10) indicating the data length of the list or the data length of the entire data above it Since the part (index = 1 to 4) representing the variable has a variable length, the start position of the target parameter data cannot be determined, and decoding using the index cannot be performed. There is.

In this regard, Patent Document 1 is known as a conventional technique for absorbing differences in communication protocols of RFID reader / writers.
Patent Document 1 discloses a technique of converting a different communication protocol for each reader into a common protocol that can be used from an application system.
However, Patent Document 1 does not mention a specific protocol processing method.

Special table 2008-524742

  The present invention has been made in view of the above-described problems, and includes variable-length data elements. Therefore, since the starting position of parameter data is indefinite, it is possible to decode received data that cannot be index-decoded. The main purpose is to realize a decoding technique.

An information processing apparatus according to the present invention includes:
The encoded parameter data and an encoded data length identifier indicating the data length of the parameter data are included, the parameter data is arranged following the data length identifier, and the start position of the parameter data A data receiving unit for receiving indefinite received data in which the data length of the data length identifier can be determined by the value of the first bit of the data length identifier;
Extracting the first bit of the data length identifier in the indefinite received data, determining the data length of the data length identifier based on the value of the first bit of the data length identifier, determining the start position of the parameter data, and determining And an indefinite received data decoding unit that decodes a bit string corresponding to the data length obtained by decoding the data length identifier from the start position of the parameter data, and extracts the parameter data after decoding.

  According to the present invention, since the variable length data element is included, it is possible to specify the start position of the parameter data from the value of the first bit of the data length identifier even for the reception data in which the start position of the parameter data is indefinite. And parameter data can be correctly decoded.

FIG. 3 is a diagram illustrating an example of a system configuration according to the first embodiment. FIG. 4 is a diagram showing an example of received data according to the first embodiment. The figure which shows the example of receiving data of a character string type. FIG. 3 is a flowchart showing an operation example of the server 100 according to the first embodiment. FIG. 3 is a flowchart showing an operation example of a data control unit according to the first embodiment. FIG. 11 shows an example of a decoding determination pattern according to the third embodiment. FIG. 6 is a diagram showing an example of a decoding parameter list (parameter decoding completed) according to the first embodiment. The figure which shows the example of the decoding parameter list | wrist (parameter undecoding) based on Embodiment 1. FIG. FIG. 6 is a diagram showing an example of a control parameter list after detailed decoding according to the first embodiment. FIG. 10 is a diagram showing a system configuration example according to a fifth embodiment. FIG. 20 is a diagram showing an example of an input file according to the fifth embodiment. FIG. 10 is a diagram illustrating an example of a system configuration according to a sixth embodiment. FIG. 20 is a diagram illustrating an example of log output according to the sixth embodiment. The figure which shows the hardware structural example of the server 100 which concerns on Embodiment 1-6.

Embodiment 1 FIG.
In this embodiment, since a variable-length data element is included, the start position of parameter data (hereinafter also referred to as a parameter) is indefinite, and an apparatus that correctly decodes received data that cannot be index-decoded is provided. explain.
More specifically, in device control software that employs an index coding scheme, ASN. An apparatus that supports communication with an RFID reader that employs one encoding method, determines a data pattern to which a high-speed decoding method can be applied, and switches the decoding method to speed up data decoding processing. explain.
In the following, since variable length data elements are included, the start position of the parameter data is indefinite, and reception data that cannot be index decoded is also referred to as indefinite reception data.
On the other hand, it does not include variable-length data elements, and the start position of the parameter data matches the position (reference position) defined by a predetermined rule (ASN.1, etc.), and defines received data that can be index decoded Also called received data.

  Here, the principle that the apparatus according to the present embodiment can determine the start position of the parameter data in the indefinite reception data in which the start position of the parameter data is indefinite because it includes a variable-length data element.

  FIG. 2 is an example of received data used in the present embodiment. As described above, ASN. It is an example of the data showing the execution result of the read command of tag ID in the RFID reader which employ | adopts 1 encoding system.

In FIG. 2, the “data length” identifier (index = 5, index = 8, etc.) is composed of the first bit of the first byte being “0” or “1”, and the “data length” identifier is composed of how many bytes. It is encoded so that it can be seen.
In the example of FIG. 2, when the value of the first 1 bit is “0”, the length of the “data length” identifier is 1 byte, and when the value of the first 1 bit is “1”, the “data length” identifier It is predefined that the length is 3 bytes, the first bit of the first byte of index = 5 (“data length” identifier of the tag number parameter) is “0”, and index = 5 (tag number parameter) At the time of decoding, it can be determined that the value of the first 1 bit is “0” and the “data length” identifier of the tag number parameter is 1 byte.
Further, the first bit of index = 8 (the first byte of the “data length” identifier of the tag ID list parameter) is “1”, and therefore the “data length” identifier of the tag ID list parameter is 3 bytes. I can judge.
For this reason, even if the starting position of the parameter data is indefinite, the data length of the “data length” identifier can be determined by detecting the value of the first bit of the “data length” identifier. The starting position of the parameter data in the data can be determined.
Further, based on the value of the first bit of the “data length” identifier, the data length of the “data length” identifier is determined to decode the “data length” identifier, and the data length of the parameter data can be obtained from the decoding result, The bit string corresponding to the data length obtained by decoding the “data length” identifier from the determined starting position of the parameter data can be decoded, and the decoded parameter data can be extracted.

  FIG. 1 shows a system configuration example according to the present embodiment.

In the present embodiment, server apparatus 100 (hereinafter simply referred to as a server) is connected to application server 200 via network 500 and is also connected to RFID reader 300 via network 600.
1 shows the network 500 and the network 600, the present invention is not limited to the network, and may be a direct connection such as a serial cable.
The server 100 is an example of an information processing apparatus.

The server 100 includes four layers: a device control unit 101, a command parameter creation unit 103, a communication control unit 107, and a communication unit 108.
The device control unit 101 is realized by, for example, device control software. The application operates on the application server 200 on the network or the server 100 on which the device control software operates.
An RFID reader 300 is a device to be controlled by the device control unit 101.
The device control unit 101 controls the overall operation of the server 100 by starting / stopping issue of commands to the RFID reader 300 and notifying the received command execution result to the application.
Further, the device control unit 101 includes a detailed decoding unit 102 in addition to a part that performs device control.
Device control is to control the overall operation of the server 100, such as device activation, command issuance, and command execution result notification to an application.
Details of the detailed decoding unit 102 will be described later. The detailed decoding unit 102 is an example of an indefinite received data decoding unit.

The command parameter creation unit 103 includes a parameter encoding unit 104, a decoding unit 105, and a decoding determination unit 106.
The encoding unit 104 converts the command parameter specified by the device control unit 101 into a data string according to the command interface of the RFID reader 300.
The decryption unit 105 decrypts the command execution result received from the RFID reader 300 into a control parameter by using an index, converts the parameter into a parameter, and passes the parameter to the device control unit 101. The name “control parameter” indicates a parameter after decoding.
Decoding of control parameters using indexes defines the command execution result data used in advance as pattern data, extracts parameters from the received data according to the definition, creates a parameter list, and requires detailed decoding Decrypted data added to the list as a flag is created.
The decoding unit 105 changes operation by changing pattern data used for decoding depending on whether detailed decoding is necessary.
The decoding determination unit 106 determines whether the received data is definition reception data that can be index-decoded by the decoding unit 105 or indefinite received data that requires detailed decoding by the detailed decoding unit 102.
As described above, the decoding unit 105 is a unit that performs index decoding on the definition reception data, and the detailed decoding unit 102 is a unit that performs decoding on the indefinite reception data by a method other than index decoding. .
The decoding unit 105 is an example of a definition reception data decoding unit, and the decoding determination unit 106 is an example of a reception data determination unit.

The communication control unit 107 transmits / receives data in accordance with the communication specification of the RFID reader 300.
The communication unit 108 secures or opens a communication path according to the communication form.
The communication unit 108 is an example of a data receiving unit.

Here, the detailed decoding unit 102 will be described.
Based on the decoding result obtained by the decoding unit 105 of the command parameter creation unit 103, the detailed decoding unit 102 converts the data that requires detailed decoding into ASN. Decoding is performed as one encoded data, and the obtained parameters are listed.
More specifically, when it is determined by the decoding determination unit 106 that the received data is indefinite received data and detailed decoding is necessary, the first bit of the “data length” identifier is extracted from the indefinite received data, and “data Based on the value of the first bit of the “length” identifier, the data length of the “data length” identifier is determined to determine the start position of the parameter data, and the “data length” identifier is decoded from the determined start position of the parameter data. A bit string corresponding to the data length to be ASN. Decoding is performed based on 1, and parameter data after decoding is extracted.

  Next, the operation at the time of data reception in the server 100 will be described using the flowchart of FIG.

First, when the device control unit 101 generates a command for the RFID reader 300 using the command parameter creation unit 103 and transmits the generated command to the RFID reader 300 via the communication control unit 107 and the communication unit 108, the RFID reader 300 Some command execution result is transmitted to the server 100 as a data string.
The transmitted data is received by the communication unit 108 (data reception step).
In step 1, the communication control unit 107 cuts the received data as a command execution result for one command.
The received data shown in FIG. 2 is data after being separated in step 1.

Next, command execution result data passes to the command parameter creation unit 103.
In step 2, the command parameter creation unit 103 confirms whether the command ID data string included in the received data matches the command ID data string defined in advance. Confirm and judge.
In FIG. 2, the command ID data string is not shown, but the command ID data string is arranged at the head of the received data in FIG. 2 (before index = 0 in FIG. 2).

Next, in step 3, the decoding determination unit 106 determines whether detailed decoding is necessary.
This determination is performed by decoding a portion representing the data length of the entire received data from the received data.
In the example of the data shown in FIG. 2, the part representing the data length of the entire received data corresponds to the second and subsequent characters from the top of the data (“total data length” identifier arranged at index = 1 to 4).
This is called ASN. Decoding is performed as the data length of one encoded data.
More specifically, since the first byte of “82016A” in FIG. 2 is “82” and the first bit is “1”, it can be seen that the “total data length” is 3 bytes, and the remaining 2 bytes are “016A”. 2 indicates that the total data length of the received data in FIG. 2 is 362 (bytes).
If the data length obtained by decryption is longer than the data length of the decryption command execution result data pattern defined in advance, it is determined that detailed decryption is necessary. to decide.

If detailed decoding is not necessary, in step 4, the decoding unit 105 performs decoding using an index to create a parameter list.
Then, in step 5, the decoding unit 105 extracts parameters from the received data according to the definition of one parameter from the index list defined by the command execution result data pattern.
In step 6, the decoding unit 105 adds a flag indicating that detailed decoding is not necessary to the list. Specifically, “false” is entered in the parameter [0] column of the list.

FIG. 7 shows an example of the decoding parameter list after the processing of step 4 to step 6.
In FIG. 7, the value of the parameter [0] is false, indicating that detailed decoding is not necessary. Further, FIG. 7 shows that two parameter data of 1,000,0001 are extracted by index decoding.

On the other hand, if it is determined that detailed decoding is necessary, the decoding unit 105 of the command parameter creation unit 103 does not perform detailed decoding of parameters, and in step 7, “data type / data length / data” of the entire received data. Are all converted into byte parameters and decoded as one parameter to create a parameter list.
That is, in the data example of FIG. 2, a parameter list is created with the entire received data from the beginning to the end of the data as one parameter.

Next, in step 8, the decoding unit 105 adds a flag indicating that detailed decoding is necessary to the list.
Specifically, True is entered in the parameter [0] field in the list.

FIG. 8 shows an example of a decoding parameter list obtained by performing Step 7 and Step 8 on the data of FIG.
In FIG. 8, the value of the parameter [0] is true, indicating that detailed decoding is necessary.
Further, the value of the parameter [1] is the entire data (3082016A...) Of FIG. 2, and the entire data of FIG.

The data subjected to the first decoding (step 5 or step 7 by the decoding unit 105) is transmitted to the device control unit 101.
The operation contents in the device control unit 101 will be described with reference to the flowchart of FIG.

The device control unit 101 first passes the decoding parameter list (FIG. 8) to the detailed decoding unit 102.
Next, in step 9, the detailed decoding unit 102 extracts flag data indicating whether detailed decoding is necessary from the parameter [0] in the decoding parameter list, and determines whether detailed decoding is necessary.

  If detailed decoding is not necessary, in step 10, the detailed decoding unit 102 extracts data other than flag data (parameter [0]) indicating whether detailed decoding is necessary from the decoding parameter list, and extracts it. It is a control parameter list.

  On the other hand, if detailed decoding is necessary, in step 11, the detailed decoding unit 102 sets the byte data string of the parameter [1] in the decoding parameter list as undecoded data, as shown in steps 12 to 16. Then, the byte data string of the parameter [1] is recursively decoded from the top of the data to perform detailed decoding (indefinite received data decoding step).

  In step 12, the detailed decoding unit 102 applies ASN1. The encoded data is decoded as “data type / data length / data” from the top of the data.

In step 13, the detailed decryption unit 102 determines whether the “data type” obtained by decryption is not a simple type (character string or numeric value) but a recursive data type (nested structure data).
For example, “data type”: 30 shown in index = 0 of the data in FIG. 2 is a recursive type, “data type” shown in index = 4: “data type” shown in 02 or index = 7: 04 is a simple type.

In the case of a recursive data type (nested structure data), the detailed decoding unit 102 sets “data” obtained by decoding as undecoded data in step 14.
In the data of FIG. 2, the entire data after index = 4 is set as undecoded data.

On the other hand, in the case of a simple data type (character string or numerical value), the detailed decoding unit 102 adds “data” obtained by decoding to the control parameter list in step 15.
As described above, the “data length” identifier is encoded so that the first bit of the first byte is 0 or 1 and it is understood how many bytes the “data length” identifier is composed of.
The detailed decoding unit 102 determines the data length of the “data length” identifier based on the value of the first bit of the “data length” identifier, decodes the “data length” identifier, and determines the data length of the parameter data from the decoding result. A bit string for the data length obtained by decoding the “data length” identifier from the start position of the determined parameter data can be obtained, the parameter data after the decoding is extracted, and the extracted parameter data is the control parameter list Add to

  Further, after the decoding in step 15, the detailed decoding unit 102 determines in step 16 whether or not undecoded data remains after the decoded data, and if undecoded data remains Returns to step 12 and further decrypts the undecoded data.

The detailed decoding unit 102 repeats the processing of step 12 to step 16 to extract parameter data and create a control parameter list.
FIG. 9 shows an example of a control parameter list created by the detailed decoding performed by the detailed decoding unit 102.
FIG. 9 shows the result of performing detailed decoding on the data of FIG. 2, and “99”, “00000001”, etc., which are the parameter data of FIG. 2, are shown.

  Thus, according to the present embodiment, the start position of the parameter data can be identified from the value of the first bit of the data length identifier even for indefinite received data in which the start position of the parameter data is indefinite, Parameter data can be correctly decoded.

  Further, in this embodiment, by switching the decoding process depending on the data pattern, it is possible to decode variable-length data such as when the number of tags is large, and at the same time, if the data is a simple pattern, it is fast. By applying the decoding method, a higher-speed decoding process can be realized.

As described above, in the present embodiment, the device control unit, the command parameter creation unit, the communication control unit, and the communication unit are provided.
The command parameter creation unit is a device control apparatus including a decoding determination unit and a decoding unit, and a device control unit including a detailed decoding unit,
The communication unit establishes a communication path with the RFID reader,
The communication control unit transmits data according to the command interface of the RFID reader to the RFID reader, receives the command execution result transmitted by the RFID reader in response to the command,
The decoding determination unit of the command parameter creating unit compares the data length obtained by decoding the portion representing the data length of the entire data from the received data with the length of the command execution result in the shortest pattern, thereby making the variable length Determine whether it is necessary to perform two-stage decoding as hierarchical data,
The decoding unit of the command parameter creation unit specifies the position, length, and data type in the byte string of the data received from the device and decodes the data as a single parameter as a byte string type parameter. If it is not necessary to decode as variable-length hierarchical structure data, specify the position, length, and data type in the byte string as fixed-length data and decode it as one or more control parameters to obtain variable-length hierarchical structure data. If you need to decrypt, specify the position, length, and data type in the byte sequence, decrypt the data as a single parameter as a byte sequence type parameter,
The device control unit determines whether or not it has been decoded as a control parameter based on the decoding result of the decoding unit,
If it has been decoded as a control parameter, the decoding parameter is obtained without going through the detailed decoding unit,
If it is not decoded as a control parameter, it is decoded as one or more control parameters by decoding the byte string parameter decoded by the decoding unit of the command parameter creation unit as variable length hierarchical structure data,
The device control unit has been described with respect to a device control apparatus that performs device control using the obtained control parameters and notifies a command execution result to a higher-level application.

Embodiment 2. FIG.
As a determination method of the decoding determination unit 106, a form in which it is determined whether detailed decoding is necessary using the length of received data itself.

In the first embodiment, in step 3 of FIG. 4, the “total data length” identifier (index = 1 to 4) of the received data is decoded from the received data according to the command interface, and compared with the command execution result data pattern for decoding. Thus, it was determined whether or not detailed decryption is necessary.
On the other hand, in the present embodiment, the length of the received data itself is used for this determination, and compared with the length of the command execution result data pattern for decoding. If it is short, it is determined that decoding by an index is possible.
That is, in the present embodiment, instead of step 3 in FIG. 4, the decoding determination unit 106 measures the data length of the entire received data, and the measured data length of the entire received data is a predetermined data length (decoding Data length of the command execution result data pattern) or less, the received data is determined to be defined received data and detailed decoding is determined to be unnecessary, and the measured data length of the entire received data is a predetermined data length (decoding command). If it exceeds the data length of the execution result data pattern, the received data is determined as indefinite received data, and it is determined that detailed decoding is necessary.

  In this method, if the received data contains redundant data that should not be included originally or if the command interface is not followed, correct determination cannot be made, but it is not necessary to perform decoding of the data length. Judgment processing can be performed.

  As described above, in the present embodiment, the decoding determination unit compares the length of the received data with the length of the shortest pattern of the command execution result to determine whether it is necessary to perform two-stage decoding as variable-length hierarchical structure data. Explained to judge.

Embodiment 3 FIG.
Further, as a determination method of the decoding determination unit 106, a form in which it is determined whether or not detailed decoding is necessary using a decoding determination pattern.

FIG. 6 shows an example of decoding determination according to the present embodiment.
The upper row is the received data, and the middle row is the decoding determination pattern.
The decryption determination pattern is a data string created so as to have the shortest command execution result. In 1 encoding, the data length is encoded to be longer than 1 byte when the first bit is 1, and therefore the byte corresponding to the data length is set to 1.
The result of ANDing the input data and the coding determination pattern is the lower part of FIG.
If the calculation results are all 0, it can be determined that there is no need for detailed decoding.
In the example of FIG. 6, since “8” is included in the AND operation result in the lower stage, detailed decoding is necessary.
In the example of FIG. 6, the decoding judgment pattern is applied to the entire received data to obtain an AND operation result for the entire received data. However, the “total data length” identifier (index = 1 to 1) of the received data is obtained. The decoding determination pattern may be applied only to the bit value of 4), and it may be determined that detailed decoding is not necessary if the AND operation result for the “total data length” identifier is all zero.

  As described above, according to the present embodiment, there is an effect that the decoding determination can be performed by a relatively high speed processing by the bit operation processing.

  As described above, in this embodiment, whether the decoding determination unit needs to perform two-stage decoding as variable-length hierarchical structure data by comparing the reception determination data with the decoding determination mask pattern for each command set in advance. Explained to determine.

Embodiment 4 FIG.
Unlike the first to third embodiments described above, this embodiment describes a configuration without the decoding determination unit 106.

If there is no decryption determination unit 106, the received data is passed directly from the communication control unit 107 to the decryption unit 105 of the command parameter creation unit 103, so there is no processing corresponding to step 3 in the flowchart of FIG. 7 targets.
Since the decryption determination is not performed, the determination result data in step 8 is not added, the determination in step 9 is not performed, and all received data is the target of step 11.
That is, in the present embodiment, whether the reception data received by the communication unit 108 is defined reception data or indefinite reception data is subject to detailed decoding, and the value of the first bit of the “data length” identifier is “ The data length of the “data length” identifier is derived, the starting position of the parameter data is derived, and the parameter data is decoded.

  As described above, in the present embodiment, there has been described that there is no decoding determination unit, and all received data is decoded in two steps as variable-length hierarchical structure data.

Embodiment 5 FIG.
When decoding using an index, it is necessary to define a data pattern and parameters in accordance with the command interface of data transmitted by the reader for each command.
In the present embodiment, an example of inputting this definition as a file will be described.

FIG. 10 shows a system configuration example according to the present embodiment.
In the present embodiment, the decoding data pattern and parameter definition are input to the decoding determination unit 106 and the decoding unit 105 as definition information.
As for the input format, what is described in a file or the like is read at the time of execution, or the definition is converted into an execution format using a code generation tool or the like, and the determination data of received data and the definition of the parameter list are created.
The decoding determination unit 106 compares the data length of the decoding command execution result data pattern described in the definition information with the entire data length of the received data obtained from the “total data length” identifier of the received data. Thus, it is determined whether or not detailed decoding is necessary.
Further, the decoding unit 105 derives the parameter data start position in the definition reception data from the reference position of the parameter data start position described in the definition information, and decodes the parameter data.

FIG. 11 shows a description example of the input file (definition information).
The first line indicates the data definition of the command execution result. This example is a definition for the InventoryTags command.
The second line indicates that the execution result pattern definition can be decoded by the index.
The third to fifth lines indicate the shortest pattern of the decryption command execution result data pattern.
The 6th to 16th lines show the decoding parameter definition.
The seventh to eleventh lines define the tag number parameter that is the first parameter. One byte from the 17th index is extracted as a parameter.
The 12th to 15th lines are definitions of the tag ID parameter that is the second parameter. The parameters from the 20th index to the end of the data are extracted as parameters.
The 17th to 21st lines are filter definitions for determining whether to use this execution result pattern definition.
Up to this point, the definition is for encoding by index.
The 23rd line indicates an execution result pattern definition when decoding by index is impossible.
The parameters are defined in the 27th to 29th lines, but the data after the index 8 are defined to be parameterized collectively.
Such a definition is described for each command necessary for device control.

  In the method according to the present embodiment, the definition can be made in accordance with the command interface of the reader, the response to the change of the command interface, and the applicability of the code can be improved.

  As described above, in the present embodiment, the decoding determination unit and the decoding unit of the command parameter creation unit input the received data pattern for each command as the setting file.

Embodiment 6 FIG.
In the present embodiment, a configuration in which the server 100 has a function of outputting a log will be described.

FIG. 12 shows a system configuration example according to the present embodiment.
In the configuration example illustrated in FIG. 12, the log control unit 109 is provided separately from each layer in order to output a log for recording the operation of the server 100.
For log setting, the operation of the log control unit 109 is set by writing in a file and reading the log output status, output level, output destination file name, file format, etc., or giving them as parameters at startup.

The server 100 outputs a log through the log control unit 109.
An example of log output is shown in FIG.
As shown in FIG. 13, the data transmission / reception, the decoding result (parameter data), the notification status to the application, and the like are added with the header information such as the log level and the date and time.

  As described above, in the present embodiment, the behavior of each part of the device control apparatus is output as a log file.

Finally, a hardware configuration example of the server 100 shown in the first to sixth embodiments will be described.
FIG. 14 is a diagram illustrating an example of hardware resources of the server 100 illustrated in the first to sixth embodiments.
Note that the configuration in FIG. 14 is merely an example of the hardware configuration of the server 100, and the hardware configuration of the server 100 is not limited to the configuration described in FIG. 14, but may be other configurations.

In FIG. 14, the server 100 includes a CPU 911 (also referred to as a central processing unit, a central processing unit, a processing unit, an arithmetic unit, a microprocessor, a microcomputer, and a processor) that executes a program.
The CPU 911 is connected to, for example, a ROM (Read Only Memory) 913, a RAM (Random Access Memory) 914, a communication board 915, a display device 901, a keyboard 902, a mouse 903, and a magnetic disk device 920 via a bus 912. Control hardware devices.
Further, the CPU 911 may be connected to an FDD 904 (Flexible Disk Drive), a compact disk device 905 (CDD), a printer device 906, and a scanner device 907. Further, instead of the magnetic disk device 920, a storage device such as an optical disk device or a memory card (registered trademark) read / write device may be used.
The RAM 914 is an example of a volatile memory. The storage media of the ROM 913, the FDD 904, the CDD 905, and the magnetic disk device 920 are an example of a nonvolatile memory. These are examples of the storage device.
A communication board 915, a keyboard 902, a mouse 903, a scanner device 907, an FDD 904, and the like are examples of input devices.
The communication board 915, the display device 901, the printer device 906, and the like are examples of output devices.

  As shown in FIG. 1, the communication board 915 is connected to a network. For example, the communication board 915 may be connected to a LAN (local area network), the Internet, a WAN (wide area network), a SAN (storage area network), or the like.

The magnetic disk device 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924.
The programs in the program group 923 are executed by the CPU 911 using the operating system 921 and the window system 922.

The RAM 914 temporarily stores at least part of the operating system 921 program and application programs to be executed by the CPU 911.
The RAM 914 stores various data necessary for processing by the CPU 911.

The ROM 913 stores a BIOS (Basic Input Output System) program, and the magnetic disk device 920 stores a boot program.
When the server 100 is started, the BIOS program in the ROM 913 and the boot program for the magnetic disk device 920 are executed, and the operating system 921 is started by the BIOS program and the boot program.

  The program group 923 stores a program for executing the function described as “˜unit” in the description of the first to sixth embodiments. The program is read and executed by the CPU 911.

In the file group 924, in the description of the first to sixth embodiments, “determination of”, “determination of”, “encoding of”, “decoding of”, “calculation of”, “ Information, data, signal values, variable values, and parameters indicating the results of the processing described as "Comparison of", "Updating", "Setting of", "Registering", "Selecting", etc. , “˜file” and “˜database”.
The “˜file” and “˜database” are stored in a recording medium such as a disk or a memory. Information, data, signal values, variable values, and parameters stored in a storage medium such as a disk or memory are read out to the main memory or cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. Used for CPU operations such as calculation, processing, editing, output, printing, and display.
Information, data, signal values, variable values, and parameters are stored in the main memory, registers, cache memory, and buffers during the CPU operations of extraction, search, reference, comparison, calculation, processing, editing, output, printing, and display. It is temporarily stored in a memory or the like.
The arrows in the flowcharts described in the first to sixth embodiments mainly indicate input / output of data and signals. The data and signal values are the RAM 914 memory, the FDD 904 flexible disk, the CDD 905 compact disk, and the magnetic field. Recording is performed on a recording medium such as a magnetic disk of the disk device 920, other optical disks, mini disks, DVDs, and the like. Data and signals are transmitted online via a bus 912, signal lines, cables, or other transmission media.

  In addition, what is described as “˜unit” in the description of the first to sixth embodiments may be “˜circuit”, “˜device”, “˜device”, and “˜step”, It may be “˜procedure” or “˜processing”. That is, what is described as “˜unit” may be realized by firmware stored in the ROM 913. Alternatively, it may be implemented only by software, or only by hardware such as elements, devices, substrates, and wirings, by a combination of software and hardware, or by a combination of firmware. Firmware and software are stored as programs in a recording medium such as a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, and a DVD. The program is read by the CPU 911 and executed by the CPU 911. That is, the program causes the computer to function as “to part” in the first to sixth embodiments. Alternatively, the computer executes the procedure and method of “to unit” in the first to sixth embodiments.

  As described above, the server 100 shown in the first to sixth embodiments includes a CPU that is a processing device, a memory that is a storage device, a magnetic disk, a keyboard that is an input device, a mouse, a communication board, and a display device that is an output device, a communication board, and the like. As described above, the function indicated as “to part” is realized by using these processing device, storage device, input device, and output device.

  100 server, 101 device control unit, 102 detailed decoding unit, 103 command parameter creation unit, 104 encoding unit, 105 decoding unit, 106 decoding determination unit, 107 communication control unit, 108 communication unit, 109 log control unit, 200 application server, 300 RFID reader, 400 tag, 500 network, 600 network.

Claims (11)

The encoded parameter data and an encoded data length identifier indicating the data length of the parameter data are included, the parameter data is arranged following the data length identifier, and the start position of the parameter data A data receiving unit for receiving indefinite received data in which the data length of the data length identifier can be determined by the value of the first bit of the data length identifier;
Extracting the first bit of the data length identifier in the indefinite received data, determining the data length of the data length identifier based on the value of the first bit of the data length identifier, determining the start position of the parameter data, and determining An indefinite received data decoding unit that decodes a bit string corresponding to the data length obtained by decoding the data length identifier from the start position of the parameter data and extracts the parameter data after decoding. Processing equipment. The indefinite received data decoding unit
Determining the data length of the data length identifier based on the value of the first bit of the data length identifier included in the indefinite received data, decoding the data length identifier, and obtaining the data length of the parameter data from the decoding result The information processing apparatus according to claim 1. The data receiver is
There is a case where the definition reception data in which the start position of the parameter data matches the reference position defined by a predetermined rule may be received.
The information processing apparatus further includes:
A reception data determination unit for determining whether the reception data received by the data reception unit is defined reception data or indefinite reception data;
When the reception data is determined to be definition reception data by the reception data determination unit, the bit string for the data length defined by the rule is decoded from the reference position in the definition reception data, and the decoded parameter data is A definition reception data decoding unit to extract,
The indefinite received data decoding unit
When the received data determining unit determines that the received data is indefinite received data, the first bit of the data length identifier is extracted from the indefinite received data, and the data length is based on the value of the first bit of the data length identifier. Determining the data length of the identifier to determine the start position of the parameter data, decoding the bit string for the data length obtained by decoding the data length identifier from the determined start position of the parameter data, and decoding the parameter The information processing apparatus according to claim 1, wherein data is extracted. The data receiver is
Receiving definition reception data and indefinite reception data including an encoded overall data length identifier indicating the data length of the entire reception data;
When the data length of the entire received data obtained by decoding the entire data length identifier included in the received data received by the data receiving unit is equal to or less than a predetermined data length, the received data is determined as defined received data, 4. The information processing apparatus according to claim 3, wherein the received data is determined as indefinite received data when the data length of the entire received data obtained by decoding the entire data length identifier exceeds the predetermined data length. The received data discrimination unit
The data length of the entire received data received by the data receiving unit is measured, and when the measured data length of the entire received data is equal to or less than a predetermined data length, the received data is determined to be defined received data, and the entire received data measured 5. The information processing apparatus according to claim 3, wherein the received data is determined as indefinite received data when the data length exceeds the predetermined data length. 6. The data receiver is
Receiving definition reception data and indefinite reception data including an encoded overall data length identifier indicating the data length of the entire reception data;
The received data discrimination unit
The data receiving unit determines whether the received data is defined received data or indefinite received data based on a bit value of an overall data length identifier included in the received data received by the data receiving unit. Item 6. The information processing device according to any one of Items 3 to 5. The definition reception data decoding unit includes:
Input definition information indicating the reference position of the start position of the parameter data in the definition reception data received by the data reception unit,
7. The parameter data of the definition reception data received by the data receiving unit from the reference position indicated in the input definition information is decoded, and the parameter data after decoding is extracted. The information processing apparatus according to any one of the above. The data receiver is
Parameter data is arranged following the data length identifier, the start position of the parameter data matches a reference position defined by a predetermined rule, and the data length of the data length identifier is determined by the value of the first bit of the data length identifier May receive definition receive data that can be determined,
The indefinite received data decoding unit
Regardless of whether the received data received by the data receiving unit is the definition received data or the indefinite received data, the first bit of the data length identifier is extracted from the received data, and the value of the first bit of the data length identifier The data length of the data length identifier is determined on the basis of the parameter data to determine the start position of the parameter data, and the bit string corresponding to the data length obtained by decoding the data length identifier from the determined start position of the parameter data is decoded. The information processing apparatus according to claim 1, wherein the parameter data after decoding is extracted. The information processing apparatus further includes:
A log control unit that generates log data indicating at least one of reception time of reception data by the data reception unit and parameter data extracted by the indefinite reception data decoding unit, and outputs the generated log data; The information processing apparatus according to any one of claims 1 to 8. The encoded parameter data and an encoded data length identifier indicating the data length of the parameter data are included, the parameter data is arranged following the data length identifier, and the start position of the parameter data A data receiving step in which the computer receives indefinite received data in which the data length of the data length identifier can be determined by the value of the first bit of the data length identifier;
The computer extracts the first bit of the data length identifier in the indefinite received data, determines the data length of the data length identifier based on the value of the first bit of the data length identifier, and determines the start position of the parameter data An indefinite received data decoding step for determining, decoding a bit string corresponding to the data length obtained by decoding the data length identifier from the determined starting position of the parameter data, and extracting the decoded parameter data A characteristic information processing method. The encoded parameter data and an encoded data length identifier indicating the data length of the parameter data are included, the parameter data is arranged following the data length identifier, and the start position of the parameter data A data reception process for receiving indefinite received data in which the data length of the data length identifier can be determined by the value of the first bit of the data length identifier;
Extracting the first bit of the data length identifier in the indefinite received data, determining the data length of the data length identifier based on the value of the first bit of the data length identifier, determining the start position of the parameter data, and determining A decoding unit that decodes a bit string corresponding to the data length obtained by decoding the data length identifier from the start position of the parameter data, and causes the computer to execute indefinite received data decoding processing for extracting the parameter data after decoding. Program.

Images