KR101493166B1 - Sevice method and system for providing web based user interface for managing instance of virtualization object in internet of things environment - Google Patents

Abstract

The present invention relates to a service method and to a system for providing a web based user interface for managing the instance of a virtualization object in internet of things (IOT) environment. The service method in the IOT environment includes the steps of: confirming information about the instance of the virtualization object for a thing inputted through setting functions of a web page supplied to a user step by step; performing authentication with an external service by using information about the external service inputted through the external service connection function of the web page; and supplying an open application program interface (API) by using information inputted through the open API setting function of the web page.

Description

TECHNICAL FIELD [0001] The present invention relates to a service method and system for providing a web-based user interface for managing instances of virtualized objects in an IoT environment. [0002]

Embodiments of the present invention are directed to a service method and system for providing a web-based user interface for managing instances of virtualized objects in an IoT environment.

The Internet of Things (IOT) has evolved from the existing USN (Ubiquitous Sensor Network) or M2M (Machine to Machine). If the existing M2M was intended to communicate with end-devices and people, Is to broaden the scope of things so that we can communicate with people, such as telephones, books, thermometers, etc., that we commonly see. In other words, IoT can refer to a three-dimensional distributed environment element of human being, object, and service, and a spatial space network that forms an intelligent relationship such as sensing, networking, and information processing cooperatively without human intervention.

In addition to IoT, various concepts and technologies such as Web of Things (WoT) and Web of Objects (WoO) are being researched and developed. Due to the development and spread of these concepts and technologies, it is expected that users will be able to easily use devices that can be connected to the Internet (gadget devices, sensor devices, actuators, etc.).

In particular, various types of web-linked gadget devices have recently been released, and most of the sensor devices provide control and monitoring functions through the web. In addition, terminals for providing a control function via the web include a function that enables the terminal itself to have a built-in web server function or to be controlled through an on-line web service.

However, at present, the above-described technologies, devices or services are individually managed, and there is a problem that users are inconvenienced. For example, a user has the inconvenience that a plurality of devices are present around a user, but each device must be controlled through an individual access path (e.g., a URL). If the device itself provides a web access function (server function), network interworking and URL (IP address) for accessing individual devices are required. In the case where a service is provided through a dedicated web service, URL is required.

In addition, there is a problem that it is difficult to utilize individually managed data in an interlocked manner. For example, in the case of a sensor that controls the boiler in the house, the environmental information that can be directly collected by the sensor device is very limited, such as the presence or absence of a person, internal temperature, and time zone. If such a sensor device can additionally utilize external information (e.g., outside temperature, user schedule information, etc.), more effective control functions may be provided, but data may be provided for each technology, It is difficult to utilize these data in an organic manner.

1 is a diagram illustrating a service providing method when an embedded web server is embedded in a device in the prior art. A user can access an embedded web server 140 embedded in a device 130 of a physical world 120 through an online (Web) It is accessible. At this time, because the embedded web server 140 is embedded in the device 130, both the data generated in the device 130 and the process logic for processing a specific function or service are loaded in the device 130. Therefore, it is impossible to provide services that are interlocked with or fused with data of other service areas or other services beyond the service area provided by the device 130. [

2 is a diagram illustrating a service providing method when a manufacturer provides a separate web server on-line in the prior art. In FIG. 2, unlike FIG. 1, a manufacturer (or a separate service provider) constructs a Web server 210 on the online 110 to provide a service. At this time, the user can access the device (IoT node) 220 through the web server 210 on-line 110. In this case, the device 210 may be equipped with a module (HTTP adapter 230 in FIG. 2) for communicating with the web server 210. Accordingly, both the data generated by the device 220 and the process logic for processing a specific function or service can be provided online. If desired, the data may reside on device 220 and the process logic may reside on web server 210. In this case, the manufacturer (or a separate service provider) may experience problems with Web service availability and persistence of hosting.

1 and 2, the user can not access the device 130 having the embedded web server 140 through the web server 210, and conversely, the user can not access the embedded web server 140 The web server 210 or the device 220 can not be accessed. That is, mutual information exchange between object instances is impossible, and thus interlocking or convergence type services can not be provided.

2, since the device 220 must provide information obtained from an object such as a sensor or personal information of a user (e.g., location of a user) to the web server 210 in order to provide a service, There is a possibility of causing a problem of the privacy of the user.

Provides a method and system for providing services to provide heterogeneous devices or various services interlocking or converging in IoT (Internet of Things), WoT (Web of Things) or WoO (Web of Objects) do.

A service method in an Internet of Things (IOT) environment, comprising: confirming information about an instance of a virtualization object for a Thing entered through a step-by-step setting function of a web page provided to a user; ; Performing authentication with the external service using information about the external service input through the external service connection function of the web page; And providing the open API to the external service using information input through an open API (Application Program Interface) setting function of the web page.

According to one aspect, the service method may further include displaying an instance-specific icon through the web page.

According to another aspect, a control function for an instance and a representative value of the instance are displayed through an area in which the icon is displayed.

According to another aspect, the state of the instance is further displayed through the region.

A method of service in an Internet of Things (IoT) environment, comprising: receiving a request from a user; And providing a web page according to a request of the user, wherein the web page comprises: a step-setting function for receiving information on an instance of a virtualization object for a Thing; An external service connection function for receiving information for authentication with an external service; And an open API setting function for receiving information on an open API to be provided to the external service.

According to another aspect, the step-by-step setting function includes a user interface for receiving a name of an instance, a user interface for receiving a tag of the instance, a user interface for receiving a URL storing a profile of the IoT node, A user interface for selecting a state of an instance, a user interface for selecting a controller, and a user interface for selecting a unit of a representative value, in a stepwise manner, can do.

According to another aspect of the present invention, the external service connection function includes a user interface for receiving account information of the user with respect to the external service.

According to another aspect of the present invention, the open API setting function includes a user interface for receiving location information including a description document of the open API.

A service system in an Internet of Things (IoT) environment, comprising: at least one storage unit storing at least one program; And at least one processor, wherein the at least one processor is operable, under the control of the at least one program, to generate a virtualization object for a Thing, input via a step-by-step configuration function of a web page, A process of confirming information about an instance of the virtualization object; Performing authentication with the external service using information about the external service inputted through the external service connection function of the web page; And providing the open API to the external service using information input through an open API (Application Program Interface) setting function of the web page.

A service system in an Internet of Things (IoT) environment, comprising: at least one storage unit storing at least one program; And at least one processor, wherein the at least one processor is configured to: receive a request of a user according to control of the at least one program; And a step of providing a web page according to a request of the user, wherein the web page has a step-setting function for receiving information on an instance of a virtualization object for a Thing; An external service connection function for receiving information for authentication with an external service; And an open API setting function for receiving information on an open API to be provided to the external service.

1 is a diagram illustrating a service providing method when an embedded web server is embedded in a device in the prior art.
2 is a diagram illustrating a service providing method when a manufacturer provides a separate web server on-line in the prior art.
FIG. 3 is an example of an overall system structure for instance hosting in an embodiment of the present invention.
4 is a diagram for explaining a concept of interfaces of an instance in an embodiment of the present invention.
5 is a diagram for explaining functions of interfaces of an instance in an embodiment of the present invention.
6 is a diagram showing an example of an instance list page in an embodiment of the present invention.
7 is a block diagram illustrating an instance manager in an embodiment of the present invention.
8 is a flowchart for explaining an instance status query function in an embodiment of the present invention.
9 is a flowchart for explaining an instance state control function in an embodiment of the present invention.
10 is a flowchart for explaining an instance installation control function in an embodiment of the present invention.
11 is a block diagram illustrating an object feed control function in an embodiment of the present invention.
12 is a flowchart for explaining a schedule registration method according to an embodiment of the present invention.
13 to 15 are diagrams for explaining an instance wizard in an embodiment of the present invention.
16 is a diagram for explaining an additional setting and an external service authentication request for a mashup instance in an embodiment of the present invention.
17 is a diagram for explaining an open API in an embodiment of the present invention.
18 is a flowchart showing a service method in an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 3 is an example of an overall system structure for instance hosting in an embodiment of the present invention. 3 illustrates an example of an IoT profile (IoT Profile) 310, an IoT node 320, an Instance Hosting Gateway 330, and an Instance Hosting Platform 340 ).

The IoT profile 310 may refer to information about the IoT node 320 provided by the manufacturer or the developer of the IoT node 320 on-line. For example, the IoT profile 310 may include information about the IoT node 320 such that the manufacturer or developer can use the IoT node 320 to minimize the inconvenience of manually entering data into the instance hosting gateway 330 320 may be an XML file generated by processing information according to a predetermined XML (extensible Markup Language) scheme.

The IoT profile 310 includes an identifier for the IoT node 320 and an identifier for the process described in relation to the operation of the IoT node 320 URL). For example, a process may be provided online with a separate file (e.g., an extension '.js' file), and the identifier for the process may be a URL that points to the location of such a file. Table 1 below shows an example of the information that the IoT profile 310 may include.

Name Description Remarks IoTProfileID The unique URL where the IoT Profile is located Expressed in URI format IoTProfileVer Version of IoT Profile 'V' + expressed as 'number format' IoTProfileDesc Description of IoT Profile IoTInput Input values for IoT Node (not required for instance nodes that do not provide input functionality), information for creating RESTful APIs Data Support Format
- JSON
- XML IoTOutput Output value of IOT Node, information for generating RESTFUL API IoTProcessID Process identifier of IoT Node Expressed in URI format

The IoT node 320 can respond to things in an IoT environment such as a sensor device and can provide its own identifier information such as 'IoTNodeID'. If the IoT node 320 is an NC (Non-Constraint) node such as a smart device, the IoT node 320 may directly provide the IoT profile 310 described above.

In FIG. 3, one IoT node 320 and one IoT profile 310 for the IoT node 320 are shown for convenience of explanation. However, in the IoT environment, a plurality of IoT nodes and IoT nodes It is quite natural that the IoT profiles can be utilized. Also, a plurality of IoT profiles for one IoT node may be provided.

One IoT node and instance can be related in various ways such as 1: 1, 1: N, N: 1, N: M. In addition, an instance may exist in the form of a process even if there is no physical IoT node, and an instance may be created and interworked through inter-process interactions, such as a mash-up process, rather than interworking with a specific device. For example, an instance can be created in the instance hosting gateway 330 by connecting a specific process to the instance hosting gateway 330 without deploying it to a separate IoT node. In the present specification, an example of processing a message received from an IoT node through a communication between an IoT node (physical node), which is generally described as a physical device, and an instance hosting gateway according to embodiments of the present invention, As described above, however, at least one IoT node may exist in the form of a process (process node) rather than a physical device.

Also, a process may be provided that receives information from a plurality of sensors without providing a physical device such as a sensor device or an actuator, and provides only the interworking function with other web services or applications on-line. For example, in the case of a service providing a specific result by analyzing the information of the sensors and the status information of a specific application used by a user or a social service, a separate processing environment for operating the service is required. In this case, the instance hosting gateway according to embodiments of the present invention may provide the processing environment.

The instance hosting gateway 330 processes messages received from the IoT node 320 with individual instances and processes them, and can interact with external services upon request of a user or service. This instance hosting gateway 330 may be implemented in an Access Point (AP) environment for the IoT node 320. [ For example, the instance hosting gateway 330 may include an Instance Application Server portion mounted on the AP and operating in the form of a Web Application Server (WAS) (For example, a module mounted in the form of software in the operating system of the AP and a module mounted in the form of hardware for communication with the IoT node 320) in a combined form of hardware.

For example, the instance hosting gateway 330 may be included in an AP installed in a specific space (e.g., a house), communicates with objects (IoT nodes) included in the specific space to receive and process data, And perform a function for providing an interworking service with the service.

At this time, if the instance hosting gateway 330 finds a new IoT node 320, the IoT profile 310 can be downloaded and installed. For example, the user can input the location of the XML file corresponding to the IoT profile 310 to the instance hosting gateway 330, and the instance hosting gateway 330 downloads and installs the XML file based on the input location .

This instance hosting gateway 330 will be described in more detail later with reference to FIGS.

The instance hosting platform 340 may provide inter-instance interworking and mash-up functionality. For example, the instance hosting gateway 330 may provide a function for providing a function for a user or a service upon request to the outside in the form of an API (Application Program Interface) and communicate with the instance hosting platform 340 can do.

4 is a diagram for explaining a concept of interfaces of an instance in an embodiment of the present invention. In virtualization objects (VO) 420 of things 410, there is a need for a basic interface for the connection between virtual objects and objects, and the connection between virtual objects and other virtual objects. In this embodiment, examples for providing a total of five instance interface functions for effective and explicit use of the interface will be described.

The information of the individual interfaces can be explicitly described in the instance profile for each instance, and the instance manager, which the instance hosting gateway 330 described with reference to FIG. 3 described above, can use, . At this time, FIG. 4 shows Associated Thing Instances related to each of the objects 410 and a Mashup Instance for inter-instance interworking. At this time, the mashup instance may enable interworking with an instance application server (IAS) 430 and a third party service (440).

The instance application server 430 may be responsible for the web application server function of the instance hosting gateway 330. At this time, functions provided through the instance application server 430 may be provided as a web interface. The third party service 440 may also refer to various external services, such as a Social Network Service (SNS) associated with the user.

5 is a diagram for explaining functions of interfaces of an instance in an embodiment of the present invention. The instances, which are the virtualization objects 420 of FIG. 4, can use the five pre-provided interfaces provided by the instance manager to (1) between objects and instances, (2) between instances and instances, Party service 440) and (4) instance hosting (IH) application functionality (e.g., the Instance Icon of FIG. 4).

F 510, which means a feeder, may include an interface that exposes information that an instance intends to provide as an instance or an external service. At this time, the F 510 may operate in a form of storing information to be fed on a message queue of an instance rather than directly transmitting a message. The following (1) to (3) and Can be utilized in the same case.

(1) You want to read a message received from a device (object) and forward it to another service or another instance.

(2) exposing a particular state value within an instance or exposing a value to be passed to an external service (e.g., a third party service 440).

(3) a value (representative attribute value) to be exposed as a representative to the user through the instance icon (for example, the instance icon of the instance application server 430) on the instance list among the status values of the instance .

The S 520, which means a subscriber, may include an interface for receiving information from an object or a feeder of another interface, and may be utilized in the following cases (4) and (5).

(4) In the case where it is used to receive information received from a device (object) (in this case, information about the physical interface of the object to be listened to by the network adapter included in the instance hosting gateway 330) Element may be described in an associatedThingInformation element).

(5) When subscribing to feeder information of another instance (if you want to use the value exposed by the feeder interface of other instance) - If you subscribe to information about feeder of other instance, You can subscribe to information through the interface.

R 530, which means a receiver, may include an interface through which an instance receives a message from a controller of another instance, and may be utilized in the following cases (6) to (8).

(6) Receiving information from another instance (receiving information from the controller interface of another instance).

(7) When the representative control value (when the representative attribute value is set on the feeder) on the instance icon is received (when the direct control of the user is processed).

(8) receiving a message from an external service (e.g., third party service 440) (e.g., when receiving user status information of a calendar service).

C 540, which means a controller, may include an interface for transmitting information from the outside of the instance, and may be utilized in the following cases (9) and (10).

(9) When delivering (controlling) messages to devices (objects) (when delivering messages to devices (objects) with related object information elements).

(10) When delivering a message to another instance (passing data through a triggering method, not in the form of entering the receiver interface message queue of another instance).

O (550), which means OAuth, may include an interface for an instance to interwork with a third party service and may be utilized in the following cases (11) and (12).

(11) When forwarding a message to a third party service (after OAuth authentication is done).

(12) When receiving (querying) a message with a third party service.

At this time, both (8) and (12) described above show a case of receiving a message from an external service. Messages from the external service may be received via the receiver or via O 550, depending on the embodiment.

The instance according to the embodiments of the present invention can generate each message queue for individual interface information, and a predetermined number (for example, 100) of messages can be stored in the message queue per interface. Even if the instance is terminated abnormally (for example, when changing to an error state), the stored message remains, and the stored message can be used again when changing to a normal operating state (run). At this time, messages received when the instance is in an error state can be stored on the message queue of the individual interface, regardless of the state of the instance (for subscriber or receiver interfaces).

In the following, the interfaces that the instance contains will be described in more detail.

1. The subscriber may be an interface for receiving and subscribing messages from a feeder interface of a Thing or other instance as described above. When receiving a message from an object, the subscriber must write the information of the physical interface necessary for the reception of the message on the 'associatedThingInformation' element of the object information. The necessary information is used to adapt the physical interface of the basic device, And the like. In addition, when a message is received from another instance, the subscriber must write information on a filter element of a feeder interface of another instance to be subscribed on the filter element, May be described on the filter element by entering the information of the instance to be subscribed in the registration process (registration using the Instance Wizard). At this time, when the trigger attribute is set to 'true', if the corresponding feeder value is generated, the instance manager can immediately call the subscriber instance that subscribes to it. The operation can be performed irrespective of the value of the instance operation cycle 'InstanceRunningPeriod'.

The attributes that a subscriber can have can be expressed as an example of the following Table 2.

<xs: element name = "subscriber"><xs:complexType>
<! - Used as an identifier to identify the interface (I / F) by instance (Instance). Up to 3 digits are available .-->
<xs: attribute name = "id" type = "xs: unsignedShort"/>
<! - NAME can be used as information to easily identify the instance, and it can be used as information provided to the user in order to distinguish the I / F of the instance in future connection between the instances .-->
<xs: attribute name = "name" type = "xs: string"/>
<! - If the value is generated when subscribing to another instance, it will be set according to whether or not it reacts immediately. Instance Manager monitors whether feeder list is triggered or not.
<xs: attribute name = "trigger" type = "xs: boolean"/>
</ xs: complexType></ xs: element>

In addition, the attributes that the filter in the subscriber can have can be expressed as an example of Table 3 below.

<xs: element name = "filter"><xs:complexType>
<! - If you subscribe to a feeder from another instance, you can subscribe only interfaces that meet the conditions defined in the filter. ->
<xs: attribute name = "instanceId" type = "xs: string"/>
<! - Enter the identifier (ID) value of the instance to subscribe to (unique value) ->
<xs: attribute name = "feederId" type = "xs: unsignedShort"/>
<! - Enter the unique identifier of the Feeder in the instance to subscribe to ->
<xs: attribute name = "minVersion" type = "xs: string"/>
<! - Enter the minimum value of the supported version of the instance to subscribe to ->
<xs: attribute name = "maxVersion" type = "xs: string"/>
<! - Enter the maximum value of the supported version of the instance to subscribe to ->
</ xs: complexType></ xs: element>
</ xs: sequence>

2. A feeder is an interface for an instance to expose information to other instances. Depending on the configuration of the interface to which it is subscribed, a value can be passed immediately, or a value can be passed to the input value of another instance at the time of operation of another instance. At this time, a message queue is created on the instance manager for each individual feeder identifier (ID), the data (message) is stored in the message queue, and the message queue is read through the subscriber interface.

Regarding the message delivery method of the feeder, a method of reading a message from the feeder is divided into a method according to whether a trigger is set on a subscriber interface or a method in which an input value is transmitted according to the execution of a subscription instance.

In the case of a subscriber interface that has triggered a feeder for that feeder, it will be called when the value for the feeder to which that subscriber interface subscribes is registered. Otherwise, the instance manager will read the runtime data of the other instance that subscribes to the feeder and pass it as the input value. At this time, even if the instance manager reads the feeder value, it does not immediately erase the data in the message queue. The size of the queue of the message may have a predetermined number (for example, 100) for each interface, and the value remains even if the corresponding instance is abnormally terminated.

The feeder can use an attribute expressed as shown in Table 4 below. When 'representative' representing a representative value is used (true), it is necessary to designate a unit so that the temperature, Kcal Etc. may be displayed.

<xs: attribute name = "id" type = "xs: unsignedShort"/>
<! - Can be used as an identifier to identify an interface by instance. Up to 3 digits are available .-->
<xs: attribute name = "name" type = "xs: string"/>
<! - NAME is used as information to easily distinguish between instances, and it will be used as information provided to users in order to distinguish interface (I / F)
<xs: attribute name = "unit" type = "xs: string"/>
<! - Used to define the data values sent and received through the interface ->
<xs: attribute name = "representative" type = "xs: boolean"/>
<! - Set the representative value. If you set the value, the corresponding value will be displayed on the instance icon on the instance list page. ->

6 is a diagram showing an example of an instance list page in an embodiment of the present invention. 6 shows a screen 600 on which a part of a page including a plurality of instance icons is displayed. At this time, examples of setting the representative value attribute of the feeder instance on the instance icon in the screen 600 are shown through the dotted ellipses 610. [

3. Receiver is an interface for receiving messages from other instances, and can receive information through the controller interface of another instance. Messages received from other instances are delivered directly to the receiving instance, and triggering (execution) of the instance occurs. This triggering can be performed regardless of the 'runningPeroid' setting, which indicates the period of operation of the instance that received the message.

The receiver can use the attributes shown in the following table 5. If 'representative' is used (representative), it is necessary to specify a unit so that a button for controlling the corresponding instance on the list page of the instance manager is created .

<xs: attribute name = "id" type = "xs: unsignedShort"/>
<! - Use as an identifier to identify the interface by instance. Digits can be used up to 3 digits ->
<xs: attribute name = "name" type = "xs: string"/>
<! - NAME is used as information to easily distinguish the interface, and is used as information provided to the user to distinguish the interface (I / F)
<xs: attribute name = "unit" type = "xs: string"/>
<! - Used to define the data values sent and received through the interface ->
<xs: attribute name = "representative" type = "xs: boolean"/>
<! - Set the representative value. If you set the value, the corresponding value will be displayed on the instance icon on the instance list page. ->

6, a button for controlling an instance corresponding to the instance icon such as "ON", "OFF", "Locked" is created in the activated icons among the icons displayed on the screen 600 .

4. A controller may contain an interface for an instance to deliver a message to another instance or device (something). The controller can invoke the instance through a direct delivery method to deliver the message to other instances, and the message can be delivered to the instance via the receiver interface. For example, the delivery of a message can be triggered regardless of the setting of the running period 'runningPeroid' of the instance that received the message. When forwarding a message to a device (object), the controller can immediately forward the message via the network adapter.

When forwarding a message to another instance, the information of the receiver interface of the other instance should be described in the filter element. At this time, the information described in the filter element can be expressed as shown in Table 6 below.

<xs: element name = "filter"><xs:complexType>
<! - When forwarding a message to a receiver of another instance, it is possible to forward the message only to interfaces that meet the conditions defined in the filter. ->
<xs: attribute name = "instanceId" type = "xs: string"/>
<! - ID value (unique value) of the instance to which to forward the message ->
<xs: attribute name = "receiverId" type = "xs: unsignedShort"/>
<! - ID value (unique value) of the receiver interface in the instance to which to deliver the message ->
<xs: attribute name = "minVersion" type = "xs: string"/>
<! - Enter the minimum value of the instance-supported version to pass ->
<xs: attribute name = "maxVersion" type = "xs: string"/>
<! - Enter the maximum value for the instance-supported version to pass ->
</ xs: complexType></ xs: element>

In addition, the controller can have the attributes shown in Table 7 below.

<xs: attribute name = "id" type = "xs: unsignedShort"/>
<! - Use as an identifier to identify the interface by instance. Digits can be used up to 3 digits ->
<xs: attribute name = "name" type = "xs: string"/>
<! - NAME is used as information to easily distinguish the interface, and is used as information provided to the user to distinguish the interface (I / F)
</ xs: complexType></ xs: element>

5. The authentication interface ('OAuth') may include an interface that an instance uses when interacting with external third party services and OAuth-based authentication. To do this, the user must first authenticate the OAuth account of the target service to which the user wants to connect. Such OAuth account authentication can be performed separately through the Instance Wizard or the OAuth menu.

For each instance, the authentication information of OAuth for interlocking can be set or unset. For example, you can configure / revoke multiple social network service accounts differently for each instance.

An instance can determine if the OAuth interworking is required, depending on the needs of OAuth. If the 'required' attribute is set to 'true', then the instance can not be in the running state if the OAuth linking is not successful, ) State.

The OAuth interface can have the attributes shown in Table 8 below.

<xs: element name = "oAuth"><xs:complexType>
<! - Use as an identifier to identify the interface (I / F) by instance. Digits can be used up to 3 digits ->
<xs: attribute name = "id" type = "xs: unsignedShort"/>
<! - Enter the name of the service that will link OAuth. For example, Twitter is 'twitter', Facebook is 'facebook', Google is 'Google'->
<xs: attribute name = "serviceName" type = "xs: string"/>
<! - Provide a description that tells the user what information to use in the Oauth account to work with. For example, information technology for accessing information for what purpose ->
<xs: attribute name = "description" type = "xs: string"/>
</ xs: complexType></ xs: element>

The following sections describe the data types of the instances that the system supports for instance hosting. In the case of the data type of the instance, in addition to the clarity of the processing according to the data type at the time of message transfer between the instances, further use may be made to indicate the unit display code displayed on the instance icon.

The data type of the instance may mean the data type of the unit information provided for each interface of the instance. The system for instance hosting provides basic data types (for example, the World Wide Web Consortium (W3C) Web Interface Definition Language (WebIDL) standard) for ease of development and user's intuitive use of information, Data sets that are frequently used can be provided separately. For example, the data type may be provided as shown in Table 9 below.

Data Type Description Icon Display percent ratio % onoff On / off Control Icon celsius Celsius ° C lockunlock Rock / unlock Control Icon lux Practical unit of lighting Lux kcal Calorie unit Kcal Cal Calorie unit Cal steps step Steps floor layer F kilogram Unit of mass KG gram Unit of mass G hour Unit of time H minute Unit of time min

In addition to the examples in Table 9, various data types may be used, such as millimeters (mm) to represent precipitation and the like.

In instance hosting, a schema structure for collecting essential information when creating virtual objects of objects and business logic can be presented. The main structure may include an instance information recording unit, a description unit of network adapter information for linking the objects in virtualization of objects, a description unit of interface information defined for each instance, and a JS (JavaScript) code description unit. Can be provided as shown in Table 10 below.

<! - Use the instance tag as the top element ->
<xs: element name = "instance">
<xs: complexType><xs:sequence>

<! - It is issued through a web page set up with a unique ID of number, alphabet, and '_' combination of up to 32 characters in length, and basic information related to the Instance is registered at the time of issuance. Represents representative name value ->
<xs: element name = "instanceId">
<xs: simpleType><xs: restriction base = "xs: string">
<xs: pattern value = "[a-zA-Z0-9 _] +"/>
<xs: maxLength value = "32"/>
</ xs: restriction></ xs: simpleType>
</ xs: element>

<! - version with a length of up to 16 characters ->
<xs: element name = "instanceVersion">
<xs: simpleType><xs: restriction base = "xs: string">
<xs: pattern value = "[0-9] (. [0-9]) +"/>
<xs: maxLength value = "16"/>
</ xs: restriction></ xs: simpleType>
</ xs: element>

<! - The main url with information of the Instance ->
<xs: element name = "instanceDetailURL" type = "xs: string"/>
<xs: element name = "instanceDescription" type = "xs: string"/>
<! - Physical location of the icon to use after registering and registering the instance (Icon should be in Png, Jpg format and size is up to 96by96) ->
<xs: element name = "instanceIconURL" type = "xs: string" minOccurs = "0"/>
<! - The duration of the instance is -1, an integer greater than or equal to 1, followed by the size of the maximum decimal value ->
<xs: element name = "instanceRunningPeriod" type = "xs: decimal"/>

<! - If the object is a virtual object, the network adapter related information should be described on the associatedThingInformation element to describe the interworking interface with the object. ->
<xs: element name = "associatedThingInformation"><xs:complexType><xs: all minOccurs = "1">

<! - Enter the name information of the object ->
<xs: element name = "thingName" type = "xs: string"/>
<! - Enter representative image information of object ->
<xs: element name = "thingImageURL" type = "xs: string"/>
<! - Enter additional information of the object ->
<xs: element name = "thingDescription" type = "xs: date"/>

<! - Providing information of objects (sending) Physical interface virtualization ->
<xs: element name = "feederInformation"><xs:complexType>
<! - Information to connect the message received from the object to the subscriber interface of the instance. The value of the attribute describes the ID value of the Subscriber Interface to be connected. ->
<xs: attribute name = "connectedInterfaceId" type = "xs: unsignedShort"/>
<! - Enter the information of the physical interface (zigbee, wifi) to be used when linking with objects ->
<xs: attribute name = "interface" type = "xs: string"/>
<! - MAC address value to send information of object when linking with object ->
<xs: attribute name = "src_mac_addr" type = "xs: string"/>
<! - IP address value of object when linking with object ->
<xs: attribute name = "src_ip_addr" type = "xs: string"/>
<! - Destination IP address value of message delivered by object when linking with object (Information to use when hooking message through network adapter) ->
<xs: attribute name = "dst_ip_addr" type = "xs: string"/>
<! - TCP port value of object when connected with object ->
<xs: attribute name = "src_tcp_port" type = "xs: string"/>
<! - Destination TCP Port value of the message delivered by the object when connected with the object (information to use when hooking message through Network Adapter) ->
<xs: attribute name = "dst_tcp_port" type = "xs: string"/>
<! - UDP Port value of object when linking with object ->
<xs: attribute name = "src_udp_port" type = "xs: string"/>
<! - destination UDP Port value of the message delivered by the object when connected with the object (information to use when hooking message through Network Adapter) ->
<xs: attribute name = "dst_udp_port" type = "xs: string"/>
<! - Address value for HTTP request when using HTTP message communication method in conjunction with object ->
<xs: attribute name = "http_request_uri" type = "xs: string"/>
</ xs: complexType></ xs: element>

<! - Virtualization of the physical interface of receiving information of objects ->
<xs: element name = "receiverInformation"><xs:complexType>
<! - This is the information to connect with the controller interface of the instance for the message to be received. The value of the attribute describes the ID value of the Controller Interface to be connected. ->
<xs: attribute name = "connectedInterfaceId" type = "xs: unsignedShort"/>
<! - Enter the information of the physical interface (zigbee, wifi) to be used when linking with objects ->
<xs: attribute name = "interface" type = "xs: string"/>
<! - MAC address value of the interface to be received when the object is linked with the object ->
<xs: attribute name = "dst_mac_addr" type = "xs: string"/>
<! - IP address value of object when linking with object ->
<xs: attribute name = "src_ip_addr" type = "xs: string"/>
<! - Destination IP address value of message delivered by object when linking with object (Information to use when hooking message through network adapter) ->
<xs: attribute name = "dst_ip_addr" type = "xs: string"/>
<! - TCP port value of object when connected with object ->
<xs: attribute name = "src_tcp_port" type = "xs: string"/>
<! - Destination TCP Port value of the message delivered by the object when connected with the object (information to use when hooking message through Network Adapter) ->
<xs: attribute name = "dst_tcp_port" type = "xs: string"/>
<! - UDP Port value of object when linking with object ->
<xs: attribute name = "src_udp_port" type = "xs: string"/>
<! - destination UDP Port value of the message delivered by the object when connected with the object (information to use when hooking message through Network Adapter) ->
<xs: attribute name = "dst_udp_port" type = "xs: string"/>
<! - Address value for HTTP request when using HTTP message communication method in conjunction with object ->
<xs: attribute name = "http_request_uri" type = "xs: string"/>
</ xs: complexType></ xs: element>

</ xs: all></ xs: complexType></ xs: element>

The above-described instance manager is an operating environment for providing a virtual objectization operating environment. For example, the instance manager may use a V8-based JavaScript engine, and may include an instance pool for instance hosting and a message router.

7 is a block diagram illustrating an instance manager in an embodiment of the present invention. The instance manager 700 includes a message router 710 for routing input / output messages, an instance lifecycle manager 710 for managing and scheduling the life cycle of the instance, 720, an instance pool 730 for instance pooling, and an engine V8 740 for providing an instance operating environment.

The interface server 750 provides an interface function between the instance manager 700 and other modules and an external service. The interface server 750 structurally includes a server module and other modules for receiving and processing requests, and a client (Client Module).

The function of the server interface through the server module of the interface server 750 is as follows.

Instance State Query Function When an Instance Application Server (IAS) and a Network Adapter (NA) want to know the status of an instance running on the Instance Manager 700, HTTP (Hyper Text Transfer Protocol A function that allows the status information of a specific instance to be known through a request.

Instance State Control (Instance State Control) - The ability to change the state of an instance to Run / Stop / Suspend through HTTP request when changing the state of a specific instance in the instance application server. .

Instance Deploy Control - The ability to pass information about an instance to the instance manager 700 via an HTTP request when a new instance is installed or an existing instance is deleted through the instance application server.

Thing Feed Control - The ability to send a physical Thing message received from a network adapter to the instance in the form of an HTTP request.

Instance State Control for Representative Control (Instance State Control for Representative Controller) - The ability to deliver a message in the form of an HTTP request when the instance state is changed through the control of the representative value of a particular instance from the instance application server.

The function of the client interface through the client module of the interface server 750 is a function of transmitting a message using a client interface when a specific instance makes a connection request to an external service (when a specific instance uses an OAuth authentication service) . &Lt; / RTI &gt;

7, the Instance API Handler can manage an open API to be provided externally with respect to an instance, and the DB Connector is a Relational Data Base Management System (RDBMS) Lt; / RTI &gt;

8 is a flowchart for explaining an instance status query function in an embodiment of the present invention. The instance application server (IAS) can query the instance manager 700 through the instance status query function to provide status information for individual instances. The state management of the individual instances on the running instance manager 700 can be handled by the instance life cycle manager 720 and the instance life cycle manager 720 can use the instance identifier (ID) . &Lt; / RTI &gt; The state information of the instance may have status values such as Run, Suspend, Stop and Error.

In step 810, the interface server 750 may receive the HTTP request message through the server module. In one example, the interface server 750 may receive an HTTP request message from an instance application server (IAS), a network adapter (NA), or an external web service (EWS).

In step 820, the interface server 750 may generate a message to obtain the instance status and forward it to the message router 710.

In step 830, the message router 710 may parse the message to obtain the instance status and forward it to the instance lifecycle manager 720. [

In step 840, the instance lifecycle manager 720 may query the registered instance state information to generate a status message for the instance if the instance identifier is successfully queried. If the instance identifier search fails, No message can be generated. For example, the status message may include status values such as Run, Suspend, Stop, and Error.

In step 850, the interface server 750 may provide a response to the HTTP request message through the server module. In one example, the interface server 750 may provide a status message or no information message, which is generated in step 840, in response to the HTTP request message through the server module.

9 is a flowchart for explaining an instance state control function in an embodiment of the present invention. The instance application server can use the instance state control function if it wants to change the state for an individual instance. When a message is delivered using the identifier information of the instance whose state is to be changed, the instance lifecycle manager 720 can change the state of the instance. At this time, the changeable state may include a state of Run, a state of Suspend, and a state of Stop.

In step 910, the interface server 750 may receive the HTTP request message through the server module. In one example, the interface server 750 may receive an HTTP request message from an instance application server, a network adapter, or an external web service.

In step 920, the interface server 750 may generate a message for instance state setup and forward it to the message router 710.

At step 930, the message router 710 may parse the message for instance status establishment and forward it to the instance lifecycle manager 720. [

In step 940, the instance lifecycle manager 720 may query the registered instance state information to change the state information for the instance if the instance identifier is successfully queried. If the instance identifier search fails, Message can be generated. For example, when the instance identifier is successfully retrieved, the instance lifecycle manager 720 changes the state of the instance to a state of one of Run, Suspend, and Stop according to the HTTP request message. .

In step 950, the interface server 750 may provide a response to the HTTP request message through the server module. In step 940, the interface server 750 may provide a response message or a no information message, which is generated according to the change of the status information, in response to the HTTP request message through the server module.

10 is a flowchart for explaining an instance installation control function in an embodiment of the present invention. Instance The application server can take advantage of instance installation control if you want to deploy a new instance or to undeploy an existing instance. When a message is delivered using the instance identifier information for which the state is to be changed, the instance lifecycle manager 720 can change the state of the instance. At this time, the deleted instance may be excluded from the instance pool 730.

In step 1010, the interface server 750 may receive the HTTP request message through the server module. In one example, the interface server 750 may receive an HTTP request message from an instance application server, a network adapter, or an external web service.

In step 1020, the interface server 750 may generate an instance install message or an instance delete message and forward it to the message router 710.

In step 1030, the message router 710 may parse and forward the instance setup message or instance deletion message to the instance lifecycle manager 720.

In step 1040, the instance lifecycle manager 720 may request registration of a new instance and generation of an identifier of a new instance if the forwarded message is an instance installation message, and if the forwarded message is an instance deletion message, Can be deleted. At this time, the registration of the new instance and the request for the generation of the identifier can be forwarded to the instance pool 730, and when a new instance is created in the instance pool 730, the identifier of the created instance is stored in the instance lifecycle manager 720 ). &Lt; / RTI &gt; In addition, the instance lifecycle manager 720 inquires the registered instance state information for deletion of the corresponding instance, and if the instance identifier is successfully retrieved, the instance lifecycle manager 720 changes the state of the instance to a stop state, You can delete information about an instance.

In step 1050, the interface server 750 may provide a response to the HTTP request message through the server module. For example, if a new instance is created according to the instance installation message, the interface server 750 may provide a message including the identifier of the created new instance. As another example, if the instance is deleted according to the delete instance message, the interface server 750 may provide a message to notify that the instance has been deleted. As another example, if the instance to be deleted is not registered in the instance lifecycle manager 720, the interface server 750 may provide an instance information message.

11 is a block diagram illustrating an object feed control function in an embodiment of the present invention. The object feed control function can provide a function to dispatch a message of a received object from a network adapter to a specific instance. When the interface server 750 receives a message from the network adapter using the server module, the interface server 750 can deliver the message to the message router 710 using the HTTP request method, and can transmit the response message to the network adapter. The message router 710 may add a message received from the server module of the interface server 750 to the corresponding instance feed using a separate thread and may use a trigger The instances can be registered in the instance scheduler on the instance lifecycle manager 720 so that they can be invoked.

In step 1110, the network adapter can recognize information on a transmitting apparatus (object) of the message using message listening table information. For example, the network adapter can acquire the necessary instance identifier by recognizing information about the object that transmits the message through the message listening table.

In step 1120, the network adapter may send an HTTP request message to the server module of the interface server 750.

In step 1130, the interface server 750 may receive the HTTP request message through the server module and forward it to the message router 710.

In step 1140, the message router 710 may determine whether the instance exists in the instance pool 730 and store the data associated with the HTTP request message in the message queue of the subscriber interface of the instance.

In step 1150, the message router 710 may provide a response to the HTTP request message through the server module of the interface server 750.

12 is a flowchart for explaining a schedule registration method according to an embodiment of the present invention. The steps included in the schedule registration method according to the present embodiment may be included between steps 1140 and 1150 described in FIG.

In step 1210, the message router 710 may notify the instance lifecycle manager 720 of the message feed information update for the particular instance.

In step 1220, the instance lifecycle manager 720 may determine whether to trigger the subscription instances for the feed of the instance, and register the schedule for the instance in which the trigger exists. In one example, the registered schedule may include a schedule for immediate operation of the instance.

In step 1150 of FIG. 11, if the schedule for the instance in which the trigger described in FIG. 12 exists is registered, the message router 710 sends a message from the device (object) to the instance in accordance with the HTTP request message from the network adapter It is possible to provide a response in response to the notification. Conversely, if a schedule for an instance in which a trigger exists is not registered, the message router 710 may respond in a message indicating that the instance does not exist.

13 to 15 are diagrams for explaining an instance wizard in an embodiment of the present invention.

The first screen 1300 shows a first step of inputting instance information using the instance wizard provided through the web. In the first step, information on the name of the instance, the tag, the URL where the profile of the IoT node is stored, and the like can be inputted.

The second screen 1400 shows a second step of inputting the instance information using the instance wizard provided through the web. In the second step, a user interface for selecting the instance icon, a user interface for selecting the state of the instance, a user interface for selecting the controller, a user interface for selecting the unit of the representative value, Various information about the instance can be input using the provided user interfaces.

The third screen 1500 shows a third step of inputting the instance information using the instance wizard provided through the web. In the third step, information for receiving the conditional information through the external service related to the user can be set.

For example, information about the amount of water at one IoT node (based on the URL of the profile) can be sensed through the first screen 1300, and the amount of water from the IoT node to the instance manager via the network adapter A message containing information can be transmitted. At this time, as described with reference to FIGS. 11 and 12, the message may be processed and the operation of the instance may be scheduled. At this time, as shown in the third screen 1500, when the amount of water becomes less than 10%, a notification can be provided through the external service A. In this case, the data type for the ratio may be set for the condition that the second screen 1400 is less than 10%.

16 is a diagram for explaining an additional setting and an external service authentication request for a mashup instance in an embodiment of the present invention. The mashup instance handles inter-instance interactions. Accordingly, in the screen 1600, an interface for selecting a feeder interface for a subscriber interface for a mashup instance according to a representative value (sensor side) and a receiver interface for a controller interface are selected according to a representative value (control device side) Respectively. In addition, the mashup instance handles interworking between instances and external services. Accordingly, the screen 1600 shows an interface for an authentication request (OAuth request) to an external service.

17 is a diagram for explaining an open API in an embodiment of the present invention. Screen 1700 represents an interface for setting an open API for values exposed through an instance feeder interface. For example, in the screen 1700, an interface for setting an open API for each instance of 'Livingroom' and 'Hee's room' is shown. As already described, the feeder interface can read a message received from a device (object) and then forward it to another service (external service). At this time, the function related to the processing of the instance can be provided to the external service in the form of API. At this time, a description document for an open API to be provided as an external service may be provided, and a URL for the description document may be provided as shown in an example of Table 11 below.

http: //$userID$.instancehosting.com/instanceId/$instanceID$/description.html
* Variable values are indicated by '$'.

In the screen 1700, 'Key / URL' may provide an interface for inputting the URL for the above described description document.

18 is a flowchart showing a service method in an embodiment of the present invention. A service method according to the present embodiment can be performed by a service system including at least one storage unit and at least one processor in which at least one program is stored. At this time, the steps included in the service method may be processed by at least one processor in accordance with control of at least one program.

In step 1810, the service system can check information about an instance of a virtualization object for a Thing, which is input through a step-by-step setting function of a web page provided to the user. For example, the step-by-step setting function includes a user interface for inputting a name of an instance, a user interface for inputting a tag of the instance, a user interface for inputting a URL storing a profile of the IoT node, A user interface for selecting a state of an instance, a user interface for selecting a state of an instance, a user interface for selecting a controller, and a user interface for selecting a unit of a representative value.

In step 1820, the service system may perform authentication with the external service using the information on the external service input through the external service connection function of the web page. For example, the external service connection function may include a user interface for receiving the user's account information for the external service.

In step 1830, the service system may provide an open API to an external service using the information input through the open API (application program interface) setting function of the web page. For example, the open API setting function may include a user interface for receiving location information including a description document of the open API.

The service method according to another embodiment may further include a step (not shown) of displaying an instance-specific icon via a web page in addition to the steps 1810 to 1830 described with reference to FIG. At this time, the control function for the instance and the representative value of the instance can be displayed through the area where the icon is displayed. For example, for instances that output temperatures, information such as '23 ° C' may be displayed as a representative value. The control function for the instance may include an on / off setting function or a lock / unlock setting function. Further, the state of the instance can be further displayed through the region, optionally as required. For example, the status of an instance can be displayed according to the color of the status bar.

The service method according to another embodiment may include a step (not shown) of receiving a user's request and a step (not shown) of providing a web page according to a request of the user. At this time, the web page includes a step-setting function for receiving information on an instance of a virtualization object for a Thing, an external service connection function for receiving information for authentication with an external service, And an open API setting function for inputting information about the open API for providing the open API. A service method according to this alternative embodiment may be performed by a service system comprising at least one storage unit and at least one processor in which at least one program is stored. At this time, the steps included in the service method may be processed by at least one processor in accordance with control of at least one program.

As described above, according to the embodiments of the present invention, heterogeneous devices and various services can be interlinked or fused in IoT (Internet of Things), WoT (Web of Things) or WoO (Web of Objects) Service can be provided.

The apparatus described above may be implemented as a hardware component, a software component, and / or a combination of hardware components and software components. For example, the apparatus and components described in the embodiments may be implemented within a computer system, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA) A programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to execution of the software. For ease of understanding, the processing apparatus may be described as being used singly, but those skilled in the art will recognize that the processing apparatus may have a plurality of processing elements and / As shown in FIG. For example, the processing unit may comprise a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as a parallel processor.

The software may include a computer program, code, instructions, or a combination of one or more of the foregoing, and may be configured to configure the processing device to operate as desired or to process it collectively or collectively Device can be commanded. The software and / or data may be in the form of any type of machine, component, physical device, virtual equipment, computer storage media, or device , Or may be permanently or temporarily embodied in a transmitted signal wave. The software may be distributed over a networked computer system and stored or executed in a distributed manner. The software and data may be stored on one or more computer readable recording media.

The method according to an embodiment may be implemented in the form of a program command that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions to be recorded on the medium may be those specially designed and configured for the embodiments or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. For example, it is to be understood that the techniques described may be performed in a different order than the described methods, and / or that components of the described systems, structures, devices, circuits, Lt; / RTI &gt; or equivalents, even if it is replaced or replaced.

Therefore, other implementations, other embodiments, and equivalents to the claims are also within the scope of the following claims.

Claims (15)

In a service method in an Internet of Things (IoT) environment,
Confirming information about an instance of a virtualization object for a Thing inputted through a step-by-step setting function of a web page provided to a user;
Performing authentication with the external service using information about the external service input through the external service connection function of the web page; And
Providing the open API to the external service using the information input through the open API (Application Program Interface) setting function of the web page
/ RTI &gt; The method according to claim 1,
Displaying an instance-specific icon via the web page
Lt; / RTI &gt; 3. The method of claim 2,
Wherein a control function for an instance and a representative value of the instance are displayed through an area in which the icon is displayed. The method of claim 3,
And the status of the instance is further displayed through the region. In a service method in an Internet of Things (IoT) environment,
Receiving a request from a user; And
Providing a web page at the request of the user
Lt; / RTI &gt;
The web page includes:
A step-setting function for receiving information on an instance of a virtualization object for a Thing;
An external service connection function for receiving information for authentication with an external service; And
An open API setting function for inputting information on an open API to be provided to the external service
Lt; RTI ID = 0.0 &gt; 1, &lt; / RTI &gt; 6. The method according to claim 1 or 5,
The step-by-step setting function includes a user interface for receiving a name of an instance, a user interface for receiving a tag of the instance, a user interface for receiving a URL storing a profile of the IoT node, a user interface for selecting an instance icon, A step of exposing a plurality of user interfaces among a user interface for selecting a state of an instance, a user interface for selecting a controller, and a user interface for selecting a unit of representative value to the user step by step. 6. The method according to claim 1 or 5,
Wherein the external service connection function includes a user interface for receiving account information of the user with respect to the external service. 6. The method according to claim 1 or 5,
Wherein the open API setting function includes a user interface for receiving location information including a description document of an open API. 6. The method of claim 5,
The web page includes:
Icon display function for displaying icon by instance
Lt; / RTI &gt; In a service system in an Internet of Things (IoT) environment,
At least one storage unit in which at least one program is stored; And
At least one processor
Lt; / RTI &gt;
Wherein the at least one processor is operable, under control of the at least one program,
A step of confirming information about an instance of a virtualization object for a Thing inputted through a step-by-step setting function of a web page provided to a user;
Performing authentication with the external service using information about the external service inputted through the external service connection function of the web page; And
A process of providing the open API to the external service using information input through an open API (Application Program Interface) setting function of the web page
Of the service system. 11. The method of claim 10,
Wherein the at least one processor comprises:
Displaying the icon for each instance through the web page
Is further processed. In a service system in an Internet of Things (IoT) environment,
At least one storage unit in which at least one program is stored; And
At least one processor
Lt; / RTI &gt;
Wherein the at least one processor is operable, under control of the at least one program,
Receiving a request from a user; And
A process of providing a web page at the request of the user
Lt; / RTI &gt;
The web page includes:
A step-setting function for receiving information on an instance of a virtualization object for a Thing;
An external service connection function for receiving information for authentication with an external service; And
An open API setting function for inputting information about an open API to be provided to the external service
And the service system. 13. The method according to claim 10 or 12,
The step-by-step setting function includes a user interface for receiving a name of an instance, a user interface for receiving a tag of the instance, a user interface for receiving a URL storing a profile of the IoT node, a user interface for selecting an instance icon, A step of exposing a plurality of user interfaces among a user interface for selecting a state of an instance, a user interface for selecting a controller, and a unit for selecting a representative value unit to the user step by step. 13. The method according to claim 10 or 12,
Wherein the external service connection function includes a user interface for receiving account information of the user with respect to the external service. 13. The method according to claim 10 or 12,
Wherein the open API setting function includes a user interface for receiving location information including a description document of an open API.

Images