Financing terminal management system and financing terminal management method

Abstract

To allow each operation manager of a plurality of financial institutions to refer to information of financing terminals being managing objects, while intensively performing management of various financing terminals of the plurality of financial institutions.SOLUTION: In a financing terminal management system which manages, via a network, a plurality of financing terminals for performing financial transaction with customers while connected with accounting system of financial institutions, a collection processing unit collects collection data from the financing terminal and stores them in a storage area when the financing terminal satisfies a collection object condition for collecting the collection data. An API processing unit acquires collection data corresponding to a data condition from the storage area when having received, from an external terminal, data access in which data condition containing at least one of installation person information and installation position information is designated, and transmits it to the external terminal.SELECTED DRAWING: Figure 1A

Description

[Technical field]

[0001] The present invention relates to a financial terminal management system and a financial terminal management method. [Background technology]

[0002] In financial institutions such as banks, a network is built in which various financial terminals are communicatively connected to the accounting system, and various services are provided to customers. Examples of financial terminals include ATMs (Automatic Teller Machines) that deposit and withdraw money at branches, and deposit and withdrawal machines (cash processing machines) that deposit and withdraw money at customer locations.

[0003] However, because the specifications of accounting systems, ATMs, and deposit / withdrawal machines vary from financial institution to financial institution, each financial institution incurs costs related to the operation and management of financial terminals, which places a burden on each financial institution.

[0004] In recent years, therefore, in order to reduce the burden on each financial institution, ATMs that are configured for shared use have been installed in stores such as convenience stores, and multiple financial institutions share the ATMs. By sharing ATMs and centrally managing them, it is possible to reduce the costs for each financial institution related to the operation and management of the ATMs. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Patent Publication No. 2021-157327 Summary of the Invention [Problem to be solved by the invention]

[0006] However, the conventional technology disclosed in Patent Document 1 merely provides a management platform for centralizing the operation and management of ATMs (white label ATMs) that are configured for shared use. In other words, the conventional technology disclosed in Patent Document 1 does not take into consideration centralized management of a wide variety of non-white label financial terminals of multiple financial institutions. Furthermore, with the conventional technology disclosed in Patent Document 1, each operation manager of multiple financial institutions was unable to refer to information on the status of the financial terminals under management that was stored in the management platform.

[0007] The present invention has been made in consideration of the above background, and aims to enable each operations manager of multiple financial institutions to access information on the financial terminals they manage in a centralized manner while managing a wide variety of financial terminals at multiple financial institutions. [Means for solving the problem]

[0008] As one aspect for solving the above problem, a financial terminal management system that manages, via a network, a plurality of financial terminals that are connected to an accounting system of a financial institution and that perform financial transactions with customers, includes a storage unit that stores terminal management information that manages installer information related to the installer of the financial terminal, device type information related to the terminal type of the financial terminal, terminal identification information that identifies the financial terminal, and installation location information related to the installation location of the financial terminal, which are assigned to the financial terminal; a collection processing unit that collects collected data from the financial terminal via the network and stores it in a storage area; and an API (Application Programming Interface) that controls data access to the storage area via the network from an external terminal operated by a user designated by the installer. and an API (Application Programming Interface) processing unit, wherein the collection processing unit determines whether the financial terminal satisfies a collection target condition for collecting the collection data, and if it is determined that the collection target condition is satisfied, collects the collection data from the financial terminal and stores it in the memory area, and when the API processing unit receives data access to the memory area from the external terminal, in which a data condition including at least one of the installer information and the installation location information is specified, obtains the collection data that corresponds to the data condition from the memory area and transmits it to the external terminal. Effect of the Invention

[0009] According to the present invention, the management of a wide variety of financial terminals of a plurality of financial institutions can be centralized, while each operations manager of the plurality of financial institutions can refer to information on the financial terminals under their management. [Brief description of the drawings]

[0010] [Figure 1A] FIG. 1 is a diagram showing an example of a configuration of a financial system according to an embodiment. [Figure 1B] FIG. 2 is a diagram showing an example of the configuration of an automated teller machine as an example of a financial terminal according to the embodiment; [Figure 1C] FIG. 2 is a diagram showing an example of the configuration of a user terminal-linked automated teller machine and a depositing / dispensing machine as an example of a financial terminal according to the embodiment. [Diagram 2]FIG. 4 is a diagram showing an example of the configuration of a terminal management table according to the embodiment. [Diagram 3] FIG. 4 is a diagram showing an example of the configuration of a resource type management table according to the embodiment. [Figure 4] FIG. 4 is a diagram showing an example of the configuration of a distribution resource management table according to the embodiment. [Diagram 5] FIG. 4 is a diagram showing an example of the configuration of a version management table according to the embodiment. [Figure 6] FIG. 4 is a diagram showing an example of the configuration of a distribution result table according to the embodiment. [Figure 7] FIG. 4 is a diagram showing an example of the configuration of a collected resource management table according to the embodiment. [Figure 8] FIG. 13 is a diagram showing an example of the arrangement of a collection result table according to the embodiment. [Figure 9] FIG. 4 is a diagram showing an example of the configuration of a terminal state management table according to the embodiment. [Figure 10] FIG. 4 is a diagram showing an example of the configuration of a notification management table according to the embodiment. [Figure 11] FIG. 4 is a diagram showing an example of the configuration of a usage management table according to the embodiment. [Figure 12] 11 is a flowchart showing an example of a distribution process according to the embodiment. [Figure 13] 11 is a flowchart showing an example of a collection process according to the embodiment. [Figure 14] 6 is a flowchart showing an example of a notification and monitoring process according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. This embodiment is merely an example for realizing the present invention, and does not limit the technical scope of the present invention. Not all of the elements and their combinations described in this embodiment are essential to the solution of the invention.

[0012] In the following explanation, the same components are generally given the same reference numerals, and repeated explanations are omitted. The number of each component in the following explanation is not limited unless otherwise noted. In the following explanation, the same components are described with reference numerals including suffixes when distinguishing between them, and with reference numerals excluding the suffixes when describing them without distinction. For example, the reference numerals 12a and 12b including suffixes a and b are used when describing financial terminals 12a and 12b with distinction between them, and the reference numeral 12 excluding the suffixes is used when describing them without distinction.

[0013] In the following explanation, the processing performed by a program may be described. A computer performs processing defined by a program using a processor (e.g., a CPU (Central Processing Unit), a GPU (Graphics Processing Unit)) while using memory in a main storage device, etc. Therefore, the processor may be the entity that performs processing by executing a program. The processor executes a program to realize a functional unit that performs processing.

[0014] Similarly, the subject of processing performed by executing a program may be a controller, device, system, computer, or node having a processor. The subject of processing performed by executing a program may be a computing unit, and may include a dedicated circuit that performs specific processing. The dedicated circuit is, for example, a field-programmable gate array (FPGA) or an application specific integrated circuit (ASIC).

[0015] In the following description, a program may be installed in a computer from a program source. The program source may be, for example, a program distribution server or a non-transitory storage medium readable by a computer. When the program source is a program distribution server, the program distribution server may include a processor and a storage resource (storage) for storing a program to be distributed, and the processor of the program distribution server may distribute the program to be distributed to other computers. In addition, in an embodiment, two or more programs may be realized as one program, and one program may be realized as two or more programs.

[0016] In the following explanation, various data will be explained in table format. However, the data format is not limited to table format, and other data formats such as queues, lists, and CSV (Comma Separated Value) may be used. Since various data do not depend on the data format, a "table" can be called "information". In addition, columns of various data that include a "number," "name," "ID," "code," etc. in the column name can all be information that identifies the item indicated by the corresponding column name.

[0017] In the following embodiments, in describing the configuration of each device such as the financial terminal management system and external storage, illustrations and descriptions of communication devices that communicate with other devices and input / output devices such as keyboards and displays are omitted.

[0018] (Structure of the financial system S) 1A is a diagram showing an example of the configuration of a financial system S according to an embodiment. The financial system S includes multiple financial institution systems 1, a financial terminal management system 2, an external storage 3, and multiple operation management terminals (external terminals) 4.

[0019] Financial institution system 1 is provided for each financial institution and is configured to include accounting system 11 including an accounting host, and multiple financial terminals 12 connected to accounting system 11. Financial terminals 12 are automated teller machines (ATMs) or deposit / withdrawal machines, as described below.

[0020] Financial terminal 12 is connected to financial terminal management system 2 via network N1 such as a virtual closed network. Financial terminal 12 is also connected to accounting system 11 of each financial institution via a leased line or an Internet banking system (network N2 described below). However, communication performed by financial terminal 12 via network N1 is not limited to virtual closed network communication. Also, communication performed by financial terminal 12 via network N2 is not limited to leased line communication or Internet banking system communication.

[0021] The financial terminal 12 can be used jointly by a plurality of different financial institution systems 1 by switching the internal processing by specifying the financial institution (installation company ID, etc.).

[0022] The financial terminal management system 2 is configured to include a storage 21 , a processor 22 , a common storage 23 , a memory 24 , and a communication unit 25 .

[0023] The storage 21 is a memory unit that stores a terminal management table 211, a resource type management table 212, a distribution resource management table 213, a version management table 214, and a distribution result table 215. The storage 21 also stores a collected resource management table 216, a collection result table 217, and a terminal status management table 218. These tables will be described later.

[0024] The processor 22 realizes a distribution processing unit 221, a collection processing unit 222, a monitor / notification processing unit 223, and an API (Application Programming Interface) processing unit 224 by executing a program.

[0025] In the processor 22 and storage 21 of the financial terminal management system 2, the program execution area and memory area are divided for each company that installs the financial terminal 12. That is, the distribution processing unit 221, the collection processing unit 222, the monitoring / notification processing unit 223, the API processing unit 224, and each table of the storage 21 are provided separately for each company.

[0026] The distribution processing unit 221 receives distribution resources (programs, setting files, etc.) to be distributed to the financial terminal 12 and information about them from users via the operation management terminal 4 and the API processing unit 224. The distribution processing unit 221 registers the received distribution resources and information about them in the resource type management table 212, the distribution resource management table 213, and the resource storage area 31. The distribution processing unit 221 also manages the distribution results of the distribution resources to the financial terminal 12 in the distribution result table 215. In response to a reference request from a user via the operation management terminal 4 and the API processing unit 224, the distribution processing unit 221 narrows down the target to the financial terminal 12 linked to each user, obtains information from the distribution result table 215, and responds.

[0027] Here, the user refers to the "monitoring company," "security company," or "maintenance company" of the financial terminal 12. The "monitoring company" operates and manages the financial terminal 12. The "monitoring company" may be the company (financial institution) that installed the financial terminal 12, or a company entrusted with operation and management by the installing company. The "security company" is entrusted by the installing company to provide security for the financial terminal 12. The "maintenance company" is entrusted by the installing company to perform maintenance and inspection of the financial terminal 12. These companies may each take on the roles of "monitoring," "security," and "maintenance," or one company may take on two or more roles. The "monitoring company," "security company," and "maintenance company" are users designated by the installer of the financial terminal 12.

[0028] The collection processing unit 222 receives information on collected resources (collected data such as journal files and log files related to processing in the financial terminal 12) to be collected from the financial terminal 12 from the user via the operation management terminal 4 and the API processing unit 224. The collection processing unit 222 then registers the received collected resources and their information in the resource type management table 212 and the collected resource management table 216. The collection processing unit 222 also registers the collected resources collected from the financial terminal 12 in the resource storage area 31.

[0029] The collection processing unit 222 also manages the collection results of the collected resources collected from the financial terminals 12 in a collection result table 217. In response to a reference request from a user via the operation management terminal 4 and the API processing unit 224, the collection processing unit 222 responds by acquiring information from the collection result table 217, focusing on the financial terminals 12 linked to each user. Alternatively, in response to a reference request from a user via the operation management terminal 4 and the API processing unit 224, the collection processing unit 222 responds by acquiring collected resources stored in the resource storage area 31, focusing on the financial terminals 12 linked to each user.

[0030] The monitoring and notification processing unit 223 records the terminal status (remaining amount of various media or cash, whether a fault has occurred, etc.) notified from the financial terminal 12 in real time or at other timings. In response to a reference request from a user via the operation management terminal 4 and the API processing unit 224, the monitoring and notification processing unit 223 narrows down the target to the financial terminal 12 to be monitored that is linked to each user, and acquires the terminal status, a list of faults, and fault details from the terminal status management table 218. The monitoring and notification processing unit 223 responds to the acquired information to the operation management terminal 4.

[0031] The API processing unit 224 controls data access from the operation management terminal 4 to the storage 21 of the financial terminal management system 2 and the resource storage area 31 of the external storage 3, and controls charges related to the use of this data access. Note that in this embodiment, the API processing unit 224 may be configured as a server separate from the financial terminal management system 2.

[0032] The common storage 23 is a storage unit that stores a notification management table 231 and a usage management table 232 that are provided in common for the distribution processing unit 221, the collection processing unit 222, the monitoring / notification processing unit 223, the API processing unit 224, and each table of the storage 21 for each installation company. The notification management table 231 and the usage management table 232 will be described in detail later.

[0033] The external storage 3 is connected to the financial terminal management system 2 via the network N1, and has a resource storage area 31 for storing distribution resources to be distributed to the financial terminal 12 and collected resources collected from the financial terminal 12.

[0034] The operation management terminal 4 is operated by the user described above, and is used to register distribution resources and related information to be distributed to the financial terminal 12 via the network N in the financial terminal management system 2, and to refer to collected resources, distribution results, and collection results collected from the financial terminal 12.

[0035] 1A, financial institution systems 1a, 1b, accounting systems 11a, 11b, and financial terminals 12a, 12b represent financial institution system 1, accounting system 11, and financial terminal 12 of each installing company as indicated by the suffixes a and b. Operation management terminals 4a, 4b represent terminals of the "monitoring company," "security company," or "maintenance company" of each installing company as indicated by the suffixes a and b.

[0036] (Specific example of financial terminal 12) The financial terminal 12 is an automated teller machine (ATM) or cash dispenser (CD) installed in a store or the like, or a deposit / withdrawal machine installed at a financial institution's customer base (cash point) for depositing and counting sales proceeds and dispensing change funds.

[0037] FIG. 1B is a diagram showing an example of the configuration of an automated teller machine 100 as an example of a financial terminal 12 according to an embodiment. As shown in FIG. 1B, the automated teller machine 100 has a processor 101, a memory 102, a communication unit 103, and a communication unit 104. The automated teller machine 100 is connected to a financial terminal management system 2 via a network N1 by the communication unit 103. The automated teller machine 100 is also connected to an accounting system 11 via a network N2, which is a dedicated line, by the communication unit 104. The automated teller machine 100 is also equipped with a processor 101 and a memory 102 that control the operation of the automated teller machine 100 as a whole. The processor 101 controls a bill handling device 105, a screen operation unit 106, a coin handling device 107, a passbook processing mechanism 108, and a card / statement processing mechanism 109.

[0038] Fig. 1C is a diagram showing an example of the configuration of a user terminal-linked automated teller machine 100B and a depositing / dispensing machine 200 as an example of the financial terminal 12 according to the embodiment. As shown in Fig. 1C, the automated teller machine 100B is configured by removing the screen operation unit 106, the passbook processing mechanism 108, and the card / statement processing mechanism 109 from the automated teller machine 100 (Fig. 1B), and by having a short-range wireless communication unit 104B instead of the communication unit 104. The automated teller machine 100B is paired with the user terminal 300 by the short-range wireless communication unit 104B, and is connected to the accounting system 11 via the user terminal 300.

[0039] The user terminal 300 is a computer such as a tablet or a smartphone, and is equipped with a processor 301, a memory 302, a communication unit 303, and a short-range wireless communication unit 304. The user terminal 300 is paired with the automated teller machine 100B via the short-range wireless communication unit 304. The automated teller machine 100B is controlled by a transaction application 301a that runs on the processor 301 and controls financial transactions using the automated teller machine 100B.

[0040] The configuration of the depositing / dispensing machine 200 is generally similar to that of the automated teller machine 100B.

[0041] (Explanation of various tables) Each table stored in the storage 21 and the common storage 23 will be described below with reference to Figures 2 to 11. Note that columns with the same name in different tables have the same possible values. Also, although not shown, a timestamp indicating the date and time of the creation of the entry or the date and time of the occurrence of the event represented by the entry is assigned to each entry in each table.

[0042] (Configuration of terminal management table 211) 2 is a diagram showing an example of the configuration of a terminal management table 211 according to an embodiment. The terminal management table 211 manages device information of pre-registered financial terminals 12. The terminal management table 211 has columns for "Installation company ID," "System ID," "Device ID," "Model code," "Serial number," "Installation location," "Location information," and "Distribution area information."

[0043] "Installer company ID" is identification information of the company using the corresponding financial terminal 12, and is installer information. "System ID" is identification information of the system to which the corresponding financial terminal 12 belongs, for example, "remote maintenance system for banks." "Device ID" is identification information of the terminal type of the corresponding financial terminal 12, and is device type information such as "ATM," "user terminal linked ATM," "deposit / withdrawal machine," etc.

[0044] The "model code" is identification information for the model of the relevant financial terminal 12. The "serial number" is a manufacturing number or the like that identifies the relevant financial terminal 12, and is terminal identification information that identifies an individual financial terminal 12.

[0045] "Installation address" is the installation address of the corresponding financial terminal 12, and is installation location information of the financial terminal 12. "Location information" is tag information indicating the latitude and longitude of the GNSS (Global Navigation Satellite System) of the corresponding financial terminal 12. "Distribution area information" is the area of ​​the distribution group to which the corresponding financial terminal 12 belongs when receiving information distribution from the financial terminal management system 2.

[0046] By specifying values ​​for each column of the terminal management table 211, each financial terminal 12 can control the distribution of distribution resources, the collection of collection resources, and the reference to the terminal information of each financial terminal 12 stored in the terminal status management table 218, in accordance with the purpose.

[0047] (Configuration of resource type management table 212) 3 is a diagram showing an example of the configuration of a resource type management table 212 according to an embodiment. The resource type management table 212 manages the types of distribution resources to be distributed to a pre-registered financial terminal 12 or collected resources to be collected from a financial terminal 12. The resource type management table 212 has columns for "installation company ID", "system ID", "model code", "resource category", "resource type", "resource type", and "timing type".

[0048] "Installation company ID" is identification information of the company using the financial terminal 12 to which the corresponding resource is to be distributed or collected. "System ID" is identification information of the system to which the financial terminal 12 to which the corresponding resource is to be distributed or collected belongs. "Model code" is identification information of the model of the financial terminal 12 to which the corresponding resource is to be distributed or collected.

[0049] "Resource classification" is identification information of the corresponding distribution resource or collection resource. "Resource type" is information indicating whether the corresponding resource is a distribution resource or a collection resource, such as "1: distribution resource" or "2: collection resource". "Timing type" is information indicating the timing of collection and distribution of the corresponding distribution resource or collection resource, such as "1: immediate (collection and distribution as soon as data is ready)" or "2: regular (collection and distribution at fixed intervals)".

[0050] (Configuration of distribution resource management table 213) 4 is a diagram showing an example of the configuration of the distribution resource management table 213 according to the embodiment. The distribution resource management table 213 manages distribution resources to be distributed to pre-registered financial terminals 12. The distribution resource management table 213 has columns for "installation company ID," "system ID," "model code," "resource category," "resource type," "resource version," and "resource storage area address."

[0051] "Installation company ID" is identification information of the company that uses the financial terminal 12 to which the corresponding distribution resource is to be distributed. "System ID" is identification information of the system to which the financial terminal 12 to which the corresponding distribution resource is to be distributed belongs. "Model code" is identification information of the model of the financial terminal 12 to which the corresponding distribution resource is to be distributed.

[0052] "Resource category" is identification information of the corresponding distribution resource. "Resource type" is information on the type of the corresponding distribution resource. "Resource version" is information indicating the version number of the corresponding distribution resource. "Resource storage area address" is the storage path of the corresponding distribution resource in the resource storage area 31 of the external storage 3.

[0053] (Configuration of version control table 214) 5 is a diagram showing an example of the configuration of the version management table 214 according to the embodiment. The version management table 214 manages the versions of the distributed resources distributed and applied to the corresponding financial terminal 12. The version management table 214 has columns for "Installation company ID", "System ID", "Device ID", "Model code", "Serial number", "Resource category", "Resource type", and "Resource version".

[0054] The "Installation Company ID" is identification information of the company that uses the corresponding financial terminal 12. The "System ID" is identification information of the system to which the corresponding financial terminal 12 belongs. The "Device ID" is identification information of the terminal type of the corresponding financial terminal 12.

[0055] The "model code" is identification information for the model of the relevant financial terminal 12. The "serial number" is identification information for the model of the relevant financial terminal 12.

[0056] The "resource type" is identification information of the distributed resource applied to the corresponding financial terminal 12. The "resource type" is information on the type of the distributed resource distributed and applied to the corresponding financial terminal 12.

[0057] The "resource version" is information indicating the version number of the distributed resource applied to the financial terminal 12 in question.

[0058] (Configuration of distribution result table 215) 6 is a diagram showing an example of the configuration of the distribution result table 215 according to the embodiment. The distribution result table 215 manages the progress of application of the relevant resource to the relevant financial terminal 12. The distribution result table 215 has columns of "Installation company ID", "System ID", "Device ID", "Model code", "Serial number", "Resource category", "Resource type", "Resource version", "Status", and "Download result".

[0059] "Installation company ID" is identification information of the company using the corresponding financial terminal 12. "System ID" is identification information of the system to which the corresponding financial terminal 12 belongs. "Device ID" is identification information of the terminal type of the corresponding financial terminal 12. "Model code" is identification information of the model of the corresponding financial terminal 12. "Serial number" is identification information of the model of the corresponding financial terminal 12.

[0060] "Resource category" is identification information of the distribution resource applied to the corresponding financial terminal 12. "Resource type" is information on the type of distribution resource applied to the corresponding financial terminal 12. "Resource version" is information indicating the version number of the distribution resource applied to the corresponding financial terminal 12.

[0061] "Status" indicates the distribution status of the corresponding distribution resource to the corresponding financial terminal 12, and can be "1: Downloaded (distributed)", "2: Not downloaded (not distributed)", etc. "Download status" indicates the distribution result of the corresponding distribution resource to the corresponding financial terminal 12, and can be "1: OK (success)", "2: NG (failure)", etc.

[0062] (Configuration of collected resource management table 216) 7 is a diagram showing an example of the configuration of the collected resource management table 216 according to the embodiment. The collected resource management table 216 manages collected resources collected from pre-registered financial terminals 12. The configuration and function of the collected resource management table 216 are similar to those of the distributed resource management table 213 (FIG. 4), except that "distribution" is replaced with "collection", and "download" with "upload", and "resource version" is deleted. "Resource type" is, for example, "journal data" or "log file", etc.

[0063] (Configuration of collection result table 217) 8 is a diagram showing an example of the configuration of the collection result table 217 according to the embodiment. The collection result table 217 manages the progress of collection of the relevant collected resource from the relevant financial terminal 12. The configuration and function of the collection result table 217 are the same as those of the distribution result table 215, except that "distribution" is replaced with "collection" and "download" with "upload", and "resource version" is deleted.

[0064] (Configuration of terminal state management table 218) 9 is a diagram showing an example of the configuration of the terminal status management table 218 according to the embodiment. The terminal status management table 218 manages the status information of each financial terminal 12 notified from each financial terminal 12. The terminal status management table 218 has columns for "Installation company ID", "System ID", "Device ID", "Model code", "Serial number", "Terminal status", "Terminal status details", and "Status".

[0065] The "Installation Company ID" is identification information of the company that uses the corresponding financial terminal 12. The "System ID" is identification information of the system to which the corresponding financial terminal 12 belongs. The "Device ID" is identification information of the terminal type of the corresponding financial terminal 12.

[0066] The "model code" is identification information for the model of the relevant financial terminal 12. The "serial number" is a manufacturing number or the like that identifies the relevant financial terminal 12.

[0067] "Terminal status" indicates the status of the relevant financial terminal 12, for example, "0: normal" or "1: abnormal." "Terminal status details" is the details of the "terminal status" of the relevant financial terminal 12, specifically indicating the location and content of the abnormality (for example, "ATM banknote unit jam" or "out of banknotes").

[0068] "Status" is information that supplements "Terminal Status Details", and for example, indicates "banknote unit 1" where a jam has occurred for "ATM banknote unit jam", or indicates "1,000 yen note" for "out of banknotes".

[0069] (Configuration of notification management table 231) 10 is a diagram showing an example of the configuration of the notification management table 231 according to the embodiment. The notification management table 231 manages the notification policy of the status information of each financial terminal 12 notified from the financial terminal 12. The notification management table 231 has columns of "Terminal Status", "Terminal Status Details", "Status", "Monitoring Company", "Security Company", and "Maintenance Company".

[0070] "Terminal status", "Terminal status details", and "Status" are the same as "Terminal status", "Terminal status details", and "Status" in terminal status management table 218. In notification management table 231, "Monitoring company", "Security company", and "Maintenance company" indicate the notification destination of the status information of the financial terminal 12 specified by "Terminal status", "Terminal status details", and "Status". Notification management table 231 stores the necessity of notification (notification policy) to each of the "Monitoring company", "Security company", and "Maintenance company" of the corresponding financial terminal 12.

[0071] (Configuration of Usage Management Table 232) 11 is a diagram showing an example of the configuration of the usage management table 232 according to the embodiment. The usage management table 232 manages the history of an operator of each user of the financial terminal 12 operating the operation management terminal 4 and referring to the terminal status management table 218 via the API processing unit 224. The usage management table 232 manages the number of times the terminal status management table 218 was referred to for each company that installed the financial terminal 12 and for each date.

[0072] (Distribution process according to the embodiment) Fig. 12 is a flowchart showing an example of a distribution process according to the embodiment. In the distribution process shown in Fig. 12, the distribution resource is a program, and an update of the program that runs on the financial terminal 12 is taken as an example.

[0073] In the distribution process according to the embodiment, each financial terminal 12 periodically inquires of the financial terminal management system 2 whether there are any distribution resources to be distributed, such as when the financial terminal 12 is powered on. If there are any distribution resources to be distributed, the financial terminal management system 2 notifies the financial terminal 12 of the address of the storage destination of the distribution resources. The financial terminal 12 then accesses the address of the storage destination of the distribution resources and downloads the distribution resources to its own device.

[0074] First, in step S11, when the installation of the financial terminal 12 is completed, the financial terminal 12 transmits a terminal registration request including the terminal information of the financial terminal 12 to the financial terminal management system 2. The terminal information is information of the financial terminal 12 corresponding to each row of the terminal management table 211.

[0075] Next, in step S 12 , the financial terminal management system 2 receives a terminal registration request from the financial terminal 12 , and registers the received terminal information in the terminal management table 211 .

[0076] Next, in step S13, the distribution processing unit 221 of the financial terminal management system 2 receives information related to distribution resources to be distributed to each financial terminal 12 via the operation management terminal 4 and the API processing unit 224, and registers the information in the resource type management table 212 and the distribution resource management table 213. The distribution processing unit 221 also receives uploads of distribution resources via the operation management terminal 4 and the API processing unit 224, and stores them in the resource storage area 31 of the external storage 3.

[0077] The order of steps S11 and S12 and step S13 may be interchanged. Furthermore, when the distribution process shown in FIG.

[0078] Next, in step S14, when the financial terminal 12 is powered on, it transmits the "serial number" of its own device and the "resource version" of the program to the distribution processing unit 221 as distribution target conditions for distribution data. If this "serial number" and "resource version" correspond to a specific serial number and the resource version is older than the resource version of the distribution resource to be distributed, the relevant financial terminal 12 is narrowed down as a distribution target, and the distribution resource is distributed. However, the distribution target conditions are not limited to the combination of "serial number" and "resource version", and may be any combination of information identifying the financial terminal 12 to be distributed and attribute information of the distribution resource to be distributed.

[0079] Next, in step S15, the distribution processing unit 221 receives the "serial number" and "resource version" transmitted in step S14.

[0080] Next, in step S16, the distribution processing unit 221 refers to the version management table 214 and checks the current "resource version" of the financial terminal 12 corresponding to the "serial number". The distribution processing unit 221 then compares the "resource version" received in step S15 with the current "resource version" and determines whether the current "resource version" is older and the program of the financial terminal 12 in question needs to be distributed and updated (satisfies the distribution target condition). If it is necessary to distribute and update (step S16 YES), the distribution processing unit 221 proceeds to step S17, and if it is not necessary to distribute (step S16 NO), ends the distribution processing.

[0081] In step S 17 , distribution processing unit 221 refers to distribution resource management table 213 , acquires the resource storage area address of the program in question for the latest “resource version”, and transmits it to financial terminal 12 .

[0082] Next, in step S18, financial terminal 12 receives from distribution processing unit 221 the resource storage area address of the program.

[0083] Next, in step S19, financial terminal 12 accesses resource storage area 31 of external storage 3 via API processor 224 based on the resource storage area address received in step S18 in order to acquire the corresponding program.

[0084] Next, in step S 20 , the distribution processing unit 221 accesses the relevant resource storage area address in the resource storage area 31 of the external storage 3 , reads out the update data for the relevant program, and transmits it to the financial terminal 12 .

[0085] Next, in step S21, financial terminal 12 applies the corresponding program acquired in step S20 to its own device, and transmits an acquisition completion notification together with the "serial number", updated "resource version", "status", "download result", etc. to distribution processing unit 221. Next, in step S22, distribution processing unit 221 updates version management table 214 and distribution result table 215 based on the "serial number", "resource version", "status", "download result", etc. received from financial terminal 12.

[0086] (Collection process according to the embodiment) Fig. 13 is a flowchart illustrating an example of a collection process according to the embodiment. In the collection process illustrated in Fig. 13, an example in which collected resources are stored as a log file will be described.

[0087] In the collection process according to the embodiment, each financial terminal 12 periodically inquires of the financial terminal management system 2 about whether or not it is necessary to collect collected resources from its own device, for example, when the financial terminal 12 is powered on. If the collected resources should be collected, the financial terminal management system 2 notifies the financial terminal 12 of the address of the storage destination of the collected resources. The financial terminal 12 then accesses the address of the storage destination of the collected resources and uploads the corresponding log file.

[0088] Steps S31 and S32 are similar to steps S11 and S12 in the distribution process (FIG. 12).

[0089] Next, in step S33, the collection processing unit 222 of the financial terminal management system 2 receives, for the financial terminals 12 registered in step S32, information related to collected resources (e.g., log files) to be collected in each financial terminal 12 via the operation management terminal 4 and the API processing unit 224. The collection processing unit 222 then registers the received information in the resource type management table 212 and the collected resource management table 216. The collection processing unit 222 also receives, via the operation management terminal 4 and the API processing unit 224, a path specification for the upload destination of the log file, and secures an upload area in the resource storage area 31 of the external storage 3.

[0090] Next, in step S34, when the financial terminal 12 is powered on, it transmits the "serial number" of its own device to the distribution processing unit 221 as a collection target condition for collected data. If the collection target condition is "serial number", and this "serial number" corresponds to a specific serial number (satisfies the collection target condition), the relevant financial terminal 12 is narrowed down as a collection target for collected resources, and the collected resources are collected. However, the collection target condition is not limited to "serial number", and may be one or any combination of items in the columns included in the terminal management table 211.

[0091] Next, in step S35, the distribution processing unit 221 receives the "serial number" transmitted in step S34.

[0092] Next, in step S36, the collection processing unit 222 refers to the collected resource management table 216 and determines whether an entry for the financial terminal 12 corresponding to the "serial number" exists. If an entry corresponding to the "serial number" received in step S35 exists (step S36 YES), the collection processing unit 222 proceeds to step S37. The reason the processing proceeds to step S37 is because it has been determined that the collected resource (e.g., a log file) indicated by the "resource type" of the corresponding entry needs to be collected. On the other hand, if a corresponding entry does not exist (step S36 NO), the collection processing unit 222 ends the collection process.

[0093] In step S 37 , the collection processor 222 refers to the collected resource management table 216 , acquires the resource storage area address of the corresponding log file, and transmits it to the financial terminal 12 .

[0094] Next, in step S38, financial terminal 12 receives from collection processor 222 the resource storage area address of the corresponding log file.

[0095] Next, in step S39, financial terminal 12 accesses the resource storage area address in resource storage area 31 of external storage 3 via API processor 224 based on the resource storage area address received in step S18, and uploads the corresponding log file.

[0096] Next, in step S40, the external storage 3 stores the corresponding log file in the corresponding resource storage area 31.

[0097] Next, in step S41, the financial terminal 12 transmits a transmission completion notice together with the "serial number", "resource type", "status", "upload result", etc. to the collection processing unit 222. Next, in step S42, the collection processing unit 222 updates the collection result table 217 based on the "serial number", "resource type", "status", "download result", etc. received from the financial terminal 12.

[0098] (Notification and monitoring process according to the embodiment) FIG. 14 is a flowchart showing an example of a notification and monitoring process according to the embodiment.

[0099] In the notification and monitoring process according to the embodiment, when a change in the terminal status occurs, such as when a failure occurs in each financial terminal 12, the financial terminal 12 notifies the financial terminal management system 2 of the terminal status from each financial terminal 12. The financial terminal management system 2 stores the notified terminal status in the terminal status management table 218. Then, in response to a reference request from a user, such as the company that installed each financial terminal 12, the financial terminal management system 2 accesses the terminal status management table 218 via the operation management terminal 4 and the API processing unit 224 and transmits the terminal status.

[0100] Steps S51 and S52 are similar to steps S11 and S12 in the distribution process (FIG. 12).

[0101] Next, in step S53, the financial terminal 12, upon receipt of a change in its terminal status, notifies the monitor / notify processor 223 of the financial terminal management system 2 of its own terminal status information. Next, in step S54, the monitor / notify processor 223 registers the terminal status information received from the financial terminal 12 in the terminal status management table 218.

[0102] Steps S53 and S54 are repeatedly executed as long as a change in the terminal status occurs in financial terminal 12, and notifications are accumulated in terminal status management table 218 for each model.

[0103] Next, in step S55, the financial terminal management system 2 notifies the operation management terminal 4 operated by one or more users of the "monitoring company", "security company" and "maintenance company" of the terminal status information registered in step S54, in accordance with the notification policy described in the notification management table 231. Alternatively, the financial terminal management system 2 does not notify the operation management terminal 4 of any user. The notification policy is a description of whether or not notification is required to each of the "monitoring company", "security company" and "maintenance company" in the notification management table 231 in accordance with the notification policy.

[0104] Next, in step S56, the operations management terminal 4 of the appropriate company, either the "monitoring company," "security company," or "maintenance company," receives the notification of the terminal status sent from the financial terminal management system 2 in step S55.

[0105] Next, in step S57, the operation management terminal 4 transmits the terminal status information or the acquisition range information of collected resources required for each purpose such as monitoring, security, maintenance, etc. to the financial terminal management system 2 in response to instructions from the user. The acquisition range information is the data conditions to be acquired, and is designation information such as the "installation company ID", "system ID", "equipment ID", "model code", "serial number", and "installation address" of the financial terminal 12, a timestamp of the status notification, and the "resource type" of collected resources. The acquisition range information may include at least one of the "installation company ID" and "installation address", for example. This allows the user to acquire data limited to the company or region they are responsible for.

[0106] The acquisition range information may include information indicating whether the user is a "monitoring company", a "security company", or a "maintenance company" along with at least one of the "installation company ID" and the "installation address". Depending on whether the user is a "monitoring company", a "security company", or a "maintenance company", the type of data to be acquired or the period of data may be different, even if the company or area in charge is the same. For example, since the mission of the "monitoring company" is to monitor the operating status, real-time and broad-perspective monitoring are emphasized, so the latest short-term data for more types of data is acquired. On the other hand, the cash demand forecast for the "security company" and the forecast of failure investigation and regular inspection timing for the "maintenance company" are based on long-term data for a specific type of data narrowed down from the perspective of usefulness in investigation and prediction, so long-term data for this specific type of data is acquired. In this way, the user's convenience can be improved by acquiring the appropriate type and amount of data according to the user's mission.

[0107] Next, in step S58, the API processing unit 224 of the financial terminal management system 2 receives terminal status information or acquisition range information of collected resources from the operation management terminal 4. Next, in step S59, the API processing unit 224 acquires the target terminal status information from the terminal status management table 218 based on the acquisition range information received in step S58. Alternatively, the API processing unit 224 acquires the target collected resource (e.g., a log file) from the resource storage area 31 based on the acquisition range information. Then, the API processing unit 224 records the number of times the terminal status management table 218 was referenced for each company that installed the financial terminal 12 and for each date in the usage management table 232.

[0108] Next, in step S60, the API processing unit 224 transmits the terminal status information or collected resources acquired in step S60 to the operation management terminal 4. Next, in step S61, the operation management terminal 4 receives the terminal status information transmitted from the API processing unit 224 in step S60, and outputs it from an output device (not shown).

[0109] The above-mentioned step S57 is repeatedly executed as many times as necessary by each of the "monitoring company," "security company," and "maintenance company." Furthermore, steps S55 to S56 and steps S57 to S61 may be executed asynchronously.

[0110] The API processing unit 224 generates billing information for billing the user based on the usage status including the number of references recorded in the usage management table 232 in step S59, during regular processing such as monthly processing or immediate processing.

[0111] (Effects of the embodiment) In the above embodiment, when the financial terminal 12 satisfies the collection target conditions for collecting collected data, the financial terminal management system 2 collects collected data from the financial terminal 12 and stores the collected data in the resource storage area 31. In addition, the financial terminal management system 2 accepts data access to the resource storage area 31, in which data conditions including installer information or installation location information are specified, from the operation management terminal 4, and obtains the collected data that meets the data conditions from the resource storage area 31 and transmits it to the operation management terminal 4.

[0112] Therefore, according to the embodiment, the management of a wide variety of financial terminals 12 of multiple financial institutions is centrally performed by the financial terminal management system 2, while each operations manager (user) of the multiple financial institutions can refer to the collected data of the financial terminals 12 under their respective management at any time.

[0113] Furthermore, in the above-described embodiment, when the financial terminal management system 2 distributes the distribution data stored in the resource storage area 31 to the financial terminal 12, if the financial terminal 12 satisfies the distribution target conditions for distributing the distribution data, the financial terminal management system 2 distributes the distribution data to the financial terminal 12. Therefore, according to the embodiment, the financial terminal management system 2 can centrally manage remote maintenance such as program updates for a wide variety of financial terminals 12 of multiple financial institutions.

[0114] Furthermore, in the above-described embodiment, the financial terminal management system 2 receives terminal status information indicating the status of the financial terminal 12 from the financial terminal 12, and stores the terminal status information. Then, when data access to terminal status information in which data conditions including at least one of installer information and installation location information are specified is accepted from the operation management terminal 4, the financial terminal management system 2 acquires terminal status information corresponding to the data conditions and transmits it to the operation management terminal 4. Thus, according to the embodiment, while the terminal status information of a wide variety of financial terminals 12 of multiple financial institutions is collectively managed by the financial terminal management system 2, each operation manager of the multiple financial institutions can refer to an appropriate range of terminal status information at any time according to his / her area of ​​responsibility.

[0115] In the above embodiment, when the financial terminal management system 2 receives terminal status information from the financial terminal 12, it notifies or does not notify the operation management terminal 4 operated by the user of the terminal status information depending on whether the user is a monitoring company, a security company, or a maintenance company. Therefore, according to the embodiment, the notification of the terminal status information is not excessive, and the notification is sent appropriately according to the user's mission.

[0116] In the above embodiment, the financial terminal management system 2 records the usage status of data access by the operation management terminal 4, and generates billing information to be charged to the user based on the usage status. Therefore, according to the embodiment, the billing amount increases according to the number of data accesses and the amount of data, and it is possible to achieve fairness in the burden of the cost for the financial terminal management system 2 to consolidate and store data in the resource storage area 31, etc.

[0117] In the above embodiment, the financial terminal management system 2 allows the user to obtain different types of data or different periods of data via the operation management terminal 4 in response to data access depending on whether the user is a monitoring company, a security company, or a maintenance company. Thus, according to the embodiment, the user can obtain the appropriate type and amount of data according to his / her mission, thereby improving the convenience of the user.

[0118] The present invention is not limited to the above-described embodiment, and can be implemented using any components without departing from the scope of the present invention. The above-described embodiments and modifications are merely examples, and the present invention is not limited to these contents as long as the features of the invention are not impaired. In addition, although various embodiments and modifications have been described above, the present invention is not limited to these contents. Other aspects conceivable within the scope of the technical idea of ​​the present invention are also included in the scope of the present invention.

[0119] For example, some of the functions provided in each device in the above-described embodiments may be provided in another device, and functions provided in another device may be provided in the same device.

[0120] Furthermore, the program configurations described in the above embodiments are merely examples. For example, a part of a program may be incorporated into another program, or multiple programs may be configured as a single program. [Explanation of symbols]

[0121] S: financial system, 1, 1a, 1b: financial institution system, 2: financial terminal management system, 3: external storage, 4, 4a, 4b: operation management terminal, 11, 11a, 11b: accounting system, 12, 12a, 12b: financial terminal, 31: resource storage area, 100, 100B: automated teller machine, 211: terminal management table, 221: distribution processing unit, 222: collection processing unit, 223: monitoring and notification processing unit, 224: API processing unit, 231: notification management table, 232: usage management table, 300: user terminal.

Claims

1. A financial terminal management system that manages, via a network, a plurality of financial terminals that are connected to an accounting system of a financial institution and that perform financial transactions with customers, comprising: a storage unit for storing terminal management information for managing installer information related to an installer of the financial terminal, device type information related to the terminal type of the financial terminal, terminal identification information for identifying an individual of the financial terminal, and installation location information related to the installation location of the financial terminal, which are assigned to the financial terminal; a collection processing unit that collects collected data from the financial terminal via the network and stores the collected data in a storage area; an API (Application Programming Interface) processing unit that controls data access to the storage area via the network from an external terminal operated by a user designated by the installer, The collection processing unit includes: determining whether the financial terminal satisfies a collection target condition for collecting the collected data, and if it is determined that the collection target condition is satisfied, collecting the collected data from the financial terminal and storing it in the storage area; The API processing unit includes: When receiving a data access to the storage area from the external terminal, in which a data condition including at least one of the installer information and the installation location information is specified, the collected data corresponding to the data condition is acquired from the storage area and transmitted to the external terminal. A financial terminal management system comprising:

2. 2. The financial terminal management system according to claim 1, The collected data is a log file or a journal file related to processing in the financial terminal. A financial terminal management system comprising:

3. 2. The financial terminal management system according to claim 1, a distribution processing unit that distributes the distribution data stored in the storage area to the financial terminal; The distribution processing unit is It is determined whether the financial terminal satisfies a distribution target condition for distributing the distribution data, and when it is determined that the distribution target condition is to be collected, the distribution data is distributed to the financial terminal. A financial terminal management system comprising:

4. 4. The financial terminal management system according to claim 3, the distribution data is a program that causes the financial terminal to execute a predetermined process, The distribution conditions include information regarding the version of the program. A financial terminal management system comprising:

5. 2. The financial terminal management system according to claim 1, a monitoring and notification processing unit for receiving terminal status information indicating a status of the financial terminal from the financial terminal and storing the terminal status information; The API processing unit includes: When receiving data access to the terminal status information from the external terminal, in which a data condition including at least one of the installer information and the installation location information is specified, the terminal status information corresponding to the data condition is acquired and transmitted to the external terminal. A financial terminal management system comprising:

6. 6. The financial terminal management system according to claim 5, managing a notification policy that specifies whether or not to notify a user of the terminal status information when the terminal status information is received from the financial terminal, depending on whether the user corresponds to a monitoring company that monitors the financial terminal, a security company that guards the financial terminal, or a maintenance company that maintains the financial terminal; The monitoring and notification processing unit includes: The terminal state information is notified or not notified to the external terminal operated by the user according to the notification policy. A financial terminal management system comprising:

7. The financial terminal management system according to any one of claims 1 to 6, The financial terminal is an automated teller machine connected to the accounting system via a dedicated line, or an automated teller machine communicatively connected to a terminal capable of communicating with the accounting system via an Internet banking system and connected to the accounting system via the terminal, or a deposit / withdrawal machine communicatively connected to the terminal and connected to the accounting system via the terminal. A financial terminal management system comprising:

8. The financial terminal management system according to any one of claims 1 to 5, The API processing unit includes: Recording the usage status of the data access by the external terminal; Generate billing information for billing the user based on the usage status A financial terminal management system comprising:

9. The financial terminal management system according to any one of claims 1 to 5, The API processing unit includes: Depending on whether the user corresponds to a monitoring company that monitors the financial terminal, a security company that guards the financial terminal, or a maintenance company that maintains the financial terminal, the type of data that the user is allowed to obtain via the external terminal in response to the data access is varied, or the period of the data is varied. A financial terminal management system comprising:

10. A financial terminal management method executed by a financial terminal management system that manages, via a network, a plurality of financial terminals that are connected to an accounting system of a financial institution and that perform financial transactions with customers, comprising: The financial terminal management system includes: a storage unit for storing terminal management information for managing installer information related to an installer of the financial terminal, device type information related to the terminal type of the financial terminal, terminal identification information for identifying an individual of the financial terminal, and installation location information related to the installation location of the financial terminal, which are assigned to the financial terminal; a collection processing step of collecting collected data from the financial terminal via the network and storing the collected data in a storage area; an API (Application Programming Interface) processing step for controlling data access to the storage area via the network from an external terminal operated by a user designated by the installer, In the collection processing step, determining whether the financial terminal satisfies a collection target condition for collecting the collected data, and if it is determined that the collection target condition is satisfied, collecting the collected data from the financial terminal and storing it in the storage area; In the API processing step, When receiving a data access to the storage area from the external terminal, in which a data condition including at least one of the installer information and the installation location information is specified, the collected data corresponding to the data condition is acquired from the storage area and transmitted to the external terminal. A financial terminal management method comprising:

11. 11. The method of claim 10, further comprising: a distribution processing step of distributing the distribution data stored in the storage area to the financial terminal; In the distribution processing step, It is determined whether the financial terminal satisfies a distribution target condition for distributing the distribution data, and when it is determined that the distribution target condition is to be collected, the distribution data is distributed to the financial terminal. A financial terminal management method comprising:

12. 11. The method of claim 10, further comprising: a monitoring and notification processing step of receiving terminal status information indicating a status of the financial terminal from the financial terminal and storing the terminal status information; In the API processing step, When receiving data access to the terminal status information from the external terminal, in which a data condition including at least one of the installer information and the installation location information is specified, the terminal status information corresponding to the data condition is acquired and transmitted to the external terminal. A financial terminal management method comprising:

Images