Information processing device

The information processing device estimates parking demand at a user's destination by analyzing location history and applying a logistic function, addressing the limitations of existing methods by accurately accounting for on-street parking demand.

WO2025238826A1PCT designated stage Publication Date: 2025-11-20NTT DOCOMO INC

Patent Information

Application Number
PCT/JP2024/018248
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-05-17
Publication Date
2025-11-20

AI Technical Summary

Technical Problem

Existing methods fail to accurately estimate parking demand at a user's destination when the user parks away from the destination, as they rely solely on the usage status of nearby parking lots, neglecting potential demand at the actual destination.

Method used

An information processing device that estimates user destinations based on location history and calculates parking demand using a logistic function, considering both on-street and existing parking lots, with a server device that includes a location information acquisition unit, estimation unit, identification unit, and calculation unit to determine parking demand.

Benefits of technology

Accurately estimates parking demand at a user's destination, accounting for on-street parking and providing precise demand calculations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024018248_20112025_PF_FP_ABST
    Figure JP2024018248_20112025_PF_FP_ABST
Patent Text Reader

Abstract

An estimation unit 24 estimates a user who performed a parking action on the basis of the user's history of location information. Specifically, on the basis of histories of location information of users, the estimation unit 24 determines whether the users' means of transportation were by vehicle, walking, or other means, and estimates a user who changed the user's means of transportation from vehicle to walking as the user who performed a parking action. An identification unit 25 identifies the location of a destination that the user estimated by the estimation unit 24 visited after the parking action. Specifically, on the basis of a history of location information of the user, the identification unit 25 identifies a location where the user stayed for a time exceeding a threshold as the location of a destination visited by the user. A calculation unit 26 calculates the amount of parking demand for a target section on the basis of the locations of destinations visited by a plurality of users as identified by the identification unit 25. An output unit 27 outputs information about the amount of demand calculated by the calculation unit 26 externally.
Need to check novelty before this filing date? Find Prior Art

Description

Information processing device

[0001] The present invention relates to techniques for estimating demand for parking.

[0002] When constructing a new parking lot, it is preferable to construct it in a location where there is a high demand for parking (hereinafter referred to as parking demand). For example, parking demand in a certain location can be roughly estimated based on the usage status of existing parking lots in the vicinity. Patent Document 1 discloses a method for analyzing demand for parking lots other than the multiple parking lots within the specified range by identifying the parking locations of parked vehicles within a specified range and the locations of multiple parking lots within the specified range, and estimating whether vehicles not parked in the parking lot have the potential to use one of the multiple parking lots.

[0003] Japanese Patent Application Laid-Open No. 2022-34172

[0004] However, when a user travels to a destination by vehicle, it is not always possible to park the vehicle at the destination, and the user may have to park the vehicle at a location different from the destination but close to it. In such cases, it should be considered that there is parking demand at the user's original destination, rather than at the location where the user actually parked.

[0005] In view of the above background, an object of the present invention is to accurately estimate parking demand.

[0006] In order to solve the above problem, the present invention provides an information processing device comprising an estimation unit that estimates the user who performed the parking act based on the user's location information history, an identification unit that identifies the locations of destinations visited by the estimated user after the parking act, and a calculation unit that calculates the parking demand in a target area based on the locations of the destinations identified for multiple users.

[0007] According to the present invention, parking demand can be estimated with high accuracy.

[0008] FIG. 1 is a block diagram showing an example of the configuration of an information processing system 1 according to an embodiment of the present invention. FIG. 2 is a block diagram showing an example of the hardware configuration of a server device 20 according to the embodiment. FIG. 3 is a block diagram showing an example of the functional configuration of the server device 20. FIG. 4 is a diagram illustrating an example of information stored in the server device 20. FIG. 5 is a flowchart showing an example of the operation of the server device 20. FIG. 6 is a diagram illustrating an example of information stored in the server device 20. FIG. 7 is a diagram explaining the content of processing of the server device 20. FIG. 8 is a diagram explaining the content of processing of the server device 20.

[0009] [Embodiment] [Configuration] FIG. 1 is a diagram illustrating an example of the configuration of an information processing system 1 according to an embodiment of the present invention. The information processing system 1 includes multiple user terminals 10 each carried by a user who drives a vehicle, a server device 20 corresponding to the information processing device of the present invention, and a communication network 2 including a wireless communication network that communicatively connects these terminals. The user terminals 10 are wirelessly communicable computers such as smartphones, wearable devices, or tablets. The server device 20 considers the location of the user terminal 10 carried by the user as the user's location, estimates the user who parked the vehicle based on the location history, identifies the locations of destinations visited by the user after parking the vehicle, and calculates parking demand based on the locations of the identified destinations. The server device 20 may be composed of a single computer or multiple computers.

[0010] FIG. 2 is a diagram showing the hardware configuration of the server device 20. The server device 20 is physically configured as a computer including a processor 2001, a memory 2002, a storage 2003, a communication device 2004, an input device 2005, an output device 2006, and a bus connecting these devices. Each of these devices operates using power supplied from a battery (not shown). In the following description, the term "device" can be interpreted as a circuit, a device, a unit, or the like. The hardware configuration of the server device 20 may be configured to include one or more of the devices shown in FIG. 2, or may be configured without including some of the devices. Furthermore, the server device 20 may be configured by communicating with multiple devices each having a different housing.

[0011] Each function in the server device 20 is realized by loading specified software (programs) onto hardware such as the processor 2001 and memory 2002, causing the processor 2001 to perform calculations, control communication via the communication device 2004, and control at least one of reading and writing data in the memory 2002 and storage 2003.

[0012] The processor 2001 controls the entire computer by running, for example, an operating system. The processor 2001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. Furthermore, for example, a baseband signal processing unit, a call processing unit, etc. may be realized by the processor 2001.

[0013] The processor 2001 reads programs (program codes), software modules, data, etc. from at least one of the storage 2003 and the communication device 2004 into the memory 2002 and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described below. The functional blocks of the server device 20 may be implemented by a control program stored in the memory 2002 and running on the processor 2001. Various processes may be executed by one processor 2001, or may be executed simultaneously or sequentially by two or more processors 2001. The processor 2001 may be implemented by one or more chips. The programs may be transmitted to the server device 20 via a telecommunications line.

[0014] The memory 2002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 2002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 2002 can store executable programs (program codes), software modules, etc. for implementing the method according to this embodiment.

[0015] Storage 2003 is a computer-readable recording medium, and may be composed of at least one of, for example, an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. Storage 2003 may also be called an auxiliary storage device.

[0016] The communication device 2004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0017] Each device, such as the processor 2001 and the memory 2002, is connected by a bus for communicating information. The bus may be configured using a single bus, or may be configured using different buses between each device.

[0018] The server device 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 2001 may be implemented using at least one of these pieces of hardware.

[0019] The user terminal 10 is physically configured as a computer device including a processor, memory, storage, a communication device, an input device, an output device, and a bus connecting these devices. The processor, memory, and storage of the user terminal 10 are hardware similar to the processor 2001, memory 2002, and storage 2003 of the server device 20. The communication device of the user terminal 10 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier unit, transmitting and receiving unit, and transmission path interface may be realized by a communication device. The transmitting and receiving unit may be implemented as a transmitting unit and a receiving unit that are physically or logically separated. The input device of the user terminal 10 is an input device that accepts input from outside (e.g., a key, a microphone, a switch, a button, a GPS unit including a GPS antenna, etc.). The output device of the user terminal 10 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device and the output device may be integrated into one device (e.g., a touch screen).

[0020] 3 is a block diagram showing the functional configuration of the server device 20. In the server device 20, a processor 2001 reads a program or the like from a storage 2003 into a memory 2002 and executes the program, thereby realizing the functions of a location information acquisition unit 21, a request acquisition unit 22, a memory unit 23, an estimation unit 24, an identification unit 25, a calculation unit 26, and an output unit 27.

[0021] The location information acquisition unit 21 acquires location information indicating the location of the user terminal 10 from a positioning means (not shown), together with date and time information indicating the date and time the positioning was performed and a user ID for identifying the user. The location measurement means referred to here may be any well-known location measurement means, and may be, for example, a positioning device such as a GPS unit provided in the user terminal 10, or a system that measures the position of the user terminal 10 using a method known as base station positioning. In this embodiment, the terminal ID assigned to the user terminal 10 is used as the user ID for identifying the user using that user terminal 10, and the location of the user terminal 10 is used as the location of the user using that user terminal 10.

[0022] The request acquisition unit 22 acquires a request for parking demand in a certain target section. This request is from a person who wants to know the parking demand in the target section. The request acquisition unit 22 may acquire the request from, for example, a communication terminal (not shown) used by the person, or may acquire the request directly input to the server device 20.

[0023] The storage unit 23 stores various types of data. For example, the storage unit 23 stores information acquired by the location information acquisition unit 21. Specifically, as illustrated in FIG. 4 , the storage unit 23 stores location information indicating the location of the user (the location of the user terminal 10) and date and time information indicating the date and time when the positioning was performed, in association with the user ID of the user. In other words, the storage unit 23 stores a history of location information for each user. In this embodiment, the location information is expressed in latitude / longitude, but the expression format of the location information is not necessarily limited to this.

[0024] The storage unit 23 also stores the locations of predetermined existing parking lots (hereinafter referred to as existing parking lots). Specifically, as illustrated in Fig. 5, the storage unit 23 stores location information indicating the location of each parking lot in association with a parking lot ID for identifying the parking lot.

[0025] The estimation unit 24 estimates a user who has parked a vehicle (hereinafter referred to as a parking user) based on the user's location information history. Specifically, the estimation unit 24 determines whether the user's means of transportation is by car, on foot, or by some other means based on the user's location information history, and estimates a user who has changed their means of transportation from a car to on foot as a parking user. At this time, the estimation unit 24 distinguishes between users who have parked a vehicle in an existing parking lot and users who have parked a vehicle in a location that is not an existing parking lot, and estimates the parking user.

[0026] The identification unit 25 identifies the location of a destination visited by the parking user estimated by the estimation unit 24 after the parking act. Specifically, the identification unit 25 identifies a location where the user's stay time exceeds a threshold (for example, an arbitrary time such as X minutes) as the location of the user's destination, based on the history of the user's location information after the parking act. As a result, when the user stays in a certain building, facility, etc. for a certain period of time or more, the location of the building, etc. where the user stayed is identified as the location of the user's destination.

[0027] The calculation unit 26 calculates the parking demand in the target section based on the locations of the destinations identified for the multiple users by the identification unit 25. A specific calculation method will be described later.

[0028] The output unit 27 outputs to the outside the information about the demand calculated by the calculation unit 26. The output here includes all output forms such as transmission, display, writing to a storage medium, and printing.

[0029] [Operation] Next, the operation of this embodiment will be described. Fig. 6 is a flowchart showing an example of the operation of the server device 20. Before the process shown in Fig. 6 is started, the storage unit 23 stores location information indicating the location of each parking lot in association with the parking lot ID of that parking lot. Furthermore, before the process shown in Fig. 6 is started, the location information acquisition unit 21 repeatedly acquires location information of each user, for example, periodically or intermittently, and stores the location information in association with the user ID and date and time information of that user in the storage unit 23.

[0030] In Fig. 6, the request acquisition unit 22 acquires a request for determining the parking demand in a certain target section (step S11). This request includes range information indicating the range of the target section. Specifically, as shown in Fig. 7, the request includes a section ID assigned to the target section and range information indicating the positions of each vertex of the outer edge of the section. In other words, the range of the target section is the inside of a rectangle connecting these vertices. Note that in this embodiment, the shape of the target section is rectangular, but this is not necessarily limited to this. The storage unit 23 stores the section ID and range information included in the request.

[0031] 6 , the estimation unit 24 estimates parked users based on the location information history of each user stored in the storage unit 23 (step S12). First, the estimation unit 24 calculates each user's speed, acceleration, stop time, and directional change from the difference between adjacent date and time information and location information on the time axis in each user's location information history. Then, the estimation unit 24 determines whether each user's transportation mode is a vehicle, walking, or other means (e.g., train) based on the location information, speed, acceleration, stop time, and directional change using a well-known algorithm for determining whether the user's transportation mode is a vehicle, walking, or other means. Then, the estimation unit 24 estimates users who have changed their transportation mode from a vehicle to walking as parked users.

[0032] The estimation unit 24 estimates that the parking action has started when the means of transportation has changed from a vehicle to walking, and that the parking action has ended when the means of transportation has changed from walking to a vehicle at the parking position after the estimation of the parking action.

[0033] For example, as shown in Figure 8, if a user with user ID "U001" travels by car from date and time T1 to T2, travels on foot from date and time T2 to T3, travels on foot from date and time T3 to T4, and travels by car from date and time T4 onwards, it is estimated that the user started parking at date and time T2 when the mode of transportation changed from car to walking, and that the parking action ended at date and time T3 when the mode of transportation changed from walking to car. Note that Figure 8 shows only representative dates and times to avoid cluttering the illustration, but in reality, the user's location information is stored in chronological order at sufficiently short time intervals.

[0034] In this embodiment, the location where the parking user performed the parking action (lat g ,long g ) is calculated as the center of gravity of the positions measured at the times T1, T2, T3, and T4 in FIG. 8. In the example of FIG. 8, lat g =lat A +lat B +lat C +lat D long g= long A +long B +long C +long D This becomes:

[0035] Furthermore, the estimation unit 24 compares the parking location with the location indicated by the location information of each parking lot shown in FIG. 5, and if the distance between the parking location and the location of the parking lot closest to the parking location is less than a threshold, it estimates that the parking action occurred in an existing parking lot. On the other hand, if the distance between the parking location and the location of the parking lot closest to the parking location is equal to or greater than a threshold, the estimation unit 24 estimates that the parking action occurred in a location other than an existing parking lot (e.g., on a street). As a result, as shown in FIG. 8, it is estimated that the parking action on the street began at date and time T2 and ended at date and time T3. All of these estimation results are stored in the memory unit 23.

[0036] In FIG. 6 , the identification unit 25 identifies the location of the destinations visited by the parked user estimated by the estimation unit 24 after the parking action (step S13). Specifically, the identification unit 25 calculates the amount of change per unit time in the parked user's location information after the parking action, and if the amount of change is within a threshold, the identification unit 25 considers the parked user's location to have not changed and to have remained in the same location. Then, if the stay time of the parked user at the same location exceeds a threshold, the identification unit 25 identifies the location as the location of the parked user's destination. As a result, as shown in FIG. 9 , the user's location between date and time T2 and date and time T3 is identified as the location of the destinations. By performing the above-described processes of steps S12 to S13 for all users, the parking locations and destinations of multiple parked users are identified, and the results are stored in the storage unit 23.

[0037] The calculation unit 26 calculates the parking demand in the target section based on the locations of the destinations identified for the multiple users by the identification unit 25 (step S14). Specifically, let a be the section ID, m be the number of destinations, k1, k2, k3, and k4 be predetermined constants, d be the walking distance between the stay point n and the target section with section ID: a, p = [0, 1] (p = 1 for parking in a parking lot and P = 0 for parking on the street), and t n is the user's staying time at the staying point n, the calculation unit 26 calculates the parking demand ParkDemand in the target section of section ID: a using the following formula (1): a Calculate.

[0038]

[0039] In addition, the parking demand ParkDemand a The formula for calculating the logistic function may be other than the formula (1). For example, the following formula (2) including a logistic function may be used.

[0040]

[0041] As a result, the shorter the distance between the target section and the destination, the larger the calculated demand for that target section. Also, the longer the user stays at the destination, the larger the calculated demand. Also, the more destinations there are, the larger the calculated demand. Furthermore, the demand can be calculated by applying different weights to users who parked at locations other than parking lots and users who parked in parking lots.

[0042] In FIG. 6, the output unit 27 outputs information about the demand calculated by the calculation unit 26 (for example, a numerical value indicating the demand) to the outside (step S15).

[0043] The present embodiment provides the following advantages. When a user travels by vehicle to a destination, it is not always possible to park the vehicle at the destination, and the user may have to park the vehicle at a location different from the destination but close to it. In such cases, it is better to consider that parking demand exists at the user's original destination rather than at the location where the user actually parked. However, the present embodiment makes it possible to accurately estimate parking demand based on the location of the destination of the parking user.

[0044] Furthermore, for example, parking demand in a certain location can be roughly estimated based on the usage status of existing parking lots in the vicinity. However, if there are no parking lots nearby or if there are insufficient parking lots, users may be forced to park on the street. Because such potential parking demand is not reflected in the usage status of existing parking lots, it is difficult to estimate parking demand based on such usage status. In contrast, this embodiment makes it possible to estimate parking demand taking into account on-street parking.

[0045] [Modifications] The present invention is not limited to the above-described embodiment. The above-described embodiment may be modified as follows. Furthermore, two or more of the following modifications may be combined and implemented.

[0046] [Modification 1] The vehicle in the present invention may be a four-wheeled vehicle, a two-wheeled vehicle, or any other vehicle.

[0047] [Variation 2] In the above embodiment, the estimation unit 24 compares the parking location where the parking user parked with the location indicated by the location information of each parking lot shown in FIG. 5 to estimate whether the parking was performed in an existing parking lot or at a location other than an existing parking lot (e.g., on a street). The method for estimating whether a parking location is an existing parking lot or on a street is not limited to the example described in the embodiment. For example, if the server device 20 is configured to acquire usage history data for each parking lot, the estimation unit 24 compares the parking location where the parking user parked with the location indicated by the location information of each parking lot shown in FIG. 5 to acquire usage history data for the parking location and the parking lot closest to that parking location. The estimation unit 24 then compares the parking start date and time and parking end date and time estimated from the user's location information history with the parking start date and time and parking end date and time included in the acquired usage history data. If the difference between these dates and times is less than a threshold, the estimation unit 24 estimates that the parking was performed in an existing parking lot. On the other hand, if the difference between these dates and times is greater than or equal to a threshold, the estimation unit 24 estimates that the parking was performed on a street.

[0048] Furthermore, if the storage unit 23 stores location information indicating the location of roads instead of location information of parking lots, the estimation unit 24 compares the parking location where the parking user parked with the location indicated by the location information of each road, and if the distance between the parking location and the location of the road closest to the parking location is less than a threshold, the estimation unit 24 estimates that the parking was performed on a road.On the other hand, if the distance between the parking location and the location of the road closest to the parking location is equal to or greater than the threshold, the estimation unit 24 estimates that the parking was performed in an existing parking lot.

[0049] [Variation 3] The formula for calculating the parking demand is not limited to the above formulas (1) and (2). For example, any formula may be used as long as it calculates a larger demand for a target section the shorter the distance between the target section and the destinations. Furthermore, any formula may be used as long as it calculates a larger demand the longer the user stays at the destinations. Furthermore, any formula may be used as long as it calculates a larger demand the more destinations there are.

[0050] Any formula may be used as long as it calculates the demand by weighting differently users who parked at locations other than parking lots and users who parked at parking lots. However, it is not necessary to calculate the demand by distinguishing between users who parked at locations other than parking lots and users who parked at parking lots.

[0051] [Other Modifications] The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or the multiple devices.

[0052] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0053] For example, the server device 20 in one embodiment of the present disclosure may function as a computer that performs the processing of the present disclosure.

[0054] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (ULtra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (ULtra-WIDE Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

[0055] The present invention may be an information processing method including: an estimation step of estimating a user who parked a vehicle based on the user's location information history; an identification step of identifying the locations of destinations visited by the estimated user after the parking event; and a calculation step of calculating the parking demand in a target space based on the locations of the destinations identified for multiple users. The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be rearranged as long as there is no contradiction. For example, the methods described in this disclosure present various step elements in an exemplary order and are not limited to the specific order presented.

[0056] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

[0057] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0058] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0059] Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc. Additionally, software, instructions, information, etc. may be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then such wired and / or wireless technologies are included within the definition of a transmission medium.

[0060] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof. Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings.

[0061] Furthermore, the information, parameters, etc. described in this disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information.

[0062] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0063] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0064] The "unit" in the configuration of each of the above devices may be replaced with "means," "circuit," "device," etc.

[0065] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0066] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0067] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0068] 1: Information processing system, 2: Communication network, 20: Server device, 21: Location information acquisition unit, 22: Request acquisition unit, 23: Memory unit, 24: Estimation unit, 25: Identification unit, 26: Calculation unit, 27: Output unit, 2001: Processor, 2002: Memory, 2003: Storage, 2004: Communication device.

Claims

1. An information processing device comprising: an estimation unit that estimates the user who performed the parking act based on the user's location information history; an identification unit that identifies the locations of destinations visited by the estimated user after the parking act; and a calculation unit that calculates the parking demand in a target section based on the locations of the destinations identified for multiple users.

2. The information processing device according to claim 1, wherein the estimation unit estimates a user who has parked in a location other than a designated parking lot.

3. The information processing device according to claim 2, wherein the estimation unit estimates a user who has parked in a predetermined parking lot.

4. The information processing device according to claim 3, characterized in that the calculation unit calculates the demand by applying different weighting to users who parked at a location other than the parking lot and users who parked in the parking lot.

5. The information processing device according to claim 1, characterized in that the estimation unit estimates a user whose means of transportation has changed from vehicle to walking based on the history of the user's location information as the user who performed the parking act.

6. The information processing device according to claim 1, wherein the identification unit identifies a location where the user has stayed for a time exceeding a threshold as a location visited by the user based on the history of the user's location information.

7. The information processing device according to claim 1, wherein the calculation unit calculates a larger demand amount as the distance to the destination becomes shorter.

8. The information processing device according to claim 1, wherein the calculation unit calculates a larger demand amount as the user stays longer at the destination.

9. The information processing device according to claim 1, wherein the calculation unit calculates a larger demand amount as the number of destinations increases.

10. An information processing method comprising: an estimation step of estimating the user who performed the parking act based on the user's location information history; an identification step of identifying the locations of destinations visited by the estimated user after the parking act; and a calculation step of calculating the parking demand in a target area based on the locations of the destinations identified for multiple users.

Citation Information

Patent Citations

  • Information processing device

    JP2019096085A

  • Method, apparatus, device and computer readable storage medium to be used in navigation

    JP2021047184A

  • Information processing device, information processing method, information processing program and storage medium

    JP2022034172A

  • Information provision system, information provision method, and program

    JP2023055901A

Cited By

  • Vehicle parking-out control method and device, vehicle and computer readable medium

    CN122474054A