JP7767835B2 - Data transfer method, communication support device, communication support program, and communication support system - Google Patents

Description

The present invention relates to a data transfer method, communication support device, communication support program, and communication support system that support communication between a vehicle and a user.

Patent Document 1 discloses an agent device that displays an image of a personified "agent" inside the vehicle and assists the driver in entering destinations for route guidance through communication between the agent and the driver. When map data is exchanged, this agent device adjusts the agent's actions so that they are consistent with the new map data.

Japanese Patent Application Laid-Open No. 2000-222688

In recent years, vehicles have come to be equipped with communication support devices that use an interactive user interface to assist communication between the vehicle and the user. When a user sells or scraps their old vehicle (hereafter referred to as the "old vehicle") and switches to another vehicle (hereafter referred to as the "new vehicle"), it is desirable to transfer the data used to support communication from the old vehicle to the new vehicle in order to maintain or improve usability.

However, if the interactive user interface is constructed using mimicked characters that users can recognize as pseudo-humans or other living creatures, the following problems arise if data is simply transferred mechanically when switching from an old vehicle to a new one.

A biomimetic character (hereafter referred to as a biomimetic character) is a symbolic interface that assists smooth and natural interactive communication between the user and the vehicle by being recognized by the user as a simulated living thing. For this reason, the biomimetic character is recognized by the user as being essentially one with the vehicle, for example, as a simulated personality of the vehicle or communication support device. Therefore, if data is simply transferred mechanically when the user switches from an old vehicle to a new one, the new biomimetic character with which the user has not yet communicated will already possess the simulated personality and memories of the familiar biomimetic character with whom the user had many conversations in the old vehicle.

However, considering that real living things cannot change their bodies and inherit memories or personalities, it would be unnatural for a biomimetic character, which is perceived as a living thing even if it is simulated, to have the memories and pseudo-personality that were perceived as being one with the old vehicle's hardware (body) continue to live on in the new vehicle's separate hardware (body), even though the old vehicle's hardware (body) is lost. In other words, the mechanical transfer of data diminishes the biomimetic character's sense of life (its lifelikeness). As a result, users find it difficult to recognize the biomimetic character as a natural target of communication, defeating the original purpose of using a biomimetic character, which is to assist in natural interactive communication between the user and the vehicle.

The present invention aims to provide a data transfer method, communication support device, communication support program, and communication support system for transferring data used to support communication in a vehicle that supports communication between the user and the vehicle through an interactive user interface using lifelike characters, without losing the lifelike feel of the characters.

One aspect of the present invention is a data transfer method for transferring data used to support communication in a vehicle equipped with a communication support device that supports communication with a user through an agent unit that is an interactive user interface using a biomimetic character. In this data transfer method, input of a special control code that triggers the start of data transfer is determined. When the special control code is a first code that instructs external output of data, the agent unit changes the character's form from a first form used for the communication to a second form different from the first form, thereby performing a separation action to notify the user of separation from the character and a keepsake creation action to notify the user that a keepsake of the character has been created . Furthermore, when the special control code is the first code, the data is saved in external storage.

According to the present invention, in a vehicle that supports communication between the user and the vehicle through an interactive user interface using lifelike characters, data used to support communication is transferred without compromising the lifelike nature of the characters.

FIG. 1 is an explanatory diagram showing a schematic configuration of a vehicle and a communication support system. FIG. 2 is a block diagram showing the configuration of the agent controller. FIG. 3 is a flowchart showing the process of taking over data from an old vehicle. FIG. 4 is an explanatory diagram showing the operation related to the transfer of data in the old vehicle. FIG. 5 is a flowchart showing the process of transferring data to the new vehicle. FIG. 6 is an explanatory diagram showing the operation related to the transfer of data in the new vehicle.

Embodiments of the present invention will be described below with reference to the drawings.

[First embodiment]
1 is an explanatory diagram showing the schematic configuration of a vehicle 100 and a communication support system 101. The vehicle 100 uses an agent system 14 to support interactive communication between a user 10 and the vehicle 100. Therefore, the vehicle 100 including the agent system 14 constitutes the communication support system 101.

In this embodiment, interactive communication between the user 10 and the vehicle 100 (hereinafter referred to as interactive communication) refers to the transmission of information primarily in a two-way direction between the user 10 and the vehicle 100. There is no limit to the type or nature of information transmitted through interactive communication; however, for example, voice or other operational input from the user 10 to the vehicle 100 or equipment mounted on the vehicle 100 (hereinafter referred to as the vehicle 100, etc.), and the expression of the user's intentions or feelings through voice, gestures, or other actions directed toward the vehicle 100, etc., are forms of interactive communication. Furthermore, for example, the provision of information about traffic or other matters from the vehicle 100, etc. to the user 10, and the response of the vehicle 100, etc. to the expression of the user's intentions or feelings (i.e., a dialogue with the user 10) belong to interactive communication.

Note that user 10 may be the regular driver of vehicle 100, a regular passenger such as a family member, or a combination of these. In this embodiment, user 10 is the owner and primary driver of vehicle 100.

As shown in FIG. 1, the vehicle 100 includes an agent system 14, a driving operation unit 11, a car navigation system 12, a vehicle controller 15, and a sensor 16.

The driving operation unit 11 is an operation unit operated by the user 10 to drive the vehicle 100. The driving operation unit 11 includes, for example, a steering wheel, an accelerator pedal, and a brake pedal.

The car navigation system 12 is a guidance device that provides the user 10 with information such as routes to a destination. The car navigation system 12 has its own display and operation keys (not shown). The user 10 uses the operation keys of the car navigation system 12 to perform operations necessary for route guidance, such as setting a destination. The user 10 can also receive information such as route guidance on the display of the car navigation system 12 and/or through sounds or voices output from the speaker 13.

The car navigation system 12 stores a driving history 21 of the vehicle 100. The driving history 21 is a record of location information acquired, for example, by a GPS (Global Positioning System) sensor (not shown). The driving history 21 includes information on routes currently or previously traveled by the vehicle 100, such as destinations, waypoints, and routes between the destinations and waypoints. The driving history 21 also includes a history of searches related to driving routes, etc. The driving history 21 can be accessed arbitrarily from devices other than the car navigation system 12, such as the agent system 14.

The speaker 13 outputs sounds, voices, etc. to the interior of the vehicle 100. Each part of the vehicle 100 can access the speaker 13 as needed to output voices, etc. In this embodiment, the car navigation system 12 outputs sounds and voices from the speaker 13 for route guidance, etc. In addition, the agent system 14 outputs sounds, voices, etc. from the speaker 13 for dialogue with the user 10 and for providing information to the user 10, etc.

The agent system 14 is a communication support device that uses an agent unit 22 to support interactive communication between the user 10 and the vehicle 100, etc. In addition to the agent unit 22, the agent system 14 also includes an agent controller 23, a display 24, and a storage device 25.

The agent unit 22 is a user interface that communicates interactively with the user 10 on behalf of the agent system 14 and/or the vehicle 100. In this embodiment, the agent unit 22 is particularly an interactive user interface that uses a lifelike character. Therefore, the agent unit 22 is recognized by the user 10 as the agent system 14 and/or the vehicle 100 itself.

The agent unit 22 has the form of, for example, a person, animal, plant, robot, object, or other symbol, and is represented by a character that essentially serves as a mascot or assistant facing the user 10 in interactive communication with the user 10. Furthermore, in this embodiment, "animated" refers to a character that has a lifelike appearance, i.e., a living creature-like appearance or other characteristics, and that allows a person interacting with it as a simulated living creature without having to be clearly aware that it is a device or a program. In particular, when the character has a human form or other characteristics, "animated" is synonymous with "anthropomorphization." Therefore, by being composed of a lifelike character, the agent unit 22 can become a natural target of interactive communication to the extent that the user 10 is not required to be clearly aware that it is a device or a program.

The lifelike feel of the agent unit 22 is created by the form and/or movements of the character that forms the agent unit 22. In other words, the agent unit 22 is configured so that the biomimetic character can express its own feelings and emotions, which are changes in feelings, through sound, voice, light, and/or changes in form, to the extent that it can at least become a communication target for the user 10. In other words, the biomimetic character that forms the agent unit 22 appropriately creates a lifelike feel of the biomimetic character through changes in facial expression, changes in line of sight, movements such as gestures, changes in tone of voice, or changes in facial color, other patterns, or colors.

The lifelike feel of the biomimetic character allows the user 10 to recognize the pseudo-personality (hereinafter referred to as the pseudo-personality) of the biomimetic character, which is the vehicle 100, the agent system 14, or the agent unit 22. The pseudo-personality of the biomimetic character is based on the settings used by the agent system 14 and other accumulated data. Therefore, the various data used by the agent system 14 to support interactive communication between the user 10 and the vehicle 100 corresponds to the pseudo-personality unique to the biomimetic character or the memories possessed by the biomimetic character with a pseudo-personality. Furthermore, the lifelike feel of the biomimetic character allows the user 10 to recognize the hardware, namely the vehicle 100 or the agent system 14, as the actual body of the biomimetic character. The lifelike feel of the biomimetic character then aids in smooth and natural interactive communication between the user 10 and the vehicle 100. Ultimately, the lifelike feel of the biomimetic character increases the user 10's attachment to the vehicle 100 and/or the agent system 14.

The agent unit 22 may be physically configured using a mechanical mechanism, such as a robot, or may be virtually configured using computer graphics or the like. In this embodiment, the agent unit 22 is a virtual configuration displayed on the display 24. In other words, the character that forms the agent unit 22 is configured by displaying a virtual reality space, an augmented reality space, or a mixed reality space constructed on the display 24.

The agent controller 23 is a control unit that controls the operation of the agent system 14. More specifically, the agent controller 23 is one or more computers programmed with various operations of the agent system 14, such as the behavior of the biomimetic character in response to the actions of the vehicle 100 and/or the user 10. The specific configuration of the agent controller 23 will be described in detail below. The program that operates the agent system 14 is a communication assistance program. The communication assistance program may be provided in the form of a recording medium that can be read by the agent system 14, for example, the vehicle 100 or the communication assistance system 101. Furthermore, the communication assistance program may be partially or completely updated after implementation using a recording medium or so-called OTA (Over The Air) technology.

The display 24 is a display unit that displays videos and various information. If the agent unit 22 is configured virtually, the agent unit 22 is displayed on the display 24. The display 24 can also display, for example, videos captured by the vehicle 100. In this embodiment, the display 24 is a HUD (Head-Up Display) that displays the agent unit 22 in part of the user 10's field of view. The display 24, together with, for example, the speaker 13, constitutes the HMI (Human Machine Interface) of the vehicle 100 and the agent system 14.

In this embodiment, the display 24 is provided as part of the agent system 14. However, instead of providing the display 24 in the agent system 14, or in addition to the display 24 of the agent system 14, a display may be provided in the vehicle 100 or the car navigation system 12. In this case, the agent system 14 can display the agent section 22, etc., on a display provided in the vehicle 100 or the car navigation system 12.

The storage device 25 is a storage device that temporarily or permanently stores the communication support program that operates the agent system 14, as well as control parameters and other setting data. The storage device 25 is composed of memory, a hard disk drive, a solid state drive, or cloud storage provided on the web. The agent controller 23 operates the mimic characters and other components in accordance with the operation settings 26 stored in the storage device 25, which correspond to the situation of the user 10 and the vehicle 100, etc.

The storage device 25 stores one or more action settings 26. In this embodiment, the storage device 25 stores, for example, four specific action settings: a normal action setting 34, a separation action setting 35, a takeover action setting 36, and a birth action setting 37 (see Figure 2). The action settings 26 include control parameters that determine the behavior of the biomimetic character and other actions, as well as control data. Control parameters are, for example, parameters that determine the basic simulated personality of the biomimetic character, such as the behavioral tendencies of the biomimetic character. Control data is, for example, motion data and voice data of the biomimetic character, as well as other data referenced by the agent system 14.

The operation settings 26, i.e., the control parameters and control data included in the operation settings 26, are set according to the selections of the user 10. For example, the control parameters and control data that determine the form and pseudo-personality of the biomimetic character are prepared in advance as one or more options (initial settings), and the user 10 can arbitrarily select and/or change from among these options.

Furthermore, the control parameters and control data included in the operation settings 26 may be adjusted as appropriate depending on the user's 10's reactions during interactive communication with the user 10. For example, if the agent unit 22 is configured using a so-called AI (Artificial Intelligence) program, the pseudo-personality of the biomimetic character is formed or adjusted through interactive communication with the user 10 through the above-mentioned adjustments. Furthermore, for example, if the agent system 14 supports interactive communication based on the driving history 21, some or all of the information obtained from the driving history 21, such as visited locations (destinations) and traveled routes, may be stored as control data. In addition, music played by the user 10 on the vehicle 100, images or videos captured or played by the user 10 on the vehicle 100, or lists of these, may also be stored as control data. Music played by the user 10 in the vehicle 100, images and videos acquired or played by the user 10 in the vehicle 100, or lists of these, are recorded in a history database (not shown) of the car navigation system 12 and can be accessed at will from the agent system 14.

In particular, in this embodiment, the user 10, for example, sells or scraps the vehicle 100 that he or she previously owned (hereinafter referred to as the old vehicle 100a (see FIG. 4)) and switches to a new vehicle 100 (hereinafter referred to as the new vehicle 100b (see FIG. 6)) that is different from the old vehicle 100a. Furthermore, some or all of the data used by the agent system 14 to support interactive communication is transferred from the old vehicle 100a to the new vehicle 100b. Hereinafter, the data used by the agent system 14 to support interactive communication and transferred from the old vehicle 100a to the new vehicle 100b is referred to as "transfer data 53" (see FIG. 4). Therefore, the old vehicle 100a is the vehicle 100 from which data is transferred, and the new vehicle 100b is the vehicle 100 to which the data is transferred. Furthermore, the transfer or transmission of the transfer data 53 from the old vehicle 100a to the new vehicle 100b is referred to as "data transfer."

The specific contents of the transfer data 53 can be set by the user 10 at will when switching vehicles, but when transferring data related to the agent system 14, it is assumed that the transfer data 53 will at least include data that forms the "memory" of the life-like character. In the above example, the transfer data 53 will include at least a list of places that have been visited, routes that have been driven, and songs, images, videos, etc. that the user 10 played in the old vehicle 100a, as memories of the pseudo-character. The transfer data 53 may also include control parameters that determine the pseudo-personality of the life-like character.

In addition, data transfer from the old vehicle 100a to the new vehicle 100b is performed using external storage 27 and external input terminal 28.

The external storage 27 is an external storage device that can be connected and disconnected to the vehicle 100 or the agent system 14 via a wired or wireless connection. The external storage 27 is, for example, a USB (Universal Serial Bus) memory, a flash memory, or cloud storage. In this embodiment, the external storage 27 is a USB memory. The external storage 27 is connected to the old vehicle 100a by the user 10 or the dealer when the old vehicle 100a is sold, and stores the transfer data 53. Furthermore, the external storage 27 that stores the transfer data 53 is connected to the new vehicle 100b by the user 10 or the car dealer, for example, when the new vehicle 100b is started for the first time, and the transfer data 53 is transferred to the new vehicle 100b. In this embodiment, the external storage 27 is directly connected to the agent system 14, but can also be indirectly connected to the agent system 14 via the external input terminal 28.

The external input terminal 28 is an external device that can be connected and disconnected to the vehicle 100 or the agent system 14 via a wired or wireless connection. The external input terminal 28 is, for example, a computer used by the user 10 or a car dealer. In this embodiment, the external input terminal 28 inputs a special control code 33 (see Figure 2) that triggers the start of data transfer to the old vehicle 100a and the new vehicle 100b. The special control code 33 is, for example, a command for executing special operations of the agent system 14, etc., when the vehicle 100 is sold or scrapped, or when the vehicle 100 or the agent system 14 is initially started up. The special control code 33 input to the old vehicle 100a is the first code 33a (see Figure 4). The first code 33a indicates, for example, the sale or scrapping of the vehicle 100, and instructs the external output of the transfer data 53, i.e., the output of the transfer data 53 from the old vehicle 100a to the external storage 27. Furthermore, the special control code 33 input to the new vehicle 100b is the second code 33b (see Figure 6). The second code 33b indicates, for example, the start of use of the vehicle 100 or the agent system 14, and instructs the external input of the handover data 53, i.e., the input of the handover data 53 from the external storage 27 to the new vehicle 100b. The location of the handover data 53 is pre-associated with the second code 33b, or is specified together with the input of the second code 33b.

In this embodiment, both the old vehicle 100a and the new vehicle 100b before and after the transfer are vehicles 100 equipped with the agent system 14 described above, but this is not limited to this. If the old vehicle 100a before the transfer is a vehicle 100 equipped with the agent system 14 described above and the new vehicle after the transfer does not have the agent system 14, at least the transfer data 53 of the old vehicle 100a before the transfer can be saved in the external storage 27. This is included in the data transfer referred to in this embodiment. The same applies when switching from the old vehicle 100a equipped with the agent system 14 to a vehicle not equipped with the agent system 14, and then switching to the new vehicle 100b equipped with the agent system 14. In other words, the transfer data 53 saved in advance in the external storage 27 can be transferred to the vehicle 100 equipped with the agent system 14. This is also included in the data transfer referred to in this embodiment.

In this embodiment, the agent system 14 configured as described above is substantially integrated with the vehicle 100. Therefore, some or all of the functions of the agent controller 23 may be configured by the vehicle controller 15. In this case, the vehicle controller 15 functions as the agent controller 23. The agent system 14 may also be configured by a separate device independent of the vehicle 100. For example, when a device such as a smartphone owned by the user 10 can be linked with the vehicle 100, the agent system 14 may be implemented in the device owned by the user 10.

The vehicle controller 15 is a control unit that comprehensively controls the operation of the vehicle 100. Based on input from the driving operation unit 11, the vehicle controller 15 controls the electric motor and/or engine that drive the vehicle 100, as well as the brakes, etc. The vehicle controller 15 is composed of, for example, one or more computers in which the operation of each component of the vehicle 100 is programmed. The vehicle controller 15 can refer to signals output by the sensors 16 as needed to control the vehicle 100. The vehicle controller 15 also acquires operations on the vehicle 100 and operations on various devices mounted on the vehicle 100. In addition, the vehicle controller 15 acquires parameters necessary to control the vehicle 100 or various devices mounted on the vehicle 100 through calculations using signals acquired from the sensors 16.

Sensor 16 is one or more sensors that measure the conditions of each part of vehicle 100 and the conditions inside or outside vehicle 100. Sensor 16 is, for example, a speed sensor, an acceleration sensor, an in-vehicle camera 29, an in-vehicle microphone 30, an exterior camera, an exterior microphone, and/or a position sensor. In this embodiment, sensor 16 includes at least an in-vehicle camera 29 and an in-vehicle microphone 30.

The in-vehicle camera 29 is one or more imaging devices that capture images of the interior of the vehicle 100 and obtain still or video images. In this embodiment, the in-vehicle camera 29 captures at least the user 10. Hereinafter, a still or video image of the user 10 captured by the in-vehicle camera 29 will be referred to as an in-vehicle image 31 (see Figure 2). The in-vehicle image 31 can detect the user 10's line of sight, position and orientation of the face, body, etc., as well as changes in these.

The in-vehicle camera 29 can acquire in-vehicle images 31 as needed in response to requests from the agent system 14 and/or the vehicle controller 15. In this embodiment, the in-vehicle camera 29 acquires in-vehicle images 31 intermittently or continuously in response to requests from the agent system 14. The in-vehicle images 31 are then retained at least temporarily and used by the agent system 14 to detect the position and orientation of the user 10's line of sight, face, body, etc., as well as changes therein.

The in-vehicle microphone 30 is one or more sound collection devices that capture sounds or voices generated inside the vehicle 100. In this embodiment, the in-vehicle microphone 30 captures at least the voice uttered by the user 10. Hereinafter, the voice captured by the in-vehicle microphone 30 will be referred to as in-vehicle voice 32 (see Figure 2). The in-vehicle voice 32 can capture the user 10's mumblings (monologue), conversations between the user 10 and other passengers, and voices from interactions between the user 10 and the agent unit 22 (hereinafter simply referred to as "conversations").

The in-vehicle microphone 30 can appropriately acquire in-vehicle audio 32 in response to a request from the agent system 14 and/or the vehicle controller 15. In this embodiment, the in-vehicle microphone 30 acquires in-vehicle audio 32 intermittently or continuously in response to a request from the agent system 14. The in-vehicle audio 32 is then stored at least temporarily and used by the agent system 14 to acquire or detect the user's 10 conversation.

Figure 2 is a block diagram showing the configuration of the agent controller 23. As shown in Figure 2, it includes a user action recognition unit 41, a special control code input determination unit 42, a communication control unit 43, and a data storage control unit 44.

The user action recognition unit 41 recognizes the actions of the user 10 using the in-car image 31 and/or the in-car audio 32. For example, the user action recognition unit 41 recognizes the user 10's line of sight, gestures, etc. using the in-car image 31. The user action recognition unit 41 also recognizes the user 10's conversation using the in-car audio 32. These recognition results (hereinafter referred to as the user 10's actions) are output to the communication control unit 43.

The special control code input determination unit 42 determines whether or not a special control code 33 has been input and the type of special control code 33. The special control code input determination unit 42 determines whether a special control code 33 has been input, and if the input special control code 33 is the first code 33a, determines that the vehicle 100 will be sold, scrapped, etc. The special control code input determination unit 42 determines whether a special control code 33 has been input, and if the input special control code 33 is the second code 33b, determines that the vehicle 100 or agent system 14 will be put into use, i.e., will be started for the first time. The determination result of the special control code input determination unit 42 is input to the communication control unit 43 and the data storage control unit 44.

The communication control unit 43 operates the life-mimicking character of the agent unit 22 in response to the actions of the user 10 in accordance with the action settings 26. The communication control unit 43 also acquires information to be notified to the user 10 from the vehicle 100, and notifies the user 10 of this information by the life-mimicking character of the agent unit 22. In this way, the communication control unit 43 supports interactive communication between the user 10 and the vehicle 100. Hereinafter, the actions of the agent unit 22, and in particular the life-mimicking character, that support interactive communication between the user 10 and the vehicle 100 in this way will be referred to as "normal actions."

In addition, the communication control unit 43 causes the agent unit 22 to perform a special action that differs from normal actions when data is transferred. This special action of the agent unit 22, and in particular the biomimetic character, when data is transferred will be referred to below as the "special action."

The communication control unit 43 includes a normal operation control unit 51 and a special operation control unit 52 to execute the normal and special operations described above.

The normal operation control unit 51 supports interactive communication between the user 10 and the vehicle 100 by operating the agent unit 22 and other units in accordance with the user's 10 actions during normal operation when the special control code 33 is not input. In particular, the normal operation control unit 51 assists in smooth and natural interactive communication by operating the biomimetic character of the agent unit 22 in accordance with the normal operation settings 34.

Normal operation setting 34 is one of operation settings 26, and includes control parameters, control data, etc. that predetermine the behavior of the mimic character that supports interactive communication between user 10 and vehicle 100. In this embodiment, transfer data 53 transferred from old vehicle 100a to new vehicle 100b is some or all of the specific control parameters, control data, etc. included in normal operation setting 34.

When the special control code 33 is input, the special action control unit 52 causes the agent unit 22 to execute a special action related to data transfer. In particular, when the special control code 33 is input, the special action control unit 52 causes the life-mimicking character of the agent unit 22 to execute a special action according to the type of special control code 33. For example, the special action control unit 52 directs separation from the life-mimicking character, data transfer, and/or the birth of a life-mimicking character through the actions of the life-mimicking character according to the special control code 33. In this way, the special action control unit 52 notifies the user 10 of separation from the life-mimicking character, data transfer, and/or the birth of a life-mimicking character.

More specifically, when the first code 33a, which indicates the sale or scrapping of the vehicle 100, is input as the special control code 33, the special operation control unit 52 causes the agent unit 22 to execute two types of special operations: a separation operation and a handover operation.

The separation action is an action that uses the agent unit 22 to notify the user 10 of separation from the life-mimicking character. Hereinafter, a separation action that reminds the user 10 of separation from the life-mimicking character is referred to as a separation action. In particular, the special action control unit 52 performs the separation action by operating the life-mimicking character of the agent unit 22 in accordance with the separation action setting 35.

The separation action setting 35 is one of the action settings 26, and includes control parameters and control data that define the behavior of the life-mimicking character that reminds the user 10 of separation from the life-mimicking character. More specifically, the separation action setting 35 defines the behavior of the life-mimicking character that reminds the user 10 of separation from the life-mimicking character by changing the form of the life-mimicking character from a first form used for normal interactive communication to a different second form. The first form of the life-mimicking character is a form that represents the life-mimicking character's normal activity. The second form of the life-mimicking character is a form unique to the separation action, and reminds the user 10 of separation from the life-mimicking character or the end of use of the vehicle 100; it can be said to be a separation form or an end form.

In particular, in this embodiment, the separation action setting 35 determines the manner of a special separation presentation (bereavement presentation) that reminds the user 10 of the loss of the life-like character by changing the form of the life-like character from a first form to a second form that represents the death of the life-like character. Therefore, in this embodiment, when the first code 33a is input as the special control code 33, the user 10 is notified that the life-like character has passed away, along with the sale or scrapping of the vehicle 100.

The takeover action is an action that uses the agent unit 22 to notify the user 10 that data will be taken over. Hereinafter, a takeover action that reminds the user 10 that data will be taken over will be referred to as a takeover effect. In particular, the special action control unit 52 performs the takeover effect by moving the mimic character of the agent unit 22 in accordance with the takeover action setting 36.

The takeover action setting 36 is one of the action settings 26, and includes control parameters and control data that determine the behavior of the mimic character that notifies the user 10 that data will be taken over. In particular, in this embodiment, the takeover action and takeover effect predetermined by the takeover action setting 36 include two types: a first takeover action and first takeover effect, and a second takeover action and second takeover effect.

The first handover operation is an operation that notifies the user 10 that data will be taken over from the vehicle 100, i.e., that data will be output externally from the vehicle 100. The first handover effect is an effect that reminds the user 10 of the handover of data from the vehicle 100, i.e., the external output, through the first handover operation. Therefore, when the first code 33a representing sale or scrapping, etc., is input as the special control code 33, the special operation control unit 52 executes the first handover operation that performs the first handover effect.

The first handover operation consists of two operations: a keepsake formation operation and a keepsake output operation.

The keepsake formation action is an action that notifies the user 10, by operation of the agent unit 22, that a keepsake has been formed for the departing life-mimetic character. A keepsake for a life-mimetic character is a parting gift for the life-mimetic character, such as an object or other symbol that evokes in the user 10 memories of the departing life-mimetic character and/or the departing life-mimetic character. In this embodiment, the life-mimetic character dies as a result of the separation action, and therefore, in the first handover action corresponding to this, the "soul" of the life-mimetic character is displayed on the display 24. Hereinafter, the performance in which the soul or other keepsake of the life-mimetic character is formed by the keepsake formation action will be referred to as the keepsake formation performance.

The keepsake output action is an action that notifies the user 10 that the keepsake of the life-mimicking character will be output outside the vehicle 100. In this embodiment, the keepsake output action moves the keepsake of the life-mimicking character on the display 24 toward the display representing the external storage 27. Hereinafter, the performance in which the keepsake of the life-mimicking character is output outside the vehicle 100 by the keepsake output action is referred to as the keepake output performance.

On the other hand, the second handover operation is an operation that notifies the user 10 that data will be handed over to the vehicle 100, i.e., that data will be externally input to the vehicle 100. The second handover operation is an effect that reminds the user 10 of the handover of data to the vehicle 100 (new vehicle 100b), i.e., the external input, and is the second handover effect.

When the second code 33b, which indicates the initial startup of the vehicle 100 or agent system 14, is input as the special control code 33, the special operation control unit 52 causes the agent unit 22 to execute two types of special operations: a takeover operation and a creation operation.

The handover action executed when the second code 33b is input is a second handover action that performs a second handover effect. In particular, the second handover action in this embodiment is configured by a keepsake input action that notifies the user 10 that a keepsake of the life-like character will be input into the vehicle 100. More specifically, the second handover action (keepsake input action) moves the keepake of the life-like character from the display representing the external storage 27 on the display 24. Hereinafter, the effect in which the keepake of the life-like character is input into the vehicle 100 by the keepake input action will be referred to as the keepake input effect.

The birth action is an action that uses the agent unit 22 to notify the user 10 of the birth of a new life-like character in the vehicle 100 or agent system 14. Hereinafter, a birth action that reminds the user 10 of the birth of a life-like character will be referred to as a birth action. In particular, the special action control unit 52 performs the birth action by moving the life-like character of the agent unit 22 in accordance with the birth action setting 37.

The birth movement setting 37 is one of the movement settings 26, and includes control parameters and control data that define the movement of the life-like character, reminding the user 10 of the birth of a new life-like character.

In this embodiment, one or more options are provided in advance for the form and pseudo-personality of the newly born life-like character, and the user 10 can select the form and pseudo-personality of the newly born life-like character. However, when transferring data, the special action control unit 52 uses the birth action to make at least some of the form and/or pseudo-personality of the life-like character separated from the old vehicle 100a and the life-like character born in the new vehicle 100b different. For example, if the life-like character in the old vehicle 100a was a dog-type character, the options for the life-like character to be born in the new vehicle 100b may be narrowed down to life-like characters other than dogs. Furthermore, even if the options for the new vehicle 100b are life-like characters of the same type and/or model as the old vehicle 100a, the color and pattern of the newly born life-like character are automatically made different from the life-like character in the old vehicle 100a, such as by changing the eye color. In either case, the special action control unit 52 avoids the morphology of the life-like character being completely identical between the old vehicle 100a and the new vehicle 100b, and creates a "new" life-like character in the new vehicle 100b that is at least morphologically different from the life-like character in the old vehicle 100a. Information regarding the morphology of the life-like character in the old vehicle 100a is included in the transfer data 53.

When the first code 33a is input as the special control code 33, the data storage control unit 44 collects handover data 53 from each component constituting the agent system 14 and/or vehicle 100 and stores the data in the external storage 27. The specific content of the handover data 53 collected by the data storage control unit 44 can be adjusted by settings made by the user 10 or the dealer. In addition, in this embodiment, the data storage control unit 44 is provided independently of the special operation control unit 52, but the data storage control unit 44 may also be configured integrally with the special operation control unit 52.

The following describes the operation of data handover in the vehicle 100, agent system 14 (communication support device), and communication support system 101 configured as described above.

Figure 3 is a flowchart showing the process for transferring data from the old vehicle 100a. As shown in Figure 3, in the old vehicle 100a, in step S101, the special control code input determination unit 42 monitors the input of the special control code 33. Then, when it is determined that a special control code 33 has been input, in step S102, the type of the input special control code 33 is determined. Here, it is assumed that the first code 33a, which indicates sale or scrapping, etc., has been input as the special control code 33.

In this case, in step S103, the special action control unit 52 causes the agent unit 22 to execute a separation action. As a result, the user 10 is notified of the separation from the life-like character by a separation performance by the life-like character of the old vehicle 100a. Furthermore, in step S104, the special action control unit 52 causes the agent unit 22 to execute a first handover action. More specifically, a keepsake formation performance and a keepsake output performance are performed.

In this way, while the agent unit 22 executes the various special actions described above, in step S105 the data saving control unit 44 collects the handover data 53 and saves it in the external storage 27. Then, once the agent unit 22 has completed the performance of the various special actions and the saving of the handover data 53, the agent system 14 stops in step S106.

Figure 4 is an explanatory diagram showing the operation related to data transfer in the old vehicle 100a. Figure 4(A) is an explanatory diagram showing a scene in which the agent unit 22 is operating normally. Figure 4(B) is an explanatory diagram showing a scene in which the first code 33a is input as the special control code 33. Figure 4(C) is an explanatory diagram showing a scene in which transfer data 53 is output. Figure 4(D) is an explanatory diagram showing a scene in which the agent system 14 is stopped.

As shown in FIG. 4(A), during normal operation, a dog-type mimicking character 22a is displayed in a first form on the display 24 of the old vehicle 100a, and the actions of this dog-type mimicking character 22a support interactive communication between the user 10 and the old vehicle 100a. The form of the dog-type mimicking character 22a in FIG. 4(A) is the first form used for normal interactive communication. When the user 10 subsequently sells the old vehicle 100a, a first code 33a, which is a special control code 33, is input to the old vehicle 100a, as indicated by arrow A1 in FIG. 4(B). When the first code 33a is input in this manner, the dog-type mimicking character 22a performs a separation presentation (bereavement presentation), for example, in which the dog-type mimicking character 22a dies. Specifically, the form of the dog-type mimicking character 22a changes to a second form that reminds the user 10 of the dog-type mimicking character's death. This allows the user 10 to sense the death of the dog-type mimicking character 22a. Additionally, the dog-shaped mimetic character 22a creates a soul-shaped keepsake 22b through a keepsake formation performance.

Then, as shown in Figure 4(C), the keepsake output performance moves the soul-shaped keepsake 22b toward the display 27a that resembles the external storage 27. Meanwhile, in the background of these various performances, as shown by arrow A2, handover data 53 is collected and saved in the external storage 27. Then, once these various performances and the saving of the handover data 53 are complete, the agent system 14 is shut down, as shown in Figure 4(D).

Figure 5 is a flowchart showing the process for transferring data in the new vehicle 100b. As shown in Figure 5, in the new vehicle 100b, in step S201, the special control code input determination unit 42 monitors the input of the special control code 33. Then, when it is determined that the special control code 33 has been input, in step S202, the type of the input special control code 33 is determined. Here, it is assumed that the second code 33b, which indicates the start of use of the vehicle 100 and the agent system 14, i.e., initial startup, has been input as the special control code 33.

In this case, in step S203, the special action control unit 52 causes the agent unit 22 to execute the second handover action. That is, on the display 24 of the new vehicle 100b, a keepsake input display notifies the user 10 that the soul-shaped keepsake 22b formed from the dog-shaped life-like character 22a in the old vehicle 100a will be input to the new vehicle 100b. Accordingly, in step S204, the handover data 53 is obtained from the external storage 27 and input to the new vehicle 100b.

Furthermore, in step S205, the special action control unit 52 causes the agent unit 22 to execute a creation action. As a result, a new life-like character is created in the new vehicle 100b. Then, in step S206, the new vehicle 100b starts normal operation by operating the new life-like character using the transfer data 53 from the old vehicle 100a.

Figure 6 is an explanatory diagram showing the data transfer process in new vehicle 100b. Figure 6(A) is an explanatory diagram showing a scene in which second code 33b is input as a special control code. Figure 6(B) is an explanatory diagram showing a scene in which a new mimic character 22c is born in new vehicle 100b.

As shown by arrow B1 in Figure 6 (A), when the second code 33b is entered into the new vehicle 100b, a display 27a simulating external storage 27 is displayed on the display 24 of the new vehicle 100b. The display 27a simulating external storage 27 then notifies the user 10 of the process of inputting a soul-shaped keepsake 22b formed from the dog-shaped life-like character 22a in the old vehicle 100a. Meanwhile, in the background of this keepsake input performance, as shown by arrow B2, transfer data 53 is obtained from the external storage 27 and entered into the new vehicle 100b.

6(B), in the new vehicle 100b, a new rabbit-type life-like character 22c is born through a birthing action, inheriting the transfer data 53, unlike the dog-type life-like character 22a in the old vehicle 100a. After this birthing action is performed, the rabbit-type life-like character 22c performs normal actions using the transfer data 53. As a result, when the rabbit-type life-like character 22c comes to a place that it has been to in the old vehicle 100a, it will say, for example, "I've been here before," even if it has never been there before as the rabbit-type life-like character 22c. Furthermore, when the rabbit-type life-like character 22c plays a song or video that it has played in the old vehicle 100a, it will say, for example, "I've heard of it," or "I've seen it," even if it has never been there before as the rabbit-type life-like character 22c. In addition, the rabbit-type life-like character 22c may provide topics of interest to the user 10 that the dog-type life-like character 22a in the old vehicle 100a knew, even if it has never been there before as the rabbit-type life-like character 22c. In addition, the rabbit-type life-like character 22c may show reactions related to the pseudo-personality of the dog-type life-like character 22a formed through interactive communication in the classic vehicle 100a. For example, the rabbit-type life-like character 22c may show a favorable reaction to music or topics that match the tastes of the dog-type life-like character 22a formed as a pseudo-personality.

In the above embodiment, when the transfer data 53 is output from the old vehicle 100a to the external storage 27, a memento output effect is performed in which the keepsake 22b is simply moved. However, this memento output effect is not limited to this form. For example, when the transfer data 53 is saved in the external storage 27, a memento output effect may be performed in which some or all of the transfer data 53 is sequentially displayed on the display 24. In other words, a memento output effect may be performed that is reminiscent of the memories of the life-like character being projected like a kaleidoscope (a flashback). This memento output effect more clearly notifies the user 10 that the memories of the life-like character of the old vehicle 100a are being output and inherited. This flashback-style effect may be performed when the memento 22b is not formed. Furthermore, it is particularly preferable that the flashback-style effect be performed when the transfer data 53 includes an image or video.

Similarly, in the above embodiment, when the transfer data 53 is input from the external storage 27 to the new vehicle 100b, a memento output effect is performed in which the keepsake 22b is simply moved, but this memento output effect is not limited to this form. For example, when the transfer data 53 is retrieved from the external storage 27, a memento input effect may be executed in which some or all of the transfer data 53 is sequentially displayed on the display 24. This more clearly notifies the user 10 that the memories of the life-like character of the old vehicle 100a have been input and will be inherited by the new life-like character of the new vehicle 100b. This form of effect may also be performed when the memento 22b is not formed.

As described above, the data transfer method according to this embodiment is a data transfer method for transferring data used to support communication in a vehicle 100 equipped with a communication support device (agent system 14) that supports communication with a user through an agent unit 22, which is an interactive user interface using bionic characters. This data transfer method achieves the following effects when transferring data from the previous vehicle 100a.

That is, in the data transfer method according to this embodiment, the input of special control code 33, which is a trigger for starting data transfer, is determined. Then, when special control code 33 is first code 33a that instructs external output of transfer data 53, the agent unit 22 executes a separation action that notifies the user 10 of separation from the life-mimetic character by changing the form of the life-mimetic character from a first form used for communication to a second form different from the first form. Furthermore, when special control code 33 is first code 33a, transfer data 53 is saved in external storage 27.

In this way, when the transfer data 53 is output in conjunction with the separation action, the data can be transferred without compromising the lifelike feel of the biomimetic character in the agent unit 22.

More specifically, for the user 10, the old vehicle 100a and its agent system 14 from which the data is being transferred are essentially the body of the life-like character in the old vehicle 100a, and the transfer data 53 are essentially the memories of that life-like character. Therefore, if the transfer data 53 is simply transferred mechanically without performing a separation operation, the memories of the life-like character will be transferred even though the body of the life-like character will be lost when the old vehicle 100a is sold or scrapped. Because this type of memory transfer does not occur in a normal living being, the lifelikeness of the life-like character in the agent unit 22 is lost. As a result, the user 10 will find it difficult to recognize the life-like character as a natural communication target, which defeats the original purpose of using a life-like character, which is to facilitate smooth and natural interactive communication between the user 10 and the vehicle 100.

In contrast, when the agent unit 22 performs a separation action as in the above embodiment, the user 10 can sense that at least the lifelike character is separating from the user 10 along with its body, the vehicle 100 or agent system 14. This maintains the lifelike feel of the lifelike character in terms of the physical unity of the vehicle 100 or agent system 14 and the lifelike character. As a result, even if the transfer data 53 is present, the user 10 is more likely to accept the lifelike character as a subject for smooth and natural interactive communication. In other words, the data transfer method according to the above embodiment makes it easier for the user 10 to get the impression that the vehicle 100 or agent system 14 and the lifelike character are one and that the lifelike character is alive, which the user 10 is more likely to accept.

In the data transfer method according to the above embodiment, particularly when the special control code 33 is the first code 33a, the agent unit 22 executes a keepsake formation operation to notify the user that a memento 22b has been created for the life-like mimic character, along with the execution of a separation operation. In this way, when the keepsake formation operation notifies the user 10 that a keepsake 22b has been created for the life-like mimic character, the life-like feel of the life-like mimic character is maintained. In other words, if the life-like mimic character's memories are inherited when switching from the old vehicle 100a to the new vehicle 100b, the life-like feel of the life-like mimic character is lost in terms of the continuity of memories between different life-like mimic characters. However, when the user 10 is notified that a keepsake 22b will be created, as described above, the user 10 is more likely to accept that memories, etc. will be inherited through the keepsake 22b. In other words, the keepsake formation operation makes it easier to maintain the life-like feel of the life-like mimic character, particularly in terms of the continuity of memories between life-like mimic characters before and after the vehicle switch.

In particular, in the data transfer method according to the above embodiment, when the special control code 33 is the first code 33a, the agent unit 22 executes a keepsake output operation that notifies the user 10 that the keepsake 22b will be output to the outside of the vehicle 100. When the keepsake output operation is executed in this manner, the user 10 is particularly likely to accept that memories and the like will be passed on via the keepsake 22b. Therefore, the keepsake output operation makes it particularly easy to maintain the lifelike feel of the lifelike character, regardless of the continuity of memories between the lifelike characters before and after changing vehicles.

Furthermore, in the data transfer method according to the above embodiment, the keepsake output operation is performed by displaying the movement of the keepsake 22b toward the display 27a representing the external storage 27. In this way, when the external output destination of the transfer data 53 is notified to the user 10, the user 10 is particularly likely to accept that memories and the like will be passed on via the keepsake 22b. Therefore, the keepsake output operation makes it easier to maintain the lifelike feel of the lifelike character, particularly in terms of the continuity of memories between the lifelike characters before and after the transfer.

In the data transfer method according to the above embodiment, the second mode represents the death of the life-like character. In this way, when transferring data from the previous vehicle 100a, notifying the user 10 of the death of the life-like character makes it easier to maintain the physical unity between the vehicle 100 or agent system 14 and the life-like character, particularly the life-like feel of the life-like character.

In the data transfer method according to the above embodiment, when the transfer data 53 is saved in the external storage 27, some or all of the transfer data 53 is displayed sequentially on the display 24. By displaying some or all of the transfer data 53 sequentially on the display 24 in this way, the user 10 is particularly clearly notified of the inheritance of the life-like character's memory. As a result, the lifelike feel of the life-like character is maintained regardless of the continuity of the memory of the life-like character between the old vehicle 100a and the new vehicle 100b.

The data transfer method according to this embodiment provides the following advantages regarding data transfer to the new vehicle 100b after the transfer:

In the data transfer method according to the above embodiment, when the special control code 33 is the second code 33b that instructs the external input of transfer data 53, the transfer data 53 associated with the second code 33b or the transfer data 53 specified along with the input of the second code 33b is acquired from the external storage 27. Then, when the special control code 33 is the second code 33b, the agent unit 22 executes a birth action that notifies the user 10 of the birth of a new life-like character 22c that differs in form from the life-like character 22a in the previous vehicle 100a from which the acquired transfer data 53 is to be transferred. After the birth action is executed, the agent unit 22 is driven using the acquired transfer data 53.

In this way, when the user 10 is notified of the birth of a new life-like character in the new vehicle 100b, the life-like feel of the life-like character is maintained in terms of the physical unity between the vehicle 100 or agent system 14 and the life-like character. As a result, even if the transfer data 53 exists, the user 10 is more likely to accept the life-like character as a subject for smooth and natural interactive communication.

In the data transfer method according to the above embodiment, if a keepsake 22b has been created in the old vehicle 100a, particularly when the transfer data 53 is acquired, the agent unit 22 executes a keepsake input operation to notify the user 10 that the keepsake 22b has been entered into the vehicle. This keepsake input operation clearly notifies the user 10 via the keepsake 22b created in the old vehicle 100a that the memories of the life-like character 22a of the old vehicle 100a will be inherited by the new vehicle 100b and the new life-like character 22c in the new vehicle 100b. This makes it easier to maintain the lifelike feel of the life-like character in terms of memory continuity between the life-like characters before and after the vehicle change.

Furthermore, in the data transfer method according to the above embodiment, the above-mentioned memento input operation is particularly performed by a display that moves the memento 22b from the display 27a representing the external storage 27. In this way, when the external input source of the transfer data 53 is notified to the user 10, the user 10 is particularly likely to accept that memories and the like will be passed on via the memento 22b. Therefore, the memento input operation makes it easier to maintain the lifelike feel of the biomimetic character, particularly in terms of memory continuity between the biomimetic characters before and after the transfer.

The above describes embodiments and variations of the present invention, but the configurations of the above embodiments and variations merely illustrate some of the application examples of the present invention and are not intended to limit the technical scope of the present invention. The configurations shown in the above embodiments and variations can be implemented in any combination, in whole or in part. Furthermore, some of the configurations shown in the above embodiments and variations can be omitted.

For example, in the separation action, takeover action, and birth action, lamps (such as room lamps) and speakers 13 inside the vehicle 100 can be used instead of, or in addition to, the display 24 of the above-described embodiments. Specifically, in the separation action, the room lamp can be flashed and the flashing interval can be gradually shortened to more effectively portray the separation from the biomimetic character.

Furthermore, for example, separation effects using a biomimetic character are not limited to death effects, and any other form of separation can be used. However, death effects in which a biomimetic character dies are particularly likely to make the user 10 sense the physical unity between the vehicle 100 or agent system 14 and the biomimetic character. For this reason, death effects are particularly likely to maintain the lifelike feel of the biomimetic character when transferring data. Furthermore, the form of the keepsake 22b created when a biomimetic character dies is arbitrary. In the above embodiment, a soul-shaped keepsake 22b is created, but the keepsake 22b created in the keepsake creation operation can take any form depending on the country, region, and/or religious beliefs of the user 10, as long as it can be recognized as a keepsake or personal belonging. For example, when a death effect is performed, the keepsake creation operation may create a keepsake in the form of a coffin, gravestone, etc. instead of a soul-shaped keepsake 22b.

Furthermore, for example, if the agent unit 22 is configured using an AI program, some or all of its learning data can be included in the handover data 53.

10: User, 12: Car navigation system, 13: Speaker, 14: Agent system (communication support device), 21: Driving history, 22: Agent unit, 22a: Mimic character, 22a: Keepsake, 22c: Mimic character, 23: Agent controller, 24: Display, 26: Operation settings, 27: External storage, 28: External input terminal, 33: Special control code, 33a: First code, 33b: Second code, 42: Special control code input determination unit, 43: Communication control unit, 44: Data storage control unit, 52: Special operation control unit, 53: Transfer data, 100: Vehicle, 101: Communication support system

Claims (11)

1. A data transfer method for transferring data used to support communication in a vehicle equipped with a communication support device that supports communication with a user by an agent unit that is an interactive user interface using a biomimetic character, comprising:
determining whether a special control code, which is a trigger for starting the data transfer, has been input;
when the special control code is a first code instructing external output of the data, changing the form of the character from a first form used for the communication to a second form different from the first form, thereby executing a separation action to notify the user of separation from the character and a keepsake formation action to notify the user that a keepsake of the character has been formed, by the agent unit;
When the special control code is the first code, the data is stored in an external storage.
How to transfer data. 2. The data transfer method according to claim 1 ,
when the special control code is the first code, a keepsake output operation is executed by the agent unit to notify the user that the keepsake will be output to the outside of the vehicle.
How to transfer data. 3. The data transfer method according to claim 2 ,
the keepsake output action is performed by a display that moves the keepsake toward a display that represents the external storage;
How to transfer data. The data transfer method according to any one of claims 1 to 3 ,
The second form represents the death of the biomimetic character.
How to transfer data. The data transfer method according to any one of claims 1 to 4 ,
When the data is stored in the external storage, a part or all of the data is displayed sequentially on a display.
How to transfer data. The data transfer method according to any one of claims 1 to 5 ,
When the special control code is a second code instructing external input of the data, the data associated with the second code or the data specified together with input of the second code is acquired from the external storage;
when the special control code is the second code, executing a creation action by the agent unit to notify the user of the creation of a new character having a form different from that of the character in the vehicle from which the acquired data is taken over;
After the creation operation is performed, the agent unit is driven using the acquired data.
How to transfer data. A data transfer method according to claim 4 , which cites any one of claims 1 to 3 ,
When acquiring the data, the agent unit executes a keepsake input operation to notify the user that the keepsake has been input into the vehicle.
How to transfer data. 8. The data transfer method according to claim 7 ,
the keepsake input action is performed by a display that moves the keepsake from the display representing the external storage;
How to transfer data. A communication support device that is mounted on a vehicle and supports communication with a user by an agent unit that is an interactive user interface using a biomimetic character,
a special control code input determination unit that determines whether a special control code is input, which is a trigger for starting the transfer of data used to support the communication;
a special action control unit that, when the special control code is a first code instructing external output of the data, changes the form of the character from a first form used for the communication to a second form different from the first form, thereby executing , by the agent unit, a separation action that notifies the user of separation from the character and a keepsake formation action that notifies the user that a keepsake of the character has been formed ;
a data storage control unit that stores the data in an external storage when the special control code is the first code;
A communication support device comprising: A communication support program that operates a communication support device that is mounted on a vehicle and supports communication with a user by an agent unit that is an interactive user interface using a biomimetic character,
The communication support device,
a special control code input determination unit that determines whether a special control code is input, which is a trigger for starting the transfer of data used to support the communication;
a special action control unit that, when the special control code is a first code instructing external output of the data, changes the form of the character from a first form used for the communication to a second form different from the first form , thereby executing, by the agent unit, a separation action that notifies the user of separation from the character and a keepsake formation action that notifies the user that a keepsake of the character has been formed ; and
a data storage control unit that stores the data in an external storage when the special control code is the first code;
A communication support program that operates as a A communication support system comprising: a vehicle; and a communication support device mounted on the vehicle, the communication support device supporting communication with a user by an agent unit which is an interactive user interface using a biomimetic character,
a special control code input determination unit that determines whether a special control code is input, which is a trigger for starting the transfer of data used to support the communication;
a special action control unit that, when the special control code is a first code instructing external output of the data, changes the form of the character from a first form used for the communication to a second form different from the first form, and executes, by the agent unit, a separation action that notifies the user of separation from the character and a keepsake formation action that notifies the user that a keepsake of the character has been formed ;
a data storage control unit that stores the data in an external storage when the special control code is the first code;
A communication support system comprising: