JP7306437B2 - registration system - Google Patents

Description

The present invention relates to a registration system applied to an elevator system that manages elevators.

2. Description of the Related Art Conventionally, there has been known a reception terminal installed at a reception desk of a facility such as a hospital or a restaurant to accept users waiting for their turn.

The reception terminal disclosed in Patent Literature 1 displays a reception screen for receiving a waiting list for a facility. When the user operates the reception screen and inputs necessary information, to send an acceptance request.

Japanese Patent Application Laid-Open No. 2019-82993 (published on May 30, 2019)

In an environment where a facility where a reception terminal is installed resides in a building and users use an elevator to go to the facility, it is assumed that a plurality of users ride together in the same elevator. In this situation, the users who came to the elevator platform earlier get off the elevator later than the users who came later, and the reception terminals may be used in that order. In other words, the order of arrival at the elevator hall and the order of reception at the facility may be reversed.

SUMMARY OF THE INVENTION An object of the present invention is to provide a registration system capable of suppressing occurrence of the above unreasonableness.

In order to solve the above problems, a registration system according to aspect 1 of the present invention includes an input reception unit that receives input information generated in response to an input operation performed by a user of an elevator, and based on the input information, a destination floor specifying unit that specifies a destination floor to be registered in the elevator; and an acceptance information generating unit for generating acceptance information for registering acceptance.

According to the above configuration, in addition to registering the destination floor in the elevator, it is possible to register reception in the facility in accordance with the input operation performed by the user of the elevator. As a result, it is possible to reduce the occurrence of irrationality in which the order of arrival at the elevator hall and the order of reception at the facility are reversed among a plurality of users.

In addition, the registration system according to aspect 2 of the present invention may further include a destination floor registration unit that registers the destination floor for the elevator based on the result of identification by the destination floor identification unit.

According to the above configuration, it is possible to construct a registration system capable of completing the registration of the destination floor in the elevator in accordance with the input operation performed by the user of the elevator.

In addition, the registration system according to aspect 3 of the present invention, in aspect 2, further includes an acceptance availability determination unit that determines acceptance availability at the facility, wherein the destination floor registration unit determines that the acceptance availability determination unit determines that the reception availability determination unit is negative. When it does, it is not necessary to register the destination floor.

According to the above configuration, when the user performs an input operation for calling an elevator, the user can know that the target facility cannot be used before the user actually arrives at the facility. Then, it is possible to avoid wastefully transporting the user to the floor of the facility that cannot be used. For the user, there is an advantage that wasteful travel can be avoided, while for the elevator system, there is an advantage that unnecessary calls and travel do not occur.

Further, the registration system according to aspect 4 of the present invention, in any one of aspects 1 to 3, performs reception registration of the user with respect to the facility based on the reception information generated by the reception information generation unit. A reception registration unit may be further provided.

According to the above-described configuration, it is possible to construct a registration system capable of completing reception registration in accordance with an input operation performed by an elevator user. Normally, the user has to perform the usage application operation separately at the reception of the facility separately from the elevator call operation, but according to the registration system of the present disclosure, the call registration and the Since the reception registration is completed, the convenience for the user is high.

Further, in the registration system according to aspect 5 of the present invention, in aspect 4, the reception registration unit maintains the reception registration of a plurality of users in the order in which the input information is received by the input reception unit. you can go

According to the above configuration, it is guaranteed that applications for use are accepted in order from the person who arrives at the elevator, and the irrational occurrence of the order of arrival at the elevator hall and the order of acceptance at the facility being reversed is prevented. can be avoided.

Further, the registration system according to aspect 6 of the present invention, in any one of aspects 1 to 5, is installed at the elevator hall and read the information recorded on the information recording medium held by the user. An information reader that generates input information may be further provided.

According to the above-described configuration, when accepting a usage application from a user, the user can easily input into the registration system various unique information related to the user that must be managed by the registration system. can. Specifically, the user only has to present the information recording medium he or she holds so that it can be read by the information reading device, saving the trouble of inputting various unique information into the registration system through complicated operations. can be done.

In order to solve the above problems, a registration system according to aspect 7 of the present invention includes an information reading device for reading information recorded on an information recording medium held by a user, and based on the information read by the information reading device, a destination floor registration unit for registering in an elevator the destination floor where the facility used by the user is installed; and a reception registration unit that performs reception registration of the user with respect to. According to the above configuration, the same effects as those of the registration system according to aspect 1 can be obtained.

The registration system according to each aspect of the present invention may be implemented by a computer. In this case, the registration system is implemented by the computer by operating the computer as each part (software element) included in the registration system. A control program for the registration system and a computer-readable recording medium recording it are also included in the scope of the present invention.

According to one aspect of the present invention, it is possible to reduce the occurrence of unreasonable occurrences such as the order of arrival at the elevator platform and the order of reception at the facility being reversed among a plurality of users.

1 is a block diagram showing the main configuration of a registration system according to one embodiment of the present invention; FIG. It is a figure which shows the external appearance of the operating panel with which an information reader is provided. It is a figure which shows an example of the data structure of the unique information memorize|stored in ID card. It is a figure which shows an example of the input guidance screen displayed on a control panel. It is a figure which shows an example of the facility selection screen displayed on a control panel. It is a figure which shows an example of the data structure of the input information which an information reading device produces|generates. It is a figure which shows an example of the data structure of user DB memorize|stored in the memory|storage part of a security system. FIG. 5 is a diagram showing an example of a data structure of reception information generated by a reception information generation unit; It is a figure which shows an example of the data structure of reception registration DB memorize|stored in the memory|storage part of a reception system. It is a figure which shows an example of the notification screen of permission displayed on a control panel. It is a figure which shows an example of the refusal notification screen displayed on a control panel. It is a figure which shows an example of the destination floor selection screen displayed on a control panel. FIG. 10 is a sequence diagram showing the flow of registration processing; FIG. 10 is a diagram showing another example of the data structure of the user DB stored in the storage unit of the security system; It is a figure which shows the other example of the notification screen of permission displayed on a control panel. It is a figure which shows the other example of an ID card. It is a figure which shows the other example of an ID card. It is a figure which shows the other example of an ID card. FIG. 12 is a sequence diagram showing another example of the flow of registration processing;

[Embodiment 1]
An embodiment of the present invention will be described in detail below. FIG. 1 is a schematic diagram showing an example of an elevator system. The schematic diagram shown in FIG. 1 includes a block diagram showing an example of the main configuration of the registration system according to the present embodiment, which is installed in the elevator system.

<Overview of Elevator System>
Elevator systems are installed in buildings with multiple floors. For example, one or more facilities are installed in a building. Facilities are facilities for providing services to users, and include, for example, hospitals, restaurants, beauty salons, karaoke parlors, banks, post offices, government offices, and the like. In the building, one facility may be installed on multiple floors, or multiple facilities may be installed on one floor. In this embodiment, as a building in which the above-described elevator system is installed, there are medical facilities operated by each tenant that provides various medical services, from the 2nd floor to the nth floor (for example, the 7th floor) A building in which one or more are installed on each floor is assumed. In addition, facilities may be installed on the first floor, or only an entrance may be provided and no facilities may be installed.

As shown in FIG. 1, the elevator system includes a registration system 100 and a plurality of reception systems 101 (101b, 101c, . . . ). The reception system 101 is a system operated individually by each facility. For example, one reception system 101 is provided for each facility. The reception system 101 is a system for receiving usage applications from users, registering information on the users, and managing users who desire services (for example, medical treatment) provided by the facility. In the reception system 101, information of users who are applicants is registered in the order in which usage applications are received. In general, services are provided to users in the order in which registration is completed.
The registration system 100 is a system for registering calls for elevators going up and down within a building and for supporting the above-described registration of user information (hereinafter referred to as "reception registration") in the reception system 101. .

"Reception registration" means that the reception system 101 accepts a usage application from the user and registers the information of the user in its own system in order to manage the user who desires the service of the facility. Point. Specifically, in the present embodiment, input information generated by the user operating the information reading device 3 is temporarily accepted by the security system 1 . Registering reception information (details will be described later) generated based on the reception of this input information by the security system 1 in the reception system 101 of the facility that actually provides the service is called "reception registration". Therefore, the “reception registration” performed by the reception system 101 is distinguished from the reception of input information by the security system 1 . By completing the user's "reception registration" in the reception system 101 of the facility, the user, who is the applicant, is officially recognized as a service provider at the facility.

"Support for reception registration" means that the registration system 100, in response to obtaining input information of the user from the information reading device 3, sends the reception information necessary for reception of the usage application of the user to the reception system 100. means to provide to By receiving user reception information from the registration system 100, the reception system 101 can perform reception registration of the user.

The registration system 100 includes a security system 1 , an elevator control system 2 , and an information reader 3 in order to register an elevator call and support reception registration by a reception system 101 .

The information reading device 3 is a device for reading unique information specific to a user recorded on an information recording medium held by the user. In this embodiment, the information reader 3 also functions as a call generator that generates an elevator call in response to reading the unique information. The information reader 3 has an operation panel for a user to call an elevator.

The information recording medium is, for example, an ID card 4 on which unique information is recorded. For example, the ID card 4 may be lent by a building management company or the like to a user who is permitted to enter and exit the building. Alternatively, the ID card 4 may be issued by a management organization of each facility to users who are permitted to use the facilities in the building. and so on.

The user performs an input operation for calling an elevator to the information reading device 3 in order to go to the facility that the user wants to use. In this "input operation", the user presents the held ID card 4 so that it can be read by the information reader 3, and causes the information reader 3 to read the unique information in the ID card 4. included. In addition, this "input operation" may include the user's operation of the control panel of the information reader 3 to input an instruction.

The information reader 3 generates input information according to the input operation, that is, based on the unique information read from the ID card 4, and transmits the input information to the security system 1 and the elevator control system 2.

The elevator control system 2 centrally controls one or more elevators installed in the building. Specifically, the elevator control system 2 selects a car for transporting the user in response to the user's input operation for calling an elevator to the information reader 3 installed on each floor. select. Then, the elevator control system 2 registers the landing floor call and the destination floor call to an elevator control device (not shown) that controls the elevation of the selected car.

The security system 1 executes various processes that mediate between the user and the reception system 101 and between the user and the elevator control system 2, and the reception system 101 and the elevator control system 2 respectively execute support the registration behavior.

Specifically, the security system 1 receives the input information transmitted from the information reading device 3, specifies the destination floor to which the user who has input the input information should be transported, and instructs the elevator control system 2 to do. Thereby, the elevator control system 2 can register the destination floor call to the elevator.

More specifically, the security system 1 receives input information transmitted from the information reader 3, and receives reception information including information about the user, which is necessary for the reception system 101 to execute the reception registration described above. is generated and provided to the reception system 101 . Thus, the reception system 101 can execute reception registration by registering the reception information in its own system. As a result, usage applications from users are formally accepted and managed at the facility.

As described above, the registration system 100 according to the present embodiment includes the information reading device 3 for reading information recorded on the ID card 4 (information recording medium) held by the user, and the unique information read by the information reading device 3. A security system 1 is provided for registering the destination floor where the facility used by the user is installed in the elevator based on (information). As a result, when the information reader 3 reads the unique information, the reception registration of the user is performed for the facility used by the user. Note that the security system 1 may be provided with the reception registration unit 32 that performs this reception registration.

According to the above configuration, it is possible to perform elevator call registration and facility reception registration in response to an input operation performed on the information reading device 3 by the user of the elevator. As a result, it is possible to reduce the occurrence of irrationality in which the order of arrival at the elevator hall and the order of reception at the facility are reversed among a plurality of users.

In the following, the main configuration of the registration system 100 for reducing the occurrence of the irrationality described above will be described in more detail.

<Information reader 3>
FIG. 2 is a diagram showing the appearance of a control panel provided in the information reader 3. As shown in FIG. The operation panel 301 includes a display unit for presenting information to the user, an operation unit for accepting input operations from the user, and reading unique information of the user from the information recording medium presented by the user. and an information reading unit 303 for As illustrated, the display unit and the operation unit may be integrally formed as a touch panel 302 .

In addition to the operation panel, the information reading device 3 includes a control section and a communication section, both of which are not shown. The control section controls each section of the information reading device 3 in an integrated manner. The communication unit communicates with the security system 1 and the elevator control system 2 to send and receive information.

The information reader 3 may be installed, for example, near the door of the elevator on each floor. Alternatively, the main body of the information reader 3 may be buried somewhere in the building, and only the operation panel 301 may be provided on the wall near the door of the elevator, for example.

Any technique can be adopted as means for the information reading unit 303 to read information. Although not limited to this, for example, the information reading unit 303 is configured as an RFID tag reader that reads information from an IC (Integrated Circuits) tag embedded in the ID card 4 and having a built-in RFID (Radio Frequency-Identification) circuit. may Alternatively, the information reading section 303 may be configured as a code reader that reads a bar code or two-dimensional code printed on the ID card 4 . Alternatively, the information reading section 303 may be configured as a magnetic reader for reading magnetic information from the ID card 4 configured as a magnetic recording medium. Alternatively, it may be configured as a code reader that reads a barcode or two-dimensional code displayed by a smartphone application, or may be equipped with an NFC (Near Field Communication) function.

The control unit of the information reading device 3 generates input information based on the unique information of the user read from the information reading unit 303 and the input operation accepted via the touch panel 302 . The communication unit of the information reader 3 transmits the generated input information to the security system 1 and the elevator control system 2 via a communication network such as a LAN (Local Area Network) in the building. The operation of the information reading device 3 will be described below with a specific example. First, the data structure of unique information read by the information reading device 3 will be described.

(Inherent information in ID card 4)
FIG. 3 is a diagram showing an example of the data structure of unique information stored in the ID card 4. As shown in FIG. A user's unique information includes at least a user ID and a facility ID, for example. The unique information may further include facility name, floor location, name, date of last visit, etc., as required.

In this embodiment, as an example, a building management company issues an ID card 4 to a user who is permitted to enter and exit the building. For example, the operator of the management company operates the information writing terminal to write the unique information of the user in the storage area of the ID card 4 in advance. A user ID is identification information for uniquely identifying a building user. The identification information may be automatically numbered by the information writing terminal or security system 1 described above so as to be unique to the user. A facility ID is identification information for uniquely identifying a facility installed in a building. The facility ID field stores the facility ID of the facility used by the user. It is assumed that the registration system 100 and the reception system 101 share which facility ID is assigned to which facility.

The facility name represents the name of the facility. The facility name is used, for example, to be displayed on the touch panel 302 of the information reader 3 as information for the user to identify the facility. The location floor indicates the floor where the facility is installed. In this embodiment, one location floor is assigned to one facility. Even if one facility is installed over a plurality of floors, it is assumed that one representative floor where the reception of the facility is installed is assigned.

For example, the operator of the management company, in the information writing terminal, performs an operation to link the user and the facility in response to a request from the user or the facility that provides the service to the user, and links the user to the user ID. Then, the facility ID is stored in the ID card 4. The facility name and the floor where the facility is located may be automatically stored in the ID card 4 when the facility ID is recorded. The illustrated unique information is the unique information of the user with the user ID "U123456". The unique information indicates that the user with the user ID "U123456" is a user of the facility "clinic A" and the facility "clinic B".

Furthermore, the ID card 4 may include a storage area for storing the name of the user. Also, the ID card 4 may include a storage area for storing the date of the last visit. For example, when the user holds the ID card 4 over the information reading section 303 of the information reading device 3, the information rewriting section (not shown) of the information reading device 3 uses the date and time at that time as the date of the last visit to the above storage area. can be stored in

(accept input operation)
FIG. 2 shows an example of a home screen normally displayed on the touch panel 302 of the information reading device 3. As shown in FIG. FIG. 4 is a diagram showing an example of an input guidance screen for prompting the user to present unique information. FIG. 5 is a diagram showing an example of a facility selection screen for accepting selection of a destination facility from a user.

For example, the information reading device 3 may display a home screen for accepting user input operations on the touch panel 302 as shown in FIG. In this embodiment, the input operation for calling the elevator differs between the user who holds the building ID card 4 and the user who does not. Therefore, the control unit of the information reading device 3 provides a GUI (graphical user interface) for allowing the user to input whether the user holds the ID card 4 or does not hold the ID card 4 on the home screen. interface) components may be placed. As an example of such a GUI component, the control unit arranges on the home screen a card present button 311 that is selected by a user holding an ID card 4 and a no card button 312 that is selected by a non-holding user. You may

The control unit may display the input guidance screen shown in FIG. While the input guidance screen is displayed, the control unit may supply power to the information reading unit 303 and wait for the ID card 4 to be held within a readable distance.

The control unit acquires the facility ID from the unique information read by the information reading unit 303 . When a plurality of facility IDs are acquired, the control unit may cause the touch panel 302 to display the facility selection screen shown in FIG. The control unit arranges the GUI component on the facility selection screen so that each of the plurality of facility IDs included in the unique information that has been read becomes an option. For example, when the unique information shown in FIG. 3 is read, the control unit displays a first button 321 for selecting "Clinic A" and a second button 322 for selecting "Clinic B" on the facility selection screen. may be placed.

The control unit generates input information based on a user's input operation. Specifically, the control unit generates input information in response to the fact that one facility ID is included in the read unique information or that one facility is selected via the facility selection screen. do. The input information is information indicating that a request has been made by the user to the registration system 100 and the content of the request, and serves as a trigger for the registration system 100 to start its operation.

(Generation of input information)
FIG. 6 is a diagram showing an example of the data structure of input information generated by the information reading device 3 according to user's input operation. The input information includes information necessary for registering an elevator call and information necessary for performing reception registration. In other words, the input information includes information indicating (1) who is going, (2) where from, and (3) where. Specifically, as illustrated, the input information includes (1) user ID, (2) hall floor, and (3) facility ID. In the case where there is a one-to-one correspondence between a user and a facility, and the destination facility is uniquely identified by identifying the user, item (3) may be omitted from the input information. .

The control unit stores the user ID read from the ID card 4, the floor on which the device (information reading device 3) is installed, that is, the boarding floor, and the facility ID read from the ID card 4. Generate input information that contains: When there are multiple facility IDs read from the ID card 4, the control unit includes the facility ID of the facility selected by the user via the facility selection screen in the input information. If only one facility ID is read from the ID card 4, the control unit may omit the facility ID from the input information. The control unit transmits the generated input information to the security system 1 and the elevator control system 2 via the communication unit.

<Security system 1>
The security system 1 includes an input reception unit 11, a destination floor identification unit 12, a reception information generation unit 13, and a storage unit 14, as shown in FIG. The security system 1 may include a communication section (not shown). Each part of the input reception unit 11, the destination floor identification unit 12, and the reception information generation unit 13 is configured as, for example, a CPU (central processing unit) or the like. It is realized by reading a program stored in the storage unit 14 stored in a RAM (random access memory) or the like and executing it.

The input reception unit 11 receives input information transmitted from the information reading device 3 . Specifically, the input reception unit 11 acquires the date and time when the communication unit received the input information, and associates the information of the date and time with the received input information as the reception date and time. The input information associated with the reception date and time may be temporarily stored in the storage unit 14 .

Based on the received input information, the destination floor specifying unit 12 specifies to which floor of the building the user who has entered the input information should be transported. That is, the destination floor identification unit 12 identifies the destination floor to be registered in the elevator based on the input information.

As will be described later, the storage unit 14 stores a user database (hereinafter referred to as DB) that stores correspondence between users and facilities used by the users. The destination floor identification unit 12 identifies the location floor of the facility associated with the user ID or the facility ID included in the input information in the user DB, and identifies the identified location floor as the destination floor. do. If one user is associated with only one facility, the destination floor identification unit 12 can identify one destination floor based on the user ID. When a plurality of facilities are associated with one user, the destination floor identification unit 12 can identify one destination floor based on one facility ID in the input information. The destination floor identification unit 12 transmits the identified destination floor (identification result) to the elevator control system 2 .

The reception information generation unit 13 generates reception information based on the input information being received by the input reception unit 11 . The reception information includes various pieces of information about the user that are necessary for registering in the reception system 101 that the input information has been received by the input reception unit 11 . The acceptance information is information indicating that the user has applied for use of the facility and when the application for use was accepted by the registration system 100 . The reception information serves as a trigger for the reception system 101 to start reception registration, and helps the reception system 101 to correctly grasp the order in which the usage applications were received.

(Specification of destination floor)
FIG. 7 is a diagram showing an example of the data structure of the user DB stored in the storage unit 14. As shown in FIG. The user DB includes, for example, items such as user ID, facility ID, facility name, and location floor. In the user DB, one or more facility IDs are associated with the user ID. Thereby, the security system 1 can grasp which user uses which facility. Specifically, the reception information generating unit 13 can grasp which user is going to which facility based on the input information. In addition, each facility is associated with the floor where it is located. Thereby, the destination floor specifying unit 12 can specify to which floor the user should be transported based on the input information.

(Generation of reception information)
FIG. 8 is a diagram showing an example of the data structure of reception information generated by the reception information generation unit 13. As shown in FIG. The reception information includes information necessary for the reception system 101 to register for reception. In other words, the reception information includes information indicating (1) whose use application was received and (2) when it was received. Specifically, as illustrated, the reception information includes (1) user ID and (2) reception date and time. A facility ID may be associated with the reception information. Thereby, the reception information generating unit 13 can grasp to which reception system 101 of the facility the generated reception information should be transmitted.

The reception information generation unit 13 generates reception information including the user ID included in the input information received by the input reception unit 11 and the reception date and time indicating the date and time when the input reception unit 11 received the input information. do. The reception information generation unit 13 may associate the generated reception information with a facility ID indicating to which facility the usage application is addressed. The facility ID is also included in the input information received by the input receiving unit 11, like the user ID.

The reception information generator 13 transmits the generated reception information to the reception system 101 of the facility indicated by the facility ID associated with the reception information. As a result, the reception system 101 can grasp (1) whose use application was received and (2) when the use application was received for the relevant facility, and maintains the order in which the use application was received. can be registered in its own system.

<Elevator control system 2>
The elevator control system 2 includes a call registration unit 21 as shown in FIG. The elevator control system 2 may include a communication section (not shown).

The call registration unit 21 registers a call to an elevator control device (not shown) that controls the elevation of the car of the elevator. When there are a plurality of elevators in the building, the call registration unit 21 also selects which car is to arrive at the hall according to the hall floor where the call in the information reader 3 is generated.

The call registration unit 21 may include a destination floor registration unit 211 and a hall registration unit 212 . The destination floor registration unit 211 registers a destination floor call in the elevator control device. The hall registration unit 212 registers the hall floor call in the elevator control device. Each unit constituting the call registration unit 21 is stored in a storage device (not shown) configured as a ROM (read only memory) or the like by a control unit (not shown) configured as a CPU (central processing unit) or the like. It is realized by reading a program into a RAM (random access memory) or the like and executing it.

In response to receiving the input information from the information reader 3, the hall registration unit 212 identifies the hall floor based on the input information. The hall registration unit 212 selects a car to be directed to the hall according to the identified hall floor, and registers the hall call to the elevator control device that controls the elevation of the car. The hall registration unit 212 may select, for example, the car at the position where the passenger can reach the floor of the hall the fastest.

The destination floor registration unit 211 receives the destination floor from the destination floor identification unit 12 of the elevator control system 2, and registers the destination floor call indicating the destination floor designated by the destination floor identification unit 12 in the selected elevator control device. do.

According to the registered landing floor call and destination floor call, the elevator control device directs the car under its control to the landing floor, and can then carry the user to the destination floor.

<Reception system 101>
The reception system 101 (101b, 101c, . . . ) is provided for each facility, and receives and manages usage applications from users who wish to use the facility. The reception system 101 includes, as shown in FIG. The reception system 101 may include a communication unit (not shown). The acceptability determination unit 31 and the acceptability registration unit 32 are stored in a storage unit 33 configured as a ROM (read only memory) or the like by a control unit (not shown) configured as a CPU (central processing unit) or the like. This is realized by reading out a program stored in a RAM (random access memory) or the like and executing it. It should be noted that the acceptance propriety determination unit 31 and the acceptance registration unit 32 may be provided in the security system 1 .

The acceptability determination unit 31 determines whether or not a facility can accept an application, specifically, whether or not a usage application from a user can be accepted. For example, the reception acceptability determination unit 31 determines that the use application cannot be accepted due to the fact that the facility is closed (for example, the clinic is closed or out of hours). good too. The acceptability determination unit 31 determines "acceptable" when the facility is in a state in which a use application can be accepted, and determines "acceptable" when the facility is in a state in which a use application cannot be accepted. In response to reception of the reception information from the reception information generation unit 13, the reception possibility determination unit 31 determines the state of the facility, and sends the judgment result indicating "reception possible" or "reception not possible" to the elevator control system 2. may be transmitted to the call registration unit 21 of the The acceptability determination unit 31 may reply to the security system 1 with the determination result described above, if necessary.

The reception registration unit 32 performs reception registration based on the reception information generated by the reception information generation unit 13 when the reception possibility determination unit 31 determines that the reception is possible. The reception registration is completed when the reception registration unit 32 registers the information about the user included in the reception information in the reception registration database (hereinafter referred to as DB) stored in the storage unit 33 .

(reception registration)
FIG. 9 is a diagram showing an example of the data structure of the reception registration DB stored in the storage unit 33. As shown in FIG. The reception registration DB, for example, includes at least the items of user ID, reception date and time, and reception number. The reception registration DB may optionally include items such as medical record number, patient name, and date of previous hospital visit. These optional items are appropriately determined according to the services provided by each facility.

For example, when receiving the reception information shown in FIG. , is registered in the reception registration DB. Then, the reception registration unit 32 issues a reception number and associates it with the registered record.

The reception number is a serial number for managing the users received on that day in the reception system 101 . The reception registration unit 32 maintains the order in which the input information was received by the input reception unit 11 of the security system 1 and associates the reception numbers. Specifically, the reception registration unit 32 associates the reception numbers in the order of reception date and time included in the reception information. In a facility, service providers (doctors, nurses, etc.) basically call users in order of reception numbers and provide services (medical treatment, etc.) to the users.

For example, the user with the user ID "U123456" (hereinafter referred to as the first user), the user with the user ID "U123462" (hereinafter referred to as the second user), and the user with the user ID "U123460" ( Assume that three users who have business at the clinic A hold their ID cards 4 over the information reader 3 in order of the third user). In this case, as an example, from the reception information generation unit 13, the following three pieces of reception information (user ID, reception date and time);
First reception information (U123456, 2020/3/16 16:23:15)
Second reception information (U123462, 2020/3/16 16:23:21)
Third reception information (U123460, 2020/3/16 16:23:28)
is supplied to the reception registration unit 32 .

Upon receiving the above three pieces of reception information, the reception registration unit 32 registers each record in the reception registration DB so that the earlier the reception date and time, the lower the reception number, as shown in FIG.

The reception registration unit 32 may further store other items associated with the user ID (medical record number, patient name, last hospital visit date, etc.). Although not shown, for example, the storage unit 33 stores a table indicating the correspondence between the user ID of each user managed in the registration system 100 and the medical record number of each patient managed in the reception system 101. is remembered in Therefore, the reception registration unit 32 can identify a patient based on the user ID included in the reception information, and identify information related to the patient (medical record number, patient name, date of previous visit, etc.). .

<Feedback to users>
When the acceptability determination unit 31 of the reception system 101 determines that the call can be accepted, the acceptability determination result is transmitted to the call registration unit 21 of the elevator control system 2 . The call registering unit 21 completes the registration of the landing floor call and the destination floor call according to the result of determination that the call is acceptable. The call registration unit 21 returns a registration completion report indicating that the call registration has been completed to the information reading device 3 that originated the call. The registration completion report includes, for example, the identification information of the elevator in which the user is placed (e.g., No. 1, No. 2, . include.

The control unit of the information reader 3 generates a permission notification screen according to the registration completion report received from the call registration unit 21 and causes the touch panel 302 to display the screen. FIG. 10 is a diagram showing an example of a permission notification screen presented to the user. The permission notification screen is a GUI screen for notifying that the use of the facility is permitted and the reception by the facility is completed, and for guiding the elevator (boarding plane) that the user should board in order to go to the facility. be.

As shown in FIG. 10, the permission notification screen may include, for example, a reception completion notification 331 that notifies that reception by the facility has been completed, and a boarding machine notification 332 that guides the boarding machine. As a result, the user can recognize that his or her use application has been accepted at the facility, and can grasp which elevator should be boarded.

An OK button 333 may be arranged on the permission notification screen as necessary. The OK button 333 is a GUI component for switching the permission notification screen to the home screen shown in FIG. As a result, the subsequent user's input operation can be accepted without making the subsequent user wait. The control unit may automatically switch to the home screen after a certain period of time has elapsed since the permission notification screen was displayed.

When the acceptability determination unit 31 determines that the call is not to be accepted, the result of the determination as to whether or not the call is to be accepted is transmitted to the call registration unit 21 . Each part of the call registration part 21 may cancel the registration of the call to the elevator control device according to the result of the determination as to whether or not the call is accepted. The call registration unit 21 returns a registration incomplete report indicating that the call was not registered to the information reading device 3 that originated the call. The registration incompletion report includes, for example, a notice that the facility did not accept the user's use application, and a facility ID that identifies the facility that did not accept the application.

The control unit of the information reading device 3 generates a refusal notification screen according to the registration incompletion report received from the call registration unit 21 and causes the touch panel 302 to display the screen. FIG. 11 is a diagram showing an example of a refusal notification screen presented to the user. The rejection notification screen is a GUI screen for notifying the user that use of the facility has been rejected.

As shown in FIG. 11, the refusal notification screen may include, for example, an unavailability notification 341 explaining why the facility cannot be used. Thereby, the user can confirm that his or her application for use was not accepted at the facility and the reason therefor.

If necessary, a return button 342 may be arranged on the rejection notification screen. The return button 342 is a GUI part for switching the rejection notification screen to the home screen shown in FIG. As a result, the subsequent user's input operation can be accepted without making the subsequent user wait. The control unit may automatically switch to the home screen after a certain period of time has elapsed since the refusal notification screen was displayed.

<Correspondence when there is no ID card 4>
If the user does not have the ID card 4 because it is the first time the user visits the library or has forgotten to carry it, the user operates the information reader 3 as a normal call generator. , you can call the elevator.

When the control unit of the information reading device 3 receives a selection operation on the no-card button 312 on the home screen shown in FIG. Let FIG. 12 is a diagram showing an example of a destination floor selection screen. As shown in FIG. 12, for example, a button corresponding to each floor for selecting a destination floor may be arranged on the destination floor selection screen.

When receiving a button operation on the destination floor selection screen, the control unit inputs input information indicating the destination floor corresponding to the operated button and the landing floor where the own device (information reading device 3) is installed, Send to the elevator control system 2 .

When the call registration unit 21 of the elevator control system 2 receives such input information that does not include the user ID, the call registration unit 21 selects a car based on the landing floor and the destination floor included in the input information. to register the hall call and destination call in the elevator controller. The call registration unit 21 returns the identification information of the elevator corresponding to the selected car to the information reader 3 .

Upon receiving the elevator identification information from the call registration unit 21, the control unit of the information reader 3 may cause the touch panel 302 to display a screen in which the reception completion notification 331 is omitted among the screens shown in FIG.

<Processing flow>
FIG. 13 is a sequence diagram showing the flow of registration processing executed in the elevator system. The illustrated series of processes are triggered by the information reading device 3 accepting an input operation from the user.

In S101, the control section of the information reading device 3 determines whether or not the unique information has been read from the ID card 4 by the information reading section 303 after the card presence button 311 shown in FIG. 2 is selected. If the reading of the unique information is successful, the control unit proceeds to S102. If the unique information could not be read, or if the no-card button 312 was selected, the control unit proceeds to S122.

In S102, the control unit generates input information based on the read unique information. The input information includes user ID, hall floor and (if necessary) facility ID.

In S103, the input reception unit 11 of the security system 1 receives input information. The input reception unit 11 records the reception date and time when the input information is received.

In S104, the reception information generation unit 13 generates reception information to be supplied to the facility specified based on the input information. The reception information includes a user ID and reception date and time.

In S105, the reception information generator 13 transmits the generated reception information to the reception system 101 of the specified facility.

In S106, the destination floor identification unit 12 identifies the destination floor of the user based on the input information received in S103, and notifies the elevator control system 2 of the destination floor.

In S<b>107 , the reception system 101 receives reception information from the security system 1 .

In S108, the acceptability determination unit 31 determines whether or not the user who is the applicant can be accepted. That is, the acceptability determination unit 31 determines whether or not the facility is in a state where it can provide services to users. The acceptability determination unit 31 proceeds to S109 if it is acceptable, and proceeds to S111 if it is not acceptable.

In S<b>109 , the acceptability determination unit 31 transmits to the elevator control system 2 a determination result indicating acceptability.

In S110, the reception registration unit 32 performs reception registration based on the reception information received in S107. The reception registration unit 32 registers a record for each user of the applicant in the reception registration DB in order of reception date and time included in the reception information.

In S<b>111 , the acceptability determination unit 31 transmits to the elevator control system 2 the determination result indicating the acceptability.

At S<b>112 , the call registration unit 21 of the elevator control system 2 acquires input information from the information reader 3 as in the security system 1 .

In S113, the call registration unit 21 identifies the hall floor based on the acquired input information.

In S<b>114 , the call registration unit 21 receives the destination floor from the destination floor identification unit 12 .

In S<b>115 , call registration unit 21 determines whether or not the user has been accepted by reception system 101 based on the determination result transmitted from reception availability determination unit 31 . If the received determination result indicates that the call is acceptable, the call registration unit 21 proceeds to S116. If the determination result indicates non-acceptance (NO in S115), the call registration unit 21 generates a registration incomplete report and returns it to the information reading device 3. FIG. In this case, the process proceeds to S121.

In S116, the call registration unit 21 selects an elevator to direct the user to the hall floor.

In S117, the hall registration unit 212 of the call registration unit 21 registers the hall floor call indicating the hall floor specified in S113 in the elevator control device of the selected elevator.

In S118, the destination floor registration unit 211 of the call registration unit 21 registers the destination floor call indicating the destination floor received in S114 in the elevator control device described above.

In S<b>119 , the call registration unit 21 generates a registration completion report and transmits it to the information reader 3 . The registration completion report includes the identification information of the boarding machine and the facility ID of the facility that accepted the user.

In S120, the control unit of the information reader 3 displays the permission notification screen shown in FIG. 10 in response to receiving the registration completion report.

In S121, the control unit displays the refusal notification screen shown in FIG. 11 in response to receiving the registration incomplete report.

In S122, the control unit of the information reader 3 displays the destination floor selection screen shown in FIG.

<Effect>
According to the above-described configuration and method, in addition to registration of the destination floor in the elevator, reception registration with the facility is performed in accordance with the input operation performed by the elevator user. As a result, it is possible to reduce the occurrence of irrationality in which the order of arrival at the elevator hall and the order of reception at the facility are reversed among a plurality of users.

It is not necessary to complete the registration of the destination floor and the reception registration within the security system 1 . The destination floor registration may be performed in the elevator control system 2 and the reception registration may be performed in the reception system 101 . In that case, the security system 1 may provide the elevator control system 2 with the destination floor identified by the destination floor identification unit 12 . Also, the security system 1 may provide the reception information generated by the reception information generation unit 13 to the reception system 101 .

The registration system 100 according to the present embodiment may be disadvantageous to users who take a long time to move, for example, users in wheelchairs, users with leg injuries, users with children, and users who carry a lot of luggage. be improved.

[Embodiment 2]
Other embodiments of the invention are described below. For convenience of description, members having the same functions as those of the members described in the above embodiments are denoted by the same reference numerals, and description thereof will not be repeated.

(Correspondence when the ID card 4 is a dedicated use card for each facility)
The ID card 4 may be issued to users who are permitted to use the facilities in the building by the organization managing each facility. In this embodiment, as an example, the ID card 4 is a patient registration card issued by each facility as a clinic to each user who is a patient. In this embodiment, the patient registration card has a storage area from which information can be read by the information reader 3 . In the patient registration card storage area, at least the user ID supplied between the reception system 101 and the registration system 100 and the facility ID of the facility that issued the patient registration card are stored as unique information. ing. In addition, the patient registration card may contain the patient's individual information required by the facility.

In this embodiment, the ID card 4 presented to the information reader 3 is an individual patient registration card for each facility. Therefore, the information reader 3 can uniquely identify the facility that the user intends to visit by reading the patient registration card.

Therefore, in this embodiment, the input information includes the facility ID in addition to the user ID and the landing floor. As a result, the security system 1 can identify one facility, which is the user's destination, and the floor where the facility is located, based on the input information. Then, the destination floor identification unit 12 identifies the destination floor based on the location floor. The reception information generation unit 13 generates reception information addressed to the destination facility.

Even when the registration system 100 is configured in this manner, the same effects as in the first embodiment are obtained.

[Embodiment 3]
Other embodiments of the invention are described below. For convenience of description, members having the same functions as those of the members described in the above embodiments are denoted by the same reference numerals, and description thereof will not be repeated.

(When each facility issues a user ID for each user)
In the first embodiment, the building management company issues a user ID common to each facility for each user, but the present invention is not limited to this. In this embodiment, a user ID is issued for each user from each facility. The facility allows the user to possess the user ID so that the issued user ID can be read by the information reading device 3 .

For example, the facility issues to the user, as the ID card 4, a patient ID card from which the information reader 3 can read the user ID. A specific example of a patient registration card as such an ID card 4 is shown in FIGS. 16 to 18. FIG. For example, if the information reading unit 303 of the information reading device 3 is a QR code (registered trademark) reader, as shown in FIG. may be issued to Alternatively, for example, if the information reading unit 303 is a tag reader that reads information from an IC chip, as shown in FIG. may be issued to Alternatively, for example, if the information reading unit 303 is a receiver that communicates with a user's mobile communication device such as a smart phone to receive information, the facility may issue a digital patient registration ticket to the user. The user operates his or her own smart phone to display a digital patient registration ticket on the display section of the smart phone, as shown in FIG. 18 . The information reading unit 303 can communicate with the smartphone of the user and receive the user ID of the user. Note that the smartphone may display a QR code indicating the user ID included in the digital patient registration card on the display unit. In this case, the information reading unit 303 as a QR code reader reads the QR code displayed on the display unit and acquires the user ID.

The information reader 3 can transmit input information including the user ID read from the patient registration card to the security system 1 .

In this embodiment, the user DB stored in the storage unit 14 of the security system 1 has a data structure in which the location floor can be specified based on the user ID issued to the user by each facility. It consists of

14 is a diagram illustrating an example of a data structure of a user DB according to the third embodiment; FIG. In this embodiment, in the user DB, the facility and the floor where the facility is located are stored in association with the user ID issued by each facility for each user. When one user uses a plurality of facilities in the same building, different user IDs are assigned to the same user and managed in different records in the user DB.

The destination floor specifying unit 12 of the security system 1 can specify the destination floor based on the user ID included in the input information by referring to the user DB shown in FIG. The reception information generating unit 13 refers to the user DB shown in FIG. 14, based on the user ID included in the input information, identifies the facility for which reception information is to be registered, and generates reception information. be able to.

In this embodiment, the user ID may be anything as long as the reception system 101 of each facility can uniquely identify the user, and may be, for example, the chart number shown in FIG. For example, in the example shown in FIG. 14, the user ID of "clinic A" is the same as the chart number shown in FIG. Also, the user ID issued by another facility may be the same as the chart number issued by the reception system 101 of each facility. As a result, the user ID issued to the user by each facility can be the same number as the chart number of each facility. Therefore, in Embodiment 3, unlike the data items of the reception registration DB shown in FIG. is adopted as a “person ID”. Specifically, as the data structure of the reception registration DB according to the third embodiment, the "user ID" column of the table shown in FIG. is configured as a user ID column for storing user IDs. The name of the data item "medical record number" may be indicated to the user (patient) as "patient number" (for example, FIGS. 16 to 18).

[Modification]
(Response when a user goes to another floor)
After reading the unique information of the ID card 4 on the input guidance screen shown in FIG. 4, it is assumed that the user ID is associated with only one facility ID. Even in such a case, the control unit of the information reader 3 may generate and display a confirmation screen for confirming the destination facility without immediately generating the input information. For example, the confirmation screen may include a message "Are you using **?" and buttons for selecting "Yes" or "No".

In this case, the control unit generates input information and transmits it to the security system 1 and the elevator control system 2 in response to the user selecting the "yes" button. Then, according to the registration completion report transmitted from the elevator control system 2, the permission notification screen shown in FIG. 10 is displayed. Note that the control unit may display the destination floor selection screen shown in FIG. 12 when the "No" button is selected.

In this way, when a user who normally only goes to a certain facility has business on another floor and calls an elevator by holding the ID card 4, the reception of the facility he usually goes to is mistakenly registered. erroneous registration can be avoided.

(Another example of acceptance completion notification)
The reception completion notification displayed on the touch panel 302 of the information reader 3 includes not only the facility name of the facility for which the reception has been completed, but also the reception number of the user accepted at the facility and the reception currently being processed by the facility. It may contain number information.

For example, the control unit of the information reading device 3 may display a reception completion notification 334 shown in FIG. 15 on the touch panel 302 instead of the reception completion notification 331 shown in FIG.

In this case, in S109, in addition to the determination result as to whether or not the reception is acceptable, the reception possibility determination unit 31 of the reception system 101 adds the reception number assigned to the user by the reception registration unit 32 and the current The receipt number processed at the facility concerned is transmitted to the elevator control system 2 .

In S119, the call registration unit 21 of the elevator control system 2 transmits to the information reader 3 a registration completion report containing the reception number of the user and the reception number currently being processed in addition to the boarding machine and facility ID. .

In S120, the control unit of the information reading device 3 sends a reception completion notification 334 based on the facility ID, the reception number of the user, and the reception number currently being processed, which are included in the registration completion report. generated and displayed on the touch panel 302 as shown in FIG.

(Registration timing of destination floor call)
The timing at which the destination floor registration unit 211 of the elevator control system 2 registers the destination floor call to the elevator is not limited to the example shown in FIG. 13 . That is, the registration of the destination floor call need not be performed at the same timing as the registration of the landing floor call. For example, the destination floor registration unit 211 registers the destination floor call after the hall registration unit 212 registers the hall floor call in S117 and the selected car arrives at the hall floor in response to the hall call. may

As an example, as shown in FIG. 19, when the landing floor call is registered by the hall registration unit 212 in S117, the destination floor call is not registered in S118. After the selected car arrives at the landing floor in response to the hall call in response to the registration of the hall call, the call registering unit 21 determines in S123 based on the behavior of the car that the user has entered the car. You may presume that you boarded the For example, the call registration unit 21 may detect that the door of the car that has reached the landing floor has been completely opened, and based on this, it may be estimated that the user has boarded the car. Alternatively, the call registration unit 21 detects the entry and exit of a person in the car based on the detection value of the phototube sensor provided on the door of the car, and based on this, it is estimated that the user has boarded the car. good.

When the call registration unit 21 estimates that the user has boarded the car that has arrived at the landing floor, the process proceeds from YES in S123 to S124. In S124, the destination floor registration unit 211 registers the destination floor call indicating the destination floor identified by the destination floor identification unit 12 in the elevator.

According to the above-described configuration, when a user does not board a car designated as a boarding machine for some reason, it is possible to prevent a car without a user from going up and down to the destination floor in vain. In other words, the elevator control system 2 has the advantage of avoiding unnecessary calls and running.

[Appendix 1]
(Appendix 1)
an input reception unit that receives input information generated according to an input operation performed by a user of the elevator;
a destination floor identifying unit that identifies a destination floor to be registered in the elevator based on the input information;
A reception information generation unit for generating reception information for registering that the input information has been received for the facility specified based on the input information among the facilities installed on any of the plurality of destination floors. and a registration system.

(Appendix 2)
The registration system according to supplementary note 1, further comprising a destination floor registration unit that registers a destination floor for the elevator based on a result of identification by the destination floor identification unit.

(Appendix 3)
Further comprising an acceptance propriety determination unit for judging acceptance propriety at the facility,
2. The registration system according to appendix 2, wherein the destination floor registration unit does not register the destination floor when the acceptability determination unit determines no.

(Appendix 4)
4. The registration system according to any one of appendices 1 to 3, further comprising a reception registration unit that performs reception registration of the user for the facility based on the reception information generated by the reception information generation unit.

(Appendix 5)
5. The registration system according to appendix 4, wherein the reception registration section performs the reception registration of a plurality of users while maintaining the order in which the input information is received by the input reception section.

(Appendix 6)
6. The apparatus according to any one of Appendices 1 to 5, further comprising an information reading device installed at the elevator hall and configured to generate the input information by reading information recorded on an information recording medium held by the user. registration system.

(Appendix 7)
an information reading device for reading information recorded on an information recording medium held by a user;
a destination floor registration unit that registers, in an elevator, the destination floor where the facility used by the user is located based on the information read by the information reading device;
A registration system comprising: a reception registration unit that performs reception registration of the user with respect to the facility used by the user in response to the reading of the information by the information reading device.

[Appendix 2]
(Appendix 2-1)
an input reception unit that receives input information generated according to an input operation performed by a user of the elevator;
a destination floor identifying unit that identifies a destination floor to be registered in the elevator based on the input information;
A reception information generation unit for generating reception information for registering that the input information has been received for the facility specified based on the input information among the facilities installed on any of the plurality of destination floors. and,
A registration system, comprising: a reception registration unit that performs reception registration of the user for the facility based on the reception information generated by the reception information generation unit.

(Appendix 2-2)
The registration system according to attachment 2-1, further comprising a destination floor registration unit that registers a destination floor for the elevator based on a result of identification by the destination floor identification unit.

(Appendix 2-3)
Further comprising an acceptance propriety determination unit for judging acceptance propriety at the facility,
The registration system according to appendix 2-2, wherein the destination floor registration unit does not register the destination floor when the acceptability determination unit determines no.

(Appendix 2-4)
According to any one of appendices 2-1 to 2-3, wherein the reception registration unit performs the reception registration of a plurality of users while maintaining the order in which the input information is received by the input reception unit. registration system.

(Appendix 2-5)
Any one of Appendices 2-1 to 2-4, further comprising an information reading device installed at the elevator hall and configured to generate the input information by reading information recorded on an information recording medium held by the user. 1. The registration system of 1.

(Appendix 2-6)
an information reading device for reading information recorded on an information recording medium held by a user;
a destination floor registration unit that registers, in an elevator, the destination floor where the facility used by the user is located based on the information read by the information reading device;
A registration system comprising: a reception registration unit that performs reception registration of the user with respect to the facility used by the user in response to the reading of the information by the information reading device.

[Example of realization by software]
The control blocks of the security system 1 (particularly, the input reception unit 11, the destination floor identification unit 12, and the reception information generation unit 13) may be realized by a logic circuit (hardware) formed on an integrated circuit (IC chip) or the like. Alternatively, it may be implemented by software.

The control blocks of the elevator control system 2 (in particular, the call registration section 21 and each section of the call registration section 21) may be realized by a logic circuit (hardware) formed in an integrated circuit (IC chip) or the like, or may be implemented by software. may be realized by

The control blocks of the reception system 101 (particularly, the acceptance propriety determination unit 31 and the reception registration unit 32) may be realized by a logic circuit (hardware) formed in an integrated circuit (IC chip) or the like, or realized by software. You may

In the latter case, each system (1, 2, 101) described above comprises a computer that executes instructions of a program, which is software that implements each function. This computer includes, for example, one or more processors, and a computer-readable recording medium storing the program. In the computer, the processor reads the program from the recording medium and executes it, thereby achieving the object of the present invention. As the processor, for example, a CPU (Central Processing Unit) can be used. As the recording medium, a "non-transitory tangible medium" such as R
In addition to OM (Read Only Memory), tapes, disks, cards, semiconductor memories, programmable logic circuits, etc. can be used. In addition, a RAM (Random Access Memory) for developing the above program may be further provided. Also, the program may be supplied to the computer via any transmission medium (communication network, broadcast wave, etc.) capable of transmitting the program. Note that one aspect of the present invention can also be implemented in the form of a data signal embedded in a carrier wave in which the program is embodied by electronic transmission.

The present invention is not limited to the above-described embodiments, but can be modified in various ways within the scope of the claims, and can be obtained by appropriately combining technical means disclosed in different embodiments. is also included in the technical scope of the present invention.

1 Security system (registration system)
2 Elevator control system (registration system)
3 Information reader 4 ID card (information recording medium)
11 Input reception unit 12 Destination floor identification unit 13 Reception information generation unit 14 Storage unit 21 Registration unit 31 Reception propriety determination unit 32 Reception registration unit 33 Storage unit 100 Registration system 101 Reception system 211 Destination floor registration unit 212 Hall registration unit 301 Operation panel 302 touch panel 303 information reading unit

Claims (5)

an information reading unit that reads information recorded on an information recording medium held by a user;
a destination floor registration unit for registering, in an elevator, the destination floor where the facility used by the user is located based on the information read by the information reading unit ;
a reception registration unit that performs reception registration of the user for the facility used by the user in response to the information reading unit reading the information ;
(1) A screen containing information indicating that the reception by the facility has been completed and information indicating the elevator number in which the user should board, or (2) Information indicating that use of the facility has been refused. A registration system comprising : a control unit that causes a display unit to display a screen containing : 2. The registration system according to claim 1, wherein the information indicating completion of reception by said facility includes a reception number numbered for said user and a reception number currently being processed at said facility. 3. The registration system according to claim 1 or 2, wherein the information indicating that use of said facility has been refused includes information explaining the reason why said facility cannot be used. Further comprising an acceptance propriety determination unit for judging acceptance propriety at the facility,
4. The registration system according to any one of claims 1 to 3, wherein said destination floor registration unit does not register said destination floor when said acceptability determination unit determines no. 5. The registration system according to any one of claims 1 to 4, wherein said reception registration section performs said reception registration of a plurality of users while maintaining the order in which said information reading section reads said information.

Images