JP7513221B2 - Notification server, notification management system, notification management method, and program - Google Patents

Description

The present invention relates to a notification server, a notification management system, a notification management method, and a program.

Local governments notify residents of various notifications by mail. When sending notifications by mail, local government officials print them out, seal them, and then send them out. This places a heavy burden on local government officials. For this reason, local governments have expressed a desire to switch from mailing to sending electronic data.
On the other hand, when providing information to residents, a system has been proposed in which information is sent by email (for example, see Patent Document 1).

JP 2005-284591 A

However, while some residents may find it convenient to receive notifications electronically via e-mail, others may not. In other words, some residents may not have a terminal device capable of receiving e-mail, or may be unfamiliar with the operation of receiving and displaying e-mail on a terminal device.
For this reason, it is difficult to uniformly switch from sending notifications by paper mail to sending them electronically, as some residents find it difficult to receive notifications electronically. On the other hand, if notifications remain sent by mail, the burden on local governments will not be reduced, and residents who want to receive notifications electronically will not be able to enjoy the benefits.
In addition, when notifications are sent by mail, they can be sent by using the addresses of residents already registered with the local government, but when they are sent electronically, the local government does not know the addressee, so they must be sent to the correct address. In this case, it is desirable to be able to prevent them from being sent to the wrong address.

The present invention was made in consideration of the above circumstances, and its purpose is to provide a notification server, notification management system, notification management method, and program that can send notifications to recipients who wish to receive them electronically while preventing erroneous delivery and reducing the amount of work required.

In order to solve the above-mentioned problems, one aspect of the present invention is a notification server having a destination list data acquisition unit that acquires destination list data including information on recipients to whom notifications are to be sent, the destinations being extracted in response to an operation by a person in charge of the institution to which the notifications are sent, the destinations including basic information of users belonging to the institution, and a determination unit that compares the acquired destination list data with registered user list data including basic information obtained by identity verification of a user who has registered in response to a user registration operation by the user who wishes to receive electronic distribution, and determines whether or not to transmit the notification to the recipients included in the destination list data as an electronic notification based on a comparison result determined based on whether the basic information of the user included in the destination list data corresponds to the basic information included in the registered user list data.

Another aspect of the present invention is a notification management system including a notification server and a user management server, the user management server having an acquisition unit that acquires personal information stored on a personal card owned by the user and a My Number card signature password input by the user, a user information inquiry unit that makes an inquiry for identity verification by sending the personal information and the My Number card signature password to a public personal authentication authority server, and a user registration unit that writes the personal information to the registered user list data if the result of the inquiry indicates that identity verification has been successful.

Another aspect of the present invention is a notification management method executed by a computer, which acquires destination list data including information on recipients of notifications, the destinations being extracted in response to an operation by a person in charge of an institution to which the notification is sent, the destinations including basic information of users belonging to the institution, and a determination unit compares the acquired destination list data with registered user list data including basic information obtained by identity verification of a user who has registered in response to a user registration operation by the user who wishes to receive electronic distribution, and determines whether or not to send the notification to the recipients included in the destination list data as an electronic notification based on a comparison result determined based on whether the basic information of the user included in the destination list data corresponds to the basic information included in the registered user list data.

Another aspect of the present invention is a program that causes a computer to execute the following steps: acquire destination list data including information on recipients to whom notifications are to be sent, the destinations being extracted in response to an operation by a person in charge at an institution to which the notifications are to be sent, the destinations including basic information on users belonging to the institution; compare the acquired destination list data with registered user list data including basic information obtained by identity verification of a user who has registered in response to a user registration operation by the user who wishes to receive electronic distribution; and determine whether or not to send the notification to the recipients included in the destination list data as an electronic notification based on a comparison result determined based on whether or not the basic information of the user included in the destination list data corresponds to the basic information included in the registered user list data.

As described above, this invention makes it possible to send notifications to recipients who wish to receive them electronically while reducing the amount of work required and preventing misdelivery.

1 is a schematic block diagram showing a configuration of a notification management system 1 according to an embodiment of the present invention. 2 is a schematic functional block diagram illustrating the functions of the usage registration system 30. FIG. 2 is a schematic functional block diagram illustrating the functions of a user management server 50. FIG. 5 is a diagram showing an example of user information stored in a user information storage unit 5301. FIG. 5 is a diagram showing an example of staff information stored in a staff information storage unit 5302. FIG. 2 is a schematic functional block diagram illustrating the functions of a notification server 60. FIG. A figure showing an example of notification information stored in electronic notification storage unit 6301. 2 is a flow chart for explaining the overall operation of the notification management system 1. FIG. 11 is a sequence diagram illustrating the flow of a usage registration process. FIG. 11 is a sequence diagram illustrating a notification transmission process. FIG. 11 is a sequence diagram illustrating a notification transmission process. FIG. 11 is a sequence diagram illustrating a notification transmission process. FIG. 11 is a sequence diagram illustrating a browsing process. FIG. 11 is a sequence diagram illustrating a browsing process.

Hereinafter, a notification management system according to an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a schematic block diagram showing the configuration of a notification management system 1 using a user management server and a notification server according to an embodiment of the present invention.
The notification management system 1 includes a user terminal 10, an IC (Integrated Circuit card) card 15, a data center server 20, a usage registration system 30, a management terminal 40a, a management terminal 40b, a notification creation terminal 45, a user management server 50, a notification server 60, a notification distribution server 70, and a viewing web server 80.

The user terminal 10 is a terminal device used by residents (users) belonging to a local government, which is an administrative agency. Here, residents belonging to a local government are residents who belong to an area governed by the local government, for example, residents who live in an area governed by the local government. Although one user terminal 10 is shown in this figure, two or more terminals may be used. When there are multiple user terminals 10, each is used by a different resident.
The user terminal 10 may be any one of a tablet, a smartphone, a mobile phone, a computer, etc. The user terminal 10a is communicatively connected to the usage registration system 30 and the browsing Web server 80 via a network such as the Internet.

The IC card 15 is issued to and owned by each resident. The IC card 15 is a personal card in which information specific to the resident is stored. For example, the IC card 15 may be issued by a local government, and for example, a My Number card may be used. The IC card 15 can be communicatively connected to the card reader 35 of the user registration system 30 in a contact or contactless manner.
The IC card 15 stores basic information about the resident and a My Number card signature password. The basic information is information about the resident, such as name, address, date of birth, and gender. The password is used for authentication when using the basic information stored in the IC card 15.

The data center server 20 is communicatively connected to the user management server 50, the notification server 60, and the notification distribution server 70. When the data center server 20 is connected to the user management server 50, the notification server 60, and the notification distribution server 70, the data center server 20 is connected via a local government wide area network (LGWAN). The LGWAN is a network exclusively for government agencies, and is a closed network separated from the Internet.
The data center server 20 functions as a resident information storage server that stores resident information, which is information about residents belonging to at least one local government. The resident information includes basic information. As described above, the basic information is information about an individual resident, and includes name, address, date of birth, and gender.
The resident information stored in the data center server 20 may be stored for one local government, or may be stored for each of a plurality of local governments. This resident information can be referenced via the notification distribution server 70 by the management terminal 40a, management terminal 40b, and notification creation terminal 45 that belong to the relevant local government. Note that the management terminal 40a, management terminal 40b, and notification creation terminal 45 are not allowed to reference resident information of any other local government than the one to which they belong.

The user registration system 30 is installed in a local government office and is communicatively connected to the user terminal 10 and the user management server 50 .
The user registration system 30 allows residents to register in order to electronically receive notifications from local governments.
The user registration system 30 has a card reader 35. When registering, the card reader 35 reads basic information from the IC card 15. When a resident registers, the resident brings the IC card 15 in which the resident's basic information is stored to the government office and registers by having the card reader 35 read the IC card 15. Here, if the user terminal 10 is equipped with the function of the card reader 35 or is connected to a card reader having the same function as the card reader 35, the resident can also register using the user terminal 10 that the resident owns without going to the government office. In other words, even if the resident does not have a card reader, the resident can register by going to the government office.
After completing the user registration, the resident can use his/her own user terminal 10 to receive and view notifications in electronic data format.

The card reader 35 communicates with the IC card 15 and reads data from the IC card 15. The card reader 35 may also have a function for writing data to the IC card 15. The card reader 35 can communicate with the IC card 15 in a contact or non-contact manner.

The management terminal 40a, the management terminal 40b, and the notification creation terminal 45 are terminal devices used by employees of local governments. The management terminal 40a, the management terminal 40b, and the notification creation terminal 45 are communicably connected to a notification distribution server 70.
The management terminal 40a has various functions for transmitting notifications from the local government to residents who have registered to use the terminal. The management terminal 40a is used by local government employees who are responsible for sending notifications. Notifications contain written information about the notification. Notifications come in two forms: printed notifications, in which the notification information is printed on a print medium, and electronic notifications, which are electronic data that include the notification information.
The management terminal 40b is a terminal device used by a manager (e.g., a superior) who manages the transmission personnel who use the management terminal 40a among the employees of the local government. When the management terminal 40b receives an approval request for electronically transmitting a notification from the management terminal 40a, it is possible for the management terminal 40b to input approval instructions in response to the operational instructions input by the manager.
The notification creation terminal 45 is a terminal device used by a person in charge of creating the notification, and is a terminal device that creates electronic data of the notification. The notification creation terminal 45 will be described as a terminal device separate from the management terminal 40a, but a single terminal device may be provided with both the functions of the management terminal 40a and the notification creation terminal 45.
Computers are used as the management terminal 40a, the management terminal 40b, and the notice creation terminal 45. Furthermore, a plurality of each of the management terminal 40a, the management terminal 40b, and the notice creation terminal 45 may be used.

The user management server 50 is communicatively connected to the usage registration system 30, the data center server 20, the notification server 60, and the browsing Web server 80.
The user management server 50 stores information about residents and staff who use the notification management system 1. For example, it stores information about residents who have registered using the user registration system 30, and information about staff who use the management terminals 40a and 40b.

The notification server 60 is communicatively connected to the data center server 20, the user management server 50, and the viewing web server 80. The notification server 60 stores electronic data of the notification (e.g., PDF data) and transmits the PDF data to the viewing web server 80 in response to a viewing request from the viewing web server 80.

The notification distribution server 70 generates data showing the correspondence between information about residents to whom notifications are to be sent and electronic data of the notifications to be sent, and generates electronic data of the notifications. The notification distribution server 70 is communicatively connected to the management terminal 40a, the management terminal 40b, the notification creation terminal 45, and the data center server 20.

When the viewing web server 80 receives a request from the user terminal 10 to view the electronic data of the notification, the user management server 50 performs a login authentication process, and if the login is permitted, the viewing web server 80 makes the electronic data of the notification available for viewing on the user terminal 10.

Next, the above-mentioned user registration system 30, user management server 50, notification server 60, notification distribution server 70, and viewing Web server 80 will be further described.
FIG. 2 is a schematic functional block diagram illustrating the functions of the user registration system 30. As shown in FIG.
The user registration system 30 is connected to a user registration server 31 and a card reader 35 .
The registration server 31 includes a communication unit 311 and a control unit 312 .
The communication unit 311 communicates with the card reader 35 and the user terminal 10 .
The control unit 312 controls each unit of the user registration server 31. The control unit 312 includes an acquired information processing unit 3121, a personal card reading processing unit 3122, and an authentication processing unit 3123.
The acquired information processing unit 3121 processes various information acquired from external devices such as the card reader 35 and the user terminal 10 .
The personal card reading processing unit 3122 reads out information stored in the personal card from the personal card. For example, the personal card reading processing unit 3122 performs processing for acquiring information from the card reader 35 or a card reader provided in the user terminal 10.
The authentication processing unit 3123 performs various authentication processes. The authentication process here is a process in which, when a resident causes the card reader 35 to read the IC card 15, in order to determine whether the IC card 15 is correct, a query is made by sending predetermined information (e.g., basic information) stored in the IC card 15 and a password for public personal authentication (signature) to a public personal authentication institution server, and a judgment is made based on the query result obtained from the public personal authentication institution server. Here, the public personal authentication institution server is a server operated by an institution that issues personal cards used as the IC card 15 and manages information stored in the IC card 15. The public personal authentication institution server is, for example, a server operated by J-LIS (Japan Agency for Local Authority Information Systems). If the query result obtained from the public personal authentication institution server indicates that the identity of the resident has been confirmed, it indicates that the IC card 15 has been issued correctly and that it has been confirmed that the resident who is going to use the IC card 15 is the owner of the IC card 15. When the IC card 15 is a My Number, the public personal authentication (signature) password is the My Number card signature password. When using the IC card 15, the user is asked to input this My Number card signature password, which is then verified by the public personal authentication organization server, thereby making it possible to confirm whether the user of the IC card 15 is the actual owner of the IC card 15.

FIG. 3 is a schematic functional block diagram illustrating the functions of the user management server 50. As shown in FIG.
The user management server 50 has a communication unit 510, a control unit 520, and a memory unit 530.
The communication unit 510 communicates with the data center server 20 , the usage registration system 30 , the notification server 60 , and the viewing Web server 80 .
The control unit 520 includes an acquisition unit 5201 , a user information inquiry unit 5202 , a user registration unit 5203 , a terms of use management unit 5204 , a local government group management unit 5205 , a status management unit 5206 , an authentication processing unit 5207 , and an encryption management unit 5208 .

The acquisition unit 5201 acquires personal information stored on a personal card owned by a resident and a My Number card signature password input by the user.
The user information inquiry unit 5202 inquires of the public personal authentication organization server as to whether or not the personal information and the My Number card signature password acquired by the acquisition unit 5201 are stored in the public personal authentication organization server.
If the result of the inquiry obtained from the public personal authentication authority server indicates that the user's identity has been verified, the user registration unit 5203 writes the personal information into the user registration list data.
The terms of use management unit 5204 refers to the terms of use agreement information stored in the user information storage unit 5301 to determine whether or not the resident who has made the viewing request has agreed to the terms of use.
The local government group management unit 5205 identifies the relationship between local governments and residents. For example, data on residents of multiple local governments can be stored in the user information storage unit 5301. Therefore, when the local government group management unit 5205 reads information on residents from the user information storage unit 5301, the local government group management unit 5205 identifies the local government to be read and then reads the information.
When an electronic notification is viewed by a resident's terminal device, the status management unit 5206 updates the viewing status corresponding to the resident's user identification information and the electronic notification identification information of the viewed electronic notification for the viewing information stored in the notification server 60 (viewing information storage unit 6303) to a status indicating that the electronic notification has been viewed.
The authentication processing unit 5207 performs authentication for the user terminal 10, the management terminal 40a, the management terminal 40b, and the like.
The encryption management unit 5208 encrypts and stores information to be stored in the user management server 50, and performs decryption processing.

The storage unit 530 stores various types of information. The storage unit 530 includes a user information storage unit 5301 and an employee information storage unit 5302.
The user information storage unit 5301 stores user information of a user who desires electronic distribution in response to a user registration operation by the user.

4 is a diagram showing an example of user information stored in the user information storage unit 5301. The user information includes basic information, an email address, a phone number, a login ID, a password, a user ID, and terms of use agreement information.
This basic information is information that corresponds to the basic information stored in the data center server 20 (the same information as the basic information). The email address represents an email address that can be received by the user terminal 10 used by the user. The telephone number is a telephone number assigned to a device owned by the user (smartphone, tablet, mobile phone, telephone, etc.). The login ID is identification information for logging in to a service site that receives notifications electronically, and is assigned to each resident (user). The password is a password for logging in to the service site. The user ID is identification information for identifying a user on the service site, and is assigned to each user.
The terms of use agreement information includes information indicating whether or not the resident has agreed to the terms of use. If the resident has agreed, the date of agreement is stored. If the resident has not agreed, this date is not stored.

The employee information storage unit 5302 stores information about local government employees who use the user management server 50 and the notification server 60.
FIG. 5 is a diagram showing an example of staff information stored in the staff information storage unit 5302. As shown in FIG.
Staff information includes name, department, email address, and role. Name is the name of the staff member. Department indicates the department to which the staff member belongs in the local government. Email address indicates the email address assigned to the staff member by the local government when performing work in the local government. Role indicates the position or role in the local government. For example, roles include "person in charge" and "manager."

FIG. 6 is a schematic functional block diagram illustrating the function of the notification server 60. As shown in FIG.
The notification server 60 includes a communication unit 610, a control unit 620, and a storage unit 630. The communication unit 610 communicates with the data center server 20, the user management server 50, and the browsing Web server 80.
The control unit 620 has a delivery destination list data acquisition unit 6201 , a user registration list data acquisition unit 6202 , a determination unit 6203 , a viewing management unit 6204 , and a consent management unit 6205 .

The destination list data acquisition unit 6201 acquires destination list data including information on the target persons to whom the notification is to be sent. For example, the destination list data acquisition unit 6201 acquires the destination list data by receiving the destination list data uploaded from a terminal device (e.g., the management terminal 40a or the management terminal 40b) used by an employee of the local government based on the operation of the terminal device.
In the destination list data acquired by the destination list data acquisition unit 6201, information about each resident is associated with notification identification information for identifying the electronic notification to be sent.

The user registration list data acquisition unit 6202 acquires user registration list data from the user information storage unit 5301, which stores user registration list data including the destination of the user registered in response to the user registration operation by the user who wishes to receive electronic distribution.

The determination unit 6203 compares the acquired destination list data with the user registration list data, and determines whether or not to send an electronic notification to a resident included in the destination list data based on the comparison result (matching process). The data used by the determination unit 6203 when making this determination is the user registration list data registered when the public personal authentication institution server has confirmed the identity of the resident based on the personal information stored in the personal card owned by the resident and the My Number card signature password entered by the user.
In addition, the judgment unit 6203 compares the notification identification information included in the destination list data with the notification identification information stored in the electronic notification memory unit 6301, and based on the comparison result, if an electronic notification corresponding to the notification identification information set as the destination list data is stored in the electronic notification memory unit 6301, it judges that it is possible to send an electronic notification corresponding to the notification identification information.

The viewing management unit 6204 gives viewing permission to the corresponding resident's terminal device for the electronic notification determined by the determination unit 6203 as transmittable, based on the destination included in the destination list data.
When the viewing management unit 6204 receives a request to view an electronic notification from a user terminal 10, it refers to the user information storage unit 5301 to determine whether or not a consent instruction has been given by the user of the user terminal 10 that made the viewing request, and allows viewing of the electronic notification if it is determined that the resident has agreed to the terms of use.
If the viewing management unit 6204 determines that the terms of use have not been agreed to, it inquires of the user terminal 10 that made the viewing request as to whether or not the user agrees to the terms of use, and if a response indicating agreement is received from the user terminal 10, it permits viewing of the electronic notification.

When the consent management unit 6205 receives a request to view an electronic notification from a resident's user terminal, it determines whether the requesting resident has agreed to the terms of use for the service of viewing the electronic notification by sending a request to the user management server 50, based on the terms and conditions consent information stored in the user information storage unit 5301.
When a response indicating consent is received from the terminal device in response to an inquiry as to whether the user agrees to the terms of use, the consent management unit 6205 writes the result of consent as terms of use consent information in the user information storage unit 5301.

The storage unit 630 stores various data. The storage unit 630 includes an electronic notification storage unit 6301, a delivery destination list data storage unit 6302, and a viewing information storage unit 6303.
The electronic notification storage unit 6301 stores the electronic notification to be transmitted and notification identification information for identifying the electronic notification.
7 is a diagram showing an example of notification information stored in the electronic notification storage unit 6301. The electronic notification storage unit 6301 stores a notification ID, notification PDF data, an operation log, and a notification record.
The notification ID is information for individually identifying an electronic notification.
The notification PDF data is electronic data of the electronic notification, and the data format is PDF.

The operation log is log data that indicates the contents of operations performed on an electronic notification. For example, the operation log includes a history of changes to the name of an electronic notification, and an approval result indicating whether or not an approval request for an electronic notification has been made.
The notification record indicates the relationship of which electronic notification each individual electronic notification was generated from when an electronic notification was edited based on one electronic notification to have contents corresponding to a resident. For example, if there is an electronic notification "Notification regarding XX benefits," and this electronic notification is used as a base to edit the contents to be individual for 10 residents, resulting in 10 types of electronic notifications, information that allows the relationship between the original electronic notification and each electronic notification obtained by editing is stored.

The destination list data storage unit 6302 stores destination list data. The destination list data is data in which basic information of residents to whom the notification is to be sent is associated with the file name of the electronic notification to be sent to each resident.
The viewing information storage unit 6303 stores user identification information, electronic notification identification information, and a viewing status indicating whether the electronic notification has been viewed.

Next, the operation of the notification management system 1 will be described.
The operations of the notification management system 1 are roughly divided into a usage registration process, a notification transmission process, and a viewing process. Each process will be described below in order.

<User registration process>
The user registration process is a process for residents to register to receive notifications from local governments electronically (receive electronic data) instead of in paper form such as by mail. Residents who wish to receive notifications electronically (receive notifications as electronic notifications instead of printed notifications) can receive the electronic data of notifications and view them on the user terminal 10 by registering to use the service.
FIG. 8 is a flow chart for explaining the overall operation of the notification management system 1. As shown in FIG.
FIG. 9 is a sequence diagram illustrating the flow of the usage registration process.

When a resident wishes to receive notifications from a local government electronically instead of by mail, the resident must first register. When registering, the resident can go to the government office and register using the registration system (step S1 in FIG. 8), or if the resident's own user terminal 10 is equipped with a card reader, the resident can register using the user terminal 10. In this embodiment, the case of registering using the user terminal 10 will be described.
When registering for use, application software for electronically receiving notifications (hereinafter referred to as a registration application) is downloaded and executed by inputting an operation to the user terminal 10. This starts the registration procedure (step S101 in FIG. 9). The application software downloaded here is equivalent to the function of the registration server 31 for performing the procedure for registering a user. Therefore, it may be executed as application software, or it may be possible to perform registration by communicating with the registration server 31 and executing the function of the registration server 31 without using the application software.

When the registration procedure is started, the user terminal 10 displays the terms of use for receiving notifications electronically and the terms of use for handling personal information related to the use of user information on the display screen of the user terminal 10. The user refers to these terms, and if they agree, touches the "Agree" button displayed on the screen on the touch panel of the user terminal 10 (FIG. 9, step S102).

When the user terminal 10 receives an operation input indicating consent to the terms of use, the user terminal 10 acquires the consent instruction indicating consent and displays an input screen for inputting an email address and a phone number on the display screen. In response, the user inputs an email address and a phone number from the touch panel (step S103 in FIG. 9). When the email address and phone number are input, the user terminal 10 passes the input data and the consent instruction to the usage registration application.
When the user registration application acquires the email address, telephone number, and consent instruction, it transmits these data and a request for transmitting a security code to the user management server 50 (FIG. 9, step S180).

The communication unit 510 of the user management server 50 receives the email address, telephone number, and consent instruction. The acquisition unit 5201 acquires the email address, telephone number, and consent instruction received by the communication unit 510. The user registration unit 5203 writes the email address, telephone number, and consent instruction acquired by the acquisition unit 5201 into the user information storage unit 5301. The user registration unit 5203 also issues a user ID, and stores the issued user ID in the user information storage unit 5301 in association with the email address, telephone number, and consent instruction.
Furthermore, the user registration unit 5203 issues a security code and transmits the issued security code by e-mail addressed to the received e-mail address (step S2 in FIG. 8, step S201 in FIG. 9).

The user terminal 10 receives the email sent from the user management server 50. The user displays the text of the received email on the display screen of the user terminal 10 and checks the security code written in the text. The user enters this security code into the security code input field of the user registration app and touches the execute button. If the entered security code matches the security code received from the user management server 50 in the user registration app, the mode transitions to a personal card reading mode. Note that if the email sent from the user management server 50 contains a uniform resource locator (URL) for user registration, the user may touch the URL written in the email (step S3 in FIG. 8) to perform authentication and transition to reading the personal card.

When the mode is changed to the personal card reading mode, the user terminal 10 displays a message such as "Please read the personal card with the card reader" on the display screen. This prompts the user to bring his/her personal card (IC card 15) close to the card reader 35 and have it read.
When the IC card 15 is brought close to within the readable range of the card reader 35, the user terminal 10 reads the basic information stored in the IC card 15 through the card reader 35. Here, if the IC card 15 is a specific card type, it may be necessary to input a password set in the IC card 15 in order to read the data stored in the IC card 15 (for example, a My Number card, etc.). In this case, the user terminal 10 displays a message such as "Please enter your password" on the display screen. Here, the password is set, for example, at the stage when the IC card 15 is issued, and the user also knows it at the time of card issuance. Upon receiving this, the user operates the touch panel of the user terminal 10 to input the My Number card signature password. This input My Number card signature password is sent to the IC card 15 through the card reader 35, and it is determined in the IC card 15 whether the password matches, and if they match, the IC card 15 outputs the basic information. The user terminal 10 acquires the basic information through the card reader 35 (step S105).
The usage registration application requests registration by acquiring the basic information and the My Number card signature password and transmitting them to the user management server 50. Here, the usage registration application encrypts the basic information and the My Number card signature password according to a predetermined encryption method and transmits them to the user management server 50 (FIG. 9, step S182).

The user information inquiry unit 5202 of the user management server 50 transmits an inquiry request to the public personal authentication organization server together with the basic information and the My Number card signature password (step S202). This inquiry request is to check whether or not the combination of the basic information and the My Number card signature password obtained from the IC card 15 is registered in the public personal authentication organization server.
When the public personal authentication institution server receives the basic information, the password, and the inquiry request, it decrypts the basic information and the password based on a predetermined encryption method, refers to the resident data stored in the storage device of the public personal authentication institution server, and executes the identity verification process by determining whether the combination of the decrypted basic information and the password is stored in the storage device (step S401 in FIG. 9). If the combination of the requested basic information and the password is stored in the storage device, the public personal authentication institution server notifies the user management server 50 that it is registered.

When the user registration unit 5203 of the user management server 50 receives a notification from the public personal authentication institution server indicating that the user has been registered, it writes the basic information to the user information storage unit 5301 and notifies the user terminal 10 via the communication unit 510 of the reading confirmation result indicating that the user has been registered (step S203 in Figure 9).
When the user terminal 10 receives the read confirmation result indicating that the user has been registered (step S106 in FIG. 9), it displays an input field for the login ID and password on the screen along with a message saying "Please enter the login ID and password to be registered." This login ID and password are information used to log in to the service site provided by the user management server 50 and the notification server 60. The login ID and password can be determined arbitrarily by the user, but the user management server 50 may issue the login ID and password and notify the user terminal 10. The password used in this login is a different password from the password for identity verification (My Number Card signature password) used when using the above-mentioned IC card 15.

When a login ID and password are input by the user (step S107 in FIG. 9), the user terminal 10 accepts the input login ID and password. The usage registration app acquires the input login ID and password and transmits them to the user management server 50 (step S4 in FIG. 8, step S183 in FIG. 9). When the user management server 50 receives the login ID and password, it encrypts the user information (step S204 in FIG. 9) and stores them in association with the user ID in the user information storage unit 5301 (step S205 in FIG. 9).

By carrying out this registration process, residents can register to receive notifications from local governments electronically, rather than by mail. In addition, the information stored in IC card 15 is compared with the information registered in the public personal authentication agency server, so it is possible to register residents who have IC card 15 after confirming whether they are residents registered in the public personal authentication agency server. In addition, when registering, residents must enter their My Number card signature password when reading basic information from IC card 15, so residents who use IC card 15 can be registered after identity authentication. This makes it possible to prevent registrations that send notifications to addresses other than the intended address (resident) to residents other than the one who wants to receive notifications electronically.

<Notification sending process>
Next, the notification transmission process will be explained. The notification transmission process is a process in which a local government employee sends a notification by electronic data to a resident who has registered for use. For residents who have not registered for use, notifications are mailed by a procedure different from this notification transmission process.
10, 11 and 12 are sequence diagrams illustrating the notification transmission process.

A local government employee accesses the notification server 60 by operating the management terminal 40a to display the login screen. The employee who will be using the management terminal 40a has been registered in advance (step S5 in FIG. 8). The employee operates an input device such as a keyboard or mouse to input the login ID and password assigned to him or her.
When the login ID and password are input (step S111 in FIG. 10), the management terminal 40a transmits the input login ID and password to the notification server 60.
When the notification server 60 receives the login ID and password from the management terminal 40a, it transmits the login ID and password together with a login authentication request to the user management server 50 (step S311 in FIG. 10).

When the user management server 50 receives a login authentication request, login ID, and password from the notification server 60, it performs login authentication by determining whether the received login ID and password combination matches the login ID and password combination stored in the user information storage unit 1031 (FIG. 10, step S211). If the received login ID and password combination matches the login ID and password combination stored in the user information storage unit 5301, the user management server 50 transmits an authentication result to the notification server 60 that permits login.

When the notification server 60 receives the authentication result of login permission, it transmits login permission to the management terminal 40a (step S312 in FIG. 10).
When the management terminal 40a receives the authentication result of login permission (step S112 in FIG. 10), it transmits a request to download a list of registered users to the notification server 60 based on the operational input from the staff member (step S113 in FIG. 10).
When the notification server 60 receives the request to download the list of registered users from the management terminal 40a, it transmits the request to download the list of registered users to the user management server 50 (step S313 in FIG. 10).
When the user management server 50 receives a download request for the list of registered users from the notification server 60, it generates data for the list of registered users (step S212 in FIG. 10). Here, the user management server 50 generates the list of registered users by targeting the local government to which the management terminal 40a that requested the list of registered users belongs and extracting registered users from among the residents of that local government from the user information storage unit 5301. This eliminates residents that belong to a local government other than the local government to which the management terminal 40a belongs, and obtains a list of registered users that includes residents who are registered as users and who belong to the local government to which the management terminal 40a belongs (step S6 in FIG. 8).

Regarding which local government the management terminal 40a belongs to, the local government group management unit 5205 may identify the local government based on the login ID used when the management terminal 40a logged in, or may identify the local government based on terminal identification information individually assigned to the management terminal 40a. In this case, the user management server 50 may store in the storage unit 530 local government data in which local government identification information identifying the local government corresponds to the login ID, or local government data in which local government identification information identifying the local government corresponds to the terminal identification information, and the local government group management unit 5205 may identify the local government by referring to the storage unit 304.
In addition, to determine which local government the management terminal 40a belongs to, a local government code for identifying the local government may be included in part of the URL accessed by the management terminal 40a when logging in. In this case, when the management terminal 40a accesses the local government group management unit 5205 and the login is permitted, the local government group management unit 5205 may identify which local government the local government is by referring to the local government code included in the accessed URL. When the local government code is included in part of the URL, for example, a predetermined character (e.g., "?") and the local government code may be described as parameters at the end of the URL. This allows the character string following the predetermined character to be recognized as the local government code.

The list of registered users generated here is data that includes basic information about residents.
When the list of registered users is generated, the user management server 50 transmits the list of registered users to the notification server 60. The data format of the list of registered users to be transmitted may be any data format, but the data format to be transmitted may be, for example, a data format of JSON (JavaScript Object Notation) data type.

When the notification server 60 receives the list of registered users from the user management server 50, it converts the list of registered users into a data format that can be used by the management terminal 40a (step S314 in FIG. 10) and transmits it to the management terminal 40a. Here, if the data format supported by the management terminal 40a is CSV (comma separated values) format, the notification server 60 converts the list of registered users from the JSON data type data format to CSV format before transmitting it.

The management terminal 40a obtains the list of registered users sent from the notification server 60 (step S114 in FIG. 10). Since not all residents in the local government to which the management terminal 40a belongs are necessarily registered users, it is possible to identify those residents who are registered to receive electronic notifications based on the list of registered users. Furthermore, since residents who are not registered users are not included in the list of registered users, the process proceeds to send notifications (notifications printed on print media based on the electronic notifications) by mail to such residents, and electronic notifications can be sent to residents included in the list of registered users.

The management terminal 40a uses the list of registered users to create a list of recipients including basic information about the residents to whom the notification is to be sent, and electronic data for the notification (for example, an electronic notification in Portable Document Format (PDF) format). The electronic notification generated here is an individual electronic notification that has been edited from the original electronic notification to have content appropriate for the resident to whom it is to be sent. When an individual electronic notification is created, a file name is assigned to the created electronic notification.
Here, the management terminal 40a generates the destination list data by adding the file name of the PDF data of the notification to be sent to the resident to the basic information of the resident based on the operational input of the staff member (FIG. 10, step S115). That is, in the destination list data, the file name of the electronic notification to be sent corresponds to each resident to be sent.

Here, step S115 will be described in more detail.
The destination list data is data in which basic information of the recipient residents is associated with the file name of the PDF data of the notification to be sent. The destination list is, for example, an electronic file in CSV format. The basic information of the recipient residents can be the basic information included in the user registration list.
Here, depending on the notification, it may be sent to all residents, but it may also be sent to residents among all residents who meet certain conditions. When sending notifications to residents who meet certain conditions, it is necessary to extract residents to whom the notifications are to be sent from the list of registered users received from the notification server 60. In such a case, the employee operates the management terminal 40a to download a list of recipients to whom the notifications are to be sent from a business system that is a business system of the local government and is a system separate from the notification management system 1. This list of recipients includes residents to whom the notification currently being sent in the local government is to be sent, and is data including residents to whom the notifications are to be sent by mail and residents to whom the notifications are to be sent electronically.

The staff visually checks the target list against the list of registered users and manually selects from the target list those residents to whom notifications will be sent electronically. A list of residents based on the extraction results (electronic resident list) is generated by the management terminal 40a in response to the staff's operational instructions. In this case, the management terminal 40a generates the electronic resident list in a local environment, separate from the functions of the user management server 50 (step S7 in FIG. 8).
The staff may also cause the notification server 60 to extract residents corresponding to the registered user list from the target list. For example, the staff operates the management terminal 40a to load the target list and the registered user list into the user management server 50. The control unit 520 of the user management server 50 compares the target list with the registered user list and extracts residents whose basic information matches, thereby extracting residents registered in the registered user list from the target list. The control unit 520 of the user management server 50 may then generate an electronic resident list as the extraction result and display it on the screen of the management terminal 40a.

Furthermore, staff members generate electronic notifications by performing operational input on the management terminal 40a (or the notification creation terminal 45). Here, when the notification has uniformly the same content for all residents to whom it is sent, the electronic data (PDF data) of the notification is used. On the other hand, the content of the notification may differ depending on the age or family structure of the resident to whom it is sent. In such cases, staff members use the management terminal 40a to process the electronic data of the notification and create electronic data (PDF data) of the notification with content appropriate for the recipient.
When the PDF data of the notification to be sent is created, the management terminal 40a associates the file name of the PDF data of the notification corresponding to each destination based on the operational instructions of the staff member, and generates destination list data.

Once the destination list data is generated, the management terminal 40a accepts input of notification information based on operational input from the staff member (FIG. 10, step S116). As the notification information, for example, a title (e.g., file name) for sorting notifications in the destination list data based on the notification file name can be used.

Next, the management terminal 40a uploads the delivery destination list data to the notification server 60 based on the operational input from the staff member (step S117 in FIG. 11). The delivery destination list data uploaded here is data in CSV format.
When the notification server 60 receives the uploaded delivery destination list, it stores it in the delivery destination list data storage unit 6302 and requests the user management server 50 to send a list of registered users (step S8 in FIG. 8, step S315 in FIG. 11). When the notification server 60 requests the user management server 50 to send a list of registered users, the user management server 50 generates a list of registered users by reading it from the user information storage unit 5301 according to the local government to which the management terminal 40a that requested the list of registered users belongs (step S213 in FIG. 11). The data format of the list of registered users generated here is the JSON data type.
After generating the list of registered users, the user management server 50 transmits it to the notification server 60 .

When the notification server 60 receives the list of registered users from the user management server 50, it converts the list of registered users from the JSON data format to the CSV format. Then, the determination unit 6203 of the notification server 60 performs a matching process between the destination list and the list of registered users (step S316 in FIG. 11) to determine whether the basic information of the residents included in the destination list corresponds to the basic information included in the list of registered users. By performing this matching process, it is possible to determine whether or not electronic notifications can be sent to residents included in the destination list data, and it is possible to prevent residents who do not wish to receive notifications electronically (for whom the user registration process has not been performed) from being set as targets for electronically sending notifications. In other words, by preventing notifications from being sent to residents who do not wish to receive notifications electronically (for whom the user registration process has not been performed), it is possible to prevent sending errors.
After performing the matching process, the notification server 60 transmits the result of the matching process to the management terminal 40a.

When the management terminal 40a receives the matching result from the notification server 60, it displays the matching result on the display screen (step S118 in FIG. 11). The staff member checks the contents displayed on the display screen, and if there is an error, returns to the process of step S115 by inputting an operation to the management terminal 40a, and corrects the delivery destination list. Here, for example, even if the staff member mistakenly selects a resident who is not registered as a user registrant when manually selecting residents to whom electronic notifications are to be sent from the target list in step S115, the resident can be corrected to be a resident to whom notifications are to be sent by mail.
In addition, if the name of a resident included in the delivery destination list data is entered incorrectly, a matching result will be obtained indicating that the name does not match the resident's name listed in the delivery destination list. In such a case, the staff member can take corrective action, such as correcting the resident's name listed in the delivery destination list data.
If no error is detected, the process proceeds to the next step (step S119 in FIG. 11).

Next, the management terminal 40a uploads the electronic notification to the notification server 60 based on operational input from the staff member (step S9 in FIG. 8, step S119 in FIG. 11). The electronic notification uploaded here is the PDF data of the electronic data of the notification created in step S115. Furthermore, if the notification differs for each resident, multiple types of notifications to be sent this time can be uploaded separately. In this case, the file names of the electronic notifications will be different for each.

When the determination unit 6203 of the notification server 60 receives an electronic notification, it stores it in the electronic notification storage unit 6301, and then performs a matching process between the file name of the received electronic notification and the file name included in the destination list (step S317 in FIG. 11). By this matching process, if an electronic notification corresponding to the notification identification information set as the destination list is stored in the electronic notification storage unit 6301, it can be determined that the electronic notification corresponding to the notification identification information can be transmitted. In other words, it can be determined whether the electronic data of the electronic notification corresponding to the electronic notification specified as the target to be transmitted in the destination list has been uploaded. Therefore, if the electronic data of the electronic notification corresponding to the electronic notification specified as the target to be transmitted in the destination list has not been uploaded, it can be detected as an error.
After performing the matching process, the notification server 60 transmits the result of the matching process to the management terminal 40a.

When the management terminal 40a receives the results of the matching process, it displays the matching results on the display screen (FIG. 11, step S120). The staff member checks the contents displayed on this display screen. If there is an error, the staff member can return to the processing of step S115 by inputting an operation to the management terminal 40a, and can correct the destination list or re-upload so that the file names of the electronic data of the notification included in the destination list correspond to the electronic data of the notification that was uploaded.

After confirming that there are no errors, the employee performs operational input to the management terminal 40a, uses the workflow function, sets the administrator (e.g., the employee's superior) as the person to be approved, and inputs an instruction to request approval. The employee may select the administrator as the approver from a list of destinations of the workflow and specify it by operational input from the management terminal 40a. In addition, the notification server 60 may specify the administrator corresponding to the employee who made the approval request by referring to the employee information stored in the employee information storage unit 5302.
In response to an input of an approval request instruction from the staff member, the management terminal 40a transmits a notification of the approval request to the management terminal 40b of the manager (FIG. 11, step S121).

The administrator uses his/her own management terminal 40b to display the requested approval on the display screen. Here, the destination list data, electronic data of the notification, etc. are displayed on the display screen.
The administrator checks the contents (step S122 in FIG. 12), and if there are no problems, presses the approve button using the mouse, keyboard, or touch panel (step S123 in FIG. 12), or presses the reject button if it is determined that corrections are necessary. When the reject button is pressed, the workflow is returned to the employee who made the application, and the process proceeds to step S115.

When the administrator presses the approval button, a notification indicating that the approval button has been pressed is sent from the management terminal 40b to the notification server 60, and the notification server 60 stores information indicating approval as notification information in association with the electronic notification storage unit 6301 (step S318 in FIG. 12). The notification server 60 then sends the electronic notification to the residents included in the destination list data, using email addresses based on the resident user registration list as destinations (step S319 in FIG. 12). When sending electronic data of the notification, an email containing a URL that can reference the electronic data of the notification is sent to the email address as the destination. The electronic data of the notification may be sent as an attachment to the email.
The electronic data of this notification may be transmitted by batch processing when a predetermined time arrives.

《Viewing process》
Next, the viewing process will be described. The viewing process is a process in which a resident uses his/her own user terminal 10 to view electronic data of a notification sent from a local government.
13 and 14 are sequence diagrams illustrating the browsing process.
When the notification server 60 causes the user terminal 10 to view an electronic notification, an email indicating that the electronic notification has arrived is sent from the notification server 60 to the user terminal 10 (step S10 in FIG. 8). By receiving this email, the resident can know that the electronic notification has arrived. When the resident wishes to view the electronic notification, he or she performs an operation input for viewing on the user terminal 10.
When a browsing request is input from a resident (step S131 in FIG. 11), the user terminal 10 transmits a login request to the browsing Web server 80. The browsing Web server 80 transmits the login request to the user management server 50.
When the user management server 50 receives the login request, it transmits a login screen to the browsing Web server 80. The browsing Web server 80 transmits the received login screen to the user terminal 10 (FIG. 13, step S231).
When the user terminal 10 receives the login screen, it performs login processing (step S132 in FIG. 13, step S11 in FIG. 8). Here, an example will be described in which two-step authentication is performed when logging in. In the login processing, the user terminal 10 accepts the resident's input of a login ID and a password into an input field via an input device and a click operation of a "Next" button. Then, the user terminal 10 displays a screen for accepting a selection input of an authentication method for two-step authentication. For example, two options of "email authentication" and "SMS (Short Message Service) authentication" are displayed as two-step authentication methods. When the resident inputs a selection of one of the two-step authentication methods, the user terminal 10 accepts the selection. The user terminal 10 instructs the user management server 50 of the two-step authentication method via the browsing Web server 80 according to the selection.

The user management server 50 performs processing based on the two-step authentication method instructed by the user terminal 10. For example, when "email authentication" is selected, the security code is sent by email to the email address registered as a contact of the user terminal 10 that has requested the two-step authentication, and when "SMS authentication" is selected, the security code is sent as an SMS message to the phone number registered as a contact of the user terminal 10 that has requested the two-step authentication.
When the user terminal 10 receives the security code sent by email or SMS, it displays it on the screen. The resident enters the security code displayed on the screen into the input field on the two-step authentication screen and presses the "Next" button. The user terminal 10 transmits the entered security code to the user management server 50.
The user management server 50 allows the login if the security code entered from the user terminal 10 matches the security code sent to the user terminal 10 (step S232 in FIG. 13), and does not allow the login if they do not match.
If the user management server 50 permits the login, it redirects the user to the notification server 60 (step S233 in FIG. 13) and notifies the notification server 60 that the login has been permitted.

When the consent management unit 6205 of the notification server 60 obtains an authentication result indicating login permission, it transmits a request to the user management server 50 requesting the date and time of agreement to the rules for the resident who has been permitted to log in (step S131 in FIG. 13). Note that, although a request requesting agreement to the rules is transmitted to the user management server 50 here, if the confirmation process based on agreement to the rules has already been completed, it is also possible to display a notification list screen in response to a request from the user terminal 10 (to be described later) (transition to step S336 in FIG. 14).
The terms of use management unit 5204 of the user management server 50 refers to the terms of use agreement information in the user information storage unit 5301 based on the user ID of the resident permitted to log in, and determines whether the resident who made the viewing request has agreed to the terms of use. If the resident has agreed to the terms of use, the terms of use management unit 5204 determines to link the terms of use agreement information to the notification server 60 (step S234 in FIG. 13), and transmits the terms of use agreement information to the notification server 60.
The consent management unit 6205 of the notification server 60 judges whether the date and time of consent to the terms of use obtained from the user management server 50 is earlier than the date and time of the latest update of the terms in the notification server 60 (step S232 in FIG. 13). Since the terms are frequently updated, the date and time of consent to the terms of use sent from the user management server 50 is compared with the latest date and time when the terms were updated (the date and time when they were last updated).

If the date and time of agreement of the terms of use obtained from the user management server 50 is earlier than the date and time of the latest update of the terms in the notification server 60, or if this is the first time the resident has logged in, the notification server 60 displays the terms of use on the user terminal 10 (step S334). The user terminal 10 displays the terms of use on the display screen, and when the resident touches the Agree button (step S133 in FIG. 14), it transmits to the notification server 60 the fact that the resident has agreed to the terms of use and the date and time of agreement.
When the notification server 60 receives the instruction to agree to the terms of use and the agreement date and time from the user terminal 10, it transmits the instruction to agree to the terms of use and the agreement date and time to the user management server 50 (step S335 in FIG. 14).
When the terms of use management unit 5204 of the user management server 50 receives the instruction to agree to the terms of use and the date and time of agreement, it writes the agreement and the date and time of agreement to the terms of use agreement information of the resident who agreed in the user information storage unit 5301 (step S235 in Figure 14), and notifies the notification server 60 that writing of the date and time of agreement has been completed.

When the notification server 60 receives the notification that the writing of the consent date and time has been completed, it generates a notification list screen and transmits it to the user terminal 10 (FIG. 14, step S336).
The user terminal 10 displays the notification list screen received from the notification server 60. Here, a list of notifications sent to the logged-in resident is displayed. When an instruction is input to specify a notification to be viewed from the list (step S134 in FIG. 10), the user terminal 10 transmits a request to the notification server 60 to display the specified notification.
The viewing management unit 6204 of the notification server 60 reads out the electronic notification corresponding to the request received from the user terminal 10 from the electronic notification memory unit 6301 and sends it to the user terminal 10, thereby displaying it on the user terminal 10 so that it can be viewed (step S12 in Figure 8, step S336 in Figure 14).
The user terminal 10 displays the electronic notification received from the notification server 60 on the display screen (step S135 in FIG. 14). This allows the resident to view the electronic notification. On the other hand, when the viewing management unit 6204 of the notification server 60 transmits the electronic notification to the user terminal 10, it notifies the user management server 50 that the electronic notification has been viewed (step S337 in FIG. 14). When the electronic notification is displayed (viewed) by the user terminal 10, the status management unit 5206 of the user management server 50 updates the viewing status corresponding to the resident's user identification information and the electronic notification identification information of the viewed electronic notification by writing the viewing status to the viewing information storage unit 6303 as a status indicating that the electronic notification has been viewed (step S236 in FIG. 14).

According to the embodiment described above, the following effects are achieved.
Benefits for local government employees: Sending work
The notification is sent electronically as an electronic notification. This eliminates the need to insert the printed notification into an envelope for mailing and seal it. In addition, the system checks whether the electronic notification corresponds to the recipient, making it easier to check whether the correspondence between the address and the electronic notification is correct.
In addition, since the sending and management of notifications can be consolidated in the notification server 60, it is possible to promote business efficiency and reduce the number of days required for the entire process. In addition, since the series of tasks for sending notifications can be completed by the local government, there is no risk of passing on sensitive information to the business that delivers the notifications.

Benefits for residents: Viewing
When checking the list of notifications, the notifications can be viewed on the notification list screen, and electronic notifications can also be easily viewed, making it easy to manage notifications.
Furthermore, since electronic notifications are sent using a user ID that is authenticated and issued by a personal card as a key, delivery errors can be eliminated compared to when printed media is delivered.

Benefits for local government employees: follow-up procedures
You will be able to check a list of past notifications and opened notifications, reducing the burden of management.

The registration server 31, the user management server 50, and the notification server 60 in the above-mentioned embodiment may be realized by a computer. In that case, a program for realizing this function may be recorded in a computer-readable recording medium, and the program recorded in the recording medium may be read into the computer system and executed to realize the function. The term "computer system" here includes hardware such as an OS and peripheral devices. The term "computer-readable recording medium" refers to portable media such as flexible disks, optical magnetic disks, ROMs, and CD-ROMs, and storage devices such as hard disks built into the computer system. The term "computer-readable recording medium" may also include a medium that dynamically holds a program for a short period of time, such as a communication line when a program is transmitted via a network such as the Internet or a communication line such as a telephone line, and a medium that holds a program for a certain period of time, such as a volatile memory inside a computer system that is a server or client in such a case. The above-mentioned program may be a program for realizing part of the above-mentioned function, or may be a program that can realize the above-mentioned function in combination with a program already recorded in the computer system, or may be a program that is realized using a programmable logic device such as an FPGA (Field Programmable Gate Array).

The above describes an embodiment of the present invention in detail with reference to the drawings, but the specific configuration is not limited to this embodiment and includes designs that do not deviate from the gist of the present invention.

1...notification management system, 10, 10a...user terminal, 15...IC card, 20...data center server, 30...usage registration system, 31...usage registration server, 35...card reader, 40a, 40b...management terminal, 45...notification creation terminal, 50...user management server, 60...notification server, 70...notification distribution server, 80...viewing web server, 304, 530, 630...storage unit, 311, 510, 610...communication unit, 312, 520, 620...control unit, 1031...user information storage unit, 3121...acquired information processing unit, 3122...personal card reading processing unit, 312 3...Authentication processing unit, 5201...Acquisition unit, 5202...User information inquiry unit, 5203...User registration unit, 5204...Terms of use management unit, 5205...Municipality group management unit, 5206...Status management unit, 5207...Authentication processing unit, 5208...Encryption management unit, 5301...User information storage unit, 5302...Staff information storage unit, 6201...Destination list data acquisition unit, 6202...User registration list data acquisition unit, 6203...Determination unit, 6204...Viewing management unit, 6205...Consent management unit, 6301...Electronic notification storage unit, 6302...Destination list data storage unit, 6303...Viewing information storage unit

Claims (12)

a destination list data acquisition unit that acquires destination list data including information on a person to whom a notification is to be sent, the destination being extracted in response to an operation of a person in charge of an institution to which the notification is to be sent, the destination including basic information of a user belonging to the institution;
a determination unit which compares registered user list data, including basic information obtained by identity verification of a user who desires electronic distribution and who has registered in response to a user registration operation by the user, with the acquired delivery destination list data, and determines whether or not to transmit the notification to a target person included in the delivery destination list data as an electronic notification based on a comparison result determined based on whether or not the basic information of the user included in the delivery destination list data corresponds to the basic information included in the registered user list data;
A notification server having: The delivery destination list data acquisition unit
The notification server according to claim 1, which acquires delivery destination list data uploaded from a terminal device used by a person in charge of the institution. The determination unit is
The notification server according to claim 1 or claim 2, wherein when a public personal authentication agency server has confirmed the identity of a user based on personal information stored on a personal card owned by the user and a My Number card signature password entered by the user, the server makes the determination using the registered user registration list data. The notification server includes:
an electronic notification storage unit that stores an electronic notification to be transmitted and notification identification information that identifies the electronic notification,
In the destination list data acquired by the destination list data acquisition unit, notification item identification information for identifying an electronic notification item to be sent is associated with information about each user,
The notification server according to any one of claims 1 to 3, wherein the determination unit compares the notification identification information included in the destination list data with the notification identification information stored in the electronic notification memory unit, and, based on the comparison result, determines that an electronic notification corresponding to the notification identification information set as the destination list data is stored in the electronic notification memory unit, and that it is possible to send the electronic notification corresponding to the notification identification information. A notification server as described in any one of claims 2 to 4, further comprising a viewing management unit that grants viewing permission to a corresponding user's terminal device for electronic notifications determined by the determination unit to be capable of being transmitted based on the transmission destination included in the registered user list data. a consent management unit that, when receiving a request to view an electronic notification from the user terminal of the user, determines whether the requesting user has consented to a term of use for the service of viewing the electronic notification by referring to the term of use consent information stored in the user information storage unit;
The notification server according to claim 5 , wherein the viewing management unit permits viewing of the electronic notification when it is determined that the user agrees to the terms of use. The notification server of claim 6, wherein when a response indicating agreement is received from a terminal device in response to an inquiry as to whether or not the user agrees to the terms of use, the consent management unit causes the result of the agreement to be written to the user information storage unit as terms of agreement information. The notification server of claim 6 or claim 7, wherein, when it is determined that the terms of use have not been agreed to, the viewing management unit inquires of the terminal device that requested the viewing as to whether or not it agrees to the terms of use, and when a response indicating agreement is received from the terminal device, permits viewing of the electronic notification. A notification management system including the notification server according to any one of claims 1 to 8 and a user management server,
The user management server includes:
an acquisition unit that acquires personal information stored in a personal card owned by a user and a My Number card signature password input by the user;
a user information inquiry unit that makes an inquiry for identity verification by transmitting the personal information and the My Number Card signature password to a public personal authentication institution server;
a user registration unit that writes the personal information into the list of registered users when the result of the inquiry indicates that the user's identity has been confirmed;
A notification management system having the above structure. The notification server includes:
a viewing information storage unit that stores user identification information, electronic notification identification information, and a viewing status that indicates whether the electronic notification has been viewed;
The user management server includes:
a status management unit that updates, when an electronic notification is viewed by a terminal device of a user, a viewing status corresponding to the user identification information of the user and the electronic notification identification information of the viewed electronic notification to a status indicating that the electronic notification has been viewed;
The notification management system according to claim 9, further comprising: 1. A computer-implemented notification management method, comprising:
Obtaining a list of destinations including information on recipients of notifications, the destinations being extracted in response to an operation of a person in charge of an institution to which the notifications are sent, the destinations including basic information on users belonging to the institution;
A notification management method in which a determination unit compares user registration list data, which includes basic information obtained by identity verification of a user who registers in response to a user registration operation by the user who wishes to receive electronic distribution, with the acquired destination list data, and determines whether or not to send the notification to the target person included in the destination list data as an electronic notification based on the result of the comparison, which is determined based on whether the basic information of the user included in the destination list data corresponds to the basic information included in the user registration list data. Obtaining a list of destinations including information on recipients of notifications, the destinations being extracted in response to an operation of a person in charge of an institution to which the notifications are sent, the destinations including basic information on users belonging to the institution;
A program that causes a computer to execute the following steps: Compare user registration list data, which includes basic information obtained by verifying the identity of a user who is registered in response to a user registration operation by the user who wishes to receive electronic distribution, with the acquired destination list data; and, based on the comparison result determined based on whether the basic information of the user included in the destination list data corresponds to the basic information included in the user registration list data, determine whether or not to send the notification to the target person included in the destination list data as an electronic notification.

Images