JP4449446B2 - In-vehicle device and data creation device - Google Patents

Description

  The present invention relates to an on-vehicle device and a data creation device, and for example, relates to an on-vehicle device that realizes an agent function for performing conversations and autonomously performing device operations through communication with a vehicle occupant, and the data creation device.

For example, pet-type robots such as dogs, and agent devices that interact with passengers by providing guidance on device operations such as navigation devices in the passenger compartment and asking questions and suggestions according to the situation have been developed. It is mounted on a vehicle as an in-vehicle device.
In such an in-vehicle device (agent device), various states conceivable for the device are assumed, and the actions to be taken when each assumed state is detected are defined according to predetermined data and programs. .
However, in the conventional agent device, since the condition setting for the agent to appear automatically can only be realized by creating and modifying the program, it cannot be created or changed without knowledge of the program, It took a lot of time and money for development.
Therefore, the applicant of the present invention considers that the various processes performed by the in-vehicle apparatus (agent apparatus) are execution of processes instructed by scenario data (which may include some programs) that specify a scenario in which each scene continues. In view of this, we have proposed a data creation device (scenario editor) that can create scenario data regardless of the knowledge of the program by standardizing the scenario data format.
Japanese Patent Application No. 2002-161744

In this data creation device, a screen element (scene) defining character display content and processing content is defined as one screen element, and a plurality of screen elements are combined with transition conditions for transition from one screen element to another screen element. By selecting and entering the screen element transition body (scenario) and the activation conditions for executing the screen element transition body in order, the creator can easily create scenario data that develops the scenes of his / her favorite conditions. Can be created.
In the in-vehicle device, the created scenario data is acquired and registered from the outside, and it is determined whether or not the conditions for all the start conditions are satisfied, and the screen element transition body of the scenario data that satisfies the start conditions Is supposed to run.

As described above, the data creation apparatus can increase the scenario data by registering the scenario data created by a third party obtained by downloading or the like and the scenario data created by the user himself / herself in the agent apparatus.
Since the activation conditions included in the scenario data can be freely set in the same manner as the screen element transition body (scenario), there are possibilities that scenes (conditions) for executing the scenario are set in a wide variety.

However, scenario data created by a conventional data creation device includes a management part including a condition part (startup condition) for executing a scenario, and an actual part (screen element transition body) of scenario data used at the time of execution. Have always been made together.
For this reason, there is a problem that scenario data having a large data size is integrally stored in the in-vehicle device, and the storage area becomes large.
In addition, there are many scenarios that are activated in accordance with the activation conditions, for example, when a vehicle exists in a specific date or a specific area. For this reason, even if the scenario is not actually used, it is necessary to save it in the storage medium of the in-vehicle device in order to start the scenario when the condition is satisfied, and the capacity of the storage medium increases. is there.
Since the capacity of the storage medium installed in the in-vehicle device is limited, there is a limit to the amount of scenarios that can be downloaded and registered. To increase this limit, the capacity of the storage medium installed in the in-vehicle device is limited. Had to be increased.
In addition, as the number of scenario data increases, there is a problem in that the load on the agent device side for determining whether or not a start condition for automatically starting a scenario is satisfied increases.

The present invention has been made to solve the above-described problems, and has as its first object to make it possible to execute more screen element transition bodies with a smaller storage capacity.
A second object is to reduce the determination load of the start condition for executing the screen element transition body.

(1) In the first aspect of the invention, a start condition storage means for storing a start condition for screen element transition body data configured by combining screen elements in which processing contents defined in synchronism with screen display are defined. Management data storage means for storing management data for managing the storage destination of the screen element transition body data corresponding to the activation condition, condition determination means for determining whether the activation condition is satisfied, and the condition determination means in case it is determined to satisfy the activation condition, an acquisition means for acquiring the screen element transition element data stored in association with the start condition in accordance with the management data, executes the screen element transition body data the acquired It includes execution means, and wherein the management data storage means, as said management data, screen element transition element data corresponding to the activation condition is stored in the device Runoka, information indicating whether stored on the outside of the device is recorded, the storage destination specifying information that specifies the storage destination of the screen element transition body data stored in the device outside, stored in association with the activation condition An in-vehicle device is provided.
(2) In invention of Claim 2 , ID is provided for every said screen element transition body data , The starting condition and preservation | save destination designation | designated information corresponding to the said ID are linked | related, It is characterized by the above-mentioned. An in-vehicle device according to claim 1 is provided.
(3) In the invention described in claim 3 , the activation conditions are classified by date or position, and the condition determining means determines whether the activation conditions are satisfied according to the classification. claim 1 or a provide a vehicle apparatus according to claim 2.
(4) In the invention according to claim 4 , the activation condition is classified into an activation condition that includes a position as a condition and an activation condition that does not include a position, and the activation condition that includes a position as a condition is an area unit divided into a certain size. And the condition determining means determines whether or not the position satisfies an activation condition that does not include a condition and an activation condition that is classified into an area corresponding to the current position of the vehicle. A vehicle-mounted device according to any one of claims 1 to 3 is provided.
(5) In the invention described in claim 5, the activation condition storage means for storing the activation condition for the screen element transition body data configured by combining the screen elements in which the processing contents executed in synchronization with the screen display are defined. And creation means for creating screen element transition body data configured by combining screen elements in which processing contents executed in the in- vehicle device are defined in synchronization with the screen display, and activation for starting the screen element transition body data Setting start condition setting means for setting a condition and management data in which information indicating whether screen element transition body data corresponding to the start condition is stored in the apparatus or stored outside the apparatus is set a management data setting means for said screen element transition body data storage destination specifying information that indicates whether the stored anywhere outside the device, set in association with the activation condition It provides data creation apparatus characterized by comprising: a storage destination information setting means.

According to the present invention, information indicating whether the screen element transition body data corresponding to the activation condition is stored in the device or stored outside the device is stored as management data, and is stored outside the device. Since the storage destination designation information for designating the storage destination of the stored data or program is stored in association with the activation condition, more data or programs can be added and executed with a smaller storage capacity.

  Hereinafter, an agent device that is a preferred embodiment of the in-vehicle device of the present invention, a server that stores a scenario, and a scenario editor that is a preferred embodiment of a data creation device will be described in detail with reference to FIGS. explain.

(1) Outline of Embodiment In the agent device of the present embodiment, an agent (character) image (planar image, stereoscopic image such as holography) having a predetermined appearance is displayed in the vehicle. The agent device has a function of recognizing and judging the surrounding state (including human movement and voice) from the detection result of the sensor and the like, and outputting an action and voice according to the result. Executes in conjunction with the movement and voice of the appearance. For example, a question requesting an answer (Japanese food, Western food, etc.) such as “Which genre do you like to eat” is performed, and the content of the user's answer to this question is determined (recognition of answer voice and selection of answer selection button) And the process corresponding to the next scene is executed. In this way, since the inquiry requesting an answer from the apparatus and the execution of the predetermined operation is started in response to the answer, the user seems to have an agent with a pseudo personality in the vehicle. Come to experience. In the following description, execution of a series of functions of such an agent device will be described as an agent action or operation.
In the agent device of the present embodiment, this agent performs various communications with the driver and substitution of operations. And various actions (each action) autonomously performed by the agent are composed of a plurality of scenarios (screen element transition bodies).
In a format standardized by a plurality of scenario data that defines the contents of a series of consecutive actions by agents and autonomous activation conditions (activation conditions) for autonomously starting (activating) the deployment of each scenario. Created.

The scenario data is composed of one or a plurality of continuous scenes with a scene (screen element) as a minimum unit. A scene composed of at least one of autonomously processed content and agent image and sound is one scene.
Scenario data includes one transition condition (transition condition) for transitioning from a predetermined scene to the next scene or a plurality of transition conditions (branching conditions (transition of scenes for each state when a plurality of states occur). The development configuration of each scene is defined from the conditions for) and the transfer destination data for specifying the transfer destination scene corresponding to each transfer condition.

Each scenario configured as described above is stored in a predetermined address such as one or a plurality of servers connected to the Internet separated from the autonomous activation condition, or a homepage.
As storage destination designation information indicating the storage destination of each scenario, a resource on the Internet is designated by a URL (Uniform Resource Locator).
The scenario creation device converts the designation of the scenario data storage URL and the classification based on the date and location information of the activation condition into a format that can be executed by the agent device after the creation of the scenario and its activation condition is completed. When you do.

Autonomous activation conditions for automatically executing each scenario are the logical product of the individual conditions based on the date, time, position, road type, vehicle status, navigation device operating status, and user data (not including logical sum) It is expanded to a set of individual conditions. And the autonomous starting conditions which consist of a logical product are grouped (classified) by sorting by the date and time which are predetermined individual conditions. The positions are classified by area (mesh) divided into a certain size. In the present embodiment, the classification is made in the order of year, month, day, primary mesh, and secondary mesh.
That is, first, the conditions that start automatically from the conditions by year (individual conditions) are grouped, and then the conditions that start automatically from the conditions by date (month and day) are the same date (Months and days) are grouped, then those that enter a large area (primary mesh) under the automatic start condition for the next position are grouped together, and finally small pieces further separated in the primary mesh Those that fall in the region (secondary mesh) are grouped together.
Note that those that do not include the year, date, and location conditions are also classified as those that do not have the applicable conditions. For example, in the case of an autonomous activation condition that has a position condition without a year / month / day condition, it is classified into a primary mesh and a secondary mesh according to the position within the classification with no date condition and the classification with no date condition. Has been.

The classified autonomous activation conditions for each scenario data are set in association with a URL (save destination designation information) indicating the save destination of the scenario data.
The autonomous activation conditions for each scenario are separated from the scenario, and the activation condition and the URL storing the scenario are acquired and stored in the agent device via the Internet, mail, a predetermined storage medium, or the like. (Start condition storage means)

On the other hand, the user of the agent device creates unique scenario data according to the defined standard using the scenario creation device. The scenario creation device can be configured by installing a scenario editing program and data in a personal computer.
The created scenario data is transmitted to the agent device via a network such as the Internet, or downloaded, or stored in the agent device via a predetermined semiconductor memory. It is possible to make an agent perform the desired action (communication and processing).
The first scene of the scenario to be created can be, for example, a scenario of a question scene that requires an answer to a human being.

Then, it is possible to store the uniquely created scenario data by specifying a URL in a server or the like by communication such as the Internet.
On the other hand, the activation condition corresponding to the created scenario data and the save destination URL of the scenario data can be input from an external device via the input device. The input device in this case corresponds to a storage medium drive device that reads the contents of the semiconductor memory when the activation condition and URL to be added to the semiconductor memory are stored, and a specific server or the like via a network such as the Internet. In the case of downloading from, the communication control device corresponds.

The agent device is provided with mail and browser software to download the scenario start condition and URL using the browser software or the like, and whether or not the downloaded file is the scenario data start condition and URL for causing the agent to function If the activation condition and the URL are included, it can be incorporated into a predetermined place and used.
Similarly, when attached to an e-mail, it is determined whether or not the attached file is an activation condition and a URL, and if so, it is incorporated into the agent system and can be used.
As a result, in addition to the conventional method, the original communication infrastructure was created using a personal computer or the like by using the existing communication infrastructure such as mail or communication using a network, or via a semiconductor memory or the like. It becomes possible to add the activation condition and URL of the scenario.
In this way, the user can easily and independently create a scenario for causing the agent to function as he / she desires, thereby eliminating resistance to the autonomous operation of the agent device.

  Furthermore, the agent device fulfills the process of determining whether the condition for autonomously starting (automatically appearing) the agent based on the scenario data created by the scenario creation device is satisfied or meets a specific state A system that can be executed occasionally and can automatically make agents appear when the conditions are met is realized with a small storage capacity.

That is, when a scenario can be executed by an agent device, only acquisition scenario management data including an autonomous activation condition and URL for executing the scenario is obtained by downloading or the like.
Then, the agent device monitors whether or not the autonomous activation condition is satisfied, and when the autonomous activation condition is satisfied, the scenario data (scenario main body) corresponding to the autonomous activation condition is represented by the URL associated with the autonomous activation condition. Download from the designated storage location and temporarily store it (screen element transition body acquisition means), and execute the acquired scenario.
As the autonomous activation condition of the scenario, a necessary portion is read from a current position and date of the condition portion into a storage medium (for example, RAM) that can be accessed at high speed, and execution is determined.
When a scenario execution request is issued as a result of the execution determination, the scenario data is downloaded from the server using the URL of the server where the scenario data exists, and is executed when the download is completed.

  As described above, the navigation device stores the acquisition scenario management data including the autonomous activation condition and the URL, and the scenario data (scenario main body) is downloaded and executed from the URL of the storage destination at the time of execution. Even if the number of scenarios (functions) is large, the capacity of the storage medium mounted on the in-vehicle device can be reduced.

  In addition, in the condition determination unit that automatically makes an agent appear, the scenario of the start condition including the condition depending on the point is, for example, whether or not only the area (mesh) where the point is located and the adjacent mesh are automatically started. Judgment. It is always determined whether or not to automatically start those that do not include a point condition. When the position of the vehicle moves and the position where the vehicle is located moves to the adjacent mesh, a new automatic start condition is acquired again. In other words, the mesh where the point where you are and the mesh next to it are acquired again. As a result, when the vehicle is located in Tokyo, a scenario that includes the condition of being in Sapporo or a scenario that includes the condition of being in Fukuoka (a scenario that cannot be started automatically based on common sense) ) Is not judged from the beginning, and the load is reduced.

In addition, in the scenario of the start condition including the condition based on the date, for example, it is determined whether to start automatically only on the current day and the next day. For those that do not include a date condition, it is always determined whether to start automatically. As a result, when the date is December 24, a scenario including a condition related to a date other than the scenario including the condition of December 24 which is the current day and December 25 which is the next day (common sense The scenario that cannot be started automatically) is not judged from the beginning and the load is reduced.
In this embodiment, when determining whether or not the autonomous activation condition of this scenario is satisfied, since the autonomous activation condition is classified by date and position, it is classified on the current day and the next day, and Within the classification, only the primary mesh including the vehicle current position and the autonomous activation conditions classified in the adjacent mesh are read, and it is determined whether or not the conditions are satisfied.

(2) Details of Embodiment FIG. 1 shows an overall system configuration including an agent device, a scenario creation device, and a server.
In this system, a scenario creation device (computer) 2 (2a, 2b,...) Incorporating a scenario editor, which is a scenario creation program, and a server 3 (A, B,. ) And an example of the configuration of the agent device 1.
The scenario creation device 2 creates scenario data according to a standard specified in accordance with a scenario creation program by an operation of a scenario data creator who is a user or a third party.

The scenario creator creates scenario data in a predetermined format with the scenario creation device 2a using, for example, a scenario editor, and separates the scenario main body and the acquired scenario management data or publishes them as a unit on the homepage (server 3A) and downloadable from the user who has the agent device 1. In the agent device 1, when the scenario body and the acquisition scenario management data are separated, the acquisition scenario management data is downloaded in a lump and stored in the information storage device. Is downloaded and temporarily stored when it is executed.
The server uploaded from the scenario creation device 2 is not limited to the server 3A, and may be any server 3A, 3B,... On the Internet, such as a provider contracted by the scenario creator. Further, another scenario creator creates the scenario with the scenario creation device 2b, posts it on the homepage, uploads it to the server B, and makes it downloadable from the user who has the agent device 1.
In this way, various scenario creators upload their created scenarios to various servers.
The user of the agent device 1 uses the browser of the agent device 1 to browse the scenario he / she wants from the server 3 group (A, B,...), Downloads the scenario he / she likes, By incorporating it into the device, the downloaded scenario data can be operated on the agent device 1.

Further, the user of the agent device 1 browses and downloads the scenario he / she wants from the server 3 (A, B,...) Using the browser of the scenario creation device 2a he has. May be.
In this case, the downloaded scenario data is stored in a semiconductor storage device or other storage medium such as a DVD-ROM or IC card and transferred to the agent device 1. The agent device 1 that has received the scenario data reads the scenario data from the storage medium by the storage medium driving device and incorporates it, so that the downloaded scenario data can be operated on the agent device 1.

First, the configuration and operation of the agent device 1 in which an agent autonomously starts according to a scenario created by a developer or user will be described.
FIG. 1 is a block diagram showing the configuration of the agent device 1 in this embodiment.
The agent device according to the present embodiment is mounted on a vehicle and has a function of communicating with a user in the vehicle and an agent function such as a vehicle control function of performing predetermined processing on the vehicle, as well as a travel route to the user. It also has a navigation function that guides users.

  In the agent device of this embodiment, the central processing unit (1), the display device (2), the voice output device (3), the voice input device (4), the input device (5) for realizing the agent function and the navigation function. ), Various status detection devices (6), various in-vehicle devices (7), a communication control device (8), a communication device (9), and an information storage device (10).

  The central processing unit (1) includes a CPU (1-1) that executes various arithmetic processes, a flash memory (1-2) that reads and stores a program from the information storage device (10), and a flash memory (1-2) ROM (1-3) that stores the program (program reading means) that performs the program check and update processing of the RAM, and RAM (1-4) that temporarily stores the data being processed as the working memory by the CPU (1-1) ), Clock (1-5), image memory (1-7) that stores image data used for screen display on display device (2), based on display output control signal from CPU (1-1) Image processor (1-6) that extracts image data from image memory (1-7), performs image processing and outputs it to display device (2), and converts audio output control signals from CPU (1-1) to analog signals Conversion and output to the audio output device (3) and conversion of the analog signal input from the audio input device (4) into a digital audio input signal To receive information from the audio processor (1-8), the input device I / F unit (1-9) that receives input from the input device (5), and detectors for detecting various situations Various input I / F units (1-10), communication I / F units (1-11) for exchanging information with other devices, information storage media such as CD-ROMs, IC cards, and hard disks (10-2) ) Includes an information storage device I / F unit (1-12) for reading information such as data and programs from / to the information storage device (10) for writing information.

This central processing unit (1) is a route search process, a display guidance process necessary for route guidance, and other processes necessary for the entire system, such as browsing the Internet and downloading scenarios using mail, in this embodiment. Agent processing (various communication between the agent and the driver, operation substitution, situation determination and autonomous processing according to the result) is performed.
The program (program reading means) for performing the update process may be stored in the flash memory (1-2) in addition to the ROM (1-3).
All the programs executed by the CPU (1-1) including the program in the present embodiment may be stored in a CD-ROM or the like as the information storage medium (10-2), or a part of the programs Alternatively, all may be stored in the ROM (1-3) or the flash memory (1-2) on the main body side.
Data and programs stored in the information storage medium (10-2) are input as external signals to the central processing unit (1) and processed to realize various agent functions and navigation functions. It has become.
Further, the central processing unit (1) of the present embodiment forms a screen element transition body execution means for executing a screen element transition body (scenario) when it is determined that the start condition (autonomous start condition) is satisfied. is doing.

The display device (2) displays the route map for road guidance and various image information by the processing of the central processing unit (1), and the screen element transition composed of various character actions (video) and screen configuration parts The body (scenario) is displayed.
For the display device (2), various display devices such as a liquid crystal display device and a CRT are used.
The display device (2) may have a function as an input device (5) such as a touch panel.

The voice output device (3) is a guidance voice when performing route guidance by voice by the processing of the central processing unit (1), a conversation for normal communication with the driver by the agent, and a question for obtaining driver information. Voice and sound are output.
The voice output device (3) is capable of voice input to the user when voice recognition is started in voice recognition processing (when input data acquisition is started by the voice input device (4)). Is output (starting sound output means). In the present embodiment, a sound such as “beep” is output as the start sound, but a buzzer sound or a chime sound may be output.
The audio output device (3) is composed of a plurality of speakers arranged in the vehicle. These may also be used as audio speakers.

In the voice input device (4), a dedicated microphone having directivity is used to accurately collect the voice of the driver. A voice recognition process is executed by the CPU (1-1) using a digital voice input signal obtained by converting an analog signal inputted from the voice input device (4).
Examples of voices that are subject to voice recognition include input voices such as destinations in navigation processing, driver conversations with agents (including responses by drivers), and the voice input device uses these voices. Functions as voice input means for inputting.
As to whether or not a scene requires voice recognition, a voice recognition instruction is set in each scene data. In addition, a dictionary for recognizing a voice that is a target of voice recognition is specified in the scene data of a scene for which a voice recognition instruction is set. This voice recognition instruction is set to any one of “automatically start”, “not automatically start”, and “judgment by agent device (on-vehicle device)”. When the voice recognition instruction is “the agent device determines”, the agent device determines that the road condition (curve, intersection, straight line, etc.) while driving the driver's load, or the driving operation condition (during rapid acceleration, sudden braking) When the load is high, voice recognition is not started. When the load is low, voice input is enabled after the start sound is output.

The voice output device (3) and the voice input device (4) may form a hands-free unit so that a call can be performed using the communication control device (8) and the communication device (9).
In addition, by combining the voice input device (4), the voice processor (1-8), and voice recognition processing, the conversation detection means for detecting whether the driver is talking with the passenger or the voice emitted by the driver. It may be used as a situation detection means for detecting the situation of the driver.

The input device (5) is used to input a phone number or coordinates on a map when setting a destination, or to request (request) a route search or route guidance to the destination. . The input device (5) is used as a trigger when the driver inputs driver information or when the use of the agent function is started. Further, the input device (5) functions as one response means for the driver to respond to an inquiry from the agent in communication with the agent by the agent function.
As the input device (5), various devices such as a touch panel (functioning as a switch), a keyboard, a mouse, a light pen, and a joystick can be used.
Moreover, you may provide the receiving part which receives the remote control using infrared rays etc., and the various signals transmitted from a remote control.
In addition to a joystick for moving the cursor displayed on the screen, the remote control is provided with various keys such as a menu designation key (button) and a numeric keypad.
Further, voice recognition using the voice input device (4) may be used instead of the input device.

The central processing unit (1) uses the contents received from the input device (5) via the input device I / F unit (1-9) to determine whether the CPU (1-1) is performing an input operation by the driver. Or / and a function (device operation status detection means) for detecting the operation status of various devices by using the voice recognition result together.
Various status detection devices (6) are not particularly shown, but as device operation status detection means, current position detection devices for detecting the absolute position of the vehicle (by latitude and longitude), traffic for detecting road congestion, etc. Situation information receiving device, brake detector, side brake (parking brake) detector, accelerator opening detector, A / T shift position detector, wiper detector, direction indicator to detect the situation such as driving operation Detectors, hazard detectors, ignition detectors, vehicle speed detectors that detect vehicle speed, light detectors that detect the operating status of lamps such as headlamps and room lamps, and detection of driver's seat belt attachment / detachment operations It has a seat belt detector and various other detectors.
Current position detection devices include, for example, a GPS (Global Positioning System) receiver that measures the position of a vehicle using an artificial satellite, a data transmitter / receiver that receives a GPS correction signal, an orientation sensor, a steering angle sensor, a distance sensor, etc. Is used.
As the traffic information receiving device, for example, a beacon receiving device that receives information from beacons arranged on the road, a device that receives information using FM broadcast radio waves, and the like are used.

In addition, a communication control device (8) can be connected to the communication device I / F unit (1-11). The communication control device (8) is connected to a communication device (9) (such as a mobile phone made up of various wireless communication devices).
In addition to telephone calls using these, communication with an information providing station that provides karaoke data used for communication karaoke in a car can be performed.
In addition to the information providing station that provides karaoke data, communication with the information base station that provides traffic information and communication with the information providing station that provides scenario data used for agent processing are communicated with the communication device (9). It is also possible to carry out via the device (8).

In the present embodiment, the central processing unit (1) is attached or described with an e-mail to which a scenario is attached via the communication control unit (8), a URL indicating a scenario storage destination, and an autonomous activation condition for the scenario. You can receive e-mail.
In addition, the central processing unit (1) can incorporate browser software that displays homepages on the Internet and can be processed by the CPU (1-1). Scenarios can be accessed from the homepage via the communication control unit (8). You can download the data including.
Further, the central processing unit (1) can download a scenario satisfying the autonomous activation condition from the server 3 by specifying a URL where the scenario is stored.
The communication control device (8) may be integrated with the communication device (9).
In addition, the central processing unit (1) receives in-vehicle communication through the communication I / F unit (1-11) to receive operation statuses of other in-vehicle devices (7), and performs various controls on the in-vehicle devices. It has come to be.
For example, the central processing unit (1) receives information on whether or not the driver is operating various switches of the air conditioner from the air conditioner that is the various in-vehicle devices (7), and increases or decreases the set temperature. The air conditioner is controlled as described above. Also, it receives information from the audio device whether the driver is operating an audio device such as a radio, CD player, cassette player, etc., and whether audio is being output by the audio device, and increases or decreases the output volume. For example, the audio device is controlled.

The information storage device (10) includes an information storage medium driving unit (10-1) and its information storage medium (10-2). The information storage device (10) controls the information storage medium driving unit through the information storage device I / F unit (1-12) in response to an instruction from the CPU (1-1), and the information storage device (10-2) Data and programs are read, and data and programs are written to the information storage medium (10-2).
As the information storage medium (10-2), for example, various storage media such as a flexible disk, a hard disk, a CD-ROM, a DVD-ROM, an optical disk, a magnetic tape, an IC card, an optical card, and the like are used. Each information storage medium driving device (10-1) is used.
A plurality of information storage devices (10) may be possessed in the system. For example, collected personal information such as driver information data (10-2-3-6), learning item data and response data (10-2-3-7) can be easily carried with an IC card or flexible disk. It is possible to configure a DVD-ROM with other data. In this way, when driving other vehicles, it is possible to read and use the data from the IC card that stores them, and to communicate with agents who have learned the situation that they have responded to in the past Become. That is, it is possible to make an agent having learning content unique to each driver appear in the vehicle instead of the agent for each vehicle.

  CPU (1-1) is a program (10-2-1) that implements various agent functions and navigation functions, as well as agent data (10-2-3) and navigation data (10-2-2) used for arithmetic processing. Is stored (installed) in another information storage device (for example, a hard disk device) from the DVD-ROM or IC card shown in the above configuration example, and necessary programs are stored in the flash memory (1-2). The data may be read (loaded) and executed, or data necessary for the arithmetic processing may be read (loaded) from the storage device into the RAM (1-4) and executed.

Next, the configuration of software to be executed will be described.
FIG. 3 shows the relationship between the agent processing unit (101) realized by the CPU (1-1) executing the program and the overall processing unit (102).
In this embodiment, an agent function navigation device is realized by adding an agent processing unit (101) for realizing an agent function to an overall processing unit (102) for realizing various navigation functions.
The agent processing unit (101) and the overall processing unit (102) each have an I / F unit for exchanging processing data with each other, and can acquire each other's processing data.
For example, if the agent processing unit (101) acquires destination data that the driver wants to set as a result of downloading scenario data or performing communication with the driver according to the scenario data, the agent processing unit (101) 102).
The overall processing unit (102) searches for a route based on the acquired destination data and performs route guidance based on the generated travel route data. In this route guidance process, when guidance such as a route change direction by image or voice is provided, the data required for guidance is supplied from the overall processing unit (102) to the agent processing unit (101) to guide the traveling route It is also possible for the agent to guide according to the scenario data converted into data.
The agent processing unit (101) will be described later.

Although not shown, the overall processing unit (102) includes a map drawing unit, a route search unit, a route guide unit, a current position calculation unit, a destination setting operation control unit, etc., and an application unit that performs navigation signal output processing, and a map display And a display output control necessary for route guidance and an OS unit such as a program for performing voice output control necessary for voice guidance.
The overall processing unit (102) also includes a speech recognition processing unit that performs speech recognition and a processing unit that converts text data into speech data. When the browser function or the mail function is added, the processing unit is added to the overall processing unit (102).
Alternatively, the agent processing unit (101) may have a browser function or a mail function.
In this embodiment, an extended function for executing agent processing is added to the overall processing unit (102). This extended function includes, for example, means for detecting the type of road (highway, national road, etc.) that is running from the road data in the navigation data and the current position, and the curve status of the road that is running (before the curve, There are means for detecting the end of the curve.

Next, the configuration of the agent processing unit will be described.
FIG. 4 shows the configuration of the agent processing unit (101).
The agent processing unit (101) includes a scenario driving unit (101-1), an autonomous activation determination unit (101-2), a learning unit (101-3), a character psychology unit (101-4), a drawing / A voice output unit (101-5), a voice recognition unit (101-7), an agent OS unit (101-8), and an external I / F unit (101-9) are provided.

The scenario driver (101-1) reads the scenario data (10-2-3-4) and instructs each processing unit using message communication based on the scenario data (functions provided by each processing unit). use. The scenario driving unit (101-1) performs central processing of the agent processing unit, such as managing scenario execution and providing various agent functions to the driver.
When the scenario data to be executed is stored in the information storage device (10), the scenario driving unit (101-1) reads out and executes it. On the other hand, when the scenario to be executed is stored in the server 3, the scenario driving unit (101-1) specifies and downloads the URL where the scenario is stored and executes it. The scenario downloaded from the server 3 is stored on the RAM (1-4) secured as a work memory, and is deleted after the execution is completed.

The autonomous activation determination unit (101-2) holds the autonomous activation condition data of each scenario in the scenario data (10-2-3-4), and the periodic activation issued by the agent OS unit (101-8) Various conditions such as time, position, and state are compared with various situations in accordance with an activation determination instruction, and determination is performed.
When the conditions are matched, the autonomous activation determining unit (101-2) issues an instruction to execute the scenario having the matched conditions to the scenario driving unit (101-1).
Various situations for comparison with the autonomous activation conditions are obtained from the agent OS unit (101-8) and the learning unit (101-3).
In addition to the periodic autonomous activation determination instruction, if the change in the situation is considered to be large, the autonomous activation determination instruction is issued from the agent OS unit (101-8). ) Performs autonomous activation determination processing. For example, when the driver makes a destination setting, when the driver leaves the driving guidance route using the navigation function, when scenario data is added, or when scenario data is deleted Etc.

The learning unit (101-3) uses the driver information data (10-2-3-6) and learning item data to obtain items (execution results and execution history) obtained through driver selection and response in communication with agents. And response data (10-2-3-7).
The character psychology unit (101-4) obtains the current situation managed by the agent OS unit (101-8), and based on the mental model change condition data, the five parameters that represent the character's psychological state (energetic and friendly) , Autonomous, self-confidence, morals).

The drawing / sound output unit (101-5) creates a control signal for displaying a screen composed of parts such as a selection button and a title in response to an instruction from the scenario driving unit (101-1). In addition, a control signal for displaying various actions (motions) of the character corresponding to the display state by the scene data is also created by an instruction from the scenario drive unit (101-1).
The drawing / voice output unit (101-5) also creates a control signal for outputting a dialogue when the agent communicates with the driver in response to an instruction from the scenario driving unit (101-1). In addition, a control signal for outputting various sound effects in response to an instruction from the scenario driving unit (101-1) is also created.
The voice recognition unit (101-7) issues a control signal for causing the voice recognition processing unit in the overall processing unit (102) to create a voice recognition dictionary in response to an instruction from the scenario driving unit (101-1). The voice recognition unit (101-7) also issues a control signal for starting and stopping the voice recognition process in response to an instruction from the scenario driving unit (101-1).

The agent OS section (101-8) acquires changes in the situation (including addition of scenarios) such as time, place, and various inputs, manages the current situation, and sends a message to the situation change as necessary. Notify each processing unit by communication. The change in the situation is supplied from the overall processing unit (102) through the external I / F unit (101-9) or obtained through an inquiry.
The agent OS unit (101-8) periodically issues an autonomous activation determination instruction to the autonomous activation determination unit (101-2). This periodic autonomous activation determination instruction is issued every predetermined time. The predetermined time may be as short as possible within a range in which the autonomous activation determination process periodically processed by the autonomous activation determination instruction issued periodically does not affect other processes of the entire central processing unit (1). Desirably, the interval is set to 5 seconds in this embodiment. The predetermined time may be arbitrarily changed by the user by an operation from the input device (5).
The agent OS unit (101-8) also issues an autonomous activation determination instruction to the autonomous activation determination unit (101-2) even when it is determined that the change in the situation is large. Cases where the change in the situation is considered to be large include, for example, when the driver has set a destination, the vehicle has been removed from the guide route, scenario data has been added, scenario data has been deleted, etc. Yes, relevant items are defined in advance and stored in RAM (1-4).

  The external I / F unit (101-9) is an interface between the agent processing unit (101) and the overall processing unit (102) (the overall processing unit (102) has an agent I / F as a receiver). Part exists). Acquisition of various types of information such as navigation information used in agent processing, and transmission of control signals from the agent processing unit to the entire processing unit control navigation.

Next, a data structure (including a program) will be described. In the present embodiment, these are stored in the information storage medium (10-2).
FIG. 5 conceptually shows information collected in the information storage medium (10-2).
The information storage medium (10-2) includes a program (10-2-1) for realizing various agent functions and navigation functions according to the present embodiment, and agent data (10-2-3) and navigation as necessary various data. Data (10-2-2) is stored.

  The navigation data (10-2-2) is composed of various data necessary for map drawing, route search, route guidance, destination setting operation, and the like. Examples include map data required for route guidance (road map, house map, building shape map, etc.), intersection data, node data, road data, photo data, registration point data, destination point data, guide road data, details The destination data, destination reading data, telephone number data, address data, and other data files are stored, and all data necessary for the navigation device is stored. Moreover, communication area data etc. are also memorize | stored as needed.

The drawn map data is drawn map data drawn on the display device (2), and this drawn map data is hierarchized.
The intersection data includes an intersection number for identifying each intersection, an intersection name, intersection coordinates (latitude and longitude), a road number at which the intersection is a starting point or an ending point, and presence / absence of a signal.
The node data is composed of information such as latitude and longitude specifying the coordinates of each point on each road. That is, this data is data relating to a single point on the road. A node connecting nodes is called an arc, and a road is represented by connecting each of a plurality of node rows with an arc.
Road data includes road numbers that identify each road, intersection numbers that are the start and end points, road numbers that have the same start and end points, road thickness, prohibition information such as entry prohibition, photo numbers of photo data that will be described later, etc. It consists of
The communication area data is displayed on the display device (2) where the mobile phone, which is a communication device (9) connected to the communication control device (8) or used in the vehicle without connection, can communicate from within the vehicle, There is communication area data for each type of mobile phone in order to use the area where communication is possible when searching for a route.

Agent data (10-2-3) includes mental model data (10-2-3-1), scenario data (10-2-3-4), character data (10-2-3-5), Driver information data (10-2-3-6), learning item data and response data (10-2-3-7). In addition, there are also recommended suggestion data, knowledge data, etc. for making recommended restaurant proposals in the agent data (10-2-3).
The mental model data (10-2-3-1) is composed of five parameters (friendship level, obedience level, confidence level, morality, spirit level) representing the character's psychological state and mental model change condition data. .

The learning item data and the response data (10-2-3-7) are data for storing the results learned by the agent by the driver's selection and response in communication with the agent.
Therefore, the learning item data and the response data (10-2-3-7) are stored / updated (learned) for each driver. For example, as the usage status of the scenario, the previous selection result, the date and time of last use, the total number of times of use, and the like are stored.
According to this learning content, for example, in a scenario where greetings are made every time the navigation power is turned on, if you are within 5 minutes from the previous use, respond `` I met you just before '' or conversely for more than a month When it is open, it responds with “Long time no see”.
It also stores the answer (including the answer of no answer) as a result of asking which team the fan is. Depending on the result of this response, it is possible to change the response such as inquiring which team the fan is in again if there is no answer, or if a specific team is stored, having a conversation about that team.

In scenario data (10-2-3-4), the scenario and its activation conditions are stored together, and the scenario activation condition and the URL where the scenario is stored are associated and stored There is. In the latter case, the scenario is stored in the server 3 specified by the URL.
The scenario data (10-2-3-4) is stored in association with the scenario activation condition and the URL where the scenario is stored, so that the activation condition and the storage destination outside the vehicle for the screen element transition body data are stored. An activation condition storage unit is configured to store the designation information in association with each other.

FIG. 6 shows the configuration of scenario data executed by the in-vehicle device, and the configuration of management data of a recorded scenario including start conditions and URLs.
The scenario data (10-2-3-4) consists of multiple scenarios. It consists of management data for the acquisition scenarios to manage them and data (scenario itself) that shows the contents of each scenario. Has been.
In the acquisition scenario management data, whether this scenario data is stored together with the acquisition scenario management data and the scenario main body, or whether only the acquisition scenario management data is stored separately from the main body data. Information to be recorded is recorded. The fact that the management data of the acquisition scenario is stored separately is indicated by the fact that the URL (storage destination designation information) of the server 3 storing the main body data is stored in association with the autonomous activation condition.

The acquisition scenario management data includes information such as the expiration date of the scenario data, date of creation, creator, etc., and data for overall management of each scenario recorded in the scenario data (scenario Number, scenario name, priority (priority)), autonomous activation condition data of the scenario recorded in the scenario file, and the driver using the input device (5) etc. in the scenario recorded in the scenario file The scenario list data that can be started manually is written.
In this embodiment, the management data part of this acquisition scenario is separated from the entire scenario data (FIG. 6 (a)), and only this part is placed on the in-vehicle device side, and scenario data 1, scenario data 2,. It becomes the composition to put in.
The scenario data 1, scenario data 2,... Placed on the server 3 may take a form in which the scenario main body and the management data are separated from each other, or may take a combined form. When taking the combined form, on the server 3, management data indicating where each scenario data is located is arranged at the head of the scenario data.

As shown in FIG. 6B, the data indicating the contents of each scenario includes management data for managing each scenario and scene data indicating the contents of the individual scenes constituting the scenario. Yes.
In the data for managing each scenario, information on the scenario, text information for creating a speech recognition dictionary used in this scenario, and data for managing the entire scene data constituting the scenario are recorded. Has been.

The agent device determines whether or not to perform the scenario processing based on the determination data set in the scenario management data and the setting on the agent device side (automatic determination, use, not use). .
The scene data includes data for managing a scene, screen configuration data, character action data, various processing data, and development management data.
In the data for managing a scene, information on the scene and data for managing each data section belonging to the scene data are described.
In the screen configuration data, data (size, display position, etc.) of each part of the screen configuration displayed on the display device (2) in this scene is described.
The character action data includes instruction data for actions performed by the character in this scene, and instruction data related to the content to be spoken. In the instruction data of the action, the instruction data is written in one of two types: scenario data that is directly instructed by means of expressing each character, and that that is instructed in a state that the character wants to express.

Various processing data includes information for controlling (processing) external devices in this scene, information for controlling navigation, instructions for executing other scenarios, timer setting information, and mental models that indicate character psychology. Information for changing the parameters is described.
The development management data describes information such as whether to end the scenario, what is the next scene, or nothing to be developed when an event occurs in this scene.

FIG. 7 conceptually shows the structure of the autonomous activation condition data stored in the management data of the acquisition scenario.
As shown in FIG. 7, the autonomous activation conditions are grouped by year, date (month / day), and position as predetermined individual conditions.
In the present embodiment, the conditions relating to the year are grouped as the highest group as the highest grouping.
As shown in Fig. 7 (a), as a group related to the year, autonomous activation conditions limited to each year (executed only in that year) and no conditions related to the year (executable regardless of year) autonomous activation They are grouped (classified) into conditions.

And, as shown in Fig. 7 (b), as the second-ranked group in each group according to the conditions related to this year, it was limited to each date as a group related to date (month and day) (only on that date) It is grouped (classified) into autonomous activation conditions (executed) and autonomous activation conditions that have no date-related conditions (can be executed regardless of date). In the group by date, as in the year, the autonomous activation conditions that do not have a date-related condition are also grouped without a date condition. And if there is no year condition and there is a date, it is grouped to the corresponding date in the group without year condition, and the autonomous start condition without all the conditions of year, month and day is Grouped without date condition.
In the group without date condition, there is a group that is not a direct date specification such as an chronology or anniversary. Although this is a date-related condition, it may be an anniversary date registered by the driver, so the agent device is registered to make a condition judgment regardless of the date in the same manner as when there is no condition.

In addition, among the groups based on the date conditions within these year conditions, grouping is further performed regarding the positions.
That is, among the groups related to the date, as the third-ranked group, as shown in FIG. 7 (c), as the group related to the position (primary mesh), the autonomous activation condition without the position related condition (regardless of the position) Group where there is no point condition that can be executed anywhere) and autonomous activation conditions limited to each primary mesh (executed only within that mesh).

Then, among the groups of primary meshes related to positions, those having conditions regarding positions (conditions belonging to some primary meshes are further divided into groups of secondary meshes divided into areas.
That is, among the primary mesh groups, as the lowest (fourth) group, as shown in FIG. 7 (d), each secondary mesh is assigned to a position (secondary mesh) group. They are grouped into limited autonomous activation conditions (executed only within the mesh).
Autonomous activation conditions that do not have a position-related condition are not grouped more than those without the primary mesh point condition, so they are one group even in the fourth-ranked group.
The automatic start conditions grouped in this way are stored in scenario data in a format (NAV format) handled by the in-vehicle device, with an index (identification code) attached so that the auto start determination unit (101-2) can quickly obtain it. ing.
That is, an index (identification code) indicating a corresponding group is attached to each automatic activation condition.

FIG. 8 shows the normalization of the position coordinates by the primary mesh and the secondary mesh.
Here, as an example, we will explain how the position of coordinates X = (35 degrees 40 minutes 8.91 seconds north, 139 degrees 43 minutes 36.48 seconds east) is expressed on coordinates normalized by a secondary mesh .
First, a primary mesh code is calculated by determining which mesh among the primary meshes shown in FIG.
Now, the point of coordinates X at 35 degrees 40 minutes 8.91 seconds north latitude and 139 degrees 43 minutes 36.48 seconds east longitude is included in the primary mesh where the lower left point is (latitude, light) = (35 degrees 20 minutes, 139 degrees) Is required.
The latitudinal primary mesh code is the lower left value multiplied by 3/2. Therefore, the primary mesh code in the latitude direction = 35 degrees 20 minutes x (3/2) = (35 + 1/3) x (3/2) = 53
Also, the primary mesh code in the longitude direction is obtained by subtracting 100 from the lower left value.
Accordingly, the primary mesh code in the longitude direction = 139-100 = 39 From this latitude direction and the primary mesh code in the longitude direction, the primary mesh code of the coordinate X is 5339.

Subsequently, a secondary mesh code is calculated. As shown in FIG. 8 (b), each primary mesh code is divided into 64 secondary meshes in the latitudinal direction 8 and the longitude direction 8, and 0 to 7 from the smallest value of both latitude and longitude. The value of is allocated.
Therefore, since the point at position X is included in the secondary mesh of the latitude direction: 4 and the longitude direction: 5, the code of the secondary mesh is 45.
From the above calculation, the position of the coordinate X = (35 degrees 40 minutes 8.91 seconds north, 139 degrees 43 minutes 36.48 seconds east) is 5339-45, combining the primary mesh code and the secondary mesh code.

In FIG. 5, the character data (10-2-3-5) stores data of a plurality of characters, and can be selected from the input device (5) or the like according to the driver's preference. Yes.
The character data (10-2-3-5) includes character image data 102351, character voice data 102352, and character image selection data 102353 for each character A, B,.
The character image data 102351 stores a still image representing the state of the character displayed in each scene specified by the scenario, a moving image (animation) representing the motion, and the like. For example, a moving image in which the character bows, a moving image that nods, a moving image that raises the right hand, and the like are stored.
In the scenario body of scenario data (10-2-3-4), the contents of each scene are defined by a common display state that does not depend on the character type.

The driver information data (10-2-3-6) in FIG. 5 is information about the driver, and is used to make the agent's communication more suitable for the driver's wishes, hobbies and preferences. .
Driver information data (10-2-3-6) contains the driver ID (identification information), name, age, gender, marriage (married or unmarried), child, for storing information for each driver. The driver basic data including the presence / absence, the number of persons, and the age, and hobby preference data such as sports and food and drink are stored.
In this embodiment, the priority order is determined for each of the driver information, and the agent asks the driver questions in descending order of priority among the driver information not yet stored. The driver basic data has a higher priority than the hobby preference data.
Driver information data (10-2-3-6) is created for each driver when there are a plurality of drivers who drive the vehicle. Then, the corresponding driver information is used by specifying the driver.

FIG. 9 shows the transition of the scene screen according to the guidance scenario transmitted from the inn to the prospective guest for each scene.
This guidance scenario is composed of scene screens (a) to (f) among a plurality of scene screens.
The next scene screen is branched into 4 and 6 depending on the user's selection result for the scene screen (c). Although not branched in the example of FIG. 9, the scene screen may be branched so that dishes corresponding to the selected dish type are displayed on the scene display screen 54 in the scene screen (d).

First, the configuration of the scene screen displayed on the display device (2) based on the scenario scene data will be described.
As shown in the scene screen (a), an agent display screen 51 on which an agent image (still image, moving image) is displayed, a balloon screen 52 on which characters corresponding to the voice of the agent are displayed, a title screen 53, and It consists of a scene display screen 54 that displays image data unique to each scene (images of actual image data, answer selection buttons, etc.).
The agent displayed on the agent display screen 51 is a character selected by the user or a default character.

Hereinafter, each action of the agent according to the reservation scenario will be described with reference to FIG.
The agent operations and screen displays described below corresponding to each scene screen are displayed according to data, images, and instructions stored in the scenario data of the external scenario. Further, although described as an agent operation, the scenario driving unit (101-1) of the agent processing unit (101) actually performs the processing.
In the scenario start process described later, when the scenario driving unit (101-1) of the agent processing unit (101) starts the guidance scenario, it first reads the screen configuration data of the scene number 1 specified by the scene header from the scenario data. Display on the display device (2). In this scene, the agent of the character managed by the agent OS section (101-8) appears on the agent display screen 51, bows and greets with voice. The content of the voice greeting is the same as the text displayed on the balloon screen 52.
The greeting by voice is performed on behalf of the inn by the agent, but it is expressed that the inn is a greeting from the inn by displaying a photo image of the landlady of the inn on the scene display screen 54. The image of the landlady is an image received and added as part of the external scenario, and is stored as actual image data of the scenario data (10-2-3-4).
The instruction for the action of the agent follows the instruction stored in the character action instruction data.
When the greeting by the agent ends, the screen transitions to the next scene 2.

In the next scene 2, an open-air bath image is displayed on the scene display screen 54. Then, the agent points to this open-air bath picture, and the agent explains the specialty of the inn (that it is for sale) by voice and display of the balloon screen 52.
When the agent's story ends, the scene transitions to the next scene 3, and an image of today's meal (an image of kaiseki cuisine) is displayed on the scene display screen 54. Question.

It is assumed that the scene data of scene 3 defines a timer setting time and a timer setting condition “set only during running”. In this case, counting by a timer is started at the start of the scene on condition that the vehicle is running. The vehicle speed sensor (6-11) or the distance sensor (6-1-5) determines whether the vehicle is running or not when the vehicle speed v = 0 is detected, and the vehicle speed v ≠ 0 is detected. It is determined that the vehicle is traveling.
If the user selects “Yes” as an answer to the question as to whether or not the displayed dish is acceptable, the process branches to Scene 4, and if “No” is selected, the process branches to Scene 6.

On the other hand, if the user gives a timer notification (elapsed set time) without answering by voice or answering by selecting the selection button displayed on the screen within the timer setting time, it is specified by the scene 3 scene data The scenario is terminated according to the transition condition at the time of timer notification.
In this way, even when there is no answer from the user, it is determined that no answer has been selected, and the process shifts to the next scene (end in the example of FIG. 9) using no answer as a transition condition. It is possible to make the communication with the character converted closer to the communication between humans.

In scene 4, a selectable list other than kaiseki cuisine is displayed on the scene display screen 54. The agent points to the list on the scene display screen 54 and asks which dishes are good.
Then, when the user selects any one, the screen transitions to the scene 5.
In scene 5, a list of the number of people to be changed from kaiseki cuisine is displayed on the scene display screen 54, and the agent points to this list and asks the number of people.
When the user selects any one, the screen transitions to scene 6.

In scene 6, an external appearance photo image of the inn is displayed on the scene display screen 54, and the agent bows and greets.
Then, as a result of the user's selection, the agent is connected to the communication control device (8) from the communication device I / F unit (1-11) to the answer result regarding the meal in the case of the guidance scenario of FIG. The external scenario being executed is transmitted to the third party (inn) that has been transmitted via the communication device (9).

In this way, when the user wants to obtain information about the user, the creator of the external scenario creates a scenario in which a scene of a question from which the desired information can be obtained is provided in the scenario and the response is sent by e-mail. To do. If it is necessary to send an answer, the e-mail address of the creator is included in the scenario data.
When the agent's story in the last scene (scene 6 in FIG. 9) ends, the scenario ends.
In this way, the scenario driving unit (101-1) sequentially displays and outputs each scene image and sound specified in the scenario up to the last scene.
When the activated scenario ends, the scenario driving unit (101-1) determines whether there is an activation request for executing another scenario.

Next, a description will be given of a process for determining whether or not to autonomously start various scenarios executed by the scenario driving unit (101-1).
FIG. 10 shows the autonomous activation determination process of the scenario by the autonomous activation determination unit (101-2).
In this autonomous activation determination process, the autonomous activation determination unit (101-2) receives information on the position and date in order to reduce the load on the device, and creates a block of activation conditions that approximate the received position and date as a scenario. A process of reading (extracting means) from the external storage device (10) holding the data and temporarily storing it in the work memory (RAM (1-4)) is performed.

That is, the autonomous activation determination unit (101-2) obtains the current status information from the agent OS unit (101-8) via the agent I / F, and acquires the current status, time, and other status information. Is acquired (step 11).
Then, the autonomous activation determination unit (101-2) determines whether or not the acquired status information such as position and time has a predetermined unit change (step 12).

As a result of the determination, when it is determined that there is a change of a predetermined unit (Step 12; Yes), the autonomous activation determination unit (101-2) determines the autonomous activation condition having conditions that approximate conditions such as the position and time. The group is read from the external storage device (10) and temporarily stored in the work memory (RAM (1-4)) (step 13).
Here, the approximate condition is, in the case of a position, the entire range of the map data is divided into rectangular blocks of a predetermined unit, and the block including the position where the vehicle exists and the eight blocks adjacent to the block are included. A condition that includes location information. In the case of a date, the current day and the next day are applicable. The change in the predetermined unit corresponds to a case where the vehicle moves to another block in the case of a position, and a case where the date changes in the case of a date.

Then, the autonomous activation determination unit (101-2) performs a condition determination process on whether or not the situation information is satisfied for the read autonomous activation condition group (step 14).
If it is determined in step 12 that there is no change in the predetermined unit (step 12; No), it is not necessary to change the autonomous activation condition group temporarily stored in the work memory, so the process proceeds to step 14 .

FIG. 11 shows the processing contents of the condition determination processing (step 14) in FIG.
The autonomous activation determination unit (101-2) acquires the first autonomous activation condition from the autonomous activation condition group temporarily stored in the work memory (RAM (1-4)) (step 21). It is determined whether or not the situation based on the obtained various situation information satisfies the obtained autonomous activation condition (step 22).
When the autonomous activation condition is satisfied (step 22; Yes), the autonomous activation determining unit (101-2) sends a scenario execution request message corresponding to the autonomous activation condition to the scenario driving unit (101-1). (Step 23).

Next, the autonomous activation determination unit (101-2) determines whether or not the next autonomous activation condition still exists in the autonomous activation condition group temporarily stored in the work memory (RAM (1-4)). (Step 24) If there is (Yes), the next autonomous activation condition is acquired (return to Step 21), and thereafter each processing of Steps 21 to 24 is temporarily stored in the work memory (RAM (1-4)). Repeat until all stored autonomous activation conditions are judged.
In step 24, if the following autonomous activation conditions do not exist (judgment for all autonomous activation conditions temporarily stored in the work memory (RAM (1-4)) is completed) (; No), the autonomous activation determination unit (101-2) ends the autonomous activation determination process.
Thus, the condition determination means for determining whether or not the input from the on-board input device satisfies the activation condition is configured by the Nario autonomous activation determination process of FIG. 10 and the condition determination process of FIG.

Next, scenario execution processing when the scenario drive unit (101-1) receives a scenario execution request from the autonomous activation determination unit (101-2) will be described.
FIG. 12 shows an example of the flow of scenario execution processing.
The flow of scenario execution processing varies depending on the user's operation content and the description content of the scenario data. Therefore, FIG. 12 shows a series of typical operations performed by each unit of the agent processing unit (101) and the entire processing unit (102) when executing a scenario. Each process is performed independently, and the flow of the scenario execution process is changed depending on the contents of the user operation and the description contents of the scenario data. That is, the independent process of each part is continued, and the typical flow shown in FIG. 12 is obtained.

Specifically, each part of the agent processing unit (101) and the entire processing unit (102) perform processing on the message when receiving the message, and wait for the next message when the processing is completed.
When the scenario driving unit (101-1) receives a scenario execution request from the autonomous activation determining unit (101-2), it performs agent start preparation processing by securing and initializing work memory (step 505-1).
Then, the scenario driving unit (101-1) confirms whether the scenario execution request is a manual activation or an automatic activation (step 505-2). Manual activation is when the user selects scenario activation from the menu of the display device (2), and automatic activation is when the autonomous activation condition of the scenario is satisfied.

If the scenario execution request is manual startup, menu scenario request processing is performed (step 505-3). Thereafter, the process proceeds to scenario data acquisition processing (step 505-4).
On the other hand, in the case of automatic activation, there is a scenario that is requested to be executed by satisfying the autonomous activation condition, so that the process directly proceeds to the scenario data acquisition process (step 505-4).

Next, the scenario driver (101-1) acquires the scenario data to be executed in the work memory (secured in the RAM (1-4)) (step 505-4). When acquiring scenario data, if there are multiple scenarios to be executed (when multiple autonomous activation conditions are satisfied, manual activation request and automatic activation overlap, etc.), the scenario driver ( 101-1) reads the scenario data with the highest priority by judging the priority order defined for each scenario.
If the priorities are the same, it is determined that the priorities are higher in the order in which the execution requests are received from the autonomous activation determination unit (101-2). The priority of the scenario exists in the scenario management data of the scenario data (10-2-3-4), and the scenario driver (101-1) acquires it together with the scenario execution request, and confirms it To do.

FIG. 13 is a flowchart showing scenario data acquisition processing in the embodiment.
If there are multiple scenarios to be executed, the scenario data with the highest priority is acquired as described above.
First, the scenario drive unit (101-1) stores the scenario data (scenario body) to be acquired in the server (the autonomous startup condition and the scenario body to be used at the time of execution are separated) on the information storage medium. Judgment is made (automatic activation condition and scenario main body used at the time of execution) (step 505-4-1). In the latter case, the scenario data is read from the information storage medium, Obtained in work memory (step 505-4-2).

In the former case, the scenario driving unit (101-1) outputs a message to the external I / F (101-9) to make a processing request. As a result, the external I / F (101-9) performs network connection processing (step 505-4-3). When the connection processing is completed, the scenario driver (101-1) downloads scenario data from the server ( Read) and stored in the RAM (1-4), which is a work memory (step 505-4-4).
The scenario driver (101-1) downloads (reads) the scenario data from the server and stores it on the RAM (1-4), which is the work memory. If it is determined that the screen element transition body data is stored, the screen element transition body acquisition means for acquiring the screen element transition body data stored in association with the activation condition from the storage destination outside the vehicle designated by the storage destination designation information is configured.
After the scenario data has been downloaded, the overall processing unit performs network disconnection processing (step 505-4-5) according to an instruction from the scenario driving unit. Note that the cutting process may not be performed here, and the cutting may be performed after a predetermined time has elapsed.

If the connection process fails (for example, the mobile phone is outside the service area), the scenario driver (101-1) rejects the scenario requested to be executed (autonomous activation determination unit (101-2)). Notification that it cannot be executed).
In response, the autonomous activation determination unit (101-2) restarts the activation determination of the scenario after a predetermined time (for example, after 1 minute), and if the condition is satisfied again, an execution request is issued, Processing from 505-1 is executed. (Reissue scenario execution request)

When the acquisition of the scenario data is completed, the scenario driving unit (101-1) next performs a scenario start process (FIG. 12: step 505-5).
In the scenario start process, the scenario driver (101-1) first performs an initialization process for starting a scenario.
Also, the scenario driving unit (101-1) determines whether or not to perform standby processing as will be described later in the scenario start processing.

After the scenario start process (step 505-5), the scenario drive unit (101-1) executes a scene process for processing character drawing and sound according to the contents of the scenes constituting the scenario (step 505-6). ).
That is, in the scene processing, the scenario drive unit (101-1) refers to the RAM (1-4) in which the scenario data downloaded in step 505-4-4 is temporarily stored, and displays the screen configuration and character actions. Analyze instructions, etc.
Then, in accordance with the rules for each scene data, the scenario drive unit (101-1) creates voice data and character drawing data to be output and instructs the drawing / voice output unit (101-5) to draw. In accordance with this instruction, the drawing / speech output unit (101-5) develops a scene in which the character bows, points in the right or left direction by hand, or talks to the user.
If the scene data being processed has an instruction for voice recognition, voice recognition processing is performed.

When the scene processing is completed, the scenario driving unit (101-1) checks whether the scenario is finished (step 505-7).
In the case of scenario end, the scenario driver (101-1) performs scenario end processing (step 505-8). In this scenario termination process, the learning unit (101-3) obtains an end ID indicating the termination method and stores it in the response data (10-2-3-7).
If the scenario is not finished (if the scenario still continues), the process returns to step 505-6 to repeat the scene process with the next scene, the next scene,.
After scenario termination processing, the scenario driver (101-1) checks whether there is another scenario execution request (step 505-9). If there is another scenario execution request, the scenario drive unit (101-1) Returning to the data reading process (step 505-4), the same process is executed.
On the other hand, when there is no other scenario to be executed, the scenario driving unit (101-1) executes an agent termination process (step 505-10). That is, the agent OS unit (101-8) is notified that the execution processing of all requested scenarios has been completed.
Thereafter, the screen displayed on the display device (2) returns to the normal navigation screen, but the subsequent processing is transferred to the overall processing unit (102) via the agent I / F.

Next, the configuration and operation of the scenario creation device 2 in which a user or a third party creates an original scenario will be described.
FIG. 14 shows the configuration of the scenario creation device.
The scenario creation device includes a control unit (200), an input device (210), an output device (220), a communication control device (230), a storage device (240), a storage medium drive device (250), Input / output I / F (260). These devices are connected by a bus line such as a data bus or a control bus.

The control unit (200) includes a CPU (200-1), a memory (200-2), and the like, and controls the entire scenario creation device.
The CPU (200-1) is a processor that executes various arithmetic processes.
The memory (200-2) is used as a working memory when the CPU (200-1) executes various arithmetic processes.
The CPU (200-1) can write and erase programs and data in the memory (200-2).
In the memory (200-2) in the present embodiment, an area for the CPU (200-1) to create, edit, and store scenario data according to the scenario editor (scenario editing program) can be secured.

The input device (210) is a device for inputting characters, numbers, and other information to the scenario creation device, and is composed of, for example, a keyboard and a mouse.
The keyboard is an input device for mainly inputting kana and English characters. It is used when inputting the target sentence.
A mouse is a pointing device. When operating a scenario creation device using a GUI (Graphical User Interface), etc., an input device used for inputting predetermined information by clicking a button or icon displayed on the display device It is.

The output device (220) is, for example, a display device or a printing device.
As the display device, for example, a CRT display, a liquid crystal display, a plasma display, or the like is used, and various screens such as a main screen for creating a scenario and a screen for selecting a screen configuration in each scene are displayed. In addition, selected information and input information are displayed on each screen.
As the printing apparatus, for example, various printer apparatuses such as an ink jet printer, a laser printer, a thermal transfer printer, and a dot printer are used.

The communication control device (230) is a device for transmitting and receiving various data and programs to and from the outside, and a modem, a terminal adapter, and other devices are used.
The communication control device (230) is configured to be connectable to, for example, the Internet or a LAN (Local Area Network).
The created scenario data is uploaded to any of the servers 3 (3A, 3B,...) Connected via these networks via the communication control device (230). Scenario data can be uploaded by uploading the management data (autonomous activation conditions, etc.) of the recorded scenario in FIG. 6 (a) and the scenario body (scenario data) in FIG. And upload it.

When uploading the scenario main body and the recorded scenario management data separately, the scenario management data includes an autonomous start condition for starting the scenario main body and a URL (storage destination designation information) indicating the storage destination of the scenario main body. .
In this case, in the agent device 1, only the recorded scenario management data needs to be downloaded while the large-capacity scenario main body is stored in the server, and a large amount of management data can be collected with a small storage capacity. Then, when the autonomous activation condition is satisfied, the URL is specified and the corresponding scenario body is temporarily stored and executed.

Also, the communication control device (230) of the scenario creation device 2 transmits / receives scenario data created with each other to / from other scenario creation devices connected to the network, and sends / receives data necessary for creating scenario data. You can do it. Even when scenario data is transmitted / received between scenario creation devices, there are cases where the scenario body and the management data are transmitted / received together, or only management data (such as the autonomous activation condition and the storage destination URL of the scenario body) is transmitted / received. is there.
The communication control device (230) is controlled by the CPU (200-1), and transmits and receives signals and data to and from these terminal devices and server devices according to a predetermined protocol such as TCP / IP.
The scenario data created by the scenario creation device 2 can be written in a storage medium such as an IC card and taken into the agent device 1.

The storage device (240) includes a readable / writable storage medium and a drive device for reading / writing programs and data from / to the storage medium. A hard disk is mainly used as the storage medium, but other storage media that can be read and written such as a magneto-optical disk, a magnetic disk, and a semiconductor memory can also be used.
The storage device (240) stores a scenario editing program (240-1), scenario editing data (240-2), and other program data (240-3). Other programs include, for example, a communication program that controls the communication control device (230) and maintains communication with the terminal device and server device connected to the scenario creation device and the network, and scenario creation such as memory management and input / output management An OS (Operating System), which is basic software for operating the apparatus, is also stored in the storage device (240).
The storage medium driving device (250) is a driving device for driving a removable storage medium to read / write data. Examples of the removable storage medium include a magneto-optical disk, a magnetic disk, a magnetic tape, IC cards, a paper tape punched with data, and a CD-ROM.

The scenario creation device 2 acquires a scenario from the storage medium storing the scenario data by driving the storage medium by the storage medium drive device (250), or stores the created scenario data from the storage medium drive device. Or it can be stored on a medium.
The input / output I / F (260) is composed of, for example, a serial interface or other standard interface.
By connecting an external device corresponding to the interface to the input / output I / F (260), the function of the scenario creation device can be expanded. Examples of such external devices include a storage device such as a hard disk, a communication control device, a speaker, and a microphone.

Next, the configuration of the scenario editing program (240-1) and scenario editing data (240-2) will be described.
FIG. 15 conceptually shows the configuration of the scenario editing program and data.
The scenario editing program (240-1) includes a scenario editor (240-1-1), a scenario compiler (240-1-2), and a DB editing tool (240-1-3).
Scenario edit data (240-2) is the common definition DB (240-2-1), local definition DB (240-2-2), and SCE scenario data (240-2-3) created with the scenario editor. And real machine format (NAV format) scenario data (240-2-4) converted by the scenario compiler exists.
The scenario editor (240-1-1) is an application program that creates scenario data.
The scenario compiler (240-1-2) converts the scenario data (240-2-3) created in the scenario editor (240-1-1) into scenario data (240-2-3) that can be used on the agent device ( It is an application program that converts to 240-2-4) and functions as a conversion means.

FIG. 16 conceptually shows a state in which the data format of the scenario data is changed by the scenario compiler (240-1-2).
As shown in FIG. 16, the scenario compiler (240-1-2) includes one or more SCE format scenario data (240-2-3), a scenario body in each actual machine format (NAV format), The data is converted into scenario data (240-2-4) consisting of one scenario-recorded acquisition scenario management data corresponding to each scenario main body.
The acquisition scenario management data is composed of data including an autonomous activation condition for each scenario body and a URL of a server storing the scenario body. Although not shown, in detail, an ID is assigned to each scenario body, and the scenario download in the in-vehicle device is performed by associating the autonomous activation condition corresponding to the scenario body ID with the URL of the server. Is possible.
The autonomous activation conditions are managed in units of identification numbers given when the activation conditions are classified by a scenario compiler (240-1-2) described later.

In FIG. 15, a DB editing tool (240-1-3) is an application program for editing / updating data stored in the common definition DB (240-2-1).
The common definition DB (240-2-1) stores definition data when creating scenario data. The common definition DB (240-2-1) stores, in addition to automatic start item data, which will be described later, action items for scene development, additional determination items, a character display state instruction table, and the like. This common definition DB (240-2-1) may exist on a server connected by a local area network (LAN) instead of the storage device of the scenario creation device. By doing so, scenario creation devices connected by a local area network (LAN) can create scenario data using a common common definition DB (240-2-1).
The local definition DB (240-2-2) stores the screen configuration defined by the scenario creator while creating the scenario data.
The SCE format scenario data (240-2-3) is data created by the scenario editor (240-1-1).
Real machine format (NAV format) scenario data (240-2-4) is converted from SCE format scenario data (240-2-3) to data format for use on agent devices by scenario compiler (240-1-2) Data.

FIG. 17 exemplifies items that can be set as automatic start items stored in the common definition DB (240-2-1).
This automatic activation item is a conceptual list of samples of each item type that can be detected, recognized, and confirmed by the agent device.
This automatic start item is described in the common definition DB (240-2-1). When creating a scenario with the scenario editor (240-1-1), it is automatically started to set the autonomous start condition. Items are read from the common definition DB (240-2-1) and displayed in a list (presentation means). The creator selects an automatic activation item from the list display (list display) (selection means).
A window for inputting a numerical value or a window for selecting from a list is displayed depending on the contents described in the type of each selected item, and a condition for determining the automatic activation item is input. Autonomous activation condition data, which is a determination condition for autonomously activating a scenario by repeating this operation one or more times, is created.
In this way, the activation condition setting means is formed by setting the activation condition of the screen element transition body (scenario).

FIG. 17B and FIG. 17C illustrate selectable items that can be selected as an autonomous activation condition for the automatic activation item.
Selectable items are also described in the common definition DB (240-2-1). In the table showing the automatic start items exemplified in FIG. 17A, items that can be selected as a lower concept for the items indicated as selection from the list in the type column are shown as selectable items in FIG. b) Specified in FIG. 17 (c). The group defined in the selectable item and the item of the automatic start item are associated with the No. item on the left side.
A combination of the selected automatic activation item, the selected selectable item, and the input numerical value, time, distance, and the like becomes an autonomous activation condition for each scenario. For example, when the selection by the user is the automatic activation item “acceleration” and the selectable item “rapid deceleration”, the autonomous activation condition is “acceleration-rapid deceleration”.
Note that this sample is just a sample and the definition may be changed.
For example, the vehicle speed input may be selected from a list and selected from items separated every 10 km / h.

The common definition DB (240-2-1) in FIG. 15 further stores transition conditions (development conditions) and branch conditions for expanding from one scene (screen element) to the next scene.
Each item of the development condition is read out when creating the development configuration of each scene, and is displayed in a list in the branch condition designation window. By selecting a development condition item from the list displayed, a scene development configuration is created as illustrated from (a) to (b) and (b) to (c) in FIG. The
In addition, it is possible to select a condition item when judging a condition from each scene and branching to a plurality of scenes from the judgment result. In the example of FIG. 9, a scene that branches from (c) to (d) and (f) is developed.
In this way, by continuing a plurality of branch scenes (in series and in parallel) after the normal scene, it is possible to develop a plurality of normal scenes that branch under various conditions with respect to one normal scene.

In the common definition DB (240-2-1), other settings are made for each scene, including voice recognition data used for voice recognition, data used for character movement instructions (separate line instruction data also exists), and so on. Character image data and character dialogue data for previewing and confirming the designated instructions, a conversion table to the expression method of each character for a unified instruction independent of characters, each part data to be displayed on the display device (2), and those Screen configuration data describing how to arrange the items and items that can be selected as processing contents in the scene, for example, actions that can be processed by the agent, on / off of the audio device, channel selection, air conditioner device Various processing content item data such as on / off, temperature setting, destination setting to be supplied to the overall processing unit (102), and the like are stored.
All these definition data can be changed and added using the DB editing tool (240-1-3) as well as each definition data.
Character image data for previewing and confirming the instruction set in each scene stores image data of various characters stored in the agent device.

Next, each operation of scenario creation by the scenario creation device configured as described above will be described according to the transition of the screen.
FIG. 18 shows the configuration of the main window displayed on the display device when the scenario editor (240-1-1) is activated.
As described below, the screen element transition body data configured by combining the screen elements in which the processing contents executed in synchronization with the display screen of the in-vehicle device are defined is created by various settings from the main window. Screen element transition body creation means is configured.
As shown in FIG. 18, the main window includes a scene screen 301 on which a scene screen being created (a scene screen (see FIG. 9) displayed on the display device (2) of the agent device 1) is displayed. A setting screen 303 for displaying setting items to be set, a scene development screen 305 in which a scene development configuration (branch state) is displayed by a tree structure of scene icons 307 representing each scene, and a processing icon display unit Has been.

When the scenario editor (240-1-1) is activated, a start point 308 is displayed on the scene development screen 305 of the main window. When this start point 308 is selected, scenario properties can be edited. The selection is made by, for example, matching the point position by the mouse cursor to the corresponding location and double-clicking the mouse.
The screen configuration change button 309 is a button for selecting a screen configuration to be displayed, and the sound effect setting button 310 is a button for displaying a screen for setting sound effects for each scene of the scenario.
When the agent display screen 311 is selected, an agent (character) action editing screen is displayed.

The dialogue editing button 313 is a button for editing a dialogue instruction of the character.
When the button part and the background speech recognition dictionary setting 315 are selected, the speech recognition dictionary to be used can be edited. The name of the word to be recognized is displayed on the scene screen when the one displayed with the answer selection button 315a mark on the scene screen 301 is selected, and when the person 315b to be recognized in the background is selected, it is recognized as a voice recognition target. The name of the word to be displayed is not displayed.
The timer setting button 317 is a button for setting and changing timer setting information.
In the control instruction editing 319 for an external device or the like, a control instruction for an external device or the like (including a navigation) is set.

The voice recognition start control instruction 320a sets a voice recognition instruction that defines how to start voice recognition when voice recognition is performed in the scene being created. As an instruction for voice recognition, one of “start automatically”, “do not start automatically”, and “judgment by agent device (on-vehicle device)” can be selected. Yes.
In the callback control instruction 320b, an instruction as to whether or not to perform a callback for confirming the result of voice recognition is set. As a callback instruction, one of “call back”, “do not call back”, or “agent device determines (automatic)” that determines whether the agent device determines the situation and determines whether to call back or not. Can be selected.

The AMM change setting change button 321 is a button for changing each long-term emotional element of the agent in the scene being created.
The scene development display unit 322 displays a development condition item and an additional condition item that are defined for a scene (active state) specified on the scene development screen, and a scene that is continued (connected) when the condition item is satisfied. Is displayed.
On the left side of the scene development display unit 322, as shown in FIG. 18, the development conditions (see Table 2) and the classification of additional conditions (see Table 3) set for the active scene are displayed in a tree structure. . In addition, on the right side of the scene development display portion, the contents of the transition condition and the connection destination (the scene number of the development destination) are displayed.
The processing icon display section includes a scene creation button 323, a branch scene creation button 324, a dummy scene creation button 325, an alias scene designation button 326, an end ID button 327, a link ID button 328, an insert button 329, an up / down replacement button 330, A scene playback button 331, a build button 332, and other processing buttons are displayed.

The scene creation button 323 is used when a new normal scene is created.
Clicking the scene creation button 323 allows you to edit the scenario flow (create the next scene). When the scene creation button 323 is clicked, a normal scene to be developed next to the currently selected scene can be created.
By branching the scenario flow with the scene creation button 323, a development configuration for each normal scene is created. For example, in the scene development configuration displayed on the scene development screen 305 in FIG. The icon of the subsequent scene is displayed on the lower layer side, and normal scenes 7, 8,... Developed after the scene 5 are branched and created by clicking a plurality of times (a plurality of creation operations are performed).

That is, when the scene creation button 323 is clicked with the scene m (normal scene or branch scene) selected, the next normal scene m1 following the scene m is created. When the scene creation button 323 is clicked with the scene m selected again, the next normal scene m2 following the scene m is created in parallel with the normal scene m1. Similarly, when the scene creation button 323 is clicked with the scene m selected again, a normal scene m3 is created.
If you want to further develop the scene that follows the created normal scene m1, click the scene creation button 323 with the normal scene m1 selected, so that the next normal scene m1-1 that follows the normal scene m1 is displayed. Created. When another scene branched from the normal scene m1 is created, the scene m1-2 subsequent to the scene m1 is created by selecting the scene m1 again and clicking the scene creation button 323.

Furthermore, when the scene creation button 323 is clicked in a state where the created normal scene m1-1 is activated, a normal scene m1-1-1 following the normal scene m1-1 is created.
Branch scene creation button 324, which is used to create a new branch scene.
Click the branch scene creation button 324 to edit the scenario flow (create the next branch scene). When the branch scene creation button 324 is clicked, a branch scene to be developed next to the currently selected scene can be created.
By using the branch scene creation button 324, branching is performed under a plurality of additional conditions following the development condition, so that a development configuration for each normal scene can be created by a logical operation (logical sum, logical product) of the transition conditions.

  For example, in the scene development configuration displayed on the scene development screen 305 in FIG. 18, when developing from the normal scene 1 to the normal scene 2, by inserting the branch scene 4 and the branch scene 6 between the two normal scenes, When the state change defined in the normal scene 1 is performed and both the branch condition 4 and the branch condition 6 are satisfied, the normal scene 2 is developed following the normal scene 1. In this way, by using a plurality of branch scenes, it is possible to create scenarios that perform various developments with various condition settings.

In FIG. 18, the branch scene is denoted by reference numeral 333. A branch scene can be created following a normal scene or a branch scene. For example, a branch scene 4 is created by selecting the branch scene creation button 324 with the normal scene 1 on the scene development screen 305 of FIG. 18 activated, and a branch scene creation button with this branch scene activated. Branch scene 6 is created by selecting 324.
The method for creating the branch scene hierarchically is the same as the method for creating the normal scene described above.

The dummy scene creation button 325 is a button for creating a dummy scene.
The dummy scene is composed of management data for managing the scene, various processing data, and development management data, and various processing such as destination setting processing and agent learning result storage processing in the navigation function is defined. The
The alias scene designation button 326 is a button for shifting from an active scene (normal scene, branch scene) to another created scene (normal scene, branch scene).
For example, in the scene development configuration of the scene development screen 305, when the branch scene 6 is activated and the alias scene designation button 326 is selected and then the scene screen 5 to be transferred is selected, the alias indicating that the scene screen 5 is transferred A screen 334 is displayed.
The end position creation button 327 is a button for creating an end ID for specifying the end position of the scenario.

When the end position creation button 327 is clicked, a scenario end position 340 can be created. An end number is assigned as an end ID to the end position 340 of each created scenario.
When the end position 340 of the created scenario is selected, an end property editing screen (see FIG. 40) is displayed, and each short-term emotion element of the agent can be set and changed on this screen.
The link ID button 328 is a button for creating a link ID for linking another scenario to the scene.

The insert button 329 is a button for inserting a normal scene, a branch scene, and a dummy scene before an active scene (normal scene, branch scene) or end mark, respectively. Select a button for each scene type.
The up / down replacement button 330 is a button for changing the vertical position of the scene, and includes a button for moving the active scene up and a button for moving down the active scene.
The scene playback button 331 is a button for playing back an active normal scene.
The build button 332 is a button for compiling the created scenario into an actual machine format (NAV format) for use by the agent device.

  Note that the main window shown in FIG. 18 is an example of a scenario being created, and only the start point 308 is displayed on the scene development screen 305 when the scenario editor (240-1-1) is started. Nothing is displayed on the scene screen 301, and the setting screen 303 is not set (the default value is displayed).

When a branch scene, for example, branch scene 4 in FIG. 18 is selected and activated on the scene development screen 305, an additional condition classification display field and an additional condition item field are displayed in the area of the scene screen 301.
The branch condition classification display field displays the classification of the additional condition item selected for the active branch scene, and the branch condition item field displays the additional condition item for designating the branch destination.

FIG. 19 shows the flow of screen operations for editing scenario properties.
In the main window shown in FIG. 18, when the start point 308 displayed on the scene development screen 305 is double-clicked, the scenario property editing window shown in FIG. 19 is displayed over the main window.
In this scenario property editing window, scenario name input, kana name input, icon selection, genre selection, priority setting, expiration date (upper limit of time lag from start condition to actual start) setting, travel Setting of medium execution condition, setting of scenario start condition (separate window), setting of standby process use condition, creator name input and comment input can be performed. The scenario name input and kana name input entered on this screen are management data in scenario data in the actual machine format.
When the OK button 402 is clicked in the scenario property editing window, the edited content is reflected in the data, and the screen returns to the main window. On the other hand, when the cancel button 403 is clicked, it is not reflected in the data and returns to the main window.
When a standby process use condition setting button 409 is clicked in the scenario property edit window (FIG. 19), a standby process condition screen is displayed, and it is possible to select whether or not to perform standby process.

When the start condition setting button 401 is selected in the scenario property edit window, the main edit window for the scenario start condition (automatic start condition) shown in FIG. 20A is displayed.
The start condition setting means for setting the start condition for starting the screen element transition body data is configured by the setting process in the main edit window of the scenario start condition described below.
The main editing window (FIG. 20 (a)) of the scenario start condition can be set so that the user can start the scenario manually. In this example, the check box 406 is unchecked and set to not start manually.

Conditions for automatically starting a scenario by the system are displayed in the list of automatic start conditions (autonomous start conditions) on the left side of the main editing window (a) for this scenario start condition. In the state of FIG. 20 (a), nothing has been set yet, so this is a blank state.
When the new creation button 405 is clicked in the main editing window (FIG. 20A) of the scenario start condition, an automatic start condition selection window (FIG. 20B) is displayed and a new start condition can be edited.

In the automatic start condition selection window (FIG. 20 (b)), the judgment condition item (category) to be set is selected, and when the decision is clicked, the process proceeds to the condition range selection window (FIG. 20 (c)) to be automatically started. In the example of FIG. 20B, since it is desired to automatically start (autonomous activation) a scenario while traveling on a highway, “select type” in “select when to activate the road state” Select the item and click OK.
Click Cancel to return to the main editing window (FIG. 20 (a)) of the scenario start condition.

Items that can be displayed and selected in the automatic start condition selection window (FIG. 20B) are the automatic start items displayed in FIG. In FIG. 20B, when the “Select when to start” folder is selected, the condition items No. 1 to No. 10 in FIG. 17A are displayed in the next lower hierarchy.
Similarly, if you select the “Select where to start” folder, No. 10 to 16 will be selected, and if you select the “Select when to start when road condition” folder, No. 21 to 23 will be displayed. , When you select the folder “Select when to start the car” No.17 ~ 20, when you select the folder “Select when to start the navigation” When No. 21 to 28 select a folder “Select when to start when user”, No. 29 to 30 are displayed in the next lower hierarchy.

In the condition range selection window (FIG. 20C) to be automatically started, the window configuration changes depending on the judgment condition item (category) selected in the previous window (b). In the illustrated example, an item window for selecting a road type is displayed.
Items that can be selected in the automatic start condition range selection window (FIG. 20C) are selectable items corresponding to the automatic start items selected in the automatic start condition selection window (FIG. 20B) (FIG. 20). 17 (b)). This selectable item is displayed in a pull-down menu by clicking the mark on the right side of the selection item column 408.

Select a condition range that may be started automatically from the list (or enter a number), and click the Add button to set the selected item and display it in the lower column. In the illustrated example, the case where “highway” is selected and the add button is clicked is displayed.
When the determination button is clicked in the condition range selection window (FIG. 20 (c)) to be automatically started, the setting state is determined, and the scenario editing condition main editing window (FIG. 20 (c)) is returned.
Click Cancel to return to the automatic start condition selection window (FIG. 20B).
In the main editing window of the scenario start condition in FIG. 20 (d), the automatic start condition list set in the above operation is displayed on the left side of the automatic start condition list (starts when the road type is a highway). .
When an automatic start condition displayed on the automatic start condition list screen is selected and the edit button is clicked, an automatic start condition selection window (FIG. 20 (b) for adding additional condition settings to the selected condition. )) Is displayed.

Next, various operations for creating a scenario other than the autonomous activation condition will be described.
The screen configuration displayed on the agent display screen 51 (see FIG. 9) is that the scene icon 307 displayed on the scene development screen 305 of the main window shown in FIG. The corresponding scene screen is displayed. When a screen configuration change button 309 on the setting screen 303 is clicked, a screen configuration selection window is displayed.
In this screen configuration selection window, as a screen configuration that can be displayed on the scene display screen 54 (see FIG. 9), there is a basic screen in which nothing is displayed, a 2-option screen in which two selection buttons are displayed, and a selection button. A plurality of selectable screens such as a plurality of button selection screens, for example, a list selection screen in which a plurality of items such as prefecture names are displayed in a list, and an image display screen in which image data is displayed are displayed.
The screen configuration is determined by selecting one screen configuration from the listed screen configurations.

When the agent display screen 311 is double-clicked with the mouse in the main window (FIG. 18) showing the editing state of the scene screen, an action editing dialog for editing a character action (agent action) instruction is displayed.
In this action editing dialog, a list of individual actions such as bowing, pointing to the right, and looking at the right, and a list of expressions such as thanks, denial, praise, greetings, etc. are displayed. Specify the action.

The dialogue of the character (agent) is set in the dialogue editing window.
The dialogue editing window is displayed by clicking the dialogue editing button 313 on the setting screen 303 in the main window (FIG. 18) showing the editing state of the scene screen.
In the dialogue editing window, setting by PCM (recorded voice data prepared) and setting by TTS (synthetic speech) are possible.
In the case of PCM, a dialogue is input with full-width hiragana (the above input box), and a search is made for the corresponding dialogue. A dialogue is selected from the retrieval result (the retrieval result list display column is present) and the character to be spoken is set.
On the other hand, in the case of TTS, a dialogue name (data for balloon display) and a reading (data for creating a synthesized speech) are input to set a dialogue that causes the character to speak.
In the dialog editing window, the contents of the set dialog are also reflected as data on the balloon screen 430.

FIG. 21 shows the flow of screen operations for compiling the created scenario into a real machine format (NAV format) that can be used by the agent device 1.
When the build button 332 is clicked in the main window (FIG. 18), a scenario compiler window (FIG. 21 (b)) is displayed.

In the scenario compiler window (FIG. 21 (b)), the name of the file to which the compiled data is output is designated in the name column 701.
Also, select the scenarios to be converted at the same time (convert the scenarios listed in the scenario list list 702 at the same time), and click the compile button 703, the scenario compiler (Figure 15: 240-1-2) will convert the data. Start.
The data conversion status is displayed on the result display unit 704.
Note that a scenario to be simultaneously converted is added by selecting an add button 705.

When the condition setting button 706 is selected in the scenario compiler window (FIG. 21B), a compile condition setting dialog (FIG. 21C) is displayed.
In this compile condition setting dialog (FIG. 21 (c)), when compiling into a real machine format (NAV format) that can be used by the agent device, the acquisition scenario management data including the autonomous start condition of the scenario is included as the compile condition The scenario execution data (scenario main body) is divided or integrated.
Further, when the acquired scenario management data and the scenario main body are separated, a URL that is a storage destination of the scenario main body is set in the storage destination designation information field 711 and a server to be set is set.
In addition to the above, items to be selected as compile conditions include an expiration date of scenario data.

  When the O.K. button is selected in the compile condition setting dialog (FIG. 21 (c)), the setting is determined and the screen returns to the scenario compiler window (FIG. 21 (b)). When the cancel button is selected, the setting is not reflected, and the screen returns to the scenario compiler window (FIG. 21B). When the end button is clicked in the scenario compiler window (FIG. 21B), the screen returns to the main window (a).

When the compile button 703 is clicked in the scenario compiler window (FIG. 21B), the autonomous activation conditions created by the scenario editor and grouping (classification) are performed by data conversion.
For example, a case where the following five conditions a to e are set as conditions for activating the Orbis warning scenario P will be described.
Condition a: The running road is an expressway Condition b: The vehicle speed is 120 km / h or more Condition c: 2 km before the point of Orbis A Condition d: 2 km before the point of Orbis B Condition e: The point of Orbis C Then, each of these condition a to condition e satisfies the conditions a and b and satisfies any one of the conditions c to e as an autonomous activation condition (in the scenario editor) Data format). The autonomous start conditions in this case are conceptually expressed as follows.
Condition a × condition b × (condition c + condition d + condition e)

When this autonomous activation condition is converted into the actual machine format (NAV format) by the compiler (240-1-2), first, the autonomous activation condition is expanded into the following three autonomous activation conditions consisting of logical products without including logical sums.
Condition a × condition b × condition c
Condition a × condition b × condition d
Condition a × condition b × condition e
Each of the autonomous activation conditions developed in this way is an autonomous activation condition for executing a corresponding scenario, and if any one is satisfied, the corresponding scenario is executed. In the case of the above example, if any one of the conditions is satisfied, a scenario for warning of Orbis will be executed. That is, one autonomous activation condition created for one scenario by the scenario compiler (240-1-2) is expanded into a plurality of autonomous activation conditions for the one scenario. Each deployed autonomous activation condition is associated with the corresponding scenario.

Similarly for other scenarios Q,
When an autonomous activation condition such as f × (g + h) × (i + j + k) is set, it is expanded into the following six autonomous activation conditions when converted into the real machine format (NAV format) by the scenario compiler (240-1-2). .
f × g × i
f × g × j
f × g × k
f × h × i
f × h × j
f × h × k
Accordingly, when the two types of scenarios P and Q are converted into the actual machine format (NAV format) by the compiler (240-1-2), nine autonomous activation conditions exist. There are three autonomous activation conditions for executing the scenario P of the Orbis warning, and six autonomous activation conditions for executing the other scenario Q.
As described above, the condition expansion means of the present invention is formed by expanding the activation condition constituted by the logical sum and logical product of the individual conditions into a plurality of activation conditions constituted by the logical product of the individual conditions. .

Next, the scenario compiler (240-1-2) has all the autonomous startup conditions after the expansion process (including the expanded autonomous startup conditions and the autonomous startup conditions that were not expanded because they do not include logical sums). On the other hand, the date and position are grouped as described with reference to FIGS.
In the grouping process, the scenario compiler (240-1-2) acquires information on the position from each autonomous activation condition, normalizes the primary mesh and the secondary mesh for the position according to the description of FIG. A primary mesh code and a secondary mesh code for the position are calculated.
Then, by sorting by year, grouping (classification) for the highest year is performed. Then, the sorting process by the second date (month and day) is performed for each grouped year and the group without year condition. Further, grouping is performed on the third and fourth positions for each grouped date and group without date condition.
In this way, the classifying means of the present invention is formed by classifying (grouping) the developed activation conditions and other set activation conditions into predetermined individual conditions.

Each automatic startup condition grouped (classified) by the scenario compiler (240-1-2) is attached with an index (identification code) that represents the group, and the scenario data (240-2) in the actual machine format (NAV format) together with the scenario body -4), it is stored in the scenario edit data (240-2) of the storage device 240.
Instead of attaching an identification code for each automatic activation condition, the automatic activation condition may be stored for each group and the identification code may be assigned for each group.

The scenario data (240-2-4) in the actual machine format (NAV format) may be separated or separated from the scenario body and the recorded scenario management data.
The following describes the case where the data is separated. In this case, the storage destination is set by associating the storage destination designation information indicating where the screen element transition body data is stored outside the vehicle with the activation condition. Corresponds to information setting means.
When “Split and place on server” is selected in the compile condition setting dialog (FIG. 21 (c)), a place for placing the compiled scenario main body and the collected scenario management data is designated.
FIG. 21C shows a state where “http://www.equos.co.jp/Sample/” is set, which means that the created scenario is placed at this address.
For example, as shown in FIG. 21 (b), a case will be described in which NAV format scenario data is created with three scenarios of sample scenario, sample scenario 2, and sample scenario 3.
The name of the management part is the one entered in the name input field of FIG. That is, Sample.NAV. Each scenario data is generated in the form of “Scenario” + sequence number in the form of Scenario0001, Scenario0002, Scenario0003. Sequence numbers are automatically assigned as 1, 2, 3,... In order from the scenario on the list of FIG.

By combining this with the address http://www.abcd.co.jp/Sample/ set in FIG. 21 (C), the actual address of each file is as follows.
(B) http://www.abcd.co.jp/Sample/Sample.NAV
(B) http://www.abcd.co.jp/Sample/Scenario0001
(C) http://www.abcd.co.jp/Sample/Scenario0002
(D) http://www.abcd.co.jp/Sample/Scenario0003

Actually, the scenario data (10-2-3-4) of the agent device 1 includes http://www.abcd.co.jp/Sample/Sample.NAV/, the address where Sample.NAV is placed, It exists in the header part, and the parts of Scenario0001, Scenario0002, and Scenario0003 are stored together with each condition of the sorted autonomous activation conditions.
The http://www.abcd.co.jp/Sample/Sample.NAV/ part in the header part is added to the scenario data (10-2-3-4) when the scenario activation condition is registered. Stored in

Scenario data in the actual machine format stored in scenario data (10-2-3-4), that is, autonomous start conditions, scenario 1, scenario 2, and scenario 3, are uploaded to the addresses (i) to (d) above. Is done.
Then, when these scenarios 1, 2 and 3 are used in the in-vehicle device, the acquisition scenario management data is downloaded from its address http://www.abcd.co.jp/Sample/Sample.NAV.

When issuing a scenario activation request on the in-vehicle device (S23 in FIG. 11), http://www.abcd.co.jp/Sample/ recorded when the scenario is registered and each of the sorted autonomous activation conditions The part of Scenario0001 stored together with the condition is combined, attached to the scenario activation request, and sent to the scenario driver (101-1).
By doing so, the scenario driver (101-1) downloads http://www.abcd.co.jp/Sample/Scenario0001 when acquiring scenario data (s505-4-4 in FIG. 17). To do.

  Further, the user may be allowed to input the file name of each scenario data without automatically generating the file name. In this case, this is done by providing a column for inputting the file name when compiling in the list of scenarios to be compiled in FIG. However, the input is the relative position from Sample.NAV.

In addition, although the case where the place where scenario data is placed is specified in the scenario editor has been described, other methods may be used.
For example, the address at the time of downloading may be stored (variation 1).
In this case, the storage destination designation information field 711 in the compilation condition setting dialog FIG. 21C is unnecessary and is not displayed.
Assume that the compiled scenario is placed at http://www.abcd.co.jp/Sample/Sample.NAV.
When downloading this with the in-vehicle device, the downloaded address http://www.abcd.co.jp/Sample/Sample.NAV is transmitted from the browser software to the agent processing unit, and Sample.NAV in the file name portion is transmitted. Record the part of http://www.abcd.co.jp/Sample/ excluding. Hereinafter, the process after issuing the scenario activation request in the in-vehicle device is the same as the above.
Even in the case of the first modification, the user may be allowed to input the file name of each scenario data without automatically generating the file name. In this case, this is done by providing a column for inputting the file name when compiling in the list of scenarios to be compiled in FIG. However, the input is the relative position from Sample.NAV.

Furthermore, the form which combined the said method and the deformation | transformation 1 may be used. That is, even in the case of the above method, when downloading, the downloaded address is transmitted from the browser software to the agent processing unit. If the file name is different from the one recorded in the scenario data (the address set in FIG. 21C), the address transmitted from the browser software is used.
In other words, scenario data was created and placed at http://www.abcd.co.jp/Sample/ for a while, but for some reason, the location was changed to http://www.efgh.co.jp/ When placed in NAVI / Sample /, there is no need to recreate scenario data.

As described above, according to the agent device of the present embodiment, the process of determining whether the condition for autonomously starting the agent (making it appear automatically) is satisfied based on the scenario data created by the scenario creation device. It is executed periodically or when a specific state is satisfied, and an agent can be automatically added when a condition is satisfied.
On the other hand, according to the scenario creation device and the scenario editor of this embodiment, regardless of whether or not there is knowledge of the program, having a scenario editor makes it possible for agents to automatically appear and respond when a specific condition is met. Scenario data can be easily created and edited.

In addition, according to the scenario creation device 1 of the present embodiment, the scenario compiler (240-1-2) expands the autonomous activation conditions into autonomous activation conditions that do not include a logical sum, and groups the year, date, and position. It can be carried out.
And since the autonomous activation conditions are grouped by the scenario creation device, the agent device only needs to determine the autonomous activation conditions in the group corresponding to the date and vehicle current position for the determination, The load can be reduced.

Furthermore, according to the scenario apparatus of the present embodiment, the scenario main body and the recorded scenario management data are separated and converted into the actual machine format by the scenario compiler (240-1-2).
For this reason, in the agent device (in-vehicle device), the scenario main body is individually downloaded from the server, temporarily stored, and executed, so the recorded scenario management data (including the URL of the scenario main body and the activation condition) is stored in the information storage device 10. What is necessary is just to store, and more power collection management data can be stored with respect to the capacity of a limited storage medium. That is, more scenarios can be executed with the same storage capacity.

As mentioned above, although 1 embodiment in the vehicle-mounted apparatus of this invention, a data creation apparatus, and a data creation program was described, this invention is not limited to described embodiment, It is possible to perform various deformation | transformation. .
For example, in the agent device according to the embodiment described above, one or more autonomous activation conditions included in the classification satisfying the current situation are extracted, and it is determined whether the conditions are satisfied for the extracted autonomous activation conditions. It is also possible to determine all autonomous activation conditions as a determination target without classifying the activation conditions. Also in this case, the corresponding scenario is downloaded and executed by specifying the URL stored in association with the satisfied autonomous activation condition.

In the described embodiment, as described in FIG. 10, when the autonomous activation condition is satisfied, a scenario corresponding to the autonomous activation condition is individually downloaded from the server and stored in the RAM (1-4). I am trying to do it.
In contrast, the autonomous activation determination unit (101-2) extracts the autonomous activation condition group (currently extracted) to reduce the determination of the autonomous activation condition, and includes conditions that approximate conditions such as the vehicle position and time. All scenarios corresponding to the autonomous activation conditions included in the classification satisfying the situation may be downloaded in a lump and stored in the RAM (1-4).
In this case, although the burden on the download and its temporary storage increases, a scenario that has a high possibility of satisfying the autonomous activation condition is downloaded in advance, so that a scenario that satisfies the autonomous activation condition can be activated immediately.

In the described embodiment, grouping related to the year, date, and position is performed on the deployed autonomous activation condition. However, grouping may be performed based on one or two of them. Further, grouping for other individual conditions may be performed.
Further, in grouping, conditions with less change with time and vehicle movement are classified into higher ranks, but the position-related conditions may be made highest.
Further, in the grouping related to the position, the normalization by the primary mesh and the secondary mesh is performed for the grouping, but the grouping by only the primary mesh may be used. In this case, the size of the primary mesh can be the same as that of the secondary mesh.

Further, in the embodiment described above, the scenario creation device has been described for the case where the scenario creation device performs the autonomous activation condition deployment processing and grouping. However, the agent device performs the deployment processing (deployment means) on the autonomous activation condition included in the scenario data. Grouping (classification means) may be performed.
Further, in the embodiment and the modification described above, the case where the autonomous activation condition is expanded to the autonomous activation condition that does not include the logical sum for the autonomous activation condition that includes the logical sum as the expansion processing of the autonomous activation condition has been described. The logical sum may be expanded only for individual conditions to be processed. That is, in the case of the described embodiment, the logical sum for individual conditions other than the year, date, and position to be classified is not expanded.

In the embodiment described above, the case where the autonomous activation conditions are grouped with respect to the year, date, and position to reduce the burden of determination processing has been described.
For example, when narrowing down menus in a scenario creation device, an agent device, a navigation function, etc., it can be applied to grouping when a user selects and starts various introduction scenarios. As for the grouping related to the position, the normalization process using the primary mesh and the secondary mesh described in FIG. 11 is performed.
In other words, it would be nice to increase information provision items (scenarios) such as leisure guides, but on the other hand, since the number of selection items increases, the menu hierarchy becomes deeper and the list display items increase, which makes scrolling difficult.
Therefore, it is possible to make selection easier by narrowing down to a scenario (necessary one) related to the region and date and displaying the menu.
For example, as an example of narrowing down by area, there are Karuizawa introduction (tourism, special product, etc.), Yokohama introduction, ..., traffic information in the case of the city center, etc. Limited to when vehicles exist in Yokohama and its surrounding mesh And display the introduction scenario of Yokohama.
In addition, examples of grouping by date include a ski resort guide, a beach guide, a first bath guide, and the like. By grouping in this way, the bathing guide is excluded from the display target in winter, and the ski guide and the initial guide are excluded from the target in summer, so that the display items can be reduced and the selection can be facilitated.
An example of narrowing down by date and region is a festival.

In this way, by narrowing down various introductory scenarios such as leisure, shopping, eating and drinking, etc., by grouping them by region or date, when the user selects a scenario to be executed individually, it is limited to scenarios that are relevant to the time and region. If the time is out of date or the area is far away, the scenario is not displayed.
As a result, unrelated scenarios are not displayed, so that the user can easily select a necessary scenario.

1 is an overall system configuration diagram including an agent device, a scenario creation device, and a server according to an embodiment of the present invention. It is a block diagram which shows the structure of the agent apparatus in one Embodiment of this invention. It is explanatory drawing showing the relationship between the agent process part implement | achieved by executing a program with CPU, and the whole process part. It is explanatory drawing showing the structure of the agent process part. It is explanatory drawing which represented the information currently collected on the external storage medium notionally. This shows the configuration of actual machine format scenario data. It is explanatory drawing which represented notionally the structure of the autonomous starting condition data stored in the management data of an acquisition scenario. It is explanatory drawing showing normalization of the position coordinate by a primary mesh and a secondary mesh. It is the screen transition diagram showing the transition of the scene screen by the guidance scenario which the inn transmitted to the prospective guest for each scene. It is the flowchart showing the autonomous start determination process of the scenario by an autonomous start determination part. It is a flowchart showing the processing content of condition judgment processing. It is a flowchart showing an example of the flow of scenario execution processing. It is a flowchart showing scenario data acquisition processing. It is a block diagram of a scenario creation apparatus. This is a conceptual representation of the scenario editing program and data structure. It is a conceptual representation of data format conversion. The items that can be set as the automatic start items are illustrated. It shows the structure of the main window displayed on the display device when the scenario editor is activated. This shows the flow of screen operations for editing scenario properties. It shows the flow of screen operations for editing scenario start conditions from the main edit window for scenario start conditions. It shows the flow of screen operations for compiling the created scenario into a real machine format that can be used for navigation.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Agent apparatus apparatus 2 Scenario preparation apparatus 3 Server (1) Central processing apparatus (2) Display apparatus (3) Audio | voice output apparatus (4) Audio input apparatus (5) Input apparatus (6) Various condition detection apparatuses (7) Various vehicle-mounted Device (8) Communication control device (9) Communication device
(10) External storage device
(200) Control unit
(210) Input device
(220) Output device
(230) Communication control device
(240) Storage device
(250) Storage medium drive
(260) Input / output I / F

Claims (5)

Start condition storage means for storing start conditions for screen element transition body data configured by combining screen elements in which processing contents executed in synchronization with screen display are defined;
Management data storage means for storing management data for managing the storage destination of the screen element transition body data corresponding to the activation condition;
Condition judging means for judging whether or not the activation condition is satisfied;
When it is determined that the activation condition is satisfied by the condition determination unit, an acquisition unit that acquires the screen element transition body data stored in association with the activation condition according to the management data;
Execution means for executing the acquired screen element transition body data ,
In the management data storage means, information indicating whether the screen element transition body data corresponding to the start condition is stored in the device or stored outside the device is recorded as the management data,
Storage location designation information for designating a storage location of screen element transition body data stored outside the device is stored in association with the activation condition,
In-vehicle device characterized by the above. Vehicle apparatus according to claim 1, wherein the screen element transition body has data every ID is imparted, the storage destination specifying information and activation condition corresponding to the ID is tied, characterized in that. The activation conditions are classified by date or position,
It said condition judging means is claim 1 or characterized by determining whether to satisfy the activation condition according to the classification-vehicle apparatus according to claim 2. The activation condition is classified into an activation condition that includes a position as a condition and an activation condition that does not include a position.In addition, the activation condition that includes a position as a condition is classified in units of areas divided into a certain size,
The condition determining means determines whether or not an activation condition that does not include a condition for the position and an activation condition classified into an area corresponding to the current position of the vehicle is satisfied.
Vehicle apparatus according to any one of claims of claims 1 to 3, characterized in that. Start condition storage means for storing start conditions for screen element transition body data configured by combining screen elements in which processing contents executed in synchronization with screen display are defined;
Creating means for creating screen element transition body data configured by combining screen elements in which processing contents executed in the in- vehicle device are defined in synchronization with the screen display ;
An activation condition setting means for setting an activation condition for activating the screen element transition body data ;
Management data setting means for setting management data in which information indicating whether the screen element transition body data corresponding to the activation condition is stored in the device or stored outside the device;
Storage destination information setting means for setting storage destination designation information indicating where the screen element transition body data is stored outside the apparatus in association with the activation condition;
A data creation device characterized by comprising:

Images