Method and system for construction time use of at least one elevator car of elevator system

Abstract

According to one aspect, a method and system for construction time usage of at least one elevator car of an elevator system is provided. A hauling call may be generated for at least one transportable entity, the hauling call defining a departure floor and a destination floor. Extended door times may be set for departure and destination floors. The hauling call may be allocated to the elevator car, and other calls may be prevented from being allocated to the elevator car simultaneously with the hauling call between the departure floor and the destination floor.

Description

Background Art

[0001] Elevators may be used during the building construction phase, and the traffic profile of the elevators may change every day. During the construction phase, elevators are mainly used for construction material and equipment transportation. In construction time use (CTU), elevators may be used very heavily and waiting time may increase. In CTU, the amount of construction materials and equipment transported with the elevator may be large, and loading and unloading the transported construction materials and equipment may take some time.

[0002] Therefore, it is important to effectively use the construction time of the elevator. Summary of the invention

[0003] According to a first aspect, a method for construction time usage of at least one elevator car of an elevator system is provided. The method comprises: generating a haul call for at least one transportable entity, the haul call defining a departure floor and a destination floor; setting extended door times for the departure floor and the destination floor; assigning the haul call to an elevator car; and preventing other calls from being assigned to the elevator car simultaneously with the haul call between the departure floor and the destination floor.

[0004] In an implementation form of the first aspect, the method further comprises: obtaining priority information related to the at least one transportable entity associated with the towing call, each transportable entity being associated with a priority; and determining the priority of the towing call according to the priority of the at least one transportable entity.

[0005] In an implementation of the first aspect, the method further includes: obtaining scheduling information about the at least one transportable entity associated with the haul call; and generating the haul call based on the scheduling information.

[0006] In an implementation form of the first aspect, the method further includes: obtaining first identification information related to the at least one transportable entity associated with the towing call, the first identification information including an identifier associated with each of the at least one transportable entity; obtaining second identification information related to the transportable entity loaded into the elevator car, the second identification information including an identifier associated with each of the at least one transportable entity loaded into the elevator car; comparing the first identification information with the second identification information; when the first identification information matches the second identification information, determining that the loading of the elevator car in the departure floor is completed; and when it is determined that the loading of the elevator car in the departure floor is completed, issuing a command to close the door at the departure floor.

[0007] In an implementation form of the first aspect, the method further includes: obtaining third identification information related to the transportable entity unloaded from the elevator car, the third identification information including an identifier associated with each of the at least one transportable entity unloaded from the elevator car; comparing the second identification information with the third identification information; determining that the unloading of the elevator car in the destination floor is complete when the second identification information matches the third identification information; and when it is determined that the unloading of the elevator car in the destination floor is complete, issuing a command to close the door at the destination floor.

[0008] In an implementation form of the first aspect, the method further comprises obtaining information that the elevator car is empty at the destination floor; and issuing a command to close the door at the destination floor in response to obtaining the information that the elevator car is empty at the destination floor.

[0009] In an implementation form of the first aspect, the method further comprises: obtaining information associated with an extended door time for a departure floor and / or a destination floor from a user device; and setting an extended door time for the departure floor and / or the destination floor based on the information.

[0010] In an implementation form of the first aspect, the method further comprises: obtaining a door closing command associated with the departure floor or the destination floor from a user device; and issuing a command to close the door at the departure floor or the destination floor in response to the door closing command.

[0011] According to a second aspect, a system for use of construction time of at least one elevator car of an elevator system is provided. The system comprises: means for generating a haul call for at least one transportable entity, the haul call defining a departure floor and a destination floor; means for setting extended door times for the departure floor and the destination floor; means for assigning the haul call to an elevator car; and means for preventing other calls from being assigned to the elevator car simultaneously with the haul call between the departure floor and the destination floor.

[0012] In an implementation form of the second aspect, the system further comprises: means for obtaining priority information relating to the at least one transportable entity of the towing call, each transportable entity being associated with a priority; and means for determining the priority of the towing call based on the priority of the at least one transportable entity.

[0013] In an implementation of the second aspect, the system further comprises means for obtaining dispatch information regarding the at least one transportable entity associated with the haul call, and means for generating the haul call based on the dispatch information.

[0014] In one implementation form of the second aspect, the system further comprises: a device for obtaining first identification information regarding the at least one transportable entity associated with the haul call, the first identification information comprising an identifier associated with each of the at least one transportable entity; a device for obtaining second identification information related to the transportable entity loaded into the elevator car, the second identification information comprising an identifier associated with each of the at least one transportable entity loaded into the elevator car; a device for comparing the first identification information with the second identification information; a device for determining that loading of the elevator car in the departure floor is complete when the first identification information matches the second identification information; and a device for issuing a command to close the door at the departure floor when it is determined that loading of the elevator car in the departure floor is complete.

[0015] In an implementation form of the second aspect, the system also includes: a device for obtaining third identification information related to the transportable entity unloaded from the elevator car, the third identification information including an identifier associated with each of the at least one transportable entity unloaded from the elevator car; a device for comparing the second identification information with the third identification information; a device for determining that unloading of the elevator car in the destination floor is completed when the second identification information matches the third identification information; and a device for issuing a command to close the door at the destination floor when it is determined that unloading of the elevator car in the destination floor is completed.

[0016] In an implementation form of the second aspect, the system further comprises means for obtaining information that the elevator car is empty at the destination floor; and means for issuing a command to close the door at the destination floor in response to obtaining information that the elevator car is empty at the destination floor.

[0017] In an implementation form of the second aspect, the system further comprises means for obtaining information associated with an extended door time for a departure floor and / or a destination floor from a user device; and means for setting an extended door time for the departure floor and / or the destination floor based on the information.

[0018] In an implementation of the second aspect, the system also includes: a device for obtaining a door closing command associated with the departure floor or the destination floor from a user device; and a device for issuing a command to close the door at the departure floor or the destination floor in response to the door closing command.

[0019] According to a third aspect, there is provided an elevator system comprising the system of the second aspect.

[0020] According to a fourth aspect, there is provided a computer program comprising instructions stored thereon for performing the method of the first aspect.

[0021] According to a fifth aspect, there is provided a computer readable medium comprising a computer program including instructions stored thereon for performing the method of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings, which are included to provide a further understanding of the invention and constitute a part of this specification, illustrate embodiments of the invention and together with the description help to explain the principles of the invention.

[0023] In the figure:

[0024] Figure 1 A flow chart of a method according to an example embodiment is shown.

[0025] Figure 2 A block diagram of an apparatus according to an example embodiment is shown.

[0026] Figure 3 A system according to an example embodiment is shown. DETAILED DESCRIPTION

[0027] Various examples and embodiments discussed herein disclose a solution in which a device, such as a field controller for construction field use (CTU), may be arranged in an elevator system.

[0028] Figure 1 A flow chart of a method for construction time usage of at least one elevator car of an elevator system according to an exemplary embodiment is shown. The method can be implemented by an apparatus, such as a site controller. In another exemplary embodiment, the method can be implemented so that one or more steps can be implemented by a site controller and one or more steps can be implemented by at least one other entity (e.g., an elevator controller or an elevator group controller).

[0029] At 100, a haul call may be generated for at least one transportable entity, the haul call defining a departure floor and a destination floor. A haul call may refer to a call or load call during which various construction materials and tools may be transported between a departure floor and a destination floor. A transportable entity may refer to, for example, at least one of a material, a tool, a batch of materials, a person, etc. In addition, one or more attributes may be associated with the transportable entity and may be known in advance, such as weight, size, priority, a time window when the transportable entity is needed at a particular location, a destination floor, an identifier, etc. The haul call may be generated, for example, by a site controller discussed in more detail below.

[0030] At 102, extended door times may be set for the departure floor and the destination floor. Since the haul call is configured to transport at least one transportable entity, loading and unloading the at least one transportable entity may take some time. Therefore, extended door times may be set for the departure floor and the destination floor, such as to a default value or to a value determined based on the at least one transportable entity, manually or automatically, such as when the haul call is generated. The extended door times may be set, such as by a site controller discussed in more detail below.

[0031] At 104, a haul call may be assigned to an elevator car. For example, the haul call assignment may be accomplished by an elevator controller or an elevator group controller. In an exemplary embodiment, the scene controller may send the haul call to the elevator controller or the elevator group controller.

[0032] At 106, other calls may be prevented from being assigned to the elevator car simultaneously with the haul call between the departure floor and the destination floor. The solution discussed above may enable a haul mode that provides an optimal configuration for logistical purposes. Furthermore, no doors need to be blocked with physical objects. The blocking of other calls may be achieved, for example, by the elevator controller or the elevator group controller.

[0033] Figure 2 A block diagram of an apparatus 200 according to an example embodiment is shown. The apparatus 200 may be, for example, a computer or a server computer, and it may be configured to implement the functions performed by a field controller. In an example embodiment, the apparatus 200 may be integrated as part of an elevator controller, an elevator group controller, or an elevator drive, as a separate circuit board / module or as integrated hardware. In another example embodiment, the apparatus 200 may be implemented, for example, using an additional software module in an elevator controller, an elevator group controller, or an elevator drive. In other words, the apparatus 200 may refer to, for example, an elevator controller, an elevator group controller, or an elevator drive configured to implement the features discussed. The apparatus may be configured to implement Figure 1 and Figure 3 One or more of the features and / or steps discussed in the description.

[0034] The apparatus 200 includes one or more processors 202, and one or more memories 204 including computer program code. The apparatus 200 may also include at least one software and / or hardware communication interface 208 for communicating with one or more other entities. Although the apparatus 200 is depicted as including only one processor 202, the apparatus 200 may include more than one processor. In an example embodiment, the memory 204 is capable of storing instructions, such as an operating system and / or various applications.

[0035] In addition, the processor 202 is capable of executing the stored instructions. In an example embodiment, the processor 202 may be embodied as a multi-core processor, a single-core processor, or a combination of one or more multi-core processors and one or more single-core processors. For example, the processor 202 may be embodied as one or more of various processing devices, such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing circuit with or without an accompanying DSP, or various other processing devices including integrated circuits (such as, for example, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), microcontroller units (MCUs), hardware accelerators, dedicated computer chips, etc.). In an example embodiment, the processor 202 may be configured to perform hard-coded functions. In an example embodiment, the processor 202 is implemented as an executor of software instructions, wherein the instructions may specifically configure the processor 202 to perform the algorithms and / or operations described herein when the instructions are executed.

[0036] The memory 204 may be embodied as one or more volatile memory devices, one or more non-volatile memory devices, and / or a combination of one or more volatile memory devices and non-volatile memory devices. For example, the memory 204 may be embodied as a semiconductor memory (such as a mask ROM, a PROM (programmable ROM), an EPROM (erasable PROM), a flash ROM, a RAM (random access memory), etc.).

[0037] In an embodiment, at least one memory 204 may store program instructions 206 that, when executed by at least one processor 202, cause the apparatus 200 to perform the functions of the various embodiments discussed herein. Furthermore, in an embodiment, at least one of the processor 202 and the memory 204 may constitute means for implementing the functions discussed.

[0038] Figure 3 A system 300 is shown according to an example embodiment. Figure 3 The system 300 described in the specification may be applied, for example, during construction time use (CTU). In a CTU, one or more elevators may be used to transport various materials and / or tools and personnel from a departure floor to a destination floor in a timely manner. The system 300 may include a device for generating a haul call for at least one transportable entity, the haul call defining a departure floor and a destination floor, a device for setting extended door times for the departure floor and the destination floor, a device for assigning the haul call to an elevator car, and a device for preventing other calls from being assigned to the elevator car simultaneously with the haul call between the departure floor and the destination floor. One or more entities of the system 300 (e.g., the scene controller 200, the elevator controller 304, and / or the elevator group controller) may be used to implement the previously described Figure 1The features / steps discussed and the features / steps discussed herein, and thus may constitute means for implementing the functions discussed.

[0039] The system includes a field controller 200 (or field hub) that can be connected to an elevator controller 304 via a field application programming interface (API) 302. In another example embodiment, the functionality of the field controller 200 can be implemented by the elevator controller 304, so the API 302 and a separate field controller 200 are not required. In an example embodiment, the field controller 200 and the elevator controller 304 can be arranged in an elevator shaft 306. The field controller 200 can generally refer to an entity that is configured to enable access or connection to various different system elements. In an exemplary embodiment, the field controller 200 can be integrated as part of an elevator controller, an elevator group controller, or an elevator drive, as a separate circuit board / module or as integrated hardware. In another example embodiment, the field controller 200 can be implemented, for example, using an additional software module in an elevator controller, an elevator group controller, or an elevator drive. In other words, the field controller 200 can refer to, for example, an elevator controller, an elevator group controller, or an elevator drive that is configured to implement the features discussed.

[0040] The site controller 200 may include a first communication interface configured to provide a connection to at least one local construction site data source 308A, 308B, 308C associated with the construction site 310, wherein the at least one local construction site data source is configured to track personnel and / or material flow during construction time use. The connection to the at least one local construction site data source 308A, 308B, 308C may be achieved, for example, using at least one of the following technologies: a Wi-Fi connection, a physical Ethernet connection, or an IoT mesh connection, depending on the location. For example, a Wi-Fi connection may be used when high data throughput is required. The IoT mesh connection may be used for small, inexpensive and / or battery-powered devices that do not send much data, for example.

[0041] Typically, at least one local construction site data source 308A, 308B, 308C may refer to an external sensor, an automated system, and / or a data source that provides information about which tools, materials, and people are to be or are currently being transported in an elevator. Different field data may be arranged in a single data source (e.g., a database) or in multiple data sources. Tools, materials, and people may be tracked and / or identified using any appropriate tracking and / or identification system, such as Bluetooth, radio frequency identification (RFID) using RFID tags, wireless positioning, and the like. Local construction site data sources 308A, 308B, 308C, and / or backend systems 316 may include identification information associated with each transportable entity. The identification information may be stored in, for example, a remotely readable device or tag, such as a radio frequency identification (RFID) tag, which is attached to or otherwise associated with a transportable entity. The construction site may then include one or more readers that are capable of remotely reading the identification information when the corresponding transportable entity is loaded into / unloaded from the elevator. The reader may be arranged at an appropriate location in the elevator or outside the elevator.

[0042] In an exemplary embodiment, at least one local job site data source 308A, 308B, 308C may include one or more of the following:

[0043] -Material and waste tracking system

[0044] -Personnel positioning and identification system

[0045] -Asset location and usage management system

[0046] - Site condition monitoring system.

[0047] The material and waste tracking system can provide information, for example, where materials and / or tools are located and how much waste has accumulated during the construction phase. The personnel location and identification system can provide information, for example, about the location of personnel and the identity of the personnel at the location. The asset location and usage management system can provide information, for example, about one or more assets that can be used in the construction site and their associated locations. Assets can refer to, for example, materials, tools, employees, etc. The asset location and usage management system can also track the usage of one or more assets, for example, when, where and / or how long an asset is used during the construction phase, where and / or how long a specific employee works at the construction site during the construction phase, etc. This can then provide management information, for example, to the backend system 316. The site condition monitoring system can provide information, for example, about the status associated with the construction site. The status can refer to, for example, the readiness of the construction site, safety and health issues (e.g., the number of reported accidents, the number of accident-free days), temperature, humidity, particulate matter levels, etc.

[0048] The site controller may also include a second communication interface, such as an application programming interface (API) 312, which is configured to provide a connection to at least one client application 314 and at least one backend system 316, the client application 314 being configured to access data provided by the site controller, and the backend system 316 being configured to provide construction project data associated with the construction site. The second communication interface 312 enables the site controller 200 to connect to an external system, and enables an external system or client to connect to the site controller 200. For example, an elevator call may be assigned from a mobile device of a person working on site. Additionally or alternatively, elevator calls may be automatically scheduled and assigned, such as by a cloud-based management entity (e.g., backend system 316). In general, one or more backend systems 316 may refer to automated systems and data sources that provide information about the cost and / or priority of different materials, tools, and personnel to be transferred using at least one elevator.

[0049] In an exemplary embodiment, the local construction site data source 308A, 308B, 308B and / or the backend system 316 may store information associated with one or more transportable entities. The transportable entity may refer to, for example, at least one of a material, a tool, a batch of materials, a person, etc. In addition, one or more attributes may be associated with the transportable entity and may be known in advance, such as weight, size, priority, time window when the transportable entity is needed at a specific location, destination floor, identifier, etc. In other words, the local construction site data source 308A, 308B, 308B and / or the backend system 316 may include any information that characterizes the transportable entity in some way. Then, based on the information stored in the field data source 308A, 308B, 308B and / or the backend system 316, the field controller 200 may be able to optimize the use of the elevator during the CTU.

[0050] In an example embodiment, the client application 314 may be executed in a device (eg, a user's mobile device). The client application 314 may be used, for example, to make elevator calls, track materials, tools, and / or personnel.

[0051] In an example embodiment, backend system 316 may refer to one or more external project planning systems from which data indicating where items should go may be obtained. Project planning systems may include, for example, cloud-based construction project planning tools that provide APIs to read data into other systems.

[0052] In an example embodiment, the backend system 316 may refer to one or more logistics systems to obtain identification information of different materials, for example, a cloud-based system for tracking material delivery and supply lines. The logistics system may provide an API to access logistics information that can be used by the site controller 200 for decision making.

[0053] In an example embodiment, the backend system 316 may reference one or more tool rental systems to obtain information about what kinds of tools are being used, how they are being used, and for what work tasks they are being used during a CTU. A tool rental system may refer to a cloud-based system that provides tool rental information to an API that the field controller 200 may use to make decisions.

[0054] In an exemplary embodiment, the field data sources 308A, 308B, 308C and / or the backend system 316 may store priority information about at least one transportable entity associated with the haul call. Different transportable entities may have different priorities. When generating a haul call, the field controller 200 may obtain priority information from the field data sources 308A, 308B, 308C and / or the backend system 316 and determine the priority of the haul call based on the priority of the at least one transportable entity. For example, the priority of the haul call may have the same priority as the highest priority of the at least one transportable entity associated with the haul call. In other exemplary embodiments, the priority of the haul call may be calculated differently.

[0055] In an example embodiment, backend system 316 may store scheduling information about at least one transportable entity associated with a haul call. The scheduling information may set, for example, a specific time or time window when / during a transportable entity is needed at a specific destination floor. Site controller 200 may then generate a haul call based on the scheduling information. This may enable a solution in which the transport timing of various transportable entities may be optimized. Additionally, if the schedule of the transportable entities changes during construction time, the changed schedule may be updated into backend system 316, and site controller 200 may be able to take this into account.

[0056] In an example embodiment, the field data sources 308A, 308B, 308C may include identification information associated with each transportable entity. In another example embodiment, the identification information may be stored in the backend system 316. The identification information may be stored in, for example, a remotely readable device or tag, such as a radio frequency identification (RFID) tag, which is attached to or otherwise associated with the transportable entity. Then, the construction site may include one or more readers that can read the identification information remotely when the corresponding transportable entity is loaded / unloaded from the elevator. The reader may be arranged in an appropriate position in the elevator or outside the elevator. The field controller 200 may first obtain identification information about at least one transportable entity associated with the haul call. In an exemplary embodiment, the field controller 200 may store identification information about at least one transportable entity associated with the haul call in a memory and obtain the information from the memory. In another example embodiment, the field controller 200 may obtain information, for example, from the field data sources 308A, 308B, 308C or the backend system 316. When the at least one transportable entity is subsequently loaded into the elevator car, the scene controller 200 may be configured to receive read identification information associated with the transportable entity loaded into the elevator car. Then, by comparing the identification information about the at least one transportable entity associated with the haul call with the identification information obtained from the reader using the scene controller 200, when the identification information about the at least one transportable entity associated with the haul call matches the identification information obtained from the reader, it can be determined that the loading of the elevator car in the departure floor is complete. In other words, it can be determined that all required transportable entities have been loaded into the elevator car. In an example embodiment, the scene controller 200 may obtain the identification information directly from the reader when the elevator car is loaded. In another example embodiment, the scene controller 200 may obtain the identification information from the scene data source 308A, 308B, 308C or the backend system 316. In response to this determination, the scene controller 200 may issue a command to close the door at the departure floor. This enables the extended door time at the departure floor to be automatically determined without having to manually set it to an approximate value. This also ensures that all transportable entities associated with the haul call will be transported to the destination floor.

[0057] In an exemplary embodiment, the scene controller 200 may similarly obtain identification information related to the transportable entity unloaded from the elevator car, the identification information including an identifier associated with each of the at least one transportable entity unloaded from the elevator car. In an exemplary embodiment, the scene controller 200 may obtain the identification information directly from the reader when the elevator car is unloaded. In another exemplary embodiment, the scene controller 200 may obtain the identification information from the scene data source 308A, 308B, 308C or the backend system 316. Then, by comparing the identification information obtained from the reader when the elevator car is loaded with the identification information obtained from the reader when the elevator car is unloaded, the unloading of the elevator car in the destination floor may be determined to be complete when the identification information obtained from the reader when the elevator car is loaded matches the identification information obtained from the reader when the elevator car is unloaded. In an exemplary embodiment, the scene controller 200 may store in a memory the identification information previously obtained by the reader when the elevator car is loaded, and obtain the information from the memory. In another example embodiment, the scene controller 200 may obtain identification information obtained from a reader earlier when the elevator car was loaded, for example, from the scene data source 308A, 308B, 308C or the backend system 316. In response to this determination, the scene controller 200 may issue a command to close the door at the destination floor. This enables the extended door time at the destination floor to be automatically determined without having to manually set it to an approximate value.

[0058] In an exemplary embodiment, the scene controller 200 may obtain information that the elevator car is empty at the destination floor, and in response to obtaining the information that the elevator car is empty at the destination floor, issue a command to close the door at the destination floor. Thus, when it is determined that the elevator car is empty, for example based on information from a weighing device, this can be used as an indication that all transportable entities have been unloaded from the elevator car and the door can be closed. This enables another solution for automatically determining the extended door time at the destination floor without having to manually set it to an approximate value.

[0059] In an exemplary embodiment, the scene controller 200 may obtain information associated with the extended door time of the departure floor and / or the destination floor, for example from a user device or other entity. This information may determine a specific value for the extended door time. The scene controller 200 may then set the extended door time for the departure floor and / or the destination floor based on this information. This enables a solution that does not require any additional identification system to identify the transportable entities loaded into / unloaded from the elevator car. The information associated with the extended door time of the departure floor and / or the destination floor may be determined, for example, based on the amount of the transportable entity and its attributes (e.g., size, weight, etc.).

[0060] In an exemplary embodiment, the scene controller 200 may obtain a door closing command associated with a departure floor or a destination floor from a user device and issue a command to close the door at the departure floor or the destination floor in response to the door closing command. This implements a solution in which no approximate value for the extended door time needs to be determined and set. Instead, when the loading / unloading of the transportable entity has been completed, the person loading the transportable entity into the elevator car may issue a door closing command using his / her mobile device.

[0061] In any of the example embodiments discussed above, a haul call can be manually generated using a device (e.g., a computer or a mobile device used by a user). The user can set the departure floor and the destination floor for the haul call. In addition, the user can manually select at least one transportable entity for the haul call, for example, from a list of available transportable entities. Alternatively, at least one transportable entity for the haul call can be automatically generated by a backend system entity, and the user only approves the automatic generation. The user can also set the priority of the haul call. Alternatively, the priority can be set by the backend system, or can be automatically set based on the priority of at least one transportable entity. In an example embodiment, when a haul call is being generated, if it is determined that using stairs will provide a faster solution for transporting at least one transportable entity, the user can be advised to use stairs. In another example embodiment, the haul call can be automatically generated locally or generated by a backend system connected to the scene controller 200.

[0062] At least one of the examples and embodiments disclosed above may implement a solution for optimizing the transportation of transportable entities during construction time usage.

[0063] The example embodiments may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The example embodiments may store information related to the various methods described herein. The information may be stored in one or more memories, such as a hard disk, an optical disk, a magneto-optical disk, a RAM, etc. One or more databases may store information for implementing the example embodiments. The database may be organized using a data structure (e.g., a record, a table, an array, a field, a graph, a tree, a list, etc.) included in one or more memories or storage devices listed herein. The method described with respect to the example embodiments may include an appropriate data structure for storing data collected and / or generated by the method of the device and subsystem of the example embodiments in one or more databases.

[0064] The components of the example embodiments may include a computer-readable medium or memory for storing instructions programmed according to the teachings and for storing data structures, tables, records and / or other data described herein. In an example embodiment, application logic, software or instruction sets are maintained on any of a variety of conventional computer-readable media. In the context of this document, a "computer-readable medium" may be any medium or component that can contain, store, communicate, propagate or transmit instructions for use by an instruction execution system, device or equipment (such as a computer) or used in combination with an instruction execution system, device or equipment (such as a computer). A computer-readable medium may include a computer-readable storage medium, which may be any medium or device that can contain or store instructions for use by an instruction execution system, device or equipment (such as a computer) or used in combination with it. A computer-readable medium may include any suitable medium that participates in providing instructions to a processor for execution. Such a medium may take many forms, including but not limited to non-volatile media, volatile media, transmission media, etc.

[0065] Although the basic novel features applied to the preferred embodiments thereof have been shown and described and pointed out, it should be understood that various omissions, substitutions and changes in the form and details of the described apparatus and methods may be made by those skilled in the art without departing from the spirit of the present disclosure. For example, it is expressly intended that all combinations of those elements and / or method steps that perform substantially the same function in substantially the same manner to achieve the same results are within the scope of the present disclosure. In addition, it should be recognized that the structures and / or elements and / or method steps shown and / or described in conjunction with any disclosed form or embodiment can be incorporated into any other disclosed or described or suggested form or embodiment as a general matter of design choice. In addition, the device plus function clause is intended to cover the structures described herein as performing the functions described, and not only covers structural equivalents, but also covers equivalent structures.

[0066] Applicants hereby disclose in isolation each individual feature described herein and any combination of two or more such features, as long as such feature or combination can be performed based on the present specification as a whole according to the common knowledge of those skilled in the art, regardless of whether such feature or combination of features solves any problem disclosed herein, and without limiting the scope of the claims. Applicants point out that the disclosed aspects / embodiments may consist of any such individual feature or combination of features. In view of the foregoing description, it will be apparent to those skilled in the art that various modifications may be made within the scope of the present disclosure.

Claims

1. A method for use of construction time of at least one elevator car of an elevator system, the method comprising: generating a haul call for at least one transportable entity, the haul call defining a departure floor and a destination floor; setting extended door times for the departure floor and the destination floor; assigning the haul call to an elevator car; and Other calls are prevented from being assigned to the elevator car simultaneously with the haulage call between the departure floor and the destination floor.

2. The method according to claim 1, further comprising: obtaining priority information regarding the at least one transportable entity associated with the haul call, each transportable entity being associated with a priority level; and A priority of the haul call is determined based on a priority of the at least one transportable entity.

3. The method according to any one of claims 1 to 2, further comprising: obtaining dispatch information regarding the at least one transportable entity associated with the haul call; and The haul call is generated based on the dispatch information.

4. The method according to any one of claims 1 to 3, further comprising: obtaining first identification information about the at least one transportable entity associated with the haul call, the first identification information comprising an identifier associated with each of the at least one transportable entity; obtaining second identification information related to transportable entities loaded into the elevator car, the second identification information comprising an identifier associated with each of the at least one transportable entity loaded into the elevator car; comparing the first identification information with the second identification information; When the first identification information matches the second identification information, determining that loading of the elevator car in the departure floor is complete; and When it is determined that loading of the elevator car in the departure floor is complete, a command is issued to close the door at the departure floor.

5. The method according to claim 4, further comprising: obtaining third identification information related to transportable entities unloaded from the elevator car, the third identification information comprising an identifier associated with each of the at least one transportable entity unloaded from the elevator car; comparing the second identification information with the third identification information; When the second identification information matches the third identification information, determining that unloading of the elevator car at the destination floor is complete; and When it is determined that unloading of the elevator car in the destination floor is complete, a command is issued to close the door at the destination floor.

6. The method according to any one of claims 1 to 4, further comprising: obtaining information that the elevator car is empty at the destination floor; and In response to obtaining information that the elevator car is empty at the destination floor, a command is issued to close the doors at the destination floor.

7. The method according to any one of claims 1 to 3, further comprising: obtaining, from a user device, information associated with the extended door time for the departure floor and / or the destination floor; and The extended door time is set for the departure floor and / or the destination floor based on the information.

8. The method according to any one of claims 1 to 3, further comprising: obtaining, from a user device, a door closing command associated with the departure floor or the destination floor; and A command to close the door at the departure floor or the destination floor is issued in response to the door closing command.

9. A system for use of construction time of at least one elevator car of an elevator system, the system comprising: means for generating a haul call for at least one transportable entity, the haul call defining a departure floor and a destination floor; means for setting extended door times for said departure floor and said destination floor; means for assigning said haul call to an elevator car; and Means for preventing other calls from being assigned to the elevator car simultaneously with the haulage call between the departure floor and the destination floor.

10. The system according to claim 9, further comprising: means for obtaining priority information regarding the at least one transportable entity associated with the haul call, each transportable entity being associated with a priority level; and Means for determining a priority of the haul call based on a priority of the at least one transportable entity.

11. The system according to any one of claims 9-10, further comprising: means for obtaining dispatch information regarding the at least one transportable entity associated with the haul call; and Means for generating the haul call based on the dispatch information.

12. The system according to any one of claims 9 to 11, further comprising: means for obtaining first identification information regarding the at least one transportable entity associated with the haul call, the first identification information comprising an identifier associated with each of the at least one transportable entity; means for obtaining second identification information associated with a transportable entity loaded into the elevator car, the second identification information comprising an identifier associated with each of the at least one transportable entity loaded into the elevator car; means for comparing the first identification information with the second identification information; means for determining that loading of the elevator car at the departure floor is complete when the first identification information matches the second identification information; and Means for issuing a command to close the doors at the departure floor when loading of the elevator car in the departure floor is determined to be complete.

13. The system of claim 12, further comprising: means for obtaining third identification information associated with transportable entities unloaded from the elevator car, the third identification information comprising an identifier associated with each of the at least one transportable entity unloaded from the elevator car; means for comparing the second identification information with the third identification information; means for determining completion of unloading of the elevator car at the destination floor when the second identification information matches the third identification information; and means for issuing a command to close the door at the destination floor when it is determined that unloading of the elevator car in the destination floor is complete.

14. The system according to any one of claims 9 to 12, further comprising: means for obtaining information that the elevator car is empty at the destination floor; and Means for issuing a command to close the doors at the destination floor in response to obtaining information that the elevator car is empty at the destination floor.

15. The system according to any one of claims 9 to 11, further comprising: means for obtaining from a user device information associated with said extended door time for said departure floor and / or said destination floor; and Means for setting the extended door time for the departure floor and / or the destination floor based on the information.

16. The system according to any one of claims 9 to 11, further comprising: means for obtaining from a user device a door closing command associated with said departure floor or said destination floor; and Means for issuing a command to close the doors at the departure floor or the destination floor in response to the door closing command.

17. An elevator system comprising the system according to any one of claims 9-16.

18. A computer program comprising instructions stored thereon for performing the method according to any one of claims 1 to 8.

19. A computer readable medium comprising a computer program including instructions stored thereon for performing the method according to any one of claims 1 to 8.

Images