Information processing device, information processing method, and information processing program

Abstract

To provide a third person with information related to a user's action history without sharing personal information on the user.SOLUTION: An information processing device 100 includes an extraction part 121, a registration part 122, an acquisition part 123, and a notification part 124. The extraction part 121 compares contact destination information on a customer of a utilization business operator with contact destination information on a user, and extracts an identifier corresponding to coincident contact destination information. The registration part 122 associates the identifier extracted by the extraction part 121 with a prescribed notification key to register them in a storage part 130. The acquisition part 123 acquires a medium whose data is read by a reading device 300 or the identifier for identifying the user from the reading device 300. The notification part 124 retrieves whether the identifier acquired by the acquisition part 123 is registered in the storage part 130, and notifies the utilization business operation of the notification key corresponding to the identifier if it is registered.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to an information processing device, an information processing method, and an information processing program. [Background technology]

[0002] Conventionally, there are services that notify pre-registered people when a user passes through a station ticket gate using an authentication medium such as an IC card (see, for example, Non-Patent Document 1). In addition, ticket gate passage information of a specific user represents the user's behavioral history, and is therefore in demand from companies that handle statistical information and conduct marketing. However, because ticket gate passage information includes information equivalent to personal information, such as the user's contact information and the IC card's unique number, permission from the user must be obtained before using this information. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] “Mamorail service details | Child monitoring service,” [online], [Retrieved October 27, 2023], Internet: https: / / www.mamorail.jp / service / Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the above-mentioned conventional technology, it is not possible to provide information about a user's behavior history to a third party without sharing the user's personal information. For example, in the conventional technology, ticket gate passage information is notified to a pre-registered person together with the above-mentioned information equivalent to personal information, thereby associating the ticket gate passage information with the user. Therefore, it is not possible to provide information about a user's behavior history to a third party without sharing the user's personal information. [Means for solving the problem]

[0005] In order to solve the above-mentioned problems and achieve the objectives, the information processing device of the present invention is characterized by having an extraction unit that compares the contact information of the customer of the using business with the contact information of the user and extracts an identifier corresponding to the matching contact information; a registration unit that associates the identifier extracted by the extraction unit with a predetermined notification key and registers it in a memory unit; an acquisition unit that acquires from the reading device an identifier that identifies the medium or user whose data has been read by the reading device; and a notification unit that searches to see if the identifier acquired by the acquisition unit is registered in the memory unit, and if so, notifies the using business of the notification key corresponding to the identifier. [Effects of the Invention]

[0006] According to the present invention, it is possible to provide information about a user's behavior history to a third party without sharing the user's personal information. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating an example of the overall configuration of a system according to an embodiment. [Figure 2] FIG. 2 is a block diagram illustrating an example of the configuration of the information processing device according to the embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example of a user business registration list according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a distribution PF customer list according to the embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of a usage notification match table according to the embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of data registered in the member system server according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating a specific example of processing by the registration unit according to the embodiment. [Figure 8] FIG. 8 is a diagram illustrating a specific example of processing by the registration unit according to the embodiment. [Figure 9]FIG. 9 is a diagram showing a specific example of information notified by the notification unit according to the present embodiment. [Figure 10] FIG. 10 is a diagram illustrating a specific example of processing by the information processing device according to the embodiment. [Figure 11] FIG. 11 is a diagram illustrating a specific example of processing by the information processing device according to the embodiment. [Figure 12] FIG. 12 is a flowchart showing an example of the flow of processing by the information processing device according to the embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of the overall configuration of a system according to a modified example. [Figure 14] FIG. 14 is a diagram illustrating an example of a computer that executes an information processing program. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, embodiments of an information processing device, an information processing method, and an information processing program according to the present application will be described in detail with reference to the accompanying drawings. Note that the information processing device, the information processing method, and the information processing program according to the present application are not limited to these embodiments.

[0009] [Overall structure] First, the overall configuration of the system according to the embodiment will be described. Fig. 1 is a diagram showing an example of the overall configuration of the system according to the embodiment. In the system shown in Fig. 1, an information processing device 100 and a member system server 400 owned by a service provider of a notification service of a user's behavior history according to the embodiment, a service provider server 200 owned by a service user, and a reading device 300-1 installed at a ticket gate of a station for reading a user or a medium entering the station and identifying the user are each connected to each other so as to be able to communicate with each other via a network.

[0010] In addition, in the network configuration shown in Fig. 1, each device may communicate via any communication network, whether wired or wireless, such as the Internet, a LAN (Local Area Network), or a VPN (Virtual Private Network). Note that the configuration shown in Fig. 1 is merely an example, and the specific configuration and the number of devices are not particularly limited.

[0011] The information processing device 100 is a server device that stores a distribution PF (Platform) customer list, which is a customer list held by the service provider, a usage notification match table (described later), etc., and is realized by a computer, etc. Similarly, the user service provider server 200 is a server device that stores a user service provider registration list, which is a customer list held by the service user, and is realized by a computer, etc.

[0012] The reader 300-1 is an information processing device that has the function of reading a user or a medium such as an IC card owned by the user and identifying the user from the read information, and is installed at a ticket gate installed at a station. The member system server 400 is a server device separate from the information processing device 100 that stores big data such as service usage history information and statistical information collected by a service provider about its own customers, and is realized by a computer, a cloud system, or the like.

[0013] The information processing device 100 compares the contact information of the customer of the service provider with the contact information of the user, extracts an identifier corresponding to the matching contact information, associates the extracted identifier with a predetermined notification key, and registers it in a storage unit.The information processing device 100 then obtains from the reading device 300 an identifier that identifies the medium or user from which data has been read by the reading device 300, searches to see if the identifier is registered in the storage unit, and if so, notifies the service provider of the notification key corresponding to the identifier.

[0014] For example, the information processing device 100 receives a user business registration list, which is a customer list of the user business, from the user business server 200, and extracts the IC card number assigned to the user corresponding to the email address for a customer listed in the customer list of the service provider that the information processing device 100 owns that matches the email address of the customer listed in the user business registration list. Next, the information processing device 100 associates the extracted IC card number with a notification key consisting of a preset character string, for example, and registers them in a storage unit.

[0015] Then, the information processing device 100, for example, obtains the number of the IC card read by a ticket gate at a station, searches to see if the number is registered in the memory unit, and if it is registered, sends a notification key corresponding to the number to the user company server 200 to notify the user company of the information.

[0016] As a result, the information processing device 100 can provide information about the user's behavioral history, such as ticket gate passage information, to the user business operator along with the corresponding notification key, rather than personal information such as the user's IC card number, thereby providing information about the user's behavioral history to a third party without sharing the user's personal information.

[0017] [Configuration of information processing device 100] An example of the functional configuration of the information processing device 100 will be described below. Fig. 2 is a block diagram showing an example of the configuration of the information processing device according to the embodiment. As shown in Fig. 2, the information processing device 100 has a communication unit 110, a control unit 120, and a storage unit 130.

[0018] The communication unit 110 is realized by, for example, a network interface card (NIC), etc. For example, the communication unit 110 controls communication regarding various information exchanged with connected devices, and mediates the processing of an acquisition unit 123 and a notification unit 124, which will be described later.

[0019] The storage unit 130 is realized by a storage device such as a RAM (Random Access Memory) or a hard disk, for example. The storage unit 130 stores data and programs necessary for various processes by the control unit 120. The storage device may be realized by a storage system or the like installed outside the information processing device 100. The storage unit 130 has, for example, a distribution PF customer list storage unit 131 and a usage notification match table storage unit 132.

[0020] The distribution PF customer list storage unit 131 registers a distribution PF customer list that is pre-registered in the information processing device 100, which is a distribution PF owned by the service provider. The distribution PF customer list is customer information owned by the service provider, and is a list that describes information about the customer, such as the customer's name, customer contact information, and also the IC card number assigned to the customer.

[0021] In addition, the distribution PF customer list can register not only information from IC cards but also, for example, segment information of users registered through other services provided by the service provider. Here, segment information refers to information about users, such as their name, address, gender, hobbies, preferences, whether they are royal customers, etc.

[0022] The usage notification matching table storage unit 132 stores a usage notification matching table in which identifiers and notification keys are associated with each other, which is registered by the registration unit 122 described later. The usage notification matching table is used when the notification unit 124 described later notifies the user business operator of ticket gate passage information, and by registering this information, notification processing can be performed without holding the user business operator registration list described later.

[0023] Here, the data used in the processing of each component of the control unit 120, which will be described later, will be explained in order. First, with reference to FIG. 3, the user business registration list transmitted from the user business server will be explained. FIG. 3 is a diagram showing an example of a user business registration list according to an embodiment. The user business registration list is customer information held by the user business, and is a list that lists contact information of customers who are the subject of notification of behavioral history by the information processing device 100. Note that since the user business registration list contains personal information such as customer contact information, it is temporarily loaded when transmitted from the user business, and is deleted after the usage notification matching table is created.

[0024] The user business registration list shown in the example of Figure 3 is composed of the following items: "membership number," "email address," and "telephone number." The "membership number" is the number assigned by the user business to the customer to whom the business wishes to receive notifications, and the "email address" and "telephone number" are the email address and telephone number of the customer corresponding to the membership number. Specifically, the user business registration list lists the following information for "membership number: 0001": "email address: a@xx.ne.jp" and "telephone number: 080-aaaa-aaaa."

[0025] Next, the distribution PF customer list will be described with reference to FIG. 4. FIG. 4 is a diagram illustrating an example of the distribution PF customer list according to the embodiment. The distribution PF customer list illustrated in the example of FIG. 4 is composed of the following items: "Customer Number," "Media Number," "Email Address," and "Telephone Number." The "Customer Number" is a number assigned by a service provider to a customer who is the target of a notification service for user behavior history, and the "Media Number" is a number of an IC card owned by the customer corresponding to the customer number. Note that the "Customer Number" may be the same character string as the "Member ID" described below. Specifically, the distribution PF customer list includes the following information for "Customer Number: 0001": "Media Number: aaaa," "Email Address: a@xx.ne.jp," and "Telephone Number: 080-aaaa-aaaa."

[0026] Next, the usage notification matching table will be described with reference to FIG. 5. FIG. 5 is a diagram illustrating an example of a usage notification matching table according to an embodiment. The usage notification matching table illustrated in the example of FIG. 5 is configured with the following fields: "medium number," "member ID," and "notification key." The "member ID" is a unique character string assigned by the service provider to each customer, and the "notification key" is a unique character string assigned to each medium number so that the user service provider can identify the user. Note that the "member ID" may be an ID assigned to all customers of the service provider, including users who are the target of services other than the user behavior history notification service according to this embodiment, while the "customer number" may be a number assigned to each customer who is the target of the user behavior history notification service according to this embodiment. Specifically, the usage notification matching table lists the following information for "medium number: aaaa": "member ID: XXX12345" and "notification key: key a."

[0027] Next, the data stored by the member system server 400 in association with the aforementioned member ID will be described with reference to Figure 6. Figure 6 is a diagram showing an example of data registered in the member system server according to the embodiment. As described above, the member system server 400 stores big data collected about each customer of the service provider in association with the member ID, for example, storing the following items: "member ID," "medium number," "service used," "purchase history," "estimated entry station," and "estimated exit station."

[0028] Here, "used services" stores information such as the names of services used by members and service IDs for multiple services provided by service providers. "Purchase history" stores information such as the names and product IDs of products purchased by members using services provided by service providers. "Estimated entry station" stores stations where members frequently enter by storing stations where members frequently enter. For more accuracy, the entry station may be estimated separately for weekdays and holidays. "Estimated exit station" stores stations where members frequently exit by calculating information based on the entry station and the day of the week (weekdays, holidays, etc.), for example.

[0029] In addition to the information shown in Figure 6, the member system server 400 stores a wide variety of data linked to member IDs in the format shown in Figure 6. As a result, the member system server 400 can manage and store a wide variety of data for each member ID, in addition to the minimum customer information listed in the distribution PF customer list.

[0030] Returning to the explanation of Fig. 2, the control unit 120 is realized by a processor such as an integrated circuit, such as a CPU (Central Processing Unit), an MPU (Micro Processing Unit), an ASIC (Application Specific Integrated Circuit), or an FPGA (Field Programmable Gate Array), executing various programs stored in a storage device inside the information processing device 100 using a RAM or the like as a work area. For example, in the example shown in Fig. 2, the control unit 120 has an extraction unit 121, a registration unit 122, an acquisition unit 123, and a notification unit 124, and also has an estimation unit 125 as necessary.

[0031] The extraction unit 121 compares the contact information of the customer of the using business with the contact information of the user, and extracts an identifier corresponding to the matching contact information. For example, the extraction unit 121 refers to the using business registration list sent from the using business and the information registered in the distribution PF customer list storage unit 131, and compares the email addresses, which are the contact information listed in each list. Then, the extraction unit 121 refers to the information registered in the distribution PF customer list storage unit 131, for example, and extracts the IC card numbers corresponding to the customers with matching email addresses.

[0032] Here, the identifier extracted by the extraction unit 121 may be the number of the IC card owned by the customer, or other information that can uniquely identify the customer, such as a customer number or a password assigned to the customer.

[0033] The registration unit 122 associates the identifier extracted by the extraction unit 121 with a predetermined notification key and registers them in the storage unit 130. For example, the registration unit 122 registers a usage notification matching table (see FIG. 5 ) in the usage notification matching table storage unit 132, which associates the identifier extracted by the extraction unit 121 with a notification key, which is a predetermined arbitrary character string. The registration unit 122 can also register, for example, the extracted identifier, a medium number (IC card number), in association with a member ID along with the notification key. In this case, the registration unit 122 can obtain the member ID by, for example, searching the extracted medium number in the member system server 400.

[0034] Here, the notification key is not particularly limited as long as it is information that can uniquely identify each customer listed in the user business registration list, but information is set that prevents the customer's personal information from being identified from the notification key.

[0035] Furthermore, the registration unit 122 generates a notification key to be associated with the identifier extracted by the extraction unit 121 so that it differs for each user service provider, and registers the generated notification key in association with the identifier extracted by the extraction unit 121 in the storage unit 130. Here, a process for creating a different notification key for each user service provider will be described with reference to Fig. 7. Fig. 7 is a diagram showing a specific example of the process of the registration unit according to the embodiment.

[0036] Figure 7 shows an example in which there are two user companies, company A and company B, and the registration unit 122 uses the user company registration list received from each user company to create a usage notification matching table unique to each company.

[0037] Specifically, the extraction unit 121 compares the A company user business registration list sent from the A company user business server 200-1 with the distribution PF customer list, and extracts "medium number: aaaa" and "medium number: cccc" as identifiers of customers with matching email addresses.Then, the registration unit 122 creates an A company usage notification matching table that lists "medium number: aaaa"-"member ID: XXX12345"-"notification key: key Aa" and "medium number: cccc"-"member ID: XXX13579"-"notification key: key Ac".

[0038] The extraction unit 121 and registration unit 122 perform the same process for Company B, and create a Company B usage notification matching table that lists "medium number: aaaa"-"member ID: XXX12345"-"notification key: key Ba," "medium number: dddd"-"member ID: XXX54321"-"notification key: key Bd," and "medium number: eeee"-"member ID: XXX97531"-"notification key: key Be." This allows the registration unit 122 to create different notification keys for Company A and Company B for customers with "medium number: aaaa" that overlap between Company A and Company B, thereby preventing the personal information of a specific user from being known between the user businesses.

[0039] Furthermore, when the acquisition unit 123 acquires an identifier registered in the storage unit 130 for the first time, the registration unit 122 authenticates the user's identity, and if the authentication is successful, registers an authentication success flag in the storage unit 130. For example, when the acquisition unit 123, which will be described later, acquires an identifier registered in the storage unit 130 for the first time, the registration unit 122 authenticates the user's identity using answers to one or more pieces of information among information registered on a medium owned by the user, information on stations the user has passed through, information on stations the user has entered or exited from, information on whether the user owns a commuter pass, and information printed on the face of the commuter pass owned by the user. Then, if the authentication is successful, the registration unit 122 registers an authentication success flag, which is information indicating whether the authentication is successful, in the usage notification matching table storage unit 132.

[0040] Here, the authentication process for personal identification performed by the registration unit 122 will be described with reference to Fig. 8. Fig. 8 is a diagram showing a specific example of the process of the registration unit according to the embodiment. Fig. 8 shows an example in which a response to information on the face of a commuter pass owned by the user is used for personal identification authentication.

[0041] The registration unit 122 refers to the information registered in the usage notification matching table storage unit 132, and when it determines that the registered IC card number has been acquired by a ticket gate for the first time since registration, it sends a question to the contact information of the user who owns the IC card, prompting them to provide information about the designated commuter pass section written on the IC card commuter pass.The registration unit 122 then accepts the answer to the question and determines whether the identity authentication has been successful based on whether the answer is correct.If the identity authentication has been successful, the registration unit 122 registers an authentication success flag in the column for the IC card number in the usage notification matching table.

[0042] In the example of FIG. 8, the information "Kamata⇔Toranomon (connecting Shimbashi)" is written on an IC card commuter pass owned by a user. Then, the registration unit 122 sends a question to a smartphone owned by the user who has passed through a ticket gate for the first time since registration, asking, "Please tell us the designated section of the commuter pass you used." The user then answers the question with, "Boarding station: Kamata Station, disembarking station: Toranomon Station, via: Shimbashi Station." As a result of this answer, the registration unit 122 determines that the information on the commuter pass owned by the user registered in the distribution PF customer list or the like matches the answer, and therefore determines that the identity authentication has been successful, and registers an authentication success flag.

[0043] Returning to the explanation of Fig. 2, the acquiring unit 123 acquires from the reading device 300 an identifier that identifies the medium or user from which data has been read by the reading device 300. For example, the acquiring unit 123 acquires from the reading device 300 such as a ticket gate an identifier that can uniquely identify the user, such as the number of the IC card owned by the user, from information such as the IC card read by the reading device 300 or the user's face authentication image.

[0044] The identifier acquired by the acquiring unit 123 may be the same as or different from the identifier extracted by the extracting unit 121 described above. The acquiring unit 123 may collect data from the reading device 300 provided in the ticket gate at any timing. Furthermore, the acquiring unit 123 may acquire data directly from the reading device 300 provided in the ticket gate, or may acquire data via a server or the like, for example.

[0045] Furthermore, the acquiring unit 123 acquires, from the reading device 300, information about the location of the user who passed the reading device 300 and information about the time, along with the identifier. For example, for a user whose data was read by the reading device 300 or a user who owns a medium, the acquiring unit 123 acquires, from the reading device 300, the location where the reading device 300 is located and the time when the data was read by the reading device 300, along with the identifier, as the usage location and usage date and time.

[0046] Furthermore, the acquiring unit 123 acquires registration information, which is information registered in association with an identifier, from the reading device 300. For example, for a user whose data is read by the reading device 300 or a user who owns a medium, the acquiring unit 123 acquires registration information registered in association with the identifier, such as face information of a commuter pass purchased by the user or information on the balance charged to an IC card, together with the identifier.

[0047] Here, the acquisition unit 123 can, for example, acquire the above-mentioned registration information via the network from the member system server 400. Specifically, the acquisition unit 123 can search the member system server 400 for the IC card number of a user whose data has been read by the reading device 300 or a user who owns an IC card (medium), and acquire the information registered in association with the corresponding member ID as registration information registered in association with the identifier.

[0048] As a result, the information processing device 100 can provide the user business with a wide variety of information about users registered on the external server, the member system server 400, as information about the user corresponding to the notification key, through processing by the notification unit 124 described below.

[0049] The acquisition unit 123 also acquires, for example, from a reader 300 provided at a ticket gate, ticket gate passage information consisting of one or more of the following data: identifier, date and time of use, railway operator, station name, ticket gate name, entry / exit, model name, and boarding pattern. Here, the boarding pattern is information indicating, for example, commuter pass use, free ticket use, charge balance use, or a combination thereof. Note that the data acquired by the acquisition unit 123 is not limited to these.

[0050] The notification unit 124 searches whether the identifier acquired by the acquisition unit 123 is registered in the storage unit 130, and if it is registered, notifies the service provider of the notification key corresponding to the identifier.

[0051] For example, the notification unit 124 searches whether the number of the IC card acquired by the acquisition unit 123, which identifies the user whose data was read by the reading device 300 or the user who owns the medium, is registered as a medium number (see Figure 5) in the usage notification matching table registered in the usage notification matching table storage unit 132, and if it is registered, notifies the user business operator of the notification key corresponding to the number of the IC card.

[0052] In addition, the notification unit 124 may notify the user business operator of the location-related information and time-related information acquired by the acquisition unit 123, the registration information acquired by the acquisition unit 123, the ticket gate passage information acquired by the acquisition unit 123, and the behavioral pattern estimated by the estimation unit 125 described below, along with the notification key.

[0053] Here, the information notified to the user business by the notification unit 124 will be described with reference to Fig. 9. Fig. 9 is a diagram showing a specific example of information notified by the notification unit according to this embodiment. The example of Fig. 9 shows information notified to the user business by the notification unit 124 when a user registered as a notification target for the user business passes through the ticket gate at Shinjuku Station.

[0054] As shown in the example of Figure 9, the notification unit 124 notifies the user business operator of the notification key "Key a" corresponding to the user who passed through the ticket gate, as well as the location of use "Shinjuku Station," the date and time of use "2023 / 5 / 26 10:10:25," the face information of the commuter pass used "Shinjuku ⇔ Toranomon (used section)," the entry / exit information "Entry," the user's riding pattern "Commuter pass use," and the user's behavior pattern "Commuting to work / school."

[0055] Returning to the explanation of Fig. 2, the estimation unit 125 estimates the user's behavioral pattern based on the data acquired by the acquisition unit 123. For example, the estimation unit 125 estimates behavioral patterns indicating usual behavior such as commuting to work or school, hobbies, habits, etc., and unusual behavior such as overtaking a train, etc., from the ticket gate passage information acquired by the acquisition unit 123 and registration information registered in the member system server 400, etc.

[0056] Here, the estimation unit 125 can estimate a behavioral pattern by determining the user's tendency to use stations from the aggregated results of the specific user's past ticket gate passing information, for example. Specifically, the estimation unit 125 refers to the information on "exit station estimation" registered in the member system server 400, and when the user exits a station where the user has a high rate of exiting, the estimation unit 125 can determine that passing through (exiting from) the ticket gate at the exit station is a normal behavior and estimate a behavioral pattern such as "commuting to work or school."

[0057] Furthermore, the estimation unit 125 can estimate a user's behavior pattern by combining not only the ticket gate passage information but also, for example, the time period when the ticket gate was passed, the type of ticket (commuter pass, electronic money, etc.), and the most recent ticket gate passage history. Specifically, when ticket gate passage information such as "Exit Shinjuku Station at 10:00" is acquired, the estimation unit 125 refers to the ticket gate passage information at the most recent entrance station. Thereafter, when information such as "Enter Kichijoji Station at 9:00 with a commuter pass" is registered, the estimation unit 125 estimates that the user's behavior is normal. On the other hand, when information such as "Enter Tokyo Station at 9:30 with SF (electronic money)" is registered, the estimation unit 125 estimates that the user's behavior is not normal.

[0058] [Specific example] Next, the overall processing flow of the information processing device 100 according to the embodiment will be described with reference to Figures 10 and 11. Figures 10 and 11 are diagrams showing a specific example of processing of the information processing device according to the embodiment. Note that the following description will be given of a case where the reading device 300 is installed in a ticket gate, but the present invention is not limited to this.

[0059] First, with reference to Fig. 10, the process from accepting a user business registration list from a user business to sending a match result list containing notification keys corresponding to the user to the user business will be described. The information processing device 100 registers the above-mentioned distribution PF customer list (see Fig. 4) in the distribution PF customer list storage unit 131 (Fig. 10(a)). Next, the information processing device 100 accepts the user business registration list (see Fig. 3) from the user business server 200 and temporarily reads it (Fig. 10(b)).

[0060] Next, the extraction unit 121 compares the email addresses listed in the user business registration list with the email addresses listed in the distribution PF customer list, and extracts the matching email addresses "medium number: aaaa" of "a@xx.ne.jp" and "medium number: cccc" of "c@xx.ne.jp" (c in FIG. 10). The registration unit 122 then associates the extracted "medium number: aaaa" with "member ID: XXX12345" and "notification key: key a", and associates "member ID: XXX13579" and "notification key: key c" with "medium number: cccc", to generate a usage notification matching table, and registers it in the usage notification matching table storage unit 132 (d in FIG. 10).

[0061] Thereafter, the information processing device 100 transmits a match result list containing the customer numbers "No. 1" and "No. 3" on the user business registration list and the corresponding notification keys "Key a" and "Key c" from the usage notification match table to the user business server 200 (e in FIG. 10). After transmitting the match result list, the information processing device 100 then deletes the accepted user business registration list (f in FIG. 10).

[0062] Through the series of processes shown in Figure 10, the information processing device 100 can obtain information on the notification key corresponding to the customer who is the target of notification and is listed in the user business registration list, without notifying the user business of the customer's medium number.

[0063] Next, the process of notifying a user business operator when a user actually passes through a ticket gate will be described with reference to Fig. 11. The reading device 300 reads an authentication medium such as an IC card or two-dimensional code ticket that is read when the user passes through a ticket gate at a station, identifies the user who owns the medium, and registers ticket gate passage information (Fig. 11(a)). Next, the acquiring unit 123 acquires the "medium number: aaaa" of the authentication medium owned by the user, the usage location "Shinjuku Station," and the usage date and time "2023 / 5 / 26 10:10:25" from the ticket gate passage information registered in the reading device 300 (Fig. 11(b)).

[0064] Next, the notification unit 124 searches whether the acquired "medium number: aaaa" is registered in the usage notification matching table (c in FIG. 11). As a result of the search, it is registered in the usage notification matching table, so the notification unit 124 notifies the user service provider server 200 of the notification key "key a" corresponding to "medium number: aaaa", the usage location "Shinjuku Station", and the usage date and time "2023 / 5 / 26 10:10:25" as a ticket gate usage notification (d in FIG. 11). Thereafter, advertising information and the like related to the ticket gate usage notification are reflected from the user service provider server 200 to the user's terminal or the like (e in FIG. 11).

[0065] Through the series of processes shown in Figure 11, the information processing device 100 can notify the user's ticket gate usage notification to the user's service provider using the notification key obtained by the service provider through the process in Figure 10, thereby enabling the user's service provider to receive a ticket gate usage notification regarding the user's behavioral history without sharing the medium number, which is information equivalent to the user's personal information.

[0066] 〔flowchart〕 Next, an example of processing by the information processing device 100 according to this embodiment will be described with reference to Fig. 12. Fig. 12 is a flowchart showing an example of the flow of processing by the information processing device according to the embodiment.

[0067] First, the extraction unit 121 of the information processing device 100 compares the contact information of the customer of the service provider with the contact information of the user, and extracts an identifier corresponding to the matching contact information (S101). Then, the registration unit 122 associates the identifier with a predetermined notification key and registers it in the storage unit 130 (S102).

[0068] Then, the acquiring unit 123 acquires an identifier that identifies the medium or user read by the reading device 300 from the reading device 300 (S103). Then, the notifying unit 124 searches whether the acquired identifier is registered in the storage unit 130 (S104).

[0069] If the acquired identifier is registered in the storage unit 130 (S105; Yes), the information processing device 100 notifies the user business of the notification key corresponding to the identifier (S106), and ends the process. On the other hand, if the acquired identifier is not registered in the storage unit 130 (S105; No), the information processing device 100 ends the process.

[0070] 〔effect〕 The information processing device 100 according to this embodiment includes an extraction unit 121, a registration unit 122, an acquisition unit 123, and a notification unit 124. The extraction unit 121 compares contact information of customers of the service provider with contact information of the user, and extracts an identifier corresponding to the matching contact information. The registration unit 122 associates the identifier extracted by the extraction unit 121 with a predetermined notification key and registers the identifier in the storage unit 130.

[0071] The acquisition unit 123 acquires from the reading device 300 an identifier that identifies the medium or user from which data has been read by the reading device 300. The notification unit 124 searches to see if the identifier acquired by the acquisition unit 123 is registered in the storage unit 130, and if it is registered, notifies the user business of the notification key corresponding to the identifier.

[0072] This allows the information processing device 100 to notify the user business operator of information regarding the behavioral history of the user to be notified using a notification key corresponding to the user, thereby making it possible to provide information regarding the user's behavioral history to third parties without sharing the user's personal information.

[0073] In addition, in the information processing device 100, the acquisition unit 123 acquires, from the reading device 300, information regarding the location and time of the user who passed through the reading device 300, along with the identifier, and the notification unit 124 notifies the user business operator of the information regarding the location and time acquired by the acquisition unit 123, along with a notification key.

[0074] This allows the information processing device 100 to notify the user business of the location and time when the user or medium to be notified was read by the reading device 300, thereby allowing the user's behavioral history to be properly notified without sharing the user's personal information.

[0075] In addition, in the information processing device 100, the acquisition unit 123 acquires registration information, which is information registered in association with an identifier, from the reading device 300, and the notification unit 124 notifies the user business operator of the registration information acquired by the acquisition unit 123 together with a notification key.

[0076] This allows the information processing device 100 to notify the user business of information such as the user's product purchase history and charge balance information along with a notification key when the medium owned by the user to be notified is read by the reading device 300, thereby enabling the user business to provide the user business with information other than behavioral history that is useful to the user business.

[0077] In addition, in the information processing device 100, the registration unit 122 generates a notification key to be associated with the identifier extracted by the extraction unit 121, so that it is different for each user service provider, and associates the generated notification key with the identifier extracted by the extraction unit 121 and registers it in the memory unit 130.

[0078] As a result, even if a user is registered with multiple user companies, the information processing device 100 creates a different notification key for each user company, thereby preventing the personal information of a specific user from being known by different user companies.

[0079] In addition, in the information processing device 100, when the identifier registered in the memory unit 130 is acquired for the first time by the acquisition unit 123, the registration unit 122 authenticates the user's identity, and if the identity authentication is successful, registers an authentication success flag in the memory unit 130.

[0080] This allows the information processing device 100 to provide accurate information to the service provider by authenticating the user's identity before processing the notification of the user's behavioral history, and also takes measures to prevent fraudulent use, such as someone fraudulently obtaining station passage information by fraudulently registering using the user's IC card, etc.

[0081] In addition, in the information processing device 100, the registration unit 122 authenticates the user's identity using answers to one or more of the following information: information on stations the user has passed through, information on stations the user has entered or exited from, information on whether the user owns a commuter pass, and information printed on the face of the commuter pass owned by the user.

[0082] As a result, the information processing device 100 can authenticate the user's identity using information about stations the user has actually passed through and the face information of the commuter pass the user owns, thereby preventing accidental matches and performing accurate authentication of the user's identity, thereby preventing fraudulent use by third parties other than the user.

[0083] In addition, in the information processing device 100, the acquisition unit 123 acquires one or more data from the reading device 300 installed at the ticket gate, including the identifier, date and time of use, railway operator, station name, ticket gate name, entry / exit, model name, and boarding pattern, and the notification unit 124 notifies the user operator of the data acquired by the acquisition unit 123 together with a notification key.

[0084] This allows the information processing device 100 to notify the user business operator of detailed information regarding the user's passage through the ticket gate when the user to be notified passes through the ticket gate, along with a notification key, thereby enabling the user business operator to be provided with information other than the user's behavioral history that is useful to the user business operator.

[0085] The information processing device 100 also has an estimation unit 125. The estimation unit 125 estimates a behavioral pattern of the user based on the data acquired by the acquisition unit 123. In this case, the notification unit 124 notifies the user business of the behavioral pattern estimated by the estimation unit 125 together with a notification key.

[0086] This allows the information processing device 100 to notify the user business operator of information indicating whether the user's behavior when the user to be notified passes through the ticket gate is normal or not, along with the notification key, thereby enabling the user business operator to be provided with information other than the behavioral history that is useful to the user business operator.

[0087] [Modification] Up to this point, an embodiment of the present invention has been described, but the present invention may be embodied in various different forms other than the above-described embodiment. Here, the overall configuration of a system according to a modified example will be described with reference to Fig. 13. Fig. 13 is a diagram showing an example of the overall configuration of a system according to a modified example. In the above-described embodiment, a case where the reading device 300 is installed in a ticket gate at a station has been described, but the present invention is not limited to this.

[0088] The system shown in Figure 13 shows an example in which the information processing device 100 according to the embodiment described above, the user service provider server 200, the member system server 400, the reading device 300-1 installed at a station ticket gate that reads a user or medium entering the station and identifies the user, as well as the reading device 300-2 installed in an IC card reader for a bus or taxi, the reading device 300-3 installed in a device installed in a building that determines entry and exit using facial recognition, and the reading device 300-4 installed in a two-dimensional code reader or the like installed in a convenience store or the like are all connected to each other via a network so that they can communicate with each other.

[0089] Here, like the reading device 300-1 according to the embodiment described above, the reading devices 300-2 to 300-4 are information processing devices having a function of reading a user or a medium such as an IC card owned by the user and identifying the user from the read information. Note that the reading device 300 may be any device other than the reading devices 300-2 to 300-4, such as a device that performs fingerprint authentication, as long as it can acquire information indicating the user and identify the user.

[0090] As shown in FIG. 13, when the reading device 300 is provided in a two-dimensional code reader installed in a convenience store or the like, and when a user uses an IC card to purchase a product and reads the code, information such as the product purchase history is registered in the member system server 400 or the like as registration information.

[0091] 〔others〕 Furthermore, among the processes described in the above embodiments, all or part of the processes described as being performed automatically may be performed manually. Conversely, all or part of the processes described as being performed manually may be performed automatically using a known method. In addition, the information including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings may be changed as desired unless otherwise specified.

[0092] Furthermore, the components of each device shown in the figures are conceptual functional units and do not necessarily have to be physically or functionally configured as shown. In other words, the specific form of distribution and integration of each device and functional configuration is not limited to that shown in the figures, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc. Furthermore, the above-mentioned embodiments and the processes performed in each embodiment may be combined as appropriate within the scope of not causing any contradiction in the processing content.

[0093] 〔program〕 The information processing device 100 according to the above-described embodiment is realized by a computer 1000 having a configuration as shown in Fig. 14, for example. Fig. 14 is a diagram showing an example of a computer that executes an information processing program. The computer 1000 is connected to an output device 1010 and an input device 1020, and has a configuration in which a central processing unit 1030, a memory 1040, a storage 1050, an output IF (Interface) 1060, an input IF 1070, and a communication interface 1080 are connected via a bus 1090.

[0094] The central processing unit 1030 operates based on programs stored in the memory 1040 or storage 1050, programs read from the input device 1020, and the like, and executes various processes. The memory 1040 is a memory device, such as a RAM, that temporarily stores data used by the central processing unit 1030 for various calculations. The storage 1050 is a storage device in which data used by the central processing unit 1030 for various calculations and various databases are registered, and is realized by a ROM (Read Only Memory), an HDD (Hard Disk Drive), a flash memory, or the like.

[0095] The output IF 1060 is an interface for transmitting information to be output to an output device 1010 that outputs various types of information, such as a monitor or a printer, and is realized by a connector conforming to a standard such as USB (Universal Serial Bus), DVI (Digital Visual Interface), or HDMI (registered trademark) (High Definition Multimedia Interface). The input IF 1070 is an interface for receiving information from various input devices 1020, such as a mouse, keyboard, camera, etc., and is realized by a USB, etc. The input device 1020 may be an external storage medium such as a device that reads information from an optical recording medium, a magneto-optical recording medium, a tape medium, a magnetic recording medium, or a semiconductor memory, or a USB memory.

[0096] The communication interface 1080 receives data from other devices via the network N and sends it to the central processing unit 1030, and also transmits data generated by the central processing unit 1030 to other devices via the network N. The central processing unit 1030 controls the output device 1010 and the input device 1020 via the output IF 1060 and the input IF 1070. For example, the central processing unit 1030 loads a program from the input device 1020 or the storage 1050 onto the memory 1040 and executes the loaded program.

[0097] For example, when the computer 1000 functions as the information processing device 100 , the central processing unit 1030 of the computer 1000 executes a program loaded onto the memory 1040 to realize the functions of the control unit 120 .

[0098] Although some embodiments of the present application have been described above with reference to the drawings, these are merely examples, and the present invention may be embodied in other forms that incorporate various modifications and improvements based on the knowledge of those skilled in the art, including the aspects described in the Disclosure of the Invention section. Furthermore, the terms "section, module, unit" mentioned above can be read as "means" or "circuit," etc. For example, the term "applying section" can be read as "applying means" or "applying circuit." [Explanation of symbols]

[0099] 100 Information processing device 110 Communications Department 120 control section 121 Extraction part 122 Registration Department 123 Acquisition Department 124 Notification Department 125 Estimation part 130 Storage section 131 Distribution PF customer list storage unit 132 Usage notification match table storage unit 200 User's server 300, 300-1 to 300-4 reading device 400 Membership System Server

Claims

1. an extraction unit that compares contact information of customers of the service provider with contact information of the user and extracts an identifier corresponding to the matching contact information; a registration unit that associates the identifier extracted by the extraction unit with a predetermined notification key and registers the association in a storage unit; an acquisition unit that acquires, from a reading device, an identifier that identifies a medium or a user from which data has been read by the reading device; a notification unit that searches whether the identifier acquired by the acquisition unit is registered in the storage unit, and if it is registered, notifies the user business of a notification key corresponding to the identifier; An information processing device comprising:

2. the acquiring unit acquires, from the reading device, information relating to the position of the user who passed through the reading device and information relating to the time, together with the identifier; The information processing device according to claim 1 , wherein the notification unit notifies the user business of the information relating to the location and the information relating to the time acquired by the acquisition unit along with the notification key.

3. the acquiring unit acquires, from the reading device, registration information that is information registered in association with the identifier; 2. The information processing apparatus according to claim 1, wherein the notification unit notifies the user business of the registration information acquired by the acquisition unit together with the notification key.

4. The information processing device described in claim 1, characterized in that the registration unit generates a notification key to be associated with the identifier extracted by the extraction unit so that it is different for each user service provider, and associates the generated notification key with the identifier extracted by the extraction unit and registers it in the memory unit.

5. The information processing device according to claim 1, characterized in that the registration unit performs authentication of the user's identity when the identifier registered in the memory unit is acquired for the first time by the acquisition unit, and if the authentication of the user's identity is successful, registers an authentication success flag in the memory unit.

6. The information processing device described in claim 5, characterized in that the registration unit authenticates the user's identity using answers to one or more of the following information: information registered on the medium owned by the user, information on stations the user has passed through, information on stations the user has entered or exited, information on whether the user owns a commuter pass, and information written on the face of the commuter pass owned by the user.

7. the acquisition unit acquires, from the reading device provided at the ticket gate, one or more pieces of data from an identifier, a date and time of use, a railway operator, a station name, a ticket gate name, an entry / exit, a model name, and a boarding pattern; The information processing apparatus according to claim 1 , wherein the notification unit notifies the user business of the data acquired by the acquisition unit together with the notification key.

8. The system further includes an estimation unit that estimates a behavior pattern of a user based on the data acquired by the acquisition unit, The information processing device according to claim 7 , wherein the notification unit notifies the user business of the behavior pattern estimated by the estimation unit along with the notification key.

9. An information processing method executed by an information processing device, an extraction step of comparing contact information of the customer of the service provider with contact information of the user and extracting an identifier corresponding to the matching contact information; a registration step of registering the identifier extracted in the extraction step and a predetermined notification key in a storage unit in association with each other; an acquiring step of acquiring, from the reading device, an identifier for identifying the medium or user from which data has been read by the reading device; a notification step of searching whether the identifier acquired by the acquisition step is registered in the storage unit, and if it is registered, notifying the user business of a notification key corresponding to the identifier; An information processing method comprising:

10. an extraction step of comparing contact information of the customer of the service provider with contact information of the user and extracting an identifier corresponding to the matching contact information; a registration step of registering the identifier extracted in the extraction step and a predetermined notification key in a storage unit in association with each other; an acquiring step of acquiring, from the reading device, an identifier for identifying the medium or user from which data has been read by the reading device; a notification step of searching whether the identifier acquired by the acquisition step is registered in the storage unit, and if it is registered, notifying the user business of a notification key corresponding to the identifier; An information processing program that causes a computer to execute the above.

Images