JP2014203227A - Terminal management operation system and method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To distribute a software patch to a large amount of terminals at a plurality of bases, while suppressing delay.SOLUTION: A management server distributes a software patch, a relay server relays the software patch, a plurality of terminals receive and execute the relayed software patch and replies the management server, a business server distributes a job related to the terminals, the relay server stores the software patch when the distribution destination terminals of the received software patch are not connected to a network and distributes the stored software patch when the distribution destination terminals are connected to the network, the management server distributes a deletion script for deleting the software patch to the relay server, and the relay server receives the deletion script and deletes the stored software patch.

Description

  The present invention relates to a terminal management and operation technique for distributing software patches to terminals at multiple locations connected to a network.

  In a terminal infrastructure system, distributing software patches such as security patches to terminals is an essential operation from the viewpoint of security. There are many distributed asset management software in the world, but software patches are applied to all terminals every day in a large-scale system where the number of managed terminals exceeds 100,000 and the number of bases exceeds 20,000. When other jobs are distributed, there is a problem that distribution cannot be performed or distribution time is delayed only by operation that relies on existing software.

  In Patent Document 1, the terminal is divided into groups based on the release date of the distribution file used at each terminal in the server device, and a tree structure is constructed by the terminal for each group. Furthermore, when the server device requests transmission of the distribution file, the server device identifies the group having the distribution file, incorporates the terminal that requested transmission into the tree structure of the identified group, and requested the transmission On the other hand, by instructing to acquire a distribution file from a terminal located above the terminal in the group, the problem of taking a distribution time is solved.

  However, with the above solutions alone, “Network traffic load is applied” “Performance is degraded due to frequent fragmentation of indexes in the database that manages the jobs to be distributed” “Terminals that have not been connected for a long time from the network When there is a large amount of jobs, a large amount of jobs are accumulated in the manager that manages the distribution and the performance of the delivery time deteriorates, and the problem that the delivery cannot be performed or the delivery time is delayed is completely solved. I'm not sure.

JP 2011-107907

  The problem to be solved is that if a job is distributed at once to a large number of terminals in a large number of locations, the network traffic load will cause the distribution job to be delayed or undeliverable, and frequently indexed in the database that manages the job to be distributed If a large number of terminals that have not been connected for a long time from the network exist, the job will be distributed to the manager that manages the distribution in large quantities. It is accumulated and the performance of the delivery time is deteriorated, and the delivery job is delayed or cannot be delivered.

  In the present invention, in order to solve the above problem, a management server distributes a software patch, a relay server relays the software patch, and a plurality of terminals receive and execute the relayed software patch. , Reply to the management server, the business server distributes the job related to the business to the terminal, the relay server, when the terminal to which the received software patch is distributed is not connected to the network, The software patch is stored, and when the distribution destination terminal is connected to the network, the stored software patch is distributed, and the management server distributes a deletion script for deleting the software patch to the relay server The relay server receives the deletion script and stores the stored software. To remove the patch.

  According to the present invention, there is an advantage that operation costs can be reduced by suppressing delays in distributing software patches and jobs such as security patches to a large number of multi-site terminals.

It is a terminal management system concerning one example of the present invention. It is the operation schedule concerning one Example of this invention. It is a file for distribution in distribution management concerning one example of the present invention. It is the deletion level of the relay file concerning one Example of this invention.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is a terminal management system according to the present embodiment. The terminal management system includes a distribution management server 101, distribution management relay servers 102a and 102b, a terminal 103 provided for each site A, and a business server 104. Each of these is communicably connected via a network 105.

  The distribution management server 101 is the highest manager, creates a software patch and distributes it to the terminal, and receives the execution result of the software patch from the terminal 103. The distribution management relay servers 102a and 102b relay software patches and execution results as relay managers, and temporarily store software patches when a terminal is not connected. Site A is where staff stay and work. The terminal 103 is an information processing apparatus that is installed at a base or can be connected to a network outside the base and is operated by a staff member. The terminal 103 includes an ATM (Automated Teller Machine) / window terminal, a dedicated terminal such as a portable terminal, and a general PC (Personal Computer), but can also be applied to a tablet, a smartphone, or the like.

  Examples of the business performed by the business server 104 include a date closing business, a cash management business, and a fund management business. The day-to-day business is a business to finalize the transaction of the whole station by aggregating receipt / payment data with other affiliated companies and collating with cash as a closing process. The daily tightening work is roughly divided into two work processes, “temporary tightening processing” and “main tightening processing”. “Temporary tightening process” is the process of closing at the end of the evening window, and “final tightening process” is the tightening process for all payments at the station on the previous day, in the morning of the next business day. is there. Cash management operations include management of cash exchanges and payments to other stations, and cash management for temporary and final tightening. The cash accountant will manage cash transfer and delivery of cash, cash payment to the cash accountant, cash balance of cash management equipment (auto cashers, ATMs, cash machines), and cash transfer information. , Output forms and books necessary for cash management. The cash account manager manages the balance of the deposit and savings account opened at the bureau. There are two types of funds management operations: “fund planning operations” and “fund receipt and delivery management operations”. “Finance planning work” refers to the past cash accounting data of the bureau, and calculates the reference amount required for each bureau as cash reserve fund. The head office / branch office makes corrections and corrections to the standard height of each station on a monthly and weekly basis, and the fund base station formulates a daily delivery plan within the jurisdiction. Request delivery to a police carrier. “Funding / shipping management business” manages the sending information from the fund sending station, the receiving information of the arrival station, and the accident information at the time of receiving / shipping (not arrived, different destination, different sending amount, etc.). In addition, as a closing process for cash management operations, the daily cash / deposit and savings records are consistent with those documents, cash in kind, etc. Make sure you do.

  During business hours, the terminal 103 performs business by communicating with the business server. The network 105 connects the nodes so that they can communicate with each other, and can be used by appropriately selecting the Internet, an intranet, a LAN (Local Area Network), a telephone line, or the like.

  The software patches distributed by the distribution management server 101 include jobs and security patches. The job is distributed to each terminal every day. When the terminal 103 receives the job, it diagnoses its own security status and returns the diagnosis result to the distribution management server as an execution result. If the message is received when the terminal is turned off, the terminal is turned on, and the terminal is turned off after the job is completed. Security patches are created and distributed when security patches are updated. The terminal 103 receives this and updates the security.

  When the software patch is distributed, if the terminal 103 is not connected to the network because it is disconnected from the LAN cable or the like, the relay server 102 temporarily stores the software patch. When detecting that the terminal 103 is connected to the network, the relay server 102 transmits a software patch to the terminal 103. The detection may be a push type in which the relay server periodically searches for a terminal or a pull type in which a software patch is searched for when the terminal is connected to the network. Since software patches are stored in the storage device of the relay server 102, if there are a large number of files that have been saved without being transmitted, the free space of the storage device is reduced, and the relay server 102 It can cause a decline in ability. In this example, three jobs distributed daily and one security patch are distributed to 100,000 terminals for nine hours during the nighttime (23:00 to 8:00 the next day) when the user does not use the terminals. . In this case, in order to avoid overloading the network traffic, the 10,000 units can be accommodated in one destination group, distributed to 10 destination groups, and scheduled to be distributed every 10 minutes. To disperse. In addition, by adopting a configuration in which the arrangement of the database index is fixed, fragmentation of the software patch is suppressed, and deterioration in distribution is prevented. In the fixed index arrangement, the size is such that most software patches are stored without division.

  FIG. 2 shows a daily operation schedule in this system. Business hours vary depending on the site, but in this schedule, 8: 00-23: 00 is the business hours, and 23: 00-next day is 8:00.

  During business hours, the terminal 103 is turned on by a staff member who works at the base, and the terminal 103 performs business while communicating with the business server 104. Then, it is assumed that the terminals are turned off at the end of business, and that almost all terminals are turned off at 23:00.

  During the maintenance time, the distribution management server 101 creates a software patch for the job and distributes it to each terminal via the relay server 102. Upon receiving the job, the terminal 103 turns on the power, executes the job, returns the execution result to the distribution management server 101, and then turns off the power. When the terminal 103 is not connected to the network, the software patch for the terminal is stored in the storage device of the relay server 102.

  When the business time comes again, the staff turns on the terminal after the job execution, and the business is resumed. The terminal 103 that has not been connected to the network is also connected to the network at the start of business. When this is detected, the relay server 102 transmits a software patch to the terminal, and the terminal executes this and executes the execution result to the distribution management server. Reply to 101.

  After a while from the start of the business time, the distribution management server 101 creates a deletion script for instructing deletion of the software patch and distributes it to the relay server 102. When receiving this, the relay server 102 deletes the software patch stored in the storage device. As a result, the free capacity of the storage device is increased and the delay in distribution can be suppressed.

  The delivery timing of the deletion script can be set arbitrarily, but it is desirable that a period of time has passed since the start of the work, and most of the terminals are connected to the network for the work. In addition, it is desirable that the work is finished and before the next software patch is distributed. Further, since the operation server 104, the distribution management server 101, and the like are determined to operate according to time, it is possible to determine the deletion script distribution according to time.

  FIG. 3 shows the relay server 102. A software patch addressed to a terminal not connected to the network is stored in the storage device.

  Of the distribution files on the relay server, the reception command file is information for managing the command received from the higher system (distribution management server) for each job. The relay command file is job relay management information generated every time a command received from a higher system (distribution management server) is relayed to a lower system (terminal). The relay untransmitted file is job information that has not been transmitted to the lower system (terminal) for some reason in the relay command file. The job execution file is information on a job executed for each terminal. The job management file is job information managed by the distribution management system. For all distribution jobs such as daily jobs and security patches, the above-mentioned distribution files excluding relay untransmitted files exist. A relay unsent file exists for a job that has not been distributed to a lower system.

  Of these, the daily job distribution file is distributed every day. In this case, even if the terminal cannot receive the file of a certain day, there is no problem as long as the file of the next day can be received. Security patches are distributed only when there is an update, but this must be performed by the terminal.

  Therefore, the level to be deleted may be divided into software patches. For example, the distribution file for the daily job is set to the deletion level 1, and the distribution file for the security patch is set to the deletion level 2. When the relay server receives the level 1 deletion script, the relay server deletes all the distribution files of the level 1 software patch while leaving the level 2 software patch. When the level 2 deletion script is received, all the distribution files of the level 1 and level 2 software patches are deleted. The distribution management server distributes the deletion script of level 1 every day, and the deletion script of level 2 distributes once a month. As a result, software patches with low importance are quickly deleted to secure the storage capacity of the relay server 102, and software patches with high importance and low distribution frequency are reduced in frequency and the relay server is restarted. The opportunity to deliver can be increased.

  When the distribution management server 101 detects that the terminal is not executing the software patch, the distribution management server 101 can redistribute the software patch, and thus the terminal can delete the software patch that is essential for execution. That the terminal is not executing can be determined by not receiving the executable file. Then, after distributing the deletion script, the distribution management server distributes software patches that are required to be executed by the terminal and that have not received the execution file, among the software patches related to the distributed deletion script.

  As described above, according to the present invention, unnecessary software patches stored in the relay server can be deleted, and distribution delay can be suppressed.

101 ... Distribution management server 102 ... Distribution management relay server 103 ... Terminal 104 ... Business server 105 ... Network

Claims (5)

A management server that distributes software patches;
A plurality of terminals that receive and execute the software patch and return to the management server;
A relay server that relays the software patch;
A business server that distributes business jobs to the terminal;
A network that connects them so that they can communicate,
With
The relay server stores the software patch when the distribution destination terminal of the received software patch is not connected to the network, and when the distribution destination terminal is connected to the network, Deliver memorized software patches,
The management server distributes a deletion script for deleting the software patch to the relay server, and the relay server receives the deletion script and deletes the stored software patch. system. In claim 1,
In the time zone when the terminal and the business server are not communicating, the management server delivers the software patch,
The terminal operation management system, wherein the management server distributes the deletion script during a time zone in which the terminal and the business server are communicating. In claim 1 or claim 2,
The deletion script is divided into levels,
The software has a deletion level;
The terminal management operation system, wherein the relay server determines whether or not to perform the deletion for each software patch based on a level of the deletion script and a deletion level of the software patch. In claim 3,
The terminal management operation system, wherein the software patch includes a first software patch having a high distribution frequency and a low deletion level, and a second software patch having a low distribution frequency and a high deletion level. A distribution process in which the management server distributes software patches;
A relay process in which the relay server relays the software patch;
A plurality of terminals receive and execute the relayed software patch, and return to the management server, a software patch execution step,
A business job distribution step in which the business server distributes a job related to the business to the terminal;
The relay server stores the software patch when a terminal to which the received software patch is distributed is not connected to the network, and stores the software patch when the terminal to which the distribution is distributed is connected to the network. Redistribution process to distribute the software patches,
The management server distributes a deletion script for deleting the software patch to the relay server, and the relay server receives the deletion script and deletes the stored software patch;
A terminal management operation method comprising:

Images