Source: https://patents.google.com/patent/US9635690B2/en
Timestamp: 2019-04-20 11:41:58+00:00

Document:
In an example embodiment, a method includes receiving, by an apparatus, one or more wireless discovery messages; determining, by the apparatus, whether a wireless device is in close proximity to the apparatus based on information obtained from the one or more received wireless discovery messages; exchanging, by the apparatus, messages with the wireless device in response to having determined that the wireless device is in close proximity to the apparatus; measuring, by the apparatus, signal strength of the exchanged messages while distance changes to the wireless device; and determining, by the apparatus, whether changes in the measured signal strength of the exchanged messages satisfy a predetermined behavior expected for signal strength as distance varies.
The technology field relates to wireless communication, more particularly to facilitating secure wireless connection establishment between closely situated apparatuses.
An example of a wireless short-range communication technology is Bluetooth™ communication protocol, which operates in the 2.4 GHz ISM band. Bluetooth™ is a short-range radio network, originally intended as a cable replacement. Bluetooth™ Technical Specifications are published by the Bluetooth™ SIG, Inc. Bluetooth™ Specification version 2.0+EDR, published Oct. 15, 2004 has the original functional characteristics of the first version Bluetooth™ Basic Rate (BR) and adds the Enhanced Data Rate (EDR) feature. Bluetooth™ Specification version 2.1+EDR, published Jul. 26, 2007 for Basic Rate/Enhanced Data Rate (BR/EDR), added definitions for new features: Encryption Pause Resume, Erroneous Data reporting, Extended Inquiry Response, Link Supervision Timeout Event, Packet Boundary Flag, Secure Simple Pairing, Sniff Subrating. Bluetooth™ Specification version 3.0+HS, published Apr. 21, 2009, updated the standard to integrate the Alternate MAC/PHY and Unicast Connectionless Data features.
The Bluetooth™ Core Specification, Version 4.0, Bluetooth™ SIG, Jun. 30, 2010 (incorporated herein by reference), includes the Extended Inquiry Response. An Extended Inquiry Response may be used to provide miscellaneous information during the inquiry response procedure. Data types may be defined for such things as local name and supported services, information that otherwise would have to be obtained by establishing a connection. A device that receives a local name and a list of supported services in an extended inquiry response does not have to connect to do a remote name request and a service discovery protocol (SDP) service search, thereby shortening the time to useful information.
Method, apparatus, and computer program product example embodiments enhance secure wireless communications.
determining, by the apparatus, whether changes in the measured signal strength of the exchanged messages satisfy a predetermined behavior expected for signal strength as distance varies.
wherein the exchanged messages are wireless discovery messages.
wherein the one or more wireless discovery messages are at least one of a Bluetooth inquiry response message or a Bluetooth Low Energy advertising message.
establishing, by the apparatus, a wireless connection with the wireless device in response to determining that the wireless device is in close proximity to the apparatus, wherein the messages are exchanged over the established wireless connection while the apparatus changes its distance from the wireless device and obtains signal information from the wireless connection messages usable for estimating the distance between the apparatus and the wireless device.
invoking, by the apparatus, a secure application in the apparatus if the changes in the measured signal strength of the exchanged messages satisfy the predetermined behavior expected for signal strength as distance varies.
wherein the information obtained from one or more wireless discovery messages and the signal information obtained from the exchanged messages, includes at least RSSI information corresponding the distance between the apparatus and the wireless device.
invoking, by the apparatus, a secure application in the apparatus if the changes in the obtained signal information satisfy the predetermined behavior expected for signal strength as distance varies.
increasing, by the apparatus, a quantity of the wireless messages exchanged with the wireless device to enhance the determining whether the predetermined behavior expected for signal strength as distance varies is satisfied, wherein the wireless connection messages are at least one of a Bluetooth basic rate/enhanced data rate data connection packet or a Bluetooth Low Energy data connection packet.
determine whether changes in the measured signal strength of the exchanged messages satisfy a predetermined behavior expected for signal strength as distance varies.
establish a wireless connection with the wireless device in response to determining that the wireless device is in close proximity to the apparatus, wherein the messages are exchanged over the established wireless connection while the apparatus changes its distance from the wireless device and obtains signal information from the wireless connection messages usable for estimating the distance between the apparatus and the wireless device.
invoke a secure application in the apparatus if the changes in the measured signal strength of the exchanged messages satisfy the predetermined behavior expected for signal strength as distance varies.
invoke a secure application in the apparatus if the changes in the obtained signal information satisfy the predetermined behavior expected for signal strength as distance varies.
increase a quantity of the wireless messages exchanged with the wireless device to enhance the determining whether the predetermined behavior expected for signal strength as distance varies is satisfied, wherein the wireless connection messages are at least one of a Bluetooth basic rate/enhanced data rate data connection packet or a Bluetooth Low Energy data connection packet.
code for determining, by the apparatus, whether changes in the measured signal strength of the exchanged messages satisfy a predetermined behavior expected for signal strength as distance varies.
code for invoking, by the apparatus, a secure application in the apparatus if the changes in the measured signal strength of the exchanged messages satisfy the predetermined behavior expected for signal strength as distance varies.
code for invoking, by the apparatus, a secure application in the apparatus if the changes in the obtained signal information satisfy the predetermined behavior expected for signal strength as distance varies.
code for increasing, by the apparatus, a quantity of the wireless messages exchanged with the wireless device to enhance the determining whether the predetermined behavior expected for signal strength as distance varies is satisfied, wherein the wireless connection messages are at least one of a Bluetooth basic rate/enhanced data rate data connection packet or a Bluetooth Low Energy data connection packet.
The resulting example embodiments enhance secure wireless communications.
FIG. 1A is an illustration of an example embodiment of a network in a device discovery phase, with a mobile wireless device detecting wireless device discovery messages received from a wireless service device, wherein the mobile wireless device is located at a first distance from the wireless service device, in accordance with at least one embodiment of the present invention.
FIG. 1B is an illustration of an example embodiment of the network of FIG. 1A, wherein the mobile wireless device has moved closer to the wireless service device, measures the RSSI of the wireless device discovery messages that it receives, and performs a touch-to-select event that initiates a communication connection to the wireless service device. The mobile wireless device commences exchanging wireless connection messages with the wireless service device and then requests a secure communications session with the wireless service device, in accordance with at least one embodiment of the present invention.
FIG. 1C is an illustration of an example embodiment of the network of FIG. 1B, wherein to insure that the wireless connection is actually the intended connection with the wireless service device and is not mistaken for an unintended connection with another wireless device, the mobile wireless displays a prompt to its user to move the device backward, away from the wireless service device. The mobile wireless device then measures and tracks the RSSI of the received wireless communications messages from the wireless service device, while the distance between the two devices increases. The mobile wireless device determines whether the estimated increasing distance to the wireless service device satisfies a predetermined behavior expected for signal strength as distance varies. The mobile wireless device will invoke and execute a secure application, if the estimated increasing distance to the wireless service device that it has measured and tracked, satisfies the predetermined behavior expected for signal strength as distance varies. In embodiments of the invention, the mobile wireless device and the wireless service device may increase the quantity of the wireless connection messages that they exchange, to increase the number of RSSI measurements, so as to enhance the determining whether the predetermined behavior expected for signal strength as distance varies is satisfied.
FIG. 1D is an illustration of an example embodiment of the network of FIG. 1C, wherein the wireless service device responds to the request for a secure communications session, by also measuring and tracking the RSSI of wireless communications messages that it receives from the mobile wireless device, while the distance between the two devices increases. The wireless service device also determines whether the estimated increasing distance between the devices satisfies the predetermined behavior expected for signal strength as distance varies. The wireless service device will invoke and execute a secure application, if the estimated increasing distance between the devices that it has measured and tracked, satisfies the predetermined behavior expected for signal strength as distance varies. In embodiments of the invention, the wireless service device and the mobile wireless device may increase the quantity of the wireless connection messages that they exchange, to increase the number of RSSI measurements, so as to enhance the determining by the wireless service device, whether the predetermined behavior expected for signal strength as distance varies is satisfied. The wireless service device and the mobile wireless device may signal to each other their respective determinations as to whether the predetermined behavior expected for signal strength as distance varies is satisfied.
FIG. 2 is a timing diagram illustrating the touch-to-select event that initiates a communication connection between the wireless devices, the request for a secure communications session, the measuring and tracking by the mobile wireless device of the RSSI of the received wireless communications messages while the distance between the two devices increases, and the increase in the quantity of the wireless connection messages that are exchanged, to increase the number of RSSI measurements, so as to enhance the determining whether the predetermined behavior expected for signal strength as distance varies is satisfied.
FIG. 3 is an example flow diagram for the mobile wireless device, in accordance with at least one embodiment of the present invention.
FIG. 4 is an example flow diagram for the wireless service device, in accordance with at least one embodiment of the present invention.
FIG. 5 is an example format diagram for a packet to indicate a required RSSI for service use, in accordance with at least one embodiment of the present invention.
FIG. 6A is an illustration of an example flow diagram of an example process in the mobile wireless device, in accordance with at least one embodiment of the present invention.
FIG. 6B is an illustration of an example flow diagram of an example process in the wireless service device, in accordance with at least one embodiment of the present invention.
FIG. 7 illustrates an example embodiment of the invention, wherein examples of removable storage media are shown, based on magnetic, electronic and/or optical technologies, such as magnetic disks, optical disks, semiconductor memory circuit devices and micro-SD memory cards (SD refers to the Secure Digital standard) for storing data and/or computer program code as an example computer program product, in accordance with at least one embodiment of the present invention.
Short-range communication technologies provide communication solutions appropriate for many data applications, without the cost, traffic and legislative concerns of longer-range communication technologies. Popular short-range communication technologies include Bluetooth basic rate/enhanced data rate (BR/EDR), Bluetooth Low Energy (LE), IEEE 802.11 wireless local area network (WLAN), Wireless Universal Serial Bus (WUSB), ZigBee (IEEE 802.15.4, IEEE 802.15.4a), and near field communication technologies, such as radio frequency identification (RFID) and near field communication (NFC) technology that enable contactless identification and interconnection of wireless devices. Bluetooth Technology provides an example of wireless short-range communication establishment.
A procedure for forming connections between Bluetooth™ devices is described in the Bluetooth™ Specification, Version 4, Jun. 30, 2010. The Bluetooth™ Baseband is the part of the Bluetooth™ system that implements the Media Access Control (MAC) and physical layer procedures to support the connection formation, exchange of data information streams, and ad hoc networking between Bluetooth™ devices. Connection formation may include inquiry, inquiry scanning, inquiry response, in addition to paging, page scanning, and page response procedures.
Inquiry is a procedure where a Bluetooth™ device transmits inquiry messages and listens for responses in order to discover the other Bluetooth™ devices that are within the coverage area and set discoverable. Bluetooth™ devices use the inquiry procedure to discover nearby devices, or to be discovered by devices in their locality. A Bluetooth™ device that tries to find other nearby devices is known as an inquiring device and actively sends inquiry requests. Bluetooth™ devices that are available to be found are known as discoverable devices, listen or scan for these inquiry requests, and send responses. The inquiry procedure uses dedicated physical channels for the inquiry requests and responses. The inquiry procedure does not make use of any of the architectural layers above the physical channel, although a transient physical link may be considered to be present during the exchange of inquiry and inquiry response information.
Bluetooth™ devices communicate with one another over 79 physical channels. An inquiring device wanting to discover other devices repetitively probes a first set of 16 frequencies, probing two frequencies every 1250 microseconds. It repeats this at least 256 times. Then, it repetitively probes a second set of 16 frequencies. The inquiring device will repeat entire cycle at least two times. Of the 79 radio carriers, 32 are considered wake-up carriers and the inquiring device broadcasts inquiry packets on these 32 carrier frequencies.
During the inquiry procedure, the inquiring device or master transmits inquiry messages with the general or dedicated inquiry access code. The timing for inquiry is the same as for paging. The identity or ID packet consists of the inquiry access code (IAC). It has a fixed length of 68 bits. The receiver uses a bit correlator to match the received packet to the known bit sequence of the ID packet. In order to discover other devices a device may enter inquiry substate. In this substate, it may repeatedly transmit the inquiry message (ID packet) at different hop frequencies. The inquiry hop sequence is derived from the Lower Address Part (LAP) of the General Inquiry Access Code (GIAC). Thus, even when dedicated inquiry access codes (DIACs) are used, the applied hopping sequence is generated from the GIAC LAP. A device that allows itself to be discovered, may regularly enter the inquiry scan substate to respond to inquiry messages. During the inquiry substate, the discovering device collects the Bluetooth™ device addresses of all devices that respond to the inquiry message. In addition, the discovering device may also collect extended information (e.g. local name and supported services) from devices that respond with an extended inquiry response packet. It may then, if desired, make a connection to any one of the discovered devices by means of the page procedure described below. The inquiry message broadcast by the source does not contain any information about the source. However, it may indicate which class of devices should respond. There is one general inquiry access code (GIAC) to inquire for any device, and 63 values have been reserved as dedicated inquiry access codes (DIAC) that only inquire for a certain type of device. The inquiry access codes are derived from reserved Bluetooth™ device addresses. There is only one DIAC defined in the Bluetooth™ Specification, and it is called the Limited Inquiry Access Code (LIAC). The LIAC is only intended to be used for limited time periods in scenarios where both devices have been explicitly caused to enter this state, usually by user action.
Inquiry scan is a procedure where a Bluetooth™ device listens for inquiry messages received on its inquiry scan physical channel. A device using one of its inquiry scan channels changes the inquiry channel every 1.28 s until it receives an inquiry message on the current channel from another Bluetooth™ device. This is identified by the appropriate inquiry access code. The inquiry scanning device will then follow the inquiry response procedure to return a response to the inquiring device. The inquiry scan substate is very similar to the page scan substate. However, instead of scanning for the device's device access code, the receiver may scan for the inquiry access code long enough to completely scan for 16 inquiry frequencies. The inquiry procedure uses 32 dedicated inquiry hop frequencies according to the inquiry hopping sequence. These frequencies are determined by the general inquiry address. The phase is determined by the native clock of the device carrying out the inquiry scan. Instead of, or in addition to, the general inquiry access code, the device may scan for one or more dedicated inquiry access codes. However, the scanning may follow the inquiry scan hopping sequence determined by the general inquiry address. The inquiry scan interval shall be less than or equal to 2.56 s.
An inquiry response packet (frequency hop synchronization (FHS)) is transmitted from the inquiry scanning device or slave to the master after the slave has received an inquiry message. This packet contains information necessary for the inquiring master to page the slave and follows 625 microseconds after the receipt of the inquiry message. The inquiry response packet is received by the master at the hop frequency when the inquiry message received by the slave was first in the master-to-slave slot. The slave response substate for inquiries differs completely from the slave response substate applied for pages. When the inquiry message is received in the inquiry scan substate, the recipient may return an inquiry response (FHS) packet containing the recipient's device address (BD_ADDR) and other parameters. If the recipient has non-zero extended inquiry response data to send, it may return an extended inquiry response packet after the FHS packet. On the first inquiry message received in the inquiry scan substate the slave may enter the inquiry response substate. If the slave has non-zero extended inquiry response data to send it may return an FHS packet, with the extended inquiry response bit set to one, to the master 625 microseconds after the inquiry message was received. It may then return an extended inquiry response packet 1250 microseconds after the start of the FHS packet. If the slave's extended inquiry response data is all zeroes the slave may only return an FHS packet with the extended inquiry response bit set to zero.
A contention problem could arise when several devices are in proximity to the inquiring device or master and all respond to an inquiry message at the same time. However, because every device has a free running clock it is highly unlikely that they all use the same phase of the inquiry hopping sequence. In order to avoid repeated collisions between devices that wake up in the same inquiry hop channel simultaneously, a device will back-off for a random period of time. Thus, if the device receives an inquiry message and returns an FHS packet, it will generate a random number, RAND, between 0 and MAX_RAND. For scanning intervals greater than or equal to 1.28 seconds MAX_RAND will be 1023, however, for scanning intervals less than 1.28 s MAX_RAND may be as small as 127. A profile that uses a DIAC may choose to use a smaller MAX_RAND than 1023 even when the scanning interval is greater than or equal to 1.28 s. The slave will return to the CONNECTION or STANDBY state for the duration of at least RAND time slots. Before returning to the CONNECTION and STANDBY state, the device may go through the page scan substate. After at least RAND slots, the device will add an offset of 1 to the phase in the inquiry hop sequence (the phase has a 1.28 second resolution) and return to the inquiry scan substate again. If the slave is triggered again, it will repeat the procedure using a new RAND. The offset to the clock accumulates each time an FHS packet is returned. During a period when the inquiry device is broadcasting inquiry packets, a slave may respond multiple times, but on different frequencies and at different times. Reserved synchronous slots should have priority over response packets; that is, if a response packet overlaps with a reserved synchronous slot, it will not be sent, but the next inquiry message is awaited. If a device has extended inquiry response data to send, but the extended inquiry response packet overlaps with a reserved synchronous slot, the FHS packet may be sent with the EIR bit set to zero.
In step 1, the master transmits an inquiry message using the inquiry access code and its own clock.
In step 2, the slave responds with the FHS packet containing the slave's Bluetooth™ device address, native clock and other slave information. This FHS packet is returned at times that tend to be random. If the slave has non-zero extended inquiry response data to send it will return an FHS packet with the EIR bit set to one to the master 625 us after the inquiry message was received. It then returns an extended inquiry response packet 1250 us after the start of the FHS packet. FHS is always returned 625 us after inquiry message was received. But, consecutive FHS packets are returned according to this random process. The FHS packet is not acknowledged in the inquiry routine, but it is retransmitted at other times and frequencies as long as the master is probing with inquiry messages.
In step 3, if the slave has non-zero extended inquiry response data, it sends an extended inquiry response packet to the master.
The retransmission of the inquiry response can be received by the inquiring devices within roughly 80 or 640 ms depending on inquiry scan interval of the discovered device. The random backoff for devices using scanning interval <1.28 s is from 0 to 79,375 ms and for other devices from 0 to 639,375 ms. The device using the default inquiry interval is using the latter value range.
In order to collect responses from all devices in the range in an error-free environment, the inquiry substate may have to last for 10.24 s unless the inquirer collects enough responses and aborts the inquiry substate earlier. If desired, the inquirer may also prolong the inquiry substate to increase the probability of receiving all responses in an error-prone environment. In consequence of long inquiry state compared to relatively short backoff times, multiple responses may be received from the single device.
An Extended Inquiry Response may be used to provide miscellaneous information during the inquiry response procedure. Data types are defined for such things as local name and supported services, information that otherwise would have to be obtained by establishing a connection. A device that receives a local name and a list of supported services in an extended inquiry response does not have to connect to do a remote name request and a service discovery protocol (SDP) service search, thereby shortening the time to useful information. If the slave transmits an extended inquiry response packet, it is transmitted 1250 microseconds after the start of the inquiry response packet. The extended inquiry response packet is received by the master at the hop frequency when the inquiry message received by the slave was first in the master-to-slave slot. The extended inquiry response packet is an Asynchronous Connection-oriented Logical transport (ACL) packet with type DM1, DM3, DM5, DH1, DH3 or DH5. To minimize interference it is recommended to use the shortest packet that is capable of containing the data. The packet is sent on the same frequency as the FHS packet, 1250 microseconds after the start of the FHS packet. In the packet header, LT_ADDR may be set to zero. TYPE may be one of DM1, DM3, DM5, DH1, DH3 or DH5. FLOW, ARQN and SEQN may all be set to zero and ignored during receipt. The HEC LFSR may be initialized with the same DCI (default check initialization) as for the FHS packet. In the payload header, LLID may contain the value 10 (start of an L2CAP message or no fragmentation). FLOW may be set to zero and ignored upon receipt. The length of the payload body (LENGTH) may be smaller than or equal to 240 bytes. The CRC LFSR may be initialized with the same DCI as for the FHS packet. The data whitening LFSR may be initialized with the same value as for the FHS packet. The length of the payload body (LENGTH) may be smaller than or equal to 240 bytes. The CRC LFSR may be initialized with the same DCI as for the FHS packet. The data whitening LFSR may be initialized with the same value as for the FHS packet. The payload data has two parts, a significant part followed by a non-significant part. The significant part contains a sequence of data structures. The non-significant part contains all zero octets. The baseband may not change any octets in the significant part. When transmitting data, the non-significant part octets may be omitted from the payload. A device may store a single extended inquiry response packet. This packet may be used with all IACs.
Page is the initial phase of the connection procedure where a device transmits a train of page messages until a response is received from the target device, stopped by the host or a timeout occurs. Page scan is a procedure where a device listens for page messages received on its page scan physical channel. In forming a connection, the paging device will become the master and the page scan device will become the slave in a piconet. Initially, after the slave has received an inquiry message, an inquiry response packet is transmitted from the slave to the master. The inquiry response packet sent from the slave contains information necessary for the inquiring master to page the slave, such as Bluetooth™ device address of the slave device. The necessary information may be received by other means, such as Out-Of-Band pairing. Also the page is not always preceded with inquiry, because the address may be known beforehand (for example saved from previous connections). In the paging procedure, one the Bluetooth™ device that will become the master carries out a page procedure by transmitting page messages in connection request packets to the specified Bluetooth™ slave device that carries out a page scanning procedure to listen for connection request packets from the paging device. A connectable Bluetooth™ device listens for a page request on its page scan channel and, once received, enters into a sequence of exchanges with the paging device. In order for a device to connect to another device, it performs frequency hopping all page scan channel frequencies, sending a page request on each frequency and listening for a response. The page scan channel uses an access code derived from the scanning device's Bluetooth™ device address BD_ADDR to identify communications on the channel. The page scan channel uses a slower hopping rate than the hop rate of the paging device, using the estimated Bluetooth™ device clock of the scanning device as an input. A device listening on its page scan channel remains passive until it receives a page request from another Bluetooth™ device, identified by the page scan channel access code. The two devices will then follow the page procedure to form a connection where the paging device is the master and the page scan device is the slave in a piconet. In order for a paging device to connect to another Bluetooth™ device, it uses the page scan channel of the target device in order to send page requests. If the paging device does not know the phase of the target device's page scan channel, it does not know the current hop frequency of the target device. Therefore, the paging device transmits page requests on each of the page scan hop frequencies and listens for a page response. This is done at a faster hop rate, allowing the paging device to cover all page scan frequencies in a short period of time. The paging device may have some knowledge of the target device's Bluetooth™ clock, such as indicated during a previous inquiry transaction between the two devices, and may be able to predict the phase of the target device's page scan channel. It may use this information to optimize the synchronization of the paging and page scanning process and speed up the formation of the connection.
During Bluetooth discovery, before a connection is created, the RSSI is measured from Inquiry Response (FHS) packets when it is received by an inquiring device if enabled by the host.
When the controller receives an Inquiry Response (FHS) without following an Extended Inquiry Response, an HCI Inquiry Result with RSSI event is sent by the controller to the host application, which indicates that a remote Bluetooth device has responded during the current Inquiry process. This event will be sent from the Controller to the Host typically as soon as an Inquiry Response from a remote device is received. The RSSI parameter is measured during the FHS packet returned by each responding slave.
When the controller receives an Inquiry Response (FHS) following with an Extended Inquiry Response, an HCI Extended Inquiry Result event is sent by the controller to the host application, which indicates that a remote Bluetooth device has responded during the current inquiry process with extended inquiry response data. This event will be sent from the Controller to the Host upon reception of an Extended Inquiry Response from a remote device. One single Extended Inquiry Response is returned per event. This event contains RSSI and inquiry response data for the remote device that responded to the latest inquiry. The RSSI parameter is measured during the FHS packet returned by each responding slave.
After the discovery phase is completed, once a Bluetooth device is connected to another Bluetooth device, the received signal strength indication (RSSI) may be used by a receiving device to monitor the received power level of the data communication packets received over the connection. The RSSI value is calculated from received packet in the Bluetooth physical layer, and may be read by the host application for example through the host controller interface (HCI) Read RSSI command, for example once per second.
For example, if Tx Power Level=+4 (dBm) and the RSSI on the inquiry response packet is −60 (dBm) then the total pathloss is +4−(−60)=+64 dB. If a second inquiry response packet were received at −40 dBm with a Tx Power Level data=+15 dBm the resulting pathloss would be +55 dB. An application may use these pathloss values to choose which device it thinks might be closer (the one with the lower pathloss value).
Unfortunately, due to fading and varying antenna, circuit, and chip characteristics, these resulting pathloss values may have some uncertainty. Some of the uncertainty (for example, due to fading) may be able to be alleviated if multiple inquiry response packets are received from the same device.
The host controller interface (HCI) is described in the Bluetooth™ Core Specification. The Host will receive asynchronous notifications of HCI events from Host Controller Transport Layer. HCI events are used for notifying the Host when something occurs. When the Host discovers that an event has occurred, it will then parse the received event packet to determine which event occurred. The commands and events are sent between the Host and the Controller. These are grouped into logical groups by function.
The HCI Inquiry command will cause the Bluetooth Controller to enter Inquiry Mode to transmit inquiry packets used to discover other nearby Bluetooth devices.
The inquiry result event indicates that a remote device has responded with an inquiry response (IR), i.e. with an FHS packet, during the current inquiry process. This event will be sent from the Bluetooth™ Controller to the Host as soon as an Inquiry Response from a remote device is received. The event parameters in the HCI inquiry result event include BD_ADDR and Class_of_Device of the remote responding device and Clock_Offset OFFSET(A,B) between the responding device and the inquiring device.
The Inquiry Result with RSSI event indicates that a remote Bluetooth device has responded with an inquiry response (FHS) packet during the current Inquiry process. The event reported to the host includes the BD_ADDR address for the device that responded, the Class of Device for the device, the clock offset between the responding device and the receiving device, and the measured RSSI of the received inquiry response packet in units of dBm. This is similar to the inquiry result event, but it includes the RSSI value calculated by the controller.
The extended inquiry result event indicates that another Bluetooth™ device has responded during the current inquiry process with extended inquiry response data. Data received in this event will be sent from the device's Controller to the Host upon reception of an EIR from a remote device. One single extended inquiry response is returned per event. The event reported to the host includes the received signal strength indication (RSSI) measurement and inquiry response data for the device that responded to the latest inquiry. The RSSI parameter is measured during the FHS packet returned by each responding device. If an extended inquiry response packet from the same remote device is correctly received in a later response, another event is generated. The Extended_Inquiry_Response data fields are not interpreted by the controller. The standard HCI Extended Inquiry Result Event logic performs the HCI extended inquiry result event procedure to extract the data from the received extended inquiry response packet and to send this data to the host application. The received EIR data extracted from the packet may be passed unaltered to the host application.
This command will read the inquiry response Transmit Power level data, expressed in a field of the EIR packet, indicating the power that was used to transmit the FHS and EIR data packets during the discovery phase.
The Write Extended Inquiry Response command writes the extended inquiry response to be sent to an inquiring device during the extended inquiry response procedure. The write extended inquiry response command will write the data that the device's host wishes to send in the extended inquiry response packet during inquiry response. The FEC_Required command parameter states if forward error correction (FEC) encoding is required. The initial value of the inquiry response data is all zero octets. The controller does not interpret the extended inquiry response data, but passes it on to the baseband medium access control and physical radio for transmission in an EIR packet.
The Write Inquiry Transmit Power Level command is used by the transmitting device to write the transmit power level used to transmit the inquiry data packets.
The RSSI parameter in the Read RSSI command is a signed 8-bit value, and is interpreted as an indication of arriving signal strength at the antenna measured in dBm. This command reads the Received Signal Strength Indication (RSSI) value from the Controller. For a Basic Rate/Enhanced Data Rate (BR/EDR) Controller, a Connection_Handle is used as the Handle command parameter and return parameter. The RSSI parameter returns the difference between the measured Received Signal Strength Indication (RSSI) and the limits of the Golden Receive Power Range for a Connection Handle to another BR/EDR Controller. The Connection_Handle must be a Connection_Handle for an ACL connection. Any positive RSSI value returned by the Controller indicates how many dB the RSSI is above the upper limit, any negative value indicates how many dB the RSSI is below the lower limit. The value zero indicates that the RSSI is inside the 20 dB-wide Golden Receive Power Range. The accuracy of the dB values will depend on the Bluetooth hardware. The only requirements for the hardware are that the BR/EDR Controller is able to tell whether the RSSI is inside, above or below the Golden Device Power Range. The RSSI measurement compares the received signal power with two threshold levels, which define the Golden Receive Power Range. The lower threshold level corresponds to a received power between −56 dBm and 6 dB above the actual sensitivity of the receiver. The upper threshold level is 20 dB above the lower threshold level to an accuracy of +/−6 dB.
The Read Transmit Power Level command will read the values for the Transmit Power Level parameter for the specified Connection_Handle for data communication packets during the connection phase, in a range of −30 to +20 dBm.
The Bluetooth Touch-to-select feature employs Received Signal Strength Indication (RSSI) information calculated from the FHS packet, which is used in determining that an inquiry scanning device is within “touch range”, i.e. proximate or in close proximity of the inquiring device, and when a threshold for that close proximity is met. This may provide an “intent to share” or “touch to connect” feature.
The inquiring device may measure the signal strength (e.g., RSSI) of each response message from an inquiry scanning device, which may be used in ordering the responding devices. In this manner, the inquiry scanning device with the highest measured signal strength is listed first (e.g., wherein the measured signal strength may correlate to the distance between the inquiring device and the responding inquiry scanning device).
An inquiry scanning device receiving inquiry packets from an inquiring device may respond by transmitting an inquiry response FHS packet or an FHS packet followed by an EIR packet. The host in the inquiring device may recognize events triggered by the responses. The reported events may include RSSI measurement values made by the inquiring device on the received FHS packets. From the RSSI values, the host in the inquiring device may detect when an inquiry scanning device is most likely within “touching range”, that is within a distance from the inquiring device that indicates touching-related operations may be executed.
It may also be possible to determine when an inquiry scanning device is moving closer to an inquiring device. The Bluetooth controller in the inquiring device may report the receipt of FHS and/or EIR inquiry responses to its host software stack as an HCI Inquiry Event that may contain the measurement of the RSSI performed on the received response. In instances where EIR responses are received, the Bluetooth controller in the inquiring device may report each received EIR as an HCI Extended Inquiry Result Event. When an inquiry scanning device moves closer to an inquiring device, the Bluetooth controller in the inquiring device may report an RSSI for each inquiry response, thereby enabling the inquiring device to track the changing RSSI levels of the scanning device and thus its relative movement. When the measured RSSI satisfies predetermined response criteria (e.g., including the RSSI being measured to be at or above a predetermined level), the corresponding scanning device may be selected for touch-related operations (e.g., expedited connection establishment).
The Bluetooth controller in an inquiring device reports the receipt of inquiry responses to its host, which also has Touch selection software running Typical response criteria may include RSSI values measured on the responses, being sensed above certain fixed threshold value, such as −30 dBm. Sensing a response packet having an RSSI of −30 dBm will then cause the Touch selection software in the inquiring device to trigger device selection, while an RSSI of −31 dBm will not. It may also be possible that responding inquiry scanning devices may send Tx power information in EIR packet, since this is an existing feature in the Bluetooth specification v4.0. In instances where Tx power information about the inquiry scanning device is available in the EIR packet, the predetermined response criteria may include an adjustable RSSI threshold value that accounts for variations in the Tx power. For example, the threshold value may be set at 30 dBm below the EIR Tx power, so that if the Tx power level in an FHS packet is +20 dBm then the threshold value that will trigger selection may be the FHS packet being measured at −10 dBm, or 30 dBm below of Tx power level. Secondly, to ensure that devices are maintained in close proximity, the predetermined response criteria may require that more than one EIR must have a sensed RSSI at or above a threshold value. In addition different thresholds may be used for different phases, for example, first the threshold value may be set above −45 dBm to select one or more candidate devices and then a second, more decisive threshold value may be set above −30 dBm.
The detected RSSI may also be a function of:  antenna location of the inquiry scanning device sending the signal and  antenna location of the inquiring device sensing the signal. The results may be improved if the antennas were brought into close proximity, which may require moving away from obstructions and changing the orientation of one or both devices.
The Bluetooth™ Core Specification, Version 4.0 includes the Bluetooth LE protocol for products that require lower power consumption, lower complexity, and lower cost than would be possible using the BR/EDR protocol. Bluetooth LE is designed for applications requiring lower data rates and shorter duty cycles, with a very-low power idle mode, a simple device discovery, and short data packets. Bluetooth LE devices may employ a star topology, where one device serves as a master for a plurality of slave devices, the master dictating connection timing by establishing the start time of the first connection event and the slave devices transmitting packets only to the master upon receiving a packet from the master. According to Bluetooth LE communication protocol all connections are point-to-point connections between two devices (the master and the slave).
The Bluetooth LE radio operates in the unlicensed 2.4 GHz ISM band, in the same manner as does the Basic Rate/Enhanced Data Rate (BR/EDR) radio. Bluetooth LE supports very short data packets, from 10 octets to a maximum of 47 octets, giving it a low duty cycle. Bluetooth LE employs a frequency hopping transceiver with many frequency hopping spread spectrum (FHSS) carriers, with a bit rate of 1 Megabit per second (Mb/s).
In the Bluetooth™ Core Specification, Version 4.0, there are four advertising event types: connectable undirected advertising (ADV_IND), connectable directed advertising (ADV_DIRECT_IND), scannable undirected advertising (ADV_SCAN_IND), and non-connectable undirected advertising (ADV_NONCONN_IND). At the start of each advertising event, the advertiser sends an advertising packet corresponding to the advertising event type. The header of the advertising channel packet identifies the packet type in a four-bit PDU Type field encoding. There are seven values currently assigned to the four-bit PDU Type field, ranging from 0000 to 0110, with the values 0111 to 1111 being reserved for future use.
The initiator device that receives the advertising packet, may make a connect request (CONNECT_REQ) to the advertiser device on the same advertising PHY channel. The CONNECT_REQ request includes fields for access address AA, CRC, WinSize, WinOffset, Interval, Latency, Timeout, ChannelMap, Hop count, and sleep clock accuracy SCA. The four-bit PDU Type field in the header of the CONNECT_REQ advertising channel packet, is 0101. When the advertiser device accepts the CONNECT_REQ request, a point-to-point connection results between the initiator device that becomes the master device, and the advertiser device that becomes the slave device in a piconet. The master and the slave devices know at what time and in which frequency the connection is in operation. The data channel changes between every connection event and the start of connection events are spaced regularly with the connection interval that is provided in the CONNECT_REQ packet.
In a non-connectable undirected event type advertising channel packet, ADV_NONCONN_IND, a scanner device is allowed to receive information in the advertising channel packet, but scanner/initiator devices are not allowed to transmit anything in the advertising channels upon receiving the ADV_NONCONN_IND advertising channel packets. When the non-connectable undirected event type is used, non-connectable advertising indications ADV_NONCONN_IND packets are sent by the Link Layer. The non-connectable undirected event type allows a scanner to receive information contained in the ADV_NONCONN_IND from the advertiser. The advertiser may either move to the next used advertising channel index or close the advertising event after each ADV_NONCONN_IND that is sent. The four-bit PDU Type field in the header of the ADV_NONCONN_IND advertising channel packet, is 0010.
In the Bluetooth™ Core Specification, Version 4.0, if the advertiser is using a connectable advertising event, an initiator may make a connection request using the same advertising PHY channel on which it received the connectable advertising packet. The advertising event is ended and connection events begin if the advertiser receives and accepts the request for a connection to be initiated. Once a connection is established, the initiator becomes the master device in a piconet and the advertising device becomes the slave device. Within a connection event, the master and slave alternate sending data packets using the same data PHY channel.
If any advertising PDU is received by an initiator/scanner, it means the initiator/scanner successfully discovers the advertising device. For the initiator, it can directly send back a “CONN_REQ” to establish a connection with that advertiser. For a scanner, it can send out a “SCAN_REQ” to ask for more information from that advertiser.
Touch-to-Select (T2S) is a technology where the received signal strength is utilized as an indicator to trigger actions between the devices in proximity. The technology enables devices that may have not been previously paired to start interacting after these devices have been taken within the a priori decided distance. The challenge with the signal strength based indication of the proximity is the error proneness of the process. This is especially crucial in applications such as payments or personal identification requiring high reliability.
Touch-to-Select (T2S) utilizes device proximity as a trigger for action. The proximity is measured utilizing received signal strengths. The challenge is that since the accurate propagation conditions between the transmitter and receiver cannot be estimated and the transmission power is not always known, the process is vulnerable to attacks. One example of such attack is transmitter having much higher transmission power level than typical transmitter or one that is indicating its transmission power lower than it actually is. This will cause error in link loss calculation and thus the set RSSI threshold to be exceeded, even if the actual transmitter is not within proximity of the receiver. Equally, if the user holds her hand on top of the user's device antenna that performs the signal strength measurement, the received signal strength is significantly reduced and the proximity may not be detected at all, due to the signal strength loss caused by the hand. The same applies also for covering the transmitting antenna by hand or any other obstacles.
In accordance with an example embodiment of the invention, the signal propagation characteristics are utilized as part of the Touch-to-Select (T2S) event, to remove errors due to objects blocking the antennas and/or accurately detect the proximity to the transmitter. This is achieved by taking several RSSI measurements at different distances and by comparing the results with a propagation model based signal strength estimates.
In accordance with an example embodiment of the invention, when the user's device is about to perform the Touch-to-Select (T2S) based interaction requiring additional security, the system behaves as with normal Touch-to-Select (T2S) until the signal strength threshold triggering Touch-to-Select (T2S) is achieved. Once this happens, either the user's device or the other device may indicate that it requests secure action. For example, when initiating or receiving a secure payment request, the device may increase the amount of transmissions (or increase the probability for more transmissions) to increase the number of following RSSI measurements. Next, the device having any form of capability to guide the user, either by voice prompts, display, lights, or the like, prompts the user to move one of the devices either towards or further from the other.
While moving, the RSSI values are measured continuously and monitored against the expected signal strength values. The comparison may be based either on absolute values, or relative values, taking into account the potential fixed attenuation caused e.g. by user's hand. When the desired RSSI behavior is detected, the successful detection is indicated both to the user and over the radio link to the peer device.
The signal strength in open, free space propagation environment attenuates along the distance based on free space loss. The loss can calculated based on Eq. 1.
Based on this, the device may calculate the estimates for the received signal strengths at different distances and power levels, as a signal strength map that is stored in the device. The signal strength map serves as a reference of the predetermined behavior expected for signal strength as distance varies. For example, if the distance between the devices increases, the predetermined behavior is that the measured signal strength values are expected to decrease.
For example, if the detected proximity of an intended device is 10 cm based on the RSSI measurement at one distance, it is possible that a masquerading device transmitting with higher power levels could erroneously be interpreted to be the intended device in proximity. The intended device with a 10 dBm output power level produces a similar RSSI value at a 10 cm distance as does the masquerading device with a 30 dBm output power level at a 1 m distance. With only a single measurement of the RSSI, it is impossible to detect the difference between a connection to the intended device and a connection to the masquerading device.
However, if the device performing the measurement is moved either closer or further away from the intended device, and the RSSI measurement is repeated while the distance changes between the devices, the identity of the connected device becomes definite. For example, if the RSSI measurement is repeated at a 30 cm distance, the 10 dBm transmitter provides a signal strength of −19.8 dBm and the 30 dBm transmitter (actually being now anywhere between 80 cm and 1.2 meters away) provides RSSI values within range [−8 . . . −11.8] dBm.
In accordance with an example embodiment of the invention, repeating the RSSI measurement at different distances while being in proximity, provides the information required to distinguish between the intended and the masquerading devices. In addition, if there is a fixed attenuation (such as the user's hand blocking the antenna), the signal strength curves are merely shifted down by the amount of the attenuation, but the difference of the signal strengths between the measurements performed at the different distances remains constant.
In accordance with an example embodiment of the invention, the specific nature of the signal propagation loss in “near” field is utilized, where the signal strength decays very rapidly as a function of the increased distance.
The distance between the devices is estimated using the measured signal strength or RSSI. For example, the user's device may determine whether the measured RSSI of the exchanged messages satisfies a predetermined behavior, wherein changes in the RSSI follow the stored “signal strength map” of a proximate device when it is moved). It is true that the variables of the “signal strength map” are RSSI and distance, but somehow the claim is not very clear.
In accordance with an example embodiment of the invention, when user is about to perform device pairing utilizing Touch-to-Select (T2S) based interaction, the system behaves as with standard Touch-to-Select (T2S) until the signal strength threshold triggering Touch-to-Select (T2S) is achieved. Once this happens, either of the devices can indicate that they request secure action. For example when initiating or receiving this secure payment request, the device may increase the amount of transmissions (or increase the probability for more transmissions) to increase the number of following RSSI measurements. Next, the device having any form of capability to guide the user, either by voice commands, display, lights, or similar, instructs the user to move one of the devices either towards or further away. While moving, the RSSI values are measured continuously and monitored against the expected signal strength values. The comparison can be based either on absolute values, or relative values taking into account the potential fixed attenuation caused e.g. by user's hand. When the desired RSSI behavior is detected, the successful detection is indicated both to the user and over the radio link to the peer device. In case the detection is not successful, the system may ask the user to repeat the process.
Similarly to the moving of the device towards or away from each other, the interaction can be any other known distance manipulation (like rotating the device, flipping it . . . ).
FIG. 1A is an illustration of an example embodiment of a network in a device discovery phase, with a mobile wireless device 100 detecting wireless device discovery messages 150 received from a wireless service device 102, wherein the mobile wireless device 100 is located at a first distance X1 from the wireless service device 102, in accordance with at least one embodiment of the present invention.
The mobile wireless device 100 is scanning for device discovery messages 150 associated with the presence of the wireless service device 102. In an example embodiment of the invention, the wireless device discovery messages 150 may be a Bluetooth™ inquiry response message transmitted by the wireless service device 102 in response to an inquiry message transmitted by the mobile wireless device 100. In an example embodiment of the invention, the wireless device discovery messages 150 may be a Bluetooth™ Low Energy advertising message transmitted by the wireless service device 102.
 instruct user to move toward device 102 to perform Touch-to-Select.
In example embodiments of the invention, the mobile wireless device 100 and the wireless service device 102 may include a processor 122 that includes from one to many central processing units (CPUs) 124 and/or 125, a random access memory (RAM) 126, a read only memory (ROM) 127, and interface circuits 128 to interface with one or more radio transceivers 116, antenna 132 170, and battery or house power sources. A smart phone may include a keypad, display 144, etc. The RAM and ROM can be removable memory devices such as smart cards, SIMs, WIMs, semiconductor memories such as RAM, ROM, PROMS, flash memory devices, etc., as shown in FIG. 7.
In an example embodiment of the invention, the Bluetooth mobile wireless device 100 and the wireless service device 102 may include control stack 115 that includes a host controller interface (HCI) 111 that provides a command interface between the host respective application 110, 110A in the device and the link layer or MAC 114. The control stack 115, also referred to as the controller, to enables access to hardware status and control registers of the Bluetooth radio 116. The host controller interface (HCI) is described in the Bluetooth™ Core Specification. The Host application 110, 110A will receive asynchronous notifications of HCI events from HCI 111. HCI events are used for notifying the Host application 110, 110A when something occurs. When the Host application discovers that an event has occurred, it will then parse the received event packet to determine which event occurred. The commands and events are sent between the Host application 110, 110A and the radio 116. The HCI 111 provides a command interface between the host application 110, 110A in a device and the Bluetooth link layer or MAC 114, provides access to hardware status and control registers of the radio 116, and provides a uniform method of accessing the Bluetooth baseband capabilities. In an example embodiment of the invention, the MAC 114 may be the Bluetooth basic rate/enhanced data rate (BR/EDR) protocol, the Bluetooth Low Energy (LE) protocol, or both protocols.
In an example embodiment of the invention, the wireless service device 102 outputs Bluetooth LE advertising packets on the advertising PHY channels in advertising events. During Bluetooth LE transmission, the RF signal is transmitted by the antenna 170.
In another example embodiment of the invention, the wireless service device 102 outputs Bluetooth protocol data units (PDU) or packets, such as inquiry response packets and extended inquiry response (EIR) packets 150, for Bluetooth transmission. During Bluetooth transmission, the RF signal is transmitted by the antenna 170.
In an example embodiment of the invention, the mobile wireless device 100 may be, for example, a miniature device such as a key fob, smart card, jewelry, or the like. In an example embodiment of the invention, the mobile wireless device 100 may be, for example, a relatively larger cell phone, smart phone, flip-phone, PDA, graphic pad. The mobile wireless device 100 may also be in an automobile or other vehicle.
FIG. 1B is an illustration of an example embodiment of the network of FIG. 1A, wherein the mobile wireless device 100 measures the RSSI of the wireless device discovery messages 150 that it receives. The mobile wireless device 100 has moved to within a distance X2 of the wireless service device 102 and performs a touch-to-select event 20 that initiates a communication connection to the wireless service device 102. The mobile wireless device 100 commences exchanging wireless connection messages 176A and 176B, shown in FIG. 1C, with the wireless service device 102. The mobile wireless device 100 then requests a secure communications session with the wireless service device 102, in accordance with at least one embodiment of the present invention.
FIG. 1C is an illustration of an example embodiment of the network of FIG. 1B, wherein so as to insure that the wireless connection is actually the intended connection with the wireless service device 102 and is not mistaken for an unintended connection with another wireless device, the mobile wireless device 100 displays a prompt to its user to move the device 100 backward, away from the wireless service device 102. The mobile wireless device 100 then measures and tracks the RSSI of the received wireless communications messages 176B from the wireless service device 102, while the distance between the two devices increases. The mobile wireless device 100 determines whether the estimated increasing distance to the wireless service device 102 satisfies a predetermined behavior expected for signal strength as distance varies, i.e. between increasing distance and the RSSI of the received wireless communication messages 176B. The mobile wireless device 100 will invoke and execute a secure application, if the estimated increasing distance to the wireless service device 102 that it has measured and tracked, satisfies the predetermined behavior expected for signal strength as distance varies.
The figure includes a graph of RSSI vs separation distance. If the mobile wireless device 100 detects the proximity (e.g. 10 cm) of a transmitter based on an RSSI measurement at only one distance, it is possible that another wireless device transmitting with higher power levels, may erroneously be interpreted to be the wireless service device 102 in proximity. The wireless service device 102 with 10 dBm output power level produces a similar measured RSSI value at 10 cm distance than another, unintended wireless device with 30 dBm output power level produces from a 1 m distance. With only a single measurement, it is impossible to detect the difference between the two transmitters.
If the mobile wireless device 100 performing the RSSI measurement is moved either closer or farther away from the intended wireless service device 102, and the RSSI measurement is repeated, there is no ambiguity in identifying the actual transmitting device. If the measurement is now repeated at 30 cm distance, the 10 dBm transmitter provides signal strength of −19.8 dBm and the unintended 30 dBm transmitter (actually being now anywhere between 80 cm and 1.2 meters away) provides RSSI values within range [−8 . . . −11.8] dBm, which easily distinguishes the intended device 102 from the unintended device.
In accordance with an example embodiment of the invention, repeating the RSSI measurement with at least two different distances while being in proximity, provides the information required to distinguish between devices. In addition, if there is a fixed attenuation (such as the user's hand), the signal strength curves are merely shifted down by the amount of the attenuation, but the difference of the signal strengths between the measurements performed at the different distances remains constant.
In embodiments of the invention, the mobile wireless device 100 and the wireless service device 102 may increase the quantity of the wireless connection messages 176A and 176B that they exchange, to increase the number of RSSI measurements, so as to enhance the determining whether the predetermined behavior expected for signal strength as distance varies is satisfied.
 invoke a secure application and receive service from wireless service device 102.
FIG. 1D is an illustration of an example embodiment of the network of FIG. 1C, wherein the wireless service device 102 responds to the request for a secure communications session, by also measuring and tracking the RSSI of wireless communications messages 176A that it receives from the mobile wireless device 100, while the distance between the two devices increases. The wireless service device 102 also determines whether the estimated increasing distance X3 between the devices satisfies the predetermined behavior expected for signal strength as distance varies, i.e., between increasing distance and the RSSI of the received wireless communication messages 176A. The wireless service device 102 will invoke and execute a secure application, if the estimated increasing distance between the devices that it has measured and tracked, satisfies the predetermined behavior expected for signal strength as distance varies.
In embodiments of the invention, the wireless service device 102 and the mobile wireless device 100 may increase the quantity of the wireless connection messages 176A and 176B that they exchange, to increase the number of RSSI measurements, so as to enhance the determining by the wireless service device 102, whether the predetermined behavior expected for signal strength as distance varies is satisfied. The wireless service device 102 and the mobile wireless device 100 may signal to each other their respective determinations as to whether the predetermined behavior expected for signal strength as distance varies is satisfied.
[9′] if connection is secure, then provide secure service.
In an example use case, a mobile device 100 is using Touch-to-Select to select payment device 102. The device 100 guides the user to touch the payment device 102, after device 102 is selected with Touch-to-Select, device 100 will guide the user to pull away device 100. This movement can be calculated with the measured RSSI, as described. The user of the device 100 wishes to pay and activates a payment application. The payment application searches for the payment device 102 by scanning Bluetooth LE devices that have a known universally unique identifier (UUID) in the advertisement field of an advertising packet. The payment device 102 advertises itself with this UUID in its advertisement field. When device 100 finds an advertisement having this known UUID, device 100 prompts the user to move closer to the payment device, for example displaying the message “Touch Device”. When device 100 touches the payment device 102, the signal strength of the advertising packets from the device 102 are sufficiently high to trigger the Touch-to-Select event in device 100, causing device 100 to create a connection to device 102. Once the connection is created, device 100 prompts the user to move his mobile device 100 away. Now either or both device 100 and/or device 102 may measure the RSSI of the data connection packets while the distance between the devices increases, in order to be certain that device 102 is the intended payment device with which to be connected.
In an example embodiment of the invention, data may be exchanged with a selected device after the touch-to-select event, without creating a connection with that device. The mobile device 100 and the service device 102 may communicate with each other using discovery messages, for example by alternating their scanning and advertising states, so that advertising data may be sent in both directions. After the mobile device 100 determines that the service device 102 is in close proximity, by using touch-to-select, the mobile device 100 and the service device 102 may exchange additional wireless discovery messages, for example by sending advertising data in both directions.
In an example embodiment of the invention, the service device 102 may use wireless discovery messages received from the mobile device 100, such as scan request packets, to measure the signal strength and determine the identity of the sender of the wireless discovery messages received from the mobile device 100.
In an example embodiment of the invention, the data exchanged by sending advertising data in both directions, may be used to configure advertising parameters, for example by making service device 102 transmit advertising packets more rapidly, such as when a touch-to-select event has occurred. This makes it possible to follow the signal characteristics of service device 102 more accurately.
FIG. 2 is a timing diagram illustrating the discovery phase 200 during which device discovery messages 150, such as Bluetooth inquiry response packet or Bluetooth LE advertising packets, transmitted by the wireless service device 102, are received by the mobile wireless device 100. The mobile wireless device 100 measures the RSSI of the wireless device discovery messages 150 that it receives. When the mobile wireless device 100 has moved sufficiently close to the wireless service device 102, it performs a touch-to-select event 20 that initiates a connection phase 220 wherein a communication connection is made to the wireless service device 102. Then the mobile wireless device 100 sends a request message 180 for a secure communications session, to the wireless service device 102. The wireless service device 102 replies with an acknowledgement message 180′.
The mobile wireless device 100 displays a prompt to its user to move the mobile wireless device 100 backward, away from the wireless service device 102. In embodiments of the invention, the mobile wireless device 100 and the wireless service device 102 may increase the quantity of the wireless connection messages 176A and 176B that they exchange during an interval 182, to increase the number of RSSI measurements, so as to enhance the determining whether the predetermined behavior expected for signal strength as distance varies is satisfied. For example, the mobile wireless device 100 and the wireless service device 102 may disable any low activity modes and thus transmit a packet in every time slot.
The mobile wireless device 100 measures and tracks the RSSI of the received wireless communications messages 176B from the wireless service device 102, during the interval 182 while the distance between the two devices increases. The mobile wireless device 100 determines whether the estimated increasing distance to the wireless service device 102 satisfies a predetermined behavior expected for signal strength as distance varies, i.e., between increasing distance and the RSSI of the received wireless communication messages 176B.
When the mobile wireless device determines that the estimated increasing distance to the wireless service device 102, satisfies the predetermined behavior expected for signal strength as distance varies, then the mobile wireless device 100 will invoke and execute a secure application and it will exchange normal packet traffic with the wireless service device 102 thereafter at 184.
FIG. 3 is an example flow diagram 300 for the mobile wireless device, in accordance with at least one embodiment of the present invention. Device 100 is trying to make a secure selection of device 102. In step 302 device 100, which is capable of Touch-to-Select operation, starts the Touch-to-Select process. In step 304, when device 100 measures an RSSI of a device discovery message 150 from device 102, which is over a predefined threshold, device 100 connects to device 102 in step 306. This connection is not an application level connection, but is some general attribute connection that does not have a security requirement. With this connection, device 100 may measure the RSSI of data connection packets from device 102 multiple times per second, in step 308. Device 100 analyses the measured RSSI values according to certain signal level changes. In addition, device 102 may analyze the RSSI of the same connection and accept secure connection of the device 100, if the RSSI satisfies a predetermined behavior expected for signal strength as distance varies. If wanted signal level change is found, the actual application level connection (secure connection) is established in step 312. If not, device 100 is disconnected in step 310 and continues the Touch-to-Select process.
FIG. 4 is an example flow diagram 400 for the wireless service device 102, in accordance with at least one embodiment of the present invention. In step 402, the wireless service device 102 waits for a general incoming connection. In step 404, the wireless service device 102 accepts the connection with device 100. In step 406, the wireless service device 102 reads the RSSI of the active link with device 100 and determines whether the RSSI satisfies a predetermined behavior expected for signal strength as distance varies. If the predetermined behavior expected for signal strength as distance varies is satisfied, then in step 410, the application connection is accepted for device 102. If not satisfied, then in step 408, the device 102 is disconnected from device 100.
FIG. 5 is an example format diagram 500 for an advertising packet from device 102, which indicates a required RSSI for service use, in accordance with at least one embodiment of the present invention. Field 502 specifies the type of information in the next field, i.e., RSSI requirement for service activation. Field 504 specifies the minimum RSSI necessary to authenticate data connection packets transmitted from the device 102. Field 506 specifies the type of information in the next field, i.e., service available from the device 102. Field 506 is the specification of the available service.
In an example embodiment of the invention, device 102 may advertises itself by using the format shown in FIG. 5. Device 100 may perform a selection of device 102 without the necessity of establishing a connection, by merely scanning advertising packets from device 102 and analyzing them and their RSSI level. Connection to device 102 may be established when specified RSSI of the advertising packets is found.
As shown in FIG. 5, the required RSSI threshold may be specified in the advertisement field, as well as the available service information. The specified RSSI threshold may be used to authenticate the advertising packet. In this manner, the payment device 102 may, for example, indicate that an RSSI of −40 dBm is required to initiate a secure payment process. When the mobile device 100 is performing a scan or inquiry process, it will determine that the payment device 102 may be used if the measured RSSI of the advertising packet is high enough. With this information, the mobile device 100 may display a prompt to the user, such as “Touch Device” and begin the Touch-to-Select process when measured RSSI is high enough (in this example, higher that −40 dBm). Now device 100 knows that it can make payment connection with payment device 192.
Step 610 determining, by the apparatus, whether changes in the measured signal strength of the exchanged messages satisfy a predetermined behavior expected for signal strength as distance varies.
Step 660: invoking, by the apparatus, a secure application in the apparatus if the changes in the obtained signal information satisfy the predetermined behavior expected for signal strength as distance varies.
Any resulting program(s), having computer-readable program code, may be embodied on one or more computer-usable media such as resident memory devices, smart cards or other removable memory devices, or transmitting devices, thereby making a computer program product or article of manufacture according to the embodiments. As such, the terms “article of manufacture” and “computer program product” as used herein are intended to encompass a computer program that exists permanently or temporarily on any computer-usable medium.
establishing, by the apparatus, the secure communications session with the wireless device, in response to determining that the changes in the measured signal strength of the exchanged messages satisfy the predetermined behavior expected for signal strength as distance varies.
2. The method of claim 1, wherein the exchanged messages are wireless discovery messages.
3. The method of claim 2, wherein the one or more wireless discovery messages are at least one of a Bluetooth inquiry response message or a Bluetooth Low Energy advertising message.
establishing, by the apparatus, the secure communications session with the wireless device, in response to determining that the changes in the obtained signal information satisfy the predetermined behavior expected for signal strength as distance varies.
establish the secure communications session with the wireless device, in response to determining that the changes in the measured signal strength of the exchanged messages satisfy the predetermined behavior expected for signal strength as distance varies.
10. The method of claim 9, wherein the exchanged messages are wireless discovery messages.
11. The apparatus of claim 10, wherein the one or more wireless discovery messages are at least one of a Bluetooth inquiry response message or a Bluetooth Low Energy advertising message.
14. The apparatus of claim 9, wherein the information obtained from one or more wireless discovery messages and the signal information obtained from the exchanged messages, includes at least RSSI information corresponding the distance between the apparatus and the wireless device.
establish the secure communications session with the wireless device, in response to determining that the changes in the obtained signal information satisfy the predetermined behavior expected for signal strength as distance varies.
code for establishing, by the apparatus, the secure communications session with the wireless device, in response to determining that the changes in the measured signal strength of the exchanged messages satisfy the predetermined behavior expected for signal strength as distance varies.
code for establishing, by the apparatus, the secure communications session with the wireless device, in response to determining that the changes in the obtained signal information satisfy the predetermined behavior expected for signal strength as distance varies.
"Bluetooth Specification Version 4.0", Jun. 30, 2010, pp. 380-767.
European Search Report for EP Application No. 08006467.8-2412/ 1965555 dated Nov. 2, 2011.
European Search Report for European Patent Application No. 12166717.4-2412-dated Jul. 20, 2012.
European Search Report for European Patent Application No. 12166717.4-2412—dated Jul. 20, 2012.
Extended European Search Report for European Patent Application No. 12167079.8-2412-dated Jul. 30, 2012.
Extended European Search Report for European Patent Application No. 12167079.8-2412—dated Jul. 30, 2012.
International Search Report for International Application No. PCT/F12012/050531-Date of Completion of Search: Sep. 3, 2012-4 pages.
International Search Report for International Application No. PCT/F12012/050531—Date of Completion of Search: Sep. 3, 2012—4 pages.
International Search Report for International Application No. PCT/F12013/050085 mailed May 13, 2013.
International Search Report for International Application No. PCT/FI2012/050442-Date of Completion of Search: Sep. 18, 2012-4 pages.
International Search Report for International Application No. PCT/FI2012/050442—Date of Completion of Search: Sep. 18, 2012—4 pages.
Notice of Allowance for Korean Application No. 10-2006-7009441 dated Jan. 7, 2008.
Office Action for Korean Application No. 10-2006-7009441 dated Apr. 23, 2007.
Opposition Notice and Filing in European Application No. 1 685 689 (No Translation).
Opposition Response in European Application Patent No. 1 685 689.
Palin, A., et al., "VoIP call over WLAN with Bluetooth headset-multiradio interoperability solutions", 2005 IEEE Application No. 12167079.8-2412-Date of Completion of Search: Jul. 13, 2012, 12 pages.
Palin, A., et al., "VoIP call over WLAN with Bluetooth headset—multiradio interoperability solutions", 2005 IEEE Application No. 12167079.8-2412—Date of Completion of Search: Jul. 13, 2012, 12 pages.
Radio Frequency Identification RFID-A basic primer, AIM Inc. White Paper; Aug. 23, 2001; 17 pages; 1.2; The Association of the Automatic Identification and Data Capture Industry (AIM Inc.); WP-98/002R2.
Radio Frequency Identification RFID—A basic primer, AIM Inc. White Paper; Aug. 23, 2001; 17 pages; 1.2; The Association of the Automatic Identification and Data Capture Industry (AIM Inc.); WP-98/002R2.
Widmer. P., "Smart Box Software Framework", Vision Document, Apr. 7, 2003, 23 pages.
Nasipuri et al. 2000 A MAC protocol for mobile ad hoc networks using directional antennas.

References: Application No. 08006467
 Application No. 12166717
 Application No. 12166717
 Application No. 12167079
 Application No. 12167079
 Application No. 10
 Application No. 10
 Application No. 1
 Application No. 12167079
 Application No. 12167079