JP6747144B2 - Information processing apparatus, information processing method, and program - Google Patents

Description

The present invention relates to an information processing device, an information processing method, and a program.

There has been proposed a method of calculating a rule for anonymizing the input individual number acquired in the past so as to satisfy k-anonymity, and anonymizing the newly acquired input individual number (Patent Document 1 Reference 3).

JP, 2013-80375, A US Patent Application Publication No. 2002/169793 Special table 2006-5122012 gazette

Patent Literature 1 to Patent Literature 3 do not disclose a method of updating a rule used for the processing in parallel with the sequential processing of the input individual number.

In one aspect, it is an object of the present invention to provide an information processing apparatus or the like capable of updating a rule used for processing while sequentially processing an input form.

The information processing device includes an acquisition unit that acquires an input vote including a plurality of items, and a conversion unit that converts the input vote acquired by the acquisition unit into an output vote including the same number of items based on a rule. A storage unit for storing the input individual numbers acquired by the acquisition unit, a generation unit for generating a new rule based on the plurality of input individual numbers accumulated by the storage unit, and a rule used by the conversion unit Is updated to the new rule generated by the generation unit.

According to one aspect, it is possible to provide an information processing device or the like that can update rules used for processing while sequentially processing input individual numbers.

It is explanatory drawing which shows the structure of an information processing system. It is explanatory drawing which shows the outline of a process. It is explanatory drawing which shows the example of an input piece. It is explanatory drawing which shows the record layout of accumulation DB. It is explanatory drawing which shows the record layout of rule DB. It is explanatory drawing which shows the example of an output individual form. It is explanatory drawing which shows the 2nd example of rule DB. It is explanatory drawing which shows the 2nd example of an output piece. It is a time chart explaining an outline of processing. It is explanatory drawing which shows the 3rd example of rule DB. It is explanatory drawing explaining the conversion result. It is a flow chart which shows a flow of rule generation processing. It is a flow chart which shows a flow of processing of a subroutine of rule creation. It is a flowchart which shows the flow of sequential data processing. It is a flow chart which shows a flow of processing of a subroutine of conversion processing. FIG. 9 is an explanatory diagram showing the configuration of the information processing system according to the second embodiment. 9 is a flowchart showing a flow of processing according to the second embodiment. FIG. 16 is an explanatory diagram illustrating a conversion result of the third embodiment. It is explanatory drawing which shows the example of rule DB of Embodiment 3. FIG. 16 is a functional block diagram showing an operation of the information processing device of the fourth embodiment. It is explanatory drawing which shows the structure of the information processing system of Embodiment 5.

[Embodiment 1]
FIG. 1 is an explanatory diagram showing the configuration of the information processing system 10. The information processing system 10 includes a server 11, which is an example of the information processing apparatus according to the present embodiment, a first client 21, and a second client 25. The server 11, the first client 21, and the second client 25 are connected via a network such as the Internet, a public communication line, or a LAN (Local Area Network).

The server 11 includes a server CPU (Central Processing Unit) 12, a main storage device 13, an auxiliary storage device 14, a communication unit 15, and a bus. The server 11 of the present embodiment performs sequential data processing for converting the input individual number 28 into the anonymized output individual number 29 and generation of a rule used for the conversion. The server 11 of the present embodiment is a general-purpose personal computer, an information device such as a large-scale computer, or the like. Further, the server 11 of this embodiment may be a virtual machine operating on a large-scale computer.

The server CPU 12 is an arithmetic and control unit that executes the program according to the present embodiment. For the server CPU 12, one or a plurality of CPUs, a multi-core CPU, or the like is used. The server CPU 12 is connected to each of the hardware components that configure the server 11 via a bus.

The main storage device 13 is a storage device such as SRAM (Static Random Access Memory), DRAM (Dynamic Random Access Memory), and flash memory. The main storage device 13 temporarily stores information required during the processing performed by the server CPU 12 and programs being executed by the server CPU 12.

The auxiliary storage device 14 is a storage device such as an SRAM, a flash memory, a hard disk or a magnetic tape. The auxiliary storage device 14 stores a program to be executed by the server CPU 12, a storage DB (Data Base) 31, a rule DB 32, and various kinds of information necessary for executing the program. The communication unit 15 is an interface that communicates with a network. The storage DB 31 and the rule DB 32 may be stored in another storage device connected to the server 11 via a network or the like.

The storage DB 31 is a DB for storing the input individual numbers 28 acquired from the network. The rule DB 32 is a DB that records rules used when sequentially converting the input form 28 into the output form 29. In the present embodiment, the server CPU 12 anonymizes by converting the input individual number 28 into the output individual number 29 based on the rule DB 32. Details of the accumulation DB 31 and the rule DB 32 will be described later.

The second client 25 is a client that sequentially acquires the input individual number 28 and sends it to the network. The second client 25 is an information terminal installed in a store or the like and an information device such as a personal computer, a tablet, or a smartphone used by a general consumer or the like. In the following description, a user who operates the second client 25 will be referred to as a second user.

The input form 28 is obtained from, for example, website member registration, mail-order transaction records, point-granting records of point cards, and the like. The input form 28 is sequentially sent from the second client 25 to the network in a predetermined format. The input form 28 may include information about an individual.

The first client 21 is a client used by a user who utilizes the output individual number 29 for marketing or the like. The first client 21 of this embodiment uses an information device such as a general-purpose personal computer or a large-scale computer. In the following description, the user who operates the first client 21 will be referred to as the first user. The first client 21 sequentially receives the output form 29 in which the server CPU 12 anonymizes the input form 28.

The first client 21 and the second client 25 include a CPU, a main storage device, an auxiliary storage device, and a communication unit, like the server 11. Further, the first client 21 and the second client 25 include an input interface such as a keyboard, a touch panel, a mouse and the like, and an output interface such as a liquid crystal display, an organic EL display, and a print. Illustration of the internal configuration of the first client 21 and the second client 25 is omitted.

FIG. 2 is an explanatory diagram showing an outline of the processing. The server CPU 12 of the present embodiment performs parallel generation of a rule for converting the input individual number 28 and sequential data processing for converting the input individual number 28 into the output individual number 29 based on the rule. The flow of each of the rule generation and the sequential data processing will be described later. The time required for the sequential data processing of the input form 28 for each case is significantly shorter than the time required for the rule generation.

The server CPU 12 creates a rule based on the data of the input form 28 accumulated in the accumulation DB 31. When the input form 28 is received during the generation of the rule, the server CPU 12 preferentially executes the sequential data processing for converting the input form 28 into the output form 29. After the processing of the input form 28 is completed, the server CPU 12 restarts the rule generation processing.

The server CPU 12 may execute the rule generation processing in parallel during the sequential data processing. For example, the load of the server CPU 12 is relatively small in the process of storing the input individual number 28 in the storage DB 31 and the process of transmitting the output individual number 29 to the network. As described above, when the load of the server CPU 12 is relatively small, even if the rule generation processing is performed in parallel, the speed of sequential data processing is not adversely affected.

The server CPU 12 updates the rule recorded in the rule DB 32 with the newly generated rule. The server CPU 12 sequentially performs data processing on the input individual form 28 received after the rule DB 32 is updated, using a new rule.

By repeating the above processes, the server CPU 12 newly generates and updates the rule for the process of converting the input individual number 28 into the output individual number 29 and the input individual number 28 accumulated in the accumulation DB 31. The processing to be performed is executed in parallel.

FIG. 3 is an explanatory diagram showing an example of the input individual form 28. One row of FIG. 3 shows one input vote 28 and ID (IDentifier). The individual vote is data treated as one lump, such as member registration information for one person or a record of one transaction. In FIG. 3, as an example, an individual vote including three items of postal code, year of birth, and gender is shown. Note that FIG. 3 shows an example in which only the first three digits of the postal code are recorded.

In the leftmost column of FIG. 3, IDs for identifying individual pieces are shown for the sake of explanation. In the present embodiment, the description will be given by assigning IDs A to H in the order in which the server CPU 12 receives the individual votes from the network. In addition to the items shown in FIG. 3, the individual vote may include various items related to an individual such as an address, a name, a telephone number, an email address, a family structure, purchased products, and a payment method.

FIG. 4 is an explanatory diagram showing a record layout of the storage DB 31. The storage DB 31 is a DB that associates the input individual number 28 with the presence or absence of use for rule generation. The storage DB 31 has an input individual number field and a use field. The input vote fields include a postal code field, a birth year field and a gender field. The accumulation DB 31 has one record for each accumulated input individual number 28. Note that in FIG. 4, the ID of the input form is described in the leftmost column for the sake of explanation.

In each field of the input individual number field, each data included in the input individual number 28 is recorded. In the used field, it is recorded whether or not the rule has been used for converting the input individual number 28.

The server CPU 12 does not store the individual pieces determined not to be used for generating the rule for converting the input individual pieces 28 in the storage DB 31. Therefore, the accumulation DB 31 does not record the individual IDs D and G. The determination of the individual bills that are stored in the storage DB 31 and the individual bills that are not stored will be described later.

FIG. 5 is an explanatory diagram showing a record layout of the rule DB 32. The rule DB 32 is a DB that records the rules used when converting the input form 28 into the output form 29. The rule DB 32 is No. It has a field, an input number field and an output number field. The input and output vote fields include a postal code field, a birth year field and a gender field, respectively. The rule DB 32 has one record for one rule used for conversion.

No. In the field, the order in which the rule applicability is determined is recorded. In the present embodiment, No. Applicability is determined sequentially from the record with the smallest number recorded in the field. A condition for applying a record is recorded in the input number field. In the output individual number field, the individual number output when the record is applied is recorded.

A more specific description will be given. No. The record 1 indicates a rule for converting the input individual number 28 into the output individual number 29 of "198, 20, female" when the input individual number 28 is "198, 20, female". Similarly, No. The record No. 2 indicates a rule for converting the input individual number 28 into the output individual number 29 of "198, 50, male" when the input individual number 28 is "198, 50, male". No. The record of No. 3 shows a rule for converting the input form 28 into the output form 29 of "*, *, *" when the input form 28 does not match the input form field of any other record.

Here, “*” means that specific data of each item of the input individual form 28 is hidden. In the following description, “*” is called a generalized code. Similarly, individual pieces “*, *, *” in which all items are generalized codes “*” are called generalized individual pieces. In addition, the process of replacing the item on the individual form with the generalized code “*” is called generalized process.

By the generalization process, the plurality of input individual numbers 28 having different contents are converted into the same output individual number 29. By processing the input form 28 in this manner, the input form 28 can be converted into the output form 29 having anonymity of a predetermined condition.

FIG. 6 is an explanatory diagram showing an example of the output individual form 29. One row in FIG. 6 shows an output vote 29 obtained by converting the input vote 28 shown in one row in FIG. 3 according to the rule shown in FIG. The ID shown in the leftmost column of FIG. 6 is a symbol for identifying each individual piece for the sake of explanation. The ID given to the output form 29 matches the ID given to the input form 28. The conversion of the input form 28 will be described with reference to FIGS. 3, 5, and 6.

The input pieces 28 having IDs A and G are No.s of the rules shown in FIG. It matches the input record field of record 1. Therefore, No. The record 1 is applied, and the output individual number 29 is “198, 20, woman”. The input individual numbers 28 with IDs B, C and D are No.s of the rules shown in FIG. It matches the input number field of the second record. Therefore, No. The record 2 is applied, and the output individual number 29 is “198, 50, man”. The input individual number fields 28 with IDs E, F, and H do not match the input individual number fields of the records other than No3 of the rule shown in FIG. Therefore, No. 3 records are applied, and the output individual number 29 is the generalized individual number “*, *, *”.

FIG. 7 is an explanatory diagram showing a second example of the rule DB 32. The record layout of the rule DB 32 shown in FIG. 7 is the same as the record layout of the rule DB 32 described with reference to FIG. No. In the record No. 1, "-" is recorded in the gender field of the input individual number field. “−” indicates that the record is applied regardless of the content of the item in the input individual form 28.

A more specific description will be given. No. In the record of No. 1, when the postal code of the input individual number 28 is "198" and the year of birth is "20", the rule for converting to the output individual number 29 of "198, 20, *" regardless of the gender data is set. Show. No. 2 and No. The record of No. 3 is the same as that of FIG.

FIG. 8 is an explanatory diagram showing a second example of the output individual form 29. One row of FIG. 8 shows an output individual number 29 obtained by converting the input individual number 28 shown in the one line of FIG. 3 according to the rule shown in FIG. The ID shown in the leftmost column of FIG. 8 is a symbol for identifying each individual piece for the sake of explanation. The ID given to the output form 29 matches the ID given to the input form 28. Conversion of the input form 28 will be described with reference to FIGS. 3, 7, and 8.

The input pieces 28 with IDs A, G and H are No.s of the rules shown in FIG. It matches the input record field of record 1. Therefore, No. The record 1 is applied, and the output individual number 29 is “198, 20, *”. Here, the input individual votes 28 of A and G whose gender is "female" and the input individual votes 28 of H whose gender is "male" are converted into the same output individual votes 29.

The input votes 28 having IDs B, C and D are No.s of the rules shown in FIG. It matches the input number field of the second record. Therefore, No. The record 2 is applied, and the output individual number 29 is “198, 50, man”. The input individual number fields 28 with IDs E and F do not match the input individual number fields of the records other than No. 3 of the rule shown in FIG. Therefore, No. 3 records are applied, and the output individual number 29 is the generalized individual number “*, *, *”.

As shown in FIGS. 6 and 8, even when the same input individual number 28 is input, if the content of the rule DB 32 is different, it is converted into a different output individual number 29. It is desirable that the rule DB 32 is appropriately adjusted in accordance with changes in the tendency of the input individual form 28 and changes in the needs of the first user who uses the converted individual form.

FIG. 9 is a time chart explaining the outline of the processing. FIG. 10 is an explanatory diagram showing a third example of the rule DB 32. FIG. 11 is an explanatory diagram illustrating a conversion result. The processing of the server CPU 12 according to the present embodiment will be described with reference to FIGS. 9 to 11.

The horizontal axis of FIGS. 9S to 9W is time. FIG. 9S shows the timing when the server CPU 12 receives the input form 28. FIG. 9T shows the timing when the server CPU 12 transmits the output individual number 29. FIG. 9U shows the timing at which the server CPU 12 stores the input form 28 in the storage DB 31.

Each time the server CPU 12 receives the input individual number 28, the server CPU 12 performs a sequential data process of converting the input individual number 28 into the output individual number 29 based on the rule recorded in the rule DB 32. The time required for the process of converting the input form 28 into the output form 29 and the process of accumulating the input form 28 in the accumulation DB 31 is short. Therefore, on the time chart shown in FIG. 9, the reception of each input form 28, the output of the output form 29, and the storage of the input form 28 are performed at substantially the same time.

FIG. 9V shows the time at which the server CPU 12 generates a rule for converting the input form 28 into the output form 29 by an outline arrow. FIG. 9W shows a change in the rule DB 32 used when the server CPU 12 converts the input form 28 into the output form 29.

FIG. 10 shows the rule X1 recorded first in the rule DB 32. The rule X1 indicates a rule for converting all input individual numbers 28 into generalized individual numbers “*, *, *”. FIG. 11 shows rules used to convert the input votes 28 with IDs A to H and the output votes 29 obtained by the server CPU 12 converting the respective input votes 28.

An example of processing performed by the server CPU 12 according to the present embodiment will be described with reference to the time chart shown in FIG. 9. The server CPU 12 receives the input pieces 28 having IDs A and B at the time when the rule X1 is used as shown in FIG. 9W. The server CPU 12 converts each input form 28 into an output form 29 of A1 and B1 and outputs it. As shown in FIG. 11, since the rule X1 shown in FIG. 10 is applied to the input individual numbers 28 with IDs A and B, the output individual numbers 29 are generalized individual numbers “*, *, *”.

Furthermore, the server CPU 12 stores the input individual numbers 28 of A and B in the storage DB 31, as shown in FIG. 9U. The server CPU 12 records “not yet” in the use field of each record to be accumulated.

After the input form 28 with ID B is accumulated in the accumulation DB 31, the server CPU 12 acquires the accumulated data from the accumulation DB 31 and starts generation of a new rule X2 used for conversion, as shown in FIG. 9U. .. The server CPU 12 changes the used field of the acquired record in the storage DB 31 to “completed”. Generating a rule is a complicated process and takes time, as indicated by a white arrow in FIG. 9V. Details of rule generation will be described later.

The server CPU 12 receives the input individual number 28 having the ID C during the process of generating the rule X2. The server CPU 12 uses the rule X1 to convert and output the output form 29 of C1. As shown in FIG. 11, the output form 29 is a generalized form “*, *, *”. The server CPU 12 accumulates the input form 28 with the ID C in the accumulation DB 31.

After the generation of the rule X2 is completed, the CPU 12 updates the content of the rule DB 32 from the rule X1 to the rule X2. After that, the server CPU 12 uses the rule X2 for the conversion of the input form 28. The rule X2 is the rule described with reference to FIG. The server CPU 12 acquires the accumulated data from the accumulation DB 31 and starts generation of a new rule X3 used for conversion.

It should be noted that the server CPU 12 does not start the generation of the rule until a new record is added to the storage DB 31 when there is no record in the storage DB 31 in which the usage field indicates “not yet”. The server CPU 12 may start generation of the rule when the number of records recorded as “unused” in the usage field reaches a predetermined number. The server CPU 12 may start the generation of the rule after a predetermined time has elapsed after the generation of the rule is completed. The server CPU 12 may start generating rules at a predetermined time, such as midnight every day.

The server CPU 12 receives the input votes 28 with IDs D, E, F, G and H at the time when the rule X2 is used, and converts them into the output votes 29 of D2, E2, F2, G2 and H2. Output. Since the input individual number 28 having the ID D is "198, 50, male", the server CPU 12 has the No. 2 shown in FIG. Apply the second record. As a result, the server CPU 12 outputs the output individual number 29 of "198, 50, man". Since the input individual number 28 having the ID G is “198, 20, female”, the server CPU 12 has the No. 2 shown in FIG. Apply the record of 1. As a result, the server CPU 12 outputs the output individual number 29 of "198, 20, female". For the input votes 28 with IDs of E, F, and H, the server CPU 12 outputs the No. shown in FIG. Apply record 3 As a result, the server CPU 12 outputs the generalized individual number “*, *, *”.

Furthermore, the server CPU 12 stores the input individual numbers 28 with IDs E, F, and H in the storage DB 31. The reason why the server CPU 12 does not store the individual IDs D and G in the storage DB 31 will be described later.

After the generation of the rule X3 is completed, the CPU 12 updates the content of the rule DB 32 from the rule X2 to the rule X3. After that, the server CPU 12 uses the rule X3 for converting the input form 28. The server CPU 12 acquires the accumulated data from the accumulation DB 31 and starts generating a new rule X4 used for conversion.

As described above, the server CPU 12 receives the input vote 28, sequentially converts the output vote 29 into the output vote 29 based on the rule, and outputs the output vote 29, while creating a new rule based on the accumulated input vote 28. To generate.

The rules generated by the server CPU 12 in this embodiment will be described. First, anonymity will be described. A state in which there are k or more individual votes including the same content in any individual vote is called k-anonymity. Here, k is an integer of 2 or more. If k-anonymity is secured, it is not possible to narrow down the number of individuals associated with the individual vote to less than k and specify.

The server CPU 12 of this embodiment generates a rule for converting the input form 28 into the output form 29 having anonymity of k=2. Specifically, when the combination of the data recorded in each item is the same as the input form 28 acquired in the past, the output form 29 having the same data as the input form 28 is output. On the other hand, when the combination of the data recorded in each item is different from any of the input individual numbers 28 acquired in the past, the generalized individual number “*, *, *” is output.

Therefore, the server CPU 12 generates the rule DB 32 having the same data as the input individual number 28 accumulated in the accumulation DB 31 in the input individual number field and the output individual number field. When the record having the same input number field is duplicately recorded in the rule DB 32, the server CPU 12 deletes the duplicate record.

When the input individual number 28 and the output individual number 29 are the same, the input individual number 28 having the same data has already been accumulated in the accumulation DB 31. Therefore, the server CPU 12 does not store the input form 28 in the storage DB 31. As described with reference to FIG. 11, since the input votes 28 with IDs D and G are converted into the output votes 29 having the same content, the server CPU 12 accumulates these input votes 28 in the accumulation DB 31. do not do.

The rule DB 32 described above is an example. The server CPU 12 may generate a rule for converting the input form 28 into the output form 29 so as to have k-anonymity of k=3 or more. The server CPU 12 may generate a rule for converting the input form 28 into the output form 29 so as to have Pk-anonymity, for example. Pk-anonymity means a state in which there is less than a 1/k possibility that an individual can be identified from individual votes.

The rule X1 used first may be a rule generated in advance based on a large number of input votes 28 collected in advance.

FIG. 12 is a flowchart showing the flow of rule generation processing. The program shown in FIG. 12 is a program that performs a process of generating the conversion rule shown in FIG. 9V. The processing flow of the program according to this embodiment will be described with reference to FIG.

The server CPU 12 acquires the notification instructing the start of the rule generation processing (step S500). The notification is, for example, a signal or interrupt signal received by the server CPU 12 via the network. The clock included in the server 11 may generate the notification at a predetermined time or at a predetermined time interval.

The server CPU 12 acquires the number of records in which “not yet” is recorded in the used field from the storage DB 31 (step S501). The server CPU 12 determines whether to start generating rules (step S502). For example, the server CPU 12 determines to start generating a rule when the number acquired in step S501 is 1 or more.

When it is determined that the generation is not started (NO in step S502), the server CPU 12 returns to step S500. When it is determined that the generation is to be started (YES in step S502), the server CPU 12 activates a rule creation subroutine (step S503). The rule creation subroutine is a subroutine for creating a rule to be recorded in the rule DB 32 based on the input pieces 28 accumulated in the accumulation DB 31. The processing flow of the rule creation subroutine will be described later.

The server CPU 12 updates the rule DB 32 with the rule created in step S503 (step S504). The server CPU 12 determines whether to end the process (step S505). The case of ending the processing is, for example, the case of receiving an input for ending the processing of generating the processing rule via the network.

When it is determined that the process is not finished (NO in step S505), the server CPU 12 returns to step S500. When it is determined that the process is to be ended (YES in step S505), the server CPU 12 ends the process.

FIG. 13 is a flow chart showing the flow of processing of the subroutine for rule creation. The rule creation subroutine is a subroutine for creating a rule to be recorded in the rule DB 32 based on the input pieces 28 accumulated in the accumulation DB 31. The process flow of the rule creation subroutine will be described with reference to FIG.

The server CPU 12 acquires the data used for generating the rule from the storage DB 31 (step S511). Specifically, the server CPU 12 acquires from the storage DB 31 the data recorded in the input number field of each record recorded as “unused” in the use field, and stores the data in the auxiliary storage device 14 or the main storage device 13. .. The server CPU 12 changes the used field of the record in the storage DB 31 to “completed”.

The server CPU 12 duplicates the rule DB 32 in the auxiliary storage device 14 or the main storage device 13 (step S512). After that, the server CPU 12 executes the process using the rule DB 32 duplicated in step S512.

The server CPU 12 sets the counter I to the initial value 1 (step S513). The server CPU 12 sets the counter J to the initial value 1 (step S514).

The server CPU 12 determines whether or not the I-th input individual vote 28 acquired in step S511 matches the input individual vote field of the J-th record of the duplicated rule DB 32 (step S515). When it is determined that they do not match (NO in step S515), the server CPU 12 adds a new record to the duplicated rule DB 32 (step S516).

Specifically, the server CPU 12 adds a record immediately before the last record in the duplicated rule DB 32. The server CPU 12 records the data of the I-th input vote 28 in the input vote field and the output vote field of the added record. The server CPU 12 determines the No. of the added record. No. of field and last record. Record the numbers serially in the field.

When it is determined that they match (YES in step S515), the server CPU 12 determines whether or not the processing of all the records of the copied rule DB 32 has been completed (step S517). When it is determined that the processing has not ended (NO in step S517), the server CPU 12 adds 1 to the counter J (step S518). The server CPU 12 returns to step S515.

When it is determined that the processing of all the records in the rule DB 32 has been completed (YES in step S517) and after the processing of step S516, the server CPU 12 has completed the processing of all the input individual numbers 28 acquired in step S511. Is determined (step S519). When it is determined that the processing is not completed (NO in step S519), the server CPU 12 increments the counter I by 1 (step S520). The server CPU 12 returns to step S514. When it is determined that the process is completed (YES in step S519), the server CPU 12 ends the process.

The rule creation subroutine described with reference to FIG. 13 is an example. It is desirable to use a subroutine that implements an algorithm that creates rules according to the needs of the first user.

The rule creation subroutine may be a subroutine that generates a rule for converting the input form 28 into the output form 29 so as to have k-anonymity of k=3 or more. In this case, the server CPU 12 does not use a copy of the existing rule DB 32, but creates a new rule DB 32 using the input individual numbers accumulated in the accumulation DB 31.

The rule creation subroutine may be, for example, a subroutine that generates a rule for converting the input form 28 into the output form 29 so as to have Pk-anonymity.

FIG. 14 is a flowchart showing the flow of sequential data processing. The program shown in FIG. 14 is a process that is sequentially executed each time the server CPU 12 receives the input individual number 28 from the network. The processing flow of the program according to the present embodiment will be described with reference to FIG.

The server CPU 12 activates a conversion processing subroutine (step S532). The conversion processing subroutine is a subroutine for converting the input individual number 28 into the output individual number 29 based on the rule recorded in the rule DB 32. The process flow of the conversion process subroutine will be described later.

The server CPU 12 transmits the output form 29 to the network (step S533). The server CPU 12 determines whether or not the input individual number 28 and the output individual number 29 match (step S534). When it is determined that they do not match (NO in step S534), the server CPU 12 accumulates the input individual number 28 in the accumulation DB 31 (step S535). Specifically, the server CPU 12 adds a new record to the storage DB 31. The server CPU 12 records the received data of the input form 28 in the input form field. The server CPU 12 records “not yet” in the usage field.

When it is determined that they match (YES in step S534) and after the end of step S535, the server CPU 12 ends the process.

FIG. 15 is a flowchart showing the processing flow of the conversion processing subroutine. The conversion processing subroutine is a subroutine for converting the input individual number 28 into the output individual number 29 based on the rule recorded in the rule DB 32.

The server CPU 12 sets the counter I to the initial value 1 (step S545). The server CPU 12 determines whether or not to apply the I-th record of the rule DB 32 to the input form 28 (step S542). Specifically, when the input individual number 28 matches the data recorded in the input individual number field of the I-th record of the rule DB 32, the server CPU 12 determines to apply the record.

When it is determined that it is not applied (NO in step S542), the server CPU 12 adds 1 to the counter I (step S543). The server CPU 12 returns to step S542. If it is determined to apply (YES in step S542), the server CPU 12 converts the input individual number 28 to create the output individual number 29 (step S544). Specifically, the server CPU 12 sets the data recorded in the output number field of the I-th record of the rule DB 32 as the data of the output number 29. After that, the server CPU 12 ends the process.

According to the present embodiment, it is possible to provide the information processing system 10 that updates the rules used in the processing while sequentially processing the input individual numbers 28 and outputting the anonymized output individual numbers 29. Therefore, the first user can receive the anonymized output vote 29 each time the input vote 28 is generated and utilize it for marketing activities and the like.

Since the rule used for conversion of the input form 28 is updated at any time, even when the tendency of the input form 28 changes, anonymization can be appropriately performed.

As described above, the rule creation subroutine described with reference to FIG. 13 is an example. It is desirable to use a subroutine that implements an algorithm that creates rules according to the needs of the first user.

It is desirable that the input DB 28 is stored in the storage DB 31 according to the algorithm for creating the rule. All input individual pieces 28 may be accumulated in the accumulation DB 31 without performing the determination in step S534. After the predetermined number of input votes 28 are recorded in the accumulation DB 31, the old input votes 28 may be sequentially deleted to keep the number of records accumulated in the accumulation DB 31 constant.

A field may be provided in the storage DB 31 to record the date and time when the input individual form 28 is stored, and a record for which a certain time has elapsed after storage may be deleted. The record for which the input individual number 28 is acquired in step S511 may be deleted without providing the use field in the storage DB 31. The server CPU 12 may record only some of the items recorded in the input form 28 in the storage DB 31.

[Second Embodiment]
The second embodiment relates to the information processing system 10 in which different CPUs perform rule generation and sequential data processing. Note that the description of the same parts as those in the first embodiment will be omitted.

FIG. 16 is an explanatory diagram showing the configuration of the information processing system 10 according to the second embodiment. The information processing system 10 includes a server 11, a conversion server 18, a first client 21 and a second client 25. The server 11, the conversion server 18, the first client 21, and the second client 25 are connected via a network.

The conversion server 18 is a server that acquires the input individual number 28, converts it into the output individual number 29, and outputs it. The conversion server 18 of the present embodiment is an information device such as a general-purpose personal computer or a large-scale computer. Further, the server 11 and the conversion server 18 according to the present embodiment may be virtual machines that operate on the same hardware. The conversion server 18 is an example of the conversion unit according to the present embodiment.

Like the server 11, the conversion server 18 includes a CPU, a main storage device, an auxiliary storage device, and a communication unit. A copy of the rule DB 32 is stored in the auxiliary storage device of the conversion server 18. Illustration of the internal configuration of the conversion server 18 is omitted.

FIG. 17 is a flowchart showing the flow of processing of the program according to the second embodiment. The process flow of this embodiment will be described with reference to FIG.

The CPU of the second client 25 acquires the input individual numbers 28 that are sequentially generated (step S601). The CPU of the second client 25 transmits the acquired input form 28 to the server 11 and the conversion server 18 via the network (step S602).

When the server CPU 12 receives the input form 28, the server CPU 12 performs interrupt processing and stores the data of the input form 28 in the storage DB 31. The interrupt processing when the input form 28 is received is omitted from the flowchart.

The server CPU 12 acquires the notification instructing the start of the rule generation processing (step S653). The notification is generated by a clock built in the server 11 at a predetermined time or at a predetermined time interval. The notification may be, for example, a signal received via the network or an interrupt signal.

The server CPU 12 activates a rule creation subroutine (step S654). The rule creation subroutine is a subroutine for creating a rule to be recorded in the rule DB 32 based on the input pieces 28 accumulated in the accumulation DB 31. The rule creation subroutine is the same as the subroutine described with reference to FIG. 13, for example.

The server CPU 12 updates the rule DB 32 with the rule created in step S654. The server CPU 12 transmits the rule DB 32 to the conversion server 18 (step S655). The server CPU 12 determines whether to end the process (step S656). The case of ending the processing is, for example, the case of receiving an input for ending the processing of generating the processing rule via the network.

When it is determined that the processing is not to be ended (NO in step S656), the server CPU 12 returns to step S653. When it is determined that the processing is to be ended (YES in step S656), the server CPU 12 ends the processing.

The CPU of the conversion server 18 receives the input form 28 (step S641). The CPU of the conversion server 18 activates a conversion processing subroutine (step S642). The conversion processing subroutine is a subroutine for converting the input individual number 28 into the output individual number 29 based on the rule recorded in the rule DB 32. The conversion processing subroutine is the same subroutine as the subroutine described with reference to FIG. 15, for example.

The CPU of the conversion server 18 transmits the output number 29 to the network (step S643). After that, the CPU of the conversion server 18 goes into a standby state.

The CPU of the conversion server 18 receives the rule DB 32 transmitted in step S655 (step S644). The CPU of the conversion server 18 updates the copy of the rule DB 32 stored in the auxiliary storage device (step S645). After that, the CPU of the conversion server 18 goes into a standby state.

According to the present embodiment, even when the frequency of occurrence of the input individual number 28 is high, the information processing system for updating the rule used for the processing while sequentially processing the input individual number 28 and outputting the output individual number 29 10 can be provided.

The rule DB 32 may be stored in a storage device (not shown) connected to the network. In this case, the conversion server 18 can perform the conversion process of step S642 using the rule DB 32 stored in the storage device (not shown).

[Third Embodiment]
The present embodiment relates to an information processing system 10 that converts an input individual number 28 in which a purchase record of Internet shopping is recorded into an output individual number 29 in which recommended products are recorded. Note that the description of the same parts as those in the first embodiment will be omitted.

In the present embodiment, the first client 21 is the same as the second client 25. That is, the output client 29 output by the server CPU 12 is received by the second client 25 which has transmitted the original input client 28 via the network.

FIG. 18 is an explanatory diagram illustrating the conversion result of the third embodiment. FIG. 18 shows an input individual form 28 in which the products purchased by the customer through the Internet shopping are described and an output individual form 29 in which the recommended products are described. One line in FIG. 18 shows one online shopping transaction.

FIG. 19 is an explanatory diagram showing an example of the rule DB 32 according to the third embodiment. The rule DB 32 is No. It has a field, a condition field, and a recommended product field. The rule DB 32 has one record for one rule used for conversion.

In the present embodiment, the second client 25 creates an input ticket 28 describing the product purchased by the customer through internet shopping and sends it to the network. The server CPU 12 converts the input form 28 into an output form 29 based on the rule DB 32, and transmits the output form 29 to the second client 25 via the network. The server CPU 12 accumulates the input form 28 in the accumulation DB 31. The second client 25 displays the recommended product for the customer on the Internet shopping screen based on the output individual number 29.

The conversion process will be described more specifically. According to the first input form 28 shown in FIG. 18, the customer purchases the learning desk and the chair, but does not purchase the school bag. The server CPU 12 determines that the school bag is a recommended product based on the rule DB 32. The server CPU 12 outputs the output form 29 in which the school bag is described.

According to the second input form 28 shown in FIG. 18, the customer purchases coffee beans and a mug. The server CPU 12 determines that the cookie is a recommended product based on the rule DB 32. The server CPU 12 outputs the output form 29 in which the cookie is described.

The server CPU 12 creates and updates the rule DB 32 based on the statistical analysis result of the input individual pieces 28 accumulated in the accumulation DB 31 and the information such as season and fashion.

According to the present embodiment, it is possible to provide the information processing system 10 that promptly outputs the recommended product according to the product purchased by the customer.

The input ticket 28 includes information on the past purchase history of the same customer, and the rule DB 32 may use the past purchase history to determine recommended products. By doing so, it is possible to provide the information processing system 10 that recommends a product such as a consumable item that can be expected to be regularly purchased to the customer in a timely manner.

In addition, it is possible to provide an arbitrary information processing system 10 that sequentially converts the input individual number 28 into the output individual number 29 and updates the rules used for the conversion in parallel.

[Embodiment 4]
FIG. 20 is a functional block diagram showing the operation of the information processing apparatus according to the fourth embodiment. The server 11, which is an example of the information processing apparatus according to the present embodiment, operates as follows under the control of the server CPU 12.

The information processing apparatus 11 includes an acquisition unit 51 that acquires the input individual number 28, a conversion unit 52 that converts the input individual number 28 acquired by the acquisition unit 51 based on a rule, and an input individual number that the acquisition unit 51 acquires. A storage unit 53 that stores 28, a generation unit 54 that generates a new rule based on the plurality of input individual numbers 28 that the storage unit 53 has accumulated, and a new generation unit 54 that generates a rule that the conversion unit 52 uses. And an updating unit 55 that updates the rules.

[Fifth Embodiment]
The fifth embodiment relates to a mode in which a general-purpose computer and a program 47 are combined and operated to realize the information processing apparatus of the present embodiment. FIG. 21 is an explanatory diagram showing the configuration of the information processing system 10 according to the fifth embodiment. The configuration of this embodiment will be described with reference to FIG. Note that the description of the parts common to those of the first embodiment will be omitted.

The information processing system 10 of the present embodiment includes a server computer 45, a first client 21 and a second client 25. The server computer 45, the first client 21 and the second client 25 are connected via a network.

The server computer 45 includes a server CPU 12, a main storage device 13, an auxiliary storage device 14, a communication unit 15, a reading unit 17, and a bus. The server computer 45 is a general-purpose personal computer, an information device such as a large computer, or the like. Further, the computer 45 of this embodiment may be a virtual machine operating on a large-scale computer.

The program 47 is recorded in the portable recording medium 48. The server CPU 12 reads the program 47 via the reading unit 17 and stores it in the auxiliary storage device 14. Further, the server CPU 12 may read the program 47 stored in the semiconductor memory 49 such as a flash memory mounted in the server computer 45. Furthermore, the server CPU 12 may download the program 47 from another server computer (not shown) connected via the communication unit 15 and a network (not shown) and store it in the auxiliary storage device 14.

The program 47 is installed as a control program for the server computer 45, loaded into the main storage device 13 and executed. As a result, the server computer 45 functions as the server 11 described above.

The technical features (components) described in each embodiment can be combined with each other, and by combining, new technical features can be formed.
It should be considered that the embodiments disclosed this time are exemplifications in all points and not restrictive. The scope of the present invention is defined not by the above meaning but by the scope of the claims, and is intended to include meanings equivalent to the scope of the claims and all modifications within the scope.

Regarding the embodiments including the above-described first to fifth embodiments, the following supplementary notes are further disclosed.

(Appendix 1)
An acquisition unit that acquires the input number,
A conversion unit that converts the input individual number acquired by the acquisition unit based on a rule;
A storage unit that stores the input individual number acquired by the acquisition unit;
A generation unit that generates a new rule based on the plurality of input votes accumulated by the accumulation unit;
An information processing apparatus, comprising: an update unit that updates a rule used by the conversion unit to a new rule generated by the generation unit.
(Appendix 2)
The information processing apparatus according to appendix 1, wherein the conversion unit sequentially converts the acquired input individual number.
(Appendix 3)
3. The information processing device according to appendix 1 or 2, wherein the conversion unit operates preferentially over the generation unit.
(Appendix 4)
4. The information processing device according to any one of appendices 1 to 3, wherein the conversion unit operates with priority over the update unit.
(Appendix 5)
When the generation unit determines that the input unit not used for generating the rule is accumulated in the accumulation unit, the generation unit starts generation of a new rule. The information processing device described.
(Appendix 6)
The information processing apparatus according to any one of appendices 1 to 5, wherein the rule is a rule for anonymizing the input individual vote.
(Appendix 7)
The information processing device according to any one of appendices 1 to 6, wherein the storage unit does not store the input individual number when the input individual number and a conversion result obtained by converting the input individual number by the conversion unit are the same.
(Appendix 8)
Get the input number,
Convert the obtained input votes based on rules,
Accumulate the acquired input votes,
Generate a new rule based on the plurality of accumulated input votes,
An information processing method for causing a computer to execute processing for updating a rule for converting the input individual number to a new rule that has been generated.
(Appendix 9)
Get the input number,
Convert the obtained input votes based on rules,
Accumulate the acquired input votes,
Generate a new rule based on the plurality of accumulated input votes,
A program that causes a computer to execute a process of updating a rule for converting the input individual number to a new rule that has been generated.

10 Information Processing System 11 Server (Information Processing Device)
12 server CPU
13 main storage device 14 auxiliary storage device 15 communication unit 17 reading unit 18 conversion server 21 first client 25 second client 28 input count 29 output count 31 storage DB
32 Rule DB
45 server computer 47 program 48 portable storage medium 49 semiconductor memory 51 acquisition unit 52 conversion unit 53 storage unit 54 generation unit 55 update unit

Claims (9)

An acquisition unit that acquires the input individual number including multiple items ,
A conversion unit that converts the input votes acquired by the acquisition unit into output votes including the same number of items based on a rule;
A storage unit that stores the input individual number acquired by the acquisition unit;
A generation unit that generates a new rule based on the plurality of input votes accumulated by the accumulation unit;
An information processing apparatus, comprising: an update unit that updates a rule used by the conversion unit to a new rule generated by the generation unit. The information processing apparatus according to claim 1, wherein the conversion unit sequentially converts the acquired input individual number. The information processing apparatus according to claim 1, wherein the conversion unit operates with priority over the generation unit. The information processing apparatus according to claim 1, wherein the conversion unit operates with priority over the update unit. The generation unit starts generation of a new rule when it is determined that the input individual pieces not used for generating the rule are stored in the storage unit. Information processing device described in. The information processing apparatus according to claim 1, wherein the rule is a rule that anonymizes the input individual vote. If the conversion result of the conversion unit and the input microdata is obtained by converting the input microdata are the same, the storage unit, any one of claims 1 to 6 which do not accumulate the input microdata The information processing device according to 1. Get the input vote that contains multiple items ,
Convert the obtained input vote into an output vote containing the same number of items based on rules,
Accumulate the acquired input votes,
Generate a new rule based on the plurality of accumulated input votes,
An information processing method for causing a computer to execute a process of updating a rule for converting the input individual number to a new rule that has been generated. Get the input vote that contains multiple items ,
Convert the obtained input vote into an output vote containing the same number of items based on rules,
Accumulate the acquired input votes,
Generate a new rule based on the plurality of accumulated input votes,
A program that causes a computer to execute a process of updating a rule for converting the input individual number to a new generated rule.

Images