CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY
[001] The present application does not claim priority from any patent application.
TECHNICAL FIELD
[002] The present disclosure in general relates to the field of elevators. More particularly, the present invention relates to an elevator for bridging two or more buildings.
BACKGROUND
[003] Nowadays a lot of official buildings are placed in the same vicinity and are situated close to each other. However, there is no direct way to connect floors of one building with another neighboring building such that users can travel from one building to a desired floor of the neighboring building. For example, if a person wants to reach from fourteenth floor in one building to the same floor in another neighboring building, he/she has to first come down to ground floor, go to the neighboring building and then again take an elevator from ground floor to fourteenth floor of the neighboring building.
[004] This results in both time and energy wastage since the elevator has to move twice first to ground floor and then again to the desired floor in the neighboring building. There are no means by which a user in the one building can directly travel and reach desired floor of another building. Some of the references available in the art teach about connecting two buildings through a bridge. However, these bridges are stationary and connect only a single floor of two adjacent buildings.
SUMMARY
[005] This summary is provided to introduce aspects related to an elevator and a system for operating the elevator bridging two buildings and the aspects are further described below in the detailed description. This summary is not intended to identify essential features of the claimed subject matter nor is it intended for use in determining or limiting the scope of the claimed subject matter.
[006] In one embodiment, an elevator for bridging two buildings is disclosed. The elevator comprises a hollow elongated body having a first gate and a second gate located at either ends of the hollow elongated body. The first gate is adapted to align with a
3
source floor of a set of source floors, corresponding to a first building, and the second gate is adapted to align with a destination floor of a set of destination floors, corresponding to a second building. In one embodiment, the source floor and the destination floor are coplanar. Further, the elevator comprises an elevator unit attached to the hollow elongated body. The elevator unit is configured to move the hollow elongated body in at least one of an upward direction or a downward direction. The elevator further comprises at least one travelator placed inside the hollow elongated body in order to carry one or more users from the source floor to the destination floor once the one or more users enter the hollow elongated body. Further, the elevator comprises a central processing unit for generating a schedule based on real-time bookings received from the one or more users, wherein the schedule enables the elevator unit to move the hollow elongated body in at least one of an upward direction and a downward direction.
[007] In one embodiment, a system for operating an elevator configured to bridge two buildings is disclosed. The system comprises a processor coupled to a memory, wherein the processor is configured to execute programmed instructions stored in the memory. The processor may execute a programmed instruction stored in the memory to receive real-time bookings from one or more users of an elevator in order to travel from a source building to a destination building. In one embodiment, the elevator comprises a hollow elongated body having a first gate and a second gate located at either ends of the hollow elongated body, and wherein the first gate is adapted to align with a source floor of a set of source floors, corresponding to the first building, and the second gate is adapted to align with a destination floor of a set of destination floors, corresponding to the second building. Further, the processor is configured to execute programmed instructions stored in the memory to generate a schedule based on the real-time bookings received from the one or more users, wherein the schedule enables an elevator unit, attached with the hollow elongated body, to move the hollow elongated body in at least one of an upward direction or a downward direction. Further, the processor is configured to execute programmed instructions stored in the memory to operate the first gate, the elevator unit, and the second gate. The first gate may be operated by the processor to allow the one or more users to enter into the hollow elongated body, wherein the elevator unit may be operated by the processor to move the hollow elongated body, carrying the one or more users, towards the destination floor, wherein the hollow elongated body is moved based on the schedule, and wherein the second gate may be operated by the processor to allow the one or more users in order to exit from the hollow elongated body and thereby
4
facilitating the one or more users to travel from the source building to the destination building.
[008] In one embodiment, a method for operating an elevator configured to bridge two buildings is illustrated. The method may comprise receiving real-time bookings from one or more users of an elevator in order to travel from a source building to a destination building. In one embodiment, the elevator comprises a hollow elongated body having a first gate and a second gate located at either ends of the hollow elongated body, and wherein the first gate is adapted to align with a source floor of a set of source floors, corresponding to the first building, and the second gate is adapted to align with a destination floor of a set of destination floors, corresponding to the second building. Further, the method may comprise generating a schedule based on the real-time bookings received from the one or more users, wherein the schedule enables an elevator unit, attached with the hollow elongated body, to move the hollow elongated body in at least one of an upward direction or a downward direction. Further, the method may comprise operating the first gate, the elevator unit, and the second gate. The first gate may be operated to allow the one or more users to enter into the hollow elongated body, wherein the elevator unit may be operated to move the hollow elongated body, carrying the one or more users, towards the destination floor, wherein the hollow elongated body is moved based on the schedule, and wherein the second gate is operated to allow the one or more users in order to exit from the hollow elongated body and thereby facilitating the one or more users to travel from the source building to the destination building.
BRIEF DESCRIPTION OF DRAWINGS
[009] The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same numbers are used throughout the drawings to refer like features and components.
[0010] Figure 1 illustrates a network implementation of a system for bridging two buildings, in accordance with an embodiment of the present subject matter.
[0011] Figure 2 illustrates the system for bridging two buildings, in accordance with an embodiment of the present subject matter.
5
[0012] Figure 3 illustrates a flow diagram for bridging two buildings, in accordance with an embodiment of the present subject matter.
DETAILED DESCRIPTION
[0013] The present subject matter relates to an elevator for bridging two or more buildings. The elevator comprises a hollow elongated body having a first gate and a second gate located at either ends of the hollow elongated body. The first gate is adapted to align with a source floor of a set of source floors, corresponding to a first building, and the second gate is adapted to align with a destination floor of a set of destination floors, corresponding to a second building. The hollow elongated body acts as a bridge for connecting first building with the second building. In one embodiment, each floor of the first building and the second building may be enabled with a floor gate. The floor gate is located such that the floor gate is aligned with the first gate or the second gate of the hollow elongated body and operates as and when the first gate and the second gate operates such that a user can enter or exit the hollow elongated body. In one embodiment, the source floor and the destination floor are coplanar.
[0014] Further, the elevator comprises an elevator unit attached to the hollow elongated body. The elevator unit is configured to move the hollow elongated body in at least one of an upward direction or a downward direction. The elevator unit comprises a motor and a pulleys arrangement similar to a conventional elevator structure. The motor and pulleys are configured to vertically maneuver the hollow elongated body and align it with the source floor or the destination floor at a time. The elevator further comprises at least one travelator placed inside the hollow elongated body in order to carry one or more users from the source floor to the destination floor once the one or more users enter the hollow elongated body. Further, the elevator comprises a central processing unit for generating a schedule based on real-time bookings received from the one or more users. The one or more users may use their electronic devices such as smart phone to provide the booking information to the central processing unit. The schedule may be in the form of a set of instructions to enables the elevator unit to move the hollow elongated body in at least one of an upward direction and a downward direction and align the hollow elongated body with the source floor or the destination floor as per the real-time booking information. The central processing unit, hereafter referred to the system is configured to control the movement of the hollow elongated body based on the booking information,
6
such that the users in the first building can safely and time efficiently reach the second building.
[0015] In one embodiment, two parallel travelators are enabled inside the hollow elongated body. The two parallel travelators are configured to carry users in the same direction or in the opposite direction such that the users can reach second building from the first building or from the second building to the first building. The direction of the travelators may be determined based on the count of real-time bookings in each direction or the expected load of bookings. This directional change of the travelators allows the simultaneous movement of people from first building to the second building and vice versa. In one embodiment, the one or more travelators in the hollow elongated body and the hollow elongated body may be folded when not in use, in order to avoid interference with birds or unmanned aerial vehicles.
[0016] In one embodiment, the system is configured to reduce the waiting time involved for reaching the hollow elongated body. For this purpose, the system enabled prior booking of the elevator through a smart phone or any other electronic device. A user may book the elevator to travel from a source floor of the first building and as soon as the hollow elongated body reached the source floor, the system/ central processing unit is configured to notify the user with presence of the elevator at his floor. In case of a conflict in booking between two users arises, a predefined priority logic would be used for resolving the conflict. In one example, priority data can be based on person, current floor, building (e.g. first building, second building) etc. The booking and the current position of the hollow elongated body can be seen by using any mobile device e.g. smart phone as well as on wearable by the user. Also the notification related with the information that the hollow elongated body has reached source floor will be indicated by giving notifications on the mobile devices of the user.
[0017] In one embodiment, the operation of the at least one travelator may be controlled by the system. In one embodiment, the system may determine a pattern of usage of the hollow elongated body and accordingly modify its operation so as to automatically position itself at a particular source floor or a destination floor.
[0018] In one embodiment, the elevator may comprise a first conventional elevator in the source building and second conventional elevator in the destination building connected by one or more travelators. The first conventional elevator and second conventional elevator may have a permanent opening on the back side, such that the one or more travelators are placed to connect the open backside of both the conventional
7
elevators. The travelator comprises a pulley and a motor to control the movement of the travelator in either direction. The system is configured to generate electronic commands for operating the pulley to move or not or to move the travelator in a particular direction. In one embodiment, both the conventional elevators may be configured to operate parallel such that the travelator is always parallel to the ground. In one embodiment, a normal belt may be used to transfer the motion of the motor to the pulley.
[0019] In one embodiment, the system is configured to monitor inputs received from a couple of proximity sensors placed selectively at unsafe zone in the hollow elongated body. The inputs received from the proximity sensors may be used by the system to avoid any accidents. In one embodiment, the real-time booking of the elevator may be performed from a mobile device of the user. The communication between the system and the mobile device may be enabled using 3G/4G connectivity. The system is then configured to generate the schedule.
[0020] In one embodiment, if the connectivity between the mobile devices and the system is lost, the system is configured to use predefined priority rules to resolve the conflict and schedule the hollow elongated body of the elevator. The system may also be configured to monitor the usage patterns and optimize the schedule generated for the movement of the elevator.
[0021] While aspects of described system and method for operating an elevator bridging two buildings may be implemented in any number of different computing systems, environments, and/or configurations, the embodiments are described in the context of the following exemplary system.
[0022] Referring now to Figure 1, a network implementation 100 of a system 102 for operating an elevator bridging two buildings is disclosed. Although the present subject matter is explained considering that the system 102 is implemented on a server, it may be understood that the system 102 may also be implemented in a variety of computing systems, such as a laptop computer, a desktop computer, a notebook, a workstation, a mainframe computer, a server, a network server, and the like. In one implementation, the system 102 may be implemented in a cloud-based environment. It will be understood that the system 102 may be accessed by multiple users through one or more user devices 104-1, 104-2…104-N, collectively referred to as user devices 104 hereinafter, or applications residing on the user devices 104. Examples of the user devices 104 may include, but are not limited to, a portable computer, a personal digital assistant, a handheld device, and a
8
workstation, file server, version control servers, bugs tracking servers. The user devices 104 are communicatively coupled to the system 102 through a network 106. The user device 104 may be used for booking the elevator connecting the two buildings.
[0023] In one implementation, the network 106 may be a wireless network, a wired network or a combination thereof. The network 106 can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and the like. The network 106 may either be a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like, to communicate with one another. Further the network 106 may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like.
[0024] Further, the system 102 is connected to the user devices 104 through the network 106. In one embodiment, the set user devices 104 are connected to the system 102 through the network 106. In one embodiment, each device from the user devices 104 is configured to provide an interface to book the elevator for travelling form source floor 114 of the first building 108 to a destination floor 116 of the second building 110. In one embodiment, the elevator comprises in a hollow elongated body 118, an elevator unit 112, and central processing unit/ the system 102. The hollow elongated body 118 may comprise a first gate 120 and a second gate 122 located at either ends of the hollow elongated body. The first gate 120 is adapted to align with a source floor 114 of a set of source floors of the first building 108. The second gate 122 is adapted to align with a destination floor 116 of a set of destination floors, corresponding to the second building 110. Further, the system 102 is configured to generate a schedule based on the real-time bookings received from the one or more users in the first building 108. The schedule enables the elevator unit 112, attached with the hollow elongated body 118, to move the hollow elongated body 118 in at least one of an upward direction or a downward direction. Further, the system 102 is configured to operate the first gate 120, the elevator unit 112, and the second gate 122. The first gate may be operated by the system 102 to allow the one or more users to enter into the hollow elongated body 118. Once the users enter the hollow elongated body, the system 102 is configured to operate a travelator 124 placed inside the hollow elongated body 118 to carry the users from the first gate 120 to the second gate 122. Further, the elevator unit 112 may be operated by the system 102 to
9
move the hollow elongated body 118, and carrying the one or more users, towards the destination floor 116, wherein the hollow elongated body 118 is moved based on the schedule. Further, the second gate 122 may be operated by the system 102 to allow the one or more users in order to exit from the hollow elongated body 118 and thereby facilitating the one or more users to travel from the source building to the destination building. The process of bridging two buildings is further elaborated with respect to figure 2.
[0025] Referring now to Figure 2, the system 102 is illustrated in accordance with an embodiment of the present subject matter. In one embodiment, the system 102 may include at least one processor 202, an input/output (I/O) interface 204, and a memory 206. The at least one processor 202 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the at least one processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 206.
[0026] The I/O interface 204 may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O interface 204 may allow the system 102 to interact with a user directly or through the user devices 104. Further, the I/O interface 204 may enable the system 102 to communicate with other computing devices, such as web servers and external data servers (not shown). The I/O interface 204 can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The I/O interface 204 may include one or more ports for connecting a number of devices to one another or to another server.
[0027] The memory 206 may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. The memory 206 may include modules 208 and data 210.
[0028] The modules 208 include routines, programs, objects, components, data structures, etc., which perform particular tasks, functions or implement particular abstract data types. In one implementation, the modules 208 may include a booking capturing
10
module 212, a schedule generation module 214, an elevator operating module 216, a gate operating module 218, and other modules 220. The other modules 220 may include programs or coded instructions that supplement applications and functions of the system 102. The data 210, amongst other things, serves as a repository for storing data processed, received, and generated by one or more of the modules 208. The data 210 may also include a local repository 226, and other data 228. The local repository 226 is configured to store the real-time bookings received from the one or more users of the system 102.
[0029] In one implementation, the booking capturing module 212 of the system 102 is configured to connect with the user devices 104 through the network 106 and receive real-time bookings from one or more users intending to user the elevator in order to travel from a source building to a destination building. The real-time bookings may comprise information associated with the travel pattern of the user. For example, the user may provide basic information such as source floor 114, destination floor 116, time to travel, number of travelers with the user, and priority information to the user device and generate real-time booking. This real-time booking information is then received by the system 102 through wired or wireless communication means. The real-time booking information is configured to operate the hollow elongated body of the elevator to carry the user from the source floor to the destination floor. In one embodiment, the hollow elongated body comprises a first gate and a second gate located at either ends of the hollow elongated body, and wherein the first gate is adapted to align with a source floor of a set of source floors, corresponding to the first building, and the second gate is adapted to align with a destination floor of a set of destination floors, corresponding to the second building.
[0030] Once the real-time booking information from one or more users is received by the booking capturing module 212, in the next step, the schedule generation module 214 is configured to generate a schedule based on the real-time bookings received from the one or more users. The schedule enables the elevator unit 112, attached with the hollow elongated body 118, to move the hollow elongated body 118 in at least one of an upward direction or a downward direction based on the schedule. In one embodiment, the schedule generation module 214 is further configured to generate the schedule for the elevator unit 112 based on a set of predefined rules in case if the real-time bookings are not available. Further, the schedule generation module 214 may be configured to optimize the schedule in order to reduce an average waiting time of one or more users. The schedule may optimized based on at least one of a count of real-time bookings received
11
from one or more users, a priority level of each real-time booking, and past usage trends of hollow elongated body 118.
[0031] Further, the gate operating module 218 is configured to operate the first gate to allow the one or more users at the source floor 120 to enter into the hollow elongated body 118. Once the one or more users enter the hollow elongated body 118, the elevator operating module 216 is configured to move the hollow elongated body 118, carrying the one or more users, towards the destination floor 116, wherein the hollow elongated body 118 is moved based on the schedule. For example, the schedule may specify reach level 4 (where the source floor 114 is situated), wait for 30 seconds and detect presence of the users in the travelator, then move to the level 7 where the destination floor 116 is located and wait for 30 seconds and detect if the users have left the hollow elongated body, and finally move towards next booked source floor. Based on this schedule, the elevator operating module 216 is configured to operate the motor and pulley arrangement to bring the hollow elongated body to the desired floor for entry and exit of the users from one building to another.
[0032] Further, the elevator operating module 216 is further configured to operate at least one travelator 124 placed inside the hollow elongated body 118 in order to carry one or more users from the source floor 114 to the destination floor 116. In one embodiment, the direction of the at least one travelator 124 may changed by the elevator operating module 216 based on a count of real-time bookings from each of the set of source floors and the set of destination floors.
[0033] Further, the gate operating module 218 may operate the second gate 122 to allow the one or more users in order to exit from the hollow elongated body 118 and thereby facilitating the one or more users to travel from the source building 108 to the destination building 110. The method for bridging two buildings is further illustrated with respect to the block diagram of figure 3.
[0034] Referring now to figure 3, a method 300 for bridging two buildings is disclosed, in accordance with an embodiment of the present subject matter. The method 300 may be described in the general context of computer executable instructions. Generally, computer executable instructions can include routines, programs, objects, components, data structures, procedures, modules, functions, and the like, that perform particular functions or implement particular abstract data types. The method 300 may also be practiced in a distributed computing environment where functions are performed by remote processing devices that are linked through a communications network. In a
12
distributed computing environment, computer executable instructions may be located in both local and remote computer storage media, including memory storage devices.
[0035] The order in which the method 300 is described is not intended to be construed as a limitation, and any number of the described method blocks can be combined in any order to implement the method 300 or alternate methods. Additionally, individual blocks may be deleted from the method 300 without departing from the spirit and scope of the subject matter described herein. Furthermore, the method 300 can be implemented in any suitable hardware, software, firmware, or combination thereof. However, for ease of explanation, in the embodiments described below, the method 300 may be considered to be implemented in the above described system 102.
[0036] At block 302, the booking capturing module 212 of the system 102 is configured to connect with the user devices 104 through the network 106 and receive real-time bookings from one or more users intending to user the elevator in order to travel from the source building 108 to a destination building 110. The real-time bookings may comprise information associated with the travel pattern of the user. For example, the user may provide basic information such as source floor 114, destination floor 116, time to travel, number of travelers with the user, and priority information to the user device and generate real-time booking. This real-time booking information is then received by the booking capturing module 212 through wired or wireless communication means.
[0037] At block 304, once the real-time booking information from one or more users is received by the booking capturing module 212, in the next step, the schedule generation module 214 is configured to generate a schedule based on the real-time bookings received from the one or more users. The schedule enables the elevator unit 112, attached with the hollow elongated body 118, to move the hollow elongated body 118 in at least one of an upward direction or a downward direction based on the schedule. In one embodiment, the schedule generation module 214 is further configured to generate the schedule for the elevator unit 112 based on a set of predefined rules in case if the real-time bookings are not available or connectivity with the system 102 is lost. Further, the schedule generation module 214 may be configured to optimize the schedule in order to reduce an average waiting time of one or more users. The schedule may optimized based on at least one of a count of real-time bookings received from one or more users, a priority level of each real-time booking, and past usage trends of hollow elongated body 118.
[0038] At block 306, the gate operating module 218 is configured to operate the first gate to allow the one or more users at the source floor 120 to enter into the hollow
13
elongated body 118. Once the one or more users enter the hollow elongated body 118, the elevator operating module 216 is configured to move the hollow elongated body 118, carrying the one or more users, towards the destination floor 116, wherein the hollow elongated body 118 is moved based on the schedule. For example, the schedule may specify reach level 4 (where the source floor 114 is situated), wait for 30 seconds and detect presence of the users in the travelator, then move to the level 7 where the destination floor 116 is located and wait for 30 seconds and detect if the users have left the hollow elongated body, and finally move towards next booked source floor. Based on this schedule, the elevator operating module 216 is configured to operate the motor and pulley arrangement to bring the hollow elongated body to the desired floor for entry and exit of the users from one building to another. Further, the elevator operating module 216 is further configured to operate at least one travelator 124 placed inside the hollow elongated body 118 in order to carry one or more users from the source floor 114 to the destination floor 116. In one embodiment, the direction of the at least one travelator 124 may changed by the elevator operating module 216 based on a count of real-time bookings from each of the set of source floors and the set of destination floors. Further, the gate operating module 218 may operate the second gate 122 to allow the one or more users in order to exit from the hollow elongated body 118 and thereby facilitating the one or more users to travel from the source building 108 to the destination building 110.
[0039] Although implementations for methods and systems operating an elevator configured to bridge two buildings has been described, it is to be understood that the appended claims are not necessarily limited to the specific features or methods described. Rather, the specific features and methods are disclosed as examples of implementations for operating an elevator configured to bridge two buildings.
14

WE CLAIM:
1. An elevator for bridging two buildings, the elevator comprising:
a hollow elongated body having a first gate and a second gate located at either ends of the hollow elongated body, wherein the first gate is adapted to align with a source floor of a set of source floors, corresponding to a first building, and the second gate is adapted to align with a destination floor of a set of destination floors, corresponding to a second building, and wherein the source floor and the destination floor are coplanar;
an elevator unit attached to the hollow elongated body, wherein the elevator unit is configured to move the hollow elongated body in at least one of an upward direction or a downward direction;
at least one travelator placed inside the hollow elongated body in order to carry one or more users from the source floor to the destination floor; and
a central processing unit for generating a schedule based on real-time bookings received from the one or more users, wherein the schedule enables the elevator unit to move the hollow elongated body in at least one of a upward direction and a downward direction.
2. The elevator of claim 1, wherein the central processing unit is further configured to optimize the schedule based on at least one of a count of real-time bookings received from one or more users, a priority level of each real-time booking, and past usage trends of hollow elongated body in order to reduce an average waiting time of one or more users.
3. The elevator of claim 2, wherein the central processing unit is configured to generate the schedule for the elevator unit based on a set of predefined rules if the real-time bookings are not available to the central processing unit.
4. The elevator of claim 1, wherein the central processing unit is configured to change direction of the travelator based on a count of real-time bookings from each floor of the set of source floors and the set of destination floors.
15
5. The elevator of claim 1, wherein either ends of the of the hollow elongated body is adapted to disengage from the source floor or the destination floor, and wherein the hollow elongated body is adapted to fold after either ends of the of the hollow elongated body is disengaged.
6. A system for operating an elevator configured to bridge two buildings, the system comprising:
a memory, and
a processor coupled to the memory, wherein the processor is configured to execute programmed instructions stored in the memory to:
receive real-time bookings from one or more users of an elevator in order to travel from a source building to a destination building, wherein the elevator comprises a hollow elongated body having a first gate and a second gate located at either ends of the hollow elongated body, and wherein the first gate is adapted to align with a source floor of a set of source floors, corresponding to the first building, and the second gate is adapted to align with a destination floor of a set of destination floors, corresponding to the second building;
generate a schedule based on the real-time bookings received from the one or more users, wherein the schedule enables an elevator unit, attached with the hollow elongated body, to move the hollow elongated body in at least one of a upward direction or a downward direction; and
operate the first gate, the elevator unit, and the second gate,
wherein the first gate is operated to allow the one or more users to enter into the hollow elongated body,
wherein the elevator unit is operated to move the hollow elongated body, carrying the one or more users, towards the destination floor, wherein the hollow elongated body is moved based on the schedule, and
wherein the second gate is operated to allow the one or more users in order to exit from the hollow elongated body and thereby
16
facilitate the one or more users to travel from the source building to the destination building.
7. The system of claim 6, further configured to optimize the schedule to reduce an average waiting time of one or more users, wherein the schedule is optimized based on at least one of a count of real-time bookings received from one or more users, a priority level of each real-time booking, and past usage trends of hollow elongated body.
8. The system of claim 7, further configured to generate the schedule for the elevator unit based on a set of predefined rules if the real-time bookings are not available.
9. The system of claim 6, further comprising at least one travelator placed inside the hollow elongated body in order to carry one or more users from the source floor to the destination floor, wherein the direction of the at least one travelator is changed based on a count of real-time bookings from each floor of the set of source floors and the set of destination floors.
10. The system of claim 6, wherein either ends of the of the hollow elongated body is adapted to disengage from the source floor or the destination floor, and wherein the hollow elongated body is adapted to fold after either ends of the of the hollow elongated body is disengaged.
11. A method for operating an elevator configured to bridge two buildings, the method comprising steps of:
receiving, by a processor, real-time bookings from one or more users of an elevator in order to travel from a source building to a destination building, wherein the elevator comprises a hollow elongated body having a first gate and a second gate located at either ends of the hollow elongated body, and wherein the first gate is adapted to align with a source floor of a set of source floors, corresponding to the first building, and the second gate is adapted to align with a destination floor of a set of destination floors, corresponding to the second building;
generating by the processor, a schedule based on the real-time bookings received from the one or more users, wherein the schedule enables an elevator unit,
17
attached with the hollow elongated body, to move the hollow elongated body in at least one of a upward direction or a downward direction; and
operating, by the processor, the first gate, the elevator unit, and the second gate,
wherein the first gate is operated to allow the one or more users to enter into the hollow elongated body,
wherein the elevator unit is operated to move the hollow elongated body, carrying the one or more users, towards the destination floor, wherein the hollow elongated body is moved based on the schedule, and
wherein the second gate is operated to allow the one or more users in order to exit from the hollow elongated body and thereby facilitate the one or more users to travel from the source building to the destination building.