JP7521910B2 - Monitoring system, server device, monitoring method, and program - Google Patents

Description

Article 30, paragraph 2 of the Patent Act applies (1) Date of website publication: November 27, 2019, Website address: https://www.nttdata. com/jp/ja/news/release/2019/112700/ <Reference> Announcement page on the website of NTT DATA Corporation (2) Publication date: December 28, 2019 Publication name: Nikkei FinTech December 2019 issue (No. 45) (Web version/website posting date: December 23, 2019) (Website address: https://xtech.nikkei.com/it/atclnft/feature/00024/121800021/) <Reference> Article published in the December 2019 issue (No. 45) of Nikkei FinTech <Reference> Article published on the Nikkei FinTech website (3) Publication date: January 1, 2020 Publication name: "Nikkin" January 1, 2020 (Wednesday) <Reference> Article published in "Nikkin" on January 1, 2020 (Wednesday)

The present invention relates to a monitoring system, a server device, a monitoring method, and a program.

In recent years, a technology has become known that allows a customer to simultaneously check the balances of his or her family members' accounts when carrying out a transaction on his or her own account (see, for example, Patent Document 1).

JP 2012-3559 A

As the population ages, it is expected that the number of people with dementia (including mild dementia) will increase, and there is a demand for a system in financial services that can inform others of transactions by people being watched over, such as the elderly. However, the above-mentioned conventional technology does not respect the wishes of the person being watched over, and does not take into consideration the privacy of the person being watched over, as it performs balance inquiries all at once. Furthermore, with the above-mentioned conventional technology, it is difficult for people in the vicinity, such as family members, to obtain transaction information about the person being watched over unless they, for example, perform the transaction operations.

The present invention has been made to solve the above problems, and its purpose is to provide a monitoring system, server device, monitoring method, and program that can properly notify the monitored person of transaction information while respecting the monitored person's personal wishes and protecting the monitored person's privacy.

In order to solve the above problems, one aspect of the present invention is a monitoring system that includes a notification condition memory unit that stores target account identification information that identifies the account of the person being monitored, monitoring person identification information that identifies the monitoring person monitoring the person being monitored, and notification conditions for notifying of transactions in the account of the person being monitored, which notification conditions are set by the person being monitored from a number of types including the amount of a single transaction, the type of deposit/withdrawal transaction, the transaction time, and the transaction location, in association with each other, and a notification processing unit that, when deposit/withdrawal data for the account of the person being monitored obtained from an accounting system satisfies the notification condition corresponding to the target account identification information stored in the notification condition memory unit , notifies the person being monitored identified by the monitoring person identification information corresponding to the target account identification information of a monitoring notification indicating that a transaction has occurred that satisfies the notification condition set by the person being monitored without the approval of the person being monitored .

In one aspect of the present invention, the above-mentioned monitoring system further includes a notification information storage unit that stores the monitoring person identification information and the notification information of the monitoring person in association with each other, and when the deposit/withdrawal data of the account of the monitored person satisfies the notification condition, the notification processing unit transmits a monitoring notification to the monitoring person indicating that a transaction that satisfies the notification condition has occurred in the deposit/withdrawal data of the account of the monitored person, based on the notification information of the monitoring person corresponding to the monitoring person identification information stored in the notification information storage unit.

In one aspect of the present invention, in the above-mentioned monitoring system, the notification destination information includes an email address, and the notification processing unit sends the monitoring notification by email to the email address of the person who is watching over the person.

In one aspect of the present invention, in the above-mentioned monitoring system, the notification destination information includes push notification destination information, and the notification processing unit transmits the monitoring notification by push notification to an internet banking application for which the watcher is registered as a user, based on the push notification destination information.

In one aspect of the present invention, in the above-mentioned monitoring system, the monitoring person identification information is monitoring person account identification information that identifies the account of the monitoring person.

In one aspect of the present invention, the monitoring system includes a usage information storage unit that stores user account identification information that identifies a user's account and usage contract information that indicates whether or not a contract to use Internet banking has been made, in association with each other, and an online banking processing unit that provides transaction services through the Internet banking, and the accounting system transmits deposit and withdrawal data for the user's account indicated by the user account identification information when the usage contract information associated with the user account identification information stored in the usage information storage unit indicates that a contract to use Internet banking has been made, and the notification processing unit determines that the deposit and withdrawal data for the user's account output by the accounting system is deposit and withdrawal data for the account of the person being monitored when the user account identification information matches the target account identification information stored in the notification condition storage unit.

In one aspect of the present invention, in the above monitoring system, the usage information storage unit stores the user account identification information, the usage contract information, and usage suspension information indicating whether or not to suspend use of the Internet banking transaction service in association with each other, and the Internet banking processing unit suspends the provision of the Internet banking transaction service to the user's account indicated by the user account identification information when the usage suspension information associated with the user account identification information stored in the usage information storage unit indicates that use of the Internet banking transaction service is to be suspended.

In one aspect of the present invention, in the above-mentioned monitoring system, the notification conditions include a condition that approval is required for a transaction in the account of the person being watched over, and when the condition that approval is required for a transaction in the account of the person being watched over that is associated with the target account identification information stored in the notification condition storage unit is satisfied when a transaction in the account of the person being watched over is made, the notification processing unit sends an approval notification to the person being watched over requesting approval of the transaction in the account of the person being watched over before making the transaction in the account of the person being watched over, and when approval of the transaction in the account of the person being watched over is received from the person being watched over, the notification processing unit causes the accounting system to complete the transaction in the account of the person being watched over.

In one aspect of the present invention, the above-mentioned monitoring system further includes a registration processing unit that, in response to a request from the monitored person, associates the target account identification information, the monitoring person identification information, and the notification conditions and stores them in the notification condition storage unit.

In addition, one aspect of the present invention is a server device characterized by comprising: a notification condition memory unit that stores target account identification information that identifies the account of the person being monitored; monitoring person identification information that identifies the monitoring person monitoring the person being monitored; notification conditions for notifying of transactions in the account of the person being monitored, which notification conditions are set by the person being monitored from a plurality of types including the amount of a single transaction, the type of deposit/withdrawal transaction, the transaction time, and the transaction location, in association with each other; and a notification processing unit that, when deposit/withdrawal data of the account of the person being monitored obtained from an accounting system satisfies the notification condition corresponding to the target account identification information stored in the notification condition memory unit , notifies the person being monitored indicated by the monitoring person identification information corresponding to the target account identification information of a monitoring notification indicating that a transaction has occurred that satisfies the notification condition set by the person being monitored without the approval of the monitoring person.

Moreover, one aspect of the present invention is a monitoring method characterized by including a registration step in which a registration processing unit corresponds target account identification information that identifies the account of the person being monitored, monitoring person identification information that identifies the person being monitored, and notification conditions for notifying of transactions in the account of the person being monitored, which notification conditions are set by the person being monitored from a plurality of types including the amount of a single transaction, the type of deposit/withdrawal transaction, the transaction time, and the transaction location, and stores them in a notification condition memory unit; and a notification processing step in which a notification processing unit notifies the person being monitored, when the deposit/withdrawal data of the account of the person being monitored obtained from an accounting system, that satisfies the notification condition corresponding to the target account identification information stored in the notification condition memory unit, to the person being monitored, indicated by the monitoring person identification information corresponding to the target account identification information, of a monitoring notification indicating that a transaction that satisfies the notification condition set by the person being monitored has occurred without the approval of the person being monitored.

Furthermore, one aspect of the present invention is a program for causing a computer to execute, in the above-mentioned monitoring system, a registration step of associating target account identification information identifying the account of the person being monitored, monitoring person identification information identifying the person being monitored monitoring the person being monitored, and notification conditions for notifying of transactions in the account of the person being monitored, which notification conditions are set by the person being monitored from a plurality of types including the amount of a single transaction, the type of deposit/withdrawal transaction, the transaction time, and the transaction location, and storing them in a notification condition memory unit, and a notification processing step of notifying the person being monitored, when the deposit/withdrawal data of the account of the person being monitored obtained from the accounting system satisfies the notification condition corresponding to the target account identification information stored in the notification condition memory unit, notifying the person being monitored identified by the monitoring person identification information corresponding to the target account identification information of a monitoring notification indicating that a transaction has occurred that satisfies the notification condition set by the person being monitored without the approval of the person being monitored .

According to the present invention, it is possible to appropriately notify the monitored person of transaction information while respecting the monitored person's wishes and protecting the monitored person's privacy.

1 is a block diagram showing an example of a monitoring system according to a first embodiment. 5 is a diagram illustrating an example of data in an account information storage unit according to the first embodiment. FIG. FIG. 4 is a diagram showing an example of data in a transaction history storage unit in the first embodiment. 11 is a diagram illustrating an example of data in a user information storage unit of an IB application server according to the first embodiment; FIG. A figure showing an example of data in a user information storage unit of an online banking server in the first embodiment. 5 is a diagram illustrating an example of data in a notification condition storage unit according to the first embodiment; FIG. FIG. 2 is a diagram showing an example of the relationship between a person being watched over and a watcher. 5 is a diagram illustrating an example of data in a notification destination storage unit according to the first embodiment; FIG. FIG. 2 is a diagram illustrating an example of a registration process of the monitoring system according to the first embodiment. FIG. 13 is a diagram showing an example of a registration screen of an IB store terminal device in the first embodiment. FIG. 11 is a diagram showing another example of the registration process of the monitoring system according to the first embodiment. FIG. 13 is a diagram showing an example of a registration screen of a watching target PC in the first embodiment. FIG. 4 is a diagram illustrating an example of a notification process of the monitoring system according to the first embodiment. FIG. 4 is a diagram showing an example of a monitoring notification by email in the first embodiment. FIG. 11 is a diagram showing an example of a detail inquiry process of the monitoring system according to the first embodiment. 13 is a diagram showing an example of a detail inquiry screen of a watcher PC in the first embodiment. FIG. FIG. 11 is a block diagram showing an example of a monitoring system according to a second embodiment. FIG. 11 is a diagram illustrating an example of data in a notification condition storage unit according to the second embodiment. 13A and 13B are diagrams illustrating an example of a process of adding memo information by a watcher in the second embodiment. A figure showing an example of a statement inquiry screen on a user's smartphone by a person being watched over in the second embodiment. FIG. 11 is a diagram illustrating an example of a transaction approval process of the monitoring system according to the second embodiment. FIG. 13 is a block diagram showing an example of a monitoring system according to a third embodiment. FIG. 13 is a diagram illustrating an example of a registration process of the monitoring system according to the third embodiment. FIG. 13 is a diagram showing another example of the registration process of the monitoring system according to the third embodiment. FIG. 13 is a diagram illustrating an example of a notification process of the monitoring system according to the third embodiment. FIG. 13 is a diagram illustrating an example of a detail inquiry process of the monitoring system according to the third embodiment. FIG. 13 is a block diagram showing an example of a monitoring system according to a fourth embodiment. FIG. 13 is a diagram illustrating an example of a registration process of the monitoring system according to the fourth embodiment. FIG. 13 is a diagram illustrating an example of a notification process of the monitoring system according to the fourth embodiment. FIG. 13 is a diagram showing an example of a detail inquiry process of the monitoring system according to the fourth embodiment.

The following describes a monitoring system, server device, monitoring method, and program according to an embodiment of the present invention with reference to the drawings.

[First embodiment]
FIG. 1 is a block diagram showing an example of a monitoring system 1 according to the present embodiment.
1, the monitoring system 1 includes an online banking server 10, an IB store terminal device 21, an accounting terminal device 22, an ATM 23, an accounting system 30, an IB application server 40, a user PC 51, and a user smartphone 52. The online banking server 10, the IB store terminal device 21, the accounting terminal device 22, the ATM 23, the accounting system 30, the IB application server 40, the user PC (user personal computer) 51, and the user smartphone 52 can be connected via a network NW1.

In this embodiment, Internet banking may be abbreviated as "IB."
In addition, in the watching system 1 according to this embodiment, the user being watched over will be referred to as a watched-over target U1, and the user watching over will be referred to as a watcher U2.

The IB store terminal device 21, the accounting terminal device 22, and the ATM 23 are devices located, for example, in a bank store ST (an example of a financial institution store).
The IB store terminal device 21 is, for example, a terminal device operated by a bank employee at the bank branch ST, and is a terminal device for performing various settings and operations related to the Internet banking service. For example, at a counter of the bank branch ST, the IB store terminal device 21 accepts registration information as input information when performing registration processing for the monitoring system 1, and transmits the registration information to the Internet banking server 10 via the network NW1.

The IB store terminal device 21 sends a registration request to the online banking server 10, which includes, for example, the account number of the person being watched over U1, the account number of the watcher U2, and the notification conditions set by the person being watched over U1.

The accounting system terminal device 22 is, for example, a terminal device operated by a bank employee at the bank branch ST, and is a terminal device for executing various processes for the accounting system 30. For example, when performing registration processing for the monitoring system 1 at the counter of the bank branch ST, the accounting system terminal device 22 accepts information for the IB contract of the monitored person U1 as input information and transmits it to the accounting system 30 via the network NW1.

The accounting terminal device 22 sends a registration request to the accounting system 30, which includes, for example, the account number of the monitored person U1, the IB contract information, and the IB usage suspension information. Details of the IB contract information and the IB usage suspension information will be described later.

The ATM (Automatic Teller Machine) 23 is, for example, a device located in a bank branch ST, and is operated by a user when performing financial transactions such as deposits and withdrawals. The ATM 23 transmits transaction information to the accounting system 30 via the network NW1 and performs the transaction.

The user PC 51 refers to a personal computer owned by a user, and is used when conducting Internet banking.
The user smartphone 52 indicates a smartphone owned by the user, and is used when using Internet banking with the IB app.

It should be noted that the users here include both the person being watched over U1 and the watcher U2.
Furthermore, the user PC 51 and the user smartphone 52 are examples of the user terminal 50. Furthermore, in the example shown in Fig. 1, for the sake of explanation, one user PC 51 and one user smartphone 52 are described, but a plurality of user PCs 51 and a plurality of user smartphones 52 may be used.

The accounting system 30 is a core system in a financial institution such as a bank, and is a system that mainly handles deposits and withdrawals, settlement of funds, and account management. The accounting system 30 includes, for example, a NW (network) communication unit 31, an account information storage unit 32, a transaction history storage unit 33, a transaction processing unit 34, and a deposit and withdrawal data distribution unit 35.

The NW communication unit 31 is connected to the network NW1 and performs various communications via the network NW1. For example, the NW communication unit 31 is mainly connected to the online banking server 10, the accounting terminal device 22, the ATM 23, and the IB application server 40 via the network NW1 and performs various communications.

The account information storage unit 32 (an example of a usage information storage unit) stores account information of users who use financial institutions such as banks. For example, as shown in FIG. 2, the account information storage unit 32 stores at least "account number," "name," "address," "IB contract information," and "IB usage suspension information" in association with each other. Here, an example of data in the account information storage unit 32 will be described with reference to FIG. 2.

FIG. 2 is a diagram showing an example of data stored in the account information storage unit 32 in this embodiment.
2, "Account Number" indicates the account number of the user who opened the account, and is an example of user account identification information that identifies the user's account. Also, "Name" and "Address" indicate the "name" and "address" of the user.

The "IB contract information" (an example of usage contract information) is flag information that indicates whether or not the account has a contract to use Internet banking. When the "IB contract information" is "1", it indicates that there is a contract to use Internet banking, and when it is "0", it indicates that there is no contract to use Internet banking. The "IB contract information" is used when distributing deposit and withdrawal data for the user's account to the online banking server 10.

In addition, the "IB usage suspension information" (an example of usage suspension information) is flag information indicating whether or not the account will be suspended from using transaction services via internet banking. When the "IB usage suspension information" is "1", it indicates that the usage of transaction services via internet banking will be suspended, and when it is "0", it indicates that the usage of transaction services via internet banking will not be suspended (will be permitted). The "IB usage suspension information" is set to "1", for example, when the monitored person U1, such as an elderly person, does not use internet banking.

For example, in the example shown in Figure 2, the account with the "Account Number" "XXXX-201-1234567" indicates that the user's "Name" is "○○ Taro" and the user's "Address" is "XX Town, XX City 1-2." In addition, the "IB Contract Information" is "1" and the "IB Suspension Information" is "1." In this case, since the "IB Suspension Information" is "1," it indicates that this account will not use transaction services via Internet banking.

The account with the "Account Number" "XXXX-202-78901234" indicates that the user's "Name" is "○○ Hanako" and the user's "Address" is "3-3-3, ○△cho, XX city." The "IB contract information" is "1" and the "IB usage suspension information" is "0." In this case, since the "IB usage suspension information" is "0," this indicates that this account uses transaction services via internet banking.

Returning to the explanation of Fig. 1, the transaction history storage unit 33 stores transaction history such as deposits and withdrawals. Here, an example of data in the transaction history storage unit 33 will be explained with reference to Fig. 3.
FIG. 3 is a diagram showing an example of data stored in the transaction history storage unit 33 in this embodiment.

As shown in Figure 3, the transaction history memory unit 33 stores the "account number,""date,""summary,""paymentamount,""depositamount,""balance,""branchnumber," and "ATM number" in association with each other.
Here, "Date" indicates the date of the transaction, and "Summary" indicates the content of the transaction. "Amount Paid" indicates the amount withdrawn, "Amount Deposited" indicates the amount deposited, and "Balance" indicates the remaining balance. "Store Number" indicates the identification number of the store where the transaction was made, and "ATM Number" indicates the identification number of the ATM where the transaction was made.

For example, the example shown in Figure 3 shows that in a transaction for an account with an "Account Number" of "XXXX-201-1234567", a withdrawal of "10,000" was made by "Card" on a "Date" of "20-212" (February 12, 2020). It also shows that this transaction was made at an ATM with a "Branch Number" of "201" and an "ATM Number" of "M0001".

Returning to the explanation of FIG. 1, the transaction processing unit 34 processes various transactions at the counter of the bank branch ST and at the ATM 23, and stores the transaction history of deposits and withdrawals in the transaction history memory unit 33. The transaction processing unit 34 stores, for example, the transaction history of deposits and withdrawals (deposit and withdrawal data) as shown in FIG. 3 in the transaction history memory unit 33.

The deposit/withdrawal data distribution unit 35 periodically extracts deposit/withdrawal data of users who have signed up for internet banking from the transaction history stored in the transaction history storage unit 33 at the specified time for distributing deposit/withdrawal data (for example, twice a day at midnight and noon) and distributes it to the online banking server 10. The deposit/withdrawal data distribution unit 35 extracts deposit/withdrawal data from the history information that corresponds to account numbers for which the "IB contract information" stored in the account information storage unit 32 is "1", and transmits the extracted deposit/withdrawal data to the online banking server 10 via the NW communication unit 31.

The IB application server 40 is a server device that provides internet banking services using an IB application (hereinafter referred to as the IB application) of the user smartphone 52. The IB application server 40 includes, for example, a network communication unit 41, a user information storage unit 42, an IB service processing unit 43, and a push notification processing unit 44.

The NW communication unit 41 connects to the network NW1 and performs various communications via the network NW1. For example, the NW communication unit 41 mainly connects to the online banking server 10 and the user smartphone 52 via the network NW1 and performs various communications.

The user information storage unit 42 (an example of a notification destination information storage unit) stores user information related to users of the IB app. For example, as shown in FIG. 4, the user information storage unit 42 stores an "account number," an "app user ID," and a "device token" in association with each other. Here, an example of data in the user information storage unit 42 will be described with reference to FIG. 4.

FIG. 4 is a diagram showing an example of data in the user information storage unit 42 in this embodiment.
4, the "app user ID" is a user ID assigned to the user smartphone 52 on which the IB app is installed, and the "device token" is device identification information acquired from the user smartphone 52 in order to send a push notification to the user smartphone 52. In this embodiment, the "device token" is notification destination information of the watcher U2, and corresponds to the notification destination information of the push notification.

For example, the example shown in Figure 4 indicates that the "Application User ID" corresponding to the "Account Number" "XXXX-202-78901234" is "UXXXXXXXXXX" and the "Device Token" is "XXXXXXXXXXXX".

Returning to the explanation of Figure 1, the IB service processing unit 43 processes various internet banking services using the IB app.

The push notification processing unit 44 executes a process of sending a push notification by the IB app. The push notification processing unit 44 sends a push notification via the network NW1 using the "device token" stored in the user information storage unit 42 as notification destination information. For example, when notifying a watcher U2 (described below) of a watcher notification by push notification, the push notification processing unit 44 executes a process of sending a watcher notification to the device of the watcher U2 (e.g., the user smartphone 52).

The online banking server 10 (an example of a server device) is a server device that provides internet banking services and is capable of, for example, carrying out various transactions via the internet banking web. The online banking server 10 includes, for example, a network communication unit 11, a server storage unit 12, and a server control unit 13.

The NW communication unit 11 is connected to the network NW1 and performs various communications via the network NW1. For example, the NW communication unit 11 is mainly connected to the IB store terminal device 21, the accounting system 30, the IB application server 40, and the user terminal 50 via the network NW1 and performs various communications.

The server storage unit 12 stores various information used by the online banking server 10. The server storage unit 12 includes, for example, a user information storage unit 121, a notification condition storage unit 122, a notification destination information storage unit 123, and a deposit/withdrawal data storage unit 124.

The user information storage unit 121 stores information on users who use internet banking. For example, as shown in FIG. 5, the user information storage unit 121 stores "account number," "user ID," "password," and "IB usage suspension information" in association with each other. Here, an example of data in the user information storage unit 121 will be described with reference to FIG. 5.

FIG. 5 is a diagram showing an example of data stored in the user information storage unit 121 in this embodiment.
5, "user ID" is user identification information for using Internet banking, for example, a login ID. "Password" indicates a password used together with the "user ID" when logging in. "IB usage suspension information" is the same as the "IB usage suspension information" in the account information storage unit 32 described above, and is flag information obtained from the account information storage unit 32 of the accounting system 30.

For example, the example shown in Figure 5 shows that the "User ID" and "Password" corresponding to the "Account Number" "XXXX-201-1234567" are "UXXXX" and "XXXXXXXXX". In addition, the "IB Use Suspension Information" for this account is "1", indicating that use of Internet banking has been suspended.

Returning to the explanation of FIG. 1, the notification condition storage unit 122 stores, in association with each other, target account identification information that identifies the account of the person being watched over U1, watcher identification information that identifies the watcher U2, and notification conditions for notifying transactions in the account of the person being watched over U1, which are set by the person being watched over U1. Here, the watcher identification information is, for example, watcher account identification information that identifies the account of the watcher U2.

The notification conditions include, for example, the type of deposit/withdrawal transaction (e.g., deposit, withdrawal, transfer, etc.), transaction amount information (e.g., transaction amount, total transaction amount for a specified period, etc.), etc. In addition, an example of data in the notification condition storage unit 122 will be described with reference to FIG. 6.

FIG. 6 is a diagram showing an example of data in the notification condition storage unit 122 in this embodiment.
As shown in Figure 6, the notification condition memory unit 122 stores the "account number of the person being watched," the "account number of the watcher," and the "notification condition" in association with each other. Here, the "account number of the person being watched" is the account number of the person being watched U1, and is an example of target account identification information. Furthermore, the "account number of the watcher" is the account number of the watcher U2, and is an example of watcher account identification information. Furthermore, the "account number of the person being watched" and the "account number of the watcher" are account numbers at the same financial institution.

For example, the example shown in Figure 6 shows that the "account number of the person being watched" of "XXXX-201-1234567" corresponds to the "account number of the person being watched" of "XXXX-202-78901234". In other words, this shows that the watcher U2 of the person being watched U1, who has an account number of "XXXX-201-1234567", is a user who has an account number of "XXXX-202-78901234".

It also indicates that the "notification condition" is "withdrawal transaction of 100,000 yen or more." In this case, it indicates that if the monitored person U1 makes a withdrawal transaction of 100,000 yen or more to the account "XXXX-201-1234567," a notification will be sent to the monitor U2 at "XXXX-202-78901234."

Here, with reference to FIG. 7, an application example of the watching target U1 and the watcher U2 in the watching system 1 in this embodiment will be described.
FIG. 7 is a diagram showing an example of the relationship between a watched-over person U1 and a watcher U2.

As shown in FIG. 7, for example, if the person being watched over U1 is an elderly person or a disabled person, the person watching over U2 may be a family member or a friend, and if the person being watched over U1 is a husband (or wife), the person watching over U2 may be the spouse who is the wife (or husband). Also, if the person being watched over U1 is a child (minor), the person watching over U2 may be a parent or sibling.

In this way, various relationships are possible between the person being watched over U1 and the watcher U2, and the "notification conditions" set in the notification condition memory unit 122 can be set to various conditions depending on the relationship between the person being watched over U1 and the watcher U2.
The information stored in the notification condition storage unit 122 is registered by a registration processing unit 132, which will be described later.

Returning to the explanation of FIG. 1, the notification information storage unit 123 stores the watcher identification information and the notification information of the watcher U2 in association with each other. For example, as shown in FIG. 8, the notification information storage unit 123 stores the "watcher's account number" and the "watcher's email address" in association with each other. Here, an example of data in the notification information storage unit 123 will be explained with reference to FIG. 8.

FIG. 8 is a diagram showing an example of data in the notification destination information storage unit 123 according to this embodiment.
8, "Watcher's account number" is the account number of the person being watched over U1, and is an example of target account identification information, similar to the notification condition storage unit 122. Also, "Watcher's email address" indicates the email address to which the watcher sends notifications, and is an example of notification destination information for watcher U2.

The example shown in Figure 8 shows that the "Watcher's account number" is "XXXX-202-78901234" and the "Watcher's email address" is "xxxx@abcd.com".

Returning to the explanation of FIG. 1, the deposit/withdrawal data storage unit 124 stores deposit/withdrawal data for accounts subscribed to Internet banking, which is distributed periodically (e.g., twice a day at midnight and noon) from the accounting system 30. The deposit/withdrawal data storage unit 124 stores account numbers in association with transaction information, which is deposit/withdrawal data, in the same manner as the transaction history storage unit 33 in FIG. 3 described above.

The server control unit 13 is a processor including, for example, a CPU (Central Processing Unit) and generally controls the online banking server 10. The server control unit 13 includes, for example, an online banking processing unit 131, a registration processing unit 132, a notification processing unit 133, and a statement inquiry processing unit 134.

The online banking processing unit 131 executes various processes for internet banking. For example, the online banking processing unit 131 provides internet banking transaction services via the Web, executes login processing using the "user ID" and "password" stored in the user information storage unit 121, and after the login processing, executes transaction processing such as deposit and withdrawal transactions in cooperation with the accounting system 30.

In addition, when the suspension information associated with the user account identification information stored in the account information storage unit 32 indicates that the use of the internet banking transaction service is to be suspended, the online banking processing unit 131 suspends the provision of the internet banking transaction service to the user's account indicated by the user account identification information. For example, the online banking processing unit 131 refers to the "IB suspension information" in the user information storage unit 121 obtained from the "IB suspension information" in the account information storage unit 32, and when the "IB suspension information" is "1", suspends the provision of the internet banking transaction service to the account with the corresponding account number.

In response to a request from the person being watched U1, the registration processing unit 132 executes a registration process that associates the target account identification information ("account number of the person being watched"), the watcher identification information ("account number of the watcher"), and the notification conditions and stores them in the notification condition storage unit 122. In response to a registration request from any of the IB store terminal device 21, the user PC 51 of the person being watched U1, and the user smartphone 52 of the person being watched U1, the registration processing unit 132 associates the account number of the person being watched U1, the account number of the watcher U2, and the notification conditions included in the registration request and stores them in the notification condition storage unit 122.

In addition, in response to a request to register IB suspension information from the accounting system 30, the registration processing unit 132 executes a registration process to set the "IB suspension information" in the user information storage unit 121 to "1."

When the deposit/withdrawal data of the account of the monitored person U1 obtained from the accounting system 30 satisfies the notification conditions corresponding to the target account identification information stored in the notification condition memory unit 122, the notification processing unit 133 notifies the watcher U2 indicated by the watcher identification information corresponding to the target account identification information. Here, when the user account identification information of the deposit/withdrawal data of the user's account periodically output by the accounting system 30 matches the target account identification information stored in the notification condition memory unit 122, the notification processing unit 133 determines that the data is deposit/withdrawal data of the account of the monitored person U1.

When the deposit/withdrawal data of the account of the person being watched over U1 satisfies the notification conditions, the notification processing unit 133 sends a monitoring notification to the watcher U2 indicating that a transaction that satisfies the notification conditions has occurred in the deposit/withdrawal data of the account of the person being watched over U1, based on the notification information (e.g., email address) of the watcher U2 corresponding to the account number of the watcher U2 stored in the notification information storage unit 123. The notification processing unit 133 sends the monitoring notification by email, for example, to the email address of the watcher U2.

The notification destination information also includes push notification destination information. Here, the push notification destination information is, for example, a "device token" stored in the user information storage unit 42 (an example of a destination information storage unit) of the IB application server 40. The notification processing unit 133 transmits a monitoring notification by push notification to the Internet banking application (IB application) for which the watcher U2 is registered as a user, based on the push notification destination information ("device token").
In addition, the notification processing unit 133 stores the deposit and withdrawal data for the user's account, which is periodically output (distributed) by the accounting system 30, in the deposit and withdrawal data memory unit 124.

The statement inquiry processing unit 134 executes a process in which the watcher U2 inquires about transaction details for the account of the person being watched over U1. For example, when a request for inquiry about transaction details for the person being watched over U2 is made from the user terminal 50 (user PC 51 or user smartphone 52) of the watcher U2, the statement inquiry processing unit 134 extracts deposit/withdrawal data that satisfies the notification conditions for the person being watched over U1 stored in the notification condition storage unit 122 from the deposit/withdrawal data corresponding to the account of the person being watched over U1 stored in the deposit/withdrawal data storage unit 124, and transmits this as statement inquiry data to the user terminal 50 (user PC 51 or user smartphone 52) of the watcher U2.

Next, the operation of the monitoring system 1 according to the present embodiment will be described with reference to the drawings.
In the following description, the user terminal 50 of the person being watched U1 is referred to as the person being watched terminal 50-1, the user terminal 50 of the watcher U2 is referred to as the watcher terminal 50-2, the user PC 51 of the person being watched U1 is referred to as the person being watched PC 51-1, and the user PC 51 of the watcher U2 is referred to as the watcher PC 51-2. Also, the user smartphone 52 of the person being watched U1 is referred to as the person being watched smartphone 52-1, and the user smartphone 52 of the watcher U2 is referred to as the watcher smartphone 52-2.

Figure 9 is a diagram showing an example of the registration process of the monitoring system 1 according to the first embodiment. Here, the registration process is described in which the monitored person U1 registers the use of the monitoring service provided by the monitoring system 1 at the counter of the bank branch ST. In addition, it is assumed that the monitored person U1 is, for example, an elderly person who does not use Internet banking.

As shown in FIG. 9, first, the IB store terminal device 21 accepts registration information (step S101). The IB store terminal device 21 is operated, for example, by a teller at the bank store ST, and accepts registration information entered based on a registration application form from the monitored person U1. The IB store terminal device 21 accepts registration information, for example, through a registration screen such as screen G1 shown in FIG. 10. Here, the registration information includes the account number of the monitored person U1, which is the target account identification information, the account number of the monitor U2, which is the monitor account identification information, and the notification conditions.

Figure 10 is a diagram showing an example of a registration screen of the IB store terminal device 21 in this embodiment. The IB store terminal device 21 displays a registration screen such as screen G1, and accepts registration information through operations by a teller at the bank store ST.

Next, the IB store terminal device 21 sends a registration request to the online banking server 10 (step S102). The IB store terminal device 21 sends the registration request including the above-mentioned registration information to the online banking server 10 via the network NW1.

Next, the online banking server 10 executes the registration process (step S103). The network communication unit 11 of the online banking server 10 receives the registration request from the IB store terminal device 21 via the network NW1. In response to the received registration request, the registration processing unit 132 of the online banking server 10 associates the account number of the monitored person U1, the account number of the watcher U2, and the notification conditions contained in the registration request, and stores them in the notification condition storage unit 122, for example, as shown in FIG. 6.

On the other hand, the accounting terminal device 22 accepts registration information (step S104). The accounting terminal device 22 is operated, for example, by a teller at the bank branch ST, and accepts registration information such as the account number of the monitored person U1, IB contract information for setting a contract to use Internet banking, and IB suspension information for setting the suspension of use of transaction services via Internet banking.

Next, the accounting terminal device 22 transmits a registration request to the accounting system 30 (step S105). The accounting terminal device 22 transmits a registration request including, for example, the account number of the monitored person U1, the IB contract information, and the IB usage suspension information to the accounting system 30 via the network NW1.

Next, the accounting system 30 executes a registration process for IB usage (step S106). The accounting system 30 receives a registration request from the accounting terminal device 22 via the NW communication unit 31, and stores the registration information included in the registration request in the account information storage unit 32 in response to the received registration request. For example, the accounting system 30 extracts account information corresponding to the account number of the monitored person U1 included in the received registration request from the account information stored in the account information storage unit 32, and changes the IB contract information and IB usage suspension information of the account information to "1".

The accounting system 30 also sends a registration request including the IB usage suspension information to the online banking server 10 via the network NW1 (step S107). Here, the monitored person U1 is a user who does not use Internet banking, such as an elderly person, so the accounting system 30 sends a registration request including flag information indicating that the IB usage suspension information is "1", via the network NW1 to the online banking server 10.

Next, the online banking server 10 executes the IB usage suspension process (step S108). The NW communication unit 11 receives the registration request from the accounting system 30 via the network NW1. Then, the registration processing unit 132 executes the IB usage suspension process to set the IB usage suspension information in the user information storage unit 121 to "1" in response to the received registration request.
This completes the registration process for the watched-over person U1 to register for use of the watching service.

Next, the registration process via Internet banking will be described with reference to FIG. 11 and FIG.
11 is a diagram showing another example of the registration process of the monitoring system 1 according to the present embodiment. Here, a registration process in which the monitored person U1 himself/herself registers the use of the monitoring service provided by the monitoring system 1 through internet banking will be described.

As shown in FIG. 11, first, the watched person terminal 50-1 accepts registration information (step S201). Here, the watched person terminal 50-1 includes the watched person PC 51-1 and the watched person smartphone 52-1. The watched person terminal 50-1 is operated by the watched person U1 himself and accepts the registration information. The watched person terminal 50-1 (watched person PC 51-1) accepts the registration information, for example, by a registration screen such as screen G2 shown in FIG. 12. Here, the registration information includes the account number of the watched person U1, which is the target account identification information, the account number of the watcher U2, which is the watcher account identification information, and the notification conditions.

FIG. 12 is a diagram showing an example of a registration screen of the watched over person's PC 51-1 in this embodiment. The watched over person's PC 51-1 displays a registration screen such as screen G2 received from the online banking server 10, and accepts registration information through operation by the watched over person U1.

Next, the monitored person terminal 50-1 sends a registration request to the online banking server 10 (step S202). The monitored person terminal 50-1 sends the registration request, including the above-mentioned registration information, to the online banking server 10 via the network NW1.

Then, the online banking server 10 executes the registration process (step S203). The NW communication unit 11 receives the registration request from the watched over person terminal 50-1 via the network NW1. Then, in response to the received registration request, the registration processing unit 132 associates the account number of the watched over person U1, the account number of the watcher U2, and the notification conditions contained in the registration request, and stores them in the notification condition storage unit 122, for example, as shown in FIG. 6.

Next, the online banking server 10 transmits a registration completion notification to the watcher terminal 50-2 (step S204). The registration processing unit 132, for example, obtains an email address corresponding to the account number of the registered watcher U2 from the notification destination information storage unit 123, and transmits the registration completion notification to the email address. The registration processing unit 132 may transmit the registration completion notification by push notification.
This completes the registration process for the watched-over person U1 to register for use of the watching service.

Next, the notification process of the monitoring system 1 according to the present embodiment will be described with reference to FIG. 13 and FIG.
13 is a diagram showing an example of the notification process of the watching system 1 according to this embodiment. Here, an example of the notification process when the watching target U1 performs a deposit/withdrawal transaction using the ATM 23 will be described.

As shown in FIG. 13, when the ATM 23 is operated by the person being watched over U1, the ATM 23 executes a deposit/withdrawal transaction process in accordance with the operation (step S301).
Next, the ATM 23 transmits the deposit/withdrawal transaction information to the accounting system 30 (step S302). The ATM 23 transmits the deposit/withdrawal transaction information, including the account number of the watched over target U1, to the accounting system 30 via the network NW1.

Next, the accounting system 30 executes deposit/withdrawal processing (step S303). The transaction processing unit 34 of the accounting system 30 executes deposit/withdrawal processing based on the deposit/withdrawal transaction information received via the NW communication unit 31. Based on the deposit/withdrawal transaction information, the transaction processing unit 34 stores transaction history such as deposits and withdrawals in the transaction history memory unit 33, for example, as shown in FIG. 3.

Next, the accounting system 30 determines whether it is the distribution time (step S304). The deposit/withdrawal data distribution unit 35 of the accounting system 30 determines whether it is the distribution time, which is the specified time for distributing deposit/withdrawal data. If it is the distribution time (step S304: YES), the deposit/withdrawal data distribution unit 35 advances the process to step S305. If it is not the distribution time (step S304: NO), the deposit/withdrawal data distribution unit 35 returns the process to step S304 and waits for the distribution time to arrive.

In step S305, the deposit/withdrawal data distribution unit 35 extracts deposit/withdrawal data. The deposit/withdrawal data distribution unit 35 extracts deposit/withdrawal data that corresponds to an account number for which the IB contract information in the account information storage unit 32 is "1" from the deposit/withdrawal data stored in the transaction history storage unit 33.

Next, the accounting system 30 transmits the extracted deposit/withdrawal data to the online banking server 10 (step S306). The deposit/withdrawal data distribution unit 35 transmits the extracted deposit/withdrawal data to the online banking server 10 via the NW communication unit 31. Note that the deposit/withdrawal data transmitted here is deposit/withdrawal data corresponding to the accounts of internet banking subscribers, including the monitored person U1.

Next, the online banking server 10 stores the deposit/withdrawal data in the deposit/withdrawal data storage unit 124 (step S307). For example, the notification processing unit 133 of the online banking server 10 stores the deposit/withdrawal data received from the accounting system 30 via the NW communication unit 11 in the deposit/withdrawal data storage unit 124.

Next, the notification processing unit 133 of the online banking server 10 extracts the notification data (step S308). From the deposit/withdrawal data received from the accounting system 30, the notification processing unit 133 extracts the deposit/withdrawal data that matches the account number and notification conditions of the monitored person U1 stored in the notification condition storage unit 122. For example, from the deposit/withdrawal data, the notification processing unit 133 extracts the deposit/withdrawal data that corresponds to the account number of the monitored person U1, and then extracts the deposit/withdrawal data that satisfies the notification conditions. The notification processing unit 133 may extract the target deposit/withdrawal data from the deposit/withdrawal data received from the accounting system 30, or may extract the target deposit/withdrawal data from the deposit/withdrawal data stored in the deposit/withdrawal data storage unit 124.

Then, the online banking server 10 sends a monitoring notification to the watcher PC 51-2 (step S309). The notification processing unit 133 obtains the notification destination of watcher U2 for the extracted deposit/withdrawal data from the notification destination information storage unit 123. That is, the notification processing unit 133 obtains the account number of watcher U2 corresponding to the monitored person U1 of the extracted deposit/withdrawal data from the notification condition storage unit 122, and obtains an email address corresponding to the account number of watcher U2 from the notification destination information storage unit 123. The notification processing unit 133 sends the monitoring notification by email to the obtained email address.

FIG. 14 is a diagram showing an example of a monitoring notification by e-mail in this embodiment.
The notification processing unit 133 sends a monitoring notification in the form of an e-mail with the contents as shown in Fig. 14 to the e-mail address of the watcher U2. Furthermore, the watcher PC 51-2 that receives the e-mail displays the monitoring notification as shown in screen G3 of Fig. 14, so that the watcher U2 can know that a deposit/withdrawal transaction has been made by the person being watched over U1.

The notification processing unit 133 also sends a push notification request to the IB application server 40 to send the monitoring notification by push notification (step S310). The notification processing unit 133 sends a push notification request including, for example, the account number of the watcher U2 and the content of the monitoring notification to the IB application server 40 via the NW communication unit 11.

Next, the IB application server 40 sends the monitoring notification to the watcher smartphone 52-2 by push notification (step S311). The push notification processing unit 44 of the IB application server 40 receives the push notification request from the online banking server 10 via the NW communication unit 41, and obtains a device token corresponding to the account number of the watcher U2 included in the received push notification request from the user information storage unit 42. Based on the obtained device token, the push notification processing unit 44 executes a process of sending the contents of the monitoring notification included in the push notification request by push notification.

The watcher smartphone 52-2 displays the received watch notification push notification. Note that the notification processing unit 133 may notify the user that a deposit/withdrawal transaction that satisfies the notification conditions has occurred, without including detailed deposit/withdrawal information in the watch notification sent via push notification.

Next, the statement inquiry process of the monitoring system 1 according to the present embodiment will be described with reference to Figs.
FIG. 15 is a diagram showing an example of a detail inquiry process of the monitoring system 1 according to this embodiment.

As shown in FIG. 15, first, the watcher PC 51-2 sends a request for an account detail inquiry for the person being watched U1 to the online banking server 10 in response to the operation of the web screen by the watcher U2 (step S401).

Next, the online banking server 10 extracts the statement data of the person being watched over (step S402). When the statement inquiry processing unit 134 of the online banking server 10 receives the statement inquiry request via the NW communication unit 11, it obtains the account number corresponding to the user ID of the internet banking user from the user information storage unit 121 as the account number of the watcher U2. The statement inquiry processing unit 134 obtains the account number and notification conditions of the person being watched over U1 corresponding to the obtained account number of the watcher U2 from the notification condition storage unit 122. The statement inquiry processing unit 134 extracts, from the deposit and withdrawal data stored in the deposit and withdrawal data storage unit 124, the deposit and withdrawal data that satisfies the account number and notification conditions of the person being watched over U1 as the statement data of the person being watched over U1.

Next, the detail inquiry processing unit 134 transmits the extracted detail data of the watched over person U1 to the watcher PC 51-2 (step S403). The detail inquiry processing unit 134 transmits the extracted detail data of the watched over person U1 to the watcher PC 51-2 via the NW communication unit 11.

Next, the watcher PC 51-2 displays the statement data (step S404). The watcher PC 51-2 displays the statement data received from the online banking server 10, for example, as shown in FIG. 16.

FIG. 16 is a diagram showing an example of a details inquiry screen of the watcher PC 51-2 in this embodiment.
16 is an example of a statement inquiry screen of the watcher PC 51-2. The watcher PC 51-2 uses Internet banking via the Web to display a statement inquiry screen such as screen G4.

In addition, the watcher smartphone 52-2 sends a request to inquire about details of the person being watched U1 to the IB app server 40 in response to the operation of the IB app screen by the watcher U2 (step S411).

Next, the IB application server 40 sends a statement inquiry request for the person being watched over U1 to the online banking server 10 (step S412). The IB service processing unit 43 of the IB application server 40 receives the statement inquiry request from the watcher smartphone 52-2 via the NW communication unit 41, and obtains the account number corresponding to the app user ID of the watcher smartphone 52-2 that sent the statement inquiry request from the user information storage unit 42 as the account number of the watcher U2. The IB service processing unit 43 sends the statement inquiry request including the obtained account number of the watcher U2 to the online banking server 10 via the NW communication unit 41.

Next, the online banking server 10 extracts the statement data of the person being watched over (step S413). When the statement inquiry processing unit 134 of the online banking server 10 receives the statement inquiry request via the NW communication unit 11, it obtains the account number and notification conditions of the person being watched over U1 that correspond to the account number of the watcher U2 included in the statement inquiry request from the notification condition memory unit 122. The statement inquiry processing unit 134 extracts, from the deposit and withdrawal data stored in the deposit and withdrawal data memory unit 124, the deposit and withdrawal data that satisfies the account number and notification conditions of the person being watched over U1 as the statement data of the person being watched over U1.

Next, the statement inquiry processing unit 134 transmits the extracted statement data of the monitored person U1 to the IB application server 40 (step S414). The statement inquiry processing unit 134 transmits the extracted statement data of the monitored person U1 to the IB application server 40 via the NW communication unit 11.

Next, the IB application server 40 transmits the statement data of the monitored person U1 to the monitor smartphone 52-2 (step S415). The IB service processing unit 43 of the IB application server 40 receives the statement data of the monitored person U1 from the online banking server 10 via the NW communication unit 41, converts the received statement data of the monitored person U1 for use in the IB application, and transmits it to the monitor smartphone 52-2.

Next, the watcher smartphone 52-2 displays the detailed data (step S416). The watcher smartphone 52-2 displays the received detailed data using the installed IB app.

As described above, the monitoring system 1 according to this embodiment includes a notification condition storage unit 122 and a notification processing unit 133. The notification condition storage unit 122 stores target account identification information (e.g., the account number of the monitored person U1) that identifies the account of the monitored person U1, watcher identification information (e.g., the account number of the watcher U2) that identifies the watcher U2 who watches the monitored person U1, and notification conditions in association with each other. Here, the notification condition is a notification condition for notifying transactions of the account of the monitored person U1, and is a condition set by the monitored person U1. When the deposit/withdrawal data of the account of the monitored person U1 acquired from the accounting system 30 satisfies the notification condition corresponding to the target account identification information stored in the notification condition storage unit 122, the notification processing unit 133 notifies the watcher U2 indicated by the watcher identification information corresponding to the target account identification information.

As a result, the monitoring system 1 according to this embodiment notifies the watcher U2 when there is deposit/withdrawal data for the watched person U1 that satisfies the notification conditions set by the watched person U1, and can therefore appropriately notify the watcher U2 of transaction information (e.g., deposit/withdrawal data) of the watched person U1 while respecting the will of the watched person U1 and protecting the privacy of the watched person U1.

The monitoring system 1 according to this embodiment also includes a notification information storage unit 123 (or a user information storage unit 42) that stores the monitoring person identification information (e.g., the account number of the monitoring person U2) in association with the notification information of the monitoring person U2 (e.g., an email address or a device token). When the deposit/withdrawal data of the account of the monitored person U1 satisfies the notification condition, the notification processing unit 133 sends a monitoring notification to the monitoring person U2 indicating that a transaction that satisfies the notification condition has occurred in the deposit/withdrawal data of the account of the monitored person U1, based on the notification information of the monitoring person U2 corresponding to the monitoring person identification information stored in the notification information storage unit 123 (or the user information storage unit 42).

As a result, the monitoring system 1 according to this embodiment can properly transmit a monitoring notification of the monitored person U1 to the monitor U2.

In this embodiment, the notification destination information includes an email address. The notification processing unit 133 sends a monitoring notification by email to the email address of the watcher U2.
As a result, the monitoring system 1 of this embodiment can appropriately send monitoring notifications for the monitored person U1 via e-mail, and the monitored person U1 can learn the transaction information of the monitored person U1 by the watcher U2 via e-mail.

In the present embodiment, the notification destination information includes push notification destination information (e.g., a device token, etc.) The notification processing unit 133 transmits a monitoring notification by push notification to an Internet banking application for which the watcher U2 is registered as a user, based on the push notification destination information.
As a result, the monitoring system 1 of this embodiment can appropriately send monitoring notifications for the monitored person U1 via push notification, and the monitored person U1 can learn the transaction information of the monitored person U1 by the watcher U2 via e-mail.

In addition, in this embodiment, the watcher identification information is watcher account identification information (e.g., the account number of watcher U2) that identifies the account of watcher U2.
As a result, the monitoring system 1 of this embodiment can reuse existing Internet banking services by using the monitoring person account identification information (e.g., the account number of the monitoring person U2), thereby reducing development labor and development costs.

The monitoring system 1 according to this embodiment also includes an account information storage unit 32 (usage information storage unit) and an online banking processing unit 131. The account information storage unit 32 stores user account identification information (e.g., the user's account number) that identifies the user's account and usage contract information (e.g., IB contract information) that indicates whether or not a contract to use Internet banking has been made, in association with each other. The online banking processing unit 131 provides transaction services through Internet banking. When the usage contract information associated with the user account identification information stored in the account information storage unit 32 indicates that a contract to use Internet banking has been made, the accounting system 30 transmits deposit and withdrawal data for the user's account indicated by the user account identification information (e.g., the user's account number). When the user account identification information of the user's account deposit and withdrawal data output by the accounting system 30 matches the target account identification information stored in the notification condition storage unit 122, the notification processing unit 133 determines that the data is deposit and withdrawal data for the account of the monitored person U1.

As a result, the monitoring system 1 according to this embodiment can utilize the existing Internet banking mechanism for distributing deposit and withdrawal data by using the usage contract information (e.g., IB contract information), thereby reducing development man-hours and development costs.

In addition, in this embodiment, the account information storage unit 32 (usage information storage unit) stores user account identification information, usage contract information (e.g., IB contract information), and usage suspension information (e.g., IB usage suspension information) indicating whether or not to suspend use of the Internet banking transaction service in association with each other. When the usage suspension information associated with the user account identification information stored in the account information storage unit 32 indicates that the Internet banking transaction service is to be suspended, the Internet banking processing unit suspends the provision of the Internet banking transaction service to the user's account indicated by the user account identification information.

As a result, the monitoring system 1 according to this embodiment can selectively suspend the use of Internet banking services while utilizing the mechanisms of Internet banking. Therefore, the monitoring system 1 according to this embodiment can prevent the misuse of Internet banking when the person being watched over U1 is elderly, for example, and does not use Internet banking services. Therefore, the monitoring system 1 according to this embodiment can ensure the safety of the person being watched over U1 while reducing development man-hours and development costs.

In addition, the monitoring system 1 of this embodiment is equipped with a registration processing unit 132 that, in response to a request from the monitored person U1, associates the target account identification information, the monitoring person identification information, and the notification conditions and stores them in the notification condition memory unit 122.
As a result, the monitoring system 1 according to this embodiment makes it easy to register for the monitoring service, for example, through an Internet banking service or an IB app, thereby improving convenience.

The online banking server 10 (server device) according to this embodiment also includes a notification condition storage unit 122 and a notification processing unit 133. The notification condition storage unit 122 stores target account identification information (e.g., the account number of the watched person U1) that identifies the account of the watched person U1, watcher identification information (e.g., the account number of the watcher U2) that identifies the watcher U2 who watches the watched person U1, and notification conditions in association with each other. Here, the notification conditions are notification conditions for notifying transactions in the account of the watched person U1, and are conditions set by the watched person U1. The notification processing unit 133 notifies the watcher U2 indicated by the watcher identification information corresponding to the target account identification information when the deposit/withdrawal data of the account of the watched person U1 acquired from the accounting system 30 satisfies the notification conditions corresponding to the target account identification information stored in the notification condition storage unit 122.

As a result, the online banking server 10 according to this embodiment achieves the same effect as the monitoring system 1 described above, and can appropriately notify transaction information (e.g., deposit and withdrawal data) of the monitored person U1 while respecting the personal wishes of the monitored person U1 and protecting the privacy of the monitored person U1.

The monitoring method according to this embodiment also includes a registration step and a notification processing step. In the registration step, the registration processing unit 132 associates target account identification information that identifies the account of the person being watched over U1, watcher identification information that identifies the watcher U2 watching over the person being watched over U1, and notification conditions that are set by the person being watched over U1 and that notify transactions in the account of the person being watched over U1, and stores them in the notification condition storage unit 122. In the notification processing step, when the deposit/withdrawal data of the account of the person being watched over U1 acquired from the accounting system 30 satisfies the notification conditions corresponding to the target account identification information stored in the notification condition storage unit 122, the notification processing unit 133 notifies the watcher U2 indicated by the watcher identification information corresponding to the target account identification information.

As a result, the monitoring method according to this embodiment has the same effect as the monitoring system 1 and online banking server 10 described above, and can appropriately notify transaction information (e.g., deposit and withdrawal data) of the monitored person U1 while respecting the personal wishes of the monitored person U1 and protecting the privacy of the monitored person U1.

Second Embodiment
Next, a monitoring system 1a according to a second embodiment will be described with reference to the drawings.
FIG. 17 is a block diagram showing an example of a monitoring system 1a according to the second embodiment.

As shown in FIG. 17, the monitoring system 1a includes an online banking server 10a, an IB store terminal device 21, an accounting terminal device 22, an ATM 23, an accounting system 30a, an IB application server 40, a user PC 51, and a user smartphone 52. The online banking server 10a, the IB store terminal device 21, the accounting terminal device 22, the ATM 23, the accounting system 30a, the IB application server 40, the user PC (user personal computer) 51, and the user smartphone 52 can be connected via a network NW1.

In this figure, the same components as those shown in FIG. 1 are given the same reference numerals, and the description thereof will be omitted here.
In this embodiment, a modified example will be described in which a request for approval of a transaction is sent to the watcher U2 before the transaction of the watched-over person U1 is made.

The accounting system 30a is a core system in a financial institution such as a bank, and is a system that mainly handles deposits and withdrawals, settlement of funds, and account management. The accounting system 30a includes, for example, a network communication unit 31, an account information storage unit 32, a transaction history storage unit 33, a transaction processing unit 34a, and a deposit and withdrawal data distribution unit 35.

When processing various transactions at the counter of the bank branch ST or at the ATM 23, the transaction processing unit 34a sends a transaction approval request to the online banking server 10a if the transaction is for an account that has an internet banking contract (if the "IB contract information" in the account information storage unit 32 is "1"). If the transaction processing unit 34a receives an approval notice from the online banking server 10a, it processes the various transactions. In addition, if the transaction processing unit 34a receives a rejection notice from the online banking server 10a, it controls not to process the various transactions.
The process of storing the deposit and withdrawal transaction history of the transaction processing unit 34a in the transaction history storage unit 33 is similar to that of the transaction processing unit 34 in the first embodiment.

The online banking server 10a (an example of a server device) is a server device that provides internet banking services and is capable of carrying out various transactions via the internet banking web, for example. The online banking server 10a includes, for example, a network communication unit 11, a server storage unit 12a, and a server control unit 13a.

The server storage unit 12a stores various information used by the online banking server 10a. The server storage unit 12a includes, for example, a user information storage unit 121, a notification condition storage unit 122a, a notification destination information storage unit 123, and a deposit/withdrawal data storage unit 124a.

The notification condition storage unit 122a stores target account identification information, watcher identification information, notification conditions, and notification information indicating the type of notification in association with each other. Here, with reference to FIG. 18, an example of data in the notification condition storage unit 122a in this embodiment will be described.

FIG. 18 is a diagram showing an example of data in the notification condition storage unit 122a in this embodiment.
18, the notification condition storage unit 122a stores the "account number of the person being watched over," the "account number of the person watching over," the "notification condition," and the "notification information" in association with each other. Here, the "notification information" is information indicating the type of notification, such as an "approval request" or a "watching notification."

For example, the example shown in Figure 18 shows that the "account number of the person being watched" of "XXXX-201-1234567" corresponds to the "account number of the person being watched" of "XXXX-202-78901234". In other words, this shows that the watcher U2 of the person being watched U1, who has an account number of "XXXX-201-1234567", is a user who has an account number of "XXXX-202-78901234".

Also, when the "notification condition" is "a withdrawal transaction of 100,000 yen or more," the "notification information" is "approval request." In this case, it is indicated that a transaction approval request notification needs to be sent to the watcher U2.
Also, when the "notification condition" is "a withdrawal transaction of less than 100,000 yen", the "notification information" is a "monitoring notification". In this case, it indicates that a monitoring notification is to be sent to the watcher U2.
In this way, the notification conditions include a condition that approval is required for transactions in the account of the monitored person U1.

Returning to the explanation of FIG. 17, the server control unit 13a is, for example, a processor including a CPU and the like, and controls the online banking server 10a in an overall manner. The server control unit 13a includes, for example, an online banking processing unit 131a, a registration processing unit 132, a notification processing unit 133a, and a statement inquiry processing unit 134a.

When making a transaction with the account of the person being watched over U1, if the condition that approval is required for the transaction with the account of the person being watched over U1 associated with the target account identification information stored in the notification condition memory unit 122a is met, the notification processing unit 133a sends an approval notification to the watcher U2 requesting approval of the transaction with the account of the person being watched over U1 before making the transaction with the account of the person being watched over U1. In response to a transaction approval request from the accounting system 30a, the notification processing unit 133a refers to the notification condition memory unit 122a, and if the notification condition that the "notification information" is an "approval request" is met, the notification processing unit 133a sends the approval notification to the watcher U2 by email and push notification, similar to the monitoring notification.

Furthermore, when the notification processing unit 133a receives approval of the transaction for the account of the watched over person U1 from the watcher U2, the notification processing unit 133a causes the accounting system 30a to complete the transaction for the account of the watched over person U1. In other words, the notification processing unit 133a sends an approval notification to the accounting system 30a.
In addition, when the notification processing unit 133a receives a refusal to make a transaction on the account of the watched over person U1 from the watcher U2, it sends a refusal notification to the accounting system 30a.

In addition, the notification processing unit 133a does not send the approval notification to the watcher U2, but sends the approval notification to the accounting system 30a, unless the "notification information" satisfies the notification condition of "approval request."

The statement inquiry processing unit 134a executes the same processing as the statement inquiry processing unit 134 of the first embodiment described above, and also executes an addition process for adding memo information to the statement inquiry data by the watcher U2. For example, as shown in Fig. 19(a), the statement inquiry processing unit 134a enables memo information to be added to each item of deposit/withdrawal data on the statement inquiry screen (screen G5).
The example shown in FIG. 19 is an example of a case where a statement inquiry is displayed on the watcher smartphone 52-2.

The statement inquiry processing unit 134a also displays a memo information addition screen (screen G6) as shown in FIG. 19(b), for example, to accept input of memo information. The statement inquiry processing unit 134a stores the accepted memo information in the deposit/withdrawal data storage unit 124a in association with the corresponding deposit/withdrawal data.

In addition, when the person being watched over U1 inquires about his/her own statement, the online banking processing unit 131a according to this embodiment displays the status of each deposit/withdrawal data (e.g., read, unread, or warning by the watcher U2) as shown in FIG. 20, and also allows the person being watched over U1 to refer to memo information added by the watcher U2.

FIG. 20 is a diagram showing an example of a statement inquiry screen of the user smartphone 52 by the watched over person U1 in this embodiment.
The online banking processing unit 131a displays a statement inquiry screen as shown in screen G7 of Fig. 20, and by selecting the mark M1 of the memo information, for example, displays the contents of the memo information as shown in Fig. 19(b) described above. In this way, by sharing the memo information between the watched-over person U1 and the watcher U2, the watching system 1a according to this embodiment can lead to smooth action (response) by the watcher U2 in the watching service.

Next, the transaction approval process of the monitoring system 1a according to this embodiment will be described with reference to FIG.
21 is a diagram showing an example of a transaction approval process of the monitoring system 1a according to the present embodiment. Note that, here, an example of a case where a transaction that does not involve a withdrawal or deposit of cash, such as a transfer transaction, is performed will be described.

As shown in FIG. 21, when the ATM 23 is operated by the person being watched over U1, the ATM 23 executes a deposit/withdrawal transaction process according to the operation (step S501). Here, it is assumed that the ATM 23 accepts a transfer transaction.

Next, the ATM 23 transmits the deposit/withdrawal transaction information to the accounting system 30a (step S502). The ATM 23 transmits the deposit/withdrawal transaction information, including the account number of the monitored person U1, to the accounting system 30a via the network NW1.

Next, before executing the deposit/withdrawal transaction, the accounting system 30a sends a transaction approval request to the online banking server 10a (step S503). The transaction processing unit 34a of the accounting system 30a sends a transaction approval request to the online banking server 10a if the transaction is for an account that has an internet banking contract (if the transaction is for an account whose "IB contract information" in the account information storage unit 32 is "1").

Next, the online banking server 10a determines whether an approval request is required (step S504). In response to the transaction approval request from the accounting system 30a, the notification processing unit 133a of the online banking server 10a refers to the notification condition storage unit 122a and determines whether an approval request is required based on whether the notification condition that the "notification information" is an "approval request" is met. If an approval request is required (step S504: YES), the notification processing unit 133a proceeds to step S505. If an approval request is not required (step S504: NO), the notification processing unit 133a proceeds to step S509 and sends an approval notification to the accounting system 30a.

In step S505, the notification processing unit 133a of the online banking server 10a sends an approval request notification to the watcher PC 51-2. The notification processing unit 133a obtains the notification destination (email address) of the watcher U2 that corresponds to the account number of the person being watched over U1 from the notification destination information storage unit 123. The notification processing unit 133a sends the approval request notification by email to the obtained email address.

The notification processing unit 133a also transmits a push notification request to the IB application server 40 to transmit the approval request notification by push notification (step S506). The notification processing unit 133a transmits a push notification request including, for example, the account number of the watcher U2 and the contents of the approval request notification to the IB application server 40 via the NW communication unit 11.
Next, the IB application server 40 sends a monitoring notification to the watcher smartphone 52-2 by push notification (step S507).

Next, the watcher PC 51-2 sends an approval (rejection) notice to the online banking server 10a (step S508). Note that the watcher smartphone 52-2 may also send an approval (rejection) notice to the online banking server 10a.

Next, the notification processing unit 133a of the online banking server 10a sends an approval notice (rejection notice) to the accounting system 30a (step S509).
The transaction processing unit 34a of the accounting system 30a determines whether the transaction is approved (step S510). The transaction processing unit 34a determines whether the transaction is approved based on whether an approval notice has been received from the online banking server 10a. If the transaction processing unit 34a receives an approval notice (step S510: YES), the transaction processing unit 34a proceeds to step S511. If the transaction processing unit 34a receives a rejection notice (step S510: NO), the transaction processing unit 34a does not execute the transaction processing.
In step S511, the accounting system 30a executes deposit/withdrawal processing.

In addition, when transaction processing is performed at the counter of a bank branch ST, the result of transaction approval may be transmitted from the accounting system 30a to, for example, an accounting system terminal device 22, and the transaction processing may be performed according to the result of the transaction approval.
Moreover, other processes of the monitoring system 1a according to this embodiment are similar to those of the first embodiment described above, and therefore will not be described here.

As described above, the monitoring system 1a according to this embodiment includes the notification condition memory unit 122a and the notification processing unit 133a described above. As a result, like the first embodiment, the monitoring system 1a according to this embodiment can appropriately notify the transaction information (e.g., deposit and withdrawal data) of the monitored person U1 while respecting the will of the monitored person U1 and protecting the privacy of the monitored person U1.

In addition, in this embodiment, the notification conditions include a condition that approval is required for a transaction in the account of the person being watched over U1. When a condition that approval is required for a transaction in the account of the person being watched over U1 associated with the target account identification information stored in the notification condition storage unit 122a is met when a transaction in the account of the person being watched over U1 is performed, the notification processing unit 133a sends an approval notification to the watcher U2 requesting approval of the transaction in the account of the person being watched over U1 before performing the transaction in the account of the person being watched over U1. Furthermore, when the notification processing unit 133a receives approval of the transaction in the account of the person being watched over U1 from the watcher U2, it causes the accounting system 30a to complete the transaction in the account of the person being watched over U1.

As a result, the monitoring system 1a according to this embodiment requires the approval of the watcher U2 when processing transactions for the account of the person being watched over U1 depending on the conditions, and can therefore prevent the person being watched over U1 from falling victim to special fraud or the like in advance.

[Third embodiment]
Next, a monitoring system 1b according to a third embodiment will be described with reference to the drawings.
In this embodiment, a modified example will be described in which the configuration of the online banking server 10 described above is included in an IB application server 40a, and various processes of the online banking server 10 are executed by the IB application server 40a.

FIG. 22 is a block diagram showing an example of a monitoring system 1b according to the third embodiment.
As shown in FIG. 22, the monitoring system 1b includes an accounting terminal device 22, an ATM 23, an IB application store terminal device 24, an accounting system 30, an IB application server 40a, a user PC 51, and a user smartphone 52.

In addition, the accounting terminal device 22, the ATM 23, the IB application store terminal device 24, the accounting system 30, the IB application server 40a, the user PC 51, and the user smartphone 52 can be connected via the network NW1.
In this figure, the same components as those shown in FIG. 1 are given the same reference numerals, and the description thereof will be omitted here.

The IB app store terminal device 24 is, for example, a terminal device operated by a bank employee at the bank branch ST, and is a terminal device for performing various settings and operations related to Internet banking services. For example, when performing registration processing for the monitoring system 1b at the counter of the bank branch ST, the IB app store terminal device 24 accepts registration information as input information and transmits it to the IB app server 40a via the network NW1.

The IB app server 40a is a server device that provides internet banking services using the IB app on the user's smartphone 52. The IB app server 40a includes the functions of the internet banking server 10 described above, and includes, for example, a network communication unit 41, a server storage unit 12b, and a server control unit 13b.

The server storage unit 12b stores various information used by the IB application server 40a. The server storage unit 12b includes, for example, a user information storage unit 121a, a notification condition storage unit 122, a notification destination information storage unit 123, and a deposit/withdrawal data storage unit 124.

The user information storage unit 121a is a storage unit that integrates the user information storage unit 121 of the first embodiment and the user information storage unit 42. The user information storage unit 121a stores, for example, the information shown in Figures 4 and 5.

The server control unit 13b is, for example, a processor including a CPU and the like, and controls the IB application server 40a in an overall manner. The server control unit 13b includes, for example, an online banking processing unit 131b, a registration processing unit 132, a notification processing unit 133b, and a statement inquiry processing unit 134.

The online banking processing unit 131b is an integration of the functions of the online banking processing unit 131 of the first embodiment and the IB service processing unit 43.
The basic functions of the notification processing unit 133b are similar to those of the notification processing unit 133 in the first embodiment, but the notification processing unit 133b further has the functions of a push notification processing unit 44 and is capable of sending a monitoring notification to the watcher smartphone 52-2 via push notification.

Next, the operation of the monitoring system 1b according to this embodiment will be described with reference to the drawings.
23 is a diagram showing an example of a registration process of the watching system 1b according to the present embodiment. Here, the registration process in which the watching target U1 registers the use of the watching service provided by the watching system 1b through a window of the bank store ST will be described.

In FIG. 23, the IB application store terminal device 24 accepts registration information (step S601).
Next, the IB application store terminal device 24 transmits a registration request to the IB application server 40a (step S602). The IB application store terminal device 24 transmits the registration request including the above-mentioned registration information to the IB application server 40a via the network NW1.

This embodiment is similar to the first embodiment shown in Figure 9 described above, except that the IB store terminal device 21 is replaced with an IB app store terminal device 24, and the online banking server 10 is replaced with an IB app server 40a.
The subsequent processes from step S603 to step S608 are similar to the processes from step S103 to step S108 shown in FIG. 9 described above, and therefore description thereof will be omitted here.

Next, the registration process via Internet banking according to this embodiment will be described with reference to FIG.
24 is a diagram showing another example of the registration process of the watching system 1b according to the present embodiment. Here, the registration process in which the watching target U1 himself/herself registers the use of the watching service provided by the watching system 1b through internet banking will be described.

This embodiment is similar to the first embodiment shown in FIG. 11 above, except that the online banking server 10 is replaced with an IB application server 40a. That is, the processes from step S611 to step S614 shown in FIG. 24 are similar to the processes from step S201 to step S204 shown in FIG. 11 above, and therefore will not be described here.

Next, the notification process of the watching system 1b according to this embodiment will be described with reference to FIG.
25 is a diagram showing an example of a notification process of the watching system 1b according to this embodiment. Here, an example of the notification process when the watching target U1 performs a deposit/withdrawal transaction using the ATM 23 will be described.

In FIG. 25, the processes from step S621 to step S625 are similar to the processes from step S301 to step S305 shown in FIG. 11 described above, so their description will be omitted here.

Next, the accounting system 30 transmits the extracted deposit/withdrawal data to the IB application server 40a (step S626). The deposit/withdrawal data distribution unit 35 transmits the extracted deposit/withdrawal data to the IB application server 40a via the NW communication unit 31, instead of the internet banking server 10. Note that the deposit/withdrawal data transmitted here is deposit/withdrawal data corresponding to the accounts of internet banking subscribers, including the monitored person U1.

Next, the IB application server 40a stores the deposit/withdrawal data in the deposit/withdrawal data storage unit 124 (step S627). For example, the notification processing unit 133b of the IB application server 40a stores the deposit/withdrawal data received from the accounting system 30 via the NW communication unit 41 in the deposit/withdrawal data storage unit 124.

Next, the notification processing unit 133b of the IB application server 40a extracts the notification data (step S628). From the deposit and withdrawal data received from the accounting system 30, the notification processing unit 133b extracts the deposit and withdrawal data that matches the account number and notification conditions of the monitored person U1 stored in the notification condition storage unit 122.

Next, the notification processing unit 133b of the IB application server 40a sends the monitoring notification to the watcher smartphone 52-2 by push notification (step S629). The notification processing unit 133b acquires, for example, a device token corresponding to the account number of the watcher U2 from the user information storage unit 121a. Based on the acquired device token, the notification processing unit 133b executes a process of sending the monitoring notification by push notification.

Next, with reference to FIG. 26, the statement inquiry process of the monitoring system 1b according to this embodiment will be described.
FIG. 26 is a diagram showing an example of a detail inquiry process of the monitoring system 1b according to this embodiment.

As shown in FIG. 26, first, the watcher smartphone 52-2 sends a request for detailed information about the person being watched U1 to the IB app server 40a in response to the operation of the IB app screen by the watcher U2 (step S631).

Next, the IB application server 40a extracts the statement data of the person being watched over (step S632). When the statement inquiry processing unit 134 of the IB application server 40a receives the statement inquiry request via the NW communication unit 41, it obtains the account number and notification conditions of the person being watched over U1 that correspond to the account number of the watcher U2 included in the statement inquiry request from the notification condition memory unit 122. The statement inquiry processing unit 134 extracts, from the deposit and withdrawal data stored in the deposit and withdrawal data memory unit 124, the deposit and withdrawal data that satisfies the account number and notification conditions of the person being watched over U1 as the statement data of the person being watched over U1.

Next, the statement inquiry processing unit 134 transmits the extracted statement data of the watched over person U1 to the watcher smartphone 52-2 (step S633). The statement inquiry processing unit 134 converts the extracted statement data of the watched over person U1 for use in the IB application and transmits it to the watcher smartphone 52-2 via the NW communication unit 41.

Next, the watcher smartphone 52-2 displays the detailed data (step S634). The watcher smartphone 52-2 displays the received detailed data using the installed IB app.

As described above, in the monitoring system 1b according to this embodiment, the IB application server 40a includes the functions of the online banking server 10 in the first embodiment.
As a result, the monitoring system 1b of this embodiment achieves the same effect as the first embodiment, and can appropriately notify transaction information (e.g., deposit and withdrawal data) of the monitored person U1 while respecting the personal wishes of the monitored person U1 and protecting the privacy of the monitored person U1.

[Fourth embodiment]
Next, a monitoring system 1c according to a fourth embodiment will be described with reference to the drawings.
In this embodiment, a modified example in which an API (Application Programming Interface) management infrastructure system 60 is further added to the configuration of the third embodiment described above will be described.

FIG. 27 is a block diagram showing an example of a monitoring system 1c according to the fourth embodiment.
As shown in FIG. 27, the monitoring system 1c includes an accounting system terminal device 22, an ATM 23, an IB application store terminal device 24, an accounting system 30b, an IB application server 40b, a user PC 51, a user smartphone 52, and an API management infrastructure system 60.

In addition, the accounting system terminal device 22, ATM 23, IB application store terminal device 24, accounting system 30b, IB application server 40b, user PC 51, user smartphone 52, and API management infrastructure system 60 can be connected via network NW1.
In this figure, the same components as those shown in FIG. 1 or FIG. 22 are given the same reference numerals, and the description thereof will be omitted here.

The accounting system 30b is a core system in a financial institution such as a bank, and is a system that mainly handles deposits and withdrawals, settlement of funds, and account management. The basic functions of the accounting system 30b are similar to those of the accounting system 30 in the first embodiment, but differ from the accounting system 30 in that it supports authentication processing with the API management infrastructure system 60 and distributes deposit and withdrawal data in response to requests from the IB application server 40b.

During the registration process of the monitoring system 1c, the accounting system 30b checks (inspects) the consistency between the authentication information entered by the monitored person U1 via the API management infrastructure system 60 and the information held by the accounting system 30b.
The accounting system 30b includes, for example, a network communication unit 31, an account information storage unit 32, a transaction history storage unit 33, a transaction processing unit 34, and a deposit/withdrawal data distribution unit 35a.

In response to a request for deposit/withdrawal data distribution from the API management infrastructure system 60 via the NW communication unit 31, the deposit/withdrawal data distribution unit 35a extracts the user's deposit/withdrawal data from the transaction history stored in the transaction history memory unit 33 and distributes it to the API management infrastructure system 60.

The API management infrastructure system 60 executes authentication processing by the accounting system 30b, and if the authentication result is satisfactory, issues a token and executes authorization processing to authorize the IB application server 40b, and authentication processing using the issued token. The API management infrastructure system 60 includes a network communication unit 61, an authorization management unit 62, and an authentication management unit 63.

The NW communication unit 61 connects to the network NW1 and performs various communications via the network NW1. For example, the NW communication unit 61 mainly connects to the accounting system 30b, the IB application server 40b, and the user smartphone 52 via the network NW1 and performs various communications.

When the authorization management unit 62 receives a transfer (redirect) of a registration request from the IB application server 40b, it sends an authentication information request to the monitored person terminal 50-1 (e.g., the monitored person smartphone 52-1) that sent the registration request. In addition, when the authorization management unit 62 receives authentication information linkage including authentication information from the monitored person terminal 50-1 (e.g., the monitored person smartphone 52-1), it transfers the authentication information linkage to the accounting system 30b. Note that authentication information is, for example, internet banking login information (user ID and password), account number and PIN, account number and date of birth, etc.

The authorization management unit 62 also receives an authentication result from the accounting system 30b, and issues a token if the authentication result is acceptable. Here, the token is a random alphanumeric character string, and includes an access token and a refresh token. The authorization management unit 62 sends an authorization notification including the issued tokens (access token and refresh token) to the IB application server 40b.

When the authentication management unit 63 receives a deposit/withdrawal data delivery request and an access token from the IB application server 40b, it performs authentication processing using the access token (verifies consistency using the access token), and if the authentication result is acceptable, it transfers the deposit/withdrawal data delivery request to the accounting system 30b.
In addition, when the authentication management unit 63 receives deposit/withdrawal data from the accounting system 30b, it transfers the received deposit/withdrawal data to the IB application server 40b.

The IB app server 40b is a server device that provides internet banking services using an IB app on the user smartphone 52. The IB app server 40b differs from the above-mentioned IB app server 40a in that it uses an API management infrastructure system 60. The IB app server 40b includes, for example, a network communication unit 41, a server storage unit 12b, and a server control unit 13c.

The server control unit 13c is, for example, a processor including a CPU and the like, and controls the IB application server 40b in an overall manner. The server control unit 13c includes, for example, an online banking processing unit 131b, a registration processing unit 132a, a notification processing unit 133c, and a statement inquiry processing unit 134a.

The basic functions of the registration processing unit 132a are similar to those of the registration processing unit 132 in the first embodiment, but the registration processing unit 132a adds a process of acquiring a token from the API management infrastructure system 60. The registration processing unit 132a transfers the received registration request to the API management infrastructure system 60 and executes a process of receiving tokens (access token and refresh token). The registration processing unit 132a stores the received tokens (access token and refresh token) in the server storage unit 12b. The refresh token is used to reacquire the access token when the access token expires.

The basic functions of the notification processing unit 133c are similar to those of the notification processing unit 133b of the third embodiment, but the process of receiving deposit/withdrawal data is different in the notification processing unit 133c. The notification processing unit 133c periodically (e.g., every 30 minutes) transmits a deposit/withdrawal data distribution request and an access token to the API management infrastructure system 60 at a specified time for transmitting a monitoring notification. In response to the deposit/withdrawal data distribution request, the notification processing unit 133c receives deposit/withdrawal data from the accounting system 30b via the API management infrastructure system 60. The monitoring notification process after receiving the deposit/withdrawal data is similar to that of the notification processing unit 133b.

The basic functions of the statement inquiry processing unit 134a are similar to those of the statement inquiry processing unit 134 in the first embodiment, but differ in that the statement inquiry processing unit 134a requests the delivery of deposit and withdrawal data each time in response to a statement inquiry request. In response to a statement inquiry request, the statement inquiry processing unit 134a sends a deposit and withdrawal data delivery request and an access token to the API management infrastructure system 60, and receives deposit and withdrawal data from the accounting system 30b via the API management infrastructure system 60. Subsequent statement inquiry processing is similar to that of the statement inquiry processing unit 134.

Next, the operation of the monitoring system 1c according to this embodiment will be described with reference to the drawings.
28 is a diagram showing an example of a registration process of the watching system 1c according to the present embodiment. Here, a registration process in which the watching target U1 himself/herself registers the use of the watching service provided by the watching system 1c through internet banking will be described.

In FIG. 28, the processing from step S701 to step S703 is similar to the processing from step S611 to step S613 shown in FIG. 24 described above, and therefore the description thereof is omitted.

In step S704, the registration processing unit 132a of the IB application server 40b transfers the received registration request to the API management infrastructure system 60. The registration processing unit 132a transmits the registration request including the request source information to the API management infrastructure system 60 via the NW communication unit 41.

Next, the API management infrastructure system 60 transmits an authentication information request to the monitored person terminal 50-1 in response to the received registration request (step S705). The authorization management unit 62 of the API management infrastructure system 60 transmits the authentication information request via the NW communication unit 61 to the monitored person terminal 50-1 (e.g., the monitored person smartphone 52-1) that sent the registration request.

Next, the monitored person terminal 50-1 (e.g., the monitored person smartphone 52-1) displays an authentication information request screen and accepts input of authentication information (step S706). Here, authentication information is, for example, internet banking login information (user ID and password), account number and PIN number, account number and date of birth, etc.

Next, the monitored person terminal 50-1 (e.g., monitored person smartphone 52-1) transmits the received authentication information to the API management infrastructure system 60 as authentication information linkage (step S707).

Next, the authorization management unit 62 of the API management infrastructure system 60 transfers the authentication information linkage to the accounting system 30b (step S708). The authorization management unit 62 transmits the authentication information linkage received via the NW communication unit 61 to the accounting system 30b via the NW communication unit 61.

Next, accounting system 30b checks (inspects) the consistency of the authentication information (step S709). For example, accounting system 30b checks (inspects) the consistency between the authentication information and information held by accounting system 30b (for example, information in account information storage unit 32).

Next, the accounting system 30b sends the results of the consistency check to the API management infrastructure system 60 as a result link (step S710).
Next, the authorization management unit 62 issues tokens (step S711). If the accounting system 30b checks the consistency of the authentication information and finds no problem, the authorization management unit 62 issues tokens (access token and refresh token).

Next, the authorization management unit 62 sends an authorization notification to the IB application server 40b (step S712). The authorization management unit 62 sends the authorization notification including the tokens (access token and refresh token) to the IB application server 40b via the NW communication unit 61.

Next, the registration processing unit 132a of the IB application server 40b saves the received tokens (access token and refresh token) (step S713). That is, the registration processing unit 132a stores the tokens (access token and refresh token) in the server storage unit 12b.

Next, the registration processing unit 132a transmits a registration completion notification to the watching over person terminal 50-1 (for example, the watching over person smartphone 52-1) (step S714).
The registration processing unit 132a also transmits a registration completion notification to the watcher terminal 50-2 (step S715).
This completes the registration process for the watched-over person U1 to register for use of the watching service.

Next, the notification process of the monitoring system 1c according to this embodiment will be described with reference to FIG.
29 is a diagram showing an example of a notification process of the watching system 1c according to this embodiment. Here, an example of the notification process when the watching target U1 performs a deposit/withdrawal transaction using the ATM 23 will be described.

In FIG. 29, the processes from step S721 to step S723 are similar to the processes from step S621 to step S623 shown in FIG. 25 described above, so their description will be omitted here.

Next, the notification processing unit 133c of the IB application server 40b determines whether it is the time to obtain deposit/withdrawal data (step S724). If it is the time to obtain deposit/withdrawal data (step S724: YES), the notification processing unit 133c advances the process to step S725. If it is not the time to obtain deposit/withdrawal data (step S724: NO), the notification processing unit 133c returns the process to step S724.

In step S725, the notification processing unit 133c sends a deposit/withdrawal data distribution request to the API management infrastructure system 60. Here, the notification processing unit 133c sends an access token together with the deposit/withdrawal data distribution request to the API management infrastructure system 60.

Next, the authentication management unit 63 of the API management infrastructure system 60 checks the consistency of the token (step S726). The authentication management unit 63 checks the consistency of the token by checking whether the access token received via the NW communication unit 61 matches the access token issued to the IB application server 40b.

Next, the authentication management unit 63 transfers the deposit/withdrawal data distribution request to the accounting system 30b (step S727). If the token consistency is confirmed, the authentication management unit 63 sends the deposit/withdrawal data distribution request to the accounting system 30b via the NW communication unit 61.

Next, the deposit/withdrawal data distribution unit 35a of the accounting system 30b extracts the deposit/withdrawal data (step S728). In response to the deposit/withdrawal data distribution request, the deposit/withdrawal data distribution unit 35a extracts the deposit/withdrawal data corresponding to the account number for which the IB contract information in the account information storage unit 32 is "1" from the deposit/withdrawal data stored in the transaction history storage unit 33.

Next, the deposit/withdrawal data distribution unit 35a transmits the extracted deposit/withdrawal data to the API management infrastructure system 60 (step S729).
Next, the API management infrastructure system 60 transmits the deposit/withdrawal data received from the accounting system 30b to the IB application server 40a (step S730).

Next, the notification processing unit 133c of the IB application server 40a determines whether there is new deposit/withdrawal data (step S731). The notification processing unit 133c determines whether there is newly added (updated) deposit/withdrawal data to the received deposit/withdrawal data. If there is new deposit/withdrawal data (step S731: YES), the notification processing unit 133c advances the process to step S732. If there is no new deposit/withdrawal data (step S731: NO), the notification processing unit 133c returns the process to step S724.

The processing from step S732 to step S734 is similar to the processing from step S627 to step S628 shown in FIG. 25 described above, so a description thereof will be omitted here.

Next, with reference to FIG. 30, the details inquiry process of the monitoring system 1c according to this embodiment will be described.
FIG. 30 is a diagram showing an example of a detail inquiry process of the monitoring system 1c according to this embodiment.

As shown in FIG. 30, first, the watcher smartphone 52-2 sends a request for detailed information about the person being watched U1 to the IB app server 40b in response to the operation of the IB app screen by the watcher U2 (step S741).

Next, the statement inquiry processing unit 134a of the IB application server 40b sends a deposit/withdrawal data distribution request to the API management infrastructure system 60 (step S742). Here, the notification processing unit 133c sends the access token together with the deposit/withdrawal data distribution request to the API management infrastructure system 60.

The subsequent processing from step S743 to step S748 is similar to the processing from step S726 to step S730 shown in FIG. 29 described above, and therefore will not be described here. The statement inquiry processing unit 134a of the IB application server 40b stores the received deposit/withdrawal data in the deposit/withdrawal data storage unit 124.

Furthermore, the processing from step S749 to step S751 is similar to the processing from step S632 to step S634 shown in FIG. 26 described above, and therefore the description thereof will be omitted here.

As described above, in the monitoring system 1c of this embodiment, similar to the third embodiment described above, the IB application server 40b includes the functions of the online banking server 10, and further includes an API management infrastructure system 60 that performs authentication using tokens.
As a result, the monitoring system 1c according to this embodiment has the same effect as the third embodiment, and can appropriately notify the transaction information (e.g., deposit and withdrawal data) of the monitored person U1 while respecting the will of the monitored person U1 and protecting the privacy of the monitored person U1. In addition, the monitoring system 1c according to this embodiment can improve security by performing authentication using a token.

The present invention is not limited to the above-described embodiments, and can be modified without departing from the spirit of the present invention.
For example, in each of the above embodiments, the notification conditions include the type of deposit/withdrawal transaction (e.g., deposit, withdrawal, transfer, etc.) and transaction amount information (e.g., transaction amount, total transaction amount for a specified period, etc.), but are not limited to this. The notification conditions may also include, for example, the time of transaction and the place of transaction (bank branch or ATM number).

In the above embodiment, the online banking server 10 (10a) is described as being a single server device, but this is not limited to this and the server may be configured with multiple server devices. In other words, a portion of the server memory unit 12 (12a) and the server control unit 13 (13a) may be provided outside the online banking server 10 (10a).

In addition, in the above embodiment, an example was described in which the notification condition storage unit 122 (122a) and the notification destination information storage unit 123 are configured as separate storage units, but the notification condition storage unit 122 (122a) and the notification destination information storage unit 123 may be configured as a single storage unit.

In addition, in each of the above embodiments, an example has been described in which one watcher U2 is associated with one watched person U1, but this is not limited to this. For example, multiple watchers U2 may be associated with one watched person U1, or one watcher U2 may be associated with multiple watched people U1. Also, the watched person U1 and the watcher U2 may be mutually set, such as between a married couple.

In the above embodiment, an example was described in which the user information storage unit 121 of the online banking server 10 (10a) stores the same "IB suspension information" as the account information storage unit 32 of the accounting system 30 (30a), but this is not limited to this. For example, the online banking server 10 (10a) may obtain the "IB suspension information" from the accounting system 30 (30a) each time.

In addition, in each of the above embodiments, an example has been described in which the monitored person U1 and the watcher U2 are identified by their account numbers, but the monitored person U1 and the watcher U2 may also be identified by other identification information such as their names or user IDs.
In addition, in each of the above embodiments, an example has been described in which the "account number of the person being monitored" and the "account number of the monitor" stored in the notification condition memory unit 122 (122a) are account numbers of the same financial institution, but this is not limited to this and may also be an account number of another financial institution.

In the above embodiment, an example was described in which the accounting system 30 (30a) distributes deposit and withdrawal data to the online banking server 10 (10a) twice a day, at midnight and noon, but this is not limited to the above. For example, deposit and withdrawal data may be distributed to the online banking server 10 (10a) once a day, or three or more times a day. Also, the online banking server 10 (10a) may obtain deposit and withdrawal data from the accounting system 30 (30a) each time it performs notification processing.

In the above second embodiment, the statement inquiry processing unit 134a adds memo information to the statement inquiry data and displays it, but the present invention is not limited to this, and other information may be added and displayed. For example, the statement inquiry processing unit 134a may display the location information of the bank branch ST or ATM 23 where the transaction was performed, the transaction time, etc., based on the branch number and ATM number shown in Fig. 3. In this case, the monitoring system 1a can easily determine that the monitored person U1 is performing a transaction different from usual, and can easily grasp an abnormality in the monitored person U1.
In the second embodiment described above, the added memo information may be collected and analyzed, and used for future functional expansion of the monitoring service.

In addition, the above third and fourth embodiments have been described as examples applied to the first embodiment, but they may also be applied to the second embodiment.

Each of the components of the above-mentioned monitoring system 1 (1a to 1c) has a computer system inside. A program for realizing the functions of each of the components of the above-mentioned monitoring system 1 (1a to 1c) may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read into a computer system and executed to perform processing in each of the components of the above-mentioned monitoring system 1 (1a to 1c). Here, "reading a program recorded on a recording medium into a computer system and executing it" includes installing the program into the computer system. The "computer system" here includes hardware such as an OS and peripheral devices.
Furthermore, a "computer system" may include a plurality of computer devices connected via a network including the Internet or communication lines such as a WAN, LAN, or dedicated line. Furthermore, a "computer-readable recording medium" refers to portable media such as a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, or a storage device such as a hard disk built into a computer system. In this manner, the recording medium storing the program may be a non-transitory recording medium such as a CD-ROM.

The recording medium also includes internal or external recording media accessible from a distribution server to distribute the program. The program may be divided into multiple parts, downloaded at different times, and then combined with each component of the monitoring system 1 (1a-1c), or each divided program may be distributed by a different distribution server. Furthermore, the term "computer-readable recording medium" includes a recording medium that holds a program for a certain period of time, such as a volatile memory (RAM) inside a computer system that becomes a server or client when a program is transmitted over a network. The program may also be a recording medium for implementing part of the above-mentioned functions. Furthermore, the program may be a so-called differential file (differential program) that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

In addition, some or all of the above-mentioned functions may be realized as an integrated circuit such as an LSI (Large Scale Integration). Each of the above-mentioned functions may be individually processed, or some or all of the functions may be integrated into a processor. The integrated circuit method is not limited to LSI, and may be realized by a dedicated circuit or a general-purpose processor. Furthermore, if an integrated circuit technology that can replace LSI appears due to advances in semiconductor technology, an integrated circuit based on that technology may be used.

Reference Signs List 1, 1a, 1b, 1c Monitoring system 10, 10a Internet banking server 11, 31, 41, 61 NW communication unit 12, 12a, 12b Server storage unit 13, 13a, 13b, 13c Server control unit 21 IB store terminal device 22 Accounting terminal device 23 ATM
24 IB application store terminal device 30, 30a, 30b Accounting system 32 Account information storage unit 33 Transaction history storage unit 34, 34a Transaction processing unit 35, 35a Deposit/withdrawal data distribution unit 40, 40a, 40b IB application server 43 IB service processing unit 44 Push notification processing unit 42, 121, 121a User information storage unit 50 User terminal 50-1 Watched person terminal 50-2 Watcher terminal 51 User PC
51-1 PC of the person being watched
51-2 Watchman PC
52 User smartphone 52-1 Watched person smartphone 52-2 Watcher smartphone 60 API management infrastructure system 62 Authorization management unit 63 Authentication management unit 122, 122a Notification condition storage unit 123 Notification destination information storage unit 124, 124a Deposit/withdrawal data storage unit 131, 131a, 131b Internet banking processing unit 132, 132a Registration processing unit 133, 133a, 133b, 133c Notification processing unit 134, 134a Statement inquiry processing unit NW1 Network U1 Watched person U2 Watcher

Claims (11)

a notification condition storage unit that stores target account identification information that identifies the account of the person being watched over, watcher identification information that identifies the watcher watching over the person being watched over, and notification conditions for notifying transactions in the account of the person being watched over, which notification conditions are set by the person being watched over from a number of types including the amount of a single transaction, the type of deposit/withdrawal transaction, the time of the transaction, and the location of the transaction, in association with each other;
A monitoring system characterized by comprising a notification processing unit that, when deposit and withdrawal data for the account of the monitored person obtained from the accounting system satisfies the notification conditions corresponding to the target account identification information stored in the notification condition memory unit, sends a monitoring notification to the monitor identified by the monitor identification information corresponding to the target account identification information indicating that a transaction has occurred that satisfies the notification conditions set by the monitored person without the approval of the monitor . A notification information storage unit is provided for storing the watcher identification information and the notification information of the watcher in association with each other,
The monitoring system described in claim 1, characterized in that when the deposit/withdrawal data of the account of the person being monitored satisfies the notification condition, the notification processing unit sends a monitoring notification to the person being monitored indicating that a transaction has occurred in the deposit/withdrawal data of the account of the person being monitored that satisfies the notification condition, based on the notification information of the person being monitored that corresponds to the monitoring person identification information stored in the notification information storage unit. The notification information includes an email address,
The watching system according to claim 2 , wherein the notification processing unit transmits the watching notification by email to the email address of the watcher. The notification destination information includes notification destination information for push notifications,
The monitoring system described in claim 2 or claim 3, characterized in that the notification processing unit sends the monitoring notification via the push notification to an Internet banking application for which the watcher is registered as a user, based on the notification destination information of the push notification. The monitoring system according to any one of claims 1 to 4, characterized in that the watcher identification information is watcher account identification information that identifies an account of the watcher. a usage information storage unit that stores user account identification information that identifies a user's account and usage contract information that indicates whether or not a contract for using internet banking has been made in association with each other;
an internet banking processing unit for providing the internet banking transaction service;
the accounting system transmits deposit and withdrawal data for the account of the user identified by the user account identification information when the usage contract information associated with the user account identification information stored in the usage information storage unit indicates that a contract has been made to use the Internet banking service;
The monitoring system described in any one of claims 1 to 5, characterized in that the notification processing unit determines that the deposit/withdrawal data for the user's account output by the accounting system is deposit/withdrawal data for the account of the person being monitored when the user account identification information matches the target account identification information stored in the notification condition memory unit. the usage information storage unit stores the user account identification information, the usage contract information, and usage suspension information indicating whether or not to suspend use of the transaction service via the Internet banking in association with each other;
The monitoring system described in claim 6, characterized in that the online banking processing unit suspends the provision of the online banking transaction service to the user's account indicated by the user account identification information when the suspension information associated with the user account identification information stored in the usage information storage unit indicates that use of the online banking transaction service is to be suspended. A monitoring system as described in any one of claims 1 to 7, characterized in that it is provided with a registration processing unit that, in response to a request from the person being monitored, corresponds the target account identification information, the monitoring person identification information, and the notification conditions and stores them in the notification condition memory unit. a notification condition storage unit that stores target account identification information that identifies the account of the person being watched over, watcher identification information that identifies the watcher watching over the person being watched over, and notification conditions for notifying transactions in the account of the person being watched over, which notification conditions are set by the person being watched over from a number of types including the amount of a single transaction, the type of deposit/withdrawal transaction, the time of the transaction, and the location of the transaction, in association with each other;
A server device characterized by comprising: a notification processing unit that, when deposit and withdrawal data for the account of the person being monitored obtained from the accounting system satisfies the notification conditions corresponding to the target account identification information stored in the notification condition memory unit, sends a monitoring notification to the person being monitored, indicated by the monitoring person identification information corresponding to the target account identification information, indicating that a transaction has occurred that satisfies the notification conditions set by the person being monitored without the approval of the monitoring person. a registration step in which a registration processing unit associates target account identification information that identifies the account of the person being watched over, watcher identification information that identifies the watcher watching over the person being watched over, and notification conditions for notifying transactions in the account of the person being watched over, which notification conditions are set by the person being watched over from a plurality of types including the amount of a single transaction, the type of deposit/withdrawal transaction, the time of transaction, and the place of transaction, and stores the associated information in a notification condition storage unit;
A monitoring method characterized by including a notification processing step in which, when the deposit and withdrawal data of the account of the monitored person obtained from the accounting system satisfies the notification condition corresponding to the target account identification information stored in the notification condition memory unit , a monitoring notification is sent to the monitoring person indicated by the monitoring person identification information corresponding to the target account identification information, indicating that a transaction has occurred that satisfies the notification condition set by the monitored person without the approval of the monitoring person. On the computer,
a registration step of associating target account identification information for identifying the account of the person being watched over, watcher identification information for identifying the watcher watching over the person being watched over, and notification conditions for notifying transactions in the account of the person being watched over, the notification conditions being set by the person being watched over from among a plurality of types including the transaction amount per transaction, the type of deposit/withdrawal transaction, the transaction time, and the transaction location, and storing the associated information in a notification condition storage unit;
A program for executing a notification processing step of, when the deposit and withdrawal data of the account of the monitored person obtained from the accounting system satisfies the notification condition corresponding to the target account identification information stored in the notification condition memory unit, notifying the monitoring person indicated by the monitoring person identification information corresponding to the target account identification information of a monitoring notification indicating that a transaction has occurred that satisfies the notification condition set by the monitored person without the approval of the monitoring person .

Images