KR102106010B1 - Apparatus and method for controlling of execution web of things mashup service - Google Patents

Abstract

A method and apparatus for controlling execution of a web of things mashup service that creates / performs / inquires a WoT mashup service suitable for a user of a WoT service by mixing various WoT services provided by objects in service execution control of a WoT service system The proposed device is an IoT web mashup service unit that responds to a request for an IoT web mashup service from a user of the IoT web service by executing an IoT web mashup service optimized for the IoT web service user. When the execution request is received, the IoT service execution unit that returns the result of performing the individual IoT service to the IoT web mashup service unit, and stores the IoT service execution specification describing the execution logic for the individual IoT service. And a web storage service storage unit.

Description

Apparatus and method for controlling of execution web of things mashup service}

The present invention relates to an apparatus and method for controlling the execution of an IoT web mashup service, and more specifically, to execute / request / register / execute a new service combining one or more IoT web services in executing an IoT web service available in a web application service environment. It relates to an apparatus and method.

Currently, interest in IoT-related services and applications is gradually increasing due to the expansion of the Internet of Things (IoT) technology and the wearable device market.

In particular, the Internet of Things provides users with useful information services (eg, temperature, humidity, heart rate, location coordinates, travel distance, etc.) through information exchange of objects equipped with a communication function, or remotely controls objects (eg, Lighting brightness, room temperature, etc.).

In this Internet of Things environment, things that communicate using the conventional World Wide Web technology and provide services to users are referred to as Web-based Internet of Things services or Web of Things (WoT) services. . At this time, in order to receive an intelligent service from objects, it is essential to create a new service by combining basic WoT services provided by the object and to perform a service mashup capable of executing a WoT service suitable for a user's needs. .

Conventional mash-up means developing a new web service by mixing various information and web service APIs published on the web. For example, in the case of mashup of the outdoor temperature inquiry service for the current location, the user's current location information and the web-based temperature inquiry service provided by the weather station can be combined to provide the service to the user.

However, if a problem occurs in a specific web service API constituting one mashup service, the entire mashup service cannot be properly performed. In other words, in the previous mashup example, if a problem occurs in the temperature inquiry service API provided to the weather station, it is impossible to perform the entire mashup service.

In addition, the conventional service mashup may use fragmented user information, such as a user's location and request time, to call a web service API. However, in this case, the service mashup method reflecting the status and quality of service of the web service API, user preferences (preferences), and personal characteristics (age, gender, region, school, job, etc.) is not provided.

Related prior arts include contents that allow users to freely browse and select ontology, automatically combine semantic services based on this, and provide an interface for users to interact with the combined composite semantic service or semantic workflow. , Republic of Korea Patent Publication No. 2010-0120905.

The present invention is proposed to solve the above-mentioned conventional problems, and generates / performs / retrieves a WoT mashup service suitable for a WoT service user by mixing various WoT services provided by objects in service execution control of a WoT service system. An object of the present invention is to provide an apparatus and method for controlling execution of a web of things mashup service.

In order to achieve the above object, the apparatus for controlling the execution of an IoT web mashup service according to a preferred embodiment of the present invention is an IoT web mashup service optimized for the IoT web service user for a request for the IoT web mashup service from the IoT web service user IoT web mashup service unit to respond by executing; As the request for execution of the individual IoT service for executing the IoT web mashup service is received from the IoT web mashup service unit, the execution of the IoT web service returns a result of performing the individual IoT web service to the IoT web mashup service unit part; And an IoT web service execution storage unit that stores an IoT web service execution specification describing execution logic for the individual IoT web service.

The IoT web mashup service unit includes: an IoT web mashup execution unit that reads the IoT web service execution specification from the IoT web service execution storage unit and executes the IoT web mashup service according to a service execution rule in the IoT web service execution specification; And an IoT web mashup logic management unit that queries, registers, and updates the IoT web service execution specification from the IoT web service execution storage unit.

The IoT web mashup execution unit is interoperable with the IoT web service execution unit.

The IoT service execution unit is interoperable with an IoT web broker or a general web service to perform the individual IoT web service.

The IoT service execution specification may define a method for executing the individual IoT web service or the IoT web mashup service in which one or more individual IoT web services are mixed.

The IoT service execution specification includes execution information of the IoT web mashup service, service execution rules for executing the IoT web mashup service generated by mixing the one or more IoT web services, and objects optimized for the IoT service user It may include a service execution profile representing parameters for distinguishing a web mashup service.

The service execution rule may be any one of sequential execution, arithmetic operation execution, logical operation execution, and condition execution.

In addition, the method for controlling execution of the IoT web mashup service according to a preferred embodiment of the present invention includes: receiving an IoT web mashup service request from the IoT web service user; The IoT web mashup service selects an IoT web mashup service optimized for the IoT web service user based on the IoT web service execution storage unit storing an IoT web service execution specification describing execution logic for individual IoT web services. step; And the IoT web mashup service unit executing the optimized IoT web mashup service by interworking with the IoT web service execution unit capable of executing the individual IoT web service.

The step of selecting an IoT web mashup service optimized for the IoT service user may include an IoT service execution specification that can be optimal for the IoT service user among the IoT service execution specifications stored in the IoT service execution storage unit. You can choose and combine.

In the IoT web mashup service, one or more of the individual IoT web services are combined, and the step of executing the optimized IoT web mashup service includes: requesting the IoT web service execution unit to execute the individual IoT web service; Receiving an execution result of each individual IoT service; And executing the optimized IoT web mashup service based on the execution result of each individual IoT web service.

The IoT service execution specification may include a service execution rule, and the service execution rule may be any one of sequential execution, arithmetic operation execution, logical operation execution, and condition execution.

The sequential execution may be expressed as "object web mashup service #C = individual IoT web service #B (individual IoT web service #A)", and the sequential execution recalls the result of executing the individual IoT web service #A. The result of the IoT web mashup service #C can be calculated by executing it as an input of the individual IoT web service #B.

The arithmetic operation execution may be expressed as “object web mashup service #C = α · individual IoT web service #A + β · individual IoT web service #B”, and the arithmetic computation execution may be performed with the individual IoT web service #A The result of the web of things mashup service #C is calculated based on the operation result of executing #B, respectively, and α and β may be parameters of the service execution file.

The logical operation execution may be expressed as " object web mashup service #C = individual IoT web service #A & individual IoT web service # B ", and the logical computation execution may respectively perform the individual IoT web services #A and #B. The result of the IoT web mashup service #C is calculated based on the result of the operation, but the logical operation & may mean a case in which the results of the individual IoT web services #A and #B satisfy certain conditions.

The logical operation execution may be expressed as " object web mashup service #C = individual IoT web service #A | individual IoT web service # B ", and the logical computation execution may respectively perform the individual IoT web services #A and #B. Calculate the result of the IoT web mashup service #C based on the result of the operation, but the logical operation | means a case in which any one of the results of the individual IoT web services #A and #B satisfies a certain condition. You can.

The execution of the condition may be expressed as "individual IoT web service #A? Individual IoT web service #B: individual IoT web service #C", and the execution of the condition may be performed when the individual IoT web service #A satisfies a specific condition. In the above, the individual IoT web service #B may be performed, otherwise, the individual IoT web service #C may be performed.

The IoT web mashup service unit may further include: querying, registering, and updating the IoT web service execution specification from the IoT web service execution storage unit.

According to the present invention having such a configuration, it is possible to register and execute the mashup of the web of things web service so that the best web service of each user can be provided.

For a WoT mashup service, a mashup service combined with the most suitable WoT services is performed according to a user's execution request time and space, mashup conditions, and priority, and as a result Can be provided to the user. For example, in the case of a mashup of a WoT service for weather inquiry, when a user requests high precision, a WoT service that provides a high-precision temperature measurement value among temperature WoT services close to the user's current location may be executed. And, the service result can be provided to the user.

1 is a block diagram of an IoT service system to which the present invention is applied.
2 is a block diagram of an apparatus for controlling execution of a web of things mashup service according to an embodiment of the present invention.
3 is an internal configuration diagram of the IoT service execution storage unit illustrated in FIG. 2.
4 is an example of applying a service execution rule among IoT web mashup services in an embodiment of the present invention.
5 is an example of applying a service execution profile among IoT web mashup services in an embodiment of the present invention.
6 and 7 are flowcharts for explaining a method of controlling execution of a web of things mashup service according to an embodiment of the present invention.

The present invention can be applied to various changes and may have various embodiments, and specific embodiments will be illustrated in the drawings and described in detail.

However, this is not intended to limit the present invention to specific embodiments, and should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

The terms used in this application are only used to describe specific embodiments, and are not intended to limit the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "include" or "have" are intended to indicate the presence of features, numbers, steps, actions, components, parts or combinations thereof described herein, one or more other features. It should be understood that the existence or addition possibilities of fields or numbers, steps, operations, components, parts or combinations thereof are not excluded in advance.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person skilled in the art to which the present invention pertains. Terms such as those defined in a commonly used dictionary should be interpreted as having meanings consistent with meanings in the context of related technologies, and should not be interpreted as ideal or excessively formal meanings unless explicitly defined in the present application. Does not.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In order to facilitate the overall understanding in describing the present invention, the same reference numerals are used for the same components in the drawings, and duplicate descriptions for the same components are omitted.

1 is a block diagram of an IoT service system to which the present invention is applied.

The IoT web service system includes the IoT web service provider 20 and the IoT web broker 30.

The IoT web service provider 20 may provide various web services (ie, WoT services) for the IoT 40 to the IoT web service user 10.

Thus, the IoT service provider 20 performs information management and service execution control functions for the WoT service. That is, the IoT service provider 20 may include a module 22 that manages information on the WoT service and a module 24 that functions to control the execution of the WoT service.

Then, the IoT service provider 20 links objects through the web to execute individual WoT services.

The IoT web broker 30 bears an access load due to a large number of things interlocking. In addition, the IoT web broker 30 provides a management function for IoT web resources. Accordingly, the thing web broker 30 can be said to be an intermediary system that supports web linkage of the objects 40.

2 is a block diagram of an apparatus for controlling execution of a web of things mashup service according to an embodiment of the present invention.

The apparatus for controlling the execution of the IoT web mashup service 50 includes the IoT web mashup service unit 52, the IoT web service execution unit 54, and the IoT web service execution storage unit 56.

The IoT Mashup Service Functional Entity 52 may respond to a request for the IoT Web mashup service from the IoT user 10. In addition, the IoT web mashup service unit 52 may perform a corresponding operation according to a request to create / retrieve / delete / modify the IoT web mashup service logic from the IoT web service user 10.

Here, the thing web mashup service unit 52 includes a thing web mashup logic management unit (Mashup logic management) 52a, and a thing web mashup execution unit (Mashup engine) 52b.

The IoT web mashup logic management unit 52a includes a function of inquiring, registering, and updating the IoT web service execution specification from the IoT web service execution storage unit 56.

The IoT web mashup execution unit 52b reads the IoT web service execution specification from the IoT web service execution storage unit 56, and executes the IoT web mashup service according to the service execution rule. That is, the IoT web mashup execution unit 52b provides the most optimal IoT web mashup service to the user when the IoT web service user 10 requests a specific IoT web mashup service (for example, an objection-based cooling service) The IoT web service execution specification can be found in the IoT web service execution storage unit 56. Thereafter, the IoT web mashup execution unit 52b executes the IoT web mashup service according to the service execution rules included in the found IoT service execution specification. At this time, the thing web mashup execution unit 52b may interwork with the thing web service execution unit 54.

The IoT service execution unit 54 receives a request to execute an individual IoT web service from the IoT web mashup service unit 52, performs a corresponding IoT web service, and returns the result back to the IoT mashup execution unit 52b To perform. In this case, the IoT service execution unit 54 may interwork with the IoT web broker 30 or a conventional web service to perform individual IoT web services.

The IoT web service execution storage unit 56 stores information related to the IoT web service execution.

3 is an internal configuration diagram of the IoT service execution storage unit 56 shown in FIG. 2.

The IoT web service execution storage unit 56 stores IoT Web service execution descriptions 56a, 56b, and 56n that describe execution logic for each individual IoT service. That is, a plurality of things web service execution specifications are stored in the thing web service execution storage unit 56.

The IoT web service execution specifications 56a, 56b, and 56n define a method of executing an individual IoT service (Simple WoT Service) or a mixture of one or more individual IoT web services (Mashup / Compound WoT Service). do.

The IoT web service execution specifications 56a, 56b, and 56n are generated by mixing the IoT web mashup service service information (eg, a subject and an access method that provides the IoT web mashup service, Qos), and one or more IoT web services. Service execution rules for executing an IoT web mashup service, and parameters for distinguishing an IoT web mashup service optimized for a user, such as user preference and execution request situation (time, location) for the IoT web mashup service Includes expressing service profiles.

Here, the IoT web mashup service execution information included in the IoT web service execution specifications 56a, 56b, and 56n includes information about the IoT web mashup service, including a URI or a web service API of a subject providing the IoT web mashup service. It can contain.

In addition, the IoT service execution specifications 56a, 56b, and 56n include execution rules of the IoT web mashup service in which one or more individual IoT web services are mixed. Accordingly, for example, when the existing individual IoT service #A and #B exist, the execution rules of the IoT web mashup service #C are as follows: sequential execution, arithmetic operation execution, logical operation execution, condition execution, etc. Can be expressed.

1) Sequential execution: #C = #B (#A)

; #A is executed first, and the result is executed as input of #B.

2) Arithmetic operation: #C = α · # A + β · # B

; #C is determined based on the operation result of executing each individual IoT service #A and #B. At this time, α and β indicate additional information that can be mixed with the performance results of individual IoT services #A and #B. α and β can be defined through the parameters of the service execution profile.

3) Execute logical operation: #C = #A &#B (or #C = #A | #B)

; #C is determined based on the operation result of executing each individual IoT service #A and #B. At this time, logical operation & means that two service results satisfy certain conditions. Logical operation | means that any one of the two service results satisfies a certain condition.

4) Condition execution: #A? #B: #C

; If the individual IoT service #A satisfies a specific condition, the individual IoT service #B is executed, otherwise the individual IoT service #C is executed.

Here, the conditional execution expresses the rule so that the individual IoT service to be performed next is changed according to the result of performing the individual IoT service.

For example: In order to calculate the thermal comfort index, it is necessary to combine and calculate numerical values for various indicators such as temperature, humidity, airflow speed, radiant temperature, and partial pressure of water vapor. In particular, in the case of the unpleasant index, which is a representative thermal comfort index, it can be calculated through the following formula using temperature (in units of T and ° C) and relative humidity (in units of RH and%).

Discomfort Index = (9/5) T-0.55 (1-RH) ((9/5) T-26) + 32

For this nasty index mashup service, first, individual IoT service #A for the current temperature (T) measurement and the individual IoT service #B for the relative humidity (RH) are performed, respectively. Subsequently, the above-described formula can be used to obtain a result of calculating the discomfort index mashup. That is, the execution rule of the unpleasant index mashup service #C can be expressed through the computational execution of individual web services #A and #B.

On the other hand, the service execution profile included in the IoT service execution specification (56a, 56b, 56n) is a user's situation (location, time, cost, preference, selection condition) or individual object requesting execution of each individual IoT service. In consideration of the state (access status, driving state, quality of service) of an object providing a web service, a parameter for providing an object web service suitable for a user may be included.

4 is an example of applying a service execution rule among IoT web mashup services in an embodiment of the present invention. That is, FIG. 4 creates a new IoT web mashup service (Service #n) using two existing individual IoT web services (Service # 1, Service # 2) existing in the IoT web service execution storage unit 56. Indicates that

In FIG. 4, a new IoT web mashup service n that performs arithmetic operations on two separate IoT web services is another service. The new IoT web mashup service n is stored (registered) in the IoT web service execution storage unit 56.

Further, the new IoT web mashup service n is performed through the IoT web mashup execution unit 52b of the IoT web mashup service unit 52 when a user requests to execute it. The IoT web mashup execution unit 52b provides the performance result to the user as a service response.

5 is an example of applying a service execution profile among IoT web mashup services in an embodiment of the present invention. That is, FIG. 5 shows a method of applying a service profile included in the IoT service execution specification to the IoT web mashup service.

A user who wants to receive a new IoT web mashup service n has a profile (ie, parameters α and β) specific to the user requesting the service for each execution result of the individual IoT service # 1 and Service # 2. It can be applied to IoT web services.

In this way, a new Internet of Things mashup service n can be provided.

As described above, an example of a service for providing a cooling mashup service based on an unpleasant index by applying an embodiment of the present invention is as follows.

1) User A (that is, the user of the IoT service) queries and executes the corresponding IoT web mashup service through the IoT web mashup service execution control device 50 in order to receive the cooling service based on the discomfort index in the house.

2) Accordingly, the IoT web mashup service execution control device 50 in the IoT web mashup service execution control unit 52b inquires the corresponding IoT web mashup service execution specification stored in the IoT web service execution storage unit 56. Thereafter, the IoT web mashup execution unit 52b performs individual IoT web services through the IoT web service execution unit 54, thereby measuring indoor temperature and relative humidity.

3) Subsequently, the IoT web mashup execution unit 52b calculates an objection index according to a calculation execution rule by reflecting the service execution profile of the IoT service execution specification. Since there is a difference between individuals who feel the discomfort index, the IoT web mashup execution unit 52b can calculate the discomfort index specialized for each user by using parameter information stored in the profile such as gender, age, temperature precision, and cooling sensitivity.

4) Subsequently, the IoT web mashup execution unit 52b uses the calculated discomfort index to execute the IoT web service for an available cooling device in order to provide comfort desired by the user. In other words, the IoT web mashup execution unit 52b provides the IoT web service for objects (eg, air conditioners, ventilators, etc.) to lower the discomfort index when the calculated discomfort index exceeds a predetermined value specified through the IoT service execution specification. Run

The execution rule and service execution profile of the IoT web mashup service for an example of the above-described discomfort index-based cooling mashup service may be expressed as Table 1 below.

-Service Info:
ID = #N;
Service Category = HVAC service;
Service Provider (WoT Service Provider) = iCooler Co., Ltd .;
Service Type (WoT Service Type) = mashup
Quality of WoT Service = good

-Service Rule:
(x = #A);
(y = #B);
(z = #M) = (1.8x + 0.55 (1-y) (1.8x-25) + 35p);
#N = (z> 80? #C: (z> 75? #D &#E:#F));

-Service Profile:
location = Daejeon ** gu ** ro ***
p = 0.9

At this time, it can be seen that the above-mentioned object web heating and cooling mash-up service (#N) is mixing the following individual object web services.

. Simple Service #A: Temperature collection

. Simple Service #B: Humidity Collection

. Simple Service #C: Air conditioning operation

. Simple Service #D: Air conditioning stop

. Simple Service #E: ventilator operation

. Simple Service #F: Ventilator stop

. Mashup Service #M: Discomfort Index Calculation Service

In addition, in calculating the discomfort index, it is possible to correct the calculation of the discomfort index value of the user through the parameter p.

Furthermore, in the execution of the individual web service of the IoT web mashup service, the service execution profile may be used to reflect the location of the user's execution request, or the parameter for setting the blowing strength of the cooling device.

That is, since the service execution specification for one IoT web mashup service is performed, the same service execution rule may provide different results according to the user request by reflecting the service execution profile suitable for the user's request situation. For example, when the execution rule of the IoT web mashup service #C is expressed as “#C = α · # A + β · # B”, a user using the IoT web mashup service parameter (α) of the execution profile , β) can be used to make the web of things suitable for the request situation.

 6 and 7 are flowcharts for explaining a method of controlling execution of a web of things mashup service according to an embodiment of the present invention.

First, the execution specification for each individual IoT service (that is, the execution of the IoT service specification) is stored in the IoT service execution storage unit 56 (S10). Here, the IoT service execution specification defines a method of executing an individual IoT web service or an IoT web mashup service in which one or more individual IoT web services are mixed.

Thereafter, a user who wants to be provided with the IoT web mashup service, that is, the IoT web service user 10 accesses the IoT web mashup service execution control device 50.

Then, the user who wants to be provided with the IoT web mashup service searches and selects the desired IoT web mashup service (S12). Here, various information (eg, age, gender, heart rate, location, etc.), selection conditions and information around the user (eg, temperature, humidity, airflow speed, radiation temperature, water vapor, etc.) for a user who wants to receive a web mashup service Partial pressure, etc.) will be transmitted to the IoT web mashup service execution control device 50.

Accordingly, the IoT web mashup execution unit 52b preferentially selects if the user's current location, the user's execution request time, the mashup condition (eg, preference, etc.), and priority (eg, the same priority IoT web mashup services) Based on the possible ranking), the most suitable thing web mashup service is selected for the user (S14). That is, the IoT web mashup execution unit 52b may select the most optimal IoT web mashup service capable of executing the IoT web mashup service selected by the user in the IoT web service execution storage unit 56. In other words, the IoT service execution storage unit 56 stores an IoT service execution specification describing execution logic for each individual IoT service. Accordingly, selecting and combining the execution specifications of the IoT web service that can be the most optimal for the user enables selection of the most optimal IoT web mashup service for the user. In this case, the IoT web mashup service selected by the IoT web mashup execution unit 52b may be regarded as a combination of one or more individual IoT web services. Here, one or more individual IoT web services are services capable of executing the selected IoT web mashup service most accurately, reliably, and effectively. Hereinafter, it is assumed that the selected IoT web mashup service is a combination of two or more individual IoT web services. And, the execution rule of the selected IoT web mashup service will be one of sequential execution, arithmetic operation execution, logical operation execution, and condition execution.

Thereafter, the IoT web mashup execution unit 52b checks a service execution rule of the IoT web mashup service (that is, the IoT web mashup service selected as the most optimal for the user) to be executed by the IoT web service execution storage unit 56. .

As a result, if the service execution rule is sequential execution, the IoT web mashup execution unit 52b performs sequential execution by interworking with the IoT web service execution unit 54 based on the selected individual IoT web services (S16, S18). For example, if the service execution rule of the corresponding IoT web mashup service is "#C = #B (#A)", the IoT web service execution unit 54 executes the individual IoT web service #A, and executes the IoT web mashup The unit 52b executes the result of the IoT web service execution unit 54 as an input of the individual IoT web service #B.

Subsequently, the IoT web mashup execution unit 52b assumes that the executed result is a result of the corresponding IoT web mashup service #C (S20).

Then, the IoT web mashup execution unit 52b registers the IoT web mashup service as a new individual IoT web service (S22). That is, the IoT web mashup execution unit 52b considers the IoT web mashup service obtained as a result in S20 to be a new individual IoT web service, and stores it in the IoT web service execution storage unit 56 for later use. . Then, the IoT web mashup execution unit 52b provides the execution result of the IoT web mashup service to the user (ie, the IoT web service user 10).

If necessary, step S22 of registering the IoT web mashup service as a new individual IoT web service may be omitted. That is, when the result of the corresponding IoT web mashup service is calculated by step S20, it may be provided directly to the corresponding IoT web user 10.

On the other hand, if the checked service execution rule is an arithmetic operation execution, the IoT web mashup execution unit 52b performs arithmetic operation execution by interworking with the IoT web service execution unit 54 based on the selected individual IoT web services (S24, S26). For example, if the service execution rule of the corresponding IoT web mashup service is “#C = α · # A + β · # B”, the IoT web service execution unit 54 sets individual IoT web services #A and #B, respectively. Run it. Subsequently, the IoT web mashup execution unit 52b obtains the results of the IoT web mashup service #C based on the calculation results of the individual IoT web services #A and #B, respectively. That is, the IoT web mashup execution unit 52b applies the parameter α to the individual IoT web service #A, applies the parameter β to the individual IoT web service #B, and then calculates the result of the IoT web mashup service #C with the sum of these. do. Then, the IoT web mashup execution unit 52b performs the operations of steps S20 and S22 described above.

On the other hand, if the checked service execution rule is a logical operation execution, the IoT web mashup execution unit 52b performs logical operation execution by interworking with the IoT web service execution unit 54 based on the selected individual IoT web services (S28, S30). For example, if the service execution rule of the corresponding IoT web mashup service is "#C = #A &#B", the IoT web service execution unit 54 executes individual IoT web services #A and #B, respectively. Thereafter, the IoT web mashup execution unit 52b calculates the result of #C based on the execution results of each individual IoT web service #A and #B. Then, the IoT web mashup execution unit 52b performs the operations of steps S20 and S22 described above.

On the other hand, if the checked service execution rule is conditional execution, the IoT web mashup execution unit 52b performs conditional execution by interworking with the IoT web service execution unit 54 based on the selected individual IoT web services (S32, S34). . For example, if the service execution rule of the corresponding IoT web mashup service is "#A? #B: #C", the IoT web mashup execution unit 52b may display the individual IoT web if the individual IoT web service #A satisfies a specific condition. Perform service #B, otherwise execute individual web service #C. In other words, when the operation result of the individual IoT service #A executed by the IoT service execution unit 54 satisfies a specific condition, the IoT web mashup execution unit 52b performs individual IoT web service #B, and If not, run individual web service #C.

Meanwhile, in the above description, creation of the mashup service logic and inquiry / deletion / modification of the mashup service are not separately described. However, such creation / query / delete / modification can be sufficiently performed by the IoT service user 10 and the IoT web mashup logic management unit 52a.

For example, when the IoT service user 10 requests creation of the desired mashup service logic, the IoT web mashup logic management unit 52a generates a corresponding mashup service logic to the IoT web service execution storage unit 56 To save. That is, it can be seen that a new specification for the execution of the IoT web service is generated and stored in the IoT service execution storage unit 56. Here, the newly generated mashup service logic may be adopted and used in accordance with the IoT web mashup service selection of the IoT user 10 later.

When the IoT service user 10 requests an inquiry of the desired mashup service, the IoT web mashup logic management unit 52a finds the corresponding mashup service in the IoT web service execution storage unit 56 and the IoT web service user 10 Send to

When the IoT service user 10 requests to delete the desired mashup service, the IoT web mashup logic management unit 52a finds and deletes the corresponding mashup service from the IoT web service execution storage unit 56.

When the IoT service user 10 requests modification (update) of the desired mashup service, the IoT web mashup logic management unit 52a finds and corrects (updates) the corresponding mashup service in the IoT storage execution unit 56 do.

As described above, optimal embodiments have been disclosed in the drawings and specifications. Although specific terms have been used herein, they are only used for the purpose of describing the present invention and are not used to limit the scope of the present invention as defined in the claims or the claims. Therefore, those skilled in the art will appreciate that various modifications and other equivalent embodiments are possible therefrom. Therefore, the true technical protection scope of the present invention should be determined by the technical spirit of the appended claims.

50: IoT web mashup service execution control device
52: IoT Web Mashup Service Department
52a: IoT web mashup logic management unit
52b: IoT web mashup execution unit
54: IoT web service execution unit
56: IoT web service execution storage

Claims (19)

An IoT web mashup service unit that executes an IoT web mashup service customized for the IoT web service user;
An IoT web service execution unit that processes execution of an individual IoT web service for executing the IoT web mashup service; And
And a thing web service execution storage unit that stores a thing web service execution specification describing execution logic for the individual web service. The method according to claim 1,
The thing web mashup service unit,
An IoT web mashup execution unit that executes the IoT web mashup service according to the IoT web service execution specification read from the IoT web service execution storage; And
And an IoT web mashup logic management unit for querying, registering, and updating the IoT web service execution specification from the IoT web service execution storage unit. The method according to claim 2,
The IoT web mashup execution unit is interlocked with the IoT web service execution unit, the IoT web mashup service execution control device. The method according to claim 3,
The IoT web service execution unit is capable of interlocking with an IoT web broker or a general web service for performing the individual IoT web service. The method according to claim 1,
The IoT web service execution specification defines a method of executing the individual IoT web service or the IoT web mashup service in which one or more individual IoT web services are mixed. The method according to claim 1,
The IoT service execution specification includes information on the IoT web mashup service, a service execution rule for executing the IoT web mashup service generated by mixing the one or more IoT web services, and a customized IoT web for the IoT service user And a service execution profile representing a parameter for distinguishing the mashup service. The method according to claim 6,
The service execution rule is any one of sequential execution, arithmetic operation execution, logical operation execution, and condition execution. The IoT web mashup service unit selects the IoT web mashup service customized for the IoT web service user based on the IoT web service execution storage unit storing the IoT web service execution specification describing execution logic for individual IoT web services; And
And executing the customized IoT web mashup service by interworking with the IoT web service execution unit capable of executing the individual IoT web service. Control method. The method according to claim 8,
The step of selecting a customized IoT web mashup service to the IoT user may include:
A method for controlling the execution of a web of mashup service of a web of things, wherein the web of service is stored in the storage of the web of the web and the web of the web is executed. The method according to claim 9,
In the IoT web mashup service, one or more individual IoT web services are combined,
The step of executing the customized IoT web mashup service is:
A method of controlling execution of a web of things mashup service, wherein the customized web of things mashup service is executed based on the execution result of each individual web service. The method according to claim 8,
The IoT service execution specification defines a method of executing the individual IoT web service or the IoT web mashup service in which one or more individual IoT web services are mixed. The method according to claim 8,
The IoT service execution specification includes information on the IoT web mashup service, a service execution rule for executing the IoT web mashup service generated by mixing the one or more IoT web services, and a customized IoT web for the IoT service user And a service execution profile representing a parameter for distinguishing the mashup service. The method according to claim 12,
The service execution rule is any one of sequential execution, arithmetic operation execution, logical operation execution, and condition execution. The method according to claim 13,
The sequential execution is expressed as " object web mashup service #C = individual IoT web service #B (individual IoT web service #A) ",
The sequential execution is performed by executing the result of executing the individual IoT web service #A as an input of the individual IoT web service #B, thereby calculating the result of the IoT web mashup service #C. Control method. The method according to claim 13,
The arithmetic operation execution is expressed as "object web mashup service #C = α · individual IoT web service #A + β · individual IoT web service #B",
The arithmetic operation execution calculates a result of the IoT web mashup service #C based on the operation result of executing the respective IoT web services #A and #B, respectively, wherein α and β are parameters of the service execution profile. Characteristic web mashup service execution control method. The method according to claim 13,
The logical operation execution is expressed as "object web mashup service #C = individual IoT web service #A & individual IoT web service #B",
The logical operation execution calculates the result of the IoT web mashup service #C based on the operation result of executing the respective IoT web services #A and #B, respectively, wherein the logical operation & is the individual IoT web service #A and A method for controlling the execution of a web of things mashup service, wherein the result of #B means a case when a certain condition is satisfied. The method according to claim 13,
The logical operation execution is expressed as "object web mashup service #C = individual IoT web service #A | individual IoT web service #B",
The logical operation execution calculates the result of the IoT web mashup service #C based on the operation result of executing the respective IoT web services #A and #B, respectively, wherein the logical operation | is the individual IoT web service #A and A method of controlling the execution of a web of things mashup service, which means that any one of the results of #B satisfies a certain condition. The method according to claim 13,
The above conditional execution is expressed as "individual IoT web service #A-individual IoT web service #B: individual IoT web service #C",
The condition execution is performed when the individual IoT service #A satisfies a specific condition, and performs the individual IoT service #B, otherwise, performing the individual IoT service #C. How to control execution. The method according to claim 8,
The IoT web mashup service unit, the method of searching, registering, and updating the IoT web service execution specification from the IoT web service execution storage unit.

Images