WO2019199049A1

WO2019199049A1 - Method for controlling device in wireless communication system and device therefor

Info

Publication number: WO2019199049A1
Application number: PCT/KR2019/004264
Authority: WO
Inventors: 송종훈
Original assignee: 엘지전자 주식회사
Priority date: 2018-04-10
Filing date: 2019-04-10
Publication date: 2019-10-17

Abstract

The present specification provides a method for controlling short-range wireless communication between first and second devices by using a third device. More particularly, the method performed by the third device receives, from the first device, a first response message including a first service list, receives, from the second device, a second response message including a second service list, determines whether the first service list and the second service list match, and performs a procedure for establishing a Bluetooth connection between the first device and the second device according to whether the first service list and the second service list match.

Description

Method for controlling device in wireless communication system and apparatus therefor

The present disclosure relates to a wireless communication system, and more particularly, to a method for controlling Bluetooth communication between first and second devices using a third device and an apparatus supporting the same.

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.

An object of the present specification is to provide a method and apparatus for receiving a service list using a Bluetooth easy pairing service.

In addition, the present specification is to improve the search speed in querying the list of services provided by the Bluetooth device using the easy pairing client device.

In addition, the present specification is to improve the connection speed in performing a Bluetooth connection using the easy pairing client device.

In addition, the present specification is to improve the power consumption in performing a Bluetooth connection using the easy pairing client device.

The technical problems to be achieved in the present invention 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 specification provides a method of controlling short-range wireless communication between first and second devices using a third device.

Specifically, the method performed by the third device includes: establishing a Bluetooth connection with the first device and the second device; Transmitting a first request message requesting a first service list supported by the first device to the first device; Receiving a first response message including the first service list from the first device based on the first request message; Transmitting a second request message requesting a second service list supported by the second device to the second device; Receiving a second response message including the second service list based on the second request message from the second device; Determining whether the first service list and the second service list match; And performing a procedure for establishing a Bluetooth connection between the first device and the second device according to whether the first service list and the second service list match each other, and included in the first response message. The service list supported by the first device may be determined based on a preset priority.

In addition, in the present specification, when the first service list and the second service list do not coincide with each other, the first device and the second device may be controlled so as not to establish a Bluetooth connection.

The method may further include transmitting a control message instructing to establish a Bluetooth connection with the first device when the first service list and the second service list match. It features.

Also, in the present specification, the second request message includes service information related to some of the services included in the first service list, and the second service list includes services that match the service information. It is done.

Also, in the present specification, the first device may perform a role of a Generic Attribute (GATT) client in a relationship of transmitting and receiving data by forming a brutus connection between the first device and the second device.

In addition, in the present specification, the second device may serve as a GATT server in a relationship of transmitting and receiving data by forming a Bluetooth connection between the first device and the second device.

In the present specification, the first service list is a part of services supported by the first device determined based on a predetermined priority.

In addition, in the present specification, some of the services supported by the first device may be a service having the highest priority.

Further, in the present specification, a third device for controlling short-range wireless communication between the first and second devices, the third device comprising: a communication unit for communicating wirelessly or wired with the outside; And a processor operatively connected with the communication unit, wherein the processor establishes a Bluetooth connection with the first device and the second device, and requests the first device for a first service list supported by the first device. Transmitting a first request message, receiving a first response message including the first service list from the first device based on the first request message, and supporting the second device with the second device. Transmit a second request message requesting a second service list, receive a second response message including the second service list from the second device based on the second request message, and transmit the first service list and the first service list; Determine whether the second service list matches, and whether or not the first service list matches the second service list; Performing a procedure for establishing a Bluetooth connection between the first device and the second device, and a service list supported by the first device included in the first response message is determined based on a preset priority; do.

Further, in the present specification, when the first service list and the second service list do not match, the processor may control not to establish a Bluetooth connection between the first device and the second device.

Also, in the present specification, when the first service list and the second service list match, the processor transmits a control message instructing to establish a Bluetooth connection with the first device to the second device. It further comprises.

Further, in the present specification, the second request message includes service information related to some of the services included in the first service list, and the second service list includes services that match the service information. It features.

In addition, in the present specification, the first device may serve as a Generic Attribute (GATT) client in a relationship of transmitting and receiving data by establishing a Bluetooth connection between the first device and the second device.

The present specification has an effect of improving the search speed in searching a list of services provided by a Bluetooth device using an easy pairing client device.

In addition, the present specification has the effect of improving the connection speed in performing a Bluetooth connection using the easy pairing client device.

In addition, the present specification has the effect of improving the power consumption in performing a Bluetooth connection using the easy pairing client device.

The effects obtainable in the present invention are not limited to the above-mentioned effects, and other effects not mentioned will be clearly understood by those skilled in the art from the following description. .

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are included as part of the detailed description in order to provide a thorough understanding of the present invention, provide embodiments of the present invention and together with the description, describe the technical features of the present 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 shows an example of an internal block diagram of a device that can implement the methods proposed herein.

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 view briefly illustrating a method for controlling another device through a control device proposed in the present specification.

6 and 7 are diagrams illustrating an example of a profile structure for providing a service for controlling a device proposed in the present specification.

8 (a) is a view showing a method for querying a service in the conventional Bluetooth technology, (b) is a view showing an example of a method for querying a service proposed in the present specification.

FIG. 9 is a diagram illustrating a method for forming a connection between first and second devices through a third device proposed herein.

10 is a diagram illustrating a method for receiving a service list from a GATT client proposed in the present specification.

11 is a diagram illustrating a method for receiving a service list from a GATT server proposed in the present specification.

12 illustrates another example of a method for receiving a service list 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 accompanying 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.

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 by 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), the first device, the second 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.

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.

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 1600 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. 4B, 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 thereto 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 is a protocol for authenticating a device and 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 present invention transmits a value for the data length when a long data request is made in the GATT profile using the attribute protocol (ATT, 43) so that the client can know the data length clearly, and from the server using the UUID (Characteristic) Can receive the value.

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, etc. 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 transmitted on an advertising physical channel, the PDU will be an advertising channel PDU, and when one packet is transmitted 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

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

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.

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 PDUs

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 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 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, and has a definition of a service and a characteristic.

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.

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

The present invention proposes a method for controlling a device by acquiring information related to controllable operation and combination information of a device to be controlled by a control device through the GATT.

Easy pairingEasy pairing

As shown in FIG. 5, 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 control device for controlling the operations of the first device 300 and the second device 400 is referred to as the third device 500.

In this case, the third device 500 needs to know information (eg, interface information, service information, etc.) of the devices in order to control the operation of the devices.

6 and 7, a service for controlling another device by the control device may be included in a profile of other services or may be defined as a separate profile.

Hereinafter, in the present invention, a service for controlling other devices by the control device will be referred to as an easy pairing service.

The third device 500 which is the control device may control other devices through the easy pairing service. For example, the third device 500 may control operations related to coupling (eg, connection, pairing, or bonding) between the first device 300 and the second device 400 through the easy pairing service. Can be.

In this case, the easy pairing service may be included in a profile of another service as shown in FIG. 7 or may be defined as a separate profile as shown in FIG. 8.

As shown in FIG. 6, when the easy pairing service is not defined as a separate profile and is included in a profile of a specific service, it is advantageous to explain an operation of one application.

However, the easy pairing service cannot be applied to a service of a profile not including the easy pairing service, and roles between devices must be clearly defined.

When the easy pairing service is defined as a separate profile as shown in FIG. 7, the server / client structure is compatible at the profile level, and the easy pairing service can be extended to another profile.

Referring to FIG. 8 (a), in the conventional Bluetooth technology, a GATT (Generic Attribute Profile) client had to connect to a GATT server to search for a service provided by a GATT server.

On the other hand, in case of controlling by a third party device (device), service inquiry of a device operating as a GATT client among target devices was not possible.

In other words, conventionally, there is a problem in that a service provided by a device operating as a GATT client cannot be inquired by a third party device to connect target devices.

In addition, there is a problem that the complexity of the search method defined in easy pairing (for example, based on recently used items and frequently used items) is high.

In addition, when inquiring a service for connection using an easy pairing service, there is a problem in that a time required for service discovery is long for a device having a large number of services provided.

In this specification, in order to solve the above problem, a method of querying a service provided by a device operating as a GATT client among target devices using a third party device is proposed.

Referring to FIG. 8 (b), the device C (EP client) may query a service list provided by the device A (GATT client) and a service list provided by the device B (GATT server).

In addition, the device C receiving the service list from the devices A and B may transmit a command to connect the devices A and B to each other.

Hereinafter, the service inquiry method provided by the present disclosure will be described in detail with reference to FIGS. 9 to 12.

Referring to FIG. 9, the EP client may control the connection between the EP servers through the easy pairing service.

First, it is assumed that device A 901, device B 902, and device C 903 support an easy pairing service.

In this case, the devices A and

B

901 and 902 may operate as an easy pairing server, and the device C 903 may operate as an easy pairing client.

Also, at this time, device A 901 may be a device operating as a GATT client, and device B 902 may be a device operating as a GATT server.

The device C 903 may receive a Bluetooth advertisement (BLE Advertise) transmitted by the device A 901 and perform a Bluetooth connection operation (S910 and S930).

In detail, the device A 901 may transmit an advertisement message for the Bluetooth connection to the device C 903, and the device C 903 receives the advertisement message and recognizes the device A 901, and then the device A request message for a Bluetooth connection with A 901 may be transmitted to form a Bluetooth connection with device A.

The device C 903 may receive a Bluetooth advertisement transmitted by the device B 902 and perform a Bluetooth connection operation (S920 and S940).

Steps S920 and S940 are the same as those of steps S910 and S930 described above.

The device C 903 requests a service list provided by the device A 901 (S950).

In one example, device C 903 may send a request message to device A 901 requesting information about a service list supported by a GATT client, and from device A 901, in response to the request message, GATT Information about the service list supported by the client can be received.

The device C 903 requests a service list provided by the device B 902 (S960).

In this case, the service list provided by the device A 901 in operation S960 may be a service list determined based on the priority, and the priority may be determined by the user.

The device C 903 determines whether the service list provided by the device B 902 received in operation S960 matches the service list provided by the device A 901 received in operation S950 (S970).

For example, in operation S970, the device C 903 receives the service specified in the first service (eg, the highest priority service) among the services included in the service list determined based on the priority received in the operation S950 and the operation received in the operation S960. It may be determined whether or not the service list is matched.

That is, it may be determined whether the first service and the service included in the service list received in operation S960 match each other (matching).

In operation S970, when it is determined that the service list is matched, the device C 903 may proceed with the connection between the devices A and

B

901 and 902 through an easy pairing service (S980).

Specifically, device C 903 may control to establish a Bluetooth connection between device A 901 and B 902.

For example, device C 903 may send a control message to devices A and

B

901 and 902 to control the establishment of a Bluetooth connection between devices A and

B

901 and 902.

When the device B 902 receives a control message from the device C 903, the device B 902 may transmit a Bluetooth advertisement message to the device A 901.

Upon receiving the advertisement message, the device A 901 transmits a message requesting a Bluetooth connection to the device B 902.

As a result, the Bluetooth connection between the devices A and

B

901 and 902 may be made.

In operation S970, when it is determined that the service list does not match, the device C 930 does not perform an operation for establishing a Bluetooth connection between the devices A and B 901 and 902 (S990).

In other words, when the service list does not match, the device C 903 does not perform a separate operation.

The basic method of service inquiry was recently used service and many service based methods.

In addition, there is no conventional method for reading service information of a device operating as a GATT client.

Therefore, the conventionally defined technique in the easy pairing service has to read all the services specified in the target device according to a search condition, and there is a problem in that a search time is lengthened by using a read long in the process.

In order to solve this problem, the EP server device (device) acting as a GATT client provides a service list to the EP client device, and uses the priority-based Client Services List up Characteristic. It demonstrates based on FIG.

First, the device C (EP client, 903) requests the client service list from the device A (EP server, 901) (S1010).

A client service list request message may be sent to request a service list, and the request message may be an ATT read request message.

Device A 901 may operate as a GATT client.

The device A 901 transmits a client service list to the device C 903 in response to the request (S1020).

In this case, the device A 901 may transmit a response message including information on the client service list to the device C 903 in response to the request.

The response message may be an ATT read response message.

In this case, the service list may be a service list determined based on a preset priority.

In this case, the preset priority may be determined by a user.

According to the method according to FIG. 10, the service list is listed by using a priority scheme for the service search of the EP server device acting as a GATT client, so that the EP client can read only the first service list (eg, priority service) information. There is an effect that a matching check is possible.

Meanwhile, the client service list characteristic may be defined, and all service lists may be read by specifying Property: Read and Read Long.

Table 2 below shows the structure of the response message in step S1020.

In Table 2, each parameter is defined as follows.

Number of 16-bit UUID: Service ID with 16 bits.

16-bit UUID List: A list of services with a size of 16 bits.

Number of 32-bit UUID: Service ID with 32 bits.

32-bit UUID List: A list of services with a size of 32 bits.

Number of 128-bit UUID: Service ID with 128 bits.

128-bit UUID List: A list of services with a size of 128 bits.

According to FIG. 11, the device C (EP client) 903 may request a service list from the device B (EP server) 902.

In this case, the device B 902 may operate as a GATT server.

The detailed procedure is the same as the procedure in FIG. 10 described above, and will be omitted.

When using the method proposed in FIG. 10 and the method proposed in FIG. 11 in combination, the service matching ratio can be increased.

12 is a diagram illustrating still another example of a method for receiving a service list proposed in the present specification.

First, the device C (EP client) 903 may request a client service list from the device A (EP server) 901. (S1210).

In this case, the device C 903 may transmit a client service list request message requesting the client service list to the device A 901, and the request message may be an ATT read request message.

The device A 901 transmits a service list provided by the device A 901 to the device C 903 in response to the request (S1220).

In this case, the device A 901 may transmit a response message including the client service list to the device C 903 in response to a request from the device C 903, and the response message may be an ATT read response message. message).

In this case, the service list provided by the device A 901 may be a service list determined based on a preset priority.

In this case, the preset priority may be determined by the user.

Device C 903 may request a server service list from device B (EP server) 902. (S1230).

In this case, the device C 901 may transmit a request message for requesting a server list to the device B 902, and the request message may be an ATT read request message.

Next, the device B 902 transmits a server service list to the device C 903 in response to the request in step S1230 (S1240).

In this case, the device B 902 may transmit a response message including a server service list to the device C 903 in response to a request of the device C 903, and the response message may be an ATT read response message. Can be).

In this case, device A 901 may operate as a GATT client, and device B 902 may operate as a GATT server.

In this case, in operation S1230, the device C 903 may deliver the client service list determined based on the priority received in operation S1220 to the device B 902, and the device B 902 may transmit the priority-based client service. The service information may be listed based on the list, and service discovery information may be exposed.

In operation S1230, the request of the device C 901 may be based on the client service list received in operation S1220.

For example, in operation S1230, the device C 903 delivers all of the client service list determined based on the priority received in operation S1220 to the device B 902 or the priority included in the service included in the client service list. Some high service can be delivered to device B 902.

In this case, the device C 903 may transmit a server service list request message requesting the server service list to the device B 902, and the request message may be an ATT write request message.

In operation S1240, the device B 902 may transmit only the list including the matching service by searching for a service based on the server service list (all or part) to the device C 903.

In this case, the device B 902 may transmit a response message including a server service list to the device C 903 in response to a request from the device C 903, and the response message may be an ATT write response message. message).

In the case of using a combination of the methods proposed in Figs. 10 to 12, the service matching ratio can be increased.

In addition, in the case of using a combination of the methods proposed in Figures 10 to 12 at the same time, the service matching ratio is the highest when using a portion of the high-priority service of the client service list determined based on the priority of Figure 12, Since the amount of data transmitted between the devices A, B, and C (901, 902, 903) is the smallest, the data transmission efficiency can be improved.

Table 3 below shows a definition of a Server Service List Characteristic transmitted by the device C 903 in step S1230.

In Table 3, each parameter is defined as follows.

Device Address: Device address.

Service List: Server service list.

Table 4 below shows the definition of the response message transmitted by the device B (902) in step S1240.

In Table 4, the definitions of the parameters are as follows.

Supported Service List: A list of supported services.

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.

Orientation-based device discovery method according to the present disclosure is not limited to the configuration and method of the embodiments described as described above, the embodiments are all or part of each of the embodiments is optional so that various modifications can be made It may be configured in combination.

Meanwhile, the direction-based device search method of the present specification may be implemented as processor-readable code in a processor-readable recording medium provided in a 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 present invention has been described with reference to the example applied to the Bluetooth system, it is possible to apply to various wireless communication systems in addition to the Bluetooth system.

Claims

A method for controlling short-range wireless communication between first and second devices using a third device, the method performed by the third device,

Establishing a Bluetooth connection with the first device and the second device;

Transmitting a first request message requesting a first service list supported by the first device to the first device;

Receiving a first response message including the first service list from the first device based on the first request message;

Transmitting a second request message requesting a second service list supported by the second device to the second device;

Receiving a second response message including the second service list based on the second request message from the second device;

Determining whether the first service list and the second service list match; And

And performing a procedure for establishing a Bluetooth connection between the first device and the second device according to whether the first service list and the second service list match.

The service list supported by the first device included in the first response message is determined based on a preset priority.
The method of claim 1, wherein the first service list and the second service list do not match.

Controlling not to establish a Bluetooth connection between the first device and the second device.
The method of claim 1, wherein when the first service list and the second service list match,

And sending a control message to the second device instructing to establish a Bluetooth connection with the first device.
The method of claim 1,

The second request message includes service information associated with some of the services included in the first service list,

And the second service list includes services that match the service information.
The method of claim 1,

And the first device acts as a generic attribute (GATT) client in a relationship of transmitting and receiving data by establishing a Bluetooth connection between the first device and the second device.
The method of claim 1,

And the second device acts as a GATT server in a relationship of transmitting and receiving data by establishing a Bluetooth connection between the first device and the second device.
The method of claim 1,

The first service list is a part of services supported by the first device determined based on a predetermined priority.
The method of claim 7, wherein

Some of the services supported by the first device are services having the highest priority.
In the third device for controlling short-range wireless communication between the first and second devices,

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

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

Establish a Bluetooth connection with the first device and the second device,

Transmit a first request message for requesting a first service list supported by the first device to the first device,

Receive a first response message including the first service list from the first device based on the first request message,

Transmitting a second request message for requesting a second service list supported by the second device to the second device;

Receive a second response message including the second service list based on the second request message from the second device,

Determine whether the first service list and the second service list match; and

Performing a procedure for establishing a Bluetooth connection between the first device and the second device according to whether the first service list and the second service list match;

And a service list supported by the first device included in the first response message is determined based on a preset priority.
The processor of claim 9, wherein the processor comprises:

If the first service list and the second service list do not match,

And control the Bluetooth connection between the first device and the second device not to be established.
The processor of claim 9, wherein the processor comprises:

When the first service list and the second service list match,

And sending a control message to the second device instructing to establish a Bluetooth connection with the first device.
The method of claim 9,

The second request message includes service information associated with some of the services included in the first service list,

And the second service list includes services that match the service information.
The method of claim 9,

The first device is a device, characterized in that the role of the Generic Attribute (GATT) client in the relationship of transmitting and receiving data by establishing a Bluetooth connection between the first device and the second device.
The method of claim 9,

The second device performs a role of a GATT server in a relationship of transmitting and receiving data by forming a Bluetooth connection between the first device and the second device.
The method of claim 9,

The first service list is a device, characterized in that some of the services supported by the first device determined based on a predetermined priority.
The method of claim 15,

Some of the services supported by the first device are services having the highest priority.