WO2019188981A1

WO2019188981A1 - Information processing system, information processing device, server, information processing method, and program

Info

Publication number: WO2019188981A1
Application number: PCT/JP2019/012506
Authority: WO
Inventors: 瑞樹横山
Original assignee: 株式会社アドバンスト・メディア
Priority date: 2018-03-29
Filing date: 2019-03-25
Publication date: 2019-10-03
Also published as: JP6729942B2; TW201942772A; JP2019175290A

Abstract

In order to implement a technology with which variations of a conversation scenario can be more easily increased, a scene determination unit 117 in a conversation scenario processing system 1 determines whether data of a scenario to be executed includes an abstract element for which a selection condition for selecting data serving as a scenario data element has been set. When the scene determination unit 117 determines that an abstract element is included, a search request unit 118 acquires data serving as a data element of a scenario corresponding to the abstract element from a server 20, on the basis of the selection condition that has been set for the abstract element, and a data execution unit 114 replaces the abstract element in the data of the scenario to be executed with the data element of the scenario corresponding to the abstract element, and executes the data of the scenario to be executed.

Description

Information processing system, information processing apparatus, server, information processing method, and program

The present invention relates to an information processing system, an information processing apparatus, a server, an information processing method, and a program.

Conventionally, a dialogue system in which a computer and a person interact is known. In such a dialogue system, the dialogue proceeds based on a dialogue scenario prepared in advance. Here, in order to realize a natural dialogue according to various situations in the dialogue system, it was necessary to prepare a lot of response patterns corresponding to each of them, assuming the contents of speech, conditions (situations), etc. .

However, even if a large number of response patterns corresponding to the utterance contents and conditions are prepared, when using a response pattern prepared in advance, the same response pattern is repeated, so that the conversation itself is not interesting. . Therefore, in order to increase the number of dialog variations, the dialog scenarios are structured, interfaces (dialog inputs and outputs) are defined in the structured dialog scenarios, and the dialog scenarios are combined on the condition that the interface is compatible. A technique to make it has been proposed. According to such a method, it is considered that it is easier than before to create a dialogue scenario with abundant variations by weakening the degree of coupling between dialogue scenarios and increasing the reusability of the dialogue scenarios.
A technique for creating a dialogue scenario is disclosed in Non-Patent Document 1, for example.

However, in the conventional technique for creating a dialogue scenario, since strict conformity is required with respect to the interface of the dialogue scenario, it is necessary to expand the dialog scenarios that can be combined. In addition, the interaction scenario was determined when the interaction scenario was created. Therefore, even if the number of interaction scenarios that can be combined increases, the number of interaction scenarios that have already been created has not necessarily increased. There was a case that could not benefit from.
As described above, in the conventional technique, it is difficult to easily increase the variation of the dialogue scenario.

The object of the present invention is to realize a technology that can more easily increase variations of dialogue scenarios.

In order to achieve the above object, an information processing system according to one embodiment of the present invention includes:
An information processing system configured to be able to communicate with an information processing apparatus that executes scenario data of a dialogue process and a server that accumulates data that is an element of the scenario data,
The information processing apparatus includes:
Element determination means for determining whether or not the scenario data to be executed includes an abstract element in which a selection condition for selecting data that is an element of the scenario data is included;
When the element determination unit determines that the abstract element is included, based on the selection condition set in the abstract element, data serving as an element of the scenario data corresponding to the abstract element is stored in the server. Data acquisition means to acquire from,
Data execution means for executing the scenario data to be executed by replacing the abstract element in the scenario data to be executed with the data to be the scenario data corresponding to the abstract element;
It is characterized by providing.

According to the present invention, it is possible to realize a technology that can more easily increase variations of dialogue scenarios.

It is a figure which shows the system configuration | structure of the dialogue scenario processing system which concerns on this invention. It is a figure which shows the hardware constitutions of the information processing apparatus which comprises a terminal device and a server. It is a block diagram which shows the function structure of a terminal device. It is a schematic diagram which shows an example of scenario creation GUI. It is a block diagram which shows the function structure of a server. It is a flowchart which shows the flow of the scenario creation process which a terminal device performs. It is a flowchart which shows the flow of the scenario execution process which a terminal device performs. It is a flowchart which shows the flow of the scenario creation assistance process which a server performs. It is a flowchart explaining the flow of the scenario execution assistance process which a server performs. It is a schematic diagram which shows an example of the scenario of the dialogue process performed in this embodiment.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[Constitution]
[System configuration]
FIG. 1 is a diagram showing a system configuration of a dialogue scenario processing system 1 according to the present invention.
The dialogue scenario processing system 1 is configured as an embodiment of an information processing system according to the present invention, and executes a scenario (a dialogue processing scenario) when a character generated on a computer interacts with a human being. This is a system that can easily increase the variation of the scenario of the interactive process by dynamically calling a part of the scenario (a scene inserted into an abstract scene described later) from the outside.

In the present embodiment, in the dialogue scenario processing system 1, scenario data representing a series of dialogue flows of a character is constructed with scene data as a structural unit. A scene is an element that constitutes a flow of dialogue, and each scene is constituted by various events that occur based on the utterances and operations of the interlocutor in the dialogue or the transition of the scene. When an event occurs, an action in which the content of the event is defined (visual program) is executed.

In addition, when scenario data is constructed in the interactive scenario processing system 1, a GUI (Graphical User Interface) including a flow builder is provided to the user as will be described later. In this embodiment, the flow builder can construct a scenario representing a flow of a series of dialogs by arranging icons representing scenes.

Also, in the scenario data and the scene data, a parameter set necessary for using the scenario and the scene and a parameter value condition (value or value range) can be designated. The dialogue scenario processing system 1 manages various parameters in the dialogue processing, and updates various parameter values in response to execution of scenario data or scene data.

For example, tags, tasks, position information, time, number of times of use, sensor information, use history, etc. can be defined as the types of parameters specified for scenario data and scene data. Specifically, a title, application, and field (sports, artist, food, etc.) can be specified as a tag. In addition, execution contents such as search, calculation, greeting, and blur can be specified as tasks. Moreover, information display around a predetermined position (current position or specific position, etc.) can be specified as position information, and the time can be specified as morning, noon, night (that is, whether or not conversation content can be selected depending on the time zone), etc. Can be specified. In addition, as the number of times of use, the number of times of use per predetermined period (for example, when it is used once, it is not used for 3 months) can be designated, and as the sensor information, the detection value of the acceleration sensor can be designated. In addition, the usage history of scenario data and scene data for each user (whether it has been used in the past or the like) can be designated as the usage history.

As shown in FIG. 1, the dialogue scenario processing system 1 includes a plurality of terminal devices 10 and a server 20, and the plurality of terminal devices 10 and the server 20 can communicate with each other via a network 30. It is configured.

The terminal device 10 is used by a user such as a creator and provides a GUI (hereinafter referred to as “scenario creation GUI”) for constructing scenario data by executing a scenario creation process described later.
Further, the terminal device 10 acquires component data for configuring a scenario from the server 20 in the scenario creation GUI, and provides it in a form that can be selected by the user. Further, the terminal device 10 uploads the scenario data created in the scenario creation GUI to the server 20. The scenario data uploaded to the server 20 can be reused as component data when creating other scenario data.

In this embodiment, the scenario data includes abstract scene data in which a condition for selecting a scene (hereinafter referred to as “scene selection condition”) is set, not a specific scene designation. Is possible. The scene selection condition can be set as a parameter condition required for a scene inserted into an abstract scene, for example. For example, in the case of an abstract scene for which “time” is set as the scene selection condition, only scenes for which “time” parameters or parameters related to “time” are specified are selected as scenes to be inserted into the abstract scene. It becomes possible.

Further, the terminal device 10 is used by a user such as a person interacting with the computer, and executes scenario data by executing scenario execution processing described later. Here, since there is no specific interaction processing in the above-described abstract scene, the terminal device 10 cannot execute the abstract scene itself. For this reason, when detecting the abstract scene, the terminal device 10 is adapted to the part data or scenario data (satisfying the scene selection condition and the current situation of the dialogue processing (dialog flow, etc.)) that suits the situation at the time of the dialogue execution. (Scene or scenario data) is acquired from the server 20 in real time, and the dialogue processing is executed in the form of being embedded in the abstract scene. That is, when abstract scene data is included in the scenario data, the terminal device 10 conforms to the current situation of the interactive processing and also satisfies the scene selection conditions set in the abstract scene. Is requested to the server 20 to dynamically select a scene and execute a dialogue process based on the scenario data.
As a result, it is possible to easily increase the variation of the scenario of the dialogue process.

The server 20 includes a component database (component DB) that stores a plurality of component data and a scenario database (scenario DB) that stores data of a plurality of scenarios. The server 20 executes scenario creation support processing described later, and when the scenario creation GUI is provided to the user in the terminal device 10, the server 20 stores the component data stored in the component DB and the scenario DB. The scenario data is provided to the terminal device 10 as appropriate. Further, the server 20 executes a scenario execution support process to be described later, so that when the scenario of the dialog process is executed in the terminal device 10, the server 20 is adapted to the current situation of the dialog process and set to an abstract scene. The component data or scenario data matching the selected scene selection condition is retrieved and provided to the terminal device 10 as appropriate.

[Hardware configuration]
Next, the hardware configuration of the terminal device 10 and the server 20 of the dialogue scenario processing system 1 will be described.
The terminal device 10 and the server 20 are configured by an information processing device. For example, the terminal device 10 can be configured by a PC (Personal Computer), and the server 20 can be configured by a server computer.

FIG. 2 is a diagram illustrating a hardware configuration of the information processing apparatus 800 that configures the terminal device 10 and the server 20.
As illustrated in FIG. 2, the information processing apparatus 800 includes a CPU (Central Processing Unit) 811, a ROM (Read Only Memory) 812, a RAM (Random Access Memory) 813, a bus 814, an input unit 815, and an output A unit 816, a storage unit 817, a communication unit 818, and a drive 819.

The CPU 811 executes various processes according to a program recorded in the ROM 812 or a program loaded from the storage unit 817 to the RAM 813.
The RAM 813 appropriately stores data necessary for the CPU 811 to execute various processes.

The CPU 811, the ROM 812, and the RAM 813 are connected to each other via a bus 814. An input unit 815, an output unit 816, a storage unit 817, a communication unit 818, and a drive 819 are connected to the bus 814.

The input unit 815 is configured with various buttons and the like, and inputs various information according to an instruction operation.
The output unit 816 includes a display, a speaker, and the like, and outputs an image and sound.
The storage unit 817 is configured by a hard disk, a DRAM (Dynamic Random Access Memory), or the like, and stores various data managed by each server.
The communication unit 818 controls communication performed with other devices via a network.

A removable medium 821 made of a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is appropriately attached to the drive 819. The program read from the removable medium 821 by the drive 819 is installed in the storage unit 817 as necessary.
Note that the above hardware configuration is a basic configuration of the information processing apparatus 800. When the terminal device 10 or the server 20 is configured, additional hardware can be appropriately provided. For example, when the terminal device 10 is configured, it is possible to include an imaging unit that captures a digital image.

[Functional configuration]
Next, functional configurations of the terminal device 10 and the server 20 will be described. FIG. 3 is a block diagram illustrating a functional configuration of the terminal device 10.
As illustrated in FIG. 3, the CPU 811 of the terminal device 10 executes the scenario creation process and the scenario execution process, so that in the CPU 811, the GUI formation unit 111, the GUI input reception unit 112, the data generation unit 113, and the data execution The unit 114, the scenario data registration unit 115, the scenario data acquisition unit 116, the scene determination unit 117, and the search request unit 118 function. In addition, a scenario data storage unit 121 and a history data storage unit 122 are formed in the storage unit 817 of the terminal device 10.

The scenario data storage unit 121 stores scenario data created in the scenario creation GUI and scenario data to be executed.
The history data storage unit 122 stores data on the history of dialogue processing executed in the terminal device 10.
The GUI formation unit 111 forms a scenario creation GUI on the display screen when the scenario creation process starts. Further, the GUI forming unit 111 displays the character image when the execution of the scenario execution process is started, and controls the movement of the character according to the data of the dialogue scenario.

FIG. 4 is a schematic diagram illustrating an example of a scenario creation GUI. As shown in FIG. 4, the scenario creation GUI includes a flow builder unit 131.
The flow builder unit 131 is a GUI for configuring the flow of the entire scenario. In the flow builder unit 131, a user can configure a scenario having a framework of a desired dialogue flow by arranging icons representing scenes constituting the scenario. That is, the user can define a scenario as a state transition of a scene. In the present embodiment, the flow builder unit 131 can define scenes with various attributes that constitute a scenario. For example, FIG. 4 shows a normal scene represented by a solid circular icon and an abstract scene represented by a broken circular icon as scene attributes. An ordinary scene can define an event, an action, and the like, and an abstract scene can set a scene selection condition.

In this embodiment, scene data (part data) representing specific contents prepared in advance in the dialogue scenario processing system 1 can be selected as a normal scene. For example, at the time of creating a scenario, scene data that is frequently incorporated can be prepared in advance as component data. Specifically, scene data or the like that the character greets can be prepared as component data. Further, as described above, in the present embodiment, scenario data uploaded to the server 20 can also be reused as component data.

Returning to FIG. 3, the GUI input receiving unit 112 receives user input to each part of the scenario creation GUI, and receives the received input content as a GUI forming unit 111, a data generation unit 113, a data execution unit 114, or a scenario data registration unit. 115. For example, the GUI input reception unit 112 receives selection of an icon representing a scene in the flow builder unit 131. Further, the GUI input receiving unit 112 receives input of input contents (specific scene contents or abstract scene scene selection conditions) according to the type of the selected icon.

The data generation unit 113 generates various data related to scenario creation in response to a user input to the scenario creation GUI. For example, when an icon representing a scene is selected in the flow builder unit 131, the data generation unit 113 adds data of a type of scene corresponding to the selected icon to the scenario data being created. In the present embodiment, as an icon representing a scene, an icon of a normal scene in which specific interactive processing is defined or an icon of an abstract scene can be selected. Further, the data generation unit 113 transmits a request for part data or scenario data to be added to the scenario data being created (request for creation data) to the server 20 in response to a user input, and the creation data The part data or scenario data provided from the server 20 in response to the request is added to the scenario data being created.

The data execution unit 114 executes the scenario data created by the scenario creation GUI or the scenario data to be executed acquired by the scenario data acquisition unit 116, and advances the dialogue with the human by the character. At this time, if the scenario data to be executed includes an abstract scene, the data execution unit 114 inserts the part data or scenario data input from the search request unit 118 into the abstract scene and executes it.
The data execution unit 114 executes a part of scenario data created in the scenario creation GUI (for example, from the scene data at the beginning of the scenario to the data of the abstract scene, etc.) according to the user's specification. It is also possible.
Accordingly, the user can create scenario data while performing a simulation when the scenario data being created is executed.

The scenario data registration unit 115 transmits scenario data created in the scenario creation GUI to the server 20 in accordance with a user instruction, and registers the scenario data in the scenario DB.
The scenario data registered in the scenario DB can be reused as component data when another user creates scenario data in the scenario creation GUI.

The scenario data acquisition unit 116 acquires scenario data (execution target scenario data) instructed to be executed by the user. For example, the scenario data acquisition unit 116 acquires the scenario data selected by the user from the scenario DB 221 of the server 20. Then, the scenario data acquisition unit 116 stores the acquired scenario data in the scenario data storage unit 121.

The scene determination unit 117 determines whether an abstract scene is included in the scenario data to be executed. When it is determined that the abstract scene is included in the scenario data to be executed, the scene determination unit 117 outputs information specifying the abstract scene to the search request unit 118.

When the scene determination unit 117 determines that an abstract scene is included in the execution target scenario data, the search request unit 118 specifies information and an interaction process that specify the abstract scene input from the scene determination unit 117. Based on the various parameters in, the server 20 is requested to request part data or scenario data (execution data request) that conforms to the current situation of the interactive processing and conforms to the scene selection conditions set in the abstract scene. Send. Then, the search request unit 118 outputs the part data or scenario data provided from the server 20 in response to the request for execution data to the data execution unit 114.

Next, the functional configuration of the server 20 will be described. FIG. 5 is a block diagram illustrating a functional configuration of the server 20.
As illustrated in FIG. 5, the CPU 811 of the server 20 executes the scenario creation support process and the scenario execution support process, whereby the scenario registration reception unit 211, the creation data request acquisition unit 212, and the creation provision data are executed in the CPU 811. The acquisition unit 213, the creation data provision unit 214, the execution data request acquisition unit 215, the execution data search unit 216, and the execution data provision unit 217 function. In addition, a scenario DB 221, a component DB 222, and a user profile storage unit 223 are formed in the storage unit 817 of the server 20.

The scenario DB 221 stores scenario data representing various conversation contents between a character and a human. The component DB 222 stores various component data representing specific contents.
The scenario data stored in the scenario DB 221 and the component data stored in the component DB 222 include a parameter set necessary for using the scenario and the scene, and parameter value conditions (values or range of values). When scenario data and part data are searched, the scenario data and part data are scored and searched using these parameter sets and parameter value conditions as keys.
The user profile storage unit 223 stores a personal profile (user profile) of each user who has performed dialogue processing in the plurality of terminal devices 10. The user profile includes, for example, age, gender, occupation, hobby, palatability, behavior pattern, personality, etc., and such information can be used as appropriate when conducting a dialogue specific to the individual of the conversation. .

The scenario registration accepting unit 211 receives the scenario data created by the scenario creation GUI in the terminal device 10 and transmitted for registration in the scenario DB, and registers the scenario data in the scenario DB 221.

The creation data request acquisition unit 212 acquires, from the terminal device 10, a request for part data or scenario data (request for creation data) to be added to the scenario data by the scenario creation GUI.

The creation provision data acquisition unit 213 acquires the part data or scenario data indicated in the creation data request acquired by the creation data request acquisition unit 212 from the component DB 222 or the scenario DB 221.

The creation data providing unit 214 provides the component data or scenario data acquired by the creation providing data acquisition unit 213 to the terminal device 10 that has requested the creation data.
The execution data request acquisition unit 215 acquires, from the terminal device 10, a request for part data or scenario data to be inserted into the abstract scene (execution data request) when executing the scenario data to be executed. The execution data request includes a parameter indicating the current state of the interactive process and a scene selection condition set for the abstract scene.

The execution data search unit 216 is based on the parameter indicating the current state of the interactive process indicated in the request for execution data acquired by the execution data request acquisition unit 215 and the scene selection condition set in the abstract scene. Thus, the component DB 222 or the scenario DB 221 is searched from the component DB 222 or the scenario DB 221 for matching the current situation of the interactive processing and matching the scene selection conditions set in the abstract scene. Specifically, the execution data search unit 216 uses the parameter set and parameter value conditions as keys to set the parameters that indicate the current state of the interactive processing and the scenario that matches the scene selection conditions set in the abstract scene. Search data or scene data by scoring. As a score calculation method at this time, a method used for a general-purpose search engine can be adopted, or a method prepared for searching for part data or scenario data can be adopted.

The execution data providing unit 217 provides the scenario data or scene data searched by the execution data search unit 216 to the terminal device 10 that has requested the execution data. In the present embodiment, the execution data providing unit 217 provides the terminal device 10 with the highest score among scenario data or scene data searched by the execution data search unit 216. However, the execution data providing unit 217 may provide the terminal device 10 with a plurality of scenario data or scene data searched by the execution data search unit 216 having a higher score.

[Operation]
Next, the operation of the dialogue scenario processing system 1 will be described. First, the operation of the terminal device 10 will be described.

[Scenario creation process]
FIG. 6 is a flowchart showing a flow of scenario creation processing executed by the terminal device 10.
The scenario creation process is started in response to an operation instructing execution of the scenario creation process in the terminal device 10.
In step S1, the GUI forming unit 111 forms a scenario creation GUI (see FIG. 4) on the display screen.

In step S 2, the GUI forming unit 111 determines whether or not an input to the scenario creation GUI has been performed via the GUI input receiving unit 112.
When input to the scenario creation GUI is performed via the GUI input receiving unit 112, it is determined as YES in Step S2, and the process proceeds to Step S3.
On the other hand, when the scenario creation GUI is not input via the GUI input receiving unit 112, it is determined as NO in Step S2, and the process proceeds to Step S10.

In step S 3, the GUI forming unit 111 determines whether an abstract scene has been input to the flow builder unit 131 via the GUI input receiving unit 112.
When an abstract scene is not input to the flow builder unit 131 via the GUI input receiving unit 112, it is determined as NO in Step S3, and the process proceeds to Step S6.
On the other hand, when an abstract scene is input to the flow builder unit 131 via the GUI input receiving unit 112, it is determined as YES in Step S3, and the process proceeds to Step S4.

In step S 4, the GUI forming unit 111 receives an input of a scene selection condition via the GUI input receiving unit 112.
In step S5, the data generation unit 113 adds the abstract scene in which the scene selection condition is set to the scenario data.
After step S5, the process proceeds to step S8.

In step S 6, the GUI forming unit 111 determines whether a normal scene (a scene in which specific interactive processing is defined) is input to the flow builder unit 131 via the GUI input receiving unit 112.
When a normal scene is input to the flow builder unit 131 via the GUI input reception unit 112, YES is determined in step S6, and the process proceeds to step S7. On the other hand, when a normal scene is not input to the flow builder unit 131 via the GUI input receiving unit 112, NO is determined in step S6, and the process proceeds to step S8.
In step S7, the data generation unit 113 adds the input normal scene to the scenario data. The normal scenes added at this time include those directly defined by the user and those obtained from the server 20 by sending a request for data for creation to the server 20.

In step S8, the GUI forming unit 111 determines whether or not the input to the scenario creation GUI is an operation for instructing execution of the scenario being created. In step S8, an instruction to execute a part of the scenario being created (only one scene or the like) or the entire scenario is accepted.
If the input to the scenario creation GUI is an operation to instruct execution of the scenario being created, YES is determined in step S8, and the process proceeds to step S9. On the other hand, when the input to the scenario creation GUI is not an operation for instructing execution of the scenario being created, NO is determined in step S8, and the process proceeds to step S10.
In step S9, the data execution unit 114 executes the scenario (partial or whole) instructed to be executed in step S8.

In step S 10, the GUI forming unit 111 determines whether the input to the scenario creation GUI is an operation for instructing to register scenario data in the scenario DB of the server 20.
When the input to the scenario creation GUI is an operation for instructing to register scenario data in the scenario DB of the server 20, YES is determined in step S10, and the process proceeds to step S11. On the other hand, if the input to the scenario creation GUI is not an operation for instructing the scenario data to be registered in the scenario DB of the server 20, NO is determined in step S10, and the process proceeds to step S12.
In step S11, the scenario data registration unit 115 transmits the scenario data to the server 20 in order to register the scenario data in the scenario DB.

In step S12, the GUI forming unit 111 determines whether or not an operation for instructing the end of the scenario creation GUI has been performed.
When an operation for instructing the end of the scenario creation GUI is performed, it is determined as YES in Step S12, and the scenario creation process ends. On the other hand, if the operation for instructing the end of the scenario creation GUI has not been performed, NO is determined in step S12, and the process proceeds to step S2.

Next, scenario execution processing executed by the terminal device 10 will be described.
[Scenario execution process]
FIG. 7 is a flowchart illustrating a flow of scenario execution processing executed by the terminal device 10. The scenario execution process is started in response to an operation instructing execution of the scenario execution process in the terminal device 10.
In step S21, the scenario data acquisition unit 116 acquires start scene data in the scenario data to be executed.

In step S22, the data execution unit 114 executes a dialogue process defined in the start scene.
In step S23, the scenario data acquisition unit 116 acquires the data of the next scene in the scenario data to be executed.
In step S24, the scene determination unit 117 determines whether or not the next scene is an abstract scene.
If the next scene is not an abstract scene, NO is determined in step S24, and the process proceeds to step S25. On the other hand, if the next scene is an abstract scene, YES is determined in step S24, and the process proceeds to step S27.

In step S25, the scene determination unit 117 determines whether or not the next scene is an end scene in the execution target scenario data.
If the next scene is not an end scene in the scenario data to be executed, NO is determined in step S25, and the process proceeds to step S26. On the other hand, if the next scene is an end scene in the scenario data to be executed, YES is determined in step S25, and the scenario execution process ends.
In step S26, the data execution unit 114 executes a dialogue process defined for the next scene. After step S26, the process proceeds to step S23.

In step S27, the search request unit 118 requests part data or scenario data (execution data request) that conforms to the current situation of the interactive processing and conforms to the scene selection conditions set in the abstract scene. Send to server 20.
In step S28, the data execution unit 114 recursively calls and executes the scenario execution process. After step S28, the process proceeds to step S23.

Next, the operation of the server 20 will be described.
[Scenario creation support processing]
FIG. 8 is a flowchart showing a flow of scenario creation support processing executed by the server 20. The scenario creation support process is started in response to an operation instructing execution of the scenario creation process in the server 20.

In step S 101, the creation data request acquisition unit 212 determines whether a request for creation data for requesting component data selected by the scenario creation GUI has been acquired from the terminal device 10.
When a request for data for creation for requesting the component data selected by the scenario creation GUI is acquired from the terminal device 10, YES is determined in step S101, and the process proceeds to step S102. On the other hand, if a request for creation data for requesting the component data selected by the scenario creation GUI has not been acquired from the terminal device 10, NO is determined in step S101, and the process proceeds to step S104.

In step S102, the creation providing data acquisition unit 213 acquires the component data indicated by the data request acquired by the creation data request acquisition unit 212 from the component DB 222. At this time, when the creation data request unit 213 requests scenario data as part data, the creation data acquisition unit 213 obtains scenario data indicated by the creation data request from the scenario DB 221.

In step S103, the creation data providing unit 214 provides the component data or scenario data acquired by the creation providing data acquisition unit 213 to the terminal device 10 that has requested the creation data.
In step S104, the scenario registration receiving unit 211 determines whether or not scenario data for registration in the scenario DB has been received.
When scenario data is received for registration in the scenario DB, YES is determined in step S104, and the process proceeds to step S105. On the other hand, if no scenario data has been received for registration in the scenario DB, NO is determined in step S104, and the scenario creation support process is repeated.

In step S105, the scenario registration receiving unit 211 registers the received scenario data in the scenario DB 221. Note that the scenario data in this embodiment can include either a normal scene or an abstract scene. After step S105, the scenario creation support process is repeated.

Next, scenario execution support processing executed by the server 20 will be described.
[Scenario execution support processing]
FIG. 9 is a flowchart for explaining the flow of the scenario execution support process executed by the server 20. The scenario execution support process is started in response to an operation instructing execution of the scenario execution support process in the server 20.

In step S 201, the execution data request acquisition unit 215 determines whether a request for part data or scenario data to be inserted into the abstract scene (request for execution data) has been acquired from the terminal device 10.
If a request for part data or scenario data (execution data request) to be inserted into the abstract scene is acquired from the terminal device 10, it is determined YES in step S201, and the process proceeds to step S202. On the other hand, if a request for part data or scenario data to be inserted into the abstract scene (request for execution data) has not been acquired from the terminal device 10, NO is determined in step S201, and the scenario execution support process is repeated. .

In step S202, the execution data search unit 216 sets the parameter indicating the current state of the interactive process indicated by the request for execution data acquired by the execution data request acquisition unit 215, and the scene set as the abstract scene. Based on the selection condition, the part DB 222 or the scenario data 221 is searched for part data or scenario data that matches the current situation of the interactive processing and matches the scene selection condition set in the abstract scene. At this time, the execution data search unit 216 uses the parameter set and parameter value conditions as keys, parameters indicating the current state of the interactive processing, and scenario data that matches the scene selection conditions set in the abstract scene or Search scene data by scoring.

In step S203, the execution data providing unit 217 acquires the scenario data or scene data searched by the execution data search unit 216, which has the highest score.
In step S204, the execution data providing unit 217 provides the acquired scenario data or scene data to the terminal device 10 that has requested the execution data. After step S204, the scenario execution support process is repeated.

As described above, in the dialogue scenario processing system 1 according to the present embodiment, when executing a scenario (dialogue processing scenario) when a character generated on a computer interacts with a human, the current situation of the dialogue processing is adapted. In addition, part data or scenario data that meets the scene selection conditions set in the abstract scene is acquired from the server 20 and executed.
Accordingly, it is possible to more easily increase the variation of the scenario of the interactive process by dynamically calling a part of the scenario from the outside.

[Specific examples of scenarios]
Next, a specific example of a scenario created in the dialogue scenario processing system 1 by the processing as described above will be described. FIG. 10 is a schematic diagram illustrating an example of a scenario of dialogue processing executed in the present embodiment.
In FIG. 10, when the start scene SC1 in the scenario data to be executed is a scene that accepts an utterance of a conversation person, it is assumed that the conversation person utters “I am hungry”.
When the next scene SC2 of the start scene SC1 is an abstract scene and “time” is set as the scene selection condition, the abstract scene SC2 is adapted to the scene selection condition (the parameter of “time” or (Time related parameters are specified) that match the current situation (dialogue flow) of the dialog process of “I am hungry” Selected.

As an example, when the execution time of scenario data is from 8:00 am to 10:00 am, “you can eat breakfast” using the current time (for example, 9:00 am) and “meal” as dialogue content as keys. If the data of the scene SC2a proposing “shop” is searched in the server 20, the scene SC2a is inserted into the abstract scene and executed. For example, a scene is displayed in which a list of shops providing breakfast is displayed together with the question “What kind of breakfast?”

As another example, when the execution time of the scenario data is from 11:00 am to 13:00 am, the current time (for example, 12:00 pm) and “meal” as the conversation content are used as keys. If the data of the scene SC2b proposing “a restaurant where you can eat lunch” is retrieved in the server 20, the scene SC2b is inserted into the abstract scene and executed. For example, a scene is displayed in which a list of shops providing lunch is displayed along with the question “Recommended lunch is curry, but how?”

As described above, according to the dialogue scenario processing system 1 in the present embodiment, different dialogues (scenarios) are generated depending on the execution time of the scenario data for the same scene selection condition (parameter) of “time” in the abstract scene. It becomes possible to execute. Therefore, it is possible to dynamically call a scene or the like to be inserted into an abstract scene, and it is possible to more easily increase variations of the scenario for the interactive process.

[Modification 1]
In the above-described embodiment, when an abstract scene is detected during execution of scenario data, component data or scenario data that matches the situation at the time of dialog execution (matches the scene selection condition and the current status of dialog processing ( However, the present invention is not limited to this.
That is, if the scene selection condition set for the abstract scene is satisfied, the part data or scenario data may be narrowed down based on other conditions. For example, in response to a request for execution scenario data by the search request unit 118, the component data or scenario data may be searched with reference to the user's personal profile (user profile) stored in the server 20. Note that the user's personal profile (user profile) may be stored in the terminal device 10.

Further, in response to a request for execution scenario data by the search request unit 118, not only the user profile of the user who is interacting but also the statistics of the user profile for a plurality of users, the component data or scenario data It is good also as searching.
In addition, it is good also as searching part data or scenario data reflecting both the user profile of the user who is interacting, and the statistics of the user profile in a plurality of users. In this case, the user profile of the user who is interacting and the user profile statistics of multiple users can be weighted and integrated, and the component data or scenario data can be searched by referring to the integrated user profile. is there.

The dialogue scenario processing system 1 configured as described above includes a terminal device 10 and a server 20. The terminal device 10 includes a scene determination unit 117, a search request unit 118, and a data execution unit 114.
The scene determination unit 117 sets a selection condition (for example, a scene selection condition) for selecting data (for example, part data or scenario data) that is an element of the scenario data in the scenario data to be executed. It is determined whether or not included abstract elements (for example, abstract scenes) are included.
When the scene determination unit 117 determines that an abstract element is included, the search request unit 118 stores data that is an element of scenario data corresponding to the abstract element based on the selection condition set for the abstract element. Get from 20.
The data execution unit 114 executes the scenario data to be executed by replacing the abstract element in the scenario data to be executed with the data to be the scenario data corresponding to the abstract element.
As a result, when executing the scenario of the interactive process, it is possible to acquire and execute data of an element that meets the selection condition set in the abstract element from the server 20. Accordingly, it is possible to more easily increase the variation of the scenario of the interactive process by dynamically calling a part of the scenario from the outside.

The search request unit 118 acquires data that is an element of the scenario data corresponding to the abstract element, based on the selection condition and the dialog content in the dialog processing.
As a result, it is possible to acquire data that is an element of scenario data that conforms to the current situation of dialogue processing, and realize more appropriate dialogue contents.

The search request unit 118 acquires data that is an element of the scenario data corresponding to the abstract element based on the individual profile of the conversation person.
As a result, it is possible to acquire and execute scenario data suitable for the characteristics of the individual person who interacts.

The search request unit 118 acquires data that is an element of the scenario data corresponding to the abstract element based on the profiles of a plurality of interactors.
As a result, it is possible to acquire and execute scenario data that matches the tendency of a plurality of users.

Parameters corresponding to the data serving as the element are set in the data serving as the data of the scenario.
The search request unit 118 acquires data that is an element of scenario data that matches the parameter condition set as the selection condition.
Accordingly, it is possible to specify data that is an element of scenario data corresponding to an abstract element by using a parameter set in the data that is an element of scenario data.

The server 20 includes an execution data search unit 216. The execution data search unit 216 searches the data that is the element of the scenario data corresponding to the abstract element by calculating a score based on the parameter set as the selection condition for the data that is the element of the scenario data. .
This makes it possible to specify more appropriate data even when there are a plurality of data serving as elements that meet the selection conditions.

The server 20 includes an execution data search unit 216 and an execution data provision unit 217.
The execution data search unit 216 uses the abstract element based on the selection condition for the abstract element in which the selection condition for selecting the data serving as the scenario data element included in the scenario data to be executed is set. Data that is the element of the scenario data corresponding to is searched.
The execution data providing unit 217 provides the data element of the scenario searched by the execution data search unit 216 to the information processing apparatus.
As a result, when executing the scenario of the interactive process, it is possible to retrieve and execute the data of the element that meets the selection condition set in the abstract element. Accordingly, it is possible to more easily increase the variation of the scenario of the interactive process by dynamically calling a part of the scenario from the outside.

In addition, this invention is not limited to the above-mentioned embodiment, The deformation | transformation in the range which can achieve the objective of this invention, improvement, etc. are included in this invention.
In the above-described embodiment, the configuration of the server 20 is shown as an example. If the dialogue scenario processing system 1 has the function of the server 20 as a whole, the function of the server 20 is divided into a plurality of servers. Or a part of the function of the server 20 can be mounted on the terminal device 10.

Moreover, it is possible to implement this invention combining the example described in the above-mentioned embodiment suitably.
The series of processes described above can be executed by hardware or can be executed by software.
In other words, the functional configuration of FIGS. 3 and 5 is merely an example, and is not particularly limited. That is, it is sufficient if the dialogue scenario processing system 1 has a function capable of executing the above-described series of processes as a whole, and what functional blocks are used to realize this function are particularly shown in FIGS. It is not limited to examples.
In addition, one functional block may be constituted by hardware alone, software alone, or a combination thereof.

When a series of processing is executed by software, a program constituting the software is installed on a computer or the like from a network or a recording medium.
The computer may be a computer incorporated in dedicated hardware. The computer may be a computer capable of executing various functions by installing various programs, for example, a general-purpose personal computer.

The recording medium including such a program is not only configured by the removable medium 821 shown in FIG. 2 distributed separately from the apparatus main body in order to provide the user with the program, but is also incorporated in the apparatus main body in advance. It is comprised with the recording medium etc. which are provided in. The removable medium 821 is configured by, for example, a magnetic disk (including a floppy disk), an optical disk, a magneto-optical disk, or the like. The optical disc is composed of, for example, a CD-ROM (Compact Disk-Read Only Memory), a DVD (Digital Versatile Disc), a Blu-ray (registered trademark) Disc (Blu-ray Disc), and the like. The magneto-optical disk is constituted by an MD (Mini-Disk) or the like. Further, the recording medium provided to the user in a state of being incorporated in advance in the apparatus main body is configured by, for example, the ROM 812 in FIG. 2 in which the program is recorded, the DRAM included in the storage unit 817 in FIG.

In the present specification, the step of describing the program recorded on the recording medium is not limited to the processing performed in chronological order according to the order, but is not necessarily performed in chronological order, either in parallel or individually. The process to be executed is also included.
Further, in the present specification, the term “system” means an overall apparatus configured by a plurality of devices, a plurality of means, and the like.

1 dialogue scenario processing system, 10 terminal device, 20 server, 30 network, 111 GUI formation unit, 112 GUI input reception unit, 113 data generation unit, 114 data execution unit, 115 scenario data registration unit, 116 scenario data acquisition unit, 117 Scene determination unit, 118 search request unit, 121 scenario data storage unit, 122 history data storage unit, 131 flow builder unit, 211 scenario registration reception unit, 212 creation data request acquisition unit, 213 creation provision data acquisition unit, 214 creation Data provision unit, 215 execution data request acquisition unit, 216 execution data search unit, 217 execution data provision unit, 221 scenario DB, 222 parts DB, 223 user profile storage unit, 800 information processing device, 81 CPU, 812 ROM, 813 RAM, 814 bus, 815 input unit, 816 output unit, 817 storage unit, 818 communication unit, 819 drive, 821 a removable media

Claims

An information processing system configured to be able to communicate with an information processing apparatus that executes scenario data of a dialogue process and a server that accumulates data that is an element of the scenario data,
The information processing apparatus includes:
Element determination means for determining whether or not the scenario data to be executed includes an abstract element in which a selection condition for selecting data that is an element of the scenario data is included;
When the element determination unit determines that the abstract element is included, based on the selection condition set in the abstract element, data serving as an element of the scenario data corresponding to the abstract element is stored in the server. Data acquisition means to acquire from,
Data execution means for executing the scenario data to be executed by replacing the abstract element in the scenario data to be executed with the data to be the scenario data corresponding to the abstract element;
An information processing system comprising:
2. The data acquisition unit according to claim 1, wherein the data acquisition unit acquires data that is an element of data of the scenario corresponding to the abstract element based on the selection condition and a dialog content in the dialog processing. Information processing system.
3. The information processing system according to claim 1, wherein the data acquisition unit acquires data that is an element of data of the scenario corresponding to the abstract element based on an individual profile of a conversation person.
The said data acquisition means acquires the data used as the element of the data of the said scenario corresponding to the said abstract element based on the profile of a several dialog person, The any one of Claim 1 to 3 characterized by the above-mentioned. The information processing system described.
In the data serving as the element of the scenario data, a parameter corresponding to the data serving as the element is set,
5. The information according to claim 1, wherein the data acquisition unit acquires data that is an element of data of the scenario that conforms to a parameter condition set as the selection condition. 6. Processing system.
The server
Data search means for searching for data that is an element of the scenario data corresponding to the abstract element by calculating a score based on the parameter set as the selection condition for the data that is an element of the scenario data The information processing system according to claim 5, further comprising:
An element determination unit that determines whether or not an abstract element in which a selection condition for selecting data as an element of the scenario data is included in the scenario data of the interactive process to be executed;
When the element determination unit determines that the abstract element is included, based on the selection condition set in the abstract element, data serving as an element of the scenario data corresponding to the abstract element is transmitted from the server. Data acquisition means for acquiring;
Data execution means for executing the scenario data to be executed by replacing the abstract element in the scenario data to be executed with the data to be the scenario data corresponding to the abstract element;
An information processing apparatus comprising:
A server in an information processing system configured to be able to communicate with an information processing device that executes interactive scenario data and a server that accumulates data that is an element of the scenario data,
For an abstract element in which a selection condition for selecting data to be an element of the scenario data included in the scenario data to be executed is set, based on the selection condition, the abstract element corresponding to the abstract element A data retrieval means for retrieving data that is an element of the scenario data;
Data providing means for providing, to the information processing apparatus, data elements of the scenario searched by the data searching means;
A server comprising:
An information processing method executed by an information processing apparatus that executes interactive scenario data,
An element determination step for determining whether or not the scenario data to be executed includes an abstract element in which a selection condition for selecting data as an element of the scenario data is included;
When it is determined by the element determination step that the abstract element is included, based on the selection condition set in the abstract element, data serving as an element of the scenario data corresponding to the abstract element is transmitted from the server. A data acquisition step to acquire;
A data execution step of executing the scenario data to be executed by replacing the abstract element in the scenario data to be executed with the data to be the scenario data corresponding to the abstract element;
An information processing method comprising:
An information processing method executed by a server in an information processing system configured to be communicable with an information processing apparatus that executes interactive scenario data and a server that stores data serving as an element of the scenario data,
For an abstract element in which a selection condition for selecting data to be an element of the scenario data included in the scenario data to be executed is set, based on the selection condition, the abstract element corresponding to the abstract element A data search step for searching for data that is an element of the scenario data;
A data providing step of providing, to the information processing apparatus, data elements of the scenario searched by the data searching step;
An information processing method comprising:
On the computer,
An element determination function for determining whether or not an abstract element in which a selection condition for selecting data as an element of the scenario data is included in the scenario data of the interactive process to be executed;
When it is determined by the element determination function that the abstract element is included, based on the selection condition set in the abstract element, data serving as an element of the scenario data corresponding to the abstract element is transmitted from the server. A data acquisition function to acquire,
A data execution function for executing the scenario data to be executed by replacing the abstract element in the scenario data to be executed with the data to be the scenario data corresponding to the abstract element;
A program characterized by realizing.
An information processing apparatus that executes interactive processing scenario data and a computer that constitutes a server in an information processing system configured to be able to communicate with a server that stores data serving as an element of the scenario data,
For an abstract element in which a selection condition for selecting data to be an element of the scenario data included in the scenario data to be executed is set, based on the selection condition, the abstract element corresponding to the abstract element A data search function that searches for data that is the element of scenario data,
A data providing function for providing, to the information processing apparatus, data elements of the scenario searched by the data search function;
A program characterized by realizing.