Service notification setting method and service notification setting system

Abstract

To make a notification for a push-type government service simply without omission.SOLUTION: A service notification setting system which transmits a notification for providing a service to a target person generates individual attribute conditions including one or more attributes, and applies the individual attribute conditions to an attribute group in demographic statistics information to calculate a predicted value of a qualified recipient rate, which is a ratio of qualified recipients for a service, for each individual attribute condition, with respect to the total population. The system specifies, based on the individual attribute information, a person whose conditions in application history information fall under the conditions for receiving a past service which is the same as or similar to the service, and calculates a predicted value of an applicant rate which is a ratio of individuals who make applications for the service for each individual attribute condition, on the basis of an application history of the specified person. The system divides the predicted value of the applicant rate by the predicted value of the qualified recipient rate to calculate a predicted value of an application rate indicating the probability that the qualified recipients make applications for the service.SELECTED DRAWING: Figure 13

Description

[Technical field]

[0001] The present invention relates to a service notification setting method and a service notification setting system. [Background technology]

[0002] For example, Patent Document 1 discloses a procedure judgment device that judges applications for other services that are necessary in relation to an application for a service received at a counter of a government office or other entity that provides administrative services, based on the applicant's attribute information, etc.

[0003] Patent document 2 also discloses an extraction device that extracts advertising content to be delivered to each user based on attribute information of the users to whom the advertisements are delivered, the users' responses to the advertisements (number of clicks), indicators of the advertising effectiveness on the users, etc. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2017-41138 A [Patent Document 2] JP 2016-62501 A Summary of the Invention [Problem to be solved by the invention]

[0005] In recent years, push-type administrative services, in which local governments and other providers of administrative services proactively provide administrative services to residents who are users of those services, have become widespread. In push-type administrative services, there is a need for providers of administrative services to use online push notification services to provide notifications about administrative services easily and without omissions.

[0006] However, the technology disclosed in the above-mentioned Patent Document 1, even when combined with the conventional technology disclosed in Patent Document 2, is only to guide residents who have applied to use other administrative services. For this reason, no follow-up can be provided for residents who have not applied in the first place, making it difficult to prevent omissions in notifications of administrative services.

[0007] The present invention has been made in consideration of the above circumstances, and has an object to enable push-type administrative services to provide notifications of administrative services conveniently and without omissions. [Means for solving the problem]

[0008] As one aspect for solving the above problem, there is provided a service notification setting method executed by a service notification setting system that transmits a notification of the provision of a service to a target person, the service notification setting system having a processor, a memory, and a storage unit, the storage unit storing personal attribute information for each individual that manages the attributes of the individual, service receiving condition information for each service that manages the receiving conditions of the service for the individual to whom the service is provided, demographic information for each attribute group including one or more of the attributes that manages information regarding the population ratio of the individuals corresponding to the attribute group to the total population, and application history information for each past service that was provided in the past that manages application history indicating whether or not each of the individuals applied for the past service, and the processor stores the attribute information and the service receiving condition information for each service that the individual receives, the demographic information and the service receiving condition information for each attribute group that includes one or more of the attributes that manages information regarding the population ratio of the individuals corresponding to the attribute group to the total population, and the process of generating personal attribute conditions including one or more characteristics, applying the personal attribute conditions to the attribute groups in the demographic information to calculate a predicted value of a recipient eligibility rate, which is the ratio of recipients of the service for each personal attribute condition to the total population, identifying, based on the personal attribute information, the individuals who fall under the recipient conditions of the past service whose recipient conditions match or are similar to the service in the application history information, and calculating a predicted value of an applicant rate, which is the ratio of the number of individuals who will apply for the service for each personal attribute condition, based on the application history of the identified individuals, and dividing the predicted value of the applicant rate by the predicted value of the recipient eligibility rate, thereby calculating a predicted value of an application rate, which indicates the possibility that the recipients will apply for the service. Effect of the Invention

[0009] According to the present invention, in push-type administrative services, notifications of administrative services can be sent easily and without omissions. [Brief description of the drawings]

[0010] [Figure 1] 1 is a diagram showing the configuration of a service notification setting system according to an embodiment. [Diagram 2] FIG. 4 is a diagram showing input and output of a notification condition generating unit according to the embodiment. [Diagram 3]FIG. 4 is a diagram showing input and output of a notification condition setting unit according to the embodiment. [Figure 4] 5 is a diagram showing input and output of a notification target extraction unit according to the embodiment. FIG. [Diagram 5] 5A and 5B are diagrams showing input and output of an application receiving unit according to the embodiment. [Figure 6] FIG. 4 is a diagram showing a configuration of personal attribute information according to the embodiment. [Figure 7] FIG. 4 is a diagram showing the configuration of service receiving condition information according to the embodiment. [Figure 8] FIG. 4 is a diagram showing the configuration of notification / application history information according to the embodiment. [Figure 9] FIG. 4 is a diagram showing a configuration of demographic information according to the embodiment. [Figure 10] FIG. 4 is a diagram showing a configuration of notification condition candidate information according to the embodiment. [Figure 11] FIG. 4 is a diagram showing a configuration of notification condition information according to the embodiment. [Figure 12] FIG. 4 is a diagram showing a notification condition setting screen according to the embodiment. [Figure 13] 10 is a flowchart showing a notification condition generating process according to the embodiment. [Figure 14] 11 is an explanatory diagram of generation of personal attribute conditions and calculation of the number of notified persons according to the embodiment. [Figure 15] FIG. 13 is an explanatory diagram of calculation of a predicted value of the total number of service recipients according to the embodiment. [Figure 16] 6 is an explanatory diagram of calculation of a notification coverage rate according to the embodiment. [Figure 17] FIG. 13 is an explanatory diagram of calculation of the application rate of qualified persons according to the embodiment. [Figure 18] 11 is a flowchart showing notification target extraction processing according to the embodiment. [Figure 19] 10 is a flowchart showing an application reception process according to the embodiment. [Figure 20] FIG. 1 illustrates an example of the hardware configuration of a computer. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] The following embodiments will be described with reference to the drawings. Note that the following embodiments do not limit the scope of the invention, and not all of the elements and combinations thereof described in the embodiments are necessarily essential to the solution of the invention.

[0012] In the following description, a program realizing each processing function unit is executed by a processor to perform a predetermined process using a storage resource (e.g., a memory) and / or a communication interface device (e.g., a port) as appropriate. The processor is, for example, a CPU (Central Processing Unit). Therefore, the process executed by each processing function unit may be a process performed by a processor or a computer having the processor.

[0013] In the following explanation, various information is expressed in table format, but the information is not limited to table format and may be in CSV (Comma Separated Values) or other formats. Since various information does not depend on the data format, for example, "XXX table" can be called "XXX information".

[0014] In addition, among the items in the various information, the names of items that include information to distinguish the corresponding record from other records, such as "# (number)", "identification information", "ID", and "name", may be interchangeable. For example, "user ID" may be interchangeable with "user identification information".

[0015] (Configuration of the service notification setting system S according to the embodiment) 1 is a diagram showing the configuration of a service notification setting system S according to an embodiment. The service notification setting system S includes a notification condition setting server 1, a notification recipient extraction server 2, an operator terminal 3, and a user terminal 4. The notification condition setting server 1, the notification recipient extraction server 2, and the operator terminal 3 are connected via an intranet N1. The user terminal 4 is connected to the notification condition setting server 1 via the Internet N2 and the intranet N1.

[0016] The notification condition setting server 1 includes an application receiving unit 11, a notification condition generating unit 12, a notification condition setting screen control unit 13, service receiving condition information 14, notification condition candidate information 15, notification and application history information 16, and demographic information 17. The service receiving condition information 14, the notification condition candidate information 15, the notification and application history information 16, and the demographic information 17 are stored in a predetermined memory area (memory unit).

[0017] The notification target person extraction server 2 includes a notification target person extraction unit 21, personal attribute information 22, and notification condition information 23. The notification condition information 23 is stored in a predetermined storage area (storage unit).

[0018] The notification condition setting server 1 and the notification recipient extraction server 2 may be an integrated server built on the same hardware, or may be separate servers built on different hardware.

[0019] The operator terminal 3 accepts operations by a notification condition setter h3 to the notification condition setting server 1. The user terminal 4 is possessed by an applicant h4, and receives a notification from a server (not shown) equipped with a notification transmission function when the applicant h4 corresponds to a user set by the notification condition setting server 1 as a destination to which the notification is to be sent.

[0020] The notification condition setter h3 is, for example, a person in charge of a local government that provides administrative services or a worker who has been commissioned to do so. The applicant h4 is, for example, a resident or his / her agent who applies to the local government to receive administrative services.

[0021] (Input / output of the notification condition generating unit 12 according to the embodiment) 2 is a diagram showing input and output of the notification condition generating unit 12 according to the embodiment. The notification condition generating unit 12 receives personal attribute information 22, service receiving condition information 14, demographic information 17, and notification and application history information 16 as input, and generates and outputs notification condition candidate information 15.

[0022] (Input / output of notification condition setting screen control unit 13 according to the embodiment) 3 is a diagram showing input and output of the notification condition setting screen control unit 13 according to the embodiment. The notification condition setting screen control unit 13 receives notification condition candidate information 15 as input, and outputs notification condition information 23 based on the notification conditions set by the notification condition setter h3 via the notification condition setting screen 13D.

[0023] (Input / output of notification recipient extraction unit 21 according to the embodiment) 4 is a diagram showing input and output of the notification target extraction unit 21 according to the embodiment. The notification target extraction unit 21 receives personal attribute information 22 and notification condition information 23 as input, and extracts and outputs notification / application history information 16 in response to an instruction from a notifier h5. The notifier h5 is, for example, a person in charge of a local government providing administrative services or a worker commissioned by the local government.

[0024] 5 is a diagram showing input and output of the application receiving unit 11 according to the embodiment. The application receiving unit 11 receives input related to an application from the applicant h4, and stores it in the notification and application history information 16.

[0025] (Configuration of personal attribute information 22 according to the embodiment) 6 is a diagram showing the configuration of the personal attribute information 22 according to the embodiment. The personal attribute information 22 manages attribute information of individuals (for example, all residents of a local government) to whom the service notification setting system S provides a push-type service (for example, an administrative service).

[0026] Personal attribute information 22 has the columns "# (number)", "Name", "Age", "Household Composition", "Tax", and "Automatic Allowance". "# (number)" is identification information for the corresponding row. "Household Composition" indicates the members of the corresponding individual's household. "Tax" indicates whether the corresponding individual's household is subject to taxation. "Child Allowance" indicates whether the corresponding individual is receiving a child allowance. Note that in this specification, receiving the provision of a service is referred to as "receiving" regardless of whether or not property is provided.

[0027] (Configuration of service receiving condition information 14 according to the embodiment) Fig. 7 is a diagram showing the configuration of service receiving condition information 14 according to the embodiment. Service receiving condition information 14 has columns of "# (number)", "service", and "receiving condition". "# (number)" is identification information for the corresponding row. Service receiving condition information 14 indicates attribute information of individuals who are eligible for the administrative service indicated in "service" in "receiving condition".

[0028] (Notification and application history information 16 according to the embodiment) FIG. 8 is a diagram showing the configuration of notification and application history information 16 according to an embodiment. Notification and application history information 16 has columns of "# (number)", "Service", "Name", "Application", and "Notification". "# (number)" is identification information for the corresponding row. Notification and application history information 16 indicates by "Application" whether an individual indicated by "Name" has applied for the administrative service indicated by "Service", and by "Notification" whether the corresponding individual has been notified of the corresponding administrative service.

[0029] (Configuration of demographic information 17 according to the embodiment) FIG. 9 is a diagram showing the configuration of demographic information 17 according to an embodiment. The demographic information 17 has columns of "# (number)", "attribute A", "attribute B", and "conditional probability P(A|B)". "# (number)" is identification information for the corresponding row. The demographic information 17 indicates a conditional probability P(A|B) indicating the population ratio of individuals (or households) corresponding to "attribute A" among individuals (or households) corresponding to "attribute B" for all individuals whose attributes are recorded in the personal attribute information 22 (FIG. 6). "Attribute A" and "attribute B" of the conditional probability P(A|B) and "attribute A" of P(A) are referred to as "attribute groups including one or more attributes".

[0030] For example, #5 shows that the conditional probability of “children living together” when “foster children are present” is P(A|B) = 90%.

[0031] In addition, when "Attribute B" does not exist and there is only "Attribute A", as in rows #8 and #9, "P(A|B)" is not a conditional probability, but the unconditional probability P(A) of "Attribute A".

[0032] (Configuration of notification condition candidate information 15 according to the embodiment) 10 is a diagram showing the configuration of notification condition candidate information 15 according to an embodiment. The notification condition candidate information 15 has columns of "# (number)", "Service", "Notification condition candidate", "Number of people to be notified", "Estimated recipient eligible rate", "Estimated application rate of eligible recipients", and "Notification coverage rate". "# (number)" is identification information for the corresponding row.

[0033] As shown in FIG. 2, the notification condition candidate information 15 is information generated by the notification condition generation unit 12 using personal attribute information 22, service receiving condition information 14, demographic information 17, and notification / application history information 16 as input.

[0034] The notification condition candidate information 15 indicates how many individuals fall under each "notification condition candidate" for each "service" ("number of people to be notified") and what percentage of the "number of people to be notified" is predicted to be eligible to receive the corresponding government service ("predicted eligible recipient rate"). The notification condition candidate information 15 also indicates how many of the predicted eligible recipients are predicted to apply for benefits ("predicted application rate of eligible recipients"). The notification condition candidate information 15 also indicates what percentage of the number of people to whom notifications will be sent under the "notification condition candidate" is compared to the total number of eligible recipients of the service ("notification coverage rate").

[0035] (Configuration of notification condition information 23 according to the embodiment) 11 is a diagram showing the configuration of the notification condition information 23 according to the embodiment. The notification condition information 23 has columns of "# (number)", "service", and "notification condition". "# (number)" is identification information of the corresponding row.

[0036] As shown in Figure 3, the notification condition information 23 is information output by the notification condition setting screen control unit 13 after narrowing down the notification condition candidate information 15 based on the notification conditions set by the notification condition setter h3 via the notification condition setting screen 13D.

[0037] (Notification condition setting screen 13D according to an embodiment) Fig. 12 is a diagram showing a notification condition setting screen 13D according to an embodiment. As described with reference to Fig. 3, the notification condition setting screen 13D is a screen controlled by the notification condition setting screen control unit 13 and used by the notification condition setter h3 to input conditions for narrowing down the notification condition candidate information 15.

[0038] When notification condition candidate information 15 (FIG. 10) is selected and setting button 13D1 is pressed, notification condition setting screen 13D displays the selected notification condition candidate information 15. For each combination of notification condition candidates, notification condition setting screen 13D displays the "number of people to be notified," "predicted rate of eligible recipients," and "predicted application rate of eligible recipients" corresponding to notification condition candidate information 15 (FIG. 10).

[0039] The notification condition candidates are, for example, the "notification condition candidates" shown in the notification condition candidate information 15 (such as "tax exempt" or "taxable," "receiving" or "not receiving" for "child allowance," "living together" or "not living together" for "child in care," "age," and "household composition"). Selection of these combinations can be input using check boxes, etc.

[0040] In Figure 12, in each column of "Tax," "Child Allowance," "Children in Care," "Age," "Household Composition," etc., an "*" indicates that the corresponding option does not exist. Also, when a check is entered in the checkbox located at the far right side of each row of "Notification Condition Candidates," it indicates that the corresponding notification condition is set.

[0041] Here, refer to the service receipt condition information 14 (Fig. 7). It can be seen that the "notification condition candidates" shown in Fig. 12, with "tax" as "non-taxable," "child allowance" as "received," and "child in care" as "living together," correspond to the receipt conditions (confirmed receipt conditions) for which receipt has been confirmed for the "2011 Benefits for Low-Income / Child-Rearing Families." In other words, the confirmed receipt conditions indicate that the applicable individual is confirmed as a recipient of the service.

[0042] On the other hand, when "tax" is set to "taxable," it is a non-definite condition for receiving benefits, not a definite condition for receiving benefits. In other words, a non-definite condition for receiving benefits indicates that the applicable individual may, although not definite, become a recipient of the applicable service. Looking at "age" and "household composition" among the non-definite conditions for receiving benefits, when "age" is "24 or younger" or "household composition" is "single parent," the predicted rate of eligible recipients is high above a certain level, and the predicted rate of application by eligible recipients is low below a certain level. The notification condition setting screen 13D clearly displays cases where a high effect of service notifications is expected not only when the "notification condition candidate" corresponds to a definite condition for receiving benefits, but also when it corresponds to a non-definite condition for receiving benefits.

[0043] The notification condition setter h3 can efficiently notify the service by selecting a notification condition candidate in which the "predicted value of the eligible recipient rate" is less than a first specified value and the "predicted value of the application rate of eligible recipients" is equal to or greater than a second specified value.

[0044] In addition, notification condition candidates in which the ``predicted value of the eligible recipient rate'' is less than a first predetermined value and the ``predicted value of the application rate of eligible recipients'' is equal to or greater than a second predetermined value may be selected in the initial state by the notification condition setting screen control unit 13.

[0045] In the notification condition setting screen 13D, the notification coverage rate corresponding to the combination of the notification condition candidates for which a check has been entered is displayed in the notification coverage rate predicted value display area 13D2. The display in the notification coverage rate predicted value display area 13D2 is the total value of the notification coverage rate for each combination of the notification condition candidates for all combinations of the notification condition candidates selected by checking. In the notification coverage rate predicted value display area 13D2, the notification coverage rate is updated according to changes in the check.

[0046] In addition, the notification condition setter h3 may input the desired notification coverage rate in the notification coverage rate predicted value display area 13D2, and a check box may be automatically entered for the combination of notification condition candidates that results in a notification coverage rate that matches or is closest to the input value.

[0047] The notification condition setting screen 13D is also provided with a confirmation button 13D3 which is pressed by the notification condition setter h3 when confirming the check of the combination of notification condition candidates.

[0048] In FIG. 12, an example is shown in which both the "predicted rate of eligible recipients" and the "predicted application rate of eligible recipients" are displayed on the notification condition setting screen 13D, but it is also possible to display only one of them.

[0049] (Notification condition generation process according to the embodiment) 13 is a flowchart showing the notification condition generating process according to the embodiment, which illustrates the process of the notification condition generating unit 12 shown in FIG.

[0050] First, in step S11, the notification condition generating unit 12 (FIG. 1) determines whether the personal attribute information 22 (FIG. 6) has been updated. If the personal attribute information 22 has been updated (step S11 YES), the notification condition generating unit 12 proceeds to step S12, and if the personal attribute information 22 has not been updated (step S11 NO), the notification condition generating unit 12 proceeds to step S13.

[0051] In step S12, the notification condition generating unit 12 generates a "condition combining personal attributes" (personal attribute condition 221a) from the personal attribute information 22, and calculates the "number of people concerned 221b=number of people to be notified (A)".

[0052] Fig. 14 is an explanatory diagram of the generation of personal attribute conditions and the calculation of the number of people to be notified (step S12 in Fig. 13) according to an embodiment. The personal attribute information 22 includes name 22a and personal attributes 22b such as "age", "household composition", "tax", and "child allowance". The notification condition generating unit 12 generates personal attribute conditions 221a as groups combining one or more items included in the personal attributes 22b. The personal attribute conditions 221a include groups such as "taxable household and child allowance recipient and household head aged 20-24", "taxable household and child allowance recipient and household head aged 25-29", "taxable household and child allowance recipient and household head aged 30-34", etc.

[0053] The notification condition generating unit 12 then determines the number of people 221b obtained by tallying up the number of individuals who belong to each group in the personal attribute information 22 as the number of people to be notified (A).

[0054] Note that the more columns of personal attribute information 22 and the more values ​​each column can take, the more combination patterns there are, and therefore the more personal attribute conditions 221a there are.

[0055] Returning to the explanation of Fig. 13, on the other hand, in step S13, the notification condition generating unit 12 judges whether new "service receiving condition information 14 (Fig. 7)" (hereinafter referred to as "receiving condition 141") has been registered. If the receiving condition 141 has been registered (step S13 YES), the notification condition generating unit 12 transfers the process to step S14, and if not registered (step S13 NO), the process returns to step S11.

[0056] In step S14, the notification condition generating unit 12 calculates the "prediction value (B) of the total number of people qualified to receive the service" based on the receiving conditions 141, the personal attribute information 22 (FIG. 6) and the demographic information 17 (FIG. 9).

[0057] FIG. 15 is an explanatory diagram of calculation of a predicted value of the total number of service recipients according to the embodiment (step S14 in FIG. 13).

[0058] The notification condition generating unit 12 expands the receiving conditions 141 and generates combinations of all the service receiving conditions. The notification condition generating unit 12 then refers to the demographic information 17 and calculates the conditional probability corresponding to the combination of the service receiving conditions.

[0059] For example, the population ratio of "recipients" and "non-recipients" of "child allowance" can be estimated to be 95:5 by referring to row #4 of Demographic Information 17. Furthermore, the population ratio of "tax non-taxable" is 10%, and "current source of income" is 90% x 5% = 4.5%. Therefore, if the 10% of "tax non-taxable" is apportioned between "recipients" and "non-recipients" of "child allowance", the population ratio (β) of "non-taxable" and "recipients" is 10% x 0.95 = 9.5%, and the population ratio (β) of "non-taxable" and "non-recipients" is 10% x 0.05 = 0.5%. Similarly, if 4.5% of the "current source of income" from "tax" is apportioned between "recipients" and "non-recipients" of "child allowance," the population ratio (β) of "current source of income" and "recipients" is 4.5% x 0.95 = 4.275% ≒ 4.3%, and the population ratio (β) of "current source of income" and "non-recipients" is 4.5% x 0.05 = 0.225% ≒ 0.2%. Therefore, the total population ratio (Σβ) = 9.5% + 0.5% + 4.3% + 0.2% = 15%. If the total population is 3 million, the predicted total number of people eligible to receive services (B) is 3 million x 15% = 450,000.

[0060] Returning to the explanation of Fig. 13, next in step S15, the notification condition generating unit 12 calculates a predicted value (C) of the service eligibility rate for the personal attribute information 22 (Fig. 6) using the demographic information 17 (Fig. 9). Next, in step S16, the notification condition generating unit 12 multiplies (C) by (A) to calculate the number of eligible persons (γ) = (A) × (C), and divides this by (B) to calculate the notification coverage rate (D).

[0061] FIG. 16 is an explanatory diagram of calculation of the notification coverage rate according to the embodiment (steps S15 and S16 in FIG. 13).

[0062] For example, for the personal attribute condition 221a "taxable household and child allowance recipient and household head aged 20-24", the notification condition generating unit 12 obtains a predicted service eligibility rate (C) of 5%×0.90=4.5% from the demographic information 17 under the condition "taxable household and child allowance recipient" that does not take into account the age of the number of household members. Similarly, for "taxable household and child allowance recipient and household head aged 25-29" and "taxable household and child allowance recipient and household head aged 30-34", a predicted service eligibility rate (C) of 4.5% is obtained.

[0063] Then, the notification condition generating unit 12 obtains the number of qualified persons (γ)=100,000×4.5%=4,500 persons for each individual attribute condition 221a from the number of qualified persons (γ)=(A)×(C).

[0064] Finally, the notification condition generating unit 12 obtains the notification coverage rate (D)=4500 people / 450,000 people=1% for each individual attribute condition 221a from (D)=(γ) / (B).

[0065] Returning to the explanation of Fig. 13, next in step S17, the notification condition generating unit 12 judges whether or not a past service having the same service receiving conditions as the newly registered service in the personal attribute information 22 (Fig. 6) exists in the notification / application history information 16 (Fig. 8). If it exists (step S17 YES), the notification condition generating unit 12 proceeds to the process of step S18, and if it does not exist (step S17 NO), the notification condition generating unit 12 proceeds to the process of step S19.

[0066] In step S18, the notification condition generating unit 12 uses the notification and application history information 16 (FIG. 8) to calculate a predicted value (Ω) of the applicant rate in the personal attribute conditions 221a based on the personal attributes of the applicants in past applications similar to the target service. The notification condition generating unit 12 then calculates the application rate (E) of eligible recipients by dividing (Ω) by (C). When step S18 is completed, the notification condition generating unit 12 proceeds to step S20.

[0067] 17 is an explanatory diagram of the calculation of the application rate of qualified persons according to the embodiment (step S18). For each personal attribute condition 221a, the notification condition generation unit 12 calculates a predicted value (Ω) of the applicant rate for the personal attribute condition 221a based on the personal attributes of the applicant recorded in the notification / application history information 16 for past services similar to the target service.

[0068] Here, "similar past services" will be described with reference to Fig. 7. Services #1 and #2 in Fig. 7 have the same service receiving conditions, so the service similarity is 100%.

[0069] On the other hand, the only difference between the conditions for receiving services #1 and #3 is that they are "non-taxable households" and "non-taxable income" among the "conditions for receiving services," and the other conditions are the same. The conditional probability that "non-taxable income" is "non-taxable households" is 90% (see Demographic Information 17 (Figure 9)). Therefore, the similarity between services #1 and #3 is 90%.

[0070] Then, another service having the highest similarity equal to or greater than a predetermined value is selected as the “similar past service.” Therefore, the service similar to the service #1 in the service receiving condition information 14 is the service #2.

[0071] The notification condition generation unit 12 then tallyes up the eligible recipients and applicants for the service in the notification and application history information 16 (Figure 8) in the "service receiving conditions" of service #2 in the service receiving conditions information 14, and calculates the ratio of applicants to eligible recipients. The eligible recipients are the number of all individuals in the notification and application history information 16 who meet the corresponding "service receiving conditions". The applicants are the number of individuals who meet the "service receiving conditions" of the service in question and have an "○" for "Application" in the notification and application history information 16.

[0072] In this way, as shown in FIG. 17, it is assumed that the predicted value (Ω) of the applicant rate for each individual attribute condition 221a is 1%.

[0073] Next, the notification condition generating unit 12 calculates from the application rate (E) of the eligible recipients (E)=(Ω) / (C) that (E)=1% / 4.5%=22.2...%≈22% for each individual attribute condition 221a.

[0074] The purpose of step S18 is to tally up all individuals who meet the “service receiving conditions” for “similar past services” in the notification and application history information 16, and calculate a predicted applicant rate (Ω) and a predicted application rate (E) for eligible recipients.

[0075] Meanwhile, in step S19, the notification condition generation unit 12 counts up individuals who have personal attribute conditions 221a corresponding to the receiving conditions 141 in the notification and application history information 16 (FIG. 8). Then, based on this count, the notification condition generation unit 12 calculates an actual applicant rate, which is the ratio of the number of individuals who actually applied across all histories in the notification and application history information 16. The notification condition generation unit 12 then calculates a predicted application rate (E) of eligible recipients by dividing the actual applicant rate by the predicted service eligibility rate (C).

[0076] In step S19, since there is no "similar past service," the purpose is to tally up all individuals who meet the eligibility conditions 141 (FIG. 5) in the notification and application history information 16, and calculate a predicted applicant rate (Ω) and a predicted application rate (E) of eligible recipients.

[0077] Next, in step S20, the notification condition generating unit 12 extracts, as notification condition candidates, personal attribute conditions 221a (FIG. 14) in which the predicted value (C) of the service qualification rate is equal to or higher than a certain value, or the predicted value (E) of the application rate of the qualified recipients is equal to or lower than a certain value.The notification condition generating unit 12 then associates the information appropriately selected from the above (A) to (E) with the "service" and the "notification condition candidate", and stores them in a specified storage area as notification condition candidate information 15 (FIG. 10).

[0078] In the notification condition generation process described above, a "predicted value of the recipient qualification rate" and a "predicted value of the application rate of the recipient qualifications" are calculated. However, this is not limited to this, and only the "predicted value of the recipient qualification rate" may be calculated, and the calculation of the "predicted value of the application rate of the recipient qualifications" may be omitted. Furthermore, the calculation of the "notification coverage rate" may be omitted.

[0079] (Notification recipient extraction process according to the embodiment) 18 is a flowchart showing the notification target person extraction process according to the embodiment of the present invention, which illustrates the process of the notification target person extraction unit 21 shown in FIG.

[0080] First, in step S21, the notification target extractor 21 narrows down the notification condition candidate information 15 (FIG. 10) when the confirm button 13D3 is pressed on the notification condition setting screen 13D (FIG. 12), and updates the notification condition information 23 (FIG. 11).

[0081] Next, in step S22, notification target extraction unit 21 determines whether the notification conditions of the new service have been registered in notification condition information 23 (FIG. 11). If the notification conditions of the new service have been registered in notification condition information 23 (YES in step S22), notification target extraction unit 21 moves the process to step S23. On the other hand, if the notification conditions of the new service have not been registered in notification condition information 23 (NO in step S22), notification target extraction unit 21 returns the process to step S21.

[0082] In step S23, the notification recipient extraction unit 21 extracts, as notification recipients, individuals who match the notification conditions of the service determined to have been newly registered in step S22 from the personal attribute information 22 (FIG. 6). Next, in step S24, the notification recipient extraction unit 21 notifies the notification recipients extracted in step S23 of the service determined to have been newly registered in step S22. Next, in step S25, the notification recipient extraction unit 21 stores "○" in the "Notification" column of the service and notification recipient in the notification / application history information 16 (FIG. 8) indicating that the notification has been sent in step S24.

[0083] (Application acceptance process according to the embodiment) 19 is a flowchart showing the application reception process according to the embodiment, which illustrates the process of the application reception unit 11 shown in FIG.

[0084] First, in step S31, the application receiving unit 11 receives an application including application documents from the applicant h4. Next, in step S32, the application receiving unit 11 stores "○" in the "Application" column for the service and the applicant in the notification and application history information 16 (FIG. 8) indicating that the application was accepted in step S31.

[0085] (Hardware configuration of computer 1000) Fig. 20 is a diagram showing an example of a hardware configuration of a computer 1000. The computer 1000 realizes a notification condition setting server 1 including an application receiving unit 11, a notification condition generating unit 12, and a notification condition setting screen control unit 13 (Fig. 1) by executing a predetermined program. The computer 1000 also realizes a notification recipient extraction server 2 including a notification recipient extraction unit 21 (Fig. 1) by executing a predetermined program.

[0086] Furthermore, the computer 1000 realizes an operator terminal 3 and a user terminal 4 by executing a predetermined program.

[0087] The computer 1000 includes a processor 1001 including a CPU, a main memory device 1002, an auxiliary memory device 1003, a network interface 1004, an input device 1005, and an output device 1006, all of which are interconnected via an internal communication line 1007 such as a bus.

[0088] The processor 1001 controls the overall operation of the computer 1000. The main memory device 1002 is composed of, for example, a volatile semiconductor memory, and is used as a work memory for the processor 1001. The auxiliary memory device 1003 is composed of a large-capacity nonvolatile memory device such as a hard disk device, an SSD (Solid State Drive), or a flash memory, and is used to store various programs and data for long periods of time.

[0089] An executable program 1003a stored in the auxiliary storage device 1003 is loaded into the main storage device 1002 when the computer 1000 is started up or when necessary, and is executed by the processor 1001 to realize each server that executes various processes.

[0090] The executable program 1003a may be recorded on a non-transitory recording medium, read from the non-transitory recording medium by a medium reading device, and loaded into the main memory device 1002. Alternatively, the executable program 1003a may be obtained from an external computer via a network, and loaded into the main memory device 1002.

[0091] The auxiliary storage device 1003 stores, in addition to the executable program 1003a, service receiving condition information 14, notification condition candidate information 15, notification / application history information 16, and demographic information 17 in the notification condition setting server 1. The auxiliary storage device 1003 also stores personal attribute information 22 and notification condition information 23 in the notification target person extraction server 2.

[0092] The network interface 1004 is an interface device for connecting the computer 1000 to each network in the system or for communicating with other computers. The network interface 1004 is, for example, configured with a NIC (Network Interface Card) for a wired LAN (Local Area Network) or a wireless LAN.

[0093] The input device 1005 is composed of a keyboard, a pointing device such as a mouse, and the like, and is used by the user to input various instructions and information to the computer 1000. The output device 1006 is composed of a display device such as a liquid crystal display or an organic EL (Electro Luminescence) display, and an audio output device such as a speaker, and is used to present necessary information to the user when necessary.

[0094] Although the embodiments of the present disclosure have been described above in detail, the present disclosure is not limited to the above-described embodiments, and various modifications can be made without departing from the spirit of the present disclosure. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present disclosure is not necessarily limited to those having all of the configurations described. In addition, it is possible to add, delete, or replace part of the configuration of the above-described embodiments with other configurations.

[0095] Furthermore, the above-mentioned configurations, functional units, processing units, etc. may be realized in part or in whole by hardware, for example, by designing them as integrated circuits. The above-mentioned configurations, functions, etc. may be realized in software by a processor interpreting and executing a program that realizes each function. Information such as the program, table, file, etc. that realizes each function can be stored in a memory, a storage device such as an HDD or SSD, or a recording medium such as an IC card, an SD card, or a DVD.

[0096] In addition, in each of the above figures, the control lines and information lines are shown as those considered necessary for the explanation, and do not necessarily show all the control lines and information lines in the actual implementation. For example, it may be considered that almost all the components are actually connected to each other.

[0097] The above-mentioned notification condition setting server 1 and notification recipient extraction server 2 are merely examples of the arrangement of the functions and data. The arrangement of the functions and data can be changed to an optimal arrangement in terms of the performance of hardware and software, processing efficiency, communication efficiency, etc. [Explanation of symbols]

[0098] S: service notification setting system, 1: notification condition setting server, 2: notification recipient extraction server, 3: operator terminal, 4: user terminal, 11: application acceptance unit, 12: notification condition generation unit, 13: notification condition setting screen control unit, 13D: notification condition setting screen, 21: notification recipient extraction unit, 22: personal attribute information, 23: notification condition information, 1000: computer, 1001: processor.

Claims

1. A service notification setting method executed by a service notification setting system that transmits a notification of the provision of a service to a target person, comprising: The service notification setting system includes a processor, a memory, and a storage unit, The storage unit is personal attribute information for managing attributes of each individual; service receiving condition information for managing, for each of the services, the receiving conditions of the service of the individual to whom the service is provided; demographic information for managing information on the population ratio of the individuals corresponding to each attribute group to the total population, for each attribute group including one or more of the attributes; application history information for managing an application history indicating whether or not each of the individuals applied for a past service provided in the past; The processor, generating a personal attribute condition including one or more of the attributes; Applying the personal attribute conditions to the attribute groups in the demographic information, a predicted value of the recipient eligibility rate, which is the ratio of recipients of the service for each personal attribute condition to the total population, is calculated.

23. A service notification setting method comprising the steps of:

2. 2. The service notification setting method according to claim 1, The processor, Identifying, based on the personal attribute information, the individuals who meet the receiving conditions of the past service whose receiving conditions match or are similar to those of the service in the application history information, and calculating, based on the application history of the identified individuals, a predicted value of the applicant rate, which is the proportion of the number of individuals who will apply for the service for each of the personal attribute conditions; A predicted application rate indicating the likelihood that the eligible recipients will apply for the service is calculated by dividing the predicted application rate by the predicted eligible recipient rate. A service notification setting method comprising each process.

3. 3. The service notification setting method according to claim 2, further comprising the steps of: The processor, If the application history information does not contain data on the past service whose receiving conditions are identical or similar to those of the service, the individuals who meet the receiving conditions in the application history information are identified based on the personal attribute information, and a predicted value of the applicant rate is calculated for each of the personal attribute conditions based on the application history of the identified individuals.

23. A service notification setting method comprising the steps of:

4. 3. The service notification setting method according to claim 2, further comprising the steps of: The processor, tallying up the number of individuals who meet each of the personal attribute conditions in the personal attribute information as the number of people to be notified; applying the receiving conditions in the service receiving condition information to the attribute group in the demographic information, and multiplying the population ratio that corresponds to the receiving condition of the service by the total population to calculate a predicted value of the total number of the eligible recipients; multiplying the predicted value of the eligible recipient rate for each of the personal attribute conditions by the notified number of people to calculate a predicted value of the number of eligible recipients for each of the personal attribute conditions; A notification coverage rate indicating the proportion of people to whom the notification is sent for each personal attribute condition is calculated by dividing the predicted number of the eligible recipients for each personal attribute condition by the predicted number of the eligible recipients. A service notification setting method comprising each process.

5. 5. The service notification setting method according to claim 4, further comprising the steps of: The processor, The receiving condition is set as a notification condition candidate indicating the attribute of the individual who is a candidate for the notification, Generate notification condition candidate information in which the notification condition candidates, one or both of the predicted value of the beneficiary eligibility rate and the predicted value of the application rate, and the notification coverage rate are associated with each other. A service notification setting method comprising each process.

6. 6. A service notification setting method according to claim 5, further comprising the steps of: The processor, Displaying on a screen either or both of the predicted value of the eligible recipient rate and the predicted value of the application rate for each of the notification condition candidates; When the notification condition candidate is selected by a notification condition setter, a total value of the notification coverage rate across the selected notification condition candidate is calculated; Displaying the calculated notification coverage rate on the screen; The notification condition candidates selected by the notification condition setter are managed as notification conditions, which are attributes of the target person to whom the notification is to be sent, for each service to generate notification condition information. A service notification setting method comprising each process.

7. 7. A service notification setting method according to claim 6, further comprising the steps of: The notification condition candidates include a confirmed receiving condition that confirms the individual who meets the notification condition candidate as a recipient of the service, and a non-confirmed receiving condition that indicates the possibility of the individual becoming a recipient of the service. A service notification setting method comprising:

8. 7. A service notification setting method according to claim 6, further comprising the steps of: The processor, extracting the target person from the personal attribute information based on the notification condition associated with the service included in the notification condition information; Execute a process of sending the notification to the extracted target person. A service notification setting method comprising each process.

9. A service notification setting system that transmits a notification of the provision of a service to a target person, A processor, a memory, and a storage unit are included. The storage unit is personal attribute information for managing attributes of each individual; service receiving condition information for managing, for each of the services, the receiving conditions of the service of the individual to whom the service is provided; demographic information for managing information on the population ratio of the individuals corresponding to each attribute group to the total population, for each attribute group including one or more of the attributes; application history information for managing an application history indicating whether or not each of the individuals applied for a past service provided in the past; The processor, generating a personal attribute condition including one or more of the attributes; Applying the personal attribute conditions to the attribute groups in the demographic information, a predicted value of the recipient eligibility rate, which is the ratio of recipients of the service for each personal attribute condition to the total population, is calculated. A service notification setting system comprising:

10. 10. The service notification setting method according to claim 9, further comprising the steps of: Identifying, based on the personal attribute information, the individuals who meet the receiving conditions of the past service whose receiving conditions match or are similar to those of the service in the application history information, and calculating, based on the application history of the identified individuals, a predicted value of the applicant rate, which is the proportion of the number of individuals who will apply for the service for each of the personal attribute conditions; A predicted application rate indicating the likelihood that the eligible recipients will apply for the service is calculated by dividing the predicted application rate by the predicted eligible recipient rate. A service notification setting system comprising:

11. The service notification setting system according to claim 10, The processor, If the application history information does not contain data on the past service whose receiving conditions are identical or similar to those of the service, the individuals who meet the receiving conditions in the application history information are identified based on the personal attribute information, and a predicted value of the applicant rate is calculated for each of the personal attribute conditions based on the application history of the identified individuals. A service notification setting system comprising:

12. The service notification setting system according to claim 10, The processor, tallying up the number of individuals who meet each of the personal attribute conditions in the personal attribute information as the number of people to be notified; applying the receiving conditions in the service receiving condition information to the attribute group in the demographic information, and multiplying the population ratio that corresponds to the receiving condition of the service by the total population to calculate a predicted value of the total number of the eligible recipients; multiplying the predicted value of the eligible recipient rate for each of the personal attribute conditions by the notified number of people to calculate a predicted value of the number of eligible recipients for each of the personal attribute conditions; A notification coverage rate indicating the proportion of people to whom the notification is sent for each personal attribute condition is calculated by dividing the predicted number of the eligible recipients for each personal attribute condition by the predicted number of the eligible recipients. A service notification setting system comprising:

13. The service notification setting system according to claim 12, The processor, The receiving condition is set as a notification condition candidate indicating the attribute of the individual who is a candidate for the notification, Generate notification condition candidate information in which the notification condition candidates, one or both of the predicted value of the beneficiary eligibility rate and the predicted value of the application rate, and the notification coverage rate are associated with each other. A service notification setting system comprising:

14. The service notification setting system according to claim 13, The processor, Displaying on a screen either or both of the predicted value of the eligible recipient rate and the predicted value of the application rate for each of the notification condition candidates; When the notification condition candidate is selected by a notification condition setter, a total value of the notification coverage rate across the selected notification condition candidate is calculated; Displaying the calculated notification coverage rate on the screen; The notification condition candidates selected by the notification condition setter are managed as notification conditions, which are attributes of the target person to whom the notification is to be sent, for each service to generate notification condition information. A service notification setting system comprising:

15. The service notification setting system according to claim 14, The notification condition candidates include a confirmed receiving condition that confirms the individual who meets the notification condition candidate as a recipient of the service, and a non-confirmed receiving condition that indicates the possibility of the individual becoming a recipient of the service. A service notification setting system comprising:

16. The service notification setting system according to claim 14, The processor, extracting the target person from the personal attribute information based on the notification condition associated with the service included in the notification condition information; Execute a process of sending the notification to the extracted target person. A service notification setting system comprising:

Images