KR102143604B1 - Method and software platform for generating of service profile - Google Patents

Abstract

The service profile generation method according to the embodiment includes receiving selection information for selecting a service type and an authentication method, hierarchically classifying a plurality of services constituting a cloud service, and properties required by each of the plurality of services. Obtaining a property list corresponding to the service type, obtaining an authentication data list corresponding to the authentication method, and obtaining the property list and the authentication data list from a cloud service ontology that has defined (property) and converted into a library. Creating a service profile template using the service profile template, receiving the specification data inserted into the service profile template, and when the creation of the service profile template is completed, the service profile template is used to build a cloud service interface in the system. It may include the step of creating a service profile to be used.

Description

How to create a service profile and a software platform that performs it {METHOD AND SOFTWARE PLATFORM FOR GENERATING OF SERVICE PROFILE}

The embodiment relates to a service profile generation method and a software platform that performs the same, and more particularly, to a service profile generation method that supports the use of a cloud service in a robot system, and a software platform that performs the same.

In order to effectively utilize the intelligent elements such as robot recognition, movement, manipulation, interaction (Human-Robot Interaction, HRI), learning, and inference for various services, the intelligent elements of the robot are integrated entirely and cloud services are provided as needed. It requires an advanced intelligence system that can utilize external expertise and intelligence resources.

However, since standardization of an interface for using a cloud service in a robot is not in progress, a developer has a difficulty in creating a new processing unit corresponding to each cloud service to be used in the robot.

A problem to be solved through an embodiment of the present invention is to provide a service profile generation method capable of simplifying the construction of a cloud service interface of a robot and a software platform for performing the same.

The software platform according to the embodiment for solving the above problems hierarchically classifies a plurality of services constituting a user interface and a cloud service, and defines a property required by each of the plurality of services to form a library. A cloud service ontology, receiving selection information for selecting a service type and an authentication method through the user interface, obtaining a property list corresponding to the service type from the cloud service ontology based on the selection information, and the authentication method A template generator for generating a service profile template using the authentication data list corresponding to and the property list, and when the creation of the service profile template is completed by the specification data received through the user interface, the service profile template is It may include a service profile generator for generating a service profile used to build a cloud service interface in the system.

The property list may include a service URL and a service method of a corresponding service, and a plurality of arguments required to use the corresponding service.

The cloud service ontology includes argument information of each of the plurality of arguments, and the argument information may include at least one of a mapping rule, a graphic library (GL) display name, an argument name, and a request level.

The mapping rule may include rule information for linking with data of a cloud service side with respect to a corresponding argument, and rule information for linking with the system.

The specification data may be specification data for each property included in the property list and each authentication data included in the authentication data list.

In addition, the service profile generation method according to the embodiment includes receiving selection information for selecting a service type and an authentication method, classifying a plurality of services constituting a cloud service hierarchically, and requiring each of the plurality of services. Obtaining a property list corresponding to the service type, obtaining an authentication data list corresponding to the authentication method, the property list and the authentication data from a cloud service ontology that has defined and converted a property to be library Creating a service profile template using a list, receiving specification data inserted into the service profile template, and when the creation of the service profile template is completed, constructing a cloud service interface in the system using the service profile template It may include the step of creating a service profile used for.

The receiving of the specification data may include receiving specification data for each property included in the property list and each authentication data included in the authentication data list.

According to an embodiment, it is possible to simplify the construction of the cloud service interface in the robot, thereby reducing the development cost, and thus, software development for providing the cloud service in the robot may be activated.

1 schematically illustrates a software platform for generating a service profile according to an embodiment.
2 illustrates an example of a cloud service ontology according to an embodiment.
3A is a diagram illustrating a configuration of argument information provided by a cloud service ontology according to an embodiment.
3B is a diagram for describing the mapping rule of FIG. 3A.
3C shows an example of the mapping rule of FIG. 3A.
4 illustrates an example of binding arguments of a cloud service in a cloud service ontology according to an embodiment.
5A illustrates an example of a cloud service authentication data model according to an embodiment.
5B is a diagram illustrating an example of acquiring information to be included in a service profile template in a software platform according to an embodiment.
5C illustrates an example of a service profile template according to an embodiment.
6 illustrates an example of creating a service profile template according to an embodiment.
7 schematically illustrates a method of generating a service profile according to an embodiment.
8 schematically shows a cloud service platform of a robot system according to an embodiment.
9A illustrates an example of a request model configuring a cloud service interface according to an embodiment.
9B is a diagram illustrating an example of a response model configuring a cloud service interface according to an embodiment.
10 schematically illustrates a method of providing a cloud service in a robot system 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 of ordinary skill in the art may easily implement the present invention. However, the present invention may be implemented in various forms and is not limited to the embodiments described herein. In the drawings, parts irrelevant to the description are omitted in order to clearly describe the present invention, and similar reference numerals are assigned to similar parts throughout the specification.

Throughout the specification and claims, when a certain part "includes" a certain component, it means that other components may be further included rather than excluding other components unless otherwise stated.

In order to effectively utilize the intelligent elements such as recognition, movement, manipulation, HRI, learning, and inference of the robot in various services, the intelligent elements of the robot are integrated entirely, and if necessary, use external expertise and intelligent resources by linking with the cloud. It requires an advanced intelligent system that can be used.

According to an embodiment, a service profile for providing a cloud service in a robot system is predefined through the ontology of a cloud service, and a method and platform for providing a cloud service in the robot system can be provided using this. have.

Hereinafter, a method of generating a service profile and a software platform performing the same according to an embodiment will be described in detail with reference to FIGS. 1 to 7.

1 schematically illustrates a software platform for generating a service profile according to an embodiment, and is for generating a service profile for providing a cloud service in a robot system.

Referring to FIG. 1, a software platform 1 for generating a service profile according to an embodiment includes a cloud service ontology 11, a template generator 12, a user interface 13, and a service profile generator 14. ) Can be included.

The cloud service ontology 11 hierarchically classifies services that can be provided by a cloud service, defines properties required by the service for each layer, and converts them into a library.

As properties included in the cloud service ontology 11, a service URL and a service method (or HTTP method) for providing a service, and arguments necessary to use each service function may be included.

2 shows an example of a cloud service ontology 11 according to an embodiment.

Referring to FIG. 2 as an example, the cloud service ontology 11 classifies services provided by the cloud service 100 hierarchically. The cloud service 100 is classified into sub-services such as cloud software 110, cloud platform 120, and cloud infrastructure 130, and the cloud software 110 service is calendar Sub-services, such as a calendar events service 111 and a geoInfomatics service 112 may be included. In addition, the calendar event service 111 may again include a calendar events make service 111-1, a calendar event remove service 111-2, and the like as sub-services.

In this way, the cloud service ontology 11 may layer services included in the cloud service 100 into an upper service and a lower service concept, and define and list properties required by the service for each layer. Referring to FIG. 2 as an example, in the cloud service ontology 11, a service URL (URL string) (P11) and a service method (HTTP method) (P12) providing the cloud service 100, and a calendar event creation service 111-1 ), the properties required to use (e.g., Calendar ID (A11), End Date (A12), Start Date (A13), Summary (A14), etc.) are defined. Can be.

On the other hand, the cloud service ontology 11 defines each factor for the factors (A11 to A14) required to use the service among the properties (P11, P12, A11 to A14) defined for the cloud service 100 It may further include argument specification.

3A is a diagram illustrating an example of argument information provided by the cloud service ontology 11 according to an embodiment, FIG. 3B is a diagram for explaining the mapping rule of FIG. 3A, and FIG. 3C is an example of the mapping rule Is shown.

Referring to FIG. 3A, for example, the argument information 200 of each argument includes a mapping rule 210 for designating an application range of the argument, and a GL (graphic library) expression to be bound. It may include a GL expression name (220) for designating an argument, an argument name (230) for designating a detailed position of an argument, and a request level (240).

Referring to FIG. 3B, the mapping rule 210 may include a cloud mapping rule 211 and a system mapping rule 212. The cloud mapping rule 211 includes rule information for linking with data on the cloud service side, and information related to body mapping 211-1 and header mapping 211-2 ), URL mapping-related information 211-3, and the like. 3C, information related to body mapping 211-1 includes a body key value and data type (LIST, OBJECT, String, Integer, Float, etc.), and information related to header mapping 211 -2) includes a header key value, and the like, and the information 211-3 related to URL mapping may include a query key value or a change target value of the URL.

Further, the system mapping rule 212 may include rule information for linking with a system to be linked (eg, a robot system). The system mapping rule 212 may include information 212-1 related to a fixed value and information 212-2 related to a floating value (eg, a linked system message key value).

Arguments defined for each service constituting a cloud service may be bound as a cloud argument together with the argument information, and may be included in the cloud service ontology 11.

4 illustrates an example of binding arguments of a cloud service in a cloud service ontology 11 according to an embodiment. In addition, FIG. 5 schematically shows the configuration of cloud factors included in the cloud service ontology 11 according to an embodiment.

Referring to FIG. 4, in the hierarchical structure of the cloud service ontology 11, arguments A11 to A14 required for each service may be bound to the cloud argument CA100 based on the argument binding property P21. In this case, the arguments of the services belonging to the lower level may include not only the arguments defined for themselves, but also the arguments defined in the own higher level service. 4, for the calendar event creation service 111-1, an argument A11 defined in the calendar event service 111, which is a higher level service of the calendar event creation service 111-1, may also be bound together. .

Again, referring to FIG. 1, the template generator 12 receives selection information for selecting a service type and an authentication method from a developer through the user interface 13, and based on the received selection information, the service of the cloud service You can create templates for profile creation.

The template generator 12 can obtain a property list required for service implementation from the cloud service ontology 11 based on the selection of a service type to be used to provide a corresponding service through the user interface 13 and an authentication method therefor. have. Also, based on the authentication method selected by the worker and the property list acquired from the cloud service ontology 11, service profile templates for providing a corresponding service function may be generated.

Hereinafter, a method of generating a template for generating a service profile in the template generator 12 according to an embodiment will be described in detail with reference to FIGS. 5A to 5C.

5A illustrates an example of a cloud service authentication data model according to an embodiment.

As an authentication method used for authentication of a cloud service, an open authentication (Open Authorization 2, OAuth2) method 310, an application programming interface (API) key authentication method 320, an open API authentication method 330, etc. This can be. Referring to FIG. 5A, the authentication data model 300 used for authentication of a cloud service is configured to classify authentication data used for authentication according to authentication methods 310, 320, and 330 used for authentication. For example, in the case of the OAuth2 method 310, a client secret (311), a client key (312), and a scope may be included in the authentication data model 300 as authentication data. Further, for example, in the case of the API key authentication method 320, the API key 321 may be included in the authentication data model 300 as authentication data.

The template generator 12 may obtain an authentication data list corresponding to the selected authentication method when selection information on the authentication method is received from the developer using the authentication data model 300.

Meanwhile, in an embodiment, the authentication data model 300 may be included in the cloud service ontology 11 so that the template generator 12 can refer to it when generating the template.

5B illustrates an example of obtaining information to be included in a service profile template by the template generator 12 according to an embodiment.

Referring to FIG. 5B as an example, the template generator 12 creates a calendar event from the cloud service ontology 11 as the Google Calendar Events Insert service 410 is selected as the service type (111-1). ) Obtain a list of properties (P11 to P13, A11 to A14) defined for the service. In addition, as the template generator 12 selects the OAuth2 420 as the authentication method of the Google Calendar Events Insert service 410, the OAuth2 420 is required from the authentication data model 300. A list of authentication data AK11 to AK13 is obtained.

When the properties of the selected service (P11-P13, A11-A14) and authentication data (AK11-AK13) are obtained, the template generator 12 can create a service profile template by inserting them into a preset service profile template format. have.

5C illustrates an example of a service profile template generated by a template generator according to an embodiment, and is a service profile for generating a service profile 510 corresponding to a calendar event creation service among service profiles 500 of a calendar service. The template 511 is shown as an example.

5C as an example, as the Google Calendar Events Insert service is selected as the service type and the OAuth2 method is selected as the authentication method, the template generator 12 provides a calendar event from the cloud service ontology 11 The property list defined for the creation service 111-1 is read, and the authentication data list defined for the OAuth2 method is read from the authentication data model 300. Then, a service profile template 511 of Google's calendar event insertion service is generated based on the property list of the cloud service and the authentication data list. The service profile template 511 created in this way includes specifications 511-1 related to service functions such as a service URL and a service method (HTTP method), and authentication data (client key, client password, scope, refresh token). )), and a data linkage method for each argument (511-3).

Again, referring to FIG. 1, when the service profile template is generated by the template generator 12 as shown in FIG. 5C, the service profile generator 14 stores data to be inserted into the service profile template through the user interface 13. Input can be received. In addition, when the creation of the service profile template is completed, a service profile including specification information of a corresponding cloud service interface may be generated using this.

6 shows an example of creating the service profile template of FIG. 5C.

6, when the service profile generator 14 receives service function-related data (service URL, service method (HTTP method)) from the developer through the user interface 13, the service profile generator 14 It can be inserted into the service function specification part 511-1. In addition, when the service profile generator 14 inputs data necessary for authentication (client key, client password, scope, refresh token) from the developer through the user interface 13, the service profile generator 14 receives the authentication-related specification part of the service profile template 511. It can be inserted in (511-2). In addition, the service profile generator 14, when data related to the data linkage method between arguments is input from the developer through the user interface 13, it is added to the specification part 511-3 related to the data linkage method of the service profile template 511. Can be inserted.

In this way, when the description of the specification parts 511-1, 511-2, and 511-3 required for service profile creation by the developer is completed, the service profile generator 14 is the service profile template 511 that has been created. You can create a service profile using.

7 schematically illustrates a method of generating a service profile according to an embodiment. The service profile generation method of FIG. 7 may be performed by the software platform described with reference to FIGS. 1 to 6.

Referring to FIG. 7, in order to create a service profile of a cloud service, a software platform 1 according to an embodiment shows a service type and authentication method of a cloud service that a developer intends to service in a robot system through a user interface 13. Selection information is received (S10). In addition, a property list required for service implementation is obtained from the cloud service ontology 11 based on the received selection information, and an authentication data list required for authentication is obtained from the authentication data model 300 (S11).

Thereafter, the software platform 1 generates a service profile template to be used for service profile generation by using the property list and the authentication data list obtained through the step S11 through the template generator 12 (S12). Then, the specification information to be inserted into the service profile template through the user interface 13 is received from the developer (S13).

Thereafter, when the creation of the service profile template is completed based on the specification information received from the developer, the software platform 1 generates a service profile used to build a corresponding cloud service interface in the robot system using this (S14). . The service profile generated in this way may be transmitted to the robot system and used to construct a cloud service interface for providing a corresponding cloud service within the robot system.

As described above, in the embodiment, properties required for cloud services are ontology, and the developer simply selects the service type and authentication method in relation to the cloud service to be developed, as shown in FIG. Templates for profile creation can be automatically generated. In addition, the developer can create a service profile used for building a cloud service interface by writing a simple specification as shown in FIG. 6 in this template.

On the other hand, the service profile created by the above-described software platform (1) is packaged as a service package along with actions for constructing a scenario of a corresponding cloud service, information on the order of performing this, and knowledge related to cloud services. After that, it can be delivered to the robot system that wants to build the interface of the corresponding cloud service.

Hereinafter, a cloud service platform for providing a cloud service in a robot system according to an embodiment will be described in detail with reference to FIGS. 8, 9A, and 9B.

8 schematically shows a cloud service platform of a robot system according to an embodiment.

Referring to FIG. 8, a cloud service platform 2 of a robot system according to an embodiment includes a cloud interface manager 20, a cloud service interface 30, and a cloud service agent. agent, 40).

The cloud interface manager 20 receives the service profile 24 of the cloud service to be serviced by the robot system, and uses it to provide a cloud service interface 30 and a cloud service agent ( 40) can be generated.

The cloud interface manager 20 may include a cloud service ontology 21, a cloud service instance parser 22, an authentication adapter 23, and a service profile 24.

The cloud service ontology 21 is the same as the cloud service ontology 11 used to create a service profile in the software platform 1 described above, and the service profile 24 is created by the software platform 1 described above. The cloud interface manager 20 may distribute and use a service package of a cloud service through a package initiator 50.

The cloud service instance parser 22 may parse the service package of the cloud service distributed through the package initiator 50 to obtain cloud service instances required to provide a cloud service in the robot system.

Cloud service instances acquired from the cloud service instance parser 22 may be used as instances for the cloud interface manager 20 to create the cloud service interface 30 and the cloud service agent 40.

The authentication adapter 23 supports the cloud service platform 2 to be authenticated in the cloud server 3 providing the corresponding cloud service by referring to the authentication-related specification part included in the service profile 24.

The cloud service interface 30 may support an interface between a cloud server 3 providing a corresponding cloud service and a robot system, that is, a cloud service agent 40 in the robot system or another agent.

The cloud service interface 30 includes a service model (31), a request model (32), a response model (33), a system interface (34), and a cloud interface (35). ), and a service interface protocol mapper (36).

The service model 31 may include a service model for a cloud service.

The request model 32 is a mapping rule between a robot system, that is, a system request message received from the cloud service agent 40 or another agent in the robot system, and an HTTP request message received from the cloud server 3 It may include.

9A illustrates an example of a request model 32 configuring the cloud service interface 30 according to an embodiment.

Taking FIG. 9A as an example, the request model 32 may include the acquisition models 32-1 and 32-2 for each cloud factor included in the service profile 24. In addition, each argument model (32-1, 32-2) includes location information (32-11) to which the corresponding argument is mapped in the system request message, and location information (32-12) to be mapped in the HTTP request message. can do.

Again, referring to FIG. 8, the response model 33 is a robot system, that is, a system response message received from the cloud service agent 40 or another agent in the robot system, and a system response message received from the cloud server 3. May contain mapping rules between HTTP response messages.

9B illustrates an example of a response model 33 configuring the cloud service interface 30 according to an embodiment.

Referring to FIG. 9B as an example, the response model 33 may include a factor model 33-1 for each cloud factor included in the service profile 24. In addition, each argument model 33-1 may include location information 33-11 to which a corresponding argument is mapped in a system response message, and location information 33-12 to be mapped within an HTTP response message.

The system interface 34 may perform an interface function with a robot system, that is, a cloud service agent 40 or other agents within the robot system in the cloud service interface 30. The cloud service interface 30 may transmit and receive system request/response messages with the cloud service agent 40 or other agents through the system interface 34.

The cloud interface 35 may perform an interface function with the cloud server 3 in the cloud service interface 30. The cloud service interface 30 may transmit and receive HTTP request/response messages with the cloud server 3 through the cloud interface 35.

The service interface protocol mapping unit 36 includes system request/response messages received through the system interface 34 and a cloud interface based on the service model 31, the request model 32, and the response model 33. 35) can perform conversion between HTTP request/response messages received.

The cloud service agent 40 may manage and process tasks related to a corresponding cloud service within the robot system.

The package initiator 50 may distribute the cloud service ontology 21 and the service profile 24 on the Internet, and may transmit them to the cloud interface manager 20.

As described above, when the cloud service interface 30 and the cloud service agent 40 are built in the robot system using the service profile, the cloud service agent 40 connects to the cloud server 3 and Service can be provided.

10 schematically illustrates a method of providing a cloud service in a robot system according to an embodiment.

Referring to FIG. 10, the package initiator 50 of the robot system according to the embodiment receives a service profile of a cloud service from the Internet and transmits it to the cloud interface manager 20 (S20).

Accordingly, the cloud interface manager 20 creates and executes the cloud service agent 40 using the received service profile and the cloud service ontology (S21).

Thereafter, when a cloud service request is received from another agent 60 in the robot system (S22), the cloud service agent 40 requests the cloud server 3 to execute a corresponding cloud service (S23). Then, a response to the execution of the requested cloud service is received from the cloud server 3 (S24), and the result value of the request is transmitted to the other agent 60 (S25).

As described above, in the embodiment, a service profile-based cloud service interface is built in the robot system, so that other agents can link with the cloud service.

The embodiments of the present invention are not implemented only through the apparatus and/or method described above, but a program recorded on a recording medium or a recording medium on which the program is recorded in order to realize a function corresponding to the configuration of the embodiment of the present invention. It may be implemented through, and such implementation can be easily implemented by an expert in the technical field 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 the present invention is not limited thereto, and various modifications and improvements by 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.

Claims (10)

User interface,
A cloud service ontology in which a plurality of services constituting a cloud service are hierarchically classified, and properties required by each of the plurality of services are defined and converted into a library,
Receive selection information for selecting a service type and an authentication method through the user interface, obtain a property list corresponding to the service type from the cloud service ontology based on the selection information, and authentication data corresponding to the authentication method A template generator for generating a service profile template using a list and the property list, and
When the creation of the service profile template is completed based on the specification data received through the user interface, comprising a service profile generator for generating a service profile using the service profile template,
The service profile is used to build a cloud service interface within a system to service a corresponding cloud service,
The template generator obtains the authentication data list based on the selection information from an authentication data model configured to classify data required for authentication for each of a plurality of authentication methods, and uses the authentication data list to obtain authentication data of the service profile template. A recording medium recording the software platform, creating a specification part for In claim 1,
The property list is a recording medium recording a software platform including a service URL and a service method of a corresponding service, and a plurality of arguments required to use the corresponding service. In paragraph 2,
The cloud service ontology includes argument information of each of the plurality of arguments,
The argument information is a recording medium recording a software platform including at least one of a mapping rule, a display name, an argument name, and a request level. In paragraph 3,
The mapping rule is a recording medium recording a software platform including rule information for linking with data of a cloud service side with respect to a corresponding argument, and rule information for linking with the system. The method of claim 1,
The specification data is a recording medium for recording a software platform which is specification data for each property included in the property list and each authentication data included in the authentication data list. Receiving selection information for selecting a service type and authentication method,
Classifying a plurality of services constituting a cloud service hierarchically, defining properties required by each of the plurality of services, and obtaining a property list corresponding to the service type from a cloud service ontology that has been converted into a library step,
Obtaining an authentication data list corresponding to the authentication method,
Generating a service profile template using the property list and the authentication data list,
Receiving specification data inserted into the service profile template, and
When the creation of the service profile template is completed, generating a service profile using the service profile template,
The service profile is used to build a cloud service interface within a system to service a corresponding cloud service,
The step of obtaining the authentication data list,
And obtaining the authentication data list from an authentication data model configured to classify data necessary for authentication according to a plurality of authentication methods, based on the selection information,
The step of creating the service profile template,
And generating a specification portion of the authentication data of the service profile template by using the authentication data list. In paragraph 6,
The property list includes a service URL and a service method of a corresponding service, and a plurality of arguments required to use the corresponding service. In clause 7,
The cloud service ontology includes argument information of each of the plurality of arguments,
The argument information includes at least one of a mapping rule, a display name, an argument name, and a request level. In clause 8,
The mapping rule is a method for generating a service profile of a software platform including rule information for linking with data of a cloud service side for a corresponding argument, and rule information for linking with the system. The method of claim 6,
Receiving the specification data,
And receiving specification data for each property included in the property list and each authentication data included in the authentication data list.

Images