JP7456969B2 - Server, mobile terminal, parking management method, and program - Google Patents

Description

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

Conventionally, in an entry/exit control system that manages entry and exit of vehicles into a predetermined space, there is a communication device for entering and exiting the predetermined space, an entry/exit control device that manages entry and exit based on authentication results obtained by communication with the communication device, and an entry/exit management device that manages entry and exit based on the history of entry and exit. 2. Description of the Related Art Techniques for controlling communication connections between communication devices and entry/exit management devices are known (for example, see Patent Document 1).

JP2020-67731A

However, the conventional technology does not consider the case of a mobile object that does not have a communication device for communicating with the input management device. Therefore, there have been cases where appropriate parking management of moving objects cannot be performed.

Aspects of the present invention have been made in consideration of such circumstances, and provide a parking management system, a mobile terminal, a parking management method, and a program that can realize more appropriate parking management for moving objects. This is one of the purposes.

A parking management system, a mobile terminal, a parking management method, and a program according to the present invention employ the following configuration.
(1): A parking management system according to one aspect of the present invention includes a mobile object, a mobile terminal of a user of the mobile object, and a server that communicates with the mobile object and the mobile terminal. The mobile terminal includes a terminal position acquisition unit that acquires location information of the mobile terminal, a first communication unit that communicates with an electronic tag attached to the mobile object, and a first communication unit that communicates with the server. When it is determined that the mobile object is parked based on the communication state between the first communication unit and the electronic tag and the position information of the mobile terminal, the second communication unit a terminal-side communication control unit that causes the server to transmit identification information of the mobile object acquired from the tag and position information of the mobile terminal, the server comprising a server-side communication unit that communicates with the mobile terminal; The parking management system includes a management section that manages parking of the mobile object based on identification information of the mobile object and position information of the mobile terminal received from the mobile terminal by the server side communication section.

(2): In the aspect of (1) above, the server includes a registration unit that registers a parking area where the mobile body can park, and a parking area registered by the registration unit based on the location information of the mobile body. The present invention further includes a providing unit that provides the mobile terminal with a parking area of the mobile object that is located within a predetermined distance from the position information of the mobile terminal among the parking areas.

(3): In the aspect of (1) or (2) above, the terminal-side communication control unit changes the state in which the first communication unit and the electronic tag are communicating to the first communication unit and the electronic tag. When the vehicle is not communicating with the tag, information indicating that parking of the mobile object has started is transmitted to the server.

(4): In any one of the aspects (1) to (3) above, the terminal-side communication control unit is configured to control, when the amount of operation of the mobile terminal operated by the user is equal to or greater than a predetermined amount. , and transmits information indicating that parking of the mobile object has started to the server.

(5): In any one of the aspects (1) to (4) above, the management unit causes the first communication unit and the electronic tag to communicate after the mobile object starts parking. In this case, the end of parking of the mobile object is managed based on the position information of the mobile terminal.

(6): In the aspect of (5) above, the management unit acquires information on one or both of the moving speed and the moving distance of the moving body based on the position information of the mobile terminal, and the acquired information The end of parking of the mobile object is determined based on the above.

(7): In the aspect of (2) above, the providing unit provides the mobile terminal with information regarding the start or end of parking of the mobile object in the parking area.

(8): Another aspect of the present invention is a mobile terminal that is carried by a user of a mobile body and communicates with a server, the mobile terminal comprising: a terminal position acquisition unit that acquires position information of the mobile terminal; a first communication unit that communicates with an electronic tag attached to the mobile terminal, a second communication unit that communicates with the server, a communication state between the first communication unit and the electronic tag, and location information of the mobile terminal. a processing unit that determines whether the mobile body is parked based on the information, and identification information of the mobile body acquired from the electronic tag by the second communication unit when it is determined that the mobile body is parked. The mobile terminal includes a terminal-side communication control unit that causes the server to transmit location information of the mobile terminal.

(9): Another aspect of the present invention is that a computer of a mobile terminal owned by a user of a mobile body and communicating with a server acquires position information of the mobile terminal, and a computer attached to the mobile body communicating with the electronic tag, determining whether or not the mobile object is parked based on the communication state with the electronic tag and position information of the mobile terminal, and when determining that the mobile object is parked; The parking management method includes transmitting identification information of the mobile object acquired from the electronic tag and position information of the mobile terminal to the server.

(10): Another aspect of the present invention is to cause a computer of a mobile terminal owned by a user of a mobile body and communicating with a server to acquire position information of the mobile terminal, and to A case where communication is performed with a tag and whether or not the mobile object is parked is determined based on a communication state with the electronic tag and position information of the mobile terminal, and it is determined that the mobile object is parked. The program causes the server to transmit identification information of the mobile object and position information of the mobile terminal acquired from the electronic tag.

According to the aspects (1) to (10) above, more appropriate parking management of moving objects can be realized.

1 is a diagram showing an example of the configuration of a parking management system 1 according to an embodiment. 1 is a diagram showing an example of the configuration of a vehicle 100 according to an embodiment. FIG. 2 is a diagram illustrating an example of the configuration of a mobile terminal 200 according to an embodiment. It is a diagram showing an example of the configuration of a parking management server 300 according to an embodiment. It is a figure for explaining the contents of user information DB371. FIG. 3 is a diagram for explaining the contents of parking area information 372. It is a figure for explaining the contents of vehicle state DB374. It is a diagram for explaining the contents of a parking usage DB 375. It is a sequence diagram which shows an example of the flow of processing until the vehicle 100 is parked in the parking area. FIG. 3 is a sequence diagram illustrating an example of the flow of processing from when the vehicle 100 is parked in the parking area until the use of the parking area is completed. It is a figure showing an example of image IM10 including parking area information. It is a figure which shows an example of image IM20 which shows the start of parking in a parking area. It is a figure which shows an example of image IM30 which shows the payment information displayed on the display 240 when the use of parking is completed. It is a figure which shows an example of image IM40 for registering a parking area.

DESCRIPTION OF EMBODIMENTS Hereinafter, embodiments of a parking management system, a mobile terminal, a parking management method, and a program of the present invention will be described with reference to the drawings. In the following, a vehicle will be 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. The mobile terminal 200 and the parking management server 300 are communicably connected, for example, via the network NW. 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, for example, a user of the vehicle 100. Parking management server 300 is an example of a "server".

The vehicle 100 is, for example, a saddle-type two-wheeled vehicle that runs on power output according to the operation of an internal combustion engine that runs on fuel such as gasoline, diesel oil, or hydrogen. Further, the vehicle 100 may be an electric two-wheeled vehicle that is driven by an electric motor (an electric motor) driven by electric power supplied by a battery. Examples of the battery include a lithium-ion secondary battery (LIB), a nickel-metal hydride battery, and an all-solid-state battery. Further, the vehicle 100 may be a hybrid vehicle using the above-mentioned internal combustion engine or electric motor as a driving source. An internal combustion engine and an electric motor are examples of power sources mounted on vehicle 100. In the following description, it will be assumed that the vehicle 100 is a saddle-ride type two-wheeled vehicle that runs using power output from the operation of an internal combustion engine using gasoline as fuel. Vehicle 100 communicates with mobile terminal 200 using, for example, an electronic tag 195 (described later) attached to vehicle 100.

The mobile terminal 200 is a terminal device (communication terminal) owned by the user U1. The mobile terminal 200 is, for example, a smartphone or a tablet terminal. Mobile terminal 200 communicates with electronic tag 195 attached to vehicle 100 and parking management server 300 .

Parking management server 300, for example, communicates with mobile terminal 200 and manages the state of vehicle 100. The state is a state related to the use and parking of the vehicle 100. Furthermore, the parking management server 300 may manage position information of the vehicle 100 and the mobile terminal 200. Furthermore, the parking management server 300 may manage registration of parking areas where the vehicle 100 can be parked, provision of information regarding the parking areas, start and end of parking in the parking areas, payment processing of usage fees, and the like. The functions of vehicle 100, mobile terminal 200, and 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 section 110, an engine 115, a switch section 120, a vehicle control section 130, a driving force output device 140, a vehicle sensor 150, an HMI (Human Machine Interface) 160, and an electronic tag 195. The vehicle control unit 130 is realized, for example, by a hardware processor such as a CPU (Central Processing Unit) executing a program (software). Some or all of these components are hardware (circuit parts) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and GPU (Graphics Processing Unit). ), or may be realized by collaboration of software and hardware. The program may be stored in advance in a storage device (a storage device including a non-transitory storage medium) such as an HDD (Hard Disk Drive) or a flash memory included in the vehicle 100, or may be stored in a storage device such as a DVD or CD-ROM. It is stored in a removable storage medium (non-transitory storage medium), and the storage medium may be installed in the HDD or flash memory provided in the vehicle 100 by being attached to a drive device provided in the vehicle 100. .

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 a cylinder, a piston, an intake valve, an exhaust valve, a fuel injection device, a spark plug, a connecting rod, a crankshaft, 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. Further, the switch unit 120 may be a changeover switch that switches between a state in which power is supplied and a state in which power is not supplied to in-vehicle equipment (for example, the vehicle control unit 130, the vehicle sensor 150, and the HMI 160). The above-mentioned changeover switch 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 will be referred to as "the ignition switch is on", and a state in which the engine 115 is stopped will be referred to as "the ignition switch is in the off state". When the ignition switch is in the on state, power may be supplied to the in-vehicle equipment from the on-board battery (not shown), etc., and when the ignition switch is in the off state, power supply to the in-vehicle equipment may be stopped at a predetermined timing. It's okay.

The vehicle control unit 130 acquires the detection results of the vehicle sensor 150. In addition, based on the acquired information, the vehicle control unit 130 controls the driving force output device 140 in response to the user U1's operation on the operator that receives driving operations regarding the steering and speed of the vehicle 100, or by autonomous driving. do. Further, the vehicle control unit 130 may perform control to display the detection result of the vehicle sensor 150 on the HMI 160.

Further, vehicle control unit 130 may determine whether engine 115 has started (or is in operation). For example, the vehicle control unit 130 determines that the engine has started (or is running) when the ignition switch is on, and determines that the engine is not running (or is running) when the ignition switch is off. or stopped). Further, the vehicle control unit 130 may determine that the engine 115 is in operation when the traveling driving force output device 140 receives the motive power output by the engine 115, and the vehicle control unit 130 may determine that the engine 115 is in operation and has not received motive power for a predetermined time or longer. In this case, it may be determined that the engine 115 is stopped. For example, the vehicle control unit 130 causes the HMI 160 to output information regarding the state of the power source. The state of the power source may be, for example, whether the engine 115 is running (started) or not, or may be the state of an ignition switch (on state, off state).

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

The vehicle sensor 150 includes a speed sensor, an acceleration sensor (3-axis G sensor), a rotational speed sensor, an odometer, and a distance sensor (mileage distance from a reset position or reference position) mounted on the vehicle 100. ) and various other sensors. Further, the vehicle sensor 150 may include, for example, an accelerator opening sensor or a brake sensor. The accelerator opening sensor is attached to an operator (for example, an accelerator lever) that receives an acceleration instruction from a driver (user U1). The accelerator opening sensor detects the operating amount of the accelerator lever, and detects the detected operating amount as the accelerator opening. The brake sensor is attached to an operator (eg, a brake lever or a brake pedal) that receives a braking instruction from a driver. The brake sensor detects the amount of operation of a brake lever or brake pedal, and detects the detected amount of operation as the amount of brake depression. Further, the vehicle sensor 150 may include, for example, a throttle opening sensor of the engine 115, a fuel exhaust amount sensor that measures the amount of fuel discharged from the fuel storage section 110, and a suspension stroke sensor. Vehicle sensor 150 outputs detection results from each sensor and the like to vehicle control section 130.

Under the control of the vehicle control unit 130, the HMI 160 outputs various information (for example, information obtained from the vehicle control unit 130, vehicle sensor 150, etc.) to the user U1 of the vehicle 100. Furthermore, the HMI 160 may accept an input operation by the user U1. The HMI 160 includes, for example, various display devices such as a meter display section (which may be a touch panel), a speaker, a microphone, a switch, and the like. The input operation by the occupant includes, for example, a switching operation of an ignition switch. Further, the input operation by the occupant may be a touch input operation using a touch panel or a voice input operation.

The electronic tag 195 is, for example, a non-contact IC tag such as a BLE (Bluetooth (registered trademark) Low Energy) tag or an RFID (Radio Frequency Identifier) tag. The electronic tag 195 is, for example, a small tag that can be attached to the inside of the vehicle 100 and can be replaced. The electronic tag 195 may be incorporated into the configuration of the vehicle 100 during manufacturing, or may be retrofitted after the vehicle 100 is manufactured. The electronic tag 195 may be an active tag that transmits radio waves using power from an internal battery, or a passive tag that operates using electromagnetic waves from a mobile terminal 200 having a reader function as a power source.

For example, the electronic tag 195 transmits radio waves (beacon signals) at predetermined intervals around the position of the electronic tag 195 (for example, within a range of several [meters]), thereby transmitting the electronic tag 195 to surrounding communication devices. can notify the existence of For example, the electronic tag 195 superimposes information including identification information (for example, vehicle ID) for identifying the vehicle 100 stored in an internal memory or the like in advance on the radio waves to be transmitted. When the mobile terminal 200 capable of receiving the radio waves receives the transmitted radio waves, the mobile terminal 200 can recognize that the vehicle 100 having the vehicle ID superimposed on the radio waves is present nearby. In the following, the electronic tag 195 will be described as a BLE tag capable of communication using Bluetooth.

[Mobile terminal 200]
Next, the configuration of the mobile terminal 200 will be explained. 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 section 210, a terminal-side communication control section 220, an input section 230, a display 240, a speaker 250, a terminal position acquisition section 260, and an application execution section 270. , an output control section 280 , and a terminal-side storage section 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 realized by, for example, a hardware processor such as a CPU executing a program (software). Ru. Further, some or all of these components may be realized by hardware (including circuitry) such as LSI, ASIC, FPGA, GPU, etc., or may be realized by collaboration between software and hardware. may be done. The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device equipped with a non-transitory storage medium), or a removable storage medium such as a DVD or CD-ROM (a non-transitory storage medium). It may be installed in the storage device of the mobile terminal 200 by inserting the storage medium into a drive device, a card slot, or the like. The application execution unit 270 is an example of a “processing unit”.

The terminal side storage unit 290 may be realized by the above-mentioned various storage devices, or an SSD (Solid State Drive), an EEPROM (Electrically Erasable Programmable Read Only Memory), a ROM (Read Only Memory), or a RAM (Random Access Memory). For example, a parking app 292, vehicle information 294, a program, and various other information are stored in the terminal side storage unit 290. The vehicle information 294 is information about the vehicle 100 used by the user of the mobile terminal 200. The information about the vehicle 100 is, for example, information about the parking position and parking start date and time of the vehicle 100 transmitted from the parking management server 300. The information about the vehicle 100 may also be information obtained from the electronic tag 195 (for example, a vehicle ID). The terminal side storage unit 290 may also store a user ID when using the parking service provided by the parking management system 1, identification information (terminal ID) of the mobile terminal 200, and the like.

The terminal-side communication unit 210 communicates with the electronic tag 195 attached to the vehicle 100, 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 includes, for example, a first communication unit 212 and a second communication unit 214. The first communication unit 212 has a function capable of communicating with, for example, the electronic tag 195. For example, the first communication unit 212 communicates with the electronic tag 195 present within a predetermined distance by a short-distance communication method such as Bluetooth. For example, if the electronic tag 195 is a passive tag, the first communication unit 212 has a function as a reader that reads information in the electronic tag 195, and transmits electromagnetic waves to operate the electronic tag 195 to operate the electronic tag 195 and read the information in the tag. If the electronic tag 195 is an active tag, the first communication unit 212 receives radio waves transmitted from the electronic tag 195 at a predetermined interval. The first communication unit 212 may also function as a writer that writes information to the internal memory of the electronic tag 195. The second communication unit 214 communicates with the parking management server 300, for example, via the network NW.

The terminal side communication control unit 220 controls transmission and reception by the terminal side communication unit 210. For example, the terminal-side communication control unit 220 receives the vehicle ID from the electronic tag 195 received by the first communication unit 212. Further, the terminal-side communication control unit 220 may manage whether or not the first communication unit 212 is communicating with the electronic tag 195. Further, the terminal side communication control unit 220 receives information from the parking management server 300 received by the second communication unit 214 via the network NW. Further, the terminal side communication control unit 220 causes the second communication unit 214 to transmit information to the parking management server 300. The information transmitted to the parking management server 300 includes, for example, a vehicle ID, a user ID, position information of the mobile terminal 200, and the like. The vehicle ID described above does not need to be included in the transmitted information when not communicating with the electronic tag 195. Further, the transmitted information may include information indicating whether or not the electronic tag 195 and the first communication unit 212 are communicating. Further, the transmitted information may include the terminal ID, destination information input by the user U1 using the parking application 292, and information regarding parking (information indicating the start and end of parking). Further, the transmitted information may include information regarding the amount of operation of the mobile terminal 200 by the user U1. The amount of operation is, for example, the amount of operation based on the number of times the display 240 of the touch panel is touched, the number of times the slide, scroll, swipe, etc. are performed, and the number of characters input. Further, the operation amount may be an amount based on operation time. The above-described functions of the terminal-side communication control unit 220 may be executed only when the parking application 292 is being activated, for example.

The input unit 230 receives input from the user U1 by operating various keys, buttons, etc., for example. The input unit 230 includes, for example, a microphone 232. The microphone 232 receives voice input from the user U1 under the control of the output control unit 280, for example. Input unit 230 may be configured integrally with 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 unit 280. The speaker 250 outputs a predetermined sound, for example, under the control of the output control unit 280.

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

The application execution unit 270 is realized by executing the parking application 292 stored in the terminal storage unit 290. The parking application 292 is, for example, downloaded from an external device via the network NW and installed on the mobile terminal 200. The parking application 292 communicates with the electronic tag 195 attached to the vehicle 100 and uses information obtained from the electronic tag 195, location information of the mobile terminal 200 acquired by the terminal location acquisition unit 260, and the electronic tag 195 and the information acquired from the electronic tag 195. This is an application program that controls the terminal side communication control unit 220 so that information indicating the communication status with the 1 communication unit 212, the start or end of parking of the vehicle 100, etc. is transmitted to the parking management server 300. In addition, the parking application 292 performs user registration and parking area registration in the parking management server 300, information regarding the parking area (parking area) provided by the parking management server 300, usage of parking services, payment information, The output control unit 280 may be controlled to output error information and other various information to the display 240 or from the speaker 250.

Furthermore, 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 second communication unit 214. Furthermore, the parking application 292 may output the position information acquired by the terminal position acquisition unit 260, various information processed by the parking application 292, etc. to the parking management server 300 via the network NW.

The output control unit 280 controls the content and display mode of the image displayed on the display 240 and the content and output mode of the audio output from the speaker 250 under the control of the application execution unit 270. For example, the output control unit 280 may output images and sounds acquired from the parking management server 300 from the display 240 and speakers 250, and generate images and voices based on the information acquired from the parking management server 300. It may also 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 section 310, a server-side communication control section 315, an acquisition section 320, a registration section 330, a management section 340, a provision section 350, and a payment processing section. 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 using a program (software). This is achieved by executing. Some or all of these components may be realized by hardware (including circuitry) such as LSI, ASIC, FPGA, or GPU, or may be realized by collaboration between software and hardware. Good too. The program may be stored in advance in a storage device such as an HDD or a flash memory (a storage device equipped with a non-transitory storage medium) included in the parking management server 300, or may be stored in a removable device such as a DVD or CD-ROM. It is stored in a storage medium (a 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 built into a cloud computing system. In this case, the functions of the parking management server 300 may be realized by a plurality of server devices and storage devices in the cloud computing system.

The server-side storage unit 370 may be realized 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, vehicle status DB 374, parking usage DB 375, programs, and other various information.

The user information DB 371 stores information that identifies users who use the 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. The user information DB 371 includes, for example, address, name, age, gender, contact information, payment information, and mobile terminal information associated with authentication information for authenticating the user when using the service by the parking management system 1. It is something. The authentication information includes, for example, a user ID, a password, etc., which are identification information for identifying a user. Further, the authentication information may include biometric 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. Further, 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 sends and receives various information. Payment information is, for example, information regarding 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). It is. Further, the payment information may include the payment date, whether the payment has been completed, the payment amount, etc. 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 included in the contact information (for example, a telephone number).

The parking area information 372 stores information regarding the parking area of the vehicle 100 registered by the registration unit 330. FIG. 6 is a diagram for explaining the contents of the parking area information 372. 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 information about an address, or information about a part of the address or area. Here, the term "parking area" refers to, for example, not only hourly parking lots and monthly parking lots that are used on a daily basis, such as coin parking lots, but also gardens, fields, and vacant lots in private residential areas. This includes areas where parking is available for private parking, private parking areas of land owners, and parking areas managed by companies, local governments, etc. Furthermore, the parking area may include, for example, an on-street parking area that is used as a parking lot for freight vehicles on weekdays. The available parking period is information regarding the available period of the parking area. The period may include the date, day of the week, time, weekday or holiday type, and the like. The parking fee is information regarding the fee for using the parking area. Parking fees are set, for example, for each predetermined period (for example, minutes, hours, days). Further, the parking fee may include information indicating that the first 30 minutes are free or not charged. By registering a parking area in the parking area information 372, it can be used as a parking area in the parking service of this embodiment.

The map information 373 includes, for example, road information associated with location information, parking area information (for example, parking area, available 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 unit 310 communicating with an external device.

The vehicle status DB 374 stores information regarding the usage status of the vehicle 100 used in the embodiment. FIG. 7 is a diagram for explaining the contents of the vehicle status DB 374. In the vehicle status DB 374, for example, a user ID, vehicle ID, date and time, vehicle location information, terminal location information, and vehicle status are associated with each other. The vehicle ID is a vehicle ID transmitted from the mobile terminal 200 associated with the user ID. The date and time is the date and time when the vehicle ID and the mobile terminal 200 (user ID) are associated with each other, and is the date and time when the vehicle ID and the mobile terminal 200 (user ID) are registered in the vehicle status DB 374. The vehicle position information is position information of the mobile terminal 200 that is stored when the electronic tag 195 and the first communication unit 212 are communicating. The terminal location information is location information of the mobile terminal 200 that is stored regardless of whether or not the electronic tag 195 and the first communication unit 212 are communicating. For example, if the information transmitted from the mobile terminal 200 includes a vehicle ID, or if the information indicating that the electronic tag 195 and the first communication unit 212 are communicating, the vehicle position The location information of the mobile terminal 200 is stored in the information and terminal location information. Furthermore, if the information transmitted from the mobile terminal 200 does not include the vehicle ID, or if the information indicates that the electronic tag 195 and the first communication unit 212 are not communicating, The location information of the mobile terminal 200 is stored only in the terminal location information. The vehicle position information and the terminal position information may be updated with the latest position information, or position information for a predetermined period may be stored as a movement history. The vehicle state is information regarding the state of the vehicle 100 managed by the management unit 340. The vehicle status may include, for example, information such as "running", "parking", and "stopping". The information registered in the vehicle status DB 374 may be deleted after a predetermined period of time has passed since the date and time of registration, or when information from the mobile terminal 200 cannot be received for a predetermined period of time or more.

The parking usage DB 375 stores, for example, a user's usage 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. In the parking usage 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 parking area is the parking position of the vehicle 100, and is the position information of the mobile terminal 200 when it is determined that the vehicle 100 has stopped. The parking time includes a parking start date and time and a parking end date and time. Note that if the use has not ended, information on the parking end date and time is not stored. Further, the parking time may include 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 in the parking area. The usage fee is the fee after the usage ends. As the usage fee, the usage fee up to now may be stored. Various types of information stored in the vehicle status DB 374 and the parking usage DB 375 are managed by the management unit 340, for example.

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

The server-side communication control unit 315 controls communication with the mobile terminal 200 by the server-side communication unit 310. The server-side communication control unit 315 receives, for example, information received by the server-side communication unit 310 from the mobile terminal 200. Further, the server-side communication control unit 315 causes the server-side communication unit 310 to transmit predetermined information to the mobile terminal 200.

The acquisition unit 320 acquires information from the mobile terminal 200. For example, the acquisition unit 320 acquires user registration information, parking area registration information, vehicle ID, user ID, location information of the mobile terminal 200, etc. from the mobile terminal 200. Further, the acquisition unit 320 may acquire information indicating whether or not the electronic tag 195 and the first communication unit 212 are communicating. Further, the acquisition unit 320 may acquire the terminal ID of the mobile terminal 200, the destination information input by the user U1 using the parking application 292, and information regarding parking (information indicating the start and end of parking).

The registration unit 330 registers information regarding 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 causes the user to input various information included in the user information DB 371 shown in FIG. The system generates an image for the user, displays it on the terminal that received the registration request, and obtains information about the user input from the terminal. Then, the registration unit 330 registers the acquired information regarding the user in the user information DB 371.

Furthermore, the registration unit 330 may authenticate users who use the services 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. For example, when receiving a usage request, the registration unit 330 generates an authentication image for inputting authentication information such as a user ID and password, and causes the generated image to be displayed on the display 240 of the mobile terminal 200 that made the request. At the same time, the authentication information in the user information DB 371 is referred to based on the input authentication information input using the displayed image, and service usage is determined depending on whether authentication information matching the input authentication information is stored. Determine whether or not to permit. For example, the registration unit 330 allows the use of the service when the user information DB 371 includes authentication information that matches the input authentication information, and rejects the use of the service when the matching information is not included. Or perform processing to cause new registration.

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

The management unit 340 manages the state of the vehicle 100 based on the location information of the mobile terminal 200 (hereinafter referred to as terminal location information) received by the server-side communication unit 310 and the vehicle ID. Furthermore, the management unit 340 may manage the parking position and parking time of the vehicle 100 based on information obtained from the mobile terminal 200. The management unit 340 may also manage the usage status of the vehicle 100 by the user U1. Furthermore, the parking management server 300 may manage registration of the parking area of the vehicle 100, provision of information regarding the parking area, payment processing for usage fees for the parking area, and the like. Furthermore, the management unit 340 may store, update, or delete information in the vehicle status DB 374 and the parking usage DB 375 based on the management information.

For example, the management unit 340 determines the usage status of the vehicle 100 (or user U1) and the status of the vehicle 100 (for example, "driving" or "parked") based on the vehicle ID, user ID, terminal location information, etc. , "stopped", etc.) and register the estimation result in the vehicle status DB 374. In this case, the management unit 340 determines whether the vehicle is running or stopped based on the movement history of the vehicle position information, for example. For example, the management unit 340 determines that the vehicle 100 is traveling when the first communication unit 212 and the electronic tag 195 are communicating and the terminal position information indicates that the vehicle 100 has moved a predetermined distance or more within a predetermined time. It is determined that Further, the management unit 340 determines that the vehicle 100 is stopped when the first communication unit 212 and the electronic tag 195 are communicating and the terminal position information indicates that the vehicle 100 has not moved more than a predetermined distance within a predetermined time. It is determined that Furthermore, the management unit 340 may estimate the moving speed of the vehicle 100 based on the terminal position information, and determine that the vehicle 100 is stopped when the moving speed is less than a predetermined speed. Furthermore, the management unit 340 determines that the vehicle 100 is parked when the first communication unit 212 and the electronic tag 195 change from communicating to not communicating. Furthermore, the management unit 340 determines that the vehicle 100 is parked when the position at which the vehicle 100 is determined to be stopped is the parking position, and the distance between the parking position and the terminal position is a predetermined distance or more. You may.

Furthermore, if the information transmitted from the mobile terminal 200 includes information regarding the amount of operation of the mobile terminal 200 and the amount of operation is equal to or greater than a predetermined amount, the management unit 340 determines that the vehicle 100 is parked. It may be determined that When the vehicle 100 is running or stopped, operations on the mobile terminal 200 are not possible or the amount of operations is reduced. It can be determined that Note that the management unit 340 may determine the state of the vehicle 100 by combining the above-mentioned conditions. In addition, the management unit 340 determines that parking of the vehicle 100 has started when acquiring information indicating that the user has pressed a button or the like that accepts the start of parking displayed on the display 240 of the mobile terminal 200. You may.

Furthermore, when the first communication unit 212 and the electronic tag 195 are in communication after the parking of the vehicle 100 has started, the management unit 340 controls the location of the vehicle 100 based on the position information of the mobile terminal 200. Manage the termination of parking. Whether or not the first communication unit 212 and the electronic tag 195 are in a state of communication depends on whether or not the vehicle ID is included in the information acquired from the mobile terminal 200, and the state in which they are communicating. This can be determined based on whether or not information indicating this is included. Furthermore, the management unit 340 acquires information on one or both of the moving speed and the moving distance of the vehicle 100 based on the position information of the mobile terminal 200, and determines whether parking of the vehicle 100 is finished based on the acquired information. It's okay. For example, if the first communication unit 212 and the electronic tag 195 are communicating and the moving speed based on the terminal position information is a predetermined speed or higher, or if the terminal position is different from the parking position. If the vehicle has moved a predetermined distance or more, it is determined that parking has been completed. In addition, the management unit 340 determines that parking of the vehicle 100 has been completed when acquiring information indicating that the user has pressed a button or the like that accepts the termination of parking displayed on the display 240 of the mobile terminal 200. You may. Note that if the determination is made using only the press of the button, the user may determine that the parking has been completed illegally. Therefore, the management unit 340 can perform a more accurate parking completion determination by combining the above-mentioned various other determination processes.

The providing unit 350 provides the user U1 with information regarding the parking area, usage fees, etc. of the embodiment. For example, the providing unit 350 refers to the parking area information 372 based on the vehicle location information, and extracts information regarding parking areas existing within a predetermined distance from the location information. Then, the providing unit 350 transmits information regarding the extracted parking area, available parking period, and parking fee to the mobile terminal 200. Further, the providing unit 350 may transmit the parking time, usage fee, payment information, etc. to the mobile terminal 200 of the user who used the parking area. Further, the providing unit 350 may transmit information regarding the amount of money that the registrant obtains by using the parking area of the vehicle 100 to the terminal of the registrant who has registered the parking area. The providing unit 350 may generate an image for displaying each of the above-mentioned information on the display 240 of the mobile terminal 200, or may generate and provide information for causing the mobile terminal 200 to generate an image. . Further, the providing unit 350 may generate and provide audio data for outputting at least part of the above-mentioned information as audio.

The payment processing unit 360 refers to the parking usage DB 375 at a predetermined period or at a predetermined timing, calculates the total usage fee for each user, and performs payment 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 obtains the parking fee. Further, the payment processing unit 360 calculates the usage fee based on the parking time and the parking fee. Further, the payment processing unit 360 refers to the payment information registered in the user information DB 371 and performs payment processing for the usage fee using the payment method included in the payment information. Note that, at the time when the usage fee is calculated, the payment processing unit 360 notifies the user of the usage fee, etc. through the providing unit 350, and performs the payment based on the instructed payment method before completing the payment. Good too. The processing result by the payment processing unit 360 may be registered, for example, in the payment information of the user information DB 371.

[Flow of parking service using parking management system 1]
Next, the flow of the parking service by the parking management system 1 of the embodiment will be specifically explained. In the following, the process will be roughly divided into the process until the vehicle 100 is parked in the parking area, and the process from the time the vehicle 100 is parked until the end of use of the parking area. Further, in the following description, it is assumed that the parking area has been registered by the registration unit 330.

[Processing until vehicle 100 is parked in the parking area]
FIG. 9 is a sequence diagram showing an example of the flow of processing until the vehicle 100 is parked in the parking area. The example in FIG. 9 shows processing in the vehicle 100, the mobile terminal 200, and the parking management server 300. In the example of FIG. 9, the mobile terminal 200 starts the parking application 292 (step S100). In the process of step S100, the user authentication process may be executed simultaneously with the activation of the parking application 292. In the following description, it is assumed that the user authentication has been successful (the use of the parking service has been permitted). When the parking application 292 is activated, the terminal-side communication control unit 220 transmits the terminal position information acquired by the terminal position acquisition unit 260 to the parking management server 300 (step S102). The process of step S102 may be repeatedly executed at a predetermined period or at a predetermined timing while the parking application 292 is activated.

Next, the electronic tag 195 attached to the vehicle 100 transmits a radio wave (beacon signal) containing the vehicle ID to the surrounding area (step S104). When the mobile terminal 200 is within the range of the radio waves transmitted by the electronic tag 195, the mobile terminal 200 receives the transmitted radio waves (step S106), and acquires the vehicle ID from the received radio waves (step S108). Next, the terminal-side communication control unit 220 transmits, for example, the vehicle ID, user ID, and terminal position information to the parking management server 300 (step S110). The process of step S110 may be repeatedly executed at a predetermined period or at a predetermined timing while the parking application 292 is activated.

The management unit 340 of the parking management server 300 receives the vehicle ID, user ID, and terminal location information transmitted from the mobile terminal 200, stores them in the vehicle status DB 374, and manages the usage status of the vehicle 100 ( Step S112). Since the information transmitted in the process of step S110 includes the vehicle ID, the management unit 340 also stores the terminal location information in the vehicle status DB 374, and uses the terminal location information as the vehicle location information. to manage. In addition, in the process of step S112, the management unit 340 estimates the state of the vehicle 100 based on the movement history based on the terminal location information and the vehicle location information, stores the estimated state in the vehicle state of the vehicle state DB 374, and stores the estimated state in the vehicle state of the vehicle state DB 374. Good too.

Next, the providing unit 350 searches for a parking area based on, for example, the terminal location information (step S114). In the process of step S114, the providing unit 350 refers to the parking area information 372 or the map information 373 based on the terminal location information, and provides parking information that exists within a predetermined distance from the terminal location and is within the available parking period. Extract the area. Further, the providing unit 350 may extract parking areas where parking is possible based on the usage status of the parking area (vacancy status and parking space). Further, the providing unit 350 may preferentially extract a parking area that exists in the direction of movement of the mobile terminal 200 (or vehicle 100) over a parking area that exists in a direction different from the direction of movement (for example, in the opposite direction). . Note that in the process of step S114, if destination information is received from the mobile terminal 200, the destination information is used instead of the terminal location information to extract parking areas where parking is available around the destination. Good too. The providing unit 350 transmits information regarding the extracted parking area (eg, parking area, available parking period, parking fee) to the mobile terminal 200 (step S116).

The parking application 292 of the mobile terminal 200 causes the display 240 to display an image including parking area information (step S118). The processes from step S110 to step S118 may be repeatedly executed, for example, until the parking application 292 is terminated.

The vehicle 100 travels to a destination etc. by the operation of the user U1 (step S120) and stops at a parking area (step S122). During the movement described above, the mobile terminal 200 transmits information to the parking management server 300 at a predetermined period or at a predetermined timing, similar to the process in step S110. Therefore, the management unit 340 of the parking management server 300 can manage the state of the vehicle 100 (for example, "running" or "stopping") based on the movement history of the terminal position information and the like. Note that in the process of step S122, the management unit 340 may transmit information regarding the state of the vehicle to the mobile terminal 200.

Next, the parking application 292 of the mobile terminal 200 determines that the vehicle 100 is parked when, for example, the first communication unit 212 and the electronic tag 195 are unable to communicate (step S124), and the parking application 292 of the mobile terminal 200 determines that the vehicle 100 is parked and and transmits the terminal position information to the parking management server 300 (step S126). Note that in the process of step S126, the parking application 292 may transmit information indicating that communication with the electronic tag 195 has become impossible, in addition to the above information. Furthermore, when the parking application 292 is unable to communicate with the electronic tag 195, the parking application 292 may send information indicating the start of parking (for example, information that the current time is the parking start time) to the parking management server 300. .

In addition, instead of the processing of steps S124 to S126 described above, when user U1 performs an operation on the mobile terminal 200 indicating the start of parking (for example, pressing a parking start button), the mobile terminal 200 may transmit information indicating the start of parking to the parking management server 300, and the parking management server 300 that receives the information may manage the usage status, etc.

The parking management server 300 receives the information transmitted from the mobile terminal 200, recognizes that the vehicle 100 is parked based on the received information, and stores the user ID, vehicle ID, parking area (parking position), Parking management is performed by registering the parking start date and time in the parking usage DB 375 (step S128). Furthermore, information indicating the parking position, parking start date and time, etc. is transmitted to the mobile terminal 200 (step S130).

The mobile terminal 200 stores information indicating the parking position, parking start date and time, etc. of the vehicle 100 in the terminal side storage unit 290 as vehicle information 294 (step S132), and displays an image indicating the parking position, parking start date and time, etc. on the display 240. (Step S134). The information indicating the parking position of the vehicle 100, the parking start date and time, etc. may be acquired by the parking application 292 of the mobile terminal 200 instead of being provided by the parking management server 300. In this case, the parking application 292 sets the terminal position information among the information transmitted in the process of step S126 as the parking position, and sets the transmission date and time as the parking start time and time. Thereby, it is possible for the user U1 to accurately understand 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 a coin parking lot, but also in a parking area that can only be used temporarily for a limited period of time, such as a residential lot. Since there are no entrance/exit gates, parking meters, or other facilities in the parking area that can only be used temporarily, there is a possibility that user U1 may be concerned about whether or not he or she is able to park the vehicle 100 in the correct parking area. . Therefore, by presenting the parking position and parking start date and time to the user through the process of step S134, it is possible to give the user a greater sense of security.

[Processing from when the car is parked until the end of parking use]
FIG. 10 is a sequence diagram showing an example of the flow of processing from when the vehicle 100 is parked in the parking area until the use of the parking area ends. Even after parking of the vehicle 100 is started, the mobile terminal 200 transmits the user ID and terminal position information to the parking management server 300 at a predetermined period or at a predetermined timing (step S200). The electronic tag 195 attached to the vehicle 100 transmits radio waves containing the vehicle ID to the surroundings (step S202). When the mobile terminal 200 is within the range of the radio waves transmitted by the electronic tag 195, the mobile terminal 200 receives the transmitted radio waves (step S204), and acquires the vehicle ID from the received radio waves (step S206). Next, the terminal side communication control unit 220 transmits, for example, the vehicle ID, the user ID, and the terminal position information to the parking management server 300 (step S208). The process of step S208 may be repeatedly executed at a predetermined period or at a predetermined timing while the parking application 292 is activated.

When the management unit 340 of the parking management server 300 receives the vehicle ID, user ID, and terminal location information transmitted from the mobile terminal 200, the management unit 340 determines that the user U1 is within a predetermined distance from the parking location. As such, the vehicle status DB 374 and parking usage DB 375 are updated to manage usage status (step S210). For example, if the usage status is "parked" and the vehicle ID is included in the information received from the mobile terminal 200, the usage status in the parking usage DB 375 is updated assuming that the user U1 has returned to the vehicle 100.

Next, the management unit 340 determines the end of parking based on the terminal position information and movement history transmitted from the mobile terminal 200 (step S212). For example, when the mobile terminal 200 is determined to be parked and the electronic tag 195 and the first communication unit 212 are communicating, the management unit 340 determines that the moving distance of the mobile terminal 200 is a predetermined distance based on the terminal position information. If the distance is greater than or equal to the distance, it is determined that parking of the vehicle 100 has been completed. Furthermore, the management unit 340 may determine that parking of the vehicle 100 has ended when the moving speed of the vehicle 100 based on the terminal position information is equal to or higher than a predetermined speed. Furthermore, the management unit 340 may determine that parking of the vehicle 100 is completed when the above-mentioned moving distance is a predetermined distance or more and the moving speed is a predetermined speed or more. Furthermore, the management unit 340 may determine that parking of the vehicle 100 has ended when the terminal position is a predetermined distance or more from the parking position of the vehicle 100.

In addition, instead of the processing in steps S200 to S210 described above, when the user U1 performs an operation on the mobile terminal 200 that indicates the end of parking (for example, pressing a parking end button), the mobile terminal 200 indicates the end of parking. The information etc. shown may be transmitted to the parking management server 300, and the usage status etc. may be managed on the receiving parking management server 300 side. Note that if the determination is made using only button presses, the user may assume that parking has been completed illegally, so the management unit 340 may combine the above-mentioned various other determination processes. Further, the process of step S212 may be performed by the parking application 292 of the mobile terminal 200 instead of the management unit 340. If it is determined that parking has ended, the management unit 340 updates the vehicle status DB 374 and the parking usage DB 375 to manage the usage status.

Next, the payment processing unit 360 executes payment processing regarding the use of the parking area (step S214). Next, the providing unit 350 transmits the payment result etc. to the mobile terminal 200 (step S216).

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

[Information notified to users by mobile devices]
Next, various types of information notified to the user U1 by the mobile terminal 200 in a series of processing of the parking service by the parking management system 1 described above will be explained. FIG. 11 is a diagram showing an example of an image IM10 including parking area information. Image IM10 is, for example, an image displayed on display 240 through the process of step S118. The image IM10 includes, for example, a map image IM11, a position specifying image IM12, a parking area image IM13, and a parking information image IM14.

The map image IM11 is, for example, map information within a predetermined distance range from a reference position included in the map information 373. The reference position may be, for example, the position of the vehicle 100 or the position information of the destination. In the following description, the reference position is assumed to be the position of the vehicle 100. In the example of FIG. 11, a position identification image IM12 associated with the vehicle position information is displayed at a position associated with coordinates (map coordinates) on the map image.

The parking area image IM13 is an image that is referenced from the parking area information 372 based on the vehicle position information and shows a parking area that exists within a predetermined distance from the vehicle parking position. In the example of FIG. 11, images IM13a to IM13c showing three parking areas are displayed superimposed on the map image IM11. Note that the images IM13a to IM13c may be displayed superimposed on the map image IM11 by being transmitted through the map image IM11 at a predetermined transmittance. Furthermore, the parking area images IM13a to IM13c may be displayed in different display modes. The display mode includes, for example, color, pattern, gradation, shape, transmittance, presence or absence of blinking, etc. For example, the parking application 292 may change the display mode depending on the parking period, parking fee, etc.

The parking information image IM14 is an image including text information related to the parking period and parking fee stored in the parking area information 372. The parking information image IM14 is displayed superimposed at a position corresponding to the display position of the parking area image IM13. In the example of FIG. 11, the parking information images IM14a to IM14c are displayed at positions corresponding to the display positions of the parking area images IM13a to IM13c, respectively. When the user U1 selects (e.g., taps) the display position of one of the parking area images IM13a to IM13c displayed on the display 240, the parking app 292 may display parking information associated with the parking area of the selected parking area image IM13. The parking app 292 may also output audio information corresponding to the parking information from the speaker 250.

By displaying image IM10, user U1 can be made aware of information regarding parking areas. Furthermore, according to this embodiment, user U1 can be made aware that areas within private premises that are not routinely used as parking areas, fields, areas managed by companies or local governments where parking is permitted, etc., can be used as parking spaces.

FIG. 12 is a diagram showing an example of an image IM20 showing the start of parking in the parking area. Image IM20 is, for example, an image displayed on display 240 through the process of step S134 described above. The image IM20 includes, for example, a usage information display area AR21, a detailed information display area AR22, and a switch display area AR23 as a parking information screen. Information (for example, text) indicating that parking of the vehicle 100 in the parking area has started is displayed in the usage information display area AR21. Detailed information regarding parking is displayed in the detailed information display area AR22. 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 regarding the parking fee for the parking area. It will be done. The switch display area AR23 includes, for example, an icon IC21. The icon IC21 is a GUI switch that accepts a request to end the display of the image IM20. By displaying image IM20, it is possible to make it easier for occupant U1 to understand that vehicle 100 is correctly parked in a regular parking area. In the embodiment, areas that are not routinely used as parking areas are also provided as parking areas, so there may be no facilities such as entrance/exit gates or parking meters. Therefore, by displaying the image IM20 shown in FIG. 12, the user U1 can be made aware that the vehicle 100 is parked in a legal parking area, and the user U1 can safely leave the vehicle 100 and move. be able to.

FIG. 13 is a diagram showing an example of an image IM30 showing payment information displayed on the display 240 when the use of parking is completed. Image IM30 is, for example, an image displayed on display 240 in step S218 described above. Image IM30 includes, for example, a usage status display area AR31, a usage result display area AR32, and a switch display area AR33.

In the usage status display area AR31, information (for example, text) indicating that the use of parking the vehicle 100 in the parking area has ended is displayed. Detailed information regarding the used parking is displayed in the usage result display area AR32. The usage result display area AR32 includes, for example, a user ID, a vehicle ID, a parking area, and a usage fee. Further, the usage result display area AR32 may include information regarding parking time.

The switch display area AR33 includes, for example, an icon IC31 and an icon IC32. The icon IC31 is a switch that allows the user to accept payment using the payment method registered in the user information DB 371. The icon IC32 is a switch for settling the usage fee using a method other than the registered payment method. When the icon IC31 is selected, the usage fee is paid using the registered payment method (for example, credit card payment). When the icon IC32 is selected, another payment method (for example, electronic payment) is accepted by the user, and the usage fee is paid using the accepted payment method.

By displaying the image IM30 and notifying the user U1, it is possible to make it easier for the user U1 to understand the end of parking. Furthermore, by displaying the image IM30, the user U1 can more smoothly perform the process up to payment for the use of the parking service.

Note that the parking application 292 may display an image on the display 240 for the registrant to register the parking area. In this case, the registrant registers the parking area by activating the parking application 292 installed on the terminal device owned by the registrant, displaying a parking area registration screen, and inputting various information. For example, the same configuration as the mobile terminal 200 can be applied to the terminal device owned by the registrant.

FIG. 14 is a diagram showing an example of an image IM40 for registering a parking area. Image IM40 includes, for example, a registration information display area AR41 and a switch display area AR42 as a parking area registration screen. The registration information display area AR41 includes, for example, a registrant ID input area AR41a, a parking area input area AR41b, a parking period input area AR41c to AR41e, and a parking fee input area AR41f. The registrant ID input area AR41a is an area where identification information for identifying a registrant is input. The parking area input area AR41b is an area for specifying a parking area used in the parking service of the embodiment. The registered information display area AR41 includes an icon IC41 for specifying an address and an icon IC42 for estimating an area. When the icon IC41 is selected, an image for selecting an address is displayed, and address information input using the image is input into the parking area input area AR41b. When the icon IC42 is selected, map information etc. are displayed, and when the range specification by the registrant is accepted, information regarding the parking area corresponding to the range (for example, latitude and longitude information) is input into the parking area input area AR41b. be done.

The available parking period input area AR41c accepts input of dates, cycles, and the like. The available parking period input area AR41d accepts input of the start time of the available parking period. The available parking period input area AR41e accepts input of the end time of the available parking period. The parking fee input area AR41f accepts input of usage fees. In the example of FIG. 14, the available parking period input area AR41c and the parking fee input area AR41f are, for example, combo boxes (drop-down lists) from which one can be selected from a plurality of selection candidates, but the available parking period input area AR41d , AR41e and may be a combo box.

The switch display area A42 includes, for example, an icon IC43 and an icon IC44. The icon IC43 is a GUI switch that accepts an instruction 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 AR41. The icon IC44 is a GUI switch that accepts ending the display of the image IM40 without performing the parking area registration process. In the example of FIG. 14, when the selection of the icon IC41 is accepted, the mobile terminal 200 transmits the information input in the registration information display area AR41 to the parking management server 300. The registration unit 330 of the parking management server 300 registers the received information in the parking area information 372. Note that the registration unit 330 may determine whether the registered parking area can be used as a parking area with the authority of the registrant. In this case, the registration unit 330, for example, accesses the external device via the network NW to acquire registry information, and if the registrant is the owner of the land that includes the parking area, the registration unit 330 can use the land as a parking area. Determine that it is possible. In addition, the registration unit 330 stores in advance information regarding land owned by the registrant (registrant information) in the server side storage unit 370, and some or all of the land registered in the registrant information is used as a parking area. If a registration request is made, it may be determined that the area can be used as a parking area.

By displaying the image IM40, the registrant can smoothly register the parking area. Furthermore, it is possible to allow the registrant to effectively utilize unused land, etc. as a parking area.

[Modified example]
In the parking management system 1 of the embodiment, for example, the radio waves emitted from the electronic tag 195 attached to the vehicle 100 are owned by a person other than the user U1 (hereinafter referred to as a third party) who exists within the radio wave range. It can also be received by a mobile terminal (specifically, a mobile terminal on which the parking application 292 installed on the terminal is running). In this case, the parking application 292 of a mobile terminal owned by a third party may transmit the vehicle ID included in the radio wave, and the user ID and terminal location information associated with the mobile terminal to the parking management server 300. . Since the parking management server 300 does not directly communicate with the vehicle 100, by acquiring vehicle ID information from a third party, it can detect that the vehicle 100 associated with the vehicle ID is parked in the parking area. This allows for more accurate understanding and management. Note that the user ID transmitted from the third party's mobile terminal 200 is different from the user ID associated with the vehicle ID in the vehicle status DB 374 and the parking usage DB 375. Therefore, the management unit 340 refers to the vehicle status DB 374 or the parking usage DB 375 based on the vehicle ID and user ID included in the received information, and determines whether the received information is information from the user U1. It is possible to accurately determine whether the information is from a third party.

Furthermore, the parking application 292 of the third party's mobile terminal determines whether the vehicle 100 parked in the parking area is a legitimate vehicle (managed by the parking management server 300) based on information acquired through communication with the electronic tag 195. The parking management server 300 may be inquired as to whether or not the vehicle is a vehicle. Thereby, a third party near the vehicle 100 can more accurately recognize that the parked vehicle 100 is a legally parked vehicle managed by the parking management server 300.

Further, in the parking management system 1 described above, at least a part of each function provided in each of the mobile terminal 200 and the parking management server 300 may be provided in another device. For example, 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 may be executed by the management unit 340. Good too.

The embodiment described above includes, for example, a vehicle (an example of a moving object), a mobile terminal 200 of a user U1 of the vehicle 100, a parking management server (an example of a server) that communicates with the vehicle 100 and the mobile terminal 200, In the parking management system 1, the mobile terminal 200 includes a terminal position acquisition unit 260 that acquires the position of the mobile terminal 200, a first communication unit 212 that communicates with the electronic tag 195 attached to the vehicle 100, and a parking management system 1. When it is determined that the vehicle 100 is parked based on the communication state between the second communication unit 214 that communicates with the server 300, the first communication unit 212, and the electronic tag 195 and the position information of the mobile terminal 200, The parking management server 300 includes a terminal side communication control unit 220 that causes the second communication unit 214 to transmit the identification information of the vehicle 100 acquired from the electronic tag 195 and the position information of the mobile terminal 200 to the parking management server 300. a server-side communication unit 310 that communicates with the mobile terminal 200; and a management unit that manages parking of the vehicle 100 based on the identification information of the vehicle 100 and the position information of the mobile terminal 200 received from the mobile terminal 200 by the server-side communication unit 310. 340, it is possible to realize more appropriate parking management for moving objects.

Specifically, according to the embodiment, even if the vehicle 100 is not equipped with a communication device such as a TCU (Telematics Control Unit), it is possible to communicate with the mobile terminal 200 using the electronic tag 195. , the state of the vehicle 100 can be appropriately managed based on the position information of the mobile terminal 200. In the embodiment, since the identification information of the vehicle 100 is stored in the electronic tag 195, the identification information is transmitted to the mobile terminal 200 using a short-range communication method, and the identification information and location information of the mobile terminal 200 are transmitted from the mobile terminal 200 to the mobile terminal 200. By transmitting the information to the parking management server 300, the parking management server 300 can be made to know that the mobile terminal 200 and the vehicle 100 are located in the vicinity. Furthermore, the parking management server 300 can manage the status of the vehicle 100 (for example, parking, stopping, and running) based on the location information of the mobile terminal 200, thereby realizing more appropriate parking management of the vehicle 100. be able to. Further, according to the present embodiment, there is no need to mount a communication device such as a TCU on the vehicle 100, and parking management can be performed using an inexpensive vehicle 100. Further, according to the embodiment, an area without facilities such as an entrance/exit gate or a parking meter can also be used as a parking area. Therefore, parking services can be provided at lower cost.

The embodiment described above can be expressed as follows.
A mobile terminal computer owned by a mobile user and communicating with a server is
a storage device that stores the program;
comprising a hardware processor;
By the hardware processor executing a program stored in the storage device,
Obtaining location information of the mobile terminal,
communicating with an electronic tag attached to the mobile object;
Determining whether the mobile object is parked based on the communication state with the electronic tag and the position information of the mobile terminal,
If it is determined that the mobile object is parked, transmitting identification information of the mobile object acquired from the electronic tag and position information of the mobile terminal to the server;
A mobile device configured as follows.

Although the mode for implementing the present invention has been described above using embodiments, the present invention is not limited to these embodiments in any way, and various modifications and substitutions can be made without departing from the gist of the present invention. can be added.

DESCRIPTION OF SYMBOLS 1...Parking management system, 100...Vehicle, 110...Fuel storage unit, 115...Engine, 120...Switch unit, 130...Vehicle control unit, 140...Travel driving force output device, 150...Vehicle sensor, 160...HMI, 195... Electronic tag, 200... Mobile terminal, 210... Terminal side communication unit, 212... First communication unit, 214... Second 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 Department, 330...Registration Department, 340...Management Department, 350...Providing Department, 360...Payment Processing Department, 370...Server Side Storage Department

Claims (9)

A mobile terminal of a user of a mobile body, comprising: a terminal position acquisition unit that acquires position information; a first communication unit that communicates with an electronic tag attached to the mobile body; and a second communication unit that communicates with a server; and the second communication unit uses the identification information of the mobile object and the position information of the mobile terminal acquired from the electronic tag by the first communication unit as information for managing parking of the mobile unit. A server that communicates with a mobile terminal having a terminal-side communication control unit that transmits data to the server,
a server-side communication unit that communicates with the mobile terminal;
a management unit that manages parking of the mobile body based on identification information of the mobile body and position information of the mobile terminal received from the mobile terminal by the server-side communication unit,
The terminal side communication control unit transmits information regarding the operation amount of the mobile terminal operated by the user to the server using the second communication unit,
The operation amount is an operation amount based on the number of times the mobile terminal is touched, slid, scrolled, or swiped, the number of input characters, or an amount based on the operation time,
The management unit determines that the mobile object is parked when the amount of operation of the mobile terminal is equal to or greater than a predetermined amount.
server. The server includes a registration unit that registers a parking area where the mobile object can be parked;
A providing unit that provides the mobile terminal with a parking area for the mobile body that exists within a predetermined distance from the position information of the mobile terminal, among the parking areas registered by the registration unit, based on the position information of the mobile body. and further comprising,
The server according to claim 1. The terminal-side communication control unit controls the movement when the first communication unit and the electronic tag change from a state in which they are communicating to a state in which the first communication unit and the electronic tag do not communicate. sending information to the server indicating that parking of the body has begun;
The server according to claim 1 or 2. The management unit is configured to control the movement of the mobile object based on the position information of the mobile terminal when the first communication unit and the electronic tag are in communication after the mobile object starts parking. Manage the termination of body parking,
The server according to any one of claims 1 to 3. The management unit acquires information on one or both of a moving speed and a moving distance of the mobile object based on the position information of the mobile terminal, and determines whether parking of the mobile object is completed based on the acquired information. do,
The server according to claim 4. The providing unit provides the mobile terminal with information regarding the start or end of parking of the mobile object in the parking area.
The server according to claim 2. A mobile terminal owned by a mobile user and communicating with a server,
a terminal location acquisition unit that acquires location information of the mobile terminal;
a first communication unit that communicates with an electronic tag attached to the mobile object;
a second communication unit that communicates with the server;
a processing unit that determines whether the mobile object is parked based on a communication state between the first communication unit and the electronic tag and position information of the mobile terminal;
When it is determined that the mobile object is parked, the first communication unit collects the identification information of the mobile object acquired from the electronic tag , the position information of the mobile terminal , and the mobile terminal operated by the user. a terminal-side communication control unit that uses the second communication unit to transmit information regarding the amount of operation including an amount corresponding to the number of operations or operation time of the terminal to the server as information for managing parking of the mobile object; and,
Equipped with
The operation amount is an operation amount based on the number of times the mobile terminal is touched, slid, scrolled, or swiped, the number of input characters, or an amount based on the operation time.
Mobile device. A mobile terminal computer owned by a mobile user and communicating with a server is
Obtaining location information of the mobile terminal,
communicating with an electronic tag attached to the mobile object;
The identification information of the mobile object acquired from the electronic tag , the position information of the mobile terminal , and the information regarding the amount of operation of the mobile terminal by the user are used as information for managing parking of the mobile object. and send it to said server as
The operation amount includes the number of times the mobile terminal is touched, slid, scrolled, or swiped, an operation amount based on the number of input characters, or an amount based on the operation time.
Parking management method. A computer on a mobile terminal owned by a mobile user and communicating with the server,
obtain location information of the mobile terminal;
communicating with an electronic tag attached to the mobile object;
The identification information of the mobile object acquired from the electronic tag , the position information of the mobile terminal, and the information regarding the amount of operation of the mobile terminal by the user are used as information for managing parking of the mobile object. cause the server to send
The operation amount includes the number of times the mobile terminal is touched, slid, scrolled, or swiped, an operation amount based on the number of input characters, or an amount based on the operation time.
program.

Images