JP2012234277A - Server device, memory management method and memory management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To efficiently use memory.SOLUTION: A server device 3 determines a data amount corresponding to a type of data which is executed in response to a request from a client 2, on the basis of used memory amount information 3b showing a data amount which is calculated from an execution history of data for each type of data which the client 2 acquires, and allocates the determined data amount to memory 3a. By this way, the data amount can be efficiently allocated to the memory 3a according to its capacity. Thus it is possible to reduce introduction cost of the server device 3 because the number of clients 2 connectable to one server device 3 can be increased and additional server device 3 is not necessary.

Description

  The present invention relates to a server device, a memory management method, and a memory management program.

  A financial institution such as a bank has a client for conducting a transaction. The client includes a passbook printer unit, a form reading unit, a palm vein authentication unit, a cash processing unit, a keyboard unit for inputting characters and numbers, and a control unit (client terminal) to which these units are connected. Yes. The client terminal controls the connected unit according to the operation input by the operator, and executes a predetermined process according to the information input from the connected unit. A plurality of such clients are connected from a client terminal to a server that processes and manages information related to transactions.

  For example, the operator causes the form reading unit connected to the client terminal to read the form, and the client terminal transmits image data of the read form to the server based on the operation input of the operator. The server can hold the image data of the received form. In addition, when the operator inputs an operation request for taking out image data of a desired form from the server to the client terminal, the client terminal notifies the server of the take-out request. When the server notifies the client terminal of the image data of the form based on the request from the client terminal, the operator can handle the image data of the desired form via the client terminal (see, for example, Patent Document 1).

  In addition, the number of client terminals connected to the server is determined based on the image data that requires the largest amount of memory among the image data of the forms handled by each client terminal in consideration of the memory usage of the server.

JP 2011-076407

  However, in such a method for determining the number of connected devices, if even one image data of a form handled by each client terminal is very large or if there is a large number of images handled at a time, this image data amount is used as a reference. Therefore, the number of client terminals to be connected to the server is limited.

  For this reason, when it is desired to process a large amount of forms, it is necessary to introduce a large number of servers and connect a client terminal to each server, resulting in an increase in server installation cost.

  The present invention has been made in view of these points, and an object thereof is to provide a server device, a memory management method, and a memory management program that efficiently use a memory.

  In order to achieve the above object, in the server device to which the client is communicably connected, the client uses the memory usage information representing the data amount calculated from the data execution history for each type of data acquired by the client. There is provided a server apparatus comprising: a request execution unit that specifies a data amount corresponding to a type of data to be executed in response to a request from a memory; and a memory management unit that allocates the data amount specified by the request execution unit to a memory. The

  In order to achieve the above object, a method and program for executing memory management similar to that of the server apparatus are provided.

  With such a server device, a memory management method, and a memory management program, the memory can be used efficiently.

It is a conceptual diagram of the server apparatus which concerns on 1st Embodiment. It is a figure for demonstrating the transaction system provided with the client and server which concern on 2nd Embodiment. It is a figure which shows the hardware structural example of the client and peripheral device which concern on 2nd Embodiment. It is a figure which shows the hardware structural example of the server which concerns on 2nd Embodiment. It is a block diagram which shows the function with which the server which concerns on 2nd Embodiment is provided. It is a figure which shows the information which hold | maintains the memory statistics information holding part of the server which concerns on 2nd Embodiment. It is a figure which shows the information which the memory statistics information holding part which concerns on 2nd Embodiment hold | maintains. It is a figure which shows the form information holding | maintenance part which hold | maintains the form information of the server which concerns on 2nd Embodiment. It is a flowchart (the 1) which shows the reading storage process of the image data of the form in the server which concerns on 2nd Embodiment. It is a flowchart (the 2) which shows the reading storage process of the image data of the form in the server which concerns on 2nd Embodiment. It is a sequence diagram in the case of the reading storage process of the image data of the form in the server which concerns on 2nd Embodiment. It is a flowchart (the 1) which shows the taking-out process of the image data of the form in the server which concerns on 3rd Embodiment. It is a flowchart (the 2) which shows the taking-out process of the image data of the form in the server which concerns on 3rd Embodiment. It is a flowchart (the 3) which shows the taking-out process of the image data of the form in the server which concerns on 3rd Embodiment. It is a sequence diagram in the case of the extraction process of the image data of the form in the server according to the third embodiment.

Hereinafter, embodiments will be described with reference to the drawings.
[First Embodiment]
FIG. 1 is a conceptual diagram of a server device according to the first embodiment.

  The server device can efficiently use the memory by previously specifying a data amount corresponding to the type of data to be executed in response to a request from the client and assigning the specified data amount to the memory. .

FIG. 1 shows an information processing system 1 including a client 2 and such a server device 3.
The client 2 causes the server device 3 to store the data acquired according to the operator's operation input. Further, the data stored in the server device 3 is extracted from the server device 3. The client 2 is, for example, a client terminal that constitutes a branch office system to which a form reading device is connected, and the operator causes the form reading device to read the image data of the form. The image data read by the form reading device is notified from the client terminal to the server device 3, and the server device 3 stores the image data. Alternatively, the operator notifies the server apparatus 3 of a request for transmitting desired image data from the client terminal, whereby the image data is notified from the server apparatus 3. Another example of the client 2 is a filing center terminal for storing documents.

  As shown in FIG. 1, the server device 3 includes a memory 3a, used memory amount information 3b, data configuration information 3c, request execution means 3d, memory management means 3e, and information management means 3f.

  The memory 3a can store data and is, for example, a storage device such as a RAM (Random Access Memory). Alternatively, not only such physical memory but also Java (registered trademark) VM (Virtual Machine) allocation may be used.

  The used memory amount information 3b represents the data amount calculated from the data execution history for each type of data acquired by the client 2. For example, when the client 2 is the client terminal of the client, the used memory amount information 3b is executed when the server device 3 executes a predetermined process on the image data of the form in response to a request from the client 2. The amount of data for each type of image data calculated based on the actual amount of image data.

  The data configuration information 3c represents the configuration of the data type for each execution type. For example, when there are a plurality of types of forms, the configuration of the type of image data to be executed when the server apparatus 3 executes a predetermined process on the image data of such a form is shown.

The request execution means 3d specifies the data amount corresponding to the type of data to be executed in response to the request from the client 2 from the used memory amount information 3b.
The memory management unit 3e allocates the data amount specified by the request execution unit 3d to the memory 3a.

  The information management means 3f updates the used memory amount information 3b based on the actual data amount of data executed in response to a request from the client 2. Further, the request execution means 3d is notified of information on the used memory amount information 3b and the data configuration information 3c.

A memory management method by the server device 3 having such a configuration will be described.
When the server 2 is notified of, for example, a data storage request or a data retrieval request from the client 2, the request execution means 3d determines the data amount corresponding to the type of data to be executed in response to the request as information management means. It is specified from the used memory amount information 3b via 3f.

The memory management means 3e confirms that the memory 3a has a sufficient capacity and allocates the specified data amount to the memory 3a.
Thereafter, the request execution unit 3d executes the processing based on the request from the client 2 on the data by appropriately reading the requested execution data into the allocated memory 3a.

  Further, the information management unit 3f can update the used memory amount information 3b by reflecting the actual data amount of the data executed in response to the request from the client 2 in the used memory amount information 3b. .

  As described above, the server device 3 changes the used memory amount information 3b representing the amount of data calculated from the data execution history for each type of data acquired by the client 2 to the type of data to be executed in response to a request from the client 2. The corresponding data amount is specified, and the specified data amount is assigned to the memory 3a. For this reason, it becomes possible to efficiently allocate the data amount to the capacity of the memory 3a. Therefore, it is possible to increase the number of clients 2 that can be connected to one server device 3, prevent an increase in the number of server devices 3, and suppress the introduction cost of the server device 3.

  Further, since the used memory amount information 3b reflects the actual data amount of the data executed in response to the request from the client 2, the used memory amount information 3b is updated as needed. The reliability of the data amount of the amount information 3b is improved.

[Second Embodiment]
In the second embodiment, assuming a financial institution in the first embodiment, a case where the information processing system 1 is a branch office system and the client 2 is a client terminal will be described more specifically as an example. . In particular, description will be made using image data of a form read by a form reading unit.

FIG. 2 is a diagram for explaining a transaction system including a client and a server according to the second embodiment.
In the store of the financial institution, as shown in FIG. 2, a branch office system 10 is constructed in which a plurality of clients 20 and a server 30 are connected to be able to communicate with each other.

  In such a branch office system 10, data storage and data retrieval requests can be made from the client 20 to the server 30. In addition, the server 30 can execute processing in response to a request from each client 20 to notify data stored and retrieved data.

Next, the client 20 and the server 30 that constitute the sales office system 10 constructed in the store will be described.
FIG. 3 is a diagram illustrating a hardware configuration example of the client and the peripheral device according to the second embodiment.

  As shown in FIG. 3, the client 20 includes a client terminal 20a. The client terminal 20a includes a touch panel 20b, a keyboard 20c, a mouse 20d, a form reading unit 20e, a passbook printer unit 20f, a cash processing unit 20g, and the like. Each unit is connected. A touch panel 20b, a keyboard 20c, a form reading unit 20e, a passbook printer unit 20f, and a cash processing unit 20g can be attached and detached from the client terminal 20a.

  The client terminal 20a controls each connected unit, is notified of information acquired by each unit, and executes processing based on the notified information. The client terminal 20a is also connected to the server 30 so as to be communicable.

  The client terminal 20a includes a CPU (Central Processing Unit) 20a1, a RAM 20a2, a communication unit 20a3, a graphic processing unit 20a4, an HDD (Hard Disk Drive) 20a5, an input interface 20a6, and an input / output control unit 20a7. These units are connected to each other by a bus 20a8.

The CPU 20a1 comprehensively controls the entire client terminal 20a by executing various programs stored in a storage medium such as the HDD 20a5.
The RAM 20a2 temporarily stores at least part of an OS (Operating System) and programs to be executed by the CPU 20a1. A data amount corresponding to data executed by the CPU 20a1 is allocated to the RAM 20a2. Various necessary data are also stored.

  The communication unit 20a3 is connected to, for example, a LAN (Local Area Network) so as to be communicable with the server 30 and a cash processing unit 20g described later, and can perform transmission / reception signal communication.

  As a specific example, the graphic processing unit 20a4 is a video card or a graphic board, and transmits image data to be displayed on the touch panel 20b to the monitor 20b1 of the touch panel 20b described later in accordance with a command from the CPU 20a1.

  The HDD 20a5 stores the OS and application programs on the client terminal 20a. The HDD 20a5 stores various data necessary for processing by the CPU 20a1.

  The input interface 20a6 receives information on the operation input from the touch detection unit 20b2, the mouse 20d, and the keyboard 20c of the touch panel 20b (described later) that has received the operation input from the customer, and notifies the CPU 20a1 of the information.

  A form reading unit 20e and a passbook printer unit 20f are connected to the input / output control unit 20a7. The form reading unit 20e and the passbook printer unit 20f exchange signals with the CPU 20a1 via the bus 20a8.

  The touch panel 20b includes a monitor 20b1 that is an LCD (Liquid Crystal Display) that displays an image based on the notified image information, and a touch detection unit 20b2 that receives an operation input by an operator.

The keyboard 20c notifies the CPU 20a1 of character information corresponding to the operation input by the operator via the input interface 20a6.
The mouse 20d notifies the input interface 20a6 of a signal corresponding to the operation of the operator. In response to the signal, processing corresponding to the movement and click of the cursor displayed on the monitor 20b1 is executed.

  The form reading unit 20e reads, for example, the image data of the form one by one with an overhead reader, or the images of a plurality of forms mixed by a form reading apparatus provided with an ADF (Auto Document Feeder). And so on. Such a form reading unit 20e reads the image data of the form in response to an operation input by the operator, and notifies the read image data to the CPU 20a1 via the input / output control unit 20a7.

  The bankbook printer unit 20f conveys the bankbook inserted by the operator to a predetermined position, and records the processing result of the process according to the execution instruction from the operator. The passbook printer unit 20f transports the passbook for which the processing result has been recorded and returns it to the operator.

  The cash processing unit 20g receives banknotes inserted from the banknote insertion / discharge port and counts the banknotes. Moreover, according to a predetermined | prescribed execution instruction of an operator, the banknote of the amount according to a process can be discharge | released from a banknote insertion / discharge port, respectively.

  The touch panel 20b, the keyboard 20c, the mouse 20d, the form reading unit 20e, the passbook printer unit 20f, and the cash processing unit 20g are controlled by the CPU 20a1, respectively.

FIG. 4 is a diagram illustrating a hardware configuration example of the server according to the second embodiment.
Since these are the same as the configurations held by the client terminal 20a in FIG. 3, detailed descriptions thereof are omitted.

  As shown in FIG. 4, the server 30 includes a CPU 30a, a RAM 30b, a communication unit 30c, a graphic processing unit 30d to which a monitor 30h is connected, an HDD 30e, a keyboard 30i, and an input interface 30f to which a mouse 30j is connected. These parts are connected to each other by a bus 30g.

Next, functions provided in such a server 30 will be described.
FIG. 5 is a block diagram illustrating functions provided in the server according to the second embodiment.
The server 30 specifies the data amount corresponding to the type of image data of the form to be executed in response to the request from the client terminal 20a in advance, and efficiently uses the memory unit by assigning the specified data amount to the memory unit. Is something that can be done.

  Such a server 30 includes a memory unit 31, a memory statistical information holding unit 32, and a form information holding unit 33. Furthermore, it includes a reception unit 34, a request execution unit 35, an information management unit 36, a memory management unit 37, a form information control unit 38, and a response unit 39.

The memory unit 31 is, for example, a shared memory, a JavaVM memory, or the like.
The memory statistical information holding unit 32 holds information regarding the memory unit 31 and image data of the form.

FIG. 6 is a diagram illustrating information stored in the memory statistical information storage unit of the server according to the second embodiment.
The memory statistical information holding unit 32 holds used memory amount information 32a, form data amount information 32b, item configuration information 32c, and memory state information 32d.

FIG. 7 is a diagram illustrating information held by the memory statistical information holding unit according to the second embodiment.
7A to 7D show used memory amount information 32a, form data amount information 32b, item configuration information 32c, and memory state information 32d, respectively.

  As shown in FIG. 7A, the used memory amount information 32a is the used memory amount (average) for each of the memories 1 to 3 in the memory unit 31 for each form type. The forms are numbered 1, 2, 3,..., N for each form type. For example, the form type “form 1” uses a data amount (average) of “300 KB” in the memory 1 and a data amount (average) of “50 KB” in the memory 2.

  The form data amount information 32b includes, for the memories 1 to 3, the number of times (frequency) the image data for each form type has been executed so far, the maximum data amount (maximum), the minimum data amount (minimum), and the average data amount ( Average). FIG. 7B shows only the case of the memory 1 as an example. According to this, “Form 2” has been executed “12000 times” so far, of which the maximum data amount is “500 KB”, the minimum data amount is “100 KB”, and the average data amount is “250 KB”. It is. The form data amount information 32b reflects the actual amount of data obtained by actually executing the image data as needed. The average data amount of the form data amount information 32b is reflected in the average data amount of the used memory amount information 32a.

  The item configuration information 32c is item configuration data for each transaction type, as shown in FIG. The transaction type is for classifying the configuration of the image data type of the form. Specifically, for example, when opening a bank account, two types of forms (documents), that is, an application form and an identification card (license etc.) are required one by one. In this case, an application form is used as “form 1” and an identity confirmation (copy) is used as “form 2” one by one. In the case of FIG. 7C, the transaction type item “a” is composed of “form 1” (one sheet) with a form size A4 and “form 2” (one sheet) with A3. The transaction type item “b” is composed of “form 2” (two sheets) with a form dimension A3 and “form 3” (one sheet) with A4. Such a transaction type is notified from the client terminal 20a to the server 30 together with a desired process execution request.

  As shown in FIG. 7D, the memory status information 32d is information on the maximum upper limit of each memory type and the current used memory amount according to the memory type of the memory unit 31. For example, the maximum memory used by “Memory 1”, “Memory 2”, and “Memory 3” is “3000 MB”, “2000 MB”, and “1000 MB”, respectively. Further, the current used memory amounts are “300 MB”, “800 MB”, and “500 MB”, respectively.

The memory statistical information holding unit 32 holds such information.
The form information holding unit 33 holds the image data of the form based on the storage request from the client terminal 20a.

FIG. 8 is a diagram illustrating a form information holding unit that holds form information stored in the server according to the second embodiment.
As shown in FIG. 8, the form information holding unit 33 holds image data of the form for each item configuration described with reference to FIG. For example, in FIG. 8A, “Form 1” (one sheet) and “Form 2” (one sheet) are held as a case a. In FIG. 8B, “Form 2” (two sheets) and “Form 3” (one sheet) are held as the case b.

The form information holding unit 33 holds such information.
The accepting unit 34 accepts a data storage request from each client terminal 20 a and a data retrieval request held by the server 30. For example, the transaction type information is received together with a request to store the image data of the form read from the client terminal 20a in the server 30. In addition, the client terminal 20a accepts transaction type information together with a request to retrieve image data of a desired form from the server 30. The receiving unit 34 outputs a request received from the client terminal 20 a to the request execution unit 35.

  The request execution unit 35 executes processing based on the request received from the reception unit 34. First, when a storage request for image data of a form is received from the reception unit 34, a notification request for the amount of image data is sent from the memory statistical information holding unit 32 to the information management unit 36 based on the transaction type. The request execution unit 35 notifies the memory management unit 37 of an allocation request for the memory unit 31 based on the notified data amount. The request execution unit 35 notifies the form information control unit 38 of a storage request for the image information read into the memory unit 31 to the form information holding unit 33.

  When receiving a request for extracting image data from the receiving unit 34, the request execution unit 35 notifies the information management unit 36 of a notification request for data of the case configuration from the memory statistical information holding unit 32 based on the transaction type. The item configuration data notified from the information management unit 36 is notified to the client terminal 20a from the response unit 39 described later. Similarly to the case of the storage request, the memory management unit 37 is notified of an allocation request for the memory unit 31 based on the data amount. Then, the image data read into the memory unit 31 is transmitted from the response unit 39 to the client terminal 20a.

  The information management unit 36 notifies the request execution unit 35 of the data in the memory statistical information holding unit 32 based on the request from the request execution unit 35. When a predetermined process is executed on the image data of the form, the actual data amount of the image data is reflected in the form data amount information 32b of the memory statistical information holding unit 32 and updated.

  Based on a request from the request execution unit 35, the memory management unit 37 allocates a predetermined amount of data to the memory unit 31 as a used memory amount, and when the predetermined processing related to the data is completed, the usage allocated to the memory unit 31 Free up memory.

  The form information control unit 38 causes the form information holding unit 33 to store the form image data read into the memory unit 31 based on the request from the request execution unit 35, and the form information data of the form information holding unit 33. The data is read into the memory unit 31.

The response unit 39 returns data to the client terminal 20a based on the request from the request execution unit 35.
Next, a process for storing the image data of the form in response to a request from the client terminal 20a performed by the server 30 will be described.

9 and 10 are flowcharts showing the reading and storing process of the form image data in the server according to the second embodiment.
[Step S <b> 10] The request execution unit 35 acquires from the reception unit 34 the storage request for the image data of the form received from the client terminal 20 a and the transaction type information.

[Step S <b> 11] The request execution unit 35 notifies the information management unit 36 of a notification request for the data of the item configuration based on the transaction type and the data amount of the image data corresponding to the item configuration.
The information management unit 36 identifies the item configuration data corresponding to the transaction type from the item configuration information 32c of the memory statistical information holding unit 32, and notifies the request execution unit 35 of the data amount of the image data of the form constituting the item. To do.

The request execution unit 35 acquires the data amount of the item configuration data corresponding to the transaction type and the image data of each form.
[Step S12] The request execution unit 35 sets 1 to the form i.

[Step S13] The request execution unit 35 determines the presence or absence of image data corresponding to the form i in the image data of the form acquired in step S11.
As a result of the determination, if there is form image data corresponding to the form i, the process proceeds to step S14; otherwise, the process proceeds to step S20 (FIG. 10).

[Step S14] The request execution unit 35 sets the data amount of the image data of the form i as the used memory amount of the form i.
[Step S15] The request execution unit 35 notifies the memory management unit 37 of a request for determining whether or not the memory amount of the image data of the form i in Step S14 is empty.

  As a result of the determination by the memory management unit 37, if the used memory amount acquired in step S14 is free, the process proceeds to step S16, and if there is no free space, the process proceeds to step S25 (FIG. 10).

[Step S <b> 16] The memory management unit 37 allocates the used memory amount of Step S <b> 14 to the memory unit 31.
[Step S <b> 17] The memory management unit 37 determines whether the used memory amount is normally allocated to the memory unit 31.

As a result of the determination, when the allocation of the used memory amount is normally performed, the process proceeds to step S18, and when it is not normally performed, the process proceeds to step S25 (FIG. 10).
[Step S18] The request execution unit 35 notifies the information management unit 36 of an update request for the memory state information 32d of the memory statistical information holding unit 32 based on the used memory amount allocated in step S16, and the information management unit 36 performs the update. Based on the request, the memory status information 32d of the memory statistical information holding unit 32 is updated.

[Step S19] The request execution unit 35 determines whether there is any other image data of the form corresponding to the form i.
As a result of the determination, if there is another image data of the form corresponding to the form i, the process proceeds again to step S14, and if there is no other image data, the process proceeds to step S20 (FIG. 10).

[Step S20] The request execution unit 35 adds 1 to the form i and sets the form i + 1.
[Step S21] The request execution unit 35 determines whether i of the set form i is N or less.

As a result of the determination, if it is N or less, the process proceeds again to step S12, and if it exceeds N, the process proceeds to step S22.
[Step S <b> 22] When the request execution unit 35 notifies the form information control unit 38 of a storage request for the case configuration data, the form information control unit 38 stores the case configuration data in the form information holding unit 33.

  [Step S23] The request execution unit 35 is notified of the image data of the form from the client terminal 20a, and causes the memory unit 31 to read the image data. Then, it notifies the form information control unit 38 of a storage request for the image data of the form read into the memory unit 31.

The form information control unit 38 stores the image data of the form from the memory unit 31 in the case configuration of the form information holding unit 33 based on the storage request.
[Step S24] The request execution unit 35 notifies the information management unit 36 of an update request for the form data amount information based on the actual data amount of the form image data read into the memory unit 31.

Based on the update request, the information management unit 36 reflects the actual data amount in the form data amount information 32b and updates the form data amount information 32b.
[Step S25] The request execution unit 35 notifies the client terminal 20a from the response unit 39 that the request from the client terminal 20a is an error.

[Step S <b> 26] The request execution unit 35 notifies the memory management unit 37 of a request to release the used memory amount allocated to the memory unit 31.
The memory management unit 37 releases the memory amount of the memory unit 31.

  [Step S27] The request execution unit 35 notifies the information management unit 36 of an update request for the memory state information 32d of the memory statistical information holding unit 32 based on the used memory amount allocated in step S26, and the information management unit 36 performs the update. Based on the request, the memory status information 32d of the memory statistical information holding unit 32 is updated.

Next, a specific example of such image data reading and storing processing by the server 30 will be described with reference to a sequence diagram.
FIG. 11 is a sequence diagram in the case of reading and storing processing of image data of a form in the server according to the second embodiment.

[Step S <b> 30] The client terminal 20 a notifies the server 30 of a storage request in which the transaction “a” is composed of the forms 1 and 2 read by the form reading unit 20 e.
When accepting the transaction type, the accepting unit 34 of the server 30 notifies the request executing unit 35 (FIG. 9: Step S10).

  [Step S31] The request execution unit 35 notifies the information management unit 36 of a notification request for the data of the case configuration (case a) based on the transaction type and the data amount of the image data of the forms 1 and 2 of the case configuration (FIG. 9: Step S11).

  [Step S32] The information management unit 36 identifies the data of the case configuration (case a) corresponding to the transaction type from the case configuration information 32c of the memory statistical information holding unit 32, and the forms 1 and 2 constituting the case a are identified. The request execution unit 35 is notified of the amount of image data.

  The request execution unit 35 stores the data of the item structure (item a) corresponding to the transaction type, the amount of image data of the form 1 (memory 1: 500 KB, memory 2: 50 KB), and the amount of image data of the form 2 (memory). 1: 250 KB) (FIG. 9: Step S11).

  [Step S33] The request execution unit 35 first notifies the memory management unit 37 of an allocation request for the used memory amount by using the acquired amount of image data of the form 1 as the used memory amount (FIG. 9: Steps S12 to S12). S14).

  [Step S34] The memory management unit 37 determines that there is sufficient space in the memory unit 31, and normally allocates the used memory amount corresponding to the notified data amount of the form 1 to the memory unit 31 (FIG. 9). : Steps S15 to S17).

  [Step S35] The request execution unit 35 notifies the information management unit 36 of an update request for the memory status information 32d of the memory statistical information holding unit 32 based on the used memory amount of the image data of the form 1, and the information management unit 36 Based on the update request, the memory status information 32d of the memory statistical information holding unit 32 is updated (FIG. 9: Step S18).

Note that the same processing as steps S33 to S35 is executed for the form 2 as well.
[Step S36] The request execution unit 35 notifies the form information control unit 38 of a storage request for the data of the case configuration (FIG. 10: Step S22).

[Step S37] The form information control unit 38 stores the data of the case a in the form information holding unit 33 (FIG. 10: step S22).
[Step S38] The client terminal 20a notifies the server 30 of the image data of the forms 1 and 2.

When receiving the image data, the receiving unit 34 of the server 30 notifies the request execution unit 35 (FIG. 10: step S23).
[Step S39] The request execution unit 35 reads the image data of the forms 1 and 2 into the memory unit 31 (FIG. 10: Step S23).

[Step S40] The storage request of the image data of the forms 1 and 2 read into the memory unit 31 is notified to the form information control unit 38 (FIG. 10: step S23).
[Step S41] Based on the storage request, the form information control unit 38 stores the image data of the forms 1 and 2 in the case configuration of the form information holding unit 33 (FIG. 10: step S23).

  [Step S42] The request execution unit 35 notifies the information management unit 36 of an update request for the form data amount information 32b based on the actual data amount of the image data of the forms 1 and 2 read into the memory unit 31.

  Based on the update request, the information management unit 36 reflects the actual data amount of the image data of the forms 1 and 2 in the form data amount information 32b to update the form data amount information 32b (FIG. 10: Step S24).

  [Step S <b> 43] The request execution unit 35 notifies the memory management unit 37 of a request to release the used memory amount of the image data of the forms 1 and 2 allocated to the memory unit 31. The memory management unit 37 releases the memory amount of the memory unit 31 (FIG. 10: step S26).

[Step S44] The memory management unit 37 releases the memory capacity of the memory unit 31 (FIG. 10: step S26).
[Step S45] The request execution unit 35 notifies the information management unit 36 of an update request for the memory status information 32d of the memory statistical information holding unit 32 based on the amount of used memory of the image data of the forms 1 and 2, and the information management unit 36 Updates the memory status information 32d of the memory statistical information holding unit 32 based on the update request (FIG. 10: step S27).

  As described above, the server 30 uses the memory usage information 32a representing the data amount calculated from the execution history of the image data for each type of image data of the form read by the form reading unit 20e by the client terminal 20a, from the client terminal 20a. A data amount corresponding to the type of image data of the form to be stored in response to the reading and storing request is specified, and the specified data amount is assigned to the memory unit 31. Therefore, it is possible to efficiently allocate the data amount of the form image data to the capacity of the memory unit 31. Therefore, the number of client terminals 20a that can be connected to one server 30 can be increased, and the server 30 can be prevented from being added and the introduction cost of the server 30 can be suppressed.

  Further, since the actual data amount of the image data of the form executed in response to the reading / storage request from the client terminal 20a is reflected and updated in the used memory amount information 32a, the reliability of the data amount of the used memory amount information 32a is updated. Will improve. Therefore, the used memory amount can be more appropriately allocated to the memory unit 31.

[Third Embodiment]
In the third embodiment, a case will be described in which the client terminal 20a of the client 20 notifies the server 30 of an extraction request in the second embodiment.

In the third embodiment, the branch office system 10 including the client 20 and the server 30 according to the second embodiment is used (FIGS. 2 to 9).
A process for taking out image data of a form in response to a request from the client terminal 20a performed in the server 30 will be described.

FIG. 12 to FIG. 14 are flowcharts showing the process of extracting form image data in the server according to the third embodiment.
In addition, the same step number is attached | subjected to what performs the same process as the process performed with the flowchart of FIG. 9, FIG. 10, and they are demonstrated easily.

[Step S <b> 50] The request execution unit 35 acquires from the reception unit 34 a request to retrieve a case composed of an arbitrary form notified from the client terminal 20 a.
[Step S <b> 51] The request execution unit 35 notifies the form information control unit 38 of a notification request for data of the item configuration to be extracted.

The form information control unit 38 identifies the notified item configuration data from the form information holding unit 33 and notifies the request execution unit 35 of the data.
The request execution unit 35 transmits the item configuration data to the client terminal 20a.

[Steps S <b> 11 to S <b> 21] An amount of used memory corresponding to the data amount of the image data of the form constituting the item to be extracted is allocated to the memory unit 31.
[Step S52] The request execution unit 35 sets the form i = 1.

[Step S53] The request execution unit 35 determines whether or not the form i is included in the item configuration to be extracted.
As a result of the determination, if the form i to be taken out includes the form i, the process proceeds to step S54, and if not, the process proceeds to step S57.

  [Step S <b> 54] The form information control unit 38 extracts the image data of the form i from the form information holding unit 33 in response to a request from the request execution unit 35. Then, the image data of the retrieved form i is output to a predetermined location assigned in the memory unit 31.

[Step S55] The request execution unit 35 transmits the image data of the form i output to a predetermined location in the memory unit 31 from the response unit 39 to the client terminal 20a.
[Step S56] The request execution unit 35 determines whether there is another image data of the form corresponding to the form i.

As a result of the determination, if there is other image data of the form corresponding to the form i, the process proceeds again to step S54, and if there is no other image data, the process proceeds to step S57.
[Step S57] The request execution unit 35 adds 1 to the form i and sets the form i + 1.

[Step S58] The request execution unit 35 determines whether i of the set form i is N or less.
As a result of the determination, if i is N or less, the process proceeds to step S53 again. If i exceeds N, the process proceeds to step S24 (FIG. 14).

[Steps S24, S26, S27] The form data amount information 32b is updated, the used memory amount is released in the memory unit 31, and the memory state information 32d is updated.
[Step S25] The client terminal 20a is notified that an error has occurred.

Next, a specific example of such image data extraction processing by the server 30 will be described with reference to a sequence diagram.
FIG. 15 is a sequence diagram in the case of a form image data extraction process in the server according to the third embodiment.

In addition, the same step number is attached | subjected to what performs the same process as the process performed in the sequence diagram of FIG. 11, and they are demonstrated easily.
[Step S <b> 60] The client terminal 20 a notifies the server 30 of a request to retrieve the item a composed of the forms 1 and 2.

When accepting the take-out request, the accepting unit 34 of the server 30 notifies the request executing unit 35 (FIG. 12: step S50).
[Step S61] A notification request for data of the configuration of the item a to be extracted is sent to the form information control unit 38 (FIG. 12: Step S51).

  [Steps S62, S63] The form information control unit 38 identifies the notified data of the item configuration from the form information holding unit 33, and notifies the request execution unit 35 of the data (FIG. 12: step S51).

[Step S64] The request execution unit 35 transmits the item configuration data to the client terminal 20a (FIG. 12: Step S51).
[Steps S <b> 31 to S <b> 35] The request execution unit 35 acquires the data of the configuration of the item a to be extracted and the amount of image data configuring the item a from the memory statistical information holding unit 32 via the information management unit 36. Further, the memory management unit 37 is caused to allocate the used memory amount to the memory unit 31 based on the data amount. The request execution unit 35 causes the information management unit 36 to update the memory state information 32d according to the allocated memory unit 31.

  [Steps S65, S66] The form information control unit 38 extracts the image data of the form 1 from the form information holding unit 33, and outputs the extracted image data of the form 1 to a predetermined location assigned in the memory unit 31 (FIG. 13: Step S54).

  [Steps S67, S68] The request execution unit 35 transmits the image data of the form 1 output to a predetermined location in the memory unit 31 from the response unit 39 to the client terminal 20a (FIG. 13: Step S55).

Note that the same processing as steps S65 to S68 is executed for the form 2 and the image data of the form 2 is transmitted to the client terminal 20a.
[Steps S42 to S45] The request execution unit 35 causes the information management unit 36 to update the forms 1 and 2 of the form data amount information 32b, and causes the memory management unit 37 to release the used memory amount. Then, the request execution unit 35 causes the memory management unit 37 to update the memory in which the forms 1 and 2 of the memory state information 32d have been read.

  As described above, the server 30 uses the memory usage information 32a representing the data amount calculated from the execution history of the image data for each type of image data of the form read by the form reading unit 20e by the client terminal 20a, from the client terminal 20a. A data amount corresponding to the type of image data of the form to be extracted in response to the extraction request is specified, and the specified data amount is assigned to the memory unit 31. Therefore, it is possible to efficiently allocate the data amount of the form image data to the capacity of the memory unit 31. Therefore, the number of client terminals 20a that can be connected to one server 30 can be increased, and the server 30 can be prevented from being added and the introduction cost of the server 30 can be suppressed.

  In the take-out process, the actual data amount of the image data of the form executed in response to the reading / storage request from the client terminal 20a is updated and reflected in the used memory amount information 32a. The reliability of the data volume is improved. Therefore, the used memory amount can be more appropriately allocated to the memory unit 31.

  The above processing functions can be realized by a computer. In that case, a program describing the processing contents of the functions that the server device 3 and the server 30 should have is provided. By executing the program on a computer, the above processing functions are realized on the computer. The program describing the processing contents can be recorded on a computer-readable recording medium. Examples of the computer-readable recording medium include a magnetic storage device, an optical disk, a magneto-optical recording medium, and a semiconductor memory. Magnetic storage devices include hard disk devices (HDD), flexible disks (FD), magnetic tapes, and the like. Optical discs include DVD (Digital Versatile Disc), DVD-RAM, CD (Compact Disc) -ROM (Read Only Memory) / RW (ReWritable), and the like. Magneto-optical recording media include MO (Magneto-Optical disk).

  When distributing the program, for example, a portable recording medium such as a DVD or a CD-ROM in which the program is recorded is sold. It is also possible to store the program in a storage device of a server computer and transfer the program from the server computer to another computer via a network.

  The computer that executes the program stores, for example, the program recorded on the portable recording medium or the program transferred from the server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. In addition, each time a program is transferred from a server computer connected via a network, the computer can sequentially execute processing according to the received program.

  Further, at least a part of the above processing functions can be realized by an electronic circuit such as a DSP (Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), or a PLD (Programmable Logic Device).

DESCRIPTION OF SYMBOLS 1 Information processing system 2,20 Client 3 Server apparatus 3a Memory 3b Memory usage information 3c Data structure information 3d Request execution means 3e Memory management means 3f Information management means 10 Branch office system 20a Client terminal 20a1, 30a CPU
20a2, 30b RAM
20a3, 30c Communication unit 20a4, 30d Graphic processing unit 20a5, 30e HDD
20a6, 30f Input interface 20a7 Input / output control unit 20a8, 30g Bus 20b Touch panel 20b1, 30h Monitor 20b2 Touch detection unit 20c, 30i Keyboard 20d, 30j Mouse 20e Form reading unit 20f Passbook printer unit 20g Cash processing unit 30 Server 31 Memory unit 32 Memory statistics information holding unit 32a Memory usage information 32b Form data amount information 32c Item configuration information 32d Memory status information 33 Form information holding unit 34 Reception unit 35 Request execution unit 36 Information management unit 37 Memory management unit 38 Form information control unit 39 Response Part

Claims (6)

In the server device to which the client is communicably connected,
A request for specifying the amount of data corresponding to the type of data to be executed in response to a request from the client, from used memory amount information representing the amount of data calculated from the execution history of the data for each type of data acquired by the client Execution means;
Memory management means for allocating the amount of data specified by the request execution means to a memory;
The server apparatus characterized by having. The request execution means includes the data amount of each type of data to be executed in response to the request based on the execution type from the client, from the data configuration information representing the configuration of the data type for each execution type together with the memory usage information Identify each
The server device according to claim 1, wherein:   2. The server apparatus according to claim 1, further comprising information management means for updating the used memory amount information based on an actual data amount of data executed in response to a request from the client.   4. The server apparatus according to claim 3, wherein the calculated data amount of the used memory amount information is an average value of an actual data amount of the executed data. In the memory management method of the server device to which the client is connected,
Data corresponding to the type of data to be executed in response to a request from the client, from the used memory amount information representing the amount of data predicted from the execution result of the data for each type of data acquired by the client Identify the quantity,
Memory management means allocates the amount of data specified by the request execution means to a memory,
And a memory management method. In the memory management program of the server device to which the client is connected,
On the computer,
For each type of data acquired by the client, from the used memory amount information representing the amount of data predicted from the execution performance of the data, the data amount corresponding to the type of data executed in response to a request from the client is specified,
Assigning the specified amount of data to the memory;
A memory management program for executing a process.

Images