WO2018131929A1 - Method and apparatus for controlling apparatus by using bluetooth technology - Google Patents

Abstract

The present invention relates to a method and an apparatus for controlling, by a client, a server via Bluetooth. The present invention provides a method and an apparatus that form a Bluetooth low energy (LE) connection with a server; transmit, to the server, a first write request message requesting writing of a control point characteristic for an instruction of a specific operation; receive a first write response message in response to the write request message; and receive, from the server, a first instruction message for instructing whether to perform the specific operation, wherein the first write request message includes a first operation code indicating the specific operation and a first effective time indicating a time of performing the specific operation.

Description

Method and device for controlling device using Bluetooth technology

The present invention relates to a method and apparatus for controlling a device using Bluetooth, which is a short-range technology in a wireless communication system, and more particularly, to a method and apparatus for controlling a server by a client using Bluetooth technology.

Bluetooth is a short-range wireless technology standard that can transmit and receive data by wirelessly connecting various devices in a short distance. When performing wireless communication between two devices using Bluetooth communication, a user performs a procedure of searching for a Bluetooth device and requesting a connection. do. In the present invention, the device may mean an apparatus and an apparatus.

In this case, the user may perform a connection after searching for the Bluetooth device according to the Bluetooth communication method to use using the Bluetooth device.

The Bluetooth communication method includes a basic rate / enhanced data rate (BR / EDR) method and a low energy (LE) method, which is a low power method. The BR / EDR scheme may be referred to as Bluetooth Classic. The Bluetooth classic includes Bluetooth technology that has been adopted since Bluetooth 1.0 using Basic Rate and Bluetooth technology that has used Enhanced Data Rate supported since Bluetooth 2.0.

Bluetooth Low energy (hereinafter referred to as Bluetooth LE) is applied from Bluetooth 4.0 and consumes less power and can provide hundreds of kilobytes (KB) of information reliably. Protocol is used to exchange information between devices This Bluetooth LE method can reduce energy consumption by reducing header overhead and simplifying operation.

Some Bluetooth devices do not have a display or a user interface. The complexity of connection / management / control / disconnection between various kinds of Bluetooth devices and similarly applied Bluetooth devices is increasing.

In addition, Bluetooth can achieve a relatively high speed at a relatively low power, low cost, but the transmission distance is generally limited to a maximum of 100m, it is suitable for use in a limited space.

It is an object of the present invention to provide a method and apparatus for controlling a device using Bluetooth technology.

It is also an object of the present invention to provide a method and apparatus for a client to control the server so that the server performs a specific operation.

Further, an object of the present invention is to provide a method and apparatus for performing a specific operation instructed during or within an operation time when an operation time for a server to perform a specific operation from a client is set.

Another object of the present invention is to provide a method and an apparatus for defining an error message according to each service when a server cannot perform a specific operation instructed by a client.

The technical problems to be achieved in the present specification are not limited to the technical problems mentioned above, and other technical problems not mentioned above will be clearly understood by those skilled in the art from the following description. Could be.

The present invention provides a method and apparatus for a client to control a server in Bluetooth to solve the above problems.

Specifically, the method for the client to control the server according to an embodiment of the present invention comprises the steps of forming a Bluetooth Low Energy (LE) connection with the server; Sending a first write request message to the server requesting writing of a control point characteristic for an indication of a particular operation; Receiving a first write response message in response to the write request message; And receiving a first indication message for indicating whether to perform the specific operation from the server, wherein the first write request message includes a first operation code indicating the specific operation and an execution time of the specific operation. It includes a first valid time indicating.

Also, in the present invention, when the specific operation is successfully performed, the first indication message includes a response code indicating the success of the specific operation.

In addition, in the present invention, when failing to perform the specific operation, the instruction message includes an error code indicating the cause of the failure.

Further, in the present invention, when the error code indicates no support of the first valid time, the indication message further includes a second valid time supported by the server.

Further, in the present invention, when the first valid time is greater than the maximum execution time of the specific operation, the second valid time indicates the maximum execution time, and the first valid time is greater than the minimum execution time of the specific operation. If small, the second valid time represents the minimum execution time.

The present invention also provides a method comprising: sending a second write request message requesting writing of the control point characteristic to the server to instruct cancellation of the specific operation; Receiving a second write response message in response to the second write request message; And receiving a second indication message indicating whether to cancel the specific operation from the server, wherein the second write request message includes a second operation code indicating cancellation of the specific operation.

In addition, in the present invention, when the specific operation is performed with another device, the first write request message further includes a device ID for identifying the counterpart device.

In addition, the present invention, the communication unit for communicating with the outside by wireless or wired; A memory for storing data; And a processor operatively connected to the communication unit, wherein the processor forms a first Bluetooth Low Energy (LE) connection with a server and requests the server to write control point characteristics for indicating a specific operation. Transmit a request message, receive a first write response message in response to the write request message, and receive a first indication message indicating whether to perform the specific operation from the server, wherein the first write request message is received; Provides a terminal including a first operation code indicating the specific operation and a first valid time indicating the execution time of the specific operation.

There is an effect that the client can control the operation of the server device by using the Bluetooth technology according to an embodiment of the present invention.

In addition, according to the method for controlling a server by a client according to an embodiment of the present invention, the client sets a specific operation and an operation time for performing a specific operation on the server, thereby reducing a waiting time for determining whether the operation is performed. It can be effective.

In addition, when the server fails the operation instructed by the client, the client can quickly recognize whether the operation failed.

In addition, by defining an error code indicating a cause of failure of the operation classified by service and cause, the client can clearly recognize the cause of failure.

Effects obtained in the present specification are not limited to the above-mentioned effects, and other effects not mentioned above may be clearly understood by those skilled in the art from the following description. will be.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings included as part of the detailed description to provide a better understanding of the invention provide embodiments of the invention, and together with the description, describe the technical features of the invention.

1 is a schematic diagram illustrating an example of a wireless communication system using the Bluetooth low power energy technology proposed in the present specification.

2 is a diagram illustrating an example of an internal block diagram of a device capable of implementing the methods proposed herein.

FIG. 3 is a diagram illustrating an example of a Bluetooth communication architecture to which the methods proposed herein may be applied.

4 is a diagram illustrating an example of a structure of a GATT (Generic Attribute Profile) of Bluetooth low power energy.

5 is a flowchart illustrating an example of a connection procedure method in a Bluetooth low power energy technology to which the present invention can be applied.

6 is a view briefly illustrating a method for controlling a connection of another device through a control device proposed in the present specification.

7 is a diagram illustrating an example of a profile structure for providing a service for controlling a device proposed in the present specification.

8 to 11 are diagrams illustrating an example of a method and data format for controlling a server by a client proposed in the present specification.

12 is a flowchart illustrating an example of a method for canceling an operation instructed by a client proposed in the specification.

13 is a flowchart illustrating an example of a method for controlling a server by a client proposed in the present specification.

The above objects, features and advantages of the present invention will become more apparent from the following detailed description taken in conjunction with the accompanying drawings. However, the present invention may be modified in various ways and may have various embodiments. Hereinafter, specific embodiments will be illustrated in the drawings and described in detail. Like numbers refer to like elements throughout. In addition, when it is determined that the detailed description of the known function or configuration related to the present invention may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

Hereinafter, a method and apparatus related to the present invention will be described in more detail with reference to the drawings. The suffixes "module" and "unit" for components used in the following description are given or used in consideration of ease of specification, and do not have distinct meanings or roles from each other.

1 is a schematic diagram illustrating an example of a wireless communication system using the Bluetooth low power energy technology proposed in the present specification.

The wireless communication system 100 includes at least one server device 120 and at least one client device 110.

The server device and the client device perform Bluetooth communication using Bluetooth Low Energy (BLE) technology.

First, compared to Bluetooth Basic Rate / Enhanced Data Rate (BR / EDR) technology, BLE technology has a relatively small duty cycle, enables low-cost production, and significantly reduces power consumption through low data rates. If you use a coin cell battery, it can operate for more than a year.

In addition, the BLE technology simplifies the connection procedure between devices, and the packet size is smaller than that of the Bluetooth BR / EDR technology.

In BLE technology, (1) the number of RF channels is 40, (2) the data rate supports 1Mbps, (3) the topology is a scatternet structure, (4) latency is 3ms, and (5) maximum current Is less than 15mA, (6) output power is less than 10mW (10dBm), and (7) is mainly used in applications such as mobile phones, watches, sports, healthcare, sensors, device control.

The server device 120 may operate as a client device in relation to other devices, and the client device may operate as a server device in relation to other devices. That is, in the BLE communication system, any one device may operate as a server device or a client device, and if necessary, operate as a server device and a client device.

The server device 120 may include a data service device, a slave device device, a slave, a server, a conductor, a host device, a gateway, and a sensing device. (Sensing Device), a monitoring device (monitoring device) and the like.

The client device 110 may be a master device, a master, a client, a member, a sensor device, a sink device, a collector, a third device, a fourth device, or the like. Can be expressed.

The server device and the client device correspond to the main components of the wireless communication system, and the wireless communication system may include other components in addition to the server device and the client device.

When the server device receives data from the client device and directly communicates with the client device, and receives a data request from the client device, the server device provides the data to the client device through a response.

In addition, the server device sends a notification message and an indication message to the client device to provide data information to the client device. In addition, when the server apparatus transmits an instruction message to the client apparatus, the server apparatus receives a confirmation message corresponding to the instruction message from the client.

In addition, the server device provides data information to the user through a display unit or receives a request input from the user through a user input interface in the process of transmitting and receiving notification, instruction, and confirmation messages with the client device. can do.

In addition, the server device may read data from a memory unit or write new data to a corresponding memory in a process of transmitting and receiving a message with the client device.

In addition, one server device may be connected to a plurality of client devices, and may be easily reconnected (or connected) with client devices by using bonding information.

The client device 120 refers to a device for requesting data information and data transmission from a server device.

The client device receives data from the server device through a notification message, an instruction message, and the like, and when receiving an instruction message from the server device, sends a confirmation message in response to the instruction message.

Similarly, the client device may provide information to the user through an output unit or receive an input from the user through an input unit in the process of transmitting and receiving messages with the server device.

In addition, the client device may read data from a memory or write new data to a corresponding memory in a process of transmitting and receiving a message with the server device.

Hardware components such as an output unit, an input unit, and a memory of the server device and the client device will be described in detail with reference to FIG. 2.

In addition, the wireless communication system may configure Personal Area Networking (PAN) through Bluetooth technology. For example, in the wireless communication system, by establishing a private piconet between devices, files, documents, and the like can be exchanged quickly and securely.

2 shows an example of an internal block diagram of a device that can implement the methods proposed herein.

As illustrated in FIG. 2, the server device may include an output unit 111, a user input interface 112, a power supply unit 113, a processor 114, and a memory unit. , 115), a Bluetooth interface 116, another communication interface 117, and a communication unit (or a transceiver unit 118).

The output unit 111, the input unit 112, the power supply unit 113, the processor 114, the memory 115, the Bluetooth interface 116, the other communication interface 117 and the communication unit 118 are proposed herein. It is functionally linked to perform the method.

In addition, the client device may include a display unit 121, a user input interface 122, a power supply unit 123, a processor 124, a memory unit 125, and a Bluetooth interface. (Bluetooth Interface) 126 and a communication unit (or a transceiver unit 127).

The output unit 121, the input unit 122, the power supply unit 123, the processor 124, the memory 125, the Bluetooth interface 126, and the communication unit 127 are used to perform the method proposed in this specification. Functionally connected

The Bluetooth interface 116, 126 refers to a unit (or module) capable of transmitting data or request / response, command, notification, indication / confirmation message, etc. between devices using Bluetooth technology.

The memories 115 and 125 are units implemented in various types of devices and refer to units in which various kinds of data are stored.

The processor 114, 124 refers to a module that controls the overall operation of the server device or the client device, and controls to process a message request and a received message through a Bluetooth interface and another communication interface.

The processors 114 and 124 may be represented by a controller, a control unit, a controller, or the like.

The processors 114 and 124 may include application-specific integrated circuits (ASICs), other chipsets, logic circuits, and / or data processing devices.

The processor 114, 124 controls the communication unit to receive an advertising message from a server device, transmits a scan request message to the server device, and scans in response to the scan request from the server device. The communication unit controls the communication unit to receive a scan response message, and controls the communication unit to transmit a connect request message to the server device for establishing a Bluetooth connection with the server device.

The processor 114 and 124 may also read or write data from the server device using a property protocol after a Bluetooth LE connection is formed through the connection procedure. To control.

The memories 115 and 125 may include read-only memory (ROM), random access memory (RAM), flash memory, memory cards, storage media, and / or other storage devices.

The communication unit 118 and 127 may include a baseband circuit for processing a radio signal. When the embodiment is implemented in software, the above-described technique may be implemented as a module (process, function, etc.) for performing the above-described function. The module may be stored in memory and executed by a processor.

The memories 115 and 125 may be inside or outside the processors 114 and 124, and may be connected to the processors 114 and 124 by various well-known means.

The output units 111 and 121 refer to modules for providing device status information and message exchange information to a user through a screen.

The power supply unit (power supply unit 113, 123) refers to a module for supplying power required for the operation of the components by receiving the external power, the internal power under the control of the controller.

As we saw earlier, BLE technology has a small duty cycle, and the low data rate can significantly reduce power consumption.

The input units 112 and 122 refer to a module that provides a user's input to the controller like a screen button so that the user can control the operation of the device.

3 is a diagram illustrating an example of a Bluetooth communication architecture to which the methods proposed herein may be applied.

Referring to FIG. 3, (a) of FIG. 3 shows an example of a protocol stack of Bluetooth Basic Rate (BR) / Enhanced Data Rate (EDR), and (b) shows a protocol stack of Bluetooth Low Energy (LE). An example is shown.

Specifically, as shown in (a) of FIG. 3, the Bluetooth BR / EDR protocol stack has an upper controller stack 10 and a lower controller stack based on a host controller interface HCI 18. It may include a host stack (20) of.

The host stack (or host module) 20 refers to a wireless transceiver module for receiving a 2.4 GHz Bluetooth signal and hardware for transmitting or receiving a Bluetooth packet. Control and perform actions.

The controller stack 10 may include a PHY layer 12, a link controller layer 14, and a link manager layer 16.

The PHY layer 12 is a layer that transmits and receives a 2.4 GHz radio signal. When PFS layer (Gaussian Frequency Shift Keying) modulation is used, the PHY layer 12 may transmit data by hopping 79 RF channels.

The link controller layer 14 is responsible for transmitting a digital signal, selects a channel sequence hopping 1400 times per second, and transmits a 625us length time slot for each channel.

The link manager layer 16 controls the overall operation (link setup, control, security) of the Bluetooth connection by using a link manager protocol (LMP).

The link manager layer 16 may perform the following functions.

ACL / SCO logical transport, logical link setup and control

Detach: Stops the connection and tells the other device why.

-Perform power control and role switch.

-Perform Security (authentication, pairing, encryption) function.

The host controller interface layer 18 provides an interface between the host module and the controller module so that the host can provide commands and data to the controller, and the controller can provide events and data to the host.

The host stack (or host module) 20 may include a logical link control and adaptation protocol (L2CAP, 21), an attribute protocol (Protocol, 22), a generic attribute profile (GATT, 23), and a generic access profile. Profile, GAP, 24), BR / EDR profile 25.

The logical link control and adaptation protocol (L2CAP) 21 may provide one bidirectional channel for transmitting data to a specific protocol or profile.

The L2CAP 21 may multiplex various protocols, profiles, etc. provided by a higher layer of Bluetooth.

L2CAP of Bluetooth BR / EDR uses dynamic channel, supports protocol service multiplexer, retransmission, streaming mode, and provides segmentation, reassembly, per-channel flow control, and error control.

The generic attribute profile (GATT) 23 may be operable as a protocol describing how the attribute protocol 22 is used in the construction of services. For example, the general attribute profile 23 may be operable to specify how ATT attributes are grouped together into services, and may be operable to describe features associated with the services.

Thus, the generic attribute profile 23 and the attribute protocol ATT 22 may use features to describe the state and services of a device and to describe how features relate to each other and how they are used.

The attribute protocol 22 and the BR / EDR profile 25 define a service profile using Bluet BR / EDR and an application protocol for sending and receiving these data, and the Generic Access Profile. , GAP, 24) defines device discovery, connectivity, and security levels.

As shown in FIG. 3B, the Bluetooth LE protocol stack is a controller stack 30 operable to handle timing-critical radio interface and a host operable to process high level data. It contains a stack (Host stack, 40).

First, the controller stack 30 may be implemented using a communication module that may include a Bluetooth radio, for example, a processor module that may include a processing device such as a microprocessor.

The host stack may be implemented as part of an OS running on a processor module, or as an instance of a package on the OS.

In some instances, the controller stack and the host stack can be operated or executed on the same processing device in the processor module.

The controller stack 30 includes a physical layer (PHY) 32, a link layer 34, and a host controller interface 36.

The physical layer (PHY) 32 is a layer that transmits and receives a 2.4 GHz radio signal and uses GFSK (Gaussian Frequency Shift Keying) modulation and a frequency hopping technique composed of 40 RF channels.

The link layer 34, which transmits or receives a Bluetooth packet, creates a connection between devices after performing advertising and scanning functions using three advertising channels, and generates up to 257 bytes of data packets through 37 data channels. Provides the ability to send and receive.

The host stack includes a logical link control and adaptation protocol (L2CAP, 41), a security manager (SM, 42), an attribute protocol (Attribute Protocol, ATT, 43), a generic attribute profile (GATT, 44). It may include a Generic Access Profile (45), LE Profile (46). However, the host stack 40 is not limited to this and may include various protocols and profiles.

The host stack uses L2CAP to multiplex the various protocols, profiles, etc. provided by Bluetooth.

First, L2CAP (Logical Link Control and Adaptation Protocol) 41 may provide one bidirectional channel for transmitting data to a specific protocol or profile.

The L2CAP 41 may be operable to multiplex data among higher layer protocols, segment and reassemble packages, and manage multicast data transmission.

In Bluetooth LE, three fixed channels (one for the signaling channel, one for the Security Manager, and one for the Attribute protocol) are used by default. And, if necessary, the dynamic channel may be used.

On the other hand, BR / EDR (Basic Rate / Enhanced Data Rate) uses dynamic channels by default and supports protocol service multiplexer, retransmission, and streaming mode.

The SM (Security Manager) 42 authenticates the device and is in charge of overall security of Bluetooth LE as a protocol for providing key distribution.

Attribute Protocol (ATT) 43 defines a rule for accessing data of a counterpart device in a server-client structure. ATT has six message types (Request, Response, Command, Notification, Indication, Confirmation).

① Request and Response message: The Request message is a message for requesting and delivering specific information from the client device to the server device, and the Response message is a response message for the request message, which can be used for transmission from the server device to the client device. Say.

② Command message: A message sent mainly from the client device to the server device to indicate a command of a specific operation. The server device does not transmit a response to the command message to the client device.

③ Notification message: This message is sent from the server device to the client device for notification such as an event. The client device does not transmit a confirmation message for the notification message to the server device.

④ Indication and Confirm message: This message is transmitted from the server device to the client device for notification such as an event. Unlike the notification message, the client device transmits a confirmation message for the Indication message to the server device.

The generic access profile 45 is a newly implemented layer for Bluetooth LE technology and is used to control role selection and multi-profile operation for communication between Bluetooth LE devices.

In addition, the general access profile 45 is mainly used for device discovery, connection creation, and security procedures, and defines a method of providing information to a user, and defines the type of an attribute as follows.

① Service: Defines the basic behavior of the device with a combination of behaviors related to data.

② Include: Define the relationship between services

③ Characteristics: data value used in service

Behavior: A computer readable format defined by UUID (Universal Unique Identifier, value type).

The LE profile 46 is mainly applied to a Bluetooth LE device as profiles having a dependency on GATT. The LE profile 46 may include, for example, Battery, Time, FindMe, Proximity, Time, and the like. Details of GATT-based Profiles are as follows.

① Battery: How to exchange battery information

② Time: How to exchange time information

③ FindMe: Provides alarm service according to distance

④ Proximity: How to exchange battery information

⑤ Time: How to exchange time information

The generic attribute profile GATT 44 may be operable as a protocol describing how the attribute protocol 43 is used in the construction of services. For example, the generic attribute profile 44 may be operable to specify how ATT attributes are grouped together into services, and may be operable to describe features associated with the services.

Thus, the generic attribute profile 44 and the attribute protocol (ATT, 43) may use features to describe the state and services of a device, and how features relate to each other and how they are used.

In the following, the procedure of the Bluetooth Low Energy (BLE) technology will be briefly described.

The BLE procedure may be classified into a device filtering procedure, an advertising procedure, a scanning procedure, a discovery procedure, a connecting procedure, and the like.

device Filter  Device Filtering Procedure

The device filtering procedure is a method for reducing the number of devices performing a response to a request, an indication, a notification, and the like in the controller stack.

When all devices receive a request, it is unnecessary to respond to it, so the controller stack can control the number of requests sent, reducing power consumption in the BLE controller stack.

The advertising device or scanning device may perform the device filtering procedure to limit the device receiving the advertising packet, scan request or connection request.

Here, the advertising device refers to a device that transmits an advertising event, that is, performs an advertisement, and is also referred to as an advertiser.

The scanning device refers to a device that performs scanning and a device that transmits a scan request.

In BLE, when the scanning device receives some advertising packets from the advertising device, the scanning device should send a scan request to the advertising device.

However, if a device filtering procedure is used so that a scan request transmission is unnecessary, the scanning device may ignore the advertisement packets transmitted from the advertisement device.

The device filtering procedure may also be used in the connection request process. If device filtering is used in the connection request process, it is not necessary to transmit a response to the connection request by ignoring the connection request.

Advertising Procedure

The advertising device performs an advertising procedure to perform a non-directional broadcast to the devices in the area.

Here, non-directional broadcast refers to broadcast in all directions rather than broadcast in a specific direction.

In contrast, directional broadcasts refer to broadcasts in a particular direction. Non-directional broadcasts occur without a connection procedure between an advertising device and a device in a listening (or listening) state (hereinafter referred to as a listening device).

The advertising procedure is used to establish a Bluetooth connection with a nearby initiating device.

Alternatively, the advertising procedure may be used to provide periodic broadcast of user data to the scanning devices that are listening on the advertising channel.

In the advertising process, all advertisements (or advertisement events) are broadcast over an advertising physical channel.

The advertising devices may receive a scan request from listening devices that are listening to obtain additional user data from the advertising device. The advertising device transmits a response to the scan request to the device that sent the scan request through the same advertising physical channel as the received advertising physical channel.

Broadcast user data sent as part of an advertisement packet is dynamic data, while scan response data is generally static data.

The advertising device may receive a connection request from the initiating device on the advertising (broadcast) physical channel. If the advertising device used a connectable advertising event and the initiating device was not filtered by the device filtering procedure, the advertising device stops the advertising and enters the connected mode. The advertising device may start advertising again after the connected mode.

Scanning Procedure

The device performing the scanning, i.e., the scanning device, performs a scanning procedure to listen to the non-directional broadcast of the user data from the advertising devices using the advertising physical channel.

The scanning device sends a scan request to the advertising device via the advertising physical channel to request additional data from the advertising device. The advertising device transmits a scan response that is a response to the scan request, including additional data requested by the scanning device over the advertising physical channel.

The scanning procedure can be used while connected to other BLE devices in the BLE piconet.

If the scanning device is in an initiator mode that can receive the broadcasted advertising event and initiate a connection request, the scanning device sends the connection request to the advertising device via the advertising physical channel to the advertising device. You can start a Bluetooth connection with.

When the scanning device sends a connection request to the advertising device, the scanning device stops initiator mode scanning for further broadcast and enters the connected mode.

Discover  Discovery Procedure

Devices capable of Bluetooth communication (hereinafter referred to as "Bluetooth devices") perform an advertisement procedure and a scanning procedure to find devices that are nearby or to be found by other devices within a given area.

The discovery procedure is performed asymmetrically. A Bluetooth device that attempts to find another device around it is called a discovering device and listens for devices that advertise a scannable advertisement event. Bluetooth devices discovered and available from other devices are referred to as discoverable devices, and actively broadcast advertising events so that other devices can scan through an advertising (broadcast) physical channel.

Both the discovering device and the discoverable device may already be connected with other Bluetooth devices in the piconet.

Connecting Procedure

The connection procedure is asymmetric, and the connection procedure requires the other Bluetooth device to perform the scanning procedure while the specific Bluetooth device performs the advertisement procedure.

That is, the advertising procedure can be the goal, so that only one device will respond to the advertising. After receiving the accessible advertising event from the advertising device, the connection may be initiated by sending a connection request to the advertising device via the advertising (broadcast) physical channel.

Next, an operation state of the BLE technology, that is, an advertising state, a scanning state, an initiating state, and a connection state will be briefly described.

Advertising State

The link layer LL enters the advertisement state by the instruction of the host (stack). If the link layer is in the advertisement state, the link layer sends advertisement packet data units (PDUs) in the advertisement events.

Each advertising event consists of at least one advertising PDU, which is transmitted via the advertising channel indexes used. The advertisement event may terminate when the advertisement PDU is transmitted through each of the advertisement channel indexes used, or may terminate the advertisement event earlier when the advertisement device needs to make space for performing another function.

Scanning State

The link layer enters the scanning state by the indication of the host (stack). In the scanning state, the link layer listens for advertising channel indices.

There are two types of scanning states: passive scanning and active scanning, each scanning type being determined by the host.

There is no separate time or advertisement channel index for performing scanning.

During the scanning state, the link layer listens for the advertising channel index during the scanWindow duration. ScanInterval is defined as the interval (interval) between the starting points of two consecutive scan windows.

If there is no scheduling conflict, the link layer must listen for completion of all scan intervals in the scan window as instructed by the host. In each scan window, the link layer must scan a different advertising channel index. The link layer uses all available advertising channel indexes.

When passive scanning, the link layer only receives packets and does not transmit any packets.

When active scanning, the link layer performs listening to rely on the advertising PDU type, which may request advertising PDUs and additional information related to the advertising device from the advertising device.

Initiating State

The link layer enters the initiation state by the indication of the host (stack).

When the link layer is in the initiating state, the link layer performs listening for the advertising channel indexes.

During the initiation state, the link layer listens for the advertising channel index during the scan window period.

Connection state

The link layer enters the connected state when the device performing the connection request, i.e., the initiating device, sends the CONNECT_REQ PDU to the advertising device or when the advertising device receives the CONNECT_REQ PDU from the initiating device.

After entering the connected state, the connection is considered to be created. However, it does not need to be considered to be established at the time the connection enters the connected state. The only difference between the newly created connection and the established connection is the link layer connection supervision timeout value.

When two devices are connected, the two devices act in different roles.

The link layer that performs the master role is called a master, and the link layer that performs the slave role is called a slave. The master controls the timing of the connection event, and the connection event is the point in time when the master and the slave are synchronized.

Hereinafter, the packet defined in the Bluetooth interface will be briefly described. BLE devices use the packets defined below.

Packet Format

The link layer has only one packet format used for both advertisement channel packets and data channel packets.

Each packet consists of four fields: Preamble, Access Address, PDU, and CRC.

When one packet is sent on an advertising physical channel, the PDU will be an advertising channel PDU, and when one packet is sent on a data physical channel, the PDU will be a data channel PDU.

Advertising channel PDU (Advertising Channel PDU )

The advertising channel PDU (Packet Data Unit) has a 16-bit header and payloads of various sizes.

The PDU type field of the advertising channel PDU included in the header indicates a PDU type as defined in Table 1 below.

Advertising PDU (Advertising PDU )

The following advertising channel PDU types are called advertising PDUs and are used in specific events.

ADV_IND: Connectable Non-Oriented Ads Event

ADV_DIRECT_IND: Connectable Directional Advertising Event

ADV_NONCONN_IND: Non-Connectable Non-Oriented Ads Event

ADV_SCAN_IND: Scannable Non-Oriented Ads Event

The PDUs are transmitted at the link layer in the advertisement state and received by the link layer in the scanning state or initiating state.

scanning PDU (Scanning PDU )

The advertising channel PDU type below is called a scanning PDU and is used in the state described below.

SCAN_REQ: Sent by the link layer in the scanning state and received by the link layer in the advertising state.

SCAN_RSP: Sent by the link layer in the advertising state and received by the link layer in the scanning state.

Start PDU (Initiating PDU )

The advertising channel PDU type below is called the initiating PDU.

CONNECT_REQ: Sent by the link layer in the initiating state and received by the link layer in the advertising state.

Data channel PDU (Data Channel PDU )

The data channel PDU has a 16-bit header, payloads of various sizes, and may include a message integrity check (MIC) field.

As described above, the procedure, state, packet format, etc. in the BLE technology may be applied to perform the methods proposed herein.

4 is a diagram illustrating an example of a structure of a GATT (Generic Attribute Profile) of Bluetooth low power energy.

Referring to FIG. 4, a structure for exchanging profile data of Bluetooth low power energy may be described.

In more detail, the GATT (Generic Attribute Profile) defines a method of exchanging data using services and characteristics between Bluetooth LE devices.

In general, a peripheral device (for example, a sensor device) serves as a GATT server, has a definition of services, characteristics, and a central device is a GATT server. It acts as a client.

To read or write data, the GATT client sends a data request to the GATT server, and all transactions begin at the GATT client and receive a response from the GATT server.

The GATT-based operating structure used in the Bluetooth LE is based on Profile, Service, and Characteristic, and may form a vertical structure as shown in FIG. 5.

The profile consists of one or more services, and the service may consist of one or more features or other services.

The service divides data into logical units and may include one or more characteristics or other services. Each service has a 16-bit or 128-bit identifier called the Universal Unique Identifier (UUID).

The characteristic is the lowest unit in the GATT based operation structure. The property contains only one data and has a UUID of 16 bits or 128 bits similar to the service.

The property is defined as a value of various pieces of information and requires one attribute to contain each piece of information. Multiple properties of the above properties can be used.

The attribute consists of four components and has the following meaning.

handle: the address of the property

Type: the type of attribute

Value: the value of the property

Permission: permission to the property

5 is a flowchart illustrating an example of a connection procedure method in a Bluetooth low power energy technology to which the present invention can be applied.

The server transmits an advertisement message to the client through the three advertising channels (S5010).

The server may be called an advertiser before connection, and may be called a master after connection. An example of the server may be a sensor (temperature sensor, etc.).

In addition, the client may be called a scanner before the connection, and may be called a slave after the connection. An example of the client may be a smartphone.

As we saw earlier, Bluetooth communicates over 40 channels across the 2.4 GHz band. Three of the 40 channels are advertising channels, and are used for exchanging packets, including various advertising packets, to establish a connection.

The remaining 37 channels are used for data exchange after connection to the data channel.

After receiving the advertisement message, the client may transmit a scan request message to the server to obtain additional data (eg, a server device name) to the server.

In this case, the server transmits a scan response message including additional data to the client in response to a scan request message.

Here, the Scan Request message and the Scan Response message are one end of the advertisement packet, and the advertisement packet may include only User Data of 31 bytes or less.

Therefore, if the data size is larger than 3 bytes, but there is a large data overhead for sending data through connection, the data is divided twice using Scan Request message / Scan Response message.

Next, the client transmits a connection request message for establishing a Bluetooth connection with the server to the server (S5020).

This establishes a Link Layer (LL) connection between the server and the client.

The server and client then perform a security establishment procedure.

The security establishment procedure may be interpreted as or included in Secure Simple Pairing.

That is, the security establishment procedure may be performed through Phase 1 to Phase 3 steps.

In detail, a pairing procedure (Phase 1) is performed between the server and the client (S5030).

In the pairing procedure, the client transmits a pairing request message to the server, and the server transmits a pairing response message to the client.

The pairing procedure exchanges authentication requirements, I (Input) / O (output) capabilities, and Key Size information between devices. This information determines which key generation method to use in Phase 2.

Next, as Phase 2, a legacy pairing or a secure connection is performed between the server and the client (S5040).

Generate a 128-bit Temporary Key and Short Term Key (STK) that perform legacy pairing in Phase 2.

Temporary Key: Key created to generate STK

Short Term Key (STK): Key value used to create an encrypted connection between devices.

If a secure connection is performed in phase 2, a 128-bit long term key (LTK) is generated.

Long Term Key (LTK): Key value that is used not only for encrypted connection between devices but also for future connections.

Next, as SSP Phase 3, a key distribution procedure is performed between the server and the client (S5050).

Through this, a secure connection is established between the server and the client, and an encrypted link can be formed to transmit and receive data.

Hereinafter, a method for transmitting and receiving long attribute values will be described.

The longest attribute that can be sent in a single packet is ATT_MTU-1 octets. Here, ATT_MTU means the maximum size of a packet transmitted between the client and the server.

At a minimum, an attribute opcode is included in an attribute PDU. The attribute value may be defined larger than the ATT_MTU-1 octet, and this attribute is called a long attribute.

A read blob request message is used to read the entire value of an attribute larger than ATT_MTU-1 octets. The read request message can be used to read the first ATT_MTU-1 octet of the long attribute value.

A ready write request message and an execute write request message may be used to write the entire value of an attribute greater than ATT_MTU-3 octets. The write request message can be used to write the first ATT_MTU-3 octets of the long attribute value.

It is difficult to determine if an attribute value is longer than ATT_MTU-3 octets using a particular protocol. The higher layer specification specifies that a given attribute may have a maximum length greater than ATT_MTU-3 octets.

The maximum length of an attribute value is 512 octets. That is, the maximum length of data that can be stored in one property is 512 octets.

6 is a view briefly illustrating a method for controlling a connection of another device through a control device proposed in the present specification.

As shown in FIG. 6, a third device 500 is required to control an operation between the first device 300 and the second device 400, and the third device 500 is the first device. A new control protocol is needed to control the association of 300 and the second device 400.

Hereinafter, a device for controlling the operations of the first device 300 and the second device 400 is called a control device, a controller, a third device 500, or a client.

In addition, a device controlled by the controller is called a first device, a second device, or a server.

At this time, the client needs to know the information of the devices (eg, binding information, interface information, service information, etc.) in order to control the operation of the devices.

In addition, when the client instructs the servers to perform a specific operation to control the operation of the server, there is a problem that can not determine whether the operation is performed properly.

In addition, although the client can control the operation of the devices, it is not possible to set the execution time of the instructed operation, and when the operation fails, there is a problem that there is no method for recognizing the failed service and cause in detail.

Therefore, the present invention controls the operation of the server by instructing the server to a specific operation and execution time by recognizing the information related to the combination of the server, if the server fails to perform a specific operation, the operation that can not perform from the server And a method for receiving an error code for identifying a cause of failure.

7 is a diagram illustrating an example of a profile structure for providing a service for controlling a device proposed in the present specification.

In Bluetooth, a service that allows a specific device to control and manage pairing and / or connection of another Bluetooth device is called an Easy Pairing Service. In FIG. 7, the controller 500 may control pairing and / or connection between the first device 300 and the second device 400 using an easy pairing service.

Referring to FIG. 7, the controller 500 may connect the first device 300 and the second device 400 through an easy pairing service.

Specifically, after the controller 500 searches for GATT services of the first device 300 through a primary service discovery procedure, the third device is a GATT of the second device 400 that is a peer device of the first device 300. Clients can be found with properties.

Through this, the controller 500 may know the GATT service available between the first device 300 and the second device 400.

The controller 500 may control pairing and / or connection of the first device 300 and the second device 400 based on the GATT service available between the first device 300 and the second device 400. have.

In the easy pairing service 500, the first device 300 and the second device 400 may manage pairing and / or connection based on which device and what connection relationship are formed.

Bluetooth is based on a one-to-one combination, but in the future, a plurality of devices can form a bonding relationship in one device through Bluetooth. That is, one-to-many combination may be possible.

8 to 11 are diagrams illustrating an example of a method and data format for controlling a server by a client proposed in the present specification.

Referring to FIG. 8, the client may set the execution time of a specific operation together while instructing the server for a specific operation, and the server may perform the indicated specific operation based on the set execution time.

In detail, the client may establish a Bluetooth LE connection with the server through the method described with reference to FIG. 5.

Thereafter, the client transmits a write request message requesting writing of the control point characteristic of the server in order to instruct the server and the server in a specific operation (S8010).

The write request message may include an operation code (Opcode) indicating a specific operation indicated by the client and a valid time associated with performing the specific operation.

9 illustrates an example of an operation code that may be instructed by a client to a server.

The server must perform the indicated action during the validity time or within the validity time set by the client according to the specified specific action.

For example, when the operation code included in the write request message is '0x04', that is, when the indicated operation is a Peripheral role for the LE connection, the server may transmit an advertisement packet to neighboring devices during the validity time. .

Alternatively, when the operation code included in the write request message is '0x06', that is, when the indicated operation is an operation of selecting one of a plurality of banks indicating a coupling relationship of the server, the server may select one of the specific banks within a valid time. Can be selected.

In this case, when the configured association information exceeds the maximum size that can be stored in one characteristic, the bank refers to each piece of data obtained by dividing the association information configured according to the maximum size.

The control point characteristic may be identified by the UUID, and may have a structure as shown in Table 2 below.

In Table 2, an Opcode includes a code indicating an operation indicated as shown in FIG. 9, and a Parameter includes parameters related to an operation indicated by the Opcode.

The parameter may include information related to a specific operation indicated by the opcode. For example, a parameter may be an operation field indicating an operation to be performed in order to perform a specific operation indicated by an opcode, and an execution time at which a specific operation is to be continuously performed or an execution time at which a specific operation should be performed. It may include an effective time field indicating.

In addition, the parameter may further include additional fields according to the instructed operation.

When the server receives the write request message from the client, the server writes the values received in the control point characteristics before the ATT timeout indicating the response time expires, and transmits the write response message to the client in response to the write request message (S8020). ).

In this case, when the server cannot write values received through the write request message of the client to the control point characteristic, the server may transmit an error response message to the client before the ATT timeout expires.

The server may perform a specific operation indicated by the client after transmitting the write response message to the client (S8030).

If the server cannot perform an operation instructed by the client, an error message including a response code indicating an unoperable operation and / or an error cause illustrated in FIGS. 10 and 11 may be transmitted.

10 and 11 show examples of response codes.

The server may perform the specific operation indicated during or within the valid time period written through the write request message, and transmit an indication message indicating successful execution of the specific operation to the client (S8040).

In this case, the indication message may be transmitted from the server to the client before the valid time expires.

The client receiving the indication message indicating the successful execution of the specific operation by the server transmits a confirmation message to the server in response (S8050).

Hereinafter, the operation of the server for “Opcode” shown in FIG. 9 will be described with reference to specific embodiments of FIG. 8.

BR / EDR  Acceptor Control Procedure

The client knows the operation and function supported by the server through the reading procedure. If the server can act as an acceptor for BR / EDR, the client instructs the server to act as an acceptor by writing the control point characteristics of the server. can do.

Specifically, when the Opcode of the control point characteristic of the server is written as "0x01" by the client, the server operates as an acceptor of BR / EDR.

In this case, the parameter of the control point characteristics of the server may be configured as shown in Table 3 below.

In Table 3, the Peer Device ID field includes an ID for identifying a target device to which the server performs as an acceptor.

The Operation field may include operations related to the acceptor role as shown in Table 4 below.

When the server receives the write request message from the client, the server must be set to the accessible mode to perform the page scan operation, and set to the searchable mode and the bondable mode as defined in the 0, 1, and 2 bits of Table 4. Can be.

In addition, for the 3, 4, and 5 bits of Table 4, if each bit is set to 1b, the server may perform each operation, otherwise the server should not perform the indicated operation.

If the 3 bits of Table 4 are set to 1b, the server can only act as an Acceptor on a device whose Bluetooth address is the same as the value of the Peer Device ID field; otherwise, the Peer Device ID field is not included and the server must Can serve as Acceptor in relation to

To set 3, and 4 bits or 4 and 5 bits to 1b, the client must be connected to two servers.

When 4 bits are set to 1b, the server generates a confirm value (a contract value of BR / EDR) and an arbitrary value and instructs the client to relay the generated value with the Confirm Value Indication Opcode to the counterpart device.

If bit 5 is set to 1b, the server waits to receive a Confirm Value Relay Opcode and any value of the counterpart device from the client to establish a secure connection with the counterpart device.

Table 5 below shows an example of the valid time field.

The server should perform the indicated operation during the following valid operation time based on the value of the valid time field.

Effective Operating Time = Time Unit × Duration Value

If the value of the time unit subfield is “0x00”, the server may ignore the value of the Duration Value subfield and perform the requested operation for the time defined in the upper layer or the implementation.

If the server successfully performs the associated operation according to the client's instructions, the server sends an indication message to the client that includes a response code indicating that the indicated operation was successfully performed.

However, when the server fails to perform the indicated operation, the server transmits an instruction message including a response code indicating the cause of failure shown in FIGS. 10 and 11 to the client.

BR / EDR Initiator Control Procedure Behavior

If the client recognizes that the server supports the Initiator role through the read procedure, the client may instruct the server to operate as an initiator by writing the control point characteristics of the server.

Specifically, when the Opcode of the control point characteristic of the server is written as "0x02" by the client, the server operates as an initiator of the BR / EDR.

In this case, the parameter of the control point characteristics of the server may be configured in the same manner as in Table 3 above, and the Operation field may include operations related to the Initiator role as shown in Table 6 below.

If 1 bit of the Operation field is set to “0b”, the server performs a bonding procedure. Otherwise, the server performs a bonding procedure according to an upper layer standard or implementation.

In order for the 1 or 2 bits to be set to "1b", the client must connect to two servers to exchange their confirmation values with other servers.

The server generates a confirmation value (a confirmation value of BR / EDR) and an arbitrary value and instructs the client to relay the generated value with the Confirm Value Indication Opcode to the counterpart device.

If two bits are set to 1b, the server waits to receive a Confirm Value Relay Opcode and any value of the counterpart device from the client to establish a secure connection with the counterpart device.

The operation below may be the same as when the server described above operates as an acceptor.

LE Peripheral Control Procedure Behavior

If the client recognizes that the server supports the LE Peripheral role through the read procedure, the client may instruct the server to operate in the LE Peripheral role by writing a control point characteristic of the server.

Specifically, when the Opcode of the control point characteristic of the server is written as "0x03" by the client, the server operates as LE Peripheral of BR / EDR.

In this case, the parameter of the control point characteristics of the server may be configured as shown in Table 7 below, and the Operation field may be configured as shown in Table 8 below.

Referring to Table 8, the search mode may be set by the 0 bit of the operation field, and the connection mode may be set by the 2 bits.

For example, when two bits of the operation field are set to "1b", the server may operate in the direct connection mode using the value of the Peer Device ID field as the initiator address.

The server may advertise the type of its advertiser address as defined by bits 4 and 5 of the action field of Table 8.

If the server includes Resolvable Private Address Only Characteristic, the server may advertise its Resolvable Private Address (RPA) together.

If the counterpart device does not have an IRK of Resolvable Private Address, the counterpart device ignores the advertisement transmitted from the server.

The server may be set to a mode in which bonding is possible by bit 7 of the operation field. If the server is not set by bit 7 of the operation field, the server may be set to a bondingable mode according to a higher layer standard or an implementation.

In order for bit 9 or bit 10 of the operation field to be set to "1b", the client must be connected to two servers, and the client must exchange the confirmation value of the server with another server.

The server generates confirm and random values and instructs the client to relay the values generated by the Confirm Value Indication Opcode to another server.

If bit 10 is set to "1b", the server waits to receive a Confirm Value Relay Opcode and any value of the counterpart device from the client to establish a secure connection with the counterpart device.

If bit 14 is set to "1b", the server receives the peer device IRK field, which is the IRK value of the Peer Device ID field. The server adds the Peer Device ID, Peer Device IRK, and Local IRK to the resolving list.

Hereinafter, the validity time and the operation associated with the success or failure of the operation may be the same as described above.

LE Central Control Procedure Behavior

If the client recognizes that the server supports the LE Central role through the read procedure, the client may instruct the server to operate in the LE Central role by writing a control point characteristic of the server.

Specifically, when the Opcode of the control point characteristic of the server is written as "0x04" by the client, the server operates as LE Central of BR / EDR.

In this case, the parameter of the control point characteristics of the server may be configured as shown in Table 9 below, and the Operation field may be configured as shown in Table 10 below.

If the server supports the Resolvable Private Address, the server may receive the Peer Device IRK together through a sub procedure such as Write Long Characteristic Values that can transmit and receive long data.

The server may form a connection according to the procedure set by bits 0 and 1 of the operation field, and when bit 3 is set to “1b”, storing the bonding information for the next connection with the counterpart device according to the pairing procedure. Bonding procedures can be performed for this purpose.

If bit 5 and bit 6 of the operation field are set to “1b”, the client can connect with two servers, and the client must exchange the confirmation value of the server with another server.

If bit 5 is set to "1b", the server generates a confirm value and an arbitrary value and instructs the client to relay the value generated by the Confirm Value Indication Opcode to another server.

If bit 10 is set to "1b", the server waits to receive a Confirm Value Relay Opcode and any value of the counterpart device from the client to establish a secure connection with the counterpart device.

If bit 14 is set to "1b", the server receives the peer device IRK field, which is the IRK value of the Peer Device ID field. The server adds the Peer Device ID, Peer Device IRK, and Local IRK to the resolving list.

Hereinafter, the validity time and the operation associated with the success or failure of the operation may be the same as described above.

Association Termination Procedure Behavior

If the client recognizes that the server supports the Easy Pairing service through the read procedure, the client terminates the association with other devices by writing the control point characteristics of the server. ) Can be instructed.

The connection termination procedure may be performed to unbind the server, including termination of the connection and deletion of the bonding.

In this case, the parameter of the control point characteristics of the server may be configured as shown in Table 11 below.

The Bearers field of Table 11 may be set to the values of Table 12 below.

The server may release the bearer according to the value set in the Bearers field of Table 11, and when the value of the Bearers field is set to a value indicating “Reserved for Future” in Table 12, the server has a value of “0x08” in FIG. 10. An error message containing the response code may be sent to the client.

The server may operate according to the value set in the operation field of Table 11.

Table 13 below shows an example of the operation indicated by each bit of the operation field.

Hereinafter, the operation of the server according to the success or failure of the operation is the same as described above.

Confirm Value Indication Opcode  Behavior

The Confirm Value Indication Opcode can be used to form a secure connection between two servers.

If the server supports Confirm Value Indication Opcode, the server must support the Read Long Characteristic Values sub-procedure to send and receive long data even if the ATT_MTU is smaller than 41 bytes.

At this time, ATT_MTU means the maximum size of the packet transmitted between the client and the server.

The two servers can be connected to the client through the BR / EDR Secure Simple Pairing, BR / EDR Secure Connection, or LE Secure Connection pairing procedure, and the Confirm Value Indication Opcode can be supported together with The Confirm Value Relay Opcode below.

As described above, the server may generate a confirmation value (commitment value in BR / EDR) and an arbitrary value, and instruct the client to operate according to the above-described procedures through the Confirm Value Indication Opcode.

Thereafter, the other server receives the following Confirm Value Relay Opcode from the client, and the two servers establish a secure connection when the relayed confirmation value is confirmed.

Confirm Value Relay Opcode  Behavior

The Confirm Value Relay Opcode can be used by the client to establish a secure connection between two servers.

If the server supports Confirm Value Indication Opcode, the server must support the Read Long Characteristic Values sub-procedure to send and receive long data even if the ATT_MTU is smaller than 41 bytes.

In addition, in order for a client to establish a secure connection between servers through a Confirm Value Relay Opcode, two servers must be connected to the client by BR / EDR Secure Simple Pairing, BR / EDR Secure Connections, or LE Secure Connections Pairing.

The Confirm Value Indication Opcode may be supported together with the Confirm Value Indication Opcode described above.

The server waits to receive the Confirm Value Indication Opcode when the client configures the Client to perform the Confirm Value Indication Opcode in the following procedures.

Before the server receives the Confirm Value Indication Opcode from the client, the counterpart server must present its confirmation and arbitrary values to the client through the Confirm Value Indication Opcode described above.

Thereafter, when the confirmation value is confirmed, a secure connection may be established between the server and the counterpart server.

Table 14 below shows an example of a parameter of a control point characteristic of a server when a Confirm Value Relay procedure is performed through a Confirm Value Indication Opcode and a Confirm Value Relay Opcode.

If the client is unable to relay the confirmation value and any value of the counterpart server with the Confirm Value Relay Opcode to the server, the server may receive an operation code from the client indicating the interruption of the procedure and stop the procedure. can do.

Control Point Response Indication Opcode  Behavior

The Control Point Response Indication Opcode may be used to indicate the success or failure of the above-described procedures, and the response codes shown in FIGS. 10 and / or 11 may be used according to each procedure.

Table 15 below shows an example of a parameter of a control point characteristic of a server when a Control Point Response Indication procedure is performed.

An indication message including a response code indicating a result of performing an operation on an operation requested or requested from a client may include an operation code indicating an operation requested from the client as shown in Table 15.

When the server successfully performs the operation requested from the client, the server may use “0x00” indicating the success of the operation as a response code. However, when the server fails an operation requested from the client, the server may select and use one response code indicating an operation failure and a cause of failure from among the response codes shown in FIGS. 10 and 11.

If an error condition occurs while performing a specific operation or a specific procedure requested from the client, the server stops the operation related to the specific operation or the specific procedure and responds with the most related error among the response codes shown in FIGS. 10 and 11. You can select the code and send it to the server.

If the server does not support the valid time set from the client, the server may transmit the valid time supported by the server to the client along with the response code.

For example, if the validity time sent by the client is greater than the maximum allowed time for the server, the server may send the client the maximum uptime supported by the server.

In addition, if the valid time sent by the client is less than the minimum allowed time for the server, the server may send the client the minimum time supported by the server.

The server cannot perform another operation until the operation instructed by the client is finished.

Therefore, when a server is instructed to perform a specific operation and / or procedure from another client while performing an operation instructed by the client, the server may transmit a response code including an error code indicating that the operation is not completed to the other client. have.

Select Client List Bank Procedure Behavior

When the server can provide the client list of the combined clients through the property, a procedure for changing the bank in the client list property in which a bank representing each of a plurality of data representing the list of the combined clients is stored may be performed. have.

The procedure for changing banks in this respect is called Select Client List Bank Procedure.

The client may control the server to change the bank stored in the client list property of the server to the next bank or a specific bank through the Select Client List Bank Opcode.

The server receiving the Select Client List Bank opcode from the client may change the value of the Client List property to the next bank or to the requested bank.

If the server does not have a bank requested by the client, the server may include a response code "0x07" indicating an unsupported bank in the error message and transmit the same to the client.

Table 16 below shows an example of a parameter of a control point characteristic of a server when a Select Client List Bank procedure is performed.

As in the above-described procedures, when the operation is successfully performed, the server transmits a response code indicating success to the client, and when the operation fails, the server sends a response code indicating failure and the cause of failure in the error message.

Reset Client UUID  Selection Policy Info Procedure Behavior

If the server can provide the list of combined clients through the client list property, the Client UUID Selection Policy Information, which means the policy for selecting the client UUID, can be reset through the Reset Client UUID Selection Policy Info Procedure.

A server that receives an action code to reset the Client UUID Selection Policy Information can reset all information related to the Client UUID Selection Policy (for example, how often the client feature is used on the server if the client feature is used on the server). Etc.)

As in the above-described procedures, when the operation is successfully performed, the server transmits a response code indicating success to the client, and when the operation fails, the server sends a response code indicating failure and the cause of failure in the error message.

Abort Opcode

The client can use Abort Opcode to cancel the above operations.

When the Abort Opcode is sent from the client, the server immediately stops all operations related to the specific operation and / or procedure indicated by the client, and includes the response message “0x11” in the indication message indicating the cancellation of the procedure shown in FIG. 10. Send to client

Abort Opcode must be received by the server before the indicated action from the client is completed. If Abort Opcode is received after the indicated action from the client is completed, the server ignores the Abort Opcode and does not send a response code of “0x11”. .

General Error Handling procedures for Write Requests of the Pairing Control Point Characteristic

In addition to the procedures for errors in specific procedures discussed earlier, the following error handling procedures can be applied in general:

If the operation code of the control point characteristic of the server is written by the client, and the characteristic configuration descriptor of the control point is not configured for the indications, the server indicates that the characteristic configuration descriptor is not configured properly. Send an error message containing the error code to the client.

12 is a flowchart illustrating an example of a method for canceling an operation instructed by a client proposed in the specification.

Referring to FIG. 12, the client may withdraw the operation of the server by instructing the operation to be canceled before the operation instructed to the server is terminated.

Specifically, the client instructs the server through the method described with reference to FIGS. 8 to 11 and then, if the client wants to withdraw the indicated operation, requests the client to write a control point characteristic for instructing the revocation of the operation. The write request message is transmitted (S12010).

In this case, the write request message may include an Abort opcode, which is an operation code indicating revocation of the operation described with reference to FIGS. 8 to 11.

A write request message requesting the withdrawal of an action must be received by the server before the server has ended the indicated action, and a write request message is received by the server requesting the withdrawal of the action after the indicated action is completed. As described above, the server may ignore the received write request message.

After receiving the write request message from the client, the server transmits a write response message in response thereto, and withdraws all the procedures that are being performed in connection with the indicated operation and / or procedure (S12020, S12030).

Thereafter, when the withdrawal of the operation is successfully performed, the server may transmit an instruction message including a response code indicating that the operation was successfully withdrawn to the client (S12040).

In this way, the client can withdraw the operation directed to the server before the indicated operation ends.

13 is a flowchart illustrating an example of a method for controlling a server by a client proposed in the present specification.

Referring to FIG. 13, the client establishes a Bluetooth Low Energy (LE) connection with the server to control the server through a specific service (S13010). In this case, the Bluetooth connection may be formed through the method described with reference to FIG. 5.

Thereafter, the client transmits a first write request message requesting the writing of the control point characteristic for the indication of the specific operation (S13020).

As described with reference to FIGS. 8 to 11, the first write request message may include at least one of an operation code indicating a specific operation, a first valid time indicating an execution time of the specific operation, or parameters related thereto.

After receiving the first write request message from the client, the server transmits the first write response message to the client in response (S13030).

At this time, the first write response message should be transmitted to the client within a specific time.

Thereafter, the client receives a first indication message indicating whether to perform the operation indicated by the server (S13040).

In this case, the first indication message may include a response code indicating the success or failure of the indicated operation as described with reference to FIGS. 10 and 11 and should be transmitted from the server to the client within the valid time.

Further, for convenience of description, the drawings are divided and described, but it is also possible to design a new embodiment by merging the embodiments described in each drawing. And, according to the needs of those skilled in the art, it is also within the scope of the present invention to design a computer-readable recording medium having a program recorded thereon for executing the embodiments described above.

Method according to the present specification is not limited to the configuration and method of the embodiments described as described above, the embodiments are configured by selectively combining all or part of each embodiment so that various modifications can be made May be

On the other hand, the law of the present specification can be implemented as processor-readable code in a processor-readable recording medium provided in the network device. The processor-readable recording medium includes all kinds of recording devices that store data that can be read by the processor. Examples of the processor-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like, and may also be implemented in the form of a carrier wave such as transmission over the Internet. . The processor-readable recording medium can also be distributed over network coupled computer systems so that the processor-readable code is stored and executed in a distributed fashion.

In addition, while the above has been shown and described with respect to preferred embodiments of the present specification, the present specification is not limited to the specific embodiments described above, the technical field to which the invention belongs without departing from the spirit of the invention claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be individually understood from the technical spirit or the prospect of the present invention.

In addition, in this specification, both the object invention and the method invention are described, and description of both invention can be supplementally applied as needed.

Although the data transmission / reception method of the present invention has been described with reference to an example applied to Bluetooth LE, it is possible to apply to various wireless communication systems in addition to the Bluetooth LE system.

Claims (14)

1. In the method for the client to control the server in Bluetooth,

   Establishing a Bluetooth Low Energy (LE) connection with the server;

   Sending a first write request message to the server requesting writing of a control point characteristic for an indication of a particular operation;

   Receiving a first write response message in response to the write request message; And

   Receiving a first indication message for indicating whether to perform the specific operation from the server,

   And the first write request message includes a first operation code indicating the specific operation and a first valid time indicating the execution time of the specific operation.
2. The method of claim 1,

   And if the specific operation was successfully performed, the first indication message includes a response code indicating the success of the specific operation.
3. The method of claim 1,

   And when failing to perform the specific operation, the indication message includes an error code indicating a cause of the failure.
4. The method of claim 3, wherein

   If the error code indicates no support of the first valid time, the indication message further includes a second valid time supported by the server.
5. The method of claim 4, wherein

   If the first valid time is greater than the maximum execution time of the specific operation, the second valid time represents the maximum execution time,

   If the first valid time is less than the minimum performance time of the particular operation, the second valid time represents the minimum performance time.
6. The method of claim 1,

   Sending a second write request message to the server requesting writing of the control point characteristic to instruct cancellation of the specific operation;

   Receiving a second write response message in response to the second write request message; And

   Receiving a second indication message indicating whether to cancel the specific operation from the server;

   And the second write request message includes a second action code indicating the cancellation of the specific action.
7. The method of claim 1,

   If the specific operation is an operation performed with another device, the first write request message further includes a device ID for identifying a counterpart device.
8. In the client for controlling the server in Bluetooth,

   Communication unit for communicating with the outside by wireless or wired;

   A memory for storing data; And

   Including a processor that is functionally connected with the communication unit, The processor,

   Establish a Bluetooth Low Energy (LE) connection with the server,

   Send a first write request message to the server requesting writing of a control point characteristic for an indication of a particular operation,

   Receive a first write response message in response to the write request message,

   Receiving a first indication message indicating whether to perform the specific operation from the server;

   The first write request message includes a first operation code indicating the specific operation and a first valid time indicating the execution time of the specific operation.
9. The method of claim 8,

   If the specific operation is successfully performed, the first indication message includes a response code indicating the success of the specific operation.
10. The method of claim 8,

    If the execution of the specific operation fails, the instruction message includes an error code indicating a cause of failure.
11. The method of claim 10,

    If the error code indicates no support of the first execution time, the indication message further includes a second valid time supported by the server.
12. The method of claim 11,

    If the first valid time is greater than the maximum execution time of the specific operation, the second valid time represents the maximum execution time,

    If the first valid time is less than the minimum execution time of the specific operation, the second valid time indicates the minimum execution time.
13. The method of claim 8, wherein the processor,

    Sending a second write request message to the server requesting writing of the control point characteristic to instruct cancellation of the specific operation; And

    Receiving a second write response message in response to the second write request message; And

    Receiving a second indication message indicating whether to cancel the specific operation from the server;

    The second write request message includes a second operation code indicating the cancellation of the specific operation.
14. The method of claim 8,

    If the specific operation is an operation performed with another device, the first write request message further includes a device ID for identifying a counterpart device.

Images