JP2022164294A - Parking management system, server, parking management method, and program - Google Patents

Abstract

To provide more appropriate parking management of moving bodies.SOLUTION: A parking management system of an embodiment includes a moving body, a mobile terminal of a user of the moving body, and a server that communicates with the moving body and the mobile terminal. The moving body includes: a power source that makes the moving body travel; a moving body position acquisition unit that detects a position of the moving body; and a moving body-side communication control unit that transmits positional information on the moving body acquired by the moving body position acquisition unit to the server based on a state of the power source. The server includes: a first acquisition unit that acquires the positional information on the moving body; a second acquisition unit that acquires information transmitted from the mobile terminal; and a management unit that manages parking of the moving body associating the moving body with the mobile terminal based on the positional information on the moving body acquired by the first acquisition unit and the information acquired by the second acquisition unit when the moving body is parked.SELECTED DRAWING: Figure 1

Description

The present invention relates to a parking management system, a server, a parking management method, and a program.

2. Description of the Related Art Conventionally, in an entry/exit management system for managing the entry/exit of a vehicle to/from a specified space, a communication device entering/exiting the specified space, an entry/exit management device for managing entry/exit based on the authentication result obtained by communication with the communication device, and an entry/exit management system based on the entry/exit history 2. Description of the Related Art A technique for controlling connection of communication between a communication device and an entrance/exit management device is known (see Patent Document 1, for example).

JP 2020-67731 A

However, since the conventional technology requires equipment such as a parking lot gate, there are cases where appropriate parking management cannot be performed for parking areas without such equipment.

Aspects of the present invention have been made in consideration of such circumstances, and provide a parking management system, a server, a parking management method, and a program capable of realizing more appropriate parking management of a moving object. is one of the purposes.

A parking management system, a server, a parking management method, and a program according to the present invention employ the following configuration.
(1): A parking management system according to an aspect of the present invention includes a mobile, a mobile terminal of a user of the mobile, and a server that communicates with the mobile and the mobile terminal. The moving body includes a power source for running the moving body, a moving body position acquisition unit for detecting the position of the moving body, and the moving body position acquiring unit based on the state of the power source. a mobile-side communication control unit configured to transmit the location information of the mobile unit acquired by a unit to the server; the server includes a first acquisition unit configured to acquire the location information of the mobile unit; a second acquisition unit that acquires the transmitted information; and based on the position information of the mobile object acquired by the first acquisition unit and the information acquired by the second acquisition unit when the mobile object is parked. and a management unit that manages parking of the mobile by associating the mobile with the mobile terminal.

(2): The aspect of (1) above further comprises a registration unit for registering information about the mobile unit and the mobile terminal, wherein the registration unit acquires identification information of the mobile unit from the mobile terminal. be.

(3): In the aspect (1) or (2) above, the second acquisition unit acquires the location information of the mobile terminal, and the management unit acquires a movement history based on the location information of the mobile device; The moving object and the mobile terminal are associated with each other based on the movement history based on the location information of the mobile terminal.

(4): In the aspect of (2) above, the registration unit registers a parking area in which the mobile object can be parked, and based on the position information of the mobile object, the parking area registered by the registration unit. Among them, the apparatus further includes a providing unit that provides the mobile terminal with a parking area existing within a predetermined distance from the location information of the moving object.

(5): In any one aspect of the above (1) to (4), the management unit makes an inquiry to the mobile terminal when the moving object is parked, and receives a response from the mobile terminal in response to the inquiry. Parking of the moving body is managed based on the answer information.

(6): In any one of the aspects (1) to (5) above, the management unit, when the position information of the mobile terminal has moved by a predetermined distance or more from the position information of the mobile body, parking is started.

(7): In the aspect of (6) above, when the power source of the moving body is activated after the parking of the moving body is started, and the position of the moving body has moved by a predetermined distance or more from the parking position. , it is determined that the parking of the moving body is finished.

(8): In the aspect (6) or (7) above, the management unit determines that the location information of the mobile terminal is within a first predetermined distance from the location information of the mobile device, and is a second predetermined distance or more from the parking position of the moving body, it is determined that the parking of the moving body is finished.

(9): In the aspect (6) or (7) above, the management unit determines that the location information of the mobile terminal is within a first predetermined distance from the location information of the moving object, and When the moving body is at least a second predetermined distance from the parking position of the moving body, it is determined that the parking of the moving body is completed.

(10): In the aspect of (4) above, the providing unit provides the mobile terminal with information regarding the start or end of parking of the moving body in the parking area.

(11): Another aspect of the present invention is a server that performs communication between a mobile unit and a mobile terminal of a user of the mobile unit, the server comprising: a first acquisition unit that acquires location information of the mobile unit; a second acquisition unit that acquires the position information of the mobile terminal; and the position information of the mobile that is acquired by the first acquisition unit and the location information of the mobile that is acquired by the second acquisition unit when the mobile is parked. a management unit that manages one or both of starting and ending parking of the moving body by associating the moving body with the mobile terminal based on location information of the mobile terminal.

(12): Another aspect of the present invention is that a computer of a server that performs communication between a mobile body and a mobile terminal of a user of the mobile body acquires location information of the mobile body, and determines the position of the mobile terminal. When the information is acquired and the moving body is parked, the moving body and the mobile terminal are associated with each other based on the acquired position information of the moving body and the acquired position information of the mobile terminal to park the moving body. A parking management method that manages one or both of the start and/or end of .

(13): Another aspect of the present invention is to cause a computer of a server that performs communication between a mobile body and a mobile terminal of a user of the mobile body to obtain location information of the mobile body, information is acquired, and when the mobile object is parked, the mobile object and the mobile terminal are associated with each other based on the acquired position information of the mobile object and the acquired position information of the mobile terminal. A program that allows you to manage the start or end of parking, or both.

According to the aspects (1) to (13) above, it is possible to realize more appropriate parking management of the moving body.

It is a figure showing an example of composition of parking management system 1 concerning an embodiment. It is a figure showing an example of composition of vehicles 100 concerning an embodiment. It is a figure which shows an example of a structure of the portable terminal 200 which concerns on embodiment. It is a figure which shows an example of a structure of the parking management server 300 which concerns on embodiment. It is a figure for demonstrating the content of user information DB371. 3 is a diagram for explaining the content of parking area information 372. FIG. It is a figure for demonstrating the content of vehicle state DB374. It is a figure for demonstrating the content of parking utilization DB375. FIG. 10 is a sequence diagram showing an example of the flow of pre-registration processing for a parking service; FIG. 4 is a sequence diagram showing an example of the flow of processing until vehicle 100 is parked in a parking area; FIG. 4 is a sequence diagram showing an example of the flow of processing from when the vehicle 100 is parked in the parking area until parking is completed. FIG. 10 is a diagram showing an example of an image IM10 for accepting registration for use of a parking service. FIG. 10 is a diagram showing an example of an image IM20 for inquiring whether or not to use a parking service; FIG. 10 shows an example of an image IM30 including parking area information; FIG. 10 is a diagram showing an example of an image IM40 for inquiring whether to start parking. FIG. 10 is a diagram showing an example of an image IM50 showing the start of parking in a parking area; FIG. FIG. 12 is a diagram showing an example of an image IM60 showing payment information displayed on display 240 when parking is completed. FIG. FIG. 11 is a diagram showing an example of an image IM70 for registering a parking area; FIG.

Hereinafter, embodiments of a parking management system, a server, a parking management method, and a program according to the present invention will be described with reference to the drawings. In the following, a vehicle is used as an example of a moving object used in the parking management system of the embodiment. The vehicle is, for example, a two-wheeled, three-wheeled, or four-wheeled vehicle. In the following description, it is assumed that the vehicle is a two-wheeled vehicle.

[System configuration]
FIG. 1 is a diagram showing an example of the configuration of a parking management system 1 according to an embodiment. The parking management system 1 shown in FIG. 1 includes, for example, a vehicle 100, a mobile terminal 200, and a parking management server 300. FIG. The vehicle 100, the mobile terminal 200, and the parking management server 300 are communicably connected via a network NW, for example. The network NW includes, for example, the Internet, a cellular network, a Wi-Fi network, a WAN (Wide Area Network), a LAN (Local Area Network), a provider device, a wireless base station, and the like. The parking management system 1 may include one or more of each of the vehicle 100 , the mobile terminal 200 and the parking management server 300 . Further, in the example of FIG. 1, the user U1 is the user of the vehicle 100, for example. The user may be the owner of the vehicle 100 or the borrower (or lentee) to whom the vehicle 100 is lent. The parking management server 300 is an example of a "server".

The vehicle 100 is, for example, a straddle-type two-wheeled vehicle that runs on power output in response to operation of an internal combustion engine that runs on fuel such as gasoline, light oil, or hydrogen. Vehicle 100 may also be an electric two-wheeled vehicle that runs with an electric motor that is driven by electric power supplied from a battery. The battery is, for example, a lithium-ion battery (LIB), a nickel-metal hydride battery, an all-solid battery, or the like. Further, vehicle 100 may be a hybrid vehicle using the above-described internal combustion engine or electric motor as a drive source. An internal combustion engine and an electric motor are examples of a power source mounted on vehicle 100 . In the following description, it is assumed that the vehicle 100 is a saddle-type two-wheeled vehicle that runs on power output by the operation of a gasoline-fueled internal combustion engine. Vehicle 100 communicates with parking management server 300 .

The mobile terminal 200 is a terminal device possessed by the user U1. The mobile terminal 200 is, for example, a smart phone or a tablet terminal. The mobile terminal 200 communicates with the parking management server 300 .

The parking management server 300 , for example, communicates with the vehicle 100 and the mobile terminal 200 to manage the state of the vehicle 100 . A state is a state related to the use or parking of the vehicle 100 . In addition, the parking management server 300 may manage the position information of the vehicle 100 and the position information of the mobile terminal 200, and may manage the usage status of the vehicle 100 and the like. Further, the parking management server 300 may manage registration of parking areas where the vehicle 100 can be parked, provision of information on parking areas, start and end of parking areas, payment processing of usage fees, and the like. The functions of the vehicle 100, the mobile terminal 200, and the parking management server 300 will be specifically described below.

[Vehicle 100]
FIG. 2 is a diagram showing an example of the configuration of the vehicle 100 according to the embodiment. The vehicle 100 includes, for example, a fuel storage unit 110, an engine 115, a switch unit 120, a vehicle control unit 130, a driving force output device 140, a vehicle sensor 150, an HMI (Human Machine Interface) 160, a vehicle A position acquisition unit 170 , a vehicle-side communication unit 180 , and a vehicle-side communication control unit 190 are provided. The vehicle control unit 130, the vehicle position acquisition unit 170, and the vehicle-side communication control unit 190 are each implemented by a hardware processor such as a CPU (Central Processing Unit) executing a program (software). Some or all of these components are hardware (circuit part; circuitry) or by cooperation of software and hardware. Some or all of the functions of these components may be realized by a dedicated LSI. The program may be stored in advance in a storage device (a storage device including a non-transitory storage medium) such as a HDD (Hard Disk Drive) or flash memory provided in the vehicle 100, or may be stored in a DVD, CD-ROM, or the like. It is stored in a removable storage medium (non-transitory storage medium), and the storage medium may be installed in an HDD or flash memory provided in vehicle 100 by being attached to a drive device provided in vehicle 100. . The vehicle position acquisition unit 170 is an example of a "moving body position acquisition unit". The vehicle-side communication control section 190 is an example of a "mobile-side communication control section."

The fuel storage unit 110 is a tank that stores fuel (an example of energy) such as gasoline. The engine 115 is an internal combustion engine that outputs power by burning fuel such as gasoline. The engine 115 is, for example, a reciprocating engine that includes cylinders and pistons, intake valves, exhaust valves, fuel injectors, spark plugs, connecting rods, crankshafts, and the like. The engine 115 outputs power according to the fuel supplied based on the accelerator opening, for example. The engine 115 is an example of an internal combustion engine and an example of a "power source."

The switch unit 120 is a changeover switch that switches between operating and stopping the engine 115 . The switch unit 120 also controls the state and supply of electric power to the in-vehicle devices (for example, the vehicle control unit 130, the vehicle sensor 150, the HMI 160, the vehicle position acquisition unit 170, the vehicle-side communication unit 180, and the vehicle-side communication control unit 190). A changeover switch may be used to switch between a state in which the display is not performed. The changeover switch described above is, for example, an ignition switch. The ignition switch may be a mechanical switch or a GUI (Graphical User Interface) switch using the HMI 160 . Hereinafter, a state in which the engine 115 is started or operated by switching the ignition switch is referred to as "the ignition switch is on", and a state in which the engine 115 is stopped is referred to as "the ignition switch is off". When the ignition switch is in the ON state, power may be supplied to the in-vehicle device from an in-vehicle battery (not shown) or the like, and when the ignition switch is in the OFF state, the power supply to the on-vehicle device is stopped at a predetermined timing. You may

The vehicle control unit 130 acquires information such as the detection result of the vehicle sensor 150 and the position of the vehicle 100 from the vehicle position acquisition unit 170 . In addition, based on the acquired information, the vehicle control unit 130 controls the driving force output device 140 according to the operation of the user U1 on the operator that accepts the driving operation for steering and speed of the vehicle 100, or by autonomous driving. do.

Vehicle control unit 130 also determines whether or not engine 115 has started (or is in operation). For example, the vehicle control unit 130 determines that the engine has started (or is in operation) when the ignition switch is in the ON state, and determines that the engine is not in operation (or is in operation) when the ignition switch is in the OFF state. or stopped). Further, vehicle control unit 130 may determine that engine 115 is in operation when power output from engine 115 is received by driving force output device 140, and vehicle control unit 130 has not received power for a predetermined time or longer. In this case, it may be determined that the engine 115 is stopped. The vehicle control unit 130 outputs, for example, position information of the vehicle 100 and information on the state of the power source to the vehicle-side communication control unit 190 . The state of the power source may be, for example, whether or not the engine 115 is operating (started), or may be the state of the ignition switch (on state, off state).

The running driving force output device 140 outputs running driving force (torque) for the vehicle 100 to run to the driving wheels based on the power output from the engine 115, for example. Thereby, the vehicle 100 can be driven.

The vehicle sensor 150 includes a speed sensor, an acceleration sensor (three-axis G sensor), a rotation speed sensor, an odometer (Odometer), a distance sensor (travel distance from a reset position or a reference position) mounted on the vehicle 100. ), and various other sensors. Further, the vehicle sensor 150 may include, for example, an accelerator opening sensor and a brake sensor. The accelerator opening sensor is attached to an operator (for example, an accelerator lever) that receives an acceleration instruction from the driver (user U1). The accelerator opening sensor detects the amount of operation of the accelerator lever, and detects the detected amount of operation as the accelerator opening. A brake sensor is attached to an operator (for example, a brake lever or a brake pedal) that receives a braking instruction from a driver. The brake sensor detects the amount of operation of the brake lever or the brake pedal, and detects the detected amount of operation as the amount of brake depression. The vehicle sensor 150 may also include, for example, a throttle opening sensor for the engine 115, a fuel discharge amount sensor for measuring the amount of fuel discharged from the fuel storage unit 110, and a suspension stroke sensor.

The vehicle sensor 150 outputs detection results from each sensor and the like to the vehicle control unit 130 at a predetermined timing. The predetermined timing includes, for example, timing based on a predetermined period, timing requested by the parking management server 300, timing instructed by the user U1, and the like. The predetermined period may be, for example, a fixed period (one day, one week) or the like, or one driving cycle (hereinafter referred to as "1DC"). 1DC is, for example, a cycle based on driving from a departure point to a destination, or driving from the start of driving until the vehicle is stopped in a parking area or the like.

Under the control of the vehicle control unit 130, the HMI 160 outputs various types of information (for example, information obtained from the vehicle control unit 130, the vehicle sensor 150, the parking management server 300, etc.) to the user U1 of the vehicle 100, and uses the information. An input operation by the person U1 is accepted. The HMI 160 includes, for example, various display devices such as a meter display (which may be a touch panel), a speaker, a microphone, switches, and the like. Input operations by the occupant include, for example, switching operations of an ignition switch. Further, the input operation by the passenger may be a touch input operation using a touch panel, or may be a voice input operation.

The vehicle position acquisition unit 170 detects the position of the vehicle 100 using a GNSS (Global Navigation Satellite System) receiver (not shown). The GNSS receiver measures the position of the vehicle 100 based on radio waves coming from GNSS satellites such as GPS (Global Positioning System) satellites. The position information determined by the GNSS receiver includes latitude and longitude.

The vehicle-side communication unit 180 includes, for example, a TCU (Telematics Control Unit). The vehicle-side communication unit 180 communicates with the parking management server 300 and other external devices via the network NW under the control of the vehicle-side communication control unit 190 .

The vehicle-side communication control section 190 controls communication with the parking management server 300 using the vehicle-side communication section 180 . For example, the vehicle-side communication control unit 190 transmits position information of the vehicle 100 and information detected by the vehicle sensor 150 (for example, the speed of the vehicle 100) to the parking management server 300 via the network NW by the vehicle-side communication unit 180. be. The information to be transmitted may include identification information (for example, vehicle ID) of the vehicle 100 .

[Mobile terminal 200]
Next, the configuration of mobile terminal 200 will be described. FIG. 3 is a diagram showing an example of the configuration of the mobile terminal 200 according to the embodiment. The mobile terminal 200 shown in FIG. 3 includes, for example, a terminal-side communication unit 210, a terminal-side communication control unit 220, an input unit 230, a display 240, a speaker 250, a terminal position acquisition unit 260, and an application execution unit 270. , an output control unit 280 , and a terminal-side storage unit 290 . The terminal-side communication control unit 220, the terminal position acquisition unit 260, the application execution unit 270, and the output control unit 280 are each implemented by a hardware processor such as a CPU executing a program (software). be. Also, some or all of these components may be realized by hardware (circuitry) such as LSI, ASIC, FPGA, GPU, etc., or by cooperation of software and hardware may be The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device with a non-transitory storage medium), or may be stored in a removable storage medium such as a DVD or CD-ROM (non-transitory storage medium). physical storage medium), and may be installed in the storage device of the mobile terminal 200 by inserting the storage medium into a drive device, card slot, or the like.

The terminal-side storage unit 290 is implemented by the above-described various storage devices, SSD (Solid State Drive), EEPROM (Electrically Erasable Programmable Read Only Memory), ROM (Read Only Memory), or RAM (Random Access Memory). good too. The terminal-side storage unit 290 stores, for example, a parking application 292, vehicle information 294, programs, and other various information. The vehicle information 294 is information about the vehicle 100 used by the user of the mobile terminal 200 . Information about the vehicle 100 is, for example, a vehicle ID. The information about the vehicle 100 may include information such as the vehicle type, shape, size, parking position, parking time, and usage history of the vehicle 100 . Information such as the vehicle ID, vehicle type, and shape and size of the vehicle 100 may be obtained from a vendor when purchasing the vehicle 100, or previously known by the user U1 based on information included in vehicle inspection information. and may be registered in the mobile terminal 200 when using the parking service of the embodiment.

The terminal-side communication unit 210 communicates with the parking management server 300 and other external devices under the control of the terminal-side communication control unit 220 . The terminal-side communication unit 210 communicates with the parking management server 300, for example, via the network NW.

Terminal-side communication control unit 220 receives the position information of vehicle 100 used by user U1 from parking management server 300 via network NW by terminal-side communication unit 210 . In addition, the terminal-side communication control unit 220 accepts that the terminal-side communication unit 210 has received from the parking management server 300 information regarding a parking area and information regarding use of a parking service, which will be described later. The terminal-side communication control unit 220 also causes the terminal-side communication unit 210 to transmit the position information of the mobile terminal 200 acquired by the terminal position acquisition unit 260 to the parking management server 300 . In addition, the terminal-side communication control section 220 may cause the terminal-side communication section 210 to transmit information regarding the intention of the user U1 to use the parking service and pre-registered vehicle information 294 to the parking management server 300 . Also, the terminal-side communication control section 220 may use the terminal-side communication section 210 to transmit and receive information to and from other external devices. Information transmitted from the mobile terminal 200 may include identification information of the mobile terminal 200 (eg, terminal ID), identification information of the user (eg, user ID), and the like.

The input unit 230 receives input from the user U1 by operating various keys and buttons, for example. The input unit 230 includes a microphone 232, for example. The microphone 232 receives voice input from the user U1 under the control of the output control unit 280, for example. The input unit 230 may be configured integrally with the display 240 as a touch panel.

The display 240 is, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro Luminescence) display. The display 240 displays various information in the embodiment under the control of the output control section 280 . The speaker 250 outputs a predetermined sound under the control of the output control section 280, for example.

The terminal location acquisition unit 260 acquires location information of the mobile terminal 200 using a built-in GPS device (not shown). The location information includes, for example, latitude and longitude.

Application execution unit 270 is implemented by executing parking application 292 stored in terminal-side storage unit 290 . The parking application 292 is an application program that controls the output control unit 280 so that the parking area (parking available area) and the like provided by the parking management server 300 are output to the display 240 and the speaker 250 . In addition, the parking application 292 displays information indicating the start or end of the application, parking position, parking time (parking start date and time, parking end date and time), usage fee (billed amount), various error information, etc. on the display 240 or the speaker. 250 may be output.

The parking application 292 is downloaded from an external device via the network NW and installed in the mobile terminal 200, for example. The parking application 292 displays an authentication screen or the like on the display 240 at the time of authentication, and causes information input by the input unit 230 to be transmitted to the parking management server 300 via the terminal-side communication unit 210 . The parking application 292 also outputs the location information acquired by the terminal location acquisition unit 260, various information processed by the parking application 292, and the like to the parking management server 300 via the network NW.

Output control unit 280 controls the content and display mode of an image to be displayed on display 240 and the content and output mode of audio to be output to speaker 250 under the control of application execution unit 270 . For example, the output control unit 280 may output the image and sound obtained from the parking management server 300 from the display 240 and the speaker 250, and generate the image and sound based on the information obtained from the parking management server 300, It may be output from the display 240 or the speaker 250 .

[Parking management server 300]
FIG. 4 is a diagram showing an example of the configuration of the parking management server 300 according to the embodiment. The parking management server 300 shown in FIG. 4 includes, for example, a server-side communication unit 310, a server-side communication control unit 315, an acquisition unit 320, a registration unit 330, a management unit 340, a provision unit 350, and a payment processing unit. 360 and a server-side storage unit 370 . The server-side communication control unit 315, the acquisition unit 320, the registration unit 330, the management unit 340, the provision unit 350, and the payment processing unit 360 are each configured by a hardware processor such as a CPU as a program (software). It is realized by executing Some or all of these components may be realized by hardware (including circuitry) such as LSI, ASIC, FPGA, GPU, etc., or by cooperation of software and hardware. good too. Some or all of the functions of these components may be realized by a dedicated LSI. The program may be stored in advance in a storage device (a non-transitory storage device) such as an HDD or flash memory provided in the parking management server 300, or may be stored in a detachable storage device such as a DVD or CD-ROM. It is stored in a storage medium (non-transitory storage medium), and even if the storage medium is installed in the HDD or flash memory provided in the parking management server 300 by being attached to the drive device provided in the parking management server 300 good. Parking management server 300 may be implemented in a server device or storage device incorporated in a cloud computing system. In this case, the functions of the parking management server 300 may be implemented by a plurality of server devices and storage devices in the cloud computing system.

The server-side storage unit 370 may be implemented by the various storage devices described above, SSD, EEPROM, ROM, RAM, or the like. The server-side storage unit 370 stores, for example, a user information DB (Database) 371, parking area information 372, map information 373, a vehicle state DB 374, a parking use DB 375, programs, and various other information.

The user information DB 371 stores information identifying users who use services provided by the parking management system 1 . The user information DB 371 is used, for example, for user authentication when using a service. FIG. 5 is a diagram for explaining the contents of the user information DB 371. As shown in FIG. The user information DB 371 includes, for example, authentication information for authenticating the user when using the service of the parking management system 1, address, name, age, gender, contact information, payment information, mobile terminal information, and used vehicle information. It is associated. The authentication information includes, for example, a user ID, password, etc., which is identification information for identifying the user. The authentication information may also include biometric authentication information such as fingerprint information and iris information. The contact information is, for example, address information for communication between the mobile terminal 200 used by the user and the parking management server 300 . Also, the contact information may include the user's telephone number, e-mail address, terminal identification information, and the like. The parking management server 300 communicates with the mobile terminal 200 via the network NW based on the contact information, and transmits and receives various information. Payment information is, for example, information on the payment method (e.g., credit card payment, electronic money payment) when the user pays the usage fee (e.g., parking fee) when using the service (e.g., parking area usage service). is. The payment information may also include the date of payment, whether the payment has been completed, the amount of payment, and the like. The mobile terminal information is identification information of the mobile terminal 200 owned by the user U1. The identification information of the mobile terminal 200 may be a terminal ID or the like, or may be information (for example, telephone number) included in the contact information. The used vehicle information is, for example, information on the vehicle 100 owned by the user U1. The used vehicle information may include a vehicle ID as identification information of the vehicle 100 used in the parking service of the embodiment, information related to the size and shape of the vehicle 100, the maximum number of passengers, and the like.

Parking area information 372 stores information about the parking area of vehicle 100 registered by registration unit 330 . FIG. 6 is a diagram for explaining the contents of the parking area information 372. As shown in FIG. In the parking area information 372, for example, a registrant ID as identification information for identifying a registrant of a parking area is associated with a parking area, a parking period, and a parking fee. The parking area stores, for example, information on areas where the vehicle 100 can be parked. The parking area may be address information, or may be information on a partial section or area of the address. Here, the parking area includes, for example, not only hourly parking lots and monthly parking lots that are used as parking lots on a daily basis, such as coin parking lots, but also gardens, fields, vacant lots, etc. in private residential land. It includes areas where parking is available for use as a parking lot, parking areas for individuals of land owners, and areas where parking is available managed by companies, local governments, etc. The parking area may also include, for example, a street parking area that is used as a parking area for freight vehicles on weekdays. The parking available period is information regarding the available period of the parking area. The period may include the date, day of the week, time, type of weekday or holiday, and the like. The parking fee is information about the usage fee of the parking area. The parking fee is set, for example, for each predetermined period (for example, minute, hour, day). The parking fee may also include information indicating that no fee is collected for the first 30 minutes, such as free parking. By registering the parking area in the parking area information 372, it can be used as a parking available area in the parking service of this embodiment.

The map information 373 includes, for example, road information associated with position information, parking area information (eg, parking area, parking period, parking fee), POI (Point Of Interest) information, traffic regulation information, address information (address・Postal code), facility information, telephone number information, etc. are stored. The location information includes latitude and longitude. The map information 373 may be updated at any time by the server-side communication section 310 communicating with an external device.

The vehicle state DB 374 stores information regarding the usage state of the vehicle 100 used in the embodiment. FIG. 7 is a diagram for explaining the contents of the vehicle state DB 374. As shown in FIG. In the vehicle state DB 374, for example, a vehicle ID is associated with a user ID, date and time, vehicle position information, terminal position information, and vehicle state. A user ID is identification information that identifies a user who uses the vehicle 100 associated with the vehicle ID. If the vehicle 100 is lent to someone other than the owner, the user ID will be different from the owner's user ID. The date and time is date and time information in which the vehicle ID and the user ID are associated with each other. The vehicle position information is position information of the vehicle 100 . The terminal location information is location information of the mobile terminal 200 owned by the user associated with the user ID. The vehicle position information and the terminal position information may be continuously stored while the vehicle ID and the user ID are associated with each other. In that case, each location information may be updated to the latest information, and a movement history for a predetermined period may be left. The vehicle state is information regarding the state of vehicle 100 managed by management unit 340 . The vehicle state may include, for example, information such as "running", "parking", and "stopping".

The parking use DB 375 stores, for example, the user's use history of the parking service provided by the parking management system 1 . FIG. 8 is a diagram for explaining the contents of the parking usage DB 375. As shown in FIG. In the parking use DB 375, for example, a user ID is associated with a vehicle ID, a parking area, a parking time, a usage state, and a usage fee. The vehicle ID is identification information of the vehicle 100 parked in the parking area by the user associated with the user ID. A parking area is a parking position of the vehicle 100 . The parking time includes a parking start date and time and a parking end date and time. In addition, when the use is not finished, the information is not stored in the parking end date and time. Also, the parking time may store the elapsed time from the parking start date and time, or the difference between the parking end date and time and the parking start date and time. The usage state is the parking state of the vehicle 100 with respect to the parking area. The charge for use is the charge after the end of use. As the usage fee, the usage fee up to the present may be stored.

The server-side communication unit 310 communicates with the vehicle 100, the mobile terminal 200, and other external devices via the network NW under the control of the server-side communication control unit 315. FIG.

The server-side communication control section 315 controls communication in the server-side communication section 310 . The server-side communication control unit 315 acquires information from the vehicle 100 or the mobile terminal 200 received by the server-side communication unit 310, for example. Further, the server-side communication control unit 315 may cause the server-side communication unit 310 to transmit an information acquisition request to the vehicle 100 or the mobile terminal 200 and cause the server-side communication unit 310 to receive information corresponding to the request. Further, the server-side communication control unit 315 may acquire information related to parking area registration received by the server-side communication unit 310, information related to a parking area information provision request, and the like.

Acquisition unit 320 acquires information from vehicle 100 and mobile terminal 200 . Acquisition unit 320 includes, for example, a first acquisition unit 322 and a second acquisition unit 324 . The first acquisition unit 322 acquires the position information of the vehicle 100 received by the server-side communication unit 310 . The second acquisition unit 324 acquires information from the mobile terminal 200 received by the server-side communication unit 310 . The information from the mobile terminal 200 includes registration information of the vehicle 100 and the mobile terminal 200, location information of the mobile terminal 200, intent to use the service according to the embodiment (for example, parking service), and information such as answers to inquiries. be

The registration unit 330 registers information about users who use the parking management system 1 . For example, when the registration unit 330 receives a user registration request from the terminal of the user U1 (for example, the parking application 292 of the mobile terminal 200), the registration unit 330 inputs various information contained in the user information DB 371 shown in FIG. An image for registration is generated and displayed on the terminal that has received the registration request, and information about the user input from the terminal is acquired. Then, the registration unit 330 registers the acquired information about the user in the user information DB 371 .

Further, the registration unit 330 may authenticate a user who uses the service provided by the parking management system 1 based on the user information DB 371 . For example, the registration unit 330 authenticates the user at the timing of receiving a request to use the service (parking service) according to the embodiment from the mobile terminal 200 . For example, when receiving a request for use, the registration unit 330 generates an authentication image for inputting authentication information such as a user ID and a password, and displays the generated image on the display of the requested mobile terminal 200. , the authentication information in the user information DB 371 is referred to based on the input authentication information input using the displayed image, and the use of the service is permitted depending on whether authentication information matching the input authentication information is stored. determine whether or not to For example, the registration unit 330 permits the use of the service if the user information DB 371 contains authentication information that matches the input authentication information, and denies the use of the service if the matching information is not included. Alternatively, a process for performing new registration is performed.

Further, the registration unit 330 may register the parking area based on the parking area registration request. For example, when the registration unit 330 receives a parking area registration request from the terminal of the registrant (the parking application 292 of the mobile terminal 200 when the registrant uses the mobile terminal 200), An image for inputting various types of information included in the parking area information 372 is generated and displayed on the terminal that has accepted the registration request, and information on the parking area input from the terminal is acquired. Then, the registration unit 330 registers the acquired information about the user in the parking area information 372 . The registration unit 330 may update, change, or delete the information stored in the user information DB 371 and the parking area information 372 at the request of the user or registrant. Further, the registration unit 330 may refer to the map information 373 to acquire information on a parking lot such as a coin parking lot and register it in the parking area information 372 .

The management unit 340 manages the location information of the vehicle 100 (hereinafter referred to as vehicle location information) and the location information of the mobile terminal 200 (hereinafter referred to as terminal location information) received by the server-side communication unit 310, and manages each location information. Based on this, the vehicle 100 and the mobile terminal 200 are associated and managed. In addition, the management unit 340 associates the vehicle 100 with the mobile terminal 200 based on the movement history based on the vehicle position information acquired at a plurality of times and the movement history based on the terminal position information acquired at a plurality of times. good too. In this case, for example, when the degree of similarity in the moving direction, moving speed, moving distance, etc. obtained from the moving history of the vehicle 100 and the mobile terminal 200 is equal to or greater than a predetermined degree, the management unit 340 It is determined that the mobile terminal 200 is being used, and the vehicle and the mobile terminal 200 are managed in association with each other. Further, when the vehicle ID included in the vehicle location information matches the vehicle ID included in the terminal location information, the management unit 340 may manage the vehicle 100 and the mobile terminal 200 in association with each other.

Moreover, the management unit 340 may manage the parking position and the parking time of the vehicle 100 based on each position information. The management unit 340 may also manage the usage status of the vehicle 100 by the user U1. In addition, the parking management server 300 may manage registration of parking areas for the vehicle 100, provision of information on the parking areas, and payment processing of parking area usage fees. Moreover, the management unit 340 may store or update information in the vehicle state DB 374 and the parking use DB 375 based on the management information.

In addition, the management unit 340 estimates the usage state and the vehicle state (for example, “driving”, “parking”, “stopping”, etc.) based on the vehicle position information and the terminal position information, and outputs the estimation result. You may register in vehicle state DB374. For example, when the vehicle position and the terminal position are within a first predetermined distance and the vehicle position has moved by a second predetermined distance or more in a predetermined time, the management unit 340 determines that the vehicle state is "running". I presume there is. In addition, the management unit 340 estimates that the vehicle state is "parking" when the ignition switch of the vehicle 100 is in the off state and the vehicle position and the terminal position are separated from each other by more than the first predetermined distance. . In addition, the management unit 340 estimates that the vehicle state is "stopped" when the ignition switch of the vehicle 100 is in the ON state and the vehicle position has not moved more than the second predetermined distance in the predetermined time. . For example, after the vehicle 100 has started to park, the management unit 340 determines that the parking of the mobile body is stopped when the power source of the vehicle 100 is activated and the position of the vehicle 100 has moved by a predetermined distance or more from the parking position. You may judge that it ended. In addition, the management unit 340 terminates parking of the vehicle 100 when the terminal position information is within a first predetermined distance from the vehicle position information and the position of the vehicle 100 is at least a second predetermined distance from the parking position. It may be determined that Moreover, the management unit 340 determines that the terminal position information is within the first predetermined distance from the vehicle position information, and the position information of both the mobile terminal 200 and the vehicle 100 is at least the second predetermined distance from the parking position of the vehicle 100. In some cases, it may be determined that the parking of the vehicle 100 has ended. Note that the management unit 340 may estimate other usage states and vehicle states based on the vehicle position information and the terminal position information, or the movement history of the vehicle 100 and the movement history of the mobile terminal 200 .

The providing unit 350 provides the user U1 with information about parking areas, information about usage fees, and the like according to the embodiment. For example, the providing unit 350 acquires vehicle position information, refers to the parking area information 372 based on the acquired vehicle position information, and extracts information about parking areas existing within a predetermined distance from the position information. Then, the providing unit 350 transmits the extracted parking area, parking period, and parking fee information to the mobile terminal 200 . Further, the providing unit 350 may use terminal position information acquired from the mobile terminal 200 instead of the vehicle position information.

In addition, the providing unit 350 may transmit the parking time, usage fee, payment information, etc. to the mobile terminal 200 of the user who uses the parking area. Further, the providing unit 350 may transmit information about the amount of money the registrant obtains by using the parking area of the vehicle 100 to the terminal of the registrant who registered the parking area.

The settlement processing unit 360 refers to the parking usage DB 375 at a predetermined cycle or predetermined timing, calculates the total usage fee for each user, and performs settlement processing for the calculated amount. For example, the payment processing unit 360 refers to the parking area information 372 based on the parking usage DB 375 and acquires the parking fee. The settlement processing unit 360 also calculates the usage fee based on the parking time and the parking fee. In addition, the settlement processing unit 360 refers to the settlement information registered in the user information DB 371, and performs the settlement processing of the usage fee according to the settlement method included in the settlement information. In addition, when the usage fee is calculated, the payment processing unit 360 notifies the user of the usage fee and the like by the providing unit 350 before completing the payment, and makes the payment based on the instructed payment method. good too. The processing result by the payment processing unit 360 may be registered in the payment information of the user information DB 371, for example.

[Flow of Parking Service by Parking Management System 1]
Next, the flow of the parking service by the parking management system 1 of the embodiment will be specifically described. In the following, the description will be roughly divided into a parking service pre-registration process, a process until the vehicle 100 is parked in the parking area, and a process from parking to completion of parking. Also, in the following, it is assumed that the parking area is registered by the registration unit 330 .

[Parking service pre-registration process]
FIG. 9 is a sequence diagram showing an example of the flow of pre-registration processing for a parking service. The example of FIG. 9 shows the processing in the mobile terminal 200 and the parking management server 300 . In the example of FIG. 9, the mobile terminal 200 activates the parking application 292 according to an instruction from the user U1 (step S010), and transmits a parking service registration request to the parking management server 300 (step S012). Parking management server 300 generates an image to be displayed as a registration screen based on the registration request from portable terminal 200 (step S014), and transmits the generated image to portable terminal 200 (step S016).

Portable terminal 200 receives the image transmitted from parking management server 300 and displays the received image on display 240 (step S018). Moreover, the portable terminal 200 receives input of registration information by the user U1 (step S020), and transmits the received registration information to the parking management server 300 (step S022).

Based on the registration information received from mobile terminal 200, parking management server 300 associates vehicle 100 with mobile terminal 200 and stores them in information user information DB 371 (step S024). The mobile terminal 200 causes the terminal-side storage section 290 to store information including vehicle information as vehicle information 294 among the information transmitted to the parking management server 300 as registration information (step S026). As a result, the pre-registration process is completed, and the parking service of the embodiment can be used. Note that the registered information may be appropriately changed according to a request from the user U1 or the like.

[Process until vehicle 100 is parked in parking area]
FIG. 10 is a sequence diagram showing an example of the flow of processing until the vehicle 100 is parked in the parking area. In the example of FIG. 10, the processing in the vehicle 100, the mobile terminal 200, and the parking management server 300 is shown. In the example of FIG. 10, when the ignition switch is turned on (IG-ON) by the operation of the user U1, the vehicle 100 starts the power source (engine 115), supplies power to various devices, and enters an operating state. (step S100). When the ignition switch is turned on, the vehicle-side communication control unit 190 transmits the vehicle position information acquired by the vehicle position acquisition unit 170 and the vehicle ID stored in the vehicle 100 in advance to the parking management server 300 (step S102). The process of step S102 may be repeatedly performed at predetermined time intervals while the power source of vehicle 100 is in operation (for example, while the ignition switch is on).

Next, when using the parking service, user U1 activates parking application 292 of mobile terminal 200 (step S104). In the process of step S104, the user authentication process may be executed at the same time when the parking application 292 is activated. In the following description, it is assumed that user authentication has succeeded (the use of the parking service is permitted). When the parking application 292 is activated, the terminal-side communication control section 220 transmits the terminal location information acquired by the terminal location acquisition section 260 and the vehicle ID included in the vehicle information 294 to the parking management server 300 (step S106). . The process of step S106 may be repeatedly executed at predetermined time intervals while the parking application 292 is running.

Next, the management unit 340 of the parking management server 300 acquires the vehicle position information transmitted from the vehicle 100 and the terminal position information transmitted from the mobile terminal 200, and if the distance between the respective position information is within a predetermined distance. If there is, and if the vehicle IDs obtained from the vehicle 100 and the mobile terminal 200 match, the inquiry information for asking the user U1 whether or not to use the parking service of the parking management system 1 is generated ( step S108). Next, the providing unit 350 transmits inquiry information to the mobile terminal 200 (step S110). The parking application 292 of the mobile terminal 200 displays the inquiry information on the display 240 (step S112), and based on the input operation using the displayed image, provides information (response information) as to whether or not to use the parking service. It is transmitted to the parking management server 300 (step S114).

When the management unit 340 of the parking management server 300 receives the information indicating that the parking service is to be used from the mobile terminal 200, the management unit 340 associates the vehicle 100 with the mobile terminal 200, and stores the information in the vehicle usage DB 374 together with the acquired date and time information. Register and manage the usage status of the vehicle 100 (step S116). Note that the association between the vehicle 100 and the mobile terminal 200 may be performed, for example, based on the movement history based on the vehicle position information and the movement history based on the terminal position information. This may be done depending on whether or not the vehicle IDs included in the information transmitted from vehicle 100 and mobile terminal 200 match. For example, by starting the use of the parking service based on the answer result from the mobile terminal 200, it is possible to suppress the start of the parking service in a situation where the user U1 does not want to use the parking service. can. Therefore, the processing load on the parking management server 300 can be reduced. A situation in which the user U1 does not want to use the parking service includes, for example, a case where the parking area of the destination (destination) has already been decided, a situation where the user U1 is going home, a situation where the user U1 does not want to use the parking service for the purpose of maintenance of the vehicle 100, or the like. This is the case when the ignition switch is turned on (without the purpose of driving).

Next, the providing unit 350 searches for a parking area, for example, based on the vehicle position information (step S118). In the processing of step S118, the providing unit 350 refers to the parking area information 372 or the map information 373 based on the vehicle position information, for example, and finds a parking area that exists within a predetermined distance from the vehicle position and is within the parking available period. Extract an area. Further, the provision unit 350 may extract a parking area in which parking is possible based on the usage status of the parking area (availability and parking space) and the size of the vehicle to be parked. Further, the providing unit 350 may preferentially extract a parking area existing in front of the vehicle 100 (or in the direction of travel) over a parking area behind the vehicle 100 . Further, instead of (or in addition to) the above process, when the destination is specified in advance, parking areas in which parking is possible around the specified destination may be extracted. In addition, in the process of step S118, the terminal position information may be used instead of the vehicle position information. The providing unit 350 transmits the extracted information about the parking area (for example, parking area, parking period, parking fee) to the mobile terminal 200 (step S120).

Parking application 292 of mobile terminal 200 causes display 240 to display an image including parking area information (step S122). The processes of steps S116 to S122 may be repeatedly executed at predetermined timings or cycles until, for example, the ignition switch is turned off or the parking application 292 is terminated. The parking management server 300 may appropriately update the vehicle position information, the terminal position information, the vehicle state, etc. of the vehicle state DB 374 based on the information acquired from the vehicle 100 and the mobile terminal 200, and may update the vehicle 100 based on the vehicle position information. and the movement history of the mobile terminal 200 based on the terminal movement information.

The vehicle 100 travels to the destination or the like by the operation of the user U1 (step S124), and stops in the parking area (step S126). Next, when the ignition switch of the vehicle 100 is turned off (IG-OFF) (step S128), the vehicle-side communication control unit 190 transmits vehicle position information to the parking management server 300 via the network NW (step S130). ). As a result, the management unit 340 of the parking management server 300 confirms whether the vehicle 100 is parked in the parking area registered in the parking area information 372 (hereinafter referred to as the official parking area) and during the parking period. can be done. If the vehicle 100 is not parked in the proper parking area or during the permitted parking period, the management unit 340 notifies the portable terminal 200 that the parking area is incorrect or that the parking period is not valid. You may In the following description, it is assumed that the vehicle 100 is parked in the regular parking area and within the parking period.

Next, the management unit 340 generates inquiry information for inquiring of the user U1 whether or not to start parking in the parking area (step S132), and transmits the generated inquiry information to the mobile terminal 200 (step S134). The parking application 292 of the mobile terminal 200 displays the inquiry information on the display 240 (step S136), and based on the input operation using the displayed image, information (response) regarding whether to park the vehicle 100 in the parking area. information) to the parking management server 300 (step S138). The reply information may include the vehicle ID.

When the management unit 340 receives the response from the mobile terminal 200 and the response indicating parking as the response result, the management unit 340 compares the vehicle position information and the terminal position information (step S140), and determines to start parking (step S140). S142). In the processing of step S142, for example, the management unit 340 determines whether or not the terminal position is separated from the vehicle position by a predetermined distance or more, and determines that parking has started when it is determined that the terminal position is separated by a predetermined distance or more. Further, the management unit 340 may transmit information indicating that the user U1 has left the vehicle 100 when the terminal position has been separated from the vehicle position by a predetermined distance or longer for a predetermined time or longer. Moreover, the management unit 340 may determine that parking has started when an answer to the effect that the vehicle is to be parked is received as the answer result. As a result, it is possible to prevent the user U1 from temporarily leaving the vehicle 100 without intending to park the vehicle 100 from being determined to start parking, thereby realizing more appropriate parking management.

Note that, instead of the processing of steps S130 to S142 described above, when the user U1 performs an operation indicating the start of parking on the mobile terminal 200, the mobile terminal 200 transmits information indicating the start of parking to the parking management server 300. The parking management server 300 that has transmitted and received the information may manage the usage status and the like. In this case, the portable terminal 200 displays a button for accepting a parking start operation from the user U1 on the display 240, and the parking start displayed on the display 240 is displayed while the user U1 is within a predetermined distance from the parking area. When the button indicating the start of parking is pressed, information such as information indicating the start of parking is transmitted to the parking management server 300 .

Next, the providing unit 350 transmits information indicating that parking has started (for example, parking position and parking start date and time) to the mobile terminal 200 (step S144).

The mobile terminal 200 stores the parking position and parking start date and time of the vehicle 100 in the terminal-side storage unit 290 (step S146), and displays the parking position and parking start date and time on the display 240 (step S148). This allows the user U1 to accurately grasp that parking of the vehicle 100 in the parking area has started and the parking start date and time. In the embodiment, the vehicle can be parked not only in a parking area that can be used on a daily basis, such as coin parking, but also in a parking area that can only be used temporarily for a limited period of time, such as a residential lot. Parking areas that can only be used temporarily do not have facilities such as entry/exit gates and parking meters, so there is a possibility that the user U1 may be worried about whether the vehicle 100 is parked in the correct parking area. . Therefore, by presenting the parking position and the parking start date and time to the user through the process of step S148, it is possible to give the user a sense of security.

[Processing from parking to completion of parking]
FIG. 11 is a sequence diagram showing an example of the flow of processing from when the vehicle 100 is parked in the parking area to when the parking is completed. Based on the vehicle position information stored in the terminal-side storage unit 290 and the terminal position information acquired by the terminal position acquisition unit 260, the position of the mobile terminal 200 is less than a predetermined distance from the vehicle position. It is determined whether or not (step S200). When it is determined that the distance from the vehicle 100 is less than the predetermined distance, the mobile terminal 200 transmits information indicating that the distance is less than the predetermined distance to the parking management server 300 (step S202). In the process of step S202, if the mobile terminal 200 continues to be at a distance less than the predetermined distance from the vehicle 100 for a predetermined time or longer, the mobile terminal 200 may transmit information indicating that the distance is less than the predetermined distance to the parking management server 300. good. As a result, it is possible to prevent the user U1 from terminating the parking even though the user U1 does not intend to terminate the parking when crossing the vicinity of the parking position, and more appropriate parking management can be realized. Note that the processing of steps S200 to S202 may be performed by the management section 340 of the parking management server 300 instead of the parking application 292 of the mobile terminal 200. FIG. After that, the portable terminal 200 repeatedly transmits the terminal location information to the parking management server 300 at a predetermined period or timing (step S204).

When the management unit 340 of the parking management server 300 receives the processing from the mobile terminal 200, it registers in the parking utilization DB 375 that the user U1 exists near the parking position of the vehicle 100 as the utilization state of the user U1 (for example, , is registered as a user return state) and managed (step S206).

Next, when the ignition switch is turned on (IG-ON), the power source of the vehicle 100 is started, power is supplied to various devices, and the vehicle 100 enters an operating state (step S208). The vehicle-side communication control unit 190 causes the vehicle position information detected by the vehicle sensor 150 to be transmitted to the parking management server 300 (step S210). After that, the vehicle-side communication control unit 190 repeatedly transmits the vehicle position information to the parking management server 300 at a predetermined cycle or predetermined timing.

The management unit 340 receives the vehicle position information transmitted from the vehicle 100 and the vehicle position information transmitted from the mobile terminal 200, registers them in the vehicle state DB 374, and manages the vehicle state (step S212). Moreover, the management unit 340 determines whether or not the parking is finished based on the vehicle position information and the terminal position information (step S214). In the process of step S214, for example, the management unit 340 determines that the ignition state of the vehicle 100 is ON and the position of the vehicle 100 or the mobile terminal 200 is the parking position (vehicle position) when the vehicle 100 is parked. When the vehicle 100 moves away from the parking area by a predetermined distance or more, it is determined that the parking of the vehicle 100 is completed. Further, the management unit 340 determines that the vehicle 100 is in the parking area when the terminal position information is within the first predetermined distance from the vehicle position information and the vehicle position information is at least the second predetermined distance from the parking position of the vehicle 100 . , and it may be determined that the parking of the vehicle 100 is completed. In addition, when the terminal location information is within the first predetermined distance from the vehicle location information and the mobile terminal 200 and the vehicle 100 are at least the second predetermined distance from the parking position of the vehicle 100, the management unit 340 It may be determined that the vehicle 100 leaves the parking area and the parking of the vehicle 100 is completed. Further, when the vehicle 100 transmits the speed of the vehicle 100 from the vehicle sensor 150 to the parking management server 300, the management unit 340 determines whether the vehicle 100 moves from the parking area when the speed of the vehicle 100 is equal to or higher than the predetermined speed. Then, it may be determined that the parking is finished. In addition, the management unit 340 continuously acquires the vehicle position information, and based on the acquired position information, when the travel time of the vehicle 100 is equal to or longer than a predetermined time, the vehicle 100 moves out of the parking area and the parking is stopped. You may judge that it ended.

Further, in place of the processing of steps S200 to S214 described above, the management unit 340 causes the mobile terminal 200 to transmit information indicating the end of parking when the user U1 performs an operation indicating the end of parking on the mobile terminal 200. The information may be transmitted to the parking management server 300, and the parking management server 300 receiving the information may manage the usage status and the like. In this case, the mobile terminal 200 displays, for example, on the display 240 a button for accepting a parking end operation from the user U1, and the user U1 is within a predetermined distance from the parking area. When the button indicating the end is pressed, information indicating the end of parking is transmitted to the parking management server 300 . Note that if the determination is made only by pressing the button, the user may conclude that the parking has ended illegally. This makes it possible to perform more accurate parking end determination. Further, in the process of step S214, if it is determined that the parking has ended, the management unit 340 registers the fact that the parking has ended in the parking usage DB 375, and manages the usage state of the parking area (for example, parking time). .

Next, the settlement processing unit 360 executes settlement processing regarding use of the parking area (step S216). Next, the providing unit 350 transmits the settlement result and the like to the mobile terminal 200 (step S218).

The mobile terminal 200 receives the information (payment information) regarding the payment result transmitted from the parking management server 300 and displays it on the display 240 (step S220). This makes it possible for the occupant to recognize that the settlement process for using the parking area has been completed.

[Information notified to the user by the mobile terminal]
Next, various information notified to the user U1 by the portable terminal 200 in a series of processing of the parking service by the parking management system 1 described above will be described. FIG. 12 is a diagram showing an example of an image IM10 for accepting registration for use of the parking service. Image IM10 is, for example, an image displayed on display 240 through the process of step S018 described above. Image IM<b>10 may be generated by providing unit 350 or may be generated by parking application 292 . The same applies to examples of subsequent images. Image IM10 includes, for example, a user information registration area AR11 and a switch display area AR12. The user information display area AR11 includes input areas AR11a to AR11i made up of text boxes for receiving input of each information to be registered in the user information DB371. Text boxes AR11a to AR11i are input areas for user ID, address, name, age, sex, contact information, payment information, mobile terminal information, and used vehicle information, respectively. A user ID may be assigned by the parking management server 300 . Also, at least one of the input areas AR11a to AR11i may be, for example, a combo box (dropdown list) that allows one to be selected from a plurality of selection candidates.

The switch display area AR12 includes, for example, icons IC11 and IC12. Icons IC11 and IC12 are GUI switches. The same applies to subsequent icons. The icon IC11 is a GUI switch that receives a command to cause the parking management server 300 to execute user registration processing based on the information input to the user information registration area AR11. The icon IC44 is a GUI switch that accepts termination of the display of the image IM10 without performing user registration processing. When the selection of the icon IC11 is accepted, the mobile terminal 200 transmits the information input to the user information registration area AR11 to the parking management server 300. FIG. Registration unit 330 of parking management server 300 registers the received information in user information DB 371 . Thereby, the user or the mobile terminal 200 and the vehicle information can be associated and managed. After completing the registration, registration unit 330 transmits information indicating that the registration has been completed to mobile terminal 200, and parking application 292 of mobile terminal 200 terminates the display of image IM10. Also, when the icon IC12 is selected, the parking application 292 terminates the display of the image IM10.

FIG. 13 is a diagram showing an example of an image IM20 for inquiring whether or not to use the parking service. The image IM20 is, for example, an image displayed on the display 240 through the process of step S112 described above. The image IM20 includes, for example, an inquiry display area AR21, a utilization target display area AR22, and a switch display area AR23.

In the inquiry display area AR21, for example, information (for example, characters) for inquiring of the user U1 whether or not to use the parking service is displayed. In the utilization target display area AR22, for example, identification information for identifying a user and a vehicle targeted for using the service is displayed. The switch display area AR23 includes, for example, an icon IC21 and an icon IC22. The icon IC21 is a GUI switch that receives an instruction to start using the parking service. The icon IC22 is a GUI switch that receives an instruction not to start using the parking service. When the icon IC21 is selected, the mobile terminal 200 transmits to the parking management server 300 information indicating that use of the parking service is to be started. When the icon IC22 is selected, the mobile terminal 200 transmits to the parking management server 300 information indicating that use of the parking service is not started. This eliminates the need for the parking management server 300 to search for unnecessary parking areas and provide information on search results, thereby reducing the system load.

FIG. 14 is a diagram showing an example of an image IM30 including parking area information. Image IM30 is, for example, an image displayed on display 240 by the process of step S122. The image IM30 includes, for example, a map image IM31, a position specifying image IM32, a parking area image IM33, and a parking information image IM34.

The map image IM31 is map information of a predetermined distance range from the reference position included in the map information 373, for example. The reference position may be, for example, the position of the vehicle 100 or the position information of the destination. The following description assumes that the reference position is the position of the vehicle 100 . In the example of FIG. 14, the position specifying image IM32 associated with the vehicle position information is displayed at the position associated with the coordinates on the map image (map coordinates).

The parking area image IM33 is an image representing a parking area existing within a predetermined distance from the vehicle parking position, which is referenced from the parking area information 372 based on the vehicle position information. In the example of FIG. 14, parking area images IM33a to IM33c showing three parking areas are superimposed on the map image IM31. The images IM33a to IM33c may be displayed superimposed on the map image IM31 with a predetermined transmittance. Also, the images IM33a to IM33c may be displayed in different display modes. The display mode is, for example, color, pattern, gradation, shape, transmittance, presence/absence of blinking, and the like. For example, the parking application 292 may change the display mode according to, for example, the parking period, the parking fee, and the like.

The parking information image IM34 is an image including character information about the parking period and parking fee stored in the parking area information 372 . The parking information image IM34 is superimposed and displayed at a position associated with the display position of the parking area image IM33. In the example of FIG. 14, parking information images IM34a to IM34c are displayed at positions associated with respective display positions of parking area images IM33a to IM33c. The parking application 292 can display the parking area of the selected parking area image IM33 when the user U1 selects (for example, taps) the display position of one of the parking area images IM33a to IM33c displayed on the display 240. You may display the parking information matched with. The parking application 292 may also cause the speaker 250 to output audio information corresponding to the parking information.

By displaying the image IM30, the user U1 can recognize the information about the parking area. In addition, according to the present embodiment, the user U1 can use as a parking space an area on a private site that is not used as a parking area on a daily basis, a field, a parking area managed by a company or a local government, and the like. can be recognized.

FIG. 15 is a diagram showing an example of an image IM40 for inquiring whether to start parking. The image IM40 is, for example, an image displayed on the display 240 through the process of step S136 described above. The image IM40 includes, for example, an inquiry display area AR41, a use target display area AR42, and a switch display area AR43.

In the inquiry display area AR41, for example, information (for example, characters) for inquiring of the user U1 whether or not to start parking is displayed. In the utilization target display area AR42, for example, the user who uses the service, the identification information for identifying the vehicle, and the information regarding the parking area are displayed. The switch display area AR43 includes, for example, an icon IC41 and an icon IC42. The icon IC41 is a GUI switch that receives an instruction to start parking. The icon IC 42 is a GUI switch that receives an instruction not to start parking. When the icon IC41 is selected, the mobile terminal 200 transmits to the parking management server 300 information indicating to start parking. When the icon IC42 is selected, the mobile terminal 200 transmits to the parking management server 300 information indicating that parking of the parking service is not started. Thereby, the parking management server 300 can more accurately manage parking.

FIG. 16 is a diagram showing an example of an image IM50 showing the start of parking in the parking area. The image IM50 is, for example, an image displayed on the display 240 by the process of step S148 described above. The image IM20 includes, for example, a usage information display area AR51, a detailed information display area AR52, and a switch display area AR53 as a parking information screen. In the usage information display area AR51, information (for example, characters) or the like indicating that parking of the vehicle 100 in the parking area is started is displayed. Detailed information on parking is displayed in the detailed information display area AR52. The detailed information includes identification information of the user who parked the vehicle 100 (user ID), identification information of the parked vehicle (vehicle ID), parking area, parking start date and time, and information on the parking fee for the parking area. be The switch display area AR53 includes, for example, an icon IC51. Icon IC51 is a GUI switch that accepts termination of display of image IM50. By displaying image IM50, occupant U1 can easily recognize that vehicle 100 has been correctly parked in the proper parking area. In the embodiment, an area that is not used as a parking area on a daily basis is also provided as a parking area, so facilities such as entrance/exit gates and parking meters may not exist. Therefore, by displaying the image IM50 shown in FIG. 16, the user U1 can recognize that the vehicle 100 is parked in the proper parking area, and the user U1 can leave the vehicle 100 at ease and move. can be done.

FIG. 17 is a diagram showing an example of an image IM60 showing payment information displayed on display 240 when parking is completed. Image IM60 is, for example, an image displayed on display 240 in step S220 described above. The image IM60 includes, for example, a usage status display area AR61, a usage result display area AR62, and a switch display area AR63.

Information (for example, characters) or the like indicating that the vehicle 100 has been parked in the parking area is displayed in the usage state display area AR61. Detailed information on the used parking is displayed in the usage result display area AR62. The usage result display area AR62 includes, for example, the user ID, vehicle ID, parking area, and usage fee. The usage result display area AR62 may also include information about parking time.

The switch display area AR63 includes, for example, an icon IC61 and an icon IC62. The icon IC 61 is a switch for accepting payment by the payment method registered in the user information DB 371 by the user. The icon IC 62 is a switch for paying the usage fee by a method other than the registered payment method. When the icon IC61 is selected, the usage fee is settled by the registered settlement method (for example, credit settlement). When the icon IC62 is selected, another payment method (for example, electronic payment) is accepted by the user, and the usage fee is settled by the accepted payment method.

By displaying the image IM60 and notifying the user U1, it is possible to make it easier for the user U1 to grasp the end of parking. In addition, by displaying the image IM60, it is possible to smoothly perform processing up to payment for use of the parking service.

The parking application 292 may display an image on the display 240 for the registrant who registers the parking area to register the parking area. In this case, the registrant registers the parking area by starting the parking application 292 installed in the terminal device owned by the registrant, displaying the parking area registration screen, and inputting various information. A terminal device owned by a registrant can apply, for example, a configuration similar to that of the mobile terminal 200 .

FIG. 18 is a diagram showing an example of an image IM70 for registering a parking area. Image IM70 includes, for example, a registration information display area AR71 and a switch display area AR72 as a parking area registration screen. The registration information display area AR71 includes, for example, a registrant ID input area AR71a, a parking area input area AR71b, parking period input areas AR71c to AR71e, and a parking fee input area AR71f. The registrant ID input area AR71a is an area where identification information for identifying a registrant is input. The parking area input area AR71b is an area for designating a parking area used in the parking service of the embodiment. The registered information display area AR71 includes an icon IC71 for designating an address and an icon IC72 for estimating an area. When the icon IC71 is selected, an image for selecting an address is displayed, and the address information input using the image is input to the parking area input area AR71b. When the icon IC72 is selected, map information or the like is displayed, and when the designation of the range by the registrant is accepted, information (for example, latitude and longitude information) related to the parking area corresponding to the range is input to the parking area input area AR71b. be done.

The parking available period input area AR71c receives inputs such as dates and cycles. The parking permitted period input area AR71d receives an input of the start time of the parking permitted period. The parking permitted period input area AR71e receives an input of the end time of the parking permitted period. The parking fee input area AR71f accepts the input of the usage fee. In the example of FIG. 18, the parking period input area AR71c and the parking fee input area AR71f are, for example, combo boxes (drop-down lists) from which one can be selected from a plurality of selection candidates, but the parking period input area AR71d , AR71e may be a combo box.

The switch display area A72 includes, for example, an icon IC73 and an icon IC74. The icon IC73 is a GUI switch that receives a command to cause the parking management server 300 to execute a parking area registration process based on the information input to the registration information display area AR71. The icon IC74 is a GUI switch that accepts termination of the display of the image IM70 without performing the parking area registration process. In the example of FIG. 18, when the selection of the icon IC71 is accepted, the mobile terminal 200 transmits the information input to the registration information display area AR71 to the parking management server 300. FIG. Registration unit 330 of parking management server 300 registers the received information in parking area information 372 . Note that the registration unit 330 may determine whether or not the registered parking area can be used as a parking area under the authority of the registrant. In this case, the registration unit 330, for example, accesses the external device via the network NW to acquire the registry information, and if the registrant is the owner of the land including the parking area, it can be used as the parking area. determine that it can be done. In addition, the registration unit 330 stores information (registrant information) about the land owned by the registrant in advance in the server-side storage unit 370, and a part or all of the land registered in the registrant information is used as a parking area. If the registration is requested, it may be determined that the area can be used as a parking area.

By displaying the image IM70, the registrant can smoothly register the parking area. In addition, it is possible to make effective use of land or the like that is not used by registrants as a parking area. The images IM10 to IM40 shown in FIGS. 12 to 18 may be displayed on the HMI 160 of the vehicle 100, for example.

[Modification]
In the parking management system 1 described above, at least some of the functions provided by each of the vehicle 100, the mobile terminal 200, and the parking management server 300 may be provided by another device. For example, the destination information may be set for the user U1 by the HMI 160, and the set destination information may be transmitted from the vehicle 100 to the parking management server 300. FIG. Some of the functions of the management unit 340 of the parking management server 300 may be executed by the parking application 292 of the mobile terminal 200, and some of the functions executed by the parking application 292 are executed by the management unit 340. good too.

The embodiment described above includes, for example, a vehicle (an example of a mobile object) 100, a mobile terminal 200 of a user U1 of the vehicle 100, and a parking management server (an example of a server) that communicates with the vehicle 100 and the mobile terminal 200. , the vehicle 100 includes a power source for running the vehicle 100, a vehicle position acquisition unit (an example of a mobile body position acquisition unit) 170 for detecting the position of the vehicle 100, and a power source. a vehicle-side communication control unit (an example of a mobile-side communication control unit) 190 that transmits the position information of the vehicle 100 acquired by the vehicle position acquisition unit 170 to the parking management server 300 based on the state; 300 includes a first acquisition unit 322 that acquires position information of vehicle 100, a second acquisition unit 324 that acquires information transmitted from portable terminal 200, and a a management unit 340 that manages parking of the vehicle 100 by associating the vehicle 100 with the mobile terminal 200 based on the acquired vehicle position information and the information acquired by the second acquisition unit 324; Appropriate parking management of moving bodies can be realized.

Specifically, according to the embodiment, an area without facilities such as an entrance/exit gate and a parking meter can be used as a parking area, so that a parking service can be provided at a lower cost. Further, according to the embodiment, parking determination is performed based on whether or not the power source of the vehicle 100 is in operation, and parking can be started and ended more appropriately based on vehicle position information and terminal position information at the time of parking. can be managed. Further, according to the embodiment, by making an inquiry to the mobile terminal 200 from the parking management server 300, it is possible to further determine whether to use the parking service according to the embodiment and whether to start parking in the parking area. It is possible to accurately grasp, and as a result, it is possible to realize more appropriate parking management.

The embodiment described above can be expressed as follows.
A server computer that performs communication between a mobile object and a mobile terminal of a user of the mobile object,
a storage device storing a program;
a hardware processor;
By the hardware processor executing the program stored in the storage device,
Acquiring location information of the moving object;
Acquiring location information of the mobile terminal,
When the mobile body is parked, the mobile terminal and the mobile terminal are associated with each other based on the acquired position information of the mobile body and the acquired position information of the mobile terminal to determine whether to start or end the parking of the mobile body. manage one or both of
A server that is configured to:

As described above, the mode for carrying out the present invention has been described using the embodiments, but the present invention is not limited to such embodiments at all, and various modifications and replacements can be made without departing from the scope of the present invention. can be added.

REFERENCE SIGNS LIST 1 parking management system 100 vehicle 110 fuel storage unit 115 engine 120 switch unit 130 vehicle control unit 140 driving force output device 150 vehicle sensor 160 HMI 170 Vehicle position acquisition unit 180 Vehicle-side communication unit 182 Vehicle-side first communication unit 184 Vehicle-side second communication unit 190 Vehicle-side communication control unit 200 Portable terminal 210 Terminal-side communication unit 220 Terminal-side communication control unit 230 Input unit 240 Display 250 Speaker 260 Terminal position acquisition unit 270 Application execution unit 280 Output control unit 290 Terminal-side storage unit 300 Parking Management server 310 Server-side communication unit 315 Server-side communication control unit 320 Acquisition unit 330 Registration unit 340 Management unit 350 Providing unit 360 Payment processing unit 370 Server-side storage unit

Claims (13)

A parking management system including a mobile, a mobile terminal of a user of the mobile, and a server that communicates with the mobile and the mobile terminal,
The moving body is
a power source for running the moving body;
a moving body position acquisition unit that detects the position of the moving body;
a mobile-side communication control unit configured to transmit the location information of the mobile object acquired by the mobile-object location acquisition unit to the server based on the state of the power source;
The server is
a first acquisition unit that acquires the position information of the moving body;
a second acquisition unit that acquires information transmitted from the mobile terminal;
When the moving object is parked, the moving object and the mobile terminal are associated with each other based on the position information of the moving object acquired by the first acquiring unit and the information acquired by the second acquiring unit. a management unit that manages parking of the moving body by
parking management system. further comprising a registration unit for registering information about the mobile unit and the mobile terminal;
The registration unit acquires identification information of the mobile object from the mobile terminal.
The parking management system according to claim 1. The second acquisition unit acquires location information of the mobile terminal,
The management unit associates the moving body with the mobile terminal based on a movement history based on the location information of the mobile body and a movement history based on the location information of the mobile terminal.
The parking management system according to claim 1 or 2. The registration unit registers a parking area where the mobile object can be parked,
Further comprising a provision unit that provides the portable terminal with a parking area existing within a predetermined distance from the position information of the mobile object among the parking areas registered by the registration unit based on the position information of the mobile object,
The parking management system according to claim 2. The management unit makes an inquiry to the mobile terminal when the mobile object is parked, and manages parking of the mobile object based on answer information from the mobile terminal to the inquiry.
The parking management system according to any one of claims 1 to 4. The management unit determines that parking of the moving object has started when the location information of the mobile terminal has moved from the location information of the moving object by a predetermined distance or more.
The parking management system according to any one of claims 1 to 5. The management unit determines that parking of the moving body is stopped when the power source of the moving body is activated after parking of the moving body is started and the position of the moving body has moved by a predetermined distance or more from the parking position. determine that it is finished
The parking management system according to claim 6. The management unit determines that the location information of the mobile terminal is within a first predetermined distance from the location information of the moving body, and the location of the moving body is at least a second predetermined distance from the parking position of the moving body. In the case, it is determined that the parking of the moving body has ended,
The parking management system according to claim 6 or 7. The management unit determines that the location information of the mobile terminal is within a first predetermined distance from the location information of the moving body, and that the mobile terminal and the moving body are within a second predetermined distance from the parking position of the moving body. If the above is the case, it is determined that the parking of the moving object has ended;
The parking management system according to claim 6 or 7. The providing unit provides the portable terminal with information regarding the start or end of parking of the mobile body in the parking area.
The parking management system according to claim 4. A server that performs communication between a mobile unit and a mobile terminal of a user of the mobile unit,
a first acquisition unit that acquires the position information of the moving body;
a second acquisition unit that acquires location information of the mobile terminal;
When the moving body is parked, the moving body and the mobile terminal are determined based on the location information of the moving body acquired by the first acquisition unit and the location information of the mobile terminal acquired by the second acquisition unit. a management unit that manages one or both of the start and end of parking of the mobile object in association with a terminal;
A server with A server computer that performs communication between a mobile object and a mobile terminal of a user of the mobile object,
Acquiring location information of the moving object;
Acquiring location information of the mobile terminal,
When the mobile body is parked, the mobile terminal and the mobile terminal are associated with each other based on the acquired position information of the mobile body and the acquired position information of the mobile terminal to determine whether to start or end the parking of the mobile body. manage one or both of
Parking management method. In a server computer that communicates between a mobile device and a mobile terminal of a user of the mobile device,
Acquiring position information of the mobile body,
Acquiring the location information of the mobile terminal,
When the moving object is parked, parking of the moving object is started or ended by associating the moving object with the portable terminal based on the obtained position information of the moving object and the acquired position information of the portable terminal. have control over one or both of
program.

Images