ELEVATOR GROUP CONTROL DEVICE AND ELEVATOR GROUP CONTROL METHOD

Abstract: In a vertically movable elevator group management control apparatus for control of a plurality of transversely shiftable cars among plural shafts, control is done by storing route data with respect to each said car, generating target floor data including a target floor, based on car call data obtained in correspondence with each said car and station call data as obtained correspondingly to each floor, estimating the time taken for said car to reach said target floor, based on at least said route data, said target floor data and said car call data, and assigning a certain car to a certain floor call, based on the estimated arrival time.

Description: FIELD OF THE INVENTION The present invention relates generally to elevator control systems, and more particularly to an elevator group management control apparatus and an elevator group management control method for control of a plurality of enclosed platforms or cars in associated vertical passages or "shafts" while permitting transverse traveling of these cars among the shafts. BACKGROUND OF THE INVENTION Conventionally, in cable-driven elevator systems with a plurality of lift passages or "shafts," various kinds of so-called "elevator group management" schemes have been provided in order to increase the transportation efficiency. The elevator group management schemes are to manage or control traveling of elevator platforms or cars (referred to as "cars" hereinafter) not by letting these cars respond individually to landing-place or "station" calls in a car-to-shaft correspondence manner but by determining an appropriate car that should respond to a station call by taking account of the actual traveling conditions of individual cars moving in respective shafts associated. In the recent years advanced elevator systems have been proposed in order to achieve further enhanced transportation efficiency, one of which is a vertical /transversal movable elevator group control system as has been disclosed in, for example, Published Unexamined Japanese Patent Application (PUJPA) No. 62-275987 and PUJPA No. 3-216477. This system disclosed is the one capable of causing a plurality of cars to move or travel in a single shaft by use of linear motors while allowing them to transversely shift among the shafts. Such elevator system is becoming more attractive in practical applications due to its advantage: the allowable transportation amount can be much improved due to the fact that it enables associative transportable cars to increase in number as compared to the prior known cable-driven elevator systems insofar as the shafts in both systems is identical in number. Furthermore, the elevator group management control apparatus and the elevator group management control method used in this type of vertically- and horizontally-movable elevator system, such as the one disclosed in PUJPA No. 5-9173, are designed on the concept that a car moves in one direction only (upward or downward) in each shaft and that a car moves in a loop. In the vertical /transversal movable elevator group control system, the system design is established under the assumption that a plurality of cars are moving in one shaft while permitting their crosswise movement among these shafts; this will possibly lead to occurrence of collision between adjacent ones of the cars. To avoid such collision, especially to retain maximized safety for passengers, several transportation management methods have been developed: one approach is to force the cars to decrease in moving speed eliminating collision by use of a car position detector means; and, another approach is to force the individual car to stop at an appropriate position that may exclude the risk of occurrence of collision. However, the elevator group management control apparatus and the elevator group management control method used in the above-mentioned conventional vertically- and horizontally-movable elevator system has the problems described below. Unfortunately, the advanced elevator system enabling plural cars to simultaneously move within a single shaft while permitting their transverse movement among shafts does not come without accompanying the problem which follows: in addition to the risk of collision, there will possibly take place some factors adversely serving as a serious bar to accomplishment of successful operation of cars, such as accumulation, congestion, dead lock, or the like. Another disadvantage encountered is that upon occurrence of locally crowded conditions such as cars' accumulation, delay or dead lock, it will no longer possible without the use of special techniques for avoidance to provide satisfactory services as minimally expected to elevator systems: i.e., assuring maximal services for efficient transportation among floors within a limited time duration. Furthermore, if there is a free car and another car that is on call operating in the same shaft, it is necessary to issue an operation instruction to the free car to ensure that it does not present any hindrance to the operation of the car on call. In addition, by positioning free cars at positions where they can respond quickly to station calls that will arise in the future, it will be possible to further improve traffic efficiency. Furthermore, when a new station call is generated in the conventional elevator group management control method (elevator group management control method) where a car moves only in one direction in each shaft, it is necessary to respond to the station call according to the direction of the shaft in which each car is moving. This means that, when there is no shaft in which a car moves into the requested direction and therefore no car can respond to the call immediately, a free car in a shaft whose direction is opposite to the requested direction, if available, is not assigned. As a result, the user who generated the new station call must wait long. In Fig. 40, assume that the operation direction of the first and third shafts is upward and that of the second and fourth shafts is downward in an elevator system with four shafts in a 20-story building. Also assume that car 1 is at the fifteenth floor and car 2 is at the seventh floor in the first shaft, car 3 is at the third floor in the second shaft, car 4 is at the eighteenth floor in the third shaft, and that car 5 is at the tenth floor in the fourth shaft. Also assume that cars 1, 2, and 4 each are in the stopped state at the respective floors and are ready to close the doors to start moving and that cars 3 and 5 are moving in the shafts. Suppose that a new station call (5, DN) is generated in the situation described above. For car 1 at the fifteenth floor in the first shaft to respond to the new station call, it must first go up to the twentieth, move horizontally to the second shaft, and then go down to the fifth floor. That is, for car 1 to respond to the new station call (5, DN), 21 steps are required, where moving up or down one floor in the shaft and moving from one shaft to another each is counted as one step. Similarly, to respond to the new station call, car 2 requires "29 steps", car 3 requires "39 steps", car 4 requires "18 steps", and car 5 requires "5 steps". In this case, if car 2 in the first shaft may be reversed, the station call is satisfied in "2 steps"; similarly, if car 3 in the second shaft may be reversed, the station call is satisfied in "2 steps". Thus, reversing a car in this manner makes it possible to respond to a new station call quickly. The present invention has been made to avoid the problems as faced with the prior art, and the object of this invention is to provide an elevator group management control apparatus and an elevator group management control method capable of eliminating occurrence of any locally crowded conditions due to cars' congestion, delay or dead lock alike in such vertical/transversal movable elevator system. SUMMARY OF THE INVENTION Accordingly, in a first aspect, the present invention provides an elevator group management control apparatus for use in an elevator system comprising a plurality of vertically- and horizontally-movable cars each capable of stopping at a plurality of floors, a car operation control means controlling the operation of the cars, one or more station call registration means installed in the station of each floor, and a car data detection means detecting the state of each of said cars, said elevator group management control apparatus comprising: route data storage means for storing therein route data with respect to each said car; a call data storage means for storing "call data" consisting of car calls from each of said cars and station calls assigned to each car; target floor instruction means for generating target floor data including a target floor based on call data stored in said call data storage means and station call data stored in said station call registration means; arrival time estimation means for estimating a time as taken for said car to reach said target floor based on said route data, said target floor data, said call data and car data detected by said car data detection means; and assignment instruction means for assigning based on the estimated arrival time as obtained by said arrival time estimation means a certain car to a certain floor call. In a second aspect, the present invention also provides an elevator group management control method for use in an elevator system comprising a plurality of vertically- and horizontally-movable cars each capable of stopping at a plurality of floors, a car operation control process controlling the operation of the cars, a station call registration process executed at the station of each floor, and a car data detection process detecting the state of each of said cars, said elevator group management control method comprising: a route data storage process storing therein route data with respect to each said car; a call data storage process storing "call data" consisting of car calls from each of said cars and station calls assigned to each car; a target floor instruction process generating target floor data including a target floor based on call data stored by said call data storage process and station call data stored by said station call registration process; an arrival time estimation process estimating a time as taken for said car to reach said target floor based on said route data, said target floor data, said call data and car data detected by said car data detection process; and an assignment instruction process assigning based on the estimated arrival time as obtained by arrival time estimation process a certain car to a certain floor call. In a third aspect, the present invention further provides a carriage management control apparatus for controlling a plurality of carriages each capable of moving across a plurality of shafts comprising: storage means for storing route data describing a route along which a carriage moves in vertical directions in said shafts and in horizontal directions across said shafts; and management means for managing the operation of said carriages in vertical directions in said shafts and in horizontal directions across said shafts according to said route data. In a fourth aspect, the present invention provides a recording medium containing an elevator group management control program for use in an elevator system comprising a plurality of vertically- and horizontally-movable cars each capable of stopping at a plurality of floors, a car operation control process controlling the operation of the cars, a station call registration process executed at the station of each floor, and a car data detection process detecting the state of each of said cars, said elevator group management control program comprising: a route data storage step for storing therein route data with respect to each said car; a call data storage step for storing "call data" consisting of car calls from each of said cars and station calls assigned to each car; a target floor instruction step for generating target floor data including a target floor based on call data stored by said call data storage process and station call data stored by said station call registration process; an arrival time estimation step for estimating a time as taken for said car to reach said target floor based on said route data, said target floor data, said call data and car data detected by said car data detection process; and an assignment instruction step for assigning based on the estimated arrival time as obtained by arrival time estimation process a certain car to a certain floor call. The invention enables achievement of high efficient car transportation responsive to any station calls and car calls. Thus, an invention to achieve the object described in this application is as follows. The route along which each car moves is pre-defined because it moves in each shaft in one direction only and, therefore, it is possible to estimate how long it will take for each car to arrive at a floor requested by a station call or a car call. This estimated time is used to calculate a time to respond to a call (wait time) or a service time (time from when a station call is received to when a car arrives at a requested floor) and, based on these calculated times, a new station call is assigned to a car which will be able to respond to the call first. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a diagram showing a configuration of a vertically/transversal movable elevator group management control apparatus in accordance with one preferred embodiment of the present invention ; Fig. 2 is a diagram showing a configuration of an elevator group management control apparatus in accordance with the first embodiment of the present invention ; Fig. 3 is a diagram for explanation of one exemplary route along which a car is expected to travel; Fig. 4 is a diagram for explanation of one exemplary route along which a car is to travel ; Fig. 5 is a diagram for explanation of operation processing of an arrival time estimation device ; Fig. 6 is a diagram showing a configuration of an elevator group management control apparatus in accordance with the fourth embodiment; Fig. 7 is a diagram showing a configuration of a derivative car call estimation device ; Fig. 8 is a diagram showing a configuration of an elevator group management control apparatus in accordance with the eighth embodiment; Fig. 9 is a diagram showing a configuration of an elevator group management control apparatus in accordance with the ninth embodiment; Fig. 10 is a diagram showing a configuration of an elevator group management control apparatus in accordance with the tenth embodiment; Fig. 11 is a diagram showing a configuration of an elevator group management control apparatus in accordance with the eleventh embodiment; Fig. 12 is a diagram showing a configuration of an elevator group management control apparatus in accordance with the twelfth embodiment; Fig. 13 is a diagram showing a configuration of an elevator group management control apparatus in accordance with the thirteenth embodiment; Fig. 14 is a diagram showing a configuration of an elevator group management control apparatus in accordance with the fourteenth embodiment ; Fig. 15 is a diagram showing a configuration of an elevator group management control apparatus in accordance with the fifteenth embodiment; Fig. 16 is a diagram showing a configuration of an elevator group management control apparatus in accordance with the sixteenth embodiment; Fig. 17 is a diagram showing a configuration of an elevator group management control apparatus in accordance with the seventeenth embodiment; Fig. 18 is a diagram showing a configuration of an elevator group management control apparatus in accordance with the eighteenth embodiment; Fig. 19 is a diagram showing the configuration of the nineteenth embodiment of the elevator group management control apparatus according to this invention ; Fig. 20 is a diagram showing the configuration of the reversing car determination device used in the nineteenth embodiment of the elevator group management control apparatus according to this invention ; Fig. 21 is a diagram explaining the nineteenth embodiment of the elevator group management control apparatus according to this invention, and shows how each car moves ; Fig. 22 is the first half of a flowchart showing the operation steps of the reversing car determination device used in the nineteenth embodiment of the elevator group management control apparatus according to this invention ; Fig. 23 is the second half of a flowchart showing the operation steps of the reversing car determination device used in the nineteenth embodiment of the elevator group management control apparatus according to this invention ; Fig. 24 is a flowchart showing the operation steps of the assignment instruction device which determines a car to respond to a new station call; Fig. 25 is a diagram showing the configuration of the reversing car determination device used in the twentieth embodiment of the elevator group management control apparatus according to this invention ; Fig. 26 is the first half of a flowchart showing the operation steps of the reversing car determination device used in the twentieth embodiment of the elevator group management control apparatus according to this invention ; Fig. 27 is the second half of a flowchart showing the operation steps of the reversing car determination device used in the twentieth embodiment of the elevator group management control apparatus according to this invention ; Fig. 28 is a diagram showing the configuration of the twenty-first embodiment of the elevator group management control apparatus according to this invention ; Fig. 29 is a diagram showing the configuration of the reversing car determination device used in the twenty-first embodiment of the elevator group management control apparatus according to this invention ; Fig. 30 is a diagram explaining the twenty-first embodiment of the elevator group management control apparatus according to this invention, and shows an example of route data stored in the route data storage device ; Fig. 31 is a diagram showing an example of route data of car 1 and car 2 stored in the route data storage device ; Fig. 32 is a diagram showing an example of route data of car 3, car 4, and car 5 stored in the route data storage device ; Fig. 33 is the first part of a flowchart showing the operation steps of the reversing car determination device used in the twenty-first embodiment of the elevator group management control apparatus according to this invention ; Fig. 34 is the middle part of a flowchart showing the operation steps of the reversing car determination device used in the twenty-first embodiment of the elevator group management control apparatus according to this invention ; Fig. 35 is the last part of a flowchart showing the operation steps of the reversing car determination device used in the twenty-first embodiment of the elevator group management control apparatus according to this invention ; Fig. 36 is a diagram showing the configuration of the reversing car determination device used in the twenty-second embodiment of the elevator group management control apparatus according to this invention ; Fig. 37 is the first part of a flowchart showing the operation steps of the reversing car determination device used in the twenty-second embodiment of the elevator group management control apparatus according to this invention ; Fig. 38 is the middle part of a flowchart showing the operation steps of the reversing car determination device used in the twenty-second embodiment of the elevator group management control apparatus according to this invention ; Fig. 39 is the last part of a flowchart showing the operation steps of the reversing car determination device used in the twenty-second embodiment of the elevator group management control apparatus according to this invention ; Fig. 40 is a diagram explaining the operation of a conventional elevator group management control apparatus, and shows how each car moves. BEST MODE FOR CARRYING OUT THE INVENTION Referring to the drawings, there are shown some embodiments of this invention. The first to eighteenth embodiments relate to an invention to achieve the object described above. In those embodiments, the route along which each car moves is pre-defined because it moves in each shaft in one direction only and, therefore, it is possible to estimate how long it will take for each car to arrive at a floor requested by a station call or a car call. This estimated time is used to calculate a time to respond to a call (wait time) or a service time (time from when a station call is received to when a car arrives at a requested floor) and, based on these calculated times, a new station call is assigned to a car which will be able to respond to the call first. The nineteenth to twenty-second embodiments relate to optional preferred features of the invention. In those embodiments, the direction of a shaft may be changed as necessary to allow a car to be reversed. This makes it possible to assign a station call to a car, which will be able to respond to a new station call first, without being limited by the direction of a shaft. It is to be noted that in the explanation of each of the embodiments presented below, it is assumed that at their current positions, all the cars are in a stationary state. The reason for this is that if a car is not in a stationary state, the indicated current position of the car relative to a call is not always the actual location where the car is being operated. In addition, from the perspective of ensuring operational safety, it is also necessary to take into consideration the position where an immediate stop is possible in response to a stop instruction (sometimes referred to as an advancer position). Consequently, in regard to a car data detection device 2 in each of the following embodiments, too, it is assumed that it detects an advancer position as a "current position" based upon the actual current position and the current speed and unless specifically stated otherwise, the current position as referred to in this specification means the "advancer position". However, if a car is in a stationary state, the current position equals "current position (advancer position)". [1. First Embodiment] This embodiment relates to an elevator group management control apparatus corresponding to recitation of claim 1 and an elevator group management control method as preferably employed therein. [1-1. Configuration of the First Embodiment] Fig. 1 is a diagram showing a configuration of a longitudinal/transverse movable elevator group management control apparatus in accordance with the first embodiment of the present invention. As shown in this drawing, the elevator group control apparatus in accordance with this embodiment is made up of a station call registration device 1 provided at a landing-place or "station" on each floor in the building, a car data detection device 2 for detection of "car data" indicative of each car's position, moving speed, weight and others, an elevator group management control apparatus 3 for acquisition of command data for use in controlling the individual car based on various kinds of information as obtained from the station call registration device 1 and car data detection device 2, and a car operation control device 4 for controlling cars' traveling operation based on the command data. [1-1-1. Configuration of Elevator group management control apparatus] The elevator group management control apparatus 3 is constituted from several devices or modules shown in Fig. 2. More specifically, it is comprised of a call data storage device 21 for storage of "call data" consisting of car calls each issued by a passenger inside a car to assign his or her desired floor and one or more station calls as presently assigned; a target floor instruction device 22 which provides the "target floor data" of each car based on the "station call data (floor and direction)" registered by said station call registration device 1 and "call data" of each car as prestored in the call data storage device 21; a route data storage device 24 that stores the route along which each car is to travel, as the "route data"; an arrival time estimation device 23 which calculates or computes for every car the time taken for each car to reach its target floor based on the "car data" of each car as obtained by said car data detection device 2, the "call data" of each car acquired from the call data storage device 21, the "target floor data" of each car obtained from the target floor instruction device 22, and the "route data" read out of the route data storage device 24, thus generating and issuing at its output the resulting value as an estimated arrival time; an assignment instruction device 25 which attempts to assign a call to a certain car based on the estimated arrival time for the target floor as estimated in said arrival time estimation device 23, while updating the "call data" being stored in said call data storage device 21; and, an operation instruction device 26 which determines depending upon car's present operating condition whether its expected stop or "landing" position instructed by the assignment instruction device 25 serves newly as a successive stop or landing position, and which issues a command to the car operation control device 4 thereby altering or modifying car's traveling operation on occasions where it becomes the next stop position. [1-2. Operation of the First Embodiment] The first embodiment thus arranged operates as follows. [1-2-1. Call Data Storage Processing] In the call data storage device 21 shown in Fig. 2, the call type, floor, direction and elapsed time are stored as the "call data" with respect to each car in a specific format shown in Table 1. Note here that the "call type" is for identification of a call from station "H" or a call from car "C" whereas the "floor" represents either the floor of a station call as presently assigned or the one being subject to a car call (a floor whereat more than one passenger wants to get off). Also, the "direction" indicates whether the car's moving direction is upward "UP" or downward "DN" whereas the "elapsed time" refers to the actual elapsed time taken from occurrence of such call to a present time. For example, in Table 1, the "call data" as defined by (H 16 DN 5) for one car E1 represents an event that "a downward station call is generated on the sixteenth floor after elapse of five seconds from call generation"; the "call data" as defined by (C 9 DN 22) for another car E2 indicates an event that "car E2 contains at least one passenger who wants to land on the ninth floor after a downward run with a car call registered 22 seconds before." Note that said "elapsed time" may be updated by registration, deletion or search of the "call data." [1-2-2. Target Floor Instruction Processing] In the target floor instruction device 22 shown in Fig. 2, the "target floor data" is obtained by a preselected method based on the "station call data (floor and direction)" registered by the station call registration device 1 and each car's "call data" as stored in the call data storage device 21. Table 2 below shows one exemplary "target floor data" obtained. While Table 2 indicates the case where one or more passengers who want an up-going elevator are on the fifth floor, the both cars are "null" in the "assignment" item because no practical assignment was done yet. Additionally, these "target floor data" items are arranged so as to be sent forth toward an arrival time estimation device 23 as will be described later. [1-2-3. Route Data Storage Processing] The route data storage device 24 shown in Fig. 2 stores therein any possible route along which each car is expected to move or travel, as the "route data." Fig. 3 is a diagram for explanation of one route along which each car is required to move. For instance, in a building structure with twenty floors and four associated vertical lift passages or "shafts," one transportation route is illustrated using dotted line, wherein a car that is presently at the level of the twentieth floor in the fourth shaft is expected to respond to an upward station call as generated on the fifth floor. Specifically, one possible route to respond such station call is that the subject car moves down in the fourth shaft to the tenth floor (M1), then transversely moves to shift to the third shaft at the level of the tenth floor (M2), next goes down to the first floor (M3), further moves to the second shaft on the first floor (M4), and finally moves up to the fifth floor in the second shaft. Where a transportation route is defined with respect to each car, such data is stored as the "route data" in the form shown in Table 3. For example, the "route data" for car E1 means that one route is given to the car E1 as a presently required moving path which follows: the transverse-shifting floor is the first, tenth and twentieth ones; at the first-floor level, the car is required to transversely move thus shifting from the third to the second shaft; on the twentieth floor, it is expected to transversely move shifting from the second to the fourth shaft; at the tenth floor, it transversely shifts from the fourth to the third shaft. [1-2-4. Arrival Time Estimation Processing] In the arrival time estimation device 23 shown in Fig. 2, the time taken for each car to reach its certain target floor is calculated with respect to every car based on four kinds of data items which follow: the "car data" of each car as obtained from said car data detection device 2, each car's "call data" obtained from the call data storage device 21, each car's "target floor data" obtained from the target floor instruction device 22, and the "route data" read from the route data storage device 24. The resulting values are then output as the estimated arrival time to the assignment instruction device 25. It should be noted in the illustrative embodiment that the estimation of arrival time for a given car toward its target floor is performed under the assumption that the remaining cars excluding the subject car do not have any newly entered station calls as their target station data. In other words, on occasions where one certain car should respond to a new station call, this means that the other cars will not respond to such station call any more. More specifically, the other cars do not have as the target station data any stop positions excluding the floors relating to the car/station calls which have been already stored in the call data storage device 21. It is also assumed that in a later described fourth embodiment, when derivative car call estimation is to be done, any stop or "land-on" positions other than the car/station/derivative-car calls are prevented from acting as the target floor data. It is further assumed that the maximum velocity, acceleration, deceleration, door's open/close time durations and the time required for cars to move are all predefined as the specific standardized values. One preferable arrival time estimation scheme will be described later in the description. [1-2-5. Assignment Instruction Processing] In the assignment instruction device 25 shown in Fig. 2, a call is assigned to a certain car based on the resultant estimated arrival time to the target floor as estimated at said arrival time estimation device 23, while allowing the contents of the call data storage device 21 to be updated as necessary. The following example is drawn to the case where a certain car is assigned by the assignment instruction device 25, updating the "call data" stored in the call data storage device 21. Table 4 indicates the situation that each car's arrival time is estimated by a later-described method with respect to the "target floor data" shown in Table 2, and, based on resultant estimated arrival time, the car E2 is assigned to the station call "5 UP" while updating the "call data" stored in the call data storage device 21. Specifically, it may be apparent from comparison with the "call data" shown in Table 1 that the last data stream ( H 5 UP 0) is added to car E2. [1-2-6. Operation Instruction Processing] The operation instruction device 26 shown in Fig. 2 operates to judge or determine whether the presently expected stop position as commanded by said assignment instruction device 25 will possibly become the next stop position by taking account of car's present operating/traveling condition, and to generate and provide a necessary command(s) to the car operation control device 4 thereby altering or modifying car's traveling operation, on occasions where the presently expected stop position is judged to become the next stop position. [1-2-7. Arrival Time Estimation Processing] A description will now be given of the estimation processing as to each car's arrival time. Note here that the "arrival time estimation" may refer to the procedure of calculating or computing the time required for each car to reach its target floor; for example, when the "target floor data" shown in Table 2 is entered as input data, such estimation is done with the target floor of cars E1, E2 being set at (5 UP). Assume that the 20-floored building structure having four elevator shafts is equipped with cars E1, E2 as shown in Fig. 4. Assume also that car E1 is presently at the twentieth floor in the fourth shaft whereas car E2 stops at the fifteenth floor in the third shaft, wherein each car is in the condition capable of rapidly closing its door for departure. Note that although the departure wait state is assumed for execution of arrival time estimation, this is not any exclusive case and permits employment of any other possible assumptions indicating a given car's state. Consider that, as station calls, (H 16 DN) and (H 3 UP) are assigned to the cars E1, E2 respectively, and also that, as car calls, (C 12 DN) and (C 4 DN) are similarly assigned to car E1 whereas (C 9 DN) is to car E2 while such data items are stored in the call data storage device 21. Further assume that each car is with the "route data" of Fig. 4 as defined therein. Under the above setting conditions, there are two possible ways of estimation due to the fact that one specific condition as to "prohibition of inclusion of any new station call in other cars' target floors whenever such station call is assigned to one car." More specifically, the first situation is that when car E1 is assigned to a new station call namely, car E1 now regards as its target floor the floor whereat such new station call takes place whereas car E2 does not regard such floor as its target floor, estimation is performed to define the time required for car E1 to arrive at (5 UP). Alternatively, the second situation is that when a new station call is assigned to car E2 i.e., car E2 regards the floor concerning occurrence of such new station call as its target floor whereas car E1 does not regard such floor as its target floor, estimation is done to define the time as required for car E2 to reach (5 UP). Next, Fig. 5 is a diagram for explanation of the flow of operation processing as executed by the arrival time estimation device 23, wherein the arrival time estimation device 23 operates to estimate the arrival time as pursuant to the task procedure shown in this drawing. The arrival-time calculation scheme will be discussed in the above first situation in connection with the flowchart shown in Fig. 5. As shown in Fig. 5, the arrival time estimation device 23 first selects a car under estimation (at step 51). In the illustrative embodiment, car E1 will be selected first. Then, the expected stop position is calculated for each car based on the "route data" and "target floor data" as stored in the route data storage device 24 (at step 52). In this embodiment the expected stop positions of cars E1, E2 are as shown in Table 5. Note that in Table 5, "16@4" represents the level of the sixteenth floor in the fourth shaft. Car E1: 16@4, 12@4, 10@4, 10@3, 4@3, 1@3, 1@2, 5@2 Car E2: 9@3, 1@3, 1@2, 3@2 Next, a car(s) is selected and extracted which is kept unknown of any arrival time calculated at its all expected stop positions (step 53). Assume here that car E1 is selected for extraction. Subsequently, a check is made to determine if there is the possibility that the selected car will collide against another car (step 54). In this embodiment determination is made to point out that collision will possibly take place between cars E1, E2 due to the fact that such two cars are both required to move in the third shaft, as shown in Table 5. When decision is made at step 54 to indicate that "collision will possibly happen" in the aforesaid way, an expected collision occurrence position is then calculated (at step 55). This collision occurrence position may be obtained by calculation from a present position of each car and its expected stop position. In this embodiment it will be estimated that collision occurs between cars E1, E2 at the 10@3 position. Next, the time required for arrival is calculated at step 56 with respect to the individual car being specified as an object of interest (that is, car El) and any car that can collide therewith (car E2). More specifically, regarding the car E1, calculation is sequentially carried out as shown in Table 6. Note here that in this embodiment, the time taken for passengers to ride on and get off is neglected for purposes of simplicity only. Arrival Time to 16@4: Door Close Time + (20@4→16@4 Transit Time) + Door Open Time Arrival Time to 12@4: Arrival Time to 16@4 + Door Close Time + (16@4→12@4 Transit Time) + Door Open Time Arrival Time to 10@4: Arrival Time to 12@4 + Door Close Time + (12@4→10@4 Transit Time) + Door Open Time Arrival Time to 10@3: Arrival Time to 10@4 + Door Close Time + (10@4→10@3 Transit Time) + Door Open Time Now, representing the door open time as "to," the door close time as "t c ," the time required for floor-to-floor movement as "t v i,j " (i, j designate floor numbers respectively, where i≠j), and the time required for transverse shift as "t h l,m " (l, m denote shaft numbers respectively, where l≠m), the time t1 (20@4→10@3) as taken for car E1 to reach the estimated collision occurrence position 10@3 is given as [Formula 1] t 1 = t υ 20,16 + t υ 16,12 + t υ 12,10 + t h 4,3 + 4 × ( t c + t o ) Note here that t v i,j and t h l,m are given in advance by use of a predetermined equation. For example, in the case of vertical transportation, assuming that the cars are given with specific standards as to the maximum velocity v MAX , acceleration "a", floor-to-floor distance "d", the time may be calculated using the following equation: Note in this embodiment that the transit time and door open/close time are to be determined for purposes of simplicity as follows: [Formula 3] t υ i,j : ( i-j +3) sec . ( i ≠ j ) t υ i,j : (10× l - m ) sec. DOOR OPEN TIME : 2 sec. DOOR CLOSE TIME : 2 sec . Therefore, the time t1 required for car E1 to reach the estimated collision occurrence position 10@3 is given by [Formula 4] t1 (20@4→10@3) = 7+7+5+10+4x(2+2) = 45 [sec.] On the other hand, regarding car E2, the arrival time to its estimated collision occurrence position 10@3 is defined as "door close time + (15@3→ 10@3 transit time) + door open time"; therefore, we obtain [Formula 5] t2 (15@3→10@3) = 6+(2+2) = 10 [sec.] In this way, after completion of calculation of the arrival time to the estimated collision occurrence position, a specific one of the cars is determined which is expected to be the first in the order of arrival at the estimated collision occurrence position 10@3. Namely, in this embodiment, the car with the minimum arrival time that is, the car E2 is identified as the first one in the sequence of arrival at the estimated collision occurrence position. For the other car (here, car E1) other than the determined first-order car, a predefined time tp is added to its 10@3 arrival time as a penalty (at step 57). Note that it can be happen that respective cars are kept unchanged in the expected stop positions thereof; if this is the case, it is then assumed that these cars will not collide with each other because of complete absence of any crossing points between the expected stop positions thereof. In this way, after completion of predetermined calculation with respect to cars with some possibility to collide (steps 55 to 57), the routine goes back to step 53 for further execution of similar analysis for checking the possibility of collision. At step 53, if decision is made to confirm that "there is no possibility of collision," further calculation is executed to define the arrival time at certain expected stop position with respect to the car(s) of interest (at step 58). Here, for car E1, the arrival time to each position 4@3, 1@3, 1@2, 5@2 will be obtained. The calculation scheme in this case is the same as the one described above. Arrival Time to 4@3: Arrival Time to 10@3 + Door Close Time + (10@3→4@3 Transit Time) + Door Open Time Arrival Time to 1@3: Arrival Time to 4@3 + Door Close Time + (4@3→1@3 Transit Time) + Door Open Time Arrival Time to 1@2: Arrival Time to 1@3 + Door Close Time + (1@3→1@2 Transit Time) + Door Open Time Arrival Time to 5@2: Arrival Time to 1@2 + Door Close Time + (1@2→5@2 Transit Time) + Door Open Time Due to this, it is possible to calculate the expected arrival time of the target floor (at step 59). This can be said because such target floor is included in the expected stop or "landing" position. Consequently, the arrival time t1 of the target floor 5@2 is given by [Formula 6] t1 (20@4→5@2) = (45+tp)+9+6+10+7+4x(2+2) = 93+tp = 123 [sec.] (where, t p =30 sec.) Next, regarding the cars being presently subject to such arrival time calculation, the routine checks for whether the arrival time has been calculated with respect to all the expected stop positions (at step 60). At step 60, when decision is made such that the arrival time calculation was completed at all the expected stop positions of the subject cars, decision is then attempted at step 61 to confirm whether the above processing tasks (steps 53 to 60) are completed for all the cars. At step 61, if it is decided that the above processing tasks are not completed yet for all the cars, the routine goes back to step 51 for repeated execution of similar processing tasks. More specifically, here, the routine goes back at step 51 performing estimation of arrival time in the second situation as discussed previously. Therefore, the estimation of arrival time of car E2 in the second situation is as follows: [Formula 7] t2 (15@3→5@2) = 9+4+11+10+5+5+5x(2+2) = 60 [sec.] In this way, execution of a respective one of the steps 51 to 61 will be repeated appropriately; after completion of calculation of arrival time of all the expected stop positions with respect to every car, the system routine will be terminated. In this embodiment the arrival time to each car's target floor as estimated by the arrival time estimation device 23 is as follows: Accordingly, as has been described above, the car E2 which is less in estimated arrival time will be assigned to the (5 UP) station call, thereby enabling achievement of high efficient car transportation responsive to any station calls and car calls. In this case, all cars will be an assigned car, but it is possible to prepare unassigned car ( for example, crowded car, car for V. I. P.). [2. Second Embodiment] This embodiment relates to an elevator group management control apparatus corresponding to recitation of claim 2 and the method therefor. [2-1. Configuration of the Second Embodiment] This embodiment is one modification of said first embodiment with the target floor instruction device 22 and assignment instruction device 25 being changed in arrangement. Note that in this embodiment, target floor instruction device 22 generates and issues the "target floor data" shown in Table 2 above, whereas arrival time estimation device 23 is designed to supply assignment instruction device 25 with the "estimated arrival time" shown in Table 8. More specifically, the target floor instruction device 22 in this embodiment is so arranged as to define as a target floor any floor of station call which is newly registered in the station call registration device 1 in all the cars associated. In other words, unlike the first embodiment, this embodiment intends to estimate the time required to reach a new landing-place's floor with respect to all the cars. Also, the assignment instruction device 25 is arranged so as to calculate the nonresponse time based on the estimated arrival time as estimated by the arrival time estimation device 23 and to determine a specific car with the minimum non-response time as an assignment car which should be assigned to the nonresponse call. Note here that the "non-response time" refers to the time duration taken for a car of interest to arrive at its target floor after generation of the target floor call. [2-2. Operation/Effect of the Second Embodiment] This embodiment thus arranged operates as follows. The following description is mainly directed to the assignment instruction processing thereof, which is principally different from that of the first embodiment. When the input data of Table 2 are used to calculate each car's nonresponse time (call elapse time + estimated arrival time) with respect to the nonresponse call (5 UP), the result is as shown in Table 9. Note here that this assumes that the time (call elapse time) from issuance of a station call to determination of assignment by the assignment instruction device 25 is 0 sec. Accordingly, a car having the minimum value of nonresponse time shown in Table 9 that is, car E2 with the nonresponse time of 60 sec. is determined as the one to be assigned to the station call. With this embodiment, a specific car corresponding to the minimum nonresponse time is assigned to a station call, enabling achievement of more efficient transportation of cars associated. [3. Third Embodiment] This embodiment relates to an elevator group management control apparatus which corresponds to the recitation of claim 3 and the control method thereof. [3-1. Configuration of the Third Embodiment] This embodiment is another modification of said first embodiment with the target floor instruction device 22 and assignment instruction device 25 being changed in configuration. More specifically, the target floor instruction device 22 in this embodiment is arranged, with respect to all the cars, to define as the target floor both a floor relating to a station call as newly registered in the station call registration device 1 and all cars' station calls as stored in the call data storage device 21. Also, the assignment instruction device 25 is arranged so that it calculates the average value of nonresponse time based on the estimated arrival time as estimated by arrival time estimation device 23 to assign an unassigned call to the car which is minimum in average nonresponse time. [3-2. Operation of the Third Embodiment] The present embodiment thus arranged operates as follows. The following description is drawn to the target floor instruction processing and assignment instruction processing which constitute main differences from the first embodiment. [3-2-1. Target Floor Instruction Processing] In the target floor instruction device 22 of this embodiment, both the floor relating to the station call as newly registered in the station call registration device 1 and all car's station calls being presently stored in the call data storage device 21 are defined to the target floor with respect to all cars associated. More specifically, unlike the second embodiment, an individual one of all the cars is allowed to contain in its target floor any station call data of the remaining cars; therefore, the resulting "target floor data" is as shown in Table 10. Note here that the estimated arrival time to each car's target floor as estimated by the arrival time estimation device 23 using the "target floor data" of Table 10 may be similar to that of the first embodiment, which derives the result shown in Table 11 below. [3-2-2. Assignment Instruction Processing] In the assignment instruction device 25 of this embodiment, the average value of nonresponse time is calculated based on the estimated arrival time as estimated by the arrival time estimation device 23, then allocating the nonresponse call to a specific car which is minimum in average nonresponse time. Practically, when the input data items shown in Table 11 are used to calculate the nonresponse time for each car's call, the result is as shown in Table 12. For example, the nonresponse time for the call (16 DN) concerning the car E1 is: the elapsed time (5 sec.) + estimated arrival time (11 sec.) = 16 sec. Here, the call elapse time after generation of a new station call (5 UP) is 0 sec. At this time, the average nonresponse time when each car is assigned with the station call (5 UP) is calculated as follows. (a) Assigning to Car E1 Table 12 involves three station calls in total, one of which is (16 DN 16 sec.) in car E1, another one of which is (5 UP 123 sec.) in car E1, and the other of which is (3 UP 61 sec.) in car E2; accordingly, the average nonresponse time is represented as average nonresponse time= (16+123+61) / 3 = 66.7 sec. (b) Assigning to Car E2 Table 12 contains three station calls in total, one of which is (16 DN 16 sec.) in car E1, another one of which is (3 UP 61 sec.) in car E2, and the other of which is (5 UP 60 sec.) in car E2; therefore, the average nonresponse time is represented by average nonresponse time= (16+61+60) / 3 = 45.7 sec. Of those average nonresponse time values thus calculated, the minimum-value car, i.e., car E2 is finally determined as the assignment car to the station call (5 UP). As has been described above, according to this embodiment, calculating the average values of nonresponse time for respective target floors with respect to every car may enable accomplishment of car transportation less in variations in wait time. [4. Fourth Embodiment] This embodiment relates to an elevator group management control apparatus corresponding to claims 4 and 5 and the method thereof for use therein. [4-1. Configuration of the Fourth Embodiment] This embodiment is still another modification of said first embodiment, which employs a derivative car call estimation device 61 with the target floor instruction device 22 and assignment instruction device 25 being changed in arrangement. More specifically, the target floor instruction device 22 in this embodiment is specifically arranged such that for each car, it defines as the "target floor data" the station call floor being newly registered in the station call registration device 1, the station call floor as stored in the call data storage device 21, and a derivative car call floor as estimated by a derivative car call estimation device 61 to be described later. Also, the derivative car call estimation device 61 is so arranged as to receive at its input the "station call data" being registered in the station call registration device 1, calculate the passenger generation frequency and the average wait time at any floors relating to such station calls, and estimate a secondary car call(s) as possibly derived from each station call. Here, the "derivative car call" may relate to estimation of passenger's destination (target floor) on part of the system at a time point of registration of a station call, whereas "car call" is to registration of passenger's destination when the passenger actually gets on that car. The "passenger generation frequency" may here refer to the rate of occurrence as defined by the average time taken from completion or deletion of a station call (that is, at a time point whereat the car responded to such station call) to registration of a new station call in the past. Further, the assignment instruction device 25 is arranged so that it calculates the service completion time based on the estimated arrival time as estimated by the arrival time estimation device 23, thereby attempting to assign the unassigned call to a specific car which is minimum in service completion time. Note that the "service completion time" refers to the time interval as taken, upon occurrence of a station call, between a start time when passengers get on a car arrived and a termination time when more than one passenger gets off from the car reached his or her target floor inside the building. In other words, for passengers, their inherent motive (aim) of using the elevator is to make transportation toward their target floor; by taking this into consideration, attaining such aim is regarded as the "service completion." [4-1-1. Configuration of Derivative Car Call Estimation Device] A detailed description will now be given of a practical arrangement of the derivative car call estimation device 61 as employed in the elevator group management control apparatus, with reference to Fig. 7. The derivative car call estimation device 61 is constituted from a passenger generation frequency storage device 71, an average wait time storage device 72, a derivative car call number estimation device 73, and a derivative car call floor estimation device 74 as will be described below. Here, said passenger generation frequency storage device 71 stores therein the rate of occurrence (or frequency) of station calls on respective floors in the past, calculates a new or updated passenger generation frequency based on the past passenger generation frequency and any newly issued station call(s), updates the presently stored passenger generation frequency data, and supplies resultant information to the derivative car call number estimation device 73. The average wait time storage device 72 is designed to update pursuant to a newly occurred station call data the average wait time being presently stored in response to issuance of each station call in the past, and supplies resulting information to the derivative car call number estimation device 73. Note here that the "average wait time" refers to the average time taken from occurrence of a station call to erasure of registration thereof (i.e., from passenger's activation of a station call button on an arbitrary floor to his or her actual getting on the car reached in responding thereto). Next, the derivative car call number estimation device 73 is arranged to estimate the number "n" of derivative calls based on the "passenger generation frequency data" and "average wait time data" as input thereto, by using the following equation: [Formula 8] n = 1 + (average wait time) / (passenger generation frequency). The derivative car call floor estimation device 74 is arranged to estimate the floor on which more than one derivative car call is generated, based on the derivative car call number as estimated by said derivative car call number estimation device 73. More practically, the derivative car call floor estimation device 74 stores therein a defined distribution or scatter of derivative car calls generated at all the floors (not shown) for separate directions with respect to every floor in such a manner that it does this under the assumption that any derivative car calls occur on a floor corresponding to the accumulated scatter rate as represented by the following equation. Note here that such "derivative car call data" is erased every time when the registration of a corresponding station call is cleared―namely, when a car reached the floor whereat the station call has been issued and then a passenger who gets on it registers his or her desired car call. [Formula 9] k/(n+1) ( where k=1,..., n ) [4-2. Operation of the Fourth Embodiment] The fourth embodiment thus arranged operates as follows. [4-2-1. Derivative Car Call Estimation Processing] In the above embodiment, discussion is made under only the assumption that the station call (5 UP) is occurred, and whether a similar station call was issued in the past was withdrawn from consideration. In contrast, this embodiment assumes that such station call (5 UP) was occurred in the past, and that the station call (5 UP) was issued at a time point after 30 sec. was elapsed after the system's power-on. This may be reworded such that initiating station call's registration after elapse of 30 sec. after power-on or activation of the system means that passengers were "generated" at the rate of once per 30 sec. Consequently, at this time, the passenger generation frequency storage device 71 updates its initial value "null" to "30" providing the value "30" as the passenger generation frequency data. Note here that said passenger generation frequency storage device 71 stores therein data for every floor with the initial value therefor being set at "null." Note also that in this embodiment, no wait time is present because of occurrence of no calls in the past; accordingly, the average wait time storage device 72 updates its initial value "null" to "0" while generating and issuing it at the output thereof. Note here that this assumes that the average wait time data is updated whenever the registration of this station call is erased, that is, when more than one passenger gets on the car. Next, the derivative car call number estimation device 73 calculates the derivative car call number "n" based on the average wait time and the passenger generation frequency, by use of the following equation, and supplies the resulting value to the derivative car call floor estimation device 74. [Formula 10] n =1+(average wait time) / (passenger generation frequency) =1+ 0/30 =1 Now, assume that the derivative car call floor estimation device 74 exhibits a derivative car call generation distribution (accumulated scatter of the density distribution) shown in Table 13. Floor Accumulated Scatter Rate 19 1/14 18 2/14 17 3/14 : : 13 7/14 : : 7 13/14 6 14/14 Consequently, the accumulated scatter rate which is to be estimated so that a derivative car call occurs based on the derivative car call number n=1 as estimated by said derivative car call number estimation device 73 is given as [Formula 11] k/(n+1) = 1/(1+1) = 1+2 (where, k=1,..., n). Accordingly, it may be estimated from Table 13 that a derivative car call will occur on the thirteenth floor. This comes under the assumption that the derivative car calls concerning the already occurred station calls (16 DN), (3 UP) are one for the eleventh floor and the other for the seventh floor, respectively, while their related information is stored in the derivative car call floor estimation device 74. It should be noted that in this embodiment, although the derivative car call is estimated by the derivative car call estimation device 61 shown in Fig. 6, the present invention should not be limited exclusively to this arrangement; it may alternatively be arranged such that the derivative car call estimation device 61 prestores therein the derivative car call occurrence data for every floor, and generates at its output the data as an estimation result with respect to a corresponding floor data. Furthermore, in an elevator system that passenger can register her/his destination floor at elevator hall before getting on a car, the destination floor can be used as "derivative car call data". With such an arrangement, the data being input to the target floor instruction device 22 is as shown in Table 14. Note here that in this case also, the elapsed time of station call is 0 sec. Here, the call type "D" indicates the derivative car call. The elapsed time of "car call data" is assumed to be updated successively so that it takes over the station call's elapsed time which was erased in registration upon occurrence of a car call. For instance, in the (C 12 DN 20 1), the elapsed time "20 sec." does not intend to mean that the elapsed time from occurrence of a car call is 20 sec., but intends to mean the elapsed time from a time point whereat one passenger who made a car call attempted to register a station call in order to get on that car. [4-2-2. Target Floor Instruction Processing] The target floor instruction device 22 in this embodiment defines to the target floor a station call floor as newly registered in the station call registration device 1, a station call floor being stored in the call data storage device 21, and a derivative car call floor as estimated by the derivative car call estimation device 61. Accordingly, the "target floor data" may be as shown in the above Table 14, with respect to every floor. Also, the time required for each car to reach its target floor as estimated by the arrival time estimation device 23 using the "target floor data" shown in Table 14 is computed using the calculation scheme as presented in the first embodiment, the result of which is as follows (Table 15): [4-2-3. Assignment Instruction Processing] The assignment instruction device 25 in this embodiment operates to calculate the service completion time based on the estimated arrival time as estimated by the arrival time estimation device 23, and assign an unassigned call to one specific car which is minimum in service completion time. More specifically, in the input data shown in Table 15, the calculation result of the service completion time (call elapsed time+estimated arrival time) regarding the derivative car call (13 UP) this is estimated to occur with respect to the unassigned station call (5 UP) that each car regards as its target floor is as follows. Note here that in this case also, the elapsed time of unassigned station call is 0 sec. As a result, the station call (5 UP) will be assigned to the car E2 which is less in service completion time. As has been described above, according to this embodiment, since it is specifically arranged to estimate the derivative car call by taking account of the passenger generation frequency and the average wait time, it is possible to attain more precise or careful management of car transportation as pursuant to the actual passengers' conditions. [5. Fifth Embodiment] This embodiment relates to an elevator group management control apparatus corresponding to claim 6 and the method thereof. [5-1. Configuration and Operation of the Fifth Embodiment] This embodiment is one modification of said fourth embodiment, with the target floor instruction device 22 and assignment instruction device 25 being changed in arrangement. The derivative car call estimation device 61 may be similar to that of the fourth embodiment. More specifically, the target floor instruction device 22 in this embodiment is arranged so that with respect to all cars, it defines as the "target floor data" the station call floor as newly registered in the station call registration device 1, the station call floor as stored in the call data storage device 21, and the derivative car call floor as estimated by the derivative car call estimation device 61. Accordingly, the target floor instruction device 22 of this embodiment is different from that of the fourth embodiment in that it includes in its target floor the "call data" of other cars, so that the resultant "target floor data" is as shown in Table 17. Note that in the following Table, data added with "*" are the "call data" relating to the other cars. Note also that the call elapse time from occurrence of the new station call (5 UP) is assumed to be 0 sec. As pursuant to this Table 17, the estimated arrival time may be calculated by the arrival time estimation device 23, the result of which is as follows. Note here that the following result assumes that the estimated arrival time is calculated in the same way as in the first embodiment. On the other hand, the assignment instruction device 25 in this embodiment is arranged so that it calculates the average value of each service completion time based on the estimated arrival time as estimated by the arrival time estimation device 23, and assigns an unassigned call to a specific car that remains minimum in average service completion time. Specifically, the service completion time (call elapse time + estimated arrival time) as to the car call/derivative car call of each car's target floor may be calculated based on Table 18, the result of which is as follows: Here, the average value of each service completion time on occasions where car E1 is assigned with the new station call (5 UP) may be calculated as follows. It can be seen from Table 19 that the car call/derivative car call on such occasions where the car E1 is assigned with the new station call (5 UP) are six: (C 12 DN 42), (D 11 DN 35), (C 4 DN 115), (D 13 UP 145) for car E1; (C 9 DN 45), (D 7 UP 72) for car E2. Therefore, the average value of each service completion time here is (42+35+115+145+45+72) / 6=75.6 sec. On the other hand, the average value of each service completion time in the case where the car E2 is assigned with the new station call (5 UP) may be calculated as follows. As can be seen from Table 19, the car call/derivative car call in the case where car E2 is assigned with the new station call (5 UP) are six: (C 12 DN 42), (D 11 DN 35), (C 4 DN 115) for car E1; (C 9 DN 45), (D 7 UP 72), (D 13 UP 82) for car E2. Therefore, the average value of each service completion time here is (42+35+115+45+72+82) / 6=65.1 sec. As a result, the station call (5 UP) will be assigned to the car E2 which is less in average value of each service completion time than car E1. It can be seen from the foregoing discussion that with the present embodiment, it becomes possible to accomplish successful management of car transportation of less variations due to the feature that the average value of individual service completion time is calculated regarding each target floor with respect to every car. [6. Sixth Embodiment] This embodiment is one modification of said third embodiment with the assignment instruction device 25 being changed in arrangement, wherein the target floor instruction device 22 is similar to that of the third embodiment while assuming that the arrival time estimation device 23 supplies the assignment instruction device 25 with the estimated arrival time data shown in Table 11. [6-1. Configuration and Operation of the Sixth Embodiment] The assignment instruction device 25 in this embodiment is arranged to compare maximal values of nonresponse times as calculated for respective cars and to assign a specific car that is minimum in such value to a new station call. More specifically, it calculates the nonresponse time data of each car shown in Table 12 based on the input data shown in Table 11, compares the maximal nonresponse time value (123 sec.) of car E1 with that (61 sec.) of car E2, and then assigns to the latter car E2 which is minimal in nonresponse time. [7. Seventh Embodiment] This embodiment is one modification of said fourth and fifth embodiments with the assignment instruction device 25 being changed in arrangement. Note that the following explanation of this embodiment will employ the estimated arrival time data shown in Table 18. [7-1. Configuration and Operation of the Seventh Embodiment] The assignment instruction device 25 of this embodiment is arranged so that it compares several maximal values of the service completion times as calculated for respective cars, causing one specific car being minimum in such value to be assigned to a new station call. More specifically, it calculates the service completion time of each car shown in Table 19 based on the input data shown in Table 18, and compares the maximal service completion time value (145 sec.) of car E1 with that (115 sec.) of car E2, letting the car E2 which is minimum in service completion time be assigned. [8. Eighth Embodiment] This embodiment is a further modification of said first embodiment with a transportation condition data storage device 81, an additional estimation command device 82, and a route change command device 83 being provided in addition to the basic configuration of the first embodiment. [8-1. Configuration of the Eighth Embodiment] More specifically, as shown in Fig. 8, the transportation condition data storage device 81 in this embodiment is arranged so that it stores therein other car's data as present along a selected route with respect to every car, based on each car's "position data" as obtained from the car data detection device 2 and each car's "route data" being stored in the route data storage device 24. The additional estimation command device 82 is arranged so that, in responding to a newly occurred station call, it provides other route candidates based on each car's actual operating condition, and generates and issues to the arrival time estimation device 23 a command that forces estimation of the arrival time to get started in the case where the car will move for transportation along such new route. Further, the route change command device 83 is arranged so that when a new station call is assigned to a certain car moving along the new route, the route change command device 83 issues a command forcing the old "route data" stored in the route data storage device 24 to be replaced with new "route data." [8-2. Operation of the Eighth Embodiment] The eighth embodiment thus arranged operates as follows. [8-2-1. Transportation Condition Data Storage Processing] In the transportation condition data storage device 81 of this embodiment, other cars' data along a route may be stored therein with respect to every car, based on each car's "position data" and "route data." Note that the following description of this embodiment assumes that the route data storage device 24 stores therein the "route data" as will be indicated in Table 20 below. Table 21 below shows the "position data" of each car as detected by the car data detection device 2. From the above tables, the transportation condition data storage device 81 stores therein the other car's data along the route shown in Table 22. As apparent from viewing Fig. 4 also, the both cars are not presently on the route so that each data item is "null." Now, assuming that the car E2 is at the level corresponding to the fifth floor in the third shaft, the resulting transportation condition data may be as follows: The above tells that car E2 is present on the E1's route (10@3) to (1@3) as the transportation condition data concerning car E1. By contrast, car E2 remains as "null" because car E1 is not on the route. [8-2-2. Additional Estimation Command Processing] The additional estimation command device 82 of this embodiment, is arranged so that, in responding to a newly occurred station call, it provides other route candidates based on each car's actual operating condition, and generates and issues to the arrival time estimation device 23 a command that forces estimation of the arrival time to get started in the case where the car will move for transportation along such new route. Here, a further description will be given by use of the second embodiment described previously (i.e. the case where the assignment is operated based on the minimum nonresponse time). At a present, in response to a new station call of (5 UP), each car is controlled to move or travel to satisfy its expected stop position shown in Table 24, based on the "route data" shown in Table 20. However, each car is enabled to move into a different shaft that is out of the predefined route by transversely shifting at a transverse-shift floor of the tenth floor. This may be reworded such that it is possible to set in the cars E1, E2 a new route shown in Table 25. This can be said because car E1 is enabled to go down to the first floor in the fourth shaft, without transverse movement on the tenth floor of the fourth shaft, then transversely shifting to the second shaft; car E2 is also allowed to transversely shift from the third shaft to the fourth shaft at the tenth floor, then downgoing from the tenth floor to the first floor in the fourth shaft so that it transversely shifts to the second shaft. In this way, in the case of transportation along a new route shown in Table 25, the other car is presently absent in either route from the "position data" of respective car shown in Table 21; however, regarding car E2, it results in a detour or "roundabout" route as compared with the presently defined route. Regarding car E2, since no other cars are present even in the defined route, setting of any new route is not carried out; only for the car E1, the "route data" shown in Table 26 is identified as a new route. In the second embodiment as mentioned earlier, the "target floor data" shown in Table 2 is supplied to the arrival time estimation device 23; in this embodiment, the "target floor data" of Table 27 is added to the arrival time estimation device 23 as a result of setting of the new route in the additional estimation command device 82. Next, the arrival time estimation device 23 attempts to estimate the arrival time shown in Table 28 by use of the calculation routine similar to that of the second embodiment. Note that since there is the possibility that the car E1a will collide with car E2 at (1@3), the estimated arrival time remains identical to that of car E1. In this case, the assignment instruction device 25 will assign or allocate the car E2 with the minimum nonresponse time to a new station call of (5 UP). Now, assume that the car E1a is minimized in nonresponse time while car E1a is to be assigned to a new station call. In this case, the route change command device 83 issues a command letting the "route data" stored in the route data storage device 24 be modified or updated to the "route data" of car E1a (the route data shown in Table 26). As has been described above, in accordance with this embodiment, it becomes possible to set a new route for each car while enabling selection of one specific car which is minimum in nonresponse time; therefore, more efficient management of car transportation can be accomplished. [9. Ninth Embodiment] This embodiment is one possible modification of said eighth embodiment with a transportation condition identifying device 91 being added to the basic configuration of the eighth embodiment (see Fig. 9). It should be noted that in contrast to the situation of the eighth embodiment, a car E3 is assumed to remain stationary 30 seconds before at the level of the seventeenth floor in the fourth shaft. In this case the transportation condition data indicative of cars' actual operating conditions may be as follows. [9-1. Configuration of the Ninth Embodiment] The transportation condition identifying device 91 in this embodiment is arranged so that it identifies whether delay or congestion is happening along the route in the transportation situation as obtained from the transportation condition data storage device 81. In the building model (Fig. 3) used in the first embodiment, a decision as delay or congestion is to be made in the cases which follow: first, when a car of interest remains stationary for more than 20 seconds; second, when two or more cars are operating in the region between adjacent upper and lower transverse-shift floors of the same shaft (for example, between the tenth and twentieth floors of the third shaft in Fig. 3). The definition of delay and congestion are established according to each building. Accordingly, the car E3 is determined from Table 29 to be in the locally crowded or congested situation; regarding car E1, the "delay/congestion data" is issued as shown in Table 30. In addition, the additional estimation command device 82 operates, if a route including such delay/congestion is found in the data obtained from the transportation condition identifying device 91, to set an appropriate route which is modifiable from a present position and has no delay/congestion and issue a command causing the arrival time estimation device 23 to begin estimating a possible arrival time of the car being expected to move along such new or updated route. In Table 30 above, delay and/or congestion is being occurred in the route of car E1. However, since a present position of car E1 is 20@4 while it is in the transverse-shift floor, any rapid route change remains available therefor. In short, a newly set route is as follows: Note that while the present position of car E1 is out of such new route at this time, it should be conditioned that the car attempts to move along the new route after movement toward its nearest position on the new route. Note also that in this embodiment, the estimation of arrival time is not performed in response to receipt of any newly occurred station call; rather, the arrival-time estimation for the presently assigned station call and/or car calls is to be effected with respect to a limited car(s) being subject to the route change. Note further that evaluation in the assignment instruction device 25 is made based on the minimum nonresponse time as has been employed in the second embodiment discussed previously. Additionally, in view of the fact that such evaluation does not correspond to any new station call, while the "target floor data" is determined by identifying as the target floor the farthest station from car's present position from among those of car E1's "target floor data" as obtained from the target floor instruction device 22, the arrival time estimation device 23 defines the "target floor data" shown in Table 32 with regard to the car E1. This was done under the assumption that the station call on the fifth floor is assigned to car E2. Assuming that the penalty time due to delay/congestion is 30 sec., the estimated arrival time is as follows: It should be here noted that some practical hardware limitations due to correlation between linear motor's power-on territories or the like are withdrawn from consideration, including a conditional limitation such as "when one car is at fifteenth floor, another car is incapable of approaching its related one-level upper/lower floors", for example. In this way, with this embodiment, on occasions where the nonresponse time is 30 sec. for car E1a as derived from the result of Table 33 which is less than that in the case of car E1, the route change will be done in such a manner that assignment instruction device 25 attempts to set the new route shown in Table 31 while route change command device 83 issues a command changing or modifying the "route data" of route data storage device 24. [10. Tenth Embodiment] This embodiment is a further modification of said first embodiment with a specific region identifying device 101 and a pattern transportation command device 102 being added to the basic configuration of the first embodiment. More specifically, as shown in Fig. 10, the specific region identifying device 101 determines if each car is within a predefined region or zone, based on the "position data" thereof as obtained from the car data detection device 2. Here, the indication (1 3 1 1) refers to (Floor Shaft Floor Shaft), which in turn represents the block of from 1@3 to 1@1 (i.e., from the first floor of the third shaft to the first floor of the first shaft). Accordingly, if (1 3 1 1) is a specific region, the result is that cars E1, E2 are both absent in such specific region at least at present. This can be said because as shown in Fig. 4, cars E1, E2 are at 20@4, 15@3, respectively. Now imagine that the car E1 is transversely moving in (1 3 1 2). This means that at least one car exists within such specific region; therefore, the pattern shown in Table 34 will be sent forth to the pattern transportation command device 102. Next, the pattern transportation command device 102 generates and issues at its output one special route as to the car being presently in the specific region, irrespective of the "route data" as stored in the route data storage device 24. For instance, since car E1 is in the specific region in the case of Table 34, the special route is defined as the data indicated in Table 35 while allowing this information to be sent forth to the arrival time estimation device 23. Note that the arrival time estimation device 23 is designed such that when the aforesaid special route is set (when car E1 is in the specific region), the arrival time estimation device 23 defines the route shown in Table 35 in the alternative of the "route data" of car E1 as obtained from the route data storage device 24, while excluding execution of any transportation other than the special route. [11. Eleventh Embodiment] This embodiment is a yet further modification of said first embodiment with a station call frequency identifying device 111 and a redundant or double-assignment instruction device 112 being added to the basic configuration of the first embodiment. More specifically, as shown in Fig. 11, the station call frequency identifying device 111 is arranged so that it identifies the frequency when registration and deletion of the same-floor/same-direction station calls are repeated at prescribed intervals in the station call registration device 1, and then calculates it as the "frequency data." One example is that where the (5 UP) station call is registered, if (5 UP) was once registered in the past, and if the registration record was happened to be erased in response to such call, the station call frequency identifying device 111 operates to identify the frequency thereof and calculates it as the "frequency data." More practically, the station call frequency identifying device 111 attempts to calculate the average value of the time as taken from registration of a station call of the same-floor/same-direction until erasure thereof. Additionally, this embodiment assumes that the repeat time interval (average value) is 30 sec. The double-assignment instruction device 112 supplies, based on the "frequency data" obtained by said station call frequency identifying device 111, a command to the assignment instruction device 25 to ensure that a certain number of cars shown in Table 36 is assigned to the station call. Repeat Interval Number of cars ∞ ∼ 4 O 1 4 O ∼ 2 O 2 ... ... In the above example the double-assignment instruction device 112 assigns two specific cars to the station call (5 UP) as pursuant to Table 36 then issuing the command shown in Table 37 below. The assignment instruction device 25 employs the preselected evaluation method as described in connection with the above-mentioned embodiments, for assigning to the station call a corresponding number of cars as instructed from the double-assignment instruction device 112. [12. Twelfth Embodiment] This embodiment is a further modification of said first embodiment with a car separation calculating device 121 and a top-car ignorance assignment command device 122 being added to the basic configuration of the first embodiment. More specifically, as shown in Fig. 12, the car separation calculating device 121 calculates the distance between cars, based on each car's "position data" as obtained from car data detection device 2. Here, the car-to-car distance may be defined by the floor shift number required to arrive along the route at the floor of interest whereat a car resides. For example, as per the building model shown in Fig. 4, the car-to-car distance is as follows: Car-to-car Distance E 2 - E 1 5 E 1 - E 2 35 The top-car ignorance assignment command device 122 is designed to determine based on said "car-to-car distance data" whether the car of interest is spaced apart from its successive car by more than a predefined distance; when a decision is made affirmatively (i.e., the cars are spaced apart from each other by more than the predefined distance), the top-car ignorance assignment command device 122 issues a command letting assignment instruction device 25 disable execution of new or additional assignment of a station call to the subject car. In the case of Table 38, since no cars are in the upgoing shaft, estimation is made to tell the impossibility of any quick reply to future occurrence of an upgoing station call(s). Then, such new station call is assigned not to the car E2 which remains satisfiable to the present call situation, but to the car E1. Also, in order to render the car E2 quick responsive to any possible occurrence of station calls in future, the embodiment apparatus is arranged so that any station calls will not be assigned to car E2 as spaced far from the top or leading car E1. [13. Thirteenth Embodiment] This embodiment is a further modification of said first embodiment with a transportation condition data storage device 131, an assignment exclusion car instruction device 132, and a specific-region identifying device 133 being added to the basic configuration of the first embodiment. More specifically, as shown in Fig. 13, the transportation condition data storage device 131 is arranged such that it stores, in substantially the same way as in the eighth embodiment, the other-car data as present on the route with respect to every car, based on each car's "position data" as obtained from car data detection device 2 and each car's "route data" as stored in route data storage device 24. Here, this embodiment assumes that the "route data" stored in route data storage device 24 is the same as that shown in Table 20, whereas the car positions as detected by car data detection device 2 is the same as that shown in Table 21. The specific-region identifying device 133 identifies, in substantially the same way as in the tenth embodiment, whether a car is within the predefined range based on each car's "position data" obtained from car data detection device 2. One example is that assuming the specific region is (10 4 1 4), the cars E1, E2 shown in Fig. 3 are identified to be absent in the specific region because these cars are presently at 20@4, 15@3, respectively. Assume that the car E1 is moving in (10 4 1 4). This means that car E1 is residing within the specific region; accordingly, the specific-region identifying device 133 issues the data shown in Table 39. Further, the assignment exclusion car instruction device 132 operates to determine whether the car being in the specific region is in a prescribed situation of transportation or not ; if a car is found which satisfies such condition, the assignment exclusion car instruction device 132 supplies assignment instruction device 25 with a command forcing inhibition of any new assignment of station calls. Now, consider that the car E1 is traveling in (10 4 1 4) as shown in Table 39 whereas car E2 is moving in (10 3 1 3). In this case, as can be seen from the route of car E1, while this car E1 attempts to transversely shift at the first floor after arrival at 1@4, car E2 is presently moving in (10 3 1 3); therefore, such car E1's transverse movement can be significantly affected due to car E2's operating condition, which will render difficult the estimation of car E1's transportation. To avoid such difficulty, this embodiment is specifically arranged so that appropriate car identification is made while forcing the assignment instruction device 25 to exclude a car(s) being presently within the region that is locally difficult in executing transportation estimation from a queue of one or more objects being assigned to station calls in this embodiment, car E1 is selected therefor. [14. Fourteenth Embodiment] This embodiment is a further modification of said first embodiment with a reassignment command device 141 being added to the basic configuration of the first embodiment, as shown in Fig. 14. This embodiment comes with the ability to reassign a car on specific occasions. More specifically, assume that the car E1 which is presently assigned to the station call (4 DN) is going down in the third shaft in order to reach and land on the seventh floor relating to issuance of a car call. On the other hand, car E2 is downgoing in the fourth shaft, wherein neither station calls nor car calls are occurred for car E2 till the fourth floor at a time when it has passed the seventh floor. In the situation, the car E2 will be expected to first reach the fourth floor; accordingly, with this embodiment, the call (4 DN) is reassigned to car E2. On such occasion the reassignment command device 141 operates to detect any car's positional change based on the car's "position data" as detected by the car data detection device 2, to detect any change in the station call's registration/deletion data as obtained from station call registration device 1, and to issue a command letting arrival time estimation device 23 review the assignment as to the station call for which car assignment has already been determined. In the exemplary case, the reassignment command device 141 attempts first to detect that the positional relation between cars E1, E2 is changed and detected by car data detection device 2; then, the reassignment command device 141 provides a command forcing the arrival time estimation device 23 to begin estimating any possible arrival time concerning the station call (4 DN). In responding to this, the arrival time estimation device 23 initiates again the estimation of an arrival time with (4 DN) being as a target floor. At this time, assignment instruction device 25 executes reevaluation the already assigned station call(s) based on the estimation result as given from arrival time estimation device 23, then reallocating an appropriate car. For such reassignment, the evaluation scheme using the minimum nonresponse time may be employed as in the second embodiment. Additionally, in the present embodiment, car E2 will be subject to reassignment. [15. Fifteenth Embodiment] This embodiment is a further modification of said first embodiment with a station call selection device 151 and a station call assignment/distribution command device 152 being added to the first embodiment, as shown in Fig. 15. This embodiment is with the ability to reassign a specific kind of call to a different car on occasions where a certain one of the cars can adversely affect the transportation of the remaining cars. By way of example, consider that the cars E1, E2 are downgoing at the ninth and the twelfth floors in the third shaft respectively while car E1 is expected to stop at the eighth floor. Imagine also that car E1 is assigned with several calls (6 DN), (5 DN), (4 DN) and (3 DN). In such case, car E1's response to a call can adversely affect successful transportation of car E2. To avoid this, two calls for example, (6 DN), (5 DN) of those calls (6 DN), (5 DN), (4 DN) and (3 DN) are reassigned to car E2, enabling achievement of increased transportation efficiency of cars E1, E2 as a whole. More specifically, in this embodiment, the station call selection device 151 determines, based on the "call data" as obtained from call data storage device 21, whether a car is present upon which the station assignment tasks are locally concentrated; if such car is found, the station call selection device 151 identifies one or several station calls under distribution, thus enabling scatter of certain ones of the concentrated station calls among associative cars including another car(s). The selection standards or criteria being preferably employed here may be as follows: (1) Determine the number of those calls to be subject to reassignment rendering the number of calls owned by a presently assigned car equal to that of any newly assigned car. (2) Regarding a car that will delay issuing its response, suppress or eliminate execution of reassignment if possible. In the above example, the calls (4 DN), (3 DN) are applicable. (3) Do not change the call indicating car's next stop position. In the above example, there is applicable the case where the transportation is being effected with car E1's next stop position being defined as the sixth floor. The station call assignment/distribution command device 152 operates, when the station call assigned by station call selection device 151 is distributed and moved to another car, to issue a command letting arrival time estimation device 23 perform estimation of arrival time of the other car at its intended floor. In the above example, the arrival time of each car (here, car E2 only) is estimated by arrival time estimation device 23 while recognizing as the target floors the calls (6 DN), (5 DN) selected by station call selection device 151. The assignment instruction device 25 is responsive to the estimated result of arrival time estimation device 23 for reallocating the already assigned station calls to those cars other than the assigned car as pursuant to a predefined evaluation scheme. The evaluation may be carried out in accordance with the minimum average nonresponse time as discussed previously in connection with the third embodiment. [16. Sixteenth Embodiment] This embodiment is a further modification of said first embodiment with a route setting device 161 being added to the basic configuration of the first embodiment. More specifically, as shown in Fig. 16, the route setting device 161 holds therein any transportable routes as "candidates" based on the car call situation, and as necessary adds such route candidates to route data storage device 24 as the "route data" also. This data addition may be performed by selecting any possible route(s) every time a call is newly occurred. By way of example, the car E1 having the "call data" shown in Table 1 remains capable of traveling along a different route other than the one shown in Table 3 e.g., the route shown in Table 40 below. Accordingly, the route setting device 161 updates the "route data" as presently stored in route data storage device 24, based on the route data candidates shown in Table 40. The updated "route data" is as follows: Here, the top data item in the "route data" of each car indicates the presently traveling route. Note that the route data alteration in the above ninth embodiment is the one which attempts to change or modify part of the present route data, which is different from that of this embodiment being arranged to newly add one or several route data items. [17. Seventeenth Embodiment] As shown in Fig. 17, this embodiment is not with the arrival time estimation device 23, but with a function evaluation device 171 being arranged within the assignment instruction device 25. Said function evaluation device 171 holds therein the function as expressed by the following Formula 12, which defines a specific function formula for determination of call number's distribution, where "i" is used to indicate that a new station call is to be assigned to car i. The assignment instruction device 25 executes the car assignment procedure for the target floor in accordance with Formula 13. Formula 13 tells that assignment is to be made to the car j which is minimum in distribution as defined by Formula 12. It should be noted that this embodiment may alternatively be modified to employ the car reassignment scheme as in the aforementioned embodiments namely, the eighth, fourteenth and fifteenth embodiments. [18. Eighteenth Embodiment] As shown in Fig. 18 this embodiment comes with a multi-purpose evaluation device 181, which assigns cars based on a specific evaluation function that may be a combination of the evaluation scheme as employed in the second to seventh embodiments and the evaluation result as provided by the function evaluation device 171 as discussed previously in connection with the seventeenth embodiment. Said multi-purpose evaluation device 181 makes use of one specific evaluation function as will be given below, where "i" indicates that a new station call is assigned to car i whereas a to e designate the weighting parameters for individual evaluation, which may be zero or positive integers. [Formula 14] σ (i) = a × (NONRESPONSE TIME SCATTER) + b × (AVERAGE NONRESPONSE TIME SCATTER) + c × (SERVICE COMPLETION TIME SCATTER) + d × (AVERAGE SERVICE COMPLETION TIME SCATTER) + e × ( CAR'S CALL NUMBER SCATTER) Alternatively, it may be arranged that in the same manner as in the seventeenth embodiment, the following equation is established to assign to the car j on the occasions where certain function value is in minimum. Note that this embodiment may be so modified as to employ the car reassignment scheme as in the aforementioned embodiments (the eighth, fourteenth and fifteenth ones). [19. Nineteenth Embodiment] This embodiment relates to an elevator group management control apparatus corresponding to claim 8 and an elevator group management control method (corresponding to claim 10) used for the elevator group management control apparatus. [19-1. Configuration of the Nineteenth Embodiment] This embodiment relates to the elevator group management control apparatus 3, used for an elevator system, comprising a car operation control device 4 which controls the operation of a plurality of elevator cars moving vertically and horizontally, a car data detection device 2 which detects the status (for example, position, speed, and load) of each car, and one or more station call registration devices 1 each installed at the elevator entrance on each floor. [19-1-1. Configuration of Elevator Group Management Control Apparatus] The elevator group management control apparatus 3 used in this embodiment comprises the devices shown in Fig. 19. That is, the elevator group management control apparatus comprises the call data storage device 210 containing "call data" consisting of car calls specifying the floors desired by the passengers in each car and station calls assigned to each car; the direction data storage device 220 estimating the direction of each shaft where each of the cars is moving, based on "car data" detected by the car data detection device 2 and "call data" stored in the call data storage device 210, and updating and storing data as "direction data"; the number-of-shafts detection device 230 receiving the "direction data" of the shafts of the cars from the direction data storage device 220 and, for each shaft, finding the number of shafts in the same direction as the direction of the shaft; the shaft data storage device 240 estimating the floor and the shaft of each of the cars with the use of "car data" detected by the car data detection device 2, and storing resulting data about estimated floors and shafts as "shaft data"; the horizontal movement destination detection device 250 receiving the "shaft data" of each car from the shaft data storage device 240, checking if there is a car moving horizontally and, if there is, finding the horizontal movement destination shaft of the car; the reversing car determination device 260A receiving "new station call data" from the station call registration device 1, "call data" from the call data storage device 210, "direction data" of each of the cars from the direction data storage device 220, "shaft data" of each of the cars from the shaft data storage device 240, the number of shafts whose direction is the same as that of each of the cars detected by the number-of-shafts detection device 230, and the number of a horizontal movement destination shaft detected by the horizontal movement destination detection device 250 to determine a car to be reversed in order to respond to a new station call added to the station call registration device 1; the assignment instruction device 270 receiving "reversing car data" determined by the reversing car determination device 260A, "call data" of each of the cars from the call data storage device 210, "new station call data" added to the station call registration device 1, "direction data" of each of the cars from the direction data storage device 220, and "car data" detected by the car data detection device 2 to determine a "response car" to respond to a new station call and, at the same time, store the information on the call in the call data storage device 210; and the operation instruction device 280 issuing an operation instruction to a "response car" determined by the assignment instruction device 270 and, if the "response car" is a reversing car determined by the reversing car determination device 260, issuing another operation instruction to the other car in the shaft where the "response car" is moving in order to prevent collision. [19-1-2. Configuration of the Reversing Car Determination Device] The configuration of the reversing car determination device 260A of the elevator group management control apparatus 3 will be described in further detail with reference to Fig. 20. The reversing car determination device 260A comprises: the opposite direction car selection module 1601 receiving "shaft data" indicating the shaft of each car from the shaft data storage device 240, "direction data" of the shaft of each car from the direction data storage device 220, and "new station call data" added to the station call registration device 1, selecting the cars in the shafts whose direction is opposite to the direction of the new station call, and outputting 0 for a car not selected; the unchecked car selection module 1602 receiving the number of an opposite-direction car selected by the opposite direction car selection module 1601 and outputting, one at a time, the number of a car not yet checked if it is eligible for a "reversing car"; the station call finding module 1603 receiving a car number selected by the unchecked car selection module 1602 and the "station call data" of each car stored in the call data storage device 210, checking if there is a station call for the car, and outputting 0 if there is a station call or -1 and the car number if there is no station call; the car call finding module 1604 receiving the value and the car number from the station call finding module 1603 and the "car call data" of each car from the call data storage device 210, outputting 0 if the value obtained by the station call finding module 1603 is 0 (there is a station call) or finding the car call of the car if the value is -1 (there is no station call), and outputting 0 if there is a car call or -1 and the car number if there is no car call; the movement direction finding module 1605 receiving the value and the car number from the car call finding module 1604, the "new station call data" added to the station call registration device 1, and the "direction data" of the shaft of each car from the direction data storage device 220, outputting 0 if the value obtained by the car call finding module 1604 is 0 (there is a car call) or, if the value is -1 (there is no car call), checking if the direction into which the car will move to respond to the new station call is opposite to the direction of the shaft of the car, and outputting -1 if the direction is opposite or 0 and the car number if the direction is the same; the shaft direction finding module 1606 receiving the value and the car number from the movement direction finding module 1605 and the number of shafts in the same direction as the direction of each shaft from the number-of-shafts detection device 230, outputting 0 if the value obtained by the movement direction finding module 1605 is 0 (same direction) or, if the value is -1 (opposite direction), checking if there is at least one other shaft moving into the same direction, and outputting -1 if there is at least one other such shaft or 0 and the car number if there is not; the other-car finding module 1607 receiving the value and the car number from the shaft direction finding module 1606 and the "shaft data" of each car from the shaft data storage device 240, outputting 0 if the value obtained by the shaft direction finding module 1606 is 0 (there is no shaft in the same direction) or , if the value is -1 (there is another shaft in the same direction), checking if there is another car in the shaft of the car, and outputting the number of the other car if there is or -1 and the car number if there is not; the other-car call finding module 1608 receiving the value, the car number, and the other car number from the other-car finding module 1607 and the "car call data" of each car from the call data storage device 210, outputting -1 if the value obtained by the other-car finding module 1607 is -1 (there is no other car) or 0 if the value is 0, checking if there is a "station call" and/or a "car call" when the other-car number was received, and outputting -1 if there is neither call nor 0 and the car number if there is either call; the horizontal movement finding module 1609 receiving the value and the car number from the other-car call finding module 1608, the "shaft data" of each car from the shaft data storage device 240, and the horizontal movement destination of the horizontally-moving car from the horizontal movement destination detection device 250, outputting 0 if the value obtained by the other-car call finding module 1608 is 0 (there is a "station call" or a "car call" in the other car) or, if the value is -1 (there is neither a "station call" nor a "car call" in the other car), checking if there is a car moving horizontally to the shaft of the car, and outputting 0 if there is such a car or -1 and the car number if there is not. the reversing car storage module 1610 receiving the value and the car number from the horizontal movement finding module 1609 and, if the value is -1 (there is no car horizontally moving to the shaft), storing and outputting information indicating that the car is reversible; the check finish confirming module 1611 receiving the value and the car number from the horizontal movement finding module 1609, and the car number selected by the opposite direction car selection module 1601, storing the number, and outputting -1 if all the car numbers selected by the opposite direction car selection module 1601 are stored or, if all the car numbers are not yet checked, issuing an instruction to the unchecked car selection module 1602 to cause it to check whether or not the next car may be reversed; and the reversing car specifying module 1612 receiving the identification value from the check finish confirming module 1611, the selection result from the opposite direction car selection module 1601, and the number of a reversible car from the reversing car storage module 1610, outputting 0 if the selection result is 0 (there is no car moving into the opposite direction), specifying the car as reversible and outputting the car number to the assignment instruction device 270 if the identification value is -1 (all the selected cars are checked) and the number of the reversible car was received or, if not, 0 (there is no reversible car) to the assignment instruction device 270. In the above discussion, only the cars, each in a shaft whose direction is opposite to the direction to the new station call, are checked. This is because the reversion of a car in order to respond to a "new station call" is done only once in this embodiment. [19-2. Operation of the Nineteenth Embodiment] The nineteenth embodiment having the configuration described above performs operation as follows. [19-2-1. Call Data Storage Processing] The call data storage device 210 shown in Fig. 19 contains information on the floors and directions (upward call or downward call) of previously-assigned station calls and information on the floors and directions of car calls (floors at which the passengers in a car will get off), as "call data", in the format shown in Table 42. Where, H indicates a station call, C indicates a car call, UP indicates an upward direction, and DN indicates a downward direction. For example, "call data" of (H, 2, DN) for car 3 indicates that a downward station call requested at the second floor is assigned to car 3; similarly, "call data" of (C, 19, UP) for car 4 indicates that there is a passenger in car 4 who wants to get off at the nineteenth floor. [19-2-2. Direction Data Storage Processing] The direction data storage device 220 shown in Fig. 19 estimates the direction of the shaft in which each car is to move (upward or downward), updates "direction data", and stores it in itself in the format shown in Table 43, based on information on the car positions obtained by the car data detection device 2 and on "call data" stored in the call data storage device 210. Shaft number Direction 1 UP 2 DN 3 UP 4 DN [19-2-3. Number-of-Shafts Detection Processing] The number-of-shafts detection device 230 shown in Fig. 19 detects, for each car, the number of shafts in which cars are moving into the same direction as the car, based on the information obtained from the direction data storage device 220. This processing is performed to prevent the cars in all the shafts from moving into the same direction when there is a car whose direction cannot be reversed. This processing ensures that there is at least one shaft in which a car is moving into the direction opposite to those of cars in other shafts. [19-2-4. Shaft Data Storage Processing] The shaft data storage device 240 shown in Fig. 19 contains information on the floor and the shaft where each car is moving, based on the position of each car obtained from the car data detection device 2. The information is stored as "shaft data." For example, Fig. 21 shows an example of a 20-story building with four elevator shafts. This Figure shows that car 1 is at the fifteenth floor and car 2 is at the seventh floor in the first shaft, car 3 is at the third floor in the second shaft, car 4 is at the eighteenth floor in the third shaft, and that car 5 is at the tenth floor in the fourth shaft. In this case, the shaft data storage device 240 contains "shaft data" in the format shown in Table 44. [19-2-5. Horizontal Movement Destination Detection Processing] For a car which moves horizontally on a horizontal movement floor, the horizontal movement destination detection device 250 shown in Fig. 19 detects the number of the shaft to which the car will move, based on the information on the position and shaft of each car obtained from the shaft data storage device 240. For example, when car 5 moves horizontally from the fourth shaft to the third shaft, " the horizontal movement destination shaft data " is stored as shown in Table 45. This table indicates that the horizontal movement destination shaft number is "3". When there is no car which moves horizontally, the table contains "null." [19-2-6. Reversing Car Determination Processing] The reversing car determination device 260A shown in Fig. 19 determines a car whose direction is to be reversed in response to the new station call added to the station call registration device 1 according to the conditions shown below and then outputs the data on the determined reversing car to the assignment instruction device 270. To do so, the reversing car determination device 260A uses "new station call data" added to the station call registration device 1, "call data" of each car stored in the call data storage device 210, "direction data" (upward or downward) of the shaft in which each car runs obtained from the direction data storage device 220, the number of shafts in which cars are moving into the same direction as that of each car obtained from the number-of-shafts detection device 230, "shaft data" of the shaft in which each car runs stored in the shaft data storage device 240, and the car movement destination shaft number obtained from the horizontal movement destination detection device 250. (A) Conditions under which a reversing car is determined (Condition 1) The direction of the shaft of a car to be examined whether to reverse the moving direction (hereafter called a target car) is opposite to the direction of the "new station call" stored in the station call registration device 1. (The opposite direction car selection module 1601 evaluates this condition). (Condition 2) The call data storage device 210 does not contain a station call for the target car. (The station call finding module 1603 evaluates this condition). (Condition 3) The call data storage device 210 does not contain a car call for the target car. (The car call finding module 1604 evaluates this condition). (Condition 4) The direction into which the target car must move to respond to the "new station call" added to the station call registration device 1 is opposite to the direction of the shaft in which the target car is moving. (The movement direction finding module 1605 evaluates this condition). (Condition 5) There is at least one other shaft whose direction is the same as the direction of the shaft in which the target car is moving. (The shaft direction finding module 1606 evaluates this condition). (Condition 6) There is no other car in the shaft in which the target car is moving. (The other-car finding module 1607 evaluates this condition). Or, for another car in the shaft in which the target car is moving, the call data storage device 210 contains neither "station calls" nor "car calls". (The other-car call finding module 1608 evaluates this condition). (Condition 7) There is no car which is moving horizontally to the shaft in which the target car is moving. (The horizontal movement finding module 1609 evaluates this condition). (B) Reversing car determination processing flow Figures 22 and 23 are the flowcharts showing the processing flow of the reversing car determination device 260A which works based on the conditions described in (A). The flowcharts in Figures 22 and 23 show how an elevator system, such as the one shown in Fig. 21, processes "call data (5, DN)" added to the station call registration device 1. That is, as shown in Fig. 21, an elevator system in a 20-story building has four elevator shafts. Assume that car 1 is at the fifteenth floor and car 2 is at the seventh floor in the first shaft, car 3 is at the third floor in the second shaft, car 4 is at the eighteenth floor in the third shaft, and that car 5 is at the tenth floor in the fourth shaft. Also assume that cars 1, 2, and 4, each in the stopped state at the respective floor, are ready to close their doors and start operation and that cars 3 and 5 are moving in their shafts. Assume that the call data storage device 210 contains "station call data" (2, DN) for car 3 and "car call data" (19, UP) for car 4 and (9, DN) for car 5. Also assume that the direction data storage device 220 contains the "direction data" of the shaft in which each car runs; UP for the first shaft, DN for the second shaft, UP for the third shaft, and DN for the fourth shaft. In addition, the shaft data storage device 240 contains the "shaft data" which indicates the combination of the floor at which the car is moving and the shaft in which the car is moving; (15@1) for car 1, (7@1) for car 2, (3@2) for car 3, (18@3) for car 4, and (10@4) for car 5. To determine a car whose direction is to be reversed, it is necessary to select a car satisfying all the seven conditions described above. The conditions will be described in further detail with reference to the flowcharts shown in Figures 22 and 23. In step 401, the reversing car determination device uses "direction data" of the shafts stored in the direction data storage device 220, "shaft data" stored in the shaft data storage device 240, and a "new station call" added to the station call registration device 1 in order to select one or more cars whose direction is opposite to that of the station call added to the station call registration device 1. As a result, the device selects cars 1, 2, and 4 (In this embodiment, the opposite direction car selection module 1601 executes step 401). These cars satisfy (condition 1). In step 403 (the unchecked car selection module 1602 executes this step), the module selects one of the cars selected in step 401 (here, assume that car 1 is selected). And, in step 404 (the station call finding module 1603 executes this step), the module checks to see if the call data storage device 210 contains "station call data" for car 1. It is found that there is no such "station call data." This satisfies (condition 2). Then, in step 405 (the car call finding module 1604 executes this step), the module checks the call data storage device 210 to see if there is "car call data" for car 1 and finds that there is no such "car call data." This satisfies (condition 3). In step 406 (the movement direction finding module 1605 executes this step), the module uses the "direction data" of the shafts obtained from the direction data storage device 220 and "new station call data" added to the station call registration device 1 to check if the direction into which car 1 will move to respond to the "new station call" is opposite to the direction of the shaft in which car 1 is moving and finds that the direction is opposite. This satisfies (condition 4). Next, in step 407 (the shaft direction finding module 1606 executes this step), the module checks to see if there is at least one other shaft whose direction is the same as that of the shaft in which car 1 is moving. Because there is the third shaft (same direction as that of the first shaft), car 1 satisfies (condition 5). In step 408 (the other-car finding module 1607 executes this step), the module checks whether or not there is another car in the shaft in which car 1 is moving and finds that there is car 2 in the first shaft. In step 409 (the other-car call finding module 1608 executes this step), the module checks the call data storage device 210 to see if there is "station call data" and "car call data" for the other car (in this case, car 2) and finds that there is neither "station call" nor "car call". This satisfies (condition 6). In step 410 (the horizontal movement finding module 1609 executes this step), the module uses the "shaft data" of the shaft in which car 1 is moving, stored in the shaft data storage device 240, and the horizontal movement destination shaft number of a car moving horizontally, stored in the horizontal movement destination detection device 250, to check to see if there is another car moving horizontally to the shaft in which car 1 is moving (first shaft) and finds that there is no such car. This satisfies (condition 7). As a result, the target car, car 1, satisfies all seven conditions described above, and it is determined that "car 1 may be reversed." (step 411) Next, control is passed to step 412 (the check finish confirming module 1611 executes this step) to confirm that all the selected cars, 1, 2, and 4, are checked to see if they may be reversed. Because cars 2 and 4 are not yet checked, control returns to step 403. The device checks car 2 , one of the cars selected in step 403, in the same way it did for car 1. As a result, the device finds that all seven conditions are satisfied and therefore determines that "car 2 may also be reversed." The device also checks car 4, one of the cars selected in step 403, in the same way. It finds that, in step 405, that there is a "car call (C, 19, UP)" for car 4 and that one of the above conditions (condition 3) is not satisfied. Therefore, it is determined that cars 1 and 2, which satisfy all seven conditions described above, "may be reversed." [19-2-7. Assignment Instruction Processing] The assignment instruction device 270 shown in Fig. 19 uses "reversing car data" determined by the reversing car determination device 260A, "call data" consisting of the car calls and the assigned station calls of the cars stored in the call data storage device 210, "new station call data" added to the station call registration device 1, "direction data" of the shafts in which the cars are moving stored in the direction data storage device 220, and "car data" detected by the car data detection device 2 to determine a car to be used in response to the new station call, issues an instruction to the operation instruction device 280 to cause it to issue an operation instruction to the determined car and, at the same time, stores the station call in the call data storage device 210. The flow of processing in the assignment instruction device 270 will be described with reference to the flowchart in Fig. 24. In step 601, the device checks to see if there are cars that may be reversed. In this embodiment, it is determined that cars 1 and 2 may be reversed. In addition, for cars 3 and 5 which were not selected in step 401 in the flowcharts in Figures 22 and 23, the device estimates in step 602 the time needed to respond to the new station call based on data such as "call data" (that is, the time needed for those cars to reach the fifth floor). In step 604, the device selects car 2, whose arrival time is the minimum, as the car to respond to the "new station call (5, DN)" and outputs an instruction to the operation instruction device 280 to cause it to issue an operation instruction to car 2 and, at the same time, sends information to the call data storage device 210 indicating that the "new station call (5, DN)" is assigned to car 2. The call data storage device 210 contains information in the format shown in Table 46. When Table 46 is compared with Table 42, it is understood that Table 46 has new "call data" for car 2. [19-2-8. Operation Instruction Processing] The operation instruction device 280 shown in Fig. 19 outputs an operation instruction to the car which was instructed by the assignment instruction device 270 as the car to respond to the call. And, if, after the "station call data" of the car to be reversed has been updated to "car data", the car to respond to the "new station call" is the one determined by the reversing car determination device 260, the operation instruction device issues another operation instruction to the car operation control device 4 to prevent the other car in the same shaft from colliding with the car to be reversed. [19-3. Effects of the Nineteenth Embodiment] The elevator group management control apparatus and the elevator group management control method used for the elevator group management control apparatus, shown in the nineteenth embodiment with the above configuration, have the following effects: When determining a car to be used in response to a new station call during elevator group management control, it is possible, before responding to the new station call, to check whether or not there is a car to be reversed without considering the current direction of each shaft, and, if there is such a car, to change the operation direction of the car as necessary. In addition, because the cars determined to be reversible are also a candidate for the "response car" in this system, the new station call is speedily responded. [20. Twentieth Embodiment] This embodiment relates to an elevator group management control apparatus corresponding to claim 8 and an elevator group management control method (corresponding to claim 10) used for the elevator group management control apparatus. [20-1. Configuration of the Twentieth Embodiment] This embodiment is a variation of the nineteenth embodiment with some changes in the configuration of the reversing car determination device. A car is reversed to move to the floor in response to a "new station call" in the nineteenth embodiment, while in this embodiment a car arrives at the floor in response to a "new station call" and then it is reversed. [20-1-1. Configuration of the Elevator Group Management Control Apparatus] The elevator group management control apparatus 3 according to this embodiment is configured in the same manner as in the nineteenth embodiment except that the part of the configuration of the reversing car determination device is changed (see Fig. 19). [20-1-2. Configuration of the Reversing Car Determination Device] The configuration of the reversing car determination device 260B of the elevator group management control apparatus 3 in this embodiment will be described in further detail with reference to Fig. 25. The reversing car determination device 260B used in this embodiment is the reversing car determination device 260A with the car call position finding module 1613 added. That is, the car call finding module 1604 in the reversing car determination device receives the value and the car number from the station call finding module 1603 and the "car call data" of each car from the call data storage device 210, outputs 0 if the value detected by the station call finding module 1603 is 0 or, if the value is -1, checks if there is a car call for the car, and outputs the "car call data" of the car if there is a car call or outputs - 1 and the car number if there is not, the car call position finding module 1613 receives the value, the car number, and the "car call data" from the car call finding module 1604 and "new station call data" added to the station call registration device 1, outputs -1 if the value obtained by the car call finding module 1604 is -1 or outputs 0 if it is 0, when the "car call data" is entered, checks if the floor requested by the car call is between the current floor and the floor requested by the new station call, and outputs -1 if the car call is one of the floors to the new station call or 0 and the car number if it is not, the movement direction finding module 1605 receives the value and the car number from the car call position finding module 1613, "new station call data" added to the station call registration device 1, and the "direction data" of the shaft of each car from the direction data storage device 220, outputs 0 if the value obtained by the car call position finding module 1613 is 0 or, if it is -1, checks if the direction to the floor where the new station call was generated is the same as the direction of the shaft of the car, and outputs -1 if the direction to that floor is the same as the direction of the shaft or outputs 0 and the car number if the direction is opposite to the direction of the shaft. The configuration of each of the other modules, which is the same as that of the reversing car determination device 260A explained in the thirty-second embodiment, is not described here. [20-2. Operation of the Twentieth Embodiment] The twentieth embodiment having the configuration described above performs operation as described below. The following explains where the twentieth embodiment differs from the nineteenth embodiment. [20-2-1. Reversing Car Determination Processing] The reversing car determination device 260B shown in Fig. 25 uses "new station call data" added to the station call registration device 1, "call data" of each car stored in the call data storage device 210, "direction data" (upward and downward) of the shaft of each car obtained by the direction data storage device 220, the number of shafts in the same direction as the direction of the shaft of each car obtained by the number-of-shafts detection device 230, "shaft data" of each car stored in the shaft data storage device 240, and the car movement destination shaft number of a horizontally-moving car stored in the horizontal movement destination detection device 250 to determine the car to be reversed in response to the new station call added to the station call registration device 1 according to the conditions described below and to output data on the determined reversing car to the assignment instruction device 270. (A) Conditions under which a reversing car is determined (Condition 1) The direction of the shaft of the target car is opposite to the direction of the "new station call" stored in the station call registration device 1. (The opposite direction car selection module 1601 evaluates this condition). (Condition 2) The call data storage device 210 does not contain a station call for the target car. (The station call finding module 1603 evaluates this condition). (Condition 3) The call data storage device 210 does not contain a "car call" for the target car. (The car call finding module 1604 evaluates this condition). Or, the "car call" stored in the call data storage device 210 requests a floor on the way to the newly-added station call. (The car call position finding module 1613 evaluates this condition). (Condition 4) The direction into which the target car must move to respond to the "new station call" added to the station call registration device 1 is the same as the direction of the shaft in which the target car is moving. (The movement direction finding module 1605 evaluates this condition). (Condition 5) There is at least one other shaft whose direction is the same as the direction of the shaft in which the target car is moving. (The shaft direction finding module 1606 evaluates this condition). (Condition 6) There is no other car in the shaft in which the target car is moving. (The other-car finding module 1607 evaluates this condition). Or, for another car in the shaft in which the target car is moving, the call data storage device 210 contains neither "station calls" nor "car calls". (The other-car call finding module 1608 evaluates this condition). (Condition 7) There is no car which is moving horizontally to the shaft in which the target car is moving. (The horizontal movement finding module 1609 evaluates this condition). (B) Reversing car determination processing flow Figures 26 and 27 are the flowcharts showing the processing flow of the reversing car determination device 260B which works based on the conditions described in (A). The flowcharts in Figures 26 and 27 show how an elevator system, such as the one shown in Fig. 21, processes "call data (4, UP)" added to the station call registration device 1. That is, as shown in Fig. 21, an elevator system in a 20-story building has four elevator shafts. Assume that car 1 is at the fifteenth floor and car 2 is at the seventh floor in the first shaft, car 3 is at the third floor in the second shaft, car 4 is at the eighteenth floor in the third shaft, and that car 5 is at the tenth floor in the fourth shaft. Also assume that cars 1, 2, and 4, each in the stopped state at the respective floor, are ready to close their doors and start operation and that cars 3 and 5 are moving in their shafts. Assume that the call data storage device 210 contains "station call data" (2, DN) for car 3 and "car call data" (19, UP) for car 4 and (9, DN) for car 5. Also assume that the direction data storage device 220 contains the "direction data" of the shaft in which each car runs; UP for the first shaft, DN for the second shaft, UP for the third shaft, and DN for the fourth shaft. In addition, the shaft data storage device 240 contains the "shaft data" which indicates the combination of the floor at which the car is moving and the shaft in which the car is moving; (15@1) for car 1, (7@1) for car 2, (3@2) for car 3, (18@3) for car 4, and (10@4) for car 5. To determine a car whose direction is to be reversed, it is necessary to select a car satisfying all the seven conditions described above. The conditions will be described in further detail with reference to the flowcharts shown in Figures 26 and 27. In step 801 (the opposite direction car selection module 1601 executes this step), the reversing car determination device uses "direction data" of the shafts stored in the direction data storage device 220, "shaft data" stored in the shaft data storage device 240, and a "new station call" added to the station call registration device 1 in order to select one or more cars whose direction is opposite to that of the station call added to the station call registration device 1. As a result, the device selects cars 3 and 5. These cars satisfy (condition 1). In step 803 (the unchecked car selection module 1602 executes this step), the module selects one of the cars selected in step 801 (here, assume that car 3 is selected). And, in step 804 (the station call finding module 1603 executes this step), the module checks to see if the call data storage device 210 contains "station call data" for car 3 and finds that there is "station call data (H, 2, DN)". This does not satisfy (condition 2). Therefore, it is determined that car 3 may not be reversed. Next, in step 813 (the check finish confirming module 1611 executes this step), the module checks to see if all the selected cars, 3 and 5, are checked. Because car 5 is not yet checked, control goes back to step 803. The check is made for car 5, one of the cars selected in step 803, in the same way the check was made for car 3. In step 804 (the station call finding module 1603 executes this step), the module checks to see if the call data storage device 210 contains "station call data" for car 5 and finds that there is no "station call data". This satisfies (condition 2). Then, in step 805 (the car call finding module 1604 executes this step), the module checks the call data storage device 210 to see if there is "car call data" for car 5 and finds that there is "car call data (C, 9, DN)". In step 806 (the car call position finding module 1613 executes this step), the module finds that the "car call" requests a floor on the way to the fourth floor requested by the "new station call". This satisfies (condition 3). In step 807 (the movement direction finding module 1605 executes this step), the module uses the "direction data" of the shafts obtained from the direction data storage device 220 and "new station call data" added to the station call registration device 1 to check if the direction (downward in this case) into which car 5 will move to respond to the "new station call (4, UP)" is same as the direction of the shaft in which car 5 is moving and finds that the direction is the same. This satisfies (condition 4). Next, in step 808 (the shaft direction finding module 1606 executes this step), the module checks to see if there is at least one other shaft whose direction is the same as that of the shaft in which car 5 is moving. Because there is the second shaft (same direction as that of the fourth shaft), car 5 satisfies (condition 5). In step 809 (the other-car finding module 1607 executes this step), the module checks whether or not there is another car in the shaft in which car 5 is moving and finds that there is no other car in the fourth shaft. This satisfies (condition 6). In step 811 (the horizontal movement finding module 1609 executes this step), the module uses the "shaft data" of the shaft in which car 5 is moving, stored in the shaft data storage device 240, and the horizontal movement destination shaft number of a car moving horizontally, stored in the horizontal movement destination detection device 250, to check to see if there is another car moving horizontally to the shaft in which car 5 is moving (fourth shaft), and finds that there is no such car. This satisfies (condition 7). As a result, the target car, car 5, satisfies all seven conditions described above, and it is determined that "car 5 may be reversed." (step 812) [20-2-2. Assignment Instruction Processing] The flow of processing in the assignment instruction device 270 will be described with reference to the flowchart in Fig. 24. In step 601, the device checks to see if there are cars that may be reversed. In this embodiment, it is determined that car 5 may be reversed. In addition, for cars 1, 2, and 4 which were not selected in step 801 in the flowcharts in Figures 26 and 27, the device estimates in step 602 the time needed to respond to the station call based on data including "call data" (that is, the time needed for those cars to reach the fourth floor). In step 604, the device selects car 5, whose arrival time is the minimum, as the car to respond to the "new station call (4, UP)" and outputs an instruction to the operation instruction device 280 to cause it to issue an operation instruction to car 5 and, at the same time, sends information to the call data storage device 210 indicating that the "new station call (4, UP)" is assigned to car 5. The call data storage device 210 contains information in the format shown in Table 47. When Table 47 is compared with Table 42, it is understood that Table 47 has new "call data" for car 5. [20-3. Effects of the Twentieth Embodiment] The elevator group management control apparatus and the elevator group management control method used for the elevator group management control apparatus, shown in the twentieth embodiment with the above configuration, have the following effects: When determining a car to be used in response to a new station call during elevator group management control, it is possible, after responding to the new station call, to check whether or not there is a car to be reversed without considering the current direction of each shaft and, if there is such a car, to change the operation direction of the car as necessary. In addition, because the cars determined to be reversible are also a candidate for the "response car" in this system, a new station call is speedily responded. [21. Twenty-first Embodiment] This embodiment relates to an elevator group management control apparatus corresponding to claim 9 and an elevator group management control method (corresponding to claim 11) used for the elevator group management control apparatus. [21-1. Configuration of the Twenty-first Embodiment] This embodiment relates to an elevator group management control apparatus 3 for use in an elevator system comprising a car operation control device 4 controlling the operation of a plurality of vertically- and horizontally-movable cars, a car data detection device 2 detecting the state of each of said cars (for example, position, speed, and load), and one or more station call registration devices 1 installed in the station of each floor. [21-1-1. Configuration of the Elevator Group Management Control Apparatus] The elevator group management control apparatus 3 used in this embodiment comprises the devices shown in Fig. 28. That is, the elevator group management control apparatus comprises: the call data storage device 210 containing "call data" consisting of car calls requested by the passengers in the cars and station calls assigned to each car; the direction data storage device 220 receiving "car data" from the car data detection device 2 and "call data" from the call data storage device 210, estimating the direction of the shaft of each of the cars, and updating and storing resulting data as "direction data"; the shaft data storage device 240 receiving "car data" detected by the car data detection device 2, estimating the floor and the shaft of each of the cars, and storing resulting data about estimated floors and shafts as "shaft data"; the route data storage device 290 receiving the "direction data" of the shaft of each car from the direction data storage device 220 and storing information on a route along which each car should run; the horizontally-moving floor arrival estimation device 300 receiving the "direction data" of the shaft of each car from the direction data storage device 220, the "shaft data" of each car from the shaft data storage device 240, and the "route data" of a route along which each car should move from the route data storage device 290, estimating a car arriving at the horizontally-moving floor of each shaft first, and outputting the car number; the horizontal movement destination detection device 250 receiving the "shaft data" of each car from the shaft data storage device 240, checking if there is a car moving horizontally and, if there is, finding the horizontal movement destination shaft of the car; the reversing car determination device 260C receiving "new station call data" from the station call registration device 1, "call data" from the call data storage device 210, "direction data" of each of the cars from the direction data storage device 220, "shaft data" of each of the cars from the shaft data storage device 240, "route data" representing a route along which each car moves from the route data storage device 290, the number of the car arriving at the horizontally-moving floor first estimated by the horizontally-moving floor arrival estimation device 300, and the number of a car moving horizontally and the number of the shaft to which the car is moving detected by the horizontal movement destination detection device 250, and determining a car to be reversed in order to respond to a new station call added to the station call registration device 1; the assignment instruction device 270 receiving "reversing car data" determined by the reversing car determination device 260C, "call data" of each of the cars from the call data storage device 210, "new station call data" added to the station call registration device 1, "direction data" of each of the cars from the direction data storage device 220, "car data" detected by the car data detection device 2, and "route data" representing a route along which each car runs from the route data storage device 290, and determining a "response car" to respond to a new station call and, at the same time, storing information on the call in call data storage device 210; and the operation instruction device 280 issuing an operation instruction to the car determined by the assignment instruction device 270 and, if the car is the one determined by the reversing car determination device 260C, issuing another operation instruction to the other car in the shaft of the response car, in order to prevent collision of each cars ; [21-1-2. Configuration of the Reversing Car Determination Device] The configuration of the reversing car determination device 260C of the elevator group management control apparatus 3 will be described in further detail with reference to Fig. 29. The reversing car determination device 260C comprises: the opposite direction car selection module 1601 receiving "shaft data" of each car from the shaft data storage device 240, "direction data" of the shaft of each car from the direction data storage device 220, and "new station call data" added to the station call registration device 1, selecting the cars in the shafts moving in the direction opposite to the direction to respond to the new station call and, if there is no such car, outputting 0; the unchecked car selection module 1602 receiving the number of a car whose direction is opposite to the direction to the floor were the new station call is generated, selecting from the cars selected by said opposite direction car selection module 1601 a car not yet checked if it is eligible for a "reversing car", one at a time, and outputting the number of the car; the station call finding module 1603 receiving the number of the car selected by the unchecked car selection module 1602, the "station call data" of each car from the call data storage device 210, and "new station call data" added to the station call registration device 1, checking if there is a station call whose direction is opposite to the direction to the new station call, and outputting 0 if there is such a station call or -1 if there is no such station call. the car call finding module 1604 receiving the value and the car number from the station call finding module 1603, the "car call data" of each car from the call data storage device 210, and "new station call data" added to the station call registration device 1, outputting 0 if the value obtained by the station call finding module 1603 is 0 or, if the value is -1, checking if there is a car call in the direction opposite to the direction to the floor requested by the new station call, and outputting 0 if there is such a car call or -1 and the car number if there is no such car call. the movement direction finding module 1605 receiving the value and the car number from the car call finding module 1604, "new station call data" added to the station call registration device 1, and the "direction data" of the shaft of each car from the direction data storage device 220, outputting 0 if the value obtained by the car call finding module 1604 is 0 or, if the value is -1, checking if the direction into which the car will move to respond to the new station call is opposite to the direction of the shaft of the car, and outputting -1 if the direction is opposite or, if the direction is the same, 0 and the car number; the other-car finding module 1607 receiving the value and the car number from the movement direction finding module 1605, "new station call data" added to the station call registration device 1, and the "shaft data" of each car from the shaft data storage device 240, outputting 0 if the value obtained by the movement direction finding module 1605 is 0 or, if the value is -1, checking if, in the shaft of the car, there is another car at a floor in the direction of the new station call, and outputting the number of the other car if there is such a car or -1 and the number of the car if there is no such car; the other-car direction finding module 1614 receiving the value or the number of the other car and the number of the car from the other-car finding module 1607, "new station call data" added to the station call registration device 1, and the "direction data" of the shaft of each car from the direction data storage device 220, outputting -1 if the value obtained by the other-car finding module 1607 is -1 or outputting 0 if it is 0, checking if, when the number of the other car is entered, the other car is in the direction of the new station call, and outputting -1 if the direction is the same or the number of the other car as well as the number of the car if the direction is opposite; the horizontally-moving floor finding module 1615 receiving the value or the number of the other car and the number of the car from the other-car direction finding module 1614 and the "shaft data" of the shaft of each car stored in the shaft data storage device 240, outputting -1 if the value obtained by the other-car direction finding module 1614 is - 1 or 0 it is 0, checking if, when the number of the other car is entered, there is a horizontally-moving floor between the car and the other car, and outputting the number of the other car and horizontally-moving floor data if there is such a horizontally-moving floor or 0 and the number of the car if there is no such horizontally-moving floor; the route crossing finding module 1616 receiving the value or the number of the other car, horizontally-moving floor data, and the number of the car from the horizontally-moving floor finding module 1615, "route data" representing a route along which the car should move from the route data storage device 290, "shaft data" from the shaft data storage device 240, and "new station call data" added to the station call registration device 1, outputting -1 if the value obtained by the horizontally-moving floor finding module 1615 is -1 or outputting 0 if it is 0, checking if, when the number of the other car is entered, the route to the floor where the new station call was generated and the route along which the other car will move cross each other, and outputting the number of the other car and horizontally-moving floor data if they cross or outputting 0 and the number of the car if they do not; the horizontally-moving route finding module 1617 receiving the value or the number of the other car, horizontally-moving floor data, and the number of the car from the route crossing finding module 1616 and "route data" representing a route along which the car will move from the route data storage device 290, outputting -1 if the value obtained by the route crossing finding module 1616 is - 1 or outputting 0 if it is 0, checking if, when the number of the other car is entered, the other car moves horizontally on the horizontally-moving floor, and outputting the number of the other car and horizontally-moving floor data if the other car moves horizontally on the horizontally-moving floor or outputting 0 and the number of the car if it does not; the horizontally-moving floor arrival car finding module 1618 receiving the value or the number of the other car, horizontally-moving floor data, and the number of the car from the horizontally-moving route finding module 1617 and the number of the car arriving first at each horizontally-moving floor estimated by the horizontally-moving floor arrival estimation device 300, outputting -1 if the value obtained by the horizontally-moving route finding module 1617 is -1 or outputting 0 if it is 0, finding the car arriving at the horizontally-moving floor first when the number of the other car is entered, and outputting -1 if that car is the other car or outputting 0 and the number of the car if it is not. the horizontal movement finding module 1609 receiving the value and the number of the car from the horizontally-moving floor arrival car finding module 1618, "new station call data" added to the station call registration device 1, the "shaft data" of each car from the shaft data storage device 240, and the destination of a horizontally-moving car detected by the horizontal movement destination detection device 250, outputting 0 if the value obtained by the horizontally-moving floor arrival car finding module 1618 is 0 or, if it is -1, checking if there is another car moving horizontally to the route along which the car will move to respond to the new station call, and, if there is such a horizontally-moving car, outputting the number of the other car or outputting -1 and the number of the car if there is no such horizontally-moving car; the after-horizontal-movement direction finding module 1619 receiving the value and the number of the car from the horizontal movement finding module 1609, "new station call data" added to the station call registration device 1, the "direction data" of the shaft of each car from the direction data storage device 220, and the destination of the horizontally-moving car detected by the horizontal movement destination detection device 250, outputting 0 if the value obtained by the horizontal movement finding module 1609 is 0 or outputting -1 if it is -1, checking if, when the number of the other car is entered, the direction of the other car after horizontal movement is the same as the direction to the floor requested by the new station call, and outputting -1 if the direction is the same or 0 if the direction is opposite; the reversing car storage module 1610 receiving the value and the number of the car from the after-horizontal-movement direction finding module 1619 and, if the value is -1, determining the car as reversible, and outputting that information; the check finish confirming module 1611 receiving the value and the number of the car from the after-horizontal-movement direction finding module 1619 and the number of a car selected by the opposite direction car selection module 1601, storing the number of the car, outputting -1 if all the numbers of cars selected by the opposite direction car selection module 1601 are stored or, if all the selected numbers are not yet stored, outputting information to the unchecked car selection module 1602 to cause it to check a car, not yet stored, if it is eligible for a reversing car; and the reversing car specifying module 1612 receiving the identification value from the check finish confirming module 1611, the selection result from the opposite direction car selection module 1601, and the number of a reversible car from the reversing car storage module 1610, outputting 0 if the selection result is 0, and specifying the car as a reversible car and outputting the car number to the assignment instruction device 270 if the identification value is - 1 and if the number of a reversible car is stored and, if not, outputting 0 to the assignment instruction device 270. [21-2. Operation of the Twenty-first Embodiment] The twenty-first embodiment having the configuration described above performs operation described below. The following explains direction data storage processing, route data storage processing, horizontally-moving floor arrival estimation processing, and reversing car determination processing which are different from those in the nineteenth embodiment or twentieth embodiment. [21-2-1. Direction Data Storage Processing] The direction data storage device 220 shown in Fig. 28 gets "car data" from the car data detection device 2, and "call data" from the call data storage device 210, estimates the direction (upward and downward) of the shaft of each car, updates "direction data" as necessary, and stores it in the format shown in Table 48. Car Shaft number Direction 1 1 UP 2 DN 3 UP 4 D N 2 1 UP 2 UP 3 UP 4 DN 3 1 D N 2 DN 3 UP 4 UP 4 1 U P 2 DN 3 UP 4 DN 5 1 DN 2 DN 3 UP 4 DN [21-2-2. Route Data Storage Processing] The route data storage device 290 shown in Fig. 28 contains "route data" along which each car should move according to the direction of the shaft of each car obtained from the direction data storage device 220. For example, one way for the car at the seventh floor in the first shaft in a 20-story building with four shafts to respond to a downward station call generated on the fourteenth floor is to go up to the tenth floor in the first shaft, move horizontally to the third shaft on the tenth floor, go up to the twentieth floor in the third shaft, move horizontally to the fourth shaft on the twentieth floor, and then go down to the fourteenth floor in the fourth shaft, as shown by the dotted line. A route along which each car should run, pre-defined for each car as in the above example, is stored as "route data" in the format shown in Table 49. For example, the "route data" for car 1 indicates that the horizontally-moving floors are the first and twentieth floors: car 1 moves from the second shaft to the first shaft on the first floor, and from the first shaft to the second shaft on the twentieth floor. Figures 31 and 32 illustrate the "route data" shown in Table 49. [21-2-3. Horizontally-Moving Floor Arrival Estimate Processing] The horizontally-moving floor arrival estimation device 300 shown in Fig. 28 uses the "direction data" of the shaft of each car stored in the direction data storage device 220, the "shaft data" of the shaft of each car stored in the shaft data storage device 240, and the "route data" representing a route along which each car should move stored in the route data storage device 290, estimates a car which arrives the horizontally-moving floor of each shaft first, and outputs the "car data" to the reversing car determination device 260. [21-2-4. Reversing Car Determination Processing] The reversing car determination device 260C shown in Fig. 28 uses "new station call data" added to the station call registration device 1, the "call data" of each car stored in the call data storage device 210, "direction data" (upward or downward) of each of the cars stored in the direction data storage device 220, "shaft data" of each of the cars stored in the shaft data storage device 240, "route data" representing a route along which each car should move stored in the route data storage device 290, the "car data" on the car arriving at the horizontally-moving floor first estimated by the horizontally-moving floor arrival estimation device 300, and the number of the shaft to which a car is moving horizontally detected by the horizontal movement destination detection device 250, determines a car to be reversed, according to the following conditions, in order to respond to a new station call added to the station call registration device 1, and outputs data on the car to be reversed to the assignment instruction device 270. (A) Conditions under which a reversing car is determined (Condition 1) The direction of the shaft of the target car is opposite to the direction of the "new station call" stored in the station call registration device 1. (The opposite direction car selection module 1601 evaluates this condition). (Condition 2) The call data storage device 210 does not contain a "station call" for the target car whose direction is opposite to the direction of the call added to the station call registration device 1. (The station call finding module 1603 evaluates this condition). (Condition 3) The call data storage device 210 does not contain a "car call" for the target car whose direction is opposite to the direction of the call added to the station call registration device 1. (The car call finding module 1604 evaluates this condition). (Condition 4) The direction into which the target car must move to respond to the "new station call" added to the station call registration device 1 is opposite to the "direction data" of the shaft in which the target car is moving. (The movement direction finding module 1605 evaluates this condition). (Condition 5) One of the following conditions is satisfied, in the shaft in which the target car is moving, for another car on a floor which is in the direction to the new station call with respect to the current floor of the target car: (a) There is no other car. (The other-car finding module 1607 evaluates this condition). (b) The other car is moving into the same direction as the direction of the new station call. (The other-car direction finding module 1614 evaluates this condition). (c) When there is a horizontally-moving floor between the target car and the other car (the horizontally-moving floor finding module 1615 evaluates this condition), when the route of the other car stored in the route data storage device 290 and the route of the target car to the new station call cross each other (the route crossing finding module 1616 evaluates this condition), and when the other car moves horizontally on the horizontally-moving floor (the horizontally-moving route finding module 1617 evaluates this condition), the other car arrives the horizontally-moving floor first (the horizontally-moving floor arrival car finding module 1618 evaluates this condition). (Condition 6) There is no other car moving horizontally to the shaft in which the target car will move to respond to the new station call . (The other-car finding module 1609 evaluates this condition). Or, the direction of the other car after horizontal movement is the same as the direction to the new station call. (The after-horizontal-movement direction finding module 1619 evaluates this condition). (B) Reversing car determination processing flow Figures 33 to 35 are the flowcharts showing the processing flow of the reversing car determination device 260C which works based on the conditions described in (A). The flowcharts in Figures 33 to 35 show how an elevator system, such as the one shown in Fig. 21, processes "call data (5, DN)" added to the station call registration device 1. That is, as shown in Fig. 21, an elevator system in a 20-story building has four elevator shafts. Assume that car 1 is at the fifteenth floor and car 2 is at the seventh floor in the first shaft, car 3 is at the third floor in the second shaft, car 4 is at the eighteenth floor in the third shaft, and that car 5 is at the tenth floor in the fourth shaft. Also assume that cars 1, 2, and 4, each in the stopped state at the respective floor, are ready to close their doors and start operation and that cars 3 and 5 are moving in their shafts. Assume that the call data storage device 210 contains "station call data" (2, DN) for car 3 and "car call data" (19, UP) for car 4 and (9, DN) for car 5. Also assume that the direction data storage device 220 contains the "direction data" of the shaft in which each car runs; UP for the first shaft, DN for the second shaft, UP for the third shaft, and DN for the fourth shaft. In addition, the shaft data storage device 240 contains the "shaft data" which indicates the combination of the floor at which the car is moving and the shaft in which the car is moving; (15@1) for car 1, (7@1) for car 2, (3@2) for car 3, (18@3) for car 4, and (10@4) for car 5. To determine a car whose direction is to be reversed, it is necessary to select a car satisfying all the six conditions described above. The conditions will be described in further detail with reference to the flowcharts shown in Figures 33 to 35. In step 1501 (the opposite direction car selection module 1601 executes this step), the reversing car determination device uses "direction data" of the shafts stored in the direction data storage device 220, "shaft data" stored in the shaft data storage device 240, and "new station call data" added to the station call registration device 1 in order to select one or more cars whose direction is opposite to that of the station call added to the station call registration device 1. As a result, the device selects cars 1, 2, and 4. These cars satisfy (condition 1). In step 1503 (the unchecked car selection module 1602 executes this step), the module selects one of the cars selected in step 1501 (here, assume that car 1 is selected). And, in step 1504 (the station call finding module 1603 executes this step), the module checks to see if the call data storage device 210 contains "station call data" for car 1 whose direction is opposite to that of the new station call, (5, DN), and finds that there is no such "station call data." This satisfies (condition 2). Next, in step 1505 (the car call finding module 1604 executes this step), the module checks to see if the call data storage device 210 contains "car call data" for car 1 whose direction is opposite to that of the new station call, (5, DN), and finds that there is no such "car call data." This satisfies (condition 3). In step 1506 (the movement direction finding module 1605 executes this step), the module uses the "direction data" of the shaft of car 1 obtained by the direction data storage device 220 and "new station call data" added to the station call registration device 1 to check to see if the direction of car 1 to respond to the "new station call" is opposite to the direction of the shaft in which car 1 is moving, and finds that the direction is opposite. This satisfies (condition 4). Next, in step 1507 (the other-car finding module 1607 executes this step), the module selects, in the shaft in which car 1 is moving, another car at a floor in the direction to the "new station call (5, DN)" with respect to the current floor and, in step 1508, selects car 2. In step 1509 (the other-car direction finding module 1614 executes this step), the module checks if car 2, selected in the previous step, is moving into the same direction as the direction of the "new station call (5, DN)" (downward), and finds that it is not. ("Direction data" in Table 76 indicates that car 2 is moving upward in the first shaft). Next, in step 1510 (the horizontally-moving floor finding module 1615 executes this step), the module checks to see if there is a horizontally-moving floor between car 1 and car 2, and finds that there is a horizontally-moving floor (tenth floor). And, in step 1511 (the route crossing finding module 1616 executes this step), the module checks if the route of car 2 stored in the route data storage device 290 and the route along which car 1 will move to respond to the "new station call (5, N)" cross each other and finds that they cross. Then, in step 1512 (the route crossing finding module 1616 executes this module), the module checks if car 2 moves horizontally on the horizontally-moving floor along its route and finds that it does. (As shown in Table 77 and Fig. 47, car 2 moves horizontally to the third shaft on the tenth floor). Next, in step 1513 (the horizontally-moving floor arrival car finding module 1618 executes this step), the module uses "car data" estimated by the horizontally-moving floor arrival estimation device 300 to check if car 2 will arrive at the horizontally-moving floor first, and finds that it does. This satisfies (condition 5). This means that, while car 1 is moving in the shaft to respond to the new station call, car 2 will have crossed the horizontally-moving floor, indicating that car 1 and car 2 do not collide. Next, in step 1514 (the horizontal movement finding module 1609 executes this step), the module uses the "shaft data" of the shaft in which car 1 is moving stored in the shaft data storage device 240 and the number of the shaft to which a car is moving horizontally obtained by the horizontal movement destination detection device 250, checks if there is another car moving horizontally to the shaft in which car 1 will move to respond to the "new station call (5, DN)", and finds that there is no such car. This satisfies (condition 6). Thus, car 1, the target car, satisfies all six conditions described above and, therefore, it is determined that "car 1 may be reversed" (step 1516). Then, in step 1517 (the check finish confirming module 1611 executes this step), the module checks if the check is made for all the selected cars, 1, 2 and 4, if they are eligible for a reversing car. Because the check is not yet made for cars 2 and 4, control goes back to step 1503. And, the reversing car determination device checks car 2, selected in step 1503, if it satisfies the above conditions as for car 1. Because the above six conditions are also satisfied for car 2, it is determined that "car 2 may also be reversed." The reversing car determination device also checks car 4, selected in step 1503, if it satisfies the above conditions. And, in step 1505, the device finds that there is a "car call (C, 19, UP)" for car 4 and that one of the above conditions (condition 3) is not satisfied. As a result, the device determines that car 1 and car 2, which satisfy all the six conditions described above, "may be reversed." [21-2-5. Assignment Instruction Processing] The assignment instruction device 270 shown in Fig. 28 uses "reversing car data" determined by the reversing car determination device 260C, "call data" consisting of the car calls and the assigned station calls of the cars stored in the call data storage device 210, "new station call data" added to the station call registration device 1, "direction data" of the shafts in which the cars are moving stored in the direction data storage device 220, "route data" indicating a route along which each car will move stored in the route data storage device 290, and "car data" detected by the car data detection device 2 to determine a car to be used in response to the new station call, issues an instruction to the operation instruction device 280 to cause it to issue an operation instruction to the determined car and, at the same time, stores the station call in the call data storage device 210. The flow of processing in the assignment instruction device 270 will be described with reference to the flowchart in Fig. 24. In step 601, the device checks to see if there are cars that may be reversed. In this embodiment, it is determined that cars 1 and 2 may be reversed. In addition, for cars 3 and 5 which were not selected in step 1501 in the flowcharts in Figures 33 to 35, the device estimates in step 602 the time needed to respond to the new station call based on data such as "call data" (that is, the time needed for those cars to reach the fifth floor). In step 604, the device selects car 2, whose arrival time is the minimum, as the car to respond to the "new station call (5, DN)" and outputs an instruction to the operation instruction device 280 to cause it to issue an operation instruction to car 2 and, at the same time, sends information to the call data storage device 210 indicating that the "new station call (5, DN)" is assigned to car 2. The call data storage device 210 contains call data in the format shown in Table 50. [21.3. Effects of the Twenty-first Embodiment] The elevator group management control apparatus and the elevator group management control method used for the elevator group management control apparatus, shown in the twenty-first embodiment with the above configuration, have the following effects: When determining a car to be used in response to a new station call during elevator group management control, it is possible, before responding to the new station call, to check whether or not there is a car to be reversed without considering the current direction of each shaft; and, if there is such a car, to change the operation direction of the car as necessary. If there is a car which will move to respond to a new station call and there is another car in the same shaft, the check is made in this embodiment to see if the other car moves horizontally. This makes it possible to know if there is a possibility that two cars will collide, ensuring safety when the car is reversed. In addition, because the cars determined to be reversible are also a candidate for the "response car" in this system, the new station call is speedily responded. [22. Twenty-second Embodiment] This embodiment relates to an elevator group management control apparatus corresponding to claim 9 and an elevator group management control method (corresponding to claim 11) used for the elevator group management control apparatus. [22-1. Configuration of the Twenty-second Embodiment] This embodiment is a variation of the twenty-first embodiment with some changes in the configuration of the reversing car determination device. A car is reversed to move to the floor in response to a "new station call" in the twenty-first embodiment, while in this embodiment a car arrives at the floor in response to a "new station call" and then it is reversed. [22-1-1. Configuration of the Elevator Group Management Control Apparatus] The elevator group management control apparatus 3 according to this embodiment is configured in the same manner as in the twenty-first embodiment except that the part of the configuration of the reversing car determination device is changed (see Fig. 28). [22-1-2. Configuration of the Reversing Car Determination Device] The configuration of the reversing car determination device 260D of the elevator group management control apparatus 3 will be described in further detail with reference to Fig. 36. The reversing car determination device 260D used in this embodiment is the reversing car determination device 260C, shown in the thirty-fourth embodiment, with the car call position finding module 1613 and the other-car-between-floor finding module 1620 added. That is, the configuration of the reversing car determination device 260D used in this embodiment is such that the car call finding module 1604, one of the modules, receives the value and the number of the car from the station call finding module 1603, the "car call data" of each car from the call data storage device 210, and "new station call data" added to the station call registration device 1, outputs 0 if the value obtained by the station call finding module 1603 is 0 or, if the value is -1, checks if there is a car call requesting a floor in the direction opposite to the direction of the added station call, and outputs the "car call data" if there is such a car call or, if there is no such car call, -1 and the number of the car; a car call position finding module 1613 is added, the module receiving the value, the number of the car, and "car call data" from the car call finding module 1604 and "new station call data" added to the station call registration device 1, outputting -1 if the value obtained by the car call finding module 1604 is -1 or outputting 0 if the value is 0, and, when "car call data" is entered, checking if the car call requests a floor between the current floor and the floor requested by the new station call, and outputting -1 if the car call requests such a floor or, if it does not, outputting 0 and the number of the car; the movement direction finding module 1605 receives the value and the number of the car from the car call position finding module 1613, "new station call" from the station call registration device 1, and the "direction data" of the shaft in which each car is moving from the direction data storage device 220, outputs 0 if the value obtained from the car call position finding module 1613 is 0, or if the value is -1, checks if the direction of the car to respond to the new station call is the same as the direction of the shaft in which the car is moving, and returns -1 if the direction is the same or, if the direction is opposite, 0 and the number of the car; the after-horizontal-movement direction finding module 1619 receives the value and the number of the car from the horizontal movement finding module 1609, "new station call" from the station call registration device 1, the "direction data" of each car from the direction data storage device 220, and the destination of the horizontally-moving car from the horizontal movement destination detection device 250, outputs 0 if the value obtained from the horizontal movement finding module 1609 is 0 or outputs -1 if the value is -1, checks if, when the number of the other car is entered, the direction of the other car after horizontal movement is opposite to the direction to the new station call, and outputs -1 if the direction is opposite, or if the direction is the same, 0 and the number of the car; and an other-car-between-floor finding module 1620 is added, the module receiving the value and the number of the car from the after-horizontal-movement direction finding module 1619, "new station call data" from the station call registration device 1, and the "shaft data" of the shaft in which each car is moving from the shaft data storage device 240, outputting 0 if the value obtained from the after-horizontal-movement direction finding module 1619 is 0, or if the value is -1, checking if there is another car at a floor between the current floor and the floor requested by the new station call, and outputting 0 if there is such a car or, if there is not such a floor, -1 and the number of the car. The description of the other modules is omitted here because they function as in the reversing car determination device 260C in the twenty-first embodiment. [22-2. Operation of the Twenty-second Embodiment] The twenty-second embodiment having the configuration described above performs operation as follows. [22-2-1. Reversing Car Determination Processing] The reversing car determination device 260D shown in Fig. 36 uses "new station call data" added to the station call registration device 1, the "call data" of each car stored in the call data storage device 210, "direction data" (upward or downward) of the shaft in which each car is moving stored in the direction data storage device 220, "shaft data" of each of the cars stored in the shaft data storage device 240, "route data" representing a route along which each car should move stored in the route data storage device 290, the "car data" on the car arriving at the horizontally-moving floor first estimated by the horizontally-moving floor arrival estimation device 300, and the number of the shaft to which a car is moving horizontally detected by the horizontal movement destination detection device 250, determines a car to be reversed, according to the following conditions, in order to respond to a new station call added to the station call registration device 1, and outputs data on the car to be reversed to the assignment instruction device 270. (A) Conditions under which a reversing car is determined (Condition 1) The direction of the shaft of the target car is opposite to the direction of the "new station call" stored in the station call registration device 1. (The opposite direction car selection module 1601 evaluates this condition). (Condition 2) The call data storage device 210 does not contain a "station call" for the target car whose direction is opposite to the direction of the call added to the station call registration device 1. (The station call finding module 1603 evaluates this condition). (Condition 3) The call data storage device 210 does not contain a "car call" for the target car whose direction is opposite to the direction of the call added to the station call registration device 1. (The car call finding module 1604 evaluates this condition). Or, there is a car call requesting a floor on the way to the floor requested by the new station call. (The car call position finding module 1613 evaluates this condition). (Condition 4) The direction into which the target car must move to respond to the "new station call" added to the station call registration device 1 is the same as the "direction data" of the shaft in which the target car is moving. (The movement direction finding module 1605 evaluates this condition). (Condition 5) One of the following conditions is satisfied, in the shaft in which the target car is moving, for another car on a floor which is in the direction to the new station call with respect to the current floor of the target car: (a) There is no other car. (The other-car finding module 1607 evaluates this condition). (b) The other car is moving into the same direction as the direction of the new station call. (The other-car direction finding module 1614 evaluates this condition). (c) When there is a horizontally-moving floor between the target car and the other car (the horizontally-moving floor finding module 1615 evaluates this condition), when the route of the other car stored in the route data storage device 290 and the route of the target car after responding to the new station call cross each other (the route crossing finding module 1616 evaluates this condition), and when the other car moves horizontally on the horizontally-moving floor (the horizontally-moving route finding module 1617 evaluates this condition), the other car arrives the horizontally-moving floor first (the horizontally-moving floor arrival car finding module 1618 evaluates this condition). (Condition 6) There is a horizontally-moving floor between the floor of the target car and the floor requested by the new station call and there is no other car moving horizontally to the shaft. (The other-car finding module 1609 evaluates this condition). Or, the direction of the other car after horizontal movement is opposite to the direction to the new station call. (The after-horizontal-movement direction finding module 1619 evaluates this condition). (Condition 7) In the shaft in which the target car is moving, there is no other car on a floor between the current floor of the target car and the floor requested by the new station call. (The other-car-between-floor finding module 1620 evaluates this condition). (B) Reversing car determination processing flow Figures 37 to 39 are the flowcharts showing the processing flow of the reversing car determination device 260D which reverses the direction of a car according to the conditions described in (A). The flowcharts in Figures 37 to 39 show how an elevator system, such as the one shown in Fig. 21, processes "call data (4, UP)" added to the station call registration device 1. That is, as shown in Fig. 21, an elevator system in a 20-story building has four elevator shafts. Assume that car 1 is at the fifteenth floor and car 2 is at the seventh floor in the first shaft, car 3 is at the third floor in the second shaft, car 4 is at the eighteenth floor in the third shaft, and that car 5 is at the tenth floor in the fourth shaft. Also assume that cars 1, 2, and 4, each in the stopped state at the respective floor, are ready to close their doors and start operation and that cars 3 and 5 are moving in their shafts. Assume that the call data storage device 210 contains "station call data" (2, DN) for car 3 and "car call data" (19, UP) for car 4 and (9, DN) for car 5. Also assume that the direction data storage device 220 contains the "direction data" of the shaft in which each car runs; UP for the first shaft, DN for the second shaft, UP for the third shaft, and DN for the fourth shaft. In addition, the shaft data storage device 240 contains the "shaft data" which indicates the combination of the floor at which the car is moving and the shaft in which the car is moving; (15@1) for car 1, (7@1) for car 2, (3@2) for car 3, (18@3) for car 4, and (10@4) for car 5. To determine a car whose direction is to be reversed, it is necessary to select a car satisfying all the seven conditions described above. The conditions will be described in further detail with reference to the flowcharts shown in Figures 37 to 39. In step 1801 (the opposite direction car selection module 1601 executes this step), the reversing car determination device uses "direction data" of the shafts stored in the direction data storage device 220, "shaft data" stored in the shaft data storage device 240, and "new station call data" added to the station call registration device 1 in order to select one or more cars whose direction is opposite to that of the station call added to the station call registration device 1. As a result, the device selects cars 3 and 5. These cars satisfy (condition 1). In step 1803 (the unchecked car selection module 1602 executes this step), the module selects one of the cars selected in step 1801 (here, assume that car 3 is selected). And, in step 1804 (the station call finding module 1603 executes this step), the module checks to see if the call data storage device 210 contains "station call data" for car 3 and finds that there is "station call data (H, 2, DN)". This does not satisfy (condition 2). Therefore, it is determined that car 3 may not be reversed. Then, in step 1820 (the check finish confirming module 1611 executes this step), the module checks if the check is made for all the selected cars, 3 and 5, if they are eligible for a reversing car. Because the check is not yet made for car 5, control goes back to step 1803. So, in step 1803, the above check is made for car 5, selected in step 1803, as for car 3. In step 1804 (the module station call finding module 1603 executes this step), the module checks the call data storage device 210 if it contains "station call data" for car 5 and finds that there is no "station call data". This satisfies (condition 2). Then, in step 1805 (the car call finding module 1604 executes this step), the module checks if the call data storage device 210 contains "car call data" for car 5 and finds that it contains "car call data (C, 9, DN)". And, in step 1806 (the car call position finding module 1613 executes this step), the module finds that this "car call" requests a floor on the way to the fourth floor where the "new station call" was generated. This satisfies (condition 3). In step 1807 (the movement direction finding module 1605 executes this step), the module receives the "direction data" of the shafts from the direction data storage device 220 and "shaft data" from the shaft data storage device 240, checks if the direction into which car 5 will move to respond to the "new station call data (4, UP)" is the same as the direction of the shaft in which car 5 is moving, and finds that the direction is the same. This satisfies (condition 4). Next, in step 1808 (the other-car finding module 1607 executes this step), the module selects, in the shaft in which car 5 is moving, an another car in the direction to the "new station call (4, UP)" with respect to the current floor and, in step 1809, the module finds that no such car is selected. This satisfies (condition 5). In step 1815 (the horizontal movement finding module 1609 executes this step), the module receives from the shaft data storage device 240 the "shaft data" of the shaft in which car 5 is moving and, from the horizontal movement destination detection device 250, the number of the shaft to which the a car is moving horizontally, checks if there is a car moving horizontally to the shaft in which car 5 will move to respond to the "new station call (4, UP)", and finds that there is no such car. This satisfies (condition 6). In step 1817 (the other-car-between-floor finding module 1620 executes this step), the module checks if there is another car at a floor between the current floor of car 5 and the floor requested by the new car call and finds that there is no such car. This satisfies (condition 7). Because car 5 satisfies all seven conditions described above, it is determined that "car 5 may be reversed." (step 1819) [22-2-2. Assignment Instruction Processing] The flow of processing in the assignment instruction device 270 will be described with reference to the flowchart in Fig. 24. In step 601, the device checks to see if there are cars that may be reversed. In this embodiment, it is determined that car 5 may be reversed. In addition, for cars 1, 2, and 4 which were not selected in step 1801 in the flowcharts in Figures 37 to 39, the device estimates in step 602 the time needed to respond to the new station call based on data such as "call data" (that is, the time needed for those cars to reach the fourth floor). In step 604, the device selects car 5, whose arrival time is the minimum, as the car to respond to the "new station call (4, UP)" and outputs an instruction to the operation instruction device 280 to cause it to issue an operation instruction to car 5 and, at the same time, sends information to the call data storage device 210 indicating that the "new station call (4, UP)" is assigned to car 5. The call data storage device 210 contains call data in the format shown in Table 51. [22-3. Effects of the Twenty-second Embodiment] The elevator group management control apparatus and the elevator group management control method used for the elevator group management control apparatus, shown in the twenty-second embodiment with the above configuration, have the following effects: When determining a car to be used in response to a new station call during elevator group management control, it is possible, after responding to the new station call, to check whether or not there is a car to be reversed without considering the current direction of each shaft, and, if there is such a car, to change the operation direction of the car as necessary. If there is a car which will move to respond to a new station call and there is another car in the same shaft, the check is made in this embodiment to see if the other car moves horizontally. This makes it possible to know if there is a possibility that two cars will collide, ensuring safety when the car is reversed. In addition, because the cars determined to be reversible are also a candidate for the "response car" in this system, the new station call is speedily responded. INDUSTRIAL APPLICABILITY As described above, this invention provides an elevator group management control apparatus and an elevator group management control method, capable of eliminating occurrence of any locally crowded conditions due to cars' congestion, delay or dead lock alike in such vertical/transversal movable elevator system. And this invention provides an elevator group management control apparatus and an elevator group management control method , capable of placing free cars that are neither on station call nor on car call at optimal locations within a plurality of shafts. In addition, this invention provides an elevator group management control apparatus and an elevator group management control method, capable of controlling the cars, which change the directions of the cars as necessary upon receiving a station call, without being limited by the directions of the shafts. This invention makes it possible to change the direction of a car depending upon the situation and therefore reduces the passenger's waiting time, significantly improving elevator system services . While a preferred embodiment has been described, variations thereto will occur to those skilled in the art within the scope of the present inventive concepts which are delineated by the following claims.

Claims: An elevator group management control apparatus (3) for use in an elevator system comprising a plurality of vertically- and horizontally-movable cars (E1, E2, ...) each capable of stopping at a plurality of floors, a car operation control means (4) controlling the operation of the cars, one or more station call registration means (1) installed in the station of each floor, and a car data detection means (2) detecting the state of each of said cars, said elevator group management control apparatus comprising: route data storage means (24) for storing therein route data with respect to each said car; a call data storage means (21) for storing "call data" consisting of car calls from each of said cars and station calls assigned to each car; target floor instruction means (22) for generating target floor data including a target floor based on call data stored in said call data storage means and station call data stored in said station call registration means; arrival time estimation means (23) for estimating a time as taken for said car to reach said target floor based on said route data, said target floor data, said call data and car data detected by said car data detection means; and assignment instruction means (25) for assigning based on the estimated arrival time as obtained by said arrival time estimation means a certain car to a certain floor call. The apparatus as recited in claim 1, characterized in that said assignment instruction means (25) computes respective non-response times based on the estimated arrival time of one car and that of another car, and for assigning to a station call a car corresponding to the minimal one of the non-response times. The apparatus as recited in claim 1, characterized in that said target floor instruction means (22) generates and issues based on call data of one car and that of another car a target floor data corresponding to the one car, and that said assignment instructions means (25) computes respective non-response time duration based on the estimated arrival time of one car and that of other cars, calculates average values based on the resulting nonresponse time duration, and assigns to the station call a car corresponding to the minimal one of those average values. An elevator group management control apparatus according to claim 1, further comprising: derivative car call estimation means (61) for estimating a derivative car call based on station call data stored in said station call registration means; said target floor instruction means (22) being adapted to generate target floor data including a target floor based on call data stored in said call data storage means, said station call data, and derivative car call data estimated by said derivative car estimation means. The apparatus as recited in claim 4, characterized in that said assignment instruction means (25) computes one or more service completion times based on a time duration as elapsed from a time point for generation of a station call until when said derivative car call will be done in response to a station call, and assigns to the station call a car corresponding to the minimal one of those serve completion times. The apparatus as recited in claim 4, characterized in that said assignment instruction means (25) computes one or more service completion times based on a time duration as elapsed from a time point for generation of a station call until when said derivative car call will be done in response to a station call, and one or more service completion times based on a time duration as elapsed from a time point for generation of a station call until when already-registered car call/derivative car call will be done, calculates average values based on these service completion times, and assigns to the station call a car corresponding to the minimal one of those average values. An elevator group management control method for use in an elevator system comprising a plurality of vertically- and horizontally-movable cars each capable of stopping at a plurality of floors, a car operation control process controlling the operation of the cars, a station call registration process executed at the station of each floor, and a car data detection process detecting the state of each of said cars, said elevator group management control method comprising: a route data storage process storing therein route data with respect to each said car; a call data storage process storing "call data" consisting of car calls from each of said cars and station calls assigned to each car; a target floor instruction process generating target floor data including a target floor based on call data stored by said call data storage process and station call data stored by said station call registration process; an arrival time estimation process estimating a time as taken for said car to reach said target floor based on said route data, said target floor data, said call data and car data detected by said car data detection process; and an assignment instruction process assigning based on the estimated arrival time as obtained by arrival time estimation process a certain car to a certain floor call. An elevator group management control apparatus according to claim 1, further comprising: a direction data storage device (220) receiving "car data" detected by said car data detection device (2) and "call data" stored in said call data storage device (210), estimating the direction of the shaft of each of said cars, and updating and storing resulting data as "direction data"; a number-of-shafts detection device (230) receiving "direction data" stored in said direction data storage device and, for each shaft, finding the number of shafts in the same direction as the direction of the shaft; a shaft data storage device (240) receiving "car data" detected by said car data detection device, estimating the floor and the shaft of each of said cars, and storing resulting data about estimated floors and shafts as "shaft data"; a horizontal movement destination detection device (250) receiving "shaft data" stored in said shaft data storage device, checking the presence of a car moving horizontally, and finding the horizontal movement destination shaft of the car; a reversing car determination device (260) receiving "new station call data" stored in said station call registration device, "call data" stored in said call data storage device, "direction data" of each of said cars stored in said direction data storage device, "shaft data" of each of said cars stored in said shaft data storage device, the number of shafts in the same direction as the direction of each of said cars detected by said number-of-shafts detection device, and the number of a horizontal movement destination shaft detected by said horizontal movement destination detection device and determining a car to be reversed in order to respond to the new station call added to said station call registration device; said assignment instruction device (270) being adapted to receive "reversing car data" determined by said reversing car determination device, "call data" of each of said cars stored in said call data storage device, "new station call data" added to said station call registration device, "direction data" of each of the cars stored in said direction data storage device, and "car data" detected by said car data detection device, determining a car to respond to the new station call and, at the same time, issuing an instruction to cause said call data storage process to store information on the car; and an operation instruction device (280) issuing an operation instruction to a car determined by said assignment instruction device and, if the car is the one determined by said reversing car determination device, issuing another operation instruction to the other car in the shaft of the determined car. An elevator group management control apparatus according to claim 1, further comprising: a direction data storage device (220) receiving "car data" detected by said car data detection device and "call data" stored in said call data storage device, estimating the direction of the shaft of each of said cars, and updating and storing resulting data as "direction data"; a shaft data storage device (240) receiving "car data" detected by said car data detection device, estimating the floor and the shaft of each of said cars, and storing resulting data about estimated floors and shafts as "shaft data"; a horizontally-moving floor arrival estimation device (300) receiving "direction data" of the shaft of each car stored in said direction data storage device, "shaft data" of the shaft of each car stored in said shaft data storage device, and "route data" of a route along which each car should move stored in said route data storage device and, for each shaft, estimating a car arriving at each horizontally-moving floor of each shaft first; a horizontal movement destination detection device (250) receiving "shaft data" stored in said shaft data storage device, checking the presence of a car moving horizontally, and finding the horizontal movement destination shaft of the car; a reversing car determination device (260) receiving "new station call data" stored in said station call registration device, "call data" stored in said call data storage device, "direction data" of each of said cars stored in said direction data storage device, "shaft data" of each of said cars stored in said shaft data storage device, "route data" of each car stored in said route data storage device, the number of a car estimated by said horizontally-moving floor arrival estimation device as a car arriving first at a horizontally-moving floor, and the number of a horizontal movement destination shaft detected by said horizontal movement destination detection device and determining a car to be reversed in order to respond to the new station call added to said station call registration device; said assignment instruction device (270) being adapted to receive "reversing car data" determined by said reversing car determination device, "call data" of each of said cars stored in said call data storage device, "new station call data" added to said station call registration device, "direction data" of each of the cars stored in said direction data storage device, "car data" detected by said car data detection device, and "route data" of each car stored in said route data storage device and determining a car to respond to the new station call and, at the same time, issuing an instruction to cause said call data storage device to store information on the car; and an operation instruction device (280) issuing an operation instruction to a car determined by said assignment instruction device and, if the car is the one determined by said reversing car determination device, issuing another operation instruction to the other car in the shaft of the determined car. An elevator group management control method according to claim 7, further comprising: a direction data storage process receiving "car data" detected by said car data detection process and "call data" stored by said call data storage process, estimating the direction of the shaft of each of said cars, and updating and storing resulting data as "direction data"; a number-of-shafts detection process receiving "direction data" stored by said direction data storage process and, for each shaft, finding the number of shafts in the same direction as the direction of the shaft; a shaft data storage process receiving "car data" detected by said car data detection process, estimating the floor and the shaft of each of said cars, and storing resulting data about estimated floors and shafts as "shaft data"; a horizontal movement destination detection process receiving "shaft data" stored by said shaft data storage process, checking the presence of a car moving horizontally, and finding the horizontal movement destination shaft of the car; a reversing car determination process receiving "new station call data" stored by said station call registration process, "call data" stored by said call data storage process, "direction data" of each of said cars stored by said direction data storage process, "shaft data" of each of said cars stored by said shaft data storage process, the number of shafts in the same direction as the direction of each of said cars detected by said number-of-shafts detection process, and the number of a horizontal movement destination shaft detected by said horizontal movement destination detection process and determining a car to be reversed in order to respond to the new station call added to said station call registration process; said assignment instruction process being adapted to receive "reversing car data" determined by said reversing car determination process, "call data" of each of said cars stored by said call data storage process, "new station call data" added to said station call registration process, "direction data" of each of the cars stored by said direction data storage process, and "car data" detected by said car data detection process, determining a car to respond to the new station call and, at the same time, issuing an instruction to cause said call data storage process to store information on the car; and an operation instruction process issuing an operation instruction to a car determined by said assignment instruction process and, if the car is the one determined by said reversing car determination process, issuing another operation instruction to the other car in the shaft of the determined car. An elevator group management control method according to claim 7, further comprising: a direction data storage process receiving "car data" detected by said car data detection process and "call data" stored by said call data storage process, estimating the direction of the shaft of each of said cars, and updating and storing resulting data as "direction data"; a shaft data storage process receiving "car data" detected by said car data detection process, estimating the floor and the shaft of each of said cars, and storing resulting data about estimated floors and shafts as "shaft data"; a horizontally-moving floor arrival estimation process receiving "direction data" of the shaft of each car stored by said direction data storage process, "shaft data" of the shaft of each car stored by said shaft data storage process, and "route data" of a route along which each car should move stored by said route data storage process and, for each shaft, estimating a car arriving at each horizontally-moving floor of each shaft first; a horizontal movement destination detection process receiving "shaft data" stored by said shaft data storage process, checking the presence of a car moving horizontally, and finding the horizontal movement destination shaft of the car; a reversing car determination process receiving "new station call data" stored by said station call registration process, "call data" stored by said call data storage process, "direction data" of each of said cars stored by said direction data storage process, "shaft data" of each of said cars stored by said shaft data storage process, "route data" of each car stored by said route data storage process, the number of a car estimated by said horizontally-moving floor arrival estimation process as a car arriving first at a horizontally-moving floor, and the number of a horizontal movement destination shaft detected by said horizontal movement destination detection process and determining a car to be reversed in order to respond to the new station call added to said station call registration process; said assignment instruction process being adapted to receive "reversing car data" determined by said reversing car determination process, "call data" of each of said cars stored by said call data storage process, "new station call data" added to said station call registration process, "direction data" of each of the cars stored by said direction data storage process, "car data" detected by said car data detection process, and "route data" of each car stored by said route data storage process and determining a car to respond to the new station call and, at the same time, issuing an instruction to cause said call data storage process to store information on the car; and an operation instruction process issuing an operation instruction to a car determined by said assignment instruction process and, if the car is the one determined by said reversing car determination process, issuing another operation instruction to the other car in the shaft of the determined car. An elevator group management control apparatus according to claim 1, further comprising: checking, for a target car to be checked if the car is to respond to a new station call, the operation state of the other car in the same shaft of the target car and the operation state of some other car moving horizontally from some other shaft, based on route data indicating each route in vertical and horizontal directions through which each of said cars should be operated, and reversing said target car when it is confirmed that said target car, if reversed, will not collide with any of said other cars and when it is determined that said target car is able to arrive at the floor requested by the new station call first. An elevator group management control method according to claim 7, further comprising: checking, for a target car to be checked if the car is to respond to a new station call, the operation state of the other car in the same shaft of the target car and the operation state of some other car moving horizontally from some other shaft, based on route data indicating each route in vertical and horizontal directions through which each of said cars should be operated, and reversing said target car when it is confirmed that said target car, if reversed, will not collide with any of said other cars and when it is determined that said target car is able to arrive at the floor requested by the new station call first. A carriage management control apparatus for controlling a plurality of carriages (E1, E2, ...) each capable of moving across a plurality of shafts comprising: storage means (24) for storing route data describing a route along which a carriage moves in vertical directions in said shafts and in horizontal directions across said shafts; and management means (3) for managing the operation of said carriages in vertical directions in said shafts and in horizontal directions across said shafts according to said route data. A carriage management control apparatus according to claim 14, wherein said management means (3) comprises estimation means (23) for estimating a time, required for said carriage to arrive at a target position, based on said route data. A carriage management control apparatus according to claim 15, wherein said management means (3) further comprises assignment means (25) for assigning a carriage based on said estimated arrival time. A carriage management control apparatus according to claim 16, wherein said assignment means comprises: non-response time calculation means for calculating a non-response time based on the estimated arrival time of a carriage and the estimated arrival time of another carriage; and selection means for selecting a carriage corresponding to the minimum non-response time. A carriage management control apparatus according to claim 14, wherein said management means further comprises target position data generation means for generating target position data for moving said carriage to a target position based on call data consisting of carriage calls given from said carriage and station calls given to said carriage. A carriage management control apparatus according to claim 16, wherein said assignment means comprises: non-response time calculation means for calculating a non-response time based on the estimated arrival time of a carriage and the estimated arrival time of another carriage; average time calculation means for calculating average times based on non-response time; and selection means for selecting a carriage corresponding to the minimum average time. A carriage management control apparatus according to claim 14, further comprising collection means for collecting information on the state of said carriages. A carriage management control apparatus according to claim 16, further comprising second estimation means for estimating derivative carriage calls based on station call data given at a position where said carriage is to stop. A carriage management control apparatus according to claim 21, wherein said assignment means comprises: service completion time calculation means for calculating a service time from the time said station call data is given to the time a derivative carriage call estimated by second estimation means is responded; and selection means for selecting a carriage corresponding to the minimum time. A carriage management control apparatus according to claim 21, further comprising: first calculation means for calculating the first service completion time required from the time said station call data is given to the time a derivative carriage call estimated by said second estimation means is responded; second calculation means for calculating the second service completion time required to respond to an already-given carriage call and derivative carriage call; and selection means for calculating the average times based on said first service completion time and said second service completion time and for selecting a carriage corresponding to the minimum average time. A recording medium containing an elevator group management control program for use in an elevator system comprising a plurality of vertically- and horizontally-movable cars (E1, E2, ...) each capable of stopping at a plurality of floors, a car operation control process controlling the operation of the cars, a station call registration process executed at the station of each floor, and a car data detection process detecting the state of each of said cars, said elevator group management control program comprising: a route data storage step for storing therein route data with respect to each said car; a call data storage step for storing "call data" consisting of car calls from each of said cars and station calls assigned to each car; a target floor instruction step for generating target floor data including a target floor based on call data stored by said call data storage process and station call data stored by said station call registration process; an arrival time estimation step for estimating a time as taken for said car to reach said target floor based on said route data, said target floor data, said call data and car data detected by said car data detection process; and an assignment instruction step for assigning based on the estimated arrival time as obtained by arrival time estimation process a certain car to a certain floor call. A recording medium according to claim 24, said program further comprising: a direction data storage step for receiving "car data" detected by said car data detection step and "call data" stored by said call data storage step, for estimating the direction of the shaft of each of said cars, and updating and for storing resulting data as "direction data"; a number-of-shafts detection step for receiving "direction data" stored by said direction data storage step and, for each shaft, for finding the number of shafts in the same direction as the direction of the shaft; a shaft data storage step for receiving "car data" detected by said car data detection step, for estimating the floor and the shaft of each of said cars, and for storing resulting data about estimated floors and shafts as "shaft data"; a horizontal movement destination detection step for receiving "shaft data" stored by said shaft data storage step, for checking the presence of a car moving horizontally, and for finding the horizontal movement destination shaft of the car; a reversing car determination step for receiving "new station call data" stored by said station call registration step, "call data" stored by said call data storage step, "direction data" of each of said cars stored by said direction data storage step, "shaft data" of each of said cars stored by said shaft data storage step, the number of shafts in the same direction as the direction of each of said cars detected by said number-of-shafts detection step, and the number of a horizontal movement destination shaft detected by said horizontal movement destination detection step and for determining a car to be reversed in order to respond to the new station call added to said station call registration step; said assignment instruction step being adapted to receive "reversing car data" determined by said reversing car determination step, "call data" of each of said cars stored by said call data storage step, "new station call data" added to said station call registration step, "direction data" of each of the cars stored by said direction data storage step, and "car data" detected by said car data detection step, to determine a car to respond to the new station call and, at the same time, to issue an instruction to cause said call data storage step to store information on the car; and an operation instruction step for issuing an operation instruction to a car determined by said assignment instruction step and, if the car is the one determined by said reversing car determination step, for issuing another operation instruction to the other car in the shaft of the determined car. A recording medium according to claim 24, said program further comprising: a step for checking, for a target car to be checked if the car is to respond to a new station call, the operation state of the other car in the same shaft of the target car and the operation state of some other car moving horizontally from some other shaft, based on route data indicating each route in vertical and horizontal directions through which each of said cars should be operated, and a step for reversing said target car when it is confirmed that said target car, if reversed, will not collide with any of said other cars and when it is determined that said target car is able to arrive at the floor requested by the new station call first.

Inventors: IMASAKI NAOKI, KIJI JUNICHI, KUBO SUSUMU, NAKAI SHOJI, YAMAURA MITSUYO, YOSHITSUGU TATSUO, IMASAKI, NAOKI, KIJI, JUNICHI, KUBO, SUSUMU, NAKAI, SHOJI, YAMAURA, MITSUYO, YOSHITSUGU, TATSUO, NAKAI, SHOJI ROOM 502
Applicants: TOSHIBA KK, KABUSHIKI KAISHA TOSHIBA
Application year: 1996
Main classification: B66B1
IPC codes: B66B9, B66B1