US20130189924A1 - Mobile communications system providing enhanced out of band (oob) bluetooth pairing and related methods - Google Patents
Mobile communications system providing enhanced out of band (oob) bluetooth pairing and related methods Download PDFInfo
- Publication number
- US20130189924A1 US20130189924A1 US13/419,987 US201213419987A US2013189924A1 US 20130189924 A1 US20130189924 A1 US 20130189924A1 US 201213419987 A US201213419987 A US 201213419987A US 2013189924 A1 US2013189924 A1 US 2013189924A1
- Authority
- US
- United States
- Prior art keywords
- communications
- clock
- bluetooth
- bluetooth transceiver
- clock data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000010295 mobile communication Methods 0.000 title claims abstract description 27
- 238000000034 method Methods 0.000 title claims description 19
- 238000004891 communication Methods 0.000 claims abstract description 121
- 230000003287 optical effect Effects 0.000 claims description 6
- 230000000007 visual effect Effects 0.000 claims description 6
- 230000004044 response Effects 0.000 claims description 5
- 238000012545 processing Methods 0.000 description 9
- 230000005540 biological transmission Effects 0.000 description 5
- 238000006243 chemical reaction Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 5
- 238000012546 transfer Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003321 amplification Effects 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000003199 nucleic acid amplification method Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- IRLPACMLTUPBCL-KQYNXXCUSA-N 5'-adenylyl sulfate Chemical compound C1=NC=2C(N)=NC=NC=2N1[C@@H]1O[C@H](COP(O)(=O)OS(O)(=O)=O)[C@@H](O)[C@H]1O IRLPACMLTUPBCL-KQYNXXCUSA-N 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000006698 induction Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B5/00—Near-field transmission systems, e.g. inductive or capacitive transmission systems
- H04B5/40—Near-field transmission systems, e.g. inductive or capacitive transmission systems characterised by components specially adapted for near-field transmission
- H04B5/48—Transceivers
-
- 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
- H04W8/00—Network data management
- H04W8/005—Discovery of network devices, e.g. terminals
Definitions
- This application relates to the field of communications, and more particularly, to mobile wireless communications systems and related methods.
- PDA Personal Digital Assistant
- NFC near field communication
- RFID radio frequency identification
- NFC technology may also be used in association with other short-range wireless communications, such as a wireless Bluetooth connection.
- an NFC connection may often used to establish an out of band (OOB) wireless Bluetooth connection in which a Bluetooth MAC address, which is used for establishing the Bluetooth connection, is communicated via NFC.
- OOB out of band
- FIG. 1 is a schematic block diagram of a communications system in accordance with an example embodiment.
- FIG. 2 is a flow diagram illustrating method aspects associated with the system of FIG. 1 .
- FIG. 3 is a front view of an example communications device that may be used with the system of FIG. 1 .
- FIGS. 4-9 are schematic block diagrams illustrating pairing sequences which may be performed by the devices of FIG. 1 .
- FIG. 10 is a schematic block diagram illustrating mobile communications device components that may be used in accordance with an example embodiment.
- a communications system may include a communications device including a first Bluetooth transceiver.
- the first Bluetooth transceiver may comprise a clock.
- the first Bluetooth transceiver may be capable of scanning a plurality of different operating frequencies for a pairing request based upon the clock.
- the communications device may further include an output device coupled with the Bluetooth transceiver and capable of outputting data associated with the clock via a communications path different than Bluetooth.
- the system may also include a mobile communications device comprising an input device capable of receiving the clock data from the output device via the communications path, and a second Bluetooth transceiver coupled with the input device and capable of generating the pairing request based upon the received clock data.
- the system may advantageously allow for out of band (OOB) pairing, yet with reduced pairing times by adjusting a paging sequence in view of the clock of the target Bluetooth transceiver.
- OOB out of band
- the output device may comprise a first near field communication (NFC) transceiver, and the input device may comprise a second NFC transceiver.
- the output device may comprise a display configured to display a visual indicium or indicia (e.g., a Quick Response (QR) code, etc.) representing the clock data, and the input device may comprise an optical reader for reading the visual indicia.
- the output device may comprise a wireline transmitter, and the input device may comprise a corresponding wireline receiver (e.g., USB, etc.).
- the output device comprises a wireless transmitter
- the input device may comprise a corresponding wireless receiver (e.g., wireless local area network (WLAN), personal area network (PAN), ultra wideband (UWB), infrared, TransferJet, etc.).
- WLAN wireless local area network
- PAN personal area network
- UWB ultra wideband
- infrared TransferJet, etc.
- the second Bluetooth transceiver may be capable of generating the pairing request based upon a paging sequence, and changing the paging sequence based upon the received clock data.
- the clock data may comprise an absolute clock value.
- the clock data may comprise clock offset data.
- a related mobile communications device such as the one described briefly above, is also provided.
- a communications method for a first Bluetooth transceiver and a mobile communications device including a second Bluetooth transceiver may include receiving clock data associated with the first Bluetooth transceiver at the mobile communications device via a communications path different than Bluetooth. The method may further include generating a pairing request with the second NFC transceiver for pairing with the first Bluetooth transceiver based upon the received clock data.
- a related non-transitory computer-readable medium may be for causing a mobile communications device to perform steps including receiving clock data associated with a first Bluetooth transceiver via a communications path different than Bluetooth, and generating a pairing request with a second NFC transceiver of the mobile communications device for pairing with the first Bluetooth transceiver based upon the received clock data.
- the system 30 illustratively includes a communications device 31 including a first Bluetooth transceiver 32 , which comprises a first Bluetooth clock 33 .
- the communications device 31 further illustratively includes an output device 34 coupled with the Bluetooth transceiver 32 .
- the system 31 also illustratively includes a mobile communications device 35 (also referred to as a “mobile device” herein) including an input device 36 and a second Bluetooth transceiver 37 coupled with the input device 36 .
- the second Bluetooth transceiver 37 includes a second Bluetooth clock 38 .
- Example mobile devices 35 may include portable or personal media players (e.g., music or MP3 players, video players, etc.), portable gaming devices, portable or mobile telephones, smartphones, portable computers such as tablet computers, digital cameras, etc.
- the communications device 31 may also be a portable communications device, or it may be a “stationary” device in the sense that it is not ordinarily carried by a user, such as a desktop computer, for example.
- SSP Secure Simple Pairing
- NFC Near Field Communication
- Bluetooth includes wireless communication in accordance with one or more of the various Bluetooth Core Specifications (v1.0/v1.0 B, v1.1, v1.2, v2.0, v2.1, v3.0, v4.0, etc.), including Bluetooth low energy (BLE) communication.
- BLE Bluetooth low energy
- NFC P2P Peer-to-Peer OOB Bluetooth pairing is based on a standard proposed by the NFC Forum. See “Bluetooth Secure Simple Pairing Using NFC”, Application Document, NFC Forum, NFCForum-AD-BTSSP — 1.0, Oct. 18, 2011; and “Connection Handover”, Technical Specification, NFC Forum, Connection Handover 1.2, NFCForum-TS-ConnectionHandover — 1 — 2.doc, Jul. 7, 2010, both of which are hereby incorporated herein in their entireties by reference.
- the target Bluetooth MAC address is the only Bluetooth related information that is expected to be transmitted over NFC.
- NFC is a short-range wireless communications technology in which NFC-enabled devices are “swiped,” “bumped” or otherwise moved in close proximity to communicate.
- NFC may operate at 13.56 MHz and with an effective range of several centimeters (typically up to about 4 cm, or up to about 10 cm, depending upon the given implementation), but other suitable versions of near field communication which may have different operating frequencies, effective ranges, etc., for example, may also be used.
- Bluetooth pairing connection times may vary significantly depending on which scan repetition modes are chosen by the target device and the connecting device, as well as the clock states of each device.
- the communication device 31 is the target (or slave) device
- the mobile communications device 35 is the connecting (or master) device.
- SSP there are three possible inquiry and page scan modes for the connecting and target devices providing a possibility of nine connection scenarios.
- These scan modes includes an R0 mode (continuous scanning), an R1 mode (scans every 1.28 seconds), and an R2 mode (scans every 2.56 seconds).
- R0 mode continuous scanning
- R1 mode scans every 1.28 seconds
- R2 mode scans every 2.56 seconds
- an average expected Bluetooth pairing time is approximately 1.5 seconds with the target device in R1 mode and the connecting device also in R1 mode, as will be described further below.
- the target device is instead in R2 mode, then the expected connection time increases to approximately three seconds as a result of the above-noted scan rate.
- R1 and R2 modes are more frequently used for inquiry and page scanning, as the R0 mode may undesirably block other Bluetooth communications.
- the pairing connection will be established and the transfer commence nearly instantaneously due to the speed with which other NFC transactions may be performed (e.g., reading a smart poster tag, scanning a security badge, etc.).
- an NFC connection is first established, the Bluetooth MAC address information is exchanged, and then the Bluetooth connection is established.
- the Bluetooth MAC address information is exchanged, and then the Bluetooth connection is established.
- this results in an overall Bluetooth connection time which may take several seconds. In some cases the pairing process may even time out and be discontinued, depending on the given time out settings of the devices.
- the communications device 31 and the mobile communications device 35 may advantageously exchange additional information over the separate (non-Bluetooth) communications path regarding the first Bluetooth clock 33 to decrease the Bluetooth connection time.
- the clock data may comprise an absolute clock value indicating a current clock count for the first Bluetooth clock 33 , indicating where the clock is in its counting sequence. This information may advantageously be used by the second Bluetooth transceiver 37 to determine an offset with respect to the first Bluetooth clock 33 , so that it may thereby adjust its paging scan sequence to more readily pair with the first Bluetooth transceiver 32 .
- the clock offset data may be determined as part of the NFC exchange.
- the output device 34 and the input device 36 may consider the delay between the time of reading the clock data from the first Bluetooth clock 33 to providing the clock data to the second Bluetooth transceiver 37 .
- the output device 34 and the input device 36 may add in a delay or otherwise provide for the adjustment of the clock data to account for any latency in providing this data over the communications path.
- the output device 34 may account for the delay between reading of the clock data from the first Bluetooth clock 33 and outputting of the clock data for the input device 36 .
- the input device 36 may account for the delay from the transmission of the clock data from the output device 34 to the time of providing the clock data to the second Bluetooth transceiver 37 .
- these delays may be added on to the absolute clock value, and the delay may be estimated or measured (or both).
- the first Bluetooth transceiver 32 may be capable of scanning a plurality of different operating frequencies for a pairing request based upon the first Bluetooth clock 33 .
- the first Bluetooth clock 33 and the second Bluetooth clock 38 may have a counting cycle of approximately forty seconds, during which the first Bluetooth transceiver 32 and the second Bluetooth transceiver 37 will cycle once through all of the thirty-two available Bluetooth communication frequencies (in R1 mode).
- the output device 34 when using a Bluetooth OOB mode (Block 51 ), for example, the output device 34 is capable of or configured to output the above-noted data associated with the first Bluetooth clock 33 via a communications path different than Bluetooth (i.e., it is not wirelessly communicated from the first Bluetooth transceiver 32 to the second Bluetooth transceiver 37 via Bluetooth communications), at Block 52 .
- the input device 36 may be capable of or configured to receive the clock data from the output device 34 via the communications path, at Block 53 .
- the output device 34 and the input device 36 may each respectively comprise a NFC transceiver to advantageously allow for exchange of the clock data via an NFC communications link.
- the clock data may be included in an extended inquiry response (BIR) or other appropriate NFC data field, for example.
- BIR extended inquiry response
- the communications device 31 comprises a tablet computer including a display which operates as the output device 34 . More particularly, a visual indicium or indicia may be displayed on the display 41 , which may in turn be read by an optical sensor (e.g., a charge-coupled device (CCD)) which operates as the input device 36 of the mobile device 35 .
- an optical sensor e.g., a charge-coupled device (CCD)
- CCD charge-coupled device
- QR Quick Response
- pixels on the display 34 may be modulated to provide an optical data transmission of the clock data, for example.
- the output device 34 may comprise a wireline transmitter (e.g., USB, etc.), and the input device 36 may comprise a corresponding wireline receiver.
- the output device 34 may comprise a wireless transmitter (e.g., wireless local area network (WLAN), personal area network (PAN), ultra wideband (UWB), infrared, TransferJet, etc.), and the input device 36 may comprise a corresponding wireless receiver.
- WLAN wireless local area network
- PAN personal area network
- UWB ultra wideband
- infrared TransferJet, etc.
- the second Bluetooth transceiver 37 may advantageously change its Bluetooth paging sequence based upon the received clock data, at Block 54 , which illustratively concludes the method of FIG. 2 (Block 55 ).
- pairing may be performed even if the clock data is not received, at Block 56 , but this may result in longer average pairing times, as noted above,
- the system 30 may advantageously allow for OOB pairing, yet with reduced pairing times, by adjusting the paging sequence in view of the first Bluetooth clock 31 of the first Bluetooth transceiver 32 .
- the target Bluetooth clock offset with respect to the first Bluetooth clock 33 is known, then it is possible to halve the expected pairing time down to approximately 0.64 seconds (when the first Bluetooth transceiver 32 and the second Bluetooth transceiver 37 are both in R1 mode, as will be described further below). More particularly, by knowing the first Bluetooth clock 33 offset, which effectively lets the second Bluetooth transceiver 37 predict which frequency the first Bluetooth transceiver 32 will be listening on, the second Bluetooth transceiver 37 may adjust the set of paging scan frequencies that it will use to first attempt a pairing.
- NFC NFC Data Exchange Format
- the connecting device i.e., the mobile device 35
- the connecting device receives the OOB pairing information, it checks to see if a record (EIR, NDEF, etc.) was included for the Bluetooth clock information (Block 53 , FIG. 2 ). If the clock information was received, a command is sent to the second Bluetooth transceiver 37 firmware to adjust its current paging sequence offset so that outgoing paging attempts are expected to match the target frequency on the first or second paging packet.
- a record EIR, NDEF, etc.
- pairing times for GOB Bluetooth pairing with and without exchanging clock data will now be further described with reference to FIGS. 4-9 .
- a slave device 62 which would correspond to the communications device 31 or target device described above
- an GOB communications transport path e.g., NFC, optical, wireline, wireless, etc.
- master device 63 which would correspond to the mobile device 35 or connecting device described above.
- the above-described clock data is only transmitted to the master device 63 in the pairing sequence 61 , and not in the pairing sequence 60 .
- the master device 63 After receipt of the Bluetooth MAC address via the OOB transport path, the master device 63 begins transmitting on A train frequencies for 1.28 seconds, but there is only a 50% chance of a frequency match with the inquiry scan of the slave device 62 , even though there is a 100% chance that the slave device will be listening during this time with an average wait time of 0.64 seconds. This is because without the benefit of the clock offset information, a frequency clock adjustment cannot be performed by the master device 63 to attempt to synchronize the paging and inquiry scans, as occurs in the pairing sequence 61 of FIG. 5 . Thus, a second transmission on B train may be required for the pairing sequence 60 , leading to an average pairing time of approximately 1.28 second, whereas this second pairing scan may be avoided in the pairing sequence 61 to advantageously reduce the average paging time to about 0.64 seconds.
- Pairing sequences 64 and 65 are respectively similar to the pairing sequences 60 and 61 described above, expect in these examples the master device 63 is operating in the R2 scan mode, rather than R1. This results in an average paging time of approximately 2.24 seconds for the pairing sequence 64 (without clock data), versus an average paging time of 0.64 seconds for the paging sequence 65 (with clock data).
- the pairing sequences 66 and 67 are respectively similarly to the pairing sequences 64 and 65 , with the exception that the slave device 62 is also using the R2 scan mode (i.e., both the slave device 62 and the master device 63 are using the R2 scanning mode in these examples). As a result, there is an average paging time of approximately 2.56 seconds for the pairing sequence 64 (without clock data), versus an average paging time of approximately 1.28 seconds for the paging sequence 63 (with clock data).
- the device 1000 illustratively includes a housing 1200 , a keyboard or keypad 1400 and an output device 1600 .
- the output device shown is a display 1600 , which may comprise a full graphic LCD. Other types of output devices may alternatively be utilized.
- a processing device 1800 is contained within the housing 1200 and is coupled between the keypad 1400 and the display 1600 . The processing device 1800 controls the operation of the display 1600 , as well as the overall operation of the mobile device 1000 , in response to actuation of keys on the keypad 1400 .
- the housing 1200 may be elongated vertically, or may take on other sizes and shapes (including clamshell housing structures).
- the keypad may include a mode selection key, or other hardware or software for switching between text entry and telephony entry.
- FIG. 10 In addition to the processing device 1800 , other parts of the mobile device 1000 are shown schematically in FIG. 10 . These include a communications subsystem 1001 ; a short-range communications subsystem 1020 ; the keypad 1400 and the display 1600 , along with other input/output devices 1060 , 1080 , 1100 and 1120 ; as well as memory devices 1160 , 1180 and various other device subsystems 1201 .
- the mobile device 1000 may comprise a two-way RF communications device having data and, optionally, voice communications capabilities. In addition, the mobile device 1000 may have the capability to communicate with other computer systems via the Internet.
- Operating system software executed by the processing device 1800 is stored in a persistent store, such as the flash memory 1160 , but may be stored in other types of memory devices, such as a read only memory (ROM) or similar storage element.
- system software, specific device applications, or parts thereof may be temporarily loaded into a volatile store, such as the random access memory (RAM) 1180 .
- Communications signals received by the mobile device may also be stored in the RAM 1180 .
- the processing device 1800 in addition to its operating system functions, enables execution of software applications 1300 A- 1300 N on the device 1000 .
- a predetermined set of applications that control basic device operations, such as data and voice communications 1300 A and 1300 B, may be installed on the device 1000 during manufacture.
- a personal information manager (PIM) application may be installed during manufacture.
- the PIM may be capable of organizing and managing data items, such as e-mail, calendar events, voice mails, appointments, and task items.
- the PIM application may also be capable of sending and receiving data items via a wireless network 1401 .
- the PIM data items may be seamlessly integrated, synchronized and updated via the wireless network 1401 with corresponding data items stored or associated with a host computer system.
- the communications subsystem 1001 includes a receiver 1500 , a transmitter 1520 , and one or more antennas 1540 and 1560 .
- the communications subsystem 1001 also includes a processing module, such as a digital signal processor (DSP) 1580 , and local oscillators (LOs) 1601 .
- DSP digital signal processor
- LOs local oscillators
- a mobile device 1000 may include a communications subsystem 1001 designed to operate with the MobitexTM, Data TACTM or General Packet Radio Service (GPRS) mobile data communications networks, and also designed to operate with any of a variety of voice communications networks, such as AMPS, TDMA, CDMA, WCDMA, PCS, GSM, EDGE, etc. Other types of data and voice networks, both separate and integrated, may also be utilized with the mobile device 1000 .
- the mobile device 1000 may also be compliant with other communications standards such as 3GSM, 3GPP, UMTS, 4G, etc.
- Network access requirements vary depending upon the type of communication system. For example, in the Mobitex and DataTAC networks, mobile devices are registered on the network using a unique personal identification number or PIN associated with each device. In GPRS networks, however, network access is associated with a subscriber or user of a device. A GPRS device therefore typically involves use of a subscriber identity module, commonly referred to as a SIM card, in order to operate on a GPRS network.
- SIM card subscriber identity module
- the mobile device 1000 may send and receive communications signals over the communication network 1401 .
- Signals received from the communications network 1401 by the antenna 1540 are routed to the receiver 1500 , which provides for signal amplification, frequency down conversion, filtering, channel selection, etc., and may also provide analog to digital conversion. Analog-to-digital conversion of the received signal allows the DSP 1580 to perform more complex communications functions, such as demodulation and decoding.
- signals to be transmitted to the network 1401 are processed (e.g. modulated and encoded) by the DSP 1580 and are then provided to the transmitter 1520 for digital to analog conversion, frequency up conversion, filtering, amplification and transmission to the communication network 1401 (or networks) via the antenna 1560 .
- the DSP 1580 provides for control of the receiver 1500 and the transmitter 1520 .
- gains applied to communications signals in the receiver 1500 and transmitter 1520 may be adaptively controlled through automatic gain control algorithms implemented in the DSP 1580 .
- a received signal such as a text message or web page download
- the communications subsystem 1001 is input to the processing device 1800 .
- the received signal is then further processed by the processing device 1800 for an output to the display 1600 , or alternatively to some other auxiliary I/O device 1060 .
- a device may also be used to compose data items, such as e-mail messages, using the keypad 1400 and/or some other auxiliary I/O device 1060 , such as a touchpad, a rocker switch, a thumb-wheel, or some other type of input device.
- the composed data items may then be transmitted over the communications network 1401 via the communications subsystem 1001 .
- a voice communications mode In a voice communications mode, overall operation of the device is substantially similar to the data communications mode, except that received signals are output to a speaker 1100 , and signals for transmission are generated by a microphone 1120 .
- Alternative voice or audio I/O subsystems such as a voice message recording subsystem, may also be implemented on the device 1000 .
- the display 1600 may also be utilized in voice communications mode, for example to display the identity of a calling party, the duration of a voice call, or other voice call related information.
- the short-range communications subsystem enables communication between the mobile device 1000 and other proximate systems or devices, which need not necessarily be similar devices.
- the short-range communications subsystem may include an infrared device and associated circuits and components, a BluetoothTM communications module to provide for communication with similarly-enabled systems and devices, or a near field communications (NFC) device (which may include an associated secure element) for communicating with another NFC device or NFC tag via NFC communications.
- NFC near field communications
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
- This application relates to the field of communications, and more particularly, to mobile wireless communications systems and related methods.
- Mobile communication systems continue to grow in popularity and have become an integral part of both personal and business communications. Various mobile devices now incorporate Personal Digital Assistant (PDA) features such as calendars, address books, task lists, calculators, memo and writing programs, media players, games, etc. These multi-function devices usually allow electronic mail (email) messages to be sent and received wirelessly, as well as access the Internet via a cellular network and/or a wireless local area network (WLAN), for example.
- Some mobile devices incorporate contactless card technology and/or near field communication (NFC) chips. NFC technology is commonly used for contactless short-range communications based on radio frequency identification (RFID) standards, using magnetic field induction to enable communication between electronic devices, including mobile communications devices. This short-range high frequency wireless communications technology exchanges data between devices over a short distance, such as only a few centimeters.
- NFC technology may also be used in association with other short-range wireless communications, such as a wireless Bluetooth connection. For example, an NFC connection may often used to establish an out of band (OOB) wireless Bluetooth connection in which a Bluetooth MAC address, which is used for establishing the Bluetooth connection, is communicated via NFC.
-
FIG. 1 is a schematic block diagram of a communications system in accordance with an example embodiment. -
FIG. 2 is a flow diagram illustrating method aspects associated with the system ofFIG. 1 . -
FIG. 3 is a front view of an example communications device that may be used with the system ofFIG. 1 . -
FIGS. 4-9 are schematic block diagrams illustrating pairing sequences which may be performed by the devices ofFIG. 1 . -
FIG. 10 is a schematic block diagram illustrating mobile communications device components that may be used in accordance with an example embodiment. - The present description is made with reference to example embodiments. However, many different embodiments may be used, and thus the description should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete. Like numbers refer to like elements throughout.
- Generally speaking, a communications system is provided herein which may include a communications device including a first Bluetooth transceiver. The first Bluetooth transceiver may comprise a clock. The first Bluetooth transceiver may be capable of scanning a plurality of different operating frequencies for a pairing request based upon the clock. The communications device may further include an output device coupled with the Bluetooth transceiver and capable of outputting data associated with the clock via a communications path different than Bluetooth. The system may also include a mobile communications device comprising an input device capable of receiving the clock data from the output device via the communications path, and a second Bluetooth transceiver coupled with the input device and capable of generating the pairing request based upon the received clock data. As such, the system may advantageously allow for out of band (OOB) pairing, yet with reduced pairing times by adjusting a paging sequence in view of the clock of the target Bluetooth transceiver.
- By way of example, the output device may comprise a first near field communication (NFC) transceiver, and the input device may comprise a second NFC transceiver. In accordance with another example, the output device may comprise a display configured to display a visual indicium or indicia (e.g., a Quick Response (QR) code, etc.) representing the clock data, and the input device may comprise an optical reader for reading the visual indicia. In yet another example embodiment, the output device may comprise a wireline transmitter, and the input device may comprise a corresponding wireline receiver (e.g., USB, etc.). Still another example embodiment is provided in which the output device comprises a wireless transmitter, and the input device may comprise a corresponding wireless receiver (e.g., wireless local area network (WLAN), personal area network (PAN), ultra wideband (UWB), infrared, TransferJet, etc.).
- The second Bluetooth transceiver may be capable of generating the pairing request based upon a paging sequence, and changing the paging sequence based upon the received clock data. By way of example, the clock data may comprise an absolute clock value. In accordance with another example, the clock data may comprise clock offset data.
- A related mobile communications device, such as the one described briefly above, is also provided. Furthermore, a communications method for a first Bluetooth transceiver and a mobile communications device including a second Bluetooth transceiver may include receiving clock data associated with the first Bluetooth transceiver at the mobile communications device via a communications path different than Bluetooth. The method may further include generating a pairing request with the second NFC transceiver for pairing with the first Bluetooth transceiver based upon the received clock data.
- A related non-transitory computer-readable medium may be for causing a mobile communications device to perform steps including receiving clock data associated with a first Bluetooth transceiver via a communications path different than Bluetooth, and generating a pairing request with a second NFC transceiver of the mobile communications device for pairing with the first Bluetooth transceiver based upon the received clock data.
- Referring initially to
FIG. 1 , acommunications system 30 and associated method aspects are first described. Thesystem 30 illustratively includes acommunications device 31 including a first Bluetoothtransceiver 32, which comprises a first Bluetoothclock 33. Thecommunications device 31 further illustratively includes anoutput device 34 coupled with the Bluetoothtransceiver 32. Thesystem 31 also illustratively includes a mobile communications device 35 (also referred to as a “mobile device” herein) including aninput device 36 and a second Bluetoothtransceiver 37 coupled with theinput device 36. The second Bluetoothtransceiver 37 includes a second Bluetoothclock 38. Examplemobile devices 35 may include portable or personal media players (e.g., music or MP3 players, video players, etc.), portable gaming devices, portable or mobile telephones, smartphones, portable computers such as tablet computers, digital cameras, etc. Thecommunications device 31 may also be a portable communications device, or it may be a “stationary” device in the sense that it is not ordinarily carried by a user, such as a desktop computer, for example. - For two Bluetooth devices to communicate, they first establish a communications link between them by a process called pairing. During the pairing process, the two devices establish a relationship by creating a shared secret known as a link key. If a link key is stored by both devices they are said to be paired or bonded. In accordance with the Bluetooth Core Specification v2.1., for example, a Secure Simple Pairing (SSP) method may be used for Bluetooth device pairing. SSP has four different modes, namely a “just works” mode, a numeric comparison mode, a passkey entry mode, and an out of band (OOB) mode. The OOB mode uses an external or separate communication transport path (i.e., different than Bluetooth), such as Near Field Communication (NFC), to exchange some information used in the pairing process. Pairing is completed by the Bluetooth transceivers, but this requires information from the OOB transfer, namely the Bluetooth MAC address of the target device. As used herein, “Bluetooth” includes wireless communication in accordance with one or more of the various Bluetooth Core Specifications (v1.0/v1.0 B, v1.1, v1.2, v2.0, v2.1, v3.0, v4.0, etc.), including Bluetooth low energy (BLE) communication.
- More particularly, NFC P2P (Peer-to-Peer) OOB Bluetooth pairing is based on a standard proposed by the NFC Forum. See “Bluetooth Secure Simple Pairing Using NFC”, Application Document, NFC Forum, NFCForum-AD-BTSSP—1.0, Oct. 18, 2011; and “Connection Handover”, Technical Specification, NFC Forum, Connection Handover 1.2, NFCForum-TS-ConnectionHandover—1—2.doc, Jul. 7, 2010, both of which are hereby incorporated herein in their entireties by reference. In the standard, the target Bluetooth MAC address is the only Bluetooth related information that is expected to be transmitted over NFC. By way of background, NFC is a short-range wireless communications technology in which NFC-enabled devices are “swiped,” “bumped” or otherwise moved in close proximity to communicate. In one non-limiting example implementation, NFC may operate at 13.56 MHz and with an effective range of several centimeters (typically up to about 4 cm, or up to about 10 cm, depending upon the given implementation), but other suitable versions of near field communication which may have different operating frequencies, effective ranges, etc., for example, may also be used.
- With respect to OOB pairing, exchanging of only the target Bluetooth MAC address leads to connection times that are sometimes greater than desirable, and potentially in the range of several seconds. More specifically, Bluetooth pairing connection times may vary significantly depending on which scan repetition modes are chosen by the target device and the connecting device, as well as the clock states of each device. In the example of
FIG. 1 , thecommunication device 31 is the target (or slave) device, and themobile communications device 35 is the connecting (or master) device. - With respect to SSP, there are three possible inquiry and page scan modes for the connecting and target devices providing a possibility of nine connection scenarios. These scan modes includes an R0 mode (continuous scanning), an R1 mode (scans every 1.28 seconds), and an R2 mode (scans every 2.56 seconds). By way of example, with just a target MAC address to work with and an appropriate combination of scan repetition modes, an average expected Bluetooth pairing time is approximately 1.5 seconds with the target device in R1 mode and the connecting device also in R1 mode, as will be described further below. If the target device is instead in R2 mode, then the expected connection time increases to approximately three seconds as a result of the above-noted scan rate. R1 and R2 modes are more frequently used for inquiry and page scanning, as the R0 mode may undesirably block other Bluetooth communications.
- However, when using the NFC P2P transfer functionality for GOB pairing, there may be an expectation from many end users that the pairing connection will be established and the transfer commence nearly instantaneously due to the speed with which other NFC transactions may be performed (e.g., reading a smart poster tag, scanning a security badge, etc.). Yet, to perform an OOB Bluetooth pairing, an NFC connection is first established, the Bluetooth MAC address information is exchanged, and then the Bluetooth connection is established. Given the above-described pairing scan times when only the target Bluetooth MAC address is known, this results in an overall Bluetooth connection time which may take several seconds. In some cases the pairing process may even time out and be discontinued, depending on the given time out settings of the devices.
- To help expedite Bluetooth OOB pairing, the
communications device 31 and themobile communications device 35 may advantageously exchange additional information over the separate (non-Bluetooth) communications path regarding thefirst Bluetooth clock 33 to decrease the Bluetooth connection time. By way of example, the clock data may comprise an absolute clock value indicating a current clock count for thefirst Bluetooth clock 33, indicating where the clock is in its counting sequence. This information may advantageously be used by thesecond Bluetooth transceiver 37 to determine an offset with respect to thefirst Bluetooth clock 33, so that it may thereby adjust its paging scan sequence to more readily pair with thefirst Bluetooth transceiver 32. In other embodiments, the clock offset data may be determined as part of the NFC exchange. - Given the importance of clock data accuracy to properly adjusting the paging scan to achieve shorter pairing times, in some embodiments it may be desirable to account for any delay or latency in the communications path from the
output device 34 to theinput device 36. More particularly, one or both of theoutput device 34 and theinput device 36 may consider the delay between the time of reading the clock data from thefirst Bluetooth clock 33 to providing the clock data to thesecond Bluetooth transceiver 37. For example, one or both of theoutput device 34 and theinput device 36 may add in a delay or otherwise provide for the adjustment of the clock data to account for any latency in providing this data over the communications path. In accordance with one example implementation, theoutput device 34 may account for the delay between reading of the clock data from thefirst Bluetooth clock 33 and outputting of the clock data for theinput device 36. Moreover, theinput device 36 may account for the delay from the transmission of the clock data from theoutput device 34 to the time of providing the clock data to thesecond Bluetooth transceiver 37. By way of example, these delays may be added on to the absolute clock value, and the delay may be estimated or measured (or both). - Referring additionally to the flow diagram 49 of
FIG. 2 , thefirst Bluetooth transceiver 32 may be capable of scanning a plurality of different operating frequencies for a pairing request based upon thefirst Bluetooth clock 33. In an example embodiment, thefirst Bluetooth clock 33 and thesecond Bluetooth clock 38 may have a counting cycle of approximately forty seconds, during which thefirst Bluetooth transceiver 32 and thesecond Bluetooth transceiver 37 will cycle once through all of the thirty-two available Bluetooth communication frequencies (in R1 mode). - Beginning at
Block 50, when using a Bluetooth OOB mode (Block 51), for example, theoutput device 34 is capable of or configured to output the above-noted data associated with thefirst Bluetooth clock 33 via a communications path different than Bluetooth (i.e., it is not wirelessly communicated from thefirst Bluetooth transceiver 32 to thesecond Bluetooth transceiver 37 via Bluetooth communications), atBlock 52. Moreover, theinput device 36 may be capable of or configured to receive the clock data from theoutput device 34 via the communications path, atBlock 53. By way of example, theoutput device 34 and theinput device 36 may each respectively comprise a NFC transceiver to advantageously allow for exchange of the clock data via an NFC communications link. Also by way of example, the clock data may be included in an extended inquiry response (BIR) or other appropriate NFC data field, for example. - Referring additionally to
FIG. 3 , another communications path which may be used is an optical communications path. In the illustrated example, thecommunications device 31 comprises a tablet computer including a display which operates as theoutput device 34. More particularly, a visual indicium or indicia may be displayed on thedisplay 41, which may in turn be read by an optical sensor (e.g., a charge-coupled device (CCD)) which operates as theinput device 36 of themobile device 35. In the illustrated example, a Quick Response (QR) code is displayed on the display, which is used to transfer not only the Bluetooth MAC address of thefirst Bluetooth transceiver 32, but also the above-noted clock data. In other embodiments, pixels on thedisplay 34 may be modulated to provide an optical data transmission of the clock data, for example. - In accordance with another example embodiment, the
output device 34 may comprise a wireline transmitter (e.g., USB, etc.), and theinput device 36 may comprise a corresponding wireline receiver. In still another example embodiment, theoutput device 34 may comprise a wireless transmitter (e.g., wireless local area network (WLAN), personal area network (PAN), ultra wideband (UWB), infrared, TransferJet, etc.), and theinput device 36 may comprise a corresponding wireless receiver. - By having the benefit of the received clock data, the
second Bluetooth transceiver 37 may advantageously change its Bluetooth paging sequence based upon the received clock data, atBlock 54, which illustratively concludes the method ofFIG. 2 (Block 55). However, pairing may be performed even if the clock data is not received, atBlock 56, but this may result in longer average pairing times, as noted above, As such, thesystem 30 may advantageously allow for OOB pairing, yet with reduced pairing times, by adjusting the paging sequence in view of thefirst Bluetooth clock 31 of thefirst Bluetooth transceiver 32. More particularly, if the target Bluetooth clock offset with respect to thefirst Bluetooth clock 33 is known, then it is possible to halve the expected pairing time down to approximately 0.64 seconds (when thefirst Bluetooth transceiver 32 and thesecond Bluetooth transceiver 37 are both in R1 mode, as will be described further below). More particularly, by knowing thefirst Bluetooth clock 33 offset, which effectively lets thesecond Bluetooth transceiver 37 predict which frequency thefirst Bluetooth transceiver 32 will be listening on, thesecond Bluetooth transceiver 37 may adjust the set of paging scan frequencies that it will use to first attempt a pairing. - The foregoing will be further understood with reference to an example use case utilizing NFC as the initial communications transport path for OOB pairing. Upon detection of an NFC connection at the target device (i.e., the communications device 31), a command is sent to the
first Bluetooth transceiver 32 firmware to inquire what the current clock value is. This offset may be used by thesecond Bluetooth transceiver 37 to calculate the current frequency that thefirst Bluetooth transceiver 32 will be using to scan for incoming paging connections. The clock offset is then communicated to the NFC firmware, and an EIR record (which may be reserved for manufacturer specific information, for example) is created to encapsulate the current Bluetooth clock offset data. In accordance with another example, a NFC Data Exchange Format (NDEF) record may also be used to transfer the Bluetooth clock information. - Once the connecting device (i.e., the mobile device 35) receives the OOB pairing information, it checks to see if a record (EIR, NDEF, etc.) was included for the Bluetooth clock information (
Block 53,FIG. 2 ). If the clock information was received, a command is sent to thesecond Bluetooth transceiver 37 firmware to adjust its current paging sequence offset so that outgoing paging attempts are expected to match the target frequency on the first or second paging packet. - The differences in pairing times for GOB Bluetooth pairing with and without exchanging clock data will now be further described with reference to
FIGS. 4-9 . For the following examples, it is assumed that there is no RF interference, and that there are no SCO (synchronous connection orientated) links active. Inpairing sequences FIGS. 4 and 5 , respectively, a slave device 62 (which would correspond to thecommunications device 31 or target device described above) provides its Bluetooth MAC address via an GOB communications transport path (e.g., NFC, optical, wireline, wireless, etc.) to a master device 63 (which would correspond to themobile device 35 or connecting device described above). However, the above-described clock data is only transmitted to themaster device 63 in thepairing sequence 61, and not in thepairing sequence 60. - Accordingly, in the
pairing sequence 60, after receipt of the Bluetooth MAC address via the OOB transport path, themaster device 63 begins transmitting on A train frequencies for 1.28 seconds, but there is only a 50% chance of a frequency match with the inquiry scan of theslave device 62, even though there is a 100% chance that the slave device will be listening during this time with an average wait time of 0.64 seconds. This is because without the benefit of the clock offset information, a frequency clock adjustment cannot be performed by themaster device 63 to attempt to synchronize the paging and inquiry scans, as occurs in thepairing sequence 61 ofFIG. 5 . Thus, a second transmission on B train may be required for thepairing sequence 60, leading to an average pairing time of approximately 1.28 second, whereas this second pairing scan may be avoided in thepairing sequence 61 to advantageously reduce the average paging time to about 0.64 seconds. - Pairing
sequences pairing sequences master device 63 is operating in the R2 scan mode, rather than R1. This results in an average paging time of approximately 2.24 seconds for the pairing sequence 64 (without clock data), versus an average paging time of 0.64 seconds for the paging sequence 65 (with clock data). Similarly, thepairing sequences pairing sequences slave device 62 is also using the R2 scan mode (i.e., both theslave device 62 and themaster device 63 are using the R2 scanning mode in these examples). As a result, there is an average paging time of approximately 2.56 seconds for the pairing sequence 64 (without clock data), versus an average paging time of approximately 1.28 seconds for the paging sequence 63 (with clock data). - Example components of a
mobile communications device 1000 that may be used in accordance with the above-described embodiments are further described below with reference toFIG. 10 . Thedevice 1000 illustratively includes ahousing 1200, a keyboard orkeypad 1400 and anoutput device 1600. The output device shown is adisplay 1600, which may comprise a full graphic LCD. Other types of output devices may alternatively be utilized. Aprocessing device 1800 is contained within thehousing 1200 and is coupled between thekeypad 1400 and thedisplay 1600. Theprocessing device 1800 controls the operation of thedisplay 1600, as well as the overall operation of themobile device 1000, in response to actuation of keys on thekeypad 1400. - The
housing 1200 may be elongated vertically, or may take on other sizes and shapes (including clamshell housing structures). The keypad may include a mode selection key, or other hardware or software for switching between text entry and telephony entry. - In addition to the
processing device 1800, other parts of themobile device 1000 are shown schematically inFIG. 10 . These include acommunications subsystem 1001; a short-range communications subsystem 1020; thekeypad 1400 and thedisplay 1600, along with other input/output devices memory devices other device subsystems 1201. Themobile device 1000 may comprise a two-way RF communications device having data and, optionally, voice communications capabilities. In addition, themobile device 1000 may have the capability to communicate with other computer systems via the Internet. - Operating system software executed by the
processing device 1800 is stored in a persistent store, such as theflash memory 1160, but may be stored in other types of memory devices, such as a read only memory (ROM) or similar storage element. In addition, system software, specific device applications, or parts thereof, may be temporarily loaded into a volatile store, such as the random access memory (RAM) 1180. Communications signals received by the mobile device may also be stored in theRAM 1180. - The
processing device 1800, in addition to its operating system functions, enables execution ofsoftware applications 1300A-1300N on thedevice 1000. A predetermined set of applications that control basic device operations, such as data andvoice communications device 1000 during manufacture. In addition, a personal information manager (PIM) application may be installed during manufacture. The PIM may be capable of organizing and managing data items, such as e-mail, calendar events, voice mails, appointments, and task items. The PIM application may also be capable of sending and receiving data items via awireless network 1401. The PIM data items may be seamlessly integrated, synchronized and updated via thewireless network 1401 with corresponding data items stored or associated with a host computer system. - Communication functions, including data and voice communications, are performed through the
communications subsystem 1001, and possibly through the short-range communications subsystem. Thecommunications subsystem 1001 includes areceiver 1500, atransmitter 1520, and one ormore antennas communications subsystem 1001 also includes a processing module, such as a digital signal processor (DSP) 1580, and local oscillators (LOs) 1601. The specific design and implementation of thecommunications subsystem 1001 is dependent upon the communications network in which themobile device 1000 is intended to operate. For example, amobile device 1000 may include acommunications subsystem 1001 designed to operate with the Mobitex™, Data TAC™ or General Packet Radio Service (GPRS) mobile data communications networks, and also designed to operate with any of a variety of voice communications networks, such as AMPS, TDMA, CDMA, WCDMA, PCS, GSM, EDGE, etc. Other types of data and voice networks, both separate and integrated, may also be utilized with themobile device 1000. Themobile device 1000 may also be compliant with other communications standards such as 3GSM, 3GPP, UMTS, 4G, etc. - Network access requirements vary depending upon the type of communication system. For example, in the Mobitex and DataTAC networks, mobile devices are registered on the network using a unique personal identification number or PIN associated with each device. In GPRS networks, however, network access is associated with a subscriber or user of a device. A GPRS device therefore typically involves use of a subscriber identity module, commonly referred to as a SIM card, in order to operate on a GPRS network.
- When required network registration or activation procedures have been completed, the
mobile device 1000 may send and receive communications signals over thecommunication network 1401. Signals received from thecommunications network 1401 by theantenna 1540 are routed to thereceiver 1500, which provides for signal amplification, frequency down conversion, filtering, channel selection, etc., and may also provide analog to digital conversion. Analog-to-digital conversion of the received signal allows theDSP 1580 to perform more complex communications functions, such as demodulation and decoding. In a similar manner, signals to be transmitted to thenetwork 1401 are processed (e.g. modulated and encoded) by theDSP 1580 and are then provided to thetransmitter 1520 for digital to analog conversion, frequency up conversion, filtering, amplification and transmission to the communication network 1401 (or networks) via theantenna 1560. - In addition to processing communications signals, the
DSP 1580 provides for control of thereceiver 1500 and thetransmitter 1520. For example, gains applied to communications signals in thereceiver 1500 andtransmitter 1520 may be adaptively controlled through automatic gain control algorithms implemented in theDSP 1580. - In a data communications mode, a received signal, such as a text message or web page download, is processed by the
communications subsystem 1001 and is input to theprocessing device 1800. The received signal is then further processed by theprocessing device 1800 for an output to thedisplay 1600, or alternatively to some other auxiliary I/O device 1060. A device may also be used to compose data items, such as e-mail messages, using thekeypad 1400 and/or some other auxiliary I/O device 1060, such as a touchpad, a rocker switch, a thumb-wheel, or some other type of input device. The composed data items may then be transmitted over thecommunications network 1401 via thecommunications subsystem 1001. - In a voice communications mode, overall operation of the device is substantially similar to the data communications mode, except that received signals are output to a
speaker 1100, and signals for transmission are generated by amicrophone 1120. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on thedevice 1000. In addition, thedisplay 1600 may also be utilized in voice communications mode, for example to display the identity of a calling party, the duration of a voice call, or other voice call related information. - The short-range communications subsystem enables communication between the
mobile device 1000 and other proximate systems or devices, which need not necessarily be similar devices. For example, the short-range communications subsystem may include an infrared device and associated circuits and components, a Bluetooth™ communications module to provide for communication with similarly-enabled systems and devices, or a near field communications (NFC) device (which may include an associated secure element) for communicating with another NFC device or NFC tag via NFC communications. - Many modifications and other embodiments will come to the mind of one skilled in the art having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is understood that various modifications and embodiments are intended to be included within the scope of the appended claims.
Claims (25)
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/419,987 US8995908B2 (en) | 2012-01-25 | 2012-03-14 | Mobile communications system providing enhanced out of band (OOB) bluetooth pairing and related methods |
PCT/CA2013/050016 WO2013110185A1 (en) | 2012-01-25 | 2013-01-11 | Mobile communications system providing enhanced out of band (oob) bluetooth pairing and related methods |
CA2862130A CA2862130C (en) | 2012-01-25 | 2013-01-11 | Mobile communications system providing enhanced out of band (oob) bluetooth pairing and related methods |
EP13740650.0A EP2807875B1 (en) | 2012-01-25 | 2013-01-11 | Mobile communications system providing enhanced out of band (oob) bluetooth pairing and related methods |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201261590614P | 2012-01-25 | 2012-01-25 | |
US13/419,987 US8995908B2 (en) | 2012-01-25 | 2012-03-14 | Mobile communications system providing enhanced out of band (OOB) bluetooth pairing and related methods |
Publications (2)
Publication Number | Publication Date |
---|---|
US20130189924A1 true US20130189924A1 (en) | 2013-07-25 |
US8995908B2 US8995908B2 (en) | 2015-03-31 |
Family
ID=48797599
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/419,987 Active 2032-11-12 US8995908B2 (en) | 2012-01-25 | 2012-03-14 | Mobile communications system providing enhanced out of band (OOB) bluetooth pairing and related methods |
Country Status (4)
Country | Link |
---|---|
US (1) | US8995908B2 (en) |
EP (1) | EP2807875B1 (en) |
CA (1) | CA2862130C (en) |
WO (1) | WO2013110185A1 (en) |
Cited By (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140006510A1 (en) * | 2012-06-27 | 2014-01-02 | Google Inc. | Techniques for transferring a data payload utilizing near-field communication |
US20140094123A1 (en) * | 2012-09-28 | 2014-04-03 | Broadcom Corporation | Managing connectivity between wireless devices |
US20140104038A1 (en) * | 2012-10-16 | 2014-04-17 | Panasonic Corporation | Radio communication apparatus and radio communication system |
US20140133584A1 (en) * | 2012-11-12 | 2014-05-15 | Mediatek Inc. | Bluetooth device and related communications establishing method |
US20140187152A1 (en) * | 2012-12-28 | 2014-07-03 | Erik J. Johnson | Secure transfer of whiteboard content |
EP2843580A1 (en) * | 2013-08-30 | 2015-03-04 | Arcadyan Technology Corporation | Method for updating network connection parameters |
US20150264732A1 (en) * | 2014-03-14 | 2015-09-17 | Sony Corporation | Electronic device, communication system, control method of electronic device, and program |
US20160057564A1 (en) * | 2014-08-25 | 2016-02-25 | Hyundai Motor Company | Bluetooth pairing method using a wired connection |
JP6132037B1 (en) * | 2016-01-15 | 2017-05-24 | カシオ計算機株式会社 | Wireless communication method and program |
JP2017130971A (en) * | 2017-03-30 | 2017-07-27 | カシオ計算機株式会社 | Radio communication method and program |
US20180049122A1 (en) * | 2015-02-26 | 2018-02-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Energy efficient ble mesh initialisation and operation |
US9924019B2 (en) | 2015-05-15 | 2018-03-20 | Microsoft Technology Licensing, Llc | Automatic device pairing |
WO2018112417A1 (en) * | 2016-12-16 | 2018-06-21 | Roche Diabetes Care, Inc. | Methods and systems for affirmation of a bluetooth® pairing |
WO2019029826A1 (en) * | 2017-08-11 | 2019-02-14 | Sonova Ag | Communication device having a wireless interface |
CN111083802A (en) * | 2018-10-22 | 2020-04-28 | 三星电子株式会社 | Electronic device using bluetooth communication and method of operating the same |
US10719148B2 (en) | 2018-07-10 | 2020-07-21 | Microsoft Technology Licensing, Llc | Coupling a pen device to a companion device based on pen proximity |
WO2020251162A1 (en) * | 2019-06-11 | 2020-12-17 | Samsung Electronics Co., Ltd. | Electronic device and method for displaying inquiry list of external electronic device in bluetooth™ network environment |
US10885512B2 (en) * | 2016-08-19 | 2021-01-05 | Roche Diabetes Care, Inc. | Methods and systems for enhanced BLUETOOTH® bonding |
US11032686B2 (en) * | 2017-03-02 | 2021-06-08 | Blackberry Limited | Method and system for wakeup trigger by out-of-band communication |
US11516673B2 (en) * | 2017-05-22 | 2022-11-29 | Becton, Dickinson And Company | Systems, apparatuses and methods for secure wireless pairing between two devices using embedded out-of-band (OOB) key generation |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6080548B2 (en) * | 2012-12-28 | 2017-02-15 | キヤノン株式会社 | COMMUNICATION DEVICE, INFORMATION TERMINAL, ITS CONTROL METHOD, PROGRAM |
US9961669B2 (en) * | 2016-04-27 | 2018-05-01 | Qualcomm Incorporated | Near field communication (NFC) to bluetooth handover |
US11882434B2 (en) | 2020-07-09 | 2024-01-23 | Western Digital Technologies, Inc. | Method and device for covertly communicating state changes |
US11582607B2 (en) | 2020-07-10 | 2023-02-14 | Western Digital Technologies, Inc. | Wireless security protocol |
EP3968681A1 (en) | 2020-09-14 | 2022-03-16 | Bayerische Motoren Werke Aktiengesellschaft | A concept for a device with two communication devices |
EP3968669B1 (en) | 2020-09-14 | 2024-08-28 | Bayerische Motoren Werke Aktiengesellschaft | A concept for a device with two communication devices |
Citations (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4442504A (en) * | 1981-03-09 | 1984-04-10 | Allen-Bradley Company | Modular programmable controller |
US20020147816A1 (en) * | 2001-02-28 | 2002-10-10 | Hlasny Daryl J. | Pseudo-random dynamic scheduler for scheduling communication periods between electronic devices |
US20040185857A1 (en) * | 2001-08-15 | 2004-09-23 | Lee Wayne A. | Dual mode bluetooth/wireless device with power conservation features |
US20050208983A1 (en) * | 2002-06-10 | 2005-09-22 | Khoo Soon H | Compound portable computing device with dual portion variable keyboards coupled over a wireless link |
US20050251003A1 (en) * | 2001-07-17 | 2005-11-10 | Gmp/Wireless Medicine, Inc. | Disposable chest assembly |
US7031660B2 (en) * | 2001-04-04 | 2006-04-18 | Connectblue Ab | Method for transferring a device identifier block on a second communication link separated from the BLUETOOTH link |
US20070042807A1 (en) * | 2002-06-10 | 2007-02-22 | Khoo Soon H | Compound portable computing device with dual portion keyboards coupled over a transmission link |
US20080048986A1 (en) * | 2002-06-10 | 2008-02-28 | Khoo Soon H | Compound Computing Device with Dual Portion Keyboards Controlled by a Single Processing Element |
US20090156126A1 (en) * | 2006-04-03 | 2009-06-18 | Resonance Holdings Limited | Methods for determining proximity between radio frequency devices and controlling switches |
US20110077056A1 (en) * | 2009-09-25 | 2011-03-31 | Samsung Electronics Co., Ltd. | Method and apparatus for controlling of bluetooth headset |
US20110183614A1 (en) * | 2010-01-25 | 2011-07-28 | Kabushiki Kaisha Toshiba | Communication terminal |
US20110302653A1 (en) * | 2010-03-01 | 2011-12-08 | Silver Tail Systems, Inc. | System and Method for Network Security Including Detection of Attacks Through Partner Websites |
US20110304585A1 (en) * | 2009-10-09 | 2011-12-15 | Egalax_Empia Technology Inc. | Method and device for signal detection |
US20110312273A1 (en) * | 2008-01-22 | 2011-12-22 | Harris Technology, Llc | Cellular Phone Entry Techniques |
US20120124444A1 (en) * | 2010-11-12 | 2012-05-17 | Husted Paul J | Sleep Clock Error Recovery Scheme |
US20120133554A1 (en) * | 2001-07-18 | 2012-05-31 | Fast Location, Net, LLC | Method and system for processing positioning signals based on predetermined message data segment |
US20120246034A1 (en) * | 2011-03-21 | 2012-09-27 | Intralot S.A. Integrated Lottery Systems and Services | Ordering lottery tickets using machine-readable code images displayed on mobile devices |
US20130029596A1 (en) * | 2011-07-29 | 2013-01-31 | Motorola Solutions, Inc. | Pairing devices using data exchanged in an out-of-band channel |
US20130095757A1 (en) * | 2011-10-12 | 2013-04-18 | Research In Motion Limited | Methods and apparatus to control accessories |
US20140122908A1 (en) * | 2010-04-07 | 2014-05-01 | Apple Inc. | Hardware Automatic Performance State Transitions in System on Processor Sleep and Wake Events |
US20140169795A1 (en) * | 2009-01-30 | 2014-06-19 | Altorr Corporation | Smartphone control of electrical devices |
US20140365305A1 (en) * | 2013-06-10 | 2014-12-11 | International Business Machines Corporation | Providing geospatial-temporal next-best-action decisions |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4378643B2 (en) | 2005-08-01 | 2009-12-09 | ソニー株式会社 | COMMUNICATION SYSTEM, COMMUNICATION DEVICE, COMMUNICATION METHOD, AND PROGRAM |
US20080279137A1 (en) | 2007-05-10 | 2008-11-13 | Nokia Corporation | Discontinuous inquiry for wireless communication |
US7970350B2 (en) | 2007-10-31 | 2011-06-28 | Motorola Mobility, Inc. | Devices and methods for content sharing |
US20110028091A1 (en) | 2009-08-03 | 2011-02-03 | Motorola, Inc. | Method and system for near-field wireless device pairing |
-
2012
- 2012-03-14 US US13/419,987 patent/US8995908B2/en active Active
-
2013
- 2013-01-11 EP EP13740650.0A patent/EP2807875B1/en active Active
- 2013-01-11 WO PCT/CA2013/050016 patent/WO2013110185A1/en active Application Filing
- 2013-01-11 CA CA2862130A patent/CA2862130C/en active Active
Patent Citations (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4442504A (en) * | 1981-03-09 | 1984-04-10 | Allen-Bradley Company | Modular programmable controller |
US7475148B2 (en) * | 2001-02-28 | 2009-01-06 | Sharp Laboratories Of America, Inc. | Pseudo-random dynamic scheduler for scheduling communication periods between electronic devices |
US20020147816A1 (en) * | 2001-02-28 | 2002-10-10 | Hlasny Daryl J. | Pseudo-random dynamic scheduler for scheduling communication periods between electronic devices |
US7024482B2 (en) * | 2001-02-28 | 2006-04-04 | Sharp Laboratories Of America, Inc. | Pseudo-random dynamic scheduler for scheduling communication periods between electronic devices |
US20060129679A1 (en) * | 2001-02-28 | 2006-06-15 | Hlasny Daryl J | Pseudo-random dynamic scheduler for scheduling communication periods between electronic devices |
US7031660B2 (en) * | 2001-04-04 | 2006-04-18 | Connectblue Ab | Method for transferring a device identifier block on a second communication link separated from the BLUETOOTH link |
US20050251003A1 (en) * | 2001-07-17 | 2005-11-10 | Gmp/Wireless Medicine, Inc. | Disposable chest assembly |
US20120133554A1 (en) * | 2001-07-18 | 2012-05-31 | Fast Location, Net, LLC | Method and system for processing positioning signals based on predetermined message data segment |
US20040185857A1 (en) * | 2001-08-15 | 2004-09-23 | Lee Wayne A. | Dual mode bluetooth/wireless device with power conservation features |
US20070042807A1 (en) * | 2002-06-10 | 2007-02-22 | Khoo Soon H | Compound portable computing device with dual portion keyboards coupled over a transmission link |
US7366552B2 (en) * | 2002-06-10 | 2008-04-29 | Wireless 3G | Compound portable computing device with dual portion variable keyboards coupled over a wireless link |
US20080048986A1 (en) * | 2002-06-10 | 2008-02-28 | Khoo Soon H | Compound Computing Device with Dual Portion Keyboards Controlled by a Single Processing Element |
US7646316B2 (en) * | 2002-06-10 | 2010-01-12 | Wireless 3G | Compound portable computing device with dual portion keyboards coupled over a transmission link |
US20050208983A1 (en) * | 2002-06-10 | 2005-09-22 | Khoo Soon H | Compound portable computing device with dual portion variable keyboards coupled over a wireless link |
US20090156126A1 (en) * | 2006-04-03 | 2009-06-18 | Resonance Holdings Limited | Methods for determining proximity between radio frequency devices and controlling switches |
US8792826B2 (en) * | 2006-04-03 | 2014-07-29 | Eckey Corporation | Methods for determining proximity between radio frequency devices and controlling switches |
US8299895B2 (en) * | 2008-01-22 | 2012-10-30 | Harris Technology, Llc | Cellular phone entry techniques |
US20110312273A1 (en) * | 2008-01-22 | 2011-12-22 | Harris Technology, Llc | Cellular Phone Entry Techniques |
US20140169795A1 (en) * | 2009-01-30 | 2014-06-19 | Altorr Corporation | Smartphone control of electrical devices |
US20110077056A1 (en) * | 2009-09-25 | 2011-03-31 | Samsung Electronics Co., Ltd. | Method and apparatus for controlling of bluetooth headset |
US20110304585A1 (en) * | 2009-10-09 | 2011-12-15 | Egalax_Empia Technology Inc. | Method and device for signal detection |
US20110183614A1 (en) * | 2010-01-25 | 2011-07-28 | Kabushiki Kaisha Toshiba | Communication terminal |
US8756684B2 (en) * | 2010-03-01 | 2014-06-17 | Emc Corporation | System and method for network security including detection of attacks through partner websites |
US20110302653A1 (en) * | 2010-03-01 | 2011-12-08 | Silver Tail Systems, Inc. | System and Method for Network Security Including Detection of Attacks Through Partner Websites |
US20140122908A1 (en) * | 2010-04-07 | 2014-05-01 | Apple Inc. | Hardware Automatic Performance State Transitions in System on Processor Sleep and Wake Events |
US20120124444A1 (en) * | 2010-11-12 | 2012-05-17 | Husted Paul J | Sleep Clock Error Recovery Scheme |
US8504889B2 (en) * | 2010-11-12 | 2013-08-06 | Qualcomm Incorporated | Sleep clock error recovery scheme |
US20120246034A1 (en) * | 2011-03-21 | 2012-09-27 | Intralot S.A. Integrated Lottery Systems and Services | Ordering lottery tickets using machine-readable code images displayed on mobile devices |
US20130029596A1 (en) * | 2011-07-29 | 2013-01-31 | Motorola Solutions, Inc. | Pairing devices using data exchanged in an out-of-band channel |
US20130095757A1 (en) * | 2011-10-12 | 2013-04-18 | Research In Motion Limited | Methods and apparatus to control accessories |
US20140365305A1 (en) * | 2013-06-10 | 2014-12-11 | International Business Machines Corporation | Providing geospatial-temporal next-best-action decisions |
Non-Patent Citations (1)
Title |
---|
Johnson Consulting, "Bluetooth-An Overview", 17 April 2004, http://www.swedetrack.com/images/bluet14.htm. * |
Cited By (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9736680B2 (en) * | 2012-06-27 | 2017-08-15 | Google Inc. | Techniques for transferring a data payload utilizing near-field communication |
US20140006510A1 (en) * | 2012-06-27 | 2014-01-02 | Google Inc. | Techniques for transferring a data payload utilizing near-field communication |
US9326239B2 (en) * | 2012-09-28 | 2016-04-26 | Broadcom Corporation | Managing connectivity between wireless devices |
US20140094123A1 (en) * | 2012-09-28 | 2014-04-03 | Broadcom Corporation | Managing connectivity between wireless devices |
US20140104038A1 (en) * | 2012-10-16 | 2014-04-17 | Panasonic Corporation | Radio communication apparatus and radio communication system |
US9741213B2 (en) * | 2012-10-16 | 2017-08-22 | Panasonic Intellectual Property Management Co., Ltd. | Radio communication apparatus and radio communication system |
US20140133584A1 (en) * | 2012-11-12 | 2014-05-15 | Mediatek Inc. | Bluetooth device and related communications establishing method |
US9236911B2 (en) * | 2012-12-28 | 2016-01-12 | Intel Corporation | Secure transfer of whiteboard content |
US20140187152A1 (en) * | 2012-12-28 | 2014-07-03 | Erik J. Johnson | Secure transfer of whiteboard content |
EP2843580A1 (en) * | 2013-08-30 | 2015-03-04 | Arcadyan Technology Corporation | Method for updating network connection parameters |
US20150264732A1 (en) * | 2014-03-14 | 2015-09-17 | Sony Corporation | Electronic device, communication system, control method of electronic device, and program |
US10257870B2 (en) * | 2014-03-14 | 2019-04-09 | Sony Corporation | Pairing of electronic devices using near field wireless communication |
US20160057564A1 (en) * | 2014-08-25 | 2016-02-25 | Hyundai Motor Company | Bluetooth pairing method using a wired connection |
US20180049122A1 (en) * | 2015-02-26 | 2018-02-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Energy efficient ble mesh initialisation and operation |
US10624028B2 (en) * | 2015-02-26 | 2020-04-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Energy efficient BLE mesh initialisation and operation |
US10659589B2 (en) | 2015-05-15 | 2020-05-19 | Microsoft Technology Licensing, Llc | Automatic device pairing |
US9924019B2 (en) | 2015-05-15 | 2018-03-20 | Microsoft Technology Licensing, Llc | Automatic device pairing |
WO2017122429A1 (en) * | 2016-01-15 | 2017-07-20 | Casio Computer Co., Ltd. | Wireless communication method, wireless communication device, electronic watch, and non-transitory recording medium |
JP2017126951A (en) * | 2016-01-15 | 2017-07-20 | カシオ計算機株式会社 | Wireless communication method and program |
JP6132037B1 (en) * | 2016-01-15 | 2017-05-24 | カシオ計算機株式会社 | Wireless communication method and program |
US10512110B2 (en) | 2016-01-15 | 2019-12-17 | Casio Computer Co., Ltd. | Wireless communication method, wireless communication device, electronic watch, and non-transitory recording medium |
US10885512B2 (en) * | 2016-08-19 | 2021-01-05 | Roche Diabetes Care, Inc. | Methods and systems for enhanced BLUETOOTH® bonding |
WO2018112417A1 (en) * | 2016-12-16 | 2018-06-21 | Roche Diabetes Care, Inc. | Methods and systems for affirmation of a bluetooth® pairing |
US10721607B2 (en) | 2016-12-16 | 2020-07-21 | Roche Diabetes Care, Inc. | Methods and systems for affirmation of a BLUETOOTH® pairing |
US11032686B2 (en) * | 2017-03-02 | 2021-06-08 | Blackberry Limited | Method and system for wakeup trigger by out-of-band communication |
JP2017130971A (en) * | 2017-03-30 | 2017-07-27 | カシオ計算機株式会社 | Radio communication method and program |
US11516673B2 (en) * | 2017-05-22 | 2022-11-29 | Becton, Dickinson And Company | Systems, apparatuses and methods for secure wireless pairing between two devices using embedded out-of-band (OOB) key generation |
US11751061B2 (en) | 2017-05-22 | 2023-09-05 | Becton, Dickinson And Company | Systems, apparatuses and methods for secure wireless pairing between two devices using embedded out-of-band (OOB) key generation |
WO2019029826A1 (en) * | 2017-08-11 | 2019-02-14 | Sonova Ag | Communication device having a wireless interface |
US11363440B2 (en) * | 2017-08-11 | 2022-06-14 | Sonova Ag | Communication device having a wireless interface |
US10719148B2 (en) | 2018-07-10 | 2020-07-21 | Microsoft Technology Licensing, Llc | Coupling a pen device to a companion device based on pen proximity |
CN111083802A (en) * | 2018-10-22 | 2020-04-28 | 三星电子株式会社 | Electronic device using bluetooth communication and method of operating the same |
WO2020251162A1 (en) * | 2019-06-11 | 2020-12-17 | Samsung Electronics Co., Ltd. | Electronic device and method for displaying inquiry list of external electronic device in bluetooth™ network environment |
US11166141B2 (en) | 2019-06-11 | 2021-11-02 | Samsung Electronics Co., Ltd | Electronic device and method for displaying inquiry list of external electronic device in Bluetooth™ network environment |
Also Published As
Publication number | Publication date |
---|---|
WO2013110185A1 (en) | 2013-08-01 |
US8995908B2 (en) | 2015-03-31 |
CA2862130C (en) | 2021-02-23 |
CA2862130A1 (en) | 2013-08-01 |
EP2807875B1 (en) | 2019-05-22 |
EP2807875A4 (en) | 2016-03-30 |
EP2807875A1 (en) | 2014-12-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8995908B2 (en) | Mobile communications system providing enhanced out of band (OOB) bluetooth pairing and related methods | |
EP2434721B1 (en) | Communications system providing data transfer using selective wireless communications formats and related methods | |
US8798532B2 (en) | Mobile wireless communications device establishing wireless communication links based upon near field communication and related methods | |
US8774713B2 (en) | Mobile wireless communications device establishing wireless communication links based upon near field communication and related methods | |
US8688043B2 (en) | Mobile wireless communications device including NFC antenna scanning switch and related methods | |
US9002275B2 (en) | Mobile wireless communications device providing Bluetooth switchover features based upon near field communication (NFC) | |
US8989767B2 (en) | Wireless communication system with NFC-controlled access and related methods | |
US9143599B2 (en) | Communication system providing data transfer direction determination based upon motion and related methods | |
US20120220221A1 (en) | Communication system providing data transfer direction determination based upon orientation and related methods | |
US20130196595A1 (en) | Mobile communications device providing enhanced near field communication (nfc) mode switching features and related methods | |
EP2618497B1 (en) | Mobile wireless communications device including nfc antenna scanning switch and related methods | |
US9072052B2 (en) | Communication system providing context-based mobile wireless communications device power consumption management and related methods | |
CA2759759C (en) | Communication system providing data transfer direction determination based upon motion and related methods | |
CA2748692C (en) | Communication system providing context-based mobile wireless communications device power consumption management and related methods | |
EP2493233A1 (en) | Wireless communication system with nfc-controlled access and related methods | |
CA2769016C (en) | Communication system providing data transfer direction determination based upon orientation and related methods | |
EP2833606A1 (en) | Mobile wireless communications device providing bluetooth switchover features based upon near field communication (nfc) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: RESEARCH IN MOTION DEUTSCHLAND GMBH, GERMANY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BLAZEVIC, MARIN;NGUYEN, DONG DUC HAI;REEL/FRAME:028256/0482 Effective date: 20120416 Owner name: RESEARCH IN MOTION CORPORATION, DELAWARE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PEDRO, JUSTIN MANUEL;CHEN, XIANFENG;SIGNING DATES FROM 20120409 TO 20120425;REEL/FRAME:028256/0345 |
|
AS | Assignment |
Owner name: RESEARCH IN MOTION LIMITED, CANADA Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE PREVIOUSLY RECORDED ON REEL 028256 FRAME 0345. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT OF ASSIGNOR'S INTEREST;ASSIGNORS:PEDRO, JUSTIN MANUEL;CHEN, XIANFENG;SIGNING DATES FROM 20120409 TO 20120425;REEL/FRAME:028292/0750 |
|
AS | Assignment |
Owner name: RESEARCH IN MOTION LIMITED, ONTARIO Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RESEARCH IN MOTION DEUTSCHLAND GMBH;REEL/FRAME:029195/0151 Effective date: 20121025 |
|
AS | Assignment |
Owner name: BLACKBERRY LIMITED, ONTARIO Free format text: CHANGE OF NAME;ASSIGNOR:RESEARCH IN MOTION LIMITED;REEL/FRAME:033279/0940 Effective date: 20130709 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: IMAGINE COMMUNICATIONS CORP., TEXAS Free format text: CHANGE OF NAME;ASSIGNOR:HBC SOLUTIONS, INC.;REEL/FRAME:036360/0930 Effective date: 20140317 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
AS | Assignment |
Owner name: MALIKIE INNOVATIONS LIMITED, IRELAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BLACKBERRY LIMITED;REEL/FRAME:064104/0103 Effective date: 20230511 |