Parking management device, vehicle, and parking management method
The parking management system addresses vehicle obstruction by enabling user-requested movement through manual or autonomous control, enhancing user convenience and safety in parking lots.
Patent Information
- Application Number
- JP2022065213
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-04-11
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2042-04-11
AI Technical Summary
Vehicles parked in a parking lot can obstruct users, creating inconvenience and a need for efficient management to move these vehicles.
A parking management system that includes infrastructure sensors, a communication device, and a server to identify and manage vehicles, allowing users to request movement via a mobile app, with options for manual or autonomous vehicle control.
Enables users to conveniently move obstructing vehicles, improving accessibility and safety by allowing vehicles to be relocated or driven autonomously to avoid obstacles.
Smart Images

Figure 0007586127000001 
Figure 0007586127000002 
Figure 0007586127000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a parking management device, a vehicle, and a parking management method. [Background technology]
[0002] 2. Description of the Related Art There is known technology for remotely controlling a parked vehicle (for example, see Patent Document 1). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2008-33438 A Summary of the Invention [Problem to be solved by the invention]
[0004] Vehicles parked in a parking lot may be a hindrance to users of the parking lot, and there is a demand to move vehicles that are in the way of users in this way. [Means for solving the problem]
[0005] A first aspect of the present disclosure is a parking management device that manages vehicles in a parking lot, comprising: a reception unit that receives a vehicle movement request transmitted from a user of the parking lot to move a parked vehicle; an identification unit that identifies a parked vehicle from among the vehicles in the parking lot based on the vehicle movement request; and a transmission unit that transmits to the parked vehicle a vehicle movement mode command that transitions the driving mode of the parked vehicle identified by the identification unit to a vehicle movement mode that causes the parked vehicle to perform a vehicle movement operation to move the parked vehicle.
[0006] A second aspect of the present disclosure is a parking management device described in the first aspect, wherein the reception unit receives a vehicle identification request including information identifying a parked vehicle as a vehicle movement request, and the identification unit identifies the parked vehicle based on the vehicle identification request.
[0007] A third aspect of the present disclosure is a parking management device described in the second aspect, wherein the identifying information includes a vehicle registration number of the parked vehicle or an identification code uniquely assigned to the parked vehicle.
[0008] A fourth aspect of the present disclosure is a parking management device described in any one of the first to third aspects, wherein a transmitter transmits a self-propelling command to a parked vehicle that has transitioned to a vehicle movement mode, and the parked vehicle self-propels in a predetermined direction as a vehicle movement operation in accordance with the self-propelling command received after transitioning to the vehicle movement mode.
[0009] A fifth aspect of the present disclosure is a parking management device described in the fourth aspect, wherein the reception unit further receives imaging data of the vehicle from an infrastructure sensor installed in the parking lot to image the vehicle in the parking lot, the parking management device further includes a self-driving route determination unit that determines a direction in which the parked vehicle will self-propel by a vehicle movement operation based on the imaging data, and the transmission unit generates a self-driving command to self-propel the parked vehicle in the direction determined by the self-driving route determination unit.
[0010] A sixth aspect of the present disclosure is a parking management device described in the fourth aspect, wherein the reception unit receives a self-propelled request to cause a parked vehicle to self-propel as a vehicle movement request, and the transmission unit generates a self-propelled command in response to the self-propelled request.
[0011] A seventh aspect of the present disclosure is a parking management device described in the sixth aspect, wherein the self-driving request includes information specifying a direction, and the transmitting unit generates a self-driving command to cause the vehicle to self-propel in the direction specified in the self-driving request.
[0012] An eighth aspect of the present disclosure is a parking management device described in any one of the first to third aspects, wherein a transmitter transmits a communication establishment command to the parked vehicle that has transitioned to a vehicle movement mode and a user's portable device to establish communication between the parked vehicle or the portable device, and after establishing communication with the portable device, the parked vehicle self-propels in a predetermined direction as a vehicle movement operation in accordance with the self-propelling command transmitted from the portable device.
[0013] A ninth aspect of the present disclosure is a vehicle that transitions to a vehicle movement mode in accordance with a vehicle movement mode command transmitted by a transmission unit of the parking management device described in any one of the first to eighth aspects, and performs a vehicle movement operation.
[0014] A tenth aspect of the present disclosure is the vehicle according to the ninth aspect, wherein the vehicle releases the actuation of the braking mechanism as a vehicle movement operation when the vehicle transitions to a vehicle movement mode.
[0015] An eleventh aspect of the present disclosure is a vehicle as described in the ninth or tenth aspect, wherein the vehicle is equipped with a sensor that detects a contact operation by a user to the vehicle, and after transitioning to a vehicle movement mode, the vehicle moves in a predetermined direction as a vehicle movement operation in response to the contact operation detected by the sensor.
[0016] A twelfth aspect of the present disclosure is a method for managing vehicles in a parking lot, wherein a processor accepts a vehicle movement request sent from a user of the parking lot to move a parked vehicle, identifies a parked vehicle from among the vehicles in the parking lot based on the vehicle movement request, and transmits a vehicle movement mode command to the parked vehicle to transition an operating mode of the identified parked vehicle to a vehicle movement mode that causes the parked vehicle to perform a vehicle movement operation to move the parked vehicle. Effect of the Invention
[0017] According to the present disclosure, if a vehicle parked in a parking lot is obstructing a user, the user can transmit a vehicle movement request to the parking management device to cause the vehicle to execute a vehicle movement operation, thereby moving the vehicle, thereby improving the convenience of the user. [Brief description of the drawings]
[0018] [Figure 1] 1 illustrates a schematic diagram of a parking management system, a parking lot, and vehicles in the parking lot according to an embodiment; [Diagram 2] FIG. 2 is a block diagram of the parking management system shown in FIG. [Diagram 3] 1 is a flowchart illustrating a parking management method according to an embodiment. [Figure 4] 1 shows a block diagram of a vehicle according to an embodiment. [Diagram 5] 3 is a block diagram showing other functions of the parking management system shown in FIG. 2. [Figure 6] 13 is a flowchart showing a parking management method according to another embodiment. [Figure 7] 13 is a flowchart showing a parking management method according to still another embodiment. [Figure 8] 3 shows an example of a vehicle operation screen. [Figure 9] 13 is a flowchart showing a parking management method according to still another embodiment. [Figure 10] FIG. 13 shows a block diagram of a vehicle according to another embodiment. [Figure 11] 13 is a flowchart showing a parking management method according to still another embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0019] Hereinafter, an embodiment of the present disclosure will be described in detail with reference to the drawings. In the various embodiments described below, similar elements are given the same reference numerals, and duplicated explanations will be omitted. First, a parking management system 10 according to one embodiment will be described with reference to Figs. 1 and 2. The parking management system 10 is a system for managing vehicles 110 parked in a parking lot 100.
[0020] The parking management system 10 includes multiple infrastructure sensors 12, a communication device 14, and a parking management server 16. Each of the infrastructure sensors 12 has a camera, a laser scanner, or the like, and is provided in the parking lot 100 so as to capture an image of a vehicle 110 in the parking lot 100. The multiple infrastructure sensors 12 are installed at multiple locations in the parking lot 100 so as to capture an image of a vehicle 110 parked in any parking space defined in the parking lot 100. The infrastructure sensors 12 capture images of the vehicles 110 in the parking lot 100, and provide the image data IM of the vehicles 110 to the parking management server 16.
[0021] The communication device 14 is capable of data communication with external communication devices including the vehicles 110 in the parking lot 100. Specifically, the communication device 14 wirelessly transmits and receives data to and from external communication devices such as the vehicles 110 in the parking lot 100 using a mobile communication network system such as 4G or 5G. Note that multiple communication devices 14 may be provided in the parking lot 100 so as to be able to communicate with vehicles 110 parked in any parking space in the parking lot 100. Furthermore, the communication device 14 may communicate with external communication devices using any communication protocol.
[0022] The parking management server 16 controls the operations of the infrastructure sensors 12 and the communication device 14. Specifically, the parking management server 16 is a computer having a processor 18, a memory 20, and an I / O interface 22, as shown in Fig. 2. The processor 18 has a CPU or a GPU, etc., and is communicatively connected to the memory 20 and the I / O interface 22 via a bus 24. The processor 18 performs calculations to realize a vehicle management function, which will be described later.
[0023] The memory 20 has a RAM or a ROM, etc., and temporarily or permanently stores various data used in the arithmetic processing executed by the processor 18 and various data generated during the arithmetic processing. The I / O interface 22 has, for example, an Ethernet (registered trademark) port, a USB port, or an HDMI (registered trademark) terminal, and communicates data with external devices such as the infrastructure sensor 12 and the communication device 14 in a wired or wireless manner.
[0024] Here, a vehicle 110 parked in the parking lot 100 may be an obstacle to a user A of the parking lot 100 when walking or carrying luggage. There is a request to move the vehicle 110 that is in the way of the user A. In this embodiment, the processor 18 manages the vehicles 110 in the parking lot 100 so as to move the parked vehicle 110 in response to a request from the user A.
[0025] A parking management method according to one embodiment will be described below with reference to Fig. 3. In this embodiment, the owner B of each vehicle 110 parked in the parking lot 100 registers himself / herself as a user of the parking lot 100 in advance in order to use the parking lot 100. For example, the owner B operates the human-machine interface (HMI) of the vehicle 110 to access the parking management server 16 through the on-board communication device of the vehicle 110, downloads an application α for registering the user of the parking lot 100 from the parking management server 16, and installs it in the electronic control unit (ECU) of the vehicle 110.
[0026] Then, owner B operates the HMI to launch app α, and enters owner B's personal information PI (name, address, telephone number, etc.) and specific information SI that identifies vehicle 110 through the user registration screen SC1 displayed on the display of the HMI of vehicle 110, and uploads this to the parking management server 16 via the vehicle 110's on-board communication device.
[0027] The specific information SI includes, for example, the vehicle registration number SI1 of the vehicle 110, or an identification code SI2 that is uniquely assigned to each vehicle 110. The vehicle registration number SI1 may be printed on license plates attached to the front and rear of the vehicle 110. On the other hand, the identification code SI2 includes a barcode, a QR code (registered trademark), or the like, and may be, for example, attached as a label sticker to the exterior (windshield, rear windshield, side windows, body, etc.) of the vehicle 110, or may be directly painted on the exterior.
[0028] The processor 18 of the parking management server 16 obtains the personal information PI and specific information SI received from the on-board communication device of the vehicle 110 through the communication device 14, and also acquires the communication address AR (e.g., IP address) assigned to the on-board communication device of the vehicle 110. The processor 18 then creates a database DB in which the obtained personal information PI, specific information SI, and address AR are stored in association with one another, and stores the information in advance in the memory 20. In this way, the specific information SI and addresses AR of multiple vehicles 110 are stored in the database DB before the parking lot 100 is used.
[0029] Here, let us assume that, among the vehicles 110 in the parking lot 100, one parked vehicle 110A (FIGS. 1 and 2) is in the way of user A. Hereinafter, the configuration of vehicle 110A will be described with reference to FIG. 4. Vehicle 110A is, for example, a four-wheeled automobile, and includes a vehicle body 112, a drive mechanism 114, a steering mechanism 116, a braking mechanism 118, an in-vehicle communication device 120, and an electronic control unit (ECU) 122, etc. Vehicle body 112 has exterior 112A including a windshield, rear windshield, side windows, a body, etc., and interior 112B including a seat, a meter panel, a room mirror, etc.
[0030] The drive mechanism 114 has an engine or an electric motor, and generates a drive force for running the vehicle 110A by driving and rotating the wheels 124 rotatably provided on the vehicle body 112. The steering mechanism 116 has a power steering device, and automatically changes the running direction of the vehicle 110A. The braking mechanism 118 has an electric brake device, and automatically brakes the vehicle 110A by applying a braking force to the wheels 124.
[0031] The ECU 122 controls the operation of the vehicle 110A. Specifically, the ECU 122 is a computer having a processor 126, a memory 128, and an I / O interface 130. The processor 126 has a CPU, a GPU, or the like, and is communicatively connected to the memory 128 and the I / O interface 130 via a bus 132.
[0032] The memory 128 has a RAM, a ROM, or the like, and temporarily or permanently stores various data used in the arithmetic processing executed by the processor 126 and various data generated during the arithmetic processing. The I / O interface 130 has, for example, a controller area network (CAN) port, an Ethernet (registered trademark) port, a USB port, an optical fiber connector, or an HDMI (registered trademark) terminal, and communicates data with in-vehicle components such as the drive mechanism 114, the steering mechanism 116, the braking mechanism 118, and the in-vehicle communication device 120 in a wired or wireless manner.
[0033] The in-vehicle communication device 120 can communicate with an external communication device such as the communication device 14 of the parking management system 10. The in-vehicle communication device 120 has, for example, a GPS receiver 120A, an inter-vehicle communication device 120B, and a data communication module (DCM) 120C. The GPS receiver 120A receives GPS signals from GPS satellites. The inter-vehicle communication device 120B can transmit and receive data to and from an in-vehicle communication device of another vehicle.
[0034] The DCM 120C can transmit and receive data to and from an external communication device of the vehicle 110A (for example, the above-mentioned communication device 14, the portable device 102 described below, a communication device provided in a management server of an automobile company, a communication base station, etc.) using a mobile communication network system such as 4G or 5G. Note that a vehicle 110 other than the vehicle 110A also has a similar configuration to the vehicle 110A.
[0035] Referring again to Figures 1 to 3, user A operates his / her portable device 102 (such as a smartphone or a tablet terminal device) to send a vehicle movement request RQ to the parking management server 16 to move the vehicle 110A that is in the way (step S1 in Figure 3).
[0036] Here, before transmitting the vehicle movement request RQ, user A operates portable device 102 to access parking management server 16, downloads the above-mentioned application α from parking management server 16, and pre-installs it on portable device 102. User A operates portable device 102 to start application α, and enters personal information PI of user A through a user registration screen SC1 displayed on the display of portable device 102. A and uploading it from the portable device 102 to the parking management server 16.
[0037] The processor 18 of the parking management server 16 transmits the personal information PI of the user A through the communication device 14. A and the communication address AR assigned to the portable device 102. A (e.g., IP address). The processor 18 obtains personal information PI A and address AR A These are stored in the database DB in association with each other. After such user registration, the user A becomes able to transmit a vehicle movement request RQ through the movement request input screen SC2 that is displayed when the application α is started on the portable device 102.
[0038] In this embodiment, in step S1, the user A inputs, as a vehicle movement request RQ, identification information SI 110A (Vehicle 110A, vehicle registration number SI1 110A , or an identification code SI2 uniquely assigned to the vehicle 110A 110A ) to the parking management server 16.
[0039] As an example, the user A operates the portable device 102 according to the guide information displayed on the travel request input screen SC2 of the application α, and captures the vehicle registration number SI1 of the vehicle 110A by the camera provided on the portable device 102. 110A The portable device 102 captures the vehicle registration number SI1 from the image captured by the camera. 110A and in response to the operation of user A, the vehicle registration number SI1 110AThe vehicle identification request RQ1 with the above information attached thereto is transmitted to the parking management server 16 as a vehicle movement request RQ.
[0040] As another example, the user A may operate the portable device 102 to capture the identification code SI2 assigned to the vehicle 110A by a camera installed in the portable device 102. 110A and the identification code SI2 110A Then, the portable device 102 reads the identification code SI2 in response to the operation of the user A. 110A The portable device 102 then transmits the vehicle identification request RQ1, to the parking management server 16, together with the identification information SI 110A (Vehicle registration number SI1 110A , or identification code SI2 110A ) to the parking management server 16.
[0041] The processor 18 of the parking management server 16 accepts the vehicle movement request RQ transmitted from user A (step S2). Specifically, the communication device 14 receives a vehicle identification request RQ1 from the portable device 102 of user A as the vehicle movement request RQ. The processor 18 of the parking management server 16 accepts the vehicle identification request RQ1 through the communication device 14. In this manner, the processor 18 functions as a reception unit 26 (FIG. 2) that accepts the vehicle movement request RQ (specifically, the vehicle identification request RQ1).
[0042] Next, the processor 18 identifies the vehicle 110A from among the vehicles 110 in the parking lot 100 based on the vehicle movement request RQ received by the reception unit 26 (step S3). Specifically, the processor 18 uses the identification information SI 110A (i.e. vehicle registration number SI1 110A , or identification code SI2 110A ) is collated with the identification information SI stored in the database DB, thereby identifying the vehicle 110A stored in the database DB.
[0043] Then, the processor 18 calculates the address AR 110A from the database DB. In this manner, in this embodiment, the processor 18 functions as an identification unit 28 (FIG. 2) that identifies the vehicle 110A from among the vehicles 110 in the parking lot 100 based on the vehicle movement request RQ (specifically, the vehicle identification request RQ1).
[0044] Next, the processor 18 transmits a vehicle movement mode command C1 to the vehicle 110A identified in step S3 (step S4). This vehicle movement mode command C1 is a command for transitioning the driving mode DM of the vehicle 110A identified in step S3 to a vehicle movement mode DM1. The vehicle movement mode DM1 is a driving mode DM for causing the vehicle 110A to execute a vehicle movement operation MO for moving the vehicle 110A from the current parking position P0.
[0045] The processor 18 receives the address AR 120 assigned to the in-vehicle communication device 120 of the vehicle 110A, which was acquired in step S3. 110A , and operates the communication device 14 of the parking management system 10 to transmit the vehicle movement mode command C1 to the in-vehicle communication device 120 of the vehicle 110A. Thus, in this embodiment, the processor 18 functions as the transmission unit 30 (FIG. 2) that transmits the vehicle movement mode command C1 to the vehicle 110A.
[0046] The processor 126 of the vehicle 110A transitions the driving mode DM of the vehicle 110A to a vehicle movement mode DM1 (step S5) in accordance with the vehicle movement mode command C1 received through the in-vehicle communication device 120. After transitioning to the vehicle movement mode DM1, the processor 126 executes a vehicle movement operation MO to move the vehicle 110A from the current parking position P0 (step S6).
[0047] As an example of the vehicle movement operation MO, when the vehicle transitions to the vehicle movement mode DM1, the processor 126 releases the operation of the braking mechanism 118. Specifically, the processor 126 sends a command to the electric brake device of the braking mechanism 118 to release the braking force applied by the electric brake device to the wheels 124 (i.e., release the brakes).
[0048] In this way, the operation of the brake mechanism 118 is released, and the vehicle 110A becomes movable. As a result, the user A can move the vehicle 110A to a parking position P1 that does not get in the way of the user A, for example, by pushing the vehicle 110A with his / her hand. Other examples of the vehicle movement operation MO will be described later.
[0049] As described above, in this embodiment, the processor 18 functions as the reception unit 26, the identification unit 28, and the transmission unit 30, thereby managing the vehicle 110 in the parking lot 100 so as to move the parked vehicle 110A in response to a vehicle movement request RQ from the user A. Therefore, the reception unit 26, the identification unit 28, and the transmission unit 30 constitute a parking management device 40 (FIG. 2) that manages the vehicle 110 in the parking lot 100.
[0050] In this parking management device 40, the reception unit 26 receives a vehicle movement request RQ sent from user A to move a parked vehicle 110A (step S2), and the identification unit 28 identifies vehicle 110A from among the vehicles 110 in the parking lot 100 based on the vehicle movement request RQ (specifically, vehicle identification request RQ1) (step S3).
[0051] Then, the transmitting unit 30 transmits to the vehicle 110A a vehicle movement mode command C1 that transitions the driving mode DM of the vehicle 110A identified by the identification unit 28 to a vehicle movement mode DM1 that causes the vehicle 110A to perform a vehicle movement operation MO (e.g., a brake release operation) to move the vehicle 110A (step S4).
[0052] According to this configuration, if the vehicle 110A is in the way of the user A, the user A can transmit a vehicle movement request RQ to the parking management device 40 to cause the vehicle 110A to execute a vehicle movement operation MO (e.g., release the brakes), thereby moving the vehicle 110A. This can improve the convenience of the user A.
[0053] In the parking management device 40, the reception unit 26 receives, as the vehicle movement request RQ, the identification information SI 110A The identification unit 28 receives the vehicle identification request RQ1 including the identification information SI and identifies the vehicle 110A based on the vehicle identification request RQ1. 110A The vehicle registration number of the parked vehicle 110A is SI1 110A , or an identification code SI2 uniquely assigned to the parked vehicle 110A. 110A Includes.
[0054] According to this configuration, the identification unit 28 can quickly and accurately identify the vehicle 110A that is requested to be moved by the user A. The vehicle movement request RQ is a vehicle identification request RQ1 (i.e., the vehicle registration number SI1 110A , identification code SI2 110A ) may include any information that can identify the parked vehicle 110A (for example, the parking space number in which the vehicle 110A is parked).
[0055] In the above-mentioned example of step S1, the user A captures the vehicle registration number SI1 of the vehicle 110A by the camera of the portable device 102. 110A and capture specific information SI 110A Vehicle registration number SI1 110A The vehicle identification request RQ1 with the attached image data IM' may be transmitted to the parking management server 16. Then, in step S3, the processor 18 of the parking management server 16 performs image analysis on the image data IM' attached to the vehicle identification request RQ1 to obtain the identification information SI 110A Vehicle registration number SI1 110A may be read from the imaging data IM'.
[0056] Next, a parking management method according to another embodiment will be described with reference to Fig. 5 and Fig. 6. The parking management system 10 shown in Fig. 5 executes the flow of the parking management method shown in Fig. 6. Note that, among the flow shown in Fig. 6, the same process as the flow shown in Fig. 3 is given the same step number, and duplicated explanations will be omitted.
[0057] In the flow of Figure 6, when the vehicle transitions to vehicle movement mode DM1 in step S5, the processor 126 of the vehicle 110A becomes capable of accepting self-propelled commands C2, C4, and C6 described below, and transmits a mode transition signal G1 indicating a transition to the vehicle movement mode DM1 to the parking management server 16.
[0058] When the mode transition signal G1 is received from the vehicle 110A through the communication device 14, the processor 18 of the parking management server 16 operates at least one infrastructure sensor 12 to capture an image of the vehicle 110A. For example, the infrastructure sensor 12 continuously captures images of each vehicle 110 (including the vehicle 110A) that enters the parking lot 100, and the processor 18 collects image data IM of the vehicle 110 captured by the infrastructure sensor 12.
[0059] Then, based on the collected imaging data IM, the processor 18 acquires the vehicle registration number SI1 of the entered vehicle 110 and identifies which parking frame (or location within the parking lot 100) the vehicle 110 has parked in. The processor 18 operates at least one infrastructure sensor 12 that has within its field of view the parking frame (or parking location) in which the vehicle 110A identified in step S3 is parked, and functions as the reception unit 26 to receive the imaging data IM of the vehicle 110A. 110A from the at least one infrastructure sensor 12 (step S7).
[0060] Then, the processor 18 outputs the acquired imaging data IM 110A Based on the image data IM, the processor 18 determines a self-propelling direction DR in which the vehicle 110A is self-propelled by the vehicle movement operation MO (step S8).110A Based on this, the presence of environmental objects (for example, other vehicles 110, user A, buildings such as walls) present around the vehicle 110A is recognized.
[0061] Then, the processor 18 determines a self-driving direction DR in which the vehicle 110A does not come into contact with the surrounding environment, and thereby determines a self-driving route RT defined by the self-driving direction DR. 110A Based on this, the vehicle 110A functions as a self-driving route determination unit 42 (FIG. 5) that determines the self-driving direction DR (or the self-driving route RT) in which the vehicle 110A is self-driving in the vehicle movement operation MO.
[0062] Then, the processor 18 generates a self-propelling command C2 for self-propelling the vehicle 110A based on the determined self-propelling direction DR (i.e., the self-propelling route RT). This self-propelling command C2 is a command for self-propelling the vehicle 110A in the self-propelling direction DR along the self-propelling route RT as a vehicle movement operation MO, and includes control signals for automatically controlling the drive mechanism 114, steering mechanism 116, and braking mechanism 118 of the vehicle 110A, and the like.
[0063] Then, the processor 18 functions as the transmitter 30 and operates the communication device 14 to transmit the generated self-travel command C2 to the vehicle 110A that has transitioned to the vehicle movement mode DM1 (step S9). 110A and transmits a self-propelling command C2 to the vehicle 110A via the communication device 14.
[0064] The processor 126 of the vehicle 110A receives the self-propelling command C2 through the in-vehicle communication device 120. Then, the processor 126 automatically controls the drive mechanism 114, the steering mechanism 116, and the braking mechanism 118 in accordance with the received self-propelling command C2, and after releasing the operation of the braking mechanism 118 as a vehicle movement operation MO, causes the vehicle 110A to self-propel in the self-propelling direction DR determined in step S8 (step S10). As a result, the vehicle 110A automatically moves from the original parking position P0 to the new parking position P1 along the self-propelling route RT without coming into contact with surrounding environmental objects.
[0065] The vehicle 110A may further include a sensor such as an exterior camera or a radar (e.g., LiDAR) that monitors the surroundings of the vehicle 110A, and the processor 126 of the vehicle 110A may recognize an environmental object around the vehicle 110A based on detection data of the sensor during execution of step S10. Then, the processor 126 may correct the self-driving direction DR (or the self-driving route RT) in the vehicle movement operation MO so as to avoid contact with the environmental object recognized from the detection data, or may operate the braking mechanism 118 to bring the vehicle 110A to an emergency stop.
[0066] Upon completing the vehicle movement operation MO in step S10, the processor 126 functions as the transmission unit 30 and transmits a self-propelling end signal G2 to the parking management server 16. Upon receiving the self-propelling end signal G2 through the communication device 14, the processor 18 of the parking management server 16 functions as the transmission unit 30 and generates a self-propelling command C3 for returning the vehicle 110A to the original parking position P0, and transmits the command from the communication device 14 to the vehicle 110A (step S11).
[0067] As an example, the processor 18 transmits the self-propelling command C3 to the vehicle 110A when a predetermined time t1 has elapsed since the time t0 when the self-propelling end signal G2 was received (or the time when the self-propelling command C2 was transmitted in step S9). More specifically, the processor 18 transmits a command to a timer (not shown) built into the parking management server 16 at the time t0 to start timing the elapsed time t from the time t0. Then, the processor 18 transmits the self-propelling command C3 to the vehicle 110A when the elapsed time t reaches t=t1.
[0068] This predetermined time t1 may be stored in advance in the memory 20. Alternatively, the user A may arbitrarily set the predetermined time t1. In this case, the user A may input the predetermined time t1 by operating the portable device 102 (for example, by using the application α) in the above-mentioned step S1, and attach the information of the time t1 to the vehicle movement request RQ. The processor 18 of the parking management server 16 acquires the information of the predetermined time t1 together with the vehicle movement request RQ in the above-mentioned step S2.
[0069] As another example, the processor 18 may receive image data IM captured by the infrastructure sensor 12. 110A Specifically, after time t0, the processor 18 causes the infrastructure sensor 12 to continuously capture an image of the parking frame (or the parking location) from which the vehicle 110A is to move, and acquires the image data IM 110A Based on the above, the processor 18 determines whether or not there is an environmental object (e.g., user A) in the parking frame of the movement origin. Then, when it is determined that there is no environmental object in the parking frame of the movement origin, the processor 18 transmits a self-travel command C3 to the vehicle 110A.
[0070] The processor 126 of the vehicle 110A drives the vehicle 110A to the original parking position P0 as a vehicle movement operation MO in accordance with the self-travel command C3 received through the in-vehicle communication device 120 (step S12). As an example, the processor 126 stores in the memory 128 the self-travel route RT (i.e., the self-travel direction DR) along which the vehicle 110A drives itself from the parking position P0 to the parking position P1 in the vehicle movement operation MO of the above-mentioned step S10, and history data on the control amounts (e.g., the rotation speed of the engine or electric motor, the steering angle of the steering wheel, and the timing of brake release and activation) that actuate the drive mechanism 114, the steering mechanism 116, and the braking mechanism 118 for the self-travel.
[0071] Then, in step S12, the processor 126 automatically controls the drive mechanism 114, the steering mechanism 116, and the braking mechanism 118 to cause the vehicle 110A to self-propel along a route opposite to the self-propelled route RT in the vehicle movement operation MO in step S10. Thus, in step S12, the processor 126 can cause the vehicle 110A to self-propel back to the original parking position P0 as the vehicle movement operation MO.
[0072] As another example, the self-propelling command C3 transmitted from the parking management server 16 to the vehicle 110A may include control signals for the drive mechanism 114, the steering mechanism 116, and the braking mechanism 118. In this case, in step S12, the processor 126 of the vehicle 110A automatically controls the drive mechanism 114, the steering mechanism 116, and the braking mechanism 118 in accordance with the control signals included in the self-propelling command C3, and causes the vehicle 110A to self-propel from the parking position P1 to the original parking position P0.
[0073] As described above, in this embodiment, the processor 18 of the parking management server 16 functions as the reception unit 26, the identification unit 28, the transmission unit 30, and the self-driving route determination unit 42 to manage the vehicles 110 in the parking lot 100. Therefore, the reception unit 26, the identification unit 28, the transmission unit 30, and the self-driving route determination unit 42 constitute a parking management device 50 (FIG. 5) that manages the vehicles 110 in the parking lot 100.
[0074] In this parking management device 50, the transmitter 30 transmits a self-traveling command C2 to the vehicle 110A that has transitioned to the vehicle movement mode DM1 (step S9), and the vehicle 110A travels in a predetermined self-traveling direction DR as a vehicle movement operation MO according to the self-traveling command C2 received after transitioning to the vehicle movement mode DM1 (step S10). With this configuration, the user A can automatically move the vehicle 110A by transmitting a vehicle movement request RQ. Therefore, the vehicle 110A that is in the way of the user A can be moved more easily, further improving the convenience of the user A.
[0075] In the parking management device 50, the reception unit 26 receives the image data IM of the vehicle 110A from the infrastructure sensor 12. 110A (step S7), the self-driving route determination unit 42 receives the image data IM 110A Based on this, the self-driving direction DR (or the self-driving route RT) in which the vehicle 110A is self-driving in the vehicle movement operation MO is determined (step S8).
[0076] Then, the transmitting unit 30 generates a self-propelling command C2 for causing the vehicle 110A to self-propel in the self-propelling direction DR determined by the self-propelling route determining unit 42 (step S9). According to this configuration, the self-propelling direction DR (self-propelling route RT) in which the vehicle 110A does not come into contact with environmental objects is transmitted to the image data IM 110A Since the vehicle movement operation MO in step S10 can be performed automatically based on the above, the vehicle 110A can be safely self-propelled.
[0077] Next, a parking management method according to still another embodiment will be described with reference to Fig. 2 and Fig. 7. The parking management system 10 shown in Fig. 2 further executes the flow of the parking management method shown in Fig. 7. Note that, among the processes in the flow shown in Fig. 7, the same step numbers are assigned to processes similar to those in the flow shown in Fig. 6, and duplicated explanations will be omitted.
[0078] 7, when the processor 126 of the vehicle 110A transitions to the vehicle movement mode DM1 in step S5, it transmits a mode transition signal G1 to the parking management server 16. Upon receiving the mode transition signal G1, the processor 18 of the parking management server 16 transmits the address AR A and transmits a mode transition signal G1' to the portable device 102 through the communication device 14.
[0079] When the mode transition signal G1' is received, the portable device 102 displays a vehicle operation screen SC3 of the application α on the display of the portable device 102. This vehicle operation screen SC3 is a graphical user interface (GUI) for remotely operating the vehicle 110A so as to make the vehicle 110A run by itself. An example of the vehicle operation screen SC3 is shown in FIG. 8. Note that any GUI other than the example shown in FIG. 8 may be used as the vehicle operation screen SC3.
[0080] 8, the vehicle operation screen SC3 includes an image of the vehicle 110A, and arrow button images BT1, BT2, BT3, and BT4 for specifying the self-driving direction DR in which the vehicle 110A drives itself. The arrow button images BT1, BT2, BT3, and BT4 are for specifying the self-driving direction DR of the vehicle 110A to be forward, backward, rightward, and leftward, respectively.
[0081] While viewing the vehicle operation screen SC3 displayed on the display of the portable device 102, user A can touch the arrow button image BT1, BT2, BT3 or BT4 on the display to specify the self-propelled direction DR of the vehicle 110A and remotely control the vehicle 110A to self-propel.
[0082] Hereinafter, a case where user A touches the arrow button image BT1 on the portable device 102 (i.e., an operation to specify the self-driving direction DR forward) will be described. In response to the touch operation of the arrow button image BT1 by user A, the portable device 102 transmits a self-driving request RQ2 for self-driving the vehicle 110A as a vehicle movement request RQ to the parking management server 16 (step S13). The self-driving request RQ2 transmitted at this time includes information specifying the self-driving direction DR forward.
[0083] The processor 18 of the parking management server 16 functions as the reception unit 26 and receives a vehicle movement request RQ (specifically, a self-propelled request RQ2) from the portable device 102 through the communication device 14 (step S14). Then, the processor 18 functions as the transmission unit 30 in response to the received self-propelled request RQ2 and generates a self-propelled command C4 for propelling the vehicle 110A in the self-propelled direction DR (forward in this example) specified in the self-propelled request RQ2.
[0084] This self-propelled command C4 is a command for causing the vehicle 110A to self-propel in the self-propelled direction DR (forward) as a vehicle movement operation MO, and includes control signals for automatically controlling the drive mechanism 114, steering mechanism 116, and braking mechanism 118 of the vehicle 110A, etc. The processor 18 functions as the transmitting unit 30, and operates the communication device 14 to transmit the generated self-propelled command C4 to the vehicle 110A (step S15).
[0085] The processor 126 of the vehicle 110A automatically controls the drive mechanism 114, the steering mechanism 116, and the braking mechanism 118 in accordance with the self-propelling command C4 received by the in-vehicle communication device 120, and after releasing the operation of the braking mechanism 118 as a vehicle movement operation MO, causes the vehicle 110A to self-propel in the self-propelling direction DR (forward) specified by the user A (step S16). Thereafter, when the vehicle 110A has self-propelled to the desired parking position P1, the user A ends the touch operation of the arrow button image BT1 displayed on the portable device 102, thereby ending the transmission of the self-propelling request RQ2.
[0086] The portable device 102 judges whether the transmission of the vehicle movement request RQ (specifically, the self-driving request RQ2) has ended (step S17). For example, in this step S17, the portable device 102 judges as YES if a touch operation on the arrow button image BT1 is not detected for a predetermined period of time, and judges as NO while the touch operation continues, and returns to step S13. Note that the portable device 102 may further display a self-driving end button image on the above-mentioned vehicle operation screen SC3, and may judge as YES in this step S17 when the user A touches the self-driving end button image with the portable device 102.
[0087] If the determination in step S17 is YES, the portable device 102 transmits a self-propelling end signal G2 to the parking management server 16. When the processor 18 of the parking management server 16 receives the self-propelling end signal G2 through the communication device 14, it executes the above-mentioned step S11 and transmits a self-propelling command C3 to the vehicle 110A. Then, the processor 126 of the vehicle 110A executes the above-mentioned step S12 in accordance with the self-propelling command C3, and causes the vehicle 110A to self-propel to the original parking position P0 as a vehicle movement operation MO.
[0088] As described above, in this embodiment, the processor 18 of the parking management server 16 functions as the parking management device 40 (specifically, the reception unit 26, the identification unit 28, and the transmission unit 30) to manage the vehicle 110 in the parking lot 100. In the parking management device 40 according to this embodiment, the reception unit 26 receives a self-propelling request RQ2 for self-propelling the vehicle 110A as a vehicle movement request RQ, and the transmission unit 30 generates a self-propelling command C4 in response to the self-propelling request RQ2 (step S15). With this configuration, the user A can remotely control the vehicle 110A by operating the portable device 102, and automatically move the vehicle 110A.
[0089] In the parking management device 40 according to the present embodiment, the self-traveling request RQ2 includes information specifying the self-traveling direction DR, and the transmitting unit 30 generates a self-traveling command C4 for causing the vehicle 110A to travel in the self-traveling direction DR specified in the self-traveling request RQ2 (step S15). With this configuration, the user A can move the vehicle 110A to the desired parking position P1 by arbitrarily specifying the self-traveling direction DR of the vehicle 110A.
[0090] Next, a parking management method according to still another embodiment will be described with reference to Fig. 2 and Fig. 9. The parking management system 10 shown in Fig. 2 further executes the flow of the parking management method shown in Fig. 9. Note that, among the processes in the flow shown in Fig. 9, the same step numbers are assigned to processes similar to those in the flow shown in Fig. 7, and duplicated explanations will be omitted.
[0091] 9, when the processor 18 of the parking management server 16 receives the mode transition signal G1 transmitted from the vehicle 110A after step S5, the processor 18 functions as the transmitter 30 and transmits a communication establishment command C5 to the portable device 102 through the communication device 14 (step S18). This communication establishment command C5 is a command for establishing communication between the vehicle 110A that has transitioned to the vehicle movement mode DM1 and the portable device 102, and for example, the address AR of the vehicle 110A is transmitted to the portable device 102 via the communication device 14. 110A Includes information such as:
[0092] When the portable device 102 receives the communication establishment command C5 from the parking management server 16, the portable device 102 reads the address AR 110A and transmits a communication establishment request CQ1 to the vehicle 110A that has transitioned to the vehicle movement mode DM1. Meanwhile, the processor 126 of the vehicle 110A replies to the portable device 102 with a communication establishment response CQ2 in response to the communication establishment request CQ1 received through the in-vehicle communication device 120. In this manner, communication is established between the vehicle 110A and the portable device 102. Note that the vehicle 110A and the portable device 102 may establish communication between them using any method other than the communication of the communication establishment request CQ1 and the communication establishment response CQ2.
[0093] When communication with vehicle 110A is established (i.e., when communication establishment response CQ2 is received from vehicle 110A), portable device 102 displays, for example, a vehicle operation screen SC3 shown in Fig. 8 on the display of portable device 102. While viewing the vehicle operation screen SC3 displayed on portable device 102, user A touches arrow button images BT1, BT2, BT3, or BT4 on the display to specify the self-propelled direction DR of vehicle 110A and inputs a self-propelled command C6 for remotely controlling vehicle 110A to self-propel.
[0094] Hereinafter, a case where user A touches the arrow button image BT1 on the portable device 102 (i.e., an operation to specify the self-driving direction DR forward) will be described. In response to the touch operation of the arrow button image BT1 by user A, the portable device 102 transmits a self-driving command C6 for self-driving the vehicle 110A as a vehicle movement operation MO to the vehicle 110A (step S19). This self-driving command C6 is a command for self-driving the vehicle 110A in the self-driving direction DR (forward in this example), and includes control signals for automatically controlling the drive mechanism 114, steering mechanism 116, and braking mechanism 118 of the vehicle 110A, and the like.
[0095] The processor 126 of the vehicle 110A executes the above-mentioned step S16 in accordance with the self-propelled command C6 received by the in-vehicle communication device 120, and after releasing the operation of the braking mechanism 118 as a vehicle movement operation MO, causes the vehicle 110A to self-propel in the self-propelled direction DR (forward) specified by the user A.
[0096] Thereafter, when the vehicle 110A has driven to the desired parking position P1, the user A ends the touch operation of the arrow button image BT1 displayed on the portable device 102, thereby ending the transmission of the self-driving command C6. The portable device 102 determines whether the transmission of the self-driving command C6 has ended (step S20).
[0097] For example, in step S20, the portable device 102 determines YES if a touch operation on the arrow button image BT1 is not detected for a predetermined period of time, but determines NO while the touch operation continues, and returns to step S19. Note that the portable device 102 may further display a self-driving end button image on the above-mentioned vehicle operation screen SC3, and may determine YES in step S20 when the user A touches the self-driving end button image.
[0098] If the answer to step S20 is YES, the portable device 102 transmits a self-propelling end signal G2 to the parking management server 16. When the processor 18 of the parking management server 16 receives the self-propelling end signal G2 through the communication device 14, it executes the above-mentioned step S11 and transmits a self-propelling command C3 to the vehicle 110A. When the processor 126 of the vehicle 110A receives the self-propelling command C3 through the in-vehicle communication device 120, it executes the above-mentioned step S12 and causes the vehicle 110A to self-propel to the original parking position P0 as a vehicle movement operation MO.
[0099] As described above, in this embodiment, the processor 18 of the parking management server 16 functions as the parking management device 40 (specifically, the reception unit 26, the identification unit 28, and the transmission unit 30) to manage the vehicles 110 in the parking lot 100. In the parking management device 40 according to this embodiment, the transmission unit 30 transmits a communication establishment command C5 to the portable device 102 to establish communication between the vehicle 110A that has transitioned to the vehicle movement mode DM1 and the portable device 102 (step S18).
[0100] Then, the vehicle 110A self-propels in the self-propelling direction DR as a vehicle movement operation MO in accordance with the self-propelling command C6 transmitted from the portable device 102 after establishing communication with the portable device 102 (step S16). According to this configuration, the user A can remotely control the vehicle 110A by directly transmitting the self-propelling command C6 from the portable device 102 to the vehicle 110A, and move the vehicle 110A to the desired parking position P1.
[0101] In addition, the processor 18 of the parking management server 16 may transmit the communication establishment command C5 to the vehicle 110A in the above-mentioned step S18. In this case, the communication establishment command C5 is transmitted to the address AR A When the processor 126 of the vehicle 110A receives the communication establishment command C5, the processor 126 of the vehicle 110A reads the address AR A and transmits a communication establishment request CQ1 to the portable device 102 via the in-vehicle communication device 120. Meanwhile, the portable device 102 replies to the vehicle 110A with a communication establishment response CQ2 in response to the communication establishment request CQ1 received from the vehicle 110A. In this manner, communication between the vehicle 110A and the portable device 102 may be established.
[0102] Next, a parking management method according to still another embodiment will be described with reference to Fig. 2, Fig. 10, and Fig. 11. In this embodiment, the vehicle 110A further includes a sensor 134 as shown in Fig. 10. The sensor 134 detects a contact operation CO by the user A to the vehicle 110A.
[0103] As an example, the sensor 134 includes a force sensor capable of detecting an external force f applied to the vehicle 110A. In this case, the sensor 134 may be interposed between the wheel 124 (or the axle) of the vehicle 110A and the braking mechanism 118 (or the vehicle body 112) and configured to detect the torque f applied to the wheel 124 when the user A pushes the vehicle 110A by hand to move the vehicle 110A.
[0104] As another example, the sensor 134 has a touch sensor capable of detecting a contact c with the vehicle 110A by the user A. In this case, the sensor 134 is installed in the front part, rear part, or side part of the exterior 112A (e.g., the body) of the vehicle 110A, and detects a contact c with the exterior 112A by the hand of the user A.
[0105] A sign (such as a sticker or paint) indicating the installation position of the sensor 134 as a touch sensor may be provided on the exterior 112A so that the user A can visually recognize the installation position of the sensor 134. In this manner, the sensor 134 detects a touch operation CO on the vehicle 110A by detecting an external force f or a contact c, and supplies detection data δ indicating the detected touch operation CO to the processor 126.
[0106] The parking management system 10 shown in Fig. 2 further executes the flow of the parking management method shown in Fig. 11. In the flow shown in Fig. 11, the same processes as those in the flow shown in Fig. 6 are given the same step numbers, and duplicated explanations are omitted. In the flow shown in Fig. 11, when the processor 126 of the vehicle 110A transitions to the vehicle movement mode DM1 in step S5, it starts an operation of acquiring detection data δ from the sensor 134 (e.g., periodically).
[0107] If the sensor 134 has a force sensor that detects the torque f, the processor 126 of the vehicle 110A may release the operation of the braking mechanism 118 when the vehicle transitions to the vehicle movement mode DM1 in step S5, and then start an operation to acquire the detection data δ (i.e., the torque f). This allows the sensor 134 to reliably detect the torque f applied to the wheel 124.
[0108] After starting the operation of acquiring the detection data δ, the processor 126 of the vehicle 110A determines whether or not a contact operation CO by the user A to the vehicle 110A has been detected (step S21). Specifically, the processor 126 determines whether or not a contact operation CO has been detected based on the detection data δ (e.g., an external force f or a contact c) acquired from the sensor 134. If the processor 126 detects a contact operation CO, the result is YES and the process proceeds to step S22, whereas if the processor 126 determines NO, the process loops back to step S21.
[0109] If the answer is YES in step S21, the processor 126 automatically controls the drive mechanism 114, the steering mechanism 116, and the braking mechanism 118 in accordance with the contact operation CO detected in step S21, and after releasing the operation of the braking mechanism 118 as a vehicle movement operation MO, causes the vehicle 110A to self-propel in a predetermined self-propelled direction DR (step S22).
[0110] As an example, if the sensor 134 includes a force sensor, the processor 126 may detect the direction of the external force f applied to the vehicle 110A by the user A as a contact operation CO (e.g., forward or backward of the vehicle 110A) based on the detection data δ of the external force f acquired from the sensor 134. Then, the processor 126 may determine the direction of the detected external force f as the self-propelled direction DR in which the vehicle 110A is to be self-propelled in step S22.
[0111] As another example, when the sensor 134 has a touch sensor, the processor 126 may determine the self-driving direction DR of the vehicle 110A based on the installation position of the sensor 134 that detected the contact c. For example, when the sensor 134 installed in the rear portion of the exterior 112A detects the contact c, the processor 126 may determine the self-driving direction DR as the front of the vehicle 110A. On the other hand, when the sensor 134 installed in the front portion of the exterior 112A detects the contact c, the processor 126 may determine the self-driving direction DR as the rear of the vehicle 110A.
[0112] Thus, in step S22, the processor 126 causes the vehicle 110A to move in a predetermined moving direction DR as a vehicle movement operation MO in response to the contact operation CO detected by the sensor 134. As a result, the user A can move the vehicle 110A to a desired parking position P1 by the contact operation CO.
[0113] When the processor 126 detects a contact operation CO in step S21, the processor 126 may cause the vehicle 110A to self-propel a predetermined distance (for example, a distance equal to the total length of the vehicle 110A), or may cause the vehicle 110A to continue self-propelling while the processor 126 is detecting the contact operation CO.
[0114] Next, the processor 126 determines whether or not the touch operation CO by the user A has ended (step S23). For example, the processor 126 may determine YES when the sensor 134 has not detected the touch operation CO for a predetermined period of time, and may determine NO while the sensor 134 continues to detect the touch operation CO. If the processor 126 determines YES in step S23, it transmits a self-traveling end signal G2 to the parking management server 16. On the other hand, if the processor 126 determines NO in step S23, it returns to step S22 and continues the vehicle movement operation MO.
[0115] In response to the self-propelling end signal G2, the processor 18 of the parking management server 16 executes the above-mentioned step S11 and transmits the self-propelling command C3 to the vehicle 110A. In accordance with the self-propelling command C3, the processor 126 of the vehicle 110A executes the above-mentioned step S12 and returns the vehicle 110A to the original parking position P0.
[0116] As described above, in this embodiment, the vehicle 110A includes the sensor 134 that detects the contact operation CO by the user A, and after transitioning to the vehicle movement mode DM1, the vehicle moves in a predetermined self-moving direction DR as a vehicle movement motion MO in response to the contact operation CO detected by the sensor 134. According to this configuration, the user A can easily move the vehicle 110A to a desired parking position P1 by performing the contact operation CO on the vehicle 110A.
[0117] The processor 18 of the parking management server 16 may execute the flow shown in Figure 3, Figure 6, Figure 7, Figure 9, or Figure 11 according to a computer program PG pre-stored in the memory 20. The functions of the parking management device 40 or 50 (i.e., the reception unit 26, the identification unit 28, the transmission unit 30, and the self-driving route determination unit 42) executed by the processor 18 may be functional modules realized by the computer program PG.
[0118] 3, 6, 7, 9, and 11 are shown as examples of the parking management method, but various modifications can be made to the flow of Fig. 3, 6, 7, 9, or 11. For example, in step S6 in Fig. 3, the processor 18 of the vehicle 110A may release the operation of the braking mechanism 118 as a vehicle movement operation MO, and then cause the vehicle 110A to run by itself for a predetermined distance (for example, a distance equal to the overall length of the vehicle 110A).
[0119] Also, step S11 may be omitted from the flow of Fig. 6, Fig. 7, Fig. 9, or Fig. 11. For example, in the flow of Fig. 6 or Fig. 11, the processor 126 of the vehicle 110A may automatically start step S12 after completing step S10. Alternatively, in the flow of Fig. 7 or Fig. 9, when the portable device 102 determines YES in step S17 or S19, the portable device 102 may directly transmit the self-traveling command C3 to the vehicle 110A.
[0120] In this way, appropriate modifications can be made to the flows of Figures 3, 6, 7, 9, and 11. Although the present disclosure has been described above through the embodiments, the invention according to the claims is not limited to the above-described embodiments. [Explanation of symbols]
[0121] 10 Parking Management System 12 Infrastructure Sensors 14 Communication Devices 16 Parking Management Server 18,126 processors 26 Reception Department 28 Specific section 30 Transmitter 40,50 Parking management device 42 Self-driving route determination unit 100 Parking 110,110A Vehicle 114 Drive mechanism 116 Steering mechanism 118 Braking mechanism 120 Vehicle communication device 122 ECU
Claims
1. A parking management device for managing vehicles in a parking lot, a reception unit that receives a vehicle movement request transmitted from a portable device of a user of the parking lot in order to move the parked vehicle; an identification unit that identifies the parked vehicle from among the vehicles in the parking lot based on the vehicle movement request; a transmitter that transmits to the parked vehicle a vehicle movement mode command to transition the driving mode of the parked vehicle identified by the identification unit to a vehicle movement mode that causes the parked vehicle to execute a vehicle movement operation for moving the parked vehicle, When the parked vehicle transitions to the vehicle movement mode in accordance with the vehicle movement mode command, the parked vehicle becomes capable of accepting a self-propelling command and transmits a mode transition signal; the transmission unit transmits a communication establishment command to one of the parked vehicle that has transitioned to the vehicle movement mode and the portable device in response to the reception unit receiving the mode transition signal, for establishing communication between the parked vehicle that has transitioned to the vehicle movement mode and the portable device; A parking management device in which, after establishing the communication with the portable device, the parked vehicle self-propels in a predetermined direction as the vehicle movement operation in accordance with the first self-propelling command transmitted from the portable device.
2. the reception unit receives, as the vehicle movement request, a vehicle identification request including information identifying the parked vehicle; The parking management device according to claim 1 , wherein the identification unit identifies the parked vehicle based on the vehicle identification request.
3. The identifying information is The vehicle registration number of the parked vehicle, or The parking management device according to claim 2 , further comprising an identification code uniquely assigned to the parked vehicle.
4. The portable device captures the identifying information using a camera provided in the portable device, and transmits the vehicle identification request accompanied by the identifying information; The parking management device according to claim 3, wherein the identification unit identifies the parked vehicle by comparing the identification information attached to the vehicle identification request received by the reception unit with a database that stores the identification information.
5. A parking management device as described in claim 1, wherein the communication establishment command includes information of the communication address of one of the devices.
6. The reception unit receives a self-propelling end signal transmitted by the portable device when the transmission of the first self-propelling command is completed, The transmitting unit transmits a second self-propelling command to the parked vehicle in response to the receiving unit receiving the self-propelling end signal, 2. The parking management device according to claim 1, wherein the parked vehicle returns to its original parking position by self-propelling in a direction opposite to the predetermined direction in accordance with the second self-propelling command as the vehicle movement operation.
7. A parking management device as described in Claim 6, wherein the transmitting unit transmits the second self-propelled command to the parked vehicle when a predetermined time has elapsed from the time when the receiving unit received the self-propelled end signal.
8. The vehicle movement request is accompanied by information on the predetermined time input by the user to the portable device, The parking management device according to claim 7 , wherein the transmission unit transmits the second self-propelling command to the parked vehicle when the predetermined time accepted by the acceptance unit has elapsed from the time point.
9. A vehicle that transitions to the vehicle movement mode in accordance with the vehicle movement mode command transmitted by the transmission unit of the parking management device according to claim 1 and performs the vehicle movement operation.
10. The vehicle according to claim 9 , wherein the vehicle releases an actuation of a braking mechanism as the vehicle movement operation when the vehicle transitions to the vehicle movement mode.
11. 1. A method for managing vehicles in a parking lot, comprising: The processor: receiving a vehicle movement request transmitted from a portable device of a user of the parking lot to move the parked vehicle; Identifying the parked vehicle from among the vehicles in the parking lot based on the vehicle movement request; Transmitting a vehicle movement mode command to the parked vehicle to transition the operation mode of the identified parked vehicle to a vehicle movement mode that causes the parked vehicle to execute a vehicle movement operation for moving the parked vehicle; When the parked vehicle transitions to the vehicle movement mode in accordance with the vehicle movement mode command, the parked vehicle becomes capable of accepting a self-propelling command and transmits a mode transition signal; the processor, in response to receiving the mode transition signal, transmits a communication establishment command to one of the parked vehicle that has transitioned to the vehicle movement mode and the portable device to establish communication between the parked vehicle and the portable device; the parked vehicle self-propels in a predetermined direction as the vehicle movement operation in accordance with the self-propelling command transmitted from the portable device after establishing the communication with the portable device.
Citation Information
Patent Citations
Power vehicle
JP2002225741A
Remote vehicle operation system
JP2008033438A
Exit support device
JP2011178264A
Parking place, parking place management system, and parking place management method
JP2018180618A
Information processor, electronic control device, information processing method, and program
JP2021099719A
