Mobile queue management system and management method

Abstract

To provide a moving body queue management system that enables the planning of a scheduled queue line of moving bodies in consideration of a main flow line.SOLUTION: A moving body queue management system 1 for managing a queue of moving bodies comprises: an information management section 13 that manages movement information on the movement of the moving bodies; and a scheduled queue line planning section 11 that plans, on the basis of the movement information, a scheduled queue line for leading moving bodies to a queue so that at least a part of the queue of the moving bodies intersects a main flow line 25.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to a mobile queue management system and a management method. [Background technology]

[0002] At facilities such as stations, airports, and commercial stores, queues for services may occur. When a queue for a service occurs during peak hours, it can obstruct the passage of people who are not interested in the service, so the queue line is adjusted by stretching guide ropes or having staff guide the queue.

[0003] In recent years, there has been a demand for technology that automates the adjustment of queue positions for facility users in order to reduce personnel costs. Prior art for guiding queue positions is disclosed in Patent Document 1 and Patent Document 2.

[0004] Patent Document 1 discloses a technology that determines the position of the next person to line up on a specific queue line based on the end of the queue captured by image recognition, etc., and displays guidance information on digital signage, etc. to guide users.

[0005] Patent Document 2 discloses a technology that subtracts the capacity of a transportation facility such as a train from the predicted number of people using the facility to determine the number of people who cannot use the facility, and creates an guidance plan based on the capacity of a waiting area in a station or the like. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Patent Publication No. 2020-086508 [Patent Document 2] Patent Publication 2015-108913 Summary of the Invention [Problem to be solved by the invention]

[0007] The technologies described in Patent Documents 1 and 2 above do not take into account traffic lines other than the queue, and therefore cannot adjust the relationship between the queue and traffic lines other than the queue. As a result, the queue may extend into areas with heavy traffic, causing a hindrance to passersby.

[0008] The present invention has been made in consideration of the above-mentioned problems, and its object is to provide a mobile object queue management system and management method that can plan the scheduled queue line of mobile objects taking into account the main traffic lines. [Means for solving the problem]

[0009] In order to solve the above-mentioned problems, a mobile object queue management system according to one aspect of the present invention is a mobile object queue management system that manages a queue of moving objects, and includes an information management unit that manages movement information related to the movement of the moving objects, and a queue planned line planning unit that plans a planned queue line for guiding the moving objects into the queue based on the movement information so that at least a portion of the queue of moving objects intersects with a main traffic line. Effect of the Invention

[0010] According to the present invention, it is possible to plan a planned queue line for guiding moving objects into a queue so that at least a portion of the queue of moving objects intersects with a main traffic line. [Brief description of the drawings]

[0011] [Figure 1] 1 is an overall schematic diagram of a people flow guidance system as a "mobile object queue management system" according to an embodiment of the present invention. [Diagram 2] FIG. 1 is a block diagram showing a basic configuration of a people flow control system. [Diagram 3] FIG. 2 is a hardware configuration diagram of the people flow control system. [Figure 4] 1 is a flowchart showing the overall processing of the people flow guidance system. [Diagram 5] 13 is an example of a flow line table of a flow line database. [Figure 6] 1 is an example of a queue state table of the queue state database. [Figure 7] 1 is an example of an obstacle table of a map database. [Figure 8] 13 is an example of a restricted passage area table in a map database. [Figure 9] 13 is an example of a main flow line table of the main flow line database. [Figure 10] 13 is an example of a matrix line definition condition table in the condition database. [Figure 11] 13 is an example of a table of the expected number of people in a queue in the condition database. [Figure 12] 13 is an example of a queue schedule line table of the queue schedule line database. [Figure 13] 13 is a flowchart of a queue schedule line planning process. [Figure 14] 13 is a flowchart of a guidance content determination process. [Figure 15] An example of a queue guide screen is shown. [Figure 16] 13 is a flowchart of a main flow line detection process. [Figure 17] 13 is a flowchart of a queue planning process. [Figure 18] 1 is an example of a user interface screen provided by the people flow control system. [Figure 19] 13 is an example of a screen for editing obstacle data. [Figure 20] 13 is an example of a screen for editing a main flow line. [Figure 21] 13 is an example of a screen for editing a matrix condition. [Figure 22] 13 is an example of a screen for editing a queue schedule line. [Diagram 23] 13 is an example of a screen for editing the expected number of people in line. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. The people flow guidance system as a "mobile object queue management system" of this embodiment plans a planned queue line for guiding mobile objects to the queue so that at least a part of the queue of mobile objects intersects with a main flow line. In this way, the people flow guidance system can manage the queue for receiving service even during busy times.

[0013] The people flow guidance system of this embodiment can be equipped with, for example, a flow line DB that holds data on the flow lines of moving objects, and a queue line planning unit that plans the guidance position of the queue of moving objects by changing the spacing and extension direction of the queue of moving objects based on the flow line DB.

[0014] The people flow guidance system of this embodiment includes a main flow line detection unit that detects the area of ​​the main flow line and its direction of movement based on the flow line DB, and the queue planned line planning unit can plan the queue guidance position by changing the spacing and extension direction of the queue of moving objects in the main flow line area based on the direction of movement of the main flow line.

[0015] The people flow guidance system of this embodiment includes a people flow prediction unit that predicts movement lines in a target area, and a planned number of people calculation unit that calculates the number of people who will line up in a queue based on the predicted movement line data, and the planned queue line planning unit can re-plan the queue line if the number of people calculated by the planned number of people calculation unit does not fit within the planned queue line.

[0016] The queue line planning unit of the people flow guidance system of this embodiment can plan the guidance position of the queue of moving objects by changing the spacing and extension direction of the queue of moving objects based on the predicted movement line data and using information on the main movement lines detected by the main movement line detection unit.

[0017] In this embodiment, a person is used as an example of a moving body, but the present invention is not limited to pedestrians, and can also be applied to queues of people using transportation means such as bicycles, cars, kickboards, etc. Furthermore, the present invention can also be applied to machines with automatic driving functions, such as drones, automatic guided vehicles, self-propelled robots, cars, construction machines, ships, and submarines, as moving bodies.

[0018] The people flow guidance system of the present embodiment can be applied to queue management in a real facility, as well as in a virtual space. Examples of the real facility or the facility in the virtual space include a station, an airport, a commercial store, a stadium, an exhibition center, and the like. EXAMPLES

[0019] A first embodiment will be described with reference to Figs. 1 to 23. Fig. 1 is an overall schematic diagram of a people flow guidance system 1 according to this embodiment. The configuration of Fig. 1 shows an overview of the people flow guidance system 1 to the extent necessary for understanding and implementing this embodiment, and the scope of the present disclosure is not limited to the illustrated configuration. A part of the configuration shown in Fig. 1 may be omitted, and a new configuration not shown may be added to the configuration shown in Fig. 1.

[0020] At busy times in facilities 2 such as stations, airports, and commercial stores, queues for various services may grow and impede the flow of people passing by. Services include, for example, ticket sales, admission ticket sales, baggage check-in, baggage delivery, merchandise sales, and food and drink provision.

[0021] If queues for a service are long, it is also necessary to ensure that the queue is long enough. If the queue can accommodate fewer people than the number of people using the service, it will be difficult to maintain an orderly queue.

[0022] Therefore, if the queue for a service becomes long when the facility is crowded, it is necessary to organize the queue by utilizing areas with high traffic volume 25 (main traffic routes 25) so as not to obstruct the movement of passersby 251 who are not related to the service.

[0023] Therefore, the people flow guidance system 1 of this embodiment plans queue lines that ensure sufficient queue length while not obstructing passersby 251, and uses the queue guide unit 21 installed within the facility 2 to guide people as to where they should line up.

[0024] When planning queue lines, it is necessary to devise a way to avoid obstructing the flow line 25, especially in areas 25 with high traffic volume. Therefore, in the people flow guidance system 1 of this embodiment, the main flow line 25 at the target time is detected based on flow line data measured by a measurement system 31 such as a laser radar or a camera, and the planned queue line is planned so as not to obstruct the flow line by changing the extension direction of the queue and the interval L1 with respect to the main flow line 25.

[0025] Here, the target time is the time when the people flow guidance system 1, the measurement system 31, and the queue guide unit 21 are operated to guide people who are the guidance targets. The main flow lines refer to a group of divided flow lines in which the number of flow lines per unit area is equal to or greater than a certain value when the flow lines are divided into a predetermined time width and into pass areas. The division of the flow lines into pass areas may be performed, for example, by dividing the target area into a grid, determining spatial intersections with each divided area, and based on the results of the determination. Alternatively, the target area may be divided based on a group of arbitrarily set boundaries, and information on each divided area may be used. The planned queue line refers to the queue line along which people who have come to join the queue are planned to be guided.

[0026] Facility 2 will now be described. A counter 22 that provides a service is provided on floor 20 of facility 2. Counter 22 can also be called, for example, a service provision point. A queue 24 is formed with person P1, who is in front of counter 22, at the head, and people P2 and P3 who wish to receive the service.

[0027] The queue guidance unit 21 guides a new user (person wishing to use) P4 to a waiting position that is the next position to the end of the queue. As described later, the people flow guidance system 1 can plan the expected queue line so that it intersects with the main flow line 25.

[0028] The other new user is instructed by the queue guide unit 21 to wait at a waiting position P5 within the area of ​​the main flow line 25. At this time, within the area of ​​the main flow line 25, the queue interval L1 is set to be longer than the interval L2 outside the area of ​​the main flow line 25 (L1>L2). Therefore, the other new user is guided to a waiting position P5 that is slightly further ahead than the waiting position Pc1 obtained from the original queue interval L1.

[0029] In the people flow guidance system 1 of this embodiment, the queue interval L1 within the main flow line area is lengthened to ensure a passageway for pedestrians 251 traveling along the main flow line 25. After the queue has passed through the main flow line area, the queue interval may be returned from the distance L1 to the original distance L2, or may be set to a different distance L3.

[0030] As described above, symbols P1 to P9 indicate waiting positions for people waiting in line (service users) or service users. If there is an obstacle 23 (or a restricted passage area) beyond the end of the line that has crossed the main traffic line area, and the number of people who can stay in line before the end of the line reaches the obstacle 23 is smaller than the planned number of people in the line, the line cannot continue.

[0031] Therefore, the people flow guidance system 1 changes the direction of the queue from the waiting position Pc2 to the waiting position P8 in order to secure the length of the queue. In this example, the direction is changed by about 90 degrees, but the direction of the queue may be changed by an angle other than 90 degrees. The angle at which the queue crosses the main flow line may be 90 degrees or may be a value other than 90 degrees. Furthermore, the queue may cross the same main flow line multiple times. For example, after the queue crosses the main flow line at a first angle at a first point, it may cross the main flow line again at a second angle at a second point away from the first point in the direction of the main flow line. The first angle and the second angle may be the same value or different values.

[0032] Therefore, the queue organized by the people flow guidance system 1 can be divided into a first queue area (P1-P4) before interfering with the main flow line area, a second queue area that interfers with the main flow line area, and a third queue area (P6-P9) after passing through the main flow line area, with the service provision point 22 at the head. Furthermore, the third queue area can also be divided into a pre-direction change area (P6, P7) before the queue direction is changed, and a post-direction change area (P8, P9) after the queue direction is changed. Although not shown in the figure, if the queue extends further, it may enter other flow line areas, pass through other flow line areas, and change direction.

[0033] We will now describe an example of the configuration of the people flow guidance system 1. The people flow guidance system 1 can include, for example, a planned queue line planning unit 11, an information acquisition unit 12, an information management unit 13, a queue determination unit 14, a guidance content determination unit 15, and a queue information provision unit 16.

[0034] The information acquisition unit 12 acquires measurement data from the measurement system 31. The information management unit 13 manages the acquired information. The queue determination unit 14 determines whether a queue has occurred. The guidance content determination unit 15 determines guidance content including the guidance position (the position to guide to the end of the queue) calculated by the queue forecast line planning unit 11, and sends it to the queue guidance unit 21.

[0035] The queue information providing unit 16 provides queue-related information to the service provider at the service counter 22 or the manager of the facility 2. The queue-related information includes, for example, the head position of the queue, the end position of the queue, the number of people in the queue, the queue growth rate (people / hour), and the like.

[0036] The queue schedule line planning unit 11 manages queues that occur on a floor 20 where a service provision point, that is, a counter 22, is located, and calculates instructions for organizing the queues. The queue schedule line planning unit 11 can manage multiple queues on the same floor 20, and can also manage queues on each of multiple floors of the facility 2. Furthermore, the people flow guidance system 1 can centrally manage multiple queues on multiple floors 20 of multiple facilities 2 that are geographically distributed.

[0037] The expected queue line planning unit 11 includes, for example, a flow line prediction unit 111, a main flow line detection unit 112, an expected number of people calculation unit 113, a queue planning unit 114, and a guide position calculation unit 115.

[0038] The flow line prediction unit 111 predicts the flow line (people flow) on the managed floor 20 based on information from the information management unit 13. The main flow line detection unit 112 detects the main flow line 25 based on the predicted flow line. The expected number of people calculation unit 113 calculates the length of the queue, that is, the maximum number of people waiting in the queue.

[0039] The queue planning unit 114 plans a planned queue line based on the maximum number of people in the queue and the main flow line. The guide position calculation unit 115 calculates a position to line up in the queue according to the planned queue line.

[0040] The people flow guidance system 1 receives measurement data from the measurement system 31 and map data from a user of the people flow guidance system 1. The people flow guidance system 1 includes a function 112 for detecting main flow lines 25 in a target area (floor 20 to be managed) using flow line data extracted from the measurement data, a function 113 for calculating the expected number of people waiting in line, a function 114 for planning a planned queue line from the main flow lines, the expected number of people, map data, etc., and a function 115 for calculating guidance information from the planned queue line, the flow line data, the map data, and the main flow line data. The calculated guidance information is transmitted to the queue guidance unit 21 and displayed to people waiting in line.

[0041] The guidance content determination unit 15 can provide information via the queue guidance unit 21 not only to those who are waiting in line (service users) but also to passersby 251 (other moving objects) who are not related to the service that is causing the queue.

[0042] The guidance content determination unit 15 provides the first content to those directly involved in the queue (service users), and provides the second content to those not directly involved in the queue (passersby). The first content can include, for example, a message such as "Those using the service SA, please line up at the location we will guide you to. The current waiting time is approximately 45 minutes," and a map showing the waiting location. A modified example of the first content provided to service users waiting in the main traffic line area can include, for example, a message such as "Those using the service SA, please line up at the location we will guide you to. Please be careful not to get in the way of passersby. The current waiting time is approximately 45 minutes," and a map showing the waiting location.

[0043] The second content may include, for example, a message such as "There is a queue for service SA up ahead. Please be careful" and a map showing the location of the queue. Here, for example, if it is possible to illuminate people waiting in the main traffic line area from above, change the color of the floor of the waiting position, or shine laser lights around the waiting position, a message such as "The floor of people waiting in line is lit in red, so please be careful" may be added to the second content.

[0044] The first content or the second content may be transmitted individually to a service user (a person who is about to queue) or a passerby, or may be transmitted collectively to a plurality of people in a predetermined area on floor 20. When transmitting individually, for example, a directional speaker that transmits sound only to a specific range may be used, or a text message or a voice message may be delivered to a mobile information terminal (wearable terminal, smartphone, etc.) carried by a service user or a passerby. For example, when it is detected that a mobile information terminal of a service user who has received numbered ticket data for using the service in advance has entered facility 2, the first content can be transmitted to the mobile information terminal.

[0045] 2 is a functional block diagram of the people flow guidance system 1. The people flow guidance system 1 includes the following functional blocks.

[0046] The people flow guidance system 1 includes, as the information acquisition unit 12, for example, a flow line data extraction unit 121, a map data input unit 122, a main flow line data input unit 123, a queue condition input unit 124, and a scheduled queue line input unit 125.

[0047] The people flow guidance system 1 includes, as the information management unit 13, for example, a flow line DB 131, a queue state DB 132, a map DB 133, a main flow line DB 134, a condition DB 135, and a scheduled queue line DB 136.

[0048] The flow line data extraction unit 121 of the information acquisition unit 12 extracts flow line data based on the sensor data received from the measurement system 31. Details will be described later.

[0049] Data is input to each of the other functions 122 to 125 of the information acquisition unit 12 from input means 32 such as a user interface (UI in the figure), a communication interface (communication I / F in the figure), or an input / output port (I / O in the figure).

[0050] The user interface is connected to an information input / output device (not shown), and a user can use the information input / output device to input data to the people flow guidance system 1. The information input / output device may be, for example, a monitor display, a keyboard, a pointing device such as a mouse, a touch panel, or a voice input device.

[0051] In addition, a user can input data to each of the functions 122-125 by transferring data stored in a storage device (not shown) to the people flow guidance system 1. The storage device (not shown) may be, for example, a storage device used by a server on a communication network, or a storage device such as a semiconductor memory directly connected to the people flow guidance system 1.

[0052] Each block will be explained. Here, an example will be explained in which multiple matrices are processed in parallel. The multiple matrices to be processed may be on the same floor or on different floors. The multiple matrices to be processed may be in different facilities. In this case, a measurement system 31 and the like are prepared for each facility.

[0053] Upon receiving data measured by the measurement system 31, the flow line data extraction unit 121 has a function of extracting flow line data from the received data and storing it in the flow line DB 131. At this time, the data measured by the measurement system 31 may be video data of the target area or laser radar data. When extracting flow line data from video data, people may be recognized using image processing technology and their coordinates may be extracted. When extracting flow line data from laser radar data, moving objects whose distance from the laser radar changes may be extracted as people and converted into coordinate information.

[0054] The queue determination unit 14 determines when, in which queue, and in which order each person (service user) is lined up, based on the flow line data, map data, and queue head point data. For example, when the flow line data in the flow line DB 131 is updated, or whenever a certain period of time has elapsed, the queue determination unit 14 has a function of determining when, in which queue, and in which order each person is lined up, using the flow line data in the flow line DB 131, the obstacle data in the map DB 133, and the queue line definition condition data in the condition DB 135, and storing the determination result in the queue state DB 132.

[0055] The map data input unit 122 has a function of receiving from the user data representing the positions and shapes of obstacle areas where people cannot pass and data representing the positions and shapes of areas where passage is restricted in the target area, and storing the data in the map DB 133. The data may be input manually by the user or as a file.

[0056] The main flow line data input unit 123 has a function of receiving data indicating the position, shape, direction of travel, and time period of occurrence of main flow lines in the target area from the user, and storing the data in the main flow line DB 134.

[0057] The matrix condition input unit 124 has a function of receiving data indicating the head position of the matrix and data indicating the direction in which the matrix extends from the head (initial direction) from the user, and storing them in the condition DB 135.

[0058] The queue planned line input unit 125 has a function of receiving data indicating the position and shape of the queue planned line from the user, and storing the data in the queue planned line DB 136.

[0059] When the expected queue line planning unit 11 receives the flow line data stored in the flow line DB 131, the queue state data stored in the queue state DB 132, the obstacle data and the restricted passage area data stored in the map DB 133, and the queue line definition condition data stored in the condition DB 135, it executes a people flow simulation or the like to predict the flow line.

[0060] The expected queue line planning unit 11 extracts a main flow line based on the measured flow line data and the predicted flow line data, and stores the extracted main flow line data in the main flow line DB 134. The expected queue line planning unit 11 uses the detected main flow line data, the queue state data stored in the queue state DB 132, and the flow line data stored in the flow line DB 131 to obtain data on how to adjust the guidance positions of people waiting in line with respect to the main flow line, and transmits the data to the guidance content determination unit 15.

[0061] The queue planned line planning unit 11 determines the maximum number of people lining up in each queue based on the predicted traffic line data, calculates the planned number of people that each queue will accommodate based on the determined maximum number of people, and stores the calculated data of the planned number of people that will be accommodated in the condition DB 135.

[0062] The planned queue line planning unit 11 has a function of defining a planned queue line for each queue using the calculated planned number of people data for each queue, the detected main flow line data, the flow line data stored in the flow line DB131, the queue state data stored in the queue state DB132, the obstacle data and the restricted passage area data stored in the map DB133, the planned queue line definition condition data stored in the condition DB135, and the correction data for the queue guidance position, and storing the defined planned queue line in the planned queue line DB136.

[0063] In order to realize the above functions, the expected queue line planning unit 11 includes, for example, a flow line prediction unit 111, a main flow line detection unit 112, an expected number of people calculation unit 113, a queue planning unit 114, and a guide position calculation unit 115. The details of each unit will be described later.

[0064] The guidance content determination unit 15 receives the flow line data stored in the flow line DB 131, the queue state data stored in the queue state DB 132, the queue planned line data stored in the queue planned line DB 136, and the correction data for the queue guidance position transmitted from the queue planned line planning unit 11.

[0065] A guidance content determination unit 15 judges which position on the planned queue line corresponds to the end of the actual queue based on the flow line data and queue state data, and determines the guidance position on the planned queue line for the next person to line up in each queue based on the judgment result.

[0066] The guidance content determination unit 15 calculates the guidance position of the queue at the overlapping point where the main flow line area and the planned queue line overlap, based on the flow line data, the queue state data, and the queue guidance position correction data. As described above, in the area where the planned queue line overlaps with the main flow line area, it is necessary to increase the distance between adjacent service users so as not to obstruct the passage of passersby who are not service users as much as possible. Then, the guidance content determination unit 15 transmits the calculated guidance position to the queue guidance unit 21.

[0067] The data stored in the flow line DB 131, the queue state DB 132, the map DB 133, the main flow line DB 134, the condition DB 135, and the scheduled queue line DB 136 will be described later.

[0068] 4 is a hardware configuration diagram of the entire system including the people flow guidance system 1. The people flow guidance system 1 is configured as a computer including a processor 101, a memory 102, a communication interface 103, a user interface 104, and a media interface 105, for example.

[0069] The memory 102 includes a main storage device and an auxiliary storage device. The memory 102 stores a computer program 1021 and data 1022. The processor 101 realizes each function of the people flow guidance system 1 by reading and executing the computer program 1021 stored in the memory 102. The processor 101 is not limited to a microprocessor, and may include a GPU (Graphics Processing Unit) or a dedicated circuit.

[0070] The communication interface 103 is connected to the queue guide unit 21, the measurement system 31, and the other system 4 via the communication network CN. The other system 4 is, for example, a computer used by a provider of a service that causes a queue, a computer that manages the security of the facility 2, etc.

[0071] The user interface 104 is connected to an information input / output device 106. The information input / output device 106 includes, for example, a monitor display, a keyboard, a mouse, and a touch panel. The medium interface 105 is connected to a storage medium MM. The storage medium MM is, for example, a semiconductor memory, a hard disk, an optical disk, and the like. At least a part of the computer program 1021 and the data 1022 of the people flow guidance system 1 can be transferred to and stored in the storage medium MM. Conversely, at least a part of the computer program and the data stored in the storage medium MM can also be transferred to and stored in the memory 102 of the people flow guidance system 1.

[0072] The queue guidance unit 21 includes at least one information transmission device, such as a display device 211, an audio device 212, and a lighting device 213. The display device 211 is, for example, a large monitor display having a communication function, known as a so-called digital signage, and is installed on a wall or a pillar in the facility 2. The audio device 212 is configured like a speaker system. When a person in the facility 2 wears an earphone capable of communication, the earphone can also be used as the audio device 212. The lighting device 213 is a ceiling lighting device, a floor lighting device, a wall lighting device, or the like. The service user can be guided by illuminating the position where the service user should wait with lighting such as a laser light or changing the color of the floor corresponding to the position. The display device 211, the audio device 212, and the lighting device 213 can also be used in combination.

[0073] A portable information terminal carried by a service user or a passerby in facility 2 may be used as queue guidance unit 21. Guidance information determined by people flow guidance system 1 may be sent to the portable information terminal as an email or a short message. An admission ticket to facility 2 may be provided with communication and display functions, and guidance information from people flow guidance system 1 may be distributed via a short-distance communication network installed in facility 2.

[0074] The measurement system 31 measures the movement of people within the facility 2 and transmits the measurement data to the people flow guidance system 1. The measurement system 31 includes, for example, at least one of a laser measurement system 311, a camera system 312, and a terminal positioning system 313. The laser measurement system 311 detects the position and movement of people within the facility 2 using a laser radar. The camera system 312 photographs the inside of the facility 2 and detects people from the photographed image data. The terminal positioning system 313 is configured as a portable information terminal carried by a person within the facility 2, and identifies the position of the person carrying the terminal. These systems 311 to 313 may be used in combination.

[0075] The flowchart in Fig. 4 shows the overall process performed by the people flow guidance system 1. Hereinafter, the reference numeral (here, S10) attached to the first step of the process indicates the start of the process, but the entire process shown in the figure may be represented by the reference numeral.

[0076] The people flow guidance system 1 calculates the main flow line and the number of people expected to stand in line at a target time based on the flow line data, map data, and queue line condition data, and defines the scheduled queue line at the target time using the calculated results, etc. (S11). Step S11 is mainly performed by the scheduled queue line planning unit 11 as follows.

[0077] The expected queue line planner 11 predicts a flow line at a target time, for example, using the flow line data stored in the flow line DB 131 and the obstacle data stored in the map DB 133. The people flow guidance system 1 detects main flow lines in the target area together with their occurrence times based on the measured flow line data and the predicted flow line data, and stores the detected main flow line data in the main flow line DB 134.

[0078] The expected queue line planning unit 11 uses the detected main flow line data, the queue state data stored in the queue state DB 132, and the flow line data stored in the flow line DB 131 to calculate data regarding how to adjust the guidance positions of people waiting in line with respect to the main flow line, and transmits the calculated data to the guidance content determination unit 15.

[0079] The estimated queue line planning unit 11 calculates the maximum number of people lining up in each queue within the target area at the target time based on the predicted traffic line data for the target time, and stores the estimated number of people to be accommodated based on the calculated maximum number of people in a estimated queue number table in the condition DB 135 together with the start time and end time of each time period.

[0080] The scheduled queue line planning unit 11 defines a scheduled queue line at a target time for each predetermined time span using the main flow line data, data on the scheduled number of people that each queue can accommodate, flow line data stored in the flow line DB 131, queue state data in the queue state DB 132, obstacle data and restricted access area data stored in the map DB 133, and queue line definition condition data stored in the condition DB 135. The scheduled queue line planning unit 11 stores data on the defined scheduled queue line together with the start time and end time of each time period in the scheduled queue line DB 136. Details of step S202 will be described later.

[0081] Step S12 is executed by the guidance content determination unit 15 as follows. The guidance content determination unit 15 determines guidance content based on the current queue state, the expected queue line, and guidance position adjustment information for the main flow line, and transmits the determined guidance information to the queue guide unit 21.

[0082] The guidance content determination unit 15 detects, for example, the planned guidance position on the planned queue line that corresponds to the current end of the queue, using the flow line data in the flow line DB 131, the queue state data in the queue state DB 132, and the planned queue line data in the planned queue line DB 136.

[0083] The planned guide position is a planned position to guide people (service users) who are waiting in line. The guidance content determination unit 15 uses data on the end of the detected planned queue line and the planned queue line data in the planned queue line DB 136 to extract a position where the next person who has come to join the queue should stand.

[0084] Based on the correction data for the queue guidance position transmitted from the queue schedule line planning unit 11, the guidance content determination unit 15 determines a position to guide the service user who is about to join the queue to the queue within the main flow line area.

[0085] The guidance content determination unit 15 transmits the flow line data in the flow line DB 131, the queue state data in the queue state DB 132, the map data group in the map DB 133, the main flow line data in the main flow line data DB, and data related to the guidance content determined in steps S32 and S33 described later in Fig. 14 to the queue guidance unit 21 to display them. The details of step S12 will be described later.

[0086] The people flow guidance system 1 determines whether a preset operation end condition is met (S13). If the operation end condition is not met (S13: NO), the people flow guidance system 1 returns to step S11. If the operation end condition is met (S13: YES), the people flow guidance system 1 ends this process.

[0087] The operation end condition may be determined based on a preset operation schedule of the people flow guidance system 1, or may be ended by a user such as a system administrator turning off the power switch of the people flow guidance system 1. When a user inputs an end command to the people flow guidance system 1 from the information input / output device 106, the people flow guidance system 1 may end operation. The operation end condition is not limited to the above.

[0088] The people flow guidance system 1 can keep some functions running at all times and automatically execute whether to start or stop. For example, the people flow guidance system 1 uses an operation determination unit to constantly monitor whether a target queue (operation determination queue) that should be guided to and organized in a target area has occurred. When the operation determination unit detects the occurrence of a queue, it starts up the remaining parts of the people flow guidance system 1. When the operation determination unit determines that there is no operation determination queue, other functions of the people flow guidance system 1 other than the operation determination unit are stopped. The operation determination unit can be configured to include, for example, an information acquisition unit 12, an information management unit 13, and a queue determination unit 14. The other functions include, for example, a scheduled queue line planning unit 11, a guidance content determination unit 15, and a queue information provision unit 16.

[0089] The information acquisition unit 12 may be used as an operation determination unit. For example, when the information acquisition unit 12 detects the presence of a predetermined number of people within a predetermined time, the information acquisition unit 12 may activate the other functions 11, 13, 14, 15, and 16.

[0090] It is also possible to automatically control the operation and termination of the people flow guidance system 1 in multiple stages. For example, when the constantly running information acquisition unit 12 detects the presence of a predetermined number of people within a predetermined time, it may start the information management unit 13 and the queue determination unit 14 to determine whether the queue is for operation determination, and if it is determined to be for operation determination, it may start the remaining functions 11, 15, and 16.

[0091] 5 is an example of a flow line table 131T stored in the flow line DB 131. The data stored in the table 131T of the flow line DB 131 may be flow line data extracted from data measured by the measurement system 31 in the target facility, or may be flow line data acquired in advance in a predetermined area.

[0092] Flow line table 131T stores flow line data. Coordinates and the like of sampled flow line data are stored in flow line table 131T for each person and at regular time intervals (for example, every second).

[0093] A start time 1311 is the time when sampling of the flow line data started. An end time 1312 is the time when sampling of the flow line data ended. A PID 1313 is information for identifying a person. A line 1314 is sampled flow line data. The data stored in the line 1314 may be geometry data such as a LINESTRING, or may be coordinate values ​​at the start and end times of sampling. Furthermore, any coordinate system may be used, such as a Cartesian coordinate system.

[0094] 6 is an example of a queue state table 132T stored in the queue state DB 132. The data stored in the queue state DB 132 may be data prepared in advance or data transmitted from the queue determination unit 14.

[0095] The queue state table 132T stores data indicating when, in which queue, and in which order each person is lined up. The start time 1321 indicates the start time of the time period in which the corresponding queue state occurred. The end time 1321 indicates the end time of the time period in which the corresponding queue state occurred. The QID 1323 is information that identifies the queue.

[0096] QID 1323 corresponds to QID 1351 in matrix line definition condition table 135T1 stored in condition DB 135. List 1324 is data relating to the order in which people with which PID 1313 are lined up in a matrix specified by QID 1323 between start time 1321 and end time 1322. For example, list 1324 is displayed in the form of an array. Each element of the array corresponds to PID 1313, and the order of the elements corresponds to the order in which people are lined up in the matrix.

[0097] Fig. 7 shows an obstacle table 133T1 stored in the map DB 133. The data stored in the map DB 133 may be data prepared in advance, or may be data input by the user via the map data input unit 122. The same applies to a table 133T2 described later in Fig. 8.

[0098] The obstacle table 133T1 stores data representing the position and shape of objects such as walls and obstacles that people cannot pass through. The WID 1331 is information for identifying the object. The area 1332 represents the position and shape information of the object. The area 1332 represents coordinates representing the object shape as geometry data in the form of a POLYGON or LINESTRING. As with lines, any coordinate system can be used.

[0099] 8 shows a traffic restricted area table 133T2 stored in the map DB 133. The traffic restricted area table 133T2 stores data representing the position and shape of an area where it is desired to restrict the passage of people. In the traffic restricted area, queues are prevented from becoming long regardless of the occurrence of a main flow line.

[0100] For example, when displaying an advertisement on digital signage, if a line forms in front of the digital signage, passersby will have difficulty seeing the advertisement. By setting the area where the digital signage is installed as a restricted-traffic area, congestion in front of the digital signage can be alleviated.

[0101] The RAID 1333 is information for identifying the restricted passage area. The area 1334 is coordinates representing the position and shape of the restricted passage area, expressed as geometry data such as a polygon. As with the line 1314, any coordinate system may be used.

[0102] 9 shows a main flow line table 134T stored in the main flow line DB 134. The main flow line table 134T stores output data from the main flow line detection unit 112, data input by the user to the main flow line data input unit 123, or data prepared in advance.

[0103] The main flow line table 134T stores data on when, where, and in which direction the main flow line moves in the flow line data at the predicted target time. The FID 1341 is information for identifying the main flow line. The start time 1342 and the end time 1343 indicate the start time and end time of the occurrence of the main flow line. The area 1344 represents the existence area of ​​the main flow line as geometry data such as a polygon. As with the line 1314, any coordinate system may be used. The travel direction 1345 represents a representative value of the travel direction of each flow line included in the main flow line. The representative value of the travel direction may be, for example, the average value, median value, or mode value of the travel direction of each flow line of the corresponding divided flow line group, or the average value of the minimum and maximum values ​​of the range of the travel direction.

[0104] 10 shows a matrix line definition condition table 135T held by the condition DB 135. The condition DB 135 stores data input by the user via the matrix condition input unit 124, or data prepared in advance.

[0105] The matrix line definition condition table 135T1 stores information on the head position of the matrix and information on the direction (initial direction) in which the matrix extends from the head. QID 1351 is information for identifying the matrix. Head point 1352 is coordinates indicating the head position of each matrix, expressed as geometry data such as POINT. Like line 1314, head point 1352 may use any coordinate system. Initial direction 1353 indicates the direction in which the matrix extends when determining the next planned guide position from the head position of the matrix.

[0106] 11 shows the expected number of people in queue table 135T2 held by the condition DB 135. The expected number of people in queue table 135T2 stores data on the expected number of people that each expected queue line can accommodate in each time slot within the target time. CID 1355 is information that identifies the expected number of people, the queue, and a data group for the time slot. Start time 1356 and end time 1357 indicate the start and end times of each time slot. QID 1358 is information that identifies the queue, and corresponds to QID 1351 in the queue line definition condition table 135T1. Expected number of people 1359 indicates the expected number of people that the expected queue line represented by QID 1358 can accommodate between the start and end times.

[0107] 12 shows a queue schedule line table 136T stored in the queue schedule line DB 136. The queue schedule line DB 136 stores output data from the queue planner 114, data input by the user to the queue schedule line input unit 125, or data prepared in advance.

[0108] The queue schedule line table 136T stores data regarding when, what shape, and for which queue the queue schedule line is planned. CID 1361 is information for identifying the queue schedule line. Start time 1362 and end time 1363 indicate the start time and end time of the time period during which the corresponding queue schedule line is used for guidance. QID 1364 is information for identifying the corresponding queue, and corresponds to QID 1351. Line 1365 is coordinates representing the object shape expressed as geometry data such as LINESTRING.

[0109] Here, the LINESTRING representing the line may be composed of a sequence of points representing the planned guide position on the planned queue line. This allows the coordinate data of this sequence of points to be directly used when the guidance content decision unit 15 decides the guide position for people waiting in line based on the data on the planned queue line. Alternatively, it may be as follows.

[0110] For example, if the planned queue line is a straight line, in order to record this shape information, it is necessary to have coordinate data of the start point and the end point of the line, and it is assumed that only these data are stored in the line. In this case, a point on the planned queue line that is a predetermined distance in a predetermined direction from the end position of the actual queue line detected from the movement line data may be determined as the guide position.

[0111] Alternatively, the guided positions to which a person has already been guided may be recorded one by one, and a position on the planned queue line that is a predetermined distance away from the guided position in a predetermined direction may be set as the next guided position. For example, when there is a person lined up on the planned queue line, the next person to join the queue may be guided to a position on the planned queue line that is a predetermined queue interval away from the head of the queue, and the guided position may be recorded even after the guidance is completed. Then, the guided position for the next person to join the queue may be set to a position on the planned queue line that is a predetermined queue interval away from the previously recorded guided position.

[0112] Alternatively, the data stored in the line may be geometry data such as POINT in the form of an array [POINT(X01 Y01), POINT(X02 Y02), ...]. In this case, each element of the array may correspond to the coordinate data of a planned guide position, and the data may be stored so that the order of the elements corresponds to the order of the planned guide positions on the planned queue line. In this case as well, when guidance content determination unit 15 determines the guide positions for people in the queue based on the data on the planned queue line, the coordinate data of each element of this array can be directly used. Like line 1314, line 1365 may use any coordinate system.

[0113] The queue schedule line planning process S20 performed by the queue schedule line planning unit 11 will be described with reference to the flowchart of FIG.

[0114] The flow line prediction unit 111 of the expected queue line planning unit 11 predicts a flow line at a target time, for example, by using the flow line data stored in the flow line DB 131 and the obstacle data stored in the map DB 133 (S21). Then, the flow line prediction unit 111 transmits the predicted flow line data to the main flow line detection unit 112 and the expected number of people calculation unit 113 (S21).

[0115] The generated flow line data includes information of each column of the flow line data in the flow line DB 131. In this case, a simulation method based on a physical model such as a social force model may be used as a method for simulating the flow line. A human movement model learned by machine learning such as support vector regression, deep learning, and gradient boosting may be applied to perform the simulation.

[0116] When machine learning is used, the current speed vector, the distances to surrounding obstacles in various directions, and a grid centered on the user may be extracted, features related to the grid may be calculated, and a movement model that predicts the speed vector one step ahead may be learned, and the speed may be predicted sequentially to perform a movement line simulation. Alternatively, movement line data from the past target time may be used as the movement line prediction result for the target time. For example, if the movement lines in the morning, afternoon, and evening do not change significantly from day to day, data from a day other than the target time may be used as the movement line prediction result for the target time. Alternatively, information equivalent to the movement line data in the movement line DB 131 may be input from the user, and the input movement line data may be used as the movement line prediction result.

[0117] The main flow line detection unit 112 of the queue schedule line planning unit 11 detects a main flow line by using the current flow line data stored in the flow line DB 131 and the subsequent flow line data predicted in step S21 (S22). The main flow line detection unit 112 stores the main flow line data detected from the current flow line data in the main flow line DB 134 (S22). Then, the main flow line detection unit 112 transmits the main flow line data to the queue planning unit 114. The details of step S22 will be described later.

[0118] The guidance position calculation unit 115 of the planned queue line planning unit 11 detects an overlap area where the queue line where people are already lined up at the current time overlaps with the main flow line area, for example, using the main flow line data detected in step S22, the queue state data stored in the queue state DB 132, and the flow line data stored in the flow line DB 131 (S23).

[0119] The guide position calculation unit 115 judges whether the extension direction of the queue line in the detected overlapping area is perpendicular or parallel to the movement direction of the main flow line (S23). When it is judged that the extension direction of the queue line is perpendicular to the movement direction of the main flow line, the guide position calculation unit 115 adjusts the interval L1 of the planned guide positions of the planned queue line in the overlapping area (S23). The guide position calculation unit 115 calculates queue adjustment data so that the interval L1 of the planned guide positions can be widened by an arbitrary distance and the number of planned guide positions is reduced according to the widening distance (S23). Then, the guide position calculation unit 115 transmits the queue adjustment data, which is the result of the adjustment and is related to how many people in the queue should be reduced in the overlapping area, to the guide information calculation unit 114 and the queue planning unit 114 (S23).

[0120] The expected number of people calculation unit 113 of the expected queue line planning unit 11 calculates the maximum number of people lining up in each queue during a predetermined time period, for example, using the flow line data predicted in step S21 (S24). The expected number of people calculation unit 113 calculates the expected number of people to be accommodated in each expected queue line based on the calculated maximum number of people, and stores the calculated expected number of people together with the start time and end time of each time period in a expected number of people in queue table of the condition DB 135 (S24).

[0121] The expected number of people to be accommodated may be the maximum predicted number of people, or the maximum predicted number of people multiplied by a constant value equal to or greater than 1. The latter corresponds to a case where the queue capacity is set with some leeway in relation to the flow line prediction results.

[0122] The queue planning unit 114 of the scheduled queue line planning unit 11 plans a scheduled queue line and stores the planned scheduled queue line in the scheduled queue line DB 136 (S25). The queue planning unit 114 defines the scheduled queue line at the target time (S25) using the queue state data stored in the queue state DB 132, the obstacle data and the traffic restriction area data stored in the map DB 133, the scheduled queue line definition condition data stored in the condition DB 135, the main flow line data detected in step S22, the queue adjustment data calculated in step S23, and the scheduled number of people data calculated in step S24. Then, the queue planning unit 114 stores the data of the defined scheduled queue line in the scheduled queue line DB 136 (S25). The details of step S25 will be described later.

[0123] The guidance content determination process S30 executed by the guidance content determination unit 15 will be described with reference to the flowchart of FIG.

[0124] The guidance content determination unit 15 determines a planned guide position corresponding to the end of the current queue based on the current queue state and the scheduled queue line (S31). The guidance content determination unit 15 determines which planned guide position on the scheduled queue line corresponds to the end of the current queue, for example, using the flow line data in the flow line DB 131, the queue state data in the queue state DB 132, and the scheduled queue line data in the scheduled queue line DB 136 (S31).

[0125] The guidance content decision unit 15 first detects the coordinate data of the person at the end of each queue at the current time based on the queue state data and the traffic line data, compares the detected coordinate data with the coordinate data of the planned guidance position of the planned queue line, and determines up to which planned guidance position in each queue people have already lined up.

[0126] Here, the guidance content determination unit 15 may extract the planned guide position closest to the position of the last person, and make a decision based on the extraction result. Alternatively, the guidance content determination unit 15 may obtain the number of elements (the number of people waiting in line) in the list 1324 of queue state data, and determine the planned guide position that is the number of elements behind the head of the planned queue line as the planned guide position corresponding to the end of the current queue. For example, when the number of elements in the list 1324 is "3" (i.e., the number of people waiting in line is three), the third planned guide position counting from the head on the planned queue line corresponds to the end of the current queue.

[0127] The guidance content determination unit 15 extracts coordinate data of the next planned guide position on the planned queue line from the planned guide position corresponding to the end of the current queue determined in step S31 (S32). The extracted coordinate data corresponds to the position data of the next person to line up in the queue.

[0128] The guidance content determination unit 15 determines additional guidance processing based on the queue adjustment data on the main flow line transmitted from the guidance position calculation unit 115 (S33). The guidance content determination unit 15 determines the content of guidance instructions to, for example, reduce the number of people in the queue area on the main flow line (on the main flow line area) (S33). The guidance instructions can include, for example, the following instructions:

[0129] First, the guidance content determination unit 15 instructs people lining up behind the area to stop temporarily so that people do not flow into the overlap area where the main traffic line area and the planned queue line overlap. Next, in order to reduce the number of people in the area and increase the spacing, the guidance content determination unit 15 instructs only the person at the front of the area to leave the area and move forward if the queue advances, and instructs the other people in the area to line up at a distance within the area.

[0130] The guidance content determination unit 15 transmits the traffic flow data in the traffic flow DB 131, the queue state data in the queue state DB 132, the map data group in the map DB 133, the main traffic flow data in the main traffic flow data DB, and the guidance information determined in steps S32 and S34 to the queue guidance unit 21, and causes the transmitted information to be displayed on the queue guidance unit 21 (S34).

[0131] 15, a description will be given of screen examples G1 and G2 displayed on queue guide unit 21. Here, queue guide unit 21 is assumed to be something like digital signage.

[0132] A screen G1 shown in the upper part of Fig. 15 shows a display screen at a certain time T1. A screen G2 shown in the lower part of Fig. 15 shows a display screen at a time T2, which is a predetermined time (for example, one second) after the time T1.

[0133] The display elements GP11 and GP21 represent the guide positions of the next person in each queue, determined in step S32. The display elements GP12 and GP22 represent positions on the planned queue line where people are already present at the relevant time.

[0134] Based on the result of judging the planned guide position corresponding to the end of the queue (S31), it may be judged that people are already lined up at all of the planned guide positions from the beginning to the end of the queue, and this judgment result may be used. Based on the data in the queue state table and the data in the flow line table, instead of the data in the queue planned line table, the position data of the actual people in the queue may be calculated and displayed instead of the planned guide position data, or both may be displayed.

[0135] Display elements GP13 and GP23 represent row and column areas that overlap main flow line areas GP16 and GP26.

[0136] Display elements GP14 and GP24 represent the flow of people who are not waiting in line and are moving at a given time based on the flow line data.

[0137] Display elements GP15 and GP25 represent the window 22 that provides the service.

[0138] The display elements GP16 and GP17 represent the area of ​​the main flow line detected at the relevant time based on the main flow line data. The display elements GP17 and GP27 represent the direction of travel of the areas GP16 and GP26 of the detected main flow line.

[0139] Display elements GP18 and GP28 represent the position and shape data of an obstacle.

[0140] The following is a supplementary explanation of the situation shown on screens G1 and G2. Assume that a person lines up at guide position GP11 between time T1 corresponding to screen G1 and time T2 corresponding to screen G2. This is determined by queue determination unit 14 and reflected in the data of queue state DB132. As a result, the position of the next person to line up is determined to be in a state where someone is already lined up, and the display changes.

[0141] As a result of the updated position of the end of the queue, the position of the next person to line up is also updated and displayed as GP21. The queue spacing in the area GP23 where the main traffic line area and the planned queue line overlap is set wider than the queue spacing in the overlap area GP13 on screen G1.

[0142] The overlapping area GP13 is a queue that has occurred on a main line of traffic, and in order to widen the gap in the queue within that area to an arbitrary setting, only the person at the front of the area can move forward, and the rest of the people can keep their distance, for example, by displaying "Only the person at the front, please move forward. Please keep your distance." Furthermore, for people lining up just behind area GP13, a message such as "Please stop" is displayed to prevent them from flowing into that area.

[0143] As time passes from time T1 to time T2, the number of people in queue area GP23 on the main flow line decreases by a certain number, so the instructions to control the inflow and outflow of the overlapping area disappear from the digital signage. In this case, only the instructions to widen the queue interval within the area are displayed on the digital signage.

[0144] In this way, the content displayed on queue guide unit 21 differs between the front and back of the queue in overlapping areas GP13 and GP23 depending on the number of people waiting in the overlapping areas. The digital signage at the front of the queue and the digital signage at the back of the queue may be separate, or a common digital signage may be used. As mentioned above, queue guide unit 21 is not limited to digital signage.

[0145] The main flow line detection process S40 executed by the main flow line detection unit 112 will be described with reference to the flowchart of FIG.

[0146] The main flow line detection unit 112 classifies the flow line data stored in the flow line DB 131 and the flow line data received from the people flow prediction unit 1131 based on the passing area and the angle of the moving direction of the flow line, and the time period when the flow line occurred (S41).

[0147] The detection of the main traffic lines is performed for each area obtained by dividing the target area. The target area may be divided into a grid, or the target area may be divided based on a group of arbitrarily set boundaries. After the divided areas are generated in this way, a spatial intersection determination is performed on the traffic line data passing through each divided area, and the traffic line data is extracted based on the determination result, and each traffic line data is further classified by a predetermined time span. The predetermined time span may be set to, for example, one hour.

[0148] The main flow line detection unit 112 uses the flow line data groups classified in step S41, the data of the corresponding divided areas, and the data of the obstacle table in the map DB 133 to calculate the number of flow line data per unit area for each flow line data group, and detects the flow line data groups whose calculated flow line density is equal to or greater than a certain value as the main flow line (S42). When calculating the number of flow line data per unit area, the number of records of the flow line data group is divided by the area of ​​the corresponding divided area. The area of ​​the divided area may be calculated by subtracting the area occupied by obstacles from the area of ​​the divided area.

[0149] After detecting the main flow line, the main flow line detection unit 112 obtains the area of ​​the main flow line and the angle of the moving direction of the main flow line (S42). For the area of ​​the main flow line, a divided area corresponding to the flow line data group detected as the main flow line may be set.

[0150] When determining the travel direction of the main flow line, first, the flow line data is classified by its travel direction. The main flow line detection unit 112 may, for example, divide the angle range from -180 degrees to 180 degrees into an appropriate number of parts, determine which divided range the travel direction angle of the flow line data falls into, and calculate the angle of the travel direction based on the determination result.

[0151] The main flow line detection unit 112 may apply an appropriate clustering method to the distribution of the number of flow line data for each travel direction, and may determine the angle of the travel direction based on the probability that the flow line data belongs to each cluster. In this case, it may be determined that the flow line data corresponds to the cluster with the highest probability. For example, k-means or EM algorithm may be used as the clustering method. Then, from among the classified flow line data groups, the flow line data group with the largest number of flow line data per unit area is detected, and the angle of the travel direction of the detected flow line data group is set. Regarding the detected data, the current main flow line data detected from the flow line data group for the time period including the current time is stored in the main flow line DB 134. Then, the main flow line detection unit 112 transmits the current main flow line data and the main flow line data from the present onward detected based on the predicted flow line data to the queue planning unit 114 (S42).

[0152] The queue planning process S50 executed by the queue planning unit 114 will be described with reference to the flowchart of FIG.

[0153] The queue planning unit 114 determines a reference point and a direction at the start of updating the scheduled queue line (S51). In steps S52 and after, the next scheduled guide position is determined based on the reference point and a predetermined extension direction, and the determined scheduled guide position is updated to a new reference point, and this process is repeated to generate the scheduled queue line.

[0154] In step S51, if there are people already in the queue at the time of defining the planned queue line, the planned guide position on the planned queue line up to the point where people are already in line is not changed, and only the planned guide position behind the end of the current queue is redefined. If the planned queue line up to the point where people are already in line is modified and people are guided to the modified line, multiple people already in line will have to be moved, which may cause confusion.

[0155] Step S51 is a process for avoiding such a situation. Alternatively, step S51 may not be performed, and the update start point of the planned queue line may always be determined to be the position next to the head of each queue. Alternatively, when the planned queue line becomes longer than the currently defined planned queue line due to an increase in the planned number of people in the queue, the planned guidance position at the end of the planned queue line may be set as the reference point.

[0156] In step S51, for example, first, it is determined whether there are two or more people waiting in line at the current time from the queue state data in queue state DB 132. If the result of the determination is that there are zero or one people waiting in line, the reference point at the start of the update is set to the leading point of each queue stored in queue line definition condition table 135T1, and the extension direction is set to the initial direction 1353 of the corresponding queue.

[0157] When there are two or more people in the queue, a point corresponding to the end of the current queue from the planned guide position on the planned queue line is extracted as a reference point. This is performed in the same manner as in step S31, using the flow line data in the flow line DB131, the queue state data in the queue state DB132, and the planned queue line data in the planned queue line DB136.

[0158] The extension direction is set to the previous extension direction, i.e., the direction of the line segment connecting the reference point and the previous planned guide position. If the number of people already in the queue is equal to or greater than the planned number stored in the table of planned queue numbers, the planned queue line may not be defined for that queue, or the planned number of people to be accommodated in the queue may be reset to a value obtained by adding an arbitrary number to the current planned number of people, and then step S51 may be performed.

[0159] The matrix planner 114 extracts points located in a predetermined direction and at a predetermined distance from the reference point as candidate points (S52).

[0160] The distance can be set to any value (for example, 1 m). Based on the data in the main flow line DB 134, the queue planning unit 114 determines whether the candidate point is on the main flow line area and whether the extension direction at this time is perpendicular to the travel direction of the main flow line. If the determination result is true, the queue planning unit 114 re-extracts a point that is a distance that is an arbitrary length greater than the predetermined distance as a candidate point. This is because, when a queue extends perpendicular to the travel direction on the main flow line, the queue spacing is widened to prevent it from obstructing passersby.

[0161] However, the above-mentioned judgment condition is not limited to the case where the extension direction of the queue is perpendicular to the direction of travel of the main line of traffic. The above-mentioned judgment condition can also be applied when the queue planned line intersects with the direction of travel of the main line of traffic at another angle. This is because the crowd density on the main line of traffic is reduced regardless of the extension direction of the queue, thereby easing congestion.

[0162] The queue planning unit 114 judges whether the queue planned line will collide with an obstacle, a main traffic line area, or a traffic restricted area when it is extended to the candidate point (S53).

[0163] The queue planning unit 114 determines whether the candidate point is located on an obstacle, a main flow line area, or a restricted area based on, for example, the map data group in the map DB 133 and the main flow line data in the main flow line DB 134, and proceeds to step S55 if the determination result is true, and proceeds to step S53 if the determination result is false. Regarding the main flow line data, not only the data stored in the main flow line DB 134 but also main flow line data detected based on the flow line data predicted by the flow line prediction unit 111 may be used together.

[0164] The queue planning unit 114 determines the candidate point extracted in step S52 as the next extension position of the queue planned line, and updates the queue planned line (S54). The queue planning unit 114 sets the reference point for determining the next extension position to the extension position determined in S54, and sets the current extension direction as the direction.

[0165] The queue planning unit 114 determines whether the extension direction of the queue can be changed at the collision point determined in step S53 (S55).

[0166] For example, the matrix planning unit 114 extracts points that are a predetermined distance away in several directions from the reference point at the time point as candidate points. The extension direction to be searched is determined by dividing the range of angles from -90 degrees to 90 degrees counterclockwise into any number of equal parts based on the current extension direction. The 0 degree direction is removed because it matches the current extension direction.

[0167] For example, a direction rotated 90 degrees clockwise or 90 degrees counterclockwise from the reference direction is used. In this case, if the matrix is ​​extended in a straight line, it corresponds to the case where the robot bends to the left or right when it collides with an obstacle.

[0168] Thereafter, in order to determine whether there will be any further collision with another obstacle or the like in the bent direction, the matrix planning unit 114 performs the same process as in step S53 on the extracted candidate point group and determines whether there is one or more candidate points for which the determination result is false. If the determination result is true, the process proceeds to step S56, and if the determination result is false, the process proceeds to step S57.

[0169] The queue planning unit 114 determines the next extension position of the queue planned line from among the candidate points extracted in step S55 that do not collide with obstacles, etc. (S56). If there are multiple candidate points, they may be selected randomly. The reference point and extension direction when determining the next extension position are set in the same way as in step S54.

[0170] Step S57 is a process performed after it is determined in step S55 that the matrix cannot be extended in any direction from the current reference point. The matrix planning unit 114 performs the following process (S57).

[0171] The matrix planning unit 114 extracts candidate points in a direction different from the current bending direction for a portion where the matrix is ​​bent before the current reference point. The matrix planning unit 114 performs the same process as in step S53 for the extracted candidate points and judges whether there is one or more candidate points for which the judgment result is false. If the judgment result is true, the matrix planning unit 114 proceeds to step S58, and if the judgment result is false, the matrix planning unit 114 proceeds to process S59. If there are multiple portions where the matrix is ​​bent before the current reference point, candidate points may be extracted and judged for all of them in the same manner.

[0172] The queue planner 114 selects a candidate point that does not collide with an obstacle or the like from among the candidate points extracted in step S57, and deletes the current queue planned line following the bend point (S58).

[0173] The queue planning unit 114 determines the selected candidate point as the next extension position of the queue planned line (S58). If there are multiple candidate points, they may be selected randomly, or the candidate point that has the smallest length of the queue planned line that must be deleted when the candidate point is selected may be selected. The reference point and extension direction when determining the next extension position are set in the same way as in step S54.

[0174] Step S59 is a process that is performed after it is determined in step S57 that the matrix cannot be extended in any direction from the current reference point, and further that the matrix cannot be extended even if the past bending point is changed.

[0175] The queue planning unit 114 extracts candidate points at positions at a predetermined distance away from the main flow line area in the direction of the queue if it is not bent, that is, in the direction of entering the main flow line area (S59). The distance at this time is set to a value L1 that is an arbitrary length larger than the interval L2 of the queue planned lines outside the main flow line area, as in step S52.

[0176] The queue planning unit 114 performs the same process as in step S53 on the extracted candidate points and judges whether there is one or more candidate points for which the judgment result is false (S59). If the judgment result is true, the queue planning unit 114 proceeds to step S60, and if the judgment result is false, it is judged that the queue planned line cannot be extended any further, and proceeds to step S62.

[0177] If there are multiple points where the queue is bent before the current reference point, candidate points may be extracted and determined for all of them in the same manner as above. The queue planned line to be sent to step S62 may be the currently defined one, or may be randomly selected from the queue planned lines before the direction was changed in steps S56, S58, and S60, or the longest queue planned line may be selected among them.

[0178] The queue planning unit 114 selects one of the candidate points extracted in step S59, and deletes the current queue planned line after the bend point (S60). Then, the queue planning unit 114 determines the selected candidate point as the next extension position of the queue planned line (S60). If there are multiple candidate points, they may be selected randomly, or the candidate point having the shortest length of the queue planned line that must be deleted when the candidate point is selected may be selected. Based on the main flow line data stored in the main flow line 110, the straight line distance from each candidate point to the exit of the main flow line area may be calculated, and the candidate point with the shortest calculated distance may be selected. The reference point for determining the next extension position is set in the same manner as in step S54. The extension direction may be selected in the direction in which the straight line distance from the candidate point to the exit of the main flow line area is the shortest, or may be set in the same manner as in step S54, or may be selected in the direction perpendicular to the traveling direction of the main flow line.

[0179] The queue planning unit 114 judges whether the queue planned line has been set for the planned number of people in the planned queue number table 135T2 (S61). If the judgment result is true, the queue planning unit 114 proceeds to step S62, and if the judgment result is false, the queue planning unit 114 returns to step S52.

[0180] The queue planning unit 114 stores data of the defined queue scheduled lines in the queue scheduled line DB 136 (S62). When there are multiple queues, the queue scheduled lines may be defined in any order, for example, in the numerical order of the QID 1351 in the queue line definition condition table 135T1, and step S62 may be performed after all the queue scheduled lines have been defined.

[0181] In defining the planned queue line, a previously defined planned queue line may be treated as an obstacle. Also, data on the queue line may be extracted based on the flow line data stored in the flow line DB 131 and the queue state data stored in the queue state DB 132, and used instead of the planned queue line.

[0182] 18 is an example of a user interface screen G3 provided to a user such as a system administrator by the people flow guidance system 1. The screen G3 is a screen that displays flow line data stored in the flow line DB 131, a map data group stored in the map DB 133, main flow line data stored in the main flow line DB 134, a condition data group stored in the condition DB 135, and queue schedule line data stored in the queue schedule line DB 136.

[0183] The upper left corner of screen G3 shows a schematic representation of the relationship between the queue and the main flow line as display elements GP312 to GP317. The upper right corner of screen G3 shows screen GP311 for displaying detailed information. The lower part of screen G3 shows buttons operated by the user as display elements GP32 to GP45.

[0184] Each flow line data or queue plan line is drawn by drawing a LINESTRING for each record, but it may be drawn with markers on the end points of the LINESTRING or on the coordinates that make up the LINESTRING, or it may be drawn in different colors for each state.

[0185] When the detailed data display button GP39 is pressed, information about the selected flow line, planned queue line, obstacles, restricted access areas, and main flow lines is displayed on the detailed information display screen GP311 of the screen G3. In the illustrated example, the planned queue line GP317 is selected after the detailed data display button GP39 is pressed, so information about the planned queue line GP317 is displayed on the detailed information display screen GP311. This information includes data about the head point and queue interval stored in the queue line definition condition table 135T1 of the condition DB135, and data about the planned number of people that the planned queue line can accommodate stored in the planned queue number of people table 135T2.

[0186] The obstacle data input button GP32 is a button for inputting obstacle data. When the button GP32 is pressed, an editing screen G4 shown in Fig. 19 is displayed. The user inputs information about the obstacle table 133T1 of the map DB 133 from the screen G4. The input information is stored in the obstacle table 133T1 of the map DB 133 by the map data input unit 122.

[0187] The traffic restricted area data input button GP33 is a button for inputting traffic restricted area data. When this button GP33 is pressed, an editing screen (not shown) appears. The screen for editing the traffic restricted area data is similar to the screen for editing the obstacle data shown in FIG. 19. The user inputs information related to the traffic restricted area table 133T2 of the map DB 133 via the screen GP33. The input information is stored in the traffic restricted area table 133T2 of the map DB 133 by the map data input unit 122.

[0188] The main flow line data input button GP34 is a button for inputting main flow line data. When the button GP34 is pressed, an editing screen G5 shown in Fig. 20 is launched. The user can input information related to the main flow line table 134T of the main flow line DB 134 via the screen G5. The input information is stored in the main flow line DB 134 by the main flow line data input unit 123.

[0189] The matrix line condition input button GP35 is a button for inputting definition condition data of a matrix line. When this button is pressed, an editing screen G6 shown in Fig. 21 is displayed. The user can input information related to the matrix line definition condition table 135T1 of the condition DB 135 via the screen G6. The input information is stored in the matrix line definition condition table 135T1 of the condition DB 135 by the matrix condition input unit 124.

[0190] The queue scheduled line input button GP36 is a button for inputting queue scheduled line data. When this button GP36 is pressed, an edit screen G7 shown in Fig. 22 appears, and the user can input information related to the queue scheduled line table 136T of the queue scheduled line DB 136. The input information is stored in the queue scheduled line DB 136 by the queue scheduled line input unit 125.

[0191] The input button GP37 for inputting data on the expected number of people in queue is a button for inputting data on the expected number of people in queue. When this button GP37 is pressed, an edit screen G8 shown in Fig. 23 is displayed. The user can input information related to the table 135T2 of the expected number of people in queue of the condition DB 135 via the screen G8. The input information is stored in the table 135T2 of the expected number of people in queue of the condition DB 135 by the queue condition input unit 124.

[0192] The queue schedule line planning button GP38 is a button for starting the processing of the queue schedule line planning unit 11. When this button GP38 is pressed, the queue schedule line planning processing S20 described in FIG.

[0193] The detailed data display button GP39 is a button for displaying detailed information of data selected on the screen G3 on the screen GP311. For example, one or more databases corresponding to the selected data, such as the flow line DB131, the queue state DB132, the map DB133, the main flow line DB134, the scheduled queue line DB136, and the condition DB135, are called up, and information on the selected data is displayed.

[0194] The play button GP40 is a button for automatically advancing the time of the data displayed on screen G3. The rewind button GP41 is a button for rewinding the time of the data displayed on screen G3. When this button GP41 is pressed, the display time can be returned to an earlier time. The fast-forward button GP42 is a button for fast-forwarding the time of the data displayed on screen G3. When this button GP42 is pressed, the rate at which the display time advances automatically can be increased. The stop button GP43 is a button for stopping the automatic advancement of the time of the data displayed on screen G3. When this button GP43 is pressed, the automatic advancement of the display time can be stopped.

[0195] The bar GP45 is a bar for indicating the progress of time of the data displayed on the screen G3. The user can arbitrarily change the time by selecting the bar GP45 and moving it left or right.

[0196] The display time GP44 is a character string that indicates the time of the data displayed on the screen G3. The user can edit this character string to change the time as desired.

[0197] 19 shows screen G4 for editing data in obstacle table 133T1. This editing screen G4 is used to edit data in obstacle table 133T1. Screen G4 includes a portion GP401 showing the value of WID1331 in obstacle table 133T1, a button GP402 for inputting an object, and buttons GP403 such as "New", "Save", "Edit", and "Delete".

[0198] The object input button GP402 is a button for starting editing, on screen G3, the position and shape of the area 1332 corresponding to the WID 1331 displayed in the text box. When this button GP402 is pressed, editing of the position and shape of the area 1332 can be started on screen G3. A passage restriction area data editing screen (not shown) can be configured in the same way as screen G4.

[0199] 20 shows a screen G5 for editing the data of the main flow line table 134T. The editing screen G5 is displayed in the screen G3 when the main flow line data input button GP34 is pressed. In this editing screen G5, the data of the main flow line table 134T stored in the main flow line DB 134 can be edited.

[0200] Screen G5 has text boxes GP501 that display each piece of information, such as FID 1341, start time 1342, end time 1343, and direction of travel 1345, of the main flow line table 134T. Area input button GP502 is a button for starting editing, on screen G3, the position and shape of area 1344 that corresponds to FID 1341 displayed in text box GP501. When this button GP502 is pressed, editing of the position and shape of area 1344 can be started on screen G3.

[0201] Like screen G4, screen G5 includes buttons GP503 such as "New," "Save," "Edit," and "Delete."

[0202] 21 shows the matrix condition editing screen G6. The editing screen G6 is displayed on the screen G3 when the matrix line condition input button GP35 is pressed. On the editing screen G6, information in the matrix line definition condition table 135T1 stored in the condition DB 135 is edited.

[0203] The screen G6 has a text box GP601 that displays information on the QID 1351 and initial direction 1353 of the matrix line definition condition table 135T1, a button GP602 for inputting a start point, and buttons GP603 such as "New" and "Save".

[0204] The button GP602 is a button for starting editing on the screen G3 of the position and shape of the start point 1352 corresponding to the QID 1351 displayed in the text box GP601. When this button GP602 is pressed, editing of the position and shape of the start point 1352 can be started on the screen G3.

[0205] 22 shows a screen G7 for editing a queue schedule line. The editing screen G7 is displayed on the screen G3 when the queue schedule line input button GP36 is pressed. On this editing screen G7, the information of the queue schedule line table 136T stored in the queue schedule line DB 136 can be edited.

[0206] The screen G7 has a text box GP701 that displays each piece of information of the CID 1361, start time 1362, end time 1363, and QID 1364 of the queue schedule line table 136T, a line input button GP702, and buttons GP703 such as "New" and "Save".

[0207] The line input button GP702 is a button for starting editing, on the screen G3, the position and shape of the line corresponding to CID 1361 displayed in the text box GP701. When this button GP702 is pressed, the position and shape of the line can be edited on the screen G3.

[0208] 23 shows an edit screen G8 for editing the expected number of people in queue. This edit screen G8 is displayed on the screen G3 when the input button GP37 for inputting the expected number of people in queue is pressed. On the edit screen G8, information in the table 135T2 for the expected number of people in queue stored in the condition DB135 is edited.

[0209] The screen G8 has text boxes GP801 that display information on the CID 1355, start time 1356, end time 1357, QID 1358, and expected number of people 1359 of the expected number of people in queue table 135T2, and buttons GP802 such as "New" and "Save".

[0210] According to the present embodiment configured as described above, a planned queue line for guiding service users to the queue is planned so that at least a part of the queue intersects with the main flow line. This allows the people flow guidance system 1 to organize and manage the queue for receiving the service even during busy times.

[0211] The people flow guidance system 1 of this embodiment widens the distance L1 between service users in overlapping areas where the queue intersects with the main traffic flow area, making it possible to smooth the flow of people within the facility 2 without impeding the movement of passersby who are not using the service.

[0212] The people flow control system 1 of this embodiment predicts the number of people waiting in line and plans the planned queue line so that at least a portion of it intersects with the main traffic flow area to accommodate the predicted number of people, so it can also accommodate queues with a large number of people.

[0213] The people flow guidance system 1 of this embodiment is equipped with a queue guide unit 21, so that even when the planned queue line intersects with the main traffic flow area, an orderly queue can be maintained by informing people of appropriate waiting positions and behavioral instructions (go, stop, increase spacing, etc.).

[0214] The people flow guidance system 1 of this embodiment notifies not only those waiting in line but also passersby along the main traffic lines of the presence of a queue, thereby enabling passersby to move smoothly and improving convenience for service users, passersby, managers of facility 2, and the like.

[0215] The people flow guidance system 1 of the present embodiment includes the queue information providing unit 16, and therefore improves convenience for, for example, the manager of the facility 2, providers of other services in the facility 2, marketing personnel, and the like.

[0216] The present invention is not limited to the above-described embodiment, and various modifications are included. For example, the above-described embodiment has been described in detail to clearly explain the present invention, and is not necessarily limited to those including all of the configurations described. It is also possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. It is also possible to add, delete, or replace a part of the configuration of each embodiment with another configuration. (Appendix 1) A mobile object queue management system for managing a queue of mobile objects, comprising: an information management unit that manages movement information related to the movement of a mobile object; a queue planned line planning unit that plans a queue planned line for guiding the moving object to the queue so that at least a part of the queue of the moving object intersects with a main flow line based on the movement information; A mobile queue management system comprising: (Appendix 2) The queue planned line planning unit plans the queue planned line such that a distance between adjacent moving bodies is different between a first region where the queue overlaps with the main flow line and the other region. The mobile object queue management system according to claim 1. (Appendix 3) The queue planned line planning unit sets a distance between adjacent moving bodies in the first area to be longer than a distance between adjacent moving bodies in other areas. The mobile object queue management system according to claim 2. (Appendix 4) The queue planned line planning unit predicts the length of the queue of the moving body, and plans the queue planned line based on the predicted queue length of the moving body and the direction of the main flow line. The mobile object queue management system according to claim 1. (Appendix 5) a queue guidance section that guides at least the moving objects that will be joining the queue to a waiting position based on the scheduled queue line; The system of claim 1 further comprising: (Appendix 6) The queue guidance unit further notifies other moving objects moving along the main flow line of the presence of the moving object waiting at the waiting position. The mobile object queue management system according to claim 5. (Appendix 7) a matrix information providing section for providing at least a part of the information managed by the information managing section to a calculation system related to a source of the matrix; The mobile object queue management system according to claim 5, further comprising: (Appendix 8) A mobile object queue management method for managing a queue of mobile objects using a computer, comprising: The computer includes: Manage movement information regarding the movement of the mobile object; planning a queue planned line for guiding the moving objects to the queue so that at least a part of the queue of the moving objects intersects with a main flow line based on the movement information; Mobile object queue management method. (Appendix 9) A computer program for causing a computer to function as a mobile object queue management system that manages a queue of mobile objects, comprising: The computer includes: an information management unit that manages movement information related to the movement of a mobile object; and a queue planned line planning unit that plans a queue planned line for guiding moving objects into a queue so that at least a portion of the queue of moving objects intersects with a main traffic line based on the movement information. [Explanation of symbols]

[0217] 1: People flow control system, 2: Facility, 11: Queue line planning unit, 12: Information acquisition unit, 13: Information management unit, 14: Queue determination unit, 15: Guidance content determination unit, 16: Queue information provision unit, 21: Queue guidance unit, 22: Service desk, 31: Measurement system

Claims

1. A mobile object queue management system for managing a queue of mobile objects, comprising: The mobile object queue management system includes an information management unit and a queue schedule line planning unit, the information management unit manages flow line data relating to the movement of each moving object, queue status data indicating the queue status of the moving objects, main flow line data indicating the area and direction of main flow lines indicating a group of flow line data having a flow line density equal to or greater than a certain value, and condition data including information on the number of moving objects to be accommodated in the queue; Each of the flow line data relating to the movement of each moving object includes information for identifying the moving object, information on a start time related to the flow line data, information on an end time related to the flow line data, and information on a flow line formed by the moving object indicated by the information for identifying the moving object from the start time to the end time related to the flow line data, information regarding a flow line formed by a moving object indicated by the information identifying the moving object from the start time to the end time related to the flow line data is information of a LINESTRING as geometry data of the moving object indicated by the information identifying the moving object, regarding the start time and the end time related to the flow line data, or information of coordinate values ​​of the moving object indicated by the information identifying the moving object at each of the start time and the end time related to the flow line data; Each of the queue state data indicating a queue state of moving objects has information on a start time associated with the queue state data, information on an end time associated with the queue state data, and information on the order of the moving objects in the queue from the start time to the end time associated with the queue state data, information on the order of the moving objects in the queue from the start time to the end time, which is related to the queue state data, is composed of an array of information for identifying the moving objects; the queue planned line planning unit creates data on a queue planned line by determining planned guide positions of the mobile objects in the queue for the number of mobile objects planned to be accommodated in the queue based on the queue state data, the main flow line data, and the condition data; the queue planned line planning unit, when setting the queue planned line indicated by the queue planned line data, is also capable of setting the queue planned line so as to intersect with an area of ​​the main flow line while giving priority to preventing the queue planned line from intersecting with an area of ​​the main flow line, In a mobile queue management system, the planned queue line planning unit determines the planned guide positions so that the distance between adjacent planned guide positions in parts of the planned queue line that intersect with the main traffic line area is longer than the distance between adjacent planned guide positions in parts of the planned queue line that do not intersect with the main traffic line area.

2. The mobile object queue management system further includes a guidance content determination unit, the guidance content determination unit specifies a next planned guide position on the planned queue line from a planned guide position corresponding to the end of the current queue based on the queue state data and the data on the planned queue line, the guidance content determination unit transmits guidance information based on the next scheduled guide position to a queue guidance unit, 2. The mobile object queue management system according to claim 1, wherein the queue guidance unit guides a mobile object that is about to join the queue to a waiting position based on the next scheduled guide position.

3. 3. The mobile object queue management system according to claim 2, wherein the queue guiding unit further notifies other mobile objects moving along the main traffic line of the presence of the mobile object waiting at the waiting position.

4. the information management unit manages, as information related to the queue, a head position of the queue, an end position of the queue, the number of people in the queue, and a queue growth rate; The mobile object queue management system further includes a queue information providing unit, the queue information providing unit provides at least one of the information regarding the queue to another system used by a provider of a service causing the queue, or another system used by a manager of a facility where a queue is formed; The mobile object queue management system according to claim 2.

5. A moving object queue management method in which a computer manages a queue of moving objects, comprising the steps of: The computer manages flow line data relating to the movement of each moving object, queue status data indicating the queue status of the moving objects, main flow line data indicating the area and direction of main flow lines indicating a group of flow line data having a flow line density equal to or greater than a certain value, and condition data including information on the number of moving objects to be accommodated in the queue, Each of the flow line data relating to the movement of each moving object includes information for identifying the moving object, information on a start time related to the flow line data, information on an end time related to the flow line data, and information on a flow line formed by the moving object indicated by the information for identifying the moving object from the start time to the end time related to the flow line data, information regarding a flow line formed by a moving object indicated by the information identifying the moving object from the start time to the end time related to the flow line data is information of a LINESTRING as geometry data of the moving object indicated by the information identifying the moving object, regarding the start time and the end time related to the flow line data, or information of coordinate values ​​of the moving object indicated by the information identifying the moving object at each of the start time and the end time related to the flow line data; Each of the queue state data indicating a queue state of moving objects has information on a start time associated with the queue state data, information on an end time associated with the queue state data, and information on the order of the moving objects in the queue from the start time to the end time associated with the queue state data, information on the order of the moving objects in the queue from the start time to the end time, which is related to the queue state data, is composed of an array of information for identifying the moving objects; The mobile object queue management method includes: the computer has a step of creating data on a planned queue line by determining planned guide positions of the moving objects in the queue for the number of moving objects planned to be accommodated in the queue based on the queue state data, the main flow line data, and the condition data; In the step of creating the queue planned line data, the computer, when setting the queue planned line indicated by the queue planned line data, can also set the queue planned line so that it intersects with an area of ​​the main flow line while giving priority to preventing the queue planned line from intersecting with the area of ​​the main flow line, In the step of creating data on the planned queue line, the computer determines the planned guide positions such that a distance between adjacent planned guide positions in a portion of the planned queue line that intersects with an area of ​​the main flow line is longer than a distance between adjacent planned guide positions in a portion of the planned queue line that does not intersect with an area of ​​the main flow line. Mobile object queue management method.

6. A computer program for causing a computer to manage a queue of moving objects, comprising: The computer manages flow line data relating to the movement of each moving object, queue status data indicating the queue status of the moving objects, main flow line data indicating the area and direction of main flow lines indicating a group of flow line data having a flow line density equal to or greater than a certain value, and condition data including information on the number of moving objects to be accommodated in the queue, Each of the flow line data relating to the movement of each moving object includes information for identifying the moving object, information on a start time related to the flow line data, information on an end time related to the flow line data, and information on a flow line formed by the moving object indicated by the information for identifying the moving object from the start time to the end time related to the flow line data, information regarding a flow line formed by a moving object indicated by the information identifying the moving object from the start time to the end time related to the flow line data is information of a LINESTRING as geometry data of the moving object indicated by the information identifying the moving object, regarding the start time and the end time related to the flow line data, or information of coordinate values ​​of the moving object indicated by the information identifying the moving object at each of the start time and the end time related to the flow line data; Each of the queue state data indicating a queue state of moving objects has information on a start time associated with the queue state data, information on an end time associated with the queue state data, and information on the order of the moving objects in the queue from the start time to the end time associated with the queue state data, information on the order of the moving objects in the queue from the start time to the end time, which is related to the queue state data, is composed of an array of information for identifying the moving objects; The computer program includes: the step of creating data on a planned queue line by determining planned guide positions of the mobile objects in the queue for the number of mobile objects planned to be accommodated in the queue based on the queue state data, the main flow line data, and the condition data, In the step of creating the queue planned line data, the computer, when setting the queue planned line indicated by the queue planned line data, can also set the queue planned line so that it intersects with an area of ​​the main flow line while giving priority to preventing the queue planned line from intersecting with the area of ​​the main flow line, In the step of creating data on the planned queue line, the computer determines the planned guide positions such that a distance between adjacent planned guide positions in a portion of the planned queue line that intersects with an area of ​​the main flow line is longer than a distance between adjacent planned guide positions in a portion of the planned queue line that does not intersect with an area of ​​the main flow line. Computer program.

Images