JPH0620114A - Code collating system - Google Patents

Abstract

PURPOSE:To surely keeping a code for data carrier secret even if the data carrier is stolen and to easily perform the operation control of the device, as well in the code collation system of a data processor executing a data processing by discriminating the coincidence of the code of the data carrier and code of a reader/writer. CONSTITUTION:A key carrier 30 preliminarily storing code data for data carrier is provided on a memory 32 capable of at least reading, the code for data carrier is read from the key carrier 30 by the instruction from a reader/writer 10, the code is registered in the volatile memory 17 of the reader/writer 10, the code is collated with code of a data carrier 20 after the code for data carrier is registered and the data are processed only when the coincidence is obtained. If the power source of the reader/writer 10 is turned off when the data carrier is stolen, the code for data carrier registered in the volatile memory 17 is diappeared.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a code code collating system for a data processing device which determines whether a code code of a data carrier and a code code of a reader / writer match each other and executes data processing.

[0002]

2. Description of the Related Art Conventionally, as a code code collating system for a data processing device using a reader / writer and a data carrier,
For example, the one shown in FIG. 5 is known. In FIG. 5, reference numeral 10 denotes a reader / writer, which uses a MPU to control a controller 11, a program ROM 12, a transmitter 13, a comparator 14, and an E ² P.
A nonvolatile memory 15 such as RPM is provided. A data carrier 20 includes a read / write unit 21 that functions as a memory control unit, a transmission unit 22, and a non-volatile memory 23 such as E ² PRPM.

The same code is registered in advance in each of the nonvolatile memory 15 of the reader / writer and the nonvolatile memory 23 of the data carrier 20. The reader / writer 10 is usually fixedly installed, and when the user brings the data carrier 20 close to the communicable distance of the reader / writer 10, the reader / writer 10 requests the data carrier 20 to read the code code, and The code code sent from the carrier 20 is compared and collated by the comparison section 14 with its own code code, and when collation is obtained, the control section 11 performs write access to general data in the nonvolatile memory 23 of the data carrier 20 or Read access is permitted and data processing can be executed.

[0004]

However, in such a conventional code code collation system, when the reader / writer itself is stolen, the code code registered in the non-volatile memory is decoded. There is a risk that the decrypted code will be registered in the data carrier and misused.

In order to solve this problem, if a nonvolatile memory 15 provided in the reader / writer 10 shown in FIG. 5 is replaced with a volatile memory that loses its contents when the power is cut off, it can be stolen. Since the code code registered in the reader / writer 10 has disappeared, the code code is not misused. However, when the volatile memory is used, every time the power of the reader / writer 10 is turned on,
The owner has to input the code code and register it in the volatile memory, and the registration operation is complicated and there is a risk of input error of the code code. There was a problem that it was hard to do.

The present invention has been made in view of such conventional problems, and makes it possible to securely conceal the code even if the data carrier is stolen, and to easily manage the operation of the device. An object is to provide a code code collation method.

[0007]

To achieve this object, the present invention is constructed as follows. First, the present invention is directed to a data processing device that executes data processing by determining the match between the code code of a data carrier and the code code of a reader / writer, and in the present invention as a code code collation method therefor, At least a readable memory is provided with a key carrier in which code data for the data carrier is stored in advance, the code code for the data carrier is read by an instruction from the reader / writer and registered in the memory of the reader / writer, and the code code for the data carrier is registered. It is characterized in that the data processing is executed only when the code code of the data carrier is collated later and they match.

As the memory for registering the code code for the data carrier provided in the reader / writer, a volatile memory, such as a RAM, whose contents are erased when the power is cut off is used. . Further, the code code for the data carrier registered in the memory of the reader / writer and the code code for the data carrier may be collated on the reader / writer side or the data carrier side.

Further, prior to the registration of the code code for the data carrier, the reader / writer number registered in the key carrier and the reader / writer number set in the reader / writer are collated, and only when the reader / writer numbers match, the code for the data carrier The code registration process may be started. Further, when the key carrier has a code code for the key carrier and a collating means for collating with the code code sent from the reader / writer is provided, when the code code sent from the reader / writer matches the code code for the key carrier. The reader / writer may be allowed to read the code for the data carrier. In this case, the matching means may be provided in the reader / writer.

[0010]

According to the code code collating method of the present invention having such a configuration, the owner of the reader / writer simply moves the dedicated key carrier for registering the code code for the data carrier close to the reader / writer. Since the code code for the carrier can be automatically registered and the input operation of the code code for the data carrier itself is not required, the operation management of the data processing device using the data carrier can be easily performed.

Further, even if the reader / writer is stolen, the code code for the data carrier registered in the volatile memory is erased when the power supply is cut off, so the code code for the data carrier cannot be decoded. It is possible to reliably prevent the misuse of the data carrier by decoding the code code for the data carrier.

[0012]

1 is a block diagram of an embodiment showing a first embodiment of the present invention. In FIG. 1, 10 is a reader / writer, and the reader / writer 10 is usually fixedly installed. On the other hand, a key carrier 30 owned by the owner of the reader / writer 10 and a reader / writer 1 or 1 A plurality of data carriers 20 are prepared.

The reader / writer 10, in addition to the control unit 11 using the MPU, the program ROM 12, the transmission unit 13, and the comparison unit 14 for comparing the code codes, newly registers the code code registration unit 16 and the data carrier code code. RAM
A volatile memory 17 for the like is provided. The registration of the code code for the key carrier in the volatile memory 17 by the code code registration unit 16 is performed by data communication with the key carrier 30.

The key carrier 30 includes a read-out section 31, E ² P.
A nonvolatile memory 32 such as a ROM and a transmission unit 32 are provided. The nonvolatile memory 32 may be at least a readable memory, and the key carrier code code to be registered in the reader / writer 10 is registered in advance. When the key carrier 30 is brought close to the communicable distance of the reader / writer 10 after the power of the reader / writer 10 is turned on, the data carrier code is registered, data communication is performed between the transmission units 13 and 32, and the key carrier 30 is non-volatile. Sex memory 3
The code code for the key carrier registered in No. 3 is read and registered in the volatile memory 17 of the reader / writer 10 by the code code registration unit 16.

A reader / writer 1 using the key carrier 30
When the code code for the data carrier for 0 is registered, the reader / writer 10 can perform data processing with the data carrier 20. The data carrier 20 is provided with a read / write unit 21, a transmission unit 22, and a nonvolatile memory 23 such as an E ² PROM storing a code and general data. When the data carrier 20 is brought close to the communicable distance of the reader / writer 10, data communication is started between the transmission units 13 and 22.

First, when the code code is read from the data carrier 20 and the comparison section of the reader / writer 10 compares and collates with the code code for the data carrier registered in the volatile memory 17, the collation coincidence is obtained. The control circuit 11 permits read access or write access to general data in the non-volatile memory 23 of the data carrier 20.

FIG. 2 is a flow chart showing the processing operation of the reader / writer 10 of FIG. In FIG. 2, when the power of the reader / writer 10 is turned on, the presence or absence of a response from the carrier side is checked in step S1, and the transmission unit 13 of the reader / writer 10 supplies power to a predetermined communicable area by, for example, electromagnetic induction coupling. When the key carrier 30 or the data carrier 20 approaches the electromagnetic field of this communication area, a power supply voltage is created by rectifying the voltage induced on the carrier side, and this power supply voltage is In response to this, the carrier side becomes operational, and for example, a response indicating that the carrier side has become the standby state is returned to the test command periodically issued by the reader / writer 10.

In the present invention, since there are two types of the key carrier 30 and the data carrier 20 on the carrier side, the key carrier or the data carrier is used as a carrier response indicating the ready state after receiving the power supply. To be able to distinguish Specifically, a response different from the data carrier 20 for the ready response of the key carrier 30 may be returned.

Usually, immediately after the power of the reader / writer 10 is turned on, the owner brings the key carrier 30 close to register the code in the reader / writer 10.
In step S2, it is determined that the key carrier is a key carrier, the process proceeds to step S3, and the key carrier nonvolatile memory 33 is used.
The code code for the data carrier is read from, and the code code for the key carrier is registered in the volatile memory 17 of the reader / writer 10 by the code code registration unit 16 in step S4.

When the user brings the data carrier 20 closer to the reader / writer 10 after the above-mentioned registration process of the code code for key carrier is completed, the response from the carrier side is discriminated in step S1 and the process proceeds to step S2. In this case, since the response is from the data carrier, the process proceeds to step S5, and the reader / writer 10 of the code code for the data carrier.
Check whether or not registered in. If not registered, the process returns to step S1 and data processing is not performed.

When it is determined in step S5 that the code code for the data carrier has been registered, the process proceeds to step S6, the code code is read from the non-volatile memory 23 of the data carrier 20, and the volatile memory 17 is read by the comparison unit 14 in step S7. The comparison unit 14 compares and collates with the registered code code for the data carrier, and if the code codes match, the comparison unit 14
Access permission is issued from the control unit 11 to the control unit 1.
1 executes read access or write access to general data in the non-volatile memory 23 of the data carrier 20 according to the contents of the program ROM 12.

If the code codes do not match in step S7, the access process in step S8 is not performed and step S9 is performed.
Then, the process of disconnecting the data carrier 20 is performed, and the user of the data carrier 20 is notified of an unusable message or an error notification. Of course, even when the access process is completed in step S8, the disconnection process of step S9 is performed. In this case, it is displayed to the user that the data processing has been effectively performed.

FIG. 3 is a block diagram showing a second embodiment of the present invention. This embodiment is characterized in that the code code is collated on the side of the data carrier, and for the reader / writer. It is characterized in that the reader / writer number is also collated with the registration of the code code for the data carrier from the key carrier. In FIG. 3, a reader / writer number setting unit 18 is newly added to the reader / writer 10.
Is provided, and a comparison unit 19 that performs matching verification of the reader / writer number is provided. Further, since the comparison and collation of the code is performed on the data carrier 20 side, the comparison unit 14 shown in the first embodiment of FIG. 1 is removed. Besides, the control unit 11, the program ROM 12, the transmission unit 1
3, the code code registration unit 16 and the volatile memory 17 are shown in FIG.
Is the same as in the first embodiment.

Like the first embodiment, the key carrier 30 includes a reading unit 31, a transmitting unit 32 and a non-volatile memory 33, but the non-volatile memory 33 stores in advance a reader / writer code in addition to a data carrier code. is doing. On the other hand, the data carrier 20 includes a writing / reading unit 21 and a transmission unit 22.
In addition to the non-volatile memory 23, a comparison unit 24 is newly provided to determine whether the code codes match each other. Comparison unit 2
4 is a reader / writer 10 sent via the transmission unit 22.
And the code registered in the non-volatile memory 23 are compared with each other, and if a match is obtained, the read gate 25 between the writing / reading section 21 and the non-volatile memory 23 is compared.
Each of the write gate 26 and the write gate 26 is allowed.

That is, the read gate 25 and the write gate 26 are composed of AND gates, and when the comparison output of the code code in the comparison unit 24 obtains the H-level coincidence output, the write access and the read access are permitted. To do. FIG. 4 is a reader / writer 1 provided in the second embodiment of FIG.
6 is a flowchart showing a processing operation of 0.

First, when the user turns on the power of the reader / writer 10, the process proceeds to step S1 to check whether or not there is a carrier response. Since the code code is registered by the key carrier 30 immediately after the power is turned on, when the ready response is received from the key carrier 30 in step S1, step S2 is performed.
In step S3, the key carrier 30 is known from the contents of the ready response, and in step S3, the reader / writer code is first read from the nonvolatile memory 33.

The reader / writer code code read from the key carrier 30 is given to the comparing section 19 of the reader / writer 10 and compared with the reader / writer code code from the reader / writer number setting section 18 stored in advance. It When it is determined in step S4 that the code codes for the reader / writer match, the process proceeds to step S5, the reader / writer 10 reads the code code for the data carrier from the key carrier 30, and the code code registration unit 16 causes the volatile memory 17 to read.
In step S6, the code code for the data carrier is registered.

Of course, if the reader / writer code code does not match in step S4, the data carrier code code is not registered after step S5. Therefore, in the unlikely event that the reader / writer 10 is stolen and the user attempts to register the code code for the data carrier using the key carrier 30 that he / she has separately, the code code for the reader / writer does not match. It is impossible to register the code code for the data carrier with respect to the writer 10.

Key carrier 3 for reader / writer 10
When the code code for the data carrier using 0 is registered, the reader / writer 10 can access the data carrier 20. That is, when the data carrier 20 is brought close to the communicable area of the reader / writer 10, the ready response of the data carrier 20 is determined in step S1,
Since it is a data carrier in step S2, the process proceeds to step S7, and it is checked whether or not the code code for data carrier in the reader / writer 10 is registered.

Since the code code for the data carrier has already been registered using the key carrier 30, the process proceeds to step S8, the control section 11 reads the code code registered in the volatile memory 17, and the data is transmitted from the transmission section 13. The code code is sent to the carrier 20. The transmission unit 22 of the data carrier 20 outputs the code code sent from the reader / writer 10 to the comparison unit 24, and the comparison unit 24 makes the nonvolatile memory 2
The data carrier code code registered in No. 3 and the code code sent from the reader / writer 10 are compared and collated. Here, if the code codes match, the match output (H level output) from the comparison unit 24 causes the read gate 25 and the write gate 26 to be in the allowable state.

Further, based on the coincidence output from the comparison unit 24, the transmission unit 22 sends a code coincidence response to the reader / writer 10. Therefore, in step S9, the reader / writer 10 is sent.
When the side confirms the code matching response in the data carrier 20, the process proceeds to step S10, and the read access or the write access to the non-volatile memory 23 of the data carrier 20 is executed.

On the other hand, if no code match response is obtained on the data carrier 20 side, there is no code match response. Therefore, for example, when no code match response is obtained within a predetermined time, the access process of step S10 is not performed and the step is skipped. Proceeding to the disconnection processing of S11, an error message or error display is given to the user, and access to the data carrier 20 thereafter is stopped.

In the second embodiment of FIG. 3, when the code code for the data carrier of the reader / writer 10 is registered, the code code for the reader / writer is matched and collated. However, the first embodiment of FIG. Similar to the example, the data carrier code code may not be matched and checked, but only the data carrier code code may be matched and checked on the data carrier 20 side.

Next, as a third embodiment of the present invention, the key carrier 30 shown in the embodiments of FIGS. 1 and 3 is provided with a code code for key carrier, and the code code sent from the reader / writer 10 is used. A comparing unit (collating means) for performing the collation is provided, and when the code code sent from the reader / writer 10 and the code code for the key carrier match, the reading of the code code for the data carrier from the key carrier 30 is permitted. You may In this case, the comparison unit for collating the code code for the key carrier is the data carrier 1
It may be provided on the 0 side.

The nonvolatile memories 23 and 33 provided in the data carrier 20 and the key carrier 30 are E ² PRO.
Instead of M, a RAM backed up by a built-in battery may be used. Further, the key carrier 30 used in the present invention
As a data carrier 20
It can also be used as a key carrier.

[0036]

As described above, according to the present invention, even if the reader / writer is stolen, the code code for the data carrier registered in the volatile memory is lost when the power is turned off. Even if a person decodes the memory, the code code for the data carrier is not known, and it is possible to reliably prevent misuse by the code code for the data carrier of the reader / writer being decoded.

Further, by comparing and collating the reader / writer code code and the code code for the key carrier when registering the code code using the key carrier with the reader / writer, the stolen key carrier is used to transfer data to another reader / writer. Even if you try to misuse by registering the carrier code,
The use of the key carrier is canceled due to the mismatch of the reader / writer code code and the key carrier code code, and the misuse of the reader / writer by the key carrier itself can be prevented.

Further, since the code code for the data carrier is registered in the reader / writer automatically by simply bringing the key carrier owned by the owner close to the reader / writer, the input operation of the code code for the data carrier itself is unnecessary. Therefore, the operation management of the data processing device using the reader / writer and the data carrier can be easily performed.

[Brief description of drawings]

FIG. 1 is a block diagram showing a first embodiment of the present invention.

FIG. 2 is a flowchart showing the processing operation of FIG.

FIG. 3 is a block diagram showing a second embodiment of the present invention.

FIG. 4 is a flowchart showing the processing operation of FIG.

FIG. 5 is an explanatory diagram of a conventional method.

[Explanation of symbols]

 10: data carrier 11: control unit (MPU) 12: program ROM 13, 22, 32: transmission unit 14, 24: comparison unit 16: code code registration unit 17: volatile memory 18: reader / writer code setting unit 20: Data carrier 21: Read / write unit 23, 32: Non-volatile memory 30: Key carrier 31: Read unit 25: Read gate 26: Write gate

Claims (7)

[Claims] 1. A data processing device for executing data processing by determining whether a code code of a data carrier and a code code of a reader / writer are coincident with each other, wherein code data for a data carrier is stored in advance in at least a readable memory. A key carrier is provided, the code code for the data carrier is read by an instruction from the reader / writer and registered in the memory of the reader / writer, and after the code code for the data carrier is registered, the code code for the data carrier is collated. A code code matching method characterized in that data processing is executed only when they match. 2. The code code collating method according to claim 1, wherein the memory for registering the code code for the data carrier of the reader / writer is a volatile memory whose contents are erased when power is cut off. A code code registration method characterized by being used. 3. The code code collation system according to claim 1, wherein the collation between the code code for the data carrier registered in the memory of the reader / writer and the code code for the data carrier is performed on the reader / writer side. Code code matching method. 4. The code code collating method according to claim 1, wherein collation between the data carrier code code registered in the memory of the reader / writer and the data carrier code code is performed on the data carrier side. Code code matching method. 5. The code code collating method according to claim 1, wherein the reader / writer number registered in the key carrier and the reader / writer number set in the reader / writer are collated before registering the code code for the data carrier. A code code collating method, wherein registration processing of a code code for a data carrier is started only when the reader / writer numbers match. 6. The code code collating method according to claim 1, wherein the key carrier has a key carrier code code, and further comprises collating means for collating with the code code sent from the reader / writer, A code code collating method characterized by permitting a reader / writer to read a code for a data carrier when a code code sent from a writer and a code code for a key carrier match. 7. The code code collating system according to claim 6, wherein the collating means is provided in a reader / writer.