KR20200079703A - Service package authoring method and robot service development system - Google Patents

Abstract

According to an embodiment of the present invention, the robot service development system can comprise: a template generator which generates a template which describes in a declaring manner the flow of robot service requiring multilateral work based on information inputted from a developer; a template analyzer which generates a question for inferring at least one ontology model required for performing the robot service among a plurality of ontology models based on a meta model including metadata provided to each of the plurality of ontology models and the template; and a service package generator which binds the at least one ontology model inferred based on the question and the template, and generates a service package which includes a role description on the flow of the robot service for each of a plurality of roles, interaction description on interactions between the plurality of roles, and knowledge information required for the robot service. The present invention aims to provide a service package generating method and a robot service development system for performing the same, capable of improving the development environment of the developers.

Description

Service package creation method and robot service development system that performs the same {SERVICE PACKAGE AUTHORING METHOD AND ROBOT SERVICE DEVELOPMENT SYSTEM}

The embodiment relates to a method for generating a service package and a robot service development system for performing the same, and more particularly, to a method for generating a service package for a service requiring a multilateral operation and a robot service development system for performing the same.

Recently, research on robots capable of providing various services using intelligent elements such as recognition, movement, manipulation, interaction (HRI), learning, and reasoning has been actively conducted.

Developers developing robot services have configured robot services by defining the behavior of robots that provide services. This method required a considerable amount of work and complexity to develop a single robot service, which prevented developers from easily accessing robot service development. In addition, this method defines only the actions performed by the robot in performing the service, so there is a limitation in expressing the service that requires multi-party work, and the robot type that performs this must be limited, so the robot is developed. Whenever possible, there is a difficulty in developing a new service.

The problem to be solved through the embodiment is to provide a robot service development system and a service package generation method for facilitating the development of a robot service requiring multilateral work, and improving the developer's development environment, and performing the same. .

The robot service development system according to an embodiment for solving the above problems is a template generator that generates a template declaratively describing the flow of a robot service requiring multi-party work based on information input from a developer, and a plurality of ontology A template interpreter for generating a query statement for inferring at least one ontology model necessary for the execution of the robot service among the plurality of ontology models, based on the meta model including the meta data given to each model and the template, and the template A role description for explaining the flow of the robot service for each of the plurality of roles that perform the robot service by binding the template and the template that are inferred based on the query statement, and explaining the interaction between the plurality of roles It may include a service package generator for generating a service package including the interaction description, and knowledge information required for the robot service.

The template may describe the plurality of roles, the actions of each of the plurality of roles, and the interaction between the plurality of roles in the form of metadata.

The service package generator may generate and disassemble and reassemble interactions described in the template into interactions suitable for the domain of the robot service based on the at least one ontology model.

The metadata may declaratively describe the properties of each of the plurality of ontology models.

The role description may include a workflow describing a target flow of the robot service for each role and a condition corresponding to pre-environment information for performing the robot service.

The interaction description may include roles for performing each interaction, start and end conditions of each interaction, and action descriptions for performing each interaction.

The service package may further include a context description describing rules for destruction and generation of contexts used in the robot service.

In addition, the service package generation method of the robot service development system according to the embodiment, based on the information input from the developer, generating a template declaratively describing the flow of the robot service requiring multi-tasking, a plurality of ontology Generating a query statement for inferring at least one ontology model necessary for the execution of the robot service among the plurality of ontology models, based on the meta model including the meta data assigned to each model and the template, the query statement Importing the at least one ontology model among the plurality of ontology models, and binding the at least one ontology model and the template to flow the robot service according to a plurality of roles for performing the robot service. The method may include generating a service package including a role description to describe, an interaction description to describe interaction between the plurality of roles, and knowledge information required for the robot service.

In the generating of the template, based on a work script input from the developer, the description of the plurality of roles, the actions of each of the plurality of roles, and the interaction between the plurality of roles in metadata form And creating a template.

The generating of the service package includes generating and disassembling and reassembling the interactions described in the template into interactions suitable for the domain of the robot service based on the at least one ontology model. can do.

In the service package generating method, the interaction description includes roles for performing each interaction, start and end conditions of each interaction, and action description for performing each interaction, and the template The interactions described in can be generated by disassembling and reassembling. In addition, the metadata may declaratively describe the attributes of each of the plurality of ontology models. In addition, the role description may include a workflow describing a target flow of the robot service for each role and a condition corresponding to pre-environment information for performing the robot service. In addition, the service package may further include a context description describing rules for destruction and generation of contexts used in the robot service.

According to the embodiment, it is possible to facilitate the development of a robot service requiring multi-party work, and further to improve the developer's development environment.

1 schematically illustrates a robot service development system according to an embodiment.
2 shows an example of metadata defining attributes of a sociality model according to an embodiment.
3 is a structural diagram schematically showing a social service template according to an embodiment.
4 shows an example of a social service template according to an embodiment.
5 is a structural diagram schematically showing a social service package according to an embodiment.
6 schematically illustrates a method of generating a social service package in a system for generating a social service package according to an embodiment.
7 illustrates an example of deriving a robot task from an interaction model included in a social service package in the robot service package conversion system according to the embodiment.
8 is a structural diagram schematically showing a social service package according to an embodiment.
9 schematically illustrates a method of generating a robot service package in a system for converting a robot service package according to an embodiment.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art to which the present invention pertains may easily practice. However, the present invention can be implemented in many different forms and is not limited to the embodiments described herein. In addition, in order to clearly describe the present invention in the drawings, parts irrelevant to the description are omitted, and like reference numerals are assigned to similar parts throughout the specification.

Throughout the specification and claims, when a part “includes” a certain component, it means that the component may further include other components, not to exclude other components, unless otherwise stated.

Hereinafter, a method for generating a service package according to an embodiment and a robot service development system performing the same will be described in detail with reference to drawings required. In this document, social service means a robot service based on multilateral work, and robot service means a service performed by a robot. In addition, a multi-party work is a work in which a plurality of subjects participate, and the work is composed of interactions between subjects.

1 schematically illustrates a robot service development system according to an embodiment.

Referring to FIG. 1, the robot service development system 1 according to an embodiment includes a knowledge information database 10, a social service package creation system 20, a work and robot model database 30, and a robot service package conversion system ( 40).

The knowledge information database 10 may include sociality models 11 to 16 and a meta model 17.

The sociality models 11 to 16 are ontology models configured by modularizing knowledge information required for a robot to perform a social service. The sociality models stored in the knowledge information database 10 are target/intention models 11, emotion models 12, personality models 13, and work models 14 according to the type of knowledge information described by each sociality model. ), interaction model 15, user model 16, and the like. The target/intention model 11 may describe knowledge information necessary to achieve a target/intention corresponding to each target/intention. The emotion model 12 may describe knowledge information necessary to express emotions corresponding to each emotion type. The personality model 13 may describe knowledge information necessary to express personality corresponding to each personality type. In addition, the work model 14 may describe knowledge information required to perform a corresponding work for each work type. The interaction model 15 may describe knowledge information required to perform interaction for each interaction. The user model 16 describes knowledge information necessary to perform a corresponding role according to a user performing each role of a social service.

The meta model 17 may include meta data describing attributes of each social model 11 to 16. Typically, meta data is structured data about data, and refers to data that describes properties of other data. Such meta data is data given to data according to a certain rule in order to efficiently find and use the information that is being searched among a large amount of information.

The meta model 17 may include meta data declaratively describing the attributes of each social model 11 to 16, and a specification defining rules for providing meta data to each social model 11 to 16. . As metadata defining the attributes of each sociality model 11 to 16, for example, the knowledge domain, purpose, name, identification information, author information, type (target/intention, emotion of the corresponding sociality model) , Personality, work, interaction, user, etc.) information, update date, etc., the knowledge information model (or sociality model) referenced by the corresponding sociality model, description of the corresponding sociality model, unit of value used in the corresponding sociality model , A class of a corresponding sociality model, properties of a corresponding sociality model, and the like.

2 shows an example of metadata defining attributes of a sociality model according to an embodiment. For example, in FIG. 2, the meta model 17 is the social model classified as the work model 14, the metadata 171 describing the purpose of knowledge information constituting the model, and the knowledge constituting the model. It may include meta data 172 describing what role information is to perform, meta data 173 describing the type of knowledge information constituting the corresponding model, and the like.

The meta model 17 may further include relation information and binding rule information between social models. The relationship information between sociality models is information used when each sociality model wants to generate information associated with other sociality models. For example, the relationship information between the sociality model A, which represents the happiness index as a value between 1 and 100, and the sociality model B, which defines the happiness index as high, normal, and low levels is:'The happiness index over 70 in the sociality model A is It corresponds to the high level of happiness index in social model B'. The binding rules between sociality models define rules for binding values between sociality models. For example, in order to generate an unpleasant index, the rules for integrating the temperature described in social model C and the humidity described in social model D are called binding rules.

The knowledge information database 10 is operated in an open type, so developers upload their sociality model to the knowledge information database 10 through their terminals or update their sociality model stored in the knowledge information database 10. can do. Also, when uploading or updating the sociality model developed by the developers, developers can create meta data about the sociality model and add or update the metamodel 17.

Meanwhile, in FIG. 1, the case where the knowledge information database 10 is included in the robot service development system 1 is illustrated as an example, but the technical spirit of the present invention is not limited thereto. According to another embodiment, the knowledge information database 10 may be implemented as an external database of the robot service development system 1.

Referring back to FIG. 1, the social service package generation system 20 is a template for generating a service package (hereinafter, referred to as a'social service package') of a social service based on a work script input from a developer (hereinafter, It is possible to create a social service package based on social models obtained from the knowledge information database 10 through association between the social service template and the meta model 17. To this end, the social service package generation system 20 may include a template generator 21, a template interpreter 22, and a service package generator 23.

The template generator 21 may generate a social service template of a social service to be developed based on work scripts input from a service developer. The social service template describes necessary information in the form of metadata according to the purpose of the social service to be developed. That is, the social service template is a template that declaratively defines the flow of the corresponding social service by describing the roles required for performing the corresponding social service, the action of each role, and the interaction between the roles in the form of metadata.

As illustrated in FIG. 3, such a social service template may include role description 110, activity information 120, and interaction description (role) for roles that are the main subjects that perform the social service (interaction) ( 130).

3 is a structural diagram schematically showing a social service template according to an embodiment.

Referring to FIG. 3, the role description 110 in the social service template 100 according to an embodiment is information defining a service flow for each role, and includes the liveness, safety, and condition of each role ( condition). Here, the liveness describes the order of interaction and/or activity that each role executes to perform the social service, and safety is a list of contexts that each role must maintain while performing the social service. And the condition may describe the dictionary environment (context list) required for each role to be assigned.

In addition, the action description 120 included in the social service template 100 describes actions that each role should perform alone in the social service, and the interaction description 130 includes two or more to perform the social service. Describe what interactions the roles should perform.

The social service template 100, in addition to the above-described role description 110, action description 120, and interaction description 130, metadata defining attributes such as knowledge information and sociality model required by the social service. It may further include.

4 shows an example of a social service template according to an embodiment.

For example, in the case of configuring the robot service for the education of the dementia elderly as a social service requiring multi-tasking, for example, the service requires two roles: a teacher (R1) and a student (R2). Therefore, the social service template 100 for the education of the elderly with dementia is configured to include a role description 110, an action description 120, and an interaction description 130 for each of the teacher role R1 and the student role R2. do.

Taking the role of the teacher R1 as an example, as the role description 110 for the teacher role R1, interactions and/or actions required for the teacher role R1 (learning guidance, learning preparation, learning performance, review performance) Declaratively the list of contexts that the teacher role R1 should maintain, such as liveness information 111 that defines the sequence of service termination, and "student concentration must be high" and "learning tools must be continuously available." Safety information 112 to be described and condition information 113 to declaratively describe a context list required for the teacher role R1 to be assigned, such as "perform according to a learning schedule," may be included. In addition, the action description 120 for the teacher role R1 may include meta data 121 for a corresponding action, and a start condition 122 and an end condition 123. In addition, the interaction description 130 includes meta data (corresponding roles (beginning role and participating role), action role for interaction) 131 for the corresponding interaction, 131, and corresponding An interaction start condition 132 and an end condition 133 may be included.

In addition, the dementia elderly education social service template 100, in addition to the above-described role description 110, behavior description 120, and interaction description 130, the elderly cognitive education work model, cognitive education learning environment model, elderly users The actor model, the cognitive education teacher intention model, and the like, may further include meta data 140 describing properties of social models required to perform social services for the elderly with dementia.

Referring again to FIG. 1, when the template interpreter 22 generates a social service template by the template generator 21, the template interpreter infers the sociality model necessary for performing the service and inquires it from the knowledge information database 10 You can create a door. The query generated by the template interpreter 22 may be generated based on the meta model 17 so as to bring social models necessary for performing a corresponding social service from the knowledge information database 10. To this end, the template interpreter 22 may share the specification information of the meta model 17 describing the rules for providing metadata for each social model with the meta model 17, and generate a query based on this. have.

The query statement generated by the template interpreter 22 may be written in the form of Sparkle (Simple Protocol and RDF Query Language, SPARQL).

The service package generator 23 infers social models necessary for the execution of a corresponding social service based on the query generated by the template interpreter 22 and the meta model 17 in the knowledge information database 10, and knowledge It can be retrieved and retrieved from the information database 10. The service package generator 23 may import a social model from the knowledge information database 10 using a Web Ontology Web Language (OWL).

The service package generator 23 may generate a social service package through binding of the imported social model and the social service template when social models are imported from the knowledge information database 10. In the process of binding the sociality models and the social service template, the interactions included in the social service template are decomposed and reassembled according to the domain of the social service, and the multilateral work required to perform the social service through such decomposition and reassembly process, , Interaction can be rebuilt to fit the domain of the social service to create a social service package.

According to an embodiment, the social service package for performing a social service includes a role description describing the overall flow of performing the social service for each role, an interaction description describing interactions between roles performing the social service, and a social service It may include a context description that describes the destruction and creation of contexts used in and domain knowledge that specifies knowledge information required for social services.

5 is a structural diagram schematically showing a social service package according to an embodiment.

Referring to FIG. 5, in the social service package 200 according to the embodiment, the role description 210 is defined for a corresponding role, and may include a workflow and a condition. The workflow describes the overall flow of performing the social service for each role in the target unit, and the condition may describe pre-environment information for each role to perform the social service.

In the social service package 200, the interaction description 220 defines a corresponding interaction, and may include a protocol and an action description for the interaction. The protocol describes the roles that perform each interaction (starting and participating roles), and the start and end conditions of each interaction, and the action descriptions describe the actions of each role to perform the interaction. Can be described.

The context description 230 in the social service package 200 may describe rules for the creation and destruction of each context utilized in the social service.

The domain knowledge 240 in the social service package 200 may include knowledge information related to the social service. The domain knowledge 240 may be generated by binding social models in the social service package 200.

The functions of the template generator 21, the template interpreter 22, and the service package generator 23 in the social service package creation system 20 having the above-described structure may include one or more central processing units (CPUs) or other chipsets, It may be performed by a processor implemented as a microprocessor.

6 schematically illustrates a method of generating a social service package in the social service package creation system 20 according to the embodiment. The method for generating the social service package of FIG. 6 may be performed by the social service package creation system 20 described with reference to FIG. 1.

Referring to FIG. 6, the social service package generation system 20 according to an embodiment generates a social service template of a social service to be developed based on work scripts input from a service developer (S10 ). Here, the social service template declaratively defines a flow of a corresponding social service by describing roles required for performing a social service to be developed, an action of each role, and interactions between roles in the form of metadata. It may include a role description, an action description, and an interaction description for a role performing a service.

When the social service template is generated, the social service package generation system 20 interprets the social service template (S11), and generates a query statement for reading social models necessary for service execution from the knowledge information database 10 (S12). ). Then, using the generated query and the meta-model 17 in the knowledge information database 10, the sociality models necessary for performing social services are inferred and taken from the knowledge information database 10 (S13).

The social service package creation system 20 generates social service packages for performing social services based on the imported sociality models and the social service templates created by the developer when social modeling is obtained from the knowledge information database 10 (S14) ).

The social service package generated by the social service package creation system 20 is stored on an external database (not shown) and is a developer who wants to develop a robot service using it or a robot system that wants to perform a robot service using the social service package. Can be distributed.

According to the foregoing, the method for generating a social service package according to an embodiment, unlike the conventional method in which a service package is generated by individually describing the work of the robot, roles required for a developer to perform a social service he or she wants to develop When the template is created by intuitively defining the actions of each role and the interaction between roles, a service package for performing a social service can be automatically generated based on the template. Accordingly, it is possible to improve the convenience and accessibility of developers by simplifying the process of developing a service package, and thereby, to actively induce developers to participate in service package development for a social service.

In addition, unlike the existing service package that only specified for one subject, it is specified for each of the roles that perform multilateral tasks in the service package, so creating a service package regardless of a specific role, environment, robot, etc. Possible, there is an effect to increase the compatibility of the service package.

Meanwhile, the social service package defines a service flow for each role performing a social service, and defines an action of roles as a multi-party operation between roles, that is, interaction. Therefore, when a robot wants to perform a specific role using the corresponding social service package, there is a need for a process of converting actions described as interaction into robot tasks performed by a real robot.

Referring again to FIG. 1, the task and robot model database 30 and the robot service package conversion system 40 convert service actions that are described as interactions in a social service package into robot tasks performed by a real robot to generate a service package. It is to understand the function to do.

The work and robot model database 30 may include one or more robot profiles 31, actor models 32, and work models 33.

The robot profile 31 is a profile for allowing the robot to drive its own sensor and behavior module, and may define an behavior module for performing a corresponding function for each robot function. For example, the robot profile 31 of the robot A uses the speech to text (STT) module as the behavior module for the robot A to perform the speech recognition function, and the text to speech (TSS) for the robot to perform the speech function. ) May include information describing the use of the module as an action module.

The robot profile 31 may be defined for each of the robot types supported by the robot service development system 1. For example, if the robot service development system 1 supports robot type A and robot type B, the job and robot model database 30 includes robot profiles 31 defined for robot time A and robot type B respectively. It may include.

The actor model 32 may describe a function used by the robot to perform each action according to a role given to the robot among roles performing social services. For example, when a robot is given a teacher role and the robot performs an action of recognizing a student's learning content, the actor model 32 defines that the robot performs a corresponding action using a speech recognition function. Information may be included.

The actor model 32 may be defined for each of the robot types supported by the robot service development system 1, like the robot profile 31.

The work model 33 describes work plans that are executable to perform a specific function in the robot. The work model 33 may be defined and used for each function supported by the robot. For example, if the robot supports the mobile function and the voice recognition function, the work and robot model database 30 may include a work model 33 for the mobile function and a work model 33 for the voice recognition function. have.

Meanwhile, in FIG. 1, the case where the work and robot model database 30 is included in the robot service development system 1 is illustrated as an example, but the technical spirit of the present invention is not limited thereto. According to another embodiment, the work and robot model database 30 may be implemented as an external database of the robot service development system 1.

Referring again to FIG. 1, the robot service package conversion system 40 is a system that performs a function of converting a social service package into a robot service package to be applied to an actual robot. The robot service package conversion system 40 may include a robot task generator 42 and a service package converter 43.

The social service package interpreter 41 may bring the social service package of the corresponding social service from an external database (not shown) when the social service to be performed by the robot is determined. In addition, when an actor for each role performing a social service package is determined, it is possible to infer the actions actually performed by the robot from the social service package. That is, the social service package interpreter 42 may decompose interactions expressed as multi-party tasks in the social service package into action units, and infer only actions that the robot actually needs to perform according to the role assigned to the robot.

When the actions to be performed by the robot are extracted by the social service package interpreter 41, the robot task generator 42 refers to the corresponding robot profile 31 and the actor model 32 to perform each action by the robot. In order to deduce the function to be used and the action module actually used by the robot to perform the corresponding function, based on this, a work plan to be actually performed by the robot can be obtained from the work model 33.

7 illustrates an example in which the robot service package conversion system 40 according to an embodiment derives a robot task from interactions included in the social service package.

7 as an example, when the robot service package conversion system 40 is assigned a teacher role to the robot, an interaction model 220-1 including a teacher role among interactions defined in the social service package 200 By interpreting, we infer the actions that the robot in the role of teacher should perform among the actions (A1, A2) constituting the interaction. In the case of FIG. 7, the teacher role learning content delivery (A1) and the learning content recognition recognition (A2) may be extracted as actions that the robot should perform. Subsequently, the robot service package conversion system 40 is linked with the robot profile 31 and the actor model 32 stored in the work and robot model database 30, and the work plans corresponding to each action that the robot needs to perform ( plan1, plan2) can be taken from the working model 33.

The service package converter 43, when the social service package interpreter 41 and the robot task generator 42 interpret the social service package based on the robot profile 31 and the actor model 32 to obtain the robot's work plans Based on this, the social service package can be converted into a service package for providing a service on the robot (hereinafter referred to as a'robot service package').

8 is a structural diagram schematically showing a social service package according to an embodiment.

Referring to FIG. 8, the service package converter 43 refers to the role assigned to the robot, and describes the role description 210 defined by the role unit in the social service package 200 in the service description 310 of the robot service package 300. ). In addition, the service package converter 43 refers to the work plans obtained by the robot task generator 42, and the interaction service 220 defined as a multi-party task in the social service package 200 is provided to the robot service package 300. To the job description 320 of the, and the context description 230 and domain knowledge 240 defined in the social service package 200 to the context description 330 and domain knowledge 340 of the robot service package 300 Can be converted.

The service description 310 of the robot service package 300 includes a workflow and a condition defined in a service unit, and the job description 320 can define work plans for performing a corresponding robot service. In addition, the context description 330 describes rules for the creation and destruction of each context utilized in the robot service, and the domain knowledge 340 may include knowledge information related to the robot service.

The functions of the social service package interpreter 41, the robot task generator 42, and the robot service package converter 43 in the robot service package conversion system 40 of the above-described structure are one or more central processing units (CPUs). Or other chipset, microprocessor, or the like.

9 schematically illustrates a method of generating a robot service package of the robot service package conversion system 40 according to the embodiment. The method for generating the robot service package of FIG. 9 may be performed by the robot service package conversion system 40 described with reference to FIG. 1.

Referring to FIG. 9, the robot service package conversion system 40 according to an embodiment reads a social service package of a social service to be performed by the robot from external data (S20), interprets it (S21), and generates a social service package in the social service package. Based on the roles assigned to the robot from the interactions defined as multilateral work, only the actions that the robot must actually perform are inferred.

When the actions to be actually performed by the robot are extracted from the social service package, the robot service package conversion system 40 refers to the corresponding robot profile 31 and the actor model 32 to be used by the robot to perform each action. The function and the behavior module of the robot actually used to perform the corresponding function are inferred, and based on this, the robot actually performs a task to be performed (S22). Then, the social service package is converted into a robot service package for providing a service on the robot based on the imported robot tasks (S23).

The robot service package thus generated may be plugged and played into a robot system that performs a service.

According to the above, the robot service package generation method according to the embodiment automatically extracts only actions corresponding to a role given to the robot from the interaction defined as a multi-party operation in the social service package, and the robot needs to perform the operation based on this Defines automatically to create a robot service package. Accordingly, when a robot wants to provide a service that performs a social service that requires a multi-party operation by performing a specific role, it facilitates the development of a service package to be applied to the robot, reducing the burden on the developer, and thereby the robot. The convenience and accessibility of developers for service development can be improved.

Meanwhile, in the above-described embodiment, the case where the robot service development system 1 exists separately from the robot system (not shown) is described as an example, but the technical spirit of the present invention is not limited thereto. In another embodiment, at least some components constituting the robot service development system 1 may be implemented and used in the robot. For example, the aforementioned robot service package conversion system 40 may be implemented and used inside the robot. In this case, when the social service to be performed by the robot and his role in the corresponding service are determined, the robot automatically converts the corresponding social service package through the robot service package conversion system 40 into a robot service package suitable for his role. You can convert it and plug and play it into your own robotic system. For example, the above-described social service package creation system 20 and robot service package conversion system 40 may be implemented and used inside the robot. In this case, the robot automatically generates a social service package using a template declaratively specified for a social service that needs to be performed through the social service package creation system 20, and through the robot service package conversion system 40 After converting it back into a robot service package for your role, you can plug and play it into your robot system.

The embodiment of the present invention is not implemented only through the apparatus and/or method described above, and a program recorded in a recording medium or a recording medium in which the program is recorded is realized in order to realize a function corresponding to the configuration of the embodiment of the present invention. It may be implemented through, such an implementation can be easily implemented by those skilled in the art to which the present invention belongs from the description of the above-described embodiment.

Although the embodiments of the present invention have been described in detail above, the scope of rights of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concept of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

1: Robot service development system
10: Knowledge information database
11~16: Sociality model
17: meta model
20: social service package creation system
21: Template Generator
22: Template interpreter
23: Service Package Generator
30: Work and robot model database
31: robot profile
32: actor model
33: working model
40: robot service package conversion system
41: social service package interpreter
42: robot task generator
100: social service template
200: social service package
300: robot service package
.

Claims (14)

Template generator that generates a template declaratively describing the flow of a robot service that requires multi-party work based on information input from a developer,
A template interpreter that generates a query statement for inferring at least one ontology model necessary to perform the robot service among the plurality of ontology models, based on the meta model and the template including meta data assigned to each of the plurality of ontology models. , And
Role description for explaining the flow of the robot service for each of the plurality of roles for performing the robot service by binding the at least one ontology model inferred based on the query statement and the template, and interaction between the plurality of roles A robot service development system including a service package generator for generating a service package including an interaction description to be described and knowledge information required for the robot service. According to claim 1,
The template is a robot service development system, characterized in that the plurality of roles, the actions of each of the plurality of roles, and the interaction between the plurality of roles are described in the form of metadata. According to claim 2,
The service package generator, based on the at least one ontology model, decomposes and reassembles interactions described in the template into interactions suitable for the domain of the robot service to generate the service package. Development system. According to claim 1,
The metadata is a robot service development system, characterized in that declaratively describes the properties of each of the plurality of ontology models. According to claim 1,
The role description, the robot service development system comprising a workflow for describing the target flow of the robot service for each role and a condition corresponding to pre-environment information for performing the robot service. According to claim 1,
The interaction description includes a role for performing each interaction, a start condition and an end condition for each interaction, and a robot service development system, characterized in that it includes an action description for performing each interaction. According to claim 1,
The service package,
A robot service development system further comprising a context description describing rules for the destruction and generation of contexts used in the robot service. In the service package generation method of the robot service development system,
Generating a template declaratively describing the flow of a robot service that requires multi-party work based on information input from a developer,
Generating a query statement for inferring at least one ontology model required to perform the robot service among the plurality of ontology models, based on the template and the meta model including meta data assigned to each of the plurality of ontology models,
Obtaining the at least one ontology model among the plurality of ontology models using the query statement, and
A role description for explaining the flow of the robot service for each of the plurality of roles for performing the robot service by binding the at least one ontology model and the template, an interaction description for explaining interactions between the plurality of roles, and the A service package generating method comprising the step of generating a service package including knowledge information required for a robot service. The method of claim 8,
The step of generating the template,
And generating the template describing metadata of the plurality of roles, actions of each of the plurality of roles, and interactions between the plurality of roles based on a work script input from the developer. Method of creating a service package, characterized in that. The method of claim 9,
The step of generating the service package,
And generating and disassembling and reassembling the interactions described in the template into interactions suitable for the domain of the robot service based on the at least one ontology model to generate the service package. . The method of claim 10,
The interaction description includes roles for performing each interaction, a start condition and an end condition for each interaction, and an action description for performing each interaction, and decomposes the interactions described in the template And re-assembled to generate the service package. The method of claim 8,
The meta data declaratively describes the properties of each of the plurality of ontology models. The method of claim 8,
The role description includes a workflow for describing a target flow of the robot service for each role and a condition corresponding to pre-environment information for performing the robot service. The method of claim 8,
The service package,
A service package generation method further comprising a context description describing rules for destruction and generation of contexts used in the robot service.

Images