KR20180043041A - System and method for interfacing of devices using multi-protocol in internet of things - Google Patents

Abstract

In processing a connection to a device to support multi-protocol in Internet of things (IoT), a server receives a service scenario defined by a user for a plurality of devices using different protocols, distributes the inputted service scenarios to an IoT gateway, and transfers at least one of a data collection request and a device control request to the IoT gateway based on the inputted service scenario; and the IoT gateway stores the service scenario distributed from the server and processes the data collection request and the device control request received from the server based on the stored service scenarios. Therefore, the system may define an interworking service scenario with various devices.

Description

[0001] SYSTEM AND METHOD FOR INTERFACING OF DEVICES [0002] [0001]

The present invention relates to a system and a method for handling interworking with various IoT devices that support multiprotocol in the Internet of Things (IoT) and have a different interworking method and procedure.

In general, an object communication network is characterized in that a large number of devices and objects of different kinds are connected to a network. Therefore, the structure of the object communication network should support the scalability of the scale, the scalability of the function, the network modularization, and the interoperability of heterogeneous devices / objects. In addition, the object communication network is composed of heterogeneous objects having different characteristics and functions, rather than a single type of object, and most of the features are characterized in that a transaction occurs according to an event occurring in the object itself or around the object. Therefore, the object communication network should support flexibility and openness, and have a hierarchical network structure that can operate based on the event.

On the other hand, in the Internet system of things, various various communication standards such as Bluetooth, Zigbee, Z-wave, Alljoyn and Allseen are used for wireless communication with various IoT devices Are used. In addition, standards such as wired and wireless oneM2M based on IP network are also used.

In order to provide the object Internet service using the IoT devices, a service is provided using interworking standards with various devices. However, there are various interworking specifications for devices, and even devices using the same standard may have different interworking procedures depending on the difference between manufacturers producing each device. Therefore, there are many limitations in the Internet system of things, such as an IoT gateway (Gateway, GW), in which one device can flexibly link with various devices.

In this regard, PCT Laid-Open Patent Application No. WO 2014/010784 (entitled " Object Internet Service Providing Method ") discloses an IoT device using a D-platform, a P- platform, an M- A technology is disclosed in which a service is provided so that information, communication, interlocking, and control commands for an IoT device can be interlocked with a mobile device through platforms, respectively.

In the United States registered patent US 20110176528, a cellular mobile radio infrastructure technology platform is implemented using a virtual mobile server, a virtual register, and a call switch in an open wireless architecture (OWA) mobile cloud infrastructure and method, And a mobile cloud solution that provides services for interworking with IoT devices.

In such a conventional object Internet system, in order to add a new device to a service, a process for exchanging or upgrading a module for interworking with the device has been required.

Since the interworking method and the interworking procedure are different for each IoT device, it is not easy to provide a service for a new device. Accordingly, an interworking procedure is defined for each device (or function) newly connected to the object Internet network, And control request and the like, and a device interlocking processing technique capable of flexibly interlocking with a new device is required.

In an embodiment of the present invention, in order to provide a flexible interworking with IoT devices by supporting a multi-protocol, a service scenario to be interworked with various devices is defined, and a device in an IoT environment supporting interworking based on the definition An interlocking processing system and a method therefor.

It should be understood, however, that the technical scope of the present invention is not limited to the above-described technical problems, and other technical problems may exist.

According to one aspect of the present invention, there is provided a device interworking system for supporting a multi-protocol on the Internet, including a service scenario defined by a user for each of a plurality of devices using different protocols, A server distributing the input service scenarios to the object Internet gateway, and delivering at least one of a data collection request and a device control request to the object Internet gateway based on the input service scenario; And a matter Internet gateway for storing a service scenario of a protocol-specific device distributed from the server and processing a data collection request and a device control request received from the server based on the stored service scenarios.

According to any one of the above-mentioned objects of the present invention, the object Internet gateway provides a bearer interworking interface necessary for interworking with a plurality of devices using different protocols, Even if the service is added, the processing procedure of the desired service is defined in advance based on the information about the device. Therefore, when the service is requested based on the service, the service can be flexibly performed without changing the firmware or software It is possible to add an interlocking device.

FIG. 1 is a diagram illustrating a configuration of a device interworking system in an object Internet environment according to an embodiment of the present invention. Referring to FIG.
FIG. 2 is a table for describing a service scenario definition format for supporting a multi-protocol according to an embodiment of the present invention.
FIG. 3 is an example of a sample in which a service scenario according to an embodiment of the present invention is defined.
4 is a table for explaining an automatic processing scenario definition format according to an embodiment of the present invention.
5 is an example of a sample in which an automatic processing scenario is defined according to an embodiment of the present invention.
FIG. 6 is a data flow diagram illustrating a service scenario registration and distribution process according to an embodiment of the present invention.
7 is a data flow chart for explaining a process of performing an automatic processing scenario according to an embodiment of the present invention.
FIG. 8 is a data flow chart for explaining a device control process according to a device interlocking process according to an embodiment of the present invention.
FIG. 9 is a data flow chart for explaining a data collecting process by a device interlocking process according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings, which will be readily apparent to those skilled in the art. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly illustrate the present invention, parts not related to the description in the drawings are omitted, and like parts are denoted by similar reference numerals throughout the specification. In the following description with reference to the drawings, the same reference numerals will be used to designate the same names, and the reference numerals are merely for convenience of description, and the concepts, features, and functions Or the effect is not limited to interpretation.

Throughout the specification, when a part is referred to as being "connected" to another part, it includes not only "directly connected" but also "electrically connected" with another part in between . Also, when a component is referred to as "comprising ", it is understood that it may include other components as well as other components, But do not preclude the presence or addition of a feature, a number, a step, an operation, an element, a component, or a combination thereof.

Herein, the term " part " or " module " means a unit realized by hardware or software, a unit realized by using both, and a unit realized by using two or more hardware Or two or more units may be realized by one hardware.

Hereinafter, a device interworking system and method for supporting multiprotocol on the Internet in accordance with an embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a diagram illustrating a configuration of a device interworking system in an object Internet environment according to an embodiment of the present invention. Referring to FIG.

As shown in FIG. 1, the device interworking processing system 10 of the Internet according to an embodiment of the present invention includes a server 100 for defining and distributing service scenarios for various protocols applied to the object Internet, (Hereinafter referred to as " IoT GW ") 200 that performs interworking service processing for object Internet devices based on service scenarios defined for each protocol, and two or more object Internet networks And a plurality of object Internet devices 300 connected to the Internet.

1, the server 100 includes a device interworking service management unit 110, a service processing unit 120, and a stuff Internet data collecting unit 130. [ The object Internet gateway 200 includes a server interlocking unit 210, a service managing unit 220, a service processing unit 230, an automatic collecting unit 240, and a device interlocking unit 250.

1, each of the object Internet devices 300 according to the present invention includes a Bluetooth communication module, a Zigbee module, a Z-wave module, an Alljoyn module, and an Allseen communication module. The device used is shown as an example. However, the communication standard of the object Internet device 300 according to the embodiment of the present invention is not limited thereto.

In the meantime, a " service scenario " according to an embodiment of the present invention to be described below defines an arbitrary service (or " function "), Remote monitoring that collects the status of an object or environmental information, remote control that remotely controls facilities or devices, remote tracking in conjunction with location information of moving objects, and information exchange through a wireless network. Hereinafter, it will be described as an example that the device-linked processing system 10 according to an embodiment of the present invention is data collection and device control among various services. However, the kind of service on the object Internet according to an embodiment of the present invention is not limited.

The server 100 and the IOT GW 200 according to an embodiment of the present invention perform various functions (e.g., data collection and device control) based on service scenarios defined in cooperation with each other.

The server 100 creates or stores and manages service scenarios defined by the user and distributes the service scenarios to at least one gateway (i.e., IoT GW) 200 in the object Internet network. In addition, the server 100 transmits a request for service processing to the IOT GW 200 based on the defined service scenario.

Specifically, the device interworking service management unit 110 manages the version of the service scenario defined by the user, and distributes the service scenario to the IoT GW 200 according to the user request.

The service processing unit 120 transmits a corresponding request to the IoT GW 200 based on the service defined in each service scenario.

The object Internet data collecting unit 130 receives, stores, and manages data collected from the various object Internet devices 300 through the IOT GW 200.

Hereinafter, a method of generating or storing a service scenario by the device interworking service management unit 110 will be described in detail with reference to FIGS. 2 to 5. FIG.

According to an embodiment of the present invention, interworking scenarios with each device are predefined in order to provide flexible interworking for a plurality of object Internet devices using various protocols. These interlocking scenarios (ie, service scenarios) can be defined using JavaScript Object Notation (JSON) or XML format. In one embodiment of the present invention, the service scenario is defined using the JSON format. For reference, service scenarios may include service interworking scenarios and automatic processing scenarios.

FIG. 2 is a table for describing a service scenario definition format for supporting a multi-protocol according to an embodiment of the present invention.

In the service interworking scenario, an instruction and related parameters for performing a service based on items such as a device type, a device ID, and a service scenario ID are defined. These commands and related parameters (that is, a service interworking scenario definition format) 2 < / RTI >

In addition, the service interworking scenario generated by applying the scenario definition format as shown in FIG. 2 can be generated as shown in FIG.

3 is an example of a sample in which a service scenario according to an embodiment of the present invention is defined

The device interworking service management unit 110 stores and manages service scenarios generated as shown in FIG. 3 by applying the definition format of FIG. At this time, the device interworking service management unit 110 receives and saves the service scenarios created and defined by the user (for example, the object Internet network manager or the object Internet service developer) or creates a service scenario . ≪ / RTI >

3, an interworking type (i.e., " Dev_type ") can be defined as shown in FIG. 2, and at least one service interworking scenario corresponding to each of a plurality of protocols is created, stored and managed .

As described above, an automatic processing scenario is defined based on generated service interworking scenarios. In this automatic processing scenario, a processing cycle in which each service interworking scenario is processed is set, and the service scheduling according to an arbitrary service interworking scenario is processed through the IOT GW 200. [

The service automatic processing scenario includes a command for automatically performing a service based on items such as a task to be automatically performed (i.e., a service interlocking scenario), a task identifier, a task description, a repetition cycle, And related parameters are defined, and these instructions and associated parameters (i. E., The automatic processing scenario definition format) can be defined as shown in FIG.

4 is a table for explaining an automatic processing scenario definition format according to an embodiment of the present invention.

In addition, the automatic process scenario generated by applying the scenario definition format as shown in FIG. 4 can be generated as shown in FIG.

5 is an example of a sample in which an automatic processing scenario is defined according to an embodiment of the present invention.

The device interworking service management unit 110 stores and manages service scenarios generated as shown in FIG. 5 by applying the definition format of FIG. At this time, the device interworking service management unit 110 receives and stores the automatic processing scenarios defined by the user (for example, the object Internet network manager) or provides a creation tool for the user to create an automatic processing scenario It is also possible.

FIG. 5 illustrates an example of a scenario in which an automatic processing scenario according to an embodiment of the present invention allows data to be periodically and automatically collected from the object Internet device 300.

2 to 5 are distributed to the IOT GW 200 through the device interworking service management unit 110 of the server 100. [ A request corresponding to the service defined in each service interworking scenario is transmitted to the IOT GW 200 through the service processing unit 120 of the server 100. [ The data collected from each device 300 periodically through the IOT GW 200 as defined in each service automatic processing scenario, which is distributed from the server 100 and stored in the IoT GW 200, 100). Accordingly, the object Internet data collecting unit 130 of the server 100 receives and stores the data collected from the various object internet devices 300 through the IOT GW 200.

1, the IoT GW 200 receives, stores, and manages service scenarios distributed from the server 100, and interworks with the object Internet devices 300 according to various protocols based on the stored service scenarios, Services (i.e., functions).

At this time, the IO T GW 200 may collect data from the devices, or may transmit a device control request to the corresponding device according to a request transmitted from the server 100.

Specifically, the server interworking unit 210 receives a request for distribution of a service scenario, a control request, a data collection request, and the like from the server 100, and forwards each received request to a corresponding processing unit.

The service management unit 220 stores and manages various service scenarios distributed from the server 100.

The service processing unit 230 processes services according to a user's request through the server 100 (i.e., various services according to service scenarios, for example, data collection and device control commands).

The automatic collection unit 240 automatically collects data based on a service scenario (for example, an automatic processing scenario) when periodic data collection is required among the stored service scenarios through the service management unit 220, To the server (100).

The device interlocking unit 250 performs interworking with devices 300 that are real object Internet devices. At this time, the device interlocking unit 250 transmits various requests according to the service by the service processing unit 230 to the corresponding object Internet device 300 and processes it, or transmits the data request by the automatic collecting unit 240 It is periodically transmitted to the object Internet device 300 to process it. In addition, the device interlocking unit 250 may check and manage the connection state with the various devices 300.

Hereinafter, the device interlocking processing method through the device interworking system 10 of the Internet of objects according to an embodiment of the present invention will be described in more detail with reference to FIG. 6 to FIG.

A service scenario according to an exemplary embodiment of the present invention may be created by a user (i.e., a developer or the like) by performing an interworking test on a specific device. These service scenario files are uploaded to the server 100 and distributed to the respective IoT GW 200 through the server 100 through the distribution procedure. Accordingly, various service scenarios are defined according to protocols of various object Internet devices in advance, so that even if a new object Internet device is added to the object Internet network, an update operation for interworking with the object can be omitted, It is possible to reduce the system load due to management or executable file distribution.

FIG. 6 is a data flow diagram illustrating a service scenario registration and distribution process according to an embodiment of the present invention.

6, a user creates (i.e., creates) a service scenario (for example, a service interworking scenario) for interworking with a device compliant with an arbitrary protocol and generates a service scenario (S601, S602).

At this time, the device interworking service management unit 110 of the server 100 may provide a user interface including a service scenario creation tool to a user terminal (not shown), or a service scenario inputted from a user terminal It is possible to provide a user interface for uploading. In addition, the device interworking service management unit 110 provides predefined formats to a user terminal (not shown) to create the service interlocking scenario and the automatic processing scenario described above with reference to FIGS. 2 and 4, You can refer to it.

Next, the device interworking service management unit 100 of the server 100 stores the uploaded service scenario through a user terminal (not shown) (S603).

At this time, a plurality of service scenarios generated by the user are generated for various protocols applied to the object Internet and various functions (i.e., services) defined by the user, and the plurality of service scenarios are stored in the server 100.

Then, the server 100 distributes the generated service scenario to the IOT GW 200, and requests the service scenario to be applied (S604).

At this time, the server 100 may distribute the new service scenario to the IoT GW 200 every time a new service scenario is uploaded, or distribute a plurality of service scenarios to the IoT GW 200 periodically.

Next, the server interworking unit 210 of the IOT GW 200 delivers the service scenario received from the server 100 and the application request in the object Internet network to the service scenario corresponding to the service scenario (S605) .

Accordingly, the service management unit 220 applies the delivered service scenario to the object Internet network (S606).

For reference, when the service of the applied service scenario is an automatic processing scenario, the service management unit 220 may transmit the service scenario application request to the automatic collection unit 240.

As described above, the service scenario created by the user can be registered in the server 100, the registered service scenario can be distributed to the IOT GW 200, and the service corresponding thereto can be processed.

If the service scenario distributed to the IOT GW 200 is an automatic processing scenario file, the data collection procedure according to the processing cycle can be scheduled based on the device and period information defined in the scenario.

7 is a data flow chart for explaining a process of performing an automatic processing scenario according to an embodiment of the present invention.

The server interworking unit 210 of the IOT GW 200 transmits an application request of the service scenario received from the server 100 (i.e., the automatic processing scenario) to the automatic collection unit 240 (S701) 240 generates a data collection request according to the scheduler applying the service scenario (S702).

Accordingly, the automatic collection unit 240 transmits a data collection request to the object Internet device 300 according to the service scenario according to the schedule (S703).

At this time, the automatic collecting unit 240 actually communicates with the object Internet devices 300 and transmits the data collection request to the device interlocking unit 250, which is interlocked.

Next, the device interlocking unit 250 collects data from the target device 300 to collect data (S704), and transfers the collected data to the server interlocking unit 210 (S705).

Then, the server interworking unit 210 converts the collected data into a storable form and transmits the data to the server 100 (i.e., the object Internet data collecting unit 130) to store the data (S706).

Meanwhile, the IoT GW 200 can receive a service request according to each service scenario, while the service scenario supporting various protocols and defining a procedure for processing various services is stored in the IoT GW 200. That is, the service processing can be performed by the request of the user.

FIG. 8 is a data flow chart for explaining a device control process according to a device interlocking process according to an embodiment of the present invention.

The service processing unit 120 of the server 100 transmits a service request for the specific device 300 to the IoT GW 200 according to the service request of the user (S801).

At this time, the service request of the user may be a control request, and the control request includes information such as an ID of the corresponding device and an ID (i.e., scene id) for identifying a scenario in the device.

Next, the server interworking unit 210 of the IoT GW 200 receiving the control request from the server 100 transmits the control request to the service processing unit 230 (S802).

Then, the service processing unit 230 searches the corresponding service scenario based on the received control request (S803), and determines whether the control request is a normal request according to the search result (S804).

As a result of the determination, if the corresponding control request is an abnormal request (for example, the corresponding service scenario is not searched), the service processing unit 230 returns an error occurrence result of the control request to the server 100 (S805).

On the other hand, if it is determined that the control request is a normal request, the service processing unit 230 transmits a command according to the service scenario to the device interface unit 250 (S806).

The service processing unit 230 receives the result of processing the command according to the service scenario through the device interface unit 250 in step S807 and returns the processing result of the control request to the server 100 in step S808, .

At this time, the processing result for the control request may differ depending on the characteristics of the device 300 and the service performed, and the step of returning the result of the control request to the server 100 may be omitted.

FIG. 9 is a data flow chart for explaining a data collecting process by a device interlocking process according to an embodiment of the present invention.

The service processing unit 120 of the server 100 transmits a service request for the specific device 300 to the IoT GW 200 according to the service request of the user (S901).

At this time, the service request of the user may be a data collection request, and the data collection request includes information such as an ID of the corresponding device and an ID (i.e., scene id) for identifying the scenario in the corresponding device.

Next, the server interworking unit 210 of the IoT GW 200 receiving the data collection request from the server 100 transmits the control request to the service processing unit 230 (S902).

Then, the service processing unit 230 searches the corresponding service scenario based on the received data collection request (S903), and determines whether the corresponding data collection request is a normal request according to the search result (S904).

As a result of the determination, when the corresponding data collection request is an abnormal request (for example, the corresponding service scenario is not searched), the service processing unit 230 transmits an error occurrence result to the server 100, (S905).

On the other hand, if it is determined that the data collection request is a normal request, the service processing unit 230 transmits a command according to the service scenario to the device interface unit 250 (S906).

The service processing unit 230 receives the result of processing the command according to the service scenario through the device interlock unit 250 (that is, the data collection result) (S907) And transmits the collected data to the server 100 through the server interworking unit 210 (S908).

At this time, the server interworking unit 210 may convert the collected data into a format for storage and then transmit the converted data to the object Internet data collecting unit 130 or the service processing unit 120 of the server 100.

An apparatus and method for supporting multi-protocol support for multi-protocol applications on the Internet according to an embodiment of the present invention includes a computer program stored in a medium executed by a computer or a recording medium including instructions executable by a computer As shown in FIG. Computer readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. In addition, the computer-readable medium may include both computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Communication media typically includes any information delivery media, including computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, or other transport mechanism.

While the methods and systems of the present invention have been described in connection with specific embodiments, some or all of those elements or operations may be implemented using a computer system having a general purpose hardware architecture.

It will be understood by those skilled in the art that the foregoing description of the present invention is for illustrative purposes only and that those of ordinary skill in the art can readily understand that various changes and modifications may be made without departing from the spirit or essential characteristics of the present invention. will be. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive. For example, each component described as a single entity may be distributed and implemented, and components described as being distributed may also be implemented in a combined form.

The scope of the present invention is defined by the appended claims rather than the detailed description and all changes or modifications derived from the meaning and scope of the claims and their equivalents are to be construed as being included within the scope of the present invention do.

10: Device interworking system of things Internet
100: Server
200: Things Internet gateway
300: Things Internet Devices

Claims (1)

A device interworking system for supporting a multi-protocol in the Internet of objects,
A service scenario that is defined by a user for each of a plurality of devices using different protocols and distributes the input service scenario to a destination Internet gateway and transmits a request for data collection to a destination Internet gateway based on the service scenario, A server for delivering at least one of the requests; And
An object Internet gateway for storing a service scenario distributed from the server and processing a data collection request and a device control request received from a server based on stored service scenarios.

Images