KR20190008595A - Gateway server for relaying between iot device on non-tcp/ip network and iot server based on onem2m and method thereof - Google Patents

Abstract

Disclosed is a method for transmitting uplink data in a gateway server to relay an Internet of things (IoT) device on a network based on a non-transmission control protocol/internet protocol (non-TCP/IP) and an IoT server based on one machine to machine (M2M) standard; and an operating method thereof. The method for transmitting uplink data comprises: a step of receiving a non-TCP/IP packet including state information from an IoT device; a step of identifying a container name corresponding to the received state information; a step of converting the state information or the container name obtained in the received non-TCP/IP packet into a format depending on the one M2M standard; and a step of transmitting the converted state information or the converted container name to an IoT server. Therefore, the present invention can guarantee compatibility between a non-IP based network and the IoT server.

Description

TECHNICAL FIELD [0001] The present invention relates to a gateway server for relaying between an IoT device on a non-TCP / IP-based network and an IoT server based on oneM2M standard and a method of operating the gateway server. METHOD THEREOF}

The present invention relates to a gateway server for relaying between an IoT device on a non-TCP / IP-based network and an IoT server based on oneM2M standard, and more particularly to an IoT server equipped with a Mobius platform and a non- And a gateway server between the IoT devices, thereby ensuring compatibility.

Currently, the Internet of Things (IoT) technology has been attracting a great deal of attention worldwide and is developing very rapidly. As a result, the number of devices related to Internet of Things is expected to increase from 2 billion in 2011 to 12 billion by 2020, and it is predicted that a larger number of devices will be supplied including smart phones.

One of the major reasons why various successful business cases do not appear in the current IoT market is that it is costly to develop base platform such as product and server to make IoT service and base platform is dependent on service. The products developed by the present invention are incompatible with each other.

OneM2M (one machine to machine) is a platform for standardization of Internet of things in various standardization organizations. In oneM2M (one Machine to Machine), the platforms suggested by various standardization organizations are grouped into one, And suggests ways to utilize the platform.

Mobius, on the other hand, is a software platform for IOT servers implemented according to the oneM2M standard. Currently, new versions are being developed and released through the open alliance for IoT standard (OCEAN). Mobius is a server platform that stores and manages data collected from objects and allows them to be controlled via the REST APIs used by communication protocols such as HTTP and CoAP.

& Cube is a software platform for gateways and devices in the IoT system, which exchanges data via Mobius and its software and socket interfaces. In general, data transmission to Mobius is transmitted over HTTP over the socket interface, and status information and control signals are received through the MQTT.

In this case, the existing oneM2M-based Mobius server and the & Cube gateway system are configured only to interface with the devices connected through the TCP / IP based network, making it difficult to be compatible with the ZigBee-based network .

According to an aspect of the present invention, there is provided an apparatus and method for controlling an Internet of Things (IOT) device on a non-TCP / IP (Non-Transmission Control Protocol / Internet Protocol) (Internet of Things) server of an Internet service provider (ISP).

It is another object of the present invention to solve the above problems and to provide an apparatus and method for controlling an Internet of Things (IOT) device on a non-TCP / IP (Non-Transmission Control Protocol / Internet Protocol) Based IoT (Internet of Things) server between a plurality of servers connected to each other.

It is another object of the present invention to solve the above problems and to provide an IoT (Internet of Things) device on a non-TCP / IP (Non-Transmission Control Protocol / Internet Protocol) Based Internet-of-things (IoT) servers.

According to one aspect of the present invention, there is provided a method of controlling an Internet of Things (IoT) device on a non-TCP / IP (Non-Transmission Control Protocol / Internet Protocol) And provides an uplink data transmission method performed in a gateway server relaying between Internet of Things (IoT) servers.

Here, the uplink data transmission method includes: receiving a non-TCP / IP packet including status information from the IoT device; identifying a container name corresponding to the received status information; Converting the status information or the container name obtained in the IP packet into a format according to the oneM2M standard, and transmitting the converted status information or the converted container name to the IoT server.

Here, the non-TCP / IP based network may be a ZigBee network, and the non-TCP / IP packets may be a ZigBee packet.

Here, the normal link data transmission method extracts a non-TCP / IP-based network address of an IoT device that has transmitted a non-TCP / IP packet in a non-TCP / IP packet, And mapping the network address to the container name and storing the network address.

Here, the gateway server can transmit data to and from the IoT server by installing & Cube's software platform, and & Cube's software platform interworking with the Mobius platform installed on the IoT server.

According to another aspect of the present invention, there is provided an Internet-of-things (IoT) device on a non-TCP / IP (Non-Transmission Control Protocol / Internet Protocol) The present invention provides a downlink data transmission method performed by a gateway server relaying Internet to Things (IoT) servers.

Here, the downlink data transmission method includes receiving a control message from the IOT server, acquiring a container name and a content instance from the control message, Obtaining a non-TCP / IP-based network address of the IoT device to transmit the non-TCP / IP-based network address, generating non-TCP / IP packets including the non-TCP / IP-based network address and the control information obtained from the content instance, And transmitting the generated non-TCP / IP packet to the IoT device for transmitting the control information.

Here, the non-TCP / IP based network may be a ZigBee network, and the non-TCP / IP packets may be a ZigBee packet.

Here, the con- nector name may be mapped to a non-TCP / IP-based network address and stored in advance.

Here, the gateway server can transmit data to and from the IoT server by installing & Cube's software platform, and & Cube's software platform interworking with the Mobius platform installed on the IoT server.

Here, receiving the control message from the IoT server can receive the control message in a character string of oneM2M standard using & Cube's software platform.

According to another aspect of the present invention, there is provided an Internet-of-things (IoT) device on a non-TCP / IP (Non-Transmission Control Protocol / Internet Protocol) And provides a gateway server that relays the IoT servers to each other.

The gateway server may include at least one processor, a memory that stores instructions that direct the at least one processor to perform at least one step.

Wherein at least one of the steps comprises: receiving a non-TCP / IP packet including status information from the IoT device; identifying a container name corresponding to the received status information; Converting the state information or the container name obtained in the packet into a format according to the oneM2M standard, and transmitting the converted state information or the converted container name to the IoT server.

Here, the non-TCP / IP based network may be a ZigBee network, and the non-TCP / IP packets may be a ZigBee packet.

At least one processor extracts a non-TCP / IP-based network address of an IoT device that has transmitted a non-TCP / IP packet in a non-TCP / IP packet, May be mapped to the container name and stored.

Here, the gateway server can transmit data to and from the IoT server by installing & Cube's software platform, and & Cube's software platform interworking with the Mobius platform installed on the IoT server.

Here, the instructions include at least one processor receiving a control message from the IOT server, obtaining a content instance from a control message, the container name being a control information, Obtaining a non-TCP / IP-based network address of the IoT device to which the control information is to be transmitted, generating a non-TCP / IP packet including the non-TCP / IP-based network address and the control information obtained from the content instance And transmitting the generated non-TCP / IP packet to the IoT device for transmitting the control information.

Here, the instructions may instruct the at least one processor to receive the control message in the form of a string of oneM2M standard.

(Internet of Things) device on a non-TCP / IP (Non-Transmission Control Protocol / Internet Protocol) based network according to the present invention and an Internet of Things (IOT) based on oneM2M When a gateway server that relays servers, an uplink data transmission method, or a downlink data transmission method is used, data communication according to the oneM2M standard can be performed with a non-IP network.

Also, it can be operated in compatibility with the & Cube & Mobius platform according to the oneM2M standard, so that it can be easily introduced into existing systems.

1 is a conceptual diagram showing a structure of a oneM2M standard platform.
2 is a conceptual diagram illustrating a Mobius platform according to an embodiment of the present invention.
3 is a conceptual diagram of a ZigBee-based network interworking with an IoT server according to an embodiment of the present invention.
FIG. 4 is a block diagram of an overall system including a gateway server according to an exemplary embodiment of the present invention. Referring to FIG.
5 is a data flow diagram of a data transmission method performed in a gateway server that relays between a ZigBee network and an M2T standard based IoT server according to an embodiment of the present invention.
FIG. 6 is a conceptual diagram illustrating a data transmission process centered on software (ZIS) driven in a gateway server according to an embodiment of the present invention, according to the flow of time.
7 is a flowchart illustrating an uplink data transmission method performed in a gateway server according to an embodiment of the present invention.
8 is a flowchart illustrating a downlink data transmission method performed in a gateway server according to an embodiment of the present invention.
9 is a configuration diagram of a gateway server according to an embodiment of the present invention.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention. Like reference numerals are used for like elements in describing each drawing.

The terms first, second, A, B, etc. may be used to describe various elements, but the elements should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component. And / or < / RTI > includes any combination of a plurality of related listed items or any of a plurality of related listed items.

It is to be understood that when an element is referred to as being "connected" or "connected" to another element, it may be directly connected or connected to the other element, . On the other hand, when an element is referred to as being "directly connected" or "directly connected" to another element, it should be understood that there are no other elements in between.

The terminology used in this application is used only to describe a specific embodiment and is not intended to limit the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In the present application, the terms "comprises" or "having" and the like are used to specify that there is a feature, a number, a step, an operation, an element, a component or a combination thereof described in the specification, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries are to be interpreted as having a meaning consistent with the contextual meaning of the related art and are to be interpreted as either ideal or overly formal in the sense of the present application Do not.

Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a conceptual diagram showing a structure of a oneM2M standard platform.

Referring to FIG. 1, a structure according to oneM2M standard platform can be divided into a field domain and an infrastructure domain.

Here, an AE (Application Entity) may mean an application providing application logic and providing various services. In addition, AEs for managing CSEs can be included in the oneM2M standard platform.

In addition, the AE can be divided into an Application Service Node-AE (ASN-AE) and an Application Dedicated Node-AE (ADN-AE) according to whether the logical device includes a CSE (Common Service Entity). AE may correspond to various IoT devices including sensors, and ASN-AE including CSE may have a function of storing and managing data like a server.

The CSE may be a platform of service functions that must be commonly provided to various AEs of the Internet of Things (IoT). These common services can be provided through reference points and classified into Application Service Node-CSE, Middle Node-CSE and Infrastructure Node-CSE depending on the location of the CSE. . ASN-CSE can be installed with Lavender provided by & Cube.

For example, the CSE can provide 12 common functions: registration, search, security, group, data, subscription and notification, and device management.

The Network Security Entity (NSE) may be a platform for providing network services. For example, an NSE may provide services such as device management, device triggering, network interworking, and the like.

The MN (Middle Node) may mean a node acting as a gateway, and may provide a common service function including the CSE as in the ASN-AE.

On the other hand, oneM2M standard platform is composed of Mca by M2M (Machine to Machine) communication between AE and CSE for each node, Mcc by M2M communication between CSEs, Mcn by M2M communication between CSE and NSE, CSE of different service domains The Mcc reference point can be provided by the M2M communication.

Here, in the inter-node connection, the dotted line may denote a wireless connection, and all the nodes express data transmission through the gateway MN.

The infrastructure node (IN) of the infrastructure domain may be an IOT server, and may be composed of AE and CSE. Here, the CSE in IN may correspond to Mobius, and Mobius can perform the functions necessary to provide the Internet service of objects in conjunction with the user application. Mobius is described in more detail below.

2 is a conceptual diagram illustrating a Mobius platform according to an embodiment of the present invention.

The Mobius platform can refer to an operating system that allows a communication network to function smoothly, which is a physical basis for Internet connectivity between objects. The Mobius platform relays communication connections between various IoT devices and user applications, making it easy and convenient to establish communication links with each other. In particular, anyone in an open development environment can help you create and use IoT services.

Referring to FIG. 2, the Mobius platform is an intermediate medium for connecting the IoT device and the user application. When the IoT device transmits data (control result, status information, etc.) to the IoT server in which the Mobius platform is operated, Can store and deliver the data to the user application.

The user application can inquire the status or sensing information of the IoT device, or control the IoT device.

2, the Mobius platform is a communication protocol with IoT devices, and can support HTTP, CoAP (Constrained Application Protocol), and MQTT (Message Queue Telemetry Transport). As a communication protocol with a user application, It can support HTTP. For example, MQTT and CoAP can be supported by implementing MQTT broker and CoAP server on HTTP server and converting MQTT and CoAP protocol messages into HTTP messages.

In addition, the database (DB) of Mobius Server can support memory-based Redis DB for large-capacity data processing and Mongo DB, which is a NoSQL (non Structured Query Language) database for storing data.

In FIG. 2, the CoAP Proxy may be a software module supporting the CoAP protocol, and the MQTT server may be a software module supporting the MQTT protocol.

As such, the IoT server with the Mobius platform can communicate with the TCP / IP based network because it supports the HTTP, CoAP, and MQTT protocols as communication protocols, while it is difficult to directly communicate with the non-TCP / You can have a problem.

Hereinafter, a ZigBee-based network which is one of non-TCP / IP based networks will be described.

3 is a conceptual diagram of a ZigBee-based network interworking with an IoT server according to an embodiment of the present invention.

Referring to FIG. 3, a ZigBee network may include a coordinator (C), a router (R), and an end device (E).

Here, one coordinator may be required for each ZigBee-based network. The coordinator can initialize the network information and perform the same function as the PAN coordinator of the IEEE 802.15.4 standard. At this time, only the FFD (Full Function Device) may become the coordinator.

A router may have multiple routers as optional devices (or nodes) to use if necessary. ZigBee-based networks are basically low-power, short-range communications, so you can extend your network to multiple hops through routers. The router can join the network through the coordinator or another router already connected to the network. It can play a role similar to the coordinator of the IEEE 802.15.4 standard, and only FFD can be a router.

An end-point device is the lowest-level device that can be installed when needed, and may not participate in routing. A single ZigBee-based network may have several end devices. The end device can join the network via a coordinator or a router already connected to the network. The data of the end-device can be relayed through the router and forwarded to another terminator or coordinator.

A ZigBee-based network to which a method or apparatus according to the present invention may be applied may be connected to an IoT server or to other networks via a gateway server.

That is, devices on a ZigBee-based network according to an embodiment of the present invention can take a method of transmitting data via a gateway server as in a TCP / IP-based network.

Hereinafter, an operation method of the gateway server proposed in an embodiment of the present invention will be described.

FIG. 4 is a block diagram of an overall system including a gateway server according to an exemplary embodiment of the present invention. Referring to FIG.

Referring to FIG. 4, a data relay system between an IoT device (represented by a device) and an IoT server (IoT server) having a ZigBee communication module can be described centering on a gateway server shown in the middle.

First, a gateway server according to an embodiment of the present invention may include Raspberry pi as hardware, and Thyme of & cube may be used as software to be driven. Here, Raspberry Pie is an example of a single board computer developed by the Raspberry Pie Foundation, and various other server-based hardware can be used.

In addition, Zigbee internetworking software (ZIS) in the gateway server is shown separately from Thyme in order to specify a software module for implementing a method of operating the gateway server according to an embodiment of the present invention, And should be understood to be illustrative.

Herein, the ZIS according to an embodiment of the present invention can send and receive data using a TCP / IP socket interface with another software module Thyme, and a ZigBee module, which is a communication module supporting ZigBee communication, You can send and receive data through a serial port.

Specifically, the ZIS receives the status information or sensing information of the IoT device from the ZigBee module, and transmits the status message or the sensing information to the Thyme module. The ZIS module receives the control message transmitted from the Thyme module and transmits the address of the target IoT device to the ZigBee module And can perform a role of explicit transmission.

Here, the ZigBee module is a module embedded in the gateway server and a module embedded in the IoT device, respectively.

Here, the IoT device may be a sensor, for example, and may be equipped with a sensor module capable of sensing temperature, humidity, distance, etc. as a hardware, and a thig adaptation software (TAS) Can be installed.

TAS can refer to the software that continuously measures the sensor value in & Cube, the Internet device platform of objects, and transmits the measured value to the server platform, Mobius, to control the object.

Specifically, the TAS can read the required data using the sensor module API (sensor module API), generate a packet to be transmitted to the ZigBee module, process the received control packet, call the seonsor module API, Can be performed.

On the other hand, the IoT server can operate the Mobius platform described in FIG. 2, and Mobius can store and manage the collected data in a tree form.

For example, there may be a Thyme functioning as a gateway in correspondence with Thyme of the gateway server. As a subtree thereof, a container which is a standard resource of oneM2M may exist.

The container acts as a folder and can store a content instance over time. For example, Humidity, Pressure, Temperature, and LEDs can be managed as containers, respectively. The content instance may be stored in the form of a string as an actual sensed temperature value, a humidity value, etc., or as a value for control.

Since the user application can refer to the description of FIG. 2, a separate description will be omitted in order to avoid redundant explanations.

Hereinafter, the operation procedure of the ZIS, which is a software module mounted on the gateway server, will be described by dividing into an uplink data transmission and a downlink data transmission, respectively.

5 is a data flow diagram of a data transmission method performed in a gateway server that relays between a ZigBee network and an M2T standard based IoT server according to an embodiment of the present invention.

Referring to FIG. 5, the process of relaying the data transfer between the IOT server and the ZigBee network of the gateway server shown in FIG. 4 can be described.

The ZIS according to FIG. 4 includes a software module, a data formatting module, a socket interface module (Entity for formatting and socket interface), a ZigBee packet processing module (Entity for processing ZigBee packets), a ZigBee network management module network management).

Therefore, although the operation procedure is described below for each module, it is an exemplary one, and all or a part of them may be integrated.

First, uplink data transmission can be performed by the following process.

When the gateway server receives packets for state information from the ZigBee network, including the device status and the result of the sensor, through the ZigBee network, the ZigBee packet processing module of the gateway server transmits the packets ZigBee module address, device status or sensor result information.

Here, the ZigBee packet processing module can identify the container name on the mobius platform of the IoT server based on the acquired device status or the result information of the sensor. The container name and device status or sensor result information thus identified can be passed to the data formatting and socket interface module.

The data formatting and socket interface module converts the received container name, device status or sensor result information into the form defined in oneM2M standard and uses other TCP / IP-based socket interface to communicate with other software modules You can pass it to Thyme of Inn & Cube. Here, Thyme can transmit the received string to the IoT server.

Next, downlink data transmission can be performed by the following process.

When Thyme transfers the control message received from the IoT server to the data formatting and socket interface module in the form of a string of oneM2M standard, the data formatting and socket interface module sends the container name and control Information instance or a content instance that is a value.

The data formatting and socket interface module then sends the container name to the ZigBee network management module, and the control information and values can be sent to the ZigBee packet processing module.

The ZigBee network management module can identify the address of the ZigBee module on the ZigBee network using the container name received and forward the confirmed address to the ZigBee packet processing module.

The ZigBee packet processing module can generate a ZigBee packet including the received control information or value and the address of the ZigBee module, and transmit the generated ZigBee packet to the IoT device on the ZigBee network.

On the other hand, the uplink and downlink do not occur in order, so that the data formatting, the socket interface module, and the ZigBee packet processing module can be implemented in a multiplexing function in order to appropriately schedule the uplink and downlink.

FIG. 6 is a conceptual diagram illustrating a data transmission process centered on software (ZIS) driven in a gateway server according to an embodiment of the present invention, according to the flow of time.

Referring to FIG. 6, TAS is a software module that is driven by an IoT device located on a ZigBee network as described above with reference to FIG. 4, ZIS is a software module driven by a gateway server according to an exemplary embodiment of the present invention, Thyme, a software module of the gateway server, is displayed in correspondence with the oneM2M standard. CSE is a representation of the Mobius platform running on the IOT server in accordance with the oneM2M standard.

The data transmission to the CSE Mobius indicates uplink transmission, and the transmission in the opposite direction to the ZigBee network indicates a downlink.

The uplink can be started from the TAS installed in the IoT device of the ZigBee network. TAS can forward state information data to ZIS using ZigBee packet. ZIS can generate the oneM2M string through the forwarded packet and send the string via TCP / IP socket with & Cube's Thyme. Thyme can forward the received string to Mobius using the HTTP protocol.

The downlink may occur mainly for acknowledgment of updated data or control message transmission. In the MobiSM platform, as described above, the MQTT protocol can mainly be used for downlink data transmission. MQTT was developed for IoT communication with low power communication technology. The operation of the MQTT protocol can be performed by transmitting a notification message to the individuals who subscribe to a specific URI when the URI information is changed. The Mobius platform can generate a downlink transmission by a method in which a user who wants to monitor status information and a device for control subscribe to and receive notifications.

7 is a flowchart illustrating an uplink data transmission method performed in a gateway server according to an embodiment of the present invention.

Referring to FIG. 7, an Internet of Things (IOT) device on a non-TCP / IP based network and an Internet of Things (IOT) server based on oneM2M The uplink data transmission method performed by the gateway server that relays to each other includes receiving a non-TCP / IP packet including status information from the IoT device (SlOO), receiving a container name corresponding to the received status information, (S120) of converting the status information acquired from the received non-TCP / IP packet or the container name into a format according to oneM2M standard (S120), and converting the converted status information or the container name into IoT To the server (S130).

Here, the Non-TCP / IP based network may be a ZigBee network, and the Non-TCP / IP packet may be a ZigBee packet.

Here, the normal link data transmission method extracts a Non-TCP / IP-based network address of the IoT device that has transmitted the Non-TCP / IP packet from the Non-TCP / IP packet, Based network address to the container name and storing the mapping.

Here, the gateway server has a & Cube software platform installed therein, and the software platform of the & Cube can communicate with the IoT server by interworking with a mobius platform installed in the IoT server.

Here, & Cube's software platform can be Rosemary, Lavender as well as Thyme mentioned above. & Cube's software platform can support Java or Node.js based frameworks.

8 is a flowchart illustrating a downlink data transmission method performed in a gateway server according to an embodiment of the present invention.

Referring to FIG. 8, an Internet of Things (IOT) device on a non-TCP / IP based network and an Internet of Things (IOT) server based on oneM2M The downlink data transmission method performed by the gateway server that relays to each other includes receiving a control message from the IoT server (S200), receiving a container name and a content instance as control information from the control message Obtaining a non-TCP / IP-based network address of the IoT device to which the control information is to be transferred using the container name (S220), obtaining the non-TCP / IP-based network address Generating a Non-TCP / IP packet including control information obtained from the content instance (S230), and transmitting the generated Non-TCP / IP packet to the IoT device for transmitting the control information Step S240.

Here, the Non-TCP / IP based network may be a ZigBee network, and the Non-TCP / IP packet may be a ZigBee packet.

Here, the con- nector name may be mapped to the non-TCP / IP-based network address and stored in advance.

Here, the gateway server has a & Cube software platform installed therein, and the software platform of the & Cube can communicate with the IoT server by interworking with a mobius platform installed in the IoT server.

Here, the step S200 of receiving the control message from the IoT server may receive the control message in the form of a character string of the oneM2M standard using the software platform of & cube.

9 is a configuration diagram of a gateway server according to an embodiment of the present invention.

Referring to FIG. 9, a gateway for relaying an IoT (Internet of Things) device on a non-TCP / IP-based network and an IoT server based on oneM2M (one Machine to Machine) A gateway server 100 includes at least one processor 110 and a memory 120 for storing instructions that direct the at least one processor to perform at least one step can do.

Wherein the at least one step comprises: receiving a non-TCP / IP packet including status information from the IoT device; identifying a container name corresponding to the received status information; Converting the state information obtained in the IP packet or the container name into a format according to the oneM2M standard, and transmitting the converted state information or the converted container name to the IoT server.

Here, the Non-TCP / IP based network may be a ZigBee network, and the Non-TCP / IP packet may be a ZigBee packet.

Here, the instructions may be such that the at least one processor extracts a non-TCP / IP-based network address of an IoT device that has transmitted the Non-TCP / IP packet in the Non-TCP / IP packet, It may be instructed to map the TCP / IP-based network address to the container name and store the same.

Here, the gateway server has a & Cube software platform installed therein, and the software platform of the & Cube can communicate with the IoT server by interworking with a mobius platform installed in the IoT server.

Wherein the instructions cause the at least one processor to receive a control message from an IoT server, obtain a content instance from the control message, the container name and control information, Obtaining a non-TCP / IP-based network address of the IoT device to which the control information is to be transmitted using a name, a non-TCP / IP-based network address of the IoT device, Generating a TCP / IP packet, and transmitting the generated non-TCP / IP packet to the IoT device for transmitting the control information.

Here, the instructions may direct the at least one processor to receive the control message in the form of a string of oneM2M standard.

Examples of the gateway server include a portable computer such as a desktop computer, a laptop computer, a notebook, a smart phone, a tablet PC, a mobile phone, Such as a smart watch, a smart glass, an e-book reader, a portable multimedia player (PMP), a portable game machine, a navigation device, a digital camera, a digital multimedia broadcasting (DMB) A digital audio recorder, a digital audio player, a digital video recorder, a digital video player, a PDA (Personal Digital Assistant), and the like.

Here, the gateway server 100 may further include a communication module 130 capable of communicating with a non-TCP / IP-based network. An example of a communication module is a ZigBee module.

Here, the gateway server 100 may further include a storage 140 for storing non-TCP / IP-based network addresses and container names.

The methods according to the present invention can be implemented in the form of program instructions that can be executed through various computer means and recorded on 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 recorded on the computer readable medium may be those specially designed and constructed for the present invention or may be available to those skilled in the computer software.

Examples of computer-readable media include hardware devices that are specially configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions may include machine language code such as those produced by a compiler, as well as high-level language code that may be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate with at least one software module to perform the operations of the present invention, and vice versa.

Furthermore, the above-mentioned method or apparatus may be implemented by combining all or a part of the structure or function, or may be implemented separately.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit or scope of the present invention as defined by the following claims It can be understood that

Claims (15)

A gateway server that relays Internet of Things (IoT) devices on a non-TCP / IP-based network to IoT (Internet of Things) servers based on oneMac OneM2M In the uplink data transmission method performed in the uplink,
Receiving a non-TCP / IP packet including status information from the IoT device;
Identifying a container name corresponding to the received status information;
Converting the status information obtained in the received Non-TCP / IP packet or the container name into a format according to oneM2M standard; And
And transmitting the converted state information or the converted container name to the IoT server. In claim 1,
Wherein the non-TCP / IP-based network is a ZigBee network, and the Non-TCP / IP packet is a ZigBee packet. In claim 1,
Extracting a non-TCP / IP-based network address of the IoT device that has transmitted the Non-TCP / IP packet from the Non-TCP / IP packet, extracting the extracted non-TCP / IP- And mapping and storing the uplink data. In claim 1,
The gateway server comprises:
≪ / RTI > wherein the software platform of & Cube is installed, and the software platform of the & Cube interacts with the Mobius platform installed in the IoT server to transmit and receive data to and from the IoT server. A gateway server that relays Internet of Things (IoT) devices on a non-TCP / IP-based network to IoT (Internet of Things) servers based on oneMac OneM2M In the downlink data transmission method performed in the mobile station,
Receiving a control message from the IoT server;
Obtaining a container name and a content instance as control information from the control message;
Obtaining a non-TCP / IP-based network address of the IoT device through which the control information is to be transmitted using the container name;
Generating a non-TCP / IP packet including the non-TCP / IP-based network address and the control information obtained from the content instance; And
And transmitting the generated non-TCP / IP packet to the IoT device for transmitting the control information. In claim 5,
Wherein the non-TCP / IP-based network is a ZigBee network, and the Non-TCP / IP packet is a ZigBee packet. In claim 5,
Wherein the con- tainer name is mapped with the non-TCP / IP-based network address and stored in advance. In claim 5,
The gateway server comprises:
≪ / RTI > wherein a software platform of & Cube is installed and the software platform of & Cube interoperates with a mobius platform installed in an IOT server to transmit and receive data to and from the IoT server. In claim 8,
The receiving of the control message from the IoT server comprises:
And receiving the control message in the form of a string of oneM2M standard using the < RTI ID = 0.0 >& Cube ' s < / RTI > software platform. It is a gateway server that relays Internet-of-Things (IoT) devices on a non-TCP / IP-based network to IoT servers based on oneM2M (one Machine to Machine) ,
At least one processor;
And a memory for storing instructions that direct the at least one processor to perform at least one step,
Wherein the at least one step comprises:
Receiving a non-TCP / IP packet including status information from the IoT device;
Identifying a container name corresponding to the received status information;
Converting the status information obtained in the received Non-TCP / IP packet or the container name into a format according to oneM2M standard; And
And transmitting the converted state information or the converted container name to the IoT server. In claim 10,
Wherein the non-TCP / IP-based network is a ZigBee network, and the Non-TCP / IP packet is a ZigBee packet. In claim 11,
Wherein the instructions cause the at least one processor to:
Extracting a non-TCP / IP-based network address of the IoT device that has transmitted the Non-TCP / IP packet from the Non-TCP / IP packet, extracting the extracted non-TCP / IP- The gateway server instructs to map and store. In claim 10,
The gateway server comprises:
&Cube's software platform, and the < Cube > software platform interacts with the Mobius platform installed in the IoT server to send and receive data to and from the IoT server. In claim 10,
Wherein the instructions cause the at least one processor to:
Receiving a control message from the IoT server;
Obtaining a container name and a content instance as control information from the control message;
Obtaining a non-TCP / IP-based network address of the IoT device through which the control information is to be transmitted using the container name;
Generating a non-TCP / IP packet including the non-TCP / IP-based network address and the control information obtained from the content instance; And
And transmitting the generated non-TCP / IP packet to the IoT device that will transmit the control information. In claim 14,
Wherein the instructions cause the at least one processor to:
directs to receive the control message in the form of a string of oneM2M standard.

Images