KR20170119098A - Apparatus and method for bluetooth communication - Google Patents

Abstract

A method and apparatus for Bluetooth communication are provided. The Bluetooth device communicates with other external devices through a gateway function provided by the gateway. In the protocol stack of a Bluetooth device, the CoAP layer is directly above the L2CAP layer. Also, in the protocol stack for the Bluetooth communication of the gateway, the CoAP layer is directly above the L2CAP layer. As part of the protocol stack is omitted, Bluetooth devices and gateways provide highly efficient communications.

Description

[0001] APPARATUS AND METHOD FOR BLUETOOTH COMMUNICATION [0002]

The following embodiments relate to a method and apparatus for Bluetooth communication, and more particularly to a method and apparatus having a simplified protocol stack for Bluetooth communication for the Internet of Things.

Bluetooth technology is a short-range wireless communication technology that provides communication with peripheral devices within 10 meters. In recent years, a Bluetooth low energy (BLE) standard has been developed to support various sensors.

As a Bluetooth standard, a profile specification is established for each type of Bluetooth device and service. However, the development of profile specifications is not keeping pace with the speed at which Bluetooth devices are newly developed. Accordingly, the manufacturer of the Bluetooth device provides an upper layer communication standard or an application programming interface (API).

This situation makes interworking between different products or interworking between products of different manufacturers difficult. For example, a Bluetooth device, such as a smartphone, must search for a variety of other Bluetooth devices and interoperate with other Bluetooth devices searched. If this interlocking is performed only through a program (e.g., an App) created by the manufacturer of the Bluetooth device, there is a problem in compatibility and interoperability.

Meanwhile, as the various objects connected to the Internet are connected to the Internet and entered into the Internet of Things (IoT) era, a technical standard has been established for a method of enabling the Bluetooth devices to interoperate with the Internet .

These technical standards include: 1) how a Bluetooth device supports a Representational State Transfer (REST) API; 2) how a Bluetooth device is connected to the Internet via a HyperText Transfer Protocol (HTTP) proxy; 3) IPv6 over low power wireless personal area networks (6LoWPAN), Internet Protocol version 6 (IPv6) and User Datagram Protocol (UDP) There is an Internet Protocol Support Profile Specification (IPSP) which is implemented as an upper layer of a L2CAP (Link Layer Control and Adaptation Protocol). Below we briefly discuss the three methods.

1) How does a Bluetooth device support the REST API?

A Bluetooth Internet gateway receives a request from a client over the Internet. The Bluetooth Internet gateway converts the request to an attribute protocol (ATT) and / or a generic attribute profile (GATT) of the Bluetooth device. Communication between the Bluetooth device and the client is performed through the above conversion.

This method uses the existing Bluetooth stack. As the existing Bluetooth stack is used intact, this method has the problems of compatibility and interoperability described above. Accordingly, the Bluetooth Internet gateway should be able to recognize the internal properties of various Bluetooth devices and be able to interoperate with various Bluetooth devices having different internal attributes. In addition, the external server must also know the internal properties of the Bluetooth device in advance.

Since this method is not a standard for the application layer, it is difficult to recognize the collected data when this method is used.

2) How a Bluetooth device accesses the Internet through an HTTP proxy

In this way, the Bluetooth stack between the Bluetooth Proxy Service (HPS) client and the Bluetooth HPS server is used as it is. The Bluetooth HPS server functions as a gateway. The Bluetooth HPS server translates the Bluetooth protocol into an internet protocol such as HTTP through its own mapping. This conversion enables communication between the Bluetooth HPS client and the remote HTTP server.

In this way, the Bluetooth HPS server performing the gateway function must know all the properties of the Bluetooth device. Therefore, when such a scheme is used, interoperability and compatibility in communication may be deteriorated.

3) How to use IPSP.

The method of using IPSP implements 6LowPAN, IPv6, UDP, TCP and application layer stack on L2CAP without using Bluetooth ATT and GATT. Communication is achieved through this implementation. In this method, since the Internet protocol is directly mounted on the Bluetooth node, high compatibility and interoperability can be ensured.

However, according to this method, the protocol stack of TCP, IP and 6LoWPAN is implemented in the Bluetooth node as it is. Therefore, when this method is used, memory problems, performance problems, and Bluetooth network efficiency problems arise.

Korean Patent Publication No. 2014-0027503 and Korean Patent No. 10-1397744 have been proposed in connection with Bluetooth.

One embodiment can provide a communication method that can be applied to various current devices and future devices by applying an international standard protocol to Bluetooth.

One embodiment may provide an apparatus and method for providing highly efficient communication by omitting some of the protocol stacks.

In one aspect, there is provided an apparatus comprising: a processing unit for performing at least one program; And a communication unit for performing Bluetooth communication, wherein the at least one program includes a code of a CoAP layer and a code of an L2CAP layer, and the CoAP layer is a layer immediately above the L2CAP layer.

In the Bluetooth device, the IP layer, the UDP layer, and the 6LoWPAN layer may be excluded.

The at least one program may include a CoAP support profile.

The CoAP support profile may allow the Bluetooth device to search through the GATT and ATT to support the function of the CoAP.

The Bluetooth device can obtain information about the gateway by broadcasting a broadcast message including a CoAP GET message and receiving a response message corresponding to the broadcast message from the gateway.

The Bluetooth device observes a broadcast message and may discover a gateway that broadcasts the broadcast message upon receiving the broadcast message.

The Bluetooth device may transmit to the gateway a data message including information on the Bluetooth device and a resource path of the Bluetooth device to register the Bluetooth device in the gateway, From the gateway.

The Bluetooth device can register the resource of the Bluetooth device with the gateway using the path.

On another side, registering the Bluetooth device with a gateway, the Bluetooth device being performed by a Bluetooth device; And performing a communication through a gateway function provided by the gateway, wherein the protocol stack of the Bluetooth device includes a CoAP layer and an L2CAP layer, and the CoAP layer is a layer directly above the L2CAP layer Method is provided.

The communication method may further include registering the resource of the Bluetooth device in the gateway.

A processing unit for executing at least one program on another side; And a communication unit for performing Bluetooth communication, wherein the at least one program includes a code of an MQTT layer and a code of an L2CAP layer, and the MQTT layer is a layer immediately above the L2CAP layer.

A processing unit for executing at least one program on another side; A first communication unit for Bluetooth communication; And a second communication unit for interworking with the Internet, wherein the at least one program includes a code for a first communication unit, the code for the first communication unit includes a code of a CoAP layer and a code of an L2CAP layer, The CoAP layer is provided as a layer directly above the L2CAP layer.

The at least one program may comprise a proxy module.

The proxy module may be an upper layer of the CoAP layer.

The proxy module may enable communication between devices connected through the Bluetooth device and the second communication unit by mapping an address of a Bluetooth device connected through the first communication unit to a URI-path inside the gateway.

The first communication unit may receive a CoAP request message from the Bluetooth device.

The processing unit may remove the URI-host and the URI-port from the CoAP request message, and may set an IP header and a UDP header in the request message.

The second communication unit may forward the request message in which the IP header and the UDP header are set to an external device.

The second communication unit may receive a CoAP request message from an external device.

The processing unit may remove URI-host, URI-port, URI-path prefix, URI-path Bluetooth device identifier, IP header, and UDP header from the CoAP request message.

The first communication unit may transmit a request message to the Bluetooth device in which the URI-host, the URI-port, the prefix, the Bluetooth device identifier, the IP header, and the UDP header are removed.

The gateway can detect the Bluetooth device by broadcasting a broadcast message including a CoAP Ping request message and receiving a CoAP Ping response message corresponding to the CoAP Ping request message from the Bluetooth device.

The gateway can observe the broadcast message.

Upon receiving the broadcast message including the virtual CoAP Ping response message, the gateway may discover a Bluetooth device that broadcasts the broadcast message.

The gateway can transmit a connection request message to the Bluetooth device, receive a response message including the path of the resource of the Bluetooth device from the Bluetooth device, send a message containing the route to the Bluetooth device And may receive a response message from the Bluetooth device that includes information about the path.

On another side, searching for a Bluetooth device, performed by a gateway; And providing a gateway function to the Bluetooth device, wherein a protocol stack for Bluetooth communication of the gateway includes a CoAP layer and an L2CAP layer, and the CoAP layer is a communication method that is a layer immediately above the L2CAP layer do.

The communication method may further include confirming a resource of the Bluetooth device.

A processing unit for executing at least one program on another side; A first communication unit for Bluetooth communication; And a second communication unit for interworking with the Internet, wherein the at least one program includes a code for a first communication unit, the code for the first communication unit includes a code of an MQTT layer and a code of an L2CAP layer, The MQTT layer is provided with a gateway which is a layer immediately above the L2CAP layer.

By applying the international standard protocol to Bluetooth, a communication method that can be applied to various current devices and future devices is provided.

An apparatus and method for providing highly efficient communication by omitting some of the protocol stacks are provided.

1 illustrates a system for communicating using Bluetooth according to one embodiment.
2 is a block diagram of a Bluetooth device according to an exemplary embodiment of the present invention.
3 is a structural diagram of a gateway according to an embodiment.
4 illustrates a protocol structure of a Bluetooth device according to an exemplary embodiment.
5 shows a protocol structure of a gateway according to an embodiment.
6 illustrates a structure of communication between a Bluetooth device and a gateway according to an embodiment.
7 is a flowchart of a communication method of a Bluetooth device according to an embodiment.
8 is a flowchart of a gateway communication method according to an embodiment.
9 illustrates communication using a CoAP between Bluetooth devices according to an example.
10 is a flowchart of a search method of a Bluetooth device supporting CoAP using broadcast according to an example.
11 is a flowchart of a search method of a Bluetooth device supporting CoAP using observation according to an example.
12 is a flowchart of a method of searching for a resource of a Bluetooth device according to an example.
13 is a flowchart of a method of processing a request from an external device of a gateway according to an example.
14 is a flowchart of a method of processing a request from an external device of a gateway according to an example.
15 is a flowchart of a gateway search method according to an example.
16 is a flowchart of a search method of a gateway supporting CoAP using observation according to an example.
17 is a flowchart of a method of registering a Bluetooth device according to an example.
18 is a flowchart of a method of registering a resource of a Bluetooth device according to an example.
19 is a structural diagram of a Bluetooth device according to an example.
20 is a structural diagram of a gateway according to an example.
21 illustrates a structure of communication between a Bluetooth device and a gateway according to an embodiment.
Figure 22 shows the format of the advertising channel frame according to an example.
23 shows a data channel frame format according to an example.

The following detailed description of exemplary embodiments refers to the accompanying drawings, which illustrate, by way of illustration, specific embodiments. These embodiments are described in sufficient detail to enable those skilled in the art to practice the embodiments. It should be understood that the various embodiments are different, but need not be mutually exclusive. For example, certain features, structures, and characteristics described herein may be implemented in other embodiments without departing from the spirit and scope of the invention in connection with an embodiment. It is also to be understood that the location or arrangement of the individual components within each disclosed embodiment may be varied without departing from the spirit and scope of the embodiments. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the exemplary embodiments is to be limited only by the appended claims, along with the full scope of equivalents to which such claims are entitled, if properly explained.

In the drawings, like reference numerals refer to the same or similar functions throughout the several views. The shape and size of the elements in the figures may be exaggerated for clarity.

The terms used in the examples are intended to illustrate the embodiments and are not intended to limit the invention. In the examples, the singular includes the plural unless otherwise stated in the specification. It is noted that the terms "comprises" and / or "comprising" used in the specification are intended to be inclusive in a manner similar to the components, steps, operations, and / And that additional configurations may be encompassed within the scope of the embodiments of the exemplary embodiments or the technical ideas of the exemplary embodiments. When it is mentioned that a component is "connected" or "connected" to another component, the two components may be directly connected or connected to each other, It is to be understood that other components may be present in the middle of the components.

The terms first and second, etc. may be used to describe various components, but the components should not be limited by the terms above. The above terms are used to distinguish one component from another. For example, without departing from the scope of the right, 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.

In addition, the components shown in the embodiments are shown independently to represent different characteristic functions, which does not mean that each component is composed of separate hardware or one software constituent unit. That is, each component is listed as each component for convenience of explanation. For example, at least two of the components may be combined into a single component. Also, one component can be divided into a plurality of components. The integrated embodiments and the separate embodiments of each of these components are also included in the scope of the right without departing from the essence.

Also, some components are not essential components to perform essential functions, but may be optional components only to improve performance. Embodiments may be implemented only with components that are essential to implementing the essentials of the embodiments, and structures within which the optional components are excluded, such as, for example, components used only for performance enhancement, are also included in the scope of the right.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings in order to facilitate embodiments of the present invention by those skilled in the art. In the following description of the embodiments, detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present disclosure rather unclear.

The existing Bluetooth standard established a profile standard for each Bluetooth device and made it conform to the profile standard. However, in the Internet world of things, the rate of standardization has not been able to keep pace with the speed of new product launches.

Due to the gap between the enactment of standards and the launch of new products, interoperability problems between products of a company have arisen. In addition, it has been difficult to develop gateways and applications capable of accommodating various devices.

Therefore, the following embodiments propose a protocol structure for ensuring compatibility to accommodate various Bluetooth-based Internet devices to be developed in the future. In addition, the following embodiments can solve the redundancy problem of function, such as message overhead, security and retransmission, which occurs when a conventional Internet protocol is implemented on a Bluetooth node as it is, thereby securing efficiency.

The following embodiments also propose a protocol structure that enables a Bluetooth device to efficiently connect to the Internet of things according to the standard.

1 illustrates a system for communicating using Bluetooth according to one embodiment.

The system 100 may include a Bluetooth device 110 and a gateway 120. The Bluetooth device 110 may be plural.

The Bluetooth device 110 can support the object Internet. The protocol structure of the Bluetooth device 110 may include a Bluetooth physical layer, a Bluetooth logical layer, an L2CAP layer, a Constrained Application Protocol (CoAP) layer, and an application layer.

The Internet networking of the Bluetooth device 110 may be accomplished through a mapping between a Uniform Resource Identifier (URI) path of the CoAP and a Bluetooth device. The process of this mapping can be performed by the gateway 120. [

The gateway 120 may communicate with the Bluetooth device 110 via Bluetooth communication. In addition, the gateway 120 can communicate with other external devices via the Internet.

2 is a block diagram of a Bluetooth device according to an exemplary embodiment of the present invention.

The Bluetooth device 110 may include a processing unit 210, a communication unit 220, and a storage unit 230.

The processing unit 210 may process a task required for the operation of the Bluetooth device 110. [ For example, the processing unit 210 may be at least one processor. The processing unit 210 may execute the code of the operation or step of the processing unit 210 described in the embodiments

The communication unit 220 may receive data or information required for the operation of the Bluetooth device 110 and may transmit data or information required for the operation of the Bluetooth device 110. [ The communication unit 220 can transmit data to other devices in the network and can receive data from other devices. For example, the communication unit 220 may be a network chip for Bluetooth communication or a component for Bluetooth communication.

The storage unit 230 may store data required for operation of the Bluetooth device 110. [ For example, the storage unit 230 may be a memory. The storage unit 230 may include a built-in storage medium such as a RAM and a flash memory, and may include a removable storage medium such as a memory card or the like.

The storage unit 230 may store at least one program. The processing unit 210 may execute at least one program. The processing unit 210 can read the code of at least one program from the storage unit 230 and execute the read code.

At least one program may be a program for Bluetooth communication.

The communication unit 220 can perform Bluetooth communication. The communication unit 220 can transmit data to another device via Bluetooth communication and can receive data from another device.

Operations, functions, and characteristics of the processing unit 210, the communication unit 220, and the storage unit 230 of the Bluetooth device 110 will be described in detail below with reference to embodiments.

3 is a structural diagram of a gateway according to an embodiment.

The gateway 120 may include a processing unit 310, a first communication unit 320, a second communication unit 330, and a storage unit 340.

The processing unit 310 can process a job required for the operation of the gateway 120. [ For example, the processing unit 310 may be at least one processor. The processing unit 310 may execute the code of the operation or step of the processing unit 310 described in the embodiments

The first communication unit 320 and the second communication unit 330 may receive data or information required for the operation of the gateway 120 and may transmit data or information required for the operation of the gateway 120 . The first communication unit 320 and the second communication unit 330 can transmit data to other devices in the network and can receive data from other devices. For example, each of the first communication unit 320 and the second communication unit 330 may be a network chip or a port.

The storage unit 340 may store data required for operation of the gateway 120. [ For example, the storage unit 340 may be a memory. The storage unit 340 may include a built-in storage medium such as a RAM and a flash memory, and may include a removable storage medium such as a memory card or the like.

The storage unit 340 may store at least one program. The processing unit 310 may execute at least one program. The processing unit 310 can read the code of at least one program from the storage unit 340 and execute the read code.

The first communication unit 320 may be a Bluetooth interface for Bluetooth communication. For example, the first communication unit 320 may be a Bluetooth communication chip.

The second communication unit 330 may be an Internet interface for interworking with the Internet. For example, the second communication unit 330 may be a Wi-Fi chip or an Ethernet chip.

The first communication unit 320 may be used for communication with the Bluetooth device 110. [ The second communication unit 330 may be used to provide a gateway function for communication between the Bluetooth device 110 and another device.

The operation, functions, and characteristics of the processing unit 310, the first communication unit 320, the second communication unit 330, and the storage unit 340 of the gateway 120 will be described in detail below with reference to embodiments.

4 illustrates a protocol structure of a Bluetooth device according to an exemplary embodiment.

The protocol structure of the Bluetooth device 110 may be classified into a controller and a host. For example, the controller corresponds to the communication unit 220, and the host can correspond to the processing unit 210. [ Alternatively, the host may correspond to a portion of at least one program executed by the processing unit 210. [

The host controller interface may be an interface for the processing unit 210 to control the communication unit 220.

The lowest layer of the protocol structure may be the physical layer. The next layer may be a link (or a data link) layer. The next layer may be the host controller interface.

The next layer may be L2CAP. The ATT layer, the GATT, the Generic Access Profile (GAP), and the CoAP Support Profile (CSP) may be the upper layers of the L2CAP layer. The CoAP may be an upper layer of L2CAP. The application may be an upper layer of the CoAP.

At least one program performed by the processing unit 210 may include a host-initiating interface layer, an L2CAP layer, a CoAP layer, and an application layer. At least one program performed by the processing unit 210 may include an ATT layer, a GATT layer, a GAP layer, and a CSP layer. For example, the at least one program may include code of a host controller interface layer, code of an L2CAP layer, code of a CoAP layer, and code of an application layer. In addition, the at least one program may include code of an ATT layer, code of a GATT layer, code of a GAP layer, and code of a CSP layer.

In the Bluetooth device 110, the Internet Engineering Task Force (IETF) CoAP layer may be directly above the L2CAP layer.

In the Bluetooth device 110 and / or the protocol structure of at least one program, the IP layer, the UDP layer and the 6LoWPAN layer may be excluded.

The L2CAP layer, the host controller interface layer, the link layer, and the physical layer, which are the following layers of the CoAP layer, can correspond to the BLE module. In other words, in the Bluetooth device 110, the CoAP layer may be directly above the BLE.

The IETF CoAP may be a protocol designed to operate above the UDP layer for low-volume handheld devices.

The L2CAP layer can transmit data in the form of a datagram. In addition, the L2CAP layer can identify the node, send the message to the node, and receive the message from the node.

That is to say, although there is no IP layer, UDP layer and 6LoWPAN layer, CoAP can operate directly above the L2CAP layer. Through this operation, the Bluetooth device 110 can use standard object Internet protocol while enabling efficient communication.

A terminal such as the gateway 120 or a smart phone can communicate with the Bluetooth device 110 using the CoAP standard. Thus, interworking between the Bluetooth device 110 and various other Bluetooth devices may be possible.

The CoAP layer may include at least a part of the CoAP client function and the CoAP server function. The CoAP client function may include the ability to send a message of a CoAP request. The CoAP server function may include a function of receiving a CoAP request and a function of transmitting a message of a response to a CoAP request.

The CSP can be configured to detect that the Bluetooth device 100 supports the CoAP function through the GATT and ATT.

GAP, GATT, ATT and L2CAP can correspond to GAP, GATT, ATT and L2CAP of the existing Bluetooth stack respectively.

If Bluetooth device 100 does not need to communicate with other Bluetooth devices that do not support CoAP, CSP, GAP, GATT, and ATT may all be omitted. In this case, the Bluetooth device 110 may be required to search another Bluetooth device using only the CoAP and the L2CAP, and to find the properties of other Bluetooth devices searched.

5 shows a protocol structure of a gateway according to an embodiment.

The protocol structure of the gateway 120 may be classified into the protocol structure of the first communication unit 320 and the protocol structure of the second communication unit 330. The protocol structure of the first communication unit 320 side is shown on the left side and the protocol structure of the second communication unit 330 side is shown on the right side.

The at least one program may include a code for the first communication unit 320 used for the first communication unit 320 and a code for the second communication unit used for the second communication unit 330. [

First, the protocol structure of the first communication unit 320 will be described.

The lowest layer of the protocol structure of the first communication unit 320 may be BLE. The BLE may include a physical layer, a link layer, a host controller interface layer, and an L2CAP. The description given above with reference to FIG. 4 can be applied to the physical layer, the link layer, the host controller interface layer and the L2CAP.

The CoAP may be an upper layer of L2CAP.

The lower layer of L2CAP may be a BLE module as shown. Alternatively, the BLE module may be replaced by a traditional Bluetooth physical layer and a logical layer. For example, the lower layer of the L2CAP may be a traditional Bluetooth physical layer and a logical layer.

At least one program executed by the processing unit 310 may include a BLE module for the first communication unit 320, an L2CAP layer, and a CoAP layer. For example, the code for the first communication unit 320 performed by the processing unit 310 may include a code of the BLE module, a code of the L2CAP layer, and a code of the CoAP layer.

In the protocol structure of the first communication unit 320 side of the gateway 120, the IETF CoAP layer may be directly above the L2CAP layer.

In the protocol structure of the first communication unit 320 of the gateway 120, the IP layer, the UDP layer, and the 6LoWPAN layer may be excluded.

Next, the protocol structure of the second communication unit 330 will be described.

The protocol structure of the second communication unit 330 may correspond to a typical TCP / IP (Internet Protocol) stack.

The lowest layer of the protocol structure of the second communication unit 330 may be WiFi and / or Ethernet. WiFi and / or Ethernet may refer to the physical and link layers for WiFi and / or Ethernet communications.

The IP may be a higher layer of WiFi and / or Ethernet.

UDP can be the upper layer of IP.

The CoAP and / or HTTP may be an upper layer of UDP.

At least one program may include a proxy module. The proxy module may be a CoAP layer of the protocol structure of the first communication unit 320 and a CoAP layer of the protocol structure of the second communication unit 330 and / or an upper layer of the HTTP layer.

6 illustrates a structure of communication between a Bluetooth device and a gateway according to an embodiment.

In Fig. 6, a Bluetooth device 110, a gateway 120, and an external device 610 are shown.

The Bluetooth device 110 may be a Bluetooth node. The external device 610 may be an external Internet node.

The external device 610 may be a matter Internet server. For example, the protocol structure of the external device 610 may include WiFi and / or Ethernet, IP, UDP and / or TCP, CoAP and an application layer.

The communication unit 220 of the Bluetooth device 110 and the first communication unit 320 of the gateway 120 can communicate with each other through Bluetooth communication. The second communication unit 330 and the external device 610 of the gateway 120 can communicate with each other through a wired / wireless network

The proxy module of the gateway 120 may manage the mapping between the Bluetooth device 110 and the URI-path within the gateway 120.

The proxy module of the gateway 120 maps the address of the Bluetooth device 110 connected through the first communication unit 320 to the URI path of the gateway 120 to thereby transmit the Bluetooth device 110 and the second communication unit 330 Thereby enabling communication between the external devices 610 connected thereto.

When the Bluetooth device 110 transmits a request to the external device 610, the Bluetooth device 110 may use the option of URI-host in the CoAP message and the option of URI-port. The processing unit 210 of the Bluetooth device 110 may generate a request message of the CoAP including an option of the URI-host and an option of the URI-port. The communication unit 220 of the Bluetooth device 110 may transmit a CoAP request message to the gateway 120. [

The first communication unit 320 of the gateway 120 may receive a request message of the CoAP including the option of the URI-host and the option of the URI-port from the Bluetooth device 110. The processing unit 310 of the gateway 120 may remove the URI-host and the URI-port from the CoAP request message, and may set the IP header and the UDP header in the request message. The second communication unit 330 of the gateway 120 may forward the request message with the IP header and the UDP header set to the external device 610.

The external device 610 may send a response message to the request message to the gateway 120. The second communication unit 330 of the gateway 120 may receive a response message to the request message. The first communication unit 320 of the gateway 120 may transmit a response message to the Bluetooth device 110. [ The communication unit 220 of the Bluetooth device 110 may receive a response message from the gateway 120. [ When the processing unit 310 of the gateway 120 receives the response message to the request message, the processing unit 310 may manage the session so that the response message may be transmitted to the Bluetooth device 110 that transmitted the request message.

7 is a flowchart of a communication method of a Bluetooth device according to an embodiment.

In step 710, the Bluetooth device 110 may register the Bluetooth device 110 with the gateway 120. [

In step 720, the Bluetooth device 110 may register the resources of the Bluetooth device 110 with the gateway 120. [

In step 730, the Bluetooth device 110 may perform communication using the gateway function provided by the gateway 120. [ The object of the communication may be the external device 610. [

The protocol stack of the Bluetooth device 110 may include a CoAP layer and an L2CAP layer, and the CoAP layer may be a layer immediately above the L2CAP layer.

8 is a flowchart of a gateway communication method according to an embodiment.

In step 810, the gateway 120 may search for the Bluetooth device 110.

In step 820, the gateway 120 can identify the resources of the Bluetooth device 110. [

At step 830, the gateway 120 may communicate with the Bluetooth device 110. [ The gateway 120 may provide a gateway function to the Bluetooth device 110.

9 illustrates communication using a CoAP between Bluetooth devices according to an example.

In the communication illustrated in Fig. 9, communication between the Bluetooth devices can be made without the gateway 120. Fig.

For example, the Bluetooth device 110 may be a destination Internet node and the other Bluetooth device 910 may be a destination Internet server. or. The Bluetooth device 110 may be a destination Internet server and the other Bluetooth device 910 may be a destination Internet node.

The Bluetooth device 110 may serve as a CoAP client and / or a CoAP server without the gateway 120. [

The Bluetooth device 110 may control a Bluetooth node such as a smart phone, and may obtain a value from the Bluetooth node. The Bluetooth device 110 may control another Bluetooth device 910 and may obtain a value from another Bluetooth device 910. [ In this case, the Bluetooth device 110 can perform the operation of the CoAP client that transmits the request message of the CoAP to the other Bluetooth device 910. The other Bluetooth device 910 can perform an operation of the CoAP server transmitting the CoAP response message to the Bluetooth device 110 in response to the CoAP request message.

The above roles may be changed. The other Bluetooth device 910 may control the Bluetooth node such as a smart phone and perform a role of acquiring a value from the Bluetooth node. Another Bluetooth device 910 may control the Bluetooth device 110 and may obtain a value from the Bluetooth device 110. [ In this case, the other Bluetooth device 910 can perform the operation of the CoAP client transmitting the CoAP request message to the Bluetooth device 110. [ The Bluetooth device 110 may perform an operation of a CoAP server that transmits a CoAP response message to a CoAP request message to another Bluetooth device 910. [

The Bluetooth device 110 and the other Bluetooth device 910 can identify each other using the Bluetooth address. That is to say, the identification between the Bluetooth nodes can be done through the Bluetooth address.

10 is a flowchart of a search method of a Bluetooth device supporting CoAP using broadcast according to an example.

The gateway 120 can search for the Bluetooth device 110. [ For example, the Bluetooth device 110 may be a Bluetooth enabled sensor node. Also, the Bluetooth device 110 may be an object Internet device and may be a BLE device supporting CoAP.

In an embodiment, the subject of the search may be a smartphone or a Bluetooth device 110, rather than a gateway 120. [ Also, the object of the search may be another Bluetooth device. In other words, in the following embodiment, the gateway 120 may be replaced with a Bluetooth device 110. [

In FIG. 10, each of the first Bluetooth device 1010 and the second Bluetooth device 1020 may correspond to the Bluetooth device 110.

Step 810 described above with reference to FIG. 8 may include the following steps 1030, 1040, and 1050.

The gateway 120 can search for the Bluetooth device 110 supporting the CoAP within the communication range of the first communication unit 320. [ In searching for the Bluetooth device 110, the GATT and ATT of a conventional Bluetooth stack may be used. However, with the structure of the CoAP and the L2CAP, when the Bluetooth device 110 can be searched, the structure of the gateway 120 can be simplified, and the procedure can be simplified.

In an embodiment, the generation of the message of the gateway 120 may be performed by the processing unit 310 of the gateway 120. [ The transmission and reception of messages of the gateway 120 may be performed by the first communication unit 320 of the gateway 120. [ The generation of the message of the first Bluetooth device 1010 may be performed by the processing unit of the first Bluetooth device 1010. The transmission and reception of the message of the first Bluetooth device 1010 may be performed by the communication unit of the first Bluetooth device 1010. The generation of the message of the second Bluetooth device 1020 may be performed by the processing unit of the second Bluetooth device 1020. [ The transmission and reception of the message of the first Bluetooth device 1020 may be performed by the communication unit of the first Bluetooth device 1020. The processing unit of the first Bluetooth device 1010 and the processing unit of the second Bluetooth device 1020 may correspond to the processing unit 210 of the Bluetooth device 110, respectively. The communication unit of the first Bluetooth device 1010 and the communication unit of the second Bluetooth device 1020 may correspond to the communication unit 220 of the Bluetooth device 110, respectively.

In step 1030, the gateway 120 may generate a broadcast message. The gateway 120 may broadcast a broadcast message.

The broadcast message may be a message for searching for a Bluetooth device 110 that supports a CoAP capable of communicating around the gateway 120. [

The Bluetooth link layer packet type of the broadcast message may be an advertisement indication (ADV_IND). The AD type of the broadcast message may have a value indicating that it is a CoAP message. The payload of the broadcast message may include a CoAP Ping (ping) request message.

The transaction type of the CoAP Ping request message may be confirmable. The token length of the CoAP Ping request message may be zero. The code of the CoAP Ping request message may be 0.00 (i.e., empty). The CoAP Ping request message may not include the transaction type, token length, and other options besides the code. The CoAP Ping request message may be 4 bytes.

Bluetooth devices within the communication range can receive broadcast messages.

In step 1040, the first Bluetooth device 1010 receiving the broadcast message may generate a response message for the broadcast message. The first Bluetooth device 1010 may send a response message to the gateway 120. [

The Bluetooth link layer packet type of the response message may be an advertising direct indication (ADV_DIRECT_IND). The AD type of the response message may have a value indicating that it is a CoAP message. The payload of the response message may include a CoAP Ping response message for the CoAP Ping request message.

The transaction type of the CoAP Ping response message may be a reset (RST). The token length of the CoAP Ping response message may be zero. The code of the CoAP Ping response message may be 0.00 (i.e., beam). The message identifier (MID) of the CoAP Ping response message may be the same as the MID of the CoAP Ping request message. The CoAP Ping reply message may be 4 bytes.

The gateway 120 receiving the response message can recognize that the first Bluetooth device 1010 supporting the CoAP is present. For example, the gateway 120 may know the address of the first Bluetooth device 1010.

In step 1050, the second Bluetooth device 1020 receiving the broadcast message may generate a response message to the broadcast message. The second Bluetooth device 1020 may send a response message to the gateway 120. [

Upon receiving the response message, the gateway 120 may recognize that the second Bluetooth device 1020 supporting the CoAP is present. For example, the gateway 120 may know the address of the second Bluetooth device 1020.

As described above, the gateway 120 can search for the Bluetooth device 110 using the broadcast message. The gateway 120 may detect the Bluetooth device 110 by broadcasting a broadcast message including the CoAP Ping request message and receiving a CoAP Ping response message corresponding to the CoAP Ping request message from the Bluetooth device 110 .

11 is a flowchart of a search method of a Bluetooth device supporting CoAP using observation according to an example.

The gateway 120 can search for the Bluetooth device 110. [ For example, the Bluetooth device 110 may be a Bluetooth enabled sensor node. Also, the Bluetooth device 110 may be an object Internet device and may be a BLE device supporting CoAP.

In an embodiment, each of the first gateway 1110 and the second gateway 1120 may be a smart phone.

In FIG. 11, each of the first gateway 1110 and the second gateway 1120 may correspond to the gateway 120.

Step 810 described above with reference to FIG. 8 may include step 1130 below.

In an embodiment, the message of the Bluetooth device 110 may be generated by the processing unit 210 of the Bluetooth device 110. The transmission and reception of the message of the Bluetooth device 110 may be performed by the communication unit 220 of the Bluetooth device 110. [ The transmission and reception of the message of the first gateway 1110 may be performed by the first communication unit of the first gateway 1110. The transmission and reception of messages of the second gateway 1120 may be performed by a communication unit of the second gateway 1120. The communication unit of the first gateway 1110 and the communication unit of the second gateway 1120 may correspond to the first communication unit 320 of the gateway 120, respectively.

At step 1130, the Bluetooth device 110 may generate a broadcast message. The Bluetooth device 110 may broadcast a broadcast message. The Bluetooth device 110 may periodically broadcast a broadcast message.

The broadcast message may be a message for notifying that the Bluetooth device 110 supporting the CoAP capable of communicating exists. The broadcast message may indicate that the Bluetooth device 110 is a Bluetooth node that supports CoAP.

The Bluetooth link layer packet type of the broadcast message may be ADV_IND. The AD type of the broadcast message may have a value indicating that it is a CoAP message. The payload of the broadcast message may include a virtual CoAP Ping response message.

The transaction type of the virtual CoAP Ping response message may be RST. The token length of the virtual CoAP Ping response message may be zero. The code of the virtual CoAP Ping reply message may be 0.00 (i.e., beam). The MID of the virtual CoAP Ping response message can have any value. The virtual CoAP Ping reply message may be 4 bytes.

Gateways within the communication range can receive broadcast messages.

The first gateway 1110 that is watching the broadcast message can receive the broadcast message. Upon receiving the broadcast message, the first gateway 1110 may discover the Bluetooth device 110, which is a BLE device supporting CoAP.

In addition, the second gateway 1120, which was watching the broadcast message, can receive the broadcast message. Upon receiving the broadcast message, the second gateway 1120 may discover the Bluetooth device 110 as a BLE device supporting CoAP.

As described above, the gateway 120 can observe the broadcast message. The gateway 120 may discover the Bluetooth device 110 that broadcasted the broadcast message as it receives the broadcast message including the virtual CoAP Ping response message.

12 is a flowchart of a method of searching for a resource of a Bluetooth device according to an example.

After the gateway 120 discovers or retrieves the Bluetooth device 110, the gateway 120 can determine what resources the Bluetooth device 110 has.

A resource may include a function and an attribute.

In an embodiment, the gateway 120 may retrieve the resources of the Bluetooth device 110 using the CoAP over the L2CAP layer.

Step 820 described above with reference to FIG. 8 may include the following steps 1210, 1220, 1230, 1240, and 1250.

In an embodiment, the transmission and reception of messages of the Bluetooth device 110 may be performed by the communication unit 220. [ The message transmitted by the Bluetooth device 110 may be generated by the processing unit 210. [ The transmission and reception of the message of the gateway 120 may be performed by the first communication unit 320. [ The message transmitted by the gateway 120 may be generated by the processing unit 310. [

At step 1210, the gateway 120 may establish a communication channel with the Bluetooth device 110. The established communication channel may be maintained for a predetermined time.

To establish a communication channel, the gateway 120 may send a connect request (CONNECT_REQ) message to the Bluetooth device 110.

In step 1220, the gateway 120 may send a "CoAP GET / .cb" message to the Bluetooth device 110. The "CoAP GET / .cb" message may be transmitted in the form of a Link Layer (LL) data packet.

".cb" may be included in the URI-route option of the CoAP message. The role of ".cb" may be the same as the role of ".wellknown / core" in the IETF CoAP specification (eg, RFC 7252) Since it can be too long, it can be used simply abbreviated.

In step 1230, the Bluetooth device 110 having received the connection request message may transmit a response message to the connection request message.

If the size of the response message is greater than or equal to a predetermined first value, the response message may be divided into a plurality of sub messages in the Bluetooth L2, and divided sub messages may be transmitted.

In addition, if the size of the response message is greater than or equal to a predetermined second value, a blockwise transfer function of the CoAP can be used.

The payload of the response message may include the path of the resource of the Bluetooth device 110. The resource may be plural. The payload may include a list of paths of a plurality of resources.

Step 1230 may include steps 1231 and 1232. [

In step 1231, the Bluetooth device 110 may send a "CoAP 2.05 Content (Content)" message to the gateway 120. [ The "CoAP 2.05 Content" message may be transmitted in the form of an LL data packet.

In step 1232, the Bluetooth device 110 may send a "CoAP 2.05 continue" message to the gateway 120. The "CoAP 2.05 continue" message may be transmitted in the form of an LL data packet.

At step 1240, the gateway 120 may send a re-question message to the Bluetooth device 110 about the path of the resource. The material message may be a message requesting details of the path.

For example, if there is a path of a resource called " container ", the gateway 120 transmits a "CoAP GET / ). The "CoAP GET / container Accept: link-format" message may be transmitted in the form of an LL data packet.

In step 1250, the Bluetooth device 110 receiving the message of the material for the path of the resource may transmit a response message to the message of the material. The response message may include information about the path of the resource.

If the size of the response message is greater than or equal to a predetermined first value, the response message may be divided into a plurality of sub messages in the Bluetooth L2, and divided sub messages may be transmitted.

Also, when the size of the response message is equal to or larger than a predetermined second value, the block-wise transmission function of CoAP can be used.

The payload of the response message may include information about the path of the resource.

Step 1250 may include steps 1251 and 1252. [

At step 1251, the Bluetooth device 110 may send a "CoAP 2.05 content" message to the gateway 120. The "CoAP 2.05 content" message may be transmitted in the form of an LL data packet.

At step 1252, the Bluetooth device 110 may send a "CoAP 2.05 continue" message to the gateway 120. The "CoAP 2.05 continue" message may be transmitted in the form of an LL data packet.

As described above, the gateway 120 may send a connection request message to the Bluetooth device 110 to retrieve the resources of the Bluetooth device 110. [ The gateway 120 may receive a response message to the connection request message from the Bluetooth device 110. [ The response message may include the path of the resource of the Bluetooth device 110. [ The gateway 120 may transmit a message of a material including the path of the resource to the Bluetooth device 110. [ The gateway 120 may receive a response message from the Bluetooth device 110 that includes information on the path of the resource. The gateway 120 may obtain information on the path of the resource from the response message to the message of the material.

13 is a flowchart of a method of processing a request from an external device of a gateway according to an example.

The gateway 120 may process the request from the external device 610. Through the gateway 120, the Bluetooth device 110 may provide a response to a request from the external device 610.

In an embodiment, the transmission and reception of messages of the Bluetooth device 110 may be performed by the communication unit 220. [ The message transmitted by the Bluetooth device 110 may be generated by the processing unit 210. [ In the gateway 120, transmission and reception of messages between the gateway 120 and the Bluetooth device 110 may be performed by the first communication unit 320. [ In the gateway 120, transmission and reception of messages between the gateway 120 and the external device 610 can be performed by the second communication unit 330. [ The message transmitted by the gateway 120 may be generated by the processing unit 310. [

In step 1310, the processing unit 310 of the gateway 120 may search for the Bluetooth device 110 and may store the address of the searched Bluetooth device 110.

Step 1310 may correspond to step 810 described above with reference to FIG. The embodiments described above with reference to FIGS. 10 and 11 may be used for the search of the Bluetooth device 110. FIG.

In step 1320, the gateway 120 may retrieve the resources of the Bluetooth device 110 and may store information of the retrieved resources.

Step 1320 may correspond to step 820 described above with reference to FIG. The above-described embodiment with reference to FIG. 12 can be used for searching for the resources of the Bluetooth device 110. FIG.

In step 1330, the processing unit 310 of the gateway 120 may generate a mapping for the resource of the Bluetooth device 110. [ The processing unit 310 of the gateway 120 may generate a mapping between the resource of the Bluetooth device 110 and the resource path of the gateway 120. [ The gateway 120 may store a mapping between a resource of the Bluetooth device 110 and a resource path of the gateway 120. [

The resource path may include a prefix, a Bluetooth device identifier, and a resource identifier.

The prefix may indicate a path to a node in the Bluetooth network.

The Bluetooth device identifier may be an identifier of the searched Bluetooth device 110. The resource identifier may be an identifier of the retrieved resource.

For example, if the prefix is "ble", the Bluetooth device identifier is "00123", and the identifier of the resource is "temp", then the resource path may be "/ ble / 00123 / temp".

Step 1330 may correspond to step 820 described above with reference to FIG. That is to say, step 820 may include steps 1320 and 1330.

The following steps 1340, 1350, 1355, 1360, 1365, 1370, 1380 and 1390 may correspond to each of step 730 described above with reference to FIG. 7 and step 830 described above with reference to FIG. 8 have.

In step 1340, the gateway 120 may receive a request message from the external device 610. [

The request message may be a request message of the CoAP.

The gateway 120 may use the URI-path of the request message to retrieve the address of the Bluetooth device 110 which is the destination of the request message.

The processing unit 310 of the gateway 120 establishes a connection between the gateway 120 and the Bluetooth device 110 when the Bluetooth connection with the Bluetooth device 110 that is the destination of the request message is not established in step 1350 . The gateway 120 may send a CONNECT_REQ message to the Bluetooth device 110 to establish a Bluetooth connection. A connection between the gateway 120 and the Bluetooth device 110 can be established through the CONNECT_REQ message.

At step 1355, the processing unit 310 of the gateway 120 may remove the field of the request message. The processing unit 310 of the gateway 120 may remove the Bluetooth device identifier of the URI-host, the URI-port, the URI-path prefix and the URI-path from the request message, Lt; RTI ID = 0.0 > UDP < / RTI >

In step 1360, the gateway 120 may forward the request message to the Bluetooth device 110.

In step 1365, the processing unit 310 of the gateway 120 may store information required to forward a response message to the request message. The processing unit 310 of the gateway 120 may store the address and the port number of the external device 610, which is the source of the request message. In addition, the gateway 120 may store the token field and the MID field of the request message.

In step 1370, the gateway 120 may receive a response message to the request message from the Bluetooth device 110. [

Upon receiving the response message, the processing unit 310 of the gateway 120 refers to the address of the external device 610, the port number of the external device 610, the token field, and the MID field in step 1380, Lt; RTI ID = 0.0 > 610 < / RTI >

In step 1390, the gateway 120 may forward the response message to the external device 610. [

14 is a flowchart of a method of processing a request from an external device of a gateway according to an example.

The gateway 120 may process the request from the Bluetooth device 110. Through the gateway 120, the external device 610 can provide a response to the request from the Bluetooth device 110. [

In an embodiment, the transmission and reception of messages of the Bluetooth device 110 may be performed by the communication unit 220. [ The message transmitted by the Bluetooth device 110 may be generated by the processing unit 210. [ In the gateway 120, transmission and reception of messages between the gateway 120 and the Bluetooth device 110 may be performed by the first communication unit 320. [ In the gateway 120, transmission and reception of messages between the gateway 120 and the external device 610 can be performed by the second communication unit 330. [ The message transmitted by the gateway 120 may be generated by the processing unit 310. [

First, the steps 1310, 1320, and 1330 described above with reference to FIG. 13 can be performed.

The following steps 1410, 1420, 1430, 1440, 1450, 1460, 1470 and 1480 may correspond to each of the above described step 730 with reference to FIG. 7 and step 830 described above with reference to FIG. 8 have.

Next, at step 1410, the gateway 120 may receive a request message from the Bluetooth device 110. [

The request message may be a request message of the CoAP.

The gateway 120 may use the URI-path of the request message to retrieve the address of the external device 610 that is the destination of the request message.

In step 1420, the processing unit 310 of the gateway 120 may extract the field of the request message and may remove the extracted field. The processing unit 310 of the gateway 120 may extract 1) URI-host and 2) URI-port from the request message. The processing unit 310 of the gateway 120 may remove 1) the URI-host and 2) the URI-port from the request message.

In step 1430, the processing unit 310 of the gateway 120 may set the header of the request message. The processing unit 310 of the gateway 120 may set the extracted URI-host as the destination address of the IP header of the request message. The processing unit 310 of the gateway 120 may set the extracted URI-host as the destination address of the IP header of the request message.

At step 1440, the gateway 120 may forward the request message to the external device 610.

In step 1450, the processing unit 310 of the gateway 120 may store information required to forward a response message to the request message. The processing unit 310 of the gateway 120 may store the token field, the MID field, the destination IP address, and the port number of the request message. The processing unit 310 of the gateway 120 may store the Bluetooth device identifier of the Bluetooth device 110, Can be stored.

In step 1460, the gateway 120 may receive a response message for the request message from the external device 610. [

Upon receiving the response message, the processing unit 310 of the gateway 120 receives the stored token field, the stored MID field, the stored destination IP address, the stored port number, the Bluetooth device identifier of the stored Bluetooth device 110, It is possible to identify the Bluetooth device 110 as a destination of the response message by referring to the stored address of the Bluetooth device 110. [

In step 1480, the gateway 120 may forward a response message to the Bluetooth device 110. [

15 is a flowchart of a gateway search method according to an example.

Depending on the operation mode of the Bluetooth device 110, it may happen that the gateway device 120 does not search for the Bluetooth device 110 but the Bluetooth device 110 needs to search for the gateway device 120. [ In the embodiment, a process in which the Bluetooth device 110 searches for the gateway 120 will be described.

The Bluetooth device 110 may be a Bluetooth-enabled sensor node. Also, the Bluetooth device 110 may be an object Internet device and may be a BLE device supporting CoAP.

Step 710 described above with reference to FIG. 7 may include the following steps 1510 and 1520.

In an embodiment, the generation of the message of the gateway 120 may be performed by the processing unit 310 of the gateway 120. [ The transmission and reception of messages of the gateway 120 may be performed by the first communication unit 320 of the gateway 120. [ The message of the Bluetooth device 110 may be generated by the processing unit 210 of the Bluetooth device 110. The transmission and reception of the message of the Bluetooth device 110 may be performed by the communication unit 220 of the Bluetooth device 110. [

At step 1510, the Bluetooth device 110 may generate a broadcast message. The Bluetooth device 110 may broadcast a broadcast message.

The broadcast message may be a message for searching for a gateway 120 supporting a CoAP capable of communicating around the Bluetooth device 110. [

The Bluetooth link layer packet type of the broadcast message may be ADV_IND. The payload of the broadcast message may include a "CoAP GET / gw " request message. The "gw" in the request message may be an example of a URI-path string indicating that it is a gateway node.

The gateway 120 within the communication range can receive the broadcast message.

In step 1520, the gateway 120 receiving the broadcast message may generate a response message for the broadcast. The gateway 120 may send a response message to the Bluetooth device 110.

The Bluetooth link layer packet type of the response message may be ADV_DIRECT_IND. The payload of the response message may include a "CoAP 2.05 Content (Content)" message.

The "CoAP 2.05 Content (Content)" message may correspond to the "CoAP GET / gw"

The "CoAP 2.05 Content (Content)" message may include information about the gateway 120 itself and may include a URI-path that allows the Bluetooth device 110 to register.

As described above, the Bluetooth device 110 obtains information about the gateway 120 by broadcasting a broadcast message including a CoAP GET message and receiving a response message corresponding to the broadcast message from the gateway 120 .

The Bluetooth device 110 may register the Bluetooth device 110 with the gateway 120 using the information about the gateway 120 and the URI-path.

16 is a flowchart of a search method of a gateway supporting CoAP using observation according to an example.

The Bluetooth device 110 may search the gateway 120.

Step 710 described above with reference to FIG. 7 may include step 1610 below.

In an embodiment, the generation of the message of the gateway 120 may be performed by the processing unit 310 of the gateway 120. [ The transmission and reception of messages of the gateway 120 may be performed by the first communication unit 320 of the gateway 120. [ The message of the Bluetooth device 110 may be generated by the processing unit 210 of the Bluetooth device 110. The transmission and reception of the message of the Bluetooth device 110 may be performed by the communication unit 220 of the Bluetooth device 110. [

At step 1610, the gateway 120 may generate a broadcast message. The gateway 120 may broadcast a broadcast message. The gateway 120 may periodically broadcast a broadcast message.

The broadcast message may be a message for notifying that the gateway 120 supporting the CoAP capable of communicating exists. The broadcast message may indicate that the gateway 120 is a Bluetooth node that supports CoAP.

The Bluetooth link layer packet type of the broadcast message may be ADV_IND. The AD type of the broadcast message may have a value indicating that it is a CoAP message. The payload of the broadcast message may include a "CoAP NON (non) PUT / gw" message.

The Bluetooth device 110 within the communication range can receive the broadcast message.

The Bluetooth device 110 that is watching the broadcast message can receive the broadcast message. The first gateway 1110 may discover a gateway 120 that is a BLE device that supports CoAP as it receives the broadcast message.

As described above, the Bluetooth device 110 can observe the broadcast message. The Bluetooth device 110 may discover the gateway 120 that broadcasted the broadcast message as it receives the broadcast message including the CoAP message.

17 is a flowchart of a method of registering a Bluetooth device according to an example.

When the Bluetooth device 110 finds the gateway 120 according to the embodiment described above with reference to FIG. 15 or 16, the Bluetooth device 110 can register the Bluetooth device 110 itself with the gateway 120 have.

Step 710 described above with reference to FIG. 7 may include steps 1710, 1720, and 1730. Steps 1710, 1720, and 1730 may also be performed after step 1520 described above with reference to FIG. 15 and may be performed after step 1610 described above with reference to FIG.

In an embodiment, the transmission and reception of messages of the Bluetooth device 110 may be performed by the communication unit 220. [ The message transmitted by the Bluetooth device 110 may be generated by the processing unit 210. [ The transmission and reception of the message of the gateway 120 may be performed by the first communication unit 320. [ The message transmitted by the gateway 120 may be generated by the processing unit 310. [

In step 1710, the Bluetooth device 110 may establish a communication channel with the gateway 120. The established communication channel may be maintained for a predetermined time.

The Bluetooth device 110 may send a CONNECT_REQ message to the gateway 120 to establish a communication channel.

In step 1720, the Bluetooth device 110 may send a data message. The data message may be an L2 data message.

If the size of the data message is greater than or equal to a predetermined first value, then in Bluetooth L2 the data message may be divided into several sub-messages, and the sub-messages may be transmitted.

In addition, if the size of the data message is greater than or equal to a predetermined second value, a blockwise transfer function of the CoAP can be used.

The payload of the data message may include information about the Bluetooth device 110. The payload may also include the path of the resource of the Bluetooth device 110. [

Step 1720 may include steps 1721 and 1722.

In step 1731, the Bluetooth device 110 may send a "CoAP POST / gw, 001" message to the gateway 120. The "CoAP POST / gw, 001" message may be transmitted in the form of an LL data packet.

At step 1732, the Bluetooth device 110 may send a "continue" message to the gateway 120. The "continue" message may be transmitted in the form of an LL data packet.

At step 1740, the gateway 120 may send a response message to the Bluetooth device 110 for a data message. The response message may indicate that information about the Bluetooth device 110 has been registered with the gateway 120.

For example, the gateway 120 may transmit a message of "CoAP 2.01, Location: / gw / ble / 001" to the Bluetooth device 110 as a response message. CoAP 2.01, Location: / gw / ble / 001 "may be transmitted in the form of an LL data packet.

The response message may indicate a path where information on the Bluetooth device 110 is recorded. In the message " CoAP 2.01, Location: / gw / ble / 001 ", the value of "Location" option "/ gw / ble / 001" may indicate the path where information on the Bluetooth device 110 is recorded.

The Bluetooth device 110 sends a data message including the information about the Bluetooth device 110 and the path of the resources of the Bluetooth device 110 to the gateway 120 in order to register the Bluetooth device 110 in the gateway 120 120, and receive a response message from the gateway 120 including a path in which information on the Bluetooth device 110 is recorded.

18 is a flowchart of a method of registering a resource of a Bluetooth device according to an example.

The Bluetooth device 110 may register the resource of the Bluetooth device 110 in the gateway 120. A resource may include functions and attributes. In addition, the Bluetooth device 110 can register a plurality of resources with the gateway 120. [

The Bluetooth device 110 may register the resource with the gateway 120 using the path where the information about the Bluetooth device 110 acquired in the step 1740 described above with reference to Fig. 17 is recorded.

Step 720, described above with reference to FIG. 7, may include the following steps 1810 and 1820.

In an embodiment, the transmission and reception of messages of the Bluetooth device 110 may be performed by the communication unit 220. [ The message transmitted by the Bluetooth device 110 may be generated by the processing unit 210. [ The transmission and reception of the message of the gateway 120 may be performed by the first communication unit 320. [ The message transmitted by the gateway 120 may be generated by the processing unit 310. [

In step 1810, the Bluetooth device 110 may send a resource registration message to the gateway 120. [

If the size of the resource registration message is greater than or equal to a predetermined first value, the resource registration message may be divided into a plurality of sub messages in the Bluetooth L2, and divided sub messages may be transmitted.

In addition, when the size of the resource registration message is larger than a predetermined second value, the block-wise transmission function of the CoAP can be used.

The payload of the resource registration message may include a path where information about the Bluetooth device 110 is recorded and information about a resource of the Bluetooth device 110. [ The resource may be plural. The payload of the resource registration message may include information about a plurality of resources.

Step 1810 may include steps 1811 and 1812.

At step 1811, the Bluetooth device 110 may send a "CoAP POST / gw / ble / 001, <resource>" message to the gateway 120. "CoAP POST / gw / ble / 001, < resource >" message can be transmitted in the form of an LL data packet.

"/ gw / ble / 001" may indicate the path where information on the Bluetooth device 110 obtained in the above-described step 1740 is recorded with reference to FIG. For example, "/ gw / ble / 001" may be an identifier of the Bluetooth device 110.

The < resource > may indicate information about a resource of the Bluetooth device 110. [ The payload of the "CoAP POST / gw / ble / 001" message may include information about the resources of the Bluetooth device 110. [

At step 1812, the Bluetooth device 110 may send a "continue" message to the gateway 120. The "continue" message may be transmitted in the form of an LL data packet.

In step 1820, the gateway 120 may send a response message to the Bluetooth device 110 in response to the resource registration message. The response message may be transmitted in the form of an LL data packet.

For example, the response message may be "CoAP 2.01, Location: / gw / ble / 001 / data1 ".

The response message may include information about the resources of the Bluetooth device 110. [

The value of the "Location" option may indicate a path where information on the resources of the Bluetooth device 110 is recorded. For example, information on the resources of the Bluetooth device 110 may be recorded in the path "/ gw / ble / 001 / data1 ".

As described above, the Bluetooth device 110 can register the resource with the gateway 120 using the path in which the information about the Bluetooth device 110 itself is recorded.

19 is a structural diagram of a Bluetooth device according to an example.

In the Bluetooth device 110, the CoAP may be replaced with an MQ Teletext Transport (MQTT).

Although MQTT is designed based on TCP, it can provide a simple message structure. Therefore, the MQTT layer can be directly above the L2CAP layer.

The application layer can provide services by using the MQTT standard even if the complicated procedures and specifications of Bluetooth are not used directly.

The contents of the CoAP described above with reference to the embodiments can be applied to the MQTT. For example, at least one program executed in the processing unit 210 may include code of an MQTT layer, and the MQTT layer may be a layer immediately above the L2CAP layer.

20 is a structural diagram of a gateway according to an example.

At the gateway 120, the CoAP may be replaced with an MQTT. UDP can be replaced with TCP. The contents of the CoAP described above with reference to the embodiments can be applied to the MQTT. In addition, the contents of UDP described above with reference to the embodiments can be applied to TCP. For example, the at least one program performed by the processing unit 310 may include code of the MQTT layer, and the MQTT layer may be a layer immediately above the L2CAP layer.

21 illustrates a structure of communication between a Bluetooth device and a gateway according to an embodiment.

In the Bluetooth device 110, the gateway 120, and the external device 610, the CoAP may be replaced with an MQTT. UDP can be replaced with TCP. The contents of the CoAP described above with reference to the embodiments can be applied to the MQTT. In addition, the contents of UDP described above with reference to the embodiments can be applied to TCP.

Basically, the communication protocol can be configured to act in one of the seven layers of the Open Systems Interconnection (OSI). When applying a protocol to a system, a protocol suitable for each layer can be selected, and the protocol stack can be configured by selected protocols.

A typical protocol layer structure may include a physical layer, a logical layer, a network layer, a transport layer, a session layer, and an application layer. IPSP according to the Bluetooth standard can also follow this structure.

The CoAP protocol corresponds to the session layer and the application layer. Depending on the characteristics of the physical layer, the logical layer and the CoAP protocol of Bluetooth, the logical layer and the CoAP protocol of the Bluetooth device 110 can be directly connected without a network layer and a transport layer protocol. Efficiency and compatibility can be ensured by direct connection. In addition, the networking function of the Bluetooth device 110 may be performed in cooperation with the gateway 120. [

Figure 22 shows the format of the advertising channel frame according to an example.

The advertisement channel frame format 2200 includes a preamble 2210, an access address 2220, an Advertising Channel PDU (Protocol Data (PDU) (CoAP Header / Options) 2250, CoAP payload 2260, and Cyclic Redundancy Check (CRC) 2270. [0040]

The advertising channel frame format 2200 may be used as the format of the message related to the advertising channel among the messages described above.

23 shows a data channel frame format according to an example.

The data channel frame format 2300 includes a preamble 2310, an access address 2320, a data channel PDU header 2330 CoAP header / options 2340, CoAP payload 2350 and Cyclic Redundancy Check (CRC) 2360. The CoAP header /

The data channel frame format 2300 can be used as the format of the message related to the data channel among the above-mentioned messages.

The apparatus described above may be implemented as a hardware component, a software component, and / or a combination of hardware components and software components. For example, the apparatus and components described in the embodiments may be implemented within a computer system, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA) A programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. The processing device may also access, store, manipulate, process, and generate data in response to execution of the software. For ease of understanding, the processing apparatus may be described as being used singly, but those skilled in the art will recognize that the processing apparatus may have a plurality of processing elements and / As shown in FIG. For example, the processing unit may comprise a plurality of processors or one processor and one controller. Other processing configurations are also possible, such as a parallel processor.

The software may include a computer program, code, instructions, or a combination of one or more of the foregoing, and may be configured to configure the processing device to operate as desired or to process it collectively or collectively Device can be commanded. The software and / or data may be in the form of any type of machine, component, physical device, virtual equipment, computer storage media, or device , Or may be permanently or temporarily embodied in a transmitted signal wave. The software may be distributed over a networked computer system and stored or executed in a distributed manner. The software and data may be stored on one or more computer readable recording media.

The method according to an embodiment may be implemented in the form of a program command that can be executed through various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions to be recorded on the medium may be those specially designed and configured for the embodiments or may be available to those skilled in the art of computer software. Examples of computer-readable media include magnetic media such as hard disks, floppy disks and magnetic tape; optical media such as CD-ROMs and DVDs; magnetic media such as floppy disks; Magneto-optical media, and hardware devices specifically configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of program instructions include machine language code such as those produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments. For example, it is to be understood that the techniques described may be performed in a different order than the described methods, and / or that components of the described systems, structures, devices, circuits, Lt; / RTI &gt; or equivalents, even if it is replaced or replaced.

110: Bluetooth device
120: Gateway
610: External device

Claims (20)

A processing unit for executing at least one program; And
A communication unit that performs Bluetooth communication
Lt; / RTI &gt;
Wherein the at least one program comprises code of a CoAP layer and code of an L2CAP layer,
Wherein the CoAP layer is a layer immediately above the L2CAP layer. The method according to claim 1,
Wherein the at least one program comprises a CoAP support profile. 3. The method of claim 2,
Wherein the CoAP support profile allows the Bluetooth device to be detected through the GATT and ATT to support the function of the CoAP. The method according to claim 1,
Wherein the Bluetooth device broadcasts a broadcast message including a CoAP GET message and obtains information about the gateway by receiving a response message corresponding to the broadcast message from the gateway. The method according to claim 1,
Wherein the Bluetooth device observes a broadcast message and finds a gateway that broadcasts the broadcast message upon receiving the broadcast message. The method according to claim 1,
The Bluetooth device transmits a data message including information on the Bluetooth device and a resource path of the Bluetooth device to the gateway in order to register the Bluetooth device in the gateway, And receives a response message from the gateway. The method according to claim 6,
And the Bluetooth device registers the resource of the Bluetooth device with the gateway using the path. Performed by a Bluetooth device,
Registering the Bluetooth device with a gateway; And
Performing communication through a gateway function provided by the gateway
Lt; / RTI &gt;
Wherein the protocol stack of the Bluetooth device includes a CoAP layer and an L2CAP layer,
Wherein the CoAP layer is a layer immediately above the L2CAP layer. 9. The method of claim 8,
Registering the resources of the Bluetooth device with the gateway
Lt; / RTI &gt; A processing unit for executing at least one program; And
A communication unit that performs Bluetooth communication
Lt; / RTI &gt;
Wherein the at least one program comprises code of an MQTT layer and code of an L2CAP layer,
Wherein the MQTT layer is a layer immediately above the L2CAP layer. A processing unit for executing at least one program;
A first communication unit for Bluetooth communication; And
A second communication unit for interworking with the Internet
Lt; / RTI &gt;
Wherein the at least one program includes a code for a first communication unit,
Wherein the code for the first communication unit includes a code of a CoAP layer and a code of an L2CAP layer,
Wherein the CoAP layer is a layer immediately above the L2CAP layer. 12. The method of claim 11,
Wherein the at least one program comprises a proxy module,
Wherein the proxy module is an upper layer of the CoAP layer,
Wherein the proxy module enables communication between devices connected through the Bluetooth device and the second communication unit by mapping an address of a Bluetooth device connected through the first communication unit to a URI-path inside the gateway. 12. The method of claim 11,
The first communication unit receives a CoAP request message from the Bluetooth device,
The processing unit removes the URI-host and the URI-port from the CoAP request message, sets an IP header and a UDP header in the request message,
And the second communication unit transmits a request message with the IP header and the UDP header set to an external device. 12. The method of claim 11,
The second communication unit receives a CoAP request message from an external device,
The processing unit removes the URI-host, URI-port, URI-path prefix, URI-path Bluetooth device identifier, IP header, and UDP header from the CoAP request message,
Wherein the first communication unit transmits to the Bluetooth device a request message in which the URI-host, the URI-port, the prefix, the Bluetooth device identifier, the IP header, and the UDP header are removed. 12. The method of claim 11,
Wherein the gateway broadcasts a broadcast message including a CoAP Ping request message, and receives a CoAP Ping response message corresponding to the CoAP Ping request message from the Bluetooth device, thereby detecting the Bluetooth device. 12. The method of claim 11,
The gateway can observe the broadcast message,
Wherein the gateway detects the Bluetooth device broadcasting the broadcast message upon receiving the broadcast message including the virtual CoAP Ping response message. 12. The method of claim 11,
The gateway transmits a connection request message to the Bluetooth device, receives a response message including the path of the resource of the Bluetooth device from the Bluetooth device, transmits a message including the route to the Bluetooth device, And receives a response message from the Bluetooth device, the response message including information about the path. Performed by the gateway,
Searching for a Bluetooth device; And
Step to provide gateway function to Bluetooth device
Lt; / RTI &gt;
The protocol stack for the Bluetooth communication of the gateway includes a CoAP layer and an L2CAP layer,
Wherein the CoAP layer is a layer immediately above the L2CAP layer. 19. The method of claim 18,
Confirming a resource of the Bluetooth device
Lt; / RTI &gt; A processing unit for executing at least one program;
A first communication unit for Bluetooth communication; And
A second communication unit for interworking with the Internet
Lt; / RTI &gt;
Wherein the at least one program includes a code for a first communication unit,
Wherein the code for the first communication unit includes a code of an MQTT layer and a code of an L2CAP layer,
Wherein the MQTT layer is a layer immediately above the L2CAP layer.

Images