Information provision device, information provision method, and program

Abstract

The present invention provides an information provision device, an information provision method, and an information provision program that, when mounted on a mobile vehicle, are capable of providing information or responses appropriate to each of the mobile vehicles. [Solution] The present invention provides an information providing device that can be mounted on multiple mobile bodies, and is characterized by comprising: a movement-related information acquisition unit that acquires movement-related information which is information relating to the movement of one mobile body and is stored in association with the one mobile body; a mobile body identification information acquisition unit that acquires mobile body identification information which is information that helps identify the mobile body on which the information providing device is currently mounted; and an information output unit that outputs information based on the movement-related information associated with the one mobile body when the one mobile body is identified based on the mobile body identification information.

Description

Technical Field

[0001] The present invention relates to an information providing apparatus, for example, an information providing apparatus, an information providing method, and a program that provide information to passengers of a moving body when mounted on the moving body.

Background Art

[0002] Conventionally, an agent terminal has been proposed that authenticates individuals using a vehicle and makes a response to an individual using agent data corresponding to each individual. (Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Depending on the agent terminal described in Patent Document 1 above, it is possible to make a response suitable for each individual by learning the preferences of each individual associated with each individual using a vehicle. However, when an agent terminal can be mounted on a plurality of different vehicles, it is difficult to make an appropriate response for each vehicle, which is an example of a problem.

[0005] The present invention has been made in view of the above points, and for example, an object thereof is to provide an information providing apparatus, an information providing method, and an information providing program capable of providing information or making a response suitable for each of the moving bodies when mounted on the moving body.

Means for Solving the Problems

[0006] The invention described in claim 1 is an information providing device that can be mounted on a plurality of mobile bodies, comprising: a movement-related information acquisition unit that acquires movement-related information which is information relating to the movement of one mobile body and is stored in association with the one mobile body; a mobile body identification information acquisition unit that acquires mobile body identification information which is information useful for identifying the mobile body on which the information providing device is currently mounted; and an information output unit that outputs providing information based on the movement-related information associated with the one mobile body when the one mobile body is identified based on the mobile body identification information.

[0007] Furthermore, the invention described in claim 7 is an information provision method that provides information using an information provision device that can be mounted on a plurality of mobile bodies, comprising the steps of: the information provision device acquiring movement-related information which is information relating to the movement of one mobile body and stored in association with the one mobile body; the information provision device acquiring mobile body identification information which is information useful for identifying the mobile body on which the information provision device is currently mounted; and the information provision device outputting provision information based on the movement-related information associated with the one mobile body when the one mobile body is identified based on the mobile body identification information.

[0008] Furthermore, the invention described in claim 8 is a program characterized by causing an information providing device that can be mounted on multiple mobile bodies to execute the following steps: acquiring movement-related information which is information relating to the movement of one mobile body and stored in association with the one mobile body; acquiring mobile body identification information which is information that helps identify the mobile body on which the information providing device is currently mounted; and outputting information based on the movement-related information associated with the one mobile body when the one mobile body is identified based on the mobile body identification information. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram of a system including an agent terminal, which is an embodiment 1 of the present invention. [Figure 2]Figure 1 is a block diagram showing an example of the configuration of the agent terminal in the system. [Figure 3] This block diagram shows an example of the server configuration of the system shown in Figure 1. [Figure 4A] This figure shows an example of a vehicle information table. [Figure 4B] This figure shows an example of a vehicle information table. [Figure 5] This is a flowchart of the operating routine for realizing a system including an agent terminal according to Embodiment 1 of the present invention. [Figure 6] This is a flowchart of the operating routine for realizing a system including an agent terminal according to Embodiment 1 of the present invention. [Figure 7] This is a flowchart of the operating routine for realizing a system including an agent terminal according to Embodiment 1 of the present invention. [Figure 8] This is a flowchart of the operating routine for realizing a system including an agent terminal according to Embodiment 1 of the present invention. [Figure 9A] This figure shows an example of a vehicle information table. [Figure 9B] This figure shows an example of a vehicle information table. [Figure 10] This is a flowchart of the operating routine for realizing a system including an agent terminal according to Embodiment 2 of the present invention. [Figure 11] This is a flowchart of the operating routine for realizing a system including an agent terminal according to Embodiment 2 of the present invention. [Modes for carrying out the invention] [Examples]

[0010] [1. System Configuration and Operation] Hereinafter, an information providing system 100 including an agent terminal 10 as an information providing device according to Embodiment 1 of the present invention and an information providing method will be described with reference to the accompanying drawings. FIG. 1 shows an information providing system 100 including an agent terminal 10 according to Embodiment 1 of the present invention. Specifically, the agent terminal 10 is, for example, a terminal having a smart speaker function.

[0011] As shown in FIG. 1, the information providing system 100 includes an agent terminal 10 and a server S (an example of a “server device”). In FIG. 1, a case where the agent terminal is mounted on an automobile M as an example of a moving body is shown.

[0012] The in-vehicle device VE is an in-vehicle device such as a car stereo mounted on the automobile M. Each of the in-vehicle devices VE has a unique device identifier (hereinafter also referred to as an in-vehicle device ID). The unique device identifier may be, for example, a MAC address or the like. In the following description, it is assumed that the in-vehicle device VE is permanently installed in the automobile M. Therefore, it is described that the device identifier of the in-vehicle device VE can be regarded as the identifier of the automobile M itself. The user terminal MT is a portable terminal such as a smartphone brought in by a user riding in the automobile M.

[0013] The agent terminal 10 and the server S can mutually transmit and receive data via a network (communication path) using a communication protocol such as TCP / IP, for example. Further, the server S can mutually transmit and receive data via a network with another server DS such as an agent server capable of performing reservation processing for facilities such as hotels, for example, using a communication protocol such as TCP / IP. The network can be constructed by, for example, mobile communication networks, wireless communication such as Wi-Fi (registered trademark), and Internet communication including wired communication.

[0014] The agent terminal 10 can be communicably connected to the in-vehicle device VE and the user terminal MT by wireless communication or wired communication such as Wi-Fi (registered trademark) or Bluetooth (registered trademark).

[0015] Figure 2 shows the configuration of the agent terminal 10. For example, the agent terminal 10 is a device in which a mass storage device 23, a control unit 25, an input unit 27, an output unit 29, a data communication unit 31, and a running information generation unit 33 cooperate via a system bus 21.

[0016] The mass storage device 23 is composed of, for example, a hard disk device, an SSD (solid state drive), a flash memory, etc., and stores various programs such as an operating system and terminal software. Note that the various programs may be acquired from other server devices etc. via a network, or may be recorded on a recording medium and read via various drive devices. That is, the various programs (including programs for executing the processing in the agent terminal 10 for the processing described later) stored in the mass storage device 23 can be transmitted via a network, and can also be recorded on a computer-readable recording medium and transferred.

[0017] The control unit 25 is composed of a CPU (Central Processing Unit) 25A, a ROM (Read Only Memory) 25B, a RAM (Random Access Memory) 25C, etc., and functions as a computer. Then, the CPU 25A reads and executes various programs stored in the ROM 25B and the mass storage device 23 to realize various functions.

[0018] The input unit 27 is a voice input device such as a microphone provided in the agent terminal 10. The control unit 25 can generate voice information based on the voice input from the input unit 27. Also, the input unit may include input devices such as a touch panel and a stylus pen, for example.

[0019] The output unit 29, which functions as an information output unit, is an audio output device such as a speaker provided in the agent terminal 10. The output unit 29 may also include, for example, a display provided in the agent terminal 10.

[0020] The output unit 29 can output audio based on data transmitted from the server device S. Furthermore, if the output unit 29 includes a display, it can also display images based on data transmitted from the server device S.

[0021] The data communication unit 31 is connected to the network described above and transmits and receives various data with other devices such as the server S. The data communication unit 31 can also communicate with the in-vehicle device VE and the user terminal MT via wireless communication such as Wi-Fi® or Bluetooth®, or via wired communication.

[0022] For example, the agent terminal 10 can communicate with the in-vehicle device VE of the vehicle M in which the agent terminal 10 is currently installed via the data communication unit 31 and obtain the device identifier of the in-vehicle device VE. As described above, the device identifier of the in-vehicle device VE can be seen as the identifier of the vehicle M in which the in-vehicle device VE is installed. Therefore, the agent terminal 10 can obtain information that helps identify the vehicle M in which the agent terminal 10 is currently installed through communication with the in-vehicle device VE via the data communication unit 31.

[0023] Furthermore, the agent terminal 10 can transmit voice information generated by the control unit 25 based on the voice input from the input unit 27 to the server S.

[0024] Furthermore, the agent terminal 10 can communicate with the user terminal MT and use the user terminal MT as a substitute for the input unit 27 or the output unit 29.

[0025] The driving information generation unit 33, which acts as a movement-related information acquisition unit or a mobile object information acquisition unit, includes, for example, a positioning device such as a GPS (Global Positioning System) device, an acceleration sensor, and a gyro sensor, and is capable of generating driving-related information, which is information relating to the driving of the automobile M. The positioning device included in the driving information generation unit 33 may be any device that can determine the position of the agent terminal 10 and, by extension, the automobile M, and may be other positioning devices, such as a device that can determine the position based on a nearby mobile phone network base station. The driving information generation unit 33 is capable of generating driving-related information that includes positioning information that can determine the position of the agent terminal 10, movement speed information, or acceleration information. The driving-related information may also include information relating to driving operations. In order to obtain information relating to such driving operations, the driving information generation unit 33 may be able to detect the operation of the steering wheel or accelerator and brakes of the automobile M by communicating with equipment installed in the automobile M.

[0026] The agent terminal 10 can transmit the driving-related information generated by the driving information generation unit 33 to other devices, including the server S, via the data communication unit 31.

[0027] Figure 3 shows the configuration of server S. For example, server S is a device in which a data communication unit 43, a large-capacity storage device 45, and a control unit 47 cooperate via a system bus 41.

[0028] The data communication unit 43 is connected to the network described above and transmits and receives various data between the agent terminal 10 and other devices such as other server DS. The data communication unit 43 can receive driving-related information from the agent terminal 10, including location information that can identify the location of the agent terminal 10. The data communication unit can also receive voice information from the agent terminal 10 that is generated based on the voice input into the input unit of the agent terminal 10.

[0029] The large-capacity storage device 45 is composed of, for example, a hard disk drive and an SSD (solid state drive), and stores various programs such as the operating system and server software.

[0030] Furthermore, the large-capacity storage device 45 stores the device identifier of the in-vehicle device VE of one or more automobiles M in which the agent terminal 10 is installed, and vehicle information including the vehicle type, inspection date, driving data, etc., associated with each of the device identifiers of the in-vehicle device VE of the one or more automobiles M. The large-capacity storage device 45 also stores setting information, including the tone and manner of voice of the voice emitted from the agent terminal 10 when installed in the automobile M, based on the voice information transmitted from the server S.

[0031] The above vehicle information is stored in the vehicle information database (indicated as "vehicle information DB" in the figure) 45A within the large-capacity storage device 45. The above configuration information is stored in the configuration information database (indicated as "configuration information DB" in the figure) 45B within the large-capacity storage device 45.

[0032] The large-capacity storage device 45 also contains a map information database (indicated as "Map Information DB" in the diagram) 45C, which stores map information including road maps. The map information in the map information database 45C is a database that contains information equivalent to, for example, the map information used in a navigation device.

[0033] The control unit 47 is composed of a CPU (Central Processing Unit) 47A, a ROM (Read Only Memory) 47B, a RAM (Random Access Memory) 47C, etc., and functions as a computer. The CPU 47A reads and executes various programs stored in the ROM 47B and the mass storage device 45 to realize various functions.

[0034] In this embodiment, a conversational AI application program is stored in the large-capacity storage device 45 or ROM 47. Therefore, the control unit 47 can execute the stored conversational AI application program and behave as an AI conversational robot.

[0035] Specifically, for example, the control unit 47 may interpret the content of the voice information transmitted from the agent terminal and generate a response voice if the voice information is a question. Alternatively, the control unit 47 may generate voice to be spoken under predetermined conditions, regardless of whether a question was asked. In generating this response or speech voice, the control unit 47 uses a database including the vehicle information database 45B and the map information database 45C as a knowledge base. In other words, the control unit 47 can function as a conversational robot using the vehicle information database 45B and the map information database 45C as its knowledge base.

[0036] In this embodiment, the agent terminal 10 may use only the information from the vehicle information database 45B that is linked to the vehicle M on which the agent terminal 10 is currently installed.

[0037] Furthermore, the large-capacity storage device 45 may include databases other than the vehicle information database 45B and the map information database 45C as a knowledge base. Alternatively, a database in another server DS, which is connected to server S in a communicative manner, may be used as a knowledge base.

[0038] Furthermore, when the control unit 47 interprets the content of the voice information transmitted from the agent terminal 10, if the voice is a command, it may perform a function in accordance with that command.

[0039] Furthermore, in this embodiment, a car navigation program is stored in the large-capacity storage device 45 or ROM 47. Therefore, the control unit 47 can execute the stored car navigation program and behave as a car navigation device. For example, if the voice information transmitted from the agent terminal 10 is a command requesting car navigation functionality, the control unit 47 may provide car navigation functionality using the car navigation program and map information database 45C.

[0040] Figure 4A shows an example of a configuration information table TB1 stored in the configuration information database 45A. A configuration information table TB1 is created for each agent terminal 10. The ID of the agent terminal 10 is listed in the upper left corner of the configuration information table TB1.

[0041] The configuration information table TB1 lists the device identifiers of the registered in-vehicle devices VE below the in-vehicle device ID column. The voice tone column describes the voice tone of the agent terminal 10 when it is installed in a vehicle M equipped with a specific in-vehicle device. The tone column also describes the tone of voice of the agent terminal 10 when it is installed in a vehicle M equipped with a specific in-vehicle device.

[0042] When the control unit 47 of server S functions as the AI ​​conversational robot described above, conversational voice is generated based on the tone and manner of speaking recorded in the configuration information table TB1, which is linked to the device identifier of the in-vehicle device VE.

[0043] The voice tone and intonation information contained in this configuration information table TB1 can be set and saved by the user when the agent terminal 10 is installed in a vehicle M that has not yet been registered, i.e., in a vehicle M in which the agent terminal 10 is installed for the first time. The contents of this setting can be entered through the input unit 27 of the agent terminal 10 or through a mobile terminal MT that can communicate with the agent terminal 10. The contents of this setting can also be saved in the configuration information database 45A when the entered settings are sent to the server S.

[0044] Figure 4B shows an example of a vehicle information table TB2 stored in the vehicle information database 45B. A vehicle information table TB2 is created for each agent terminal 10. The ID of the agent terminal 10 is listed in the upper left corner of the vehicle information table TB2.

[0045] The vehicle information table TB2 lists the device identifiers of the registered in-vehicle devices VE below the in-vehicle device ID column. The vehicle type column records vehicle data, including vehicle information such as the vehicle type of the car M on which each in-vehicle device VE is installed, maintenance data including maintenance and inspection information such as the vehicle inspection date of the car M, and driving data including the driving history of the car M.

[0046] In addition to the vehicle type of car M, or in place of the vehicle type, the vehicle's fuel type, passenger capacity, whether it is right-hand or left-hand drive, and vehicle size may also be included in the vehicle information. Furthermore, the maintenance and inspection information for car M may include information such as the oil change date or wiper replacement date.

[0047] The vehicle information contained in this vehicle information table TB2 can be entered and saved by the user when the agent terminal 10 is installed in a vehicle M that has not yet been registered, for example, when the agent terminal 10 is installed in a vehicle M for the first time. This vehicle information can be entered through the input unit 27 of the agent terminal 10, or through a mobile terminal MT that can communicate with the agent terminal 10. This vehicle information can also be saved in the vehicle information database 45B when the entered vehicle information is transmitted to the server S.

[0048] Furthermore, the driving history may include, for example, the departure point, destination, and stops of the vehicle M, the driving route of the vehicle M, the driving speed, and the acceleration history. The information included in the driving history may be generated based, for example, on driving-related information transmitted from the agent terminal 10 when the agent terminal 10 is installed in the vehicle M, and map information stored in the map information database 45C. Note that the driving data can be updated at any time while the agent terminal 10 is installed in the vehicle M.

[0049] [2. Control Routines] The following describes the method of Example 1 and the control routines for realizing the system including the agent terminal 10 and the server S. In the diagrams of the routines used in the following description, the dashed lines schematically represent the transmission and reception of notifications or data between the agent terminal 10 and the server S.

[0050] [2-1. Driving Data Recording Routine] Figure 5 shows the driving data recording routine R1 that is executed by the agent terminal 10 and the server S when the user brings the agent terminal 10 into the automobile M, that is, when the agent terminal 10 is installed in the automobile M. The routine executed by the agent terminal 10 is shown as R1A, and the routine executed by the server S is shown as R1B.

[0051] For example, routines R1A and R1B may be started when agent terminal 10 and server S are activated, respectively, and then executed repeatedly thereafter.

[0052] When the control unit 25 of the agent terminal 10 (hereinafter referred to simply as "agent terminal 10" in the routine description) starts routine R1A, it first determines in step S11A whether the accessory power supply (hereinafter referred to as ACC power supply) of the vehicle M on which it is installed is turned on (step S11A). This determination may also be made by the agent terminal 10 attempting to establish communication with the in-vehicle device VE. That is, if communication is established, it is determined that the power to the in-vehicle device VE is on and the ACC power supply is on. If communication is not established, it is determined that the power to the in-vehicle device VE is off and the ACC power supply is not on.

[0053] In step S11A, if it is determined that the ACC power is not turned on (step S11A: NO), monitoring of the ACC power continues. In step S11A, if it is determined that the ACC power is turned on (step S11A: YES), the device identifier (vehicle device ID) of the in-vehicle device VE is acquired (step S12A). That is, in S12A, the control unit 25 functions as a mobile object identification information acquisition unit. When step S12A is completed, the terminal identifier (terminal ID) of the agent terminal 10 and the acquired vehicle device ID of the in-vehicle device VE are sent to the server S (step S13A).

[0054] When the control unit 47 of server S (hereinafter referred to simply as "server S" in the description of the routine) starts routine R1B, it first waits in step S11B for the reception of the terminal ID and in-vehicle device ID of the agent terminal 10 (step S11B). Then, in step S12B, it determines whether or not the terminal ID and in-vehicle device ID transmitted in step S13A have been received (step S12B).

[0055] In step S12B, if it is determined that the terminal ID and in-vehicle device ID have not yet been received (step S12B: NO), the system waits for a certain period of time for these IDs to be received, and then step S12B is executed again.

[0056] In step 12B, if it is determined that the terminal ID and the in-vehicle device ID have been received (step S12B: YES), it is determined whether the combination of the received terminal ID and in-vehicle device ID is registered in the configuration information database 45A and the vehicle information database 45B (step S13B). This determination can be made by checking whether there is a table in the configuration information table TB1 in the configuration information database 45A and the vehicle information table TB2 in the vehicle information database 45B that contains the received terminal ID, and whether the received in-vehicle device ID is recorded in that table.

[0057] In step S13B, if it is determined that the in-vehicle device VE is not registered (step S13B: NO), the server S requests registration information, including configuration information and vehicle information, from the agent terminal 10 (step S14B), and then the server-side information registration subroutine is executed (step S15B). In this server-side information registration subroutine, configuration information related to conversational voice, such as tone and manner of speaking, and vehicle information are received from the agent terminal 10, and this information is stored in association with the in-vehicle device ID of the in-vehicle device VE to be registered. In subsequent processing, information transmitted from the agent is stored in association with the in-vehicle device ID saved and registered in step S15B.

[0058] In step S13B, if it is determined that the in-vehicle device VE is registered (step S13B: YES), then in subsequent processing, the information transmitted from the agent terminal 10 is stored in association with the registered in-vehicle device VE.

[0059] After step S13A is completed, the agent terminal 10 determines whether or not it has received the registration information request sent in step S14B on the server S side (step S14A). This determination may be made by determining whether or not the registration information request was received within a certain period of time after the completion of step S13A.

[0060] If it is determined in step S14A that a request for registration information has been received (step S14A: YES), the agent-side information registration subroutine is executed (step S15A). This agent-side information registration subroutine receives input from the user regarding settings information related to conversational voice, such as tone and manner of speaking, and vehicle information, and processes this information to send to the server S. If it is determined in step S14A that a request for registration information has not been received (step S14A: NO), step S16A is executed.

[0061] After the subroutine in step S15B is completed, server S sends a notification to agent terminal 10 to start recording driving data and waits for the reception of data for recording driving data (step S16B).

[0062] After the completion of the subroutine in step S15A, the agent terminal 10 determines whether or not it has received a notification to start recording driving data (step S16A). This determination may be made by determining whether or not it has received the notification to start recording driving data within a certain period of time after the completion of step S15A.

[0063] In step S16A, if it is determined that a notification to start recording driving data has been received (step S16A: YES), the transmission of driving data, including, for example, the driving-related information of the agent terminal 10 described above, is started to the server S (step S17A). This transmission of driving data may be done continuously, or intermittently or intermittently at regular or uneven time intervals. In step S16A, the transmitted data is received by the server S and stored in the vehicle information database 45B linked to the in-vehicle device ID.

[0064] If it is determined in step S16A that a notification to start recording driving data has not been received (step S16A: NO), step S16A will be executed again after a certain period of time.

[0065] After step S17A, in step S18A, it is determined whether or not the ACC power supply of the vehicle M has been turned off. This determination may be made by the agent terminal 10 attempting to establish communication with the in-vehicle device VE. That is, if communication is established, it is determined that the power supply to the in-vehicle device VE is on and the ACC power supply is not turned off. If communication is not established, it is determined that the power supply to the in-vehicle device VE is off and the ACC power supply is turned off.

[0066] In step S18A, if it is determined that the ACC power is not turned off (step S8: NO), the transmission of driving data (step S17A) continues, and after a certain period of time, step S18A is executed again.

[0067] In step S18A, if it is determined that the ACC power supply has been turned off (step S18A: YES), a data transmission completion notification is sent to server S (step S19A), and routine R1A terminates.

[0068] After step S16B is completed, server S determines whether or not it has received the data transmission completion notification sent by agent terminal 10 in step S19A (step S17B). If it is determined in step S17B that the data transmission completion notification has not been received (step S17B: NO), the waiting for the receipt of driving data continues (step S16B), and after a certain period of time, step S17B is executed again.

[0069] In step S17B, if it is determined that a data transmission completion notification has been received (step S17B: YES), the data reception waiting is terminated (step S18B), and then routine R1B terminates.

[0070] [2-2. Information Registration Subroutine] Figure 6 shows the information registration subroutine R2 within the driving data recording routine R1. The routine executed by the agent terminal 10 is denoted as R2A, and the routine executed by the server S is denoted as R2B.

[0071] When the agent terminal 10 starts routine R2A, it first waits for input of registration information, including vehicle information and configuration information (step S21A). This may be done, for example, by prompting the user to input registration information, including vehicle information and configuration information, via voice or images using the output unit 29 of the agent terminal 10, and accepting the input via the input unit 27. In this case, the input may be made via a mobile terminal MT that can communicate with the agent terminal 10 instead of the input unit 27.

[0072] After step S21A is completed, it is determined whether or not the input of registration information has been completed (step S22A). This determination may be made by whether or not a certain amount of time has elapsed or whether or not the user has indicated their intention to complete the input of registration information via the input unit 27 or the mobile terminal MT. If it is determined in step S22A that the input has not been completed (step S22A: NO), the waiting for the input of registration information (step S21A) continues, and after a certain amount of time, step S22A is executed again.

[0073] The vehicle information entered in steps 21A and 22A may include, for example, the vehicle inspection date and vehicle type included in the table TB1 described above, as well as vehicle specifications, vehicle size, type of fuel used, passenger capacity, left-hand drive or right-hand drive, etc. In other words, in steps 21A and 22A, the control unit 25 functions as a mobile vehicle information acquisition unit.

[0074] Furthermore, the setting information input in steps 21A and 22A is voice setting information that includes at least one of the tone and manner of voice of the voice output from the output unit of the agent terminal 10 included in table TB2. In other words, in steps 21A and 22A, the control unit 25 also functions as a voice setting information receiving unit.

[0075] In step S22A, if it is determined that input has finished (step S22A: YES), the received registration information is sent to server S (step S23A), and routine R2A ends.

[0076] When the server device S starts routine R2B, it first waits for registration information to be received from the agent terminal 10 (step S21B). After that, the server device S determines whether or not registration information has been received from the agent terminal 10 (step S22B). If it is determined in step S22B that registration information has not been received (step S22 B:NO) and the waiting for registration information (step S21B) continues, and after a certain period of time, step S22B is executed again.

[0077] In step S22B, the server device S determines that registration information has been received (step S22B: YES). In step S12B of routine R1B, the received registration information is linked to the in-vehicle device ID received, and the configuration information is saved in the configuration information database 43A, and the vehicle information is saved in the vehicle information database 43B (step S23B). After step S23B is executed, routine R2B terminates.

[0078] [2-3. Conversation Routines] Figures 7 and 8 show the conversation routine R3 executed by the agent terminal 10 and the server S when the server S communicates with the user via the agent terminal 10, i.e., when the user brings the agent terminal 10 into the car M, i.e., when the agent terminal 10 is installed in the car M. The routine executed by the agent terminal 10 is denoted as R3A, and the routine executed by the server S is denoted as R3B.

[0079] For example, routines R3A and R3B may be started when agent terminal 10 and server S are activated, respectively, and then executed repeatedly.

[0080] When the agent terminal 10 starts routine R3A, it first determines in step S31A whether the ACC power supply of the vehicle M on which it is installed is turned on (step S31A). This determination may also be made by the agent terminal 10 attempting to establish communication with the in-vehicle device VE. That is, if communication is established, it is determined that the power supply to the in-vehicle device VE is on and the ACC power supply is on. If communication is not established, it is determined that the power supply to the in-vehicle device VE is off and the ACC power supply is not on.

[0081] In step S31A, if it is determined that the ACC power is not turned on (step S31A: NO), step S31A is executed again after a certain period of time. In step S31A, if it is determined that the ACC power is turned on (step S31A: YES), the vehicle device ID of the vehicle device VE is obtained (step S32A). When step S32A is completed, the terminal identifier (terminal ID) of the agent terminal 10 and the obtained vehicle device ID of the vehicle device VE are sent to the server S (step S33A).

[0082] When server S starts routine R3B, it first waits in step S31B for the terminal ID and in-vehicle device ID of the agent terminal 10 to be received (step S31B). Then, in step S32B, it determines whether or not the terminal ID and in-vehicle device ID transmitted in step S33A have been received (step S32B).

[0083] In step S32B, if it is determined that the terminal ID and in-vehicle device ID have not yet been received (step S32B: NO), the system waits for a certain period of time for these IDs to be received, and then step 32B is executed again.

[0084] In step 32B, if it is determined that the terminal ID and the in-vehicle device ID have been received (step S32B: YES), it is determined whether the combination of the received terminal ID and in-vehicle device ID is registered in the configuration information database 45A or the vehicle information database 45B (step S33B). This determination can be made by checking whether there is a table in the configuration information table TB1 in the configuration information database 45A or the vehicle information table TB2 in the vehicle information database 45B that contains the received terminal ID, and whether the received in-vehicle device ID is listed in that table.

[0085] In step S33B, if it is determined that the in-vehicle device VE is not registered (step S33B: NO), routine R3B terminates. If server S determines in step S33B that the in-vehicle device VE is registered (step S33B: YES), it sends a conversation waiting notification to agent 10 and starts waiting for a conversation (step S34B). In this conversation waiting state, server S waits to receive voice data from agent terminal 10. Also in this conversation waiting state, server S performs speech processing as needed, depending on the situation, for example, based on driving data received by routine R1.

[0086] When step S33A is completed, the agent terminal 10 determines in step S34A whether or not it has received a conversation waiting notification sent from the server S in step S33B. This determination can be made by determining whether or not it has received a conversation waiting notification within a predetermined time after the completion of step 33A, that is, after sending the terminal ID and the in-vehicle device ID to the server S.

[0087] If the agent terminal 10 determines in step S34A that it did not receive a conversation waiting notification (step S34A: NO), it determines that the in-vehicle device ID of the in-vehicle device VE was not registered in the server S, and terminates routine R3A. As described above, routine R3A is executed repeatedly. Therefore, if, for example, the information registration subroutine R2 described above is executed during the repeated execution of routine R3A and the in-vehicle device ID of the in-vehicle device VE is registered, the determinations in steps S33B and S34A may change.

[0088] In step S34A, the agent terminal 10 determines that it has received a conversation waiting notification (step S34A: YES) and starts conversation waiting (step S35A). In this conversation waiting state, the agent terminal 10 maintains the state of accepting voice input via the input unit 27 or the mobile terminal MT. In this conversation waiting state, the agent terminal 10 is also waiting to receive voice information from the server device S.

[0089] After entering a conversation standby state, the agent terminal 10 determines whether or not there has been voice input via the input unit 27 or the mobile terminal MT (step S36A). If the agent terminal 10 determines in step S36A that there has been voice input (step S36A: YES), it converts the input voice into data and sends it to the server S (step S37A).

[0090] In step S36A, the agent terminal 10 determines that there was no voice input (step 36A: NO), or after executing step S37A, it determines in step S38A whether or not it has received voice data from the server S. This determination may also be made based on whether or not voice data has been received from the server S within a certain period of time after the determination in step S36A or after the execution of step S37A.

[0091] If the agent terminal 10 determines in step S38A that it has received voice data (step S38A: YES), it generates voice based on the voice data and outputs the voice as provided information via the output unit 29 or the mobile terminal MT (step S39A). The voice may be output from the built-in speaker of the agent terminal 10, or it may be output from an in-vehicle device VE such as a car stereo that is connected to the agent terminal.

[0092] The agent terminal 10 determines in step S38A that it did not receive voice data (step S38A: NO), or after executing step S39A, it determines whether the ACC power of the vehicle M has been turned off (step S310A). This determination may also be made by the agent terminal 10 attempting to establish communication with the in-vehicle device VE. That is, if communication is established, it is determined that the power to the in-vehicle device VE is on and the ACC power is not turned off. If communication is not established, it is determined that the power to the in-vehicle device VE is off and the ACC power is turned off.

[0093] If it is determined in step S310A that the ACC power is not turned off (step S310A: NO), the conversation waiting state is maintained and S36A is executed again.

[0094] In step S310A, if it is determined that the ACC power supply has been turned off (step S310A: YES), a conversation waiting completion notification is sent to server S (step S311A), and routine R3A terminates.

[0095] After step S34B is completed and the server device S enters a conversation waiting state, in step S35B, it determines whether or not it has received voice data from the agent terminal 10. If the server device S determines in step S35B that it has received voice information (step S35B: YES), it analyzes the voice data and determines whether or not a response is required (step S36B).

[0096] This determination is made, for example, by whether the content of the audio is a conversation between passengers of car M. For example, if the content of audio 1 is in the form of a question, but there is another audio immediately following that answer, it may be determined that the content of the audio is a conversation between passengers of car M, and therefore no response is required. Alternatively, for example, if the content of audio 1 is in the form of a question, and there is no other audio for a certain period of time, it may be determined that the audio is a question from a passenger of car M to server S, and therefore a response is required.

[0097] If the server device S determines in step S35B that it has not received voice information, it determines whether or not a speech condition has been met (step S37B). This determination may be made, for example, based on driving-related information transmitted from agent 10. For example, if an anomaly in the mobile vehicle M, such as dangerous driving, is detected based on driving-related information, it is determined that a speech condition has been met. When a speech condition is met, advice regarding driving operations generated based on driving-related information may be generated.

[0098] If the server device S determines in step S36B that a response is required (step S36B: YES) or determines in step S37B that a speech condition has occurred (step S37B: YES), it generates voice data and sends it to the agent terminal 10 (step S38B).

[0099] This voice data is generated based on the analysis in the determination in step S36, or based on the speech conditions in step S37B. Alternatively, this voice data may be generated based on the knowledge-based vehicle information database 45B and the map information database 45C.

[0100] For example, advice regarding driving operations generated based on the above-mentioned driving-related information may be generated as provided information and transmitted as voice data. This voice data is generated based on at least one of the voice tone and intonation stored in table TB1, linked to the on-board device ID of the on-board device VE.

[0101] The server device S determines in step 36B that a response is not necessary (step S36B), or in step 37B that no speech conditions have been met (step S37B), or, after step 38B is completed, determines whether a conversation waiting end notification has been received from the agent terminal 10 (step S39B).

[0102] In step 39B, if it is determined that no conversation waiting end notification has been received (step S39B: NO), the conversation waiting state is maintained and step S35B is executed again. In step 39B, if it is determined that a conversation waiting end notification has been received, the conversation waiting state is released and routine R3B terminates.

[0103] The conversations that take place in the above conversation routine include the following: For example, if the user asks, "When is my next vehicle inspection?", the server S generates a response, and the agent terminal 10 outputs, "It's on [date] this year." Also, for example, if the user asks, "How many kilometers are left to my destination?", the server S accesses the map information database 45C to generate a response, and the agent terminal 10 outputs, "You have XX km left."

[0104] Furthermore, when the user commands, "Make a reservation at our usual restaurant this coming Saturday night," server S accesses another server DS to generate a response, and agent terminal 10 outputs, "A reservation is available at [time]. Would you like to make the reservation?"

[0105] Furthermore, when a user asks, "Where did I go to have fun at the end of last month?", server S accesses the vehicle information database 45B to generate a response, and agent terminal 10 outputs, "At the end of last month, you went to XX amusement park."

[0106] Furthermore, if a user says "I'm hungry" to express their current feelings, Server S will determine what kind of food the user likes based on their past restaurant visit history. For example, if it determines that the user likes ramen, it will output "There is a famous ramen shop 1km away. Do you want to set it as a stopover point?"

[0107] As described above, in the system 100 including the agent terminal 10 of this embodiment, various information is managed in association with the in-vehicle device ID of the in-vehicle device VE, which is information that can identify the automobile M. Therefore, the agent terminal 10 can provide information based on the information stored in association with the in-vehicle device ID on which the agent terminal 10 is installed.

[0108] Specifically, the agent terminal 10 can, for example, provide information based on the driving history of the vehicle in which the agent terminal 10 is installed, in voice based on the settings made for that vehicle. Therefore, even if the agent terminal 10 can be installed in multiple different automobiles M, it is possible to provide information that is suitable for each automobile M. [Examples]

[0109] [1. System Configuration and Operation] Below, an information provision system 100 including an agent terminal 10 as an information provision device and an information provision method, which are two embodiments of the present invention, will be described with reference to the attached drawings. In two embodiments, the overall configuration of the system 100 and the configurations of the agent terminal 10 and the server S are the same as in one embodiment.

[0110] Figure 9A shows an example of a configuration information table TB3 stored in the configuration information database 45A. A configuration information table TB3 is created for each agent terminal 10. The ID of the agent terminal 10 is listed in the upper left corner of the configuration information table TB3.

[0111] Unlike the configuration information table TB1 (see Figure 4A) in Example 1, in the configuration information table TB3, the vehicle identifiers set for each vehicle M are listed under the vehicle identifier column in the form of nicknames such as "Bill" and "Jennifer".

[0112] The vehicle device IDs for the vehicle device VE are listed below the vehicle device ID column. The voice tone column describes the voice tone when the agent terminal 10 is installed in a vehicle M that has been given a specific identifier (nickname). The tone column describes the tone of voice when the agent terminal 10 is installed in a vehicle M that has been given a specific identifier (nickname). In other words, in Example 2, the vehicle identifier (nickname) is associated with the vehicle device ID, as well as the voice tone and tone of voice.

[0113] When the control unit 47 of server S functions as an AI conversational robot as described in Example 1, conversational audio is generated based on the voice tone and manner of speaking recorded in the configuration information table TB3, which is associated with the vehicle identifier (nickname).

[0114] The voice tone and intonation information contained in this configuration information table TB3 can be set and saved by the user when the agent terminal 10 is installed in a vehicle M that has not yet been registered, i.e., in a vehicle M in which the agent terminal 10 is installed for the first time. The contents of this setting can be entered through the input unit 27 of the agent terminal 10 or through a mobile terminal MT that can communicate with the agent terminal 10. The contents of this setting can also be saved in the configuration information database 45A when the entered settings are sent to the server S.

[0115] Figure 9B shows an example of a vehicle information table TB4 stored in the vehicle information database 45B. Unlike the configuration information table TB2 in Example 1 (see Figure 4B), in the configuration information table TB4, the vehicle identifiers set for each vehicle M are listed below the vehicle identifier column in the form of nicknames such as "Bill" and "Jennifer". A vehicle information table TB4 is created for each agent terminal 10. The ID of the agent terminal 10 is written in the upper left corner of the vehicle information table TB4.

[0116] In the vehicle information table TB4, the device identifiers of the registered in-vehicle devices VE are listed below the in-vehicle device ID column. In the vehicle type column, for example, vehicle data including vehicle information such as the vehicle type of the automobile M on which each in-vehicle device VE is installed, maintenance data including maintenance and inspection information such as the vehicle inspection date of the automobile M, and driving data including the driving history of the automobile M are recorded. In other words, in Example 2, the vehicle identifier (nickname) is linked to the in-vehicle device ID, as well as the vehicle data, maintenance and inspection data, and driving data.

[0117] In addition to the vehicle type of car M, or in place of the vehicle type, the vehicle's fuel type, passenger capacity, whether it is right-hand or left-hand drive, and vehicle size may also be included in the vehicle information. Furthermore, the maintenance and inspection information for car M may include information such as the oil change date or wiper replacement date.

[0118] The vehicle information contained in this vehicle information table TB4 can be entered and saved by the user when the agent terminal 10 is installed in a vehicle M that has not yet been registered, i.e., when the agent terminal 10 is installed in a vehicle M for the first time. This vehicle information can be entered through the input unit 27 of the agent terminal 10, or through a portable terminal MT that can communicate with the agent terminal 10. This vehicle information can also be saved in the vehicle information database 45B when the entered vehicle information is transmitted to the server S.

[0119] Furthermore, the driving history may include the departure point, destination, and stops of the vehicle M, the driving route, driving speed, and acceleration history of the vehicle M. The information included in the driving history may be generated, for example, based on driving-related information transmitted from the agent terminal 10 when the agent terminal 10 is installed in the vehicle M, and map information stored in the map information database 45C. Note that the driving data can be updated at any time while the agent terminal 10 is installed in the vehicle M.

[0120] [2. Control Routines] The method of Example 2 and the control routines for realizing the system including the agent terminal 10 and server S are described below. Note that the driving data recording routine and conversation routine are the same as in Example 1, so their explanation is omitted.

[0121] In Example 2, when registering information, the user enters a vehicle identifier in addition to the registration information from Example 1, and this is registered in the database of Server S. The registration information is then stored linked to the vehicle identifier (nickname).

[0122] [2-1. Information Registration Subroutine] Figure 10 shows the information registration subroutine R4 in Example 2. The routine executed by the agent terminal 10 is denoted as R4A, and the routine executed by the server S is denoted as R4B.

[0123] When the agent terminal 10 starts routine R4A, it first waits for a selection between registering new information or changing vehicles (step S41A). This may be done, for example, by prompting the user to select whether to register new information or change vehicles by using voice or images via the output unit 29 of the agent terminal 10, and then accepting the selection input via the input unit 27.

[0124] In this case, input may be performed via a mobile terminal MT that can communicate with the agent terminal 10, instead of the input unit 27.

[0125] When step S41A is completed, the agent terminal 10 determines whether or not to perform a vehicle replacement (step S42A). This determination is made based on whether or not vehicle replacement was selected in step S41A.

[0126] In step S42A, if agent terminal 10 determines that a vehicle replacement is occurring (step S42A: YES), it sends a vehicle replacement process start notification to server S (step S43A) and starts the vehicle replacement subroutine (step S44A). When the subroutine in step S44A finishes, routine R4A finishes.

[0127] In the vehicle replacement subroutine, the agent terminal 10 receives from the server S a set of one or more vehicle identifiers stored for the agent terminal 10 and the vehicle information associated with those one or more identifiers.

[0128] The user then selects a vehicle identifier, which is a nickname, that they want to transfer to the new vehicle M they are currently riding in, and the result of this selection is sent to server S. Server S then removes the information specific to vehicle M (in-vehicle device VE) that was previously associated with the selected vehicle identifier, and transfers the remaining information (vehicle information and configuration information that is not specific to vehicle M) to the vehicle M that the user is currently riding in, i.e., the vehicle M on which agent terminal 10 is currently installed.

[0129] If the agent terminal 10 determines in step S42A that it is not a vehicle replacement (step S42A: NO), it starts the new information registration process and waits for input of the vehicle identifier and registration information (step S45A). This may be done, for example, by prompting the user to input registration information, including a nickname, vehicle information, and setting information, via voice or image using the output unit 29 of the agent terminal 10, and accepting the input via the input unit 27. In this case, the input may be made via a mobile terminal MT that can communicate with the agent terminal 10 instead of the input unit 27.

[0130] In other words, in step S45A, an identifier 1 is assigned to the automobile M on which the agent terminal 10 is currently installed. To put it another way, in step S45A, the control unit 25 of the agent terminal 10 functions as an assignment receiving unit.

[0131] After step S45A is completed, the agent terminal 10 determines whether the input of the vehicle identifier and registration information has been completed (step S46A). This determination may be made by whether a certain period of time has elapsed or whether the user has indicated their intention to complete the input of the registration information via the input unit 27 or the mobile terminal MT. If it is determined in step S46A that the input has not been completed (step S46A: NO), the waiting for the input of the vehicle identifier and registration information (step S45A) continues, and after a certain period of time, step S46A is executed again.

[0132] In step S46A, if it is determined that the input has finished (step S46A: YES), the received vehicle identifier and registration information are sent to server S (step S47A), and routine R4A ends.

[0133] When the server device S starts routine R4B, it first waits for information to be received from the agent terminal 10 (step S41B). Then, the server device S determines whether or not it has received a notification from the agent terminal 10 to start the vehicle replacement process (step S42B). This determination may be made based on whether or not the vehicle replacement process notification is received within a certain period of time.

[0134] In step S42B, if it is determined that a notification to start the vehicle replacement process has been received (step S42: YES), the vehicle replacement subroutine is started (step S43B).

[0135] In step S42B, if server S determines that it has not received a notification to start the vehicle replacement process (step S42B: NO), it starts the new information registration process and determines whether or not it has received the vehicle identifier and registration information from agent terminal 10 (step S44B). This determination may be made based on whether or not the vehicle identifier and registration information are received within a certain period of time.

[0136] If server S determines in step S44B that it has received a vehicle identifier and registration information, it stores the received registration information and the in-vehicle device ID of the in-vehicle device VE on which agent terminal 10 is currently installed, associating them with the received vehicle identifier (step S45B), and then routine R4B ends.

[0137] If server S determines in step S44B that it has not received the vehicle identifier and registration information, it temporarily suspends the new information registration process and executes step S42B again.

[0138] [2-2. Vehicle Replacement Subroutine] Figure 11 shows the vehicle replacement subroutine R5 in Example 2. The routine executed by the agent terminal 10 is denoted as R5A, and the routine executed by the server S is denoted as R5B.

[0139] As described above, in the vehicle replacement subroutine, the agent terminal 10 receives from the server S a set of vehicle identifiers (nicknames) stored for the agent terminal 10 and the vehicle information associated with those vehicle identifiers. The user then selects a vehicle identifier, which is a nickname, that they want to transfer to the new vehicle M they are currently riding in, and the result of this selection is sent to the server S. The server S then removes the information specific to the vehicle M (in-vehicle device VE) that was previously associated with the selected vehicle identifier, and transfers the remaining information (vehicle information and configuration information that is not specific to the vehicle M) to the vehicle M that the user is currently riding in, i.e., the vehicle in which the agent terminal 10 is currently installed.

[0140] When routine R5A is started, agent terminal 10 waits to receive the vehicle identifier and the registration information associated with it (step S51A).

[0141] When routine R5B is started, server S sends one or more sets of vehicle identifiers and registration information contained in tables TB3 and TB4 corresponding to the terminal ID of agent terminal 10 within server S, and waits for the agent terminal 10 to receive one vehicle identifier selected by the user (step S51B).

[0142] After executing step S51A, the agent terminal 10 determines whether or not it has received the vehicle identifier and registration information (step S52A). If there is no vehicle identifier stored in the agent terminal 10, a message to that effect is sent to the agent terminal 10, and this is considered to have resulted in the transmission of the set of vehicle identifier and registration information.

[0143] If the agent terminal 10 determines in step S52A that it has received a vehicle identifier, etc. (step A52A: YES), it waits for the user to select one nickname from the one or more vehicle identifiers that it has received (step S53A). In other words, in step S53A, the control unit 25 of the agent terminal 10 functions as an assignment reception unit that accepts the assignment of changes.

[0144] This may be done, for example, by prompting the user to select a vehicle identifier, which is a nickname to be transferred to the unregistered vehicle M currently in use, via voice or image using the output unit 29 of the agent terminal 10, and accepting the selection input via the input unit 27.

[0145] In this case, input may be performed via a mobile terminal MT that can communicate with the agent terminal 10, instead of the input unit 27.

[0146] If the agent terminal 10 determines in step S52A that it has not received the vehicle identifier, etc. (step S52A: NO), it will execute step S52A again after a certain period of time has elapsed.

[0147] After step S53A is completed, the agent terminal 10 determines whether the vehicle identifier selection input has been completed (step S54A). This determination may be made by whether a certain amount of time has elapsed or whether the user has indicated their intention to complete the input of registration information via the input unit 27 or the mobile terminal MT. If it is determined in step S54A that the selection input has not been completed (step S54A: NO), the waiting for vehicle identifier selection input (step S53A) continues, and after a certain amount of time, step S54A is executed again.

[0148] In step S54A, if it is determined that the selection input has been completed (step S54A: YES), the agent terminal 10 sends the selected vehicle identifier to the server and waits for a response from the server (step S55A).

[0149] If Server S determines in step S52B that the selected vehicle identifier has not been received (step S52B: NO), it executes step S52B again after a certain period of time. If Server S determines in step S52 that the selected vehicle identifier has been received (step S52B: YES), it deletes the vehicle-specific information associated with the selected vehicle identifier, which is information specific to or unique to the currently registered vehicle M, and queries Agent Terminal 10 for the vehicle-specific information of the newly registered vehicle M (step S53B).

[0150] For example, the vehicle-specific information to be deleted includes at least one of the following: information relating to the characteristics of vehicle M and information relating to the maintenance of vehicle M. The information relating to the characteristics of vehicle M includes information relating to the physical characteristics of vehicle M. This information relating to physical characteristics may include, for example, the vehicle type, vehicle specifications, vehicle size, type of fuel used, passenger capacity, and whether it is left-hand or right-hand drive. The information relating to the maintenance of vehicle M may include scheduled maintenance dates such as oil changes and parts replacements, or vehicle inspection dates.

[0151] Furthermore, the information deleted in step S53B may include driving data that depends on the characteristics of the vehicle M and is not suitable for the new vehicle M. Specifically, for example, if vehicle M changes from a gasoline car to an electric car, gas stations included in the list of stops may be deleted; if the vehicle changes from a small car to a large car, roads where large vehicles are prohibited may be deleted from the route; and if the vehicle becomes taller, the usage history of parking lots with height restrictions may be deleted. By deleting information that is not suitable for the new vehicle in this way, even facilities that were frequently used in the past may not be recommended via the agent terminal if they are no longer available to the new vehicle M.

[0152] After step S55A is completed, agent terminal 10 determines whether or not a query has been received from server S (step S56A). If agent terminal 10 determines in step S56A that no query has been received (step S56A: NO), it executes step S56A again after a certain period of time.

[0153] In step S56A, the agent terminal 10 determines that it has received an inquiry (step S56A: YES) and waits for input of vehicle-specific information (step S57A). This may be done, for example, by prompting the user to input vehicle-specific information of the unregistered car M currently in use via voice or image using the output unit 29 of the agent terminal 10, and accepting the input via the input unit 27.

[0154] In this case, input may be performed via a mobile terminal MT that can communicate with the agent terminal 10, instead of the input unit 27.

[0155] After step S57A is completed, the agent terminal 10 determines whether the vehicle identifier selection input has been completed (step S58A). This determination may be made by whether a certain amount of time has elapsed or whether the user has indicated their intention to complete the input of registration information via the input unit 27 or the mobile terminal MT. If it is determined in step S58A that the selection input has not been completed (step S58A: NO), the waiting for vehicle identifier selection input (step S57A) continues, and after a certain amount of time, step S58A is executed again.

[0156] The vehicle-specific information entered in steps 57A and S58A may include, as described above, the vehicle inspection date and vehicle type included in the table TB3 described above, as well as vehicle specifications, vehicle size, type of fuel used, passenger capacity, left-hand drive or right-hand drive, etc. In other words, in steps 57A and 58A, the control unit 25 functions as a mobile information acquisition unit.

[0157] Furthermore, the setting information input in steps 57A and 58A is voice setting information that includes at least one of the tone and manner of voice of the voice output from the output unit of the agent terminal 10 included in table TB4. In other words, in steps 57A and 58A, the control unit 25 also functions as a voice setting information receiving unit.

[0158] In step S58A, if it is determined that the selection input has been completed (step S58A: YES), the agent terminal 10 sends the entered vehicle-specific information to the server S (step S59A), and routine R5A ends.

[0159] After step S53B is completed, server S determines whether or not vehicle-specific information has been received from agent terminal 10 (step S54B). If server S determines in step S54B that vehicle-specific information has not been received (step S54B: NO), it executes step S54B again after a certain period of time. If server S determines in step S54 that vehicle-specific information has been received (step S54B: YES), it associates the received vehicle-specific information with the vehicle identifier received in step S52B, i.e., the nickname selected by the user, and saves it (step S55B), and routine R5B ends.

[0160] In routine R5 of Example 2, step S53B deletes vehicle-specific information, which is information unique to vehicle M among the registration information associated with the vehicle identifier. However, it is also possible to disable and retain the vehicle-specific information and additionally save the vehicle-specific information of newly registered vehicle M. In that case, the disabled vehicle-specific information will not be used as a source of information for conversation generation in conversation routine R3.

[0161] In the second embodiment, in step S38B of the conversation routine R3, in which voice data is generated and sent to the agent terminal 10, the voice data is generated based on at least one of the tone of voice and intonation stored in table TB3 in association with the vehicle identifier.

[0162] According to the above embodiment 2, a nickname can be assigned to a vehicle by registering a vehicle identifier. Furthermore, by storing various information linked to the vehicle identifier, the familiar personality of the previous vehicle can be transferred to a newly acquired vehicle.

[0163] Furthermore, according to the above embodiment 2, by registering the vehicle identifier in the form of a nickname, users can perceive the vehicle as having a more familiar personality. In addition, by using the registered nickname as a keyword, it becomes possible to more accurately determine whether it is a conversation between occupants in the vehicle or a speech directed to the agent terminal 10, contributing to improved accuracy of the agent function.

[0164] For example, if agent terminal 10 responds to a passenger's comment like "I hope it's sunny tomorrow," the conversation may be interrupted, which can be annoying.

[0165] Therefore, in the above conversation routine R3, it is set to determine that a response is not necessary during a conversation involving multiple people. Even during a conversation between passengers, if a nickname is included before or after the utterance, such as "I hope it's sunny tomorrow, Bill" or "Bill, do you think it'll rain tomorrow?", it is determined that the utterance is directed to the agent terminal, and a response is required, and voice information is generated.

[0166] Up to this point, we have described an embodiment in which a user can assign a nickname as a vehicle identifier. However, even if a nickname can be freely assigned to the vehicle identifier, it may also be possible for the user to select from a set of attributes, such as "My Car 1" and "My Car 2". Furthermore, in the above embodiment, we described an example in which the agent terminal 10 stores various information in the large-capacity storage device 45 of the external server S. However, a storage unit may be provided within the agent terminal, and some or all of the various information may be stored in that storage unit.

[0167] In the above embodiment, if all of the various information held by the server S is stored in the memory unit of the agent terminal 10, a closed system may be constructed in which a conversational AI application program, a car navigation program, etc., are built into the agent terminal 10 and no connection is made to the server S.

[0168] Furthermore, in the above embodiment, in order to identify the vehicle M on which the agent is installed, the agent communicates with the in-vehicle device VE and obtains the in-vehicle device ID. However, instead, the agent terminal 10 may be equipped with a camera, and the agent 10 may identify the vehicle type of the vehicle M on which the agent is installed based on the image pattern of the interior structure captured by the camera.

[0169] Furthermore, although the above embodiment was described as an example in which the agent terminal 10 outputs the provided information as voice, the provided information may be output as an image instead, or in addition to this. For example, the provided information may be displayed as text on an external heads-up display.

[0170] The configurations, routines, and display or input methods of the agent terminal, user terminal, in-vehicle device, or server in the above-described embodiments are merely examples and can be appropriately selected or modified depending on the application. For example, each step in the routine may be performed by the server, agent terminal, user terminal, or in-vehicle device, regardless of the above-described examples. [Explanation of Symbols]

[0171] 100 Information Provision System 10 Agent terminals 10 21,41 System bus 25,47 Control Unit 23,45 Mass storage 33 Driving Information Generation Unit S Server

Claims

[Claim 1] An information providing device that can be mounted on multiple mobile bodies, A movement-related information acquisition unit acquires movement-related information which is information relating to the movement of a moving object and is stored in association with the moving object. The aforementioned information providing device includes a mobile object identification information acquisition unit that acquires mobile object identification information, which is information that helps identify the mobile object currently mounted on it, When the mobile body 1 is identified based on the mobile body identification information, an information output unit outputs information based on the movement-related information associated with the mobile body 1, An information providing device characterized by having the following features.

Images