Vehicle information management device

Abstract

To provide a vehicle information management device allowing a user to smoothly ride after a vehicle arrives at a scheduled riding area.SOLUTION: A vehicle information management device 10 comprises: a road surface information acquisition unit that acquires road surface information of a scheduled riding area 50 before a vehicle V arrives at the scheduled riding area 50 of a user P; a determination unit that determines whether or not a road surface height H of a scheduled riding position where the user P stands by in the scheduled riding area 50 is a height at which a slope 18 of the vehicle V can be installed, based on the road surface information acquired by the road surface information acquisition unit; and a proposing unit that proposes a change of the scheduled riding position to the user P when the determination unit determines that the road surface height H is not a height at which the slope 18 can be installed.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a vehicle information management device.

Background Art

[0002] The following Patent Document 1 discloses a slope system for a vehicle. The slope system of the following Patent Document 1 determines whether there is an obstacle in a slope deployment area where the slope of the vehicle is deployed at a boarding and alighting location (boarding planned area) such as a bus stop, and if it is determined that there is an obstacle in the slope deployment area, the vehicle is moved to a position where there is no obstacle.

Prior Art Document

Patent Document

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, in the vehicle slope system described in the above Patent Document 1, an obstacle detection device for detecting an obstacle is mounted on the vehicle. Therefore, the determination of whether the slope can be installed at the boarding and alighting location is made after the vehicle arrives at the boarding and alighting location (boarding planned area). Thus, if there is an obstacle at the user's waiting location (boarding planned position) and the slope cannot be installed, the user is forced to move to a location where the slope can be installed. As a result, it takes time from when the vehicle arrives at the boarding and alighting location (boarding planned area) until the user boards the vehicle.

[0005] In consideration of the above facts, an object of the present invention is to obtain a vehicle information management device that can smoothly allow a user to board the vehicle after the vehicle arrives at the boarding planned area.

Means for Solving the Problems

[0006] The vehicle information management device according to claim 1 includes a road surface information acquisition unit that acquires road surface information of the planned boarding area before the vehicle arrives at the planned boarding area of the user, and based on the road surface information acquired by the road surface information acquisition unit, determines whether the road surface height of the planned boarding position where the user waits in the planned boarding area is a height at which the slope of the vehicle can be installed. A determination unit, and when the determination unit determines that the road surface height is not a height at which the slope can be installed, Before the vehicle arrives at the user's scheduled boarding area, a proposal unit that proposes to the user to change the planned boarding position.

[0007] According to the present invention described in claim 1, before the vehicle arrives at the planned boarding area of the user, the road surface information of the planned boarding area is acquired by the road surface information acquisition unit. Further, based on the road surface information acquired by the road surface information acquisition unit, the determination unit determines whether the road surface height of the planned boarding position where the user waits in the planned boarding area is a height at which the slope of the vehicle can be installed. Therefore, it is possible to determine whether the slope can be installed earlier than in the case of determining whether the slope can be installed at the planned boarding position after the vehicle arrives at the planned boarding area. Here, the "planned boarding position" is a concept narrower than the "planned boarding area" such as a bus stop, which is an area where the user plans to board, and refers to the position where the user is actually waiting and it is assumed that the slope will be deployed from the vehicle.

[0008] Also, in the determination unit, when it is determined that the road surface height of the planned boarding position is not a height at which the slope can be installed, Before the vehicle arrives at the user's scheduled boarding area, the proposal unit proposes to the user to change the planned boarding position. As a result, the user can know that the current planned boarding position where they are waiting is a position where the slope cannot be installed, and can move before the vehicle arrives or immediately after the vehicle arrives.

[0009] The vehicle information management device according to claim 2, in the invention described in claim 1, the determination unit further determines whether there is an obstacle that becomes an obstacle when installing the slope at the planned boarding position based on the road surface information, and when there is no such obstacle and the road surface height is a height at which the slope can be installed, it is determined that the slope can be installed at the planned boarding position, and when there is such an obstacle and / or the road surface height is not a height at which the slope can be installed, it is determined that the slope cannot be installed at the planned boarding position.

[0010] According to the present invention described in claim 2, the determination unit further determines whether there is an obstacle that becomes an obstacle when installing a slope at the planned boarding position based on the road surface information. When there is no such obstacle and the road surface height is a height at which the slope can be installed, it is determined that the slope can be installed at the planned boarding position. On the other hand, when there is such an obstacle and / or the road surface height is not a height at which the slope can be installed, it is determined that the slope cannot be installed at the planned boarding position. When an obstacle is detected after the vehicle arrives at the planned boarding area, or when it is found that the slope cannot be installed due to an obstacle after the vehicle arrives at the planned boarding area and deploys the slope, the vehicle and the user are forced to move. In contrast, according to the present invention, it is possible to determine at an early stage whether the slope can be installed before the vehicle arrives at the planned boarding area, including the presence of obstacles.

[0011] The vehicle information management device according to claim 3, in the invention described in claim 2, the road surface information acquisition unit acquires the road surface information from a detection device provided in the planned boarding area.

[0012] According to the present invention described in claim 3, the road surface information is acquired from a detection device provided in the planned boarding area. For example, when a detection device is provided in a planned boarding area such as a bus stop, the road surface information is acquired from this detection device. Therefore, for example, even if the user does not deliberately photograph the planned boarding area while waiting for the vehicle, the road surface information is automatically acquired from the planned boarding area.

[0013] The vehicle information management device according to claim 4, in the invention described in claim 2, the road surface information acquisition unit acquires the road surface information from a terminal possessed by the user.

[0014] According to the present invention described in claim 4, the road surface information is acquired from a terminal possessed by the user. Thereby, for example, even when a detection device is not provided in the planned boarding area designated by the user in advance, the road surface information of the planned boarding area can be acquired from the terminal possessed by the user.

[0015] The vehicle information management device according to claim 5 includes a road surface information acquisition unit that acquires road surface information of a planned boarding area before a vehicle arrives at the planned boarding area of the user, and based on the road surface information acquired by the road surface information acquisition unit, a determination unit that determines whether there is an obstacle that becomes an obstacle when the door of the vehicle opens at a planned boarding position where the user waits in the planned boarding area, and when the determination unit determines that the obstacle exists, Before the vehicle arrives at the user's scheduled boarding area, a notification unit that notifies the user that the boarding opening has become narrow, and a control unit that changes the opening amount of the door when the determination unit determines that the obstacle exists.

[0016] According to the present invention described in claim 5, before the vehicle arrives at the planned boarding area of the user, the road surface information of the planned boarding area is acquired by the road surface information acquisition unit. Further, based on the road surface information acquired by the road surface information acquisition unit, the determination unit determines whether there is an obstacle that becomes an obstacle when the door of the vehicle opens at the planned boarding position where the user waits in the planned boarding area. Therefore, it is possible to determine whether the door can be opened earlier as compared with the case of determining after the vehicle arrives at the planned boarding area.

[0017] Also, when it is determined that an obstacle exists, Before the vehicle arrives at the user's scheduled boarding area, the notification unit notifies the user that the boarding opening has become narrow. Thereby, the user can determine the suitability of the current waiting place based on the opening amount of the door before the vehicle arrives.

[0018] Furthermore, when it is determined that an obstacle exists, the control unit changes the opening amount of the door. Thereby, after the vehicle arrives at the planned boarding area, it is possible to avoid a situation where the door hits an obstacle.

Advantages of the Invention

[0019] As described above, the vehicle information management device according to the present invention described in claim 1 has an excellent effect of enabling a user to board the vehicle smoothly after the vehicle arrives at the planned boarding area.

[0020] The vehicle information management device according to the present invention described in claim 2 has an excellent effect of enabling a user to board the vehicle even more smoothly after the vehicle arrives at the planned boarding area.

[0021] The vehicle information management device according to the present invention described in claim 3 has an excellent effect of being able to acquire road surface information without causing trouble to the user.

[0022] The vehicle information management device according to the present invention described in claim 4 has an excellent effect of being able to acquire road surface information even when a detection device is not installed in the planned boarding area.

[0023] The vehicle information management device according to the present invention described in claim 5 has an excellent effect of enabling a user to board the vehicle smoothly after the vehicle arrives at the planned boarding area.

Brief Description of the Drawings

[0024]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Mode for Carrying Out the Invention

[0025] Hereinafter, with reference to FIGS. 1 to 5, a vehicle information management system S including a vehicle V equipped with an on-vehicle unit 10 as a vehicle information management device according to an embodiment of the present invention will be described. Note that the arrow UP shown in FIG. 1 indicates the upper side in the vehicle up-and-down direction, the arrow FR indicates the front side in the vehicle front-and-rear direction, and the arrow RH indicates the right side in the vehicle width direction (left-and-right direction). In addition, when the directions of up-and-down, front-and-rear, and left-and-right are used without special mention in the following description, they indicate up-and-down in the vehicle up-and-down direction, front-and-rear in the vehicle front-and-rear direction, and left-and-right when the vehicle is facing the traveling direction.

[0026] (Overall System Configuration) As shown in FIG. 1, the vehicle information management system S of the present embodiment includes a vehicle V, a signpost 52 provided at a stop 50 as a boarding planned area where the user P waits to board the vehicle V, and a terminal 60 held by the user P. The terminal 60 has an imaging function and a communication function such as a smartphone. The user P is assumed to be riding in a wheelchair W as an example. Note that the user is not limited to a wheelchair user.

[0027] The on-vehicle unit 10, the terminal 60, and the control device 58 are connected via a network (not shown) and can communicate with each other. The network is connected to on-vehicle units of a plurality of vehicles, terminals of a plurality of users, and control devices of a plurality of stops.

[0028] (Configuration of Stop 50) At the bus stop 50, as an example, there is a signpost 52 on which the name of the bus stop 50, a timetable, a route map, etc. are displayed. Note that the bus stop is not limited to having the signpost 52 illustrated in FIG. 1, and may be, for example, one equipped with a roof or a wall. Further, the boarding scheduled area has a predetermined sign such as the signpost 52, and is not limited to the bus stop 50 where the vehicle V repeatedly stops, and may be, for example, a place designated by the user P on the vehicle allocation application of the terminal 60.

[0029] In addition, a guard pipe 54 is installed at the bus stop 50. In the present embodiment, when the user P is waiting for the vehicle V in front of the guard pipe 54, the guard pipe 54 is described as corresponding to an obstacle in the present invention.

[0030] At the bus stop 50, there is a height difference H as a road surface height between the sidewalk F where the user P waits and the road R on which the vehicle V travels. Specifically, the sidewalk F is provided at a position higher by the height difference H than the road R. Note that the boarding scheduled area is not limited to a road that can distinguish between the sidewalk F and the road R, and may be, for example, a parking lot without a step.

[0031] The signpost 52 is provided with a camera 56 as a detection device for acquiring road surface information of the bus stop 50. The camera 56 is configured to be able to photograph a predetermined road surface area (the shaded portion shown in FIG. 1) including the sidewalk F and the road R at the bus stop 50 as an example. Note that the detection device is not limited to the camera 56, and other devices such as a millimeter wave radar that transmits a probing wave to a predetermined range and receives a reflected wave, a lidar (Laser Imaging Detection and Ranging) that scans a predetermined range, and an ultrasonic sensor may be used, or a plurality of these devices may be used in combination.

[0032] In addition, the signpost 52 is provided with a control device 58 that transmits the road surface information to the in-vehicle device 10 of the vehicle V. The control device 58 records the height difference H between the sidewalk F and the road R at the bus stop 50 as registered information, and transmits it to the in-vehicle device 10 as road surface information in combination with the image photographed by the camera 56.

[0033] (Hardware Configuration of Vehicle V) Vehicle V equipped with in-vehicle device 10 is, as an example, an electric bus that runs in autonomous driving and can also run by remote control. Note that the vehicle may be a vehicle that runs in manual driving.

[0034] As shown in FIG. 1, a substantially rectangular opening 12 is formed in the left side portion of vehicle V. This opening 12 can be opened and closed by a pair of slide doors 14 that slide along the vehicle front-rear direction. Further, vehicle V includes a substantially rectangular plate-shaped slope 18 that moves outward in the vehicle width direction from opening 12 and is deployed outside vehicle V.

[0035] FIG. 1 shows vehicle V in a state where a pair of slide doors 14 are fully opened and slope 18 is deployed. The front slide door 14A is disposed outside the vehicle width direction of the left side portion of vehicle V on the front side in the vehicle front-rear direction of opening 12 in the opened state. The rear slide door 14B is disposed outside the vehicle width direction of the left side portion of vehicle V on the rear side in the vehicle front-rear direction of opening 12 in the opened state. Hereinafter, the region through which slide door 14 passes from the state where a pair of slide doors 14 are closed after vehicle V arrives at stop 50 to the fully opened state as shown in FIG. 1 is referred to as the "door deployment planned region". The pair of slide doors 14 are each opened and closed by a door opening / closing mechanism 28B (see FIG. 2).

[0036] Further, the floor surface 20A of the floor portion 20 of vehicle V is fully flat, and a storage portion 22 configured to be able to store slope 18 is provided below floor portion 20. Slope 18 is deployed and stored by a slope deployment / storage mechanism 28A (see FIG. 2) including a drive motor (not shown). Slope 18 is formed shorter than the width dimension of opening 12.

[0037] When the drive motor (not shown) drives with the slope 18 stored in the storage unit 22, the slope 18 is moved outward in the vehicle width direction by the slope deployment and storage mechanism 28A (see FIG. 2) and deployed outside the vehicle. At the rear end of the slope 18 in the deployment direction, a shaft portion (not shown) having an axis along the vehicle longitudinal direction is provided. When the slope 18 is drawn out from the storage unit 22, the tip 18A of the slope 18 can be rotated downward about the shaft portion. That is, when there is a height difference between the floor surface 20A of the floor portion 20 of the vehicle V and the sidewalk F, the slope 18 will incline downward as it moves toward the sidewalk F in the deployed state. Hereinafter, the region through which the slope 18 passes from the state where the slope 18 is stored after the vehicle V arrives at the station 50 to the deployed state shown in FIG. 1 is referred to as the "slope deployment planned region".

[0038] On the other hand, when the drive motor (not shown) drives with the slope 18 in the deployed state, the slope 18 moves toward the vehicle V side and is stored in the storage unit 22. Note that the slope may be composed of a single sheet or a plurality of sheets.

[0039] As shown in FIG. 2, the vehicle V includes an in-vehicle device 10, a plurality of ECUs (Electronic Control Units) 26, and a plurality of in-vehicle devices 28.

[0040] The in-vehicle device 10 includes a CPU (Central Processing Unit) 30A, a ROM (Read Only Memory) 30B, a RAM (Random Access Memory) 30C, an in-vehicle communication I / F (Interface) 30D, and a wireless communication I / F 30E. The CPU 30A, the ROM 30B, the RAM 30C, the in-vehicle communication I / F 30D, and the wireless communication I / F 30E are communicably connected to each other via an internal bus 30F.

[0041] The CPU 30A is a central processing unit that executes various programs and controls each part. That is, the CPU 30A reads a program from the ROM 30B and executes the program using the RAM 30C as a work area. The CPU 30A performs control of each of the above configurations and various arithmetic processes according to the program recorded in the ROM 30B.

[0042] The ROM 30B stores various programs and various data. The ROM 30B stores vehicle information 100 and a control program 110 for controlling the vehicle V. The vehicle information 100 is information including information regarding the width of the opening 12 and information regarding the relative positions of the slope deployment planned area and the door deployment planned area with respect to the vehicle V.

[0043] The RAM 30C temporarily stores a program or data as a work area.

[0044] The in-vehicle communication I / F 30D is an interface for connecting to each ECU 26. The in-vehicle communication I / F 30D uses a communication standard based on the CAN protocol. The in-vehicle communication I / F 30D is connected to the external bus 30G.

[0045] The wireless communication I / F 30E is connected to a network (not shown) and is a wireless communication module for communicating with the control device 58 of the stop 50 and the terminal 60 of the user P. The wireless communication I / F 30E uses a communication standard such as 5G, LTE, Wi-Fi (registered trademark), etc.

[0046] The ECU 26 is configured to include a body system ECU 26A. The body system ECU 26A comprehensively controls the slope deployment storage mechanism 28A, the door opening / closing mechanism 28B, and the vehicle height adjustment mechanism 28C. The vehicle height adjustment mechanism 28C includes a suspension (not shown) and is configured to be able to change the height of the floor surface 20A with respect to the road R and the sidewalk F. That is, the vehicle V can adjust the vehicle height by the vehicle height adjustment mechanism 28C. Thereby, the slope 18 can be installed on the sidewalk F within a predetermined range of road surface heights.

[0047] (Functional Configuration of On-Vehicle Device 10) As shown in FIG. 3, the on-vehicle device 10 functions as a road surface information acquisition unit 200, an obstacle detection unit 202, a determination unit 204, a proposal unit 206, a calculation unit 208, a notification unit 210, a reception unit 212, and a control unit 214 when the CPU 30A executes the control program 110.

[0048] The road surface information acquisition unit 200 has a function of acquiring road surface information of the stop 50 while the vehicle V is traveling on the route toward the stop 50. The road surface information acquisition unit 200 acquires road surface information from at least one of the control device 58 provided on the signpost 52 of the stop 50 and the terminal 60 held by the user P. As an example, the timing at which the road surface information acquisition unit 200 acquires road surface information is one minute before the arrival scheduled time when the vehicle V arrives at the boarding scheduled area, but it is not limited to this. For example, after the on-vehicle device 10 receives boarding request information from the terminal 60 of the user P, the road surface information may be acquired at any time at a predetermined time interval until the vehicle V arrives at the stop 50. In addition, the road surface information acquisition unit 200 acquires information regarding the dimension in the width direction of the user P together with the road surface information. For example, when the user P is boarding the wheelchair W as shown in FIG. 1, the dimension in the width direction of the wheelchair W is acquired.

[0049] The obstacle detection unit 202 has a function of detecting an obstacle that may exist in the slope deployment planned area and the door deployment planned area when the vehicle V arrives at the stop 50, that is, an obstacle that may interfere with the deployed slope 18 or the pair of sliding doors 14.

[0050] The determination unit 204 has a function of determining whether the slope 18 is necessary when the user P boards and alights from the vehicle V based on the boarding request information received by the reception unit 212 described later.

[0051] Further, based on the road surface information acquired by the road surface information acquisition unit 200, the determination unit 204 has a function of determining whether there is an obstacle that becomes an obstacle when installing the slope 18 of the vehicle V at the scheduled boarding position where the user P waits at the bus stop 50.

[0052] Furthermore, the determination unit 204 has a function of determining, based on the road surface information, whether the road surface height at the scheduled boarding position is a height at which the slope 18 of the vehicle V can be installed. Here, whether the road surface height is a height at which the slope 18 can be installed is determined in consideration of the vehicle height adjustment by the vehicle height adjustment mechanism 28C and the adjustment amount by rotating the tip 18A of the slope 18 downward around the shaft portion (not shown).

[0053] When there is no obstacle that becomes an obstacle when installing the slope 18 at the scheduled boarding position and the road surface height is a height at which the slope 18 can be installed, the determination unit 204 determines that the slope 18 can be installed at the scheduled boarding position. On the other hand, when at least one of the case where there is an obstacle that becomes an obstacle when installing the slope 18 at the scheduled boarding position and the case where the road surface height is not a height at which the slope 18 can be installed occurs, the determination unit 204 determines that the slope 18 cannot be installed at the scheduled boarding position.

[0054] As an example, when the user P is waiting for the vehicle V in front of the guard pipe 54 (sidewalk side), that is, when the position where the guard pipe 54 exists is set as the scheduled boarding position, the determination unit 204 determines that the slope 18 cannot be deployed at the scheduled boarding position. On the other hand, as shown in FIG. 1, when there is no obstacle at the scheduled boarding position where the user P waits and the height difference H between the road lane R and the sidewalk F is a height at which the slope 18 can be installed, the determination unit 204 determines that the slope 18 can be deployed at the scheduled boarding position.

[0055] Further, the determination unit 204 has a function of determining, based on the road surface information, whether there is an obstacle that becomes an obstacle when the pair of sliding doors 14 are opened at the scheduled boarding position.

[0056] As an example, when user P is waiting for vehicle V in front of (on the sidewalk side of) guard pipe 54 and it is predicted that sliding door 14 will interfere with guard pipe 54 during deployment, determination unit 204 determines that the pair of sliding doors 14 cannot be fully opened at the boarding planned position. On the other hand, as shown in FIG. 1, when there is no obstacle in the door deployment planned area where the pair of sliding doors 14 are to be deployed, determination unit 204 determines that the pair of sliding doors 14 can be fully opened.

[0057] Furthermore, when there is an obstacle that will become an obstruction when the pair of sliding doors 14 open, determination unit 204 has a function of determining whether the pair of sliding doors 14 will open to a width greater than or equal to the width at which user P can board, based on information regarding the dimensions of user P in the width direction.

[0058] When determination unit 204 determines that the pair of sliding doors 14 will open to a width greater than or equal to the width at which user P can board, it has a function of determining whether user P wishes to move locations. As an example, determination unit 204 determines whether user P has pressed a button indicating a wish to move locations on terminal 60. On the other hand, when user P has pressed a button indicating no wish to move locations on terminal 60 or when the application is terminated without making a selection, determination unit 204 determines that user P did not wish to move locations.

[0059] Furthermore, determination unit 204 has a function of determining whether user P has agreed to the location movement proposed by proposal unit 206, which will be described later. As an example, determination unit 204 determines whether user P has pressed a button indicating agreement to the location movement on terminal 60. When user P has pressed a button indicating disagreement to the location movement on terminal 60 or when the application is terminated without making a selection, determination unit 204 determines that user P did not agree to the location movement.

[0060] When it is determined by the determination unit 204 that the slope 18 cannot be installed at the planned boarding position, the proposal unit 206 has a function of proposing to the user P to change the planned boarding position. Further, when it is determined by the determination unit 204 that the pair of sliding doors 14 cannot be opened by a width that allows the user P to board due to an obstacle, the proposal unit 206 has a function of proposing to the user P to change the planned boarding position.

[0061] When the user P agrees to the location movement proposed by the proposal unit 206 or when the notification unit 210 receives a notification that the boarding opening will become narrow and the user P wishes to move the location, the calculation unit 208 has a function of calculating a recommended movement area as a candidate for the new planned boarding position. Here, the recommended movement area is an area based on the road surface information, where the slope 18 can be installed and the pair of sliding doors 14 can be fully opened, that is, an area without obstacles that can interfere with the slope deployment planned area and the door deployment planned area and with a road surface height at which the slope can be deployed.

[0062] When it is determined by the determination unit 204 that although there is an obstacle, the pair of sliding doors 14 can open wider than the width that allows the user P to board, the notification unit 210 has a function of notifying the user P's terminal 60 that the boarding opening will become narrower than normal. Here, the "normal time" referred to here means the state where both of the pair of sliding doors 14 are fully opened. Further, after or at the same time as the notification unit 210 notifies the user P's terminal 60 that the boarding opening will become narrower than normal, the notification unit 210 has a function of sending a notification to the terminal 60 to inquire whether the user P wishes to move the location, that is, change the planned boarding position. Furthermore, the notification unit 210 has a function of notifying the user P's terminal 60 of the recommended movement area calculated by the calculation unit 208.

[0063] The reception unit 212 has a function of receiving boarding request information from the user P's terminal 60. For example, when the user P calls the vehicle V and inputs at the terminal 60 that "barrier-free is desired", the reception unit 212 receives the boarding request information. Further, the reception unit 212 has a function of receiving information on the user P's desire to change the planned boarding position from the terminal 60.

[0064] Based on the control program 110, the control unit 214 has a function of controlling the in-vehicle device 28 including the slope deployment storage mechanism 28A, the door opening / closing mechanism 28B, and the vehicle height adjustment mechanism 28C. Further, when it is determined by the determination unit 204 that there is an obstacle in the door deployment planned area and the boarding gate becomes narrow, but the movement request information cannot be received, the control unit 214 has a function of changing the door opening amount of the control program 110.

[0065] (Operation of this Embodiment) Next, the flow of the process executed by the in-vehicle device 10 will be described using the flowcharts shown in FIGS. 4 and 5, and the operation of this embodiment will be described through this description. FIG. 4 shows the flow of the process performed by the in-vehicle device 10 after receiving the boarding request information from the terminal 60 of the user P and before the vehicle V arrives at the stop 50.

[0066] In step S100, the CPU 30A of the in-vehicle device 10 acquires road surface information from the control device 58 of the stop 50 and the terminal 60 of the user P.

[0067] Subsequently, in step S102, the CPU 30A detects obstacles in the slope deployment planned area and the door deployment planned area based on the road surface information.

[0068] Then, in step S104, the CPU 30A determines whether there is an obstacle in the slope deployment planned area.

[0069] If it is determined in step S104 that there is no obstacle in the slope deployment planned area, the CPU 30A determines in step S106 whether the road surface height of the sidewalk F including the boarding planned position where the user P waits is a height at which the slope 18 can be installed.

[0070] If, in step S106, it is determined that the road surface height at the planned boarding position is a height at which slope 18 can be installed, the CPU 30A determines, in step S108, whether there is an obstacle in the planned door deployment area.

[0071] If, in step S108, it is determined that there is no obstacle in the planned door deployment area, the CPU 40A ends the processing before the vehicle V arrives at the stop 50.

[0072] On the other hand, if it is determined in step S104 that there is an obstacle in the planned slope deployment area, the CPU 30A determines that slope 18 cannot be installed at the planned boarding position, and in step S110, proposes to the user P a location movement, that is, a change in the planned boarding position.

[0073] Subsequently, in step S112, the CPU 30A determines whether the user P agrees to the location movement.

[0074] If, in step S112, it is determined that the user agrees to the location movement, the CPU 30A calculates, in step S114, a recommended movement area.

[0075] The CPU 30A notifies the user P of the recommended movement area calculated in step S114 in step S116, and executes the processing after step S100 again.

[0076] On the other hand, if it is determined in step S112 that the user P does not agree to the location movement, the CPU 30A ends the processing before the vehicle V arrives at the stop 50.

[0077] Also, if, in step S106, it is determined that the road surface height at the planned boarding position is not a height at which slope 18 can be installed, the CPU 30A determines that slope 18 cannot be installed at the planned boarding position, and executes the processing after step S110.

[0078] Furthermore, if it is determined in step S108 that there is an obstacle in the door deployment planned area, the CPU 30A determines in step S118 whether a pair of slide doors 14 can be opened by the width that the user P can board.

[0079] If it is determined in step S118 that a pair of slide doors 14 cannot be opened by the width that the user P can board, the CPU 30A executes the processes after step S110.

[0080] On the other hand, if it is determined in step S118 that a pair of slide doors 14 can be opened by the width that the user P can board, the CPU 30A notifies the user P in step S120 that the boarding opening will become narrow.

[0081] Subsequently, in step S122, the CPU 30A inquires whether the user P wishes to move in view of the fact that the boarding opening will become narrow. As a result, the user P can determine the suitability of the current waiting location based on the opening amount of the door before the vehicle arrives.

[0082] Then, in step S124, the CPU 30A determines whether the user P has pressed a button indicating the wish to move on the terminal 60, that is, whether movement wish information has been received.

[0083] If it is determined in step S124 that movement wish information has been received did not exist the CPU 30A changes the door opening amount of the control program 110 in step S126 and ends the process before the vehicle V arrives at the stop 50. The door opening amount is set as the maximum opening amount for each of the pair of slide doors 14 within the range where they do not interfere with the obstacle. As a result, it is possible to avoid a situation where the pair of slide doors 14 interfere with the obstacle after the vehicle V arrives at the stop 50. Note that when it is determined in step S124 that movement request information has been received, the CPU 30A calculates a recommended movement area in step S114. Then, the CPU 30A notifies the user P of the recommended movement area calculated in step S114 in step S116, and executes the processing from step S100 and later again.

[0084] FIG. 5 shows the flow of processes performed in the on-vehicle device 10 after the vehicle V arrives at the stop 50. In step S200, the CPU 30A adjusts the vehicle height according to the road surface height so that the slope 18 can be installed at the planned boarding position. Subsequently, in step S202, the CPU 30A opens the pair of sliding doors 14. Further, in step S204, the CPU 30A deploys the slope 18 and ends the process. Note that the processes after the vehicle V arrives at the stop 50 are not limited to the above, and for example, vehicle height adjustment and door deployment may be performed simultaneously.

[0085] According to the on-vehicle device 10 according to the present embodiment, before the vehicle V arrives at the stop 50, it is determined whether the slope 18 can be installed and whether the sliding door 14 can be deployed. Therefore, compared with the case where it is determined whether the slope 18 can be installed and whether the sliding door 14 can be deployed after the vehicle V arrives at the stop 50, it is possible to early determine whether the user P can smoothly board at the planned boarding position where the user P waits.

[0086] Also, when the planned boarding position is not appropriate, the proposal unit proposes to the user P to change the planned boarding position. As a result, the user P can know that it is not possible to smoothly board while staying at the current planned boarding position, and can move to a new planned boarding position before the arrival of the vehicle V or immediately after the arrival of the vehicle V.

[0087] Furthermore, according to the on-vehicle device 10 according to the present embodiment, since road surface information is acquired from both the camera 56 at the stop 50 and the terminal 60 held by the user P, more accurate road surface information can be acquired. Also, when the user does not have a terminal and waits for the vehicle V at the stop 50, road surface information can be acquired from the camera 56 at the stop 50. On the other hand, even when the user P designates a planned boarding area without a detection device, road surface information can be acquired from the terminal 60 of the user P.

[0088] Furthermore, according to the in-vehicle device 10 according to the present embodiment, the movement recommended area calculated by the calculation unit 208 is notified by the notification unit 210. Therefore, the user P can know the position where boarding can be smoothly performed before the vehicle V arrives.

[0089] 〔Supplementary Explanation of the Above Embodiment〕 In the above embodiment, the vehicle information management device has been described as the in-vehicle device 10 mounted on the vehicle V. However, it is not limited to this, and it may be a server provided outside the vehicle. In this case, the server, the in-vehicle device, the detection device for the boarding planned area, and the user's terminal are connected by a network. The vehicle may be controlled by a signal sent from the server to the in-vehicle device.

[0090] Also, in the above embodiment, the guard pipe 54 has been cited as an example of an obstacle, but it is not limited to this. For example, other objects such as pillars provided at bus stops, curbstones, trees, stones, etc. may be used. Also, it is not limited to objects, and animals or people other than users may be used.

[0091] Furthermore, in the above embodiment, the road surface information acquisition unit 200 has been described as acquiring road surface information from the camera 56 provided on the signpost 52 of the bus stop 50 and the terminal 60 of the user P. However, it is not limited to this. For example, road surface information may be acquired from only one of the detection device for the boarding planned area and the user's terminal. Also, the detection device is not limited to bus stops and may be provided, for example, on utility poles near the boarding planned area.

[0092] Furthermore, in the above embodiment, the road surface information acquisition unit 200 has been described as acquiring road surface information after receiving the user P's boarding request. However, it is not limited to this. For example, a road surface bus that stops at a plurality of bus stops may acquire road surface information from the detection device of each bus stop before arriving at each bus stop. In this case, for example, from the detection device of the bus stop, it may also be detected whether a wheelchair user is waiting, and when there is a wheelchair user, it may be determined whether a slope can be installed and whether the door can be deployed for the boarding planned position where the user is waiting.

[0093] Also, in the above embodiment, the determination unit 204 has been described as determining the presence or absence of obstacles that become obstacles during slope deployment and door deployment. However, the present invention is not limited to this, and the determination unit may not determine the presence or absence of obstacles.

[0094] Furthermore, in the above embodiment, the opening 12 of the vehicle V has been described as being opened and closed by a pair of sliding doors 14. However, the type of door is not limited to this, and for example, it may be a folding door or a hinged door.

Explanation of Reference Numerals

[0095] 10 In-vehicle device (vehicle information management device) 14 A pair of sliding doors (doors) 18 Slope 50 Bus stop (boarding planned area) 54 Guard pipe (obstacle) 56 Camera (detection device) 60 Terminal 200 Road surface information acquisition unit 204 Determination unit 206 Proposal unit 210 Notification unit 214 Control unit H Height difference between sidewalk and roadway (road surface height) P User V Vehicle

Claims

1. A road surface information acquisition unit that acquires road surface information of the planned boarding area before a vehicle arrives at the user's planned boarding area; A determination unit that determines, based on the road surface information acquired by the road surface information acquisition unit, whether the road surface height of the planned boarding position where the user waits in the planned boarding area is a height at which the slope of the vehicle can be installed; If the determination unit determines that the road surface height is not a height at which the slope can be installed, a proposal unit that proposes to the user to change the planned boarding position before the vehicle arrives at the user's planned boarding area; A vehicle information management device having the above.

2. The determination unit further determines, based on the road surface information, whether there is an obstacle that becomes an obstacle when installing the slope at the planned boarding position. If there is no obstacle and the road surface height is a height at which the slope can be installed, it is determined that the slope can be installed at the planned boarding position. If there is an obstacle or the road surface height is not a height at which the slope can be installed in at least one of the cases, it is determined that the slope cannot be installed at the planned boarding position. The vehicle information management device according to Claim 1.

3. The road surface information acquisition unit acquires the road surface information from a detection device provided in the planned boarding area. The vehicle information management device according to Claim 2.

4. The road surface information acquisition unit acquires the road surface information from a terminal possessed by the user. The vehicle information management device according to Claim 2.

5. A road surface information acquisition unit that acquires road surface information of the planned boarding area before a vehicle arrives at the user's planned boarding area; A determination unit that determines, based on the road surface information acquired by the road surface information acquisition unit, whether there is an obstacle that becomes an obstacle when the door of the vehicle opens at the planned boarding position where the user waits in the planned boarding area; If the determination unit determines that there is an obstacle, a notification unit that notifies the user that the boarding opening will be narrowed before the vehicle arrives at the user's planned boarding area; If the determination unit determines that there is an obstacle, a control unit that changes the opening amount of the door; A vehicle information management device having the above.

Images