WO2015093770A1

WO2015093770A1 - M2m network system, m2m gateway, and method for installing software module in m2m gateway so as to perform data communication with device

Info

Publication number: WO2015093770A1
Application number: PCT/KR2014/012000
Authority: WO
Inventors: 심재희; 오준호
Original assignee: 주식회사 엔텔스
Priority date: 2013-12-16
Filing date: 2014-12-08
Publication date: 2015-06-25
Also published as: KR20150069768A

Abstract

A method (500) for installing a software module in an M2M gateway(130) so as to perform data communication with a device (110), comprises: a step (510) in which a user accesses an M2M server (150) for providing a software development tool (SDK) on a web basis through a computer device; a step (520) in which the user manufactures a software module which is necessary for communication between the device (110) and the M2M gateway(130) based on an open type framework by using the software development tool; and a step (550) in which the M2M server (150) installs the software module in the M2M gateway (130).

Description

How to install software modules for data communication with devices in M2M network systems, M2M gateways, and M2M gateways

The technology described below relates to a network system for machine-to-machine communication and an M2M gateway to communicate with a device collecting specific data.

Recently, research and market for M2M communication are growing. In the M2M network, the M2M gateway communicates with a device (sensor) that collects specific data and transmits the collected data to a control unit of the M2M network. There are applications that provide various information to users by using the collected data.

In the field of M2M network, there are research fields for efficient network systems and service applications based on network systems.

A wide variety of devices can be used in an M2M network system. There are a variety of products, such as devices that measure actual temperatures, devices that measure humidity, devices that collect data from specific devices, and devices that measure human body information. Each device may be different from each other, and even the same manufacturer may have different OSs and / or communication protocols. Therefore, current M2M networks generally use devices and dedicated gateways manufactured by one manufacturer.

The technology described below is intended to provide an M2M network system and an integrated gateway capable of communicating with various devices as described above.

The M2M network system includes a device that collects data, an open framework-based architecture, a gateway that sends and receives data to and from the device using a software module, and an M2M server that receives data transmitted from the gateway and controls the gateway. .

If there is no software module for the device found in the gateway coverage, the gateway requests the software module from the M2M server and installs the software module transmitted from the M2M server. The M2M server installs software modules in the gateway.

The open framework is OSGi, and the software module may be a bundle that runs on OSGi.

The device and the gateway may be connected using at least one of NFC, Bluetooth, Wi-Fi, SUN, LAN network, mobile communication 3G network, mobile communication 4G network, local area communication network or mobile communication network.

The gateway may use at least one of the mId protocol of the ESTI 102.921 standard or the CoAP protocol of the IETF standard.

The M2M network system stores tool data for software development tools (SDKs) that produce software modules, receives development instructions from users connected via the Internet, creates software modules, and delivers the created software modules to the M2M server. The module development server may further include.

The M2M server may store tool data for a software development tool (SDK) for manufacturing a software module, and receive a development command from a user connected through the Internet to manufacture a software module.

The method of installing a software module for performing data communication with a device in an M2M gateway is performed by a user accessing an M2M server that provides a software development tool (SDK) based on a web through a computer device. M2M gateway based on an open framework to produce a software module required to communicate with the device, and M2M server includes installing a software module in the M2M gateway.

The manufacturing step includes a user selecting a communication protocol to be used between the device and the M2M gateway in a web-based software development tool, transmitting the source code for the selected communication protocol to the computer device, and generating the source code through the computer device. Producing a software module.

The producing step may further include the software development tool verifying the software module after producing the software module using the source code.

When the M2M server requests a software module for a device found in coverage, the M2M server may deliver a software module stored in the M2M server to the M2M gateway or remotely install the software module in the M2M gateway.

The M2M gateway includes a transmitter that transmits a scanning signal and a module request signal to an M2M server to determine whether an M2M device operates in coverage, a receiver that receives a response signal for a scanning signal from an M2M device, and analyzes an M2M device. A memory for storing a software module installed according to the module request signal and a controller for determining whether a software module for communicating with the device is installed and for transmitting a module request signal for requesting the software module to the M2M server if the software module is not present; The software module is a bundle that runs on OSGi, which is an open framework. The M2M server receives specific data collected by the M2M device through the M2M gateway, and the M2M server manages the software module.

In the technology described below, the M2M gateway communicates with the device using a software module, and if there is no corresponding software module, the M2M gateway may request a dedicated software module from the M2M server to access various devices provided by the developer through one gateway.

1 is an example of a block diagram showing a configuration of an M2M network system.

2 is another example of a block diagram illustrating a configuration of an M2M network system.

3 is an example illustrating a hierarchical structure of a gateway for communicating with a device.

4 is an example of a block diagram showing the configuration of a gateway.

5 is an example of a flowchart for a method of installing a software module for performing data communication with a device in an M2M gateway.

6 is a flowchart illustrating a process of providing a software module to a gateway.

As the present invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

The terms first, second, A, B, etc. may be used to describe various components, but the components are not limited by the terms, but merely for distinguishing one component from other components. Only used as For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. The term and / or includes a combination of a plurality of related items or any item of a plurality of related items.

As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It is to be understood that the present invention means that there is a part or a combination thereof, and does not exclude the presence or addition possibility of one or more other features or numbers, step operation components, parts or combinations thereof.

Prior to the detailed description of the drawings, it is to be clear that the division of the components in the present specification is only divided by the main function of each component. That is, two or more components to be described below may be combined into one component, or one component may be provided divided into two or more for each function. Each of the components to be described below may additionally perform some or all of the functions of other components in addition to the main functions of the components, and some of the main functions of each of the components are different. Of course, it may be carried out exclusively by. Therefore, the existence of each component described through this specification should be interpreted functionally, and for this reason, the configuration of the components according to the M2M network system 100, M2M gateway 130 of the present invention is an object of the present invention It should be clear that the drawings may be different from the corresponding drawings to the extent that can be achieved.

In addition, in carrying out the method or operation method, each process constituting the method may occur differently from the stated order unless the context clearly indicates a specific order. That is, each process may occur in the same order as specified, may be performed substantially simultaneously, or may be performed in the reverse order.

First, the terms used in the following description will be described. The technology described below relates to an M2M network system, its configuration and operation. Accordingly, devices, gateways, servers, and the like, which are referred to below, are all M2M network system elements. In some cases, in order to clarify this, it will be referred to as "M2M gateway" and the like, but the same configuration is also referred to as "gateway" in which M2M is omitted.

The network refers to a physical environment or a device capable of transmitting and receiving data between a specific device and a device by wire or wirelessly. In the technology described below, a device connecting various components of the M2M network system may use various technologies or communication methods. In other words, the technology described below does not limit the scope of the technology described below in terms of the type of network connecting the configuration.

A device refers to an apparatus that collects various pieces of information data, such as sensor nodes in a sensor network. For example, it refers to a device for collecting specific data such as a sensor for measuring temperature, a sensor for measuring humidity, a CCTV for capturing an image, and the like. Furthermore, a device for transmitting a signal for controlling a specific mechanism, such as a device for controlling indoor heating and the like, is also included.

In addition, in the following specification, technologies or configurations that are not specifically described in addition to the core configurations of the technologies described below refer to technologies or configurations that are well known in the conventional M2M network system, or refer to published M2M related standard documents. Knowledgeable ones will be fully understood.

Hereinafter, a method 500 for installing a software module for performing data communication with the device 110 in the M2M network system 100, the M2M gateway 130, and the M2M gateway will be described in detail with reference to the accompanying drawings.

1 is an example of a block diagram showing a configuration of an M2M network system 100. The M2M network system 100 has a device 110 for collecting data, an architecture based on an open framework, and is transmitted from the device 110 and the device 110 to exchange data with the device 110 using a software module. M2M server 150 that receives the data, and controls the device 110.

1, two devices 110 are shown, denoted by D1 and D2. The device 110 is connected to the device 110 through first networks Network1 and 120. The first networks Network1 and 120 may be networks such as Zigbee, NFC, Bluetooth, Wi-Fi, SUN, LAN networks, mobile communication 3G networks, mobile communication 4G networks, and the like. As a result, various short-range communication networks and mobile communication networks can be used. In general, since the device 110 uses a limited power (energy), it uses a lot of near field communication.

In order for the device 110 to communicate with the device 110, communication protocols using each other should be common. Therefore, in general, the device 110 has a built-in protocol according to the communication protocol used in the specific device (110). 1 includes a "D1 communication module" for communicating with D1 and a "D2 communication module" for communicating with D2. The device 110 may communicate with the device 110 through such a communication module.

As described above, the type of device 110 that can be used for M2M communication is very diverse and may use different communication protocols and OSs. That is, in order to communicate with the device 110 using different protocols, the device 110 must include all protocols. However, in reality, it is difficult for the device 110 to have all protocols, and it is difficult for one device 110 to collectively manage and control the device 110 using various OSs.

Therefore, the device 110 basically has an architecture based on an open framework that can be easily accessed by a developer, and intends to implement a protocol for communicating with the device 110 through a specific software module used in the open framework. Various open frameworks may be used, but once an open framework is OSGi, it is assumed that a software module is a bundle running on OSGi.

The Open Service Gateway initiative (OSGi) is a framework for creating a dynamic platform based on the Java language that allows networked devices to share a variety of services. It works in module units called bundles. OSGi is a framework that allows you to install, run, update, stop, and remove one or more bundled applications on the framework.

That is, when a developer for a specific device 110 provides a device 110 with a software module (bundle) that can be used based on OSGi, communication between the device 110 developed by the developer and the device 110 is possible. .

To this end, the device 110 requests a software module from the M2M server 150 when there is no software module for the device 110 found in the device 110 coverage. The M2M server 150 is configured to receive data collected by the device 110, manage the device 110 and the gateway 130, and provide a specific service to other users based on the collected information.

The M2M server 150 is connected to the gateway 130 and the second networks Network2 and 140. Various networks may be used for the second network Network2 140, like the first network 120. The gateway 130 and the M2M server 150 are generally located remotely from each other. Therefore, although a wired network such as a telephone line network or an optical communication may be used, the second network (Network2, 140) generally uses a mobile communication network. In the latter case, the M2M server 150 is connected to the mobile communication core network. For example, it may be connected to a configuration such as Packet Data Serving Node (PDSN) of 3G network or Serving Gateway (SGW) of 4G network. In FIG. 1 and FIG. 2, the second network (Network2, 140) and the M2M server 150 is indicated by a dotted box, which means that the M2M server 150 is connected to the second network (Network2, 140).

2 is another example of a block diagram illustrating a configuration of the M2M network system 100. In FIG. 2, it is assumed that the devices 110, D1, D2, and D3 use different communication protocols. In FIG. 2, the D1 communication module and the D2 communication module are already installed in the gateway 130, but the D3 communication module is not currently installed. Accordingly, the gateway 130 may not receive data collected from the device 110 D3.

The gateway 130 determines that the communication module (software module) for the device 110 D3 is not installed, and then requests the M2M server 150 for the communication module for the D3. Thereafter, the M2M server 150 may transfer the stored D3 communication module to the gateway 130 so that the gateway 130 may install or remotely install the D3 communication module in the gateway 130.

That is, when the gateway 130 determines that there is no protocol (driver) for communication, the gateway 130 requests and installs the corresponding protocol and then communicates with the device 110. From the standpoint of the device 110, it is called a plug-and-play method. In the description of the present invention, various names such as a software module, a communication module, a protocol, and a driver are described, but in the end, the same object will be described. In OSGi-based architectures, software modules are provided in so-called bundles.

Meanwhile, the M2M server 150 may not store or manage all communication modules in advance. The developer who develops the specific device 110 must provide the M2M server 150 with the communication protocol (communication module) used in the device 110 in advance. In FIG. 2, a path through which a developer accesses the M2M server 150 via the Internet through the developer computer 50 is illustrated. A method of providing a software module by a developer will be described later.

3 is an example illustrating a hierarchical structure of the gateway 130 in communication with the device 110. The gateway 130 shown in FIG. 3 has an OSGi based architecture. The device 110 and the gateway 130 have been shown to be connected in various ways, such as Bluetooth, SUN, NFC, Wi-Fi, 3G, 4G. Since the M2M server 150 receives and collects data collected by the device 110, the M2M server 150 is indicated as a collector.

Referring to the gateway 130 illustrated in FIG. 3, the layers essential to the OSGi architecture are shown. Detailed description of the configuration generally used in OSGi will be omitted. Gateway Bundle is a software module. Bundle includes the contents such as the protocol that can communicate with the specific device (110). In addition, standard interfaces (SUN, Zigbee, NFC, Bluetooth, Wi-Fi, HTTP, TCP, etc.) for the first network and the protocol for the second network are illustrated in the Common Bundle layer. Protocols such as the mId protocol of the ESTI 102.921 standard or the CoAP protocol of the IETF standard may be used between the gateway 130 and the M2M server 150. Using standard protocols will allow M2M service providers to use M2M network systems more easily.

4 is an example of a block diagram showing the configuration of the gateway 130. 4 also shows an operational flow for installing a software module (communication module) in the gateway 130 between the device 110, the gateway 130, and the M2M server 150.

The gateway 130 transmits a scanning signal and a transmission unit 131 for transmitting a module request signal to the M2M server 150 and a response signal for the scanning signal from the M2M device to determine whether the M2M device 110 operates in the coverage. Receiving unit 132 that receives the, and analyzes the response signal to determine whether the software module for communicating with the M2M device is installed, and if there is no software module to transmit a module request signal for requesting the software module to the M2M server 150 A control unit 133 for controlling and a memory unit 134 for storing a software module installed according to the module request signal.

Currently, the memory unit 134 is installed with a D1 communication module, a D2 communication module, a D4 communication module, a D5 communication module, and a D6 communication module. It is assumed that each device 110 of D1 to D6 uses a different protocol. Accordingly, the gateway 130 may receive data from the devices 110, D1 and D2, but may not receive data from the device D3.

The method of initiating communication between the device 110 and the gateway 130 may be varied. For example, the device 110 transmits a signal for scanning whether there is a specific gateway 130 present in the periphery, and the gateway 130 transmits a response message to the device 110 to transmit the response message to the device 110 and the gateway ( 130) can be established between channels. Or a channel between the device 110 and the gateway 130 in such a manner that the gateway 130 transmits a signal for scanning whether the device 110 exists around the device and the device 110 transmits a response signal thereto. This may be true. Since device 110 generally uses limited power, it is assumed and described in the latter manner. However, the technology described herein does not limit the method of establishing a channel for exchanging data between the device 110 and the gateway 130.

The transmitter 131 of the gateway 130 transmits a scanning signal for searching for a device 110 present in the periphery, and the device D3 transmits a response signal to the gateway 130 to the gateway 130. Therefore, even if the device 110 does not currently have a communication module in the gateway 130, it is assumed that a scanning signal and a response signal thereof are possible by a certain communication protocol. Since the scanning signal and the response signal are transmitted and received according to a standard interface used in the first network 120, the scanning signal and the response signal may exchange signals according to the corresponding standard. The response signal contains an identifier for device D3 or information about the protocol used.

The control unit 133 analyzes the response signal transmitted from the receiving unit 132 of the gateway 130 to determine whether there is a communication module corresponding to the corresponding protocol in the current memory unit 134. If there is a corresponding communication module, communication may be possible between the gateway 130 and the device 110 immediately, but there is no communication module for the device D3.

The controller 133 transmits a module request signal for the D3 communication module to the M2M server 150 through the transmitter 131. The M2M server 150 receives and analyzes a module request signal and transmits a D3 communication module, which is a corresponding communication module, to the gateway 130 or installs the corresponding communication module in the gateway 130.

Further, although not shown in the figure, the M2M network system 100 may further include a separate module development server 160 in addition to the M2M server 150. In this case, the software communication module provided by the developer is stored in the module development server 160, and the M2M server 150 manages the communication module stored in the module development server 160, and uses the communication module to the gateway 130. Install it.

Now, the process of providing a communication module to the M2M server 150 or the module development server 160 by the developer in advance and the process of installing the communication module to the gateway 130 by the M2M server 150 will be described. 5 is an example of a flowchart for a method 500 of installing a software module for performing data communication with the device 110 in the M2M gateway 130.

The method 500 for installing a software module for performing data communication with the device 110 in the M2M gateway 130 includes an M2M server 150 in which a user provides a software development tool (SDK) based on a web through a computer device. Approaching (510), a user using a software development tool, the M2M gateway (130) based on an open framework to create a software module necessary for communicating with the device (110) and the M2M server (150) Install 550 the software module in the M2M gateway 130.

The manufacturing step 520 is specifically a step in which a user selects a communication protocol to be used between the device 110 and the M2M gateway 130 in a web-based software development tool (521), the source code for the communication protocol selected in the computer device. The step 522 may be transmitted, and the user may create a software module using source code through a computer device (523). Further, the manufacturing step 520 may further include a step 524 of verifying the software module by the software development tool after the step of manufacturing the software module using the source code.

As shown in FIG. 2, a developer connects to an M2M server 150 that provides a web-based SDK through the developer computer 50 used by him, and then develops a device according to the interface provided by the SDK. Input the communication protocol, etc. of 110, the source code is automatically created through the SDK. Alternatively, the developer can write or modify the source code directly through the SDK interface.

In general, you can use source code that is accessible from a public program such as Eclipse. The developer may open the source code downloaded to the developer computer 50 and modify the source code to match the device 110 developed by the developer. After that, the developer compiles the completed code and transmits it to the M2M server 150. Compiled files can also be verified using the SDK. Furthermore, without downloading and using the source code from the M2M server 150, the developer may input a predetermined command in the developer computer 50 and the source code may be remotely performed in the M2M server 150. As a result, the source code prepared by the developer through the M2M server 150 may be actually provided in the M2M server 150 in various ways.

The software module does not necessarily have to be produced by the web-based SDK. However, in order to easily access the developer M2M network system, the M2M server 150 providing the SDK should be accessible through the Internet. Therefore, the web-based SDK is described as an embodiment. In addition, the M2M server 150 does not have to provide a web-based SDK, but a separate SDK providing server may be sufficient.

Meanwhile, the software module (communication module) provided by the developer is stored in the M2M server 150 (530), and then the M2M gateway 130 requests the M2M server 150 for the software module for the specific device 110 ( In case 540, the M2M server 150 installs a software module in the M2M gateway 130 (550).

When the M2M server 150 requests a software module for the device 110 that is retrieved from the coverage, the M2M server 150 delivers the software module stored in the M2M server 150 to the M2M gateway 130 or remotely executes the software module. The module is installed in the M2M gateway 130.

6 is a flowchart of a process in which a software module is provided to the gateway 130. 6 summarizes the above-described process. First, the device scanning signal for scanning the device 110 is transmitted from the M2M gateway 130 (311), and the device 110 transmits a scanning response signal 312 for the scanning signal to the M2M gateway 130. 6 assumes that there is no software module for the device 110 that has currently sent the scanning response signal to the M2M gateway 130.

The M2M gateway 130 transmits a module request signal requesting the installation of the corresponding software module to the M2M server 150 (321), and the M2M server 150 transmits the requested software module to the gateway 130 or remotely. The software module is installed in the gateway 130 (322). Meanwhile, when using a separate module development server 160 for storing software development modules, the M2M server 150 searches for a module to inquire whether the module development server 160 has a software module requested from the M2M gateway 130. Send a request (331). In response to the module search request, the module development server 160 transmits the corresponding software module to the M2M gateway 130 (332).

Although not shown, if there is no corresponding software module, the module development server 160 will transmit a message informing the M2M server 150 of this. Although not shown in the figure, a service provided through the M2M network system is provided to a third person or a company. The individual receiving the service is provided with a service through a terminal such as a PC or a smartphone, and if there is no appropriate software module in the module development server 160, the individual who wants to receive the service is informed, and also the developer (service provider). ) Should also be notified.

After the software module is installed in the M2M gateway 130, the user requests a service, or when the M2M server 150 requests, the M2M gateway 130 requests the device 110 to transmit the collected data. In operation 341, the device 110 transmits the collected data to the M2M gateway 130 (342). Data received by the M2M gateway 130 is transmitted to the M2M server 150 (343). Thereafter, the M2M server 150 may directly process or manage the received data to provide a service to a user, or may transmit data to a separate server that provides a service to a user.

The embodiments and drawings attached to this specification are merely to clearly show some of the technical ideas included in the present invention, and those skilled in the art can easily infer within the scope of the technical ideas included in the specification and drawings of the present invention. Modifications that can be made and specific embodiments will be apparent that all fall within the scope of the present invention.

[Description of the code]

50: Developer Computer 100: M2M Network System

110: device 120: first network

130: gateway 131: transmitter

132: receiving unit 133: control unit

134: memory section 140: second network

150: M2M Server 160: Module Development Server

Claims

In an M2M network system,

A device for collecting data;

A gateway having an architecture based on an open framework and exchanging data with the device using a software module; And

M2M network system for receiving the data delivered by the gateway, and M2M server for controlling the gateway.
The method of claim 1,

The gateway is

M2M network system for installing the software module requesting the software module in the M2M server, if there is no software module for the device that is found in the gateway coverage.
The method of claim 1,

The open framework is OSGi, and the software module is a bundle running on the OSGi.
The method of claim 1,

The M2M server system for installing the software module in the gateway.
The method of claim 1,

The device and the gateway is connected to the M2M network system using at least one of the Zigbee, NFC, Bluetooth, WiFi, SUN, LAN network, mobile communication 3G network, mobile communication 4G network, local area communication network or mobile communication network.
The method of claim 1,

The gateway uses at least one of the mId protocol of the ESTI 102.921 standard or the CoAP protocol of the IETF standard.
The method of claim 1,

Stores tool data for a software development tool (SDK) for manufacturing the software module, receives a development command from a user connected through the Internet, produces the software module, and delivers the produced software module to the M2M server. M2M network system further comprising a module development server.
The method of claim 1,

The M2M server

M2M network system for storing the tool data for the software development tool (SDK) for producing the software module, and receives the development command from a user connected through the Internet to produce the software module.
A user accessing an M2M server providing a software development tool (SDK) on a web basis through a computer device;

The user using the software development tool to create a software module for an M2M gateway based on an open framework to communicate with a device; And

And installing, by the M2M server, the software module in the M2M gateway.
The method of claim 9,

The manufacturing step

Selecting, by the user, a communication protocol to be used between the device and the M2M gateway in the web-based software development tool;

Transmitting source code for the selected communication protocol to the computer device;

And installing, by the user, the software module using the source code through the computer device, to install a software module for performing data communication with a device in an M2M gateway.
The method of claim 10,

And verifying the software module by the software development tool after producing the software module using the source code.
The method of claim 9,

The M2M server

When the M2M gateway requests a software module for the device found in coverage, the M2M gateway delivers the software module stored in the M2M server to the M2M gateway, or remotely installs the software module in the M2M gateway. A method of installing a software module for performing data communication with a device.
The method of claim 9,

The open framework is an OSGi, and the software module is a method for installing a software module for performing data communication with a device in a M2M gateway that is a bundle running in the OSGi.
In the M2M gateway,

A transmitter for transmitting a module request signal to a M2M server and a scanning signal to determine whether an M2M device operating in coverage exists;

A receiver configured to receive a response signal to the scanning signal from the M2M device;

A controller configured to analyze the response signal to determine whether a software module for communicating with the M2M device is installed, and to transmit a module request signal for requesting the software module to the M2M server if there is no software module; And

Including a memory unit for storing a software module installed according to the module request signal,

The software module is a bundle running in OSGi, which is an open framework, and the M2M server receives specific data collected by the M2M device through an M2M gateway, and the M2M server manages the software module. .