JP4368718B2 - Book lending history management method, program, storage medium - Google Patents

Description

  The present invention relates to a book lending history management method, a library system, and a user terminal.

Techniques for managing the lending history of books have been proposed. For example, a non-contact ID card incorporating a non-contact transmission mechanism capable of identifying a user and recording / updating a use history in a non-contact manner, a non-contact ID card reader / writer capable of reading and writing to the non-contact ID card, books An RF-ID book classification label having an integrated circuit chip and an antenna attached to either the front cover, the back cover, the back cover, or a page bound in a book, and data of the RF-ID book classification label In a library system that is equipped with an RF-ID reader that reads a book in a contactless manner, and an entrance / exit gate device that can be used for preventive purposes such as taking out a book without permission. B) When a user passes through an entry / exit gate device together with a book with an RF-ID book classification label, the RF-ID book classification label of the book is displayed. Recorded on the non-contact ID card, the non-contact ID card reader / writer for reading the user's non-contact ID card lending history, the inspection means for checking the read lending history, and the non-contact ID card Automatic book lending management provided with a non-contact ID card read / write device for writing to update a certain lending history, a memory for a lending lending management means for recording the renewed lending history, and a monitor device capable of displaying lending process progress (B) a return box having a mechanism capable of receiving a returned book, an RF-ID reader for reading a registration number of an RF-ID book classification label of the returned book, and a use for returning the book The contactless ID card that reads the loan history of the contactless ID card of the person and inquires the registered number to update the return information of the loan history Automatic book return management system consisting of de reading and writing apparatus, such as a higher (b) and library system characterized by comprising (b) (see Patent Document 1) has been proposed.
Japanese Patent Laid-Open No. 10-275183

  In the prior art, there has been proposed a method for storing a book lending history in a user's IC card or the like. However, since the information storage capacity of the IC card is limited, the amount of lending history that can be accumulated is limited. There was a problem. On the other hand, when managing the loan history of individual users in a library or the like, it is difficult to manage the loan history as personal information while considering security.

  Accordingly, the present invention has been made in view of the above problems, and provides a book lending history management method, a library system, and a user terminal that can manage lending history information in consideration of privacy protection regardless of the amount of data. The main purpose is to do.

The book lending history management method of the present invention that solves the above problems is a book lending history management method in a network system that includes a terminal and a library system connected to the terminal via a network, A process in which the library system acquires lending information including at least attribute information of a lending book accompanying lending a book to a user, and obtains the public key of the user from a user database storing user information ; The user's lending information is encrypted with the public key to generate lending history information, and the lending history information stored in the lending history database is stored in the lending history database. And processing to transmit to the terminal via the terminal, the terminal accepts a browsing request for loan history information via the input unit And checking the attribute information of the terminal against the processing authority table for each computer, which is stored in the storage unit of the terminal, and determines whether the browsing history information can be viewed or stored for each attribute of the terminal. Processing for determining whether or not the loan history information can be browsed or stored, processing for acquiring the user authentication information from the user authentication medium, and signature verification based on the acquired user authentication information , A process for determining whether or not the loan history information can be viewed or stored in the user, a first flag of a determination result regarding whether or not the loan history information can be viewed or stored in the terminal, and the loan history information of the user The process of storing in the memory the second flag of the determination result relating to whether or not browsing or saving is possible, and both the first and second flags can be viewed or saved. And the process of acquiring the loan history information from the library system via the network, and decrypting the acquired loan history information with a secret key included in the acquired user authentication information And a process of outputting the decrypted lending history information to an output unit .

Further, the program of the present invention is a program for causing a terminal to execute processing necessary for management of a book lending history, the terminal receiving a book lending history browsing request via the input unit, and the terminal The attribute information of the terminal is checked against the processing authority table for each computer, which is stored in the storage unit of the terminal, and whether or not the browsing history information can be viewed or stored is determined for each terminal attribute. Alternatively, a process for determining whether or not storage is possible, a process for acquiring user authentication information from the user authentication medium, and signature verification based on the acquired user authentication information are performed, and the user lends. A process for determining whether or not history information can be browsed or stored, a first flag of a determination result regarding whether or not the rental history information can be viewed or stored in the terminal, and the user The second flag of the determination result regarding whether or not the loan history information can be browsed or stored, and when the first and second flags indicate that browsing or saving is possible. A process of acquiring loan history information from a library system that is communicably connected to a terminal and stores information on the book loan history, and the acquired loan history information is included in the acquired user authentication information. A process of decrypting with a key and a process of outputting the decrypted loan history information to an output unit are executed.

In addition, the storage medium of the present invention includes a process for accepting a request for browsing a book lending history via an input unit to the terminal, and attribute information of the terminal stored in the lending history information stored in the storage unit of the terminal. Checking whether or not browsing or saving is possible for each terminal attribute by checking the processing authority table for each computer and determining whether or not the loan history information can be browsed or saved on the terminal and the user authentication medium, Processing for acquiring the authentication information, processing for verifying the signature based on the acquired authentication information of the user, determining whether or not the user can view or store the loan history information, and loan history information in the terminal The first flag of the determination result regarding whether or not the user can browse or store the data and the second flag of the determination result regarding whether the user can view or store the loan history information From the library system that stores information on the book lending history and is connected to the terminal so as to be able to communicate with the terminal when the first and second flags indicate that browsing or saving is possible. , A process of acquiring the loan history information, a process of decrypting the acquired loan history information with a secret key included in the acquired user authentication information, and outputting the decrypted loan history information to the output unit And storing a program for executing the process.

  In addition, the problems disclosed by the present application and the solutions thereof will be clarified by the embodiments of the present invention and the drawings.

  According to the present invention, it is possible to manage lending history information in consideration of privacy protection regardless of the amount of data.

  Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a schematic diagram of a book lending history management system 5 in the present embodiment. The book lending history management system 5 here includes at least the library system 0032 and the user terminal 50 (the window terminal 0020, the library window terminal 0021, and the resident terminal 0022) in the present invention, and further includes the use environment setting system 0030 and the key. A network configuration including the generation system 0031 is illustrated. However, not only such a network configuration example but also an example in which the functions of the library system of the present invention are aggregated in any one of the above systems and the functions of the user terminal of the present invention are aggregated in any of the above terminals. it can.

  The library system 0032 of the present invention is a server computer, stores a program 101 for realizing the function of executing the book lending history management method of the present invention in the memory 102, and reads and executes it by the control unit 103 including a CPU as an arithmetic unit. . In addition, the library system 0032 is connected to an external device such as a user terminal, the use environment setting system 0030, and the key generation system 0031 through a network 0700 such as a LAN or the Internet or a firewall 0750, and executes data exchange. An I / O unit 104 is provided. Further, the library system 0032 can use a storage device 105 such as a hard disk device storing various databases 0400 to 0600.

  In the following, functional units that the library system 0032 configures and holds as a program will be described. The library system 0032 obtains lending information including at least lending book attribute information accompanying lending the book to the user, and obtains the public key of the user from the user database 0400 storing the user information. An information acquisition unit 106 is provided. In addition, a history information generation unit 107 is provided that generates rental history information by encrypting the user's loan information with the public key and stores the information in the loan history database 0500.

  On the other hand, as described above, the user terminal 50 that implements the book lending history management method of the present invention together with the library system 0032 is any one of the window terminal 0020, the library window terminal 0021, and the resident terminal 0022, and includes the network 0700, As long as it is possible to exchange data with the library system 0032, the use environment setting system 0030, the key generation system 0031, etc. through the Internet 0770 or through an appropriate server or the like, the installation location is not limited. Similarly to the library system 0032, the user terminal 50 is a computer, stores the program 111 in the memory 112, and reads and executes it by the control unit 113 including a CPU as an arithmetic unit. In addition, the I / O unit 114 is connected to the library system 0032, the use environment setting system 0030, the key generation system 0031, and the like to execute data exchange.

  Such a user terminal 50 configures and holds a program for realizing the book lending history management method of the present invention together with the library system 0032 as, for example, the following functional units. The user terminal 50 includes an authentication information acquisition unit 116 that acquires authentication information including at least the user's private key from the user's authentication medium 0010. In addition to performing user authentication based on the authentication information, a decryption unit 117 is provided for extracting the corresponding loan history information from the loan history database 0500 for the authenticated user and decrypting it with the secret key. . Further, an output processing unit 118 is provided for outputting the decrypted rental history information to an output interface such as a display device.

  Also, the attribute information of the user terminal 50 is checked against a computer-specific processing authority table 119 that determines whether the browsing history information can be viewed or stored for each computer attribute, and the browsing history information on the user terminal 50 is viewed or stored. It is possible to include a first flag determination unit 120 that determines whether or not this is possible.

  Further, the authentication information acquired from the authentication medium 0010 at the time of the user authentication in the user terminal 50 is each information of a user attribute of the user, a private key, and an electronic certificate, and based on these authentication information A second flag determination unit 121 that executes at least signature verification and determines whether or not the user can view or store the loan history information can be provided.

  Further, the first flag of the determination result regarding whether or not the loan history information can be browsed or stored in the user terminal 50 and the second flag of the determination result regarding whether or not the user can browse or store the loan history information are stored in the memory. 112, when both the first and second flags can be viewed or stored, extraction of loan history information from the loan history database 0500, decryption of the loan history information with a secret key, An authority determination unit 122 that determines that at least one of the process of outputting the decrypted loan history information to the output interface and storing the loan history information in the user terminal 50 can be executed can be provided.

  In addition, the use environment setting system 0030 shown in this embodiment is a system with which the city hall in the location of the citizen who is a user is provided, for example. Then, for the resident card as the authentication medium 0010, a user application is generated by setting a user number for the citizen along with the service of the book lending history management method of the present invention, and a card application including this user information Is set in the resident card. Also, user information is registered in the library system 0032 (user database 0400).

  Further, the key generation system 0031 in the present embodiment generates a secret key and a public key for each user, for example. The generated public key is stored in the library system 0032 (user database 0400), while the secret key is stored in the card application in the resident card as the authentication medium 0010.

  An authentication medium 0010 such as a resident card used by a user stores a card application 0011 and a personal authentication card application 0012 as shown in FIG. The card application 0011 stores the above-described user number and secret key. The personal authentication card application 0012 includes certificate information for use in personal authentication and an in-card application. If various applications in the authentication medium 0010 realize all or part of the functions of the user terminal 50 of the present invention, the authentication medium 0010 itself can be used as the user terminal 50.

  Next, a database that can be used by the library system 0032 of the present embodiment, a database of the usage environment setting system 0030, and a database of the key generation system 0031 will be described. The use environment setting system database 0200 is a database that stores user information generated by the use environment setting system 0030. As shown in FIG. 3A, for example, the item number 0201 and the user number 0202 are used as keys for the name 0203. , Address 0204, date of birth 0205, gender 0206, and the like.

  The key generation system database 0300 is a database that stores a secret key generated for each user by the key generation system 0031. As shown in FIG. 3B, for example, the item number 0301 and the user number 0302 are used as keys. , Name 0303, address 0304, date of birth 0305, gender 0306, and key information 0307 (secret key). .

  The user database 0400 is a database that stores user information. As shown in FIG. 4A, for example, the item number 0401 and the user number 0402 are used as keys, and the name 0403, address 0404, date of birth 0405. , Gender 0406, public key information 0407, and certificate information 0408.

  The lending history database 0500 is a database that stores lending history information generated by encrypting lending information of a user with the public key of the user. For example, as shown in FIG. Lending date 0502, return date 0503, bibliographic information number 0504, material number 0505, material title 0506, responsibility display 0507, publication year 0508, publisher 0509, classification number 0510, lending hall 0511, and holding hall 0512 using 0501 as a key It is a collection of records that relate information such as.

  The terminal management number database 0600 is a database that stores user terminal attribute information. As shown in FIG. 4C, for example, the item number 0601 and the terminal management number 0602 are used as keys to set the installation location 0603 and the hardware. It is a collection of records in which information such as type name 0604 is associated. The user terminal 50 collates the attribute information of the user terminal against a computer-specific processing authority table 119 (see FIG. 1) that determines whether the browsing history information can be viewed or stored for each computer attribute. It is possible to determine whether or not the browsing history information can be viewed or stored.

  The function units 106 and 107 in the library system 0032 shown so far may be realized as hardware in the library system 0032 or may be realized as a program stored in an appropriate storage device such as an HDD or a memory. . In this case, the control unit 103 reads the corresponding program from the storage device into the memory 102 and executes it in accordance with the program execution. Similarly, the functional units 116 to 122 in the user terminal 50 may be realized as hardware in the user terminal 50 or may be realized as programs stored in an appropriate storage device such as an HDD or a memory. . In this case, the control unit 113 of the user terminal 50 reads the corresponding program from the storage device into the memory 112 and executes it in accordance with the program execution.

  As for the network 0700, various networks such as the Internet, a dedicated line, a WAN (Wide Area Network), a power line network, a wireless network, a public line network, and a mobile phone network can be adopted in addition to the LAN. Similarly, various networks can be employed for the Internet 0700. Further, if a virtual private network technology such as VPN is used, communication with improved security is established when the Internet is adopted.

  Hereinafter, the actual procedure of the book lending history management method will be described based on the schematic diagram of the book lending history management method of FIG. 5 and the detailed flows of FIGS. Of the various operations corresponding to the book lending history management method described below, what the library system 0032 executes is realized by the program 101 provided in the memory 102 of the library system 0032. And this program 101 is comprised from the code | cord | chord for performing the various operation | movement demonstrated below. Further, among various operations corresponding to the book lending history management method, what the user terminal 50 executes is realized by the program 111 provided in the memory 112 of the user terminal 50. And this program 111 is comprised from the code | cord | chord for performing the various operation | movement demonstrated below.

  In the book lending history management method of the present embodiment, for example, a resident of a local government (city) is assumed as a user. This user has a resident card issued by the city. This resident card includes an IC chip and serves as an authentication medium 0010 in the present invention. The user carries the resident card 0010, goes to the city hall, and registers the use of the library. At this time, as shown in FIG. 6, the resident card 0010 is set in the reader / writer at the window terminal 0020 of the city hall. The use environment setting system 0030 downloads user information such as the user's name, address, date of birth, and gender from the resident card 0010 via the reader / writer (4010).

  The usage environment setting system 0030 generates a user number for the user based on the acquired user information (4020), and registers the user information in the usage environment setting system database 0200 using this as a key ( 4030). The card application 0011 is downloaded to the resident card 0010 (4041). When the processing so far is completed, the user information is subsequently transmitted to the library system 0032 (4050). The library system 0032 receives this user information and stores it in the user database 0400.

  Next, the key generation system 0031 linked with the usage environment setting system 0030 executes a second setting process. FIG. 7 is a flowchart showing the second setting process in the present embodiment. The key generation system 0031 acquires user information including, for example, the user number of the user from the resident card 0010 inserted into the reader / writer of the window terminal 0020. Based on the user information, a public key / private key pair is generated (5010). Among the generated keys, for example, the secret key is registered in the key generation system database 0300 (5030). The secret key is downloaded to the card application 0011 of the resident card 0010 (5041). On the other hand, the public key is transmitted to the library system 0032 (5050). The library system 0032 receives this public key and stores it in the user database 0400.

  Next, user registration processing in the library system 0032 will be described. FIG. 8 is a flowchart showing user registration processing in the present embodiment. The library system 0032 reads the information in the card from the resident card 0010 set in the reader / writer of the library window terminal 0021 and registers the registered data (by the processing in FIGS. 4 and 5) from the user number. The database 0400 is searched (6005). Among them, the certificate information is acquired and registered in the library system 0032 (6010). Further, the user's lending history is acquired from an appropriate storage device, and encrypted with the user's public key. Thereby, the rental history information is generated (6030). The lending history information is stored in the lending history database 0500.

  Next, authentication processing in the book lending history management method of this embodiment will be described. FIG. 9 is a flowchart showing the first authentication process in the present embodiment. When a user requests to browse a book lending history, the user terminal 50 (of which, for example, the library window terminal 0021 or the resident terminal 0022) determines whether or not lending history information can be stored (or viewed) according to computer attributes. Software (e.g., corresponding to the first flag determination unit 120) is activated (1005), and the attribute information of the user terminal 50 is retrieved and acquired from the terminal management number database 0600 together with the user information of the user (1010). ).

  Then, the attribute information of the user terminal 50 is checked against the computer-specific processing authority table 119 that determines whether or not the loan history information can be viewed or stored for each computer attribute (1020). Determine whether or not to view or save. If the determination result is “saveable”, “1” is set to the first flag. If “cannot be saved”, the first flag is set to “0”. The information of the first flag is temporarily stored in the software (applet) downloaded from the library system 0032, for example. When the saving is completed, the software is terminated (1050).

  FIG. 10 is a flowchart showing the second authentication process in the present embodiment. Following the first authentication process, the user terminal 50 executes a second authentication process. The user terminal 50 activates software (e.g., corresponding to the second flag determination unit 121) that determines whether or not the lending history information can be stored (or viewed) according to the user authentication result (2005), and the user terminal 50 User information such as a user number, a secret key, and a personal authentication certificate is acquired from the card application 0011 of the resident card 0010. Then, based on this user information, information search in the user database 0400 is executed (2010), and verification relating to the user number, private key, and personal authentication certificate of the corresponding user is executed. As a result, the user terminal 50 executes at least signature verification based on the authentication information, and determines whether the user can view or store the loan history information (2020).

  If the determination result is “saveable”, “1” is set to the second flag. If “cannot be saved”, the second flag is set to “0”. The information on the second flag is temporarily stored in the software (applet) downloaded from the library system 0032, for example. When the saving is completed, the software is terminated (2050).

  FIG. 11 is a flowchart showing the browsing software activation process in this embodiment. Next, a process for determining whether or not the lending history information is stored (or viewed) using the first and second flags will be described. The user terminal 50 activates the loan history browsing software in response to the user's request (3005), and along with this, reads the user number and secret key from the resident card 0010 of the user, Lending history information is extracted from the lending history database 0500 based on the user number.

  The authority determination unit 122 of the user terminal 50 stores the first flag (in the figure: storage permission / impossibility flag) and the second flag (in the figure: storage authority permission / inhibition flag) in a memory. (3010, 3020) When both the first and second flags can be stored (or browsed) (1030, 2030), the browsing software displays a menu for storing rental history information (3040). On the other hand, if either of the first and second flags is a flag indicating that the image cannot be saved (1040, 2040), the save menu display is not executed (3030).

  Thus, through the process of displaying / hiding the stored menu, the loan history information is decrypted with the secret key (3050), the browsing process is started, and an appropriate output interface in the user terminal 50 (eg, display device) (3050). When the browsing process ends (3053), the browsing software ends (3054), and the flow ends. Of course, when the saving menu is displayed when browsing the lending history information, the user terminal 50 receives a saving instruction from the user and saves the lending history information (for example, an auxiliary storage device of the user terminal). Storage, storage on an appropriate recording medium, etc.).

  In the above example, it is determined whether or not the loan history information can be stored using the first and second flags. However, not only the storage of the loan history information but also the extraction of the loan history information from the loan history database, It may be determined whether or not execution of any one of the decryption of the loan history information with the secret key and the output of the decrypted loan history information to the output interface is possible.

  Further, by referring to the information on the return date 0503 of the corresponding user in the loan history database 0500, a display prompting the return of the book whose return date has exceeded may be performed on the screen of the browsing software. In the browsing software, data processing such as statistical display of book rental history, aged display, and cumulative display of book types may be performed and provided to the user.

  In addition to the management of the book lending history shown in the present embodiment, the book lending history management method of the present invention involves various history management such as usage history of other administrative services, purchase history of goods and services, etc. It may be applied to.

According to the present invention, the lending history of a book is stored in a computer-usable storage device such as a hard disk device instead of the user's IC card, and the limitation of the lending history amount that can be accumulated can be substantially eliminated. Also, since the loan history information stored on the library side is encrypted with the private key of the individual user, it is possible to manage the loan history as personal information in consideration of security.
Therefore, it is possible to manage lending history information in consideration of privacy protection regardless of the amount of data.

  As mentioned above, although embodiment of this invention was described concretely based on the embodiment, it is not limited to this and can be variously changed in the range which does not deviate from the summary.

It is a schematic diagram of the book lending history management system in this embodiment. It is a figure which shows the example of a data structure of the IC card in this embodiment. It is a figure which shows (a) utilization environment setting system database and (b) key generation system database in this embodiment. It is a figure which shows (a) user database, (b) rental history database, (c) terminal management number database in this embodiment. It is a schematic diagram of the book lending history management method in this embodiment. It is a flowchart which shows the 1st setting process in this embodiment. It is a flowchart which shows the 2nd setting process in this embodiment. It is a flowchart which shows the user registration process in this embodiment. It is a flowchart which shows the 1st authentication process in this embodiment. It is a flowchart which shows the 2nd authentication process in this embodiment. It is a flowchart which shows the starting process of the browsing software in this embodiment.

Explanation of symbols

IC card, authentication medium 0020 Window terminal, user terminal 0021 Library window terminal, user terminal 0022 Resident terminal, user terminal 0030 Usage environment setting system 0031 Key generation system 0032 Library system 0200 Usage environment setting system database 0300 Key generation System database 0400 User database 0500 Lending history database 0600 Terminal management number database 0700 Network 0750 Firewall 0770 Internet

Claims (7)

A library lending history management method in a network system including a terminal and a library system connected to the terminal via a network,
The library system
Acquiring lending information including at least attribute information of a lending book accompanying lending a book to a user, and acquiring the public key of the user from a user database storing user information ;
A process of generating loan history information by encrypting the user's loan information with the public key, and storing the information in a loan history database ;
Executing the process of transmitting the loan history information stored in the loan history database to the terminal via the network;
The terminal is
A process of accepting a browsing request for loan history information via the input unit;
Check the attribute information of the terminal against the processing authority table for each computer, which is stored in the storage unit of the terminal, and determines whether the browsing history information can be viewed or stored for each attribute of the terminal. The process of determining whether to view or save
A process of obtaining the user authentication information from the user authentication medium;
A process of performing signature verification based on the acquired authentication information of the user, and determining whether or not the loan history information can be viewed or stored in the user;
Processing for storing in memory a first flag of a determination result related to whether or not the loan history information can be browsed or stored in the terminal and a second flag of a determination result related to whether or not the user can view or store the loan history information When,
A process of obtaining the lending history information from the library system via the network when both the first and second flags indicate that browsing or storage is possible;
A process of decrypting the acquired loan history information with a secret key included in the acquired user authentication information;
Executing the process of outputting the decrypted loan history information to an output unit,
A book lending history management method. In claim 1,
When the terminal indicates that both the first and second flags can be viewed or stored, a process for outputting a save menu to the output unit, and an instruction to save the decrypted loan history information A process of receiving via the input unit and a process of storing the decrypted loan history information in the storage unit,
A book lending history management method. In claim 1 or 2,
The book lending history management method , wherein the user authentication information is a user attribute of the user, the secret key, and an electronic certificate . A program for causing a terminal to execute processing necessary for managing a book loan history,
In the terminal,
A process of accepting a browsing request for a book rental history via the input unit;
Check the attribute information of the terminal against the processing authority table for each computer, which is stored in the storage unit of the terminal, and determines whether the browsing history information can be viewed or stored for each terminal attribute. The process of determining whether to view or save
Processing to obtain user authentication information from the user authentication medium;
A process of performing signature verification based on the acquired authentication information of the user, and determining whether or not the loan history information can be viewed or stored in the user;
Processing for storing in memory a first flag of a determination result related to whether or not the loan history information can be browsed or stored in the terminal and a second flag of a determination result related to whether or not the user can view or store the loan history information When,
When both the first and second flags indicate that browsing or storage is possible, the lending history information is acquired from the library system that is connected to the terminal so as to be able to communicate with the network and stores the book lending history information. Processing,
  A process of decrypting the acquired loan history information with a secret key included in the acquired user authentication information;
  And a process for outputting the decrypted lending history information to an output unit. In claim 4,
In the terminal,
When both the first and second flags indicate that browsing or saving is possible, a process for outputting a save menu to the output unit, and an instruction to save the decrypted loan history information are sent to the input unit. And a process of receiving the decrypted loan history information in the storage unit, and
A program characterized by that. In claim 4 or 5,
The book lending history management method , wherein the user authentication information is a user attribute of the user, the secret key, and an electronic certificate . On your device,
A process of accepting a browsing request for a book rental history via the input unit;
Check the attribute information of the terminal against the processing authority table for each computer, which is stored in the storage unit of the terminal, and determines whether the browsing history information can be viewed or stored for each terminal attribute. The process of determining whether to view or save
Processing to obtain user authentication information from the user authentication medium;
A process of performing signature verification based on the acquired authentication information of the user, and determining whether or not the loan history information can be viewed or stored in the user;
Processing for storing in memory a first flag of a determination result related to whether or not the loan history information can be browsed or stored in the terminal and a second flag of a determination result related to whether or not the user can view or store the loan history information When,
When both the first and second flags indicate that browsing or storage is possible, the lending history information is acquired from the library system that is connected to the terminal so as to be able to communicate with the network and stores the book lending history information. Processing,
  A process of decrypting the acquired loan history information with a secret key included in the acquired user authentication information;
  A computer-readable storage medium storing a program for executing the process of outputting the decrypted loan history information to an output unit.

Images