Recommended System

Abstract

To provide a technique capable of providing a new way of use that is not assumed by a user.SOLUTION: A device recommendation system comprises: a history information acquisition unit which acquires history information indicating a use history and use condition of a device in a vehicle for each user of the vehicle; a recommended device acquisition unit which acquires the device with a smaller use frequency of a target user in the use condition of a recommendation target than a predetermined reference and with a greater use frequency of a reference user than the predetermined reference as a recommended device on the basis of the history information of the target user being the recommendation target of the device and the history information of the reference user being the user other than the target user; and an output control unit which recommends the use of the recommended device or operates the recommended device.SELECTED DRAWING: Figure 1

Description

Technical Field

[0004] , ,

[0005] , , , , , , ,

[0003] , , ,

[0001] The present invention relates to a device recommendation system.

Background Art

[0002] Patent Document 1 discloses a technique for notifying a vehicle of a proposal to use a vehicle function when the driving situation of a vehicle of a user who does not use the vehicle function becomes a recommended driving situation.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In the conventional technology, the recommended driving situations in which the use of vehicle functions is proposed are predetermined. Therefore, the proposal to use vehicle functions can be made only under fixed situations predicted in advance. In a configuration where a proposal to use vehicle functions is made for fixed situations, it is not possible to make a proposal to use them in situations different from those situations. For this reason, it has not been possible to propose new usage methods that the user has not assumed. The present invention has been made in view of the above problems, and an object thereof is to provide a technology capable of providing a new usage method of a device that the user has not assumed.

Means for Solving the Problems

[0005] To achieve the above objective, the device recommendation system comprises: a history information acquisition unit that acquires history information showing the usage history and usage conditions of devices equipped in a vehicle for each user of the vehicle; a recommendation device acquisition unit that, based on the history information of the target user for whom the device is recommended and the history information of a reference user who is a user other than the target user, acquires as a recommended device a device in which the frequency of use by the target user in the usage conditions for which the device is recommended is less than a predetermined standard and the frequency of use by the reference user is more than a predetermined standard; and an output control unit that recommends the use of the recommended device or operates the recommended device.

[0006] In other words, the device recommendation system, based on historical information, recommends devices that are used less frequently by the target user and more frequently by reference users under the recommended usage conditions. Therefore, devices that the target user has not used much under the recommended usage conditions are recommended or operated. As a result, it is possible to suggest new ways of using these devices that the target user had not anticipated. [Brief explanation of the drawing]

[0007] [Figure 1] This is a block diagram of the recommended system for the device. [Figure 2] This figure shows an example of historical information. [Figure 3] This is a block diagram of the in-vehicle system. [Figure 4] Figure 4A is a flowchart of the history information acquisition process, and Figure 4B is a flowchart of the history information recording process. [Figure 5] This is a flowchart of the recommended device output processing. [Figure 6] This figure shows an example of processed historical information. [Figure 7] This figure shows an example of historical information after scoring. [Modes for carrying out the invention]

[0008] Here, embodiments of the present invention will be described in the following order. (1) System configuration: (1-1) Recommended system configuration for the device: (1-2) Vehicle configuration: (2) History information acquisition process: (3) Historical information recording process: (4) Recommended device output processing: (5) Other embodiments:

[0009] (1) System configuration: Figure 1 is a block diagram showing the configuration of the device recommendation system 10 according to the present invention. In this embodiment, the device recommendation system 10 cooperates with multiple vehicles C (in-vehicle systems used within the vehicles C) and an information management system 50 via communication. Vehicle C is a vehicle used by a user of vehicle C. Although three vehicles C are shown in Figure 1, the number of vehicles C is not limited. The information management system 50 is a system that collects and stores information on weather and traffic congestion. In response to a request from the device recommendation system 10, the information management system 50 transmits information indicating the weather and traffic congestion for the requested date, time, and location to the device recommendation system 10.

[0010] (1-1) Recommended system configuration for the device: In this embodiment, the recommended device system 10 is a stationary server computer, but of course, the configuration of the recommended device system 10 can be any configuration. The recommended device system 10 includes a control unit 20 equipped with a CPU, RAM, ROM, etc., a storage medium 30, and a communication unit 40. The communication unit 40 is a device for communicating with other devices. In this embodiment, the control unit 20 can communicate with an in-vehicle system and an information management system 50 used in the vehicle C via the communication unit 40.

[0011] The storage medium 30 stores history information 30b collected from vehicle C. The history information 30b is information that shows the usage history and usage conditions of the devices equipped in vehicle C for each user of the vehicle. In this embodiment, the devices equipped in vehicle C are devices that can be used while driving vehicle C by the user of vehicle C, such as by setting them on / off. The devices are not limited and may differ from vehicle C to vehicle, but for example, at least one of the following devices equipped in the vehicle is a sunroof, tailgate, sliding door, seat, window, mirror, speed control device, wiper, headlight, gear ratio selector, air conditioning device, and audio device. Note that the windows include the opening and closing mechanism of the glass window of the tailgate in addition to the power windows of the driver's seat, passenger seat, and rear seats, and the history may be collected separately for each, or the history may be collected without distinction. The speed control device is any device that can adjust the speed of vehicle C, and in this embodiment, it is an adaptive cruise control device (a cruise control device that follows a preceding vehicle). The gear ratio switching device can be any type of device, such as an automatic transmission, a continuously variable transmission, a manual transmission, or an E-axle utilizing a motor, inverter, and reduction gear.

[0012] The usage history only needs to show the history of when these devices were operated, and in this embodiment, it is information indicating whether or not they were operated. That is, if a device is operated while vehicle C is in motion or parked at a destination, information indicating that it was operated is recorded in the history information 30b.

[0013] The usage conditions indicate the conditions under which the device was used. In this embodiment, these conditions include the location where the device was used, the date and time of use, the environment in which it was used, and the state of the vehicle at the time of use. The environment in which the device was used refers to the environment surrounding vehicle C at the time of use, and in this embodiment, this includes the weather and the degree of traffic congestion. The state of vehicle C at the time of use can be defined by various factors, and in this embodiment, it is the speed of vehicle C. Of course, other states, such as driving in a straight line or driving on a curve, may also be the state of the vehicle at the time of use.

[0014] Figure 2 shows an example of the history information 30b. Since the history information 30b is the history for each device provided in the vehicle C, information is recorded for each device such as a sunroof provided in the vehicle C. Further, the history item indicates an item of a value recorded as the history information 30b, and includes an item indicating the usage history and a plurality of items indicating the usage conditions. The usage history indicates, for the sunroof, the history when the sunroof changes from the closed state to the open state as "open", and usage conditions such as the date and time and position when the sunroof becomes open are associated with the "open" history. Also, in the history information 30b, the history when the sunroof changes from the open state to the closed state is indicated as "closed", and usage conditions such as the date and time and position when the sunroof becomes closed are associated with the "closed" history. Therefore, by specifying the period from the date and time associated with the "open" history to the date and time associated with the "closed" history, it is also possible to specify the length of time the sunroof has been in the open state.

[0015] The control unit 20 can execute programs stored in the storage medium 30, a ROM (not shown), etc. In the present embodiment, the control unit 20 can execute a device recommendation program 21 as this program. When the device recommendation program 21 is executed, the control unit 20 functions as a history information acquisition unit 21a, a recommended device acquisition unit 21b, and an output control unit 21c.

[0016] The history information acquisition unit 21a is a function of acquiring history information indicating the usage history and usage conditions of the devices provided in the vehicle C for each user of the vehicle. That is, the control unit 20 collects the history information 30b from the vehicle C and the information management system 50 via the communication unit 40 and stores it in the storage medium 30 by the function of the history information acquisition unit 21a.

[0017] Specifically, in vehicle C, a usage history of the device and a part of usage conditions (date and time of use, location, and speed of vehicle C at the time of use) are collected. The usage history and a part of the usage conditions are associated with identification information of the user of vehicle C and transmitted to the device recommendation system 10 at a predetermined transmission timing. In the present embodiment, the identification information of the user is the identification information of vehicle C, and individual persons using vehicle C are not distinguished. Of course, each person may be distinguished.

[0018] The control unit 20 acquires the information transmitted from vehicle C via the communication unit 40 and stores it in the storage medium 30 as history information 30b. Further, the control unit 20 refers to the received history information 30b to acquire the date and time when the device was used (or the use was terminated) and the location of vehicle C. Then, the control unit 20 outputs a transmission request for the weather and traffic congestion degree at the date and time and location via the communication unit 40 to the information management system 50. The information management system 50 returns information indicating the weather and traffic congestion degree at the date and time and location in response to this request. The control unit 20 receives the information via the communication unit 40 and adds it to the history information 30b. As a result, as shown in FIG. 2, the usage history and usage conditions of the device are collected as the history information 30b.

[0019] The recommended device acquisition unit 21b is a function of acquiring, as a recommended device, a device in which the usage frequency of the target user under the usage conditions of the recommendation target is less than a predetermined standard and the usage frequency of the reference user, who is a user other than the target user, is more than the predetermined standard, based on the history information of the target user, who is the target of device recommendation, and the history information of the reference user, who is a user other than the target user. In the present embodiment, the user is a person who uses vehicle C, the target user is a user to whom the recommended device is provided, and the reference user is a user whose history information 30b is similar to the history information 30b of the target user. An example of a method for specifying the reference user will be described later.

[0020] Furthermore, the recommended usage conditions are the conditions under which the recommended device is recommended for the target user or the conditions under which the recommended device is operated. In this embodiment, the recommended usage conditions are the current conditions, i.e., the current date and time and the current location of vehicle C used by the target user, but other usage conditions may also be used. For example, the date and time and location where the target user plans to drive vehicle C may be the recommended usage conditions, or the date and time and location at the driving destination may be the recommended usage conditions. Weather, traffic congestion, and the speed of vehicle C may also be included in the recommended usage conditions.

[0021] Since the history information 30b is defined for each user, the control unit 20 can analyze the history information 30b to evaluate the frequency of use of each device for each usage condition. Therefore, the control unit 20 analyzes the history information 30b of the target user and evaluates how often the target user uses the device under the recommended usage conditions. Devices that the target user uses more frequently under the recommended usage conditions than under other usage conditions are devices that the target user already prefers to use. Consequently, even if recommended, the usage pattern is a pattern that the target user has anticipated, and it does not offer a new way to use the device.

[0022] On the other hand, devices that are used less frequently by the target user under the recommended usage conditions than under other usage conditions are devices that the target user has not used much under the recommended usage conditions. Therefore, if the target user uses the device according to the recommendation, it can provide the target user with a new way of using it.

[0023] However, even if a device is not frequently used by the target user under the recommended usage conditions, recommending a device that does not match the usage conditions at all would not benefit the target user. Therefore, the control unit 20 identifies devices that the reference user uses more frequently than a predetermined standard, based on the reference user's history information 30b. Such devices are likely to represent a desirable usage because they have been used relatively frequently by the reference user under the recommended usage conditions. Consequently, by selecting devices that the target user uses less frequently than a predetermined standard under the recommended usage conditions, but that the reference user uses more frequently than a predetermined standard, as recommended devices, it is possible to recommend devices that can provide the target user with new and desirable usage methods. The criteria for evaluating the frequency of device use can be any criteria that can evaluate the frequency of use for each user. The acquisition of recommended devices based on such criteria will be described later.

[0024] The output control unit 21c has the function of recommending the use of the recommended device or activating the recommended device. Either the recommendation to use the recommended device or the activation of the recommended device may be performed, or both may be possible, but in this embodiment, the mode in which the use of the recommended device is recommended will be described. In this embodiment, the recommended device is recommended to the target user when the target user uses vehicle C. Therefore, the control unit 20 targets vehicle C used by the target user as the transmission target and transmits the recommended device via the communication unit 40.

[0025] In vehicle C used by the target user, recommended devices are displayed on the display unit of the in-vehicle system described later. These recommended devices are those that the target user uses infrequently but which reference users frequently use, given the current date and time and the location of vehicle C, which are the recommended usage conditions. Therefore, the target user can learn about new ways of using the devices that they were previously unaware of. Furthermore, by using these recommended devices, the target user can experience new ways of using the devices that they were previously unaware of. And because these ways of using the devices and the experiences gained are those that reference users have extensive experience using, they are likely to be favorable ways of using the devices for the target user as well.

[0026] (1-2) Vehicle configuration: Next, the in-vehicle system 100 that works in cooperation with the recommended device system 10 will be described. Each vehicle C is equipped with an in-vehicle system 100 as shown in Figure 3. Vehicle C is also equipped with devices such as a sunroof 440, windows 441, and an air conditioning system 442, and ECUs (Electronic Control Units) 430 to 432 that control each device. The sunroof 440, windows 441, and air conditioning system 442 shown in Figure 3 are examples of devices that are subject to the collection of history information 30b, and other devices may also be included as targets for the collection of history information 30b.

[0027] In this embodiment, the in-vehicle system 100 is a computer fixed to the vehicle C, but of course, the in-vehicle system 100 may be portable or in any other form. The in-vehicle system 100 includes a control unit 200 equipped with a CPU, RAM, ROM, etc., a communication unit 400, a position measurement unit 410, and a user I / F unit 420. The communication unit 400 is a device for communicating with other devices. In this embodiment, the control unit 200 can communicate with the device recommendation system 10.

[0028] The position measurement unit 410 is a device that measures the current position of vehicle C. The position measurement unit 410 may acquire the current position by various methods. In this embodiment, it includes a GNSS receiver, a vehicle speed sensor, and a gyro sensor (not shown). The GNSS receiver is a device that receives signals from the Global Navigation Satellite System, receives radio waves from navigation satellites, and outputs a signal for calculating the current position of vehicle C via an interface (not shown). The vehicle speed sensor outputs a signal corresponding to the rotational speed of the wheels of vehicle C. The gyro sensor detects the angular acceleration of vehicle C turning in the horizontal plane and outputs a signal corresponding to the orientation of vehicle C. The vehicle speed sensor and gyro sensor are used to determine the driving trajectory of vehicle C. In this embodiment, the current position of vehicle C is determined based on the starting position and driving trajectory of vehicle C, and the current position of vehicle C determined based on the starting position and driving trajectory is corrected based on the output signal of the GNSS receiver.

[0029] The user interface unit 420 is an interface unit for receiving user instructions and providing the user with various information, and includes a display unit consisting of a touch panel display (not shown), input units such as switches, and an audio output unit such as a speaker. The display unit of the user interface unit 420 can display various information under the control of the control unit 200.

[0030] The control unit 200 can execute a program stored on a storage medium (not shown). In this embodiment, the recommended device suggestion program 210 can be executed as this program. When the recommended device suggestion program 210 is executed, the control unit 200 functions as a communication control unit 210a and a recommended device suggestion unit 210b.

[0031] The communication control unit 210a has the function of controlling the exchange of information via communication between the device recommendation system 10 and the in-vehicle system 100. In this embodiment, communication is used for transmitting history information 30b and receiving information regarding recommended devices. Specifically, the ECU 430, etc., controls devices such as the sunroof 440 in response to user instructions or the fulfillment of predetermined driving conditions. In addition to the control function of these devices, the ECU 430, etc., also has a function of transmitting operation information. That is, when a controlled device such as the sunroof 440 operates, it transmits information indicating the content of the operation to the control unit 200.

[0032] The control unit 200 identifies the details of the operation and generates history information 30b. That is, when the device is operated, the control unit 200 generates information indicating the usage history of the device. The control unit 200 also generates information indicating the usage conditions of the device. Specifically, the control unit 200 obtains the date and time when the device was operated (the date and time indicating the start and end of the operation) based on a timing circuit (not shown). Furthermore, the control unit 200 obtains the position of vehicle C when the device was operated based on the output information of the position measurement unit 41. Furthermore, the control unit 200 obtains the speed of vehicle C when the device was operated based on the output signal of the vehicle speed sensor provided by the position measurement unit 41.

[0033] The control unit 200 considers this information as part of the device history information 30b and associates it with the identification information of vehicle C. The control unit 200 then transmits this information to the device recommendation system 10 via the communication unit 400. The device recommendation system 10 adds information indicating the weather and congestion level to this information and records it in the storage medium 30 as history information 30b. As this process is carried out for each vehicle C, the device recommendation system 10 accumulates history information 30b for multiple users.

[0034] In this embodiment, the recommendation of the recommended device is performed when predetermined conditions are met. The predetermined conditions can be defined in various ways. For example, a configuration in which the conditions are considered to be met when driving in vehicle C begins, or a configuration in which the conditions are considered to be met each time a certain period of time has elapsed while vehicle C is driving. In addition, the predetermined conditions can be defined in various ways, such as when arriving at a destination, driving in traffic congestion, or driving towards a tourist destination.

[0035] In any case, once the predetermined conditions are met, the control unit 200 identifies the recommended usage conditions using the functions of the communication control unit 210a. Specifically, the control unit 200 identifies the current date and time based on a timing circuit (not shown) and identifies the current position of vehicle C based on the output signal of the position measurement unit 410. The control unit 200 then uses these current date and time and the current position of vehicle C as the recommended usage conditions and transmits them to the device recommendation system 10 via the communication unit 400, and requests a reply from the recommended device. The device recommendation system 10 identifies a recommended device based on the recommended usage conditions and transmits the recommended device to vehicle C, which made the request. The control unit 200 receives the recommended device via the communication unit 400.

[0036] The recommended device suggestion unit 210b is a function that suggests recommended devices to the target user. That is, the control unit 200 suggests recommended devices to the target user by controlling the display unit of the user I / F unit 420 and displaying the recommended devices transmitted by the device recommendation system 10. The method of suggesting recommended devices can take various forms. For example, a display encouraging the use of the recommended device may be made, or the usage conditions (date, time, and location) for using the recommended device may be displayed. Furthermore, the content of the experience obtained by using the recommended device may also be displayed.

[0037] (2) History information acquisition process: Next, the history information acquisition process performed in each vehicle C will be explained. Figure 4A is a flowchart of the history information acquisition process. When the electrical components of vehicle C are turned on and the in-vehicle system 100 starts up, the history information acquisition process begins. Once the history information acquisition process begins, the control unit 200 determines whether or not any device provided in vehicle C has been used (step S100). That is, the control unit 200 monitors the output signals of the ECU 430, etc., and when it receives a signal indicating that any device has been used, it determines that the device has been used. If it is not determined in step S100 that the device has been used, the control unit 200 repeats the process from step S100 onward.

[0038] In step S100, if it is determined that the device has been used, the control unit 200 acquires the usage history of the device that was determined to have been used (step S105). That is, the control unit 200 acquires the usage status (for example, in the case of the sunroof 440, either open or closed) based on the output signal of the ECU 430 or the like. Next, the control unit 200 acquires the usage conditions (step S110). That is, the control unit 200 acquires the date and time when the device was operated, the position of vehicle C when the device was operated, and the speed of vehicle C when the device was operated.

[0039] Then, the control unit 200, using the functions of the communication control unit 210a, associates this information with the user's identification information to create history information and transmits it to the device recommendation system 10 via the communication unit 400 (step S115).

[0040] (3) Historical information recording process: Next, the history information recording process performed in each vehicle C will be described. Figure 4B is a flowchart showing the history information recording process. When history information (or part of it) is transmitted from any vehicle C, the control unit 20 of the device recommendation system 10 executes the history information recording process. When the history information recording process starts, the control unit 20 receives the history information transmitted from vehicle C via the communication unit 40 using the function of the history information acquisition unit 21a (step S200).

[0041] Next, the control unit 20, using the functions of the history information acquisition unit 21a, refers to the history information received in step S200 and acquires the weather and congestion level for the date and time and location of the device, based on the date and time the device was operated and the location of vehicle C (step S205). That is, the control unit 20 acquires the date and time the device was operated and the weather and congestion level at the location where the device was operated from the information management system 50. Then, using the functions of the history information acquisition unit 21a, the control unit 20 records the history information in association with the user's identification information (step S210). That is, the control unit 20 associates the information acquired in step S205 with the information acquired in steps S105 and S110, and further associates the user's identification information, and records it on the storage medium as history information 30b.

[0042] (4) Recommended device output processing: Next, the recommended device output processing performed by the device recommendation system 10 will be described. Recommended device output processing is performed when the control unit 200 of vehicle C transmits the current status in vehicle C, i.e., the usage conditions for the recommended device, and a recommendation for device output is requested. At this time, the user of vehicle C that requested the recommendation for device output becomes the target user, and the identification information of the target user is also transmitted. Figure 5 is a flowchart of the recommended device output processing. When the recommended device output processing is started, the control unit 20 acquires the usage conditions for the recommended device and the target user via the communication unit 40 using the function of the recommended device acquisition unit 21b (step S300).

[0043] Next, in steps S305 to S310, the control unit 20 performs processing to identify history information similar to the target user's history information 30b as the reference user's history information. Specifically, the control unit 20 processes the history information based on processing conditions using the function of the recommended device acquisition unit 21b (step S305). This processing is performed to make the history information 30b easier to compare for each user. In this embodiment, the processing conditions are conditions for statistically processing the history information 30b so that the user's behavioral tendencies and preferences can be identified.

[0044] Specifically, the control unit 20 performs statistical analysis on user-specific history information 30b for multiple statistical items corresponding to usage history and usage conditions. In this embodiment, the statistical items are items that clarify the characteristics of how the user uses the device. Figure 6 shows an example of processed history information processed based on processing conditions. In the example shown in Figure 6, usage time, most frequently used month, and most frequently used season are exemplified as statistical items for the sunroof 440, which is a device installed in vehicle C.

[0045] The control unit 20 refers to the history information 30b for each user and performs statistical processing on each statistical item based on the usage history and usage conditions. For example, in the example shown in Figure 6, the control unit 20 refers to the history information 30b of user 1 and considers the period from the date and time when the sunroof 440 was in the open state to the date and time when it returned to the normal state as the usage time. The control unit 20 obtains the average value of the usage time obtained in this way as the usage time statistic. In the example shown in Figure 6, the average usage time of the sunroof 440 by user 1 is 30 minutes.

[0046] The most frequently used month is the month in which the user uses the device most often. In the example in Figure 6, the month in which User 1 uses the sunroof 440 most is April. The most frequently used season is the season in which the user uses the device most often. In the example in Figure 6, the season in which User 1 uses the sunroof 440 most often is season number 3, which is autumn. In this example, seasons are represented by values ​​1 to 4, with values ​​1 to 4 representing spring, summer, autumn, and winter, respectively. Of course, these are just examples, and various other statistical items may be adopted, and there may be multiple values ​​for the same statistical item. For example, the system may be configured to acquire the top three most frequently used values ​​for each month.

[0047] Once the above processing is performed, the control unit 20, using the function of the recommended device acquisition unit 21b, identifies reference users whose history information 30b is similar to that of the target user based on the processed history information 30b (step S310). Identifying users with similar history information can be carried out by various methods. For example, by considering the processed history information 30b processed in step S305 as a vector with the values ​​of each statistical item as components and obtaining the cosine similarity, the similarity of the processed history information 30b can be identified. Then, by identifying the top k users (k is a predetermined number) with high similarity to the target user's history information 30b, reference users whose history information 30b is similar to that of the target user can be identified. Of course, this example is just one example of processing for identifying reference users. In addition, the values ​​of each statistical item may be normalized to be within the same range before the similarity is compared.

[0048] Next, in steps S315 to S320, the control unit 20 performs processing to evaluate the frequency of device use by the reference user and the target user. Specifically, the control unit 20 converts the values ​​of each item in the history information 30b of the reference user and the target user into frequencies of multiple levels using the function of the recommended device acquisition unit 21b (step S315). Here, the multiple levels are introduced to limit the range of change of the values ​​of each item in the history information 30b. That is, in this embodiment, by classifying the values ​​of each item indicating usage conditions included in the user's history information 30b into one of multiple levels, it becomes possible to analyze, for example, information about dates and times that can change continuously as frequencies. The control unit 20 refers to the history information 30b and acquires the frequencies of each of the predetermined multiple levels for each item.

[0049] Furthermore, the control unit 20 scores based on the frequency of each level using the function of the recommended device acquisition unit 21b (step S320). Scoring is a process that converts frequency into a value corresponding to the magnitude of the frequency, and is expressed using multiple values ​​such that the value increases as the frequency increases. Figure 7 is a diagram illustrating the processes of steps S315 and S320. In Figure 7, multiple levels set for each item of the usage conditions are shown. For example, the date and time the sunroof 440 was used is classified into one of multiple time periods which are multiple levels.

[0050] If 24 hours are divided into 6 equal parts, the resulting time zones 1 to 6 represent 4-hour intervals. Figure 7 shows time zones 1 to 3. In Figure 7, frequency is scored on a 5-point scale from 1 to 5, with higher numbers indicating greater frequency. Therefore, in the example shown in Figure 7, user 1 uses the sunroof 440 more often in time zone 1 than in time zones 2 and 3.

[0051] Other usage conditions also yield scores for multiple levels. The levels corresponding to the location where the device was used are represented in Figure 7 as Area 1, Area 2, etc. Area classification can be carried out using various methods; areas may be defined by geographical classifications such as meshes or administrative divisions, or by area characteristics and attributes such as urban areas, suburbs, tourist areas, coastal areas, mountainous areas, or elevations above a predetermined value. In the example shown in Figure 7, User 1 uses the sunroof 440 more in Area 2 than in Areas 1 and 3.

[0052] Regarding weather, frequency is scored based on known classifications of weather, such as sunny, cloudy, and rainy. In the example shown in Figure 7, User 1 uses the sunroof 440 more often in sunny weather than in cloudy or rainy weather. Regarding traffic congestion, frequency is scored based on classifications indicating the degree of congestion (in order of severity: congested, crowded, and empty). In the example shown in Figure 7, User 1 uses the sunroof 440 more often in empty conditions than in congested or crowded conditions. Regarding speed, frequency is scored based on classifications indicating speed ranges. In the example shown in Figure 7, User 1 uses the sunroof 440 more often when driving in speed range 1 than when driving in speed ranges 2 and 3.

[0053] Figure 7 shows the score for the sunroof 440. Similarly, for devices whose usage conditions are recorded in the history information 30b, the score is calculated based on the frequency at multiple levels. Since the score shown in Figure 7 is generated based on the frequency indicated in the history information 30b, the information after scoring also reflects the history information 30b for each user. Therefore, this information is referred to here as the history information 30b after scoring.

[0054] The above process makes it possible to identify which devices each user tends to use most frequently under what usage conditions. Therefore, by selecting the usage conditions with high scores from each device's score, it is possible to identify the usage conditions under which each device is used most frequently. Conversely, by selecting the usage conditions with low scores from each device's score, it is possible to identify the usage conditions under which each device is used less frequently.

[0055] Therefore, by referring to the historical information 30b after scoring the target user and excluding the usage conditions with high scores, it is possible to identify the usage conditions for each device that the target user uses less frequently than the standard and that the target user does not use often. Also, by referring to the historical information 30b after scoring the reference user and identifying the usage conditions with high scores, it is possible to identify the usage conditions for each device that the reference user uses more frequently than the standard and that the reference user uses often.

[0056] As described above, by setting thresholds for scores corresponding to frequency, it is possible to identify the usage conditions that each user frequently uses and those that they rarely use for each device. However, in this embodiment, a configuration is adopted to further increase the possibility of identifying recommended devices. Specifically, the usage conditions in this embodiment are defined by multiple items including date and time, location, weather, traffic congestion, and speed, and each item is further classified into multiple levels, and a score is obtained for each level. Therefore, since there are many variable elements in the usage conditions, it may be difficult to find a device whose combination of usage conditions with a high score matches the recommended usage conditions when considering all items of the usage conditions.

[0057] Therefore, when identifying usage conditions that match the recommended usage conditions, the system is configured to consider some of the multiple items indicating usage conditions while excluding others. Specifically, the items indicating usage conditions are assigned priorities in advance, and the control unit 20 filters out items with low priority (step S325), and does not consider those items when identifying usage conditions that match the recommended usage conditions.

[0058] Priority may be determined based on various factors. In this embodiment, items with low reproducibility are given lower priority. For example, weather and traffic congestion may be considered unstable conditions that fluctuate regardless of the user's intentions and therefore given low priority. Similarly, speed may be considered an unstable condition that can fluctuate significantly during driving and therefore given low priority. With this configuration, it becomes easier to identify devices whose combination of high-scoring usage conditions matches the recommended usage conditions.

[0059] Of course, this configuration is just one example, and priorities may be defined lower for other items, or higher for items such as weather. Furthermore, priorities may be defined in three or more levels. The priority to be filtered may also change based on various factors, such as the number of samples in the history information 30b or the number of candidate recommended devices remaining after filtering. Furthermore, if filtering is not required, step S325 may be omitted.

[0060] Next, the control unit 20, using the function of the recommended device acquisition unit 21b, identifies usage conditions for each device where the reference user's score is greater than the standard and the target user's score is less than the standard (step S330). For example, in Figure 7, when the standard for determining the frequency of use is set to a score of 4, usage conditions with a score greater than the standard are colored in dark gray, and usage conditions with a score less than the standard are colored in light gray.

[0061] In this example, assuming User 1 is the reference user and User 2 is the target user, the usage conditions in which the reference user's score for the sunroof 440 is higher than the standard are time zone 1 and area 2. Note that in this example, we assume that weather, traffic congestion, and speed are not considered due to filtering by step S325.

[0062] Furthermore, regarding the sunroof 440, the usage conditions in which the target user's score is lower than the standard are time zones 1 and 2, and areas 1, 2, and 3. Therefore, in this example, the control unit 20 identifies time zone 1 and area 2, which are the usage conditions for the sunroof 440, as usage conditions in which the reference user's score is higher than the standard and the target user's score is lower than the standard. The control unit 20 performs the above identification of usage conditions for each device.

[0063] For simplicity, this explanation uses the example of only one reference user, but in step S310, k reference users are identified. Therefore, the control unit 20 analyzes the scored history information 30b for the k reference users. Various methods can be used to consider the k reference users. For example, one configuration may involve multiplying the scores of the k users by a gain that increases with increasing similarity to the target user and then calculating the sum. Of course, the average of the k users may also be used, and the scores of the k users may be considered using various methods.

[0064] In any case, the above process results in a state where usage conditions that are rarely used by the target user but frequently used by the reference user are identified for each device. Therefore, the control unit 20 uses the function of the recommended device acquisition unit 21b to identify the recommended device under the recommended usage conditions and outputs it to the target user's in-vehicle system 100 using the function of the output control unit 21c (step S335). That is, the control unit 20 compares the recommended usage conditions acquired in step S300 with the usage conditions identified in step S330 and identifies matching usage conditions. Then, it identifies the device that was used under the matching usage conditions as the recommended device.

[0065] For example, in Figure 7, let's assume an example where User 1 is a reference user and User 2 is the target user. Let's also assume an example where the usage conditions for the sunroof 440, namely time zone 1 and area 2, are conditions where the reference user's score is greater than the standard and the target user's score is less than the standard. In this example, if the recommended usage conditions, i.e., the current time and the current location of vehicle C, which are the current usage conditions of the target user, are included in time zone 1 and area 2, then the sunroof 440 becomes a recommended device. If the time and location of vehicle C, which are the recommended usage conditions, are not included in time zone 1 and area 2, then the sunroof 440 does not become a recommended device. For each of the other devices, the usage conditions identified in step S330 are compared with the recommended usage conditions, and if they match, that device becomes a recommended device.

[0066] Once the recommended device is identified as described above, the control unit 20 outputs the recommended device to the target user's in-vehicle system 100 via the communication unit 40 (step S335). As a result, the target user's in-vehicle system 100 proposes the recommended device to the target user.

[0067] (5) Other embodiments: The embodiments described above are merely examples for carrying out the present invention, and various other embodiments can be adopted. For example, each system constituting the above-described embodiments may consist of fewer devices. One such example is that at least one device shown in Figure 1 is identical to one or more other devices. For example, the device recommendation system 10 and the information management system 50 may be configured as a single device, or the vehicle C may be configured as a single device with the information management system 50. Furthermore, the system shown in Figure 1 may consist of more systems. For example, at least some of the functions of the device recommendation system 10 may be configured as a cloud server.

[0068] Furthermore, at least some of the components constituting the device recommendation system 10 (history information acquisition unit 21a, recommended device acquisition unit 21b, output control unit 21c) and the components constituting the in-vehicle system 100 (communication control unit 210a, recommended device proposal unit 210b) may be divided among multiple devices. Also, configurations in which some of the components of the above-described embodiment are omitted, or configurations in which processing is varied or omitted, are conceivable. In addition, the in-vehicle system 100 may communicate with the information management system 50 to acquire usage conditions such as weather and traffic congestion, and use this as history information. In this case, step S205 in Figure 4B is executed by the in-vehicle system 100.

[0069] The history information acquisition unit only needs to acquire history information that shows the usage history and usage conditions of the devices installed in the vehicle for each vehicle user. In other words, the devices installed in the vehicle are used in various ways by each user. If the usage history of such devices is recorded as history information in association with the usage conditions, it becomes possible to identify past usage methods of the devices according to the usage conditions based on this history information.

[0070] The devices installed in a vehicle are not limited to specific devices, and may include, for example, various devices used by users such as vehicle occupants or various devices that operate automatically under various conditions. The devices installed in a vehicle may change depending on the vehicle type and the selection of optional specifications. For this reason, in the history information for vehicles that do not have a particular device, the usage history of that device may not be recorded. In this case, when determining the similarity between the history information of the target user and the history information of a reference user, the usage history of a non-existent device does not need to be considered.

[0071] Usage history may be recorded in various ways, and in addition to the mode in which information indicating whether or not the device was used is recorded, as in the embodiment described above, various other modes can be adopted. For example, continuously changing values ​​such as the degree to which the sunroof is opened or closed, the position of the seats, and the degree to which the windows are opened or closed may be recorded.

[0072] The usage conditions only need to describe the conditions under which the device was used. In other words, the usage conditions specify the conditions under which the device was used, so that at least some of the circumstances and environment in which the device was used can be reproduced. In addition to the conditions mentioned above, various other conditions may be included in the usage conditions. For example, the values ​​of various items such as the elevation of the road the vehicle traveled on, the type of road, the type of destination, and the type of vehicle may be included in the usage conditions. In any case, once the usage conditions are specified, it is sufficient that the system is configured so that when the same device is used under the same usage conditions as those recorded in the history information, the user can have the same or similar experience as in that history.

[0073] Vehicle users may be identified in various ways. Therefore, in addition to the configuration in which different vehicles are considered to be different users, as in the embodiment described above, various other configurations may be adopted. For example, if different users use the same vehicle, they may be distinguished as different users and their history information may be recorded. Users may be distinguished by having them input identification information such as their name or user number, or by facial recognition based on images captured by an in-vehicle camera. In addition, users may be distinguished based on identification information of a mobile device they own, and various other configurations may be adopted.

[0074] The recommended device acquisition unit should, based on the history information of the target user for whom the device is recommended and the history information of reference users (users other than the target user), acquire as recommended devices devices in which the target user's usage frequency is less than a predetermined standard and the reference user's usage frequency is more than a predetermined standard under the recommended usage conditions. In other words, by comparing the history information, it is possible to identify devices that the target user uses relatively infrequently under the recommended usage conditions compared to other usage conditions. It is also possible to identify devices that the reference user uses relatively frequently under the recommended usage conditions compared to other usage conditions.

[0075] Furthermore, recommended devices are those that reference users have used relatively frequently under the recommended usage conditions. When a vehicle's equipment, such as a sunroof, is used, the amount of wind and light introduced into the cabin, the scenery visible from inside the cabin, etc., change, and the content of the user's experience may change compared to when the sunroof is not used. Therefore, if a reference user uses a specific device under specific usage conditions, it is possible that the target user can be provided with the same or a similar experience by using the same device under the same or similar usage conditions. Ideally, by selecting recommended devices that the target user uses less frequently under the recommended usage conditions compared to other usage conditions, it should be possible to acquire devices as recommended devices that provide the same or a similar experience as the reference user, but that the target user may not have experienced before.

[0076] Furthermore, recommended devices are those whose usage frequency by the target user under the recommended usage conditions is less than a predetermined criterion, but this criterion can be various. For example, in the above embodiment, a threshold is set for the score obtained based on frequency. The value of this threshold can be various. Alternatively, a threshold may be set for the frequency itself instead of the score. Furthermore, for example, a device whose usage frequency by the target user under the recommended usage conditions is 0 may be a recommended device, but a device whose usage frequency is 1 or more may not be a recommended device. Also, the criterion used to compare the usage frequency of the target user and the criterion used to compare the usage frequency of the reference user may be the same or different.

[0077] The output control unit only needs to be able to recommend the use of a recommended device or to operate a recommended device. The usage conditions under which the use of a recommended device is recommended may consider some of several items. For example, in the above embodiment, a device may become a recommended device if one of the high-scoring time and location matches the recommended usage conditions, rather than both. Furthermore, the suggestion to the target user may also be a suggestion of usage conditions. For example, if a sunroof is a recommended device, the configuration may output the usage conditions for a sunroof. Also, when usage conditions for the same device are identified, multiple usage conditions may be identified for the same item. For example, if the score in multiple time periods is greater than the standard, those time periods may be identified and output as recommended usage conditions.

[0078] When operating the recommended devices, it is sufficient to output control signals to the ECUs that control each device in the vehicle, thereby operating each device. The control objectives when operating the devices can be various types of control objectives. For example, the history information of a reference user may record the operation details of each device (such as the degree of sunroof opening or the intensity of the air conditioning), and a control objective may be set to perform the same or similar operation. Of course, various other configurations may be adopted besides this one. For example, each device may be controlled to achieve a predetermined control objective, or the user may be allowed to input the control objective.

[0079] Whether the history information of the target user and the reference user are similar can be determined in various ways. For example, certain items in the usage conditions (such as vehicle speed) may be excluded from the items considered when determining similarity. In addition, whether the usage location or vehicle destination is similar can be determined. Furthermore, information other than usage conditions, such as whether the vehicle type is similar, may also be considered.

[0080] If the historical information is similar, it can be assumed that the user's preferences when using the device are similar. Therefore, in the above embodiment, the target user and the reference user can be considered to have similar preferences. On the other hand, the reference user may be identified from information other than the device usage history. For example, a user whose behavioral data or data that directly indicates preferences is similar to the target user's data may be a reference user. Examples of behavioral data include travel history to destinations, website browsing history, and comment history on products and facilities. Examples of data that directly indicates preferences include positive comments in the user's comment history on products and facilities. Data showing positive comments indicates products and facilities that the user likes, and similarity in user preferences can be identified based on the similarity of such data.

[0081] Furthermore, the present invention is also applicable as a program or method. Moreover, such systems, programs, and methods may be implemented as standalone devices, or they may be implemented using parts shared with various components provided in a vehicle, encompassing a variety of embodiments. For example, it is possible to provide methods and programs implemented using such systems. Furthermore, the components can be modified as appropriate, such as being partly software and partly hardware. The invention also functions as a storage medium for programs that control a device. Of course, the storage medium for the software may be a magnetic storage medium, a semiconductor memory, or any storage medium developed in the future can be considered in exactly the same way. [Explanation of symbols]

[0082] 10...Device recommendation system, 20...Control unit, 21a...History information acquisition unit, 21b...Recommended device acquisition unit, 21c...Output control unit, 30...Storage medium, 30b...History information, 40...Communication unit, 41...Location measurement unit, 50...Information management system, 100...In-vehicle system, 200...Control unit, 210...Recommended device suggestion program, 210a...Communication control unit, 210b...Recommended device suggestion unit, 400...Communication unit, 410...Location measurement unit, 420...User I / F unit, 430...ECU, 440...Sunroof, 441...Window, 442...Air conditioning unit

Claims

1. A history information acquisition unit acquires history information that shows the usage history and usage conditions of the devices installed in the vehicle for each user of the vehicle, A recommended device acquisition unit acquires, based on the history information of the target user for whom the device is recommended and the history information of a reference user who is a user other than the target user, the device in which the frequency of use by the target user under the recommended usage conditions is less than a predetermined standard and the frequency of use by the reference user is more than a predetermined standard, as the recommended device. An output control unit that recommends the use of the aforementioned recommended device or operates the aforementioned recommended device, Equipped with, The aforementioned usage conditions are: The device is defined by a value associated with an item that includes at least one of the following: the location where the device was used, the date and time of use, the environment in which it was used, and the state of the vehicle at the time of use. The aforementioned recommended device acquisition unit is: The values ​​for each item indicating the usage conditions included in the history information of the reference user are classified into one of several levels, the frequency for each of the several levels is obtained, and the recommended device is obtained based on the frequency. Recommended system for this device.

2. The history information of the aforementioned reference user is similar to the history information of the aforementioned target user. The similarity of the aforementioned historical information is The history information is statistically analyzed for multiple statistical items corresponding to the usage history and usage conditions items, and the results are identified based on the similarity of the history information indicated by the statistically analyzed values. The recommended system for the apparatus according to claim 1.

3. The recommended usage conditions are defined by some of the items that indicate the usage conditions. The recommended system for the apparatus according to claim 1.

4. The aforementioned device is At least one of the following: sunroof, tailgate, sliding door, seats, windows, mirrors, speed control, wipers, headlights, gear ratio selector, air conditioning system, and audio system. The recommended apparatus system according to any one of claims 1 to 3.

Images