KR102503257B1 - Apparatus and method for bluetooth communication - Google Patents

Abstract

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

Description

Apparatus and method for Bluetooth communication {APPARATUS AND METHOD FOR BLUETOOTH COMMUNICATION}

The following embodiments relate to a method and apparatus for Bluetooth communication, and more specifically, a method and apparatus having a simple protocol stack for Bluetooth communication for the Internet of Things are provided.

Bluetooth technology is a short-distance wireless communication technology, and is a technology that provides communication with nearby devices within 10 m. Recently, a Bluetooth Low Energy (BLE) standard, which is a low power standard, has been developed to support various sensors.

As a Bluetooth standard, profile standards are being established for each type of Bluetooth device and service. However, the development of the profile standard is not keeping up with the speed at which Bluetooth devices are newly developed. Accordingly, manufacturers of Bluetooth devices provide upper layer communication standards or application programming interfaces (APIs).

This situation makes it difficult to interlock between different products or between products of different manufacturers. For example, a Bluetooth device such as a smartphone must search for various other Bluetooth devices and interoperate with the searched other Bluetooth devices. If such interworking is performed only through a program (for example, an App) written by a manufacturer of a Bluetooth device, problems arise in compatibility and interoperability.

On the other hand, as we enter the Internet of Things (IoT) era in which various things connected through the Internet are connected to the Internet and interoperate with each other, technical standards for how to enable Bluetooth devices to interoperate with the Internet have been established. .

These technical standards include 1) a method for enabling a Bluetooth device to support Representational State Transfer (REST) API, 2) a Bluetooth device accessing the Internet through a HyperText Transfer Protocol (HTTP) proxy. How to access and 3) Layers of 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) implemented as a layer above Link Layer Control and Adaptation Protocol (L2CAP). Below is a brief overview of the three methods.

1) How Bluetooth devices support REST API

A Bluetooth Internet gateway receives requests from clients over the Internet. The Bluetooth Internet gateway converts the request into the Bluetooth device's Attribute Protocol (ATT) and/or Generic Attribute Profile (GATT). Through the above conversion, communication between the Bluetooth device and the client is performed.

This method uses the existing Bluetooth stack as it is. As the existing Bluetooth stack is used as it is, this method has the aforementioned problems of compatibility and interoperability. Therefore, the Bluetooth Internet gateway should be able to recognize internal properties of various Bluetooth devices and interwork with various Bluetooth devices having different internal properties. In addition, the external server must also know the internal properties of the Bluetooth device in advance.

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

2) How Bluetooth devices access the Internet through HTTP proxy

In this method, an existing Bluetooth stack is used as it is in a Bluetooth section between a Bluetooth HTTP Proxy Service (HPS) client and a Bluetooth HPS server. The Bluetooth HPS server performs the function of a gateway. The Bluetooth HPS server converts Bluetooth protocols to Internet protocols such as HTTP through its own mapping. This translation enables communication between the Bluetooth HPS client and the remote HTTP server.

In this way, the Bluetooth HPS server performing the function of the gateway must know all the attributes of the Bluetooth device. Therefore, when this method is used, interoperability and compatibility in communication may deteriorate.

3) How to use IPSP.

The method using IPSP implements 6LowPAN, IPv6, UDP, TCP and application layer stacks on L2CAP without using Bluetooth ATT and GATT. Communication is achieved through this implementation. This method can ensure high compatibility and interoperability because the Internet protocol is loaded into the Bluetooth node as it is.

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

In relation to Bluetooth, Korean Patent Publication No. 2014-0027503 and Korean Patent Registration No. 10-1397744 have been proposed.

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

An embodiment may provide an apparatus and method for providing high-efficiency communication by omitting some of the protocol stacks.

In one aspect, a processing unit that executes at least one program; and a communication unit that performs Bluetooth communication, wherein the at least one program includes CoAP layer code and L2CAP layer code, and the CoAP layer is a layer immediately above the L2CAP layer.

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

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

The CoAP support profile enables a discovery that the Bluetooth device supports CoAP functions through GATT and ATT.

The Bluetooth device may acquire 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 the broadcast message and, upon receiving the broadcast message, can discover the gateway that broadcast the broadcast message.

The Bluetooth device may transmit a data message including information about the Bluetooth device and a path of a resource of the Bluetooth device to the gateway to register the Bluetooth device with the gateway, and a path in which the information about the Bluetooth device is recorded. A response message including a may be received from the gateway.

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

In another aspect, the step of registering the Bluetooth device to the gateway, performed by the Bluetooth device; and performing communication through a gateway function provided by the gateway, wherein a protocol stack of the Bluetooth device includes a CoAP layer and an L2CAP layer, and the CoAP layer is a communication layer immediately above the L2CAP layer. A method is provided.

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

In another aspect, a processing unit that executes at least one program; and a communication unit that performs Bluetooth communication, wherein the at least one program includes an MQTT layer code and an L2CAP layer code, and the MQTT layer is a layer immediately above the L2CAP layer.

In another aspect, a processing unit that executes at least one program; 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 first communication unit code, the first communication unit code includes a CoAP layer code and an L2CAP layer code, The CoAP layer is provided with a gateway, which is a layer immediately above the L2CAP layer.

The at least one program may include a proxy module.

The proxy module may be a layer above the CoAP layer.

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

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

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

The second communication unit may transmit 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 processor may remove a URI-host, a URI-port, a prefix from a URI-path, a Bluetooth device identifier from a URI-path, an IP header, and a UDP header from the request message of the CoAP.

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

The gateway may 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 may observe broadcast messages.

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

The gateway may transmit a connection request message to the Bluetooth device, receive a response message including a resource path of the Bluetooth device from the Bluetooth device, and transmit a material message including the path to the Bluetooth device. and receive a response message including information about the route from the Bluetooth device.

In another aspect, searching for a Bluetooth device performed by a gateway; and providing a gateway function to a 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 layer immediately above the L2CAP layer. do.

The communication method may further include checking resources of the Bluetooth device.

In another aspect, a processing unit that executes at least one program; A first communication unit for Bluetooth communication; and a second communication unit for interworking with the Internet, wherein the at least one program includes code for the first communication unit, the code for the first communication unit includes an MQTT layer code and an L2CAP layer code, and the The MQTT layer is provided with a gateway that 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 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 that communicates using Bluetooth according to one embodiment.
2 is a structural diagram of a Bluetooth device according to an embodiment.
3 is a structural diagram of a gateway according to an embodiment.
4 shows a protocol structure of a Bluetooth device according to an 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 CoAP between Bluetooth devices according to an example.
10 is a flowchart of a method for discovering a Bluetooth device supporting CoAP using broadcast according to an example.
11 is a flowchart of a method for discovering 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 method for discovering 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.
22 illustrates an advertising channel frame format according to an example.
23 illustrates a data channel frame format according to an example.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS For detailed descriptions of exemplary embodiments described below, reference is made to the accompanying drawings, which illustrate specific embodiments by way of example. 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, specific shapes, structures, and characteristics described herein may be implemented in one embodiment in another embodiment without departing from the spirit and scope of the invention. Additionally, it should be understood that the location or arrangement of individual components within each disclosed embodiment may be changed without departing from the spirit and scope of the embodiment. Accordingly, the detailed description set forth below is not to be taken in a limiting sense, and the scope of the exemplary embodiments, if properly described, is limited only by the appended claims, along with all equivalents as claimed by those claims.

Like reference numbers in the drawings indicate the same or similar function throughout the various aspects. The shapes and sizes of elements in the drawings may be exaggerated for clarity.

Terms used in the examples are for describing the examples and are not intended to limit the present invention. In the examples, the singular also includes the plural unless specifically stated in the text. As used herein, "comprises" and/or "comprising" means that a stated component, step, operation, and/or element is present in the presence of one or more other components, steps, operations, and/or elements. Or, it does not exclude addition, and means that additional configurations may be included in the practice of exemplary embodiments or the scope of the technical idea of exemplary embodiments. When a component is referred to as being “connected” or “connected” to another component, the two components may be directly connected or connected to each other, but It will be understood that other components may exist in the middle of the two components.

Terms such as first and second may be used to describe various elements, but the above elements should not be limited by the above terms. The above terms are used to distinguish and refer to one component from another. For example, without departing from the scope of rights, a first element may be termed a second element, and similarly, a second element may also be termed a first element.

In addition, the components appearing in the embodiments are shown independently to represent different characteristic functions, and each component does not mean that each component consists of only a separate hardware or one software unit. That is, each component is listed as each component for convenience of description. For example, at least two of the components may be combined into one component. Also, one component may be divided into a plurality of components. An integrated embodiment and a separate embodiment of each of these components are also included in the scope of rights unless departing from the essence.

In addition, some of the components may not be essential components for performing essential functions, but may be optional components for improving performance. Embodiments may be implemented by including only components essential to implement the essence of the embodiment, and structures excluding optional components, such as components used only for performance improvement, are also included in the scope of rights.

Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily practice the embodiments. In describing the embodiments, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present specification, the detailed description will be omitted.

In the existing Bluetooth standard, a profile standard was established for each Bluetooth device, and the profile standard was complied with. However, in the age of the Internet of Things, the rate of establishment of standards is not keeping up with the rate of release of new products.

Due to the gap between the establishment of standards and the release of new products, a problem of compatibility in which only one company's products are interlocked occurred. In addition, there has been a problem that it is difficult to develop gateways and applications that can accommodate various devices.

Therefore, the following embodiments propose a protocol structure that secures compatibility capable of accommodating various Bluetooth-based IoT devices to be developed in the future. In addition, the following embodiments can secure efficiency by solving duplication of functions such as message overhead, security, and retransmission, which occur when the existing Internet protocol is implemented on a Bluetooth node as it is.

In addition, in the following embodiments, a protocol structure enabling a Bluetooth device to efficiently connect to the Internet of Things according to a standard is proposed.

1 illustrates a system that communicates using Bluetooth according to one embodiment.

System 100 may include a Bluetooth device 110 and a gateway 120 . The number of Bluetooth devices 110 may be plural.

The Bluetooth device 110 may support IoT. 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.

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

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

2 is a structural diagram of a Bluetooth device according to an embodiment.

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 tasks 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 codes of operations or steps of the processing unit 210 described in the embodiments.

The communication unit 220 may receive data or information required for operation of the Bluetooth device 110 and may transmit data or information required for operation of the Bluetooth device 110 . The communication unit 220 may transmit data to another device within the network and may receive data from the other device. 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 the 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.

The storage unit 230 may store at least one program. The processing unit 210 may execute at least one program. The processing unit 210 may read at least one program code 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 may perform Bluetooth communication. The communication unit 220 may transmit data to another device through Bluetooth communication and may receive data from the other 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 may process tasks 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 codes of operations or steps 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 may transmit data to and receive data from other devices within the network. For example, each of the first communication unit 320 and the second communication unit 330 may be a network chip or 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.

The storage unit 340 may store at least one program. The processing unit 310 may execute at least one program. The processing unit 310 may read at least one program code 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 other devices.

Operations, 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 shows a protocol structure of a Bluetooth device according to an embodiment.

The protocol structure of the Bluetooth device 110 may be classified into a controller and a host. For example, the controller may correspond to the communication unit 220 and the host may correspond to the processing unit 210 . Alternatively, the host may correspond to a part 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 a physical layer. The next layer may be a link (or data link) layer. The next layer may be the host controller interface.

The next layer may be L2CAP. The ATT layer, GATT, Generic Access Profile (GAP), and CoAP Support Profile (CSP) may be layers above the L2CAP layer. CoAP may be a layer above L2CAP. An application may be a layer above CoAP.

At least one program executed by the processor 210 may include a host interface layer, an L2CAP layer, a CoAP layer, and an application layer. At least one program executed by the processor 210 may include an ATT layer, a GATT layer, a GAP layer, and a CSP layer. For example, at least one program may include host controller interface layer code, L2CAP layer code, CoAP layer code, and application layer code. Also, at least one program may include ATT layer code, GATT layer code, GAP layer code, and CSP layer code.

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

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

Layers below the CoAP layer, such as the L2CAP layer, the host controller interface layer, the link layer, and the physical layer, may correspond to the BLE module. In other words, in the Bluetooth device 110, the CoAP layer may be a layer directly above the BLE.

IETF CoAP may be a protocol designed to operate on top of the UDP layer for small devices with low capacity.

The L2CAP layer may transmit data in the form of datagrams. Additionally, the L2CAP layer may identify nodes, may transmit messages to nodes, and may receive messages from nodes.

In other words, even without an IP layer, a UDP layer, and a 6LoWPAN layer, CoAP can operate directly above the L2CAP layer. Through this operation, the Bluetooth device 110 can use a standard IoT protocol while enabling efficient communication.

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

The CoAP layer may include at least part of a CoAP client function and a CoAP server function. The CoAP client function may include a function of transmitting a message of 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 the CoAP request.

The CSP may make it possible to discover that the Bluetooth device 100 supports the CoAP function through GATT and ATT.

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

If the 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 requested to search for other Bluetooth devices using only CoAP and L2CAP and to find out properties of the other Bluetooth devices found.

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

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

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

First, the protocol structure of the first communication unit 320 is examined.

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

CoAP may be a layer above L2CAP.

A lower layer of L2CAP may be a BLE module as shown. Alternatively, the BLE module can be replaced with a traditional Bluetooth physical layer and logical layer. For example, layers below 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 BLE module code, an L2CAP layer code, and a CoAP layer code.

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

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

Next, the protocol structure of the second communication unit 330 is examined.

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

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

IP may be a layer above WiFi and/or Ethernet.

UDP may be a layer above IP.

CoAP and/or HTTP may be layers above UDP.

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

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

In FIG. 6 , the Bluetooth device 110 , the gateway 120 and the 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 an IoT 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 may communicate with each other through Bluetooth communication. The second communication unit 330 of the gateway 120 and the external device 610 may communicate with each other through a wired or wireless network.

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

The proxy module of the gateway 120 connects the Bluetooth device 110 and the second communication unit 330 by mapping the address of the Bluetooth device 110 connected through the first communication unit 320 to the URI-path within the gateway 120. Communication between the external devices 610 connected through may be enabled.

When the Bluetooth device 110 transmits a request to the external device 610, the Bluetooth device 110 may use a URI-host option and a URI-port option in the CoAP message. The processing unit 210 of the Bluetooth device 110 may generate a CoAP request message including a URI-host option and a URI-port option. 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 CoAP request message including a URI-host option and a URI-port option 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 an IP header and a UDP header in the request message. The second communication unit 330 of the gateway 120 may transmit the request message in which the IP header and the UDP header are set to the external device 610 .

The external device 610 may transmit 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 receiving a response message to the request message, the processing unit 310 of the gateway 120 may manage a session so that the response message can be delivered to the Bluetooth device 110 that sent 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 a resource of the Bluetooth device 110 with the gateway 120.

At step 730, the Bluetooth device 110 may perform communication using the gateway function provided by the gateway 120. The target of 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.

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

In step 820, the gateway 120 may check the resources of the Bluetooth device 110.

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

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

In the communication illustrated in FIG. 9 , communication between Bluetooth devices may be performed without the gateway 120 .

For example, the Bluetooth device 110 may be an IoT node, and another Bluetooth device 910 may be an IoT server. or. The Bluetooth device 110 may be an IoT server, and another Bluetooth device 910 may be an IoT node.

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

Like a smart phone, the Bluetooth device 110 may control a Bluetooth node and obtain a value from the Bluetooth node. The Bluetooth device 110 can control other Bluetooth devices 910 and obtain values from the other Bluetooth devices 910 . In this case, the Bluetooth device 110 may perform a CoAP client operation of transmitting a CoAP request message to another Bluetooth device 910 . The other Bluetooth device 910 may perform a CoAP server operation of transmitting a CoAP response message to the CoAP request message to the Bluetooth device 110 .

The above roles may change. Another Bluetooth device 910 may play a role of controlling a Bluetooth node and obtaining a value from the Bluetooth node, like a smart phone. Another Bluetooth device 910 can control the Bluetooth device 110 and obtain a value from the Bluetooth device 110 . In this case, another Bluetooth device 910 may perform a CoAP client operation of transmitting a CoAP request message to the Bluetooth device 110 . The Bluetooth device 110 may perform a CoAP server operation of transmitting a CoAP response message to another Bluetooth device 910 in response to a CoAP request message.

Bluetooth device 110 and other Bluetooth devices 910 can identify each other using Bluetooth addresses. In other words, identification between Bluetooth nodes can be made through a Bluetooth address.

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

The gateway 120 may search for the Bluetooth device 110. For example, the Bluetooth device 110 may be a Bluetooth enabled sensor node. In addition, the Bluetooth device 110 may be an IoT device and may be a BLE device supporting CoAP.

In an embodiment, the search subject may be a smartphone or a Bluetooth device 110 rather than the gateway 120 . Also, a search target may be another Bluetooth device. In other words, in the embodiments below, the gateway 120 may be replaced by the 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 steps 1030, 1040, and 1050 below.

The gateway 120 may search for a Bluetooth device 110 supporting CoAP within a communication range of the first communication unit 320 . For discovery of the Bluetooth device 110, GATT and ATT of the traditional Bluetooth stack may be used. However, if the discovery of the Bluetooth device 110 is possible with only the CoAP and L2CAP structures, the structure of the gateway 120 may be simpler and the procedure may be simpler.

In an embodiment, generation of the message of the gateway 120 may be performed by the processing unit 310 of the gateway 120 . Message transmission and reception of the gateway 120 may be performed by the first communication unit 320 of the gateway 120 . Generation of the message of the first Bluetooth device 1010 may be performed by a processing unit of the first Bluetooth device 1010 . Message transmission and reception of the first Bluetooth device 1010 may be performed by a communication unit of the first Bluetooth device 1010 . Generation of the message of the second Bluetooth device 1020 may be performed by a processing unit of the second Bluetooth device 1020 . Message transmission and reception of the first Bluetooth device 1020 may be performed by a communication unit of the first Bluetooth device 1020 . Each of 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 . Each of 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 .

At step 1030, gateway 120 may generate a broadcast message. Gateway 120 may broadcast a broadcast message.

The broadcast message may be a message for searching for a Bluetooth device 110 supporting CoAP capable of communication in the vicinity of the gateway 120 .

The Bluetooth link layer packet type of the broadcast message may be advertising 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 0. The code of the CoAP Ping request message may be 0.00 (ie, empty). The CoAP Ping request message may not include options other than transaction type, token length, and code. A CoAP Ping request message may be 4 bytes.

Bluetooth devices within communication range can receive the broadcast message.

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

The Bluetooth link layer packet type of the response message may be 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 to the CoAP Ping request message.

The transaction type of the CoAP Ping response message may be reset (RST). The token length of the CoAP Ping response message may be 0. The code of the CoAP Ping response message may be 0.00 (ie beam). A message identifier (MID) of the CoAP Ping response message may be the same as the MID of the CoAP Ping request message. A CoAP Ping response message may be 4 bytes.

Upon receiving the response message, the gateway 120 may recognize that the first Bluetooth device 1010 supporting CoAP exists in the vicinity. 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 transmit a response message to the gateway 120 .

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

As described above, gateway 120 may discover Bluetooth device 110 using a broadcast message. The gateway 120 may detect the Bluetooth device 110 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 110. .

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

The gateway 120 may search for the Bluetooth device 110. For example, the Bluetooth device 110 may be a Bluetooth enabled sensor node. In addition, the Bluetooth device 110 may be an IoT 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 smartphone.

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 generation of the message of the Bluetooth device 110 may be performed by the processing unit 210 of the Bluetooth device 110. Message transmission and reception of the Bluetooth device 110 may be performed by the communication unit 220 of the Bluetooth device 110 . Message transmission and reception of the first gateway 1110 may be performed by the first communication unit of the first gateway 1110 . Message transmission and reception of the second gateway 1120 may be performed by a communication unit of the second gateway 1120 . Each of 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 .

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 a Bluetooth device 110 supporting communicable CoAP exists. The broadcast message may indicate that the Bluetooth device 110 is a Bluetooth node supporting 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 0. The code of the virtual CoAP Ping response message may be 0.00 (ie beam). The MID of the virtual CoAP Ping response message can have any value. A virtual CoAP Ping response message may be 4 bytes.

Gateways within communication range can receive the broadcast message.

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

Also, the second gateway 1120 observing the broadcast message may receive the broadcast message. Upon receiving the broadcast message, the second gateway 1120 may discover the Bluetooth device 110, which is a BLE device supporting CoAP.

As mentioned above, gateway 120 can observe broadcast messages. Upon receiving the broadcast message including the virtual CoAP Ping response message, the gateway 120 may discover the Bluetooth device 110 that broadcast the broadcast 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 searches for the Bluetooth device 110, the gateway 120 can check which resources the Bluetooth device 110 has.

Resources can include functions and attributes.

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

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

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

In 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 amount of time.

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

In step 1220, the gateway 120 may transmit 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" of the IETF CoAP standard (eg, RFC7252 (RFC7252)). Since it can be too long for a short text, it can be used as a shorthand for simplicity.

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

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

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

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

Step 1230 may include steps 1231 and 1232 .

In step 1231, the Bluetooth device 110 may transmit 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.

In step 1232, the Bluetooth device 110 may transmit 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.

In step 1240, the gateway 120 may transmit a re-question message about the path of the resource to the Bluetooth device 110. The message of the material may be a message requesting detailed information about the route.

For example, if a resource path named “container” exists, the gateway 120 sends a “CoAP GET /container Accept (accept):link-format” message to the Bluetooth device 110 ) can be transmitted. 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 material message for the resource path may transmit a response message to the material message. The response message may include information about the path of the resource.

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

In addition, when the size of the response message is larger than a predetermined second value, a blockwise transmission function of CoAP may 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 .

In step 1251, the Bluetooth device 110 may transmit 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.

In step 1252, the Bluetooth device 110 may transmit 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 transmit a connection request message to the Bluetooth device 110 to search for 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 a resource path of the Bluetooth device 110. The gateway 120 may transmit a material message including a resource path to the Bluetooth device 110 . The gateway 120 may receive a response message including information about a path of a resource from the Bluetooth device 110 . The gateway 120 may obtain information about a path of a resource from a response message to a message of a 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 a 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, transmission and reception of messages of the Bluetooth device 110 may be performed by the communication unit 220 . A 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 may be performed by the second communication unit 330 . A 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 store the address of the searched Bluetooth device 110.

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

In step 1320, the gateway 120 may search for resources of the Bluetooth device 110 and store information of the searched resources.

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

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

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

A prefix may indicate a route to a node within a Bluetooth network.

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

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

Step 1330 may correspond to step 820 described above with reference to FIG. 8 . In other words, step 820 may include steps 1320 and 1330 .

Steps 1340, 1350, 1355, 1360, 1365, 1370, 1380 and 1390 below may correspond to each of step 730 described above with reference to FIG. 7 and step 830 described above with reference to FIG. there is.

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

The request message may be a CoAP request message.

The gateway 120 may search the address of the Bluetooth device 110, which is the destination of the request message, using the URI-path of the request message.

In step 1350, when the Bluetooth connection with the Bluetooth device 110, which is the destination of the request message, is not established, the processor 310 of the gateway 120 establishes a connection between the gateway 120 and the Bluetooth device 110. can make it To establish a Bluetooth connection, the gateway 120 may transmit a CONNECT_REQ message to the Bluetooth device 110. A connection between the gateway 120 and the Bluetooth device 110 may be established through the CONNECT_REQ message.

In step 1355, the processing unit 310 of the gateway 120 may remove the field of the request message. Processing unit 310 of gateway 120 may remove 1) URI-host, 2) URI-port, 3) prefix from URI-path and 4) Bluetooth device identifier from URI-path from the request message, IP headers and UDP headers can be removed from

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

In step 1365, the processor 310 of the gateway 120 may store information required to deliver a response message to the request message. The processor 310 of the gateway 120 may store the address and port number of the external device 610 that is the source of the request message. In addition, the gateway 120 may store the token field and 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.

In step 1380, upon receiving the response message, the processing unit 310 of the gateway 120 refers to the stored address of the external device 610, the port number of the external device 610, the token field, and the MID field for the response message. The destination of the external device 610 can be identified.

In step 1390, the gateway 120 may transfer 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 a request from the Bluetooth device 110. Through the gateway 120, the external device 610 may provide a response to a request from the Bluetooth device 110.

In an embodiment, transmission and reception of messages of the Bluetooth device 110 may be performed by the communication unit 220 . A 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 may be performed by the second communication unit 330 . A message transmitted by the gateway 120 may be generated by the processing unit 310 .

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

Steps 1410, 1420, 1430, 1440, 1450, 1460, 1470 and 1480 below may correspond to each of step 730 described above with reference to FIG. 7 and step 830 described above with reference to FIG. there is.

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

The request message may be a CoAP request message.

The gateway 120 may search the address of the external device 610, which is the destination of the request message, using the URI-path 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. Processing unit 310 of gateway 120 may extract 1) URI-Host and 2) URI-Port from the request message. Processing unit 310 of gateway 120 may remove 1) URI-Host and 2) URI-Port from the request message.

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

In step 1440, the gateway 120 may transfer the request message to the external device 610.

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

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

In step 1470, upon receiving the response message, the processing unit 310 of the gateway 120 stores the stored token field, the stored MID field, the stored destination IP address, the stored port number, the stored Bluetooth device identifier of the Bluetooth device 110, and The Bluetooth device 110, which is the destination of the response message, may be identified by referring to the stored address of the Bluetooth device 110.

In step 1480, the gateway 120 may transfer the response message to the Bluetooth device 110.

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

Depending on the operating mode of the Bluetooth device 110, a case may occur in which the Bluetooth device 110 searches for the gateway 120 instead of the gateway 120 searching for the Bluetooth device 110. In the embodiment, a process for the Bluetooth device 110 to search for the gateway 120 will be described.

The Bluetooth device 110 may be a Bluetooth enabled sensor node. In addition, the Bluetooth device 110 may be an IoT device and may be a BLE device supporting CoAP.

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

In an embodiment, generation of the message of the gateway 120 may be performed by the processing unit 310 of the gateway 120 . Message transmission and reception of the gateway 120 may be performed by the first communication unit 320 of the gateway 120 . Generation of the message of the Bluetooth device 110 may be performed by the processing unit 210 of the Bluetooth device 110. Message transmission and reception 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 that supports CoAP capable of communication 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. "gw" in the request message may be an example of a string of URI-paths indicating that it is a gateway node.

A gateway 120 within communication range may receive the broadcast message.

In step 1520, the gateway 120 receiving the broadcast message may generate a response message to the broadcast. The gateway 120 may transmit 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" message.

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

The "CoAP 2.05 Content" message may include information about the gateway 120 itself, and may include a URI-path enabling the Bluetooth device 110 to be registered.

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. can

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

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

The Bluetooth device 110 may search for the gateway 120 .

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

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

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

The broadcast message may be a message for notifying that the gateway 120 supporting communicable CoAP exists. The broadcast message may indicate that the gateway 120 is a Bluetooth node supporting 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 (put) /gw" message.

A Bluetooth device 110 within a communication range may receive a broadcast message.

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

As mentioned above, the Bluetooth device 110 can observe the broadcast message. Upon receiving the broadcast message including the CoAP message, the Bluetooth device 110 may discover the gateway 120 that broadcast the broadcast message.

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

When the Bluetooth device 110 discovers the gateway 120 according to the embodiment described above with reference to FIG. 15 or 16, the Bluetooth device 110 may register itself with the gateway 120. there is.

Step 710 described above with reference to FIG. 7 may include steps 1710 , 1720 and 1730 . Also, steps 1710, 1720, and 1730 may 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. 16 .

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

At 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 amount of time.

To establish a communication channel, the Bluetooth device 110 may transmit a CONNECT_REQ message to the gateway 120.

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

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

In addition, when the size of the data message is larger than a predetermined second value, a blockwise transfer function of CoAP may be used.

The payload of the data message may include information about the Bluetooth device 110. Also, the payload may include a resource path of the Bluetooth device 110.

Step 1720 may include steps 1721 and 1722.

In step 1731 , the Bluetooth device 110 may transmit a “CoAP POST (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.

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

In step 1740, the gateway 120 may transmit a response message to the data message to the Bluetooth device 110. The response message may indicate that information about the Bluetooth device 110 is registered in 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 about the Bluetooth device 110 is recorded. In the "CoAP 2.01, Location: /gw/ble/001" message, "/gw/ble/001", a value of the "Location" option, may represent a path where information about the Bluetooth device 110 is recorded.

As described above, in order to register the Bluetooth device 110 with the gateway 120, the Bluetooth device 110 sends a data message including information about the Bluetooth device 110 and a resource path of the Bluetooth device 110 to the gateway ( 120), and a response message including a route in which information about the Bluetooth device 110 is recorded may be received from the gateway 120.

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 its own resources with the gateway 120 . Resources can contain functions and properties. Also, the Bluetooth device 110 may register a plurality of resources with the gateway 120 .

The Bluetooth device 110 may register a resource with the gateway 120 using the path in which information about the Bluetooth device 110 obtained in step 1740 described above with reference to FIG. 17 is recorded.

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

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

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

When the size of the resource registration message is larger than a predetermined first value, the resource registration message may be divided into several sub-messages in Bluetooth L2, and the divided sub-messages may be transmitted.

In addition, when the size of the resource registration message is larger than a predetermined second value, a blockwise transmission function of CoAP may be used.

The payload of the resource registration message may include a path in which information about the Bluetooth device 110 is recorded, and may include information about resources of the Bluetooth device 110. A resource may be plural. A payload of the resource registration message may include information on a plurality of resources.

Step 1810 may include steps 1811 and 1812 .

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

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

<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 resources of the Bluetooth device 110.

In step 1812, the Bluetooth device 110 may transmit 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 transmit a response message to the resource registration message to the Bluetooth device 110. The response message may be transmitted in the form of an LL data packet.

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

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

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

As described above, the Bluetooth device 110 may register a resource with the gateway 120 using a path in which 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, CoAP may be replaced with MQ Telemetry Transport (MQTT).

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

The application layer can provide services by using the MQTT standard without directly using the complicated procedure and standard of Bluetooth.

The contents of CoAP described above with reference to the embodiments may be applied to MQTT. For example, at least one program executed by the processing unit 210 may include an MQTT layer code, 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 gateway 120, CoAP may be replaced with MQTT. UDP can be replaced by TCP. The contents of CoAP described above with reference to the embodiments may be applied to MQTT. In addition, the contents of UDP described above with reference to the embodiments may be applied to TCP. For example, at least one program executed by the processing unit 310 may include an MQTT layer code, 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, CoAP may be replaced with MQTT. UDP can be replaced by TCP. The contents of CoAP described above with reference to the embodiments may be applied to MQTT. In addition, the contents of UDP described above with reference to the embodiments may be applied to TCP.

Basically, the communication protocol may be configured to play a role in one of the Open Systems Interconnection (OSI) 7 layers. When a protocol is applied to the system, a protocol suitable for each layer may be selected, and a protocol stack may be configured by the 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 may also follow this structure.

The CoAP protocol corresponds to the session layer and the application layer. According to the characteristics of the physical layer, logical layer, and CoAP protocol of Bluetooth, the logical layer and CoAP protocol of the Bluetooth device 110 may be directly connected without network layer and transport layer protocols. Efficiency and compatibility can be ensured by direct connection. Also, the networking function of the Bluetooth device 110 may be performed through cooperation with the gateway 120 .

22 illustrates an advertising channel frame format according to an example.

The advertising channel frame format 2200 includes a preamble 2210, an access address 2220, and an advertising channel PDU header Unit) Header (2230), Advertising Address (2240), CoAP Header/Options (2250), CoAP Payload (2260) and Cyclic Redundancy Check (Cyclic Redundancy Check) ;CRC) 2270.

The advertising channel frame format 2200 may be used as a format of a message related to an advertising channel among the aforementioned messages.

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

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

The data channel frame format 2300 may be used as a format of a message related to a data channel among the aforementioned messages.

The devices described above may be implemented as hardware components, software components, and/or a combination of hardware components and software components. For example, devices and components described in the embodiments may include, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA), It may be implemented using one or more general purpose or special purpose computers, such as a programmable logic unit (PLU), microprocessor, or any other device capable of executing and responding to instructions. A processing device may run an operating system (OS) and one or more software applications running on the operating system. A processing device may also access, store, manipulate, process, and generate data in response to execution of software. For convenience of understanding, there are cases in which one processing device is used, but those skilled in the art will understand that the processing device includes a plurality of processing elements and/or a plurality of types of processing elements. It can be seen that it can include. For example, a processing device may include a plurality of processors or a processor and a controller. Other processing configurations are also possible, such as parallel processors.

Software may include a computer program, code, instructions, or a combination of one or more of the foregoing, which configures a processing device to operate as desired or processes independently or collectively. The device can be commanded. Software and/or data may be any tangible machine, component, physical device, virtual equipment, computer storage medium or device, intended to be interpreted by or provide instructions or data to a processing device. , or may be permanently or temporarily embodied in a transmitted signal wave. Software may be distributed on networked computer systems and stored or executed in a distributed manner. Software and data may be stored on one or more computer readable media.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer readable medium. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination. Program commands recorded on the medium may be specially designed and configured for the embodiment or may be known and usable to those skilled in computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CD-ROMs and DVDs, and magnetic media such as floptical disks. - includes hardware devices specially configured to store and execute program instructions, such as magneto-optical media, and ROM, RAM, flash memory, and the like. Examples of program instructions include high-level language codes that can be executed by a computer using an interpreter, as well as machine language codes such as those produced by a compiler. 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.

As described above, although the embodiments have been described with limited examples and drawings, those skilled in the art can make various modifications and variations from the above description. For example, the described techniques may be performed in an order different from the method described, and/or components of the described system, structure, device, circuit, etc. may be combined or combined in a different form than the method described, or other components may be used. Or even if it is replaced or substituted by equivalents, appropriate results can be achieved.

110: Bluetooth device
120: gateway
610: external device

Claims (20)

a processing unit that executes at least one program; and
Communication unit that performs Bluetooth communication
including,
The at least one program includes ATT (Attribute protocol) layer code, GATT (Generic Attribute Profile) layer code, GAP (Generic Access Profile) layer code, CSP (CoAP Support Profile) layer code, CoAP (Constrained Application Protocol ) layer and the code of the Logical Link Control and Adaptation Protocol (L2CAP) layer,
The ATT layer, the GATT layer, the GAP layer, the CSP layer, and the CoAP layer are higher layers of the L2CAP layer,
wherein the CoAP layer searches for a CoAP Bluetooth device, transmits a CoAP request message, receives the CoAP request message, and transmits a response message to the CoAP request. According to claim 1,
Wherein the at least one program includes a CoAP support profile. According to claim 2,
The CSP enables the Bluetooth device to discover that the Bluetooth device supports the CoAP function through GATT and ATT. According to claim 1,
The Bluetooth device obtains 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. According to claim 1,
The Bluetooth device observes a broadcast message, and discovers a gateway that broadcasts the broadcast message upon receiving the broadcast message. According to claim 1,
The Bluetooth device transmits a data message including information about the Bluetooth device and a path of a resource of the Bluetooth device to the gateway to register the Bluetooth device with the gateway, and sends a path in which the information about the Bluetooth device is recorded. A Bluetooth device receiving a response message including a response message from the gateway. According to claim 6,
The Bluetooth device registers a resource of the Bluetooth device with the gateway using the route. performed by a Bluetooth device,
registering the Bluetooth device discovered by the gateway with the gateway; and
performing communication through a gateway function provided by the gateway;
including,
The protocol stack of the Bluetooth device includes an ATT layer, a GATT layer, a GAP layer, a CSP layer, a CoAP layer, and an L2CAP layer,
The ATT layer, the GATT layer, the GAP layer, the CSP layer, and the CoAP layer are higher layers of the L2CAP layer,
wherein the CoAP layer searches for a CoAP Bluetooth device, transmits a CoAP request message, receives the CoAP request message, and transmits a response message to the CoAP request. According to claim 8,
Registering the resource of the Bluetooth device with the gateway
A communication method further comprising a. a processing unit that executes at least one program; and
Communication unit that performs Bluetooth communication
including,
The at least one program includes ATT layer code, GATT layer code, GAP layer code, MQTT layer code, and L2CAP layer code,
The ATT layer, the GATT layer, the GAP layer, and the MQTT layer are upper layers of the L2CAP layer. a processing unit that executes at least one program;
A first communication unit for Bluetooth communication; and
Second communication unit for linking with the Internet
including,
The at least one program includes a code for the first communication unit,
The code for the first communication unit includes a code of a first CoAP layer and a code of an L2CAP layer,
The first CoAP layer is a layer immediately above the L2CAP layer,
The protocol stack of the second communication unit includes a Wi-Fi or Ethernet layer, an IP layer, a UDP layer, and a second CoAP layer,
The at least one program includes a proxy module,
The proxy module is a layer above the second CoAP layer,
The proxy module enables communication between the Bluetooth device and a device connected through the second communication unit by mapping an address of the Bluetooth device connected through the first communication unit to a URI-path inside the gateway. delete According to claim 11,
The first communication unit receives a CoAP request message from a Bluetooth device,
The processing unit removes a URI-host and a URI-port from the request message of the CoAP, sets an IP header and a UDP header in the request message,
The second communication unit transfers the request message in which the IP header and the UDP header are set to an external device. According to claim 11,
The second communication unit receives a CoAP request message from an external device,
The processing unit removes a URI-host, a URI-port, a prefix from a URI-path, a Bluetooth device identifier from a URI-path, an IP header, and a UDP header from the request message of the CoAP;
The first communication unit transfers the request message from which the URI-host, the URI-port, the prefix, the Bluetooth device identifier, the IP header, and the UDP header are removed to the Bluetooth device. According to claim 11,
The gateway detects 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. According to claim 11,
the gateway may observe the broadcast message;
wherein the gateway discovers the Bluetooth device that broadcast the broadcast message upon receiving the broadcast message including the virtual CoAP Ping response message. According to claim 11,
The gateway transmits a connection request message to the Bluetooth device, receives a response message including a path of a resource of the Bluetooth device from the Bluetooth device, transmits a material message including the path to the Bluetooth device, and A gateway for receiving a response message including route information from the Bluetooth device. delete delete a processing unit that executes at least one program;
A first communication unit for Bluetooth communication; and
Second communication unit for linking with the Internet
including,
The at least one program includes a code for the first communication unit,
The code for the first communication unit includes a code of a first MQTT layer and a code of an L2CAP layer,
The first MQTT layer is a layer immediately above the L2CAP layer,
The protocol stack of the second communication unit includes a Wi-Fi or Ethernet layer, an IP layer, a TCP layer, and a second MQTT layer.

Images