# US 2014/0195467 A1 · Behavior history management system, and behavior history management method

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0195467 A1
- Document ID: US20140195467A1
- Status: Published application
- Kind: A1
- Application number: 14/239,948
- Filed: 2011-08-30
- Published: 2014-07-10
- Earliest claimed: 2011-08-30
- Assignees: Toyota Jidosha Kabushiki Kaisha
- Inventors: Sayaka Yoshizu
- Web page: https://patentgrep.com/patent/US20140195467A1

## CPC

- G06N 5/04: Inference or reasoning models
- G06N 20/00: Machine learning
- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q 50/40: Business processes related to the transportation industry (shipping G06Q10/083)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

Movement histories of a vehicle are registered appropriately in a database. A point specification unit specifies a geographical base of a user as a point serving as a nucleus of behavior of the user. When the need arises to delete a movement history stored in the database, a deletion subject data determination unit specifies a movement history having a low degree of relatedness to the geographical base of the user. A data deletion unit then deletes the movement history specified by the deletion subject data determination unit from the database. As a result, behavior histories having a high utility value to the user are held preferentially in the database.

## Claims

### Claim at position 1

1-15. (canceled)

### Claim 16

A behavior history management system comprising:
a database in which behavior histories of a user are stored;
a point specification unit that specifies a point serving as a nucleus of behavior of the user; and
a data management unit that specifies a behavior history having a low degree of relatedness to the point specified by the point specification unit, and when data are to be deleted from the database, deletes the specified behavior history preferentially, wherein
the point specification unit learns information relating to departure and arrival points including departure points from which the user departs and arrival points at which the user arrives after departing from the departure points, and estimates that a departure point having a relatively wide distribution of arrival points emanating therefrom, from among the learned departure and arrival points, is the point serving as the nucleus of the behavior of the user.

### Claim 17 (depends on 16)

The behavior history management system according to claim 16, wherein
the point serving as the nucleus of the behavior of the user is specified in relation to at least one category based on the behavior histories of the user, and the point specification unit specifies the point serving as the nucleus of the behavior of the user for each category, and
the database stores the behavior histories for each category.

### Claim 18 (depends on 16)

The behavior history management system according to claim 16, wherein
the behavior histories are histories representing behaviors of the user, which are generated every time the user travels to a destination, and
the data management unit specifies a behavior history generated on a journey to a destination having a low degree of relatedness to the specified point as a behavior history to be deleted from the database.

### Claim 19 (depends on 18)

The behavior history management system according to claim 18, wherein
the point serving as the nucleus of the behavior of the user is a geographical base of the user, and
the data management unit determines the degree of relatedness between the specified point and the behavior history on the basis of a distance from the geographical base of the user to the destination.

### Claim 20 (depends on 19)

The behavior history management system according to claim 19, wherein the data management unit specifies a behavior history generated on a journey to a destination located a relatively great distance from the geographical base of the user as the behavior history having the low degree of relatedness to the specified point.

### Claim 21 (depends on 16)

The behavior history management system according to claim 16, wherein the data management unit manages acquisition dates of the behavior histories of the user, and specifies the behavior history to be deleted preferentially from the database in consideration of the acquisition dates of the behavior histories.

### Claim 22 (depends on 21)

The behavior history management system according to claim 21, wherein the data management unit multiplies an element indicating the degree of relatedness between the specified point and the behavior history and the acquisition date of the behavior history by respective coefficients, and specifies the behavior history to be deleted preferentially from the database on the basis of two multiplication values obtained by the multiplication.

### Claim 23 (depends on 16)

The behavior history management system according to claim 16, wherein the data management unit determines the degree of relatedness between the specified point and the behavior history on the basis of at least one of a generation frequency of behavior histories representing identical or similar behaviors, from among the behavior histories emanating from the specified point, and a stay time of the user at a target point arrived at from the specified point.

### Claim 24 (depends on 16)

The behavior history management system according to claim 16, wherein the behavior history is a movement history of a vehicle operated by the user.

### Claim 25

A behavior history management method comprising:
storing behavior histories of a user in a database;
specifying a point serving as a nucleus of behavior of the user; and
specifying a behavior history having a low degree of relatedness to the specified point, and when data are to be deleted from the database, deleting the specified behavior history preferentially.

### Claim 26 (depends on 25)

The behavior history management method according to claim 25, wherein the point serving as the nucleus of the behavior of the user is specified in relation to at least one category based on the behavior histories of the user, and the behavior histories are stored in the database for each specified category.

### Claim 27 (depends on 25)

The behavior history management method according to claim 25, wherein
the behavior histories are histories representing behaviors of the user, which are generated every time the user travels to a destination, and
a behavior history generated on a journey to a destination having a low degree of relatedness to the specified point is specified as a behavior history to be deleted from the database.

### Claim 28 (depends on 27)

The behavior history management method according to claim 27, wherein
a geographical base of the user is specified as the point serving as the nucleus of the behavior of the user, and
the degree of relatedness between the specified point and the behavior history is determined on the basis of a distance from the geographical base of the user to the destination.

### Claim 29 (depends on 25)

The behavior history management method according to claim 25, further comprising attaching an acquisition date to the behavior history of the user when the behavior history is obtained, wherein
the behavior history to be deleted preferentially from the database is specified in consideration of the acquisition dates attached to the behavior histories.