Server, terminal device, information processing program, management system and management method

Abstract

A registration server (100) receives, from a terminal device (50) for reading and writing information from and to a tag, tag information including first key information recorded in the tag and information relating to the attachment position of the tag, attendance information of a user, and terminal information including information relating to the terminal device (50). If authentication based on the tag information and the terminal information is successful, the registration server (100) transmits second key information associated with the tag to the terminal device (50), and causes the terminal device 50 to execute processing to write the second key information, the terminal information, and the attendance information to the tag.

Description

[Technical field]

[0001] The present disclosure relates to a server, a terminal device, an information processing program, a management system, and a management method. [Background technology]

[0002] Companies are required to manage the attendance status of their employees. For example, a seat management system is a conventional technology for managing attendance status. In this seat management system, an IC (Integrated Circuit) tag is attached to each seat, and employees read the seat information stored in the IC tag using their own mobile terminals and notify the server of the mobile terminal's ID (Identification) and the seat information. The server identifies the employee's personal information corresponding to the mobile terminal's ID, and generates and displays screen information that associates the identified personal information with the seat information. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2006-318058 A [Patent Document 2] JP 2008-276633 A [Patent Document 3] JP 2017-138773 A [Patent Document 4] JP 2013-196302 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, the conventional seat management systems left room for improvement in identifying employee attendance status using IC tags.

[0005] Therefore, this disclosure proposes a server, a terminal device, an information processing program, a management system, and a management method that can appropriately identify the attendance status of employees using IC tags. [Means for solving the problem]

[0006] In order to solve the above problems, a server of one embodiment of the present disclosure has a receiving unit that receives tag information including first key information recorded on the tag and information regarding the attachment position of the tag, a user's attendance information, and terminal information including information regarding the terminal device from a terminal device that reads and writes information to the tag, and a write control unit that, if authentication based on the tag information and the terminal information is successful, sends second key information associated with the tag to the terminal device and causes the terminal device to execute a process of writing the second key information, the terminal information, and the attendance information to the tag. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating a configuration of a system according to an embodiment. [Diagram 2] FIG. 1 illustrates an example of an IC card. [Diagram 3] FIG. 13 illustrates an example of a registration screen. [Figure 4] FIG. 13 is a diagram showing an example of a seat status screen. [Diagram 5] FIG. 4 is a diagram illustrating an example of a processing procedure of the system according to the embodiment. [Figure 6] FIG. 11 is a diagram illustrating an example of a processing procedure of the system according to the embodiment when the network is unavailable. [Figure 7] 4 is a diagram showing an example of a data structure of an IC tag according to the embodiment; FIG. [Figure 8] FIG. 2 is a diagram illustrating an example of the configuration of a terminal device according to the present embodiment. [Figure 9] FIG. 2 is a diagram illustrating an example of the configuration of a registration server according to the embodiment. [Figure 10] FIG. 4 is a diagram illustrating an example of a data structure of a registration DB according to the embodiment. [Figure 11] 5 is a diagram showing an example of a data structure of an authentication table according to the embodiment; FIG. [Figure 12] 4 is a diagram showing an example of a data structure of a seat history table according to the embodiment; FIG. [Figure 13] 11 is a diagram for explaining a process of an authentication unit according to the embodiment; FIG. [Figure 14] FIG. 2 is a diagram illustrating an example of the configuration of a view server according to the present embodiment. [Figure 15] 4 is a diagram illustrating an example of a data structure of a user management table according to the embodiment. FIG. [Figure 16] 4 is an example of a data structure of seating layout data according to the embodiment. [Figure 17] 6 is a flowchart showing a processing procedure of the terminal device according to the embodiment. [Figure 18] 13 is a flowchart showing a processing procedure when the device is unavailable. [Figure 19] 10 is a flowchart showing a processing procedure of a registration server according to the embodiment; [Figure 20] FIG. 2 is a hardware configuration diagram showing an example of a computer that realizes the functions of a registration server and a view server. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, the server, the terminal device, the terminal program, the system, and the method disclosed in the present application will be described in detail with reference to the accompanying drawings. Note that the present invention is not limited to the embodiments.

[0009] The present disclosure will be described in the following order. 1. Embodiment 1-1. System configuration according to the embodiment 1-2. Processing procedure of the system according to the embodiment 1-3. Data structure of IC tag according to embodiment 1-4. Configuration of terminal device 50 according to embodiment 1-5. Configuration of the registration server 100 according to the embodiment 1-6. Configuration of the view server 200 according to the embodiment 1-7. Processing procedure of the terminal device 50 according to the embodiment 1-8. Processing procedure of the registration server 100 according to the embodiment 1-9. Effects of the embodiment 2. Other embodiments 3. Hardware Configuration 4. Conclusion

[0010] [1. Embodiment] [1-1. System configuration according to embodiment] First, an example of a system according to an embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing the configuration of a system according to an embodiment. As shown in Fig. 1, the system 1 includes an IC card 10, a terminal device 50, a registration server 100, and a view server 200. In the present embodiment, the registration server 100 and the view server 200 are described as separate servers as an example, but the registration server 100 and the view server 200 may be a single server.

[0011] The terminal device 50 , the registration server 100 , and the view server 200 are connected to each other via a network 5 .

[0012] The terminal device 50 is a terminal device equipped with NFC (Near field communication), and when a user brings the terminal device 50 close to the IC card 10, it is possible to write and read information to and from an IC tag mounted on the IC card 10. In the following description, the IC tag mounted on the IC card 10 is simply referred to as an "IC tag." The terminal device 50 corresponds to a smartphone, a tablet terminal, etc.

[0013] Assume that the IC card 10 is attached to each seat in the office. FIG. 2 is a diagram showing an example of an IC card. As shown in FIG. 2, a QR (Quick Response) code (registered trademark) is set in an area 10a of the IC card 10. In this embodiment, the QR code (registered trademark) in the area 10a corresponds to a URL (Uniform Resource Locator) of the registration server 100. The number of the seat to which the IC card 10 is attached is set in an area 10b. A wave mark is set in an area 10c.

[0014] The office where the user works is assumed to be a free address system. When the user sits at the seat where the user works and brings the terminal device 50 close to the holding mark (area 10c), the terminal device 50 reads information from the IC tag included in the IC card 10 and displays the registration screen shown in FIG. 3. The information read from the IC tag includes key information, seat number information, URL information of the registration server 100 to be connected to, and the like. The user may photograph a QR code (registered trademark) with the camera of the terminal device 50 and obtain the URL of the registration server 100. In the following description, the key information read from the IC tag by the terminal device 50 will be referred to as "first key information" where appropriate.

[0015] Fig. 3 is a diagram showing an example of a registration screen. As shown in Fig. 3, the registration screen 20 of the terminal device 50 includes areas 20a, 20b, and 20c, radio buttons 20d and 20e, and a registration button 20f. The area 20a is an area for setting a seat number. The terminal device 50 automatically registers the seat number read from the IC tag in the area 20a.

[0016] A user ID for identifying a user is registered in area 20b. The user operates terminal device 50 to set his / her own user ID in area 20b. Area 20c is where supplementary information (comments) related to the user's work is registered. For example, the user operates terminal device 50 to register the comments "In a meeting" or "Having lunch, etc."

[0017] The radio buttons 20d and 20e indicate whether the user has come to work or left work. When the user has come to work, the user operates the terminal device 50 to select the radio button 20d. On the other hand, when the user has left work, the user operates the terminal device 50 to select the radio button 20e.

[0018] The registration button 20f is a button that a user presses when making a registration request to the registration server 100. For example, when the registration button 20f is pressed, the terminal device 50 transmits tag information, terminal information, and attendance information to the registration server 100.

[0019] The tag information includes the first key information and the seat number read from the IC tag. The terminal information includes a terminal ID, location information, touch date and time, comments, etc. The terminal ID is information for identifying the terminal device 50. The location information indicates the location information of the terminal device 50. The touch date and time indicates the date and time when the terminal device 50 was brought close to the wave mark (area 10c) and wrote the information. The comment is supplementary information regarding the user's work. The attendance information is information indicating whether the user has come to work or left work. The terminal device 50 may further include the user ID in the terminal information and transmit it to the registration server 100.

[0020] The registration server 100 executes authentication processing when it receives tag information, terminal information, and attendance information from the terminal device 50. If the authentication processing is successful, the registration server 100 transmits new key information corresponding to the IC tag to the terminal device 50. In the following description, the key information transmitted by the registration server 100 to the terminal device 50 will be referred to as "second key information" as appropriate.

[0021] When the terminal device 50 receives the second key information from the registration server 100, it writes the second key information, the terminal information, and the attendance information to the IC tag. As a result, the first key information recorded in the IC tag is updated to the second key information. When writing to the IC tag is completed, the terminal device 50 transmits a writing completion notification to the registration server 100.

[0022] When the registration server 100 receives a writing completion notification from the terminal device 50, the registration server 100 registers in the registration DB the first key information, the terminal information, and the attendance information of the tag information received from the terminal device 50. The registration server 100 transmits a registration completion notification to the terminal device 50.

[0023] Here, the registration server 100 generates a seat history table based on the information registered in the registration DB. The seat history table is a table that associates terminal IDs, seat numbers, attendance information, comments, and task hours. The registration server 100 transmits the information of the seat history table to the view server 200.

[0024] The view server 200 generates a seat status screen based on the seat history table. Fig. 4 is a diagram showing an example of the seat status screen. As shown in Fig. 4, the seat status screen 25 includes a date and time setting area 25a. When a user who has logged in to the view server 200 sets a date and time in the date and time setting area 25a, the relationship between the seat number at the set date and time and the name of the user who will use the seat with that seat number is displayed on the seat status screen 25.

[0025] In the example shown in Fig. 4, "August 25, 2020, 9:49" is set in the date and time setting area 25a, and the user "Hiroi" is displayed in seat number 8_2_5. When a user viewing the seat status screen 25 places the mouse cursor 25b on the seat with seat number 8_2_5, the view server 200 displays the comment 25c "Meal time" from the user "Hiroi."

[0026] [1-2. Processing procedure of the system according to the embodiment] Next, an example of a processing procedure of the system 1 shown in Fig. 1 will be described. Fig. 5 is a diagram showing an example of a processing procedure of the system according to this embodiment. As shown in Fig. 5, when a user brings the terminal device 50 close to the holding mark on the IC card 10, the terminal device 50 reads the first key information and the seat number from the IC tag of the IC card 10 (step S101).

[0027] The terminal device 50 transmits the tag information, terminal information, and attendance information to the registration server 100 (step S102). As described above, the tag information includes the first key information and the seat number. The terminal information includes the terminal ID, position information, touch date and time, and comments.

[0028] The registration server 100 executes authentication processing based on the tag information, the terminal information, and the attendance information (step S103). If the authentication processing is successful, the registration server 100 transmits second key information, which is different from the first key information, to the terminal device 50 (step S104).

[0029] When the terminal device 50 receives the second key information, it writes the second key information, the terminal information, and the attendance information to the IC tag (step S105). The terminal device 50 transmits a writing completion notification to the registration server 100 (step S106).

[0030] When the registration server 100 receives the writing completion notification, the registration server 100 registers the tag information, the terminal information, and the attendance information in the registration DB (step S107). The registration server 100 transmits a registration completion notification to the terminal device 50 (step S108).

[0031] As described in FIG. 5, in the system 1 according to the first embodiment, the registration server 100 executes authentication processing based on the tag information (first key information, seat number), terminal information, and attendance information received from the terminal device 50. If the authentication is successful, the registration server 100 writes the second key information, terminal information, and attendance information to the IC tag of the IC card 10 by sending second key information different from the first key information to the terminal device 50. If the registration server 100 receives a writing completion notification from the terminal device 50, it registers the tag information, terminal information, and attendance information in the registration DB. This allows the terminal information and attendance information to be stored not only in the registration server 100 but also in the IC tag (allowing double storage).

[0032] The registration server 100 controls the terminal device 50 to write new key information (second key information) to the IC tag each time the IC tag (IC card 10) is used, thereby preventing the unauthorized reading of information from the IC tag and the execution of processes such as registration requests using only the unauthorized read information without using the IC card.

[0033] The registration server 100 executes authentication processing using tag information (seat number) and terminal information (location information), and therefore can prevent the IC card from being taken out and used in a place other than the intended one.

[0034] Incidentally, the system 1 according to this embodiment executes the process shown in Fig. 6 when the network 5 is unavailable. Fig. 6 is a diagram showing an example of the processing procedure of the system according to this embodiment when the network is unavailable. As shown in Fig. 6, when the terminal device 50 is brought close to the holding mark of the IC card 10 by a user at a timing when the network 5 is unavailable, the terminal device 50 reads the first key information and the seat number from the IC tag of the IC card 10 (step S201). The terminal device 50 writes the first key information, terminal information, and attendance information to the IC tag (step S202).

[0035] When the terminal device 50 is brought close to the holding mark of the IC card 10 by the user after the network 5 is restored, the terminal device 50 reads the first key information, the seat number, and the plurality of pieces of registered information (step S203). Here, the plurality of pieces of registered information are the terminal information and attendance information (a set of a plurality of pieces of terminal information and attendance information) registered in the IC tag while the network 5 was unavailable.

[0036] The terminal device 50 transmits the tag information and multiple pieces of registration information (step S204). The registration server 100 executes authentication processing based on the tag information and multiple pieces of registration information (step S205). If the authentication processing is successful, the registration server 100 transmits second key information, which is different from the first key information, to the terminal device 50 (step S206).

[0037] Upon receiving the second key information, the terminal device 50 writes the second key information to the IC tag (step S206). The terminal device 50 transmits a writing completion notification to the registration server 100 (step S207).

[0038] The registration server 100 registers the tag information and the multiple pieces of registration information in the DB (step S208). The registration server 100 transmits a registration completion notification to the terminal device 50 (step S209).

[0039] 6, in the system 1 according to this embodiment, when the network 5 is unavailable, the terminal device 50 writes the terminal information and attendance information to the IC tag of the IC card 10, and when the network 5 is restored, transmits the tag information and multiple pieces of registration information together to the registration server 100. As a result, even if the network 5 is temporarily unavailable, the tag information, terminal information, and attendance information can be stored (double storage) by the IC tag and the registration server 100 after the network 5 is restored.

[0040] [1-3. Data structure of IC tag according to embodiment] Next, an example of the data structure of the IC tag stored in the IC card 10 will be described with reference to Fig. 7. Fig. 7 is a diagram showing an example of the data structure of the IC tag 11 according to this embodiment. As shown in Fig. 7, the IC tag 11 has seat information 11a, key information 11b, a registration information table 11c, and connection destination information 11d.

[0041] The seat information 11a includes information on the seat number of the seat to which the IC card 10 (IC tag 11) is attached. Initial key information is written to the key information 11b by a reader / writer at the factory when the vehicle is shipped from the factory. The key information 11b is updated by key information written from the terminal device 50.

[0042] The registration information table 11c is a table that stores registration information written from the terminal device 50. The registration information includes terminal information and attendance information. As described above, the terminal information includes a terminal ID, location information, touch date and time, comments, etc. The attendance information is information that indicates whether a user has come to work or left work.

[0043] In the registration information table 11c, a flag is associated with the registration information. The flag is information for identifying whether the corresponding registration information has been sent to the registration server 100. For example, if the registration information has been sent to the registration server 100, the flag is "on." If the network 5 is unavailable and the registration information has not been sent to the registration server 100, the flag is "off."

[0044] The connection destination information 11d stores information such as the URL of the registration server 100. The terminal device 50 may acquire the URL of the registration server 100 by photographing the QR code (registered trademark) described with reference to FIG.

[0045] [1-4. Configuration of terminal device 50 according to embodiment] Next, the configuration of the terminal device 50 shown in FIG. 1 will be described with reference to FIG. 8. FIG. 8 is a diagram showing an example of the configuration of the terminal device 50 according to this embodiment. As shown in FIG. 8, this terminal device 50 has a communication unit 51, a reader / writer 52, a camera 53, a timer 54, a touch panel 55, a storage unit 56, and a control unit 57. Note that FIG. 8 describes only the configuration of the terminal device 50 closely related to this embodiment. The other configurations are similar to those of conventional smartphones and tablet terminals, and therefore descriptions thereof will be omitted.

[0046] The communication unit 51 is realized by, for example, a NIC (Network Interface Card) etc. The communication unit 51 is connected to the network 5 by wired or wireless connection, and transmits and receives information between the registration server 100 and the view server 200 via the network 5.

[0047] The reader / writer 52 reads and writes information from and to the IC tag 11 based on NFC.

[0048] The camera 53 captures an image or a video. For example, the terminal device 50 may use the camera 53 to capture the QR code (registered trademark) of the IC card 10 described in FIG.

[0049] The timer 54 outputs current date and time information to the control unit 57. The timer 54 may access an external device connected to the network 5 to synchronize the date and time information.

[0050] The touch panel 55 is an electronic device that combines a display device and an input device. The touch panel 55 displays various types of screen information output from the control unit 57. The touch panel 55 also receives various types of input information input by a user's touch operation, and outputs the input information to the control unit 57.

[0051] For example, touch panel 55 displays registration screen 20 described in Fig. 3. The user inputs a user ID, selects radio button 20d or 20e, and presses registration button 20f by performing a touch operation on touch panel 55. The user may also perform other touch operations.

[0052] The storage unit 56 is realized by, for example, a semiconductor memory element such as a random access memory (RAM) or a flash memory, or a storage device such as a hard disk or an optical disk. The storage unit 56 stores various data used in information processing. The storage unit 56 has tag information 56a and registration information 56b.

[0053] The tag information 56a is information read from the IC tag 11 by the reader / writer 52. For example, the tag information 56a includes key information (first key information) and a seat number.

[0054] The registration information 56b includes terminal information and attendance information. The terminal information includes a terminal ID, location information, touch date and time, and a comment. The terminal ID is information for identifying the terminal device 50, and is assumed to be set in advance. The location information indicates date and time information when the reader / writer 52 reads out the key information from the IC tag 11. The comment corresponds to a comment input on the registration screen 20. The terminal information may include a user ID.

[0055] The control unit 57 is realized, for example, by a central processing unit (CPU) or a micro processing unit (MPU) executing a program stored in the terminal device 50 using a random access memory (RAM) or the like as a working area. The control unit 57 is also a controller, and may be realized, for example, by an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA).

[0056] The control unit 57 includes a transmitting / receiving unit 57a, a position information identifying unit 57b, a reader / writer control unit 57c, and a display control unit 57d. The transmitting / receiving unit 57a is an example of a transmitting unit. The reader / writer control unit 57c is an example of a reading unit and a writing unit.

[0057] The transmission / reception unit 57a is a processing unit that transmits and receives information to and from the registration server 100 via the network 5. The transmission / reception unit 57a periodically accesses the network 5 and outputs information as to whether the network 5 is available or not to the reader / writer control unit 57c.

[0058] When the transmitting / receiving unit 57a receives a transmission request from the display control unit 57d, it transmits the tag information 56a and the registration information 56b (terminal information, attendance information) stored in the storage unit 56 to the registration server 100. The transmitting / receiving unit 57a identifies the URL of the registration server 100 based on the connection destination information 11d read from the IC tag 11 or the QR code (registered trademark) photographed by the camera 53, and transmits the information.

[0059] The transmitting / receiving unit 57a transmits the tag information 56a and the registration information 56b (terminal information, attendance information) to the registration server 100, and if the authentication of the tag information 56a and the registration information 56b is successful, receives the second key information from the registration server 100. When the transmitting / receiving unit 57a receives the second key information from the registration server 100, it outputs the second key information to the reader / writer control unit 57c.

[0060] When the transmitting / receiving unit 57a acquires information indicating that writing of the second key information has been completed from the reader / writer control unit 57c, the transmitting / receiving unit 57a transmits a writing completion notification to the registration server 100. When the transmitting / receiving unit 57a receives a registration completion notification from the registration server 100, the transmitting / receiving unit 57a outputs the registration completion notification to the display control unit 57d.

[0061] Meanwhile, when the network 5 recovers from an unavailable state and the tag information 56a registered in the IC tag 11 and the multiple pieces of registration information are read by the reader / writer 52, the transmitter / receiver 57a transmits the tag information and the multiple pieces of registration information to the registration server 100.

[0062] The transmitting / receiving unit 57a transmits the tag information 56a and multiple pieces of registration information (terminal information, attendance information) to the registration server 100, and if the tag information 56a and multiple pieces of registration information are successfully authenticated, receives second key information from the registration server 100. When the transmitting / receiving unit 57a receives the second key information from the registration server 100, it outputs the second key information to the reader / writer control unit 57c.

[0063] If authentication of the registration server 100 based on the tag information 56a and the registration information 56b (multiple pieces of registration information) fails, the transmission / reception unit 57a receives error information from the registration server 100. The transmission / reception unit 57a outputs the error information to the display control unit 57d.

[0064] The position information identifying unit 57b is a processing unit that identifies the position information of the terminal device 50 when the reader / writer 52 reads the first key information of the IC tag 11. For example, the position information identifying unit 57b calculates the position information using a GPS (Global Positioning System) function. The position information identifying unit 57b registers the position information in the terminal information of the registration information 56b.

[0065] The reader / writer control unit 57c is a processing unit that controls the reader / writer 52 to read and write information from and to the IC tag 11. Below, a description will be given in order of the processing of the reader / writer control unit 57c when the network 5 is available, the processing of the reader / writer control unit 57c when the network 5 is unavailable, and the processing of the reader / writer control unit 57c when the network 5 has recovered from an unavailable state.

[0066] The process of the reader / writer control unit 57c when the network 5 is available will be described. When the terminal device 50 approaches the holding mark (area 10c), the reader / writer control unit 57c controls the reader / writer 52 to read the first key information, the seat number, and the connection destination information from the IC tag 11. The reader / writer control unit 57c registers the first key information and the seat number in the tag information 56a. The reader / writer control unit 57c outputs the connection destination information to the transmission / reception unit 57a.

[0067] When the reader / writer control unit 57c acquires the second key information from the transmitting / receiving unit 57a, the reader / writer control unit 57c controls the reader / writer 52 to write the second key information into the key information 11b of the IC tag 11. The reader / writer control unit 57c also controls the reader / writer 52 to register the registration information 56b in the registration information table 11c of the IC tag 11 and sets the corresponding flag to "ON." The reader / writer control unit 57c transmits a write completion notification to the registration server 100 via the transmitting / receiving unit 57a.

[0068] The reader / writer control unit 57c obtains from the timer 54 the date and time when the information is read from the IC tag 11, and sets this as the touch date and time in the registration information 56b.

[0069] The following describes the process of the reader / writer control unit 57c when the network 5 is unavailable. When the terminal device 50 approaches the holding mark (area 10c), the reader / writer control unit 57c controls the reader / writer 52 to read the first key information from the IC tag 11.

[0070] The reader / writer control unit 57c obtains from the timer 54 the date and time when the information is read from the IC tag 11, and sets this as the touch date and time in the registration information 56b.

[0071] The reader / writer control unit 57c registers the registration information 56b (terminal information, attendance information) in the registration information table 11c of the IC tag 11, and sets the flag corresponding to the registration information 56b to "OFF." In addition, the reader / writer control unit 57c registers the key information (first key information) read from the IC tag 11 in the key information 11b of the IC tag.

[0072] The process of the reader / writer control unit 57c when the network 5 recovers from an unusable state will be described. When the terminal device 50 approaches the holding mark (area 10c), the reader / writer control unit 57c controls the reader / writer 52 to read the first key information from the IC tag 11. The reader / writer control unit 57c also reads registration information (plurality of registration information) whose flag is "OFF" from the registration information table 11c of the IC tag 11, and outputs the read registration information to the transmission / reception unit 57a. Although not shown in the figure, the plurality of registration information are temporarily registered in the storage unit 56.

[0073] When the reader / writer control unit 57c acquires the second key information from the transmitting / receiving unit 57a, the reader / writer control unit 57c controls the reader / writer 52 to write the second key information into the key information 11b of the IC tag 11. The reader / writer control unit 57c sets flags corresponding to the multiple pieces of registration information that have already been transmitted to "ON". The reader / writer control unit 57c transmits a write completion notification to the registration server 100 via the transmitting / receiving unit 57a.

[0074] When the reader / writer 52 reads out the tag information 56a (first key information, seat number), the display control unit 57d generates the registration screen 20 and displays the registration screen 20 on the touch panel 55.

[0075] For example, the process of the display control unit 57d will be described using the registration screen 20 in Fig. 3. The display control unit 57d sets the seat number of the tag information 56a in the area 20a of the registration screen 20.

[0076] The user operates touch panel 55 to input a user ID in area 20b. The user operates touch panel 55 to input a comment in area 20c. When arriving at work, the user operates touch panel 55 to select radio button 20d. When leaving work, the user operates touch panel 55 to select radio button 20e. When making a registration request, the user operates touch panel 55 to press registration button 20f.

[0077] When the register button 20f is pressed, the display control unit 57d sets the information inputted in the registration screen 20 to the registration information 56b. For example, the display control unit 57d registers a comment inputted in the area 20c of the registration screen 20 to the terminal information of the registration information 56b. When the radio button 20d is selected, the display control unit 57d sets the attendance information of the registration information 56b to "Come to work". When the radio button 20e is selected, the display control unit 57d sets the attendance information of the registration information 56b to "Leave work". The display control unit 57d may set the user ID inputted in the area 20b to the registration information 56b.

[0078] After completing the setting in the registration information 56b, the display control unit 57d outputs a transmission request to the transmitting / receiving unit 57a.

[0079] If authentication of the registration server 100 based on the tag information 56a and the registration information 56b (multiple registration information) fails and error information is obtained, the display control unit 57d outputs an error screen to the touch panel 55 and requests re-input into the registration screen 20.

[0080] [1-5. Configuration of the registration server 100 according to the embodiment] Next, the configuration of the registration server 100 shown in Fig. 1 will be described with reference to Fig. 9. Fig. 9 is a diagram showing an example of the configuration of the registration server 100 according to the present embodiment. As shown in Fig. 9, the registration server 100 has a communication unit 110, an input unit 120, a display unit 130, a storage unit 140, and a control unit 150.

[0081] The communication unit 110 is realized by, for example, a NIC etc. The communication unit 110 is connected to the network 5 by wired or wireless connection, and transmits and receives information to and from the terminal device 50 and the view server 200 via the network 5.

[0082] The input unit 120 is an input device for inputting various information to the registration server 100. The input unit 120 corresponds to a keyboard, a mouse, a touch panel, or the like.

[0083] The display unit 130 is a display device that displays various information output from the control unit 150. The display unit 130 corresponds to a liquid crystal display, an organic EL (Electro Luminescence) display, a touch panel, or the like.

[0084] The storage unit 140 is realized by, for example, a semiconductor memory element such as a RAM or a flash memory, or a storage device such as a hard disk or an optical disk. The storage unit 140 stores various data used for information processing. The storage unit 140 has a registration DB 141, an authentication table 142, and a seat history table 143.

[0085] The registration DB 141 stores tag information and registration information that have been transmitted from the terminal device 50 and have been successfully authenticated. Fig. 10 is a diagram showing an example of the data structure of the registration DB 141 according to this embodiment. As shown in Fig. 10, the registration DB 141 includes seat numbers, key information, terminal IDs, position information, touch dates and times, comments, attendance information, user IDs, and the like.

[0086] The authentication table 142 holds information used when authenticating tag information and registration information transmitted from the terminal device 50. FIG. 11 is a diagram showing an example of a data structure of the authentication table 142 according to this embodiment. As shown in FIG. 11, this authentication table 142 associates seat numbers, seat position information, and key information history. In the authentication table 142, the seat number is a number that identifies a seat. The seat position information indicates the position of the seat corresponding to the seat number. The key information history is a history of key information set in an IC tag. For example, the key information history is stored in order from newest key information to oldest key information.

[0087] The seat history table 143 is a table that holds the history of the usage status of each seat. Fig. 12 is a diagram showing an example of the data structure of the seat history table 143 according to this embodiment. As shown in Fig. 12, in this seat history table 143, date and time are associated with seat usage status. The seat usage status includes multiple seat numbers, and for each seat number, usage status, terminal ID, user ID, and comments are included.

[0088] The control unit 150 is realized, for example, by a CPU, an MPU, or the like, executing a program stored in the registration server 100 using a RAM or the like as a working area. The control unit 150 is also a controller, and may be realized, for example, by an integrated circuit such as an ASIC or an FPGA.

[0089] The control unit 150 includes a receiving unit 151 , an authentication unit 152 , a write control unit 153 , a registration unit 154 , a generation unit 155 , and a transmission unit 156 .

[0090] The receiving unit 151 is a processing unit that receives various information from the terminal device 50. When the receiving unit 151 receives tag information and registration information (terminal information and attendance information) from the terminal device 50, the receiving unit 151 outputs the received information to the authentication unit 152.

[0091] When the receiving unit 151 receives a write completion notification from the terminal device 50 , the receiving unit 151 outputs the write completion notification to the registration unit 154 .

[0092] The authentication unit 152 is a processing unit that authenticates the tag information and registration information (terminal information, attendance information) transmitted from the terminal device 50. The authentication unit 152 executes a first authentication process, a second authentication process, and a third authentication process, and if all of the authentication processes are successful, outputs a message indicating that the authentication is successful to the writing control unit 153. If any of the authentication processes is not successful, the authentication unit 152 outputs a message indicating that the authentication is unsuccessful to the writing control unit 153.

[0093] The first authentication process executed by the authentication unit 152 will be described. The first authentication process is to determine whether or not the seat position information of the seat number matches the position information included in the registration information. The authentication unit 152 compares the seat number included in the tag information with the authentication table 142 to identify the seat position information corresponding to the seat number.

[0094] When the difference between the identified seat position information and the position information included in the registration information is less than a predetermined difference, the authentication unit 152 determines that the seat position information and the position information match (determines that the first authentication process is successful). On the other hand, when the difference between the identified seat position information and the position information included in the registration information is equal to or greater than a predetermined difference, the authentication unit 152 determines that the seat position information and the position information do not match (determines that the first authentication process is unsuccessful).

[0095] The second authentication process executed by the authentication unit 152 will be described. In the second authentication process, it is determined whether the first key information included in the tag information matches the previous key information. The authentication unit 152 compares the seat number included in the tag information with the authentication table 142 to identify the previous key information corresponding to the seat number.

[0096] The authentication unit 152 determines that the second authentication process has been successful when the specified previous key information matches the first key information included in the tag information. On the other hand, the authentication unit 152 determines that the second authentication process has failed when the specified previous key information does not match the first key information included in the tag information.

[0097] The third authentication process executed by the authentication unit 152 will be described. In the third authentication process, it is determined whether or not the seat corresponding to the seat number included in the tag information is an available seat. For example, in order to prevent COVID-19, the authentication unit 152 compares the touch date and time and the seat number with the seat history table 143, and if there is no user in the nearby seat, it determines that the seat is available (determines that the third authentication process is successful). On the other hand, if there is a user in the nearby seat, the authentication unit 152 determines that the seat is not available (determines that the third authentication process has failed).

[0098] 13 is a diagram for explaining the processing of the authentication unit. For example, it is assumed that the seats with the seat numbers 8_3_2, 8_4_1, and 8_4_3 are used by other users. In this case, when the seat numbers in the tag information are 8_3_1, 8_3_3, 8_4_2, and 8_4_3, the authentication unit 152 determines that the seats are unavailable. When the seat number in the tag information is 8_3_4, the authentication unit 152 determines that the seats are available.

[0099] Returning to the description of Fig. 9, when the write control unit 153 acquires information indicating that the authentication has been successful from the authentication unit 152, the write control unit 153 generates second key information different from the first key information included in the tag information transmitted from the terminal device 50. The write control unit 153 transmits the second key information to the terminal device 50, thereby causing the terminal device 50 to execute a process of writing the second key information and the registration information into the IC tag 11.

[0100] The write control unit 153 compares the seat number included in the tag information with the authentication table 142, specifies the corresponding key information history in the authentication table 142, and additionally registers the second key information.

[0101] On the other hand, when the write control unit 153 receives information from the authentication unit 152 that the authentication has failed, the write control unit 153 transmits error information to the terminal device 50.

[0102] When the registration unit 154 receives a write completion notification transmitted from the terminal device 50, the registration unit 154 registers the tag information and registration information in the registration DB 141.

[0103] The generating unit 155 is a processing unit that generates seat usage status for each date and time based on the registration DB 141 and registers it in the seat history table 143. For example, the generating unit 155 selects a seat number in the registration DB 141, scans the attendance information for one day corresponding to the selected seat number, and specifies the time from arrival at work to leaving work as being in use. The generating unit 155 specifies the terminal ID and user ID when the attendance information is set to arrival at work. The generating unit 155 executes the above process for each date and each seat number to specify the usage status, terminal ID, and user ID corresponding to the seat number at each date and time. In addition, the generating unit 155 sets a comment corresponding to the date and time of the seat usage status in the seat history table 143 from the relationship between the seat number, touch date and time, and comment in the registration DB 141.

[0104] The transmission unit 156 is a processing unit that transmits information of the seat history table 143 to the view server 200. When the seat history table 143 is updated by the generation unit 155, the transmission unit 156 transmits the updated information of the seat history table 143 to the view server 200.

[0105] [1-6. Configuration of the view server 200 according to the embodiment] Next, the configuration of the view server 200 shown in Fig. 1 will be described with reference to Fig. 14. Fig. 14 is a diagram showing an example of the configuration of the view server 200 according to this embodiment. As shown in Fig. 14, the view server 200 has a communication unit 210, an input unit 220, a display unit 230, a storage unit 240, and a control unit 250.

[0106] The communication unit 210 is realized by, for example, a NIC etc. The communication unit 210 is connected to the network 5 by wired or wireless connection, and transmits and receives information between the terminal device 50, the registration server 100, and other terminal devices via the network 5.

[0107] The input unit 220 is an input device for inputting various information to the view server 200. The input unit 220 corresponds to a keyboard, a mouse, a touch panel, or the like.

[0108] The display unit 230 is a display device that displays various information output from the control unit 250. The display unit 230 corresponds to a liquid crystal display, an organic EL display, a touch panel, or the like.

[0109] The storage unit 240 is realized by, for example, a semiconductor memory element such as a RAM or a flash memory, or a storage device such as a hard disk or an optical disk. The storage unit 240 stores various data used for information processing. The storage unit 240 has a user management table 241, seat layout data 242, and a seat history table 143.

[0110] The user management table 241 is a table that holds various information related to users. FIG. 15 is a diagram showing an example of the data structure of the user management table 241 according to this embodiment. As shown in FIG. 15, the user management table 241 associates a user ID, a name, and an affiliation department. The user ID is information that identifies a user. The name is the name of the user. The affiliation department is the department to which the user belongs.

[0111] The seat layout data 242 is an image of the layout of each seat. Fig. 16 shows an example of the data structure of the seat layout data 242 according to this embodiment. Each seat in the seat layout data 242 is associated with a seat number.

[0112] The seat history table 143 is a table for storing the history of the usage status of each seat. The explanation of the seat history table 143 is the same as that of FIG.

[0113] The control unit 250 is realized, for example, by a CPU, an MPU, or the like executing a program stored in the view server 200 using a RAM or the like as a working area. The control unit 250 is also a controller, and may be realized, for example, by an integrated circuit such as an ASIC or an FPGA.

[0114] The control unit 250 includes a receiving unit 251 and a service providing unit 252. The service providing unit 252 is an example of a providing unit.

[0115] The receiving unit 251 receives the seat history table 143 from the registration server 100, and stores the received seat history table in the storage unit 240. When the receiving unit 251 receives a new seat history table 143, the receiving unit 251 updates the seat history table 143 in the storage unit 240 with the received seat history table 143.

[0116] The service providing unit 252 is a processing unit that generates a seat status screen and displays it on the terminal device 50 when a display request for a seat status screen is received from the terminal device 50 or the like. For example, when the service providing unit 252 receives a date and time setting from the terminal device 50, it extracts the seat usage status corresponding to the received date and time from the seat history table 143.

[0117] The service providing unit 252 identifies each coordinate number, usage status, and user ID set in the extracted coordinate usage status. The service providing unit 252 identifies a name corresponding to the user ID based on the identified user ID and the user management table 241. The service providing unit 252 generates a seat status screen (for example, seat status screen 25) based on the usage status corresponding to each seat number, the user's name, and the seat layout data 242.

[0118] When the service providing unit 252 does not receive a date and time setting from the terminal device 50, the service providing unit 252 may generate the seat status information based on the current date and time.

[0119] When the service providing unit 252 detects that a user operating the terminal device 50 has placed a mouse or the like over a seat that is in use, it displays a comment associated with the seat number of the seat that is overlaid.

[0120] [1-7. Processing procedure of terminal device 50 according to the embodiment] Next, an example of the processing procedure of the terminal device 50 shown in Fig. 8 will be described. Fig. 17 is a flowchart showing the processing procedure of the terminal device according to this embodiment. As shown in Fig. 17, the reader / writer control unit 57c of the terminal device 50 acquires the first key information and the seat number from the IC tag 11 using the reader / writer 52 (step S301).

[0121] In the terminal device 50, the display control unit 57d displays a registration screen on the touch panel 55 and acquires registration information (step S302). The transmitting / receiving unit 57a of the terminal device 50 determines whether the network 5 is available (step S303).

[0122] When the network 5 is not available (step S303, No), the terminal device 50 executes a process for when the network 5 is unavailable (step S304). On the other hand, when the network 5 is available (step S303, Yes), the transmitting / receiving unit 57a transmits the tag information and the registration information (terminal information, attendance information) to the registration server 100.

[0123] When the reader / writer control unit 57c of the terminal device 50 receives the second key information from the registration server 100 (step S306, Yes), it controls the reader / writer 52 to write the second key information, the terminal information, and the attendance information to the IC tag 11 (step S307). The reader / writer control unit 57c transmits a write completion notification to the registration server 100 via the transmitting / receiving unit 57a (step S308).

[0124] On the other hand, if the second key information is not received from the registration server 100, the display control unit 57d causes an error to be displayed on the touch panel 55 (step S309).

[0125] Here, the process when the IC tag 11 is unusable, explained in step S304 of Fig. 17, will be explained. Fig. 18 is a flowchart showing the process when the IC tag 11 is unusable. As shown in Fig. 18, the reader / writer control unit 57c of the terminal device 50 controls the reader / writer 52 to write the first key information and registration information into the IC tag 11 (step S401).

[0126] The terminal device 50 waits until the network 5 is restored (step S402). If the network 5 is restored when the terminal device 50 is brought close to the holding mark of the IC card 10 by the user, the terminal device 50 executes the processes from step S403 onward.

[0127] The reader / writer control unit 57c controls the reader / writer 52 to read the first key information, the seat number, and multiple pieces of registration information from the IC tag 11 (step S403). The registration information read in step S403 is the registration information for which the flag in the registration information table 11c is set to "OFF."

[0128] The transmitting / receiving unit 57a of the terminal device 50 transmits the tag information (first key information, seat number) and the plurality of pieces of registration information to the registration server 100 (step S404).

[0129] When the reader / writer control unit 57c receives the second key information from the registration server 100 (step S405, Yes), it controls the reader / writer 52 to write the second key information into the IC tag 11 (step S405). The reader / writer control unit 57c transmits a write completion notification to the registration server 100 via the transmitting / receiving unit 57a (step S407).

[0130] On the other hand, if the second key information is not received from the registration server 100, the display control unit 57d causes an error to be displayed on the touch panel 55 (step S408).

[0131] [1-8. Processing procedure of the registration server 100 according to the embodiment] Next, an example of the processing procedure of the registration server 100 shown in Fig. 9 will be described. Fig. 19 is a flowchart showing the processing procedure of the registration server 100 according to this embodiment. As shown in Fig. 19, the receiving unit 151 of the registration server 100 receives tag information (first key information) and registration information (terminal information, attendance information) from the terminal device 50 (step S501).

[0132] The authentication unit 152 of the registration server 100 executes an authentication process (step S502). For example, in step S502, the authentication unit 152 executes the first authentication process, the second authentication process, and the third authentication process described above.

[0133] If all authentications are successful in the first to third authentication processes, the authentication unit 152 determines that the authentication is successful (Yes in step S503) and proceeds to step S504. On the other hand, if authentication is unsuccessful in any of the first to third authentication processes, the authentication unit 152 determines that the authentication is unsuccessful (No in step S503) and proceeds to step S507.

[0134] The description of step S504 will be continued. The writing control unit 153 of the registration server 100 generates second key information different from the first key information, and transmits it to the terminal device 50 (step S504). When the registration unit 154 of the registration server 100 receives a writing completion notification from the terminal device 50, it registers the tag information and registration information in the registration DB 141 (step S505). The registration unit 154 transmits a registration completion notification to the terminal device 50 (step S506).

[0135] The following is an explanation of step S507. The write control unit 153 transmits an error to the terminal device 50 (step S507).

[0136] [1-9. Effects of the embodiment] As described above, the registration server 100 (server) according to this embodiment receives, from a terminal device that reads and writes information from the IC tag, tag information including the first key information recorded in the IC tag and information regarding the attachment position of the IC tag, attendance information of the user, and terminal information including information regarding the terminal device 50. If authentication based on the tag information and terminal information is successful, the server transmits second key information associated with the tag to the terminal device 50 and causes the terminal device 50 to execute a process of writing the second key information, terminal information, and attendance information to the IC tag. This allows the terminal information and attendance information to be stored not only in the registration server 100 but also in the IC tag 11 (allowing for double storage).

[0137] The registration server 100 performs authentication based on the tag information and the terminal information, thereby preventing unauthorized use of the IC card 10.

[0138] The registration server 100 performs authentication based on the previous key information that the write control unit 153 sent to the terminal device 50 and had written in the IC tag, and the first key information. This makes it possible to prevent fraudulent acts such as illegally copying information in the IC tag 11 to the terminal device 50 and registering based on the copied information.

[0139] The registration server 100 performs authentication based on the tag information and the location information of the terminal device 50. This makes it possible to prevent someone from illegally taking the IC card 10 out of the office and performing registration.

[0140] The registration server 100 performs authentication based on information about the surroundings based on the attachment position of the IC tag 11. This makes it possible to prevent users from gathering in close proximity to one another, thus preventing infection.

[0141] When the registration server 100 receives a completion notification of writing to the IC tag 11 from the terminal device 50, it registers the tag information, terminal information, and attendance information in the registration DB 141. The terminal information further includes the time when the terminal device 50 reads the first key information from the IC tag 11. This allows the registration server 100 to store the terminal information and attendance information in conjunction with the information registration of the IC tag 11.

[0142] The registration server 100 generates a seat history table in which the seats corresponding to the attachment positions of the IC tags 11 are associated with the attendance information of the users, based on the registration DB 141. This makes it possible to manage the usage status of each seat.

[0143] The view server 200 (server) provides screen information that visually associates the seats corresponding to the attachment positions of the IC tags 11 with the attendance information of the users according to the specified time. This makes it possible to notify the usage status of each seat corresponding to the specified time.

[0144] The registration server 100 further executes a process of generating second key information different from the first key information, thereby making it possible to increase the reliability of the authentication process.

[0145] The terminal device 50 reads the tag information, including the first key information and information on the attachment position of the IC tag 11, from the IC tag 11, and obtains the user's attendance information and terminal information, including information on the terminal device 50 itself. The terminal device 50 transmits the tag information, terminal information, and attendance information to a server (registration server 100). When the server (registration server 100) is successful in authenticating the terminal device 50 based on the tag information and terminal information and the terminal device 50 receives second key information from the server, the terminal device 50 writes the second key information, terminal information, and attendance information to the IC tag. This allows the terminal information and attendance information to be stored not only in the registration server 100 but also in the IC tag 11 (allowing double storage).

[0146] When the network 5 between the terminal device 50 itself and the server cannot be used, the terminal device 50 writes the tag information, the terminal information, and the attendance information to the IC tag 11. This makes it possible to leave a history in the IC tag 11 even when the network 5 cannot be used.

[0147] When the network 5 changes from unavailable to available, the terminal device 50 reads the tag information from the IC tag 11 and one or more pieces of terminal information and attendance information that have not been transmitted to the server, and transmits the read information to the server. This makes it possible to request the server to perform authentication and registration processes after the network is restored.

[0148] [2. Other embodiments] The processes of the terminal device 50, the registration server 100, and the view server 200 included in the system 1 described in the above embodiment are merely examples, and other processes may be executed.

[0149] In the system 1 of this embodiment, the number of selectable seats and the location of the seats may be changed depending on the position. For example, the registration server 100 registers the number of selectable seats and the seats (seat numbers) for each position in advance, and performs authentication based on the information transmitted from the terminal device 50.

[0150] In the system 1, the seat lock / unlock control may be performed in conjunction with the seat registration of the terminal device 50. For example, the registration server 100 may perform control not to accept registration from terminal devices other than those registered in advance.

[0151] The registration server 100 may count the number of times a seat is used and the duration of use, and may predict when to replace consumables. The registration server 100 may also determine whether the seat is in order by acquiring image information after the user has finished using the seat.

[0152] The registration server 100 may accept advance seat reservations from each terminal device. For example, when performing the third authentication process, the authentication unit 152 of the registration server 100 may determine that the seat corresponding to the seat number included in the tag information is reserved and the terminal ID of the reserved seat is different from the terminal ID of the terminal information, and the seat is not available.

[0153] In the above-mentioned system 1, as an example, the registration server 100 and the view server 200 are described as separate servers, but the present invention is not limited to this, and the registration server 100 and the view server 200 may be one server. For example, the registration server 100 may have the functions of the view server 200 described in FIG. 14.

[0154] [3. Hardware configuration] Information devices such as the registration server 100 and the view server 200 according to each of the above-described embodiments are realized by a computer 1000 having a configuration as shown in FIG. 20, for example. FIG. 20 is a hardware configuration diagram showing an example of a computer that realizes the functions of the registration server 100 and the view server 200. The registration server 100 according to the embodiment will be described below as an example. The computer 1000 has a CPU 1100, a RAM 1200, a ROM (Read Only Memory) 1300, a HDD (Hard Disk Drive) 1400, a communication interface 1500, and an input / output interface 1600. Each unit of the computer 1000 is connected by a bus 1050.

[0155] The CPU 1100 operates and controls each unit based on programs stored in the ROM 1300 or the HDD 1400. For example, the CPU 1100 loads the programs stored in the ROM 1300 or the HDD 1400 into the RAM 1200 and executes processes corresponding to the various programs.

[0156] The ROM 1300 stores boot programs such as a basic input output system (BIOS) executed by the CPU 1100 when the computer 1000 is started, and programs that depend on the hardware of the computer 1000.

[0157] HDD 1400 is a computer-readable recording medium that non-temporarily records programs executed by CPU 1100 and data used by such programs. Specifically, HDD 1400 is a recording medium that records an information processing program according to the present disclosure, which is an example of program data 1450.

[0158] The communication interface 1500 is an interface for connecting the computer 1000 to an external network 1550 (e.g., the Internet). For example, the CPU 1100 receives data from other devices and transmits data generated by the CPU 1100 to other devices via the communication interface 1500.

[0159] The input / output interface 1600 is an interface for connecting the input / output device 1650 and the computer 1000. For example, the CPU 1100 receives data from an input device such as a keyboard or a mouse via the input / output interface 1600. The CPU 1100 also transmits data to an output device such as a display, a speaker, or a printer via the input / output interface 1600. The input / output interface 1600 may also function as a media interface for reading a program or the like recorded on a predetermined recording medium. The medium may be, for example, an optical recording medium such as a DVD (Digital Versatile Disc) or a PD (Phase change rewritable Disk), a magneto-optical recording medium such as an MO (Magneto-Optical disk), a tape medium, a magnetic recording medium, or a semiconductor memory.

[0160] For example, when the computer 1000 functions as the registration server 100 according to the embodiment, the CPU 1100 of the computer 1000 executes a program loaded on the RAM 1200 to realize functions of the control unit 150, etc. Also, the HDD 1400 stores the program according to the present disclosure and data in the storage unit 140. Note that the CPU 1100 reads and executes the program data 1450 from the HDD 1400, but as another example, the CPU 1100 may obtain these programs from other devices via an external network 1550.

[0161] It is also possible to realize the functions of the terminal device 50 by the computer 1000 described in Fig. 20. For example, the CPU 1100 of the computer corresponding to the terminal device 50 realizes the functions of the control unit 57 and the like by executing a program loaded on the RAM 1200. The information processing program according to the present disclosure and data in the storage unit 56 are stored in the HDD 1400. The CPU 1100 reads and executes the program data 1450 from the HDD 1400, but as another example, the CPU 1100 may obtain these programs from other devices via an external network 1550.

[0162] [4. Conclusion] The server includes a receiving unit that receives, from a terminal device that reads and writes information from the tag, tag information including first key information recorded in the tag and information regarding the attachment position of the tag, user attendance information, and terminal information including information regarding the terminal device, and a write control unit that, when authentication based on the tag information and the terminal information is successful, transmits second key information associated with the tag to the terminal device and causes the terminal device to execute a process of writing the second key information, the terminal information, and the attendance information to the tag. This allows the terminal information and attendance information to be stored not only in the server but also in the tag (allowing for double storage).

[0163] The server further has an authentication unit that performs authentication based on the tag information and the terminal information. The authentication unit of the server performs authentication based on the previous key information that the write control unit transmits to the terminal device and causes it to be written in the tag, and the first key information. This makes it possible to prevent unauthorized use of the IC card. It is also possible to prevent unauthorized use, such as unauthorized copying of tag information to the terminal device 50 and registration based on the copied information.

[0164] The terminal information includes the location information of the terminal device, and the authentication unit of the server performs authentication based on the tag information and the location information of the terminal device. This makes it possible to prevent unauthorized registration of IC cards by illegally taking them out of the office.

[0165] The server's authentication unit performs authentication based on information about the surrounding area based on the tag's attachment position. This helps prevent users from gathering in close proximity to each other, helping to prevent infection.

[0166] The server further has a registration unit which, when receiving a completion notification of writing to the tag from the terminal device, registers the tag information, the user's attendance information, and the terminal information in a database. The terminal information further includes the time when the terminal device reads the first key information from the tag, and the registration unit registers the tag attachment position and the user's attendance information in the database in association with each other. This allows the server to store the terminal information and attendance information in conjunction with the tag information registration.

[0167] The server further includes a generating unit that generates a seat history table that associates the seats corresponding to the tag attachment positions with the attendance information of the users based on the database, thereby making it possible to manage the usage status of each seat.

[0168] The system further includes a provision unit that provides screen information that visually associates the seats corresponding to the tag attachment positions and the attendance information of the users according to a specified time based on the seat history table, thereby making it possible to notify the usage status of each seat corresponding to a specified time.

[0169] The write control unit of the server further executes a process of generating the second key information different from the first key information, thereby making it possible to increase the reliability of the authentication process.

[0170] The terminal device includes a reading unit that reads tag information including first key information and information on the tag attachment position from the tag, an acquiring unit that acquires terminal information including a user's attendance information and information on the terminal device itself, a transmitting unit that transmits the tag information, the terminal information, and the attendance information to a server, and a writing unit that writes the second key information, the terminal information, and the attendance information to the tag when authentication based on the tag information and the terminal information by the server is successful and second key information is received from the server. This allows the terminal information and attendance information to be stored not only in the server but also in the tag (double storage).

[0171] When the network between the terminal device and the server is unavailable, the writing unit of the terminal device writes the tag information, the terminal information, and the attendance information to the tag. This makes it possible to leave a history in the tag even when the network is unavailable.

[0172] When the network is changed from unavailable to available, the reading unit reads the tag information from the tag and one or more pieces of terminal information and attendance information that have not been transmitted to the server, and the transmitting unit transmits the information read by the reading unit to the server. This makes it possible to request the server to perform authentication and registration processes after the network is restored. [Explanation of symbols]

[0173] 5. Network 10 IC Card 11 IC tag 50 Terminal Equipment 51 Communications Department 52 Reader / Writer 53 Camera 54 Timer 55 Touch Panel 56,140,240 storage section 56a Tag Information 56b Registration information 57,150,250 Control section 57a Transmitter / receiver 57b Location information identification section 57c Reader / writer control unit 57d Display control unit 100 Registration Servers 141 Registration DB 142 Authentication Table 143 Seat History Table 151,251 Receiver 152 Authentication Department 153 Write control section 154 Registration Department 155 Generation part 156 Transmitter 200 View Server 241 User Management Table 242 Seat layout data 252 Service Provision Department

Claims

1. a receiving unit that receives, from a terminal device that reads and writes information from the tag, tag information including first key information recorded in the tag and information regarding an attachment position of the tag, user attendance information, and terminal information including information regarding the terminal device; a write control unit that, when authentication based on the tag information and the terminal information is successful, transmits second key information associated with the tag to the terminal device, and causes the terminal device to execute a process of writing the second key information, the terminal information, and the attendance information to the tag; A server comprising:

2. The server according to claim 1 , further comprising an authentication unit that performs authentication based on the tag information and the terminal information.

3. 3. The server according to claim 2, wherein the authentication unit performs authentication based on the previous key information that the write control unit transmitted to the terminal device and caused to be written in the tag, and the first key information.

4. The server according to claim 2 , wherein the terminal information includes location information of the terminal device, and the authentication unit performs authentication based on the tag information and the location information of the terminal device.

5. The server according to claim 2 , wherein the authentication unit performs authentication based on surrounding information based on a position where the tag is attached.

6. The server according to claim 1 , further comprising a registration unit that registers the tag information, the user's attendance information, and the terminal information in a database when a notification of completion of writing to the tag is received from the terminal device.

7. The server according to claim 6, wherein the terminal information further includes the time when the terminal device reads the first key information from the tag, and the registration unit registers the attachment position of the tag in a database in association with the user's attendance information.

8. 7. The server according to claim 6, further comprising a generating unit that generates a seat history table that associates the seats corresponding to the tag attachment positions with the attendance information of the users based on the database.

9. The server according to claim 8, further comprising a provision unit that provides screen information that visually associates the seat corresponding to the tag attachment position according to a specified time with the user's attendance information based on the seat history table.

10. The server according to claim 1 , wherein the write control unit further executes a process of generating the second key information different from the first key information.

11. a reader that reads tag information from the tag, the tag information including first key information and information regarding an attachment position of the tag; An acquisition unit that acquires user attendance information and terminal information including information related to the user's own terminal device; A transmission unit that transmits the tag information, the terminal information, and the attendance information to a server; a writing unit that writes the second key information, the terminal information, and the attendance information into the tag when the authentication based on the tag information and the terminal information by the server is successful and second key information is received from the server; A terminal device is provided.

12. The terminal device according to claim 11 , wherein the writing unit writes the tag information, the terminal information, and the attendance information to the tag when a network between the terminal device itself and the server is unavailable.

13. The terminal device described in claim 12, wherein when the network changes from an unavailable state to an available state, the reading unit reads the tag information from the tag and one or more of the terminal information and the attendance information that have not been transmitted to the server, and the transmission unit transmits the information read by the reading unit to the server.

14. Computer, a reader that reads tag information from the tag, the tag information including first key information and information regarding an attachment position of the tag; An acquisition unit that acquires user attendance information and terminal information including information related to the user's own terminal device; A transmission unit that transmits the tag information, the terminal information, and the attendance information to a server; a writing unit that writes the second key information, the terminal information, and the attendance information into the tag when the authentication based on the tag information and the terminal information by the server is successful and second key information is received from the server. An information processing program that functions as a

15. A management system having a terminal device for reading and writing information to a tag and a server, The server, a receiving unit that receives, from the terminal device, tag information including the first key information recorded in the tag and information regarding the attachment position of the tag, user attendance information, and terminal information including information regarding the terminal device; a write control unit that, when authentication based on the tag information and the terminal information is successful, transmits second key information associated with the tag to the terminal device, and causes the terminal device to execute a process of writing the second key information, the terminal information, and the attendance information to the tag; A management system having:

16. The terminal device reads out tag information from the tag, the tag information including the first key information and information regarding the attachment position of the tag; The terminal device acquires the user's attendance information and terminal information including information about the terminal device itself, The terminal device transmits the tag information, the attendance information of the user, and the terminal information to a server; The server receives the tag information, the attendance information of the user, and the terminal information, When the authentication based on the tag information and the terminal information is successful, the server transmits second key information associated with the tag to the terminal device; The terminal device writes the second key information, the terminal information, and the attendance information to the tag. Management method.

Images