Remote elevator control device and remote elevator control method

Abstract

We provide standardized elevator control services, create an environment that allows for efficient development and configuration tailored to specific sites, and improve elevator control and operational efficiency. [Solution] The elevator management device 100 includes a database, a processor, and a communication unit. The database is configured to store a first identification number corresponding to a first tier, a second identification number corresponding to a second tier, a third identification number corresponding to a third tier, and a fourth identification number corresponding to a fourth tier, which indicate a group including multiple buildings. The elevator management device 100 receives an authentication key and a control request to control elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c via the communication unit. The processor verifies whether the authentication key is an authentication key generated by the elevator management device 100 and transmits the control request to a terminal that controls the elevator.

Description

Technical Field

[0001] The present disclosure relates to a remote elevator control device and a remote elevator control method, and more particularly, to a remote elevator control device and a remote elevator control method for a specific area where external things of the system, for example, a robot participates in the elevator control environment.

Background Art

[0002] Things such as robots are utilized in an area where a plurality of buildings with elevators are gathered. For example, service robots in hotels and restaurants, delivery robots, etc. can provide services while moving through many buildings. In order for a robot to use the elevator in a building, the robot and the elevator must communicate. When developing protocols / programs for each building or building area to connect each robot and the elevator system, an inefficient environment may be formed. Also, when a robot directly controls an elevator, an inefficient environment may be formed when developing protocols / programs to connect the robot and the elevator one by one. The entire contents of the documents described in Korean Patent Publication No. 10-2022-0122961 and Korean Patent Publication No. 10-2022-0032857 are incorporated herein by reference.

[0003]

Summary of the Invention

Problems to be Solved by the Invention

[0004] Provide a standardized elevator control service and create an environment that can improve on-site development and setting efficiency. Thereby, the control and operation efficiency of the elevator can be improved.

Means for Solving the Problems

[0005] According to one aspect of the present disclosure, an elevator management system includes a database, a processor, and a communication unit. The database is configured to store a first identification number corresponding to a first level indicating a group of multiple buildings, a second identification number corresponding to a second level indicating one of the multiple buildings, a third identification number corresponding to a third level indicating multiple elevators contained in one building, and a fourth identification number corresponding to a fourth level indicating one of the multiple elevators. The elevator management system receives an authentication key and a control request to control an elevator via the communication unit. The processor is configured to verify whether the authentication key is an authentication key generated by the elevator management system, and, in response to the verification that the authentication key is an authentication key generated by the elevator management system, to transmit the control request to a terminal that controls the elevator.

[0006] In one embodiment, the elevator management device may be configured to receive at least one of the first to fourth identification numbers and an authentication request from an external device via the communication unit, and the processor may be configured to generate the authentication key and transmit it to the external device.

[0007] In one embodiment, the database may be configured to store the first identification number and related information in the first database table, the second identification number and related information in the second database table, the third identification number and related information in the third database table, and the fourth identification number and related information in the fourth database table.

[0008] In one embodiment, the second database table may be configured such that a row contains the first identification number and the second identification number, the third database table may contain the second identification number and the third identification number, and the fourth database table may contain the third identification number and the fourth identification number.

[0009] In one embodiment, the second database table may be configured to show which group the second tier belongs to, the third database table may be configured to show which building the third tier belongs to within the second tier, and the fourth database table may be configured to show which line the fourth tier belongs to within the third tier.

[0010] In one embodiment, the control request received by the elevator management device for controlling the elevator may include the first identification number, the second identification number, and the third identification number.

[0011] In one embodiment, the control request may include a request to control one of the plurality of elevators corresponding to the third layer.

[0012] In one embodiment, elevator information is received from a public data portal via the communication unit—the elevator information is in a different format from the first to fourth identification numbers—and the processor is configured to generate the first to fourth identification numbers corresponding to the elevator information based on the elevator information and store them in the database.

[0013] In one embodiment, the control request received by the elevator management device for controlling the elevator includes the first identification number, the second identification number, the third identification number, and the fourth identification number, and may include a request to control one elevator corresponding to the fourth floor.

[0014] In one aspect of this disclosure, the elevator management system includes a database, a processor, and a communication unit. The database is configured to store a first identification number corresponding to a first level indicating a group of multiple buildings, a second identification number corresponding to a second level indicating one of the multiple buildings, and a third identification number corresponding to a third level indicating multiple elevators contained within one building. The elevator management system receives an authentication key and a control request to control an elevator via the communication unit. The processor is configured to verify the authentication key and, upon verification that the authentication key is a valid authentication key, transmit the control request to a terminal device that controls the elevator.

[0015] An elevator control method for an elevator management device utilizing an Open API according to one aspect of the present disclosure, wherein the elevator management device includes a database, a processor, and a communication unit. The database is configured to store a first identification number corresponding to a first level indicating a group including multiple buildings, a second identification number corresponding to a second level indicating one of the multiple buildings, a third identification number corresponding to a third level indicating multiple elevators included in one building, and a fourth identification number corresponding to a fourth level indicating one of the multiple elevators. The elevator control method includes the steps of: providing first information by the processor so that an external device can select the group including the multiple buildings, one of the multiple buildings, the multiple elevators, and the one elevator; receiving at least a portion of the first information and an authentication request by the communication unit; generating an authentication key by the processor in response to receiving the authentication request and transmitting it to the external device; receiving the authentication key and a control request to control the elevator by the communication unit; and transmitting the control request to a terminal device to control the elevator in response to verifying that the authentication key is valid by the processor.

[0016] In one embodiment, the processor may further include the step of generating a first database table containing the first identification number and related information, a second database table containing the second identification number and related information, a third database table containing the third identification number and related information, and a fourth database table containing the fourth identification number and related information, and storing these in the database.

[0017] In one embodiment, the processor may further include the step of configuring the second database table to include the first identification number and the second identification number in a single row, the third database table to include the second identification number and the third identification number in a single row, and the fourth database table to include the third identification number and the fourth identification number in a single row.

[0018] In one embodiment, the control request for controlling the elevator may include at least a portion of the first information.

[0019] In one embodiment, the control request may include a request to control one of the plurality of elevators corresponding to the third layer.

[0020] In one embodiment, the communication unit may further include the steps of receiving elevator information from a public data portal (the elevator information being in a format different from the first to fourth identification numbers); and the processor may further include the steps of generating the first to fourth identification numbers corresponding to the elevator information based on the elevator information and storing them in the database.

[0021] In one embodiment, the control request for controlling the elevator may include the first identification number, the second identification number, the third identification number, and the fourth identification number, and may include a request for controlling one elevator corresponding to the fourth floor.

[0022] According to one aspect of the present disclosure, an elevator control method for a remote elevator control device including a processor, memory, and a communication unit includes the steps of: receiving first information by the communication unit indicating an elevator, a line including the elevator, a building including the line, and a group of buildings including the building; transmitting the first information and an authentication request by the communication unit to an elevator management device that controls the elevator; receiving an authentication key corresponding to the authentication request from the elevator management device by the communication unit; storing the authentication key in the memory; and transmitting the authentication key, at least a portion of the first information, and an elevator control request by the communication unit to the elevator management device.

[0023] In one embodiment, the memory may further include the step of storing the authentication key and a list of elevators that can be controlled by the authentication key.

[0024] In one embodiment, the process may further include storing in the memory a first identification number indicating the group of the plurality of buildings, a second identification number indicating the building containing the line, a third identification number indicating the line, and a fourth identification number indicating the elevator.

[0025] In one embodiment, the step of receiving a signal via the communication unit indicating that the elevator control request has been approved may be further included.

[0026] In one aspect of the present disclosure, the remote elevator control device includes a processor, a memory, and a communication unit. When the instruction words stored in the memory are executed by the processor, the processor receives, via the communication unit, first information indicating an elevator, a line in which the elevator is included, a building in which the line is included, and a group of a plurality of buildings including the building; transmits, via the communication unit, the first information and an authentication request to an elevator management device that controls the elevator; receives, via the communication unit, an authentication key corresponding to the authentication request from the elevator management device, stores the authentication key in the memory, and is configured to transmit, via the communication unit, at least a part of the authentication key and the first information and an elevator control request to the elevator management device.

[0027] In one embodiment, the memory may be configured to store the authentication key and an elevator list that can be controlled by the authentication key.

[0028] In one embodiment, the memory may be configured to store in the memory a first identification number indicating the group of the plurality of buildings, a second identification number indicating the building in which the line is included, a third identification number indicating the line, and a fourth identification number indicating the elevator.

[0029] In one embodiment, when the instruction words are executed, the processor may further include receiving, via the communication unit, a signal indicating that the elevator control request has been approved.

Advantages of the Invention

[0030] The states and control functions of different elevator systems are abstracted, and the system can provide a standardized protocol, such as maintaining a standardized database for each elevator, and provide compatibility for robots using the platform of this model.

Brief Description of the Drawings

[0031] [Figure 1] This is a block diagram of an elevator control environment according to one embodiment of the present disclosure. [Figure 2] This is a block diagram showing an example of a lower hierarchy of the elevator area 400 according to one embodiment of the present disclosure. [Figure 3] This is a block diagram of an elevator management system according to one embodiment of the present disclosure. [Figure 4-11] This is an illustrative diagram of a data table stored in a database according to one embodiment of the present disclosure. [Figure 12] This is a flowchart of an elevator control method according to one embodiment of the present disclosure. [Modes for carrying out the invention]

[0032] The embodiments of this disclosure will be described in detail below, with reference to the attached drawings, so that they can be easily implemented by a person with ordinary skill in the art to which this disclosure pertains. However, this disclosure can be embodied in a variety of different forms and is not limited to the embodiments described herein.

[0033] Furthermore, in order to clearly illustrate this disclosure, parts unrelated to the description have been omitted from the drawings, and similar parts throughout the specification have been denoted by similar reference numerals.

[0034] Throughout the specification, when a part is described as "containing" a component, this means, unless otherwise stated, that it may contain other components rather than excluding them.

[0035] The technologies described herein are not intended to limit to any particular embodiment and should be understood to include a variety of modifications, equivalents, and / or substitutions of the embodiments described herein.

[0036] The expression “configured (or set up)” as used in this disclosure may be replaced, depending on the context, with, for example, “suitable for,” “capable of,” “designed to,” “modified to,” “made to,” or “capable of.” The term “configured (or set up)” does not necessarily mean “specifically designed” in terms of hardware. Instead, in some contexts, the expression “device configured to” may mean that the device is “capable” of doing something together with other devices or components.

[0037] Prior art described herein is incorporated herein by reference in its entirety, and it can be understood that the contents of the prior art are applicable to the parts described herein by a person with general art knowledge.

[0038] Figure 1 is a block diagram of an elevator control environment 1000 according to one embodiment of the present disclosure.

[0039] Referring to Figure 1, the elevator control environment 1000 includes an elevator management device 100, an object management device 200, an object 300, and an elevator area 400. For convenience of explanation, the object 300 will be assumed to be a robot and the object management device 200 to be a robot management device. However, it should be understood that the scope of this disclosure is not limited to the control of robots and elevators. For example, an object 300 may be an external device / system not belonging to the elevator area 400 that can be remotely connected to the elevator management device 100 for elevator control. For example, an object 300 may be a building management system, an access control system, a passenger identification device (e.g., facial recognition, iris recognition, fingerprint recognition), a mobile device, a drone, etc., and may include all devices for remotely controlling devices inside a building from an external location. One object management device 200 can be connected to and control multiple objects 300.

[0040] In Figure 1, for convenience, the object management device 200 and the object 300 are shown separately. However, it can be understood that when the methods performed through the object 300 and the methods performed by the object management device 200 are carried out by a single management entity, they can be described as being performed by a single device. That is, it can be understood that the object 300 can be directly connected to the central management device 100 to perform elevator control, or connected to the central management device 100 through the object management device 200 to perform elevator control. The steps performed by the object 300 may also be performed by the object management device 200, and the steps performed by the object management device 200 may also be performed by the object 300. It can also be understood that the object management device 200 and the object 300 can be considered as a single device.

[0041] In one embodiment, the elevator management device 100 may be provided in the form of a cloud platform. The elevator management device 100 may be provided in a location physically separated from the elevator area 400. The elevator management device 100 may include at least one computing device, which may be embodied as a server. The elevator management device 100 may be embodied as a cloud server (system).

[0042] The elevator management device 100 is configured to authenticate the robot 300 and to have the authority to control elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c within the elevator area 400. The elevator management device 100 is configured to check the status of elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c and to control them. The elevator management device 100 is configured to receive control requests for elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c from the robot 300, verify the control requests received from the robot 300, and transmit them to the elevator area 400.

[0043] The elevator management device 100 is configured to provide a development environment for external users to develop applications using the resources of the elevator management device 100.

[0044] The elevator management device 100 may include an Open Application Programming Interface (OpenAPI) and a Developer Site that provides information about the OpenAPI. The administrator of the robot management device 200 can use the Developer Site to develop applications based on the OpenAPI provided by the elevator management device 100.

[0045] The robot management device 200 may be a device that controls the movement of the robot 300 and the provision of services within the building by the robot 300. The robot management device 200 may include at least one computing device, which may be implemented as a server. The robot management device 200 may be implemented as a cloud server (system).

[0046] The robot management device 200 can connect with the robot 300 using the open API of the elevator management device 100 and monitor elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c. The robot management device 200 can connect with the robot 300 using the open API of the elevator management device 100 and control elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c. For example, the robot management device 200 can develop an elevator control application using information from the open API, register the elevator control application with the elevator management device 100, and obtain authentication. For this purpose, the elevator management device 100 can abstract into a standardized web service and provide services to the robot management device 200.

[0047] The robot management device 200 can control elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c through an elevator control application. The robot management device 200 is configured to control robot 300 and is configured to control elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c through the elevator management device 100.

[0048] The robot management device 200 can connect to the database 120 (see Figure 3) of the elevator management device 100 and receive information recorded in the database tables stored in the database 130.

[0049] Robot 300 may be a service robot used to provide services within a building. Robot 300 can provide services to users within a building at a predetermined location (a specific floor) through autonomous navigation. Although not shown in the drawings, robot 300 may include an autonomous mobile robot that can be embodied by prior art and may be equipped with a communication unit for communicating with other devices (such as other robots or robot management device 200). Robot 300 may include a device that can determine the current location of robot 300 (e.g., GPS). Robot 300 may be configured to select an elevator that it wishes to control based on its location. For example, robot 300 can search for an elevator that can reach a target location and move to board the found elevator. Robot 300 can search for an elevator to be controlled using an address (e.g., building name, floor number, etc., such as an apartment building). Robot 300 can search for an elevator to be controlled using an address and a first to fourth identification number. The first to fourth identification numbers will be explained later.

[0050] The robot 300 can receive information about elevators within a specific area from the robot management device 200 before arriving at or before arriving at a specific area within the site, for example, the elevator area 400. The robot 300 can also transmit information about elevators within a specific area to the robot management device 200.

[0051] The robot 300 is configured to control elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c within the elevator area 400 via the robot management device 200. In one embodiment, the robot 300 can determine which elevator to control from among elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c via position recognition or the robot management device 200. In one embodiment, the robot management device 200 receives control authority from the elevator management device 100. The control authority received by the robot management device 200 concerns which elevators it can control. The control authority can be received in the form of an authentication key.

[0052] In one embodiment, the robot 300 controlling the elevator may mean calling a specific elevator, boarding the elevator, and then moving to the destination floor.

[0053] The elevator region 400 may refer to the region in which elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c are grouped together.

[0054] In one embodiment, the elevator area 400 may be a specific area that has been selected in advance. For example, the elevator area 400 may be an apartment complex, a collection of selected buildings, etc. Assuming that the elevator area 400 is an apartment complex, the elevator area 400 includes a first selected apartment group 410 (e.g., the first complex) and a second selected apartment group 420 (e.g., the second complex). The first complex 410 includes buildings 101 412 and 102 414. The second complex 420 includes buildings 201 422 and 202 424. Multiple elevators 412a, 412b, and 412c may be installed in building 101 412, and multiple elevators (e.g., elevators 1 to 3) 414a, 414b, and 414c may be installed in building 102 414. Multiple elevators 422a, 422b, and 422c may be installed in Building 201 422, and multiple elevators 424a, 424b, and 424c may be installed in Building 202 424. It should be understood that the number of elevators, the number of buildings, the housing complex, the building names, etc., are illustrative examples. That is, the elevator area 400 may include buildings in which elevators are installed, sets of buildings in which elevators are installed, sets of buildings belonging to a particular area, etc. The elevator area 400 may include multiple groups of elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c grouped into many floors, or it may include any one of these groups of elevators grouped into many floors.

[0055] In one embodiment, at least one of the four levels (for example, the first level (apartment complex 400), the second level (apartment complex 410, apartment complex 420), the third level (buildings 412 to 424), and the fourth level (each elevator 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, 424c) is an elevator It may include elevator interlocking terminals. For example, each of the third floors (buildings 412 to 424 in building 101) may include an elevator interlocking terminal. Control of each elevator 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, 424c may be performed through the elevator interlocking terminal.

[0056] In one embodiment, multiple elevators may be managed by a single system. The multiple elevators may belong to the first floor 400, the second floor 410, 420, or the third floor 412 to 424. A system that manages multiple elevators by a single system can be called a control panel. In contrast, a system that controls each of the elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c individually can be called a standalone system.

[0057] Figure 1 shows that the elevator area 400 consists of four levels (for example, the first level (apartment complex 400), the second level (apartment complex 410, apartment complex 420), the third level (buildings 412 to 424), and the fourth level (each elevator 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, 424c), but the number of levels may be variable depending on the settings. For example, the elevator area 400 can have at least three or more lower levels.

[0058] Figure 2 is a block diagram showing an example of a lower hierarchy of the elevator area 400 according to one embodiment of the present disclosure. The hierarchy shown in Figure 2 is a different example from the hierarchy shown in Figure 1.

[0059] Referring to Figure 2, the second level 2410 may correspond to an apartment or building. For example, the second level 2410 may correspond to a specific building in the apartment area 400, specifically an apartment wing (e.g., wing 101). That is, the second level 410 may be omitted in Figure 1. The third level 2412 may correspond to an elevator call line for a specific building (e.g., line 101-102 for wing 101 2410). The fourth levels 2412a and 2412b may correspond to actual individual elevators (e.g., elevators 1 and 2 of the call lines (101-102, 2412) for wing 101 2410).

[0060] Thus, the elevator area 400 may be divided and recognized as having multiple depths / hierarchies. It can be understood that the hierarchy of the elevator area 400 is not limited to those illustrated in Figures 1 and 2, but can be varied in many ways.

[0061] In one embodiment, one floor may be equipped with a server (or system) for elevator control. The server / system equipped on the floor can receive control signals from the elevator management device 100 and control the elevators accordingly. For example, buildings 101 412 to 202 424 may each be equipped with a server / system for controlling multiple elevators. Alternatively, the elevator management device 100 can also control each elevator immediately.

[0062] Referring again to Figure 1, each of the elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c has an Id for identification. Each Id may contain all the codes corresponding to each floor. In one embodiment, the Id may be configured to indicate which floor the elevator belongs to. For example, the Id may include a code indicating whether the elevator belongs to elevator area 400, a code indicating whether it belongs to the first housing complex 410 or the second housing complex 420, a code indicating whether it belongs to one of buildings 101 412 to 202 424, and a code indicating which of elevators 1 to 3 it is. Thus, each elevator may be assigned an Id containing a code indicating each floor of each area (for example, each of the four floors in Figure 1). The elevator management device 100 can assign an ID to each elevator, and manage and store these IDs.

[0063] In one embodiment, each level may have an identification ID. An ID corresponding to the first level 400, an ID corresponding to the second level (first housing complex 410, second housing complex 420), an ID corresponding to the third level (buildings 101 to 202, 424), and an ID corresponding to the fourth level (each elevator 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, 424c) may be assigned. By combining the IDs of each level, an ID for a specific individual elevator can be generated.

[0064] Referring again to Figure 2, each of the elevators 2412a and 2412b has an identification ID. Each ID may contain all the codes corresponding to each floor. Each elevator may be assigned an ID containing codes that indicate each floor in each area (taking Figure 2 as an example, each of the second to fourth floors). The elevator management device 100 can assign, manage, and store an ID corresponding to each elevator. In one embodiment, each floor may have an identification ID. By combining the IDs of each floor, an ID for a specific individual elevator can be generated.

[0065] Information for each level may be composed of database tables and stored and managed in the elevator management device 100. Figures 4 to 11 are illustrative diagrams of tables stored in the database of this disclosure. Figures 4 to 11 are illustrative diagrams of database tables corresponding to the first to fourth levels, and in one embodiment, the first level may correspond to a site (e.g., apartment complex, factory, hotel, etc.), the second level to a building, the third level to a line, and the fourth level to an elevator.

[0066] In one embodiment, siteId, buildingId, lineId, and elId shown in Figures 4 to 11 may correspond to the first to fourth identification numbers.

[0067] Referring to Figures 4 and 5, site information can include site name, address, region name, sub-region name, location (e.g., latitude, longitude), registrant, registration date and time, etc. Site information can also include a site ID (e.g., siteId) corresponding to each site. Referring to Figure 4, site information can include site name, address, region name, sub-region name, location (e.g., latitude, longitude, etc.), registrant, registration date and time, etc., and may be arranged in columns of a database table as shown in Figure 4. Referring to Figure 5, a database table storing site information can include at least one of site ID, address, site name, latitude, longitude, registrant, and registration date and time in a single row. That is, in one embodiment, at least one item on a column in Figure 4 may be an item on a row in Figure 5, as shown in Figure 5. The blanks in the database in Figure 5 may be filled with a form pre-selected by the user.

[0068] Referring to Figures 6 and 7, building information can include the building name, registrant, registration date and time, etc. Building information can also include a building ID (buildingId) corresponding to each building. Referring to Figure 6, the columns of the database table in Figure 6 include the building ID, the site ID to which the building ID belongs, the building name, the registrant, the registration date and time, etc. Referring to Figure 7, the database table that stores building information can include at least one of the following in each row: building ID, site ID to which the building ID belongs, building name, registrant, and registration date and time. That is, in one embodiment, at least one item on the column in Figure 6 may be an item on the row in Figure 7, as shown in Figure 7. The database table that stores building information can include a reference value of the site (location) to which the table belongs. For example, in Figure 7, building IDs B000002 to B000007 refer to site ID S000002. That is, it can be seen that buildings corresponding to B000002 to B000007 belong to the location S000002. Therefore, when selecting any one site in database 130 (for example, site ID S000002), it is possible to retrieve the buildings (or the corresponding building IDs) belonging to that site. The blanks in the database tables in Figures 6 and 7 may be filled with a form pre-selected by the user.

[0069] Referring to Figures 8 and 9, line information can include line name, highest floor of the line, lowest floor of the line, presence or absence of destination floor, presence or absence of group management, monitoring panel, registrant, registration date and time, project number, terminal number, presence or absence of robot boarding, and classification of monitoring panel terminal. Line information can include a line ID (lineId) corresponding to each line. Referring to Figure 9, a database table storing line information can include at least one of the following in each row: line ID, building ID to which the line ID belongs, line name, highest floor of the line, lowest floor of the line, presence or absence of destination floor, presence or absence of group management, monitoring panel, registrant, registration date and time, project number, terminal number, presence or absence of robot boarding, and classification of monitoring panel terminal. That is, in one embodiment, at least one item on the column in Figure 6 may be an item on the row in Figure 9, as shown in Figure 9. A database table storing line information can include a reference value for the building to which the table belongs. For example, in Figure 9, lines Id L000002 and L000003 refer to building Id B000002, and lines Id L000004 and L000005 refer to building Id B000003. In other words, lines corresponding to L000002 through L000003 belong to building B000002, and lines corresponding to L000004 through L000005 belong to building B000003. Therefore, when selecting any one building (for example, site Id B000002) in database 130, it is possible to retrieve the lines (or line Ids corresponding to the lines) belonging to it.

[0070] In one embodiment, the project number may be a unique identifier assigned to the elevator. The project number may indicate the elevator construction site. Alternatively, the project number may correspond to a contract (e.g., an elevator contract).

[0071] Referring to Figures 10 and 11, elevator information can include elevator name, elevator number, terminal number, registrant, registration date and time, project number, agent ID, etc. The elevator number is the elevator number registered with the National Elevator Information Center. The agent ID may be used in an open API system (i.e., an elevator management device) to identify each field program (e.g., an application installed in a robot management device) and to check and manage its operating status. That is, in one embodiment, at least one item on the column in Figure 10 may be an item on the row in Figure 11, as shown in Figure 11.

[0072] Elevator information can include an elevator ID (elId) corresponding to each elevator. Although not all are shown in Figure 11, a database table that stores elevator information can contain at least one of the following in each row: elevator ID, line ID to which the elevator ID belongs, elevator name, elevator number, agent ID, project number, registrant, registration date and time, and terminal number. Referring to Figure 11, a database table that stores elevator information can also include a reference value to the line to which the table belongs. For example, in Figure 11, elevator IDs E000004 and E000005 refer to line ID L000004. That is, it can be seen that elevators corresponding to E000004 and E000005 belong to line L000004. Therefore, when selecting one of the lines (for example, site ID L000004) in database 130, it is possible to retrieve the elevators (or the elevator IDs corresponding to the elevators) belonging to that line.

[0073] The robot management device 200 may have an ID for identifying the robot management device. The robot 300 may have an ID for robot identification.

[0074] In one embodiment, the robot management device 200 can control elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c through an elevator control application. Although Figure 1 shows one robot management device 200, the robot management device 200 may consist of multiple different entities. Each entity may have a different elevator control application. The elevator management device 100 can receive information about the elevator control application from the robot management device 200 and authenticate the elevator control application.

[0075] In one embodiment, the robot 300 or robot management device 200 can transmit authentication information to the elevator management device 100 and request registration. The robot 300 or robot management device 200 can transmit authentication information to the elevator management device 100 through an elevator control application installed on the robot 300 or robot management device 200.

[0076] The authentication information may include at least one of the following: (identification) information of the robot 300, robot management device 200, or elevator control application (e.g., an ID corresponding to the robot 300, robot management device 200, or elevator control application), contract information including contracting parties, and site information (first-tier ID (e.g., siteId), second-tier ID (e.g., buildingId), third-tier ID (e.g., lineId), and fourth-tier ID (e.g., elId)). The elevator management device 100 or the administrator of the elevator management device 100 can authenticate / register the robot 300 or robot management device 200 based on the contract information. The contract information may already be stored in the memory 120 or database 130 of the elevator management device 100.

[0077] For example, the elevator management device 100 can determine whether the robot management device 200 or the robot 300 has the authority to control a site requested by contract or the like, and can receive the determination result from an external source (e.g., another database or administrator). The elevator management device 100 may store information on whether the robot management device 200 or the robot 300 has the authority to control a site requested by contract or the like. In this case, the elevator management device 100 can query the authority granted to the robot management device 200 or the robot 300 and accept or reject the authentication request from the robot management device 200 based on this.

[0078] In one embodiment, the administrator of the elevator management device 100 can verify whether the robot management device 200 or the robot 300 has the authority to control the site as requested by contract or the like, and can accept or reject the authentication request from the robot management device 200 or the robot 300.

[0079] Authenticating / registering the robot 300 or the robot management device 200 may include authenticating and registering the elevator control application installed on the robot 300 or the robot management device 200. Authentication / registration of the robot 300 or the robot management device 200 allows the robot 300 to have control authority over elevators at a designated site.

[0080] Once the elevator management device 100 authenticates and registers an elevator control application, the robot 300 or robot control device 200 can control an already registered elevator simply by installing the authenticated elevator control application on the robot 300 or robot control device 200. In other words, the robot 300 or robot control device 200 may request separate authentication from the elevator management device 100 and may not register itself.

[0081] In one embodiment, the authentication and registration of the robot 300 or robot control device 200 by the elevator management device 100 may include the ability for the administrator of an external device (e.g., robot control device 200, robot 300) to register an interlocking program (e.g., control application) that intends to interact with the elevator management device 100. If there are multiple interlocking programs, an authentication key can be issued for each interlocking program. If there are multiple external devices, an authentication key can be issued for each interlocking program installed on each external device. This allows each interlocking program to have its own unique authority over the external device on which it is installed. In this case, it is possible to set individual authority for each external device. In one embodiment, in order to set individual authority for each application or for each external device, the elevator management device 100 may assign an agent ID to the interlocking program when generating the authentication key.

[0082] In one embodiment, the elevator management device 100 can provide an authentication key to the robot management device 200 or robot 300 after authenticating the elevator control application. The elevator management device 100 can transmit the authentication key to the robot 300 or robot management device 200 and register the authentication key with the elevator management device 100. The elevator management device 100 can assign and store an authentication key for each robot 300, robot management device 200, or elevator control application installed on the robot 300 or robot management device 200. The authentication key may be matched with the ID of the robot 300, robot management device 200, or elevator control application and stored in the elevator management device 100.

[0083] The robot management device 200 can control elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c using an authentication key.

[0084] In one embodiment, the robot management device 200 can control elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c through an elevator control application. The elevator management device 100 can receive control requests, site information (e.g., siteId, buildingId, lineId, elId, etc.), and authentication keys from the robot management device 200 or the robot 300. The elevator management device 100 can pre-store information related to the elevator area 400 (e.g., a database, database table, as shown in Figures 4 to 11). The robot management device 200 or the robot 300 can send the authentication key assigned to the robot 300, the robot management device 200, or the elevator control application each time it sends an API requesting necessary control or information. The elevator management device 100 can determine whether the authentication key is valid and, in response to determining whether the authentication key is valid, can authorize the control or request received from the robot management device 200 or the robot 300. That is, the elevator management device 100 can transmit the control request received from the robot management device 200 or the robot 300 to the relevant elevator.

[0085] In one embodiment, an authentication key may be assigned to the application. The robot 300 or robot management device 200 can transmit the authentication key assigned to the application and the control request to the elevator management device 100. In this case, the robot 300 or robot management device 200 may not be assigned an authentication key.

[0086] In one embodiment, the elevator management device 100 sends a control request received from the robot management device 200 or the robot 300 to the elevator interlocking terminal, and the elevator interlocking terminal that receives the control request can control the elevator according to the control request.

[0087] In one embodiment, a control request from the robot management device 200 or the robot 300 may include a request to call a specific elevator. Alternatively, a control request from the robot management device 200 or the robot 300 may include a request to call an elevator belonging to a specific line. In this case, the elevator management device can call the most suitable elevator from among several elevators belonging to the specific line. Since elevator calling is well known to those ordinary skill in the art, a detailed explanation thereof will be omitted.

[0088] In one embodiment, multiple requests may be transmitted sequentially to the elevator management device 100. In this case, a unique identifier may be generated for each request. Each unique identifier can be generated by the elevator management device 100, the robot management device 200, or the robot 300. The unique identifier for each request is also called the transaction ID.

[0089] Figure 3 is a block diagram of an elevator management device 100 according to one embodiment of the present disclosure.

[0090] The elevator management device 100 may include a processor 110, a memory 120, a database 130, and a communication unit 140. In one embodiment, the processor 110 may be an ASIC (application specific integrated circuits), a DSP (digital signal processor), a DSPD (digital signal processing device), a PLD (programmable logic device), an FPGA (field programmable gate array), a controller, a microcontroller, a microprocessor, or any other form of processor or controller for performing functions.

[0091] The memory 120 may be configured to store information for the operation of the elevator management device 100. The memory 120 can store numerous application programs or applications driven by the elevator management device 100, each piece of data readable by the processor, and each instruction word. For example, the memory 120 can include a variety of storage spaces such as an HDD (Hard Disk Drive), SSD (SolId State Disk), SDD (Silicon Disk Drive), ROM, RAM, EPROM, flash drive, hard drive, and cloud using a network.

[0092] The database 130 is configured to store information related to the elevator area 400. The database 130 can include a variety of storage spaces such as HDDs, SSDs, ROMs, RAMs, EPROMs, flash drives, hard drives, and cloud storage using networks. Although the memory 120 and the database 130 have been described in their respective configurations, it can be understood that the memory 120 and the database 130 can be considered as a single configuration.

[0093] In one embodiment, database 130 may be configured to store the database tables shown in Figures 4 to 11. Database 130 can store identification information for individual elevators 412a, 412b, 412c, 414a, 414b, 414c, 422a, 422b, 422c, 424a, 424b, and 424c. Database 130 can store elevator information managed or produced by the administrator of the elevator management device 100 (e.g., the first administrator). For example, the first administrator can supply elevators to a location where a new building is being constructed and register the supplied elevator information in database 130 or another database of the first administrator (not shown). Database 130 and the other database of the first administrator may be synchronized, and elevator information stored in the other database of the first administrator may be updated in database 130. If elevators supplied by another administrator (e.g., a second administrator) rather than the first administrator are provided at the site where a new building is to be constructed, information about the elevators supplied by the second administrator may be stored in the database of the national public platform (e.g., a third administrator). The elevator information stored in the third administrator's database may be updated in database 130.

[0094] In one embodiment, the database 130 can receive elevator information from a national public platform (e.g., a public data portal) using an open API. The elevator information retrieved from the data received from the public data portal may include an elevator-specific number. The elevator information retrieved from the data received from the public data portal may differ from or not include the format of already stored data (e.g., siteId, buildingId, lineId, elId). Therefore, the elevator management device 100 may be configured to generate siteId, buildingId, lineId, and elId from the data received from the public data portal and store them in the database 130. The elevator-specific number includes an elevator number issued by a public institution (e.g., an elevator safety management corporation). The elevator management device 100 may be configured to generate siteId, buildingId, lineId, and elId from the data using information such as address and building name, based on the elevator-specific number issued by the public institution, and store them in the database 130. For example, the elevator management device 100 may be configured to use the elevator's unique number as a basic identifier, generate and match siteId, buildingId, lineId, and elId, and store them in the database 130. In this case, the elevator management device 100 may be configured to generate a unique identifier and store it in the database 130. That is, the database 130 may store the unique identifier matched with siteId, buildingId, lineId, and elId. The unique identifier may also be stored matched with the elevator's unique number.

[0095] In one embodiment, there may be cases where there is no elevator-specific identification number issued by the government or public institutions. For example, in countries other than South Korea, there may be no government-approved identifier such as an elevator-specific identification number. Alternatively, the format of the elevator-specific identification number issued in a country other than South Korea may differ from the format of the elevator-specific identification number pre-selected in the elevator management device 100 or the format of the elevator-specific identification number issued in South Korea. In this case, the elevator management device 100 may independently generate an arbitrary identifier that is substantially identical to the format of the elevator-specific identification number pre-selected in the elevator management device 100 or the format of the elevator-specific identification number issued in South Korea, and use this as a basic identifier. Subsequently, the elevator management device 100 may be configured to use the independently generated arbitrary identifier as a basic identifier to generate and match siteId, buildingId, lineId, and elId and store them in the database 130.

[0096] To this end, in one embodiment, when the elevator management device 100 reads elevator information from a database other than database 130 and updates database 130, it can perform the following steps: confirm whether the elevator information stored in the other database has an elevator unique number in the format of an elevator unique number pre-selected by the elevator management device 100 or an elevator unique number in the format of an elevator unique number issued in Korea; and, in response to determining that the elevator information stored in the other database does not have an elevator unique number in the format of an elevator unique number pre-selected by the elevator management device 100 or an elevator unique number in the format of an elevator unique number issued in Korea, it can perform the following steps: generate an arbitrary identifier.

[0097] The communication unit 140 is configured to communicate with external devices via a network. The network communication method can utilize, but is not limited to, networks constructed using GSM (Global System for Mobile communication), CDMA (Code Division Multi Access), HSDPA (High Speed ​​Downlink Packet Access), HSUPA (High Speed ​​Uplink Packet Access), LTE (Long Term Evolution), LTE-A (Long Term Evolution-Advanced), etc., WLAN (Wireless LAN), Wi-Fi (Wireless-Fidelity), Wi-Fi (Wireless Fidelity)-Direct, DLNA (Digital Living Network Alliance), WiBro (Wireless Broadband), and WiMAX (World Interoperability for Microwave Access). It can also include all transmission method standards that will be developed in the future. Furthermore, the network communication method can include any method that allows data to be exchanged via wired or wireless connections.

[0098] The processor 110 and memory 120 can be combined to embody an artificial intelligence model. In this disclosure, an artificial intelligence model may mean a model that learns a learning model including an artificial neural network (ANN) through a large amount of training data, optimizes the parameters within the ANN, and uses the learned learning model to participate in the operation of a dialogue system (not shown). In one embodiment, an artificial intelligence module (not shown) may be learned through MRC (Machine Reading Comprehension). In one embodiment, the artificial neural network model used in the artificial intelligence module may be at least one of the following, or a combination thereof: Convolutional Neural Network (CNN), Deep Neural Network (DNN), Recurrent Neural Network (RNN), Restricted Boltzmann Machine (RBM), Deep Belief Network (DBN), Bidirectional Recurrent Deep Neural Network (BRDNN), Variational Auto Encoder (VAE), or Deep Q-Networks. However, it is not limited to the examples described above.

[0099] Figure 12 is a flowchart of an elevator control method according to one embodiment of the present disclosure.

[0100] The elevator management system may be provided in the form of a cloud platform. The elevator management system may be provided in a location physically separated from the elevators. The elevator management system may include at least one computing device, which may be implemented as a server. The elevator management system may be implemented as a cloud server (system). The elevator management system is configured to provide a development environment for external users to develop applications using the resources of the elevator management system 100. The elevator management system may include an open API and a Developer Site that provides information on the open API.

[0101] The object may include devices that can be remotely connected to an elevator management system for elevator control. For example, the object may include a building management system, access control system, passenger identification devices (e.g., facial recognition, iris recognition, fingerprint recognition), mobile devices, object management servers, drones, robots, and all other devices for remotely controlling devices inside a building from an external location.

[0102] Referring to Figure 12, the elevator management device can generate a database (block S1210). The generated database may be stored in the elevator management device. The database may be configured to store a first identification number corresponding to a first level indicating a group including multiple buildings, a second identification number corresponding to a second level indicating one of the multiple buildings, a third identification number corresponding to a third level indicating multiple elevators contained in one of the buildings, and a fourth identification number corresponding to a fourth level indicating one of the multiple elevators. Database 130 may be generated by receiving elevator information from a national public platform (e.g., a public data portal) in an open API manner. The database may be updated periodically.

[0103] The person in charge of the equipment can develop an interlocking program based on the open API provided by the elevator management system using the developer site (block S1215). Alternatively, they can install an already developed interlocking program on the equipment.

[0104] The elevator management device can transmit first information to an object that indicates an elevator, a line containing the elevator, a building containing the line, and a group of multiple buildings including the building (block S1220). The first information may include information that is matched with first to fourth identification numbers.

[0105] The object can transmit to the elevator management device the information corresponding to the elevator it wishes to control from the first information, along with an authentication request (block S1225).

[0106] The elevator control device can transmit an authentication key to an object (block S1230). The elevator control device can receive a command indicating that the authentication request has been confirmed, generate an authentication key in response, and transmit the authentication key to the object. The elevator control device can store the authentication key. The elevator control device can store the authentication key in association with each interlocking program. The elevator control device can store the authentication key in association with elevators that can be controlled via the authentication key. The elevator control device can store the first to fourth identification numbers in association with the authentication key. The object can store the authentication key and the elevator information corresponding to the authentication key.

[0107] The object can transmit an authentication key and an elevator control request to the elevator management device (block S1235). The object can transmit at least a portion of the first information, an authentication key, and an elevator control request to the elevator management device. The object can transmit at least a portion of the first to fourth identification numbers, an authentication key, and an elevator control request to the elevator management device. The elevator control request may also be an elevator call.

[0108] The elevator management device can verify the received authentication key (block S1240). The elevator management device can verify the authentication key using the received authentication key and already stored information (for example, already stored authentication keys, elevator information stored in association with the authentication key, etc.).

[0109] The elevator management device can transmit an elevator control request to the elevator control terminal in response to the authentication key being verified (block S1245). The elevator control terminal, upon receiving the elevator control request, controls the elevator. The elevator management device can transmit to the object that the elevator control request it made has been approved (block S1250).

[0110] The methods relating to this disclosure can be embodied as processor-readable code on a processor-readable recording medium installed in a server, system, equipment, computer, integrated control device, etc., used by an entity. Processor-readable recording mediums include all types of recording devices that store data readable by a processor. Examples of processor-readable recording mediums include ROM, RAM, CD-ROM, magnetic tape, floppy disks, optical data storage devices, and also include those embodied in the form of carrier waves, such as transmission over the Internet. Furthermore, processor-readable recording mediums may be distributed across networked computer systems, and processor-readable code may be stored and executed in a distributed manner.

[0111] The apparatus and methods described above may be embodied in hardware components, software components, and / or combinations of hardware and software components. For example, the apparatus and components described in each embodiment may be embodied using one or more general-purpose or special-purpose computers, such as a processor, controller, ALU (arithmetic logic unit), digital signal processor, microcomputer, FPA (field programmable array), PLU (programmable logic unit), microprocessor, or any other device capable of executing and responding to instructions. The processing device can perform an operating system (OS) and one or more software applications performed on the OS. The processing device can also access, store, manipulate, process, and generate data in response to software execution. Although it has sometimes been described that a single processing device is used for convenience of understanding, a person with ordinary skill in the art will understand that a processing device may include multiple processing elements and / or multiple types of processing elements. For example, a processing device may include multiple processors or one processor and one controller. Furthermore, other processing configurations, such as parallel processors, are also possible.

[0112] Software may include computer programs, code, instructions, or a combination of one or more of these, which can configure a processing unit to operate as desired, or independently or collectively issue instructions to the processing unit. Software and / or data may be permanently or temporarily embodied in any type of machine, component, physical device, virtual device, computer storage medium or device, or transmitted signal wave, for interpretation by the processing unit or for providing instructions or data to the processing unit. Software may be distributed across a network of computer systems and stored or executed in a distributed manner. Software and data may be stored on one or more computer-readable recording media.

[0113] Furthermore, each embodiment of the present disclosure may be implemented in a distributed computing environment in which any task is performed by each remote processing unit connected via a communication network. In a distributed computing environment, program modules may reside in all local and remote memory storage devices.

[0114] As described above, each embodiment has been illustrated with limited drawings, but a person with ordinary skill in the relevant art can apply a variety of technical modifications and variations based on the above. For example, even if the described techniques are performed in a different order than described, and / or if the components of the described systems, structures, devices, circuits, etc. are combined or assembled in a different manner than described, or substituted or replaced by other components or equivalents, suitable results can still be achieved.

[0115] Therefore, other embodiments, other embodiments, and claims equivalent to those described below also fall under the scope of the claims.

Claims

1. An elevator management device comprising a database, a processor, and a communication unit, The database is configured to store a first identification number corresponding to a first level indicating a group of multiple buildings, a second identification number corresponding to a second level indicating one of the multiple buildings, a third identification number corresponding to a third level indicating multiple elevators contained within one building, and a fourth identification number corresponding to a fourth level indicating one of the multiple elevators. The elevator management device receives an authentication key and a control request to control the elevator via the communication unit. An elevator management device configured such that the processor verifies whether the authentication key is an authentication key generated by the elevator management device, and, in response to the verification that the authentication key is an authentication key generated by the elevator management device, transmits the control request to a terminal device that controls the elevator.

2. The elevator management device receives at least one of the first to fourth identification numbers and an authentication request from an external device via the communication unit. The elevator management device according to claim 1, wherein the processor is configured to generate the authentication key and transmit it to the external device.

3. The elevator management device according to claim 1, wherein the database is configured to store the first identification number and related information in a first database table, the second identification number and related information in a second database table, the third identification number and related information in a third database table, and the fourth identification number and related information in a fourth database table.

4. The second database table includes the first identification number and the second identification number in a single row, The third database table includes the second identification number and the third identification number in a single row, The elevator management device according to claim 3, wherein the fourth database table is configured to include the third identification number and the fourth identification number in a single row.

5. The second database table is configured to indicate which of the groups the second hierarchy belongs to, The third database table is configured to show which building in the second layer the third layer belongs to, The elevator management device according to claim 4, wherein the fourth database table is configured to indicate which line of the third hierarchy the fourth hierarchy belongs to.

6. The control request received by the elevator management device for controlling the elevator is: The elevator management device according to claim 1, including the first identification number, the second identification number, and the third identification number.

7. The elevator management device according to claim 6, wherein the control request includes a request to control one of the plurality of elevators corresponding to the third floor.

8. The communication unit receives elevator information from the public data portal via the aforementioned communication unit—the elevator information is in a different format from the first to fourth identification numbers. The elevator management device according to claim 1, wherein the processor is configured to generate the first to fourth identification numbers corresponding to the elevator information based on the elevator information and store them in the database.

9. The control request received by the elevator management device for controlling the elevator is: The elevator management device according to claim 1, comprising a request to control one elevator corresponding to the fourth floor, including the first identification number, the second identification number, the third identification number, and the fourth identification number.

10. An elevator management device comprising a database, a processor, and a communication unit, The database is configured to store a first identification number corresponding to a first level indicating a group including multiple buildings, a second identification number corresponding to a second level indicating one of the multiple buildings, and a third identification number corresponding to a third level indicating multiple elevators included in one of the buildings. The elevator management device receives an authentication key and a control request to control the elevator via the communication unit. An elevator management device configured such that the processor verifies the authentication key and, in response to verifying that the authentication key is a valid authentication key, transmits the control request to a terminal device that controls the elevator.

11. An elevator control method for an elevator management system that utilizes an open API, The elevator management device comprises a database, a processor, and a communication unit. The database is configured to store a first identification number corresponding to a first level indicating a group of multiple buildings, a second identification number corresponding to a second level indicating one of the multiple buildings, a third identification number corresponding to a third level indicating multiple elevators contained within one building, and a fourth identification number corresponding to a fourth level indicating one of the multiple elevators. The processor provides first information so that an external device can select a group including the plurality of buildings, one building from the plurality of buildings, the plurality of elevators, and the one elevator; The communication unit receives at least a portion of the first information and an authentication request; The processor generates an authentication key in response to receiving the authentication request and transmits it to the external device; The communication unit receives an authentication key and a control request to control the elevator; and The processor includes the step of verifying that the authentication key is valid and transmitting the control request to a terminal that controls the elevator; Elevator control method.

12. The elevator control method according to claim 11, further comprising the step of generating a first database table containing the first identification number and related information, a second database table containing the second identification number and related information, a third database table containing the third identification number and related information, and a fourth database table containing the fourth identification number and related information using the processor, and storing these in the database.

13. The aforementioned processor, The second database table includes the first identification number and the second identification number in a single row, The third database table includes the second identification number and the third identification number in a single row, The elevator control method according to claim 12, further comprising the step of configuring the fourth database table so that each row contains the third identification number and the fourth identification number.

14. The control request that controls the elevator is, The elevator control method according to claim 11, comprising at least a portion of the first information.

15. The elevator control method according to claim 14, wherein the control request includes a request to control one of the plurality of elevators corresponding to the third floor.

16. The communication unit receives elevator information from the public data portal—the elevator information is in a different format from the first to fourth identification numbers; and The elevator control method according to claim 11, further comprising the step of: the processor generating first to fourth identification numbers corresponding to the elevator information based on the elevator information, and storing them in the database.

17. The control request that controls the elevator is, The elevator control method according to claim 11, comprising a request to control one elevator corresponding to the fourth floor, including the first identification number, the second identification number, the third identification number, and the fourth identification number.

Images