KR101478902B1 - Method and system for providing service based on profile according to node property in instance hosting environment - Google Patents

Abstract

A method and system for providing a service based on a profile according to node-specific characteristics in an instance hosting environment. The service providing method includes: generating an IoT profile using information about the IoT node provided from a developer of an Internet of Things (IoT) node; storing the IoT profile in the IoT profile database and managing or providing the IoT profile to the developer; (1) the IoT profile stored in the IoT profile database; (2) the IoT profile provided to the developer and provided via a URL associated with the developer; IoT profile, or (3) the IoT node is registered using the IoT profile provided to the developer and included in the IoT node.

Description

[0001] METHOD AND SYSTEM FOR PROVIDING SERVICE BASED ON PROPERTIES IN INSTANCE HOSTING ENVIRONMENT [0002]

Embodiments of the present invention are directed to a method and system for providing a service based on a profile according to node-specific characteristics in an instance hosting 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 evolution and diffusion of these concepts and technologies, it is expected that the use of devices (gadget devices, sensor devices, actuators, etc.), which users can easily connect to the Internet, will increase.

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.

Generating an IoT profile using information about the IoT node provided from a developer of an Internet of Things (IoT) node; and storing the IoT profile in the IoT profile database and managing or providing the IoT profile to the developer (1) the IoT profile stored in the IoT profile database; (2) the IoT profile provided through the URL provided to the developer and associated with the developer; or (3) the IoT profile provided to the developer, Wherein the IoT node is provided to a developer and the IoT node is registered using the IoT profile included in the IoT node.

According to one aspect, the information on the information about the IoT node includes at least one of a URL associated with the developer, and a URL of process information associated with the IoT profile.

According to another aspect, the information on the information about the IoT node may include at least one of a unit, a minimum value, and a maximum value as information on a data stream produced by the IoT node.

According to another aspect of the present invention, the step of generating the IoT profile may include processing the information about the IoT node according to a predetermined XML Schema Definition (XSD) to generate the IoT profile .

According to another aspect of the present invention, a data stream of the IoT node is provided through an external API generated using the information of the IoT profile at the instance hosting gateway.

According to another aspect of the present invention, the data log of the IoT node is provided in a form of JavaScript Object Notation (JSON) or XML (eXtensible Markup Language).

An IoT profile generation unit for generating an IoT profile using information about the IoT node provided from a developer of an Internet of Things (IoT) node; an IoT profile database for storing and managing the IoT profile; (1) the IoT profile provided to the instance hosting gateway, (2) the IoT profile provided to the developer and provided to the instance hosting gateway provided by the IoT node, The IoT profile provided through the URL associated with the developer, or (3) the IoT node provided to the developer and included in the IoT node.

An IoT profile receiving unit that receives the IoT profile of the IoT node through an IoT node requesting a connection, a URL associated with a developer of the IoT node or an IoT profile database of a server generating an IoT profile of the IoT node; And an IoT node registration unit for registering an IoT node requesting the connection based on the information about the IoT node provided by the developer of the IoT node and the predefined XML schema definition, And an instance hosting gateway is provided.

Receiving the IoT profile of the IoT node through an IoT node requesting a connection, a URL associated with a developer of the IoT node or an IoT profile database of a server generating an IoT profile of the IoT node; Registering an IoT node requesting the connection, and generating an external API for providing the data stream of the IoT node to the outside using the IoT profile.

In the Internet of Things (IOT), Web of Things (WoT), or Web of Objects (WoO) environments, heterogeneous devices and various services can be interlinked or fused to be managed and integrated.

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 block diagram for explaining an example of an internal structure of an instance hosting gateway, in an embodiment of the present invention.
5 is a block diagram for explaining an example of a network adapter in an embodiment of the present invention.
6 is a block diagram for explaining an example of an instance manager in an embodiment of the present invention.
7 is a block diagram for explaining an example of an instance application server according to an embodiment of the present invention.
8 is a diagram for explaining an example of an instance hosting platform in another embodiment of the present invention.
9 is a block diagram illustrating an internal configuration of an instance hosting platform in another embodiment of the present invention.
10 is a diagram illustrating an example of a process of creating and utilizing an IoT profile in an embodiment of the present invention.
11 is a flowchart illustrating an example of a method for setting an open API for external exposure 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 may correspond to objects of the IoT environment such as a sensor device, and may 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 block diagram for explaining an example of an internal structure of an instance hosting gateway, in an embodiment of the present invention. The instance hosting gateway 330 according to the present embodiment includes a network adapter 410, a network handler 420, an instance manager 430, and an instance An application server 440, and the like.

The network adapter 410 may provide a function of physically connecting to the IoT node through a wired or wireless network through a network interface standard supported by the instance hosting gateway 330. For example, the network adapter 410 may be a wireless LAN such as Zigbee, Bluetooth, Z-wave, Ethernet, Wi-Fi, USB (Universal Serial Bus) And the like. In addition, a message parsing function may be additionally provided for message processing according to each network interface standard.

In particular, in the IoT environment, the IoT nodes use various message formats according to their respective characteristics. Therefore, when the proximity network interface technology such as Zigbee, Bluetooth, GeWave, etc. is used, It is possible to further provide a function of structuring the message data received from the nodes according to the instance-specific format.

Such a network adapter 410 will be described later in more detail with reference to FIG.

The network handler 420 may forward the message received from the network adapter 410 to the instance manager 430. In addition, when the network adapter 410 uses ZigBee, the network handler 420 may perform a function of adding an instance ID (Instance ID) assigned by the system to a message value structured in accordance with the instance-specific format.

The instance manager 430 is a module for performing core functions for instance hosting and can provide a function of deploying IoT profiles and processes. The role of interworking messages of individual IoT nodes with instances, And the like.

The instance manager 430 will be described later in more detail with reference to FIG.

The instance application server 440 may be responsible for the web application server function of the instance hosting gateway 330. At this time, the functions provided through the instance application server 440 may be provided as a web interface.

The instance application server 440 will be described later in more detail with reference to FIG.

5 is a block diagram for explaining an example of a network adapter in an embodiment of the present invention. The network adapter 410 according to the present embodiment may be a wireless LAN such as Zigbee, Bluetooth, Z-wave, Ethernet, Wi-Fi, ), And the like, can be provided. In addition, the network adapter 410 may provide a function for ensuring the integrity of data received by distinguishing messages for each interface and for each device in the interface. In order to process messages in accordance with each network interface standard, And a message parser 510 for providing a parsing function.

The message parser 510 may be used to obtain structure information of a message associated with an individual instance during an instance deployment. At this time, the message parser 510 can parse the message according to the message format provided by the individual terminal device (IoT node). For example, different message formats may be used between devices using the same ZigBee network interface.

6 is a block diagram for explaining an example of an instance manager in an embodiment of the present invention. The instance manager 430 according to the present embodiment includes a message router 610, a loader 620, an updater 630, a deployer 640, A controller (Instance Lifecycle Controller) 650 and a logger (Logger) 660. In addition, the instance hosting gateway 330 described in FIG. 4 may further include a database (Simple DB) 670 and a JavaScript engine (JavaScript engine) 680 as needed.

The message router 610 may route the requested message from the network handler 420 or the instance application server 440 described with reference to FIG. At this time, basically, all the transactions of the message router 610 can be logged.

The loader 620 may be responsible for calling individual instances when processing a process instance by instance. In addition to the message based call, the loader 620 may also provide a call function for instances that must be self-called based on a timer. For example, the loader 620 may provide the ability to invoke the JavaScript engine 680 in invoking the instance process by matching the methods of the individual processes that the received data should invoke. To this end, the loader 620 may provide a function for determining a calling method for each message parameter.

The updater 630 may perform the function of downloading the externally existing IoT profile and process information to the instance hosting gateway 330.

The deployer 640 can perform the role of parsing the information of the IoT profile and registering the process information in the instance manager 430. Individual IoT profiles and process information can be formally used as instance hosting services through the deployment process.

The instance life cycle controller 650 is a module that provides a function of managing the life cycle of an instance and can provide functions for controlling the loader 620, the updater 630, and the deployer 640. For example, the instance lifecycle controller 650 may control the functions of the instance manager 430 and may provide a contact function with an instance management unit (Instance Mgmt.) To be described later.

The logger 660 may provide a function to log data input / output and application operating information occurring in the instance manager 430. [

The database 670 may store data of the IoT node.

The JavaScript engine 680 may process JavaScript. For example, the instance process of an IoT node can be handled according to the syntax of JavaScript, and can be used as a standalone programming language, unlike scripts in the Web environment running in a browser. At this time, the JavaScript engine 680 may be used to process the JavaScript syntax of this process. As another example, each function of the instance application server 440 may be based on JavaScript.

7 is a block diagram for explaining an example of an instance application server according to an embodiment of the present invention. The instance application server 440 according to the present embodiment may include an API Exposure 710 and a Management Portal 720 as shown in FIG.

The API-exposing unit 710 can perform a function of externally providing functions provided by the instance hosting gateway 330 in an API form. 7, the API exposure unit 710 includes a rest pool management unit 711, a feeder 712, an API trigger 713, a key generator 713, ) 714 and an authentication unit (OAuth) 715.

The rest pool management unit 711 can provide the input value and the output value of the IoT node instance to the interface of the rest pool management unit 711 based on the information of the IoT profile.

The feeder 712 may provide the output value of the IoT node instance in the form of a feed based on the information of the IoT profile. At this time, the format provided in the form of a feed may follow the format of at least one of JavaScript Object Notation (JSON) and XML.

API trigger 713 may provide the ability to trigger an external API, such as third-party (3 ^rd party) API. At this time, if the message includes an API triggering function according to the service characteristic of the instance, the API trigger 713 can push a message to the API.

The key generation unit 714 may provide a key generation function for controlling access authentication for interworking with external services.

The authentication unit 715 may provide a function for authentication when interworking with external services. For example, the authentication unit 715 may perform authentication for external services using the key generated by the key generation unit 714. [

The management portal 720 may provide functionality for the user to manipulate the functionality of the instance hosting gateway 330 through a web or application. 7, the management portal 720 includes a user management unit 721, an instance management unit 722, a system management unit 723, (API Mgmt.) 724, as shown in FIG.

The user management unit 721 can provide a user account management function (user interface) in a web form.

The instance management unit 722 can provide an instance management function (user interface) in a web form.

The system management unit 723 can provide a system management function (user interface) in a web form.

The API management unit 724 can provide an API management function (user interface) in the form of a web.

As described above, at least some of the elements constituting the instance hosting gateway 330 according to the present embodiment may be implemented in software form. In this case, at least a part thereof may be provided in the form of an application including a plurality of modules, and a file distribution system for providing a file for installation of such an application may be provided. In one embodiment, the application includes a module for connecting through a wired or wireless network with a plurality of nodes to receive data from a plurality of nodes and a module for receiving data from a plurality of nodes using profiles and processes provided for the plurality of nodes. And a module for interworking and processing data received from at least two nodes in one instance. In another embodiment, such an application may be installed in an access point (AP) to which a plurality of nodes are connected. These modules may vary depending on which of the elements constituting the instance hosting gateway 330 is implemented in software.

In addition, a service providing method including the steps performed by the instance hosting gateway 330 according to the present embodiment may be provided. For example, a method of providing a service may include connecting to a plurality of nodes via a wired or wireless network to receive data from a plurality of nodes, using profiles and processes provided for the plurality of nodes, Processing the data received from at least two or more nodes in a single instance and processing the result, and providing the result of the processing to the user via the web or application. In another embodiment, the step of processing the data received from at least two nodes in one instance in an interlocked manner includes the steps of calling the individual instance to process the instance by instance and managing the life cycle of the individual instance And the like.

8 is a diagram for explaining an example of an instance hosting platform in another embodiment of the present invention. The instance hosting platform 340 described in the embodiment of FIG. 3 receives and processes APIs on-line from the instance hosting gateway 330 installed in an AP in a specific space, and performs inter-instance interworking functions and mash- Function. The instance hosting platform 800 according to another embodiment illustrated in FIG. 8 may provide a service on-line in the form of a combination of the instance hosting gateway 330 and the instance hosting platform 340 of FIG.

The instance hosting platform 800 of FIG. 8 includes components for connection to the outside, such as an instance hosting manager 810, a first network adapter 820 and a second network adapter 820. [ 830 < / RTI > Other components that the instance hosting platform 800 may include are described in more detail in FIG.

The instance hosting manager 810 may provide a function for connecting with an end user. The end user may refer to a terminal used by users of the IoT nodes and may communicate with the instance hosting platform 800 through at least one web browser and at least one application installed in the terminal.

The first network adapter 820 may provide functionality for connection to personal instances representing various external services such as social network services, map services, weather services, and the like. For example, the first network adapter 820 may be used for connections with servers that provide various external services. The information of the instance according to the external service may exist in the form of individual service.

The second network adapter 830 may include functionality for coupling with various IoT nodes. For example, the instance hosting platform 800 may provide services in cooperation with existing IoT nodes that provide services in various forms, such as the devices 130 and 220, respectively, illustrated in FIGS. 1 and 2 It can be possible.

9 is a block diagram illustrating an internal configuration of an instance hosting platform in another embodiment of the present invention. The instance hosting platform 800 according to the present embodiment includes an instance update manager 840, an instance BUS 850, an instance pool (not shown) 860, an Instance Logger 870, an Instance Monitor 880, and an Instance Lifecycle Manager 890.

The instance update manager 840 can perform functions of downloading, updating, storing, and managing an instance hosting profile and a personal instance profile. The instance hosting profile may correspond to the IoT profile already described, and the individual instance profile may include a profile for the individual instances described in FIG. For example, a profile for individual instances may be provided by a provider or developer providing external services.

The instance bus 850 may provide message bus functionality between instances. For example, the data 'D1' of the IoT node 130 stored in the instance pool 860 to be described later is provided through the instance bus 850 in response to a request from the web server 210 in communication with the IoT node 220 . The instance bus 850 may also provide mutual authentication functionality.

The instance pool 860 may refer to an execution environment of the instances, and may be a space where the instances are executed, which means a space where individual processes are deployed. Additionally, it can provide functions for loading and storing instances, and managing instances and instance pool 860. The instance pool 860 may process an instance in a wake-up form using a timer or the like, depending on the characteristics of the instance. Since data for various IoT nodes can be transferred to the instance pool 860 via the instance bus 850, data transmitted from IoT nodes using heterogeneous or different protocols can be interlocked and fused It becomes possible to provide a service.

Instance logger 870 can handle logging of messages associated with the instance.

The instance monitor 880 may monitor whether the instance is operating normally.

The instance lifecycle manager 890 can manage the periodic / repetitive operation function of the instance.

In addition, a service providing method including steps performed by the instance hosting platform 800 according to the present embodiment may be provided. For example, a service providing method includes relaying a node or a web server equipped with an embedded Web server to receive data through a connected node, exchanging data between instances, and providing profiles and processes And processing data received from at least two of the plurality of nodes in a single instance by using the plurality of nodes. In another embodiment, the method of providing a service may further include downloading and managing profiles and personal instance profiles, and associating with an external service including a web service using a personal instance profile.

Hereinafter, the IoT profile will be described in more detail.

10 is a diagram illustrating an example of a process of creating and utilizing an IoT profile in an embodiment of the present invention. FIG. 10 shows a service provider system 1010 and a developer system 1020.

The service provider system 1010 may be a system of a service provider providing the service of the instance hosting gateway, and the developer system 1020 may be a system used by the developer (or developer) of the IoT node. For example, the service provider system 1010 may be a server that the service provider provides to create and manage an IoT profile, and the developer system 1020 may be a client used by the developer to access a web site provided by the server Lt; / RTI >

The developer can access the website provided by the service provider system 1010 using the developer system 1020 to input information about the IoT node.

At this time, the service provider system 1010 can generate the IoT profile using the information about the IoT node received through the website. For example, the service provider system 1010 may include an IoT profile generation unit 1011, and the IoT profile generation unit 1011 may use the information about the received IoT node and the XML Schema Definition (XSD) 0.0 > 1011). ≪ / RTI >

The generated IoT profile may be stored and managed in the service provider system 1010. For example, the service provider system 1010 may include an IoT profile database 1012, and the generated IoT profiles may be stored and managed in the IoT profile database 1012. [ The IOT profile database 1012 can be implemented as a Universal Description Discovery and Integration (UDDI), which is a repository for registering and searching Web services. The generated IoT profile may also be provided to the developer system 1020.

The information on the IoT node provided by the developer may include, for example, the information shown in Table 2 below.

Element Description IoT_Profile Root Tag Profile Multiple profiles can be set on one IoT profile url URL information where the corresponding IoT profile is located Display_name The name that represents the profile during the Deploy process. Product_Name The product name (IoT Node Name) Product_image IoT profile provides the image of the product to be modified (loading image information when loading profile) description Description of IoT Node schema Schema for IoT profile created IoT profile creation date version IoT profile version creator IoT Profile Creator Process_url Process URL associated with IoT profile datastream Tag related to data stream (datastream) produced by IoT Node
Various data streams of input / output type can exist in one sensor id Eigenvalues for distinguishing Sensor data streams name Name to distinguish the Sensor data stream units The unit the data stream will use Min_value Minimum value (signed numeric value) Max_value Maximum value (signed numeric value)

The information about the IoT node provided by the developer can be prepared and provided according to a predetermined document generation rule (IoT node schema), and as described above, the service provider system 1010 can provide the IoT node created and provided A function for generating an IoT profile can be provided in the form of a web service. For example, the IoT profile may be generated using the information about the IoT node represented as Table 2, and may include the basic description and interface information of the IoT node.

The generated IoT profile can be distributed through the IoT profile database 1012, or uploaded to the developer's web site and distributed through the developer's web site. Also, as described above, when the IoT node is an NC (Non-Constraint) node such as a smart device, the IoT node includes the IoT profile so that the IoT node directly provides the IoT profile.

Hereinafter, a method for recognizing information provided from individual IoT nodes as information on a service based on the IoT profile in the instance hosting gateway according to the embodiments of the present invention will be described. As described with reference to FIGS. 6 and 7, the instance hosting gateway can download the IoT profile and process information existing externally (see the updater 630 described with reference to FIG. 6). At this time, the instance hosting gateway can provide the input value and the output value of the IoT node instance through the interface (restful interface) of the rest pool management unit based on the information of the IoT profile.

In the case of general content / data aggregation systems, the user must set the exposed API either directly or using a wizard form, and specify the naming of the individual interfaces and the data source to be exposed. .

The instance hosting gateway according to the embodiments of the present invention may provide a function of generating an API for automatically externally exposing a data stream value after reading the IoT profile in connection with the generation of the rest pool interface. For example, an API exposing unit 710 has been described with reference to FIG. 7 for performing a function of externally providing functions provided by an instance hosting gateway in an API form.

11 is a flowchart illustrating an example of a method for setting an open API for external exposure in an embodiment of the present invention. The method of generating the rest pool interface according to the present embodiment can be performed by the instance hosting gateway (or the instance application server included in the instance hosting gateway) according to the embodiments of the present invention.

In step 1110, the instance hosting gateway may load the data stream information. Here, the data stream information may be raw data stream information generated and received at the IoT node. If there is no data stream information for loading, the process for setting the open API may be terminated.

In step 1120, the instance hosting gateway can confirm whether the user agrees. The functionality for APIs for external exposure of registered instances may be provided in a rest pool format. The API generation information can be provided with the user's agreement based on the IoT profile and the information of the individual instances. Accordingly, the instance hosting gateway can confirm whether or not the user agrees to provide the API generation information. If the user does not agree to provide the API generation information, the process for setting the open API may be terminated.

In step 1130, the instance hosting gateway may select a rest pool type or a feed type. Step 1140 may be performed if the rest pool format is selected, and step 1180 may be performed if the feed format is selected.

The rest pool format provides raw data stream information generated by the IoT node directly to the outside through the API web interface. The process of providing raw data stream information is performed by installing an IoT node instance ) Can be performed according to the user's selection. To do this, the instances can individually populate the interface information for external exposures, and the instance hosting gateway can read the instance-mounted information at the time of instance installation and provide it to the user. For example, if you expose the rest pool interface, the form of utilization of the data for each individual instance or the information of the data that can be provided may vary, thus forming a new system address each time. Accordingly, in the present embodiments, in order to provide the rest pool interface, a description document that reads the IoT profile and the process information and provides the rest pool interface in an automated form can be generated, and a URL for the description document can be generated .

In step 1140, the instance hosting gateway may obtain a user identifier (User ID). For example, the management portal 720 described with reference to FIG. 7 can confirm whether the instance is actually owned by each instance. In this case, the instance hosting gateway may obtain the user identity of the user identified in step 1140.

In step 1150, the instance hosting gateway may obtain an instance identifier (Instance ID). The instance identifier may be given for each message received from the IoT node (or for each of the above-described data stream information).

In step 1160, the instance hosting gateway may generate the URL of the API. As described above, in the present embodiment, in order to provide a rest pool interface, the instance hosting gateway reads a description document (an open API to be provided externally) that reads the IoT profile and process information and provides a rest pool interface in an automated form And a URL for such a description document can be generated. Table 3 below is an example of the generated URL.

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

In step 1170, the instance hosting gateway may register the URL generated on the server. For example, if the information about the rest pool interface call for a particular instance is needed for an external 3 ^rd party service, the instance hosting gateway can provide basic information for the related rest pool call in the form of a web page when providing the API. This basic information can be provided through the URL in the form of a descriptive document providing a rest pool interface. Therefore, the instance hosting gateway can refer to this description document in the external 3 ^rd party service by registering the generated URL on the server.

At step 1180, the instance hosting gateway may select a specification. For the feed format, the data log of the IoT node that individual instances store can be provided formatted in JSON or XML format. For example, data stream information of an IOT node may be stored as a data log in association with at least one instance associated with the IoT node. The instance hosting gateway may select at step 1080 whether to provide this data log using JSON or XML. In this case, a function may be provided that allows the user to set whether or not to disclose data in the related fields of the data log. The feed may include interface information for providing a standard (for example, a JSON standard) required when providing information that can be provided for each interface in a data stream or a feed format. At this time, the provision position information of the feed may be generated for each unique information of the individual instance. Table 4 below shows an example of basic data provision values in the JSON-based feed format.

ID Value Description Status String Indicates the operation status of the corresponding feed and can have running, suspend, and stop values title String Title of the Feed Feed URL Feed-specific URL tags String Tag information for this feed description String Description of the Feed created String Date of creation of this feed version String Version Information creator URL The constructor (user ID) updated Date Last Message Update Time id Number Unique Feed ID datastreams  ( current _ value ) If the value of the data you provide is provided in datastream format at String Time + GeoLocation "at": "2012-12-14T05: 25: 57.529014Z", unit String Unit information with label information max _ value String Maximum value of data min _ value String Minimum value of data

In Table 4, the underlined fields may indicate repeated information.

In step 1190, the instance hosting gateway may register the instance identifier. For example, the instance hosting gateway includes a feeder (corresponding to the feeder 712 described with reference to FIG. 7) that can provide the output value of the IoT node instance in the form of a feed based on the information of the IoT profile can do. The instance hosting gateway may register the instance identifier to this feeder at step 1090 and the data log may be formatted according to the established specification via the registered instance identifier and provided externally.

In addition, in an embodiment of the present invention, it is possible to support a function for avoiding a security hole when requesting a full pool type. In the instance hosting gateway according to the present embodiment, the rest pool can provide the authentication function in two ways, a key type and an 'OAuth' type.

First, when a rest pool interface is requested in the form of a key, the URL of the API can be configured as shown in Table 5 below.

http: //$userID$.instancehosting.com/instanceId/$instanceID$/key/
$ tokenKey $ / start / $ startingPoint $ / display / $ requestCount $

In addition, the 'OAuth' type can proceed according to the normal OAuth authentication process, and the instance hosting gateway can provide the function of the service provider role. When the rest pool interface is requested in the form of 'OAuth', the URL of the API can be configured as shown in Table 6 below.

http: //$userID$.instancehosting.com/instanceId/$instanceID$/start/
$ startingPoint $ / display / $ requestCount $

The key information is not requested in the form of a separate URL since the authentication process has been performed through 'OAuth'.

The terms used in Tables 3, 5 and 6 are, for example, as shown in Table 7 below.

URL Parameter Description Remarks userID User identifiers registered on the instance hosting gateway system instanceID Instance identifier running on the instance hosting gateway Key The key that the user issued For OAuth authentication, no key value is entered in the URL, and the address part is excluded. Start Start of request data Access to data values or logs in a single unit display Number of request data Supports 1 ~ 10,000

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 > 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.

330: Instance Hosting Gateway (Instance Hosting Gateway)
410: Network Adapter
420: Network Handler
430: Instance Manager (Instance Manager)
440: Instance Application Server

Claims (15)

A service providing method performed by a service providing system,
An IoT (Internet of Things) profile generating unit included in the service providing system provides a web site to a system of a developer of an IoT node, and uses information about the IoT node provided by the developer's system through the web site Creating an IoT profile; And
The IoT profile providing unit included in the service providing system stores the IoT profile in the IoT profile database and provides the IoT profile to the system of the developer
Lt; / RTI >
(1) the IoT profile stored in the IoT profile database; (2) the IoT profile provided via the URL associated with the developer and provided to the system of the developer; or (3) Wherein the IoT node is registered with the IoT profile using the IoT profile included in the IoT node after being provided to the system of the developer through the IoT profile provider. The method according to claim 1,
Wherein the information about the IoT node includes at least one of a URL associated with the developer's system and a URL of process information associated with the IoT profile. 3. The method of claim 2,
Wherein the information about the IoT node is information on a data stream produced by the IoT node, and further comprises at least one of a unit, a minimum value, and a maximum value. The method according to claim 1,
Wherein the step of generating the IoT profile comprises:
And processing the information about the IoT node according to a predetermined XML Schema Definition (XSD) to generate the IoT profile. The method according to claim 1,
Wherein the data stream of the IoT node is provided through an external API generated using the information of the IoT profile in the instance hosting gateway. The method according to claim 1,
Wherein the data log of the IoT node is provided in JSON (JavaScript Object Notation) or XML (eXtensible Markup Language) format. An IoT profile generating unit for providing a web site to a system of a developer of an Internet of Things (IOT) node and generating an IoT profile using information about the IoT node provided by the developer's system through the web site;
An IoT profile database for storing and managing the IoT profile; And
Providing the IoT profile to the system of the developer or providing the IoT profile to the instance hosting gateway to which the IoT node is connected,
Lt; / RTI >
(1) the IoT profile provided to the instance hosting gateway, (2) the IoT profile provided to the system of the developer and provided via a URL associated with the developer's system, or (3) the IoT profile Wherein the IoT node is registered in the IoT node using the IoT profile included in the IoT node after being provided to the system of the developer through the provision unit. 8. The method of claim 7,
Wherein the information about the IoT node includes at least one of a URL associated with the developer's system and a URL of process information associated with the IoT profile. 8. The method of claim 7,
Wherein the IoT profile generator comprises:
And the IoT profile is generated by processing the information about the IoT node according to a predetermined XML schema definition. (1) an IoT node requesting a connection, (2) a URL associated with a developer's system of the IoT node, or (3) an IoT profile database of a server generating an IoT profile of the IoT node. An IoT profile receiving unit for receiving a profile; And
An IoT node registration unit for registering an IoT node requesting the connection based on the IoT profile;
Lt; / RTI >
The IoT profile may be generated in the server using information on the IoT node provided by the system of the developer and a predetermined XML schema definition through a website provided to the system of the developer of the IoT node in the server It features an instance hosting gateway. 11. The method of claim 10,
An external API generation unit for generating an external API for providing the data stream of the IoT node to the outside using the IoT profile,
Further comprising an instance hosting gateway. 11. The method of claim 10,
A data log provider for providing the data log of the IoT node to the outside in the form of JSON or XML
Further comprising an instance hosting gateway. In a service providing method performed by an instance hosting gateway,
(2) a URL associated with a system of a developer of the IoT node; or (3) an IoT profile of a server that generates an IoT profile of the IoT node. Receiving, via a database, the IoT profile of the IoT node;
Registering an IoT node registration unit included in the instance hosting gateway, the IoT node requesting the connection based on the IoT profile; And
An external API generation unit included in the instance hosting gateway, an external API for providing the data stream of the IoT node to outside using the IoT profile,
Lt; / RTI >
Wherein the IoT profile is generated in the server using information on the IoT node provided by the developer's system through a website provided by the server to the developer's system of the IoT node . 14. The method of claim 13,
Wherein the IoT profile is generated in the server by further using a predetermined XML schema definition. 14. The method of claim 13,
Providing the data log of the IoT node to the outside in the form of JSON or XML
Further comprising the steps of:

Images