WO2016017909A1 - 블루투스 통신을 지원하는 무선 통신 시스템에서 전자기기를 제어하기 위한 방법 및 장치 - Google Patents
블루투스 통신을 지원하는 무선 통신 시스템에서 전자기기를 제어하기 위한 방법 및 장치 Download PDFInfo
- Publication number
- WO2016017909A1 WO2016017909A1 PCT/KR2015/004675 KR2015004675W WO2016017909A1 WO 2016017909 A1 WO2016017909 A1 WO 2016017909A1 KR 2015004675 W KR2015004675 W KR 2015004675W WO 2016017909 A1 WO2016017909 A1 WO 2016017909A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bluetooth
- information
- edr
- connection
- handover
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 340
- 238000004891 communication Methods 0.000 title claims description 275
- 230000004044 response Effects 0.000 claims abstract description 143
- 230000005540 biological transmission Effects 0.000 claims description 17
- 230000008859 change Effects 0.000 claims description 7
- 238000006243 chemical reaction Methods 0.000 claims 2
- 238000005516 engineering process Methods 0.000 abstract description 27
- 108091006146 Channels Proteins 0.000 description 273
- 238000010586 diagram Methods 0.000 description 35
- 230000008569 process Effects 0.000 description 22
- 230000000977 initiatory effect Effects 0.000 description 17
- 230000002093 peripheral effect Effects 0.000 description 12
- 238000001914 filtration Methods 0.000 description 8
- 239000003999 initiator Substances 0.000 description 8
- 230000006870 function Effects 0.000 description 7
- 238000012790 confirmation Methods 0.000 description 6
- 238000003860 storage Methods 0.000 description 6
- 230000006978 adaptation Effects 0.000 description 4
- 230000006399 behavior Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000000060 site-specific infrared dichroism spectroscopy Methods 0.000 description 3
- 238000001228 spectrum Methods 0.000 description 3
- 101001080597 Spinacia oleracea 50S ribosomal protein 5 alpha, chloroplastic Proteins 0.000 description 2
- 230000002457 bidirectional effect Effects 0.000 description 2
- 230000015572 biosynthetic process Effects 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 241000722721 Capparis Species 0.000 description 1
- 235000017336 Capparis spinosa Nutrition 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000003213 activating effect Effects 0.000 description 1
- 230000003044 adaptive effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 239000004020 conductor Substances 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 238000005265 energy consumption Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 230000004622 sleep time Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/03—Reselecting a link using a direct mode connection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/03—Reselecting a link using a direct mode connection
- H04W36/035—Reselecting a link using a direct mode connection in self-organising networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/14—Direct-mode setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/005—Discovery of network devices, e.g. terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
- H04W36/142—Reselecting a network or an air interface over the same radio air interface technology
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/18—Interfaces between hierarchically similar devices between terminal devices
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- the present invention relates to a method and apparatus for transmitting information of a wireless network in a wireless communication system, and more particularly, to connect a Bluetooth LE through a Bluetooth Low Energy (LE) to a Bluetooth BR / EDR or a Bluetooth BR / EDR.
- a method and apparatus are disclosed.
- 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.
- Bluetooth communication methods include Bluetooth BR / EDR (Basic Rate / Enhanced Data Rate) and Bluetooth Low Energy (LE).
- the Bluetooth BR / EDR scheme may be referred to as classic Bluetooth.
- Classic Bluetooth includes Bluetooth technology that has been passed from Bluetooth 1.0 to 2.1 using Basic Rate and Bluetooth technology that uses Enhanced Data Rate supported from Bluetooth 2.0.
- Bluetooth Low Energy (hereinafter referred to as Bluetooth LE) technology can consume hundreds of kilobytes of information and reliably consume less power.
- the Bluetooth low energy energy technology uses an attribute protocol to exchange information between devices. This Bluetooth LE method can reduce energy overhead by reducing the header overhead and simplifying the 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 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 of establishing a connection by discovering an alternative communication means and a service of the alternative communication means through Bluetooth Low Energy (LE) communication.
- LE Bluetooth Low Energy
- an object of the present invention is to provide a method for reducing power consumption by deactivating other communication means other than Bluetooth LE (Low Energy) communication.
- Another object of the present invention is to provide a method for simplifying a connection procedure of alternative communication means by acquiring information necessary for connection of alternative communication means using Bluetooth LE (Low Energy) communication.
- Bluetooth LE Low Energy
- a plurality of wireless communication means can be connected using one wireless communication means to increase the user convenience.
- the present invention provides a method and apparatus for connecting alternative communication means through Bluetooth Low Energy (LE) technology in order to solve the above problems.
- Bluetooth Low Energy (LE) Low Energy
- a method for connecting an alternative communication means via Bluetooth Low Energy (LE) comprises the steps of: receiving an advertisement message from a second device; Transmitting a request message for requesting detailed information related to a Bluetooth BR / EDR connection based on the advertisement message to the second device; Receiving a response message including the detailed information from the second device in response to the request message; Transmitting a connection request message to the second device based on the detailed information; And establishing a Bluetooth BR / EDR connection with the second device, wherein the advertisement message comprises at least one of location information of the detailed information or available information of the Bluetooth BR / EDR.
- the advertisement message comprises at least one of location information of the detailed information or available information of the Bluetooth BR / EDR.
- the location information is characterized in that one of the scan response message, GATT data base or scan response message and GATT data base.
- the detailed information may include at least one of frequency information, channel map switching information, transmission power information, and connection state information.
- the Bluetooth BR / EDR channel map is generated based on the channel map of the Bluetooth LE.
- the present invention may further include forming a Bluetooth BR / EDR channel map through a channel estimation algorithm.
- connection request message may include at least one of device type information, service type information, and service providing distance information.
- the present invention includes the steps of transmitting an ID packet to a second device; Receiving a response message from the second device in response to the ID packet, the response message including first information related to an alternate interface; Establishing a Bluetooth BR / EDR connection with the second device; Transmitting a handover request message through the formed Bluetooth BR / EDR connection; Receiving a handover response message in response to the handover request message; And forming an alternate interface link with the second device, wherein the first information related to the alternate interface includes at least one of a device type, a service type, a service providing range, and the handover request message or hand. And wherein at least one of the over response messages includes second information related to the connection of the alternate interface.
- the second information may include at least one of frequency information, channel map switching information, transmission power information, connection time information, and connection state information.
- the channel map of the alternative interface is generated based on the channel map of the Bluetooth LE.
- the present invention may further include forming a Bluetooth BR / EDR channel map through a channel estimation algorithm.
- the communication unit for transmitting and receiving a signal to the outside by wire and / or wireless; And a controller operatively connected to the communication unit, wherein the controller is configured to receive an advertisement message from a second device and request detailed information related to a Bluetooth BR / EDR connection based on the advertisement message from the second device. Transmit a request message, receive a response message including the detailed information from the second device in response to the request message, transmit a connection request message to the second device based on the detailed information, And controlling to form a Bluetooth BR / EDR connection with two devices, wherein the advertisement message includes at least one of location information of the detailed information or available information of the Bluetooth BR / EDR.
- the location information is characterized in that one of the scan response message, GATT data base or scan response message and GATT data base.
- the detailed information may include at least one of frequency information, channel map switching information, transmission power information, or connection state information.
- the Bluetooth BR / EDR channel map is generated based on the channel map of the Bluetooth LE.
- the communication unit for transmitting and receiving a signal to the outside by wire and / or wireless; And a control unit operatively connected to the communication unit, wherein the control unit transmits an ID packet to a second device and includes a response message including first information related to an alternative interface in response to the ID packet from a second device.
- Receive a message establish a Bluetooth BR / EDR connection with the second device, transmit a handover request message through the formed Bluetooth BR / EDR connection, and receive a handover response message in response to the handover request message.
- the first information related to the replacement interface includes at least one of a device type, a service type, and a service providing range, and the handover request message or handover.
- the response messages is connected to the alternate interface. It provides a device comprising a second information associated with.
- connection method of the wireless communication means it is possible to obtain the information for the Bluetooth BR / EDR connection via Bluetooth Low Energy (LE) has the effect of efficient handover have.
- LE Bluetooth Low Energy
- the device does not go through the device discovery process for Bluetooth BR / EDR connection via Bluetooth Low Energy (LE), thereby simplifying the connection procedure and reduce power consumption It can be effected.
- LE Bluetooth Low Energy
- connection method of the wireless communication means it is possible to configure the channel map of the Bluetooth BR / EDR after the handover through the channel map of the Bluetooth LE, simplifying the channel map configuration procedure and power reduction effect There is.
- connection method of the wireless communication means it is possible to configure the channel map of the Bluetooth LE after the handover through the channel map of the Bluetooth BR / EDR to simplify the channel map configuration procedure and power reduction effect There is.
- 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 illustrates an example of a method of connecting a wireless communication interface between devices.
- FIG. 3 shows an example of a Bluetooth low power energy topology.
- FIG. 4 is a diagram illustrating an example of a Bluetooth communication architecture to which the methods proposed herein may be applied.
- FIG. 5 shows an example of an internal block diagram of a device that can implement the methods proposed herein.
- FIG. 6 is a diagram illustrating a search and connection procedure of a Bluetooth BR / EDR.
- FIG. 7 is a view briefly illustrating a search and connection procedure of a Bluetooth BR / EDR.
- FIG. 8 is a diagram illustrating a connection procedure of a Bluetooth BR / EDR after a Bluetooth LE connection.
- 10 is a diagram illustrating a channel map configuration of Bluetooth LE and Bluetooth BR / EDR.
- FIG. 11 shows an example of a structure of a wireless communication interface proposed in the present specification.
- FIG. 12 is a flowchart illustrating an example of a method for providing information of a wireless communication interface proposed in the present specification.
- FIG. 13 is a diagram illustrating an example of a data format of the detailed information described with reference to FIG. 12.
- 16 is a diagram illustrating still another example of a method for providing information of a wireless communication interface proposed in the present specification.
- FIG. 17 and 18 are diagrams illustrating a GATT (Generic Attribute Profile) structure of Bluetooth as an example of the tree structure illustrated in FIG. 16.
- GATT Generic Attribute Profile
- 19 and 20 are diagrams illustrating an example of radio communication interface information of a GATT structure proposed in the present specification.
- 21 and 22 illustrate examples of a method and a data format for providing information of a wireless communication interface through a Bluetooth LE connection process proposed in the present specification.
- FIG. 23 is a flowchart illustrating still another example of a method for providing information of a wireless communication interface through a Bluetooth LE connection process proposed in the present specification.
- 24 is a flowchart illustrating an example of a method of providing information of a wireless communication interface through Bluetooth LE proposed in the present specification.
- FIG. 25 is a flowchart illustrating still another example of a method for providing information of a wireless communication interface through Bluetooth LE according to the present specification.
- FIG. 26 is a flowchart illustrating an example of a method for providing information of a wireless communication interface through a Bluetooth LE connection procedure and a Bluetooth LE proposed in the present specification.
- FIG. 27 is a flowchart illustrating still another example of a Bluetooth LE connection procedure and a method for providing information of a wireless communication interface through Bluetooth LE, proposed in the present specification.
- FIG. 28 is a flowchart illustrating still another example of a method for providing information of a wireless communication interface through a Bluetooth LE connection process proposed in the present specification.
- 29 and 30 are diagrams illustrating still another example of a data format proposed in the present specification.
- FIG. 31 is a flowchart illustrating still another example of a method for providing information of a wireless communication interface through Bluetooth LE according to the present specification.
- FIG. 32 is a diagram illustrating an example of a UI (user interface) proposed in the present specification.
- 33A and 33C are flowcharts illustrating a method of exchanging information required for a Bluetooth BR / EDR connection through a Bluetooth LE proposed in the present specification.
- 34A and 34B illustrate examples of state changes of the Bluetooth LR and the Bluetooth BR / EDR proposed in the present specification.
- FIG. 35 is a flowchart illustrating an example of a method for handover from Bluetooth Low Energy (LE) to Bluetooth BR / EDR as proposed herein.
- LE Bluetooth Low Energy
- FIG. 37 is a diagram illustrating an example of a method of sharing a channel map between wireless communication interfaces proposed in the present specification.
- 38 is a flowchart illustrating an example of a method of sharing a channel map between wireless communication interfaces proposed in the present specification.
- FIG. 39 is a diagram comparing channels for estimating a channel map between Bluetooth Low Energy (LE) and Bluetooth BR / EDR proposed in the present specification.
- LE Bluetooth Low Energy
- 40A and 40B are diagrams illustrating an example of a method of estimating a channel map between Bluetooth Low Energy (LE) and Bluetooth BR / EDR proposed in the present specification.
- LE Bluetooth Low Energy
- 40C and 40D illustrate examples of channel map estimation results proposed in the specification.
- 41 is a flowchart illustrating an example of a method for handover from Bluetooth LE to Bluetooth BR / EDR proposed in the specification.
- 43 is a flowchart illustrating another example of a method for handover from Bluetooth LE to Bluetooth BR / EDR proposed in the specification.
- 44 and 45 are diagrams illustrating an example of a method and data structure for handover from Bluetooth BR / EDR to Bluetooth LE proposed in the present specification.
- 46 and 47 are diagrams illustrating an example of a method and data structure for handover from Bluetooth LE to Bluetooth BR / EDR proposed in the present specification.
- 48 is a flowchart illustrating another example of a method for handover from Bluetooth LE to Bluetooth BR / EDR proposed in the specification.
- 49 is a flowchart illustrating still another example of a method for handover from Bluetooth LE to Bluetooth BR / EDR proposed in the specification.
- 50 is a flowchart illustrating another example of a method for handover from Bluetooth LE to Bluetooth BR / EDR proposed in the specification.
- 51A and 51B illustrate an example of a method and data format for estimating a channel map at handover from a Bluetooth LE to a Bluetooth BR / EDR as proposed herein.
- FIG. 52 is a flowchart illustrating still another example of a method for estimating a channel map at handover from a Bluetooth LE to a Bluetooth BR / EDR proposed in the specification.
- FIG. 53 illustrates an example of a method for notifying of a serviceable range between wireless communication interfaces proposed in the present specification.
- FIG. 54 is a flowchart illustrating an example of exchanging FHS (Frequency Hopping Synchronization) information of a Bluetooth BR / EDR proposed through the present specification.
- FHS Frequency Hopping Synchronization
- Electronic devices described herein may include a mobile phone, a smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), navigation, and the like.
- PDA personal digital assistant
- PMP portable multimedia player
- the configuration according to the embodiments described herein may also be applied to fixed terminals such as digital TVs, desktop computers, etc., except when applicable only to mobile terminals.
- the signals described herein may be transmitted in the form of a message as well as a frame, and the wireless communication interface and the wireless communication means are given or used in consideration of the ease of specification, meaning that they are distinguished from each other or It does not have a role.
- 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 110 and at least one client device 120.
- the server device and the client device perform Bluetooth communication by 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 server device 110 may operate as a client device in a relationship with another device, and the client device may operate as a server device in a relationship with another device. 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 110 may include a data service device, a master device, a master, a server, a conductor, a host device, an audio source device,
- the client device may be a slave device, a slave device, a slave device, a client, a member, a sink device, an audio sink device, or a second device. It may be represented by a device or the like.
- 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 refers to a device that receives data from a client and directly communicates with the client device, thereby providing data to the client device through a response when receiving a data request from the client device.
- the server device also sends a notification message and an indication message to the client device to provide data information to the client device.
- the server device transmits an indication message to the client device
- the server device receives a confirmation message corresponding to the indication 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, indication, 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 the client devices by using bonding information.
- the client device 120 refers to an apparatus 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 the memory or write new data to the memory in the 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. 5.
- 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.
- the BLE device (or device) may be operable to support various Bluetooth-related protocols, profiles, processing, and the like.
- the electronic device including the BLE technology includes a plurality of wireless communication interfaces such as Wi-Fi, Bluetooth BR / EDR, and NFC in addition to the BLE.
- the present invention proposes a method in which BLE is used as a wake-up interface and the other wireless communication interface wakes up only when a request is made.
- FIG. 2 illustrates an example of a method of connecting a wireless communication interface between devices.
- wireless communication interfaces included in the device perform a connection according to each procedure.
- each of the wireless communication interfaces of the electronic device is different for the same or similar purposes as shown in FIG. It does so in a way and form.
- the first device 200 and the second device 300 intend to perform wireless communication through a Bluetooth BR / EDR
- the first device 200 transmits the first device via the Bluetooth BR / EDR.
- the device may search for the Bluetooth BR / EDR of the device 300 and check and connect the capability to perform wireless communication.
- the first device 200 and the second device 300 are to perform wireless communication through NFC (Near Field Communication)
- the first device 200 is the second through NFC
- the Bluetooth BR / EDR of the device 300 should be searched for, and the wireless communication should be performed by checking and connecting the capability.
- the present invention proposes a method of unifying an interface for waiting for communication with a target device to BLE and activating other wireless communication interfaces only through BLE when necessary.
- FIG. 3 shows an example of a Bluetooth low power energy topology.
- device A corresponds to a master in a piconet (piconet A, shaded portion) having device B and device C as slaves.
- a piconet means a set of devices occupying a shared physical channel in which any one of a plurality of devices is a master and the remaining devices are connected to the master device.
- the BLE slave does not share a common physical channel with the master. Each slave communicates with the master through a separate physical channel. There is another piconet (piconet F) with master device F and slave device G.
- a scatternet means a group of piconets in which connections between other piconets exist.
- Device K is a master of device L and a slave of device M.
- Device O is also on scatternet O.
- Device O is a slave of device P and a slave of device Q.
- Device D is an advertiser and device A is an initiator (group D).
- Device E is a scanner and device C is an advertiser (group C).
- Device H is an advertiser and devices I and J are scanners (group H).
- Device K is also an advertiser and device N is an initiator (group K).
- Device R is the advertiser and device O is the initiator (group R).
- Devices A and B use one BLE piconet physical channel.
- Devices A and C use another BLE piconet physical channel.
- device D advertises using an advertisement event connectable onto an advertising physical channel, and device A is an initiator.
- Device A may establish a connection with device D and add the device to piconet A.
- device C advertises on the ad physical channel using some type of advertisement event captured by scanner device E.
- Group D and Group C may use different advertising physical channels or use different times to avoid collisions.
- Piconet F has one physical channel. Devices F and G use one BLE piconet physical channel. Device F is the master and device G is the slave.
- Group H has one physical channel. Devices H, I and J use one BLE advertising physical channel. Device H is an advertiser and devices I and J are scanners.
- devices K and L use one BLE piconet physical channel.
- Devices K and M use another BLE piconet physical channel.
- device K advertises using an advertisement event connectable onto an advertising physical channel
- device N is an initiator.
- Device N may form a connection with device K.
- device K becomes a slave of two devices and simultaneously becomes a master of one device.
- devices O and P use one BLE piconet physical channel.
- Devices O and Q use another BLE piconet physical channel.
- device R advertises using an advertisement event connectable onto an advertising physical channel, and device O is an initiator.
- Device O may form a connection with device R.
- device O becomes a slave of two devices and simultaneously becomes a master of one device.
- FIG. 4 is a diagram illustrating an example of a Bluetooth communication architecture to which the methods proposed herein may be applied.
- FIG. 4 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.
- HCI host controller interface
- 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.
- the host stack (or host module) 20 is connected to a Bluetooth module which is the controller stack 10 to connect a Bluetooth module. Control and perform actions.
- the host stack 20 may include a BR / EDR PHY layer 12, a BR / EDR baseband layer 14, and a link manager layer 16.
- the BR / EDR PHY layer 12 is a layer for transmitting / receiving a 2.4 GHz radio signal and may transmit data by hopping 79 RF channels when using Gaussian Frequency Shift Keying (GFSK) modulation.
- GFSK Gaussian Frequency Shift Keying
- the BR / EDR baseband layer 14 plays a role of 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) includes a logical link control and adaptation protocol (L2CAP, 21), a BR / EDR protocol (22), a generic access profile (GAP, 23), and a BR / EDR profile. (24).
- L2CAP logical link control and adaptation protocol
- BR / EDR protocol 22
- GAP generic access profile
- BR / EDR profile. 24
- 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 BR / EDR Protocol 22 and Profiles 24 define a service profile using Bluet BR / EDR and an application protocol for sending and receiving these data, and the Generic Access Profile (GAP). , 23) defines the method of device discovery, connection, and providing information to the user, and provides privacy.
- GAP Generic Access Profile
- 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).
- 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 42 bytes of data packets through 37 data channels. Provides the ability to send and receive.
- the information for the connection procedure of the wireless communication interface other than the BLE can be exchanged between the devices by using the advertising or scanning function, and the connection procedure of the other wireless communication interface is performed based on the exchanged information. can do.
- the host stack includes a generic access profile (GAP) 40, a logical link control and adaptation protocol (L2CAP, 41), a security manager (SM, 42), an attribute protocol (ATT, 440), and a general attribute profile.
- GAP generic access profile
- L2CAP logical link control and adaptation protocol
- SM security manager
- ATT attribute protocol
- 440 general attribute profile
- GATT Generic Attribute Profile
- GATT Generic Access Profile
- LT profile 46 may be included.
- 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 uses three fixed channels (one for the signaling channel, one for the Security Manager, and one for the Attribute protocol).
- BR / EDR Base Rate / Enhanced Data Rate
- 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).
- the Request message is a message for requesting specific information from the client device to the server device
- the Response message is a response message to the request message, which is a message transmitted from the server device to the client device.
- Command message A message sent 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 General Access Profile (GAP) 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 be, for example, Battery, Time, FindMe, Proximity, Time, Object Delivery Service, 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, and the like 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 user data from the advertising device.
- the advertising device transmits a scan response that is a response to the scan request, including additional user 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 other devices around it is called a discovering device and listens for devices that advertise scannable advertising events.
- 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.
- 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 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. 5 shows an example of an internal block diagram of a device that can implement the methods proposed herein.
- the first device 200 and the second device 300 may include a network interface 210, 310, an output unit 220, 320, and an input unit 230, 330.
- the internal block diagram of the device shown in FIG. 5 may further include other components (modules, blocks, parts), and some of the components of FIG. 5 may be omitted.
- the network interface 210, 310, the output unit 220, 320, the input unit 230, 330, the control unit 240, 340, the multimedia module 250, 350, the first storage unit 260, 360 and / or the second storage unit 270, 370 are functionally connected to perform the method proposed in the present specification.
- the network interfaces 210 and 310 refer to a unit (or module) capable of data transmission between devices using various network technologies (or means).
- the network interfaces 210 and 310 may again include energy efficiency interfaces 212 and 312 and / or external interfaces 214 and 314.
- the energy efficiency interfaces 212 and 312 are units (or modules) that use network technology for low power wireless communication, and may search for other devices to be connected or perform data transmission (for example, BLE (Bluetooth). Low Energy).
- BLE Bluetooth Low Energy
- the external interface 214, 314 refers to an interface (or wireless communication means) for wireless communication other than the energy efficiency interfaces 212, 312.
- the first device 200 and the second device 300 may transmit and receive information for connection of the external interface (214, 314) through the energy efficiency interface (212, 312), Through this, the connection procedure of the external interfaces 214 and 314 may be performed.
- the output units 220 and 320 refer to a module for providing device status information and message exchange information to a user through a screen.
- the input unit 230 or 330 refers to a module that provides a user input to the control unit 240 or 340 as a screen button so that the user can control the operation of the device.
- the multimedia modules 250 and 350 refer to modules for various types of multimedia playback, and the multimedia module may be implemented in the controllers 240 and 340 or may be implemented separately from the controllers 240 and 340. .
- the first storage units 260 and 360 refer to nonvolatile physical devices capable of storing various kinds of data.
- the second storage units 270 and 370 refer to physical devices having a volatile characteristic in which various types of data are temporarily stored.
- the first device 200 and the second device 300 may include a power supply unit, and the power supply unit may supply external power and / or internal power under the control of the controller. It can be supplied with the power required to operate each component.
- BLE technology has a small duty cycle and can significantly reduce power consumption through a low data rate, so that the power supply is required for operation of each component even with a small output power (10 mW (10 dBm or less). Can supply power.
- FIG. 6 is a diagram illustrating a search and connection procedure of a Bluetooth BR / EDR.
- the first device 200 and the second device 300 are in a standby state, the first device 200 is in a query state for the Bluetooth BR / EDR search, and the second device 300 is in a standby state. ) Becomes the Inquiry Scan State.
- the first device 200 transmits an ID packet to perform a Bluetooth BR / EDR discovery procedure (S610), and in response to the FHS packet (FHS packet) from the second device (300). Frequency Hop Synchronization Packet) is received (S620).
- the second device 300 may transmit additional information to the first device 200 using an enhanced inquiry packet. (S630).
- the paging procedure is performed.
- the first device 200 page state (Paging State)
- the second device 300 enters the page scanning state (Paging Scan Sate).
- the first device 200 transmits an ID packet to the second device 300 in a paging state (S640).
- the first device 200 When the second device 300 receives the ID packet transmitted by the first device, the first device 200 enters a BR / EDR master response state of a BR / EDR paging state, and the second device 300 enters the BR / EDR slave state of the BR / EDR paging state.
- the first device 200 transmits a second ID packet in the channel that transmitted the ID packet (S650).
- the second device 300 Upon receiving the second ID packet, the second device 300 transmits a frequency hopping synchronization (FHS) packet to the first device 200 for frequency synchronization (S660).
- FHS frequency hopping synchronization
- the first device 200 and the second device 300 is switched to BR / EDR connected state.
- the second device 300 is switched to the hopping pattern of the first device 200, and the first device 200 transmits a Poll packet to the second device 300 in order to confirm this. S670).
- the second device 300 receiving the Poll packet transmits a data packet to the first device 200 in response to the Poll packet (S680), and terminates the Bluetooth BR / EDR connection procedure.
- FIG. 7 is a view briefly illustrating a search and connection procedure of a Bluetooth BR / EDR.
- the first device 200 requests a search, receives a response, and informs a user of peripheral device information, and plays a role of requesting a connection.
- the second device 300 serves to respond to the search request and to respond to the connection request.
- the second device 300 since the second device 300 may not know when there is a search request and a connection request of the first device 200, the second device 300 must maintain a scan state.
- the second device 300 has a problem that consumes a lot of power.
- FIG. 8 is a diagram illustrating a connection procedure of a Bluetooth BR / EDR after a Bluetooth LE connection.
- the device when the Bluetooth BR / ED and the Bluetooth LE communication are alternately performed, the device must perform a connection procedure defined in each wireless communication.
- both the first device 200 and the second device 300 initially exist in a disconnected state.
- the second device 300 may discover the first device 200 by performing a Bluetooth LE search procedure (S810). In this case, both the first device 200 and the second device 300 are in a disconnected state.
- the second device 300 performs a Bluetooth LE connection procedure to communicate with the searched first device 200 via Bluetooth LE (S820), and the second device 300 through the Bluetooth LE connection procedure. ) And the first device 200 enter the Bluetooth LE connection state.
- the first device 200 and the second device 300 enters the Bluetooth BR / EDR connection state by performing the Bluetooth BR / EDR connection procedure again (S830).
- Table 2 below is a table showing an example of the channel configuration of Bluetooth.
- the RF channels of Bluetooth may be assigned indices from 0 to 39 for 40 channels.
- Channel Type is composed of two channels advertising channel (Advertising Channel) and data channel (Data Channel).
- Indexes from 0 to 36 are assigned to the data channels, and 37, 38, and 39 indexes are assigned to the advertising channels.
- the Bluetooth LE channel map is used or unused for 36 data channels of Bluetooth LE as shown in Table 8 above. Choose.
- the master device may transmit channel map information indicating whether the available or unavailable flag is displayed in a process of requesting a connection to a slave device. It is included in the ChM field shown in b).
- 10 is a diagram illustrating a channel map configuration of Bluetooth LE and Bluetooth BR / EDR.
- the Bluetooth LE and the Bluetooth BR / EDR use the same frequency band, and the channel configuration is similar.
- Bluetooth LE and BR / EDR use the 2,400 MHz to 2483.5 MHz spectrum, which is an Industrial Science Medical (ISM) band. As shown in FIG. 32, communication is performed using 79 channels at 1 MHz in the case of Bluetooth BR / EDR, and communication is performed using 20 channels at 2 MHz in the case of Bluetooth LE.
- ISM Industrial Science Medical
- Bluetooth uses a frequency hopping technique that performs communication by changing the channel 1600 times per second to prevent interference.
- the device may use frequency hopping to check a channel with high interference while performing communication and perform frequency hopping on channels other than the checked channel.
- AFH Adaptive Frequency Hopping
- the master device when interference occurs due to other wireless communication on channels 0, 1, 2, and the like, the master device does not use channels 0, 1, and 2 Check the) and check the remaining channels as Used to compose the channel map.
- a hopping pattern is constructed using channels without interference based on a channel map and frequency hopping is performed.
- the Bluetooth BR / EDR When performing communication using Bluetooth LE and performing handover to Bluetooth BR / EDR, the Bluetooth BR / EDR also configures separate channel maps for 79 channels and performs frequency hopping to perform AFH.
- the present invention provides a method of configuring a channel map by using an existing channel map when handing over from Bluetooth BR / EDR to Bluetooth LE or handover from Bluetooth LE to Bluetooth BR / EDR. Suggest.
- FIG. 11 shows an example of a structure of a wireless communication interface proposed in the present specification.
- the first device 200 and the second device 300 may operate while all wireless communication interfaces except the BLE module are set to a sleep state.
- the first device 200 and the second device 300 include various wireless communication interfaces (or means) such as BLE, Wi-Fi Direct, WiGig, Bluetooth BR / EDR, Wi-Fi, and the like.
- the first device 200 and the second device 300 are set to a sleep state except for the BLE among the various wireless communication interfaces.
- the first device 200 or the second device 300 wants to use a wireless communication interface such as Wi-Fi Direct, WiGig, Bluetooth BR / EDR, a wireless communication interface to use through the BLE
- the wireless communication interface can be connected by exchanging capability information.
- the first device 3000 when the first device 3000 wants to perform a service such as Miracast or Print using Wi-Fi Direct, the first device 200 may be connected to Wi-Fi of the second device 300. After negotiating the availability of Fi Direct through BLE, information necessary for connection of Wi-Fi Direct (eg, Listen Channel, BSSID, and IEEE MAC addr) may be exchanged.
- Wi-Fi Direct eg, Listen Channel, BSSID, and IEEE MAC addr
- the first device 200 and the second device 300 may perform Wi-Fi Direct connection based on the exchanged information.
- the wireless communication interface except for the BLE can be put in the sleep state, thereby reducing power consumption than when all the wireless communication interfaces are in the wake-up state.
- connection information of the wireless communication interface can be obtained through BLE, the connection procedure and time of the wireless communication interface can be reduced.
- FIG. 12 is a flowchart illustrating an example of a method for providing information of a wireless communication interface proposed in the present specification.
- the first device 200 receives information related to a wireless communication interface included in the second device 300 from the second device 300, and if necessary, the first device 200. Is a protocol type method that can request detailed information from the second device 300 and receive the information.
- the second device 300 transmits the information of the wireless communication interface included in the second device to the first device 200 through BLE technology (S1210), the first device 200 is Based on the information transmitted from the second device 300, information of a wireless communication interface supported by the second device 300 may be obtained.
- BLE technology S1210
- Information on the wireless communication interface transmitted by the second device 300 to the first device 200 may be transmitted in the form of a bit mask.
- bit mask form which wireless communication interface is supported by the second electronic device 300 and which service can be supported is shown in bit form.
- Table 3 below shows an example of the bit mask type
- Table 4 shows an example of the air interface type indicated by each bit.
- the second device 300 may inform the first device 200 of a wireless interface or a service that can be supported through each bit value of the bit mask of Table 3 above.
- the second device 300 sends Wi-Fi Direct, WFDS Print, and WFDS Display to the first device 200. It can tell you that it can support NFC.
- the second device 300 When the first device 200 that has received the information of the air interface needs detailed information (or additional information) about the air interface, the second device 300 provides detailed information (or additional information) about the wireless communication interface. ) Can be requested (S1220).
- the second device 300 may transmit detailed information (or additional information) about the requested wireless communication interface to the first device (S1230).
- the detailed information may include information of a wireless interface or detailed information (or additional information) of a service provided by the wireless interface.
- FIG. 13 is a diagram illustrating an example of a data format of the detailed information described with reference to FIG. 12.
- the detailed information includes an information type field indicating the type of information and a detailed information field including detailed information of the information.
- the second device 300 uses the data format of FIG. 8 to display the first device.
- the detailed information of the Classic Bluetooth may be transmitted to the 200.
- the information type includes the information of the address or the type of the device. It may include a value indicating that, and the detailed information may include an address value or a value indicating a device type.
- Table 5 below shows an example of parameters constituting the detailed information.
- Device Address value Unique ID value to identify device Device Address type Identify which type of air interface corresponds to the address Device Address length Length of Device Address value
- Device class Indicates which device class the device belongs to. (ex: Print, Head set, etc.)
- Security information Information sent and received for security when pairing Synch code Send and receive values to match the synch of two devices Scan Window Interval Indicates how often a device listens to receive signals from other devices
- Link Address ID value identifying the link when a wireless connection is made between two devices
- Clock Native clock on the device Scan Mode Represents a pattern that a device lists to receive signals from other devices.
- Connection start Command for instructing connection between devices using a specific air interface
- Number of connections The number of devices connected to a specific air interface Device Status Device status, such as on / off status of specific air interfaces Carrier Bitmask Value indicating the type of air interface the device has Listen Channel Channels where P2Ps exchange data with each other during the discovery phase Channel Class Frequency band used in Wi-Fi, etc.
- P2P Capability Indicates whether connection to P2P Group is possible Configuration Method How to connect to external interface (eg, WSCIE (Wi-Fi)) Supported Rate Tx Rate Peer addr External Interface Address of Peer Device Channel Information Information about the overall channel, such as the Supported Channel List or Channel Map.
- WSCIE Wi-Fi
- each device can exchange information on a supportable wireless communication interface by a protocol type method.
- the first device 200 or the second device 300 may exchange all information on a wireless communication interface supported by each device. As shown in FIG. 14 and FIG. 15, the first device 200 or the second device is divided into a header part and a payload part.
- the data format shown in FIG. 14 includes summary information of the wireless communication interface in the header portion and detailed information of each wireless communication interface in the payload portion.
- the summary information includes information on the number of wireless communication interfaces supported by each device and / or an offset value where detailed information of each wireless communication interface is located.
- the header portion includes not only summary information of the wireless communication interface, but also information on the number of wireless communication interfaces supported by the device.
- the summary information of the interface consists of information offsets for each wireless communication interface, and each information offset includes an interface indicator field and a detailed information position offset field.
- the interface indicator field includes information related to a type of a wireless communication interface included in each device, and the detailed information location offset field includes information on which position of a payload is included in a specific air interface. Is included.
- the payload portion is composed of wireless communication interface detail fields, and each wireless communication interface detail field is composed of an information type field indicating a type of information and a field including detailed information corresponding to the type of information. It is.
- the detailed information field may include the parameters shown in Table 3 above.
- each device may exchange information on a wireless communication interface included in each device, and perform a wireless communication interface connection procedure based on the exchanged information.
- 16 is a diagram illustrating still another example of a method for providing information of a wireless communication interface proposed in the present specification.
- a common data tree defined between two devices may be held, and information of a wireless communication interface may be exchanged by exchanging tree numbers thereof.
- the first device 200 and the second device 300 classify all data related to the wireless communication interface for each item and manage them in a tree structure, and all items are given a unique ID.
- the structure of the differentiated wireless communication interface is known to the first device 200 and the second device 300.
- the Tree structure is a hierarchical structure. Each entity existing in each layer has a unique ID, and the first device 200 is provided through each unique ID. Alternatively, the second device 300 may request and receive information on a wireless communication interface of a device to be connected.
- the first device 200 when the first device 200 requests the second device 300 for information on the Wi-Fi SSID, the first device 200 sends the second device 300 “01.02. By requesting and reading the information contained in .02.01 ”, it is possible to obtain information on the“ Wi-Fi SSID ”.
- the user may obtain a Capability value for the air interface to determine the state of the air communication interface or change the value.
- FIG. 17 and 18 are diagrams illustrating a GATT (Generic Attribute Profile) structure of Bluetooth as an example of the tree structure illustrated in FIG. 16.
- GATT Generic Attribute Profile
- Bluetooth GATT defines how to send and receive data between two BLE devices using service and character.
- a command is provided to transmit data about a characteristic from a server device to a client device and from the client device to the server device. It can specify the UUID of the property or read the value through the handle value provided by the information retrieval command.
- GATT may also provide notifications and indications.
- the client device may request a notification for a particular characteristic from the server device, and the server device may send a corresponding value to the client device whenever it is available.
- one profile is composed of a number of services (Service), each service is composed of a number of characteristics.
- One property contains one value and n descriptors, and each descriptor describes a value of the property.
- the information on the wireless communication interface is stored in the device in the GATT structure, the information of the stored GATT structure can be read or transmitted from the counterpart device.
- 19 and 20 are diagrams illustrating an example of radio communication interface information of a GATT structure proposed in the present specification.
- information about a wireless communication interface included in a device may be dependent on a wireless communication interface service in a specific profile.
- a separate wireless communication interface profile may be operated in a form independent of other profiles.
- each wireless communication interface service is defined in the wireless communication interface profile, and information on the wireless communication interface is defined as a characteristic of each wireless communication interface service.
- the wireless communication interface information of another device can be read through the wireless communication interface information of the GATT structure shown in FIGS. 19 and 20, and the wireless communication interface is based on the read wireless communication interface information.
- the connection procedure can be performed.
- 21 and 22 illustrate examples of a method and a data format for providing information of a wireless communication interface through a Bluetooth LE connection process proposed in the present specification.
- two devices may request and receive information on a wireless communication interface other than BLE through an advertising process without performing BLE pairing.
- the first device 200 in the scanning state and the second device 300 in the advertisement state may be used for discovery and capability in order to discover a counterpart device and exchange information on a wireless communication interface. Information exchange procedures will be performed.
- the second device 300 in the advertising state may transmit an advertising message to the first device 200 through an advertising channel in order to perform a BLE connection procedure (S2110).
- the advertisement message is used for informing the second device 300 to the devices having the surrounding BLE function, and may include information of a possible wireless communication interface.
- the information of the wireless communication interface included in the advertisement message may include the bit mask (Bit_Mask) form described with reference to FIG. 7 or interface summary information of the data stream described with reference to FIGS. 9 and 10.
- FIG. 22A illustrates an example of the advertisement message PDU, and it can be seen that information on a wireless communication interface of the second device 300 is included in the form of a bit mask.
- the AdvA field includes a value indicating what type of PDU the advertisement message PDU is.
- the advertisement message PDU may be a PDU of the following type.
- EXTENDED_ADV_IND and LONG_ADV_NONCONN_IND are the ADV_IND and ADV_NONCONN_IND types of which the data length is extended.
- the AdvData field includes information of the wireless communication interface, and includes a Type field indicating an information type and a Bitmask field including an information value corresponding to the Type.
- the Type field may include one of Supported Tech, Status, or Availability information.
- the Supported Tech field may include supportable wireless communication interface information
- the Status field may include operation status information of the supportable wireless communication interface
- the Availability field may include information related to whether the supportable wireless communication interface is available. Can be.
- the device 300 requests information on a wireless communication interface through a scan request (S2120).
- the scan request PDU may have a SCAN_REQ type among the types of Table 1, or may have a LONG_SCAN_REQ type that is an extension of the SCAN_REQ.
- the second device 300 may transmit detailed information of the requested wireless communication interface to the first device 200 through a scan response (S2130).
- the first device 200 and the second device 300 that have acquired information necessary for discovery of a counterpart device and connection of a wireless communication interface through the discovery and capability information exchange procedure are connected to the corresponding wireless communication interface.
- a link may be formed through the procedure (S2140).
- 22 (b) shows an example of the scan response message PDU, it can be seen that the radio communication interface details of the second device 300 is included in the scan response message PDU.
- the scan response message PDU includes an AdvA field and a ScanRspData field.
- the AdvA field may indicate a type of the scan response PDU, and may have a SCAN_RSP type among the types of Table 1, or may have a LONG_SCAN_RSP type that is an extension of the SCAN_RSP type.
- the ScanRspData field includes a Type field indicating information type of the wireless communication interface requested by the first device 200 and a Data field including detailed information of the information type.
- handover may be performed by transmitting information for handover from Bluetooth LE to Bluetooth BR / EDR or from Bluetooth BR / EDR to Bluetooth LE.
- Table 6 shows an example of a proposed mode, procedure, message, and parameter when performing a handover between Bluetooth BR / EDR and Bluetooth LE.
- handover between BR / EDR and Bluetooth LE is performed, an example of information that can be exchanged through the capability information exchange procedure is shown.
- Handover Response (Type: BR / EDR) Message Response message to BR / EDR Handover Request Handover Request (Type: BLE) Message In the BLE Disable state, after enabling BR / EDR, a message requesting to switch to BR / EDR Handover Standby state and to set up a BLE connection.
- Handover Response (Type: BLE) Message Response message for BLE Handover Request Channel Estimation Algorithm based on Channel map Algorithm Algorithm for changing the channel map created by BR / EDR for BLE or Algorithm for changing the channel map created for BLE for BR / EDR Channel map Parameter Parameter Parameters needed to create a channel map
- Device name Parameter The name of the device Service ID Parameter UUIDs for services provided by the device Device type Parameter Indicates which device class the device belongs to. (ex: Print, Headset, TV, etc. Connection status Parameter Information about which device your device is connected to Service range Parameter The distance value that each interface of the device can serve. (ex-BR / EDR 30m) Interface power Parameter Power of each interface of the instrument (ex-BR / EDR 4dBm) Service name Parameter The name of the service Icon ID Parameter ID value to distinguish icon for device type or ID value to distinguish icon for service type Version information Parameter Version of the language that composes human-readable text
- FIG. 23 is a flowchart illustrating still another example of a method for providing information of a wireless communication interface through a Bluetooth LE connection process proposed in the present specification.
- the Bluetooth BR / EDR connection procedure may be performed by exchanging information of the Bluetooth BR / EDR through the BLE connection procedure described with reference to FIG. 21.
- steps S2310 to S2330 of FIG. 23 are the same as steps S2110 to S2130 of FIG. 21, a description thereof will be omitted.
- the first device 200 having obtained the information on the Bluetooth BR / EDR through the scan response message from the second device 300 connects with the second device 300 to perform the Bluetooth BR / EDR connection procedure. And a service start command (S2340).
- the first device 200 performs a paging procedure to connect the Bluetooth BR / EDR.
- a BR / EDR paging state is entered, and the second device 300 enters a paging scan state.
- the first device 200 transmits an ID packet to the second device 300 in the paging state (S2350).
- the first device 200 When the second device 300 receives the ID packet transmitted by the first device, the first device 200 enters a BR / EDR master response state of a BR / EDR paging state, and the second device 300 enters the BR / EDR slave state of the BR / EDR paging state.
- the first device 200 transmits a second ID packet in the channel in which the ID packet is transmitted (S2360).
- the second device 300 Upon receiving the second ID packet, the second device 300 transmits a frequency hopping synchronization (FHS) packet to the first device 200 for frequency synchronization (S2370).
- FHS frequency hopping synchronization
- the first device 200 and the second device 300 is switched to BR / EDR connected state.
- the second device 300 is switched to the hopping pattern of the first device 200, and the first device 200 transmits a Poll packet to the second device 300 in order to confirm this. S2180).
- the second device 300 Upon receiving the poll packet, the second device 300 transmits a data packet to the first device 200 in response to the poll packet, and terminates the Bluetooth BR / EDR connection procedure.
- the first device 200 and the second device 300 may perform a Bluetooth BR / EDR connection procedure and may find a counterpart device through BLE without performing a separate query procedure. .
- 24 is a flowchart illustrating an example of a method of providing information of a wireless communication interface through Bluetooth LE proposed in the present specification.
- a connection may be formed by exchanging information of a wireless communication interface other than BLE through BLE between devices.
- the first device 200 and the second device 300 form a BLE connection by performing the BLE connection (or pairing) procedure described above (S2410).
- the first device 200 forming the BLE connection is operated as a master device, and the second device 300 is operated as a slave device.
- the roles of the master device and the slave device may change according to circumstances.
- the first device 200 and the second device 300 that have formed the BLE connection want to connect a wireless communication interface different from the BLE
- the first device 200 and the second device 300 may exchange information on the wireless communication interface through the BLE (S2420). ).
- the first device 200 and the second device 300 may exchange information of the wireless communication interface using the method described with reference to FIGS. 9 to 15, such as a GATT profile.
- the first device 200 and the second device 300 exchange a start command (S2430) and perform a connection procedure of the wireless communication interface based on the exchanged information.
- FIG. 25 is a flowchart illustrating still another example of a method for providing information of a wireless communication interface through Bluetooth LE according to the present specification.
- connection procedure of the Bluetooth BR / EDR may be performed by exchanging information of the Bluetooth BR / EDR through the BLE described with reference to FIG. 21.
- the first device 200 exists in an initiating state, and the second device 300 exists in an advertising state.
- the second device 300 transmits an advertising message to inform itself of the peripheral device (S2510).
- the first device 200 Upon receiving the advertising message, the first device 200 transmits a connection request message to the second device 300 to form a BLE connection with the second device 300 (S2520).
- the first device 200 and the second device 300 may enter a BLE connection state, and may transmit and receive data.
- the first device 200 and the second device 300 having the BLE connection may exchange information on the wireless communication interface through BLE (S2530). .
- the first device 200 and the second device 300 may exchange information of the wireless communication interface by the method described with reference to FIGS. 9 to 15.
- the first device 200 and the second device 300 having exchanged information on the wireless communication interface exchange a start command for connecting a Bluetooth BR / EDR (S2540).
- the first device 200 performs a paging procedure to connect the Bluetooth BR / EDR.
- a BR / EDR paging state is entered, and the second device 300 enters a paging scan state.
- FIG. 26 is a flowchart illustrating an example of a method for providing information of a wireless communication interface through a Bluetooth LE connection procedure and a Bluetooth LE proposed in the present specification.
- two devices exchange capability information of a simple wireless communication interface through an advertising procedure without performing BLE pairing and then perform wireless communication. If detailed information of the interface is required, detailed capability information of the wireless communication interface may be exchanged after BLE pairing.
- the first device 200 and the second device 300 do not perform a BLE pairing procedure and thus are not connected to the BLE, and the first device 200 is in a scanning state.
- the second device 300 exists in an advertising state.
- the second device 300 may exchange information on a wireless communication interface that the device supports by the first device 200 through an advertisement PDU (S2610).
- the first device 200 and the second device 300 having exchanged information on the wireless communication interface may perform a BLE pairing procedure to form a BLE link (S2620).
- the first device 200 and the second device 300 exchange a start command (S2640), and then, based on the information of the wireless communication interface, The connection procedure can be performed.
- the method described with reference to FIG. 26 is a mixture of the methods described with reference to FIG. 21 and FIG. 24, so that the efficiency and immediateness of the BLE connection procedure and the exchange of information in an upper layer through the BLE link can be provided.
- FIG. 27 is a flowchart illustrating still another example of a Bluetooth LE connection procedure and a method for providing information of a wireless communication interface through Bluetooth LE, proposed in the present specification.
- connection procedure of the Bluetooth BR / EDR may be performed by exchanging information of the Bluetooth BR / EDR through the BLE described with reference to FIG. 26.
- the first device 200 exists in an initiating state, and the second device 300 exists in an advertising state.
- the second device 300 may exchange information on the wireless communication interface with the first device (S2700).
- the information of the wireless communication interface may include a bit mask (Bit_Mask) form described with reference to FIG. 10 or interface summary information of the data stream described with reference to FIGS. 14 and 15.
- Bit_Mask bit mask
- the first device 200 having exchanged information on the wireless communication interface enters an initiating state.
- the second device 300 transmits an advertising message to the first device 200 in order to perform a BLE connection procedure (S2710).
- the first device 200 that recognizes the second device 300 through the advertising message transmits a connection request message for BLE connection to the second device 300 (S2720).
- the first device 200 and the second device enter a connection state.
- the first device 200 and the second device 300 exchange detailed information of the wireless communication interface by using the method described with reference to FIGS. 9 to 15 through BLE (S2730) and perform a connection procedure.
- Exchange start commands to perform S2740).
- the first device 200 performs a paging procedure to connect the Bluetooth BR / EDR.
- a BR / EDR paging state is entered, and the second device 300 enters a paging scan state.
- FIG. 28 is a flowchart illustrating still another example of a method for providing information of a wireless communication interface through a Bluetooth LE connection process proposed in the present specification.
- the device may perform the connection procedure of the wireless communication interface by acquiring information on the wireless communication interface supported by the counterpart device through BLE.
- the first device 200 and the second device 300 do not have a BLE connection.
- the first device 200 enters a scanning state in order to recognize a device capable of other BLE communication, and the second device 300 enters an advertising state. do.
- the wireless communication interface between the first device 200 and the second device 300 is in an active state.
- the first device 200 in the scanning state and the second device 300 in the advertising state may exchange information on a supportable wireless communication interface in a state in which a BLE connection is not established (S2800).
- the second device 300 that receives the information of the wireless communication interface that the first device 200 can support transmits an advertisement PDU to the first device (S2810).
- the advertisement PDU may be for transmitting a scan request message of the first device 200 or may be a message for handover.
- the advertisement PDU is a PDU for transmitting a scan request PDU
- the advertisement PDU may have the same form as the data format of the advertisement PDU described with reference to FIGS. 16 and 17.
- the advertisement PDU when the advertisement PDU is a PDU for handover, the advertisement PDU has a separate type and has one of the reserved values shown in Table 1 above.
- the second device 300 may obtain information that a handover procedure will proceed through the information included in the advertisement PDU.
- the first device 200 receiving the advertisement PDU transmits a scan request PDU to the second device 300 to request detailed information of a wireless communication interface supported by the second device 300 (S2820). ).
- the scan request PDU has a type described with reference to FIGS. 16 and 17.
- the second device 300 Upon receiving the scan request PDU, the second device 300 transmits detailed information of the requested wireless communication interface to the first device 200 through a scan response PDU (S2830).
- the first device 200 and the second device 300 perform a connection procedure based on the information of the wireless communication interface (S2840), and the first device 200 and the second device 300 ) Is connected via the wireless communication interface.
- 29 and 30 are diagrams illustrating still another example of a data format proposed in the present specification.
- the AdvA field included in each embodiment may be the same as the AdvA field of FIGS. 21 and 22 or the AdvA field described with reference to FIG. 28 described above.
- the AdvData field may include a Service Data field, an SDO ID / SIG ID field, and a Length field.
- the SDO ID / SIG ID field indicates the type of the wireless communication interface, and the Length field indicates the length of the PDU field.
- Table 8 below shows an example of wireless communication interface types that may be included in the SDO ID / SIG ID.
- AdvData field of the advertisement message shown in FIG. 29 (a) and FIG. 30 (b) may further include a PDU field.
- the PDU field is a field containing simple information of a wireless communication interface and includes different information according to the type of the wireless communication interface.
- the PDU field includes a BR / EDR header field and an Entire Contents field.
- the BR / EDR header field indicates in which message the detailed information of the wireless communication interface is included.
- Table 9 shows an example of the BR / EDR header.
- Table 10 below shows an example of detailed information positions of the wireless communication interface according to the sixth seventh bit.
- Table 10 6th bit value 7th bit value Details Location 0 0 No More Data 0 One More Data in Scan Response One 0 More Data in GATT information One One More Data in Scan response and GATT information
- the advertisement PDUs of FIGS. 29B and 30B further include a Common Header field and an SDO Specific Content field.
- the fraud Common Header field has the same format as the BR / EDR field, and the SDO Specific Content field may include information necessary to obtain detailed information of the wireless communication interface.
- the frequency hopping synchronization (FHS) information may be included in the SDO specific content.
- the advertising PDU described above may be used throughout in the embodiments herein.
- FIG. 31 is a flowchart illustrating still another example of a method for providing information of a wireless communication interface through Bluetooth LE according to the present specification.
- the first device 200 and the second device 300 do not have a BLE connection.
- the first device 200 enters a scanning state in order to recognize a device capable of other BLE communication, and the second device 300 enters an advertising state. do.
- the wireless communication interface between the first device 200 and the second device 300 is in an inactive state.
- the first device 200 in the scanning state and the second device 300 in the advertising state may exchange information on the supportable wireless communication interface without a BLE connection (S3110).
- the first device 200 and the second device 300 enter a BLE connection state through a BLE connection procedure.
- the first device 200 transmits a GATT Read request to the second device 300 to obtain detailed information of the wireless communication interface (S3120).
- the second device 300 may transmit information requested from the first device 200 to the first device 200 through a GATT Read response (S3130).
- the first device 200 Upon receiving the GATT Read response including the detailed information of the wireless communication interface, the first device 200 transmits a GATT write request to the second device 300 to exchange anchor point information or delay value information; In operation S3140, a GATT write response is received in response to the GATT write request (S3150).
- the anchor point information and the delay value information may be exchanged in three ways.
- the first device 200 includes its anchor point information and / or delay value information in a GATT write request and transmits it to the second device 300, and the second device 300 also itself.
- Anchor Point information and / or Delay Value information is included in the GATT Write response and transmitted to the first device 200 to share Anchor Point and / or Delay Value information.
- the first device 200 includes its anchor point information and / or delay value information in the GATT write request and transmits it to the second device 300, and the second device 300 transmits the information. You can set the Anchor Point and / or Delay Values according to the information.
- the second device 300 includes its anchor point information and / or delay value information in the GATT write response to transmit it to the first device 200, and the first device 200 transmits the information. You can set the Anchor Point and / or Delay Values according to the information.
- the Anchor Point is information related to when to start the connection procedure of the wireless communication interface
- the Delay Value is information related to how long to start the connection procedure of the wireless communication interface after transmitting or receiving the GATT write response.
- the first device 200 and the second device 300 sharing the Anchor Point or Delay Value are activated to connect the deactivated wireless communication interface.
- the first device 200 and the second device 300 perform a connection procedure of the wireless communication interface after a time when the first device 200 and the second device 300 are set as anchor points or after a delay value from the reception / transmission of the GATT write response.
- the wireless communication interface is connected.
- FIG. 32 is a diagram illustrating an example of a UI (user interface) proposed in the present specification.
- devices such as the TV 300-1, the headset 300-2, the band 300-3, and the projector 300-4 include various wireless interfaces.
- the TV 300-1 may include a wireless communication interface for Bluetooth BR / EDR, Bluetooth LE, Wi-Fi, or Wi-Fi Direct, and in the case of the Headset 300-2, It may include a wireless communication interface for Bluetooth BR / EDR or Bluetooth LE.
- Such wireless communication interfaces connect devices through various embodiments described above to enable wireless communication between the first device 200 and the second device 300.
- the peripheral devices when searching for a peripheral device using the BLE included in the first device 200, the peripheral devices to the first device 200 using the BLE to determine which wireless communication interface it contains Inform.
- 32 (b) shows the types of wireless communication interfaces included in the peripheral devices searched by the first device 200 and the searched devices are displayed on the first device 200.
- a connection procedure of the selected wireless communication interface is performed, and the first device and the selected device are connected through the selected wireless communication interface.
- Table 11 is a table showing an example of the command used in the embodiment of the present specification.
- Table 11 Name Description Power on Command to turn on when the user wants to use interface is Off Power off Command to turn off the interface when the service you want to use is terminated Information Update The command to update the information of the interface stored in BLE when the information of the interface is changed. Time out If the handover procedure is not completed within a certain time, the operation stops. Direct connection Immediate connection to other interfaces without delay Handover start Command to perform handover Handover end Command to stop service of the handed over interface Reason Request Command requesting the cause of the failure factor when the handover fails Authority setting Command to set the control authority of the connection target device Force disconnection Command to disconnect the connection when the target device is connected to other devices Security setting Command to set security strength for each interface
- 33A and 33C are flowcharts illustrating a method of exchanging information required for a Bluetooth BR / EDR connection through a Bluetooth LE proposed in the present specification.
- a Bluetooth BR / EDR connection may be performed by performing a handover information exchange procedure in a non-connected state.
- the first device 200 in the scanning state and the second device 300 in the advertisement state in the non-connected state of the Bluetooth LE may obtain information necessary for connection of the Bluetooth BR / EDR through a handover information exchange procedure. There is (S3312).
- the first device 200 and the second device 300 perform a procedure for connecting the Bluetooth BR / EDR (S3314).
- a part of the connection procedure may be omitted by utilizing the information exchanged through the handover information exchange procedure.
- the first device 200 and the second device 300 may perform a Bluetooth BR / EDR connection.
- FIG. 33B is a method of exchanging handover information in a connected state of a Bluetooth LE.
- the first device 200 in the scanning state and the second device 300 in the advertisement state are in a Bluetooth LE connection state through a Bluetooth LE connection procedure (S3322).
- the first device 200 and the second device 300 perform a handover information exchange procedure in order to exchange information necessary for handover of the Bluetooth BR / EDR through the Bluetooth LE link (S3324).
- the first device 200 and / or the second device 300 having obtained the information necessary for the Bluetooth BR / EDR connection through the handover information exchange procedure may have a Bluetooth BR / EDR connection state through the BR / EDR connection procedure. do.
- connection procedure may be omitted by utilizing the information exchanged through the handover information exchange procedure.
- FIG. 33A illustrates a specific process of the handover information exchange procedure described with reference to FIGS. 33A and 33B.
- the first device 200 transmits a handover request message to the second device 300 in order to exchange handover information with the second device 300 (S3332).
- the handover request message may have a format as shown in (b) of FIG. 33C.
- the interface type field includes type information of an interface to be handed over, and the handover information includes information for connection of the interface, and may include information of Table 12 below.
- the handover request message may include information for performing a handover, and the second device 300 transmits a handover response message to the first device 200 in response to the handover request message. (S3334).
- the handover response message may include information for handover or may simply be a response to the handover request message.
- the corresponding interface is enabled according to the information included in the handover request message to perform the connection procedure.
- connection procedure of the corresponding interface may be performed from the beginning, or part of the connection procedure may be omitted based on the information exchanged in the capability information exchange procedure and the handover information exchange procedure described above.
- Table 12 below shows an example of information exchanged through the handover information exchange procedure.
- Table 12 Name Category Description Class of device Parameter Indicates which device class the device belongs to. (ex: Print, Headset, TV,...) Clock information Parameter Information about the native clock Link Address Parameter ID value of the Link Device address Parameter MAC address of the device Scan window interval Parameter Information on the Scan Window of the Machine Number of connections Parameter The number of devices currently connected Channel map Parameter Parameter Parameters needed to create a channel map Connection status Parameter Information about which device your device is connected to Active period Parameter Active time value when operating alternately between Sleep and Sleep states Sleep period Parameter Time value in Sleep state when operating alternately between Active and Sleep states Role information Parameter Select whether the device will perform a page scan and become a slave, or perform a page and become a master device Connection Address Parameter Address to manage BLE connection (Ex: AA) CRC Parameter Parameter Value for BLE CRC Calculation (Ex: CRCInit) Winidowsize Parameter Duration information of data transmission section.
- the information in Table 12 may be used not only in the handover information exchange procedure but also in the capability information exchange procedure described above.
- the first device 200 and the second device 300 may obtain information for a Bluetooth LE or a Bluetooth BR / EDR connection.
- Bluetooth BR / EDR connection can be performed.
- 34A and 34B illustrate examples of state changes of the Bluetooth LR and the Bluetooth BR / EDR proposed in the present specification.
- the Bluetooth LE or the Bluetooth BR / EDR may be connected without any intermediate state through the information obtained in the connected state of the Bluetooth BR / EDR or LE.
- a connection state may be entered from a stand-by state, which is one of non-connection states, but this may be a separate connection establishment state or advertisement state for broadcast information. (Advertising State), etc.
- the device when the information for handover is obtained through the Bluetooth LE connection, the device enters the BR / EDR handover standby state for the Bluetooth BR / EDR connection.
- the device may enter a connection state without going through a separate intermediate state, for example, a connection establishment state.
- the device acquires information for handover through the Bluetooth BR / EDR connection, the device enters the BLE handover standby state for the Bluetooth LE connection.
- the device may enter a connection state without going through a separate intermediate state, for example, an advertisement state.
- the method of FIGS. 34A and 34B may be used to efficiently perform handover by not performing unnecessary procedures when connecting an interface in a non-connected state by using information obtained through an already connected interface.
- FIG. 35 is a flowchart illustrating an example of a method for handover from Bluetooth Low Energy (LE) to Bluetooth BR / EDR as proposed herein.
- LE Bluetooth Low Energy
- information for connecting a Bluetooth BR / EDR may be obtained through a Bluetooth LE connection, and a Bluetooth BR / EDR connection may be made using the obtained information.
- FIG. 35A illustrates a flow of performing a Bluetooth BR / EDR connection through a Bluetooth LE connection, wherein the first device 200 and the second device 300 are Bluetooth LE and Bluetooth BR. Both / EDRs are non-connected.
- the first device 200 and the second device 300 may discover the counterpart device through the BLE discovery procedure (S3510).
- the first device 200 and the second device 300 that have found the counterpart device perform the BLE connection procedure for BLE connection, and are in a BLE connection state (S3520).
- the first device 200 transmits a handover request message to the second device 300 to perform a handover to the Bluetooth BR / EDR through the connected Bluetooth LE link (S3530).
- the second device 300 receiving the handover request message transmits a handover response message to the first device 200 in response to the handover request message (S3540).
- the handover request message and / or the handover response message may include information for the Bluetooth BR / EDR connection described in Table 8.
- the two devices exchanging the handover request message and the handover response message are in a BLE connection state as shown in (b) of FIG. 35, and the BR / EDR handover wait state (BR / EDR) described in FIG. 34A. Handover Standby State).
- the first device 200 and the second device 300 may directly enter the Bluetooth BR / EDR connection state as described with reference to FIG. 34A, and are in a state where communication is possible.
- the BLE connection state and the BR / EDR handover standby state are simultaneously maintained, and the Bluetooth BR / EDR connection is performed through the handover request message and the handover response message. It is possible to perform fast Bluetooth BR / EDR connection without unnecessary procedures because it exchanges information for the network.
- FIG. 36 briefly illustrates a process of performing a Bluetooth BR / EDR connection through the Bluetooth LE connection described with reference to FIG. 35, and it can be seen that the scan interval is shorter than that of FIG. 7.
- the handover can be efficiently performed.
- FIG. 37 is a diagram illustrating an example of a method of sharing a channel map between wireless communication interfaces proposed in the present specification.
- the channel map parameter indicates whether to configure a channel map after handover or a new channel map based on the channel map before handover.
- the channel map parameter may be newly configured without using the channel map used in the existing BLE.
- the channel map is used based on the channel map before the handover, it is possible to reduce the time and power consumption for generating the channel map and to efficiently generate the channel map.
- 38 is a flowchart illustrating an example of a method of sharing a channel map between wireless communication interfaces proposed in the present specification.
- the first device 200 forms a channel map based on the existing channel map
- the second device 300 forms a new channel map
- the communication between the two cannot be performed smoothly.
- the first device 200 and the second device 300 may exchange the channel map parameter information described with reference to FIG. 37 to determine a new channel map formation.
- the first device 200 and the second device 300 form a BLE connection (S3810).
- the first device 200 and the second device 300 forming the BLE connection may form a channel map for BLE communication.
- the first device 200 and the second device 300 perform a handover procedure to the Bluetooth BR / EDR through one of the above-described embodiments (S3820) to form a Bluetooth BR / EDR connection. (S3830).
- the first device 200 and the second device 300 exchange the channel map parameter value through the handover procedure.
- the first device 200 and the second device 300 configure a channel map based on the channel map before handover, and the value of the channel map parameter is If set to the Fasle value, a new channel map is constructed to perform Bluetooth BR / EDR communication.
- FIG. 39 is a diagram comparing channels for estimating a channel map between Bluetooth Low Energy (LE) and Bluetooth BR / EDR proposed in the present specification.
- LE Bluetooth Low Energy
- the Bluetooth LE and the Bluetooth BR / EDR use an ISM band 2400 MHz to 2483.5 MHz spectrum, and have a similar method of classifying channels.
- the unused channel of the Bluetooth LE can be estimated as the unesed channel in the Bluetooth BR / EDR, and thus the channel map can be configured quickly and efficiently.
- 40A and 40B are diagrams illustrating an example of a method of estimating a channel map between Bluetooth Low Energy (LE) and Bluetooth BR / EDR proposed in the present specification.
- LE Bluetooth Low Energy
- the channel estimation algorithm is an algorithm for estimating a Bluetooth BR / EDR channel state using channel information obtained from a Bluetooth LE, and an algorithm for estimating Bluetooth LE channel state using channel information obtained from a Bluetooth BR / EDR. It is composed.
- C and CL are variables representing channel status.
- the variables C and CL may have a value of '0' or '1', and may be defined as 1 for unused and 0 for used. That is, if the channel state is not good, it is represented by 1.
- the 2402MHz channel is CL1 and the 2404MHz channel is CL2 In this way, the variable CL is defined up to 2480MHz. CL can be defined up to CL40.
- a variable C may be defined in this way as a C1 and a 2402 MHz channel as a C2, and a C2 may be defined up to C79.
- the variable is defined as ECL, and in case of Bluetooth BR / EDR.
- the channel of the Bluetooth BR / EDR may be estimated by Equation 1 below.
- Equation 1 the even channel can be estimated by the above equation, and the odd channel can be estimated by the following equation.
- Equation 1 S represents a scale factor and may have a value from 0 to 1.
- the state value of the channel estimated through the channel estimation may have a value of '1' or '0', through which the channel state of the Bluetooth BR / EDR may be configured by estimating the state of the channel.
- the channel of the Bluetooth LE may be estimated by Equation 2 below.
- Equation 2 S represents a scale factor and may have a value from 0 to 1.
- the state value of the channel estimated by the channel estimation may have a value of '1' or '0'.
- the channel state of the Bluetooth LE may be configured by estimating the state of the channel.
- the channel map after the handover can be quickly and efficiently configured through the channel map of the previously connected interface.
- 40B illustrates another example of a method for changing a channel between Bluetooth BR / EDR and Bluetooth LE, proposed in the specification.
- FIG. 40B illustrates a method of converting a channel from Bluetooth LE to Bluetooth BR / EDR.
- the channel state of the Bluetooth BR / EDR may be estimated according to the channel state of the Bluetooth LE. For example, if the RF channel index 4 of the Bluetooth LE is unused, the Bluetooth BR / EDR RF channel indexes 7,8, and 9 may be unused.
- the channel state of the Bluetooth LE may be estimated according to the channel state of the Bluetooth BR / EDR. For example, if the channel index 5 of the Bluetooth BR / EDR is unused, the RF channel indexes 2 and 3 of the Bluetooth LE may be unused.
- 40C and 40D illustrate examples of channel map estimation results proposed in the specification.
- Table 13 below shows a classification of the embodiments described with reference to FIGS. 12 to 44.
- 41 is a flowchart illustrating an example of a method for handover from Bluetooth LE to Bluetooth BR / EDR proposed in the specification.
- information required for a Bluetooth BR / EDR connection procedure may be obtained through a Bluetooth LE connection.
- the first device 200 exists in a BLE scanning state
- the second device 300 exists in a BLE advertisement state.
- the second device 300 transmits an advertisement message to the first device 200 (S4110).
- the advertisement message is a message for a capability information exchange procedure and may include capability information for a Bluetooth BR / EDR connection.
- the PDU type of the advertisement message may have the following type.
- the second device 300 that has transmitted the advertisement message may transmit an advertisement message for BLE connection to the first device 200 (S4120).
- the advertisement message is an advertisement message for BLE connection and may have the following PDU type.
- the first device 200 Upon receiving the advertisement message for the BLE connection, the first device 200 transmits a connection request message for requesting a BLE connection to the second device to perform a BLE connection (S4130).
- the first device 200 and the second device 300 want to make a Bluetooth BR / EDR connection, they can obtain handover information for the Bluetooth BR / EDR connection through a handover information exchange procedure and perform handover. have.
- the first device 200 may transmit a handover request message to the second device 300 (S4140).
- the handover request message may include the information for the Bluetooth BR / EDR connection described above, and the second device 300 receiving the handover request message sends a handover response message in response thereto. 2 may be transmitted to the device 300 (S4150).
- the handover request message and / or the handover response message may include information for Bluetooth BR / EDR connection.
- the first device 200 and the second device 300 which have obtained the information for the connection of the Bluetooth BR / EDR through the handover request message and the handover response message, have the Bluetooth BR / EDR handover described with reference to FIG. 34A. Enters the Handover Standby State.
- the Bluetooth BR / EDR handover standby state refers to a state in which the Bluetooth BR / EDR connection state can be directly entered as described with reference to FIG. 34A.
- the first device 200 and the second device 300 enter the Bluetooth connection state from the Bluetooth BR / EDR handover standby state.
- the second device 300 is switched to a hopping pattern of the first device 200.
- the first device 200 is connected to the second device 300.
- Poll packet is transmitted to the user (S4160).
- the second device 300 Upon receiving the poll packet, the second device 300 transmits a data packet to the first device 200 in response to the poll packet (S4170) and terminates the Bluetooth BR / EDR handover procedure.
- handover may be performed by obtaining capability information of an interface to be handed over through a scan request and a scan response.
- the first device and the second device exist in a BLE scanning state and a BLE advertisement state to perform a Bluetooth LE connection procedure.
- the second device 300 transmits an advertisement message to inform itself of the peripheral devices (S4210).
- the advertisement message may have the following PDU type.
- the first device that discovers the second device 300 through the advertisement message performs a procedure for a Bluetooth LE connection with the second device.
- the second device 300 transmits an advertisement message to the first device 200 for exchanging Bluetooth BR / EDR capability information (S4220).
- the advertisement message may be an advertisement message for a scanning procedure and may have a PDU type as follows.
- the first device 200 Upon receiving the advertisement message for the scanning procedure, the first device 200 transmits a scan request message to the second device 300 (S4230). In this case, the first device 200 may request the capability information of Table 8 to handover to the Bluetooth BR / EDR from the second device 300 through the scan request message.
- the second device 300 may transmit the requested capability information to the first device 200 through a scan response message in operation S4240.
- the second device 300 may transmit an advertisement message to the first device 200 for a BLE connection procedure (S4250).
- the advertisement message may have the following PDU type.
- the first device 200 receiving the advertisement message transmits a connection request message to the second device 300 for a BLE connection (4260), and the first device 200 and the second device 300. ) Becomes a BLE connection state.
- the second device 300 When the first device 200 communicating with the second device 300 in the BLE connection state wants to perform a handover with a Bluetooth BR / EDR, the second device ( 300, a BR / EDR handover request message is transmitted (S4270).
- the handover request message may include the handover information of Table 8.
- the second device 300 transmits a handover response message to the first device 200 in response to the handover request message (S4280).
- the first device 200 and the second device 300 having obtained the information for the connection of the Bluetooth BR / EDR through the handover request message and the handover response message are the Bluetooth BR / EDR described with reference to FIG. 34A. It enters the Handover Standby State.
- the Bluetooth BR / EDR handover standby state refers to a state in which the Bluetooth BR / EDR connection state can be directly entered as described with reference to FIG. 34A.
- the first device 200 and the second device 300 enter the Bluetooth connection state from the Bluetooth BR / EDR handover standby state.
- 43 is a flowchart illustrating another example of a method for handover from Bluetooth LE to Bluetooth BR / EDR proposed in the specification.
- the first device and the second device exist in a BLE scanning state and a BLE advertisement state to perform a Bluetooth LE connection procedure.
- the second device 300 transmits an advertisement message to inform itself of the peripheral devices (S4310).
- the advertisement message may have the following PDU type.
- the first device that discovers the second device 300 through the advertisement message performs a procedure for a Bluetooth LE connection with the second device.
- the second device 300 transmits an advertisement message to the first device 200 for exchanging Bluetooth BR / EDR capability information (S4320).
- the advertisement message may be an advertisement message for a scanning procedure and may have a PDU type as follows.
- the first device 200 that receives the advertisement message for the scanning procedure may request the capability information of the Bluetooth BR / EDR of Table 8.
- the first device 200 may have a different capability from the scan request message to the second device 300.
- the capability information may be requested through an information exchange request message (S4330).
- the second device 300 Upon receiving the capability information exchange request message, the second device 300 provides a caper to the first device 200 through a capability information exchange response message that may include more data than a scan response message.
- the capability information may be transmitted (S4340).
- the PDU type of the capability information exchange request message and the capability information exchange response message may have a Capability Exchange information_REQ and a Capability Exchange information_RSP type shown in Table 10 below, and may be defined through a reserved area.
- steps S4350 to S4380 are the same as S4250 to S4280 of FIG. 42, description thereof is omitted.
- 44 and 45 are diagrams illustrating an example of a method and data structure for handover from Bluetooth BR / EDR to Bluetooth LE proposed in the present specification.
- handover may be performed to a Bluetooth LE by exchanging capability information through an Extended Inquiry Response message for a Bluetooth BR / EDR connection.
- the first device 200 and the second device 300 in a Bluetooth BR / EDR non-connected state exist in a standby state, and the first device 200 is in an inquiries state to search for a Bluetooth BR / EDR. (Inquiry State), the second device 300 is in an Inquiry Scan State.
- the first device 200 transmits an ID packet to perform a Bluetooth BR / EDR discovery procedure (S4410), and in response to the FHS packet (FHS packet) from the second device 300. Frequency Hop Synchronization Packet) is received (S4420).
- the second device 300 may transmit additional information to the first device 200 using an enhanced inquiry packet. (S4430).
- the second device may transmit the capability information for the connection of the Bluetooth LE to the first device 200 through the EIR packet.
- the Extended Inquiry Response has a size of 240 bytes and consists of a plurality of EIR data structures.
- the EIR Data Structure is composed of a Length field indicating the size of the data and a Data field including the data.
- the Data field includes an EIR Data Type field indicating a data type and an EIR Data field including substantial data
- the second device 300 includes the capability information in the EIR Data field. It may transmit to the first device 200.
- the first device 200 and the second device 300 are in a BR / EDR connection state through a Bluetooth BR / EDR connection procedure (S4440).
- the second device When the first device 200 communicating with the second device 300 in the Bluetooth BR / EDR connection state intends to perform a handover to the Bluetooth LE, the second device is performed to perform a handover procedure.
- the BR / EDR handover request message is transmitted to the 300 (S4450).
- the handover request message may include the handover information of Table 8.
- the second device 300 transmits a handover response message to the first device 200 in response to the handover request message in operation S4460.
- the first device 200 and the second device 300 having obtained the information for the connection of the Bluetooth BR / EDR through the handover request message and the handover response message are the Bluetooth BR / EDR described with reference to FIG. 34A. It enters the Handover Standby State.
- the Bluetooth LE handover standby state refers to a state in which the Bluetooth LE connection state can be directly entered as described with reference to FIG. 34B.
- the first device 200 and the second device 300 enter the Bluetooth LE connection state from the Bluetooth LE handover standby state.
- 46 and 47 are diagrams illustrating an example of a method and data structure for handover from Bluetooth LE to Bluetooth BR / EDR proposed in the present specification.
- capability information may be exchanged through a Bluetooth control message.
- the first device 200 and the second device 300 may perform a capability information exchange procedure in order to exchange connection information of the Bluetooth BR / EDR in the Bluetooth LE connection state.
- the first device 200 may transmit a capability information request message to the second device 200 to request the capability information of Table 8 (S4610).
- the capability information request message is transmitted on a physical channel and may include an LL control PDU for link layer (LL) connection control among data channel PDUs.
- LL link layer
- the payload of the LL control PDU includes an Opcode field indicating the type of the LL control PDU and a Ctr Data field including control data as shown in FIG. 47A.
- the second device 300 may transmit capability information to the first device 200 through a capability information exchange response message in operation S4620. .
- the PDU type of the capability information request message and the capability information response message may have a PDU type of LL_Capability information exchange_REQ and LL_Capability information exchange_RSP of FIG. 47 (b), and may be defined through a reserved area.
- the second device 300 When the first device 200 communicating with the second device 300 in the BLE connection state wants to perform a handover with a Bluetooth BR / EDR, the second device ( 300, a BR / EDR handover request message is transmitted (S4630).
- the handover request message may include the handover information of Table 8.
- the second device 300 transmits a BR / EDR handover response message to the first device 200 in response to a BR / EDR handover request message (S4640).
- the first device 200 and the second device 300 having obtained the information for the connection of the Bluetooth BR / EDR through the handover request message and the handover response message are the Bluetooth BR / EDR described with reference to FIG. 34A. It enters the Handover Standby State.
- the Bluetooth BR / EDR handover standby state refers to a state in which the Bluetooth BR / EDR connection state can be directly entered as described with reference to FIG. 34A.
- the first device 200 and the second device 300 enter the Bluetooth connection state from the Bluetooth BR / EDR handover standby state.
- 48 is a flowchart illustrating another example of a method for handover from Bluetooth LE to Bluetooth BR / EDR proposed in the specification.
- the first device 200 and the second device 300 may perform handover by obtaining interface information through a GATT of a Bluetooth LE in a BLE connection state.
- the capability information of Table 5 is stored in the GATT form described above in the second device 300.
- the first device 200 reads a GATT to the second device 300 to read the capability information for the Bluetooth BR / EDR connection stored in the second device 300 in the Bluetooth LE connection state.
- a request message (GATT Read Request message) may be transmitted (S4810).
- the second device 300 Upon receiving the GATT read request message, the second device 300 sends the capability information requested by the first device 200 to the first device 200 through a GATT read response message. Can be transmitted (S4820).
- the GATT read request and GATT read response message may be freely used among ATT messages, which are protocols used by GATT.
- step S4830 to step S4840 are the same as step S4630 to step S4640 of FIG. 46, description thereof is omitted.
- 49 is a flowchart illustrating still another example of a method for handover from Bluetooth LE to Bluetooth BR / EDR proposed in the specification.
- the Bluetooth BR / EDR connection is performed by exchanging information for the Bluetooth BR / EDR connection while the Bluetooth LE connection is not made.
- the first device 200 and the second device 300 exist in a BLE scanning state and a BLE advertisement state to perform a Bluetooth LE connection procedure.
- the second device 300 may transmit a handover message to the first device 200 (S4910).
- the handover message is an example of a message defined for retrieval, connection, and service of Bluetooth BR / EDR interface information.
- the handover message includes the capability information of Table 5 for the Bluetooth BR / EDR connection.
- the first device 200 Upon receiving the handover message, the first device 200 transmits a BR / EDR handover request message to the second device 300 in order to perform a handover procedure (S4920).
- the handover request message may include the handover information of Table 8.
- the second device 300 transmits a BR / EDR handover response message to the first device 200 in response to a BR / EDR handover request message (S4930).
- the handover message, the handover request message and the handover response message are transmitted in an advertising physical channel and include an advertising channel PDU.
- Table 15 shows an example of a PDU type of the handover message, the handover request message, and the handover response message.
- the handover message may have an ADV_BR / EDR Handover
- the handover request message may have a BR / EDR Handover Request
- the handover response message may have a PDU type of BR / EDR Handover Response, and each PDU type is reserved in Table 11 above. Can be defined by a region.
- the first device 200 and the second device 300 that have obtained the information for performing the handover with the Bluetooth BR / EDR through the handover request message and the handover response message are the Bluetooth described with reference to FIG. 34A. It enters the BR / EDR Handover Standby State.
- the Bluetooth BR / EDR handover standby state refers to a state in which the Bluetooth BR / EDR connection state can be directly entered as described with reference to FIG. 34A.
- the first device 200 and the second device 300 enter the Bluetooth connection state from the Bluetooth BR / EDR handover standby state.
- 50 is a flowchart illustrating another example of a method for handover from Bluetooth LE to Bluetooth BR / EDR proposed in the specification.
- two devices may perform handover by exchanging information for handover in a state where Bluetooth LE connection is not established.
- the first device 200 and the second device 300 exist in a Bluetooth LE non-connected state, a Bluetooth LE scanning state and a BLE advertisement state.
- the second device 300 may transmit a handover message to the first device 200 to perform a Bluetooth BR / EDR capability information exchange procedure (S5010).
- the handover message has the same PDU type as the handover message described with reference to FIG. 49 and is an advertisement message that allows the BR / EDR handover request message to be transmitted to the first device 200.
- the first device 200 Upon receiving the handover message, the first device 200 transmits a capability information request message to the second device 300 to request capability information for the Bluetooth BR / EDR connection (S5020). ).
- the second device 300 transmits a capability information response message including the requested information to the first device 200 in response to the capability information request message (S5030).
- the second device 300 may allow the handover request message to be transmitted by transmitting a handover message to the first device (S5040).
- steps S5050 to S5060 are the same as steps S4920 to S4930 of FIG. 49, description thereof is omitted.
- 51A and 51B illustrate an example of a method and data format for estimating a channel map at handover from a Bluetooth LE to a Bluetooth BR / EDR as proposed herein.
- two devices may perform Bluetooth BR / EDR connection by exchanging information for Bluetooth BR / EDR connection in a Bluetooth LE connection state.
- the first device 200 is in a Bluetooth BLE scanning state
- the second device 300 is in a BLE advertisement state.
- the capability information of FIG. 5 may be exchanged through the capability information exchange procedure described above (S5110).
- the second device 300 having exchanged the capability information may allow a Bluetooth LE connection request message by transmitting an advertisement message to the first device 200 (S5120).
- the advertisement message may have the following PDU type.
- the first device 200 receiving the advertisement message transmits a connection request message to the second device 300 for the Bluetooth LE connection (S5130), and the first device 200 and the second device ( 300 enters the Bluetooth LE connection state.
- the second device 300 When the first device 200 communicating with the second device 300 in the BLE connection state wants to perform a handover with a Bluetooth BR / EDR, the second device ( 300, a BR / EDR handover request message is transmitted (S5140).
- the handover request message may include the handover information of Table 8.
- the second device 300 transmits a handover response message to the first device 200 in response to the handover request message (S5150).
- the handover request message and the handover response message are transmitted on a physical channel, and may include an LL control PDU for link layer (LL) connection control among data channel PDUs.
- LL link layer
- the payload of the LL control PDU is composed of an Opcode field indicating the type of the LL control PDU and a Ctr Data field including control data as shown in FIG. 51B (a).
- 51B illustrates a type of control PDU included in the opcode.
- the handover request message may have a PDU type of LL_BR / EDR Handover_REQ
- the handover response message may have a PDU type of LL_BR / EDR Handover_RSP, and may be defined through a reserved area.
- the first device 200 and the second device 300 may perform the channel map parameter exchange and channel estimation algorithm described with reference to FIGS. 37 to 40B (S5160).
- the first device 200 and the second device 300 which have constituted the channel map through the channel map parameter exchange and channel estimation algorithm, are in the Bluetooth BR / EDR handover standby state described with reference to FIG. 34A. Will enter.
- the Bluetooth BR / EDR handover standby state refers to a state in which the Bluetooth BR / EDR connection state can be directly entered as described with reference to FIG. 34A.
- the first device 200 and the second device 300 enter the Bluetooth connection state from the Bluetooth BR / EDR handover standby state.
- FIG. 52 is a flowchart illustrating still another example of a method for estimating a channel map at handover from a Bluetooth LE to a Bluetooth BR / EDR proposed in the specification.
- two devices may perform handover by exchanging information stored in a GATT form in a BLE connection state.
- Steps S5210 to 5230 are the same as steps S5110 to S5130 of FIG. 51A, and thus description thereof is omitted.
- the second device When the first device 200 communicating with the second device 300 in the BLE connection state wants to perform a handover with a Bluetooth BR / EDR, the second device ( In operation S5240, the GATT write request message may be transmitted to the GATT.
- the GATT write request message includes the handover information of Table 8, and the first device 200 may instruct the second device to handover through the GATT write request message.
- the second device 300 may transmit a GATT write response message to the first device 200 in response to the GATT write request message (S5250).
- the GATT write response message may include the handover information of Table 8.
- the GATT write request and GATT write response message may be freely used among ATT messages, which are protocols used by GATT.
- step S5260 is the same as step S5160 of FIG. 51A, description thereof is omitted.
- the first device 200 and the second device 300 which have obtained the information for the connection of the Bluetooth BR / EDR through the handover request message and the handover response message, have the Bluetooth BR / EDR handover described with reference to FIG. 34A. Enters the Handover Standby State.
- the Bluetooth BR / EDR handover standby state refers to a state in which the Bluetooth BR / EDR connection state can be directly entered as described with reference to FIG. 34A.
- the first device 200 and the second device 300 enter the Bluetooth connection state from the Bluetooth BR / EDR handover standby state.
- FIG. 53 illustrates an example of a method for notifying of a serviceable range between wireless communication interfaces proposed in the present specification.
- the first device 200 may search for a peripheral device through BLE and perform a handover with the found second device 300 to a wireless communication interface other than BLE.
- a parameter indicating information related to a service coverage of the wireless communication interface may be transmitted.
- the service area of the wireless communication interface may be determined based on the parameter, and handover is performed only when service is possible, thereby solving a problem in that a service cannot be provided after the handover.
- the serviceable area can be estimated through information such as transmission power of a wireless communication interface other than BLE.
- FIG. 54 is a flowchart illustrating an example of exchanging FHS (Frequency Hopping Synchronization) information of a Bluetooth BR / EDR proposed through the present specification.
- FHS Frequency Hopping Synchronization
- the first device 200 and the second device 300 form a BLE connection through a BLE connection procedure (S5410).
- the first device 200 and the second device 300 forming the BLE connection may exchange frequency hopping synchronization (FHS) information (S5420) and store the exchanged FHS information in a GATT data base.
- FHS frequency hopping synchronization
- the first device 200 and the second device 300 perform a handover procedure from BLE to Bluetooth BR / EDR based on the FHS information stored in the GATT data base (S5430).
- the connection state is established (S5440).
- the first device 200 and the second device 300 do not exchange FHS information in a situation where the Bluetooth BR / EDR connection is not established, and exchange handover information by directly exchanging information for connection. Can be done.
- the present disclosure relates to handover of Bluetooth, and more particularly, to a method and apparatus for connecting a Bluetooth BR / EDR or a Bluetooth LE interface using Bluetooth Low Energy (BR) or BR / EDR technology.
- BR Bluetooth Low Energy
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
PDU Type | Packet Name |
0000 | ADV_IND |
0001 | ADV_DIRECT_IND |
0010 | ADV_NONCONN_IND |
0011 | SCAN_REQ |
0100 | SCAN_RSP |
0101 | CONNECT_REQ |
0110 | ADV_SCAN_IND |
0111 - 1111 | Reserved |
RF Channel | RF CenterFrequency | 채널 타입(Channel Type) | 데이터 채널(Data Channel) | 광고 채널(Advertising Chanenl) |
0 | 2402 MHz | Advertising channel | 37 | |
1 | 2404 MHz | Data Channel | 0 | |
2 | 2406 MHz | Data Channel | 1 | |
... | ... | Data Channel | ... | |
11 | 2424 MHz | Data Channel | 10 | |
12 | 2426 MHz | Advertising channel | 38 | |
13 | 2428 MHz | Data Channel | 11 | |
14 | 2430 MHz | Data Channel | 12 | |
... | ... | Data Channel | ... | |
38 | 2478 MHz | Data Channel | 36 | |
39 | 2480 MHz | Advertising channel | 39 |
7th bit | 6th bit | 5th bit | 4th bit | 3rd bit | 2nd bit | 1st bit |
0 | 1 | 0 | 1 | 1 | 1 | 0 |
Bit | Network Interface |
1st bit | Wi - Fi |
2nd bit | Wi - Fi Direct |
3rd bit | WFDS Print |
4th bit | WFDS Display |
5th bit | Wi - Fi Display |
6th bit | NFC |
7th bit | Classic Bluetooth |
8th bit | WiGig |
9th bit | Zigbee |
10th bit | Future Interface |
Parameter | Description |
Device Address value | Device를 구별해주는 unique ID 값 |
Device Address type | 어떤 종류의 무선 인터페이스에 해당하는 Address인지를 구별 |
Device Address length | Device Address value의 길이 |
Device Class | 장치가 어느 장치부류에 속하는지를 가리킨다. (ex: Print, Head set 등) |
Security Information | Pairing 시 보안을 위하여 주고 받는 정보 |
Synch Code | 두 장치의 Synch를 맞추기 위해 주고 받는 값 |
Scan Window Interval | 장치가 다른 장치들이 보내는 신호를 수신하기 위하여 Listening하는 주기를 나타냄 |
Link Address | 두 장치 사이의 무선 연결이 이루어진 경우 Link를 구별하는 ID 값 |
Clock | 장치의 Native Clock |
Scan Mode | 장치가 다른 장치들이 보내는 신호를 수신하기 위하여Listening하는 패턴을 나타냄. |
Connection Start | 특정 무선 인터페이스를 이용한 장치간의 연결을 지시하는 명령 |
Number of connections | 특정 무선 인터페이스에 연결되어 있는 기기의 수 |
Device Status | 특정 무선 인터페이스의 on/off 상태 등 기기 상태 |
Carrier Bitmask | 기기가 가진 무선 인터페이스의 종류를 나타내는 값 |
Listen Channel | 검색 단계에서 P2P가 서로의 데이터를 교환하는 채널 |
Channel Class | Wi-Fi 등에서 사용되는 주파수 대역 (2.4GHz / 5GHz / 60GHz) |
SSID | 무선 기기와 AP 간에 접속용 식별자 |
P2P Capability | P2P Group에 연결이 가능한지 여부를 나타냄 |
Configuration Method | External Interface 에 종족적인 연결 방법 (e.g., WSCIE (Wi-Fi)) |
Supported Rate | Tx Rate |
Peer addr | Peer Device의 External Interface Address |
Channel Information | Supported Channel List 또는 Channel Map 등, 전반적인 Channel에 관한 정보 |
Operating Channel | 두 기기가 연결되어 데이터를 교환하는 채널 |
Connection Status | 기기가 타 기기와 연결되어 있는지, 어떤 기기와 연결되어 있는지에 대한 정보 |
Active Period | 인터페이스가 Active 상태와 Sleep 상태를 번갈아 가면서 동작할 경우 Active 상태인 시간 값 |
Sleep Period | 인터페이스가 Active 상태와 Sleep 상태를 번갈아 가면서 동작할 경우 Sleep 상태인 시간 값 |
Packet Transmission Interval | 인터페이스가 주기적으로 packet을 보내도록 설정되어 있을 경우 두 packet 사이의 시간 값 |
Service UUID(Universal Unique Identifier) | 디바이스 및 각 인터페이스가 제공하는 서비스들에 대한 UUID |
Name | Category | Description |
Capability information exchange | Procedure | BR/EDR의 connection을 위해 필요한 설정 정보 Parameters를 교환하기 위한 절차 BLE의 connection을 위해 필요한 설정 정보 Parameters를 교환하기 위한 절차 |
Capability information Parameter | Parameter | Capability information exchange procedure에서 교환되는 Parameters기기가 가지고 있는 Interface의 종류, 사용 가능한 서비스에 대한 정보 |
Handover information exchange | Procedure | Interface 전환 시 전환하는 Interface를 Enable 시키고 연결과정을 수행하도록 하는 절차 |
Handover information Parameter | Parameter | Interface 전환 시 필요한 Parameters |
BR/EDR Handover Standby | State | BR/EDR을 Standby 또는 off 상태에서 Connection 상태로 변환하기 위한 중간 상태 |
BLE Handover Standby | State | BLE를 Standby 또는 off 상태에서 Connection 상태로 변환하기 위한 중간 상태 |
Handover Request (Type: BR/EDR) | Message | BR/EDR이 Disable 상태인 경우 BR/EDR을 Enable 시킨 후, BR/EDR Handover Standby state로 전환하고, BR/EDR Connection 을 설정하도록 요청하는 Message |
Handover Response(Type: BR/EDR) | Message | BR/EDR Handover Request에 대한 응답 Message |
Handover Request(Type: BLE) | Message | BLE Disable 상태인 경우 BR/EDR을 Enable 시킨 후, BR/EDR Handover Standby state로 전환하고, BLE Connection 을 설정하도록 요청하는 Message |
Handover Response (Type: BLE) | Message | BLE Handover Request에 대한 응답 Message |
Channel Estimation Algorithm based on Channel map | Algorithm | BR/EDR이 생성한 Channel map을 BLE에 맞게 변경하는 알고리즘 또는 BLE가 생성한 Channel map을 BR/EDR에 맞게 변경하는 알고리즘 |
Channel map Parameter | Parameter | Channel map을 생성하는데 필요한 Parameters |
Name | Category | Description |
Device name | Parameter | 기기의 이름 |
Service ID | Parameter | 기기가 제공하는 서비스들에 대한 UUID |
Device type | Parameter | 장치가 어느 장치 부류에 속하는지를 가리킨다. (ex: Print, Headset, TV, …) |
Connection status | Parameter | 기기가 다른 어떤 기기와 연결되어 있는지에 대한 정보 |
Service Range | Parameter | 기기의 각 인터페이스가 서비스를 제공할 수 있는 거리 값. (ex - BR/EDR 30m) |
Interface Power | Parameter | 기기의 각 인터페이스의 Power (ex - BR/EDR 4dBm) |
Service Name | Parameter | 서비스의 이름 |
Icon ID | Parameter | 기기 Type에 대한 Icon을 구별하는 ID값 or 서비스의 종류에 대한 Icon을 구별하는 ID 값 |
Version information | Parameter | Human-readable Text를 구성하는 언어의 version |
SDO/SIG ID | Description |
1 | Wi - Fi |
2 | Wi - Fi Direct |
3 | WFDS Print |
4 | WFDS Display |
5 | Wi - Fi Display |
6 | NFC |
7 | Classic Bluetooth |
8 | WiGig |
9 | Zigbee |
10 | Future Interface |
7th bit | 6th bit | 5th bit | 4th bit | 3rd bit | 2nd bit | 1st bit |
MD1 | MD0 | TBD |
6번째 비트 값 | 7번째 비트 값 | 상세 정보 위치 |
0 | 0 | No More Data |
0 | 1 | More Data in Scan Response |
1 | 0 | More Data in GATT information |
1 | 1 | More Data in Scan response and GATT information |
Name | Description |
Power On | 사용자가 사용하기 원하는 인터페이스가 Off 상태일 경우 On 시키는 명령어 |
Power Off | 사용자가 사용하기 원하는 서비스가 종료되었을 경우 인터페이스를 Off 시키는 명령어 |
Information Update | 인터페이스의 정보가 변경되었을 경우 BLE에 저장된 인터페이스의 정보를 최신화 시키는 명령어 |
Time out | 일정 시간 내에 핸드오버 절차가 수행 완료되지 못할 경우 해당 동작을 중지 |
Direct Connection | Delay 없이 즉각적으로 다른 인터페이스에 대한 연결 수행 |
Handover Start | 핸드오버를 수행하라는 명령어 |
Handover End | 핸드오버된 인터페이스의 서비스를 중단시키는 명령어 |
Reason Request | 핸드오버 실패시 실패 요인에 대한 원인을 요청하는 명령어 |
Authority setting | 연결 대상 기기의 제어 권한을 설정하는 명령어 |
Force Disconnection | 연결 대상 기기가 타 기기들과 연결되어 있을 경우 해당 연결을 Disconnect 하는 명령어 |
Security setting | 각 인터페이스 별 보안 강도를 설정하는 명령어 |
Name | Category | Description |
Class of Device | Parameter | 장치가 어느 장치 부류에 속하는지를 가리킨다. (ex: Print, Headset, TV, …) |
Clock Information | Parameter | Native clock에 대한 정보 |
Link Address | Parameter | Link의 ID 값 |
Device Address | Parameter | 기기의 MAC 주소 |
Scan window interval | Parameter | 기기의 Scan window에 대한 정보 |
Number of connections | Parameter | 현재 connection되어 있는 기기의 수 |
Channel map Parameter | Parameter | Channel map을 생성하는데 필요한 Parameters |
Connection status | Parameter | 기기가 다른 어떤 기기와 연결되어 있는지에 대한 정보 |
Active Period | Parameter | Active 상태와 Sleep 상태를 번갈아 가면서 동작할 경우 Active 상태인 시간 값 |
Sleep Period | Parameter | Active 상태와 Sleep 상태를 번갈아 가면서 동작할 경우 Sleep 상태인 시간 값 |
Role information | Parameter | 기기가 Page scan을 수행하고 Slave가 될 것인지, Page를 수행하고 Master기기가 될 것인지를 선정 |
Connection Address | Parameter | BLE Connection을 관리하기 위한 주소 (Ex: AA) |
CRC Parameter | Parameter | BLE CRC 계산을 위한 값 (Ex: CRCInit) |
WinidowSize | Parameter | 데이터 송수신 구간의 duration 정보. BLE transmitWindowSize 값을 세팅하기 위한 값. (Ex: WinSize) |
Windowoffset | Parameter | 전송 Window의 시작 지점 정의. BLE transmitWindowOffset 값을 세팅하기 위한 값. (Ex: WinOffset) |
Connection Interval | Parameter | Connection Event의 간격에 대한 정보. BLE connInterval을 세팅하기 위한 값 (Ex: Interval) |
Connection Latency | Parameter | 데이터 교환이 없는 Connection Event의 수. BLE connslavelatency 를 세팅하기 위한 값(Ex: Latency) |
Timeout | Parameter | 연결 해제 상태를 감지 하기 위한 정보. BLE connSupervisionTimeout 을 세팅하기 위한 값 (Ex: Timeout) |
Channel map parameter | Parameter | BLE Channel map을 구성하기 위한 값 (Ex: ChM) |
Hop | Parameter | 데이터 교환 채널을 선정하는데 사용되는 값. BLE hopIncrement를 구성하기 위한 값 (Ex: Hop) |
Clock Accuracy | Parameter | 기기간 Clock을 맞추기 위한 정보. BLE masterSCA를 구성하기 위한 값 (Ex: SCA) |
절차 변경 여부 | ||||
케이퍼빌리티 정보 교환 | Non-connected | Advertising | Advertising 이용 Capability information Parameter 전달 Advertising packet size 부족할 우려가 있음 | |
New Advertising | Capability information Parameter 전달 위한 Advertising packet 정의 새로운 message 정의 필요 | |||
Scan Response | Scan Response 부족할 우려가 있음. 다수의 기기 검색이 어려움 | |||
New Scan Response | Capability information Parameter 전달 위한 Advertising packet 정의 다수의 기기 검색이 어려움. 새로운 message 정의 필요 | |||
EIR | ||||
Connected | GATT database | 검색을 위해 연결 절차를 수행해야 하는 번거로움이 있음 | ||
Combination | Advertising | |||
New Advertising | 새로운 message 정의 필요 | |||
Scan Response | 다수의 기기 검색이 어려움 | |||
New Scan Response | 다수의 기기 검색이 어려움 | |||
핸드오버 정보 교환 | Non-connected | Advertising | 변경 없음 | 보안의 문제가 있을 수 있음. 연결 시간이 오래 걸림 |
일부 변경 | 보안의 문제가 있을 수 있음 | |||
생략 | 보안의 문제가 있을 수 있음 | |||
New Advertising | 변경 없음 | 보안의 문제가 있을 수 있음. 새로운 message 정의 필요 | ||
일부 변경 | 보안의 문제가 있을 수 있음. 새로운 message 정의 필요 | |||
생략 | 보안의 문제가 있을 수 있음. 새로운 message 정의 필요 | |||
Connected | GATT database | 변경 없음 | 연결 상태에서만 Handover를 할 수 있다는 번거로움이 있음. 연결 시간이 오래 걸림 | |
일부 변경 | 연결 상태에서만 Handover를 할 수 있다는 번거로움이 있음. | |||
생략 | 연결 상태에서만 Handover를 할 수 있다는 번거로움이 있음. |
PDU Type | Packet Name |
0000 | ADV_IND |
0001 | ADV_DIRECT_IND |
0010 | ADV_NONCONN_IND |
0011 | SCAN_REQ |
0100 | SCAN_RSP |
0101 | CONNECT_REQ |
0110 | ADV_SCAN_IND |
Capability Exchange information_REQ | |
Capability Exchange information_RSP | |
0111 - 1111 | Reserved |
PDU Type | Packet Name |
0000 | ADV_IND |
0001 | ADV_DIRECT_IND |
0010 | ADV_NONCONN_IND |
0011 | SCAN_REQ |
0100 | SCAN_RSP |
0101 | CONNECT_REQ |
0110 | ADV_SCAN_IND |
ADV_BR/EDR Handover | |
BR/EDR Handover Request | |
BR/EDR Handover Response | |
0111 - 1111 | Reserved |
Claims (15)
- 무선 통신 시스템에서, 블루투스 LE(Low Energy)를 이용하여 블루투스 BR/EDR을 연결하는 방법에 있어서, 제 1 디바이스에 의해 수행되는 방법은,제 2 디바이스로부터 광고 메시지를 수신하는 단계;상기 제 2 디바이스에게 상기 광고 메시지에 기초하여 블루투스 BR/EDR 연결과 관련된 세부 정보 요청을 위한 요청 메시지를 전송하는 단계;상기 요청 메시지에 대한 응답으로 상기 제 2 디바이스로부터 상기 세부 정보를 포함하는 응답 메시지를 수신하는 단계;상기 세부 정보에 기초하여 상기 제 2 디바이스에게 연결 요청 메시지를 전송하는 단계; 및상기 제 2 디바이스와 블루투스 BR/EDR 커넥션을 형성하는 단계를 포함하되,상기 광고 메시지는 상기 세부 정보의 위치 정보 또는 상기 블루투스 BR/EDR의 이용가능 정보 중 적어도 어느 하나를 포함하는 것을 특징으로 하는 방법.
- 제 1 항에 있어서,상기 위치 정보는, 스캔 응답 메시지, GATT(Generic Attribute Profile) data base 또는 스캔 응답 메시지 및 GATT data base 중 하나를 나타내는 것을 특징으로 하는 방법.
- 제 1항에 있어서,상기 세부 정보는, 주파수 정보, 채널맵 전환 정보, 전송 파워 정보 또는 연결상태 정보 중 적어도 하나를 포함하는 것을 특징으로 하는 방법.
- 제 3 항에 있어서,상기 채널맵 전환 정보가 ‘True’ 값인 경우, 블루투스 BR/EDR 채널맵은 블루투스 LE의 채널 맵을 기초로 생성되는 것을 특징으로 하는 방법.
- 제 4 항에 있어서,채널 추정 알고리즘을 통해 블루투스 BR/EDR 채널 맵을 형성하는 단계를 더 포함하는 것을 특징으로 하는 방법.
- 제 1 항에 있어서,상기 연결 요청 메시지는 디바이스 타입 정보, 서비스 종류 정보, 서비스 제공 거리 정보 중 적어도 어느 하나를 포함하는 것을 특징으로 하는 방법.
- 무선 통신 시스템에서, 블루투스 BR/EDR을 통해서 대체통신 수단의 커넥션을 형성하는 방법에 있어서, 제 1 디바이스에 의해 수행되는 방법은,제 2 디바이스에게 ID 패킷을 전송하는 단계;제 2 디바이스로부터 상기 ID 패킷에 대한 응답으로 대체 인터페이스와 관련된 제 1 정보가 포함된 응답 메시지를 수신하는 단계;상기 제 2 디바이스와 블루투스 BR/EDR 커넥션을 형성하는 단계;상기 형성된 블루투스 BR/EDR 커넥션을 통해 핸드오버 요청 메시지를 전송하는 단계;상기 핸드오버 요청 메시지에 대한 응답으로 핸드오버 응답 메시지를 수신하는 단계; 및상기 제 2 디바이스와 대체 인터페이스 링크를 형성하는 단계를 포함하되,상기 대체 인터페이스와 관련된 제 1 정보는 디바이스 타입, 서비스 종류, 서비스 제공 범위 중 적어도 어느 하나를 포함하고,상기 핸드오버 요청 메시지 또는 핸드오버 응답 메시지 중 적어도 하나는 상기 대체 인터페이스의 연결과 관련된 제 2 정보를 포함하는 것을 특징으로 하는 방법.
- 제 7 항에 있어서,상기 제 2 정보는, 주파수 정보, 채널맵 전환 정보, 전송 파워 정보, 연결 시간 정보 또는 연결상태 정보 중 적어도 하나를 포함하는 것을 특징으로 하는 방법.
- 제 8 항에 있어서,상기 채널맵 전환 정보가 ‘True’ 값인 경우, 상기 대체 인터페이스의 채널맵은 블루투스 LE의 채널 맵을 기초로 생성되는 것을 특징으로 하는 방법.
- 제 9항에 있어서,채널 추정 알고리즘을 통해 블루투스 BR/EDR 채널 맵을 형성하는 단계를 더 포함하는 것을 특징으로 하는 방법.
- 무선 통신 시스템에서, 블루투스 LE(Low Energy)를 이용하여 블루투스 BR/EDR을 연결하는 방법에 있어서, 제1 디바이스는,외부와 유선 및/또는 무선으로 신호를 송수신하기 위한 통신부; 및상기 통신부와 기능적으로 연결되는 제어부를 포함하되, 상기 제어부는,제 2 디바이스로부터 광고 메시지를 수신하고,상기 제 2 디바이스에게 상기 광고 메시지에 기초하여 블루투스 BR/EDR 연결과 관련된 세부 정보 요청을 위한 요청 메시지를 전송하며,상기 요청 메시지에 대한 응답으로 상기 제 2 디바이스로부터 상기 세부 정보를 포함하는 응답 메시지를 수신하고,상기 세부 정보에 기초하여 상기 제 2 디바이스에게 연결 요청 메시지를 전송하며,상기 제 2 디바이스와 블루투스 BR/EDR 커넥션을 형성하도록 제어하되,상기 광고 메시지는 상기 세부 정보의 위치 정보 또는 상기 블루투스 BR/EDR의 이용가능 정보 중 적어도 어느 하나를 포함하는 것을 특징으로 하는 장치.
- 제 11 항에 있어서,상기 위치 정보는 스캔 응답 메시지, GATT(Generic Attribute Profile) data base 또는 스캔 응답 메시지 및 GATT data base 중 하나를 나타내는 것을 특징으로 하는 장치.
- 제 11항에 있어서,상기 세부 정보는 주파수 정보, 채널맵 전환 정보, 전송 파워 정보 또는 연결상태 정보 중 적어도 하나를 포함하는 것을 특징으로 하는 장치.
- 제 13 항에 있어서,상기 채널맵 전환 정보가 ‘True’ 값인 경우, 블루투스 BR/EDR 채널맵은 블루투스 LE의 채널 맵을 기초로 생성되는 것을 특징으로 하는 장치.
- 무선 통신 시스템에서, 블루투스 BR/EDR을 통해서 대체통신 수단의 커넥션을 형성하는 방법에 있어서, 제 1 디바이스는,외부와 유선 및/또는 무선으로 신호를 송수신하기 위한 통신부; 및상기 통신부와 기능적으로 연결되는 제어부를 포함하되, 상기 제어부는,제 2 디바이스에게 ID 패킷을 전송하고,제 2 디바이스로부터 상기 ID 패킷에 대한 응답으로 대체 인터페이스와 관련된 제 1 정보가 포함된 응답 메시지를 수신하며,상기 제 2 디바이스와 블루투스 BR/EDR 커넥션을 형성하고,상기 형성된 블루투스 BR/EDR 커넥션을 통해 핸드오버 요청 메시지를 전송하며,상기 핸드오버 요청 메시지에 대한 응답으로 핸드오버 응답 메시지를 수신하고,상기 제 2 디바이스와 대체 인터페이스 링크를 형성하도록 제어하되,상기 대체 인터페이스와 관련된 제 1 정보는 디바이스 타입, 서비스 종류, 서비스 제공 범위 중 적어도 어느 하나를 포함하고,상기 핸드오버 요청 메시지 또는 핸드오버 응답 메시지 중 적어도 하나는 상기 대체 인터페이스의 연결과 관련된 제 2 정보를 포함하는 것을 특징으로 하는 장치.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020177003257A KR102397285B1 (ko) | 2014-07-31 | 2015-05-11 | 블루투스 통신을 지원하는 무선 통신 시스템에서 전자기기를 제어하기 위한 방법 및 장치 |
US15/500,677 US10548068B2 (en) | 2014-07-31 | 2015-05-11 | Method and apparatus for controlling electronic device in wireless communication system supporting bluetooth communication |
Applications Claiming Priority (10)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201462031167P | 2014-07-31 | 2014-07-31 | |
US62/031,167 | 2014-07-31 | ||
US201462067406P | 2014-10-22 | 2014-10-22 | |
US62/067,406 | 2014-10-22 | ||
US201462068749P | 2014-10-26 | 2014-10-26 | |
US62/068,749 | 2014-10-26 | ||
US201462080383P | 2014-11-16 | 2014-11-16 | |
US62/080,383 | 2014-11-16 | ||
US201562103025P | 2015-01-13 | 2015-01-13 | |
US62/103,025 | 2015-01-13 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016017909A1 true WO2016017909A1 (ko) | 2016-02-04 |
Family
ID=55217768
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2015/004675 WO2016017909A1 (ko) | 2014-07-31 | 2015-05-11 | 블루투스 통신을 지원하는 무선 통신 시스템에서 전자기기를 제어하기 위한 방법 및 장치 |
Country Status (3)
Country | Link |
---|---|
US (1) | US10548068B2 (ko) |
KR (1) | KR102397285B1 (ko) |
WO (1) | WO2016017909A1 (ko) |
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2017175446A (ja) * | 2016-03-24 | 2017-09-28 | キヤノン株式会社 | 通信装置、通信装置の制御方法及びプログラム |
WO2018004303A1 (ko) * | 2016-07-01 | 2018-01-04 | 엘지전자(주) | 블루투스 기술을 사용하는 장치의 인증 방법 및 장치 |
WO2018038459A1 (ko) * | 2016-08-22 | 2018-03-01 | 엘지전자(주) | 블루투스 기술을 이용하여 디바이스를 제어하기 위한 방법 및 장치 |
WO2018147592A1 (ko) * | 2017-02-09 | 2018-08-16 | 삼성전자 주식회사 | 근거리 무선 통신 시스템에서 디바이스의 연결 방법 및 장치 |
WO2018202651A1 (en) | 2017-05-03 | 2018-11-08 | British American Tobacco (Investments) Limited | A method and an aerosol delivery device for transmitting aerosol delivery device information |
CN109417758A (zh) * | 2016-06-27 | 2019-03-01 | 华为技术有限公司 | 一种蓝牙连接的方法及终端 |
WO2019147107A1 (ko) * | 2018-01-29 | 2019-08-01 | 엘지전자 주식회사 | 무선 통신시스템에서 블루투스를 이용하여 핸드오버를 수행하기 위한 방법 및 이를 위한 장치 |
CN110121902A (zh) * | 2016-12-28 | 2019-08-13 | 华为技术有限公司 | 一种通信建立的方法及终端 |
CN112399396A (zh) * | 2021-01-19 | 2021-02-23 | 深圳市汇顶科技股份有限公司 | 一种蓝牙连接切换方法、蓝牙芯片以及蓝牙设备 |
CN112469015A (zh) * | 2019-09-06 | 2021-03-09 | 华为技术有限公司 | 蓝牙连接的方法和电子设备 |
CN112911556A (zh) * | 2016-06-27 | 2021-06-04 | 华为技术有限公司 | 用于双模蓝牙设备之间建立经典蓝牙连接的方法和双模蓝牙设备 |
CN113329389A (zh) * | 2021-06-29 | 2021-08-31 | 北京小米移动软件有限公司 | 基于蓝牙连接的服务提供方法、装置、设备及存储介质 |
WO2022155797A1 (zh) * | 2021-01-19 | 2022-07-28 | 深圳市汇顶科技股份有限公司 | 一种蓝牙连接切换方法、蓝牙芯片以及蓝牙设备 |
US11871321B2 (en) | 2017-12-29 | 2024-01-09 | Nicoventures Trading Limited | Device identification method |
WO2024079178A1 (en) | 2022-10-11 | 2024-04-18 | Nicoventures Trading Limited | Data communication |
WO2024079207A1 (en) | 2022-10-11 | 2024-04-18 | Nicoventures Trading Limited | Data communication |
US12004574B2 (en) | 2017-12-29 | 2024-06-11 | Nicoventures Trading Limited | Data capture across devices |
Families Citing this family (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6463163B2 (ja) * | 2015-02-16 | 2019-01-30 | キヤノン株式会社 | 通信装置及びその制御方法、並びにプログラム |
US10111172B2 (en) * | 2015-03-20 | 2018-10-23 | Google Llc | Systems and methods for localized device wakeup using bluetooth low energy communications |
CN105263194A (zh) * | 2015-09-18 | 2016-01-20 | 北京金山安全软件有限公司 | 移动设备与固定设备之间通信连接的建立方法及装置 |
JP6184580B1 (ja) * | 2016-01-29 | 2017-08-23 | キヤノン株式会社 | 情報処理装置、制御方法およびプログラム |
JP6300855B2 (ja) * | 2016-03-24 | 2018-03-28 | キヤノン株式会社 | 印刷装置、印刷装置の制御方法及びプログラム |
JP6619682B2 (ja) | 2016-03-31 | 2019-12-11 | キヤノン株式会社 | 情報処理装置、制御方法およびプログラム |
US10749568B2 (en) * | 2016-08-10 | 2020-08-18 | Apple Inc. | Multiband Bluetooth |
US10334515B2 (en) | 2017-01-13 | 2019-06-25 | ENK Wireless, Inc. | Conveying information via auxiliary device selection |
CN108923819B (zh) * | 2017-04-24 | 2020-04-21 | 广东虚拟现实科技有限公司 | 一种通信连接的方法、设备及系统 |
WO2018222024A1 (ko) * | 2017-06-02 | 2018-12-06 | 엘지전자(주) | 블루투스 le 기술을 이용하여 디바이스를 연결하기 위한 방법 및 장치 |
JP6832794B2 (ja) * | 2017-06-05 | 2021-02-24 | ルネサスエレクトロニクス株式会社 | 無線通信システム |
US10039057B1 (en) * | 2017-06-06 | 2018-07-31 | Hong Kong Applied Science And Technology Research Institute Co., Ltd. | Optimized deployment of BLE network and power efficient and secure management of data exchange between BLE devices |
WO2019009686A1 (ko) * | 2017-07-07 | 2019-01-10 | 엘지전자 주식회사 | 블루투스 저전력 에너지 기술을 이용하여 디바이스를 탐색하기 위한 방법 및 장치 |
US10149340B1 (en) | 2017-07-18 | 2018-12-04 | Thales Avionics, Inc. | Slave bluetooth device switching between active bluetooth connections with different master bluetooth devices |
CN111095935A (zh) * | 2017-09-19 | 2020-05-01 | Lg电子株式会社 | 显示装置及用于控制显示装置的终端 |
CN108734826B (zh) * | 2018-04-08 | 2020-11-17 | 珠海市芸鼎电子科技有限公司 | 一种混合模式的蓝牙自动解锁验证方法 |
US12004061B2 (en) * | 2018-08-01 | 2024-06-04 | Huawei Technologies Co., Ltd. | Bluetooth communication method and dual-mode Bluetooth terminal |
KR102600892B1 (ko) | 2018-08-08 | 2023-11-10 | 삼성전자주식회사 | 블루투스 저전력을 이용하여 통신을 수행하는 장치 및 방법 |
WO2020055047A1 (ko) | 2018-09-13 | 2020-03-19 | 엘지전자 주식회사 | 차량용 무선 배터리 관리 시스템 |
US11601995B2 (en) | 2018-09-13 | 2023-03-07 | Lg Electronics Inc. | Wireless battery management system for vehicle |
US11051154B2 (en) * | 2018-10-03 | 2021-06-29 | Google Llc | Systems and methods for wirelessly coupling a wearable computing device |
KR20200044505A (ko) * | 2018-10-19 | 2020-04-29 | 삼성전자주식회사 | 링크 공유를 지원하는 전자 장치 및 이를 위한 방법 |
CN111200805B (zh) * | 2018-11-19 | 2023-11-24 | 福建天泉教育科技有限公司 | 基于蓝牙设备的蓝牙组网方法及其系统 |
US20220030505A1 (en) * | 2019-01-17 | 2022-01-27 | Lg Electronics Inc. | Method and device for providing audio service using bluetooth technology |
CN112073955B (zh) * | 2019-06-10 | 2022-03-15 | 海信视像科技股份有限公司 | 显示设备及蓝牙设备扫描方法 |
KR102258323B1 (ko) * | 2019-07-17 | 2021-05-31 | (주) 로보라이즌 | 블루투스 디바이스의 군집을 형성하는 방법 |
CN115379435A (zh) * | 2019-08-10 | 2022-11-22 | 华为技术有限公司 | 一种设备能力发现方法及p2p设备 |
CN112584364B (zh) | 2019-09-30 | 2024-03-08 | 阿里巴巴集团控股有限公司 | 蓝牙网络及其通信方法、设备和存储介质 |
KR20210039818A (ko) * | 2019-10-02 | 2021-04-12 | 삼성전자주식회사 | 블루투스 네트워크 환경에서 데이터 패킷을 전송하기 위한 전자 장치 및 그에 관한 방법 |
KR20210041927A (ko) * | 2019-10-08 | 2021-04-16 | 삼성전자주식회사 | 블루투스 네트워크 환경에서 데이터를 전송하기 위한 전자 장치 및 그에 관한 방법 |
CN112822663B (zh) * | 2019-10-31 | 2022-06-14 | 华为技术有限公司 | 蓝牙连接方法及相关装置 |
WO2021095918A1 (ko) * | 2019-11-13 | 2021-05-20 | 엘지전자 주식회사 | 영상표시장치, 서버 및 이를 포함하는 영상표시시스템 |
US11329842B2 (en) | 2020-02-07 | 2022-05-10 | Ademco Inc. | Dynamic superframe slotting |
CN111294737B (zh) * | 2020-02-28 | 2020-11-10 | 深圳市中科蓝讯科技股份有限公司 | 通过经典蓝牙生成和发射ble广播包的方法和系统 |
CN113395685B (zh) * | 2020-03-10 | 2023-07-11 | 华为技术有限公司 | 蓝牙通信系统和无线通信系统 |
JP7115498B2 (ja) * | 2020-03-17 | 2022-08-09 | カシオ計算機株式会社 | 無線通信装置、端末装置、無線通信システム、通信接続制御方法及びプログラム |
US11190920B2 (en) * | 2020-03-26 | 2021-11-30 | Ademco Inc. | Bluetooth using secondary channel |
US11412511B2 (en) | 2020-05-05 | 2022-08-09 | Facebook Technologies, Llc | Switching between different communication protocols |
WO2022019345A1 (ko) * | 2020-07-20 | 2022-01-27 | 엘지전자 주식회사 | 블루투스 디바이스를 검색 및 연결하기 위한 방법 및 장치 |
US11418362B2 (en) * | 2020-11-25 | 2022-08-16 | Schneider Electric It Corporation | Systems and methods for group control using service data objects |
DE112022000565T5 (de) * | 2021-02-16 | 2023-11-02 | Milwaukee Electric Tool Corporation | Kommunikation zwischen einem drahtlosen Staubsauggerät und einem Elektrowerkzeug |
US11582746B2 (en) | 2021-04-01 | 2023-02-14 | Ademco Inc. | Dynamic, multi-frequency superframe slotting |
CN113329381B (zh) * | 2021-04-28 | 2022-03-11 | 荣耀终端有限公司 | 一种建立蓝牙连接的方法及电子设备 |
FI130079B (en) * | 2021-06-16 | 2023-01-31 | Wirepas Oy | Configuration system for a wireless communication network |
EP4336873A4 (en) * | 2021-07-12 | 2024-05-01 | Huawei Technologies Co., Ltd. | BLUETOOTH CONNECTION METHOD AND DEVICE |
US11658736B2 (en) | 2021-07-13 | 2023-05-23 | Ademco Inc. | Keypad with repeater mode |
CN114938542B (zh) * | 2022-04-26 | 2023-10-27 | 珠海极海半导体有限公司 | Ble协议栈多链路管理方法、芯片和系统 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130288600A1 (en) * | 2012-04-25 | 2013-10-31 | Nokia Corporation | Method, apparatus, and computer program product for wireless charging detection |
US20140057567A1 (en) * | 2010-06-24 | 2014-02-27 | Broadcom Corporation | Method and system for multi-stage device filtering in a bluetooth low energy device |
US20140059235A1 (en) * | 2012-08-22 | 2014-02-27 | Nokia Corporation | Method and apparatus for utilizing advertisements to provide information regarding connection setup |
US20140188348A1 (en) * | 2012-12-27 | 2014-07-03 | GM Global Technology Operations LLC | Method and system for detecting proximity of an end device to a vehicle based on signal strength information received over a bluetooth low energy (ble) advertising channel |
Family Cites Families (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040014422A1 (en) * | 2002-07-19 | 2004-01-22 | Nokia Corporation | Method and system for handovers using service description data |
US8737917B2 (en) * | 2009-07-24 | 2014-05-27 | Broadcom Corporation | Method and system for a dual-mode bluetooth low energy device |
US20120052802A1 (en) * | 2010-08-24 | 2012-03-01 | Nokia Corporation | Advertisement of an existing wireless connection |
US9247212B2 (en) * | 2010-08-26 | 2016-01-26 | Blast Motion Inc. | Intelligent motion capture element |
JP5100854B2 (ja) * | 2011-01-31 | 2012-12-19 | 株式会社東芝 | 通信装置、及び通信方法 |
US20120196534A1 (en) * | 2011-02-01 | 2012-08-02 | Nokia Corporation | Method, apparatus, and computer program product for broadcasting in short-range communication |
US9706496B2 (en) * | 2011-10-31 | 2017-07-11 | Avago Technologies General Ip (Singapore) Pte. Ltd | Concurrent BLE scanning and initiation for bandwidth efficiency and power saving |
US9392545B2 (en) * | 2011-12-28 | 2016-07-12 | Intel Corporation | Power-efficient wireless data transfer |
US9094424B2 (en) * | 2012-01-18 | 2015-07-28 | Nokia Technologies Oy | Method, apparatus, and computer program product for digital stream swapping between signal sources |
US8929192B2 (en) * | 2012-01-25 | 2015-01-06 | Nokia Corporation | Method, apparatus, and computer program product for short-range communication based direction finding |
JP5242816B1 (ja) * | 2012-01-30 | 2013-07-24 | 株式会社東芝 | 通信装置、プログラム、及び通信方法 |
WO2013181778A1 (en) * | 2012-06-04 | 2013-12-12 | Qualcomm Incorporated | Automatic connection of bluetooth human interface devices |
US9044171B2 (en) * | 2012-06-22 | 2015-06-02 | Fitbit, Inc. | GPS power conservation using environmental data |
US9641239B2 (en) * | 2012-06-22 | 2017-05-02 | Fitbit, Inc. | Adaptive data transfer using bluetooth |
US8880051B2 (en) * | 2012-11-16 | 2014-11-04 | Intel Corporation | Automatic seamless context sharing across multiple devices |
US10912131B2 (en) * | 2012-12-03 | 2021-02-02 | Samsung Electronics Co., Ltd. | Method and mobile terminal for controlling bluetooth low energy device |
US9066197B2 (en) * | 2013-01-22 | 2015-06-23 | Nokia Corporation | Method, apparatus, and computer program product for power save control for tethering connections |
US9077729B2 (en) * | 2013-02-26 | 2015-07-07 | Qualcomm Incorporated | Content management in peer-to-peer systems |
US9215075B1 (en) * | 2013-03-15 | 2015-12-15 | Poltorak Technologies Llc | System and method for secure relayed communications from an implantable medical device |
US9294903B2 (en) * | 2013-04-04 | 2016-03-22 | Nokia Technologies Oy | Method and apparatus for facilitating handover utilizing a predefined attribute protocol |
US20140304381A1 (en) * | 2013-04-05 | 2014-10-09 | Nokia Corporation | Method and apparatus for communicating with smart objects |
US20140307600A1 (en) * | 2013-04-15 | 2014-10-16 | Nokia Corporation | Method, apparatus, and computer program product for reducing power consumption for wireless communications |
US9451436B2 (en) * | 2013-05-31 | 2016-09-20 | Nokia Technologies Oy | Method, apparatus, and computer program product for wireless device discovery |
GB201312398D0 (en) * | 2013-07-10 | 2013-08-21 | Powa Technologies Ltd | Electronic transaction validation |
KR102194301B1 (ko) * | 2013-11-14 | 2020-12-22 | 삼성전자주식회사 | 전자 장치들의 통신 연결 방법 및 장치 |
US10159044B2 (en) * | 2013-12-09 | 2018-12-18 | GM Global Technology Operations LLC | Method and apparatus for controlling operating states of bluetooth interfaces of a bluetooth module |
US9258695B2 (en) * | 2013-12-16 | 2016-02-09 | Nokia Technologies Oy | Method, apparatus, and computer program product for service discovery in short-range communication environment |
US9635690B2 (en) * | 2014-06-24 | 2017-04-25 | Nokia Technologies Oy | Method, apparatus, and computer program product for improving security for wireless communication |
-
2015
- 2015-05-11 KR KR1020177003257A patent/KR102397285B1/ko active IP Right Grant
- 2015-05-11 WO PCT/KR2015/004675 patent/WO2016017909A1/ko active Application Filing
- 2015-05-11 US US15/500,677 patent/US10548068B2/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140057567A1 (en) * | 2010-06-24 | 2014-02-27 | Broadcom Corporation | Method and system for multi-stage device filtering in a bluetooth low energy device |
US20130288600A1 (en) * | 2012-04-25 | 2013-10-31 | Nokia Corporation | Method, apparatus, and computer program product for wireless charging detection |
US20140059235A1 (en) * | 2012-08-22 | 2014-02-27 | Nokia Corporation | Method and apparatus for utilizing advertisements to provide information regarding connection setup |
US20140188348A1 (en) * | 2012-12-27 | 2014-07-03 | GM Global Technology Operations LLC | Method and system for detecting proximity of an end device to a vehicle based on signal strength information received over a bluetooth low energy (ble) advertising channel |
Cited By (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2017175446A (ja) * | 2016-03-24 | 2017-09-28 | キヤノン株式会社 | 通信装置、通信装置の制御方法及びプログラム |
US10645559B2 (en) | 2016-06-27 | 2020-05-05 | Huawei Technologies Co., Ltd. | Bluetooth connection method and terminal |
CN112911556B (zh) * | 2016-06-27 | 2023-07-14 | 华为技术有限公司 | 用于双模蓝牙设备之间建立经典蓝牙连接的方法和双模蓝牙设备 |
CN112911556A (zh) * | 2016-06-27 | 2021-06-04 | 华为技术有限公司 | 用于双模蓝牙设备之间建立经典蓝牙连接的方法和双模蓝牙设备 |
CN109417758A (zh) * | 2016-06-27 | 2019-03-01 | 华为技术有限公司 | 一种蓝牙连接的方法及终端 |
EP3462802A4 (en) * | 2016-06-27 | 2019-06-12 | Huawei Technologies Co., Ltd. | BLUETOOTH CONNECTION METHOD, AND TERMINAL |
WO2018004303A1 (ko) * | 2016-07-01 | 2018-01-04 | 엘지전자(주) | 블루투스 기술을 사용하는 장치의 인증 방법 및 장치 |
US11012227B2 (en) | 2016-07-01 | 2021-05-18 | Lg Electronics Inc. | Authentication method and system for device using Bluetooth technology |
WO2018038459A1 (ko) * | 2016-08-22 | 2018-03-01 | 엘지전자(주) | 블루투스 기술을 이용하여 디바이스를 제어하기 위한 방법 및 장치 |
US10798548B2 (en) | 2016-08-22 | 2020-10-06 | Lg Electronics Inc. | Method for controlling device by using Bluetooth technology, and apparatus |
CN110121902A (zh) * | 2016-12-28 | 2019-08-13 | 华为技术有限公司 | 一种通信建立的方法及终端 |
CN110121902B (zh) * | 2016-12-28 | 2021-02-12 | 华为技术有限公司 | 一种通信建立的方法及终端 |
EP4164265A1 (en) * | 2016-12-28 | 2023-04-12 | Huawei Technologies Co., Ltd. | Communication establishment method and terminal |
EP3554109A4 (en) * | 2016-12-28 | 2019-10-16 | Huawei Technologies Co., Ltd. | METHOD FOR CONSTRUCTION OF A COMMUNICATION AND DEVICE |
US11172530B2 (en) | 2016-12-28 | 2021-11-09 | Huawei Technologies Co., Ltd. | Communication establishment method and terminal |
US11082856B2 (en) | 2017-02-09 | 2021-08-03 | Samsung Electronics Co., Ltd. | Method and device for connecting device in short-range wireless communication system |
WO2018147592A1 (ko) * | 2017-02-09 | 2018-08-16 | 삼성전자 주식회사 | 근거리 무선 통신 시스템에서 디바이스의 연결 방법 및 장치 |
US11510040B2 (en) | 2017-05-03 | 2022-11-22 | Nicoventures Trading Limited | Method and an aerosol delivery device for transmitting aerosol delivery device information |
WO2018202651A1 (en) | 2017-05-03 | 2018-11-08 | British American Tobacco (Investments) Limited | A method and an aerosol delivery device for transmitting aerosol delivery device information |
EP3928643A1 (en) | 2017-05-03 | 2021-12-29 | Nicoventures Trading Limited | A method and a aerosol delivery device for transmitting aerosol delivery device information |
US11924728B2 (en) | 2017-05-03 | 2024-03-05 | Nicoventures Trading Limited | Method and an aerosol delivery device for transmitting aerosol delivery |
EP4218457A1 (en) | 2017-05-03 | 2023-08-02 | Nicoventures Trading Limited | Data communication |
US12004574B2 (en) | 2017-12-29 | 2024-06-11 | Nicoventures Trading Limited | Data capture across devices |
US11871321B2 (en) | 2017-12-29 | 2024-01-09 | Nicoventures Trading Limited | Device identification method |
WO2019147107A1 (ko) * | 2018-01-29 | 2019-08-01 | 엘지전자 주식회사 | 무선 통신시스템에서 블루투스를 이용하여 핸드오버를 수행하기 위한 방법 및 이를 위한 장치 |
US11576100B2 (en) | 2018-01-29 | 2023-02-07 | Lg Electronics Inc. | Method for performing handover by using Bluetooth in wireless communication system, and device therefor |
US11825539B2 (en) | 2019-09-06 | 2023-11-21 | Huawei Technologies Co., Ltd. | Bluetooth connection method and electronic device |
CN112469015B (zh) * | 2019-09-06 | 2022-04-12 | 华为技术有限公司 | 蓝牙连接的方法和电子设备 |
CN112469015A (zh) * | 2019-09-06 | 2021-03-09 | 华为技术有限公司 | 蓝牙连接的方法和电子设备 |
WO2022155797A1 (zh) * | 2021-01-19 | 2022-07-28 | 深圳市汇顶科技股份有限公司 | 一种蓝牙连接切换方法、蓝牙芯片以及蓝牙设备 |
CN112399396A (zh) * | 2021-01-19 | 2021-02-23 | 深圳市汇顶科技股份有限公司 | 一种蓝牙连接切换方法、蓝牙芯片以及蓝牙设备 |
CN113329389B (zh) * | 2021-06-29 | 2023-05-23 | 北京小米移动软件有限公司 | 基于蓝牙连接的服务提供方法、装置、设备及存储介质 |
CN113329389A (zh) * | 2021-06-29 | 2021-08-31 | 北京小米移动软件有限公司 | 基于蓝牙连接的服务提供方法、装置、设备及存储介质 |
WO2024079178A1 (en) | 2022-10-11 | 2024-04-18 | Nicoventures Trading Limited | Data communication |
WO2024079207A1 (en) | 2022-10-11 | 2024-04-18 | Nicoventures Trading Limited | Data communication |
Also Published As
Publication number | Publication date |
---|---|
US10548068B2 (en) | 2020-01-28 |
US20170223615A1 (en) | 2017-08-03 |
KR20170038825A (ko) | 2017-04-07 |
KR102397285B1 (ko) | 2022-05-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2016017909A1 (ko) | 블루투스 통신을 지원하는 무선 통신 시스템에서 전자기기를 제어하기 위한 방법 및 장치 | |
WO2016017908A1 (ko) | 블루투스 통신을 지원하는 무선 통신 시스템에서 전자기기를 제어하기 위한 방법 및 장치 | |
WO2016017907A1 (ko) | 블루투스 통신을 지원하는 무선 통신 시스템에서 전자기기를 제어하기 위한 방법 및 장치 | |
WO2016167541A1 (ko) | 블루투스 저전력 기술을 이용하여 디바이스를 연결하기 위한 방법 및 장치 | |
WO2016122186A1 (ko) | 블루투스 기술을 이용하여 디바이스를 제어하기 위한 방법 및 장치 | |
WO2016039598A1 (ko) | 블루투스 기술을 이용하여 디바이스를 제어하기 위한 방법 및 장치 | |
WO2018074892A1 (ko) | 블루투스 기술을 이용하여 데이터를 송수신하기 위한 방법 및 장치 | |
WO2016182404A1 (ko) | 블루투스 저전력 에너지 기술을 이용하여 대체 통신 수단을 연결하기 위한 방법 및 장치 | |
WO2015194854A1 (ko) | 블루투스 le(low energy) 기술을 이용하여 디바이스 간 커넥션을 형성하기 위한 방법 및 장치 | |
WO2016010347A1 (ko) | 블루투스 le(low energy) 기술을 이용하여 디바이스의 위치를 측정하기 위한 방법 및 장치 | |
WO2016036139A2 (ko) | 블루투스 le(low energy) 기술을 이용하여 디바이스를 제어하기 위한 방법 및 장치 | |
WO2018222024A1 (ko) | 블루투스 le 기술을 이용하여 디바이스를 연결하기 위한 방법 및 장치 | |
WO2016175638A1 (ko) | 블루투스 메쉬 네트워크에서 디바이스의 주소를 할당하기 위한 방법 및 장치 | |
WO2015069030A1 (ko) | 블루투스 연결 방법 및 장치 | |
WO2018038459A1 (ko) | 블루투스 기술을 이용하여 디바이스를 제어하기 위한 방법 및 장치 | |
WO2018169380A1 (ko) | 블루투스 기술을 이용하여 오디오 신호를 처리하기 위한 방법 및 장치 | |
WO2016178542A1 (ko) | 블루투스에서 데이터를 송수신하기 위한 방법 및 장치 | |
WO2018048268A1 (ko) | 블루투스 기술을 이용하여 디바이스를 연결하기 위한 방법 및 장치 | |
WO2016159678A1 (ko) | 블루투스 저 전력 에너지 기술을 이용하여 디바이스를 제어하기 위한 방법 및 장치 | |
WO2015163680A1 (ko) | 무선 통신 시스템에서 블루투스 저전력 에너지 기술을 이용하여 데이터를 송수신하기 위한 방법 및 장치 | |
WO2017043869A1 (ko) | 블루투스 기술을 이용하여 디바이스를 제어하기 위한 방법 및 장치 | |
WO2016175454A1 (ko) | 블루투스 메쉬 네트워크를 이용하여 데이터를 송수신하기 위한 방법 및 장치 | |
WO2018097687A1 (ko) | 블루투스를 이용한 메쉬 네트워크에서 데이터를 송수신하기 위한 방법 및 장치 | |
WO2016108646A1 (ko) | 블루투스 le 기술을 이용하여 디바이스를 제어하기 위한 방법 및 장치 | |
WO2018135926A1 (ko) | 블루투스 통신 방법 및 장치 |
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: 15826538 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15500677 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 20177003257 Country of ref document: KR Kind code of ref document: A |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15826538 Country of ref document: EP Kind code of ref document: A1 |