KR20160119370A - System for interoperation network of IoT and network of Zigbee based DDS and Method thereof - Google Patents

System for interoperation network of IoT and network of Zigbee based DDS and Method thereof Download PDF

Info

Publication number
KR20160119370A
KR20160119370A KR1020150047470A KR20150047470A KR20160119370A KR 20160119370 A KR20160119370 A KR 20160119370A KR 1020150047470 A KR1020150047470 A KR 1020150047470A KR 20150047470 A KR20150047470 A KR 20150047470A KR 20160119370 A KR20160119370 A KR 20160119370A
Authority
KR
South Korea
Prior art keywords
zigbee
service
data
network
topic
Prior art date
Application number
KR1020150047470A
Other languages
Korean (ko)
Other versions
KR101673755B1 (en
Inventor
이규철
임형준
백문기
김인아
Original Assignee
충남대학교산학협력단
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 충남대학교산학협력단 filed Critical 충남대학교산학협력단
Priority to KR1020150047470A priority Critical patent/KR101673755B1/en
Publication of KR20160119370A publication Critical patent/KR20160119370A/en
Application granted granted Critical
Publication of KR101673755B1 publication Critical patent/KR101673755B1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0226—Mapping or translating multiple network management protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The present invention relates to a system and method for interworking with a DDS-based Internet and a ZigBee network, and in which different applications can exchange information through topic connection A Data Distributed Service (DDS) system, which provides an interface to allow the user to interact with the system; Events, or services from ZigBee nodes in a ZigBee network and converts them into data topics, event topics, or service topics and publishes them to the DDS system, subscribes data topics, event topics, or service topics from the DDS system, And a ZigBee adapter that allocates virtual ZigBee nodes to provide to the network and provides interoperation between different networks of the object Internet environment. Accordingly, the present invention provides a ZigBee-based ZigBee packet data / event / service in an Internet environment using a ZigBee adapter, a data / event / service in a ZigBee network as a DDS-based topic, Based on DDS, it provides interoperability between ZigBee network and other networks in the Internet environment, thereby enabling bidirectional communication and data / event / service interworking between different networks. Through the quality of service (QoS) supported by DDS Real-time and reliable interoperability can be ensured.

Figure P1020150047470

Description

[0001] The present invention relates to a system and an interworking system of a DDS-based Internet network and a Zigbee network,

The present invention relates to a system and method for interworking between a DDS-based Internet and a ZigBee network, and more particularly, to a system and method for interworking between a ZigBee network and another network of the Internet, The present invention relates to a system and method for interworking with a DDS-based object Internet network and a ZigBee network.

Recently, the development of sensing actuators, wired and wireless communication technologies and the Internet is a trend that includes human versus object and inter-object communication in person-to-person communication. The Internet of Things (IoT) defined by the International Telecommunication Union (ITU) means that all objects exchange information through the network anytime and anywhere, thereby providing advanced services.

A typical object Internet architecture is divided into sensing, network, and application system domains. In particular, the sensing domain includes an IEEE 802.15 wireless personal area network (WPAN) such as IEEE 802.11 wireless LAN and Bluetooth, and ZigBee UWB (Ultra Wide Band) such as WiFi in the presence of physical objects .

The Internet consists of a variety of networks. The Internet must support technologies for identifying, sensing, and communicating objects. A useful technique is the Wireless Sensor Network (WSN) based on the IEEE 802.15.4 standard. The WSN is an ad hoc network composed of a wide range of wireless sensor nodes in a physical space. Each wireless sensor node consists of MCU, sensor, wireless communication module, and power supply. A service for remotely controlling the device through the wireless communication module can be handled. The information and services in the WSN are delivered to the collection node and delivered through the network domain to be used for various applications such as local monitoring and remote device control.

The WSN constituting the Internet of objects constructs topologies such as star, tree, and mesh according to physical constraints and operational purposes. Therefore, 1: N, N: 1, N: N communication is possible as well as 1: 1 request-response communication such as service. Because existing TCP / IP-based Internet and mobile communications communicate with each other with clear end-points, it is necessary to have a server that manages endpoints to manage P2P-based communications, do.

Objects Things in the Internet environment are exchanged through the network to provide various services. The WSN, which constitutes the Internet of things, is typically used for ZigBee network, which consists of low-cost and low-power devices, for local monitoring and remote device control.

The WSN uses the IEEE 802.15.4 standard as a basic subordinate communication layer, but uses another higher protocol depending on the purpose of network operation. The ZigBee standard is used as the WSN's upper protocol stack consisting of low-cost and low-power wireless sensor nodes. A ZigBee network conforming to the ZigBee standard forms a network topology in the form of a star, a tree mesh, etc. according to physical environment and operation purpose.

The wireless sensor nodes in the ZigBee network act as a ZigBee coordinator that creates and maintains a network and collects information, a ZigBee router that supports an ad hoc network configuration, and a ZigBee end device that generates and consumes information and controls other devices. It is classified.

In particular, ZigBee Coordinator plays a central role in creating and maintaining a ZigBee network. It grasps the status of all wireless sensor nodes in the ZigBee network and collects all data, events and services in the ZigBee network.

Objects Things in the Internet environment are themselves connected to the Internet to communicate with other objects, but they are also dependent on application systems that use WSNs. Therefore, if the application system does not support communication with the external network, the objects can not exchange information with other objects in the Internet environment.

Non-patent papers 1 and 2 describe a connection between a WSN and an external network, and describe a WSN gateway and an IoT gateway that link information in a WSN with a wide area network such as a WLAN and a cellular network.

The WSN gateway stores the information collected by the WSN proprietary protocol in the registry and interworks with the external network communicating this information by exchanging XML messages. Similar to WSN gateways, the IoT gateways in the Object Internet Application Architecture use WSN information composed of various purposes such as wirelessHART, MiWi, Z-Wave, Rubee, and ZigBee as TCP / IP-based Internet protocols Works with external application system. That is, the WSN gateway and the IoT gateway have a server communicating with TCP / IP, and provide the information in the WSN to the external network.

Non-patent papers 1 and 2 can request information from a client of an external network capable of TCP / IP communication, but there is a limitation in providing information of an event type occurring according to a specific condition to an external client in real time. The sensor nodes can not request information of the external network.

A non-patent document 3 for connecting the WSN and the IP network describes the content of each sensor node in the WSN communicating with the host of the external IP network through the gateway.

In the non-patent document 3, the gateway manages each node in the WSN by assigning a virtual IP address, and bidirectional communication is possible through mutual conversion between the WSN protocol and the IP network protocol. However, there is no common specification for representing information from the viewpoint of information exchange, and there is a problem in that a sensor node having a resource constraint is burdened in processing the maximum transmission unit of TCP / IP, and there is a limit to expanding to the object internet environment.

Non-patent papers 4 describe the contents of a smart gateway that links WSN and Web contents. The smart gateway converts the operational content already existing on the web such as weather information and web cam image into a virtual sensor node and provides it to the WSN.

The virtual sensor node periodically updates the web content to provide it to the physical sensor node, but the entity is a software function of the smart gateway. In particular, considering the sensor nodes that have resource constraints in protocol conversion, CoAD (Constrained Application Protocol) of Internet Engineering Task Force (IETF) is used to alleviate the burden.

However, since CoAP is an application layer protocol based on UDP or TCP, there is a problem that it is difficult to quickly apply the existing WSN sensor node operating as a unique protocol without considering it.

1. Lili Wu, J. Riihijarvi J. and P. Mahonen, "A Modular Wireless Sensor Network Gateway Design", Communications and Networking in China, CHINACOM '07. Second International Conference, pp.882-886, 2007. 2. Q. Zhu, R. Wang, Q. Chen, Y. Liu and W. Qin, "IOT Gateway: Bridging Wireless Sensor Networks into Internet of Things", Embedded and Ubiquitous Computing, 2010 IEEE / IFIP 8th International Conference, pp .347-352, 2010. 3. K. A. Emara, M. Abdeen and M. Hashem, "A Gateway-based Framework for Transparent Interconnection WSN and IP Network", In EUROCON '09, pp. 1775-1780, 2009. 4. D. Bimschas, H. Hellbruck, R. Mietz, D. Pfisterer, K. Romer and T. Teubler, "Middleware for Smart Gateways Connecting Sensors to the Internet", In Proceedings of the 5th International Workshop on Middleware Tools, Services and Run-time Support for Sensor Networks (MidSens' 10), pp. 8-14, 2010.

The present invention designs a data / event / service of an object Internet environment using a ZigBee adapter as a ZigBee packet based on the ZigBee standard, provides interoperation between the ZigBee network and other networks of the object internet environment based on the DDS, The present invention provides a system and method for interworking with a ZigBee network and a DDS-based object Internet network that enables bidirectional communication and data / event / service interworking between different networks.

Among the embodiments, an interworking system of a DDS-based Internet and a ZigBee network has an interface for allowing different applications to exchange information through a topic connection so as to manage distributed data based on a publication / subscription model A Data Distributed Service (DDS) system; Events, or services from ZigBee nodes in a ZigBee network and converts them into data topics, event topics, or service topics and publishes them to the DDS system, subscribes data topics, event topics, or service topics from the DDS system, And a ZigBee adapter for allocating a virtual ZigBee node for providing to the network to provide interoperation between other networks in the object Internet environment.

The data topic and the event topic include a field of an adapter identifier (ID), a data / event type (TYPE), and a data / event value (VALUE) that have issued the topic.

The service topic includes a service publication topic, a service request topic, and a service response topic. The service publication topic includes a service providing adapter identifier (ID), a service identifier (NAME), parameters required for a call (PARAMETERS) Wherein the service request topic includes a field of a service providing adapter identifier (DESTINATION), a service request adapter identifier (SOURCE), a service identifier (NAME), and parameters to be transmitted in a service call (PARAMETERS) The service response topic includes a field of a service request adapter identifier (DESTINATION), a service providing adapter identifier (SOURCE), a service identifier (NAME), and a service call result value (RESULT).

The virtual Zigbee node is allocated a valid address and performs bidirectional communication with another network of the object Internet environment while maintaining Zigbee communication to perform a role of a physical Zigbee node.

Wherein the ZigBee adapter maintains the ZigBee network, collects data, events or services from the ZigBee nodes, extracts data, events or services from topics subscribed from the DDS system, converts the data, events or services into virtual ZigBee nodes, A ZigBee coordinator provided to the network; A meta data manager for converting the data, event or service collected through the Zigbee coordinator or subscribed in the DDS system into a meta data type and storing the meta data; A topic instance manager for creating a topic instance for publishing data, events or services stored in the meta data manager to the DDS system, checking the validity of the subscribed topic instance in the DDS system, and transmitting the checked topic to the meta data manager; And a DDS entity manager for generating an entity related to a topic instance created in the topic instance manager, for publishing the topic to the DDS system, and for transmitting the topic subscribed in the DDS system to the topic instance manager. do.

And the ZigBee coordinator transmits and receives information on data, events or services from the ZigBee nodes in the form of a ZigBee packet.

The ZigBee packet includes a receiver section, a sender section, a data number section, and a data section, and the data section includes an operation field for determining an operation of the corresponding packet, a pattern field for determining a transmission / And a data field including information of data, events or services of the ZigBee network.

Wherein the operation field includes first information for managing the ZigBee network, second information for an ad hoc network configuration, third information for specifying the data, an event or a service, And fourth information for search or interworking.

Wherein the first information includes Join information for informing the ZigBee coordinator of a unique address and role of the ZigBee node when a new ZigBee node is connected to the ZigBee network; Reset information for reconfiguring the network by considering the physical constraints of the ZigBee node by the ZigBee coordinator; Leave information indicating that the Zigbee node in the Zigbee network is disconnected from the ZigBee coordinator before disconnecting from the ZigBee network to which the ZigBee node belongs; And heartbeat information for periodically checking the operation status of the ZigBee node.

And the second information is routing information for extending the communication range by configuring the ZigBee network as an ad hoc network through a ZigBee router.

The third information is type information indicating a type of information of data, event or service of the ZigBee network, and metadata information including data indicating data, event or service .

The fourth information may include activity information that the Zigbee nodes search for their data, events, or services from other Zigbee nodes, and transmits the retrieved data, events, or services to the Zigbee coordinator to be transmitted / .

The DDS entity manager includes a plurality of data writers (DataWriters) or a plurality of data readers. The topic instances generated by the topic instance manager are assigned a service quality of the DDS system to generate a topic, And publishes or subscribes to a topic.

The ZigBee adapter may further include a service invoker supporting a request / response type service call to a data communication of a publication / subscription type based on a quality of service (QoS) of the DDS system.

The Topic Instance Manager makes a service call without converting the request / response type service call into a meta data type.

Among the embodiments, a method of interworking a DDS-based object Internet network with a ZigBee network is a method of interworking between a ZigBee network and other objects in the Internet through a data distribution service (DDS) based on a publication / A method of interworking with a ZigBee network and a DDS-based Internet for supporting information exchange, comprising the steps of: designing a ZigBee packet based on a ZigBee standard on data, events or services of the Internet of objects; Generating and managing a DDS entity so that a Zigbee adapter that maintains the DDS operates based on the DDS; Collecting data, events or services from ZigBee nodes in the ZigBee network, converting the data, events or services into data topics, event topics or service topics, and publishing the data, events or services to the DDS; The ZigBee adapter allocating a virtual ZigBee node for subscribing to a data topic, an event topic, or a service topic published in the external network from the DDS and providing it to the ZigBee network; And the ZigBee nodes performing interworking of bi-directional communication, data, event or service with an external network while maintaining Zigbee communication.

The data topic and the event topic include a field of an adapter identifier (ID), a data / event type (TYPE), and a data / event value (VALUE) that have issued the topic.

The service topic includes a service publication topic, a service request topic, and a service response topic. The service publication topic includes a service providing adapter identifier (ID), a service identifier (NAME), a parameter required for a call (PARAMETERS) Wherein the service request topic includes a field of a service providing adapter identifier (DESTINATION), a service request adapter identifier (SOURCE), a service identifier (NAME), and parameters to be transmitted in a service call (PARAMETERS) The response topic includes a field of a service request adapter identifier (DESTINATION), a service providing adapter identifier (SOURCE), a service identifier (NAME), and a service call result value (RESULT).

Wherein the ZigBee adapter collects data, events, or services from ZigBee nodes in the ZigBee network and converts the data, events, or services into data topics, event topics, or service topics and publishes the data, events, And a ZigBee coordinator for communicating with the ZigBee network. The ZigBee coordinator collects data, events or services in the ZigBee network through the ZigBee coordinator.

The ZigBee packet includes a receiver section, a sender section, a data number section, and a data section, and the data section includes an operation field for determining an operation of the corresponding packet, a pattern field for determining a transmission / And a data field including information of data, events or services of the ZigBee network.

Wherein the operation field includes first information for managing the ZigBee network, second information for an ad hoc network configuration, third information for specifying the data, an event or a service, And fourth information for search or interworking.

Wherein the first information includes Join information for informing the ZigBee coordinator of a unique address and role of the ZigBee node when a new ZigBee node is connected to the ZigBee network; Reset information for reconfiguring the network by considering the physical constraints of the ZigBee node by the ZigBee coordinator; Leave information indicating that the Zigbee node in the Zigbee network is disconnected from the ZigBee coordinator before disconnecting from the ZigBee network to which the ZigBee node belongs; And heartbeat information for periodically checking the operation status of the ZigBee node.

And the second information is routing information for extending the communication range by configuring the ZigBee network as an ad hoc network through a ZigBee router.

The third information is type information indicating a type of information of data, event or service of the ZigBee network, and metadata information including data indicating data, event or service .

The fourth information may include activity information that the Zigbee nodes search for their data, events, or services from other Zigbee nodes, and transmits the retrieved data, events, or services to the Zigbee coordinator to be transmitted / .

Wherein the ZigBee node performs a bidirectional communication, data, event or service interworking with an external network while maintaining Zigbee communication, the ZigBee adapter verifies the validity of a ZigBee node added to the ZigBee network, A ZigBee node connection step of collecting an event or a service; A connection termination step of a Zigbee node releasing a resource allocated to the Zigbee node when the connection with the Zigbee node is terminated; A ZigBee node failure detection step of periodically checking the connection status of the ZigBee node to detect a ZigBee node disconnected from the ZigBee network and not to provide the resources allocated to the detected ZigBee node to another ZigBee node; Event, or service from the DDS, and when the service quality of the subscribed topic is valid, assigning an ID of a virtual Zigbee node to the topic, and storing the virtual ZigBee node in a metadata form step; Event, or service from the DDS, and, when the service quality of the subscribed topic is not valid, disconnecting the ID of the virtual Zigbee node associated with the topic and releasing the associated resources And an ending step.

Wherein the ZigBee adapter includes a service invoker supporting a service call in a request-response type, and when the service invoker receives a service request from a service request adapter or a ZigBee node, the service invoker transmits a service request topic for the service request to the DDS Publishing; The service invoker transmits the service response topic to the service request adapter or the ZigBee node when the service response topic is subscribed from the service providing adapter, the ZigBee node or the virtual ZigBee node.

A system and method for interworking with a DDS-based Internet and a ZigBee network according to the present invention is a system and method for designing a data / event / service in an object Internet environment using a ZigBee adapter as a ZigBee packet based on ZigBee standard, Events / services in a DDS-based topic to provide interoperability between ZigBee networks and other networks in the Internet environment based on DDS, thereby enabling bi-directional communication and data / event / Service interworking is possible, and real-time and reliability of interoperability can be ensured through quality of service (QoS) supported by DDS.

FIG. 1 is a diagram for explaining an interworking system between a DDS-based Internet and a ZigBee network according to an embodiment of the present invention.
2 is a diagram illustrating a structure of a ZigBee packet for data / event / service in a Zigbee network.
3 is a block diagram illustrating the configuration of the ZigBee adapter of FIG.
FIG. 4 is a view for explaining a process of issuing and subscribing a topic instance through an organic operation between components of the Zigbee adapter of FIG. 3;
FIG. 5 is a view for explaining an operation simulation of the ZigBee adapter of FIG. 1;
FIG. 6 is a flow chart illustrating a process of issuing data / event / service among a method of interworking between a DDS-based Internet and a ZigBee network according to the present invention.
FIG. 7 is a flowchart illustrating a virtual ZigBee allocation process among a method of interworking a DDS-based Internet and a ZigBee network according to the present invention.
FIG. 8 is a flowchart for explaining a connection process of a Zigbee node among a method of interworking a DDS-based Internet and a ZigBee network according to the present invention.
FIG. 9 is a flowchart illustrating a connection termination process of a Zigbee node among a method of interworking a DDS-based Internet and a ZigBee network according to the present invention.
10 is a flowchart for explaining a process of discarding a topic due to a failure of a Zigbee node among a method of interworking between a DDS-based Internet and a Zigbee network according to the present invention.
FIG. 11 is a flowchart illustrating a connection procedure of a virtual Zigbee node among a method of interworking a DDS-based Internet and a ZigBee network according to the present invention.
FIG. 12 is a flowchart illustrating a connection termination process of a virtual Zigbee node among a method of interworking a DDS-based Internet and a ZigBee network according to the present invention.

The description of the present invention is merely an example for structural or functional explanation, and the scope of the present invention should not be construed as being limited by the embodiments described in the text. That is, the embodiments are to be construed as being variously embodied and having various forms, so that the scope of the present invention should be understood to include equivalents capable of realizing technical ideas. Also, the purpose or effect of the present invention should not be construed as limiting the scope of the present invention, since it does not mean that a specific embodiment should include all or only such effect.

Meanwhile, the meaning of the terms described in the present invention should be understood as follows.

The terms "first "," second ", and the like are intended to distinguish one element from another, and the scope of the right should not be limited by these terms. For example, 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.

It is to be understood that when an element is referred to as being "connected" to another element, it may be directly connected to the other element, but there may be other elements in between. On the other hand, when an element is referred to as being "directly connected" to another element, it should be understood that there are no other elements in between. On the other hand, other expressions that describe the relationship between components, such as "between" and "between" or "neighboring to" and "directly adjacent to" should be interpreted as well.

It should be understood that the singular " include "or" have "are to be construed as including a stated feature, number, step, operation, component, It is to be understood that the combination is intended to specify that it does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

In each step, the identification code (e.g., a, b, c, etc.) is used for convenience of explanation, the identification code does not describe the order of each step, Unless otherwise stated, it may occur differently from the stated order. That is, each step may occur in the same order as described, may be performed substantially concurrently, or may be performed in reverse order.

All terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs, unless otherwise defined. Commonly used predefined terms should be interpreted to be consistent with the meanings in the context of the related art and can not be interpreted as having ideal or overly formal meaning unless explicitly defined in the present invention.

FIG. 1 is a diagram for explaining an interworking system between a DDS-based Internet and a ZigBee network according to an embodiment of the present invention.

Referring to FIG. 1, the DS-based Internet of the Internet and the interworking system of the ZigBee network operates based on the DDS system 100, which is a real-time communication middleware standard supporting publication / subscription communication, and the DDS, And a ZigBee adapter 200 that provides interoperation between different networks of the Internet of things.

The DDS system 100 provides the data, events, or services in the ZigBee network to the external network and enables bidirectional communication to receive data, events, or services from the external network. 1 type of communication, and 1: N, N: 1 or N: N types.

The network environment constituting the Internet of things is diverse, and the communication protocol of each network environment has a heterogeneous problem. Accordingly, the ZigBee adapter 200 can publish / subscribe to the DDS system 100 as a topic defined by IDL (Interface Definition Language) based on data, events or services of the object Internet environment based on the DDS.

In other words, the ZigBee adapter 200 converts data / events / services in the ZigBee network into topics, publishes them to the DDS system 100, subscribes to topics of data / events / services published in the external network, In the form of a node.

Therefore, ZigBee nodes in the ZigBee network maintain bi-directional communication and data / event / service interworking with the external network while maintaining ZigBee communication without regard to DDS or topic.

At this time, the data and events of the object Internet are defined by the IDL having the same structure, but the data to deal with the measurement value and the log and the characteristic of the event that occurs according to the specific condition and the state are different.

The data topic (Tdata) and the event topic (Tevent) are composed of the adapter identifier (ID) that issued the topic, the type of data / event (TYPE), and the value of data / event (VALUES).

The service of the Internet of Things issues the service publication topic (Ts.pub) to the DDS system 100 to identify each service of the Internet environment. The adapter that has subscribed to the service publication topic issues a service request topic (Ts.req) to the DDS system 100, and subscribes to the service response topic (Ts.res) to make a service call.

For example, the service provisioning adapter publishes Ts.pub to the DDS system 100, and the other adapters subscribe to Ts.pub to identify the service. After that, the adapter requesting the service issues Ts.req, and the service providing adapter issues it, and after processing the service, Ts.res is issued, and the adapter that originally requested is subscribed to Ts.res.

The service publication topic (Ts.pub) consists of a service provider adapter identifier (ID), a service identifier (NAME), a parameter required for a call (PARAMETERS), and a call result (RESULT) field.

The service request topic (Ts.req) consists of a service providing adapter identifier (DESTINATION), a service request adapter identifier (SOURCE), a service identifier (NAME), and parameters to be transmitted in service call (PARAMETERS).

The service response topic (Ts.res) consists of a service request adapter identifier (DESTINATION), a service provider adapter identifier (SOURCE), a service identifier (NAME), and a service call result (RESULT) field.

ZigBee end devices produce data / events / services individually, transfer them to a ZigBee coordinator, or collaborate between ZigBee end devices under the control of a ZigBee coordinator to produce data / events / services.

For example, Zigbee node of the wireless sensor node X is the data D A, dealing with a service S A, S A is and X is requesting D B to the ZigBee coordinator when they require D A and D B, receiving the A Zigbee coordinator informs wireless sensor node Y of the presence of X, and Y provides direct D B to X, allowing X to produce S A.

All wireless sensor nodes in the ZigBee network communicate according to the ZigBee standard, but they do not meet all the requirements of the application system utilizing the ZigBee network. Therefore, ZigBee packets must be designed based on the ZigBee standard in order to handle the data / events / services of the Internet environment in the ZigBee network.

2 is a diagram illustrating a structure of a ZigBee packet for data / event / service in a Zigbee network.

2, the ZigBee adapter 200 can maintain and manage a ZigBee network through a ZigBee packet, and can link data / events / services with other networks on the Internet.

Zigbee nodes in a ZigBee network communicate with each other with a unique address. The size of the address is 2 bytes, the ZigBee coordinator has an address of 0x00, and the ZigBee router and ZigBee end devices have addresses of 0x01 to 0xFE. The address of 0xFF is used as the broadcast address.

At this time, the ZigBee packet includes a receiver section, a sender section, a number of data section, and a data section. The ZigBee node receives when the address value of the receiver section is its own address or broadcast address, and writes its own address in the sender section and transmits it.

The data section includes an operation field for determining an operation of the corresponding packet, a pattern field for determining a transmission / reception mode, and a data field including information of a data / event / service of the ZigBee network.

The ZigBee nodes determine the operation to be performed through the operation field of the received ZigBee packet, and determine the transmitting and receiving methods such as forwarding, request-response, request-response-confirmation, etc. through the pattern field.

The operation field includes first information for managing the ZigBee network, second information for configuring the ad hoc network, third information for specifying the data / event / service, and fourth information for searching and interworking of the data / event / service .

First, the first information for managing the ZigBee network includes Join, Reset, Leave, and Heartbeat.

In the Join field, the operation field value is Operation 0x01, and when the new payment node accesses the ZigBee network, it informs the ZigBee coordinator of its own address and role (ZR / ZED / ZR + ZED). At this time, ZR is a ZigBee router and ZED is a ZigBee end device.

Reset is the operation field whose value is Operation 0x02, and the ZigBee coordinator reconfigures the network considering the physical constraints of the ZigBee node. In order to maintain a long life of a wireless sensor node operating with a limited power supply, a network structure having a low transmission / reception cost is typically reconstructed.

If the value of the operation field is Operation 0x03, and the ZigBee network sends a Rib packet to the ZigBee coordinator before the ZigBee network disconnects the ZigBee network, the ZigBee coordinator that received the Rib packet transmits the resource allocated for the ZigBee node Can be released.

The heartbeat may have intermittent failures due to physical constraints (frequency interference, power supply, etc.) due to the nature of the ZigBee node in the operation field value of Operation 0x04. When the ZigBee coordinator periodically sends heartbeats Packets can be sent to grasp the operating state of the ZigBee node.

Next, the second information for the ad hoc network configuration is routing information, a ZigBee network consisting of a wireless sensor node, i.e., a ZigBee node, whose operation field value is Operation 0x05 and the communication range is about 10 to 75 m, And configure the ad hoc network through the router to extend the communication range. Exchange routing information packets between ZigBee routers and exchange routing tables.

The third information for the specification of the data / event / service is Metadata, and the value of the operation field is Operation 0x06. The ZigBee nodes specify to the ZigBee coordinator what metadata / data / event / service they are producing. At this time, the metadata packet is used to write the type (data: 0x01, event: 0x02, service: 0x03) of the information included in the metadata packet in the type field, and data / Express an event / service.

Finally, the fourth information for retrieval and interlocking of the data / event / service is an activity, and the value of the operation field is Operation 0x07. The ZigBee nodes in the ZigBee network can send activity packets to the ZigBee coordinator to search for data / events / services of other ZigBee nodes (Type: 0x04). The retrieved data / events / services send and receive activity packets between ZigBee nodes .

3 is a block diagram illustrating the configuration of the ZigBee adapter of FIG.

3, the ZigBee adapter 200 includes a ZigBee coordinator 210, a metadata manager 220, a topic instance manager 240, a DDS entity manager 250, and a service invoker 230.

Zigbee nodes in the Zigbee network include a Zigbee Coordinator (ZC) 210 for creating, maintaining and managing a network, collecting information, a Zigbee Router (ZR) 202 for supporting an ad hoc network configuration ), A Zigbee End Device (ZES) 201 for producing and consuming information, and controlling other devices.

The ZigBee coordinator 210 transmits and receives ZigBee packets to maintain and manage the ZigBee network, and collects data, events, and services transmitted by the ZigBee nodes. Also, the ZigBee coordinator 210 converts the data / events / services extracted from the topics subscribed in the DDS system 100 into virtual zigbee nodes 203 and provides them to the zigbee network.

At this time, since the virtual ZigBee node 203 is assigned a valid address and is recorded in the routing table of the ZigBee router 202, it can be operated as a physical node. Accordingly, the virtual ZigBee node 203 enables bi-directional communication with another network of the object Internet environment while maintaining the original Zigbee communication without consideration of the DDS or the topic by the Zigbee nodes in the ZigBee network.

The metadata manager 220 converts data / events / services collected in the ZigBee network or subscribed in the DDS system 100 into a metadata form and stores the data / event / service in the relational database 221.

Table 1 is a part of the metadata table stored in the database 221, and distinguishes each row with a unique ID as a node ID and a time stamp (Time Stamp). The Role field distinguishes between a physical ZigBee node and a virtual ZigBee node, and the specification of the data / event / service produced by each node is stored in a Type field, a Key field, and a Value field.

Figure pat00001

Topic instance manager 240 creates a topic instance so that it can publish data / events / services to DDS system 100, validates the topic instance subscribed in DDS system 100 and stores it in relational database 221 To be stored. Topic instance manager 240 allows calls to be made without converting the service call of the request-response type into a metadata form.

The DDS entity manager 250 generates and manages the DDS entity using the DDS API for publishing-subscription communication based on the DDS. The DDS entity manager 250 includes a publisher 120 and a subscriber 110, which are core entities for managing publish-subscribe communication, and have a plurality of data readers and data writers.

The DDS entity manager 250 may generate a topic by giving the specification QoS of the data / event / service defined by IDL, and publish / subscribe a plurality of topics through a plurality of data readers and data writers.

In the meantime, data and events are mainly composed of 1: N, N: 1, and N: N, but service is called in 1: 1 request-response format and is called as synchronous / asynchronous . Accordingly, the service invoker 230 supports the service call of the request-response type in the issue-subscription type data communication based on the QoS of the DDS.

The service invoker 230 takes the time-out into consideration in the case of a synchronous service and receives a response in response to a service requester through a service listener in the case of an asynchronous service Support.

FIG. 4 is a view for explaining a process of issuing and subscribing a topic instance through an organic operation between components of the Zigbee adapter of FIG. 3;

Referring to FIG. 4, the data / event / service in the ZigBee network is collected through the ZigBee coordinator 210, transferred to the metadata manager 220, and stored in the form of metadata.

The topic instance manager 240 converts the data / event / service converted into the metadata form into a topic instance and is published to the DDS system 100 through the DDS entity manager 250.

The DDS entity manager 250 subscribes to the topic instance of data / event / service from the DDS system 100 and passes the subscribed topic to the topic instance manager 240 for validation.

Topic instance manager 240 passes valid topic instances to metadata manager 220 to be stored in metadata form. The ZigBee coordinator 210 extracts data / events / services from the stored metadata and allocates virtual ZigBee nodes to provide the corresponding data / events / services to the ZigBee network.

In particular, in the case of a service, when a physical Zigbee node requests a service to a virtual Zigbee node, the service requesting topic instance is published to the DDS system 100 through the service invoker 230, not the metadata manager 220. Then, the ZigBee coordinator 210 delivers the service response to the service invoker 230 when the service response topic instance is subscribed, and sends the service response packet to the physical Zigbee node that requests the service by loading the address of the virtual Zigbee node.

Although the virtual ZigBee node has no physical entity, it acts as if the physical node in the ZigBee network actually exists by the organic operation between the components of the Zigbee adapter 200. [ Accordingly, the ZigBee network can perform bidirectional communication with other networks in the object Internet environment through the ZigBee adapter 200, thereby organically linking data / events / services.

FIG. 5 is a view for explaining an operation simulation of the ZigBee adapter of FIG. 1;

5, the ZigBee adapter 200 converts a service in the ZigBee network into a service publication topic and issues it to the DDS system 100, and the virtual adapter 300 replaces the other network of the object's internal net.

For example, the virtual adapter 200 may be an RFID adapter that manages data collected through an RFID tag, a REST adapter that handles RESTful web services, and so on.

The ZigBee coordinator 210 of the ZigBee adapter 200 receives the service information transmitted by the ZigBee node in the form of a zigbee packet, converts the received service information into a meta data format, and transmits the converted meta data to the meta data manager.

The metadata manager 220 stores the received metadata in the database 221, and the stored metadata is used by the topic instance manager to create a topic instance. Topic instance manager 240 translates the metadata into service publication topic instances and delivers them to DDS system 100 with appropriate QoS when DDS entity manager 250 exits.

FIG. 6 is a flow chart illustrating a process of issuing data / event / service among a method of interworking between a DDS-based Internet and a ZigBee network according to the present invention.

6, the ZigBee adapter 200 converts a data / event / service of a ZigBee network into a topic and publishes it to the DDS system 100 or subscribes to a topic from the DDS system 100 to create a virtual ZigBee node in the ZigBee network .

First, the ZigBee adapter 200 internally holds a ZigBee coordinator 210 to communicate with a ZigBee network, and collects data / events / services transmitted in the form of a ZigBee packet (PPP frame) from a ZigBee node in the ZigBee network. WaitForAllZigbeeMetadata)

The ZigBee adapter 200 converts the collected data / event / service into metadata (PPPFrameToZigbeeMetadata), transfers the metadata to the metadata manager, and stores it in the relational database 221. (SaveZigbeeMetadata, nsertMetadata)

The metadata manager 220 sends the metadata to the topic instance manager 240 to request topic publishing (DeliverMetadata), and the topic instance manager 240 converts the metadata to a topic instance. (MetadataToTopicInstance)

Topic instance manager 240 translates actual data / events with valid values into data / event topic instances without publishing them to DDS system 100 in the case of data / events, and to DDS system 100 in case of services Create a service publishing topic instance for publication.

The topic instance manager 240 requests the DDS entity manager 250 to publish the topic instance (PublishTopicInstance), and the DDS entity manager registers the topic instance in the DDS system with the data writer. (DataWriter.register_instance)

The DDS entity manager 250 issues a sample of the corresponding topic instance through the data writer. (DataWriter.write)

FIG. 7 is a flowchart illustrating a virtual ZigBee allocation process among a method of interworking a DDS-based Internet and a ZigBee network according to the present invention.

Referring to FIG. 7, when the ZigBee adapter 200 subscribes to the data topic, the event topic, and the service publication topic published in the DDS system 100, the QoS is confirmed and only the valid topics are assigned to the IDs of the virtual Zigbee nodes, 221).

The DDS entity manager 250 subscribes to all the subscriptionable samples for the existing registered topic (WaitForDDSMetadata) and subscribes all the subscribable samples for the existing registered topic from the DDS system (DataReader.take).

The DDS entity manager 250 delivers the subscribed sample to the topic instance manager 240. (DeliverTopicInstance) The topic instance manager 240 verifies the validity of the sample delivered from the DDS entity manager. (CheckTopicInstanceState)

The Topic Instance Manager 240 transforms the subscribed sample into metadata (TopicInstanceToDDSMetadata), and transmits the metadata to the metadata manager 220 to request to save it (SaveDDSMetadata)

The metadata manager 220 stores the metadata in the database 221 and the ZigBee coordinator 210 creates a virtual ZigBee node based on the metadata stored in the database 221. (JoinVirtualZibeeNode)

The ZigBee coordinator 210 converts the metadata into a ZigBee packet and provides it to the ZigBee network (MetadataToPPPFrame), and assigns an ID for creating a virtual ZigBee node to the ZigBee network (AllocateVirtualZigbeeNode)

The metadata manager 220 receives a virtual ZigBee node (device_id) from the ZigBee coordinator 210 and updates the metadata of the virtual ZigBee node. (UpdataMetadata)

FIG. 8 is a flowchart for explaining a connection process of a Zigbee node among a method of interworking a DDS-based Internet and a ZigBee network according to the present invention.

Referring to FIG. 8, the ZigBee adapter checks whether the ZigBee node added to the ZigBee network has a valid address after the initial value is set, and transmits its data / event / service to the ZigBee coordinator 210.

The ZigBee coordinator 210 connects to the ZigBee network when a new ZigBee node transmits a hello message (HelloMessage), and registers the data / event / service held by the ZigBee node in the ZigBee coordinator 210. (RegisterZigbeeMetadata)

The ZigBee coordinator 210 converts a ZigBee packet into a metadata format (PPPFrameToZigbeeMetadata), and transmits the metadata to the metadata manager 220 to request storage of the metadata (SaveZigbeeMetadata)

The metadata manager 220 stores the metadata in the database 221 (InsertMetadata), and transmits the metadata to the topic instance manager 240 to request topic publishing (DeliverMetadata)

The topic instance manager 240 converts the metadata to a topic instance (MetadataToTopicInstance) and requests the DDS entity manager 250 to publish the topic instance (PublishTopicInstance)

The DDS entity manager 250 registers the topic instance in the DDS system via the DDS writer (DataWriter.register_instance) and publishes the sample of the topic instance via the data writer (DataWriter.write)

FIG. 9 is a flowchart illustrating a connection termination process of a Zigbee node among a method of interworking a DDS-based Internet and a ZigBee network according to the present invention.

Referring to FIG. 9, the ZigBee node can not maintain the network connection due to power supply restriction, or terminates the connection with the ZigBee network according to the network reconfiguration policy of the ZigBee coordinator 210. Therefore, the ZigBee coordinator 210 explicitly releases the resources allocated to the corresponding ZigBee node through the connection termination process of the corresponding ZigBee node.

When the ZigBee node attempts to terminate the connection with the ZigBee network (ByeMessage), the ZigBee coordinator 210 converts the ZigBee packet type ending attempt into the metadata type (PPPFrameToZigbeeMetadata).

The ZigBee coordinator 210 transmits the metadata to the metadata manager 220 to request deletion (DropZigbeeMetadata), and the metadata manager 220 searches the database 221 for metadata requested to be deleted. (SelectMetadata)

The metadata manager 220 delivers the retrieved metadata to the topic instance manager 240 (DeliverMetadata), and the topic instance manager 240 converts the metadata into a topic instance. (MetadataToTopicInstance)

The topic instance manager 240 requests the DDS entity manager 250 to remove the topic instance (UnregisterTopicInstance), and the DDS entity manager 250 removes the topic instance from the data writer. (DataWriter.unregister_instance)

The metadata manager 220 deletes the corresponding metadata stored in the database 221. (DeleteMetadata)

10 is a flowchart for explaining a process of discarding a topic due to a failure of a Zigbee node among a method of interworking between a DDS-based Internet and a Zigbee network according to the present invention.

Referring to FIG. 10, a ZigBee node may have an intermittent connection failure due to physical constraints such as frequency interference, natural disaster, and power supply. The ZigBee coordinator 210 periodically checks the connection of the ZigBee node to detect the disconnected ZigBee node and does not release the resources allocated to the disconnected ZigBee node but does not provide it to other ZigBee nodes.

When the ZigBee coordinator 210 detects a ZigBee node whose connection to the ZigBee network has been terminated, the ZigBee coordinator 210 determines that the connection is terminated due to a failure. (DetectDisconnectedZigbeeNode) The ZigBee coordinator 210 transmits a ZigBee packet- (PPPFrameToZigbeeMetadata), and transmits the metadata to the metadata manager 220 to request deletion. (DropZigbeeMetadata)

The metadata manager 220 searches the database 221 for metadata requested to be deleted (SelectMetadata), and delivers the metadata to the topic instance manager 240. (DeliverMetadata)

The topic instance manager 240 converts the corresponding metadata into a topic instance (MetadataToTopicInstance), and requests the DDS entity manager 250 to discard the topic instance (DisposeTopicInstance)

The DDS entity manager 250 disposes of the topic instance in the data writer, but the topic instance does not publish / subscribe for a period of time during which the ZigBee node is disconnected, but is not a completely removed topic instance. (DataWriter.dispose)

The metadata manager 220 updates the access to the metadata stored in the database 221. (UpdataeMetadata)

FIG. 11 is a flowchart illustrating a connection procedure of a virtual Zigbee node among a method of interworking a DDS-based Internet and a ZigBee network according to the present invention.

Referring to FIG. 11, the ZigBee adapter 200 continuously subscribes to data / event topics and service publishing topics that have been published to the DDS system 100. At this time, the ZigBee adapter 200 assigns a virtual ZigBee node to a topic stored in the relational database 221. The topic is stored in the relational database 221, and the QoS is valid.

The DDS entity manager 250 subscribes to all of the subscribable samples (WaitForDDSMetadata) and delivers the newly subscribed sample to the topic instance manager 240. (DeliverTopicInstance)

Topic instance manager 240 validates the subscribed samples (CheckTopicInstanceState) and converts them to DDS metadata (TopicInstanceToDDSMetadata).

The Topic Instance Manager 240 sends the DDS metadata to the Meta Data Manager 220 to request a SaveDDSMetadata and the Meta Data Manager 220 stores the DDS Metadata in the Database 221. [

The metadata manager 220 creates a virtual ZigBee node based on the DDS metadata stored in the database 221 with the ZigBee coordinator 210. (JoinVirtualZigbeeNode)

The ZigBee coordinator 210 converts the DDS metadata into a ZigBee packet and provides the ZigBee packet to the ZigBee network. (MetadataToPPPFrame) The ZigBee coordinator 210 assigns an ID for creating a virtual ZigBee node to the ZigBee network (AllocateVirtualZigbeeNode)

The metadata manager 220 receives the ID of the virtual Zigbee node from the ZigBee coordinator 210 and updates the ZigBee metadata.

FIG. 12 is a flowchart illustrating a connection termination process of a virtual Zigbee node among a method of interworking a DDS-based Internet and a ZigBee network according to the present invention.

Referring to FIG. 12, the ZigBee adapter 200 subscribes to the data / event topic and the service publishing topic published in the DDS system 100, and confirms the QoS of each topic. If the QoS of the subscribed topic is not valid, the ZigBee adapter 200 releases the ID of the virtual ZigBee node associated with the topic and related resources so that the ZigBee node can not access the corresponding virtual ZigBee node.

The DDS entity manager 250 subscribes to all of the subscribable samples (WaitForDDSMetadata) and forwards the subscribed samples to the topic instance manager 240. (DeliverTopicInstance)

The topic instance manager 240 validates the subscribed samples (CheckTopicInstanceState) and converts the subscribed samples to DDS metadata (TopicInstanceToDDSMetadata).

The Topic Instance Manager 240 sends the DDS metadata to the Meta Data Manager 220 to request deletion (DropDDSMetadata) and the Meta Data Manager 220 retrieves the corresponding DDS Meta Data from the Database 221. (SelectMetadata )

The metadata manager 220 requests the ZigBee coordinator 210 to terminate the connection of the virtual ZigBee node based on the DDS metadata stored in the database. (LeaveVirtualZigbeeNode)

The ZigBee coordinator 210 converts the DDS metadata into a ZigBee packet and provides it to the ZigBee network. (MetadataToPPPFrame) The ZigBee coordinator 210 releases the ID for creating a virtual ZigBee node in the ZigBee network (DeallocateVirtualZigbeeNode) (220) deletes the ZigBee metadata of the virtual ZigBee node (DeleteMetadata)

As described above, the operation of the ZigBee adapter 200 can be largely divided into an initial value setting state and a run time state. The initial setup state is an operation in which the ZigBee adapter 200 previously converts data and events / services of the existing ZigBee network into a DDS-based topic and subscribes to the existing DDS topic to create a virtual ZigBee node in the ZigBee network . The runtime state is a state in which a ZigBee node or a virtual ZigBee node is connected according to a ZigBee network and a DDS topic that change after initial setting such as when a new ZigBee node is connected to the ZigBee network or a new DDS topic is subscribed while the ZigBee adapter 200 is operating Or terminate the operation.

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

100: DDS system 200: ZigBee adapter
210: ZigBee coordinator 220: Meta data manager
221: Database 230: Service Invoker
240: Topic Instance Manager 250: DDS Entity Manager

Claims (27)

A Data Distributed Service (DDS) system that provides an interface for different applications to exchange information through topic connections so that distributed data can be managed based on a publication / subscription model; And
An event topic or a service topic from the ZigBee nodes in the ZigBee network and converts it into a data topic, an event topic, or a service topic and publishes it to the DDS system, subscribes a data topic, an event topic, or a service topic from the DDS system, And a ZigBee adapter for providing interoperability between other networks in the object Internet environment by allocating a virtual ZigBee node to the ZigBee network.
The method according to claim 1,
Wherein the data topic and the event topic include fields of an adapter identifier (ID), a data / event type (TYPE), and a data / event value (VALUE) that have issued the topic. Interworking system with ZigBee network.
The method according to claim 1,
The service topic includes a service publication topic, a service request topic, and a service response topic,
The service publishing topic includes fields of a service providing adapter identifier (ID), a service identifier (NAME), a parameter required for a call (PARAMETERS), and a result of a call (RESULT)
The service request topic includes fields of a service providing adapter identifier (DESTINATION), a service request adapter identifier (SOURCE), a service identifier (NAME), and parameters to be transmitted in a service call (PARAMETERS)
Wherein the service response topic includes a field of a service request adapter identifier (DESTINATION), a service provider adapter identifier (SOURCE), a service identifier (NAME), and a service call result value (RESULT) And ZigBee network.
The method according to claim 1,
Wherein the virtual ZigBee node allocates a valid address and performs bi-directional communication with another network of the object Internet environment while maintaining Zigbee communication so as to perform a role of a physical Zigbee node. The DDS- Interworking system with network.
The method according to claim 1,
The ZigBee adapter includes:
Events, or services from the ZigBee nodes, extracts data, events, or services from topics subscribed from the DDS system, converts them into virtual ZigBee nodes, and provides them to the ZigBee network. coordinator;
A meta data manager for converting the data, event or service collected through the Zigbee coordinator or subscribed in the DDS system into a meta data type and storing the meta data;
A topic instance manager for creating a topic instance for publishing data, events or services stored in the meta data manager to the DDS system, checking the validity of the subscribed topic instance in the DDS system, and transmitting the checked topic to the meta data manager; And
And a DDS entity manager for generating an entity related to the topic instance generated in the topic instance manager, for publishing the topic to the DDS system, and for transmitting the topic subscribed in the DDS system to the topic instance manager A system of interworking between DDS - based Internet and ZigBee networks.
6. The method of claim 5,
The ZigBee coordinator
And transmits / receives data, event, or service information from the ZigBee nodes in the form of a ZigBee packet to / from a ZigBee network.
The method according to claim 6,
The ZigBee packet includes a receiver section, a sender section, a data number section, and a data section,
Wherein the data interval further includes an operation field for determining an operation of the corresponding packet, a pattern field for determining a transmission / reception mode, and a data field for storing data, event or service information of the ZigBee network. A system for interworking between Internet and ZigBee networks.
8. The method of claim 7,
Wherein the operation field includes first information for managing the ZigBee network, second information for an ad hoc network configuration, third information for specifying the data, an event or a service, And fourth information for search or interworking with the ZigBee network.
9. The method of claim 8,
The first information
Join information for informing the ZigBee coordinator of a unique address and role of the ZigBee node when a new ZigBee node is connected to the ZigBee network;
Reset information for reconfiguring the network by considering the physical constraints of the ZigBee node by the ZigBee coordinator;
Leave information indicating that the Zigbee node in the Zigbee network is disconnected from the ZigBee coordinator before disconnecting from the ZigBee network to which the ZigBee node belongs; And
Wherein the ZigBee coordinator periodically includes heartbeat information for checking the operation status of the ZigBee node.
9. The method of claim 8,
Wherein the second information is routing information for expanding the communication range by configuring the ZigBee network through the ZigBee router to form an ad hoc network, wherein the second information is a DDS-based Internet of objects and a ZigBee network.
9. The method of claim 8,
The third information
Type information indicating a type of information of a data, an event or a service of the Zigbee network, and metadata information including data indicating data, an event or a service. And a system for interworking with a ZigBee network.
9. The method of claim 8,
The fourth information may include activity information that the Zigbee nodes search for their data, events, or services from other Zigbee nodes, and transmits the retrieved data, events, or services to the Zigbee coordinator to be transmitted / A system for interworking with a DDS-based Internet network and a ZigBee network.
6. The method of claim 5,
The DDS entity manager,
A plurality of data writers (DataWriter) or a plurality of data readers (DataReader), and the topic instance generated by the topic instance manager is given a service quality of the DDS system to generate a topic, and then a plurality of topics are published or subscribed A system for interworking with a DDS-based Internet network and a ZigBee network.
6. The method of claim 5,
The ZigBee adapter includes:
Further comprising a service invoker supporting a request / response type service call to a publication / subscription type data communication based on a quality of service (QoS) of the DDS system. Interworking system with network.
15. The method of claim 14,
Wherein the Topic Instance Manager causes a service call to be made without converting the service call of the request / response type into a meta data format.
A method of interworking with a DDS-based Internet network and a ZigBee network that supports exchange of information between a ZigBee network and other networks via a data distribution service (DDS) based on a publication / subscription model ,
Designing a ZigBee packet based on the ZigBee standard for data, events, or services of the object Internet, and creating and managing a DDS entity so that a ZigBee adapter that manages the ZigBee network through the ZigBee packet operates based on the DDS;
Collecting data, events or services from ZigBee nodes in the ZigBee network, converting the data, events or services into data topics, event topics or service topics, and publishing the data, events or services to the DDS;
The ZigBee adapter allocating a virtual ZigBee node for subscribing to a data topic, an event topic, or a service topic published in the external network from the DDS and providing it to the ZigBee network; And
Wherein the ZigBee nodes include a step of performing bidirectional communication, data, event or service interworking with an external network while maintaining Zigbee communication, and a method of interworking between a DDS-based Internet and a ZigBee network.
17. The method of claim 16,
Wherein the data topic and the event topic include fields of an adapter identifier (ID), a data / event type (TYPE), and a data / event value (VALUE) that have issued the topic. How to interwork with ZigBee network.
17. The method of claim 16,
The service topic includes a service publication topic, a service request topic, and a service response topic,
The service publishing topic includes fields of a service providing adapter identifier (ID), a service identifier (NAME), a parameter required for a call (PARAMETERS), and a result of a call (RESULT)
The service request topic includes fields of a service providing adapter identifier (DESTINATION), a service request adapter identifier (SOURCE), a service identifier (NAME), and parameters to be transmitted in a service call (PARAMETERS)
Wherein the service response topic includes a field of a service request adapter identifier (DESTINATION), a service provider adapter identifier (SOURCE), a service identifier (NAME), and a service call result value (RESULT) And ZigBee network.
17. The method of claim 16,
Wherein the ZigBee adapter collects data, events, or services from ZigBee nodes in the ZigBee network and converts the data, events, or services into data topics, event topics, or service topics,
And a ZigBee coordinator for communicating data, events or services of the object Internet environment in the form of ZigBee packets based on the ZigBee standard and communicating with the ZigBee network, and collecting data, events or services in the ZigBee network through the ZigBee coordinator A method for interworking with a network of a DDS-based Internet and a ZigBee network.
20. The method of claim 19,
The ZigBee packet includes a receiver section, a sender section, a data number section, and a data section,
Wherein the data interval further includes an operation field for determining an operation of the corresponding packet, a pattern field for determining a transmission / reception mode, and a data field for storing data, event or service information of the ZigBee network. A method of interworking with the Internet network and the ZigBee network.
21. The method of claim 20,
Wherein the operation field includes first information for managing the ZigBee network, second information for an ad hoc network configuration, third information for specifying the data, an event or a service, And a fourth information for searching or interworking with the ZigBee network.
22. The method of claim 21,
The first information
Join information for informing the ZigBee coordinator of a unique address and role of the ZigBee node when a new ZigBee node is connected to the ZigBee network;
Reset information for reconfiguring the network by considering the physical constraints of the ZigBee node by the ZigBee coordinator;
Leave information indicating that the Zigbee node in the Zigbee network is disconnected from the ZigBee coordinator before disconnecting from the ZigBee network to which the ZigBee node belongs; And
Wherein the ZigBee coordinator periodically includes heartbeat information for checking the operation status of the ZigBee node.
22. The method of claim 21,
Wherein the second information is routing information for expanding the communication range by configuring the ZigBee network through the ZigBee router to form an ad hoc network, wherein the second information is the routing information for the ZigBee network.
22. The method of claim 21,
The third information
Type information indicating a type of information of a data, an event or a service of the Zigbee network, and metadata information including data indicating data, an event or a service. And a method of interworking with a ZigBee network.
22. The method of claim 21,
The fourth information may include activity information that the Zigbee nodes search for their data, events, or services from other Zigbee nodes, and transmits the retrieved data, events, or services to the Zigbee coordinator to be transmitted / A method for interworking with a network of a DDS-based Internet and a ZigBee network.
17. The method of claim 16,
The step of performing interworking of bidirectional communication, data, event, or service with an external network while maintaining Zigbee communication,
The ZigBee adapter may include a ZigBee node connecting step of collecting data, events or services of the Zigbee node after confirming the validity of the Zigbee node added to the ZigBee network;
A connection termination step of a Zigbee node releasing a resource allocated to the Zigbee node when the connection with the Zigbee node is terminated;
A ZigBee node failure detection step of periodically checking the connection status of the ZigBee node to detect a ZigBee node disconnected from the ZigBee network and not to provide the resources allocated to the detected ZigBee node to another ZigBee node;
Event, or service from the DDS, and when the service quality of the subscribed topic is valid, assigning an ID of a virtual Zigbee node to the topic, and storing the virtual ZigBee node in a metadata form step;
Event, or service from the DDS, and, when the service quality of the subscribed topic is not valid, disconnecting the ID of the virtual Zigbee node associated with the topic and releasing the associated resources And terminating the DDS-based object-based Internet network and the ZigBee network.
19. The method of claim 18,
Wherein the ZigBee adapter includes a service invoker supporting a service call in a request-response form,
When the service invoker requests a service request from a service request adapter or a ZigBee node, publishing a service request topic for the service request to the DDS;
Wherein the service invoker transmits the service response topic to the service request adapter or the Zigbee node when the service response topic is subscribed from the service providing adapter, the Zigbee node or the virtual Zigbee node. And ZigBee network.
KR1020150047470A 2015-04-03 2015-04-03 System for interoperation network of IoT and network of Zigbee based DDS and Method thereof KR101673755B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020150047470A KR101673755B1 (en) 2015-04-03 2015-04-03 System for interoperation network of IoT and network of Zigbee based DDS and Method thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020150047470A KR101673755B1 (en) 2015-04-03 2015-04-03 System for interoperation network of IoT and network of Zigbee based DDS and Method thereof

Publications (2)

Publication Number Publication Date
KR20160119370A true KR20160119370A (en) 2016-10-13
KR101673755B1 KR101673755B1 (en) 2016-11-08

Family

ID=57173952

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020150047470A KR101673755B1 (en) 2015-04-03 2015-04-03 System for interoperation network of IoT and network of Zigbee based DDS and Method thereof

Country Status (1)

Country Link
KR (1) KR101673755B1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20180072918A (en) * 2016-12-21 2018-07-02 경북대학교 산학협력단 Apparatus and method for transmitting data, and iot system employing the same
WO2019129089A1 (en) 2017-12-26 2019-07-04 Sengled Co., Ltd. Method and apparatus for monitoring zigbee node network status

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140122966A (en) * 2013-04-11 2014-10-21 한국전자통신연구원 Apparatus and method for sharing topic between autonomic computing devices

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140122966A (en) * 2013-04-11 2014-10-21 한국전자통신연구원 Apparatus and method for sharing topic between autonomic computing devices

Non-Patent Citations (5)

* Cited by examiner, † Cited by third party
Title
1. Lili Wu, J. Riihijarvi J. and P. Mahonen, "A Modular Wireless Sensor Network Gateway Design", Communications and Networking in China, CHINACOM ’07. Second International Conference, pp.882-886, 2007.
2. Q. Zhu, R. Wang, Q. Chen, Y. Liu and W. Qin, "IOT Gateway: Bridging Wireless Sensor Networks into Internet of Things", Embedded and Ubiquitous Computing, 2010 IEEE/IFIP 8th International Conference, pp.347-352, 2010.
3. K. A. Emara, M. Abdeen and M. Hashem, "A Gateway-based Framework for Transparent Interconnection WSN and IP Network", In EUROCON ’09, pp.1775-1780, 2009.
4. D. Bimschas, H. Hellbruck, R. Mietz, D. Pfisterer, K. Romer and T. Teubler, "Middleware for Smart Gateways Connecting Sensornets to the Internet", In Proceedings of the 5th International Workshop on Middleware Tools, Services and Run-time Support for Sensor Networks (MidSens ’10), pp.8-14, 2010.
백문기, 임형준, 송찬호, 이규철, "사물 인터넷에서 지그비 네트워크를 위한 어댑터 설계", 한국정보과학회 학술발표논문집, pp.355-356 (2013.06.)* *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20180072918A (en) * 2016-12-21 2018-07-02 경북대학교 산학협력단 Apparatus and method for transmitting data, and iot system employing the same
WO2019129089A1 (en) 2017-12-26 2019-07-04 Sengled Co., Ltd. Method and apparatus for monitoring zigbee node network status
EP3732922A4 (en) * 2017-12-26 2021-08-25 Sengled Co., Ltd. Method and apparatus for monitoring zigbee node network status

Also Published As

Publication number Publication date
KR101673755B1 (en) 2016-11-08

Similar Documents

Publication Publication Date Title
Wang et al. A lightweight XMPP publish/subscribe scheme for resource-constrained IoT devices
WO2022262465A1 (en) Opc ua-based centralized user configuration method and system for time sensitive network
Hussain Internet of Things: challenges and research opportunities
Sheng et al. Lightweight management of resource-constrained sensor devices in internet of things
Kim et al. M2M service platforms: Survey, issues, and enabling technologies
Huang et al. An SDN_based management framework for IoT devices
JP6514315B2 (en) Resource and attribute management in machine-to-machine network
Han et al. Semantic service provisioning for smart objects: Integrating IoT applications into the web
De Poorter et al. Enabling direct connectivity between heterogeneous objects in the internet of things through a network-service-oriented architecture
Hada et al. EPC based internet of things architecture
FI125252B (en) A method, device, and system for managing a web service
Amadeo et al. Information-centric networking for M2M communications: Design and deployment
Efremov et al. An integrated approach to common problems in the Internet of Things
Azzara et al. Middleware solutions in WSN: The IoT oriented approach in the ICSI project
Yim et al. Description and classification for facilitating interoperability of heterogeneous data/events/services in the Internet of Things
Klauck et al. Chatty things-Making the Internet of Things readily usable for the masses with XMPP
Kovatsch Scalable Web technology for the Internet of Things
Corici et al. OpenMTC: Prototyping Machine Type communication in carrier grade operator networks
US20090198806A1 (en) Data structure for managing sensor network using id of sensor node and method using the same
Sadok et al. A middleware for industry
CN112769602A (en) System and method for unified configuration management of white box switch and network operating system
CN104243198B (en) A kind of network management and system based on network configuration protocol
CN104320347A (en) Method and device for initiatively updating LLDP
Hornsby et al. μXMPP: Lightweight implementation for low power operating system Contiki
KR101673755B1 (en) System for interoperation network of IoT and network of Zigbee based DDS and Method thereof

Legal Events

Date Code Title Description
A201 Request for examination
E902 Notification of reason for refusal
E701 Decision to grant or registration of patent right
GRNT Written decision to grant
FPAY Annual fee payment

Payment date: 20191031

Year of fee payment: 4