JP7399077B2 - Traffic management device, traffic management method, and traffic management system - Google Patents

Description

The present invention relates to a traffic management device, a traffic management method, and a traffic management system that manage the traffic of a mobile object.

As this type of technology, there is conventionally known a traffic management system that generates a travel route for a mobile object that operates via stops in response to a user's request to get on and off at each stop (for example, Patent Document (see 1). In the traffic management system of Patent Document 1, a traffic route is generated so as to pass through a stop where a boarding/alighting request is made.

Japanese Patent Application Publication No. 2002-208091

In the operation management system described in Patent Document 1, the moving object travels along a predetermined operation route and users can only get on and off at predetermined stops, which provides high efficiency and satisfaction for the user. It is difficult to carry out operational management.

The operation management device, which is one aspect of the present invention, includes an operation route generation unit that generates an operation route of a shared vehicle that a user can ride, an operation information acquisition unit that acquires operation information of the shared vehicle, and a traffic management device that allows users to get on and off the vehicle. a user information acquisition unit that acquires a request, current location information, destination information , and movable range information including the current location and movable distance of a portable mobile object that the user can ride and carry; When the user's boarding/alighting request is acquired by the section, the operation information of the shared vehicle acquired by the operation information acquisition section and the user's current location information , destination information, and movable range information acquired by the user information acquisition section are combined. a boarding and alighting point determination unit that determines a boarding point for the user to board the shared vehicle and an alighting point for the user to alight from the shared vehicle on the service route generated by the service route generating unit; The vehicle includes an output section that outputs the boarding point and the alighting point determined by the boarding and alighting point determination section.

Another aspect of the present invention is a traffic management method, which is executed by a computer, and includes the steps of : generating a travel route of a shared vehicle in which a user can ride ; acquiring operation information of the shared vehicle; A step of obtaining a boarding/disembarkation request, current location information, destination information, and movable range information including the current location and movable distance of a portable mobile object that the user can ride and carry; Once acquired, based on the operation information of the shared vehicle, the user's current location information, destination information, and movable range information, the boarding point for the user to board the shared vehicle on the operation route and the shared travel information are determined. and a step of outputting the boarding point and the getting off point.

Still another aspect of the present invention is a traffic management system including a traffic management device, an on-vehicle terminal mounted on a shared vehicle, and a user terminal owned or carried by a user, wherein the on-vehicle terminal is connected to a driving route. The user terminal includes a control unit that controls the movement of the shared vehicle according to the operation route generated by the generation unit, and a communication unit that transmits operation information of the shared vehicle to the operation management device. It has a communication unit that transmits a boarding/alighting request, current location information, and destination information to the operation management device.

According to the present invention, the operation of moving objects can be managed efficiently.

FIG. 1 is a diagram schematically showing an example of an operation performed by applying a traffic management system according to an embodiment of the present invention. 1 is a diagram schematically showing the configuration of a traffic management system according to an embodiment of the present invention. FIG. 3 is a block diagram showing a schematic configuration of the traffic management server in FIG. 2. FIG. 4 is a flowchart showing an example of a process executed by the traffic management server of FIG. 3.

Embodiments of the present invention will be described below with reference to FIGS. 1 to 4. The operation management system according to the embodiment of the present invention manages the operation of large-sized mobility vehicles (public transportation) such as buses according to requests for boarding and alighting from users, and notifies users of boarding and alighting points and the like.

FIG. 1 is a diagram schematically showing an example of an operation performed by applying a traffic management system according to an embodiment of the present invention. FIG. 1 shows two large-sized mobility vehicles 2a and 2b (sometimes collectively referred to as large-sized mobility 2) operating on a predetermined route, and also shows operation routes RB1 and RB2 of each large-sized mobility 2 (these (sometimes referred to collectively as the operating route RB) are each indicated by a solid arrow. The operation route RB may be a predetermined operation route, but is preferably an operation route that is dynamically generated so that the large-sized mobility vehicles 2a and 2b are operated at a distance from each other. On the operation route RB, boarding and alighting points P1 to P4 (these may be collectively referred to as boarding and alighting points P) at which the large-sized mobility vehicle 2 stops and allows the user 3 to board and alight are shown.

User 3 is meeting a friend at facility B, and plans to stop by facility A on the way to facility B, and uses large-sized mobility vehicle 2 at that time. Specifically, in order to board the large-sized mobility vehicles 2a and 2b, the user 3 moves along the boarding routes RS1 and RS3 and accesses the operating routes RB1 and RB2. Further, after getting off the large mobility vehicle 2a, 2b, the user 3 moves along the alighting routes RS2, RS4 and heads for the destination (boarding routes RS1, RS3, and alighting routes RS2, RS4 are combined into a boarding/alighting route RS). (sometimes called).

The large-sized mobility vehicle 2 is, for example, a vehicle (for example, a bus) having an automatic driving function, and travels automatically on the operating route RB, and stops at a boarding/disembarking point P to allow the user 3 to board or alight. When the large-sized mobility device 2 allows the user 3 to get on and off the vehicle, it means, for example, to perform operations necessary for the user 3 to get on and off, such as opening/closing a door or raising/lowering a step, in response to the getting on/off motion of the user 3 detected by an in-vehicle camera or the like. means. The large-sized mobility vehicle 2 is not a means of transportation for the purpose of high-speed transportation of cargo or people, but is a means of transportation that circulates at a relatively leisurely speed between various facilities including high-speed transportation stations and the like. The large-sized mobility device 2 not only functions as a means of transportation, but also constitutes various spaces that provide various services to the user 3. For example, the inside of the large-sized mobility vehicle 2 can be configured as a social salon, a coffee shop, a bar, or a plurality of types of small-scale stores.

The user 3 carries a user terminal 4 such as a smartphone, a tablet terminal, a mobile phone, or the like. The user 3 manages his or her own action schedule by inputting it into the user terminal 4 or displaying it on the user terminal 4 (including notifications by sound, vibration, etc.). The activity schedule includes a possible departure time from the current location of the user 3, a destination, a desired time of arrival at the destination, and the like. In addition to the activity schedule, the user's own preference information is also managed via the user terminal 4. The preference information is what the user 3 desires when traveling, and includes information such as wanting to play games while traveling, shopping while traveling, and wanting to shorten waiting time while traveling.

The user 3 has a small mobility device 5 that can be ridden and carried freely. The small mobility device 5 is a simple electric means of transportation, such as a skateboard or kick skater, on which one or two people can stand and ride. Although the small mobility device 5 may have a seat, the size and weight are such that the user 3 can carry it when not riding. The small mobility vehicle 5 has an automatic driving function and moves automatically on the boarding and alighting route RS. That is, when the user 3 heads to the boarding point P1 or P3 or to the destination from the drop-off point P2 or P4, the user 3 turns on the power of the small mobility vehicle 5 and gets on the small mobility vehicle 5. When the user 3 gets on the large-sized mobility 2, the user 3 turns off the power of the small-sized mobility 5 and carries the small-sized mobility 5. That is, the small mobility 5 is brought into the large mobility 2.

The configuration of a traffic management system that can realize the above operations will be explained. FIG. 2 is a diagram schematically showing the configuration of the traffic management system 100 according to the embodiment of the present invention. The operation management system 100 uses in-vehicle terminals 20a and 20b (collectively referred to as in-vehicle terminals 20) mounted on a plurality of (two in FIG. 1) large-sized mobility vehicles 2a and 2b registered in advance as shared transportation means. ), a user terminal 4, an in-vehicle terminal 50 mounted on a small mobility vehicle 5, and an operation management server 10. These in-vehicle terminals 20, user terminals 4, in-vehicle terminals 50, and operation management server 10 are connected to a network 6 including a wireless communication network constituted by a cellular network such as 3G (3rd Generation) or LTE (Long Term Evolution), for example. Ru.

The in-vehicle terminal 20 of the large-sized mobility vehicle 2 includes a communication section 21, a GPS receiver 22, and a control section 23.

The communication unit 21 is configured to be able to communicate wirelessly with the operation management server 10 via the network 6 . The communication unit 21 may be configured to include a close proximity wireless communication unit (not shown) to which close proximity wireless communication technology such as Wi-Fi (registered trademark) and Bluetooth (registered trademark) can be applied. The communication unit 21 transmits operation information including identification information for identifying the large-sized mobility 2 and the current location of the large-sized mobility 2 detected by the GPS receiver 22 to the operation management server 10. The communication unit 21 receives from the operation management server 10 an operation route RB generated by the operation management server 10 or predetermined in which the large-sized mobility 2 should travel, and a boarding/disembarking point P at which the large-sized mobility 2 should stop. do. Note that the operation information includes, in addition to the current location, the congestion situation of the passengers in the large mobility vehicle, abnormality information (information such as failure) that may impede the operation of the large mobility vehicle 2, and the like.

The GPS receiver 22 receives positioning signals from a plurality of GPS satellites, and thereby measures the position (latitude, longitude, etc.) of the large-sized mobility vehicle 2.

The control unit 23 includes a computer having a calculation unit such as a CPU, a storage unit such as a ROM or RAM, and other peripheral circuits, and can be wirelessly connected to the network 6 via the communication unit 21. When the communication unit 21 receives the operation route RB from the operation management server 10, the control unit (calculation unit) 23 controls various actuators (travel motors, (steering motor, etc.). Further, when the communication unit 21 receives the boarding and alighting point P from the operation management server 10, the control unit 23 controls the traveling actuator, door opening/closing actuator, etc. of the large-sized mobility vehicle 2 so as to stop at the boarding and alighting point P and allow the user 3 to get on and off. do.

Further, the control unit 23 may control the travel actuator, door opening/closing actuator, etc. of the large-sized mobility vehicle 2 in response to a boarding/alighting request from the user 3 near the travel route RB, without using the traffic management server 10 . A request for boarding or alighting by the user 3 who is near the operating route RB can be detected by, for example, using an on-vehicle camera or the like to detect an action (such as a raised hand) of the user 3 who desires to board or alight. The boarding/alighting request of the user 3 can also be received from the user terminal 4 via close proximity wireless communication.

The user terminal 4 includes a communication section 41, a GPS receiver 42, an input section 43, and a display section 44.

The communication unit 41 is configured to be able to communicate wirelessly with the operation management server 10 via the network 6 . The communication unit 41 may be configured to include a close proximity wireless communication unit, and in this case, when the user 3 is in the vicinity of the large mobility 2 while riding in the large mobility 2, the on-vehicle terminal 20 of the large mobility 2 It is possible to communicate with the communication unit 21 of , via close proximity wireless communication. The communication unit 41 transmits to the operation management server 10 a request for the user 3 to get on and off the large-sized mobility vehicle 2 and current location information including the current location of the user 3 (user terminal 4) detected by the GPS receiver 42, and also inputs The user information including the action schedule and preference information of the user 3 input through the section 43 is transmitted. The communication unit 21 receives various information and notifications from the operation management server 10, including the boarding and alighting point P, the boarding and alighting route RS, and the identification information of the large-sized mobility vehicle 2.

The GPS receiver 42 receives positioning signals from a plurality of GPS satellites, and thereby measures the position of the user 3 carrying the user terminal 4.

The input unit 43 is configured by a physical switch (for example, a touch panel) that can be operated by pressing. The input unit 43 may be configured with a microphone, and various commands may be input by voice via the microphone. The user 3 inputs user information via the input unit 43, and inputs a request for getting on and off the large-sized mobility vehicle 2 when the user 3 desires to get on and off the large-sized mobility vehicle 2.

The display unit 44 is configured by, for example, a liquid crystal display, and displays user information in response to a request input by the user 3 via the input unit 43, or displays various information and notifications received from the operation management server 10 or the like. . In addition to the display unit 44, a speaker, a vibrator, or the like may be provided to read out the displayed content aloud or to notify the user by sound, vibration, or the like.

The control unit 45 includes a computer having a calculation unit such as a CPU, a storage unit such as a ROM or RAM, and other peripheral circuits, and can be wirelessly connected to the network 6 via the communication unit 41. The control unit (calculation unit) 45 causes the display unit 44 to display the user information input by the user 3 and various information and notifications received from the operation management server 10. The control unit (storage unit) 45 stores user information input by the user 3 and various information received from the operation management server 10.

The in-vehicle terminal 50 of the small mobility vehicle 5 includes a communication section 51, a GPS receiver 52, and a control section 53.

The communication unit 51 is configured to be able to communicate wirelessly with the operation management server 10 via the network 6 . The communication unit 51 may be configured to include a close proximity wireless communication unit. The communication unit 51 transmits movable range information including the current location of the small mobility 5 detected by the GPS receiver 52 and information on the distance and speed that the small mobility 5 can travel to the operation management server 10. The communication unit 51 receives the boarding and alighting route RS from the current location to the boarding and alighting point P where the small mobility vehicle 5 should travel from the operation management server 10 .

The GPS receiver 52 receives positioning signals from a plurality of GPS satellites, and thereby measures the position (latitude, longitude, etc.) of the small mobility vehicle 5.

The control unit 53 includes a computer having a calculation unit such as a CPU, a storage unit such as a ROM or RAM, and other peripheral circuits, and can be wirelessly connected to the network 6 via the communication unit 51. After the communication unit 51 receives the boarding and alighting route RS from the operation management server 10, the control unit (computing unit) 53 controls the small mobility 5 to travel on the boarding and alighting route RS when the user 3 performs an operation to start traveling. Controls the actuators for driving (travel motor, steering motor, etc.).

Note that the small mobility device 5 may have the functions of the user terminal 4. That is, the in-vehicle terminal 50 of the small mobility vehicle 5 may have an input section and a display section. Alternatively, the in-vehicle terminal 50 may be omitted from the small mobility device 5, and the control unit 45 of the user terminal 4 may control the traveling actuator of the small mobility device 5. The user 3 may move on foot following the guidance of the boarding/disembarking route RS by the user terminal 4, or may move manually by operating the small mobility vehicle 5.

FIG. 3 is a block diagram showing a schematic configuration of the traffic management server 10. As shown in FIG. The operation management server 10 is configured to include an arithmetic processing unit having a processor, memory, etc., that is, a CPU, ROM, RAM, and other peripheral circuits, and communicates with the in-vehicle terminal 20 of the large-sized mobility device 2, the user terminal 4, It is also possible to communicate with the in-vehicle terminal 50 of the small mobility vehicle 5. As shown in FIG. 3, the operation management server 10 has a functional configuration including an operation route generation section 12, an operation information acquisition section 13, a user information acquisition section 14, a selection section 15, and a boarding/alighting point determination section 16. , a boarding/alighting route generating section 17 , an output section 18 , and a storage section 19 . Although not shown, the operation management server 10 also has an input section and a display section.

The operation route generation unit 12 generates an operation route RB for each large-sized mobility vehicle 2, and determines an operation schedule for traveling on the operation route RB. For example, the operation route generation unit 12 generates the operation route RB so that the large-sized mobility vehicles 2a and 2b are operated at a distance from each other on a main road or the like within the operation area of the large-sized mobility vehicle 2 registered in advance.

The large-sized mobility vehicle 2 is stored in a garage at a predetermined location, for example, outside of operating hours, leaves the garage to start operating, and returns to the garage when the operation is finished. The operation route generation unit 12 determines the operation schedule according to the pre-registered departure time and arrival time of the large-sized mobility vehicle 2, stop times at facilities within the area, and scheduled boarding and alighting times for users. The operation route generation unit 12 generates an operation route RB and determines the operation schedule, taking into consideration the weather conditions in the operation area on that day, the status of events on the operation route, and traffic conditions such as congestion and road closures. You can also do this. The operation route RB of the large-sized mobility vehicle 2 generated by the operation route generation unit 12 and the determined operation schedule are stored in the storage unit 19 in association with each large-scale mobility device 2.

The operation information acquisition unit 13 transmits information transmitted from the in-vehicle terminal 20 of the large-sized mobility 2 via the communication unit 21, that is, identification information of the large-sized mobility 2 and operation information including the current location of the large-sized mobility 2, to the communication unit 11. Get it through. The identification information of the large-sized mobility 2 also includes information about various services provided within the large-sized mobility 2. The operation information acquisition unit 13 acquires identification information and operation information of the large-sized mobility vehicle 2 periodically (for example, every few minutes or every few seconds). The identification information and operation information of the large-sized mobility vehicle 2 acquired by the operation information acquisition section 13 are stored in the storage section 19 and updated at any time.

The user information acquisition unit 14 acquires, via the communication unit 11, the boarding/alighting request of the user 3 and the current location information transmitted from the user terminal 4 via the communication unit 41. The user information acquisition unit 14 also has a function of receiving a boarding/alighting request and current location information, and always acquires (always accepts) a boarding/alighting request and current location information transmitted from the user terminal 4. Further, the user information acquisition unit 14 acquires, via the communication unit 11, the movable range information of the small mobility 5 transmitted from the in-vehicle terminal 50 of the small mobility 5 via the communication unit 51. The user information acquisition unit 14 also has a function of receiving movable range information, and always acquires movable range information transmitted from the small mobility device 5 (always accepts it). Note that when the user 3 does not use the small mobility device 5 and moves on foot, the user 3's movable range information may be acquired from the user terminal 4.

Further, the user information acquisition unit 14 acquires, via the communication unit 11, the user information of the user 3, which is stored in the storage unit of the user terminal 4 and transmitted from the user terminal 4 via the communication unit 41. The user information acquired by the user information acquisition unit 14 is stored in the storage unit 19. Note that the usage history of the user 3 including the user information stored in the storage unit 19 may be utilized when the user 3 uses the large-sized mobility vehicle 2 next time. Alternatively, the operation management server 10 may propose the use of the large-sized mobility vehicle 2 to the user 3 based on the usage history, regardless of whether or not the user 3 requests to get on or off the vehicle. Such a proposal can be made, for example, when an event targeting a specific user is held in the large-sized mobility vehicle 2.

The selection unit 15 selects the large-sized mobility vehicle 2 to be used by the user 3, when the user information acquisition unit 14 acquires the boarding/alighting request of the user 3, the user information, and the movable range information of the small-sized mobility vehicle 5. In this case, the selection unit 15 selects the operation route RB, identification information, and operation information of the large-sized mobility vehicle 2 stored in the storage unit 19, the user information of the user 3, and the current location of the user 3 acquired by the user information acquisition unit 14. Based on the information and the movable range information of the small mobility 5, the large mobility 2 on which the user 3 (and the small mobility 5) gets on and off is selected.

More specifically, the selection unit 15 matches the action schedule of the user 3 based on the operation route RB and operation information of the large mobility 2, the current location information of the user 3, and the movable range information of the small mobility 5. Select Large Mobility 2. Furthermore, the selection unit 15 selects a large-sized mobility device 2 that matches the preference information of the user 3 based on the identification information of the large-sized mobility device 2 . The selection unit 15 may select a plurality of candidates for the large-sized mobility vehicle 2 on which the user 3 gets on and off, transmit the selected plurality of candidates to the user terminal 4, and allow the user 3 to select one of them.

The boarding and alighting point determining unit 16 determines the boarding and alighting point P on the operating route RB when the large-sized mobility vehicle 2 on which the user 3 gets on and off is selected by the selection unit 15. In this case, the boarding and alighting point determining unit 16 determines the boarding and alighting point P based on the operation route RB and operation information of the large-sized mobility 2 selected by the selection unit 15 and the movable range information of the small-sized mobility 5. Specifically, the boarding and alighting point P is determined so that the travel distance or travel time of the small mobility vehicle 5 is the shortest.

The boarding and alighting point determining unit 16 may determine the boarding points P1 and P3 so that the waiting time for the user 3 is the shortest. For example, if user 3's preference information includes information such as ``I want to shorten the waiting time when moving,'' user 3 may want to wait for the arrival of large mobility vehicle 2 at boarding points P1 and P3 to be as short as possible. Boarding points P1 and P3 are determined so that In this case, although the travel distance of the small mobility device becomes longer, by giving the user 3 the feeling of actually moving, it is possible to suppress the occurrence of a situation in which the user 3 is made to wait and becomes irritated. Alternatively, weather information may be acquired separately and the boarding points P1 and P3 may be determined based on the weather information. In this case, for example, if the scheduled boarding time is a rainy day, a place with a roof or under a large tree is set as the boarding points P1 and P3. Further, when the temperature is low, a sunny place can be used, and when the wind is strong, a place with weak wind such as an alley surrounded by buildings or inside a tunnel can be used as the boarding points P1 and P3.

When the boarding and alighting point P is determined by the boarding and alighting point determination unit 16, the boarding and alighting route generation unit 17 generates a small mobility vehicle based on the current location information of the user 3 and the movable range information of the small mobility device 5 acquired by the user information acquisition unit 14. 5 (and user 3) to the boarding and alighting point P determined by the boarding and alighting point determining unit 16 is generated. If the user 3 does not wish to shorten the waiting time during travel, the boarding/disembarking route generation unit 17 generates the boarding/disembarking route RS so that the travel distance or travel time of the small mobility vehicle 5 is the shortest. If the user 3 desires to shorten the waiting time during movement, the boarding/alighting route generation unit 17 generates the boarding/alighting route RS so that the user 3's waiting time during movement becomes the shortest. That is, in order to shorten the waiting time of the user 3, the boarding/disembarking route generation unit 17 generates a boarding/disembarking route RS that takes a detour as necessary.

The output unit 18 transmits various information including the identification information of the large mobility vehicle 2 selected by the selection unit 15 and the boarding and alighting route RS generated by the boarding and alighting route generating unit 17 to the user terminal 4, and notifies the user 3. At the same time, the boarding/disembarking route RS is transmitted to the small mobility vehicle 5. If there are a plurality of large mobility vehicles 2 selected by the selection unit 15, the user 3 determines the large mobility vehicle 2 that the user 3 desires to board and alight from among the large mobility vehicles 2 selected based on various information. Even when the number of large-sized mobility vehicles 2 selected by the selection unit 15 is one, the user 3 may decide whether or not he or she agrees to get on and off the selected large-sized mobility vehicle 2 based on various information.

The output unit 18 transmits (notifies) the boarding and alighting point P determined by the boarding and alighting point determination unit 16 to the large-sized mobility vehicle 2 selected by the selection unit 15 (determined by the user 3). Note that if the user 3 who is planning to get on and off the vehicle wishes to use the elevating steps or support the occupants, such user information may also be notified.

FIG. 4 is a flowchart showing an example of a process executed by the traffic management server 10 according to a program stored in advance in the storage unit 19 of the traffic management server 10. Of the processes executed by the operation management server 10, FIG. Indicates the processing to be performed. The process shown in this flowchart is started, for example, when the operation management server 10 is powered on, and is repeated at a predetermined period. Note that the process in FIG. 4 is started in a state in which the operation route RB has been generated by the operation route generation unit 12 and the initial operation schedule has been determined. The operation route RB and the initial operation schedule are stored in the storage unit 19 in association with each large-sized mobility vehicle 2.

First, in step S1, the operation information acquisition section 13 reads the identification information and operation information of the large-sized mobility vehicle 2 received via the communication section 11. That is, the signal from the large mobility vehicle 2 (in-vehicle terminal 20) is read. Next, in step S2, the user information acquisition unit 14 reads the boarding/alighting request of the user 3, current location information, and user information received via the communication unit 11, and the movable range information of the small mobility vehicle 5. That is, signals from the user terminal 4 and the small mobility device 5 (in-vehicle terminal 50) are read. Next, in step S3, it is determined whether a boarding/alighting request has been received. If the answer in step S3 is affirmative, the process proceeds to step S4, and if the answer is negative, the process ends.

In step S4, the selection unit 15 selects a user based on the operation route RB, identification information, and operation information of the large mobility 2, user information and current location information of the user 3, and movable range information of the small mobility 5. 3 selects the large-sized mobility device 2 to get on and off from. Next, in step S5, the boarding and alighting point determination unit 16 processes the operation route RB corresponding to the large-sized mobility vehicle 2 selected in step S4, that is, the operation route RB stored in the storage unit 19, and the operation route RB acquired in step S1. The boarding and alighting point P is determined based on the operation information obtained in step S2 and the movable range information of the small mobility device 5 acquired in step S2. Next, in step S6, the operation route generation unit 12 changes the operation schedule, and through the processing in the output unit 18, the boarding and alighting point P determined in step S5 is changed to the on-vehicle terminal of the large mobility vehicle 2 selected in step S4. Send (notify) to 20. Note that the operation route generation unit 12 changes the initial operation schedule so that the vehicle stops at the boarding and alighting point P for a predetermined period of time.

Next, in step S7, the boarding and alighting route generation unit 17 generates a boarding and alighting route RS for the user 3 and the small mobility 5 based on the current location information of the user 3 and the movable range information of the small mobility 5. Next, in step S8, the output unit 18 transmits (notifies) various information including the identification information of the selected large-sized mobility vehicle 2 and the boarding/alighting route RS to the user 3 (user terminal 4), and also transmits (notifies) the user 3 (user terminal 4) Send the route RS to the small mobility vehicle 5.

The main operations of the traffic management system 100 according to this embodiment will be explained in more detail. The storage unit of the user terminal 4 stores preference information input by the user 3 in advance, such as "I want to play online games while traveling" and "I want to shorten waiting time while traveling." Via the user terminal 4, for example, as an activity schedule, the possible departure time is the current time (for example, 11 o'clock), and after stopping at facility A in FIG. Assume that an action schedule is input that requires arrival at 4:00 p.m.

At this time, when the user 3 inputs a request to get on and off the large mobility vehicle 2 into the user terminal 4, various types of information including the departure point and recommended departure time, boarding and alighting routes RS1 to RS4, and identification information of the large mobility vehicles 2a and 2b on which the user 3 gets on and off are sent. The information is displayed on the display unit 44 of the user terminal 4 (step S6, step S8). As a result, the user 3 can recognize the recommended departure time, the route to the destination, the services available in the large-sized mobility vehicle 2 that is scheduled to be boarded, and the like.

When the user 3 who has received the notification boards the small mobility vehicle 5 and departs from the current location at the recommended departure time (for example, 11:05), the small mobility vehicle 5 automatically moves along the boarding route RS1 to the boarding point P1 ( Step S8). That is, when the user 3 performs a starting operation, the small mobility vehicle 5 drives the traveling actuator and moves to the boarding point P1 along the boarding route RS1 instructed by the operation management server 10. Thereby, the user 3 can travel to the boarding point P1 along the boarding route RS1 by simply getting on the small mobility vehicle 5 at the starting point and performing a starting operation.

The boarding point P3 is determined to be a point on the operating route RB1 of the large-sized mobility vehicle 2a that is closest to the current location of the user 3 (step S5). Further, the boarding route RS1 is generated so that the travel distance or travel time of the user 3 and the small mobility vehicle 5 is the shortest (step S7). Thereby, the user 3 can efficiently move to the boarding point P1 along the boarding route RS1.

The user 3 who has arrived at the boarding point P1 gets off the small mobility vehicle 5, turns off the power of the small mobility device 5, carries it with him, and boards the large mobility vehicle 2a that has arrived at the boarding point P1. The large-sized mobility vehicle 2a in which user 3 rides is a vehicle that provides free Wi-Fi (registered trademark) service in the vehicle, which was selected based on user 3's preference information that ``I want to play online games while moving.'' (Step S4). Therefore, the user 3 can play online games while riding in the large-sized mobility vehicle 2a. Moreover, many passengers who have registered the same preference information as the user 3 are riding in the large-sized mobility vehicle 2a, and therefore the user 3 can communicate with other passengers, such as exchanging information. The user 3 can receive various services suitable for his or her preference information, and can feel highly satisfied while riding. Note that if passengers who have registered preference information similar to that of user 3 are gathered into one large mobility vehicle 2a, the distance of the operating route RB and the boarding and alighting points P will increase in order to collect the passengers, and the operation time will become longer. 3 can receive various services suited to his or her own preference information, so the disadvantage of longer service times becomes less noticeable.

When the large-sized mobility vehicle 2a reaches the drop-off point P2 instructed by the operation management server 10, it stops (step S6). Therefore, the user 3 can easily recognize the timing for getting off the vehicle, and can prevent forgetting to get off the vehicle or getting off the vehicle at the wrong place.

When the user 3 who gets off the large mobility vehicle 2a at the drop-off point P2 gets on the small mobility vehicle 5 and performs a starting operation, the small mobility vehicle 5 automatically drives to the facility A along the drop-off route RS2 instructed by the operation management server 10. (Step S8). The drop-off point P2 is determined to be the point on the operating route RB1 of the large-sized mobility vehicle 2a closest to the facility A (step S5), and the drop-off route RS2 is generated as the shortest route from the drop-off point P2 to the facility A (step S7). Thereby, the user 3 can efficiently move from the drop-off point P2 to the facility A.

When the user 3 who has finished his/her planned activity at the facility A departs from the facility A and gets on the small mobility vehicle 5 at the notified recommended departure time (for example, 3:05 p.m.), the small mobility vehicle 5 receives information from the operation management server 10. The vehicle moves to the boarding point P3 along the commanded boarding route RS3. The boarding point P3 and the boarding route RS3 are not determined so that the travel distance is the shortest, but are determined, for example, so that the waiting time of the user 3 during travel is the shortest (steps S5, S7).

That is, user 3's activity schedule includes a desired time of departure from facility A and a desired time of arrival at facility B, and the preference information includes information that "I want to shorten the waiting time while moving." Based on this information, the point where the user 3's waiting time is the shortest is determined as the boarding point P3 for the large mobility vehicle 2b, rather than the point closest to the facility A on the operation route RB2 of the large mobility vehicle 2b (step S5). Further, in order to shorten the waiting time at the boarding point P3, the boarding route RS3 is generated as a detour route instead of the shortest route connecting the facility A and the boarding point P3 (step S7). Thereby, the user 3 can board the large-sized mobility vehicle 2b without having to wait at the facility A or the boarding point P3.

At the boarding point P3, the user 3 can board the large-sized mobility vehicle 2b that matches the user's 3 preference information. When the large mobility 2b stops at the drop-off point P4 and the user 3 gets off the vehicle and gets on the small mobility 5, the small mobility 5 moves to the facility B along the drop-off route RS4 instructed by the operation management server 10. Thereby, user 3 can arrive at facility B at the scheduled time (for example, 16:00).

That is, according to the present embodiment, the user 3 simply inputs an action plan and a boarding/alighting request into the user terminal 4, and the optimal boarding/alighting point for the user 3 is determined on the operation route RB of the large-sized mobility vehicle 2, and the current location is determined. You will be notified with an efficient route and schedule from to your destination. For this reason, it is possible to efficiently manage the operation of the large-sized mobility vehicle 2 with a high level of satisfaction for the user 3.

According to this embodiment, the following effects can be achieved.
(1) The operation management server 10 includes an operation route generation unit 12 that generates an operation route RB of the large-sized mobility vehicle 2 that the user 3 can ride, an operation information acquisition unit 13 that acquires operation information of the large-scale mobility unit 2, and a user 3 When the user information acquisition unit 14 acquires the boarding and alighting request of the user 3, the user information acquisition unit 14 acquires the boarding and alighting request of the user 3, the current location information, and the destination information. Based on the operation information of the mobility 2 and the current location information and destination information of the user 3 acquired by the user information acquisition unit 14, the user 3 on the operation route RB generated by the operation route generation unit 12 a boarding point determining unit 16 that determines boarding points P1, P3 for boarding the vehicle, and boarding points P2, P4 for disembarking from the large-sized mobility vehicle 2; It is provided with an output unit 18 that outputs P3 and alighting points P2 and P4 (FIG. 3). This makes it possible to determine the boarding and alighting points P (P1 to P4) according to the boarding and alighting requests of the user 3, and to transmit the information to the user terminal 4 and the like. Therefore, it is possible to efficiently manage the operation of the large-sized mobility vehicle 2 with a high level of satisfaction for the user 3.

(2) The operation management server 10 generates boarding routes RS1, RS3 from the current location of the user 3 to the boarding points P1, P3, and alighting routes RS2, RS4 from the alighting points P2, P4 to the destination of the user 3. The vehicle further includes a boarding/alighting route generating section 17 (FIG. 3). The output unit 18 further outputs the boarding routes RS1 and RS3 and the alighting routes RS2 and RS4 generated by the boarding and alighting route generation unit 17 (step S8). The boarding and alighting routes RS1 to RS4 are transmitted to the small mobility device 5 owned by the user 3, for example. Thereby, the user 3 can board the small mobility vehicle 5 and efficiently travel from the current location to the boarding points P1, P3 and the alighting points P2, P4 to the destination.

(3) The user information acquisition unit 14 further acquires movable range information including the current location and the movable distance of the small mobility device 5 that the user 3 can ride and carry, and the boarding/alighting point determining unit 16 further acquires the user information. Based on the movable range information acquired by the acquisition unit 14, boarding points P1, P3 and alighting points P2, P4 are determined (step S5). The movable distance information can include speed information of the small mobility device 5, so that the boarding and alighting point P can be determined based on the movable distance, speed, etc. of the small mobility device 5 that the user 3 uses for transportation. Therefore, more efficient operation management of the large-sized mobility vehicle 2 can be performed.

(4) The user information acquisition unit 14 further acquires the preference information of the user 3, and the boarding point determination unit 16 further determines the boarding point P1, based on the preference information of the user 3 acquired by the user information acquisition unit 14. P3 and alighting points P2 and P4 are determined (step S5). As a result, for example, if user 3's preference information includes information such as ``I want to shorten the waiting time when traveling,'' the boarding and alighting points are set so that the waiting time for user 3 at the boarding point etc. is the shortest. P1 to P4 can be determined, and operation management of the large-sized mobility vehicle 2 can be performed with higher satisfaction for the user 3.

(5) The operation management server 10 operates a selection unit 15 that selects large-sized mobility vehicles 2a and 2b suitable for the user 3 from the plurality of large-sized mobility vehicles 2 based on the preference information of the user 3 acquired by the user information acquisition unit 14. Furthermore, it is provided (Figure 3). The large-sized mobility vehicle 2 has specific attributes such as a smoking vehicle or a women-only vehicle, or provides various services such as a network. By selecting a large mobility 2 that is more suitable for the preference information of the user 3 from among the large mobility 2 that provides such various services, the operation management of the large mobility 2 is performed with higher satisfaction for the user 3. I can do it.

(6) The operation management method according to the embodiment of the present invention generates an operation route RB of the large-scale mobility 2 that the user 3 can ride, acquires operation information of the large-scale mobility 2 (step S1), and The request, current location information, and destination information are acquired (step S2), and when the boarding/alighting request of the user 3 is acquired, based on the operation information of the large-sized mobility vehicle 2 and the current location information and destination information of the user 3 Then, the boarding points P1 and P3 for the user 3 to board the large mobility vehicle 2 and the alighting points P2 and P4 for the user 3 to get off the large mobility vehicle 2 on the operation route RB are determined (steps S3 and S5); The boarding points P1, P3 and the alighting points P2, P4 are output (step S8). This makes it possible to efficiently manage the operation of the large-sized mobility vehicle 2 with a high level of satisfaction for the user 3.

(7) The traffic management system 100 includes a traffic management server 10, an in-vehicle terminal 20 mounted on the large-sized mobility vehicle 2, and a user terminal 4 that is owned or carried by the user 3 (FIG. 2). The in-vehicle terminal 20 of the large-sized mobility vehicle 2 controls the movement of the large-sized mobility device 2 according to the operating route RB generated by the operating route generation unit 12, transmits operation information of the large-sized mobility device 2 to the operation management server 10, and sends the operation information of the large-sized mobility device 2 to the operation management server 10, 4 transmits the boarding/alighting request of the user 3, current location information, and destination information to the operation management server 10. The operation management system 100 as described above determines the optimum boarding and alighting points for the user 3 on the operation route RB of the large-sized mobility vehicle 2, and performs efficient operation management of the large-sized mobility device 2 with high satisfaction for the user 3.

Note that the above embodiment can be modified in various forms. Modifications will be described below. In the embodiment described above, the operation of a vehicle such as a bus having an automatic driving function is managed, but the configuration of a shared vehicle in which a user can ride is not limited to the above-mentioned configuration. The shared vehicle may be, for example, a shared taxi, a streetcar, a water bus, etc., and may be a small vehicle instead of a large vehicle. In addition, the shared vehicle may be operated by a driver rather than autonomously, and in this case, the on-vehicle terminal of the shared vehicle may be equipped with a display, etc., so that the driver can It may also be possible to provide guidance on operating routes and boarding and alighting points.

In the above embodiment, the operating route RB is shown as being fixed or generated, but it may be changeable according to a request. For example, based on the current location information of the user 3 and the movable range information of the small mobility 5, the operation route RB may be modified as appropriate through the processing of the operation route generation unit 12 of the operation management server 10, and the large mobility 2 may be notified. good. That is, the configuration of the travel route generation section is not limited to that described above.

In the above embodiment, the operation management server 10 as an example of the operation management device generates the operation route RB of the large-sized mobility vehicle 2, but the operation route is not limited to this. For example, the owner or the like of each large-sized mobility vehicle 2 may decide and register in advance. Alternatively, the operation route generated or modified on the large-sized mobility vehicle 2 side may be transmitted to the operation management server 10 side. That is, the operation route generation unit may be provided in a place other than the operation management device (for example, in a shared vehicle, etc.).

In the embodiment described above, information including the current location and the movable distance of the small mobility vehicle 5 is transmitted to the operation management server 10 as movable range information, but the movable range information is not limited to this. For example, when the user 3 moves on foot without using the small mobility device 5, the movable range information may be information including the user's current location and the movable distance.

In the above embodiment, the boarding and alighting point P is determined based on the activity schedule including the possible departure time from the user 3's current location, the destination, the desired time of arrival at the destination, etc. However, the user's destination information is It is not limited to those mentioned above. The destination information may be, for example, only the destination of the shared vehicle, and may not specify the possible departure time or desired arrival time. For example, destination information may include only boarding a shared vehicle. That is, the configuration of the user information acquisition unit that acquires movable range information and destination information is not limited to that described above.

In the above embodiment, the user 3 moves by using a simple electric compact mobility 5 such as a skateboard or kick skater that can be ridden while standing. For example, any portable moving object may be used. For example, it may be a wheelchair that can be ridden in the large mobility vehicle 2. If the size or weight of the small mobility vehicle 5 limits the large mobility devices 2 that can be ridden, such information may be included in the preference information of the user 3, and the large mobility device 2 may be selected accordingly. . Furthermore, if assistance is required from the occupants (staff or fellow passengers) of the large mobility vehicle 2, such information is included in the preference information of the user 3, and is transmitted to the large mobility vehicle 2 and notified to the occupant. Good too. Moreover, the small mobility 5 and the user terminal 4 may be formed integrally.

In the embodiment described above, the operation management server 10 as an example of the operation management device selects the large-sized mobility vehicle 2 that the user 3 rides, but the user 3 selects the large-sized mobility vehicle 2 that the user 3 wishes to ride via the user terminal 4. You may choose. That is, the selection unit for selecting a shared vehicle may be provided in a location other than the operation management device (for example, a user terminal).

The above description is merely an example, and the present invention is not limited to the above-described embodiments and modifications as long as the characteristics of the present invention are not impaired. It is also possible to arbitrarily combine the above embodiment and one or more of the modifications, and it is also possible to combine the modifications.

2 (2a, 2b) large mobility, 4 user terminal, 5 small mobility, 6 network, 10 operation management server, 11 communication department, 12 operation route generation section, 13 operation information acquisition section, 14 user information acquisition section, 15 selection section , 16 boarding and alighting point determination unit, 17 boarding and alighting route generation unit, 18 output unit, 19 storage unit, 20 in-vehicle terminal, 21 communication unit, 22 GPS receiver, 23 control unit, 41 communication unit, 42 GPS receiver, 43 input unit , 44 display unit, 45 control unit, 50 in-vehicle terminal, 51 communication unit, 52 GPS receiver, 53 control unit, 100 operation management system

Claims (6)

an operation route generation unit that generates an operation route of a shared vehicle that the user can ride;
an operation information acquisition unit that acquires operation information of the shared vehicle;
a user information acquisition unit that acquires a user's boarding/alighting request, current location information, destination information, and movable range information including the current location and movable distance of a portable mobile object that the user can ride and carry;
When the user information acquisition unit acquires the user's boarding/alighting request, the operation information of the shared vehicle acquired by the operation information acquisition unit, the user's current location information, and the destination acquired by the user information acquisition unit a boarding point for the user to board the shared vehicle and an alighting point for the user to alight from the shared vehicle on the operation route generated by the operation route generation unit based on the information and the movable range information; , a boarding and alighting point determination unit that determines the
An operation management device comprising: an output section that outputs the boarding point and the alighting point determined by the boarding and alighting point determination section. The traffic management device according to claim 1,
further comprising a boarding and alighting route generation unit that generates a boarding route from the user's current location to the boarding point and a boarding and alighting route from the alighting point to the user's destination,
The operation management device is characterized in that the output unit further outputs the boarding route and the alighting route generated by the boarding and alighting route generating unit. The traffic management device according to claim 1 or 2,
The user information acquisition unit further acquires user preference information,
The operation management device is characterized in that the boarding and alighting point determination unit determines the boarding and alighting points based on the user's preference information acquired by the user information acquisition unit. The traffic management device according to claim 3,
The operation management device further includes a selection unit that selects a shared vehicle based on the user's preference information acquired by the user information acquisition unit. executed by a computer,
generating an operating route for a shared vehicle that the user can ride;
a step of acquiring operation information of the shared vehicle;
obtaining the user's boarding/alighting request, current location information, destination information, and movable range information including the current location and movable distance of a portable mobile object that the user can ride and carry;
When the user's boarding/alighting request is acquired, the user on the operation route is requested to board the shared vehicle based on the operation information of the shared vehicle, the current location information, destination information, and movable range information of the user. determining a boarding point for boarding and a boarding point for disembarking from the shared vehicle;
An operation management method comprising the step of outputting the boarding point and the alighting point. The traffic management device according to any one of claims 1 to 4,
an in-vehicle terminal mounted on the shared vehicle;
An operation management system comprising: a user terminal owned or carried by the user;
The in-vehicle terminal includes a control unit that controls movement of the shared vehicle according to the operation route generated by the operation route generation unit, and a communication unit that transmits operation information of the shared vehicle to the operation management device. and,
The traffic management system, wherein the user terminal includes a communication unit that transmits the user's boarding/alighting request, current location information, and destination information to the traffic management device.

Images