KR20080072780A - Gateway and method for transforming a packet using the same - Google Patents

Abstract

A gateway and a method for converting a packet using the same are provided to convert between a zigbee packet and an IP packet each other having different address systems, thereby interoperating a packet transmitted or received between a zigbee network and an IP-USN. A zigbee interface layer unit(310) is connected to a zigbee network(100). An IP(Internet Protocol) interface layer unit(330) is connected to an IP-USN(Internet Protocol-Ubiquitous Sensor Network). An application layer unit(320) converts a zigbee packet provided in the zigbee network via the zigbee interface layer unit into an IP packet and provides the IP packet to the IP interface layer unit, and converts the IP packet provided in the IP-USN via the IP interface layer unit into a zigbee packet and provides the zigbee packet to the zigbee interface layer unit. The zigbee interface layer unit includes a first MAC(Media Access Control)/physical layer(312), a first parsing layer(314), a zigbee network layer(316), and a zigbee application layer(318). The IP interface layer unit includes a second MAC/physical layer(331), a second parsing layer(332), an adaptation layer(333), an IP layer(334), and a TCP(Transmission Control Procedure)/UDP(User Datagram Protocol) layer(335).

Description

GATEWAY AND METHOD FOR TRANSFORMING A PACKET USING THE SAME}

1 is a conceptual diagram illustrating a gateway hierarchy structure according to an embodiment of the present invention.

2 is a diagram illustrating a header format of IPv6 applied to the present invention.

3 shows an example of a data frame format of the first and second MAC / PHY layers shown in FIG. 1.

4 is a diagram illustrating a Zigbee destination mapping table according to an embodiment of the present invention.

5 is a diagram illustrating an IP destination mapping table according to an embodiment of the present invention.

6 is a conceptual diagram illustrating a table reference relationship in a packet conversion process according to an embodiment of the present invention.

7A and 7B are conceptual diagrams illustrating interworking between a user-agent node of a Zigbee network and a service-agent node of an IP-based ubiquitous sensor network (USN).

8A and 8B are conceptual diagrams illustrating interworking between a service-agent node and an IP-based ubiquitous sensor network (USN) node of a Zigbee network.

The present invention relates to a gateway and a packet conversion method using the same, and more particularly, to a gateway for interworking between a Zigbee network and an IP-based ubiquitous sensor network and a packet conversion method using the same.

In general, ZigBee is a wireless communication technology suitable for a home network based on control and sensors, which can be implemented at lower power than Bluetooth, and its manufacturing cost is only one half of Bluetooth.

The Zigbee is based on the IEEE 802.15.4 radio standard. It is designed to meet the needs of networks not provided by Bluetooth or WIPI as a foundation technology of near-field communication of 10 ~ 20m in homes, offices, industrial sites, etc. and ubiquitous computing. . The IEEE has released the 802.15.4 specification, which defines low-cost, low-power wireless PAN technology. Founded to promote industry, such as marketing and product certification, the ZigBee Association is working to further define the network / security layer on the IEEE-defined PHY and MAC. In the IEEE 802.15.4 standard, DSSS modulation is performed in three frequency bands: 868 MHz (BPSK / 1 channel / Europe), 902 to 928 MHz (BPSK / 10 channel / US), and 2.4 GHz (OQPSK / 16 channel / world). It is defined to support the transmission speed of 20 ~ 250 kbps up to 100m. In addition, up to 65,000 nodes can be used by assigning 64 bits to the address.

ZigBee is expected to attract attention as a competitive short-range wireless communication technology for vertical applications such as sensor networks. ZigBee is a technology that combines low-power ZigBee transceivers with sensors (motion, light, pressure, temperature, humidity) to form a large sensor network. Among other things, Zigbee's biggest feature is its ultra-low power consumption. ZigBee's average power consumption during transmission and reception is about 50 mW, which is very low compared to UWB or wireless LAN. In addition, ZigBee's slave devices use power only when there is a call from the master device, which can be used for up to two or three years with a single battery. ZigBee can be used in a variety of applications, including wireless sensors, industrial control, wireless switches, and air conditioning, making it an excellent choice for creating automated sensor networks for a variety of applications including industrial, home, medical, and military.

Ubiquitous computing, on the other hand, is based on the premise that all computers are connected to each other, invisible to the user, can be used anytime, anywhere, and soak into real-world objects and environments and integrate into everyday life.

In addition, ubiquitous network means an information communication network that anyone can use anytime, anywhere without restriction of communication speed, and can distribute all information or content, and by implementation of this, various limitations of existing information communication network or service have It allows the user to freely use the information and communication service away from the system.

Efforts are being made to develop new services using ubiquitous computing and ubiquitous networks, and the importance of related technologies is rapidly increasing. In addition, the ubiquitous computing environment requires a ubiquitous computing environment capable of providing various information services anytime, anywhere by configuring a wireless sensor network with autonomous sensing, low power communication functions, and thousands of node objects.

Many industries, universities, and universities are researching and developing the technologies necessary to provide this environment. For example, the ZigBee Alliance is based on these technologies. Standardization is underway for the Application Framework and Application Profile.

As part of this ubiquitous network, a ubiquitous sensor network (USN) service is proposed that provides extensive scalability and guarantees mobility of sensor nodes, gateways, and sink nodes based on the existing IP infrastructure. For example, an Internet Protocol-Ubiquitous Sensor Network (hereinafter referred to as IP-USN) has been proposed. In relation to the above IP-USN, the IETF 6LowPAN Working Group, an international standardization organization, is in the process of standardization.

Therefore, the technical problem of the present invention has been made in view of the above, an object of the present invention is to provide a gateway for interworking between a Zigbee network and an IP-based ubiquitous sensor network (IP-USN).

Another object of the present invention is to provide a packet conversion method between a Zigbee network using the gateway and an IP-based ubiquitous sensor network.

In order to realize the above object of the present invention, the gateway includes an interface layer unit, an IP interface layer unit, and an application layer unit. The Zigbee interface layer is connected to a Zigbee network. The IP interface layer unit is connected to an IP-based ubiquitous sensor network. The application layer unit converts a Zigbee packet provided from the Zigbee network to an IP packet via the Zigbee interface layer unit and provides the converted IP packet. The application layer unit converts an IP packet provided from the IP-based ubiquitous sensor network into a Zigbee packet through the IP interface layer unit and provides the converted ZigBee packet to the ZigBee interface layer unit.

In order to achieve the above object of the present invention, a packet conversion method according to an embodiment includes (a) an IP packet and a Zigbee address corresponding to a TCP / UDP port number of the IP packet in a ZigBee destination mapping table. Searching for a Zigbee end-point; (b) in step (a), obtaining a destination ZigBee address and a destination endpoint from the ZigBee destination mapping table if the ZigBee address and ZigBee end-point are found; (c) generating a source ZigBee address and a source end-point based on the corresponding IP packet and registering the source ZigBee address and source endpoint in the IP destination mapping table, and transmitting the IP packet converted to the ZigBee address system to the ZigBee network; (d) retrieving an IP address and a TCP / UDP port number corresponding to the ZigBee packet from the IP destination mapping table as the ZigBee packet is provided; And (e) defining the IP address and TCP / UDP port number retrieved in step (d) as a destination IP address and a destination TCP / UDP port number, defining an IP address of the gateway as a source IP address, and a Zigbee destination mapping table. And transmitting the ZigBee packet converted to the IP address system by defining the source TCP / UDP port number retrieved from the IP address.

In order to realize the above object of the present invention, a packet conversion method according to another embodiment provides a service request message to service agents on an IP network as an end-device-binding-request message is provided from a user agent on a Zigbee network. Sending a cast; And as a service response message is provided from any of the service agents, providing an end-device binding response message to the user agent. Here, the IP packet provided from the service agent side is converted into a Zigbee address system and provided to the user agent side, and the Zigbee packet provided from the user agent side is converted into an IP address system and provided to the service agent side. It features.

In order to realize the above object of the present invention, a packet conversion method according to another embodiment provides a service act message to the service agent side as a service request message is provided from a service agent on an IP network, and the service agent information. Holding a; And providing an end-device binding response message to the user agent side as an end-device-binding-request message is provided from a user agent on a Zigbee network. Here, the IP packet provided from the service agent side is converted into a Zigbee address system and provided to the user agent, and the Zigbee packet provided from the user agent side is converted into an IP address system and provided to the service agent side. It features.

According to another aspect of the present invention, a packet conversion method includes multicasting a service request message to service agents on a Zigbee network as a service request message is provided from a user agent on an IP network. ; And as a service matching message is provided from any of the service agents, providing a service response message to the user agent. Here, the ZigBee packet provided by the service agent side is converted into an IP address system and provided to the user agent side, and the IP packet provided by the user agent side is converted into a Zigbee address system and provided to the service agent side. It features.

In accordance with still another aspect of the present invention, there is provided a packet conversion method, comprising: providing a service matching request message to service agents on a Zigbee network; Providing a binding request message to the service agent side as a service matching message is provided from any one of the service agents; Retaining the service agent information as a binding response message is provided according to the response of the binding request message; And as a service request message is provided from a user agent on an IP network, providing a service response message to the user agent side. Here, the ZigBee packet provided by the service agent side is converted into an IP address system and provided to the user agent side, and the IP packet provided by the user agent side is converted into a Zigbee address system and provided to the service agent side. It features.

According to such a gateway and a packet conversion method using the same, by converting ZigBee packets having different address systems and IP packets from each other, packets transmitted and received between different ZigBee networks and IP-based ubiquitous sensor networks can be interlocked.

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

1 is a conceptual diagram illustrating a hierarchical structure of a gateway according to an embodiment of the present invention. In particular, a hierarchical structure of a gateway for interworking a Zigbee network and an IP-USN is shown.

Referring to FIG. 1, the gateway 300 interposed between the ZigBee network 100 and the IP-USN 200 includes a ZigBee interface layer unit 310, an IP interface layer unit 330, and an application layer unit 320. do.

The gateway 300 converts a Zigbee packet provided from the Zigbee network 100 or an IP packet provided from the IP-USN 200 and provides the converted network to the corresponding network.

The Zigbee interface layer 310 has a first MAC / PHY layer 312, a first parsing layer 314, a Zigbee network layer 316, a Zigbee application layer 318, the Zigbee network 100 Connected to communicate.

The IP interface layer unit 320 includes a second MAC / PHY layer 331, a second parsing layer 332, an adaptation layer 333, an IP layer 334, and a TCP / UDP layer 335. It is connected to and communicates with the IP-USN 200.

The first and second MAC / PHY layers 312, 332 are in accordance with the IEEE 802.15.4-2003 standard, and the adaptation layer 333 is the IETF Internet draft (montenegro-lowpan-ipv6-over-802.15.4) The IP layer 334, for example the IPv6 layer, is in accordance with RFC 2460 and related standards. An IPv6 header format applied to the present invention is shown in FIG. 2 below.

2 is a diagram illustrating a header format of IPv6 applied to the present invention. 3 shows an example of a data frame format of the first and second MAC / PHY layers shown in FIG. 1.

Referring to FIG. 2, the IPv6 header format has a size of 10 rows x 32 bits = 40 octets, version, priority, flow level, payload length, next header, hop limit, 128 bits of source address, and 128 bits. Consists of the destination address.

In addition, the frame according to the IEEE 802.15.4-2003 standard is a beacon frame for transmitting beacons in the coordinator, a data frame for transmitting data, a response frame for notifying the other party when the data frame is successfully received, MAC command It is divided into frames.

Referring to FIG. 3, each of the data frames of the first and second MAC / PHY layers 312 and 332 includes a packet format of the PHY layer and a packet format of the MAC layer.

The packet format of the PHY layer includes a preamble sequence, a start of frame delimiter, a frame length, and a MAC layer data unit (MPDU).

The packet format of the MAC layer includes a frame control, a sequence number, an addressing field, a data payload, and a frame check sequence (FCS).

Returning to the description of FIG. 1, the application layer unit 330 converts a ZigBee packet provided from the ZigBee network 100 into an IP packet (a kind of protocol conversion), or an IP provided from the IP-USN 200. Convert the packet to a Zigbee packet. The converted IP packet is delivered to the IP-USN 200 side, and the converted Zigbee packet is delivered to the Zigbee network 100 side.

As shown in FIG. 1, in order for the ZigBee network 100 and the IP-USN 200 to interwork with each other to transmit / receive ZigBee packets or IP packets, the address system of each other is appropriately converted on the gateway 300. Must be delivered. To this end, there are two mapping tables managed on the gateway 300, that is, a Zigbee destination mapping table and an IP destination mapping table.

4 is a diagram illustrating a Zigbee destination mapping table according to an embodiment of the present invention.

1 and 4, the Zigbee destination mapping table 340 includes a Zigbee end-point, a Zigbee address, and a TCP / UDP port number. The Zigbee destination mapping table 340 is used to obtain a Zigbee address and an end-point corresponding to the TCP / UDP port number of the IP packet arriving at the gateway 300.

5 is a diagram illustrating an IP destination mapping table according to an embodiment of the present invention.

1 and 5, the IP destination mapping table 350 includes a TCP / UDP port number, an IP address, a Zigbee end-point, and a Zigbee address.

The IP destination mapping table 350 is used to obtain a corresponding IP address and TCP / UDP port through the Zigbee address and the end-point of the Zigbee packet arriving at the gateway 300.

The Zigbee address is generally a 16-bit address, and one address is assigned to each node provided in the Zigbee network.

The Zigbee end-point has a 1 byte value (1-240) present for identification of a plurality of applications in the Zigbee node. The Zigbee end-point is included in the header of the Zigbee packet.

On the other hand, when an IP node of an IP-USN, for example, an IPv6 network, wishes to transmit an IP packet to a Zigbee network, the IP-USN, for example, recalls a destination TCP / UDP port number of the corresponding IP packet, a corresponding destination Zigbee address, and an endpoint. Registration with the Zigbee Destination Mapping Table must be done in advance.

Conversely, when a ZigBee node of a ZigBee network wishes to send a ZigBee packet via communication with an IP-USN, e.g. an IPv6 network, the ZigBee address and end-point corresponding to the destination IP address and TCP / UDP port number Registration with the IP destination mapping table should be performed in advance.

The registration method of the mapping table may be a manual registration (explicit registration) method or a registration method through a binding process of Zigbee. This information may be used if the information in the mapping table in the opposite direction is generated by packet transmission in the opposite direction.

Next, a series of operations for translating a detailed address on the gateway using the mapping tables will be described with reference to FIG. 4.

6 is a conceptual diagram illustrating a table reference relationship in a packet conversion process according to an embodiment of the present invention.

1 to 6, the Zigbee destination mapping table 340 and the IP destination mapping table 350 included in the gateway 300 are connected to the Zigbee network 100 and also connected to the IP destination mapping table 200. do.

First, a description will be given of a series of operations for converting an IP packet into a Zigbee packet as the IP packet is provided. Next, as a ZigBee packet is provided, a series of operations for converting the ZigBee packet into an IP packet will be described.

<IP packet-> Zigbee packet>

When an IP packet provided in an IP-USN, for example, an IPv6 network, arrives at the gateway 300, in particular, the application layer of the gateway 300, the gateway 300 receives a TCP / UDP port of the arrived IP packet. The Zigbee address and the Zigbee end-point corresponding to the number are retrieved from the Zigbee destination mapping table 340.

If the corresponding Zigbee address and Zigbee end-point pair are not retrieved by the gateway 300, the corresponding IP packet is discarded.

Meanwhile, when the corresponding Zigbee address and the Zigbee end-point are found by the gateway 300, the corresponding IP packet performs a packet conversion process to the Zigbee packet. Important information required in the above packet conversion process is the source / destination Zigbee address and the source / destination end-point.

The destination Zigbee address and the destination end-point may be obtained from the Zigbee destination mapping table 340.

Meanwhile, the source Zigbee address and the source end-point are generated using an IP address and a TCP / UDP port included in the corresponding IP packet. For example, the source Zigbee address and the end-point may be generated by randomly selecting an unused address and endpoint pair among 50,000 or more addresses. The generated source Zigbee address and source end-point are registered in the IP destination mapping table 350 along with the source IP address and TCP / UDP port number. When the packet conversion process is completed, the packet is transmitted to the Zigbee network through the Zigbee Network Service.

<Zigbee Packet-> IP Packet>

Meanwhile, when a Zigbee packet arrives at the gateway 300, the gateway 300 searches for a corresponding IP address and TCP / UDP port number through the destination Zigbee address and the end-point in the IP destination mapping table 350.

If the corresponding IP address and TCP / UDP port number are not retrieved by the gateway 300, the packet is discarded.

Meanwhile, when the corresponding IP address and the TCP / UDP port number are found by the gateway 300, the searched IP address and the TCP / UDP port number are used as the destination IP address and the destination TCP / UDP port number.

The source IP address uses the IP address of the gateway 300.

In order to obtain a source TCP / UDP port, the Zigbee destination mapping table 340 retrieves and uses the TCP / UDP port corresponding to the source Zigbee address and the end-point pair of the Zigbee packet.

If a search result does not appear in the ZigBee destination mapping table 340, a TCP / UDP port number representing a ZigBee address and an end-point is generated and then registered and used in the ZigBee destination mapping table 340. For example, the TCP / UDP port number may be generated through a method of arbitrarily selecting a port not used in the dynamic and / or private port areas 49152 to 65535.

If the destination address of the IP packet or Zigbee packet is a broadcast or multicast address, it is not forwarded to another network. However, the service discovery message may be delivered to another network as an exception. This is to allow natural service discovery and use between the Zigbee network and IP-USN. This service discovery and use is made possible by converting Zigbee binding packets into Service Location Protocol (SLP) packets. The ZigBee binding function is a function that allows a service between a device defined by a profile and a cluster to be dynamically connected and used without defining address information between each other in advance.

7A and 7B are conceptual diagrams illustrating interworking between a user-agent node of a Zigbee network and a service-agent node of an IP-USN. In FIG. 7A and FIG. 7B, a node (or user-agent node) UA to request (or discover) a service on a Zigbee network is disposed at one side of the gateway, and the service is provided on the IP-USN at the other side of the gateway. A node (or service-agent node) SA is disposed.

Referring to FIG. 7A, a case in which the gateway merely serves as a translation will be described.

First, a user-agent node UA existing on a Zigbee network transmits an 'End device bind req' message by broadcasting or unicasting to a gateway GW to search for a node providing a desired service.

The gateway GW receiving the 'End device bind req' message may simply act as a service discovery message translation function or as a directory agent (hereinafter referred to as DA) of the SLP.

If the gateway GW simply performs a service discovery message conversion function, the 'end device bind req' message is converted into an 'SrvRqst' message of the SLP in IP-USN, and then multicasted.

If a service-agent (SA) on the IP-USN receives a 'SrvRqst' message corresponding to its service, it will respond by providing the gateway (GW) through a 'SrvRply' message.

In addition, the gateway (GW) receiving the 'SrvRply' message from the service-agent node (SA) on the IP-USN returns it to the user-agent node (UA) on the ZigBee network as an 'End device bind rsp' message. As a result, the binding process between the gateway GW and the user-agent node UA is completed. Thereafter, the user-agent node UA and the service-agent node SA may communicate with each other in a TCP / UDP from the service-agent node SA to the gateway GW and in a Zigbee packet thereafter.

Referring to FIG. 7B, a case in which the gateway plays a directory-agent role in addition to the translation role will be described.

First, the gateway (GW), which performs the role of the directory agent node (DA), exchanges the 'SrvReq' message and the 'SrvAck' message of the SLP from the service-agent node (SA) in advance, and the service-agent node (SA). Has information about In this case, when the 'end device bind req' message is received from the user-agent node UA, the binding process is completed by returning the 'end device bind rsp' message to the user-agent node UA.

On the other hand, if there is a user-agent node (UA) on the IP-USN and a service-agent node (SA) on the Zigbee network, the user-agent node (UA) on the IP-USN is uni- versed to the gateway GW. It will attempt to find a service-agent node (SA) by sending a 'Srv Rqst' message, either cast or multicast.

8A and 8B are conceptual diagrams illustrating interworking between a service-agent node and an IP-USN node of a Zigbee network. In particular, FIG. 8A illustrates the case where the gateway GW serves only as a translation, and FIG. 8B illustrates the case where the gateway GW also serves as a directory-agent.

Referring to FIG. 8A, if a gateway (GW) that merely performs a message conversion function receives a 'SrvRqst' message from a user-agent node (UA), the gateway (GW) is a service-agent node (SA) on a Zigbee network. It will broadcast a 'Match Desc Req' message to retrieve the.

If any node on the Zigbee network receives a 'Match Desc Req' message that matches the service it provides, it responds to the gateway GW as a 'Match Desc Rsp' message.

When the gateway GW receives the 'Match Desc Rsp' response, the gateway GW returns a 'SrvRqst' message to the user-agent node UA on the IP-USN and simultaneously to the corresponding node, that is, the service-agent node SA. The binding process is performed by sending 'Bind Req' message.

Here, Zigbee binding is a function that logically connects end-points on one or more devices that meet specific ZigBee profile and ZigBee Cluster Identifier conditions to source and destination pairs. The ZigBee profiles are a bundle of device descriptions, which are grouped together to form a cooperative application. For example, a node with a temperature sensor and a node with a fan are tied together to form a heating profile.

The Zigbee cluster refers to a functional grouping such as attribute values or messages distinguished within each profile. The Zigbee Cluster Identifier is a unique identifier of the cluster and is used as an identifier of the binding table.

At the end of the above binding process, the user-agent node UA and the service-agent node SA on the Zigbee network may exchange packets with the node on the IP-USN as if they were bound.

Likewise, a node on an IP-USN can send and receive packets with a node on a Zigbee network as if the TCP / UDP port was open.

In addition, the address information obtained in the service discovery message exchange process of the Zigbee network with the SLP is recorded in the Zigbee destination mapping table and the IP destination mapping table to be used for subsequent packet transmission.

Referring to FIG. 8B, if the gateway GW also serves as the directory-agent node DA and already has the information of the service-agent, the information is simply transferred to the user-agent node UA through the 'SrvRqst' message. You can finalize the binding process by returning to.

As described above, according to the present invention, by converting ZigBee packets having different address systems and IP packets from each other, packets transmitted and received between different ZigBee networks and IP-based ubiquitous sensor networks can be interworked.

Although described above with reference to the embodiments, those skilled in the art can be variously modified and changed within the scope of the invention without departing from the spirit and scope of the invention described in the claims below. I can understand.

Claims (14)

A Zigbee interface layer unit connected to a Zigbee network; An IP interface layer unit connected to the IP-based ubiquitous sensor network; And Converts a ZigBee packet provided from the ZigBee network into an IP packet via the ZigBee interface layer unit, and provides the IP packet from the ZIB interface layer unit And an application layer unit for converting an IP packet provided from the IP-based ubiquitous sensor network into a Zigbee packet and providing it to the Zigbee interface layer via the IP interface layer unit. The gateway of claim 1, wherein the Zigbee interface layer unit has a first MAC / physical layer, a first parsing layer, a Zigbee network layer, and a Zigbee application layer. The gateway of claim 1, wherein the IP interface layer unit has a second MAC / physical layer, a second parsing layer, an adaptation layer, an IP layer, and a TCP / UDP layer. The method of claim 1, further comprising a Zigbee network destination mapping table, And the Zigbee destination mapping table has a Zigbee end-point, a Zigbee address, and a TCP / UDP port number. Further comprising an IP destination mapping table, And the IP destination mapping table has a TCP / UDP port number, an IP address, a Zigbee end-point, and a Zigbee address. (a) retrieving a ZigBee address and a ZigBee end-point corresponding to the TCP / UDP port number of the IP packet in the ZigBee destination mapping table as the IP packet is provided; (b) in step (a), obtaining a destination ZigBee address and a destination endpoint from the ZigBee destination mapping table if the ZigBee address and ZigBee end-point are found; (c) generating a source ZigBee address and a source end-point based on the corresponding IP packet and registering the source ZigBee address and source endpoint in the IP destination mapping table, and transmitting the IP packet converted to the ZigBee address system to the ZigBee network; (d) retrieving an IP address and a TCP / UDP port number corresponding to the ZigBee packet from the IP destination mapping table as the ZigBee packet is provided; And (e) define the IP address and the TCP / UDP port number retrieved in step (d) as the destination IP address and the destination TCP / UDP port number, define the IP address of the gateway as the source IP address, and in the Zigbee destination mapping table Transmitting a ZigBee packet converted to an IP address system by defining the retrieved source TCP / UDP port number to an IP-based ubiquitous sensor network (IP-USN). 7. The method of claim 6, further comprising, in step (a), discarding the IP packet if the corresponding ZigBee address and ZigBee end-point are not retrieved. 7. The method of claim 6, further comprising discarding the ZigBee packet if the corresponding IP address and the TCP / UDP port number are not found in the step (d). 7. The method of claim 6, wherein the source TCP / UDP port number corresponds to a TCP / UDP port corresponding to a source ZigBee address and an end-point pair of the ZigBee packet retrieved from the destination mapping table. The method according to claim 6, wherein when the TCP / UDP port is not detected in the Zigbee destination mapping table, a TCP / UDP port number representing a Zigbee address and an endpoint is generated and used as the source TCP / UDP port number. Packet conversion method further comprising the step. Multicast sending a service request message to service agents on an IP-USN as an end-device-binding-request message is provided from a user agent on a Zigbee network; And As a service response message is provided from one of the service agents, providing an end-device binding response message to the user agent, Converts the IP packet provided by the service agent into a Zigbee address system and provides the same to the user agent; And converting a ZigBee packet provided by the user agent into an IP address system and providing the same to the service agent. As a service request message is provided from a service agent on IP-USN, providing a service act message to the service agent side and retaining the service agent information; And Providing an end-device binding response message to the user agent side as an end-device-binding-request message is provided from a user agent on a Zigbee network, Converts the IP packet provided by the service agent into a Zigbee address system and provides the same to the user agent; And converting a ZigBee packet provided by the user agent into an IP address system and providing the same to the service agent. Multicast sending a service request message to service agents on a Zigbee network as a service request message is provided from a user agent on an IP-USN; And Providing a service response message to the user agent as a service matching message is provided from any of the service agents, Converts a Zigbee packet provided by the service agent to an IP address system and provides the same to the user agent; And converting an IP packet provided from the user agent into a Zigbee address system and providing the same to the service agent. Providing a service matching request message to service agents on a Zigbee network; Providing a binding request message to the service agent side as a service matching message is provided from any one of the service agents; Retaining the service agent information as a binding response message is provided according to the response of the binding request message; And As a service request message is provided from a user agent on an IP-USN, providing a service response message to the user agent side; Converts a Zigbee packet provided by the service agent to an IP address system and provides the same to the user agent; And converting an IP packet provided from the user agent into a Zigbee address system and providing the same to the service agent.

Images