Server, Program, and Information Processing Method

Abstract

Without using specific sensing technologies, information about the environment inside the elevator car is provided to the user in advance. [Solution] The server 101 is configured to communicate with a plurality of mobile terminals 2 and to process information about the elevator 5. The server 101 comprises a processor 111 and a memory 112 that stores environmental information indicating the environment inside the elevator car 51 of the elevator 5. The plurality of mobile terminals 2 include a first mobile terminal 21 carried by a first user and a second mobile terminal 22 carried by a second user. The processor 111 collects environmental information based on posts from the first mobile terminal 21 by the first user while riding in the car 51 or after getting off the car and stores it in the memory 112, and when a second user boards the car, it provides the environmental information to the second mobile terminal 22 before the second user boards the car.

Description

Technical Field

[0001] The present disclosure relates to a server, a program, and an information processing method, and more specifically, to an information processing technology related to an elevator.

Background Art

[0002] JP-A-2023-70524 (Patent Document 1), JP-A-2022-80424 (Patent Document 2), JP-A-2018-34986 (Patent Document 3), and JP-A-2017-218236 (Patent Document 4) all disclose systems for calculating or acquiring information indicating the degree of congestion of an elevator.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Patent Document 2

Patent Document 3

Patent Document 4

Summary of the Invention

Problems to be Solved by the Invention

[0004] What the environment inside the elevator car is like is a concern for users. More specifically, if it is possible to grasp in advance whether the car is crowded or comfortable, for example, the user can appropriately determine whether to use the elevator. It is desirable for the user to be able to grasp the environment inside the car before boarding the car.

[0005] It is conceivable to provide users with information acquired through specific sensing technologies as information indicating the environment inside the elevator car. For example, there is a known technology that uses image recognition with a camera (image sensor) to determine the level of congestion inside the car. However, image recognition can be affected by posters on the car walls, the material of the walls (such as the walls of see-through elevators), and the landing conditions at each floor, which can lead to the acquisition of incorrect information. Similarly, information acquired through sensing of temperature, odor, and dirt can also suffer from the problem of false detection. It is desirable to provide users with information indicating the environment inside the elevator car in advance without using specific sensing technologies.

[0006] This disclosure was made to solve the above-mentioned problems, and one of its purposes is to provide users with information indicating the environment inside the elevator car in advance, without using specific sensing technologies. [Means for solving the problem]

[0007] A server relating to a certain aspect of this disclosure is configured to communicate with multiple mobile terminals and to process information about an elevator. The server comprises a processor and memory that stores environmental information indicating the environment inside the elevator car. The multiple mobile terminals include a first mobile terminal carried by a first user and a second mobile terminal carried by a second user. The processor collects and stores environmental information in memory based on posts from the first mobile terminal by the first user while riding in the car or after disembarking from the car, and provides the environmental information to the second mobile terminal before the second user boards the car when the second user boards the car.

[0008] Programs relating to other aspects of this disclosure are executed by the processor of a mobile device carried by the user. The program includes the step of posting environmental information indicating the environment inside the elevator car to a server based on user actions when it is detected that the user has boarded or alighted from the elevator car.

[0009] Programs relating to other aspects of this disclosure are executed by the processor of a mobile device carried by the user. The program includes the steps of requesting an elevator car, receiving environmental information from a server indicating the environment inside the car based on posts from other users while riding in or after getting out of the car, and displaying the environmental information on the display of the mobile device before the user boards the car.

[0010] Information processing methods relating to other aspects of this disclosure process information relating to an elevator. The information processing method includes the steps of: posting environmental information indicating the environment inside the elevator car from a first mobile terminal of a first user while riding in or after alighting from the elevator car; collecting the environmental information with a server; and, when a second user boards the elevator car, providing the environmental information from the server to the second user's second mobile terminal before the second user boards the elevator car. [Effects of the Invention]

[0011] According to this disclosure, information indicating the environment inside the elevator car can be provided to the user in advance without using specific sensing technologies. [Brief explanation of the drawing]

[0012] [Figure 1] This figure shows the overall configuration of the elevator system according to the embodiment of the present disclosure. [Figure 2] This is a block diagram showing an example of a monitoring center configuration. [Figure 3] This is a block diagram showing an example of a mobile device configuration. [Figure 4] This is a schematic diagram showing the configuration of an elevator. [Figure 5] This figure shows an example of the user interface of an application program displayed on the first mobile device when the first user calls for a shopping cart. [Figure 6] This figure shows an example of the user interface of an application program that is displayed on the first mobile device before the first user boards the cart. [Figure 7] FIG. 1 is a diagram showing an example of a user interface of an application program displayed on the first mobile terminal when the first user posts the congestion level of the car. [Figure 8] FIG. 2 is a conceptual diagram for explaining an example of a method for generating congestion information of the car. [Figure 9] FIG. 3 is a diagram showing an example of a user interface of an application program displayed on the first mobile terminal when the first user posts the comfort level of the car. [Figure 10] FIG. 4 is a diagram showing a first example of a user interface of an application program displayed on the second mobile terminal when the second user calls the car. [Figure 11] FIG. 5 is a diagram showing another second example of a user interface of an application program displayed on the second mobile terminal when the second user calls the car. [Figure 12] FIG. 6 is a diagram showing another third example of a user interface of an application program displayed on the second mobile terminal when the second user calls the car. [Figure 13] FIG. 7 is a flowchart showing the processing procedure of the information processing method according to the present embodiment. MODE FOR CARRYING OUT THE INVENTION

[0013] Hereinafter, the present embodiment will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and the description thereof will not be repeated.

[0014] <System Configuration> <<Overall Configuration>> FIG. 1 is a diagram showing the overall configuration of an elevator management system according to an embodiment of the present disclosure. The elevator management system 100 includes a monitoring center 1, a plurality of mobile terminals 2, and an administrator terminal 3. The monitoring center 1 is communicably connected to the plurality of mobile terminals 2 and the administrator terminal 3 via a network NW.

[0015] Monitoring Center 1 monitors the usage status of elevator 5 (see Figure 4). Monitoring Center 1 is operated, for example, by the maintenance company of elevator 5. The configuration of Monitoring Center 1 is explained in Figure 2.

[0016] Each of the multiple mobile terminals 2 is a device carried by a user (a user of elevator 5). Each mobile terminal 2 is typically a smartphone. Each mobile terminal 2 may also be a tablet, notebook PC (Personal Computer), wearable device (e.g., smartwatch), etc., as long as it is portable. Each mobile terminal 2 stores an application program 42 (see Figure 3) for using elevator 5. The configuration of the mobile terminals 2 is explained in Figure 3.

[0017] Administrator terminal 3 is a terminal used by the administrator of the facility where elevator 5 is installed (ABC Building in the example described later). Administrator terminal 3 is, for example, a desktop PC. The administrator has entered into a contract with the maintenance company for elevator 5 to receive reports on the usage status of elevator 5 (information on congestion and comfort levels, described later).

[0018] Due to space limitations, only two mobile devices 2 are shown in Figure 1, but the number of mobile devices 2 can be any number greater than or equal to two. Typically, multiple mobile devices 2 are used by multiple users. For ease of understanding, two of the multiple mobile devices 2 will be referred to as the first mobile device 21 and the second mobile device 22.

[0019] <<Monitoring Center>> Figure 2 is a block diagram showing an example of the configuration of monitoring center 1. Monitoring center 1 includes a server 101, an input device 102, a display 103, and a communication device 104. Server 101 includes a processor 111, memory 112, and a network interface 113. The components of monitoring center 1 are connected to each other by a communication bus.

[0020] The processor 111 is an arithmetic processing unit such as a CPU (Central Processing Unit) or MPU (Micro-Processing Unit). The memory 112 includes volatile memory such as RAM (Random Access Memory) and rewritable non-volatile memory such as an HDD (Hard Disk Drive), SSD (Solid State Drive), or flash memory. The memory 112 stores a system program 31 including the OS (Operating System), a control program 32 including computer-readable code necessary for control calculations, a congestion database 33 (described later) for collecting and storing elevator congestion levels, and a comfort database 34 (described later) for collecting and storing elevator comfort levels. The processor 111 performs various processes by reading the system program 31 and the control program 32, expanding them into the memory 112, and executing them. The network interface 113 controls data communication between the server 101 and other devices (mobile terminal 2, administrator terminal 3, etc.) via the communication device 104.

[0021] The input device 102 is a keyboard, mouse, or the like, and accepts input from the operator of the server 101. The display 103 displays various information to the operator of the input device 102.

[0022] Although Figure 2 shows an example where server 101 includes one processor 111, server 101 may include multiple processors. That is, server 101 includes one or more processors. The same applies to memory 112. The same also applies to the configuration of the mobile terminal 2, which will be described later.

[0023] In this specification, "processor" is not limited to processors that execute processing using stored-program methods, but may also include hardwired circuits such as ASICs (Application Specific Integrated Circuits) and FPGAs (Field-Programmable Gate Arrays). Therefore, the term "processor" can also be interpreted as processing circuitry in which processing is predefined by computer-readable code and / or hardwired circuits.

[0024] ≪Mobile Devices≫ Figure 3 is a block diagram showing an example of the configuration of the mobile terminal 2. The mobile terminal 2 includes a processing unit 201, a touch panel display 202, a GPS (Global Positioning System) module 203, a mobile communication module 204, and a beacon communication module 205. The processing unit 201 includes a processor 211, memory 212, and a network interface 213. The components of the mobile terminal 2 are connected to each other by a communication bus.

[0025] The processor 211 is an arithmetic processing unit such as a CPU or MPU. The memory 212 includes volatile memory such as RAM and rewritable non-volatile memory such as flash memory. The memory 212 stores a system program 41 including the OS, and also has application programs 42 installed to improve the convenience of the elevator 5. The processor 211 performs various processes by reading the system program 41 and application programs 42, loading them into the memory 212, and executing them. The network interface 213 controls data communication between the mobile terminal 2 and external sources (server 101, beacons 6, 7 (see Figure 4), etc.).

[0026] The touch panel display 202 accepts user input and displays various information to the user. The GPS module 203 can be used by the server 101 to obtain the location of the mobile terminal 2 (i.e., the user's current location). The mobile communication module 204 is a long-range communication module that enables communication between the mobile terminal 2 and the server 101. The beacon communication module 205 is a short-range communication module that enables communication between the mobile terminal 2 and the beacons 6 and 7 installed in the elevator 5.

[0027] <Elevator Configuration> Figure 4 is a schematic diagram showing the configuration of elevator 5. In this embodiment, elevator 5 is installed in the "ABC Building," which is assumed to be a 10-story building with one basement floor. Also, for simplicity, it is assumed that there is only one elevator installed in the ABC Building. Elevator 5 is, for example, a rope-type elevator and includes a car 51, a counterweight 52, a rope 53, a hoisting machine 54, and a deflector wheel 55.

[0028] The elevator car 51 and counterweight 52 are installed inside the elevator shaft in the ABC Building. The elevator car 51 and counterweight 52 are suspended from both ends of a rope 53, respectively. The rope 53 is attached to a hoisting machine 54 and a deflector wheel 55. The elevator car 51 moves up and down within the elevator shaft, traveling between floors from the lowest floor (basement 1st floor) to the highest floor (10th floor). The counterweight 52 moves in the elevator shaft in the opposite direction to the elevator car 51. The elevator car 51 can stop at each floor.

[0029] Beacons 6 are installed at the boarding areas on each floor. In addition, beacons 7 are installed inside the elevator car 51. Communication between the mobile terminal 2 and beacons 6 and 7 allows for detection of when the mobile terminal 2 (i.e., the user) approaches a boarding area, when the mobile terminal 2 enters the elevator car 51, and when the mobile terminal 2 exits the elevator car 51.

[0030] <Crowding level and comfort level> In many elevators, especially during peak hours, it's impossible to know whether you'll be able to board until the elevator car arrives and the doors open. This can make it difficult for users to decide whether to use the elevator or another mode of transportation, and how long they'll have to wait for a rideable car. It would be desirable for users to be able to see the level of congestion inside the elevator car before it arrives. In addition, it would be desirable for users to be able to see the level of comfort inside the elevator car. On the other hand, a challenge may arise in determining what kind of environmental information, such as the level of congestion or comfort inside the elevator car, should be provided to the user.

[0031] In the example shown in Figure 4, the first user U1 is carrying the first mobile terminal 21, and the second user U2 is carrying the second mobile terminal 22. First, the first user U1 moves from the first floor to the eighth floor. Subsequently, the second user U2 moves from the first floor to the ninth floor. Under these circumstances, the application programs 42 (see Figure 3) installed on the first mobile terminal 21 and the second mobile terminal 22 are used in a chronological manner.

[0032] Calling the cart First, let's assume that the first user U1 is on the first floor and has not yet boarded elevator 51. Before arriving at the boarding area on the first floor (for example, when arriving at the entrance of the ABC building), the first user U1 operates the first mobile terminal 21 to cause elevator 51 to move to the first floor.

[0033] Figure 5 shows an example of the user interface of the application program 42 displayed on the first mobile terminal 21 when the first user U1 calls the elevator car 51. As shown in Figure 5, when calling the elevator car 51, the first user U1 uses a scroll list 811 that shows the floors of the ABC building that can be reached using the elevator 5 to select the current floor to board (in this example, "1st floor") 812 and the destination floor to disembark ("8th floor") 813. Subsequently, when the first user U1 presses the confirm button ("Call") 814, the elevator car 51 moves to the current floor selected by the first user U1. Although not shown, a similar user interface is displayed on the second mobile terminal 22 when the second user U2 calls the elevator car 51.

[0034] ≪Posts about crowd levels≫ The first user U1 boards elevator 51 from the first floor, and disembarks when elevator 51 arrives on the eighth floor. Immediately afterward, the first user U1 posts the congestion level of elevator 51 to the application program 42.

[0035] Figure 6 shows an example of the user interface of an application program 42 that is displayed on the first mobile terminal 21 before the first user U1 boards the elevator car 51. While the first user U1 is waiting for the arrival of the elevator car 51, the first mobile terminal 21 displays a pop-up (overlay) 821 prompting the first user U1 to post the congestion level. A further pop-up 822 may be displayed for the first user U1 to select the congestion level. Pop-up 822 may be grayed out so that input is not possible at this point.

[0036] Figure 7 shows an example of the user interface of the application program 42 displayed on the first mobile terminal 21 when the first user U1 posts the congestion level of the carriage 51. When the first user U1 boards the carriage 51 or subsequently alights from the carriage 51, a popup 831 is displayed on the first mobile terminal 21 for the first user U1 to select the congestion level. In this example, the popup 831 includes a button 832 indicating that the carriage 51 is not crowded ("plenty of space"), a button 833 indicating that the carriage 51 is relatively crowded ("shoulders touching"), and a button 834 indicating that the carriage 51 is very crowded and it is difficult to board ("cannot board").

[0037] The first user, U1, subjectively evaluates the congestion level of cart 51 and submits the evaluation result by selecting one of the three buttons 832-834. Figure 7 shows an example of evaluating the congestion level of cart 51 on a three-point scale. However, the congestion level of cart 51 can be evaluated on any two or more points.

[0038] <<Generating congestion information>> Posts from the first user U1 are sent to the server 101 at the monitoring center 1. Posts from numerous other users' mobile terminals 2 (not shown) are also sent to the server 101 and collected by the server 101 along with posts from the first user U1's first mobile terminal 21. The server 101 aggregates the posts regarding the congestion level of the shopping cart 51 and stores the aggregated results in the congestion level database 33. The server 101 then generates congestion information for the shopping cart 51 by statistically processing the numerous posts. Congestion information is an example of environmental information.

[0039] Figure 8 is a conceptual diagram illustrating an example of a method for generating congestion information for the elevator car 51. The server 101 collects congestion levels for the elevator car 51 from numerous mobile terminals 2 and aggregates them, for example, by attributes such as floor, boarding time, and boarding date.

[0040] The horizontal axis in Figure 8 represents the time of day when passengers board the train. The vertical axis represents the level of congestion. The level of congestion is calculated by quantifying posts from a large number of users. For example, posts from each user are quantified by assigning points such as 0 for "comfortable," 1 for "shoulders touching," and 2 for "unable to board." Then, the average of these values ​​is taken for each time period.

[0041] Regarding floors, server 101 aggregates congestion levels for each combination of the current floor and the destination floor. Server 101 may aggregate congestion levels for two or more floors instead of aggregating for each floor. In the example in Figure 4, server 101 may, for example, designate floors B1-B3 as low-rise floors, floors 4-B7 as middle-rise floors, and floors 8-B0 as high-rise floors, and aggregate congestion levels for each of the low-rise, middle-rise, and high-rise floors. The same applies to destination floors. Server 101 may use a combination of the current floor and the direction of movement (whether going up or down from the current floor) instead of a combination of the current floor and the destination floor. Alternatively, server 101 may use only the current floor instead of a combination of the current floor and the destination floor.

[0042] Regarding the time of use, in the example shown in Figure 8, congestion levels are compiled every hour to avoid making the diagram too complex. However, in most cases, the number of elevator users changes over shorter periods of time, so it is desirable to shorten the time unit for compiling congestion levels (e.g., every 10 minutes, every 15 minutes, every 30 minutes).

[0043] The attributes of the boarding date are factors that can influence the level of congestion on Kago 51. More specifically, the attributes of the boarding date may include, for example, the time of year (e.g., which month, which week of which month), the day of the week (weekday, weekend, or public holiday), and weather conditions (weather, temperature, etc.). The attributes of the boarding date may be based on statistical data over a predetermined period in the past (e.g., one month, one year). Alternatively, instead of the attributes of the boarding date, congestion information for Kago 51 may be generated based on the latest posts collected during a predetermined time (30 minutes) prior to the boarding time.

[0044] When server 101 receives a request from mobile terminal 2 for congestion information for car 51, it generates congestion information for car 51 by referring to congestion levels previously compiled under the same conditions as the requesting mobile terminal 2 (i.e., attributes of the same floor, same boarding time, and same boarding day).

[0045] Server 101 may provide administrator terminal 3 with detailed congestion information for elevator car 51 (aggregated results as shown in Figure 8). This allows the administrator of ABC Building to adjust the waiting location (waiting floor) of elevator car 51 according to the time of day in order to alleviate congestion in elevator car 51. Specifically, the administrator can set the waiting floor of elevator car 51 near a floor with high congestion.

[0046] ≪Comfort Level Post≫ The first user U1 may post a comfort level for cart 51 in addition to or instead of posting a congestion level for cart 51. Server 101 aggregates the posts regarding the comfort level of cart 51 and stores the aggregated results (comfort information) in the comfort level database 34. Comfort information is another example of environmental information.

[0047] Figure 9 shows an example of the user interface of an application program 42 displayed on a first mobile terminal 21 when a first user U1 submits a rating for the comfort level of the basket 51. A popup 841 is displayed on the first mobile terminal 21 for the first user U1 to select a comfort level. In this example, the popup 841 includes a button 842 indicating that the basket 51 was hot and uncomfortable ("The basket is hot"), a button 843 indicating that the basket 51 was cold and uncomfortable ("The basket is cold"), a button 844 indicating that there was some kind of odor in the basket 51 ("There is an odor"), a button 845 indicating that the floor or walls of the basket 51 were dirty ("The floor or walls are dirty"), and a button 846 indicating that there was trash or other debris in the basket 51 ("There is trash"). Although not shown, a button indicating that the basket 51 was comfortable may also be provided.

[0048] The first user U1 subjectively evaluates the comfort level of the basket 51. If there are any unpleasant aspects, the first user U1 submits their comfort level by selecting any number of buttons from the five buttons 842 to 846.

[0049] Server 101 may provide comfort information about the elevator car 51 to the administrator terminal 3. This allows the administrator terminal 3 to adjust the operating status of the elevator car 51 to improve its comfort level. Specifically, if a certain number of posts are collected indicating that the temperature of the elevator car 51 was uncomfortable, the administrator terminal 3 may adjust the air conditioning temperature of the elevator car 51. If a certain number of posts are collected indicating that the odor of the elevator car 51 was unpleasant, the administrator terminal 3 may activate the ventilation fan of the elevator car 51. Alternatively, the administrator terminal 3 may increase the rotation speed of the ventilation fan of the elevator car 51. If a certain number of posts are collected indicating the presence of dirt or debris on the floor or walls, the administrator terminal 3 may send instructions to the cleaning staff of the elevator car 51 to clean it.

[0050] <<Display of congestion information>> Subsequently, the second user U2, heading towards the first-floor platform, operates the second mobile terminal 22 (with a user interface similar to that in Figure 5) to summon elevator car 51 to the first floor. At this time, the server 101 provides the second mobile terminal 22 with congestion information for elevator car 51.

[0051] Figure 10 shows a first example of the user interface of an application program 42 that is displayed on a second mobile terminal 22 when a second user U2 calls for elevator car 51. A pop-up 851 showing congestion information for elevator car 51 is displayed on the second mobile terminal 22. The pop-up 851 includes, for example, an icon 852 and a message 853 indicating that elevator car 51 is available. As a result, the second user U2, having seen the pop-up 851, can proceed to the landing on the first floor knowing in advance that elevator car 51 is not crowded.

[0052] Figure 11 shows a second example of the user interface of the application program 42 that is displayed on the second mobile terminal 22 when the second user U2 calls for the elevator car 51. The popup 861 includes an icon 862 and a message 863 indicating that the elevator car 51 is very crowded. This allows the second user U2, upon seeing the popup 861, to proceed to the first-floor boarding area knowing in advance that the elevator car 51 may be crowded and they may not be able to board.

[0053] Popup 861 may further include message 864 suggesting the use of other means of transportation (stairs, escalator, etc.). Message 864 may be determined depending on which floors in Building ABC are accessible by stairs or escalator. Second user U2 may choose other means of transportation to travel from the 1st floor to the 9th floor, following the suggestion from server 101.

[0054] Figure 12 shows a third example of the user interface of the application program 42 displayed on the second mobile terminal 22 when a second user U2 calls for elevator 51. Popup 871, like popup 861 (see Figure 11), includes an icon 872 and a message 873 indicating that elevator 51 is very crowded. Popup 871 may further include a message 874 suggesting boarding from a landing on a different floor than the current floor. This allows the second user U2 to travel to a landing on another floor by other means of transportation, following the suggestion from the server 101. For example, if past congestion data shows that many users from the basement or first floor disembark on the fourth floor, the second user U2 can travel to the fourth floor by other means of transportation, and then board elevator 51 to go to the ninth floor.

[0055] <Processing Flow> Figure 13 is a flowchart showing the processing procedure of the information processing method according to this embodiment. The steps included in this flowchart are executed when predetermined conditions are met. Each step on the left is executed by the server 101 (processor 111) located in the monitoring center 1. Each step on the right is executed by the mobile terminal 2 (processor 211 of the arithmetic processing unit 201). Each step is typically implemented by software processing (execution of application program 42), but may also be implemented by hardware (electrical circuit). Hereinafter, steps will be abbreviated as S.

[0056] Referring to Figures 2 to 4 and Figure 13, in S21, the mobile terminal 2 (application program 42) accepts user input to select the current floor and destination floor (see Figure 5). The current floor and destination floor may be registered in the mobile terminal 2 in advance. The mobile terminal 2 transmits the current floor and destination floor selected by the user to the server 101.

[0057] In S22, the mobile terminal 2 accepts a user input to select whether or not to receive environmental information (congestion information and / or comfort information). If the user wishes to receive environmental information, the mobile terminal 2 requests the server 101 to provide it. Whether or not the user wishes to receive environmental information may be set in advance. If the user has been set in advance to wish to receive environmental information, the mobile terminal 2 requests the server 101 to provide it without any user input.

[0058] In S11, server 101 generates congestion information for elevator car 51 when it moves from the current floor to the destination floor selected by the user, based on past posts from other users. This generation method was explained in Figure 8, so it will not be repeated here. Server 101 may also generate comfort information based on comfort level as explained in Figure 9. Server 101 provides the generated environment information to the mobile terminal 2 (S12).

[0059] In S23, the mobile terminal 2 displays the provided environmental information on the touch panel display 202 (see Figures 10 to 12). If the destination floor has not been determined (NO in S24), the mobile terminal 2 returns to processing in S21.

[0060] If the destination floor is determined (YES in S24), the user checks the environmental information and decides whether to call car 51, and operates the mobile terminal 2 according to that decision (S25). If the mobile terminal 2 receives a user operation that does not call car 51, or if the user operation to call car 51 is not performed within the specified time (NO in S25), the mobile terminal 2 skips the subsequent processing and returns processing to the main routine. If the mobile terminal 2 receives a user operation to call car 51 (YES in S25), the mobile terminal 2 requests the server 101 to move car 51 to the current floor (S26). The server 101 responds to the request from the mobile terminal 2 and moves car 51 to the current floor (S13). When car 51 arrives at the current floor, the user boards car 51. The server 101 can also determine that the user has boarded car 51 from information from beacons 6 and 7. The server 101 may also determine that the user has boarded from GPS information.

[0061] In S14, server 101 determines whether car 51 has arrived at the destination floor. Server 101 waits until car 51 arrives at the destination floor (NO in S14), and when car 51 arrives at the destination floor (YES in S14), requests mobile terminal 2 to post the congestion level of car 51 (S15). Server 101 can also determine that a user has disembarked from car 51 based on information from beacons 6 and 7. Server 101 may also determine that a user has disembarked based on GPS information.

[0062] Although not shown in the diagram, server 101 may request mobile terminal 2 to post the congestion level of car 51 while the user is riding in car 51 (i.e., from the time the user boards car 51 until they alight from it).

[0063] In S27, the user performs an operation to post the congestion level of the cart 51 (see Figures 6 and 7). The mobile terminal 2 sends the congestion level entered by the user to the server 101. In addition, the user performs an operation to post the comfort level of the cart 51 (see Figure 9). The mobile terminal 2 sends the comfort level entered by the user to the server 101 (S28). The order of processing between S27 and S28 may be reversed.

[0064] In S16, server 101 stores the congestion level received from mobile terminal 2 in congestion database 33, and stores the comfort level received from mobile terminal 2 in comfort database 34.

[0065] The ABC building may be equipped with a dedicated storage device (not shown) for aggregating the congestion and comfort levels of the elevator car 51 from the mobile terminal 2. In this case, the storage device periodically (for example, once a day) transmits the aggregated results of the congestion and comfort levels to the server 101.

[0066] In S17, server 101 grants mobile terminal 2 an incentive for the user to post the congestion level. The incentive may be, for example, the right to receive environmental information from server 101 for a predetermined period. The incentive may also be points that can be exchanged for goods or services within the ABC building. This completes the series of processes.

[0067] It is conceivable to quantitatively evaluate the degree of congestion in car 51 based on objective numerical values ​​such as the number of passengers in car 51 and the total weight of car 51 (see, for example, Patent Documents 1-4). However, such objective numerical values ​​may not necessarily match the user's perception. Even if the number of passengers is identified by image recognition of images captured by a camera, luggage being transported (number and size of luggage) may be omitted from the evaluation. Image recognition can be affected by posters on the car walls, the material of the walls (such as see-through elevators), and the landing conditions at each floor, so incorrect information may be output. Alternatively, the total weight measured by a weighing device does not evaluate the degree of spatial occupancy within car 51. Similar problems of false detection can occur with information obtained by sensing temperature, odor, dirt, etc.

[0068] In contrast, in this embodiment, the congestion level of the elevator car 51 can be posted from the mobile terminal 2 to the server 101. Therefore, with this embodiment, information indicating the environment inside the elevator car can be provided to the user in advance without using specific sensing technology.

[0069] The congestion information, which shows the aggregated results of congestion levels obtained from user submissions, reflects the subjective evaluations of users who have actually ridden on the Kago 51. Furthermore, the level of congestion perceived by other users who subsequently ride Kago 51 is also subjective. Thus, in this embodiment, the input and output of congestion levels are unified by subjective evaluations. Therefore, according to this embodiment, useful information can be provided to users in that it matches the users' perceptions.

[0070] Furthermore, in this embodiment, the comfort level of the elevator car 51, including temperature, smell, scratches, dirt, and trash, can be posted from the mobile terminal 2 to the server 101. This comfort information, which shows the aggregated results of the comfort level, is also subjective, based on the feelings of other users who have ridden in the elevator car 51. Therefore, both the input and output of the comfort level are unified by subjective evaluations. From this point of view, this embodiment can provide users with useful information that matches the user's perception. In addition, the comfort level of the elevator car 51 can be improved by adjusting the operating conditions of the elevator car 51 in accordance with the comfort information showing the aggregated results of the comfort level.

[0071] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of this disclosure is indicated by the claims rather than by the description of the embodiments above, and all modifications within the meaning and scope equivalent to the claims are intended to be included. [Explanation of Symbols]

[0072] 100 Elevator management system, 1 Monitoring center, 101 Server, 102 Input device, 103 Display, 104 Communication device, 111 Processor, 112 Memory, 113 Network interface, 2 Mobile terminals, 21 First mobile terminal, 22 Second mobile terminal, 201 Processing unit, 202 Touch panel display, 203 GPS module, 204 Mobile communication module, 205 Beacon communication module 205, 211 Processor, 212 Memory, 213 Network interface, 3 Administrator terminal, 31 System program, 32 Control program, 33 Congestion level database, 34 Comfort level database, 41 System program, 42 Application program, 5 Elevator, 51 Car, 52 Counterweight, 53 Rope, 54 Hoisting machine, 55 Deflection vehicle, 6,7 Beacons.

Claims

1. A server configured to communicate with multiple mobile devices and to process information about elevators, Processor and The elevator includes a memory for storing environmental information that indicates the environment inside the elevator car, The aforementioned plurality of mobile terminals include a first mobile terminal carried by a first user and a second mobile terminal carried by a second user. The aforementioned processor, The system collects the environmental information based on a post made by the first user from the first mobile terminal while riding in the basket or after disembarking from the basket, and stores it in the memory. A server that provides the environmental information to the second mobile terminal before the second user boards the basket when the second user boards the basket.

2. The server according to claim 1, wherein the environmental information includes congestion information indicating the degree of congestion of the basket.

3. The server according to claim 2, wherein the processor suggests to the second mobile terminal the use of a means of transportation other than the elevator when the level of congestion in the elevator car in which the second user is riding exceeds a standard value.

4. The aforementioned processor, The aforementioned level of congestion is aggregated by distinguishing it according to the attributes of the floor, time of boarding, and day of boarding. The server according to claim 2, which, when the second user boards the elevator car, provides the second mobile terminal with the congestion information corresponding to the floor on which the second user boards, the time of boarding, and the date of boarding.

5. The server according to claim 4, wherein the processor provides the elevator administrator terminal with congestion information indicating the degree of congestion aggregated for each attribute of the floor, the time of travel, and the day of travel.

6. The aforementioned environmental information includes comfort information indicating the comfort level of the basket, The server according to claim 1, wherein the comfort level is determined based on at least one of the temperature, smell, dirt, and debris inside the basket.

7. The server according to claim 6, wherein the processor provides the comfort information to the elevator's administrator terminal.

8. The server according to any one of claims 1 to 7, wherein the processor provides the environmental information to the second mobile terminal when the cage is invoked by the second mobile terminal.

9. The server according to any one of claims 1 to 7, wherein the processor requests the first mobile terminal to post the environmental information when it is detected that the first user has boarded the basket or has alighted from the basket.

10. A program executed by the processor of a mobile device carried by a user, A program that, when it is detected that the user has boarded an elevator car or has alighted from the car, includes the step of posting environmental information indicating the environment inside the car to a server based on the user's actions.

11. A program executed by the processor of a mobile device carried by a user, Steps to request the elevator car, The steps include receiving environmental information from a server that indicates the environment inside the cart based on posts from other users while riding in the cart or after disembarking from the cart, A program comprising the step of displaying the environmental information on the display of the mobile terminal before the user boards the basket.

12. An information processing method for processing information related to elevators, The first step of posting environmental information indicating the environment inside the elevator car to a server from the first mobile terminal of the first user while riding in the elevator car or after alighting from the elevator car, The steps include: collecting the aforementioned environmental information using the server; An information processing method comprising the step of providing the environmental information from the server to the second user's second mobile terminal before the second user boards the basket when the second user boards the basket.

Images