WO2018009040A1 - Procédé et dispositif de transmission/réception de données à l'aide d'une technologie bluetooth - Google Patents

Procédé et dispositif de transmission/réception de données à l'aide d'une technologie bluetooth Download PDF

Info

Publication number
WO2018009040A1
WO2018009040A1 PCT/KR2017/007327 KR2017007327W WO2018009040A1 WO 2018009040 A1 WO2018009040 A1 WO 2018009040A1 KR 2017007327 W KR2017007327 W KR 2017007327W WO 2018009040 A1 WO2018009040 A1 WO 2018009040A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
server
characteristic
client
request message
Prior art date
Application number
PCT/KR2017/007327
Other languages
English (en)
Korean (ko)
Inventor
권영환
Original Assignee
엘지전자(주)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자(주) filed Critical 엘지전자(주)
Publication of WO2018009040A1 publication Critical patent/WO2018009040A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information

Definitions

  • the present invention relates to a method and apparatus for transmitting and receiving data using Bluetooth, which is a short-range technology, in a wireless communication system, and more particularly, to a method and apparatus for transmitting and receiving mass information 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.
  • a user 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.
  • the device may mean an apparatus and an apparatus.
  • 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.
  • 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.
  • Another object of the present invention is to provide a method and apparatus for transmitting and receiving association information associated with a plurality of devices associated with a device.
  • Another object of the present invention is to provide a method and apparatus for storing and transmitting and receiving specific information among association information of a plurality of devices associated with a device.
  • an object of the present invention is to provide a method and apparatus for transmitting and receiving data exceeding the size that can be stored in one characteristic (Characteristic).
  • the present invention provides a method and apparatus for a client to send and receive data with a server in Bluetooth for solving the above problems.
  • a method for a client to transmit and receive data with a server in Bluetooth comprises the steps of forming a Bluetooth Low Energy (LE) connection with the server; Sending a first read request message requesting reading of a first characteristic including first information to the server; Receiving a read response message containing the first information from the server; Performing a change procedure for changing the information stored in the first characteristic to second information; Sending a second read request message to the server requesting reading of the first characteristic; And receiving a read response message including the second information from the server, wherein the first information and the second information are information divided from specific information stored in the server.
  • LE Bluetooth Low Energy
  • the performing of the change procedure may include: sending a first write request message requesting writing of a control characteristic for indicating a change of information included in the first characteristic to the server; And receiving from the server a first write response message indicating that the information of the first characteristic has changed in response to the first write request message, wherein the information included in the first characteristic is a first response. The information is changed from the second information.
  • the first write request message includes at least one of an operation code indicating change of information included in the first characteristic or counter information indicating information to be changed.
  • the first characteristic includes counter information indicating information included in the first characteristic or count information indicating the number of pieces of information divided from the specific information.
  • the specific information is association information associated with devices associated with the server, or UUID information of associated devices.
  • the first characteristic may further include at least one of first list information indicating whether all of the related information is divided or only related information of a specific state or order information indicating the order of the divided information. Include.
  • the order information indicates one of recent use, frequent use, and no order.
  • the list information when the list information indicates that only relevant information of a specific state is divided, the list information further includes second list information indicating the specific state.
  • the present invention further includes performing a configuration procedure for configuring specific information to be stored by the server.
  • the performing of the configuration procedure may include: sending a second write request message requesting writing of a second characteristic indicating configuration of the specific information to the server; And receiving the second write request message from the server, wherein the second write request message includes at least one of list information indicating the specific information or order information indicating a division order of the specific information. .
  • the communication unit for communicating with the outside by wireless or wired;
  • a memory for storing data;
  • a processor operatively connected to the communication unit, wherein the processor forms a Bluetooth Low Energy (LE) connection with a server, transmits to the server, and reads a read response message including the first information from the server.
  • the processor forms a Bluetooth Low Energy (LE) connection with a server, transmits to the server, and reads a read response message including the first information from the server.
  • a Bluetooth Low Energy (LE) connection with a server
  • the processor forms a Bluetooth Low Energy (LE) connection with a server, transmits to the server, and reads a read response message including the first information from the server.
  • Perform a change procedure for receiving, changing the information stored in the first characteristic to second information, sending a second read request message requesting reading of the first characteristic to the server, and transmitting the second read request message from the server.
  • Receiving a read response message comprising a second information, wherein the first information and the second information is information
  • the divided data can be alternately stored in one characteristic by dividing the data exceeding the size of data that can be stored in one characteristic.
  • FIG. 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.
  • FIG. 2 shows an example of an internal block diagram of a device that can implement 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.
  • FIG. 4 is a diagram illustrating an example of a structure of a GATT (Generic Attribute Profile) of Bluetooth low power energy.
  • GATT Generic Attribute Profile
  • FIG. 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.
  • FIG. 6 is a diagram illustrating an example of a characteristic for transmitting and receiving information of devices associated with a device to which the present invention may be applied.
  • 7 and 8 illustrate an example of a method and a data format for transmitting and receiving large data through one characteristic to which the present invention is applied.
  • FIG. 9 is a diagram illustrating an example of a method for dividing data to which the present invention is applied and storing the data in one characteristic.
  • 10 to 12 are diagrams illustrating an example of a method and a data format for transmitting and receiving divided data through one characteristic to which the present invention is applied.
  • FIG. 13 is a flowchart illustrating an example of a method for a client to which the present invention is applied to receive divided data from a server through one characteristic.
  • FIG. 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.
  • BLE Bluetooth Low Energy
  • BLE technology 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.
  • BR / EDR Bluetooth Basic Rate / Enhanced Data Rate
  • the BLE technology simplifies the connection procedure between devices, and the packet size is smaller than that of the Bluetooth BR / EDR technology.
  • the number of RF channels is 40
  • the data rate supports 1Mbps
  • the topology is a scatternet structure
  • latency is 3ms
  • (6) output power is less than 10mW (10dBm)
  • (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.
  • the server 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.
  • the server device sends a notification message and an indication message to the client device to provide data information to the client device.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the wireless communication system may configure Personal Area Networking (PAN) through Bluetooth technology.
  • PAN Personal Area Networking
  • the wireless communication system by establishing a private piconet between devices, files, documents, and the like can be exchanged quickly and securely.
  • FIG. 2 shows an example of an internal block diagram of a device that can implement the methods proposed herein.
  • 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.
  • 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).
  • Bluetooth Interface Bluetooth Interface
  • 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.
  • ASICs application-specific integrated circuits
  • 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.
  • ROM read-only memory
  • RAM random access memory
  • 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.
  • 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 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.
  • 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.
  • FIG. 3 is a diagram illustrating an example of a Bluetooth communication architecture to which the methods proposed herein may be applied.
  • 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.
  • BR Basic Rate
  • EDR Enhanced Data Rate
  • LE Bluetooth Low Energy
  • 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.
  • PFS layer Global System for Mobile Communications
  • 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).
  • LMP link manager protocol
  • the link manager layer 16 may perform the following functions.
  • 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.
  • L2CAP logical link control and adaptation protocol
  • Protocol 22
  • GATT generic attribute profile
  • GAP BR / EDR profile
  • 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.
  • 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.
  • 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.
  • the Bluetooth LE protocol stack is a controller stack 30 operable to handle timing critical radio interface and a host stack operable to process high level data. (Host stack, 40).
  • 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.
  • 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.
  • PHY physical layer
  • link layer 34 link layer
  • host controller interface 36 host controller interface
  • 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.
  • GFSK Gausian Frequency Shift Keying
  • 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.
  • 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.
  • Bluetooth LE 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.
  • BR / EDR Base Rate / Enhanced Data Rate
  • 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).
  • the Request message is a message for requesting and delivering specific information from the client device to the server device
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the generic attribute profile 44 and the attribute protocol may use features to describe the state and services of a device, and how features relate to each other and how they are used.
  • 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.
  • 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.
  • 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.
  • 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.
  • the scanning device when the scanning device receives some advertising packets from the advertising device, the scanning device should send a scan request to the advertising device.
  • 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.
  • the advertising device performs an advertising procedure to perform a non-directional broadcast to the devices in the area.
  • non-directional broadcast refers to broadcast in all directions rather than broadcast in a specific direction.
  • Non-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.
  • the advertising procedure may be used to provide periodic broadcast of user data to the scanning devices that are listening on the advertising 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.
  • 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.
  • the scanning device 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.
  • the scanning device 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.
  • Bluetooth devices 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.
  • 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.
  • the advertising procedure can be the goal, so that only one device will respond to the advertising.
  • the connection may be initiated by sending a connection request to the advertising device via the advertising (broadcast) physical channel.
  • 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.
  • PDUs advertisement packet data units
  • 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.
  • 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.
  • scanning states There are two types of scanning states: passive scanning and active scanning, each scanning type being determined by the host.
  • ScanInterval is defined as the interval (interval) between the starting points of two consecutive scan windows.
  • 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.
  • the link layer When passive scanning, the link layer only receives packets and does not transmit any packets.
  • the link layer 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.
  • the link layer enters the initiation state by the indication of the host (stack).
  • the link layer When the link layer is in the initiating state, the link layer performs listening for the advertising channel indexes.
  • the link layer listens for the advertising channel index during the scan window period.
  • 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.
  • connection 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.
  • 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.
  • BLE devices use the packets defined below.
  • 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.
  • the PDU 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
  • PDU Packet Data Unit
  • 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 )
  • 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.
  • 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.
  • 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.
  • the data channel PDU has a 16-bit header, payloads of various sizes, and may include a message integrity check (MIC) field.
  • MIC message integrity check
  • the procedure, state, packet format, etc. in the BLE technology may be applied to perform the methods proposed herein.
  • FIG. 4 is a diagram illustrating an example of a structure of a GATT (Generic Attribute Profile) of Bluetooth low power energy.
  • GATT Generic Attribute Profile
  • the GATT Generic Attribute Profile
  • a peripheral device for example, a sensor device
  • a central device is a GATT. It acts as a client.
  • 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).
  • UUID Universal Unique Identifier
  • 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.
  • Type the type of attribute
  • FIG. 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.).
  • 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.
  • 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.
  • the client may transmit a scan request message to the server to obtain additional data (eg, a server device name) to the server.
  • additional data eg, a server device name
  • the server transmits a scan response message including additional data to the client in response to a scan request message.
  • 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.
  • 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.
  • the client transmits a connection request message for establishing a Bluetooth connection with the server to the server (S5020).
  • the server and client then perform a security establishment procedure.
  • the security establishment procedure may be interpreted as or included in Secure Simple Pairing.
  • the security establishment procedure may be performed through Phase 1 to Phase 3 steps.
  • a pairing procedure (Phase 1) is performed between the server and the client (S5030).
  • 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.
  • Phase 2 a legacy pairing or a secure connection is performed between the server and the client (S5040).
  • STK Temporary Key and Short Term Key
  • STK Short Term Key
  • LTK long term key
  • LTK Long Term Key
  • SSP Phase 3 a key distribution procedure is performed between the server and the client (S5050).
  • ATT_MTU-1 octets The longest attribute that can be sent in a single packet.
  • ATT_MTU means the maximum size of a packet transmitted between the client and the server.
  • 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.
  • 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.
  • the present invention proposes a method of transmitting and receiving data through one characteristic by dividing the data when the maximum length that can be stored in one characteristic is exceeded to solve this problem.
  • FIG. 6 is a diagram illustrating an example of a characteristic for transmitting and receiving information of devices associated with a device to which the present invention may be applied.
  • the server device may transmit information related to its association status to the client device through an association status characteristic that indicates the association status of the current server illustrated in FIG. 6A.
  • the server device may transmit information related to devices connected, paired, and / or bonded with the server device to the client device through a property indicating the connection state.
  • the association status property may be composed of a Number of Associations field, a Peer device ID field, a Bearer field, and a Status field.
  • the Number of Associations field is a field indicating the number of devices present in association with the server device.
  • the number of Peer device ID fields, Bearer fields, and Status fields may be determined according to the value of the Number of Associations field.
  • the value of the Number of Associations field is 1, there is only one Peer device ID field, the Bearer field, and the Status field. If the value of the Number of Associations field is n, the Peer device ID field, the Bearer field, and the Status field are n. There may be n fields each.
  • the Peer device ID field is a field indicating an address of a peer device associated with a server device.
  • the address of the peer device may be a public address type or a random address type according to a transmission type.
  • the Bearer field is a field indicating a connection type with a peer device. For example, when the peer device is connected via Bluetooth BR / EDR, the Bearer field is set to a value indicating the Bluetooth BR / EDR, and when the peer device is connected via Bluetooth LE, the Bearer field is set to Bluetooth LE. It is set to the value indicated.
  • the Status field is a field indicating the association status with the peer device and may be configured as shown in FIG. For example, when the 0 th bit is set to 1 in FIG. 6B, the server device indicates that the server device is connected to the peer device.
  • Bluetooth is based on one-to-one connection, but multiple devices can be connected to one device via Bluetooth. That is, one to many connections may be possible.
  • the number of devices bonded or paired with the server device is large, there is a problem in that it is not possible to provide both the information of the server device and the associated devices with the size of the currently defined characteristic.
  • a plurality of devices may be associated with each other.
  • a server device is associated with multiple sensors (eg, window sensor, temperature sensor, illuminance sensor, humidity sensor, etc.), the server device may include all information related to the devices associated with one characteristic. Can't.
  • a method of dividing specific information into a plurality of pieces and alternately storing the divided information in one characteristic transmits all the divided information to the client device.
  • 7 and 8 illustrate an example of a method and a data format for transmitting and receiving large data through one characteristic to which the present invention is applied.
  • the specific information exceeds the maximum length of data that can be stored in one characteristic, the specific information is divided and stored in one of the divided information and transmitted to the client device.
  • the information stored in the property may be updated with other divided information to transmit all the divided information to the client device.
  • the client establishes a BLE connection with the server through the aforementioned method.
  • the client which has established a BLE connection with the server, may transmit a read request message to the server to request attribute values of specific characteristics of the server. However, if the attribute value of the characteristic exceeds the maximum size of a packet that can be transmitted in a single packet between the server and the client, the client sends a read blob request message to the server to request the attribute value of the specific characteristic.
  • the server When the server receives the attribute value of a specific characteristic from the client, the server transmits the attribute value of the specific characteristic to the client through the read blob response message by the maximum size of the packet.
  • the client may receive an attribute value of a specific characteristic through a read blob response message from the server.
  • the client sends a read blob request message to the server until all the attribute values of a particular attribute have been sent, and when the server receives a read blob request message from the client, it continues reading to the client until all attribute values of the particular attribute have been sent.
  • the attribute value may be transmitted through a blob response message (S7010).
  • the server may update the attribute value of the specific characteristic with the additional information (S7020).
  • a server may store the data according to the maximum size of the attribute value.
  • the data is divided into a plurality of data and one of the plurality of divided data is stored in the property.
  • the server When the server transmits all the data stored in the characteristic to the client, the server updates (or replaces) the other data among the plurality of data obtained by dividing the characteristic data.
  • the server transmits an indication message to the client to inform the client that the property value of the property has been updated (S7030).
  • the server sends an indication message to the client to inform that there is additional data.
  • FIG. 8 is a diagram illustrating an example of an indication message when data stored in a property is association information of devices associated with a server.
  • an indication message for notifying that the property value has been updated may include an MD field, a CL field, an RFU field, and a # of Association field. It may include.
  • MD Me Data field (1 bit): field indicating whether additional data exists. If the bit of the MD field is enabled, the data of the property is updated to indicate that there is additional data.
  • CL Completed List field (1 bit): A field indicating whether all association information is divided or only a part of association information is divided. It may indicate whether all of the association information is divided through the CL field, or at least one of the association information, the bonding information, or the pairing information is divided.
  • RFU Reserved for Future Use
  • field (4 bit): An empty field for future use.
  • # of Association field (10 bits): field indicating the number of devices associated with the server device.
  • the client receiving the indication message from the server may recognize that additional data exists by updating the property value, and transmits a confirmation message to the server in response to the indication message (S7040).
  • the client may receive the updated attribute value of the property from the server through the same method as in operation S7010 (S7050).
  • the client and the server may repeatedly perform steps S7020 to S7050 until all of the plurality of divided data are transmitted. When the plurality of divided data are transmitted and received, the procedure may be terminated.
  • FIG. 9 is a diagram illustrating an example of a method for dividing data to which the present invention is applied and storing the data in one characteristic.
  • the server may divide the specific data into a plurality of data and store the specific data in the characteristic.
  • the server may configure the association information to be stored in the characteristic of all association information (All Association Information).
  • the configuration of the association information may receive configuration information related to the configuration of the association information from the client, or the server may directly configure the association information.
  • the server when the server receives configuration information related to the configuration of the connection information from the client, the server acquires and configures only the connection information related to the connected device.
  • the server device may obtain and configure related information of all devices associated with the same, or may obtain and configure related information including at least one of connection information, bonding information, and / or pairing information.
  • the server may divide the configured association information into a plurality of data according to the maximum size.
  • each of the plurality of divided data is referred to as a bank.
  • the server selects each divided bank in order and stores them in the property. That is, the divided banks are selected in a specific order, and the selected banks are stored in a related property (hereinafter, referred to as a related property).
  • the server receives a message requesting an attribute value of the association status characteristic from the client, the server sends the attribute value of the association status characteristic to the client through read response or read blob response messages.
  • the server sends all of the attribute values of the association status property to the client, the server selects the next bank in a specific order and updates (or replaces) the property values of the properties with the selected bank.
  • the server may change the property value of the association status property to another Bank. Replace with, and send a write response message to the client indicating that the attribute value of the association status property has changed.
  • a write request message from the client requesting the writing of a particular property (eg, a control point property) instructing replacement of the property value of the property
  • the server may change the property value of the association status property to another Bank. Replace with, and send a write response message to the client indicating that the attribute value of the association status property has changed.
  • the client may change the attribute value of the association status characteristic to a specific bank regardless of the order by transmitting a value indicating a bank (eg, a specific number of the order) indicating the bank to be changed in the write request message.
  • a value indicating a bank eg, a specific number of the order
  • the server After the server changes the attribute value of the association status property and receives from the client a read response or read blob response messages requesting the changed attribute value of the association status property, the server changes the read response message or read blob response messages to the client. Attribute values can be sent to the client.
  • data when data exceeding the maximum size that can be stored in one characteristic occurs, data can be divided according to the maximum size and stored in one characteristic, and the divided data are alternately stored in one characteristic in a specific order.
  • One characteristic is that data exceeding the maximum size can be sent to the client.
  • 10 to 12 are diagrams illustrating an example of a method and a data format for transmitting and receiving divided data through one characteristic to which the present invention is applied.
  • the server device when the information configured by the server device to store in one characteristic exceeds the maximum size of data that can be stored in the characteristic, the server device divides the configured information into a plurality of data and assigns the characteristic to the characteristic. Can be stored.
  • the client establishes a BLE connection with the server through the aforementioned method.
  • the client which has established a BLE connection with the server, transmits a write request message for writing a configuration characteristic to the server in order to request configuration of specific information (S10010).
  • the write request message may include list information indicating the type of information to be configured by the server, when the configured information is divided, order information indicating the order of the divided data, and / or count information related to the number of types of information to be configured. Can be.
  • the server may transmit a write response message to the client in response to the write request message (S10020).
  • the server may store the first bank of the plurality of banks divided according to the order information in a specific characteristic.
  • the server may inform the client how the specific information is configured through the write response message or the separate message of step S10020.
  • the write response message or the separate message of step S10020 may include list information indicating what kind of information is configured, counter information indicating the order of banks stored in the current property, number information indicating the number of all banks, and divided banks. May include order information indicating the order and / or bank information associated with the current bank.
  • the client may recognize the information configured by the server through a write response message or a separate message transmitted from the server, and transmits a read blob request message to the server to request an attribute value of a specific characteristic in which the configured information is stored (S10030). .
  • the server transmits a read blob response message including an attribute value of a specific characteristic to the client in response to the read blob request message (S10040).
  • the header of the read blob response message may include information related to an attribute value included in the read blob response message.
  • the header of the read blob message includes list information indicating the type of the configured information, order information indicating the order of divided banks, counter information indicating which bank is the attribute value transmitted through the current read blob response message, and segmentation. It may include number information indicating the total number of the banks, and Bank information associated with the current Bank.
  • the client may repeatedly send the read blob request message to the server until all the attribute values stored in the specific characteristic are transmitted, and may receive all the attribute values of the specific characteristic through the read response message from the server.
  • the client may determine whether all the attribute values of a specific characteristic are transmitted through a specific bit or the position of the attribute value included in the read blob response message.
  • the client If the client recognizes that all the attribute values of the specific characteristic have been transmitted, the client transmits a write request message requesting the writing of the control point characteristic for instructing the change of the attribute value of the specific characteristic (S10050).
  • the write request message may include an operation code indicating a change of an attribute value of a specific characteristic and bank information indicating a bank to be changed.
  • the server transmits a write response message to the client in response to the write request message (S10060).
  • the server selects a bank according to the write request message sent from the client, and changes the attribute value of a specific characteristic from the data of the existing bank to the data of the selected bank (S10070).
  • Step S10070 may be performed before step S10060.
  • the client may receive the changed attribute value of the specific characteristic from the server through the same method as steps S10030 and S10040 (S10080 and S10090).
  • Steps S10030 to S10090 may be repeatedly performed until all the divided banks are transmitted to the client.
  • 11 is a diagram illustrating an example of each message and characteristic when specific information is association information.
  • FIG. 11A illustrates an example of a header of a read blob response message and a read response message or a separate message for notifying a client of what kind of information is configured when the specific information is related information.
  • Association Status Info This field provides summary information of Association Status. It contains the following information. This field can be repeated for each bank.
  • Paired Device List (4 bit): Information indicating whether information on a paired device is included and a coupling state, and each bit represents LE Secure Connection Pairing, Authenticated MITM Protection, Unauthenticated no MITM protection, and No Security requirements.
  • Bonded Device List (1 bit): Indicates whether or not the information of the bonded device is included.
  • Association Order Information indicating the order of the divided association information, and may indicate the following order according to the bit.
  • Bank Counter The number of the bank stored in the current property. The maximum value of the bank counter is equal to the value of the Number of Bank.
  • Number of Bank Total number of banks divided
  • Association Number Association number of the currently selected bank (number of associated devices according to the selected bank).
  • 11B illustrates an example of a write request message transmitted from a client device or a configuration property of a server to configure information to be stored in the association status property.
  • Association Status Info A field indicating an association type of information to be configured, such as a pairing type, a connection type, a bonding type, and the order of divided banks.
  • Paired Device List (4 bit): Information indicating whether information on a paired device is included and a coupling state, and each bit represents LE Secure Connection Pairing, Authenticated MITM Protection, Unauthenticated no MITM protection, and No Security requirements.
  • Bonded Device List (1 bit): Indicates whether or not the information of the bonded device is included.
  • Association Order Information indicating the order of the divided association information, and may indicate the following order according to the bit.
  • Association Number The number of associations provided with the association status. That is, the number of associations configured (or selected) by the server. If the CL indicates that all association types have been split, the value of Association Number may be '0x00000000' because all association information is provided.
  • 11C illustrates an example of a write request message and a control point characteristic for changing an attribute value stored in the association state characteristic.
  • Opcode The action code for changing the attribute value of the association status property. If the opcode is a value that changes the attribute value of the association state property, the server changes the attribute value of the association state property from the previous bank to the next bank according to the Bank Number field.
  • -Bank Number A parameter indicating the number of the bank to be changed. If the bank indicates a specific number, the server changes the attribute value of the association status property to the corresponding bank. If no value is indicated, the server changes the attribute value of the Association Status property to Bank in the following order.
  • FIG. 12 is a diagram illustrating another example of each message and characteristic when specific information is client list information related to devices performing a client role of GATT and specific characteristics are client list characteristics including client list information. .
  • 12A illustrates another example of a header of a read blob response message and a read response message or a separate message for notifying a client of what kind of information is configured when specific information is client list information. Indicates.
  • Client list properties are identified using UUID ⁇ GATT Client List >>.
  • the client list property is optionally used to provide client list information of the server.
  • the Client List Info field indicates whether the client list property provides a list of all clients and the type of the client list property such as the type of service UUID (16 bit, 32 bit and / or 128 bit) included in the client list property. Contains information.
  • CL Completed List (1 bit): Indicates whether the server provides all client list information through the client list characteristic.
  • 16 bit UUID List (1 bit): Indicates whether the server provides a client list corresponding to 16 bit UUID services.
  • 128 bit UUID List (1 bit): Indicates whether the server provides a client list corresponding to 128 bit UUID services.
  • Client UUID Selected Policy (2 bits): Information indicating the selection criteria of the divided client list information, and may indicate the following criteria according to the bit.
  • Bank Counter The number of the bank stored in the current property. The maximum value of the bank counter is equal to the value of the Number of Bank.
  • Number of Bank Total number of banks divided
  • FIG. 12B illustrates an example of a write request message transmitted by a client device or a client list configuration characteristic of a server to configure information to be stored in the client list characteristic.
  • Client List Info A field indicating the type of UUID to be constructed and the criteria by which divided banks are selected.
  • 16 bit UUID List (1 bit): Indicates whether the server provides a client list corresponding to 16 bit UUID services.
  • 128 bit UUID List (1 bit): Indicates whether the server provides a client list corresponding to 128 bit UUID services.
  • Client UUID Selected Policy (2 bits): Information indicating the selection criteria of the divided client list information, and may indicate the following criteria according to the bit.
  • Client List Number indicates the number of client UUIDs of the configured client list information. This value is used to determine the number of divided banks. If the CL indicates that the UUID types of all client lists have been split, the value of the Client List Number may be '0x00000000' because all client UUIDs are provided.
  • 12C illustrates an example of a write request message and a control point characteristic for changing an attribute value stored in the client list characteristic.
  • Opcode The action code for changing the attribute value of the client list property. If the opcode is a value that changes the attribute value of the client list attribute, the server changes the attribute value of the client list attribute from the previous bank to the next bank according to the Bank Number field.
  • -Bank Number a parameter indicating the number of the bank to be changed.
  • the server changes the attribute value of the client list property to the corresponding bank. If no value is indicated, the server changes the attribute value of the Association Status property to Bank in the following order.
  • FIG. 13 is a flowchart illustrating an example of a method for a client to which the present invention is applied to receive divided data from a server through one characteristic.
  • a client may receive data by dividing a large size data by changing data stored in one characteristic from a server.
  • the client establishes a Bluetooth low energy (LE) connection with the server through the above-described method (S13010).
  • LE Bluetooth low energy
  • the client transmits a first read request message for requesting reading of the first characteristic including the first information among the plurality of pieces of information divided from the specific information through the formed Bluetooth LE (S13020).
  • the client may transmit the first read blob request message to the server instead of the first read request message.
  • the first read request message and the first read blob request message may be configured in the same manner as the read request message and the read blob request message described with reference to FIGS. 10 to 12.
  • the client receives a read response message including the first information in response to the first read request message from the server (S13030). If the client transmits the first read blob request message to the server in step S13020, the client may receive a first read blob response message including a part of the first information. All can be sent from the server.
  • the first read response message and the first read blob response message may be configured in the same manner as the read response message and the read blob response message described with reference to FIGS. 10 to 12.
  • the client may perform a change procedure for changing the information stored in the first characteristic to the second information among the plurality of pieces of information divided from the specific information. It may be (S13040).
  • the procedure for changing the first information of the first characteristic to the second information may be the same as the procedure and messages for changing the data included in the specific characteristic described with reference to FIGS. 10 to 12.
  • the client transmits a second read request message to the server in order to request the second information which is the changed information of the first characteristic (S13050).
  • the client may transmit a second read blob request message to the server instead of the second read request message.
  • the second read request message and the second read blob request message may be configured in the same manner as the read request message and the read blob request message described with reference to FIGS. 10 to 12.
  • the client receives a read response message including the second information in response to the second read request message from the server (S13060). If the client transmits the second read blob request message to the server in step S13050, the client may receive a second read blob response message including a part of the second information. All can be sent from the server.
  • the second read response message and the second read blob response message may be configured in the same manner as the read response message and the read blob response message described with reference to FIGS. 10 to 12.
  • the client may repeatedly perform steps S13040 to S13060 to receive the changed information.
  • Each of the first information and the second information may be one of a plurality of pieces of information divided from the specific information, and the specific information may be association information of a server device or client list information indicating devices performing a client role.
  • the client may alternately store information divided from the specific information in one characteristic and receive all the specific information.
  • Orientation-based device discovery method 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)

Abstract

La présente invention concerne un procédé et un dispositif au moyen desquels un client transmet/reçoit des données à destination/en provenance d'un serveur par Bluetooth. La présente invention concerne un procédé et un dispositif qui : forment une connexion basse énergie (LE) Bluetooth avec un serveur ; transmettent au serveur un premier message de requête de lecture pour demander la lecture d'une première caractéristique comprenant des premières informations ; reçoivent un message de réponse de lecture comprenant les premières informations provenant du serveur ; effectuent une procédure de changement pour modifier les informations stockées dans la première caractéristique en de secondes informations ; transmettent au serveur un second message de requête de lecture pour demander la lecture de la première caractéristique ; et reçoivent un message de réponse de lecture comprenant les secondes informations provenant du serveur, les premières informations et les secondes informations étant des informations divisées à partir d'informations spécifiques stockées dans le serveur.
PCT/KR2017/007327 2016-07-08 2017-07-07 Procédé et dispositif de transmission/réception de données à l'aide d'une technologie bluetooth WO2018009040A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201662359715P 2016-07-08 2016-07-08
US62/359,715 2016-07-08
US201662369222P 2016-08-01 2016-08-01
US62/369,222 2016-08-01

Publications (1)

Publication Number Publication Date
WO2018009040A1 true WO2018009040A1 (fr) 2018-01-11

Family

ID=60912208

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/007327 WO2018009040A1 (fr) 2016-07-08 2017-07-07 Procédé et dispositif de transmission/réception de données à l'aide d'une technologie bluetooth

Country Status (1)

Country Link
WO (1) WO2018009040A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019235892A1 (fr) * 2018-06-07 2019-12-12 엘지전자 주식회사 Procédé et appareil de commande de puissance d'un dispositif au moyen d'une technologie bluetooth
KR102177201B1 (ko) * 2020-06-09 2020-11-10 (주)한성기술단 무선 통신시스템에서 데이터의 송수신 방법, 장치 및 시스템
KR102197942B1 (ko) * 2020-06-09 2021-01-04 (주)한성기술단 무선 통신시스템에서 데이터의 송수신 방법, 장치 및 시스템
KR102221849B1 (ko) * 2020-06-09 2021-03-03 (주)한성기술단 무선 통신시스템에서 데이터의 송수신 방법, 장치 및 시스템
KR20210055936A (ko) * 2019-11-08 2021-05-18 주식회사제이엘텍코퍼레이션 블루투스 환경에서 단말기와 스마트폰 간의 자동접속방법 및 이를 이용한 컴퓨터 보안유지방법

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110021142A1 (en) * 2009-07-24 2011-01-27 Prasanna Desai Method and system for a dual-mode bluetooth low energy device
KR20120063926A (ko) * 2010-12-08 2012-06-18 한국전자통신연구원 비대칭 클러스터링 파일시스템에서의 패리티 산출 방법
KR20150080952A (ko) * 2013-12-30 2015-07-13 은호 한 개인정보 일부 저장을 통한 사용자 인증 결제 방법 및 시스템
WO2015163680A1 (fr) * 2014-04-21 2015-10-29 엘지전자(주) Procédé et appareil pour transmettre et recevoir des données à l'aide d'une technique bluetooth à faible consommation d'énergie dans un système de communication sans fil
KR20160065886A (ko) * 2013-11-11 2016-06-09 엘지전자 주식회사 블루투스 연결 방법 및 장치

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110021142A1 (en) * 2009-07-24 2011-01-27 Prasanna Desai Method and system for a dual-mode bluetooth low energy device
KR20120063926A (ko) * 2010-12-08 2012-06-18 한국전자통신연구원 비대칭 클러스터링 파일시스템에서의 패리티 산출 방법
KR20160065886A (ko) * 2013-11-11 2016-06-09 엘지전자 주식회사 블루투스 연결 방법 및 장치
KR20150080952A (ko) * 2013-12-30 2015-07-13 은호 한 개인정보 일부 저장을 통한 사용자 인증 결제 방법 및 시스템
WO2015163680A1 (fr) * 2014-04-21 2015-10-29 엘지전자(주) Procédé et appareil pour transmettre et recevoir des données à l'aide d'une technique bluetooth à faible consommation d'énergie dans un système de communication sans fil

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019235892A1 (fr) * 2018-06-07 2019-12-12 엘지전자 주식회사 Procédé et appareil de commande de puissance d'un dispositif au moyen d'une technologie bluetooth
US11445453B2 (en) 2018-06-07 2022-09-13 Lg Electronics Inc. Method and apparatus for controlling power of device by using bluetooth technology
KR20210055936A (ko) * 2019-11-08 2021-05-18 주식회사제이엘텍코퍼레이션 블루투스 환경에서 단말기와 스마트폰 간의 자동접속방법 및 이를 이용한 컴퓨터 보안유지방법
KR102308076B1 (ko) 2019-11-08 2021-10-05 주식회사제이엘텍코퍼레이션 블루투스 환경에서 단말기와 스마트폰 간의 자동접속방법 및 이를 이용한 컴퓨터 보안유지방법
KR102177201B1 (ko) * 2020-06-09 2020-11-10 (주)한성기술단 무선 통신시스템에서 데이터의 송수신 방법, 장치 및 시스템
KR102197942B1 (ko) * 2020-06-09 2021-01-04 (주)한성기술단 무선 통신시스템에서 데이터의 송수신 방법, 장치 및 시스템
KR102221849B1 (ko) * 2020-06-09 2021-03-03 (주)한성기술단 무선 통신시스템에서 데이터의 송수신 방법, 장치 및 시스템

Similar Documents

Publication Publication Date Title
WO2018074892A1 (fr) Procédé et dispositif d'émission et de réception de données à l'aide de la technologie bluetooth
WO2018135926A1 (fr) Procédé et appareil de communication bluetooth
WO2016182404A1 (fr) Procédé et dispositif destinés à la connexion de moyens de communication de remplacement à l'aide de la technologie bluetooth à faible énergie
WO2015194854A1 (fr) Procédé et appareil d'établissement d'une connexion entre des dispositifs à l'aide d'une technologie bluetooth à faible énergie énergie (le)
WO2016167541A1 (fr) Procédé et appareil pour connecter des dispositifs à l'aide de la technologie bluetooth à faible consommation d'énergie
WO2016175454A1 (fr) Procédé et dispositif de transmission/réception de données utilisant un réseau maillé bluetooth
WO2018038459A1 (fr) Procédé de commande de dispositif à l'aide d'une technologie bluetooth, et appareil
WO2018097687A1 (fr) Procédé et appareil d'émission/réception de données dans un réseau maillé au moyen de bluetooth
WO2016178542A1 (fr) Procédé et appareil pour envoyer et recevoir des données par bluetooth
WO2018048268A1 (fr) Procédé et appareil de connexion de dispositif en utilisant la technologie bluetooth
WO2018169380A1 (fr) Procédé et appareil de traitement de signal audio au moyen d'une technologie bluetooth
WO2016039598A1 (fr) Procédé et dispositif destinés à commander un dispositif en utilisant la technologie bluetooth
WO2017043869A1 (fr) Procédé et appareil de commande de dispositifs au moyen de la technologie bluetooth
WO2018222024A1 (fr) Procédé et appareil permettant de connecter des dispositifs à l'aide de la technologie bluetooth à faible consommation d'énergie
WO2016175638A1 (fr) Procédé et dispositif pour attribuer une adresse de dispositif dans un réseau maillé bluetooth
WO2016122186A1 (fr) Procédé et dispositif de commande d'un dispositif en utilisant la technologie bluetooth
WO2018021877A1 (fr) Procédé et appareil d'établissement de connexion à un dispositif
WO2015163680A1 (fr) Procédé et appareil pour transmettre et recevoir des données à l'aide d'une technique bluetooth à faible consommation d'énergie dans un système de communication sans fil
WO2018066925A1 (fr) Procédé et appareil de transmission et de réception de données utilisant la technologie bluetooth
WO2016017907A1 (fr) Procédé et appareil de commande d'un dispositif électronique dans un système de communication sans fil prenant en charge une communication bluetooth
WO2015137601A1 (fr) Procédé et dispositif pour adapter une vitesse de transmission de données dans un système de communication sans fil
WO2018124852A1 (fr) Procédé et dispositif de commande de dispositif utilisant la technologie bluetooth
WO2016175640A1 (fr) Procédé et dispositif pour émettre/recevoir des données dans un réseau maillé via bluetooth
WO2016036139A2 (fr) Procédé et dispositif de commande d'un dispositif à l'aide d'une technologie bluetooth à basse énergie (le)
WO2016175575A1 (fr) Procédé et dispositif pour transmettre/recevoir des données à l'aide d'un réseau maillé bluetooth

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17824595

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17824595

Country of ref document: EP

Kind code of ref document: A1