Information providing device, information providing method and program
The information providing device addresses the challenge of providing tailored responses across multiple vehicles by using vehicle-specific data to ensure personalized information delivery.
Patent Information
- Application Number
- JP2024148026
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2017-09-29
- Filing Date
- 2024-08-29
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2038-09-21
AI Technical Summary
Existing agent terminals struggle to provide tailored responses when mounted on multiple vehicles, as they lack the ability to identify and adapt to individual vehicles effectively.
An information providing device and method that acquires and utilizes vehicle-specific information, including a movement-related information acquisition unit and mobile object identification, to provide personalized information based on the vehicle's characteristics and history.
Enables the device to provide appropriate information to each vehicle it is mounted on, even when installed in multiple vehicles, by leveraging vehicle-specific data for personalized responses.
Smart Images

Figure 2024164247000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to an information providing device, and more particularly to an information providing device, an information providing method, and a program that, when mounted on a moving body, provides information to a passenger of the moving body. [Background technology]
[0002] Conventionally, an agent terminal has been proposed that authenticates individuals who use a vehicle and responds to the individuals by using agent data corresponding to each individual (Patent Document 1). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent No. 4664524 Summary of the Invention [Problem to be solved by the invention]
[0004] The agent terminal described in Patent Document 1 above is capable of responding appropriately to each individual by associating it with each person who uses the vehicle and learning the individual's preferences, etc. However, when the agent terminal may be installed in a number of different vehicles, one example of a problem is that it is difficult to make an appropriate response for each vehicle.
[0005] The present invention has been made in consideration of the above-mentioned points, and aims to provide an information providing device, an information providing method, and an information providing program that, when mounted on a moving body, are capable of providing information or responding appropriately to each moving body. [Means for solving the problem]
[0006] The invention described in claim 1 is an information providing device that can be mounted on multiple moving bodies, and is characterized in having a movement-related information acquisition unit that acquires movement-related information, which is information related to the movement of one moving body and is stored in association with the one moving body, a moving body identification information acquisition unit that acquires moving body identification information, which is information that contributes to identifying the moving body on which the information providing device is currently mounted, and an information output unit that outputs provided information based on the movement-related information associated with the one moving body when the one moving body is identified based on the moving body identification information.
[0007] The invention described in claim 7 is an information providing method for providing information using an information providing device that can be mounted on a plurality of moving bodies, the information providing device acquiring movement-related information, which is information related to the movement of one moving body and is stored in association with the one moving body; The method includes a step in which the information providing device acquires mobile unit identification information, which is information useful for identifying the mobile unit in which the information providing device is currently mounted, and a step in which the information providing device outputs provided information based on the movement-related information associated with the one mobile unit when the one mobile unit is identified based on the mobile unit identification information.
[0008] The invention described in claim 8 is a program that causes an information providing device that can be mounted on multiple moving bodies to execute the steps of acquiring movement-related information, which is information regarding the movement of one moving body and is stored in association with the one moving body; acquiring moving body identification information, which is information that helps identify the moving body on which the information providing device is currently mounted; and, when the one moving body is identified based on the moving body identification information, outputting provided information based on the movement-related information associated with the one moving body. [Brief description of the drawings]
[0009] [Figure 1] FIG. 1 is a diagram illustrating a system including an agent terminal according to a first embodiment of the present invention. [Diagram 2]2 is a block diagram showing an example of the configuration of an agent terminal in the system of FIG. 1. [Diagram 3] 2 is a block diagram showing an example of a configuration of a server in the system of FIG. 1. [Figure 4A] FIG. 4 is a diagram illustrating an example of a vehicle information table. [Figure 4B] FIG. 4 is a diagram illustrating an example of a vehicle information table. [Diagram 5] FIG. 1 is a flow diagram of an operation routine for implementing a system including an agent terminal according to a first embodiment of the present invention. [Figure 6] FIG. 2 is a flow diagram of an operation routine for implementing a system including an agent terminal according to the first embodiment of the present invention. [Figure 7] FIG. 2 is a flow diagram of an operation routine for implementing a system including an agent terminal according to the first embodiment of the present invention. [Figure 8] FIG. 2 is a flow diagram of an operation routine for implementing a system including an agent terminal according to the first embodiment of the present invention. [Figure 9A] FIG. 4 is a diagram illustrating an example of a vehicle information table. [Figure 9B] FIG. 4 is a diagram illustrating an example of a vehicle information table. [Figure 10] FIG. 11 is a flow diagram of an operation routine for realizing a system including an agent terminal according to a second embodiment of the present invention. [Figure 11] FIG. 11 is a flow diagram of an operation routine for realizing a system including an agent terminal according to a second embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS EXAMPLES
[0010] [1. System configuration and operation] An information provision system 100 including an agent terminal 10 as an information provision device according to a first embodiment of the present invention and an information provision method will be described below with reference to the accompanying drawings. Fig. 1 shows an information provision system 100 including an agent terminal 10 according to a first embodiment of the present invention. Specifically, the agent terminal 10 is, for example, a terminal having a function of a smart speaker.
[0011] As shown in Fig. 1, an information providing system 100 includes an agent terminal 10 and a server S (an example of a "server device"). Fig. 1 shows a case where the agent terminal is mounted on an automobile M, which is an example of a moving body.
[0012] The in-vehicle device VE is an in-vehicle device such as a car stereo installed in the automobile M. Each in-vehicle device 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. In the following explanation, the in-vehicle device VE is described as being permanently installed in the automobile M. Therefore, the device identifier of the in-vehicle device VE is described as being equivalent to the identifier of the automobile M itself. The user terminal MT is a portable terminal such as a smartphone brought by a user who is in the automobile M.
[0013] The agent terminal 10 and the server S are capable of transmitting and receiving data to and from each other via a network (communication path) using a communication protocol such as TCP / IP. The server S is also capable of transmitting and receiving data to and from other servers DS, such as an agent server capable of processing reservations for facilities such as hotels, via the network using a communication protocol such as TCP / IP. The network may be constructed, for example, by Internet communication including wireless communication such as a mobile communication network, Wi-Fi (registered trademark), and wired communication.
[0014] The agent terminal 10 is communicably connected to the in-vehicle device VE and the user terminal MT via wireless communication such as Wi-Fi (registered trademark) or Bluetooth (registered trademark) or wired communication.
[0015] 2 shows the configuration of the agent terminal 10. For example, the agent terminal 10 is a device in which a large-capacity storage device 23, a control unit 25, an input unit 27, an output unit 29, a data communication unit 31, and a driving information generation unit 33 cooperate with each other via a system bus 21.
[0016] The mass storage device 23 is composed of, for example, a hard disk device, a solid state drive (SSD), a flash memory, etc., and stores various programs such as an operating system and software for terminals. The various programs may be acquired, for example, from other server devices, etc., via a network, or may be recorded on a recording medium and read via various drive devices. In other words, the various programs stored in the mass storage device 23 (including a program for executing the processing in the agent terminal 10 of the processing described below) 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 configured with a CPU (Central Processing Unit) 25A, a ROM (Read Only Memory) 25B, a RAM (Random Access Memory) 25C, etc., and functions as a computer. The CPU 25A reads out and executes various programs stored in the ROM 25B and the large-capacity 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. The input unit may also include an input device such as a touch panel or a stylus pen.
[0019] The output unit 29 serving as an information output unit is a voice output device such as a speaker provided in the agent terminal 10. The output unit 29 may also include a display provided in the agent terminal 10, for example.
[0020] The output unit 29 can output sound based on the data transmitted from the server device S. In addition, if the output unit 29 includes a display, the output unit 29 can also display an image based on the data transmitted from the server device S.
[0021] The data communication unit 31 is connected to the above-mentioned network, and transmits and receives various data to and from other devices such as the server S. In addition, the data communication unit 31 can communicate with the in-vehicle device VE and the user terminal MT by wireless communication such as Wi-Fi (registered trademark) or Bluetooth (registered trademark) as described above, or by wired communication.
[0022] For example, the agent terminal 10 can communicate with the in-vehicle device VE of the automobile M in which the agent terminal 10 is currently mounted, 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 an identifier of the automobile M in which the in-vehicle device VE is mounted. Therefore, by communicating with the in-vehicle device VE via the data communication unit 31, the agent terminal 10 can obtain information that helps to identify the automobile M in which the agent terminal 10 is currently mounted.
[0023] Furthermore, the agent terminal 10 is capable of transmitting to the server S voice information generated by the control unit 25 in response to voice input via the input unit 27 .
[0024] 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 travel information generating unit 33 as a travel-related information acquiring unit or a mobile body information acquiring unit includes, for example, a position identifying device such as a GPS (Global Positioning System) device, an acceleration sensor, and a gyro sensor, and can generate travel-related information that is information related to the travel of the automobile M. The position identifying device included in the travel information generating unit 33 may be any device that can identify the position of the agent terminal 10 and therefore the automobile M, and may be, for example, another position identifying device such as a device that can identify the position based on a nearby base station of a mobile phone network. The travel information generating unit 33 can generate travel-related information including position identifying information, travel speed information, or acceleration information that can identify the position of the agent terminal 10. The travel-related information may include information related to driving operations. In order to obtain the information related to the driving operations, the travel information generating unit 33 may be capable of detecting the operation of the steering wheel, accelerator, and brake of the automobile M by communicating with a device mounted on the automobile M, for example.
[0026] The agent terminal 10 is capable of transmitting the driving-related information generated by the driving information generating unit 33 to other devices including the server S via the data communication unit 31.
[0027] 3 shows the configuration of the server S. For example, the server S is a device in which a data communication unit 43, a large-capacity storage device 45, and a control unit 47 cooperate with each other via a system bus 41.
[0028] The data communication unit 43 is connected to the above-mentioned network, and transmits and receives various data between the agent terminal 10 and other devices such as other servers DS. The data communication unit 43 can receive driving-related information including location identification information capable of identifying the location of the agent terminal 10 from the agent terminal 10. The data communication unit can also receive voice information from the agent terminal 10 that is generated based on a voice input to the input unit of the agent terminal 10.
[0029] The mass storage device 45 is configured, for example, from a hard disk device and an SSD (solid state drive), and stores various programs such as an operating system and server software.
[0030] The mass storage device 45 also stores vehicle information including the device identifiers of the on-vehicle devices VE of one or more automobiles M on which the agent terminal 10 is mounted, and the vehicle models, vehicle inspection dates, driving data, etc. of the one or more automobiles M that are linked (associated) with each of the device identifiers of the on-vehicle devices VE. The mass storage device 45 also stores setting information including the tone and voice of the voice to be emitted from the agent terminal 10 when it is mounted in the automobile M, based on the voice information transmitted from the server S.
[0031] The vehicle information is stored in a vehicle information database (indicated as vehicle information DB in the drawing) 45A in the large-capacity storage device 45. The setting information is stored in a setting information database (indicated as setting information DB in the drawing) 45B in the large-capacity storage device 45.
[0032] A map information database (indicated as map information DB in the drawing) 45C in which map information including road maps is stored is also included in the large-capacity storage device 45. The map information in the map information database 45C is a database that contains information equivalent to the map information used in, for example, a navigation device.
[0033] The control unit 47 is configured with 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 out and executes various programs stored in the ROM 47B and the large-capacity storage device 45 to realize various functions.
[0034] In this embodiment, a conversational AI application program is stored in the mass storage device 45 or the 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 contents of the voice information transmitted from the agent terminal and generate a reply voice if the voice information is a question. Also, the control unit 47 may generate a voice to be spoken under a predetermined condition regardless of whether a question has been asked. In generating the reply or utterance 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 conversation robot with the vehicle information database 45B and the map information database 45C as a knowledge base.
[0036] It should be noted that the agent terminal 10 of this embodiment can use only the information in the vehicle information database 45B that is linked to the automobile M in which the agent terminal 10 is currently installed.
[0037] The large-capacity storage device 45 may include, as a knowledge base, a database other than the vehicle information database 45B and the map information database 45C. Also, a database in another server DS communicably connected to the server S may be used as a knowledge base.
[0038] It should be noted that when the control unit 47 interprets the contents of the voice information transmitted from the agent terminal 10, if the voice is some kind of command, it may perform a function according to that command.
[0039] In this embodiment, a car navigation program is stored in the mass storage device 45 or the ROM 47. Therefore, the control unit 47 can execute the stored car navigation program and act as a car navigation device. For example, when the voice information transmitted from the agent terminal 10 is a command requesting a car navigation function, the control unit 47 may provide the car navigation function by the car navigation program and the map information database 45C.
[0040] 4A shows an example of a setting information table TB1 stored in the setting information database 45A. The setting information table TB1 is created for each agent terminal 10. The ID of the agent terminal 10 is written in the upper left corner of the setting information table TB1.
[0041] In the setting information table TB1, the device identifiers of the registered in-vehicle devices VE are listed under the column of in-vehicle device ID. In the column of voice tone, the voice tone when the agent terminal 10 is mounted on the automobile M equipped with the specific in-vehicle device is described. In the column of tone of voice, the voice tone when the agent terminal 10 is mounted on the automobile M equipped with the specific in-vehicle device is described.
[0042] When the control unit 47 of the server S functions as the AI conversation robot described above, conversational voice is generated based on the tone of voice and speech pattern associated with the device identifier of the in-vehicle device VE and entered in the setting information table TB1.
[0043] The tone of voice and speech tone information included in this setting information table TB1 can be set and saved by the user when the agent terminal 10 is installed in an automobile M in which the agent terminal 10 has not yet been registered, i.e., in an automobile M in which the agent terminal 10 is installed for the first time. The setting contents can be input through the input unit 27 of the agent terminal 10, or through a portable terminal MT capable of communicating with the agent terminal 10. The setting contents can be saved in the setting information database 45A by transmitting the input setting contents to the server S.
[0044] 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 written in the upper left corner of the vehicle information table TB2.
[0045] In the vehicle information table TB2, the device identifiers of the registered on-vehicle devices VE are listed under the column of on-vehicle device ID. In the column of vehicle type, for example, vehicle data including vehicle information such as the vehicle type of the automobile M in which each on-vehicle device VE is installed, maintenance inspection data including maintenance 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.
[0046] In addition to or instead of the model of the automobile M, the vehicle information may include information such as the type of fuel used by the automobile M, the number of passengers that can ride, whether the steering wheel is right-hand or left-hand, and the size of the vehicle. Furthermore, the maintenance and inspection information of the automobile M may include information such as the oil change date or the windshield wiper change date.
[0047] The vehicle information included in this vehicle information table TB2 can be input and stored by a user when the agent terminal 10 is installed in an automobile M that has not yet been registered, for example, an automobile M in which the agent terminal 10 is installed for the first time. This vehicle information can be input through the input unit 27 of the agent terminal 10, or through a mobile terminal MT that can communicate with the agent terminal 10. In addition, the input vehicle information can be transmitted to the server S, whereby the vehicle information can be stored in the vehicle information database 45B.
[0048] The driving history may also include, for example, the history of the departure point, arrival point, and stopover points of the automobile M, the driving route, driving speed, and acceleration of the automobile 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 mounted on the automobile M, and map information stored in the map information database 45C. Note that the driving data may be constantly updated while the agent terminal 10 is mounted on the automobile M.
[0049] [2. Control routine] The following describes a control routine for implementing the method of the first embodiment and the system including the agent terminal 10 and the server S. The dashed lines in the diagrams of the routines used in the following description typically indicate the transmission and reception of notifications, data, etc. between the agent terminal 10 and the server S.
[0050] [2-1. Driving data recording routine] 5 shows a driving data recording routine R1 executed by the agent terminal 10 and the server S when the user brings the agent terminal 10 into the automobile M, i.e., when the agent terminal 10 is installed in the automobile M. The routine executed by the agent terminal 10 is indicated as R1A, and the routine executed by the server S is indicated as R1B.
[0051] For example, the routine R1A and the routine R1B can be started when the agent terminal 10 and the server S are started, respectively, and then repeatedly executed.
[0052] When the control unit 25 of the agent terminal 10 (hereinafter, in the explanation of the routine, simply referred to as "the agent terminal 10") starts routine R1A, it first determines in step S11A whether the accessory power supply (hereinafter, referred to as the ACC power supply) of the automobile M in which it is installed is on or not (step S11A). 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 in-vehicle device VE is powered on and the ACC power supply is on. Conversely, if communication is not established, it is determined that the in-vehicle device VE is not powered on and the ACC power supply is not on.
[0053] If it is determined in step S11A that the ACC power supply is not on (step S11A: NO), monitoring of the ACC power supply continues. If it is determined in step S11A that the ACC power supply is 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 moving object identification information acquisition unit. When step S12A ends, the terminal identifier (terminal ID) of the agent terminal 10 and the acquired in-vehicle device ID of the in-vehicle device VE are transmitted to the server S (step S13A).
[0054] When the control unit 47 of the server S (hereinafter, simply referred to as "the server S" in the description of the routine) starts the routine R1B, it first waits for the reception of the terminal ID and the in-vehicle device ID of the agent terminal 10 in step S11B (step S11B). Then, in step S12B, it determines whether or not the terminal ID and the 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 the in-vehicle device ID have not yet been received (step S12B: NO), the reception of these IDs is awaited for a certain period of time, and step S12B is executed again.
[0056] In step S12B, when 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 the in-vehicle device ID is registered in the setting information database 45A and the vehicle information database 45B (step S13B). This determination can be made based on whether or not there is a table with the received terminal ID assigned thereto among the setting information table TB1 in the setting information database 45A and the vehicle information table TB2 in the vehicle information database 45B, and whether or not the received in-vehicle device ID is described in the table.
[0057] If it is determined in step S13B that the in-vehicle device VE is not registered (step S13B: NO), the server S requests registration information including setting information and vehicle information from the agent terminal 10 (step S14B), and then a server-side information registration subroutine is executed (step S15B). In this server-side information registration subroutine, setting information related to conversational voice such as tone of voice and speech and vehicle information are received from the agent terminal 10, and these pieces of information are stored in association with the in-vehicle device ID of the in-vehicle device VE to be registered this time. In the subsequent processing, the information transmitted from the agent is stored in step S15B in association with the registered in-vehicle device ID.
[0058] In step S13B, if it is determined that the vehicle-mounted device VE is registered (step S13B: YES), in the subsequent processing, the information transmitted from the agent terminal 10 is associated with the registered vehicle-mounted device VE and stored.
[0059] After the completion of step S13A, the agent terminal 10 judges whether or not a request for registration information transmitted in step S14B on the server S side has been received (step S14A). This judgment may be made based on whether or not the request for registration information has been 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), an agent-side information registration subroutine is executed (step S15A). In this agent-side information registration subroutine, input of setting information related to conversation voice such as tone of voice and speech and vehicle information from the user is accepted, and this information is transmitted 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 completing the subroutine of step S15B, the server S transmits a notification of the start of recording of the traveling data to the agent terminal 10, and waits to receive data for recording the traveling data (step S16B).
[0062] After the subroutine of step S15A is completed, the agent terminal 10 judges whether or not a notification to start recording of the traveling data has been received (step S16A). This judgment may be made based on whether or not the notification to start recording of the traveling data has been received within a certain period of time after the completion of step S15A.
[0063] In step S16A, when it is determined that a notification to start recording of driving data has been received (step S16A: YES), transmission of driving data including, for example, the above-mentioned driving-related information of the agent terminal 10 to the server S is started (step S17A). This transmission of driving data may be performed continuously, or may be performed intermittently or intermittently at regular or non-uniform time intervals. In step S16A, the transmitted data is received by the server S and stored in the vehicle information database 45B in association with the vehicle-mounted device ID.
[0064] In step S16A, if it is determined that a notification to start recording of driving data has not been received (step S16A: NO), step S16A is executed again after a certain period of time.
[0065] After step S17A, in step S18A, it is determined whether the ACC power supply of the automobile 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 in-vehicle device VE is powered on and the ACC power supply is not turned off. On the other hand, if communication is not established, it is determined that the in-vehicle device VE is powered off and the ACC power supply is turned off.
[0066] If it is determined in step S18A that the ACC power supply is not turned off (step S8: NO), the transmission of the driving data (step S17A) continues, and step S18A is executed again after a certain period of time.
[0067] In step S18A, if it is determined that the ACC power supply has been turned off (step S18A: YES), a data transmission end notification is transmitted to the server S (step S19A), and the routine R1A ends.
[0068] After step S16B is completed, the server S determines whether or not the data transmission end notification transmitted by the agent terminal 10 in step S19A is received (step S17B). If it is determined in step S17B that the data transmission end notification has not been received (step S17B: NO), the server S continues to wait for reception of the travel data (step S16B) and executes step S17B again after a certain period of time.
[0069] If it is determined in step S17B that a data transmission end notification has been received (step S17B: YES), the data reception wait is ended (step S18B), and then the routine R1B ends.
[0070] [2-2. Information registration subroutine] 6 shows an information registration subroutine R2 in the driving data recording routine R1. Note that the routine executed by the agent terminal 10 is shown as R2A, and the routine executed by the server S is shown as R2B.
[0071] When the agent terminal 10 starts the routine R2A, it first waits for the input of registration information including vehicle information and setting information (step S21A). This may be done, for example, by prompting the user to input the registration information including the vehicle information and setting information by using voice or images or the like via the output unit 29 of the agent terminal 10, and accepting the input via the input unit 27. At this time, instead of the input unit 27, the input may be made via a portable terminal MT capable of communicating with the agent terminal 10.
[0072] After step S21A is completed, it is determined whether or not the input of the registration information is completed (step S22A). This determination may be made based on whether a certain time has passed or whether the user has expressed an intention to end the input of the registration information via the input unit 27 or the mobile terminal MT. If it is determined in step S22A that the input is not completed (step S22A: NO), the waiting for the input of the registration information (step S21A) continues, and step S22A is executed again after a certain time has passed.
[0073] The vehicle information input in steps 21A and 22A may include, for example, the vehicle inspection date and vehicle model included in the above-described table TB1, as well as vehicle specifications, vehicle size, type of fuel used, passenger capacity, whether the handle is left or right, etc. That is, in steps 21A and 22A, the control unit 25 functions as a mobile object information acquisition unit.
[0074] Moreover, the setting information input in steps 21A and 22A is voice setting information including at least one of the tone of voice and the speech tone of the voice output from the output unit of the agent terminal 10, which are included in table TB2. That is, in steps 21A and 22A, the control unit 25 also functions as a voice setting information receiving unit.
[0075] If it is determined in step S22A that the input has been completed (step S22A: YES), the accepted registration information is transmitted to the server S (step S23A), and the routine R2A ends.
[0076] When the server device S starts the routine R2B, it first waits for the reception of registration information from the agent terminal 10 (step S21B). After that, the server device S determines whether or not the registration information has been received from the agent terminal 10 (step S22B). If it is determined in step S22B that the registration information has not been received (step S22B: NO), the process continues to wait for reception of the registration information (step S21B), and step S22B is executed again after a certain period of time.
[0077] When the server device S determines in step S22B that the registration information has been received (step S22B: YES), the server device S associates the received registration information with the in-vehicle device ID received in step S12B of the routine R1B, and stores the setting information in the setting information database 43A and the vehicle information in the vehicle information database 43B (step S23B). After step S23B is executed, the routine R2B ends.
[0078] [2-3. Conversation routine] 7 and 8 show a conversation routine R3 executed by the agent terminal 10 and the server S when the server S converses with the user via the agent terminal 10 when the user brings the agent terminal 10 into the automobile M, i.e., when the agent terminal 10 is installed in the automobile M. The routine executed by the agent terminal 10 is indicated as R3A, and the routine executed by the server S is indicated as R3B.
[0079] For example, the routine R3A and the routine R3B can be started when the agent terminal 10 and the server S are started, respectively, and then repeatedly executed.
[0080] When the agent terminal 10 starts the routine R3A, it first determines in step S31A whether the ACC power supply of the automobile M in which it is mounted is on or not (step S31A). 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 in-vehicle device VE is powered on and the ACC power supply is on. On the other hand, if communication is not established, it is determined that the in-vehicle device VE is not powered on and the ACC power supply is not on.
[0081] In step S31A, if it is determined that the ACC power supply is not on (step S31A: NO), step S31A is executed again after a certain time has elapsed. In step S31A, if it is determined that the ACC power supply is on (step S31A: YES), the in-vehicle device ID of the in-vehicle device VE is acquired (step S32A). When step S32A ends, the terminal identifier (terminal ID) of the agent terminal 10 and the acquired in-vehicle device ID of the in-vehicle device VE are transmitted to the server S (step S33A).
[0082] When the server S starts the routine R3B, it first waits for the reception of the terminal ID and the vehicle-mounted device ID of the agent terminal 10 in step S31B (step S31B). Then, in step S32B, it is determined whether or not the terminal ID and the vehicle-mounted device ID transmitted in step S33A have been received (step S32B).
[0083] In step S32B, if it is determined that the terminal ID and the in-vehicle device ID have not yet been received (step S32B: NO), the reception of these IDs is awaited for a certain period of time, and step S32B is executed again.
[0084] In step S32B, when 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 the in-vehicle device ID is registered in the setting information database 45A or the vehicle information database 45B (step S33B). This determination can be made based on whether or not there is a table with the received terminal ID assigned thereto in the setting information table TB1 in the setting information database 45A or the vehicle information table TB2 in the vehicle information database 45B, and whether or not the received in-vehicle device ID is described in that table.
[0085] If it is determined in step S33B that the in-vehicle device VE is not registered (step S33B: NO), the routine R3B ends. If the server S determines in step S33B that the in-vehicle device VE is registered (step S33B: YES), the server S transmits a conversation standby notification to the agent 10 and starts conversation standby (step S34B). In this conversation standby state, the server S waits for reception of voice data from the agent terminal 10. Also, in this conversation standby state, the server S performs speech processing as necessary depending on the situation, for example, based on the driving data received by routine R1.
[0086] When step S33A is completed, the agent terminal 10 determines in step S34A whether or not the conversation waiting notification transmitted from the server S in step S33B is received. This determination can be made based on whether or not the conversation waiting notification is received within a predetermined time after the completion of step S33A, that is, after the terminal ID and the in-vehicle device ID are transmitted to the server S.
[0087] When the agent terminal 10 determines in step S34A that the conversation waiting notification has not been received (step S34A: NO), it determines that the in-vehicle device ID of the in-vehicle device VE has not been registered in the server S, and ends the routine R3A. As described above, the routine R3A is repeatedly executed. Therefore, if, for example, the above-described information registration subroutine R2 is executed during the repeated execution of the 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] When the agent terminal 10 determines in step S34A that it has received a conversation standby notification (step S34A: YES), it starts conversation standby (step S35A). In this conversation standby state, the agent terminal 10 maintains a state of accepting voice input via the input unit 27 or the mobile terminal MT. Also, in this conversation standby state, the agent terminal 10 waits to receive voice information from the server device S.
[0089] After entering the conversation standby state, the agent terminal 10 determines whether or not there has been a 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 a voice input (step S36A: YES), it converts the input voice into data and transmits it to the server S (step S37A).
[0090] After determining in step S36A that no voice input has been made (step S36A: NO) or executing step S37A, the agent terminal 10 determines in step S38A whether or not voice data has been received from the server S. This determination may be made based on whether or not voice data has been received from the server S within a certain time period after the determination in step S36A or the execution of step S37A.
[0091] When the agent terminal 10 determines in step S38A that it has received the voice data (step S38A: YES), it generates a voice based on the voice data and outputs the voice as information to be provided via the output unit 29 or the portable terminal MT (step S39A). The voice may be output from a built-in speaker of the agent terminal 10, or may be output from an in-vehicle device VE such as a car stereo connected for communication.
[0092] The agent terminal 10 determines that no voice data has been received in step S38A (step S38A: NO) or determines whether the ACC power supply of the automobile M has been turned off after execution of step S39A (step S310A). 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 in-vehicle device VE is powered on and the ACC power supply is not turned off. On the other hand, if communication is not established, it is determined that the in-vehicle device VE is powered off and the ACC power supply is turned off.
[0093] In step S310A, if it is determined that the ACC power is not turned off (step S310A: NO), the conversation standby state is maintained and S36A is executed again.
[0094] In step S310A, if it is determined that the ACC power has been turned off (step S310A: YES), a conversation standby end notification is transmitted to the server S (step S311A), and the routine R3A ends.
[0095] After step S34B ends and the server device S enters a conversation waiting state, in step S35B, the server device S determines whether or not voice data has been received from the agent terminal 10. If the server device S determines in step S35B that voice information has been received (step S35B: YES), it analyzes the voice data and determines whether or not a reply is required (step S36B).
[0096] This determination is made, for example, based on whether the content of the voice is a conversation between passengers in the automobile M. For example, if the content of voice 1 is in the form of a question, but another voice is immediately heard that answers the question, it may be determined that the content of the voice is a conversation between passengers in the automobile M, and that a reply is unnecessary. Also, for example, if the content of voice 1 is in the form of a question, and there is no other voice for a certain period of time, it may be determined that the voice is a question from a passenger in the automobile M to the server S, and that a reply is necessary.
[0097] When the server device S determines in step S35B that it has not received the voice information, it determines whether or not the utterance condition has occurred (step S37B). This determination may be made, for example, based on the driving-related information transmitted from the agent 10. For example, when an abnormality in the moving body M, such as dangerous driving, is detected based on the driving-related information, it is determined that the utterance condition has occurred. When the utterance condition has occurred, advice regarding driving operation may be generated based on the driving-related information.
[0098] When the server device S determines in step S36B that a reply is required (step S36B: YES) or determines in step S37B that a speech condition has occurred (step S37B: YES), it generates voice data and transmits it to the agent terminal 10 (step S38B).
[0099] The voice data is generated based on the analysis in the determination in step S36 or based on the utterance condition in step S37B. The voice data may be generated based on the vehicle information database 45B and the map information database 45C, which are knowledge bases.
[0100] For example, advice on driving operations generated based on the above-mentioned driving-related information may be generated as provided information and transmitted as voice data. The voice data is generated based on at least one of a tone of voice and a tone of speech that are associated with the in-vehicle device ID of the in-vehicle device VE and stored in table TB1.
[0101] The server device S determines that no reply is necessary in step 36B (step S36B), determines that the condition for speaking has not occurred in step 37B (step S37B), or, upon completion of step 38B, determines whether a conversation waiting end notification has been received from the agent terminal 10 (step S39B).
[0102] In step S39B, if it is determined that the conversation wait end notification has not been received (step S39B: NO), the conversation wait state is maintained and step S35B is executed again. In step S39B, if it is determined that the conversation wait end notification has been received, the conversation wait state is released and routine R3B ends.
[0103] The conversations that take place in the above conversation routine include the following: For example, when a user asks "When is the next vehicle inspection?", a response is generated in the server S, and "It is on XX day of this year" is output from the agent terminal 10. Also, when a user asks "How many kilometers left until the destination?", the server S accesses the map information database 45C to generate a response, and the agent terminal 10 outputs "XX kilometers left."
[0104] In addition, when the user issues an instruction such as "Make a reservation at our usual restaurant for next Saturday night," server S accesses another server DS to generate a response, and the agent terminal 10 outputs a message saying "Reservations can be made at XX o'clock. Would you like to make a reservation?"
[0105] In addition, when the user asks, "Where did you go for fun at the end of last month?", the server S accesses the vehicle information database 45B to generate a response, and the agent terminal 10 outputs, "We went to XX amusement park at the end of last month."
[0106] In addition, when the user expresses his / her current feelings by saying "I'm hungry," server S determines what the user's favorite food is based on the history of restaurants visited in the past. For example, if server S determines that the user's favorite food is ramen, it will output a message saying, "There is a famous ramen restaurant 1 km away. Would you like to set it as a stopover?"
[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 capable of identifying the automobile M. Therefore, the agent terminal 10 can provide information based on the information stored in association with the in-vehicle device ID in which the agent terminal 10 is mounted.
[0108] Specifically, the agent terminal 10 can provide, for example, information based on the driving history of the vehicle in which the agent terminal 10 is mounted, in the form of a voice based on the settings made for the vehicle. Therefore, even if the agent terminal 10 can be mounted in a plurality of different automobiles M, it is possible to provide information suited to each of the automobiles M. EXAMPLES
[0109] [1. System configuration and operation] Hereinafter, an information providing system 100 including an agent terminal 10 as an information providing device and an information providing method according to a second embodiment of the present invention will be described with reference to the accompanying drawings. In the second embodiment, the overall configuration of the system 100 and the configurations of the agent terminal 10 and the server S are the same as those in the first embodiment.
[0110] 9A shows an example of a setting information table TB3 stored in the setting information database 45A. The setting information table TB3 is created for each agent terminal 10. The ID of the agent terminal 10 is written in the upper left corner of the setting information table TB3.
[0111] Unlike the setting information table TB1 of Example 1 (see FIG. 4A), in the setting information table TB3, under the vehicle identifier column, the vehicle identifiers set for each automobile M are listed in the form of nicknames such as “Bill” and “Jennifer.”
[0112] The vehicle-mounted device IDs of the vehicle-mounted devices VE are listed under the vehicle-mounted device ID column. The voice tone column lists the voice tone when the agent terminal 10 is mounted on the automobile M given a specific identifier (nickname). The tone of voice column lists the voice tone when the agent terminal 10 is mounted on the automobile M given a specific identifier (nickname). That is, in the second embodiment, the vehicle identifier (nickname) is associated with the vehicle-mounted device ID, as well as the voice tone and tone of voice.
[0113] When the control unit 47 of the server S functions as an AI conversational robot as described in Example 1, a conversational voice is generated based on the tone of voice and speech pattern associated with the vehicle identifier (nickname) and entered in the setting information table TB3.
[0114] The tone of voice and speech tone information included in this setting information table TB3 can be set and saved by the user when the agent terminal 10 is installed in an automobile M in which the agent terminal 10 has not yet been registered, i.e., in an automobile M in which the agent terminal 10 is installed for the first time. The setting contents can be input through the input unit 27 of the agent terminal 10, or through a portable terminal MT capable of communicating with the agent terminal 10. The setting contents can be saved in the setting information database 45A by transmitting the input setting contents to the server S.
[0115] Fig. 9B shows an example of a vehicle information table TB4 stored in the vehicle information database 45B. Unlike the setting information table TB2 (see Fig. 4B) of the first embodiment, in the setting information table TB4, the vehicle identifiers set for each automobile M are listed in the form of nicknames such as "Bill" and "Jennifer" under the vehicle identifier column. The 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 on-vehicle devices VE are listed under the column of on-vehicle device ID. In the column of vehicle type, for example, vehicle data including vehicle information such as the vehicle type of the automobile M in which each on-vehicle device VE is installed, maintenance and inspection 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. That is, in the second embodiment, the vehicle identifier (nickname) is linked to the on-vehicle device ID, the vehicle data, the maintenance and inspection data, and the driving data.
[0117] In addition to or instead of the model of the automobile M, the vehicle information may include information such as the type of fuel used by the automobile M, the number of passengers that can ride, whether the steering wheel is right-hand or left-hand, and the size of the vehicle. Furthermore, the maintenance and inspection information of the automobile M may include information such as the oil change date or the windshield wiper change date.
[0118] The vehicle information included in this vehicle information table TB4 can be input and stored by a user when the agent terminal 10 is installed in an automobile M that has not yet been registered, i.e., an automobile M in which the agent terminal 10 is installed for the first time. This vehicle information can be input through the input unit 27 of the agent terminal 10, or through a mobile terminal MT that can communicate with the agent terminal 10. In addition, the input vehicle information can be transmitted to the server S, whereby the vehicle information can be stored in the vehicle information database 45B.
[0119] The driving history may also include a history of the departure point, arrival point, and stopover points of the automobile M, the driving route, driving speed, and acceleration of the automobile 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 mounted on the automobile M, and map information stored in the map information database 45C. Note that the driving data may be constantly updated while the agent terminal 10 is mounted on the automobile M.
[0120] [2. Control routine] The following describes a control routine for implementing the method of the second embodiment and the system including the agent terminal 10 and the server S. Note that the driving data recording routine and conversation routine are similar to those of the first embodiment, and therefore will not be described here.
[0121] In the second embodiment, when registering information, the user inputs a vehicle identifier in addition to the registration information of the first embodiment, and the vehicle identifier is registered in the database of the server S. The registration information is then stored in association with the vehicle identifier (nickname).
[0122] [2-1. Information registration subroutine] 10 shows the information registration subroutine R4 in the embodiment 2. The routine executed by the agent terminal 10 is shown as R4A, and the routine executed by the server S is shown as R4B.
[0123] When the agent terminal 10 starts the routine R4A, it first waits for a selection between new information registration or vehicle replacement (step S41A). This may be performed, for example, by prompting the user by voice or image or the like via the output unit 29 of the agent terminal 10 to select whether to register new information or to replace the vehicle by transferring the vehicle identifier (nickname) and information linked to the identifier to the new automobile M (vehicle-mounted device VE) currently being driven, and accepting the selection input via the input unit 27.
[0124] At this time, instead of using the input unit 27, the input may be performed via a portable terminal MT capable of communicating with the agent terminal 10.
[0125] When step S41A is completed, the agent terminal 10 judges whether or not vehicle replacement is to be performed (step S42A). This judgment is made based on whether or not vehicle replacement is selected in step S41A.
[0126] When the agent terminal 10 determines in step S42A that it is a vehicle replacement (step S42A: YES), it transmits a vehicle replacement process start notification to the server S (step S43A) and starts a vehicle replacement subroutine (step S44A). When the subroutine of step S44A ends, the routine R4A ends.
[0127] In the vehicle replacement subroutine, the agent terminal 10 transmits from the server S to the agent terminal 10 a set of one or more vehicle identifiers stored for the agent terminal 10 and vehicle information linked to the one or more identifiers.
[0128] Then, the user selects a vehicle identifier, which is a nickname that the user wants to transfer to the new automobile M that the user is currently riding in, and the selection result is transmitted to the server S. The server S deletes information unique to the automobile M (vehicle-mounted device VE) that has been linked up until now from the selected vehicle identifier, and transfers the other information (vehicle information and setting information that are not unique to the automobile M) to the automobile M that the user is currently riding in, i.e., the automobile M in which the agent terminal 10 is currently installed.
[0129] When the agent terminal 10 determines in step S42A that the vehicle is not being replaced (step S42A: NO), it starts new information registration processing and waits for input of a 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 by voice or image using the output unit 29 of the agent terminal 10, and accepting the input via the input unit 27. At this time, instead of the input unit 27, the input may be made via a portable terminal MT capable of communicating with the agent terminal 10.
[0130] That is, in step S45A, an identifier 1 is assigned to the automobile M in which the agent terminal 10 is currently mounted. In other words, 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 judges whether or not the input of the vehicle identifier and the registration information is completed (step S46A). This judgment may be made based on whether a certain time has passed or whether the user has expressed an intention to end 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 is not completed (step S46A: NO), the agent terminal 10 continues to wait for the input of the vehicle identifier and the registration information (step S45A), and step S46A is executed again after a certain time has passed.
[0132] In step S46A, if it is determined that the input has been completed (step S46A: YES), the accepted vehicle identifier and registration information are transmitted to the server S (step S47A), and the routine R4A ends.
[0133] When the server device S starts the routine R4B, it first waits for reception of information from the agent terminal 10 (step S41B). After that, the server device S determines whether or not a vehicle exchange processing start notification has been received from the agent terminal 10 (step S42B). This determination may be made based on whether or not the vehicle exchange processing notification is received within a certain period of time.
[0134] If it is determined in step S42B that a vehicle exchange process start notification has been received (step S42: YES), a vehicle exchange subroutine is started (step S43B).
[0135] When the server S determines in step S42B that the vehicle replacement process start notification has not been received (step S42B: NO), the server S starts a new information registration process and determines whether or not a vehicle identifier and registration information have been received from the 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 the server S determines in step S44B that a vehicle identifier and registration information have been received, it stores the received registration information and the in-vehicle device ID of the in-vehicle device VE in which the agent terminal 10 is currently installed, linked to the received vehicle identifier (step S45B), and then routine R4B ends.
[0137] If the server S determines in step S44B that the vehicle identifier and the registration information have not been received, the server S temporarily halts the new information registration process, and executes step S42B again.
[0138] [2-2. Vehicle switching subroutine] 11 shows the vehicle switching subroutine R5 in the embodiment 2. The routine executed by the agent terminal 10 is shown as R5A, and the routine executed by the server S is shown as R5B.
[0139] As described above, in the vehicle replacement subroutine, the agent terminal 10 transmits from the server S to the agent terminal 10 one or more vehicle identifiers (nicknames) stored for the agent terminal 10 and a set of vehicle information linked to the one or more vehicle identifiers. Then, the user selects a vehicle identifier, which is a nickname that the user wishes to transfer to the new automobile M that the user is currently riding in, and the selection result is transmitted to the server S. The server S deletes, from the selected vehicle identifier, information unique to the automobile M (vehicle-mounted device VE) that has been linked up until now, and transfers the other information (vehicle information and setting information that is not unique to the automobile M) to the automobile M that the user is currently riding in, i.e., the automobile M in which the agent terminal 10 is currently installed.
[0140] When the routine R5A starts, the agent terminal 10 waits to receive a vehicle identifier and registration information associated with the vehicle identifier (step S51A).
[0141] When routine R5B is started, the server S sends one or more vehicle identifiers and a set of registration information contained in tables TB3 and TB4 corresponding to the terminal ID of the agent terminal 10 in the server S and waits to receive one vehicle identifier selected by the user at the agent terminal 10 (step S51B).
[0142] After executing step S51A, the agent terminal 10 judges whether or not the vehicle identifier and the registration information have been received (step S52A). If there is no vehicle identifier stored in the agent terminal 10, a message to that effect is transmitted to the agent terminal 10, and this is regarded as having transmitted a set of the vehicle identifier and the registration information.
[0143] When the agent terminal 10 determines in step S52A that it has received a vehicle identifier or the like (step S52A: YES), it waits for a selection input of one nickname from the one or more received vehicle identifiers (step S53A). That is, in step S53A, the control unit 25 of the agent terminal 10 functions as an assignment receiving unit that receives a change assignment.
[0144] This may be done, for example, by having the output unit 29 of the agent terminal 10 prompt the user using voice or images to select and input a vehicle identifier, which is the nickname that the user wishes to transfer to the unregistered automobile M that the user is currently riding in, and accepting the selection input via the input unit 27.
[0145] At this time, instead of using the input unit 27, the input may be performed via a portable terminal MT capable of communicating with the agent terminal 10.
[0146] When the agent terminal 10 determines in step S52A that the vehicle identifier and the like have not been received (step S52A: NO), it executes step S52A again after a certain period of time has elapsed.
[0147] After step S53A is completed, the agent terminal 10 judges whether the vehicle identifier selection input is completed (step S54A). This judgment may be made based on whether a certain time has passed or whether the user has expressed an intention to end the input of the registration information via the input unit 27 or the mobile terminal MT. If it is determined in step S54A that the selection input is not completed (step S54A: NO), the agent terminal 10 continues to wait for the vehicle identifier selection input (step S53A), and step S54A is executed again after a certain time has passed.
[0148] If it is determined in step S54A that the selection input has been completed (step S54A: YES), the agent terminal 10 transmits the selected vehicle identifier to the server and waits for an inquiry from the server (step S55A).
[0149] If the 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 time. If the server S determines in step S52 that the selected vehicle identifier has been received (step S52B: YES), it erases the vehicle-specific information that is specific or unique to the currently registered automobile M from the registration information linked to the selected vehicle identifier, and queries the agent terminal 10 for vehicle-specific information of the automobile M to be newly registered (step S53B).
[0150] For example, the vehicle-specific information to be deleted includes at least one of information depending on the characteristics of the automobile M and information regarding the maintenance of the automobile M. Furthermore, the information depending on the characteristics of the automobile M includes information regarding the physical characteristics of the automobile M. This information regarding the physical characteristics may include, for example, the vehicle model, vehicle specifications, vehicle size, type of fuel used, passenger capacity, whether the handle is left or right, etc. Furthermore, the information regarding the maintenance of the automobile M may include the scheduled dates for maintenance such as oil changes and part replacements of the automobile M, or the date of vehicle inspection.
[0151] Furthermore, the information deleted in step S53B may include, among the driving data, information that depends on the characteristics of the automobile M and is not suitable for the new automobile M. Specifically, for example, when the automobile M is changed from a gasoline-powered automobile to an electric automobile, gas stations included in the stopovers are deleted, when the vehicle is changed from a small vehicle to a large vehicle, roads that are prohibited for large vehicles included in the route are deleted, and when the vehicle becomes taller, the usage history of parking lots with vehicle height restrictions is deleted. In this way, by deleting information that is not suitable for the new vehicle, facilities that were once frequently used but cannot be used by the new automobile M can be prevented from being recommended via the agent terminal.
[0152] After step S55A is completed, the agent terminal 10 determines whether or not an inquiry has been received from the server S (step S56A). If the agent terminal 10 determines in step S56A that no inquiry has been received (step S56A: NO), it executes step S56A again after a certain period of time.
[0153] When the agent terminal 10 determines in step S56A that it has received an inquiry (step S56A: YES), it waits for the input of vehicle-specific information (step S57A). This may be done, for example, by prompting the user to input the vehicle-specific information of the unregistered automobile M currently being driven by the output unit 29 of the agent terminal 10 using voice, images, or the like, and accepting the input via the input unit 27.
[0154] At this time, instead of using the input unit 27, the input may be performed via a portable terminal MT capable of communicating with the agent terminal 10.
[0155] After step S57A is completed, the agent terminal 10 judges whether the vehicle identifier selection input is completed (step S58A). This judgment may be made based on whether a certain time has passed or whether the user has expressed an intention to end the input of the registration information via the input unit 27 or the mobile terminal MT. If it is determined in step S58A that the selection input is not completed (step S58A: NO), the agent terminal 10 continues to wait for the vehicle identifier selection input (step S57A), and step S58A is executed again after a certain time has passed.
[0156] The vehicle specific information input in steps 57A and S58A may include, for example, the vehicle inspection date and vehicle model included in the above-described table TB3, as well as vehicle specifications, vehicle size, type of fuel used, passenger capacity, whether the handle is left or right, etc. That is, in steps 57A and 58A, the control unit 25 functions as a mobile object information acquisition unit.
[0157] Moreover, the setting information input in steps 57A and 58A is voice setting information including at least one of the tone of voice and the speech tone of the voice output from the output unit of the agent terminal 10, which are included in table TB4. That is, in steps 57A and 58A, the control unit 25 also functions as a voice setting information receiving unit.
[0158] If it is determined in step S58A that the selection input has been completed (step S58A: YES), the agent terminal 10 transmits the input vehicle specific information to the server S (step S59A), and the routine R5A ends.
[0159] After step S53B is completed, the server S determines whether or not the vehicle-specific information has been received from the agent terminal 10 (step S54B). If the server S determines in step S54B that the vehicle-specific information has not been received (step S54B: NO), the server S executes step S54B again after a certain period of time. If the server S determines in step S54 that the vehicle-specific information has been received (step S54B: YES), the server S associates the received vehicle-specific information with the vehicle identifier received in step S52B, i.e., the nickname selected by the user, and stores the information (step S55B), and the routine R5B ends.
[0160] In the routine R5 of the second embodiment, in step S53B, the vehicle-specific information that is specific to the automobile M among the registration information linked to the vehicle identifier is erased, but the vehicle-specific information may be left invalidated and the vehicle-specific information of the newly registered automobile M may be additionally stored. In that case, the vehicle-specific information that has been invalidated in the conversation routine R3 is not used as an information source for conversation generation.
[0161] In the second embodiment, in the conversation routine R3, in step S38B in which voice data is generated and transmitted to the agent terminal 10, the voice data is generated based on at least one of the tone of voice and the tone of voice stored in table TB3 in association with the vehicle identifier.
[0162] According to the above-mentioned second embodiment, a nickname can be given to a vehicle by registering a vehicle identifier. Furthermore, by storing various information in association with the vehicle identifier, the personality of the previous vehicle that the user is familiar with can be transferred to the new vehicle.
[0163] According to the second embodiment, the vehicle identifier is registered in the form of a nickname, which allows the user to feel that the vehicle has a more familiar personality. Furthermore, by using the registered nickname as a keyword, it becomes possible to more accurately determine whether the conversation is between passengers in the vehicle or is directed to the agent terminal 10, which contributes to improving the accuracy of the agent function.
[0164] For example, if the agent terminal 10 responds to an utterance such as "I hope it will be sunny tomorrow" during a conversation between passengers, the conversation may be interrupted, which may be annoying.
[0165] Therefore, in the above conversation routine R3, it can be determined that no reply is necessary when multiple people are talking, and even when passengers are talking to each other, only if the utterance includes a nickname before or after it, such as "I hope it's sunny tomorrow, Bill," or "Will it rain again tomorrow, Bill?", it can be determined that the utterance is directed at the agent terminal, and a reply is required and voice information can be generated.
[0166] So far, we have described an embodiment in which the user can assign a nickname as a vehicle identifier, but the vehicle identifier may be freely assigned a nickname, or may be selected by the user from a number of pre-defined attributes, such as "My Car 1" and "My Car 2." In the above embodiment, an example has been described in which the agent terminal 10 stores various pieces of 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 pieces of information may be stored in the storage unit.
[0167] In addition, when storing all of the various information held by the server S in the above embodiment in a memory unit within the agent terminal 10, a conversational AI application program, a car navigation program, etc. may be built into the agent terminal 10, and a closed system without connection to the server S may be constructed.
[0168] In addition, in the above embodiment, in order to identify the automobile M in which the agent 10 is installed, a communication connection is made with the in-vehicle device VE and the in-vehicle device ID is obtained, but instead, a camera may be built into the agent terminal 10 and the type of automobile M in which the agent 10 is installed may be identified based on the image pattern of the structures inside the vehicle cabin captured by the camera.
[0169] In the above embodiment, the agent terminal 10 outputs the provided information by voice, but instead of or in addition to this, the provided information may be output as an image. For example, the provided information may be displayed as text on an external head-up display.
[0170] The configurations, routines, or display or input modes of the agent terminal, user terminal, in-vehicle device, or server in the above-mentioned embodiments are merely illustrative and can be appropriately selected or changed according to the application, etc. For example, each step in the routine may be performed by any of the server, agent terminal, user terminal, or in-vehicle device, regardless of the above-mentioned examples. [Explanation of symbols]
[0171] 100 Information provision system 10 Agent terminal 10 21,41 System bus 25,47 Control section 23,45 mass storage 33 Driving information generation unit S Server
Claims
1. An information providing device that can be mounted on a plurality of moving bodies, an identification unit that identifies one moving object in which the information providing device is currently mounted; a travel-related information acquisition unit that acquires travel-related information stored in association with the one moving body and including information on a travel history of the one moving body; an input information acquisition unit that acquires input information input by a passenger of the one moving body; an information output unit that outputs information regarding the driving history for a period designated by the input information; An information providing device comprising:
2. 2. The information providing device according to claim 1, wherein the information output unit outputs information regarding the driving history for the period specified by the input information in a voice based on voice setting information set for the one moving body.
3. a voice setting information receiving unit that receives voice setting information stored in association with the one moving object and related to at least one of a tone of voice and a tone of voice of the voice; 3. The information providing device according to claim 2, wherein the information output unit outputs a sound based on the sound setting information.
4. 4. The information providing device according to claim 1, wherein the travel-related information includes information regarding a destination, a stopover point, or a route during travel of the one mobile object.
5. 5. The information providing device according to claim 1, wherein the travel-related information includes information regarding a driving operation performed on the mobile object while the mobile object is traveling.
6. The information providing device according to claim 5 , wherein the information output unit outputs advice information including advice on driving operation generated based on the travel-related information.
7. The information providing device according to claim 1 , wherein the identification unit acquires identification information of the moving object, and identifies the moving object on which the information providing device is currently mounted, using the acquired identification information.
8. The information providing device according to claim 1, characterized in that the travel-related information acquisition unit acquires travel-related information stored in association with the one moving body from a database in which a plurality of travel-related information associated with each of the plurality of moving bodies is stored.
9. The information providing device according to claim 1 , wherein the input information acquiring unit acquires a voice of a passenger of the one moving object as the input information.
10. An information providing method for providing information using an information providing device that can be mounted on a plurality of moving bodies, comprising: A step of identifying one moving body in which the information providing device is currently installed; a travel-related information acquisition step of acquiring travel-related information stored in association with the one moving body and including information on a travel history of the one moving body; an input information acquisition step of acquiring input information input by a passenger of the one moving body; an information output step of outputting information regarding the driving history for a period designated by the input information; 13. An information providing method comprising the steps of:
11. An information providing device that can be mounted on multiple moving objects, A step of identifying one moving body in which the information providing device is currently installed; a travel-related information acquisition step of acquiring travel-related information stored in association with the one moving body and including information on a travel history of the one moving body; an input information acquisition step of acquiring input information input by a passenger of the one moving body; an information output step of outputting information regarding the driving history for a period designated by the input information; An information providing program characterized by causing the program to execute the above steps.
12. An information providing device that can be mounted on multiple moving objects, A step of identifying one moving body in which the information providing device is currently installed; a travel-related information acquisition step of acquiring travel-related information stored in association with the one moving body and including information on a travel history of the one moving body; an input information acquisition step of acquiring input information input by a passenger of the one moving body; an information output step of outputting information regarding the driving history for a period designated by the input information; A computer-readable storage medium having a program recorded thereon for executing the above-mentioned program.
Citation Information
Patent Citations
Agent device
JP2001056225A
Navigation device, navigation method, and navigation program
JP2012177703A
Home Network System
JP4664524B2
