Reception Terminal, Registration Method, Program, and Registration System

Abstract

To effectively use a user terminal in a call in a facility.SOLUTION: A terminal for reception includes a terminal number acquisition unit, a user identification information acquisition unit, and a registration request unit. The terminal number acquisition unit acquires a user terminal number used in a call to a user in a facility. The user identification information acquisition unit acquires user identification information used in predetermined application software installed in a user terminal from the user terminal in response to the user terminal number being acquired by the terminal number acquisition unit. The registration request unit requests association between the acquired user terminal number and user identification information and requests registration indicating that the user terminal number is being used on the basis of the user terminal number and the user identification information.SELECTED DRAWING: Figure 7

Description

Technical Field

[0001] The present invention relates to a reception terminal, a registration method, a program, and a registration system.

Background Art

[0002] Conventionally, in facilities such as hospitals, pharmacies, and food courts, a system has been used in which a lending terminal is lent from the facility to a user waiting in line, and the user is called. As a related technology, there is known a system that accepts reservation for examination, input of a questionnaire, and check-in procedure, guides a user waiting in line for examination, and calls the user based on the examination order (see, for example, Patent Document 1 below). In recent years, it has become common for users to possess a user terminal such as a smartphone on which various applications can be installed.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the above-described conventional technology, there has been a problem that the user terminal cannot be effectively utilized in the call at the facility.

[0005] In view of the above circumstances, an object of the present invention is to provide a technology capable of effectively utilizing a user terminal in a call at a facility.

Means for Solving the Problems

[0006] In view of the above problems, a reception terminal according to an aspect of the present invention includes a terminal number acquisition unit that acquires a user terminal number used for calling a user at a facility, When the user terminal number is acquired by the terminal number acquisition unit, a prompting unit that prompts to acquire user identification information used for a predetermined application software installed in the user terminal, and the prompting is performed by the prompting unit in response to this, from the user terminal the user identification information a user identification information acquisition unit that acquires; and a registration request unit that, based on the acquired user terminal number and the user identification information, makes a request to associate the user terminal number and the user identification information, and a request for registration indicating that the user terminal number is in use, the reception terminal comprising the same.

[0007] Also, a registration method according to an aspect of the present invention is a registration method in which a computer used for a reception terminal executes a terminal number acquisition step of acquiring a user terminal number used for calling a user at a facility, When the user terminal number is acquired in the terminal number acquisition step, a prompting step of prompting to acquire user identification information used for a predetermined application software installed in the user terminal, and the prompting is performed in the prompting step in response to this, from the user terminal the user identification information a user identification information acquisition step of acquiring; and a registration request step of, based on the acquired user terminal number and the user identification information, making a request to associate the user terminal number and the user identification information, and a request for registration indicating that the user terminal number is in use.

[0008] Also, a program according to an aspect of the present invention causes a computer used for a reception terminal to function as a terminal number acquisition unit that acquires a user terminal number used for calling a user at a facility, When the user terminal number is acquired by the terminal number acquisition unit, a prompting unit that prompts to acquire user identification information used for a predetermined application software installed in the user terminal, and the prompting is performed by the prompting unit in response to this, from the user terminal the user identification information a user identification information acquisition unit that acquires; and a registration request unit that, based on the acquired user terminal number and the user identification information, makes a request to associate the user terminal number and the user identification information, and a request for registration indicating that the user terminal number is in use. Also, a registration system according to an aspect of the present invention is a registration system including a user terminal, a reception terminal, and a management device that performs registration related to calling a user at a facility, wherein the reception terminal includes a terminal number acquisition unit that acquires a user terminal number used for the call, When the user terminal number is acquired by the terminal number acquisition unit, a prompting unit that prompts to acquire user identification information used for a predetermined application software installed in the user terminal, and the prompting is performed by the prompting unit in response to this, from the user terminal the user identification information A registration system comprising: a user identification information acquisition unit that acquires; and a registration request unit that, based on the acquired user terminal number and the user identification information, makes a request to the management device to associate the user terminal number and the user identification information, and a request to register indicating that the user terminal number is in use.

Effect of the Invention

[0009] According to the present invention, the user terminal can be effectively utilized in a call at a facility.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4A

Figure 4B

Figure 5A

Figure 5B

Figure 5C

Figure 5D

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16A

Figure 16B

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

Figure 23A

Figure 23B

Figure 24

Embodiments for Carrying Out the Invention

[0011] (Regarding the System Configuration of the Calling System 1) Hereinafter, specific configuration examples of the present invention will be described with reference to the drawings. FIG. 1 is a system configuration diagram showing an example of the system configuration of the calling system 1. The calling system 1 is used in facilities such as hospitals, pharmacies, food courts, administrative institutions (offices, police, etc.). The calling system 1 includes a reception terminal 100, a management device 200, a plurality of lending terminals 300, and a plurality of user terminals 400. Each device is wirelessly connected via the network 10. Also, each device is a computer device equipped with a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), a communication unit, and the like.

[0012] The reception terminal 100 is arranged for each facility and is a terminal device that manages the waiting state of each visiting user and accepts the fact that a call is made to the lending terminal 300 or the user terminal 400. The reception terminal 100 is, for example, a tablet terminal. In the illustration, there is one reception terminal 100, but it is also possible to have a plurality of them.

[0013] The management device 200 manages the reception terminal 100 and also manages the lending terminals 300 and user terminals 400 that are being used. Note that the management device 200 may be provided on the cloud.

[0014] The lending terminal 300 is a terminal device that is arranged for each facility and lent to users. The lending terminal 300 is a dedicated calling terminal device that rings or displays a predetermined message when calling a user.

[0015] The user terminal 400 is a portable terminal device, for example, a smartphone. However, the user terminal 400 is not limited to a smartphone and may be a tablet terminal or a mobile phone. The user terminal 400 is owned by the user, for example, the user's property. However, the user terminal 400 can also be a lent item lent from a store. In addition, in the present embodiment, the user is a user who uses various facilities, for example, including patients in hospitals and pharmacies, customers using food courts, and users of administrative institutions.

[0016] The network 10 is composed of a mobile phone line (such as 5G (5th Generation), 4G (4th Generation: LTE (Long Term Evolution)), etc.), a WAN (Wide Area Network), a LAN (Local Area Network), etc.

[0017] The reception terminal 100 receives operations related to the management of the lending terminal 300 and the user terminal 400 from the facility staff. The operations related to the management are, for example, a lending operation for lending the lending terminal 300 to a user, a registration operation for calling using the user terminal 400, and a calling operation for calling the lending terminal 300 or the user terminal 400. In addition, the operations related to the management also include a return operation for returning the lending terminal 300 and a cancellation operation for canceling the registration of the user terminal 400.

[0018] Note that the reception terminal 100 and the lending terminal 300 are provided for each facility. For example, the reception terminal 100 and the lending terminal 300 are provided in each of the facilities such as Hospital A, Hospital B, Pharmacy C, etc. The reception terminal 100 can manage only the lending terminal 300 provided in the same facility. That is, for example, the lending terminal 300 provided in Hospital B cannot be called from the reception terminal 100 of Hospital A. The management device 200 manages the reception terminal 100, the lending terminal 300, and the user terminal 400, which are used in a plurality of facilities.

[0019] (Regarding the functional configuration of the reception terminal 100) FIG. 2 is a functional block diagram showing an example of the functional configuration of the reception terminal 100. The reception terminal 100 includes a communication unit 110, an input unit 111, a display unit 112, an imaging unit 113, a facility information storage unit 141, and a control unit 120.

[0020] The communication unit 110 is a network interface. The communication unit 110 communicates with the management device 200 via the network 10. The input unit 111 is configured using input devices such as a touch panel and buttons. The display unit 112 is an output device such as a liquid crystal display or an organic EL (Electro Luminescence) display. Since the display unit 112 is a touch panel display, it has the function of the input unit 111. The imaging unit 113 is configured by, for example, a CCD (Charge Coupled Device) image sensor or a CMOS (Complementary Metal Oxide Semiconductor) image sensor.

[0021] The facility information storage unit 141 is a storage device such as a magnetic hard disk device or a semiconductor storage device. The facility information storage unit 141 stores a facility code. The facility code is a code for uniquely identifying a facility.

[0022] (Regarding the facility code) Here, the facility code will be described with reference to FIG. 5A. FIG. 5A is an explanatory diagram showing an example of a facility code. As shown in FIG. 5A, the facility code of the facility where the calling system 1 is used is "abc". The management device 200 can determine which facility's reception terminal 100 the communication partner is by using the facility code to communicate with the reception terminal 100 of each facility.

[0023] (Regarding the control unit 120) In FIG. 2, the control unit 120 controls the operations of each part of the reception terminal 100. The control unit 120 includes a display control unit 121, a management operation reception unit 122, a lending terminal unique number acquisition unit 123, a terminal number acquisition unit 124, a two-dimensional code reading unit 125, a lending terminal state management unit 126, a user ID acquisition unit 127, a registration request unit 128, a notification request unit 129, and a reminder unit 130. Each functional unit included in the control unit 120 is realized by the CPU of the reception terminal 100. That is, by the CPU executing a registration program stored in the memory or auxiliary storage device, the functions of each functional unit included in the control unit 120 are realized.

[0024] The display control unit 121 controls the screen to be displayed on the display unit 112. The management operation reception unit 122 (an example of a reception unit) receives operations related to the management of the lending terminal 300 and the user terminal 400 using the lending terminal number described later.

[0025] (Regarding the acquisition of information related to the lending terminal 300) First, the acquisition of information related to the lending terminal 300 will be described. The lending terminal unique number acquisition unit 123 acquires a lending terminal unique number (an example of lending terminal destination information). The lending terminal unique number is a number used for communication between the lending terminal 300 and the management device 200. Specifically, the lending terminal unique number is a number unique to the terminal, and it can also be a SIM number or a phone number.

[0026] The lending terminal 300 can encode and display its own unique lending terminal number. The code may be, for example, a two-dimensional code, but it may also be a one-dimensional code. Note that, for the other codes described below, although they are represented by two-dimensional codes, they may also be one-dimensional codes.

[0027] The imaging unit 113 images the two-dimensional code displayed on the lending terminal 300. The two-dimensional code reading unit 125 reads the two-dimensional code imaged by the imaging unit 113. Specifically, the two-dimensional code reading unit 125 reads the two-dimensional code in the subject imaged by the imaging unit 113 and decodes the two-dimensional code.

[0028] The lending terminal unique number acquisition unit 123 acquires the unique lending terminal number decoded by the two-dimensional code reading unit 125. Note that, including each two-dimensional code described below, the two-dimensional code is not limited to being read from the imaging result by the imaging unit 113, and it is also possible to read it from the reading result of a code reader (not shown).

[0029] The terminal number acquisition unit 124 acquires the lending terminal number. The lending terminal number is the number attached to a so-called number tag. The lending terminal number is composed of, for example, fewer characters than the number of characters constituting the unique lending terminal number. In the present embodiment, the lending terminal number is, for example, numbers such as "1", "2", "3". However, the lending terminal number and the user terminal number described later are not limited to numbers, and it is also possible to use alphabets or kana (a, i, u, e, o). The lending terminal number is associated with the unique lending terminal number in advance.

[0030] In the facility, the lending terminal number is encoded in a two-dimensional code and drawn on a medium (code plate). The code plate (hereinafter referred to as the "lending terminal code plate") is stored in a pair (set) with the lending terminal 300 on a tray corresponding to the lending terminal number. For example, when there are 10 lending terminals 300, 10 corresponding lending terminal code plates are prepared.

[0031] Here, the code plate for the lending terminal will be described with reference to FIG. 6. FIG. 6 is an explanatory diagram showing an example of the code plate. FIG. 6(A) shows an example of the code plate for the lending terminal. In FIG. 6(A), on the code plate 170 for the lending terminal, a two-dimensional code 171 indicating the lending terminal number is drawn. The code plate 170 for the lending terminal is made of plastic, for example, the size of a credit card. Also, "Terminal Number 1" is drawn so that the operator can visually confirm the lending terminal number. Thus, the facility staff can confirm the number (numerical value) of the code plate 170 for the lending terminal and lend the lending terminal 300 to the user.

[0032] Returning to FIG. 2, the imaging unit 113 images the two-dimensional code drawn on the code plate 170 for the lending terminal. The two-dimensional code reading unit 125 (an example of a reading unit) reads the two-dimensional code imaged by the imaging unit 113. The terminal number acquisition unit 124 acquires the lending terminal number decoded by the two-dimensional code reading unit 125. The lending terminal number is pre-associated with the lending terminal unique number acquired by the lending terminal unique number acquisition unit 123 in the management device 200.

[0033] Note that the mode of acquiring the lending terminal number by the terminal number acquisition unit 124 is not limited to code reading. For example, it may be a mode of obtaining the number (numerical value) described on the code plate 170 for the lending terminal by image recognition.

[0034] The lending terminal state management unit 126 manages the state of each lending terminal 300 (such as the charge level and whether it is on loan).

[0035] (Regarding the acquisition of information related to the user terminal 400) Next, the acquisition of information related to the user terminal 400 will be described. The terminal number acquisition unit 124 acquires the user terminal number. The user terminal number is the number attached to a so-called number tag. The user terminal number is a number that enables the facility staff to easily grasp that it is different from the lent terminal number. For example, the user terminal number is represented by alphabets such as "A", "B", "C". Note that the user terminal number is not limited to alphabets and may be, for example, three-digit numbers or kana.

[0036] In the facility, the user terminal number is encoded and drawn as a two-dimensional code on a code plate (hereinafter referred to as the "user terminal code plate"), similar to the lent terminal number. The user terminal code plate is stored alone, for example, on a tray corresponding to the user terminal number. For example, when assuming that up to 10 user terminals 400 are to be registered, 10 user terminal code plates are prepared.

[0037] Here, with reference to FIG. 6(B), the user terminal code plate will be described. FIG. 6(B) shows an example of the user terminal code plate. In FIG. 6(B), on the user terminal code plate 180, a two-dimensional code 181 indicating the user terminal number is drawn. The user terminal code plate 180 is made of plastic, for example, the size of a credit card. Also, "Terminal Number A" is drawn so that the operator can visually confirm the user terminal number. Thereby, the facility staff can confirm the number (alphabet) of the user terminal code plate 180 and register the user terminal 400.

[0038] Returning to FIG. 2, the imaging unit 113 images the two-dimensional code 181 drawn on the user terminal code plate 180. The two-dimensional code reading unit 125 reads the two-dimensional code imaged by the imaging unit 113. The terminal number acquisition unit 124 acquires the user terminal number decoded by the two-dimensional code reading unit 125. Note that the mode of acquiring the user terminal number by the terminal number acquisition unit 124 is not limited to code reading. For example, it may be a mode of obtaining the number (alphabet) described on the user terminal code plate 180 by image recognition.

[0039] The user ID acquisition unit 127 (an example of the user identification information acquisition unit) acquires user identification information (user ID). The user ID is user identification information used when using a predetermined application software (hereinafter referred to as the "call application") already installed in the user terminal 400. The user ID is an ID dedicated to the call application assigned to the user. The call application is an application having a notification function, for example, an application of SNS (Social Networking Service). Specifically, the call application is a chat application such as the LINE (registered trademark) application. However, the predetermined application is not limited to this, and may be a message application, a talk application, or other applications such as SMS (Short Message Service).

[0040] When the user terminal number acquisition unit 124 acquires the user terminal number, the user ID acquisition unit 127 acquires the user ID from the user terminal 400. The mode of acquiring the user ID by the user ID acquisition unit 127 is, for example, by reading a code. Specifically, the user terminal 400 encodes the user ID into a one-dimensional code and a two-dimensional code, and can display them respectively. However, the user ID only needs to be encoded by at least one of the one-dimensional code and the two-dimensional code. The imaging unit 113 images the two-dimensional code displayed on the user terminal 400. The two-dimensional code reading unit 125 reads the two-dimensional code imaged by the imaging unit 113. Specifically, the two-dimensional code reading unit 125 reads the two-dimensional code in the subject imaged by the imaging unit 113 and decodes the two-dimensional code. The user ID acquisition unit 127 acquires the user ID decoded by the two-dimensional code reading unit 125.

[0041] Note that the mode of acquiring the user ID by the user ID acquisition unit 127 is not limited to reading a code. For example, the communication unit 110 may receive the user ID from the user terminal 400 by short-range wireless communication. Examples of short-range wireless communication include NFC (Near Field Communication), Bluetooth (registered trademark), and infrared communication.

[0042] Based on the acquired user terminal number and user ID, the registration request unit 128 requests registration related to the user's call (hereinafter referred to as "outgoing registration of the user terminal 400"). Specifically, the outgoing registration of the user terminal 400 includes associating the user terminal number with the user ID and registering that the user terminal number is in use. The registration that the user terminal number is in use specifically means setting the usage status of the user terminal number (for example, "not in use" and "in use") to "in use".

[0043] In this embodiment, the functional unit for performing the going-out registration of the user terminal 400 is provided in the management device 200. Therefore, the registration request unit 128 requests the management device 200 to perform the going-out registration of the user terminal 400. However, the functional unit for performing the going-out registration of the user terminal 400 may be provided in the reception terminal 100. In this case, the registration request unit 128 may request the corresponding functional unit of its own terminal to perform the going-out registration of the user terminal 400.

[0044] When the user terminal number registered as being in use is acquired by the terminal number acquisition unit 124, the notification request unit 129 requests the calling application using the user ID associated with the user terminal number to send a notification from the facility. The notification from the facility is, for example, a call prompting a visit to the facility such as "Please return to the reception desk", a notification such as "Please call as there is something to confirm", or a notification such as "Today's business has ended." for a user who does not return within business hours. When the two-dimensional code 181 drawn on the user terminal code plate 180 is read and the user terminal number is acquired, the management operation reception unit 122 receives an operation indicating a call. When the operation is received, the notification request unit 129 requests the management device 200 to make a call in the calling application.

[0045] (Regarding the registration request of the loan terminal 300) Based on the loan terminal number acquired by the terminal number acquisition unit 124, the registration request unit 128 requests registration related to the call of the loan terminal 300 (hereinafter referred to as "going-out registration of the loan terminal 300"). The going-out registration of the loan terminal 300 is a registration indicating that the loan terminal number is in use. Specifically, the registration indicating that the loan terminal number is in use means setting the usage status of the user terminal number (for example, "not in use" and "in use") to "in use".

[0046] In this embodiment, the functional unit that performs the going-out registration of the lending terminal 300 is provided in the management device 200. Therefore, the registration request unit 128 requests the management device 200 to perform the going-out registration of the lending terminal 300. However, the functional unit that performs the going-out registration of the lending terminal 300 may be provided in the reception terminal 100. In this case, the registration request unit 128 may request the functional unit of its own terminal to perform the going-out registration of the lending terminal 300.

[0047] When the lending terminal number indicating being in use is acquired by the terminal number acquisition unit 124, the notification request unit 129 requests the lending terminal 300 at the destination indicated by the lending terminal unique number (such as the SIM number) associated with the lending terminal number to issue a notification from the facility. Specifically, when the two-dimensional code 171 drawn on the lending terminal code plate 170 is read and the lending terminal number is acquired, the management operation reception unit 122 receives an operation indicating a call. When the operation is received, the notification request unit 129 requests the management device 200 to make a call to the lending terminal 300.

[0048] (Regarding the urging for obtaining the user ID) When the user terminal number is acquired by the terminal number acquisition unit 124, the urging unit 130 urges the user ID acquisition unit 127 to acquire the user ID. Specifically, after the two-dimensional code 181 of the user terminal code plate 180 is read by the two-dimensional code reading unit 125, the urging unit 130 prompts the user terminal 400 to read the user ID represented by the two-dimensional code 471 (see FIG. 11(A)). Thereby, the facility staff can be made to perform the reading operation of the two-dimensional code 181 of the user terminal code plate 180 and the reading operation of the two-dimensional code 471 of the user terminal 400.

[0049] The registration request unit 128 requests the management device 200 to perform the going-out registration of the user terminal 400 based on the user ID acquired by the user ID acquisition unit 127 in response to the urging of the urging unit 130 and the user terminal number.

[0050] Since the lending terminal number and the unique number of the lending terminal are associated in advance, when the lending terminal number is acquired by the terminal number acquisition unit 124, the urging unit 130 does not urge the lending terminal unique number acquisition unit 123 to acquire the unique number of the lending terminal. Specifically, after the two-dimensional code 171 of the lending terminal code plate 170 is read by the two-dimensional code reading unit 125, the urging unit 130 does not prompt the reading of the unique number of the lending terminal. That is, when lending out the lending terminal 300, the facility staff only performs the reading operation of the two-dimensional code 181 of the user terminal code plate 180 for the reading operation of the two-dimensional code.

[0051] (Regarding operations received from facility staff) The management operation reception unit 122 receives various operations from the facility staff via the input unit 111. In response to the management operation reception unit 122 receiving an operation indicating a call, the notification request unit 129 makes a call to prompt a visit to the facility.

[0052] In addition, when the registration request unit 128 receives an operation indicating a visited (going out release) from the management operation reception unit 122, it requests the release of the going out registration. The release of the going out registration is to release the association between the user terminal number and the user ID, and register the user terminal number with the use status of the user terminal number indicating "not in use". Thereby, the management device 200 releases the association between the user terminal number and the user ID, and sets the use status of the user terminal number to "not in use".

[0053] Supplementary to the release of the going out registration of the lending terminal 300, when the registration request unit 128 receives an operation indicating the release of going out from the management operation reception unit 122, it requests the management device 200 to register the user terminal number as not in use. In this case, the management device 200 does not release the association between the lending terminal number and the unique number of the lending terminal, but sets the use status of the lending terminal number to "not in use".

[0054] Note that all or part of each functional unit included in the control unit 120 may be implemented using hardware such as an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array). The registration program may be recorded on a computer-readable recording medium. A computer-readable recording medium is, for example, a portable medium such as a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, or a storage device such as a hard disk built into a computer system. The registration program may be transmitted via an electric communication line.

[0055] Also, regarding the control units of the other devices (management device 200, lending terminal 300, user terminal 400) described below, it is assumed that they are realized by a CPU, but they may also be realized using hardware such as an ASIC, a PLD, or an FPGA. Also, regarding the various programs to be executed on the other devices, they may be recorded on a computer-readable recording medium such as a portable medium like a flexible disk, a magneto-optical disk, a ROM, or a CD-ROM, or a hard disk built into a computer system, or they may be transmitted via an electric communication line.

[0056] (Regarding the functional configuration of the management device 200) FIG. 3 is a functional block diagram showing an example of the functional configuration of the management device 200. The management device 200 includes a communication unit 210, an associated terminal number storage unit 241, and a control unit 220. The communication unit 210 is a network interface. The communication unit 210 communicates with the reception terminal 100, the lending terminal 300, and the user terminal 400 via the network 10. In communication with the user terminal 400, the communication unit 210 communicates via an application management server (not shown) that manages the calling application. The associated terminal number storage unit 241 is configured using a storage device such as a magnetic hard disk device or a semiconductor storage device. The associated terminal number storage unit 241 stores a terminal management table.

[0057] (Example of Terminal Management Table) Here, an example of the terminal management table will be described with reference to FIG. 5B. FIG. 5B is an explanatory diagram showing an example of the terminal management table. In FIG. 5B, (A) shows the lending terminal management table for the lending terminal 300. The lending terminal management table is a table stored in advance and is generally a table that is not updated.

[0058] In (A) of FIG. 5B, the lending terminal management table includes a facility code, a lending terminal number, a SIM number, and a usage status. For example, in a facility with a facility code of "abc", it shows that a plurality of lending terminals 300 with lending terminal numbers such as "1" to "3" are used. Also, a unique lending terminal number is associated with each lending terminal number. For example, a SIM number "XY0123456789123" is associated with the lending terminal number "1". The usage status of the lending terminal number "1" indicates "in use".

[0059] By using the lending terminal management table, when the management device 200 receives the facility code and the lending terminal number from the reception terminal 100, it can identify the corresponding unique lending terminal number. That is, even if the unique lending terminal number is not included in the information received from the reception terminal 100, the management device 200 can identify the unique lending terminal number.

[0060] In FIG. 5B, (B) shows the user terminal management table for the user terminal 400. The user terminal management table is a table in which the user ID is appropriately updated according to the going-out registration and going-out cancellation (cancellation of going-out registration) of the user terminal 400.

[0061] In (B) of FIG. 5B, the user terminal management table includes a facility code, a user terminal number, a user ID, and a usage status. For example, in a facility with a facility code of "abc", it indicates that a plurality of user terminals 400 with user terminal numbers such as "A" to "G" are available. Also, each user terminal number is associated with a user ID. For example, the user ID "12343212334456900" is associated with the user terminal number "A". The usage status indicates "in use" when the user terminal number and the user ID are associated. Also, the user ID of the user terminal number "F" is blank, that is, the user terminal number and the user ID are not associated, and the usage status indicates "not in use".

[0062] By using the user terminal management table, when the management device 200 receives a facility code, a user terminal number, and a user ID from the reception terminal 100, it associates them. Also, by using the user terminal management table, when the management device 200 receives a facility code and a user terminal number from the reception terminal 100, it can identify the corresponding user ID. That is, even if the received information from the reception terminal 100 does not include a user ID, the management device 200 can identify the user ID.

[0063] (Regarding the control unit 220) In FIG. 3, the control unit 220 controls the operations of each part of the management device 200. The control unit 220 includes an association unit 221, a registration unit 222, and a lent terminal status acquisition unit 223. Each functional unit included in the control unit 220 is realized by the CPU of the management device 200. That is, by the CPU executing a management program stored in a memory or an auxiliary storage device, the functions of each functional unit included in the control unit 220 are realized.

[0064] When the paging system 1 is operated, first, the SIM number and the terminal number are linked. Specifically, when there is a registration request from the reception terminal 100 requesting linking for the lending terminal 300 before operation, the linking unit 221 links the transmitted SIM number with the lending terminal number and registers them in advance in the lending terminal management table together with the facility code. When the linking by the linking unit 221 is completed, the lending terminal number is transmitted to the lending terminal 300. This allows the lending terminal 300 to obtain the lending terminal number assigned to itself before operation.

[0065] Furthermore, the linking unit 221 links the user ID transmitted from the reception terminal 100 in the request for registering the user terminal 400 going out with the user terminal number, and registers the linked user ID and the user terminal number together with the facility code in the user terminal management table.

[0066] The registration unit 222 performs registration indicating that the usage status of the user terminal number transmitted from the reception terminal 100 in the request for outside registration of the user terminal 400 is in use. The registration unit 222 also performs registration indicating that the usage status of the rental terminal number transmitted from the reception terminal 100 in the request for outside registration of the rental terminal 300 is in use.

[0067] The lending terminal status acquisition unit 223 acquires the status (charged amount) from the lending terminal 300. The management device 200 transmits the status acquired by the lending terminal status acquisition unit 223 to the acceptance terminal 100.

[0068] (Functional configuration of the rental terminal 300) FIG. 4A is a functional block diagram showing an example of the functional configuration of the lending terminal 300. The lending terminal 300 includes a communication unit 310, an operation unit 311, a display unit 312, a lending terminal number storage unit 341, and a control unit 320. The communication unit 310 is a network interface. The communication unit 310 communicates with the management device 200 via the network 10. The operation unit 311 includes, for example, one operation button. The operation unit 311 only accepts the pressing of the operation button from the user. When the operation unit 311 accepts a press from the user during the ringing, the ringing ends. The display unit 312 is an output device such as a liquid crystal display or an organic EL display.

[0069] The lending terminal number storage unit 341 is configured using a storage device such as a semiconductor storage device. The lending terminal number storage unit 341 stores a lending terminal number table.

[0070] (Regarding the lending terminal number table) Here, with reference to FIG. 5C, the lending terminal number table will be described. FIG. 5C is an explanatory diagram showing an example of the lending terminal number table. In FIG. 5C, the lending terminal number table includes a lending terminal unique number (for example, a SIM number) and a lending terminal number. The lending terminal unique number is the lending terminal unique number of the own terminal of the lending terminal 300. The lending terminal number is a lending terminal number associated with the lending terminal unique number of the own terminal. At the time of factory shipment of the lending terminal 300, the lending terminal number is not associated with the lending terminal unique number, and NULL is stored in the lending terminal number.

[0071] (Regarding the control unit 320) The control unit 320 in FIG. 4A controls the operations of each part of the lending terminal 300. The control unit 320 includes a display control unit 321, a two-dimensional code generation unit 322, a ringing unit 323, and a state acquisition unit 324. Each functional unit included in the control unit 320 is realized by the CPU of the lending terminal 300. That is, by the CPU executing the lending terminal program stored in the memory or the auxiliary storage device, the functions of each functional unit included in the control unit 320 are realized.

[0072] The display control unit 321 controls the screen to be displayed on the display unit 312. The two-dimensional code generation unit 322 acquires the lending terminal number from the lending terminal number table and encodes the acquired lending terminal number, thereby generating a two-dimensional code indicating the lending terminal number and the like.

[0073] Here, with reference to FIG. 9, the two-dimensional code 371 displayed on the lending terminal 300 will be described. FIG. 9 is an explanatory diagram showing an example of the screen displayed on the lending terminal 300. In FIG. 9(A), a two-dimensional code 371 indicating the lending terminal number is displayed on the display unit 312 of the lending terminal 300. This two-dimensional code 371 is the same as the two-dimensional code 171 drawn on the lending terminal code plate 170. For example, the two-dimensional code displayed on the lending terminal 300 indicating the terminal number 1 is the same as the two-dimensional code 171 drawn on the lending terminal code plate 170 indicating the terminal number 1.

[0074] Also, on the display unit 312, "Terminal Number 1" is displayed so that the operator can visually confirm the lending terminal number. Thereby, the facility staff can confirm the number (numerical value) displayed on the display unit 312 and lend the lending terminal 300 to the user.

[0075] Returning to FIG. 4A, the sounding unit 323 sounds the lending terminal 300 using a speaker or a motor (vibrator) (not shown) when receiving a call from the reception terminal 100. The state acquisition unit 324 acquires the state of the lending terminal 300, such as the remaining battery level (not shown).

[0076] (Regarding the functional configuration of the user terminal 400) FIG. 4B is a functional block diagram showing an example of the functional configuration of the user terminal 400. The user terminal 400 includes a communication unit 410, an input unit 411, a display unit 412, an imaging unit 413, a user terminal number storage unit 441, and a control unit 420.

[0077] The communication unit 410 is a network interface. The communication unit 410 communicates with the management device 200 via the network 10. The input unit 411 is configured using input devices such as a touch panel and buttons. The display unit 412 is an output device such as a liquid crystal display or an organic EL display. Since the display unit 412 is a touch panel display, it has the function of the input unit 411. The imaging unit 413 is composed of, for example, a CCD image sensor or a CMOS image sensor, etc.

[0078] The user terminal number storage unit 441 is configured using a storage device such as a semiconductor storage device. The user terminal number storage unit 441 stores a user terminal number table.

[0079] (Regarding the user terminal number table) Here, with reference to FIG. 5D, the user terminal number table will be described. FIG. 5D is an explanatory diagram showing an example of the user terminal number table. In FIG. 5D, the user terminal number table includes a user ID and a user terminal number. The user ID is the user ID of the user registered in the calling application. The user terminal number is the user terminal number associated with the user ID of the own terminal. The user terminal number is received from the management device 200. When the out registration using the calling application has not been performed, the user ID is not associated with the user terminal number, and NULL is stored in the user terminal number.

[0080] (Regarding the control unit 420) In FIG. 4B, the control unit 420 controls the operations of each part of the user terminal 400. The control unit 420 includes a display control unit 421, a two-dimensional code generation unit 422, a sounding unit 423, and a status information acquisition unit 424. Each functional unit included in the control unit 420 is realized by the CPU of the user terminal 400. That is, by the CPU executing a display control program stored in the memory or the auxiliary storage device, the functions of each functional unit included in the control unit 420 are realized.

[0081] The display control unit 421 controls the screen to be displayed on the display unit 412. The two-dimensional code generation unit 422 acquires the user ID from the user terminal number table and generates a two-dimensional code indicating the user ID and the like by encoding the user ID.

[0082] Here, with reference to FIG. 11, the two-dimensional code 471 displayed on the user terminal 400 will be described. FIG. 11 is an explanatory diagram showing an example of the screen displayed on the user terminal 400. In FIG. 11(A), a two-dimensional code 471 indicating the user ID is displayed on the display unit 412 of the user terminal 400. When the user activates the calling application and operates (taps) the membership card button 481, the two-dimensional code 471 is displayed. If the calling application is not installed on the user terminal 400, the user causes the imaging unit 413 to image a posted object such as a facility poster shown in FIG. 11(Z) or a desktop registration code 971 placed on a facility counter or the like. Thereby, it is possible to install the calling application on the user terminal 400.

[0083] Returning to FIG. 4B, the sounding unit 423 sounds the user terminal 400 using a speaker or a motor (vibrator) (not shown) when called from the reception terminal 100.

[0084] The status information acquisition unit 424 acquires status information indicating the status of each facility reception terminal 100 until the own terminal is called. Specifically, the status information acquisition unit 424 acquires the status information output from the reception terminal 100 by receiving it via the management device 200. The status information is information indicating either the status of "being out" or "being called".

[0085] When the user terminal 400 is registered as being out in the management device 200, the status information acquisition unit 424 acquires the status information of "being out". Specifically, when there is a request for registering the user terminal 400 as being out from the reception terminal 100, the management device 200 registers the user terminal 400 as being out, and transmits the status information indicating the status of "being out" to the user terminal 400 via the application management server. The status information transmitted from the management device 200 is received by the communication unit 410. The status information acquisition unit 424 acquires the status information from the communication unit 410.

[0086] Based on the status information acquired by the status information acquisition unit 424, the display control unit 421 displays the status related to the call for each facility. Specifically, the display control unit 421 displays either the status of "being out" or "being called" for each facility. Also, the display mode of "being called" may be a display mode different from the display mode of "being out". The display mode referred to here is, for example, color, size, font, etc. Note that the status of "being out" may include more detailed statuses such as, for example, "before medicine preparation", "during medicine preparation", "waiting for ○ people", "waiting for ○○ minutes". Also, the status of "being called" may include more detailed statuses such as, for example, "○○ minutes have passed after the call".

[0087] (Regarding the display order of the status for each facility) The display control unit 421 can display the display order of each facility in an arbitrary priority order. Displaying in a priority order means that a facility with a higher priority can be displayed at the top of the screen, or can be superimposed and displayed so as to be the most forward side from the user's view. For example, the display control unit 421 displays the status of each facility in a priority order based on the order in which the own device is registered in the reception terminal 100 of each facility. The priority order based on the registered order is an order in which the older one of the times when the own device is registered in each reception terminal 100 is given priority. However, the priority order based on the registered order may be an order in which the newer one of the times when the own device is registered in each reception terminal 100 is given priority.

[0088] In addition, among the facilities, there are facilities where prompt visits are desired (facilities with a high degree of urgency for visits), such as hospitals where patients are waiting for examination and facilities where items whose quality deteriorates over time are being waited for. Therefore, the display order of each facility may be based on the degree of urgency of the visit. That is, facilities with a higher degree of urgency may be preferentially displayed. Also, the display order of each facility may be the priority order according to the contract with the facility (for example, the priority order according to the option fee, etc.). Further, the display order of each facility may be made changeable according to the operation of the facility staff.

[0089] In addition, the display control unit 421 preferentially displays a facility whose status indicates a call ( "in call") among the statuses of each facility. For example, if there is a call from a facility with a low priority, the display control unit 421 sets the status of the facility to "call" display and rearranges and displays it so that it becomes the top priority.

[0090] In addition, when there are a plurality of facilities whose status indicates a call, the display control unit 421 displays each facility in a predetermined priority order. The predetermined priority order is the order based on the degree of urgency of the visit. Also, the predetermined priority order can be the order based on the number of calls (for example, in the order of the number of calls). The predetermined priority order may be made changeable according to the selection of the operator.

[0091] (Regarding the deletion of the status display) The status information acquisition unit 424 acquires, from the reception terminal 100 of each facility, a notification (going-out cancellation notification) indicating that the user who holds the own terminal has visited the facility. Specifically, when an operation indicating going-out cancellation is received from the facility staff at the reception terminal 100, the management device 200 releases the association between the user terminal number and the user ID and transmits the going-out cancellation notification to the user terminal 400 via the application management server. The going-out cancellation notification transmitted from the management device 200 is received by the communication unit 410. The status information acquisition unit 424 acquires the going-out cancellation notification from the communication unit 410.

[0092] When the status information acquisition unit 424 acquires a going-out cancellation notice, the display control unit 421 erases (hides) the status of the facility. For example, when the statuses of a plurality of facilities are being displayed, the display control unit 421 displays the statuses of the remaining facilities.

[0093] (Example of a screen displayed on the reception terminal 100 during the operation of the calling system 1) FIG. 7 is an explanatory diagram showing an example of the main screen 600 displayed on the reception terminal 100 during the operation of the calling system 1. During the operation of the calling system 1, an operation button 601 is displayed on the display unit 112 of the reception terminal 100. The operation button 601 includes a going-out registration button 601a, a calling button 601b, and a going-out cancellation button 601c. The going-out registration button 601a is a button that receives from an operator (facility staff) the start of going-out registration of the user terminal 400 or the going-out registration of the lending terminal 300.

[0094] The calling button 601b is a button that receives from the facility staff the instruction to send a notice from the facility to the user. The calling button 601b can receive multiple times. That is, the customer can be called multiple times. For example, if the user does not visit the facility despite the call, the facility staff can operate the calling button 601b again to make another call. The going-out cancellation button 601c is a button that receives the cancellation of the going-out registration of the user terminal 400 or the cancellation of the going-out registration of the lending terminal 300 by the facility staff.

[0095] Next, the status display column 602 will be described. The status display column 602 is a column that displays various statuses of the lending terminal 300 and the user terminal 400 for each terminal. Specifically, the status display column 602 shows a terminal number column, a status column, a terminal type column, a lending date and time column, a calling date and time column, a message column, and a calling frequency column. In the terminal number column, a lending terminal number (numerical) is displayed for the lending terminal 300, and a user terminal number (alphabetical) is displayed for the user terminal 400.

[0096] The status bar indicates one of the following: the terminal number (lending terminal code plate 170 or user terminal code plate 180) is not being used, the device is out (on loan), or a call is in progress. "Out" means that the out registration of the terminal number (lending terminal code plate 170 or user terminal code plate 180) has been made and indicates the state before a call. "Call in progress" means that one or more calls have been made. In the status bar, either "Out", "Call in progress", or a blank space is displayed. The blank space in the status bar indicates that the terminal number is not being used (see the terminal number 3 in FIG. 7). Also, for the lending terminal 300, the charging state is displayed in the status bar. The charging state is represented by a gauge indicating the charging state of the lending terminal 300 in four levels.

[0097] In addition, "Call Confirmed" and "Unavailable" are displayed in the status bar. "Call Confirmed" indicates whether the user who holds the lending terminal 300 or the user terminal 400 has confirmed the call when the call is made. For example, in the case of the lending terminal 300, it indicates whether the operation unit 311 has been operated during ringing. When the operation unit 311 is operated by the user, "Call Confirmed" is displayed. Also, in the case of the user terminal 400, when "Read" is received due to the user terminal 400 starting the call application and a message related to the call being displayed, "Call Confirmed" is displayed. "Unavailable" indicates a lending terminal 300 that cannot be lent to customers due to a failure, loss, etc. In the illustration, "Call Confirmed" and "Unavailable" are displayed in the same display area, but they may also be displayed in different display areas.

[0098] The terminal type column indicates either the lending terminal 300 or the user terminal 400. The lending date and time column indicates the date and time when the lending terminal 300 was lent to the user, or the date and time when the user terminal 400 was registered for going out. An empty column in the lending date and time column indicates that the terminal number (the code plate 170 for the lending terminal or the code plate 180 for the user terminal) is not being used. The calling date and time column indicates the date and time when a call was made to the lending terminal 300 or the user terminal 400. When multiple calls are made, the most recent call date and time is displayed in the calling date and time column. An empty column in the calling date and time column indicates that the lending terminal 300 or the user terminal 400 has not been called.

[0099] The message column indicates the message displayed on the lending terminal 300 or the user terminal 400. When the reception terminal 100 receives an operation of the call button 601b from the facility staff, it receives a selection of the terminal number of the call target. Then, the reception terminal 100 displays a message selection screen 633 (see FIG. 12(B)) for selecting a message and receives a message selection from the facility staff. The received message is transmitted to the lending terminal 300 or the user terminal 400 via the management device 200.

[0100] The lending terminal 300 or the user terminal 400 displays the received message at the time of a call (when ringing). In the case of the lending terminal 300, the message is continuously displayed until the return process is performed. Therefore, even if the user does not notice the ringing by chance, the user can recognize that they have been called by looking at the display unit 312 of the lending terminal 300. On the other hand, in the case of the user terminal 400, the message is notified by the call application. An empty column in the message column indicates that the lending terminal 300 or the user terminal 400 has not been called.

[0101] Here, the call system 1 is designed to make effective use of the waiting time in the facility by the user. For example, when waiting for an item that does not easily deteriorate over time, such as medicine, if calls are automatically made multiple times, it may rush the user and there is a risk that the user will not be able to effectively utilize the waiting time.

[0102] On the other hand, in this embodiment, the reception terminal 100 makes a call according to the operation of the facility staff. For example, when there is no operation by the facility staff, the reception terminal 100 can be set not to make a call. Therefore, when waiting for an item that is less likely to deteriorate over time, it is possible to prevent automatic repeated calls and effectively utilize the waiting time of the user. When waiting for a product that is likely to deteriorate over time, after the first call is made based on the operation of the facility staff, a call may be automatically made every time a predetermined time elapses.

[0103] In the example of FIG. 7, the total number of lending terminals 300 and user terminals 400 that display various states on one screen is five, but it is not limited to this. The total number may be less than five or six or more. Also, when the total number is large and all the devices cannot be displayed on one screen, it is also possible to scroll and display the non-displayable part by the operation of the facility staff.

[0104] As shown in FIG. 7, for the lending terminal 300, the going-out registration of the lending terminal 300 can be performed using the lending terminal number without using the SIM number or the telephone number. Therefore, the going-out registration of the lending terminal 300 can be easily performed, and the occurrence of human errors in the registration can be suppressed.

[0105] As described above, "call confirmed" can be displayed in the status column. In the lending terminal 300, when the operation unit 311 is operated during ringing, "call confirmed" is displayed. On the other hand, when the operation unit 311 is not operated, "call confirmed" is not displayed. When the operation unit 311 is not operated, a display indicating that the call has not been confirmed, such as "call not confirmed" or an "X" display, may be made. The facility staff can determine that the user has noticed the ringing when "call confirmed" is displayed in the status column, and can determine that it is highly likely that the user has not noticed the ringing when "call confirmed" is not displayed.

[0106] Also, on the user terminal 400, the display or non-display of "Call Confirmed" indicates whether the "Read" has been received by the call application. When the "Read" is received, "Call Confirmed" is displayed. On the other hand, when the "Read" has not been received, "Call Confirmed" is not displayed. Note that when the "Read" has not been received, a display indicating that the call has not been confirmed, such as "Call Not Confirmed" or an "X" display, may be made.

[0107] In FIG. 7, when the go-out registration button 601a among the operation buttons 601 is operated (tapped), the user is redirected to the reminder screen 611 shown in FIG. 8(A). Hereinafter, the screen transition when registering for going out will be described with reference to FIG. 8.

[0108] (Screen transition displayed on the reception terminal 100 when registering the lending terminal 300 for going out) FIG. 8 is an explanatory diagram showing an example of the screen transition displayed on the reception terminal 100 when registering the lending terminal 300 for going out. FIG. 8(A) shows the reminder screen 611. The reminder screen 611 is a screen that prompts the code reader to read the two-dimensional code 171 drawn on the code plate 170 for the lending terminal or the two-dimensional code 181 drawn on the code plate 180 for the user terminal.

[0109] Note that the two-dimensional code 171 can also be read by imaging the two-dimensional code 171 drawn on the code plate 170 for the lending terminal as a subject in the imaging image display area 610 without using a code reader. When the two-dimensional code reading unit 125 reads the two-dimensional code 171, the reception terminal 100 acquires the number for the lending terminal.

[0110] FIG. 8(B) shows a reading completion screen 613 after reading the two-dimensional code 171 of the lending terminal code plate 170. On the reading completion screen 613, it is indicated that the lending terminal 300 with the lending terminal number "1" is lent out, a button for accepting a request for going out registration of the lending terminal 300, and a button for accepting cancellation of the request are displayed. When the button for accepting a request for going out registration is operated, the reception terminal 100 makes a request for going out registration of the lending terminal 300 to the management device 200. Specifically, the reception terminal 100 transmits the acquired lending terminal number and the facility code to the management device 200 as a request for going out registration.

[0111] The management device 200 identifies the SIM number from the received lending terminal number and facility code, and transmits a notification indicating that the going out registration has been performed to the lending terminal 300. In addition, the management device 200 performs registration indicating that the lending terminal 300 with the lending terminal number "1" is in use according to the request.

[0112] (Example of a screen displayed on the lending terminal 300 when going out registration is performed) Next, with reference to FIG. 9, an example of a screen displayed on the lending terminal 300 when going out registration is performed will be described. FIG. 9(A) shows a standby screen of the lending terminal 300 when it is not lent out. On the standby screen, the lending terminal 300 displays a two-dimensional code 371 obtained by encoding the lending terminal number. The two-dimensional code 171 drawn on the lending terminal code plate 170 and the two-dimensional code 371 displayed on the lending terminal 300 for the same lending terminal numbers are the same. Therefore, in the going out registration of the lending terminal 300, it is also possible to make a request for going out registration of the lending terminal 300 to the management device 200 by having the two-dimensional code 371 displayed on the lending terminal 300 read.

[0113] When going out registration is performed in the management device 200, a going out registration notification indicating that to the lending terminal 300 is transmitted from the management device 200 to the lending terminal 300. When the lending terminal 300 receives the going out registration notification, it transitions to the screen shown in FIG. 9(B).

[0114] FIG. 9(B) shows a preparation screen displayed on the lending terminal 300 after receiving the going-out registration notice. The preparation screen indicates that it is in the preparation process. Accordingly, the facility staff lends the lending terminal 300 to the user. After the going-out registration is performed and a predetermined time has elapsed, the lighting of the backlight disappears. Then, after making a call, the text "Preparing" shown on the preparation screen switches to a message for the call.

[0115] (Screen transition displayed on the reception terminal 100 when registering the user terminal 400 for going out) FIG. 10 is an explanatory diagram showing an example of a screen transition displayed on the reception terminal 100 when registering the user terminal 400 for going out. FIG. 10(A) shows a reminder screen 611 similar to FIG. 8(A). While the reminder screen 611 is being displayed, the facility staff uses a code reader to have the two-dimensional code 181 drawn on the user terminal code plate 180 read. Note that it is also possible to read the two-dimensional code 181 by imaging the two-dimensional code 181 drawn on the user terminal code plate 180 as a subject in the imaging image display area 610 without using a code reader.

[0116] FIG. 10(B) shows a reminder screen 623 that prompts the user to read the two-dimensional code 471 displayed on the user terminal 400 after reading the two-dimensional code 181 of the user terminal code plate 180. The reminder screen 623 is a screen that prompts the user to display the two-dimensional code 471 on the user terminal 400 and have it read by a code reader.

[0117] Also, on the reminder screen 623, an imaging image during the operation of having the user read the two-dimensional code 471 displayed on the user terminal 400 with a code reader is displayed in the imaging image display area 610. Note that it is also possible to read the two-dimensional code 471 by imaging the two-dimensional code 471 displayed on the user terminal 400 as a subject in the imaging image display area 610 without using a code reader.

[0118] FIG. 10(C) shows a reading completion screen 624 after reading the two-dimensional code 471 displayed on the user terminal 400. On the reading completion screen 730, it is indicated that the user terminal number uses "A", an OK button for accepting a request for going out registration of the user terminal 400, and a cancel button for accepting cancellation of the request are displayed. When the OK button is operated, the reception terminal 100 makes a request for going out registration of the user terminal 400 to the management device 200. The management device 200 performs the going out registration of the user terminal 400 for the user terminal number "A" according to the request.

[0119] (Example of a screen displayed on the user terminal 400 when performing going out registration) Next, with reference to FIG. 11, an example of a screen displayed on the user terminal 400 when performing going out registration will be described. FIG. 11(A) shows a membership card screen displayed on the user terminal 400 when performing going out registration. On the membership card screen, the user terminal 400 displays a one-dimensional code 470 and a two-dimensional code 471 obtained by encoding the user ID. Hereinafter, the case where the one-dimensional code 470 is read by the reception terminal 100 will be omitted from the description, but this case is the same as the case where the two-dimensional code 471 is read by the reception terminal 100.

[0120] The user performs an operation to let the reception terminal 100 read the two-dimensional code 471. When the reception terminal 100 reads the two-dimensional code 471, it makes a request for going out registration of the user terminal 400 to the management device 200. As a result, in the management device 200, the going out registration is performed, and a going out registration notification is transmitted from the management device 200 to the user terminal 400. When the user terminal 400 receives the going out registration notification, it transitions to the going out registration completion screen shown in FIG. 11(B). Also, a call status button 482 is displayed on the user terminal 400. When the call status button 482 is pressed, as will be described later with reference to FIG. 14, it transitions to a call status confirmation screen where the call status of each facility can be confirmed.

[0121] FIG. 11(B) shows the out registration completion screen displayed on the user terminal 400 upon receiving the out registration notice. On the out registration completion screen, a registration completion message 484 indicating that the out registration of the user terminal 400 has been completed is displayed. Thereby, the user can grasp that the out registration of the user terminal 400 has been completed.

[0122] (Screen transition displayed on the reception terminal 100 when making a call registration) Next, with reference to FIG. 12, the screen transition displayed on the reception terminal 100 when making a call registration will be described. In FIG. 12, the call registration of the user terminal 400 will be described, and the description of the call registration of the lending terminal 300 will be omitted. Note that the code plates to be read by the reception terminal 100 are different between the case of making a call registration for the user terminal 400 and the case of making a call registration for the lending terminal 300.

[0123] FIG. 12 is an explanatory diagram showing an example of the screen transition displayed on the reception terminal 100 in the call registration of the user terminal 400. FIG. 12(A) shows the prompting screen 631 that transitions when the call button 601b among the operation buttons 601 shown in FIG. 7 is operated (tapped). The prompting screen 631 is a screen that prompts the code reader to read the two-dimensional code 171 drawn on the lending terminal code plate 170 or the two-dimensional code 181 drawn on the user terminal code plate 180.

[0124] During the display of the prompting screen 631, the facility staff causes the code reader to read, for example, the two-dimensional code 181 drawn on the user terminal code plate 180. When the two-dimensional code reading unit 125 reads the two-dimensional code 181, the reception terminal 100 acquires the user terminal number (for example, "A"). After acquiring the user terminal number, the reception terminal 100 transitions to the message selection screen 633 shown in FIG. 12(B).

[0125] Figure 12(B) shows the message selection screen 633. The message selection screen 633 is a screen for receiving the selection of a message to be displayed on the user terminal 400 with the user terminal number "A". The message selection screen 633 is a screen for receiving the selection of one message from a plurality of preset messages. When one message is selected by the facility staff on the message selection screen 633, the reception terminal 100 transmits the facility code, the user terminal number "A", and the selected message to the management device 200 as a call request.

[0126] The management device 200 identifies the user ID from the facility code and the user terminal number "A", and notifies the user terminal 400 that a call process has been performed. In this notification, the message is also transmitted. When the user terminal 400 with the user terminal number "A" receives the message from the management device 200, the call application notifies the message. Note that the message transmitted from the management device 200 may be encoded. In this case, the user terminal 400 may store the message corresponding to the code in advance and notify the message corresponding to the received code.

[0127] Also, when one message is selected on the message selection screen 633, the reception terminal 100 transitions to the list screen 634 shown in Figure 12(C).

[0128] Figure 12(C) shows the list screen 634. On the list screen 634, the message selected on the message selection screen 633 is displayed in the item of the message corresponding to the user terminal number "A". Thereby, the facility staff can confirm the message they selected.

[0129] (Example of a screen of a message displayed on the lending terminal 300) Fig. 13 is an explanatory diagram showing an example of a message screen displayed on the lending terminal 300. In Fig. 13, the display unit 312 of the lending terminal 300 displays a message selected in the call registration of the reception terminal 100. The lending terminal 300 continues to display the message until it receives an outing release notification.

[0130] (Call status confirmation screen displayed on user terminal 400) FIG. 14 is an explanatory diagram showing an example of a call status confirmation screen displayed on the user terminal 400. FIG. 14(A) shows a call status confirmation screen 900 displayed on the display unit 412 of the user terminal 400. The call status confirmation screen 900 shows a message 901 (901a, 901b, 901c) and a status 902 (902a, 902b, 902c) for each facility. For example, the status 902 for each facility shows "getting ready", which corresponds to "out". The order of the facilities displayed on the display unit 412 is the order in which the outing registration was made. Specifically, the earlier the outing registration time, the lower it is displayed, and the more recent the outing registration, the higher it is displayed.

[0131] Fig. 14(B) shows a call status confirmation screen 910 when a call is made. The order of facilities on the call status confirmation screen 910 is different from that on the screen of Fig. 14(A). On the call status confirmation screen 910, XX Clinic is displayed at the top, indicating a status 902b of calling. The status 902a of XX Clinic indicates that a call is being made. Furthermore, the message 901b of XX Clinic indicates a message selected by the facility staff on the reception terminal 100.

[0132] (Screen transition displayed on the reception terminal 100 when canceling going out) Next, the transition of screens displayed on the reception terminal 100 when canceling going out will be described with reference to FIG. 15 and FIG. 16A. FIG. 15 is an explanatory diagram showing an example of screen transition displayed on the reception terminal 100 when releasing the going-out of the lending terminal 300. FIG. 15(A) shows a prompting screen 641 that transitions when the going-out release button 601c among the operation buttons 601 shown in FIG. 7 is operated (tapped). The prompting screen 641 is a screen that prompts the 2D code 171 drawn on the user terminal code plate 180 or the 2D code 181 drawn on the user terminal code plate 180 to be read by the code reader.

[0133] During the display of the prompting screen 641, the facility staff causes the code reader to read, for example, the 2D code 171 drawn on the lending terminal code plate 170. When the 2D code reading unit 125 reads the 2D code 171, the reception terminal 100 acquires the lending terminal number (for example, "1").

[0134] The reception terminal 100 notifies the management device 200 that the lending terminal 300 with the acquired lending terminal number has been returned. The management device 200 sends a going-out release notice to the lending terminal 300 corresponding to the notified lending terminal number. When the lending terminal 300 receives the going-out release notice, it ends the display of the calling message and displays the standby screen (see FIG. 9(A)).

[0135] After the facility staff causes the code reader to read the 2D code 171 on the lending terminal code plate 170, the facility staff causes the reception terminal 100 to read the 2D code 371 displayed on the lending terminal 300 (standby screen). Note that after reading the 2D code 171 drawn on the lending terminal code plate 170, the reception terminal 100 may display a screen that prompts the code reader to read the 2D code 371 displayed on the lending terminal 300.

[0136] The reception terminal 100 reads the two-dimensional code 371 displayed on the lending terminal 300 to obtain the lending terminal number. The reception terminal 100 determines whether the lending terminal number obtained from the two-dimensional code 371 displayed on the lending terminal 300 matches the lending terminal number obtained from the two-dimensional code 171 of the lending terminal code plate 170. That is, the terminal number determination is a determination as to whether the lending terminal 300 intended by the facility staff has been returned.

[0137] FIG. 15(B) shows the main screen 600 displayed when a matching determination result is obtained in the terminal number determination. The main screen 600 indicates that the return of the lending terminal 300 with the lending terminal number (for example, "1") has been completed. Specifically, "Unavailable" is hidden from the status column of the lending terminal number "1", and the lending date and time column, etc. are also hidden. When a non-matching determination result is obtained in the terminal number determination, a screen indicating that the lending terminal numbers are different is displayed. Thus, by displaying the result of the terminal number determination, it is possible to prevent the return of a lending terminal 300 not intended by the facility staff.

[0138] A series of processes from lending to returning the above-described lending terminal 300 will be described by taking the delivery of medicine at a pharmacy as an example. At the reception at the pharmacy, the facility staff causes the reception terminal 100 to read the two-dimensional code 171 of the code plate 170 for the lending terminal, and lends the lending terminal 300 to the user. Then, the facility staff clips the code plate 170 for the lending terminal to the prescription form with a clip or the like and hands it to the pharmacist. The pharmacist clips the code plate 170 for the lending terminal to the bag containing the medicine prescribed according to the prescription form with a clip or the like and returns it to the facility staff. The facility staff causes the reception terminal 100 to read the two-dimensional code 171 of the code plate 170 for the lending terminal, selects a message, and makes a call to the lending terminal 300. When a call registration is performed on the reception terminal 100, the lending terminal 300 makes a call. When the user visits the facility, the facility staff causes the reception terminal 100 to read the two-dimensional code 171 of the code plate 170 for the lending terminal and the two-dimensional code 371 displayed on the lending terminal 300, and releases the going-out restriction. By performing such an operation, it is possible to prevent the wrong delivery of medicine and ensure the return of the lending terminal 300.

[0139] (Screen transition displayed on the reception terminal 100 when releasing the going-out restriction of the user terminal 400) FIG. 16A is an explanatory diagram showing an example of a screen transition displayed on the reception terminal 100 when releasing the going-out restriction of the user terminal 400. (A) of FIG. 16A shows a reminder screen 641 similar to FIG. 15(A). While the reminder screen 641 is being displayed, the facility staff causes the code reader to read the two-dimensional code 181 drawn on, for example, the code plate 180 for the user terminal. When the two-dimensional code reading unit 125 reads the two-dimensional code 181, the reception terminal 100 acquires the user terminal number (for example, "A").

[0140] (B) of FIG. 16A shows a confirmation screen 653 after reading the two-dimensional code 181 of the user terminal code plate 180. The confirmation screen 653 acquires a user terminal number (for example, "A") and indicates that the out registration of the user terminal 400 is to be cancelled. When the cancel button is operated on the confirmation screen 653, the reception terminal 100 notifies the management device 200 that the use of the user terminal 400 with the acquired user terminal number has ended. The management device 200 releases the association between the notified user terminal number and the user ID, and transmits an out cancellation notice indicating that the out cancellation has been performed to the user terminal 400.

[0141] FIG. 16B is an explanatory diagram showing an example of an out cancellation screen when the user terminal 400 receives an out cancellation notice. When the user terminal 400 receives the out cancellation notice, as shown in FIG. 16B, the call application displays a thank-you message 485 indicating that the out cancellation has been performed. Also, after the cancel button is operated on the confirmation screen 653, the reception terminal 100 displays the main screen 600 shown in (C) of FIG. 16A. In (C) of FIG. 16A, the main screen 600 indicates that the out registration of the user terminal 400 with the user terminal number (for example, "A") has been cancelled. Specifically, "Unusable" becomes non-displayed from the status column of the user terminal number "A", and the loan date and time column etc. also become non-displayed.

[0142] Regarding the series of processes from the lending to the return of the user terminal 400 described above, an example of the delivery of medicine at a pharmacy will be used for explanation. At the reception in the pharmacy, the facility staff causes the reception terminal 100 to read the two-dimensional code 181 of the user terminal code plate 180. The user causes the two-dimensional code 471 to be displayed on the user terminal 400 and causes the reception terminal 100 to read it. Then, the facility staff clips the user terminal code plate 180 to the prescription form with a clip or the like and hands it to the pharmacist. The pharmacist clips the user terminal code plate 180 to the bag containing the prescribed medicine according to the prescription form with a clip or the like and returns it to the facility staff. The facility staff causes the reception terminal 100 to read the two-dimensional code 181 of the user terminal code plate 180 and selects a message to call the user terminal 400. When a call registration is performed on the reception terminal 100, the user terminal 400 is notified of the call by the call application. When the user visits the facility, the facility staff causes the reception terminal 100 to read the two-dimensional code 181 of the user terminal code plate 180 to cancel the going out. By performing such operations, it is possible to prevent the wrong delivery of medicine and to call the user using the user terminal 400.

[0143] (Processing related to going out registration, call, and going out cancellation) Next, with reference to FIGS. 17 to 22, each process related to going out registration, call registration, and going out cancellation performed by the reception terminal 100, the management device 200, the lending terminal 300, and the user terminal 400 will be described.

[0144] (Processing related to going out registration of the lending terminal 300) FIG. 17 is a sequence diagram showing an example of the process related to going out registration of the lending terminal 300. In FIG. 17, first, the reception terminal 100 receives an operation of the going out registration button 601a (step S201). Next, the reception terminal 100 reads the two-dimensional code 171 of the lending terminal code plate 170 (or the two-dimensional code 371 displayed on the lending terminal 300) (step S202) and acquires the lending terminal number (numerical value) (step S203).

[0145] Then, the reception terminal 100 acquires the facility code stored in the facility information storage unit 141 (step S204). The reception terminal 100 transmits the facility code and the number for the lending terminal as a request for going-out registration (step S205). When receiving the request for going-out registration, the management device 200 refers to the lending terminal management table ((A) in FIG. 5B) and identifies the SIM number associated with the number for the lending terminal and the facility code (step S206). In step S206, the usage status corresponding to the number for the lending terminal in the lending terminal management table is set to "in use".

[0146] Then, the management device 200 transmits a going-out registration notification indicating that the lending terminal 300 has accepted the going-out registration (step S207). When receiving the going-out registration notification, the lending terminal 300 displays a preparation screen (see FIG. 9(B)) (step S208). Thereby, the process related to the going-out registration of the lending terminal 300 is completed.

[0147] (Regarding the process related to the going-out registration of the user terminal 400) FIG. 18 is a sequence diagram showing an example of the process related to the going-out registration of the user terminal 400. In FIG. 18, the reception terminal 100 receives an operation of the going-out registration button 601a (step S231). Next, the reception terminal 100 reads the two-dimensional code 181 on the user terminal code plate 180 (step S232) and acquires the number for the user terminal (alphabet) (step S233).

[0148] On the other hand, the user terminal 400 starts or installs the calling application (step S234). Then, the user terminal 400 receives an operation of the membership card button 481 (see FIG. 11(A)) (step S235), and displays a two-dimensional code 471 indicating the user ID of the calling application on the display unit 412 (step S236).

[0149] The reception terminal 100 reads the two-dimensional code 471 displayed on the user terminal 400 (step S237) and acquires the user ID of the calling application (step S238). Then, the reception terminal 100 acquires the facility code stored in the facility information storage unit 141 (step S239). Next, the reception terminal 100 transmits the facility code, the user terminal number, and the user ID as an out-going registration request (step S240). When the management device 200 receives the out-going registration request, it associates and stores the facility code, the user terminal number, and the user ID in the user terminal management table ((B) of FIG. 5B) (step S241). In step S241, the usage status corresponding to the user terminal number in the user terminal management table is set to "in use".

[0150] Then, the management device 200 transmits an out-going registration notification indicating that the out-going registration has been received to the user terminal 400 (step S242). When the user terminal 400 receives the out-going registration notification, the calling application displays a registration completion message 484 (see FIG. 11(B)) (step S243). Thereby, the process related to the out-going registration of the user terminal 400 is completed.

[0151] (Regarding the process related to the call registration of the lending terminal 300) FIG. 19 is a sequence diagram showing an example of the process related to the call registration of the lending terminal 300. In FIG. 19, first, the reception terminal 100 receives an operation of the call button 601b (step S301). Then, the reception terminal 100 reads the two-dimensional code 171 of the lending terminal code plate 170 (step S302) and acquires the lending terminal number (numerical value) (step S303). Next, the reception terminal 100 displays a message selection screen 633 (see FIG. 12(B)) (step S304) and acquires the message selected by the facility staff (step S305).

[0152] Then, the reception terminal 100 acquires the facility code (step S306). Next, the reception terminal 100 transmits the facility code, the number for the lending terminal, and the code corresponding to the selected message to the management device 200 as a call request (step S307). The management device 200 refers to the lending terminal management table ((A) in FIG. 5B) and identifies the SIM number from the facility code and the number for the lending terminal (step S308).

[0153] Then, the management device 200 transmits a call notification to the lending terminal 300 (step S309). In this notification, the code corresponding to the message is also transmitted. The lending terminal 300 rings and displays the message corresponding to the received code (step S310). Thereby, the process related to the call registration of the lending terminal 300 is completed.

[0154] (Regarding the process related to the call registration of the user terminal 400) FIG. 20 is a sequence diagram showing an example of the process related to the call registration of the user terminal 400. In FIG. 20, first, the reception terminal 100 receives an operation of the call button 601b (step S331). Then, the reception terminal 100 reads the two-dimensional code 181 of the user terminal code plate 180 (step S332) and acquires the number for the user terminal (alphabet) (step S333). Next, the reception terminal 100 displays the message selection screen 633 (see FIG. 12(B)) (step S334) and acquires the message selected by the facility staff (step S335).

[0155] Then, the reception terminal 100 acquires the facility code (step S336). Next, the reception terminal 100 transmits the facility code, the number for the user terminal, and the selected message to the management device 200 as a call request (step S337). The management device 200 refers to the user terminal management table ((B) in FIG. 5B) and identifies the user ID from the facility code and the number for the user terminal (step S338).

[0156] Then, the management device 200 transmits a call notification to the user terminal 400 by the call application (step S339). This notification also transmits a message. The user terminal 400 rings by the call application and displays the received message (step S340). This completes the process related to the call registration of the user terminal 400.

[0157] (Regarding the process for canceling the outing of the rental terminal 300) Fig. 21 is a sequence diagram showing an example of a process related to the release of the outing of the lending terminal 300. In Fig. 21, first, the reception terminal 100 accepts the operation of the outing release button 601c (step S401). Then, the reception terminal 100 reads the two-dimensional code 171 of the lending terminal code plate 170 (step S402) and acquires the lending terminal number (numbers) (step S403). Next, the reception terminal 100 acquires the facility code (step S404).

[0158] Then, the reception terminal 100 transmits the facility code and the lending terminal number to the management device 200 as a request to release the user from outside (step S405). The management device 200 refers to the lending terminal management table ((A) of FIG. 5B) and identifies the SIM number from the facility code and the lending terminal number (step S406). In step S406, the usage status corresponding to the lending terminal number in the lending terminal management table is changed to "not in use".

[0159] Then, the management device 200 transmits an outing release notification to the lending terminal 300 (step S407). The lending terminal 300 that has received the outing release notification displays a standby screen (see FIG. 9(A)) (step S408). The reception terminal 100 then reads the two-dimensional code 371 displayed on the standby screen of the lending terminal 300 (step S409) and obtains the lending terminal number (step S410).

[0160] Then, the reception terminal 100 determines whether the lending terminal number obtained from the two-dimensional code 171 of the lending terminal code plate 170 matches the lending terminal number from the two-dimensional code 371 displayed on the lending terminal 300 (step S411). Next, the reception terminal 100 displays the determination result of the terminal number determination (step S412). Thereby, the process related to the release of the lending terminal 300 going out is completed.

[0161] (Regarding the going-out release process of the user terminal 400) FIG. 22 is a sequence diagram showing an example of the going-out release process of the user terminal 400. In FIG. 22, first, the reception terminal 100 receives an operation of the going-out release button 601c (step S431). Then, the reception terminal 100 reads the two-dimensional code 181 of the user terminal code plate 180 (step S432) and acquires the user terminal number (alphabet) (step S433). Next, the reception terminal 100 acquires the facility code (step S434).

[0162] Then, the reception terminal 100 transmits the facility code and the user terminal number as a request for going-out release to the management device 200 (step S435). The management device 200 refers to the user terminal management table ((B) in FIG. 5B) and specifies the user ID from the facility code and the user terminal number (step S436). Then, the management device 200 releases the association between the user ID, the facility code, and the user terminal number (step S437). In step S437, the usage status corresponding to the user terminal number in the user terminal management table is set to "not in use".

[0163] Then, the management device 200 transmits a going-out release notification to the user terminal 400 (step S438). The user terminal 400 that has received the going-out release notification displays a thank-you message 485 (see FIG. 16B) (step S439). Thereby, the process related to the release of the user terminal 400 going out is completed.

[0164] (Regarding the display control process performed by the user terminal 400) Next, the display control process performed by the user terminal 400 will be described. FIGS. 23A and 23B are flowcharts showing an example of the display control process performed by the user terminal 400. In FIG. 23A, the user terminal 400 determines whether the calling application installed on its own terminal has been launched (step S501). The user terminal 400 waits until the calling application is launched (step S501; NO), and when the calling application is launched (step S501: YES), it determines whether an operation of the membership card button 481 (see FIG. 11(A)) has been received (step S502).

[0165] If the operation of the membership card button 481 is not received (step S502: NO), the user terminal 400 proceeds to step S504. If the operation of the membership card button 481 is received (step S502: YES), the user terminal 400 displays the two-dimensional code 471 on the display unit 412 (step S503). Then, the user terminal 400 determines whether an out registration notification has been received from the management device 200 (step S504). If the out registration notification is not received (step S504: NO), the user terminal 400 proceeds to step S508.

[0166] If the out registration notification is received (step S504: YES), the user terminal 400 displays a registration completion message 484 (see FIG. 11(B)) (step S505). Then, the user terminal 400 determines whether out registration for a plurality of facilities has been performed (step S506). If out registration for a plurality of facilities has not been performed (step S506: NO), that is, if out registration for only one facility has been performed, the user terminal 400 proceeds to step S508.

[0167] When performing the check-out registration for multiple facilities (step S506: YES), the user terminal 400 displays each facility and its status in the order of check-out registration (with the oldest registered time at the top) (step S507). Then, the user terminal 400 determines whether it has received a call notification from the management device 200 (step S508). If it has not received a call notification (step S508: NO), the user terminal 400 proceeds to step S514.

[0168] If it has received a call notification (step S508: YES), the user terminal 400 rings and displays the received message (step S509). Then, the user terminal 400 determines whether multiple facilities are being displayed (step S510). If multiple facilities are not being displayed (step S510: NO), that is, if only one facility is being displayed, the user terminal 400 proceeds to step S514.

[0169] If multiple facilities are being displayed (step S510: YES), it is determined whether there is another facility on a call (step S511). If there is no other facility on a call (step S511: NO), the user terminal 400 displays the facility that received the call at the top (step S511) and proceeds to step S514. If there is another facility on a call (step S511: YES), the user terminal 400 displays the facilities in a predetermined priority order (such as an order based on the urgency of the visit or the number of calls) (step S513).

[0170] Then, the user terminal 400 determines whether it has received a check-out cancellation notification from the management device 200 (step S514). If it has not received a check-out cancellation notification (step S514: NO), the user terminal 400 proceeds to step S517.

[0171] When receiving a notice to lift the going-out status (step S514: YES), the user terminal 400 displays a gratitude message 485 (see FIG. 16B) (step S515). Then, the user terminal 400 deletes the facility (step S516). Next, the user terminal 400 determines whether there is another facility being registered (step S517). If there is another facility being registered (step S517: YES), the user terminal 400 returns to step S502.

[0172] If there is no other facility being registered (step S517: NO), the user terminal 400 determines whether the calling application has ended (step S518). If the calling application has not ended (step S518: NO), the user terminal 400 returns to step S502. If the calling application has ended (step S518: YES), the user terminal 400 ends the series of processes.

[0173] (Effect related to the going-out registration of the reception terminal 100) As described above, in the present embodiment, upon obtaining the user terminal number, the reception terminal 100 requests the going-out registration of the user terminal 400 (association of the user terminal number and the user ID, and registration indicating being in use) based on the user ID (user identification information) of the calling application obtained accordingly and the user terminal number. Thereby, the user terminal 400 can be registered as a terminal for calling in the facility. Therefore, the user terminal 400 can be effectively utilized in calls at the facility. Also, the customer can freely spend the waiting time at home or go shopping without carrying the lending terminal 300. Further, according to the present embodiment, at the facility, it is not necessary to prepare a large number of lending terminals 300, so the costs related to the management (charging, maintenance, loss prevention, etc.) of the lending terminals 300 (the work load of the facility staff, various expenses, etc.) can be reduced.

[0174] Also, in this embodiment, the reception terminal 100 requests a notification from the facility to the calling application that uses the user ID associated with the user terminal number registered as being in use, by acquiring the user terminal number. Therefore, the facility staff can cause the reception terminal 100 to acquire the user terminal number, and various notifications such as calls to customers can be made by the calling application.

[0175] Also, in this embodiment, the reception terminal 100 requests a notification from the facility in response to receiving an operation indicating a call. Thereby, with the confirmation of the facility staff, a user can make a call. Also, when waiting for an item that is less likely to deteriorate in quality over time, the user can automatically refrain from making calls multiple times, so that the user can effectively utilize the waiting time.

[0176] Also, in this embodiment, when the reception terminal 100 acquires the lending terminal number, it requests an out-of-facility registration of the lending terminal 300 that is associated with the lending terminal number in advance. Thereby, as a terminal for making calls in the facility, not only the user terminal 400 but also the lending terminal 300 can be used. Therefore, either one of the lending terminal 300 and the user terminal 400 can be used according to the user's selection. Also, even in the case of a user who does not possess the user terminal 400 or a case where the calling application is not installed on the user terminal 400, the lending terminal 300 can be used.

[0177] Also, in this embodiment, the reception terminal 100 requests a facility notification to the lending terminal 300 at the destination indicated by the SIM number associated with the lending terminal number obtained by acquiring the lending terminal number registered as being in use. Therefore, the facility staff can cause the lending terminal 300 to make a customer call or the like by having the reception terminal 100 acquire the lending terminal number. Also, the facility staff can make a customer call or the like regardless of whether the user has the lending terminal 300 or the user terminal 400. Therefore, the convenience of the calling system 1 can be improved.

[0178] Also, in this embodiment, the reception terminal 100 acquires the user terminal number or the lending terminal number by reading the two-dimensional codes 171, 181 depicted on the lending terminal code plate 170 or the user terminal code plate 180. Thereby, the facility staff can cause the reception terminal 100 to acquire the user terminal number or the lending terminal number simply by having the two-dimensional codes 171, 181 read. Therefore, the operation load on the facility staff related to the acquisition of the user terminal number or the lending terminal number can be reduced.

[0179] Also, in this embodiment, the reception terminal 100 acquires the user ID by reading the two-dimensional code 471 displayed on the user terminal 400. Thereby, the user (or the facility staff) can cause the reception terminal 100 to acquire the user ID simply by having the two-dimensional code 471 read. Therefore, the operation load on the user (or the facility staff) related to the acquisition of the user ID can be reduced.

[0180] Also, in this embodiment, when the reception terminal 100 acquires the user terminal number, it makes a prompt to acquire the user ID. As a result, the reception terminal 100 can surely acquire the user ID. Further, when the reception terminal 100 acquires the lending terminal number, it does not make this prompt. Thereby, different operations can be performed between the case of performing the going-out registration of the user terminal 400 and the case of performing the going-out registration of the lending terminal 300. For this reason, it is possible to prevent a human error when the facility staff performs the going-out registration, such as accidentally lending out the lending terminal 300 even though the user terminal number has been acquired.

[0181] Also, in this embodiment, when an operation indicating going-out cancellation is received, the reception terminal 100 requests cancellation of the going-out registration (cancellation of the association between the user terminal number and the user ID and registration indicating that the user terminal number is not in use). As a result, when a customer visits the facility, the association between the user terminal number and the user ID can be cancelled, and the user terminal number can be set to a non-use state. Therefore, the user terminal number whose association with the user ID has been cancelled can be used by another user. On the other hand, for the lending terminal 300, the reception terminal 100 does not request cancellation of the association between the lending terminal number and the lending terminal unique number even when an operation indicating going-out cancellation is received. That is, the association between the lending terminal number and the lending terminal unique number is made not to change in principle. For this reason, it is possible to prevent storing the lending terminal code plate 170 and the lending terminal 300 in the wrong combination. That is, it is possible to prevent a mix-up between the lending terminal code plate 170 and the lending terminal 300.

[0182] (Effect related to display control of user terminal 400) Also, in this embodiment, the user terminal 400 is configured to display the status related to the call for each facility based on the status information indicating the status until the user terminal is called by the reception terminal 100 of each facility. Thereby, the user can grasp the statuses of a plurality of facilities using the user terminal 400 and can wait for a call from each facility. Therefore, the convenience related to the call from the facility can be improved.

[0183] Also, in this embodiment, the user terminal 400 is configured to display the status for each facility in the order based on the order in which the own device is registered in the reception terminal 100 of each facility. Thereby, the user can grasp the approximate order until the call of each facility.

[0184] Also, in this embodiment, the user terminal 400 is configured to preferentially display the facility with the status indicating a call among the statuses for each facility. Thereby, it is possible to efficiently prompt the user to visit the facility.

[0185] Also, in this embodiment, when there are a plurality of facilities with the status indicating a call, the user terminal 400 is configured to display each facility in a predetermined priority order. Thereby, when a prompt visit to the facility is required, such as when waiting for a medical examination or waiting for an item whose quality deteriorates over time, the facility can be preferentially displayed. Therefore, a prompt visit to the facility can be promoted.

[0186] Also, in this embodiment, when the user terminal 400 acquires a going-out cancellation notice indicating that the user has visited the facility from the reception terminal 100 of each facility, the user terminal 400 is configured to delete the facility. Thereby, only the statuses of the facilities that have not been visited can be displayed. Therefore, the statuses of each facility can be efficiently displayed.

[0187] (Modification Example of the Embodiment) Next, a modification example of the embodiment will be described. In the following modification examples, the description of the content described in the above-described embodiment will be omitted as appropriate. Also, the following modification examples and the above-described embodiment can be combined with each other.

[0188] In the above-described embodiment, when canceling the going-out registration of the user terminal 400, the cancellation is performed by reading the two-dimensional code 171 of the user-terminal code plate 180. In the modification example, a configuration will be described in which, when canceling the going-out registration of the user terminal 400, the cancellation is performed by accepting the selection of the user-terminal number on the screen.

[0189] FIG. 24 is an explanatory diagram showing a modified example of the screen transition displayed on the reception terminal 100 when canceling the going-out of the user terminal 400. FIG. 24(A) shows the main screen 600 shown in FIG. 7. When the going-out cancellation button 601c is operated on the main screen 600, the process proceeds to the terminal selection screen 662 shown in FIG. 24(B). The terminal selection screen 662 is a screen for accepting the cancellation of the registration of the terminal number for which the going-out registration has been performed. For example, as shown in the figure, if the area indicating the user-terminal number "A" is selected, the process proceeds to the confirmation screen 653 shown in FIG. 24(C).

[0190] The confirmation screen 653 in FIG. 24(C) shows the same confirmation screen 653 as that in FIG. 16A(B). When the cancellation button is operated on the confirmation screen 653, the going-out registration in the management device 200 is canceled. Then, as shown in FIG. 16B, the user terminal 400 displays a thank-you message 485 indicating that the going-out cancellation has been performed by the calling application.

[0191] Regarding the lending terminal 300 as well, on the terminal selection screen 662, it is also possible to cancel the going-out registration of the lending terminal 300 by accepting the selection of the lending terminal number. However, in the case of the lending terminal 300, after accepting the selection of the lending terminal number on the terminal selection screen 662, the reception terminal 100 is made to read the two-dimensional code 371 displayed on the lending terminal 300. Then, the reception terminal 100 is made to perform a terminal number determination as to whether the selected lending terminal number matches the lending terminal number acquired from the two-dimensional code 171. Thereby, it is possible to prevent the lending terminal 300 not intended by the facility staff from being returned.

[0192] According to Modification 1, the cancellation of the going-out registration of the user terminal 400 can be easily performed. Also, the user terminal number whose association with the user ID has been canceled can be used by another user.

[0193] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the gist of the invention. These embodiments and their modifications are included in the scope and gist of the invention, and are also included in the invention described in the claims and the equivalent scope thereof.

[0194] Incidentally, a program for realizing the reception terminal 100 and the user terminal 400 described above may be recorded on a computer-readable recording medium, and the program may be read into a computer system and executed. Here, the "computer system" shall include hardware such as an OS and peripheral devices. Further, the "computer-readable recording medium" refers to a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, etc., and a storage device such as a hard disk built into a computer system. Furthermore, the "computer-readable recording medium" also includes a volatile memory (RAM) inside a computer system that becomes a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line, and that holds the program for a certain period of time. Also, the above program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the "transmission medium" for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. Also, the above program may be for realizing a part of the functions described above. Furthermore, it may be a so-called difference file (difference program) that can realize the functions described above in combination with a program already recorded in a computer system.

Explanation of Signs

[0195] 1...call system, 100...reception terminal, 110...communication unit, 111...input unit, 112...display unit, 113...imaging unit, 120...control unit, 121...display control unit, 122...management operation reception unit, 123...rented terminal unique number acquisition unit, 124...terminal number acquisition unit, 125...two-dimensional code reading unit, 126...rented terminal status management unit, 127...user ID acquisition unit, 128...registration request unit, 129...notification request unit, 130...prompting unit, 141...facility information storage unit, 200...management device, 210...communication unit, 220...control unit, 221...linking unit, 222...registration unit, 223 ...rented terminal status acquisition unit, 241...linked terminal number storage unit, 300...rented terminal, 310...communication unit, 311...operation unit, 312...display unit, 320...control unit, 321...display control unit, 322...two-dimensional code generation unit, 323...sound unit, 324...status acquisition unit, 341...rented terminal number storage unit, 400...user terminal, 410...communication unit, 411...input unit, 412...display unit, 413...imaging unit, 420...control unit, 421...display control unit, 422...two-dimensional code generation unit, 423...sound unit, 424...status information acquisition unit, 441...user terminal number storage unit

Claims

1. A terminal number acquisition unit that acquires a user terminal number used for calling a user at a facility; An urging unit that, when the user terminal number is acquired by the terminal number acquisition unit, urges to acquire user identification information used for a predetermined application software installed on the user terminal; A user identification information acquisition unit that acquires the user identification information from the user terminal in response to the urging by the urging unit; A registration request unit that, based on the acquired user terminal number and the user identification information, makes a request to associate the user terminal number and the user identification information, and a request to register indicating that the user terminal number is in use; Comprising: A reception terminal.

2. A notification request unit that, in response to the user terminal number indicating use being acquired by the terminal number acquisition unit, makes a request for notification from the facility to the predetermined application that uses the user identification information associated with the user terminal number; The reception terminal according to claim 1.

3. Comprising a reception unit that receives an operation from a facility staff member; The notification request unit makes a request for notification from the facility in response to an operation indicating a call being received by the reception unit; The reception terminal according to claim 2.

4. The terminal number acquisition unit acquires a lending terminal number to which lending terminal destination information indicating the destination of a lending terminal lent to a user is pre-associated; The registration request unit makes a registration request indicating that the lending terminal number is in use based on the lending terminal number acquired by the terminal number acquisition unit; The reception terminal according to any one of claims 1 to 3.

5. A notification request unit that, in response to the lending terminal number indicating use being acquired by the terminal number acquisition unit, makes a request for notification from the facility to the lending terminal at the destination indicated by the lending terminal destination information associated with the lending terminal number; The reception terminal according to claim 4.

6. Comprising a reading unit that reads a code; The user terminal number and the lending terminal number are encoded and displayed on a medium; The terminal number acquisition unit acquires the user terminal number or the lending terminal number based on the code read by the reading unit; The reception terminal according to claim 4 or 5.

7. It is provided with a reading unit that reads a code, The user identification information is encoded and displayed on the display unit of the user terminal, The terminal number acquisition unit acquires the user identification information based on the code read by the reading unit, The reception terminal according to any one of claims 1 to 6.

8. It is provided with a reception unit that receives an operation from a facility staff member, When the registration request unit receives an operation indicating that a visit has been made by the reception unit, the registration request unit requests the cancellation of the associated registration and the registration that the user terminal number is not in use. The reception terminal according to any one of claims 1 to 7.

9. A computer used for a reception terminal, A terminal number acquisition step of acquiring a user terminal number used for calling a user at a facility, When the user terminal number is acquired in the terminal number acquisition step, a prompting step of prompting to acquire user identification information used for a predetermined application software installed on the user terminal, A user identification information acquisition step of acquiring the user identification information from the user terminal in response to the prompting in the prompting step, Based on the acquired user terminal number and the user identification information, a registration request step of requesting to associate the user terminal number and the user identification information and a registration request indicating that the user terminal number is in use, A registration method for executing a process including.

10. A computer used for a reception terminal, A terminal number acquisition unit that acquires a user terminal number used for calling a user at a facility, A prompting unit that prompts to acquire user identification information used for a predetermined application software installed on the user terminal when the user terminal number is acquired by the terminal number acquisition unit, A user identification information acquisition unit that acquires the user identification information from the user terminal in response to the prompting by the prompting unit, A registration request unit that requests to associate the user terminal number and the user identification information and a registration request indicating that the user terminal number is in use based on the acquired user terminal number and the user identification information, A program for functioning as.

11. A registration system including a user terminal, a reception terminal, and a management device that performs registration related to calling a user at a facility, The reception terminal includes a terminal number acquisition unit that acquires a user terminal number used for the call, a prompting unit that, when the user terminal number is acquired by the terminal number acquisition unit, prompts for acquisition of user identification information used for a predetermined application software installed in the user terminal, a user identification information acquisition unit that acquires the user identification information from the user terminal in response to the prompting by the prompting unit, and a registration request unit that makes a request to the management device to associate the acquired user terminal number and the user identification information, and a request to register indicating that the user terminal number is in use and is a registration system provided with the above components.

Images