USRE47488E1 - Method, apparatus, and computer program product for wireless device discovery process - Google Patents
Method, apparatus, and computer program product for wireless device discovery process Download PDFInfo
- Publication number
- USRE47488E1 USRE47488E1 US15/259,577 US201615259577A USRE47488E US RE47488 E1 USRE47488 E1 US RE47488E1 US 201615259577 A US201615259577 A US 201615259577A US RE47488 E USRE47488 E US RE47488E
- Authority
- US
- United States
- Prior art keywords
- device discovery
- wireless device
- detecting
- inquiry
- messages
- 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.)
- Expired - Fee Related, expires
Links
- 238000000034 method Methods 0.000 title claims abstract description 70
- 238000004590 computer program Methods 0.000 title claims abstract description 35
- 230000008569 process Effects 0.000 title abstract description 26
- 230000004044 response Effects 0.000 claims abstract description 264
- 230000015654 memory Effects 0.000 claims description 19
- 230000007423 decrease Effects 0.000 claims description 11
- 230000003247 decreasing effect Effects 0.000 claims description 7
- 238000003860 storage Methods 0.000 claims description 6
- 238000004891 communication Methods 0.000 abstract description 47
- 238000005516 engineering process Methods 0.000 description 15
- 238000010586 diagram Methods 0.000 description 12
- 230000006870 function Effects 0.000 description 7
- 238000005259 measurement Methods 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 6
- 230000015572 biosynthetic process Effects 0.000 description 5
- 230000000694 effects Effects 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 5
- 238000004904 shortening Methods 0.000 description 5
- 239000004065 semiconductor Substances 0.000 description 4
- 238000004519 manufacturing process Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000001360 synchronised effect Effects 0.000 description 3
- 239000000872 buffer Substances 0.000 description 2
- 239000000969 carrier Substances 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000005562 fading Methods 0.000 description 2
- 238000012544 monitoring process Methods 0.000 description 2
- 239000000523 sample Substances 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000002087 whitening effect Effects 0.000 description 2
- 206010000210 abortion Diseases 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000013467 fragmentation Methods 0.000 description 1
- 238000006062 fragmentation reaction Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000035945 sensitivity Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- 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
- the technology field relates to controlling device discovery process based on received discovery messages.
- Wireless communication devices can vary from battery powered handheld devices to stationary household and/or commercial devices utilizing electrical network as a power source. Due to rapid development of the wireless communication devices a number of areas capable of enabling entirely new types of communication applications have emerged.
- BluetoothTM communication protocol which operates in the 2.4 GHz ISM band.
- BluetoothTM is a short-range radio network, originally intended as a cable replacement.
- BluetoothTM Technical Specifications are published by the BluetoothTM SIG, Inc.
- BluetoothTM Specification version 2.0+EDR published Oct. 15, 2004 has the original functional characteristics of the first version BluetoothTM Basic Rate (BR) and adds the Enhanced Data Rate (EDR) feature.
- BluetoothTM 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.
- BluetoothTM Specification version 3.0+HS published Apr. 21, 2009, updated the standard to integrate the Alternate MAC/PHY and Unicast Connectionless Data features.
- the BluetoothTM Core Specification, Version 4.0, BluetoothTM SIG, Jun. 30, 2010 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.
- SDP service discovery protocol
- Method, apparatus, and computer program product example embodiments enhance wireless communications device discovery processes.
- the predefined criterion comprises at least one of a received signal strength indication of the wireless device discovery message exceeding a threshold value, an interval since a previous increase in the rate of detecting a wireless device discovery message is greater than a first threshold interval, an interval since detecting a previous wireless device discovery message is less than a second threshold duration, and a predetermined number of previously detected one or more wireless device discovery messages is less than a threshold number.
- the apparatus tunes the device discovery parameters to increase the rate of detecting wireless device discovery messages by at least one of reducing an inquiry scan interval, increasing an inquiry scan window, and performing interlaced inquiry scanning.
- the apparatus tunes the device discovery parameters to increase the rate of detecting wireless device discovery messages for a predetermined time period after receipt of the wireless device discovery message.
- the apparatus transmitting, by the apparatus, in response to detecting the wireless device discovery message, one or more wireless response messages usable for a wireless device receiving the one or more wireless response messages, to estimate a distance to the apparatus, the one or more wireless response messages including at least one of a received signal strength indication of the wireless device discovery message and an indication that the apparatus and the wireless device are in close proximity with each other.
- the rate of detecting the wireless device discovery messages in response to at least one of a received signal strength indication of the wireless device discovery message decreases below a threshold value, an interval since a previous increase in the rate of detecting wireless device discovery messages is less than a first threshold interval, an interval since detecting a previous wireless device discovery message is greater than a second threshold interval, and a predetermined number of previously detected wireless device discovery messages is greater than a threshold number.
- At least one memory including computer program code
- the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to:
- the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to:
- the predefined criterion comprises at least one of a received signal strength indication of the wireless device discovery message exceeding a threshold value, an interval since a previous increase in the rate of detecting a wireless device discovery message is greater than a first threshold interval, an interval since detecting a previous wireless device discovery message is less than a second threshold duration, and a predetermined number of previously detected one or more wireless device discovery messages is less than a threshold number.
- the apparatus tunes the device discovery parameters to increase the rate of detecting wireless device discovery messages by at least one of reducing an inquiry scan interval, increasing an inquiry scan window, and performing interlaced inquiry scanning.
- the apparatus tunes the device discovery parameters to increase the rate of detecting wireless device discovery messages for a predetermined time period after receipt of the wireless device discovery message.
- the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to:
- the wireless device discovery message transmits, in response to detecting the wireless device discovery message, one or more wireless response messages usable for a wireless device receiving the one or more wireless response messages, to estimate a distance to the apparatus, the one or more wireless response messages including at least one of a received signal strength indication of the wireless device discovery message and an indication that the apparatus and the wireless device are in close proximity with each other.
- the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to:
- An example embodiment of the invention includes a computer program product comprising computer executable program code recorded on a computer readable, non-transitory storage medium, the computer executable program code comprising:
- the predefined criterion comprises at least one of a received signal strength indication of the wireless device discovery message exceeding a threshold value, an interval since a previous increase in the rate of detecting a wireless device discovery message is greater than a first threshold interval, an interval since detecting a previous wireless device discovery message is less than a second threshold duration, and a predetermined number of previously detected one or more wireless device discovery messages is less than a threshold number.
- the apparatus tunes the device discovery parameters to increase the rate of detecting wireless device discovery messages by at least one of reducing an inquiry scan interval, increasing an inquiry scan window, and performing interlaced inquiry scanning.
- the apparatus tunes the device discovery parameters to increase the rate of detecting wireless device discovery messages for a predetermined time period after receipt of the wireless device discovery message.
- the apparatus code for transmitting, by the apparatus, in response to detecting the wireless device discovery message, one or more wireless response messages usable for a wireless device receiving the one or more wireless response messages, to estimate a distance to the apparatus, the one or more wireless response messages including at least one of a received signal strength indication of the wireless device discovery message and an indication that the apparatus and the wireless device are in close proximity with each other.
- the rate of detecting the wireless device discovery messages in response to at least one of a received signal strength indication of the wireless device discovery message decreases below a threshold value, an interval since a previous increase in the rate of detecting wireless device discovery messages is less than a first threshold interval, an interval since detecting a previous wireless device discovery message is greater than a second threshold interval, and a predetermined number of previously detected wireless device discovery messages is greater than a threshold number.
- the resulting example embodiments enhance wireless communications device discovery processes.
- FIG. 1A is an illustration of an example timing diagram of an example sequence of operations conducted between two mobile wireless devices, wherein a scanning device receives one or more device discovery messages. After detecting a discovery message, the scanning device tunes its inquiry parameters, for example the inquiry scan interval, the inquiry scan window, or whether to do interlaced/non-interlaced scanning, which has the effect of increasing the rate of transmitting one or more response messages.
- the response messages include information usable for a wireless device receiving them, to estimate a distance to the scanning device, in accordance with at least one embodiment of the present invention.
- FIG. 1B is an illustration of an example timing diagram of the device discovery process, using the Bluetooth communications standard, in accordance with at least one embodiment of the present invention.
- FIG. 2A is an illustration of an example embodiment of a network in a device discovery phase, with a first device, the inquiring device, broadcasting one or more wireless device discovery messages to one or more wireless devices, including a second wireless device, the scanning device, in accordance with at least one embodiment of the present invention.
- FIG. 2B is an illustration of an example embodiment of the network of FIG. 2A , in the device discovery phase, wherein scanning device receives one or more device discovery messages and in response, the scanning device tunes the scanning parameters, which has the effect of shortening the times between successive response messages, increasing the rate of transmitting the response messages.
- the response messages include information usable for a wireless device receiving the one or more response messages, to estimate a distance to the scanning device.
- the inquiring device detects one or more response messages received at the increased rate from the scanning device, which identifies that a touch-to-select event has occurred, in accordance with at least one embodiment of the present invention.
- FIG. 2C is an illustration of an example embodiment of the network of FIG. 2B , wherein the occurrence of the touch-to-select event results in the two devices establishing a connection, in accordance with at least one embodiment of the present invention.
- FIG. 3A is an illustration of an example flow diagram of an example process in the scanning device 100 carrying out the example operations in the device discovery phase shown in FIG. 1A , in accordance with at least one embodiment of the present invention.
- FIG. 3B is an illustration of an example flow diagram of an example implementation of the process in the inquiring device 102 , carrying out the example operations in the device discovery phase, in accordance with at least one embodiment of the present invention.
- FIG. 3C is an illustration of an example message format for device discovery messages, using the Bluetooth communications standard, in accordance with at least one embodiment of the present invention.
- FIG. 3D is an illustration of an example message format for discovery response messages, using the Bluetooth communications standard, in accordance with at least one embodiment of the present invention.
- FIG. 3E is an illustration of an example message format for extended discovery response messages, using the Bluetooth communications standard, in accordance with at least one embodiment of the present invention.
- FIG. 3F is an illustration of an example message format for communication connection messages, using the Bluetooth communications standard, in accordance with at least one embodiment of the present invention.
- FIG. 4 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.
- SD Secure Digital standard
- 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.
- BluetoothTM Baseband is the part of the BluetoothTM 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 BluetoothTM devices. Connection formation may include inquiry, inquiry scanning, inquiry response, in addition to paging, page scanning, and page response procedures.
- MAC Media Access Control
- Inquiry is a procedure where a BluetoothTM device transmits inquiry messages and listens for responses in order to discover the other BluetoothTM devices that are within the coverage area and set discoverable.
- BluetoothTM devices use the inquiry procedure to discover nearby devices, or to be discovered by devices in their locality.
- a BluetoothTM device that tries to find other nearby devices is known as an inquiring device and actively sends inquiry requests.
- BluetoothTM 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.
- BluetoothTM 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 625 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.
- 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.
- IAC inquiry access code
- 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).
- LAP Lower Address Part
- GIAC General Inquiry Access Code
- a device that allows itself to be discovered may regularly enter the inquiry scan substate to respond to inquiry messages.
- the discovering device collects the BluetoothTM device addresses of all devices that respond to the inquiry message.
- 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.
- GIAC general inquiry access code
- the inquiry access codes are derived from reserved BluetoothTM device addresses. There is only one DIAC defined in the BluetoothTM 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.
- DIAC Limited Inquiry Access Code
- Inquiry scan is a procedure where a BluetoothTM 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 BluetoothTM 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
- An inquiry response packet (frequency hop sequence (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.
- 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.
- FHS frequency hop sequence
- the slave 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 close 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.
- 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.
- step 1 the master transmits an inquiry message using the inquiry access code and its own clock.
- step 2 the slave responds with the FHS packet containing the slave's BluetoothTM 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.
- step 3 if the slave has non-zero extended inquiry response data, it sends an extended inquiry response packet to the master.
- 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.
- 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.
- SDP service discovery protocol
- 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.
- 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.
- 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.
- 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 BluetoothTM device address of the slave device. The necessary information may be received by other means, such as Out-Of-Band pairing.
- the page is not always preceded with inquiry, because the address may be known beforehand (for example saved from previous connections).
- one the BluetoothTM device that will become the master carries out a page procedure by transmitting page messages in connection request packets to the specified BluetoothTM slave device that carries out a page scanning procedure to listen for connection request packets from the paging device.
- a connectable BluetoothTM 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 BluetoothTM 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 BluetoothTM 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 BluetoothTM 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.
- a paging device In order for a paging device to connect to another BluetoothTM device, it uses the page scan channel of the target device in order to send page requests.
- the paging device 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 BluetoothTM 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.
- the received signal strength indicator is a measurement of the power present in a received radio signal.
- Bluetooth receiver circuits may include an RSSI detector circuit to measure the strength of an incoming signal and generate an output representing the signal strength. For example, the received RF signal may be amplified and downconverted to an intermediate frequency (IF); then channel selection is performed on the IF signal, and the power of the IF signal in the selected channel is measured as the receiver signal strength indicator (RSSI) value. If the Bluetooth receiver circuit supports RSSI, the accuracy may be +/ ⁇ 6 dBm or better.
- the RSSI is measured from Inquiry Response (FHS) packets when it is received by an inquiring device if enabled by the host.
- FHS 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 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.
- 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.
- the received signal strength indication 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.
- the Read RSSI Command will read the value of the received signal strength indication (RSSI) for data communication packets received over the connection to another Bluetooth controller.
- RSSI received signal strength indication
- the Connection_Handle is used by the Bluetooth controller to determine which set of buffers to use and the logical link over which the data is to be sent.
- the TX Power Level data field in the Extended Inquiry Response packet indicates the transmitted power level of the FHS and EIR packets at the transmitter of the sending device.
- the BluetoothTM radio in a device may include the host controller interface that provides a command interface between the host application in the device and the link layer of the BluetoothTM radio, also referred to as the controller, to enable access to hardware status and control registers of the BluetoothTM radio.
- the host controller interface (HCI) is described in the BluetoothTM 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.
- HCI events are used for notifying the Host when something occurs.
- 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 provides a command interface between the host application in a device and the BluetoothTM link layer, provides access to hardware status and control registers of the BluetoothTM radio, and provides a uniform method of accessing the BluetoothTM baseband capabilities.
- the device discovery group of commands and events allow a device to discover other devices in the surrounding area.
- the host controller interface includes the standard HCI Inquiry Result Event logic and HCI Extended Inquiry Result Event logic that recognizes the receipt of the FHS packet and the following EIR packet, respectively.
- 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 BluetoothTM Controller to the Host as soon as an Inquiry Response from a remote device is received.
- IR inquiry response
- 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 dB. 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 BluetoothTM 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 received signal strength indication 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 by the Bluetooth physical layer, and may be read by the host application through the host controller interface (HCI) Read RSSI command.
- the Read RSSI command will read the value of the received signal strength indication (RSSI) for data communication packets received over the connection to another Bluetooth controller.
- RSSI received signal strength indication
- the RSSI value is referenced with respect to a Connection_Handle that identifies the connection and is assigned when the connection is created.
- the Connection_Handle is used by the Bluetooth controller to determine which set of buffers to use and the logical link over which the data is to be sent.
- 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.
- RSSI Received Signal Strength Indication
- BR/EDR Basic Rate/Enhanced Data Rate
- 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 meaning of the RSSI metric is an absolute receiver signal strength value in dBm to ⁇ 6 dBm accuracy. If the RSSI cannot be read, the RSSI metric is set to 127. (When the Read_RSSI command has completed, a Command Complete event is generated.)
- 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.
- RSSI Received Signal Strength Indication
- 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).
- RSSI signal strength
- 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 EIR events triggered by the responses.
- the reported EIR 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.
- 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.
- 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.
- 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.
- responding inquiry scanning devices may send Tx power information in EIR packet, since this is an existing feature in the Bluetooth specification v4.0.
- the predetermined response criteria may include an adjustable RSSI threshold value that accounts for variations in the Tx power.
- 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 dBm below of Tx power level.
- the predetermined response criteria may require that more than one EIR must have a sensed RSSI at or above a threshold value.
- 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: [1] antenna location of the inquiry scanning device sending the signal and [2] 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.
- FIG. 1A is an illustration of an example timing diagram of an example sequence of operations conducted between two mobile wireless devices, according to an example embodiment of the invention.
- a scanning device 100 receives one or more wireless device discovery messages 150 from an inquiring device 102 , shown in FIG. 2A .
- the wireless device discovery messages 150 may be Bluetooth inquiry packets transmitted by the inquiring device 102 in master-to-slave (M-S) slots.
- M-S master-to-slave
- the scanning device 100 scans for wireless device discovery messages with smaller scan windows 22 and larger scan intervals 24 .
- the scanning device 100 After detecting the first discovery message, the scanning device 100 temporarily tunes its inquiry scanning parameters, for example the inquiry scan interval, the inquiry scan window, or whether to do interlaced/non-interlaced scanning.
- the scanning device 100 in response to detecting the wireless device discovery message 150 , temporarily tunes the device discovery parameters to increase the rate of detecting wireless device discovery messages.
- the scanning device 100 in response to detecting the wireless device discovery message 150 , may tune the device discovery parameters to increase the rate of detecting wireless device discovery messages for a predetermined time period after receipt of the wireless device discovery message 150 .
- the tuning may be done at the controller or by the host.
- the HCI Write Inquiry Scan Activity command may be used, for example, to control the interval and window sizes.
- the figure shows that when the scanning device 100 detects one or more device discovery messages 150 , scanning device 100 tunes the scanning parameters to increase the scan windows 22 ′, 22 ′′, 22 ′′′ and reduce the scan intervals 24 ′, 24 ′′, 24 ′′′.
- each Bluetooth FHS response message 158 is transmitted by the scanning device 100 in the slave-to-master (S-M) slot following the Bluetooth inquiry packet 150 received from inquiring device 102 in the preceding master-to-slave (M-S) slot.
- S-M slave-to-master
- M-S master-to-slave
- the figure shows that in response to detecting at “D”, the device discovery message 150 , the scanning device 100 tunes its scanning parameters to increase scan windows 22 and reduce scan intervals 24 .
- the rate “R” of detecting device discovery messages 150 is increased in response to the scanning device 100 tuning its scanning parameters, resulting in an increased rate of transmitting the response messages 158 .
- the scanning device 100 may tune the scanning parameters to shorten the times between successive response messages, thereby increasing the rate of transmitting one or more response messages 158 and 160 .
- the response messages may include information usable for an inquiring device 102 receiving the one or more response messages 158 and 160 , to estimate a distance to the scanning device 100 , in response to the one or more discovery messages 150 meeting the predefined criterion, in accordance with at least one embodiment of the present invention.
- the predefined criterion may be at least one of a received signal strength indication (RSSI) of the one or more device discovery messages 150 exceeds a threshold value, an interval since a previous increase in the rate of receiving or detecting one or more device discovery messages 150 is greater than a first threshold interval, an interval since receiving or detecting a previous device discovery message 150 is less than a second threshold duration, a predetermined number of previously received or detected one or more device discovery messages 150 is less than a threshold number, and a host control signal based on prescribed conditions or user settings.
- RSSI received signal strength indication
- the scanning device 100 increases the rate of receiving or detecting one or more device discovery messages 150 by at least one of reducing an inquiry scan interval, increasing an inquiry scan window, and performing interlaced inquiry scanning
- the information in the one or more response messages 158 and 160 usable for the inquiring device 102 receiving the one or more response messages, to estimate a distance to the scanning device 100 , includes at least one of a received signal strength indication (RSSI) of the one or more device discovery messages 158 and 160 and an indication that the scanning device 100 and the inquiring device 102 are in close proximity with each other.
- RSSI received signal strength indication
- the scanning device 100 may tune the scanning parameters to reduce the scan windows and increase the scan intervals to thereby decrease the rate of receiving or detecting the one or more device discovery messages 150 .
- This mode of tuning to reduce the rate of receiving may be in response to at least one of a received signal strength indication (RSSI) of the one or more device discovery messages 150 decreases below a threshold value, an interval since a previous increase in the rate of receiving or detecting one or more device discovery messages 150 is less than a first threshold interval, an interval since receiving or detecting a previous device discovery message 150 is greater than a second threshold interval, a predetermined number of previously received or detected one or more device discovery messages 150 is greater than a threshold number, and a host control signal based on prescribed conditions or user settings.
- RSSI received signal strength indication
- the tuning of the scanning parameters in this mode has the effect of lengthening the times between successive response messages 158 , decreasing the rate of transmitting the response messages 158 .
- FIG. 1B is an illustration of an example timing diagram of the device discovery process, using the Bluetooth communications standard, in accordance with at least one embodiment of the present invention. The following is one example embodiment applied to Bluetooth technology.
- the inquiring device or master device 102 transmits inquiry messages 150 with the general or dedicated inquiry access code.
- An inquiry response packet (FHS) 158 is transmitted from the inquiry scanning device or slave 100 to the master 102 after the slave has received the inquiry message 150 .
- the device discovery is specified so that the discoverable inquiry scanning device 100 is doing inquiry scan and the inquiring device 102 doing device discovery is in the inquiry state. This means that the inquiring device 102 in inquiry state sends inquiry packets (ID packets) 150 , as shown in FIG. 2A , and the discoverable inquiry scanning device 100 scans periodically whether it receives and detects any of the transmitted inquiry packets 150 and responds to those with FHS packets 158 , as shown in FIG. 2B .
- ID packets inquiry packets
- the discoverable inquiry scanning device 100 may send an Extended Inquiry Response (EIR) packet 160 after the FHS packet 158 , as shown in FIG. 1B , to deliver more information about the inquiry scanning device 100 .
- the EIR packet 160 may include for example name of the inquiry scanning device 100 or transmission power.
- the inquiry scanning device 100 transmits an extended inquiry response packet 160 , it is transmitted 1250 microseconds after the start of the inquiry response FHS packet 158 .
- the extended inquiry response packet 160 is received by the inquiring device 102 at the hop frequency when the inquiry message received by the inquiry scanning device 100 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.
- ACL Asynchronous Connection-oriented Logical transport
- FIG. 2A is an illustration of an example embodiment of a network in a device discovery phase, with a first device, the inquiring device 102 , broadcasting one or more wireless device discovery messages 150 to one or more wireless devices, including a second wireless device, the scanning device 100 , in accordance with at least one embodiment of the present invention.
- the figure shows an example embodiment of the network in the device discovery phase 200 , with the first device 102 broadcasting one or more wireless device discovery messages 150 to one or more wireless devices, including the second wireless device 100 , in accordance with at least one embodiment of the present invention.
- the following is one example embodiment applied to Bluetooth technology.
- the example network includes a first BluetoothTM inquiring device 102 broadcasting one or more inquiry packets 150 to one or more inquiry scanning devices, including a second BluetoothTM inquiry scanning device 100 , in accordance with at least one embodiment of the present invention.
- the inquiry scanning device 100 and the inquiring device 102 include a processor 122 that includes from one to many central processing units (CPUs) 124 and 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 , battery or house power sources, keyboard, 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.
- the BluetoothTM inquiry scanning device 100 and the inquiring device 102 include the host controller interface (HCI) 111 that provides a command interface between the host application 110 B in the device and the link layer or MAC 114 and the radio 116 , also referred to as the controller, to enable access to hardware status and control registers of the BluetoothTM radio 116 .
- the host controller interface (HCI) is described in the BluetoothTM Core Specification.
- the Host application 110 B will receive asynchronous notifications of HCI events from HCI 111 . HCI events are used for notifying the Host application 110 B 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 B and the radio 116 .
- the HCI 111 provides a command interface between the host application 110 B in a device and the BluetoothTM 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 BluetoothTM baseband capabilities.
- the processor 122 in the inquiring device 102 (shown in FIG. 2B ) outputs data to the BluetoothTM MAC 114 that packages the data into BluetoothTM protocol data units (PDU) or packets, such as inquiry packets 150 , that are input to the BluetoothTM PHY radio 116 for normal BluetoothTM transmission.
- PDU BluetoothTM protocol data units
- inquiry packets 150 such as inquiry packets 150
- Inquiry scanning device 100 and inquiring device 102 may be, for example, a miniature device such as a key fob, smart card, jewelry, or the like.
- Inquiry scanning device 100 and inquiring device 102 may be, for example, a relatively larger cell phone, smart phone, flip-phone, PDA, graphic pad, or even larger devices such as a laptop computer, desktop computer, kitchen appliance, such as a refrigerator, an automobile dashboard, and the like.
- the relative sizes of devices 100 and 102 may be arbitrary, either one of the devices may be either mobile or fixed-base.
- FIG. 2B is an illustration of an example embodiment of the network of FIG. 2A , in the device discovery phase, wherein scanning device 100 receives and detects one or more device discovery messages 150 and determines that the one or more discovery messages 150 meet a predefined criterion.
- the scanning device 100 may tune the scanning parameters to shorten the times between successive response messages, thereby increasing the rate of transmitting one or more response messages 158 and 160 .
- the scanning device 100 increases a rate of transmitting one or more response messages 158 and 160 including information usable for the inquiring device 102 receiving the one or more response messages 158 and 160 to estimate a distance to the scanning device 100 , in response to the one or more discovery messages 150 meeting the predefined criterion.
- the inquiring device 102 detects one or more response messages 158 and 160 received at the increased rate from the scanning device 100 , which identifies that a touch-to-select event 20 has occurred, in accordance with at least one embodiment of the present invention.
- the second BluetoothTM device transmits one or more response messages including a response packet, such as an inquiry response FHS packet 158 and an inquiry response with an extended inquiry response (EIR) packet 160 , in response to the inquiry packet 150 , in accordance with at least one embodiment of the present invention.
- a response packet such as an inquiry response FHS packet 158 and an inquiry response with an extended inquiry response (EIR) packet 160 , in response to the inquiry packet 150 , in accordance with at least one embodiment of the present invention.
- EIR extended inquiry response
- an RSSI value may be measured by the inquiring device 102 , for the inquiry response FHS packet 158 .
- the RSSI is measured for the FHS packet, whether or not the EIR packet is present. When there is an EIR packet, it is accompanied by a preceding FHS packet that is measured for its RSSI.
- the RSSI is measured for Inquiry Response (FHS) packet when it is received by the inquiring device 102 .
- FHS Inquiry Response
- the radio 116 receives an Inquiry Response (FHS) packet 158 with EIR bit set to zero
- an HCI Inquiry Result with RSSI event is sent by the radio 116 to the host application 110 B, which indicates that a remote Bluetooth device 100 has responded during the current Inquiry process. This event will be sent from the radio 116 to the Host application 110 B as soon as an Inquiry Response 158 from a remote device 100 is received.
- the RSSI parameter is measured during the receipt of the FHS packet 158 .
- an HCI Extended Inquiry Result event is sent by the radio 116 to the host application 110 B, which indicates that a remote Bluetooth device 100 has responded during the current inquiry process with extended inquiry response data. This event will be sent from the radio 116 to the Host application 110 B upon reception of an Extended Inquiry Response 160 from a remote device 100 .
- One single Extended Inquiry Response 160 is returned per event. This event contains RSSI and inquiry response data for the remote device 100 that responded to the latest inquiry 150 . The RSSI parameter is measured during the receipt of the FHS packet 158 .
- the inquiring device may use the RSSI of the response message 158 from an inquiry scanning device 100 , in ordering the responding devices. In this manner, the inquiry scanning device with the highest measured signal strength may be listed first. For example, the measured signal strength may correlate with the distance between the inquiring device and the responding inquiry scanning device.
- 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.
- the Bluetooth radio 116 in the inquiring device may report the receipt of FHS and/or EIR inquiry responses to the host application as an HCI Inquiry Event that may contain the measurement of the RSSI performed on the received response 158 .
- the Bluetooth radio 116 in the inquiring device 102 may report each received EIR as an HCI Extended Inquiry Result Event.
- the Bluetooth radio 116 in the inquiring device 102 may report an RSSI for each EIR response 160 , thereby enabling the inquiring device 102 to track the changing RSSI levels of the inquiry scanning device 100 and thus its relative movement.
- the measured RSSI satisfies predetermined response criterion, such as a threshold value
- the corresponding inquiry scanning device 100 may be selected for touch-related operations, such as expedited connection establishment.
- predetermined response criterion such as a threshold value
- EIR packet There is only one event per FHS packet and the type depends on whether the EIR bit is set to zero or one (EIR packet follows the FHS packet). The latter event is typically reported each time an FHS is received with the EIR bit set to one. The former is typically reported only once per inquiry process.
- the Bluetooth radio 116 in the inquiring device 102 reports the receipt of inquiry responses 158 to its host application 110 B, which also has Touch selection software running.
- Typical response criteria may include RSSI values measured on the response 158 , 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 host application of inquiring device 102 to trigger device selection, while an RSSI of ⁇ 31 dBm will not. It may also be possible that responding inquiry scanning devices 100 may send Tx power information in EIR packet 160 , since this is an existing feature in the Bluetooth specification v4.0.
- the predetermined response criteria may include an adjustable RSSI threshold value that accounts for variations in the Tx power of the inquiry scanning device 100 .
- the threshold value may be set at 30 dBm below the EIR Tx power, so that if the Tx power level of an FHS packet 158 is +20 dBm, then the threshold value that will trigger selection may be the FHS packet 158 being measured at ⁇ 10 dBm, or 30 dBm below of Tx power level.
- the predetermined response criteria may require that more than one FHS 158 have a sensed RSSI at or above a threshold value.
- 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 100 and then a second, more decisive threshold value may be set above ⁇ 30 dBm.
- the detected RSSI may also be a function of: [1] antenna location of the inquiry scanning device 100 sending the signal and [2] antenna location of the inquiring device 102 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.
- FIG. 2C is an illustration of an example embodiment of the network of FIG. 2B , wherein the occurrence of the touch-to-select event 20 results in the two devices 100 and 102 establishing a connection, in accordance with at least one embodiment of the present invention.
- the figure shows an example embodiment of the network of FIG. 2B , in the connection phase 220 after the discovery phase 200 has been completed and the wireless communication has been established.
- a communication connection 176 is formed as a piconet, with the inquiry scanning device 100 becoming the slave device 100 and the inquiring device 102 becoming the master device 102 in the piconet.
- FIG. 3A is an illustration of an example flow diagram of an example process in the scanning device 100 carrying out the example operations in the device discovery phase shown in FIG. 1A , in accordance with at least one embodiment of the present invention.
- the figure shows an example embodiment of the invention, of the example process in the scanning device 100 in accordance with at least one embodiment of the present invention.
- the steps of the flow diagram 180 represent computer code instructions stored in the RAM and/or ROM memory of the device 100 , which when executed by the central processing units (CPU) 124 and/or 125 , carry out the functions of the example embodiments of the invention.
- the steps may be carried out in another order than shown and individual steps may be combined or separated into component steps.
- the flow diagram has the following steps:
- Step 182 detecting a wireless device discovery message at an apparatus.
- Step 184 in response to detecting the wireless device discovery message, temporarily tuning, by the apparatus, device discovery parameters to increase a rate of detecting wireless device discovery messages.
- FIG. 3B is an illustration of an example flow diagram of an example implementation of the process in the inquiring device 102 , carrying out the example operations in the device discovery phase, in accordance with at least one embodiment of the present invention.
- the figure shows an example embodiment of the invention, of the example process in the inquiring device 102 in accordance with at least one embodiment of the present invention.
- the steps of the flow diagram 190 represent computer code instructions stored in the RAM and/or ROM memory of the device 102 , which when executed by the central processing units (CPU) 124 and/or 125 , carry out the functions of the example embodiments of the invention.
- the steps may be carried out in another order than shown and individual steps may be combined or separated into component steps.
- the flow diagram has the following steps:
- Step 192 transmitting, by an apparatus, wireless signals comprising one or more device discovery messages;
- Step 194 receiving, by the apparatus, one or more response messages from a wireless device, including information usable by the apparatus to estimate a distance to the wireless device, the one or more response messages being received at an increased rate;
- Step 196 estimating, by the apparatus, a distance to the wireless device using the information usable for estimating the distance to the wireless device included in the one or more response messages, the estimation being carried out rapidly based on the increased rate of receipt of the one or more response messages.
- FIG. 3C is an illustration of an example message format for device discovery messages 150 , using the Bluetooth communications standard, in accordance with at least one embodiment of the present invention.
- the inquiring device 102 or master transmits inquiry messages 150 with the general or dedicated inquiry access code.
- the identity or ID packet consists of the inquiry access code (IAC). It has a fixed length of 68 bits.
- IAC inquiry access code
- the inquiring device 102 may enter inquiry substate where it may repeatedly transmits 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).
- LAP Lower Address Part
- GIAC General Inquiry Access Code
- FIG. 3D is an illustration of an example message format for inquiry response messages 158 , using the Bluetooth communications standard, in accordance with at least one embodiment of the present invention.
- An inquiry response packet (FHS) 158 is transmitted from the inquiry scanning device 100 or slave to the master after the slave has received an inquiry message 150 .
- the inquiry response packet 158 contains information necessary for the inquiring device 102 to page the slave and follows 625 microseconds after the receipt of the inquiry message 150 .
- the inquiry response packet 158 is received by the inquiring device 102 at the hop frequency when the inquiry message 150 received by the slave was first in the master-to-slave slot.
- the inquiry scanning device 100 may return an inquiry response (FHS) packet 158 containing the recipient's device address (BD_ADDR) and other parameters. If the recipient has non-zero extended inquiry response data to send, it indicates this by the EIR bit 159 , indicating that it will return an extended inquiry response packet 160 after the FHS packet 158 .
- the slave 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 159 set to zero.
- FHS inquiry response
- BD_ADDR device address
- FIG. 3E is an illustration of an example message format for extended discovery response messages 160 , using the Bluetooth communications standard, in accordance with at least one embodiment of the present invention.
- An Extended Inquiry Response 160 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.
- the inquiring device 102 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.
- SDP service discovery protocol
- the inquiry scanning device 100 transmits an extended inquiry response packet 160 , it is transmitted 1250 microseconds after the start of the inquiry response packet 158 .
- the extended inquiry response packet 160 is received by the inquiring device 102 at the hop frequency when the inquiry message 150 received by the inquiry scanning device 100 was first in the master-to-slave slot.
- FIG. 3F is an illustration of an example message format for communication connection messages 175 , using the Bluetooth communications standard, in accordance with at least one embodiment of the present invention.
- the standard frame format for Bluetooth systems is illustrated in the figure, which shows the packet contents of the Bluetooth frame.
- the function of the access code is to identify the packets exchanged within a piconet, where each piconet has a unique access code.
- the access code is used to synchronize the slaves in a piconet to its master.
- the main function of the header of the Bluetooth packet is to determine an individual slave address in the piconet by the Logical Transport-Address (LT ADDR).
- LT ADDR Logical Transport-Address
- the last part of the Bluetooth frame is the payload.
- Bluetooth has several types of packets.
- Asynchronous Connectionless Communications (ACL) packet payload may be one of two types; medium data rate packets and, high data rate packets.
- ACL Asynchronous Connectionless Communications
- the Bluetooth controller of the scanning device 100 may be tuned to adjust it's inquiry scanning state so that, at least, it is based on whether or not an inquiry packet 150 is received. In this manner, an inquiring device 102 may more quickly receive an inquiry response because more responses are received.
- the implementation includes detection of the inquiry. This may be, for example, based on the received inquiry (ID) packet 150 or by sending the FHS packet 158 or the EIR packet 160 .
- the scanning device 100 tunes its inquiry scanning parameters, such as inquiry scan interval, inquiry scan window or whether to do interlaced/non-interlaced scan.
- the functionality may be implemented into the Bluetooth controller, thus making it most power efficient, or alternately by delivering the inquiry detection occurrence (probably with some conditions) to the host of the scanning device 100 and let the host decide whether to change the inquiry scanning parameters.
- the end of tuning of the scanning device 100 inquiry scanning parameters may have several conditions:
- the enhanced inquiry scan operation of the Bluetooth controller in the scanning device 100 may controlled by the host via HCI interface, by defining new command, editing existing commands or using vendor specific commands.
- the scanning device 100 has only roughly 50% chance to receive inquiry packet 150 from inquiring device 102 during the single scan window, due to inquiring device 102 possibly being on a different FHS sequence than the scanning device 100 (the inquiry hopping sequence is divided over two inquiring FHS sequences A and B of 16 frequencies).
- the inquiry packet 150 is received during next scan interval.
- the standard Bluetooth inquiry scanning device 100 will return to the inquiry scan after 0 to 639,375 ms and responds to inquiry packets until the devices go into different FHS sequences.
- the next inquiry packet 150 is most likely found in the following scan, i.e. after 2.56 s from the last trial.
- the standard Bluetooth first inquiry response 158 is received, most likely, within 5.12 s, and then likely few inquiry responses are received with interval of roughly 5 m to 645 ms until FHS sequence switch happens.
- the next response 158 is then received after 2.56 s from last inquiry scan event.
- the Inquiry scan type is changed to interlaced scan after receiving the first inquiry packet and in addition the scan interval may also be decreased for example to 1.28 s.
- the scan interval may also be decreased for example to 1.28 s.
- the pause typically is at maximum of 1.28 s (+0 to 639,375 ms). Multiples of 1.28 s pauses are present only due to collisions or some other error, not due to protocol constraints like in standard scan.
- the first inquiry response 158 is received most likely within 5.12 s, and then likely many inquiry responses 158 are received with interval of roughly 5 m to 645 ms. If there is a collision or some other errors, the next response 158 is then received after 1.28 s from last inquiry scan event. Thus, long pauses in receiving inquiry responses 158 are eliminated and system works much faster in touch-to-select use cases.
- FIG. 4 illustrates an example embodiment of the invention, wherein examples of removable storage media 126 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.
- SD Secure Digital standard
- the embodiments may be implemented as a machine, process, or article of manufacture by using standard programming and/or engineering techniques to produce programming software, firmware, hardware or any combination thereof.
- 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.
- 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.
- memory/storage devices include, but are not limited to, disks, optical disks, removable memory devices such as smart cards, SIMs, WIMs, semiconductor memories such as RAM, ROM, PROMS, etc.
- Transmitting mediums include, but are not limited to, transmissions via wireless communication networks, the Internet, intranets, telephone/modem-based network communication, hardwired/cabled communication network, satellite communication, and other stationary or mobile network systems/communication links.
Abstract
Description
pathloss=Tx Power Level−RSSI of the inquiry response packet
-
- RSSI of the ID packet exceeds the threshold (only near device)
- Controlled by host (host may have own conditions such as only when backlight on or activate by the user from settings)
- Inquiry parameters are already good enough
- When the last tuning was made
-
- No inquiry received during last x number of inquiry intervals
- Number of sent packets
- Time from the start of the tuning
Claims (18)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/259,577 USRE47488E1 (en) | 2013-01-23 | 2016-09-08 | Method, apparatus, and computer program product for wireless device discovery process |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/747,836 US9258694B2 (en) | 2013-01-23 | 2013-01-23 | Method, apparatus, and computer program product for wireless device discovery process |
US15/259,577 USRE47488E1 (en) | 2013-01-23 | 2016-09-08 | Method, apparatus, and computer program product for wireless device discovery process |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/747,836 Reissue US9258694B2 (en) | 2013-01-23 | 2013-01-23 | Method, apparatus, and computer program product for wireless device discovery process |
Publications (1)
Publication Number | Publication Date |
---|---|
USRE47488E1 true USRE47488E1 (en) | 2019-07-02 |
Family
ID=51208066
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/747,836 Ceased US9258694B2 (en) | 2013-01-23 | 2013-01-23 | Method, apparatus, and computer program product for wireless device discovery process |
US15/259,577 Expired - Fee Related USRE47488E1 (en) | 2013-01-23 | 2016-09-08 | Method, apparatus, and computer program product for wireless device discovery process |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/747,836 Ceased US9258694B2 (en) | 2013-01-23 | 2013-01-23 | Method, apparatus, and computer program product for wireless device discovery process |
Country Status (1)
Country | Link |
---|---|
US (2) | US9258694B2 (en) |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8879993B2 (en) * | 2012-03-30 | 2014-11-04 | Nokia Corporation | Method, apparatus, and computer program product for wireless short-range communication establishment |
US9788288B2 (en) * | 2014-01-13 | 2017-10-10 | Qualcomm Incorporated | Systems and methods for reducing power consumption in wireless communication |
US9753562B2 (en) * | 2014-01-15 | 2017-09-05 | Nokia Technologies Oy | Dynamic threshold for local connectivity setup |
WO2016155989A1 (en) | 2015-04-02 | 2016-10-06 | Telefonaktiebolaget Lm Ericsson (Publ) | A user equipment and a method for link quality determination |
US9565514B2 (en) | 2015-06-12 | 2017-02-07 | Qualcomm Incorporated | Systems and methods for disabling page scans |
KR101673308B1 (en) * | 2015-08-20 | 2016-11-07 | 현대자동차주식회사 | Method And Apparatus For Automatic Bluetooth Connection Using Bluetooth Dual_Mode |
US9949168B2 (en) | 2015-09-24 | 2018-04-17 | Qualcomm Incorporated | Reliable data channel over periodic discovery messages |
US9826387B2 (en) * | 2015-11-04 | 2017-11-21 | Abb Technology Oy | Indicating a drive status in communications |
US9992808B2 (en) | 2015-12-22 | 2018-06-05 | Motorola Mobility Llc | Devices and methods for establishing an ad hoc peer-to-peer network |
CN108990029B (en) * | 2018-05-29 | 2020-08-04 | 阿里巴巴集团控股有限公司 | Scanning start-stop method of wireless equipment and wireless equipment |
Citations (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1187504A2 (en) | 2000-09-11 | 2002-03-13 | Texas Instruments Inc. | Wireless communication channel selection using passive interference avoidance techniques |
US20040042413A1 (en) | 2001-07-30 | 2004-03-04 | Harumi Kawamura | Radio communication system, radio communication control apparatus, radio communication control method,recording medium, and computer program |
EP1418781A1 (en) | 2002-11-11 | 2004-05-12 | Nokia Corporation | Location dependent messaging |
US20040215816A1 (en) | 2002-12-16 | 2004-10-28 | Hayes Stephen T | Apparatus and methods for communication among devices |
WO2005091573A1 (en) | 2004-03-17 | 2005-09-29 | Koninklijke Philips Electronics N.V. | Making time-of-flight measurements in master/slave and ad hoc networks by eavesdropping on messages |
US20050278646A1 (en) | 2004-06-15 | 2005-12-15 | Mitel Networks Corporation | Spontaneous discovery of remote service profiles |
US20060240777A1 (en) | 2005-04-25 | 2006-10-26 | Ruuska Paivi M | Decreasing mutual interference between multiple bluetooth piconets by controlling the channel usage with the help of the adaptive frequency hopping methods |
US20060267794A1 (en) | 2005-05-27 | 2006-11-30 | Lg Electronics Inc. | Encoding and decoding traffic information using encoding fields |
US20070141985A1 (en) | 2005-12-21 | 2007-06-21 | Jukka Parkkinen | Method for closing a communication link |
US20070206660A1 (en) | 2006-03-06 | 2007-09-06 | Texas Instruments Incorporated | Radio frequency collision avoidance mechanism in wireless networks using frequency synchronization |
US20080013502A1 (en) | 2006-02-08 | 2008-01-17 | Clark Alan R | Wireless data bus |
US20080161026A1 (en) | 2007-01-03 | 2008-07-03 | Motorola, Inc. | Expandable text messaging service protocol for use with a two-way radio transceiver |
US20080242220A1 (en) | 2007-03-29 | 2008-10-02 | Research In Motion Limited | Method, system and mobile device for prioritizing a discovered device list |
EP2015274A1 (en) | 2007-07-09 | 2009-01-14 | Alcatel Lucent | A system and related method for appliance control |
US20090320098A1 (en) | 2008-06-19 | 2009-12-24 | Microsoft Corporation | Hosted network device user interface |
US20100105409A1 (en) | 2008-10-27 | 2010-04-29 | Microsoft Corporation | Peer and composite localization for mobile applications |
US20100118736A1 (en) | 2007-01-25 | 2010-05-13 | Kangnung-Wonju National University Industrial Academy | Routing method and wireless network system |
US7775432B2 (en) | 2003-10-16 | 2010-08-17 | Nokia Corporation | Terminal, method and computer program product for interacting with a signaling tag |
WO2010108235A1 (en) | 2009-03-26 | 2010-09-30 | Xped Holdings Pty Ltd | An arrangement for managing wireless communication between devices |
US20110037610A1 (en) | 2009-08-12 | 2011-02-17 | International Business Machines Corporation | Locating computer-controlled entities |
US20110066850A1 (en) | 2009-09-11 | 2011-03-17 | Nokia Corporation | Communication using multiple apparatus identities |
KR20110032370A (en) | 2009-09-22 | 2011-03-30 | 삼성전자주식회사 | Distributed resource allocation method and apparatus for multiple piconet environment |
US20110103428A1 (en) | 2009-10-29 | 2011-05-05 | Avago Technologies Eccbu Ip (Singapore) Pte. Ltd. | Method and device for intelligent frequency hopping in a shared frequency band |
US20110281519A1 (en) | 2010-05-11 | 2011-11-17 | Plantronics, Inc. | Information Exchange Via Bluetooth Service Discovery Protocol Service Records |
WO2012048442A1 (en) | 2010-10-13 | 2012-04-19 | Intel Corporation | Mechanism for proximity detection based on wi-fi signals |
WO2012127095A1 (en) | 2011-03-18 | 2012-09-27 | Nokia Corporation | Non-networked wireless communication |
US20120289159A1 (en) | 2011-05-13 | 2012-11-15 | Nokia Corporation | Multiple apparatus selection via touch |
US20130065584A1 (en) | 2011-09-12 | 2013-03-14 | Microsoft Corporation | Low energy beacon encoding |
US20130138786A1 (en) | 2011-11-29 | 2013-05-30 | At&T Intellectual Property I, Lp | Facilitating virtual personal area networks |
US20130136033A1 (en) * | 2011-11-28 | 2013-05-30 | Abhishek Patil | One-click connect/disconnect feature for wireless devices forming a mesh network |
WO2013083868A1 (en) | 2011-12-07 | 2013-06-13 | Nokia Corporation | Close proximity based event triggering |
US20130165044A1 (en) | 2011-12-22 | 2013-06-27 | Broadcom Corporation | Bluetooth Low Energy Module Systems and Methods |
US20140082185A1 (en) * | 2012-09-19 | 2014-03-20 | Qualcomm Incorporated | Systems and methods for transmitting and receiving discovery messages |
US20140133584A1 (en) * | 2012-11-12 | 2014-05-15 | Mediatek Inc. | Bluetooth device and related communications establishing method |
US20140358685A1 (en) | 2013-06-03 | 2014-12-04 | Google Inc. | Method and System for Providing Sign Data and Sign History |
US20140373100A1 (en) | 2013-06-18 | 2014-12-18 | Google Inc. | NFC Triggered Two Factor Protected Parental Controls |
US20140380159A1 (en) | 2013-06-24 | 2014-12-25 | Sonos, Inc. | Intelligent Amplifier Activation |
US20150135087A1 (en) | 2013-11-08 | 2015-05-14 | Ceruus Oy | User interface for sensor system |
US20150193198A1 (en) | 2014-01-06 | 2015-07-09 | Harman International Industries, Inc. | Apparatus and method for automatic device selection for wireless media devices |
US20150256954A1 (en) | 2014-03-06 | 2015-09-10 | Sony Corporation | Networked speaker system with follow me |
US9158395B2 (en) | 2009-04-02 | 2015-10-13 | Samsung Electronics Co., Ltd | Method and system for controlling other devices using a remote user interface |
US20150304209A1 (en) | 2012-12-18 | 2015-10-22 | Juniper Networks, Inc. | Dynamic control channel establishment for software-defined networks having centralized control |
US20150341876A1 (en) | 2012-10-26 | 2015-11-26 | Qualcomm Incorporated | Systems and methods for synchronization of wireless devices in a peer-to-peer network |
US20150373083A1 (en) | 2012-12-21 | 2015-12-24 | Koninklijke Philips N.V. | Electronic devices for, a system and a method of controlling one of the electronic devices |
US20160072573A1 (en) | 2014-09-10 | 2016-03-10 | Kabushiki Kaisha Toshiba | Communication device, relay device, and, communication method |
-
2013
- 2013-01-23 US US13/747,836 patent/US9258694B2/en not_active Ceased
-
2016
- 2016-09-08 US US15/259,577 patent/USRE47488E1/en not_active Expired - Fee Related
Patent Citations (45)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1187504A2 (en) | 2000-09-11 | 2002-03-13 | Texas Instruments Inc. | Wireless communication channel selection using passive interference avoidance techniques |
US20040042413A1 (en) | 2001-07-30 | 2004-03-04 | Harumi Kawamura | Radio communication system, radio communication control apparatus, radio communication control method,recording medium, and computer program |
EP1418781A1 (en) | 2002-11-11 | 2004-05-12 | Nokia Corporation | Location dependent messaging |
US20040215816A1 (en) | 2002-12-16 | 2004-10-28 | Hayes Stephen T | Apparatus and methods for communication among devices |
US7775432B2 (en) | 2003-10-16 | 2010-08-17 | Nokia Corporation | Terminal, method and computer program product for interacting with a signaling tag |
WO2005091573A1 (en) | 2004-03-17 | 2005-09-29 | Koninklijke Philips Electronics N.V. | Making time-of-flight measurements in master/slave and ad hoc networks by eavesdropping on messages |
US20050278646A1 (en) | 2004-06-15 | 2005-12-15 | Mitel Networks Corporation | Spontaneous discovery of remote service profiles |
US20060240777A1 (en) | 2005-04-25 | 2006-10-26 | Ruuska Paivi M | Decreasing mutual interference between multiple bluetooth piconets by controlling the channel usage with the help of the adaptive frequency hopping methods |
US20060267794A1 (en) | 2005-05-27 | 2006-11-30 | Lg Electronics Inc. | Encoding and decoding traffic information using encoding fields |
US20070141985A1 (en) | 2005-12-21 | 2007-06-21 | Jukka Parkkinen | Method for closing a communication link |
US20080013502A1 (en) | 2006-02-08 | 2008-01-17 | Clark Alan R | Wireless data bus |
US20070206660A1 (en) | 2006-03-06 | 2007-09-06 | Texas Instruments Incorporated | Radio frequency collision avoidance mechanism in wireless networks using frequency synchronization |
US20080161026A1 (en) | 2007-01-03 | 2008-07-03 | Motorola, Inc. | Expandable text messaging service protocol for use with a two-way radio transceiver |
US20100118736A1 (en) | 2007-01-25 | 2010-05-13 | Kangnung-Wonju National University Industrial Academy | Routing method and wireless network system |
US20080242220A1 (en) | 2007-03-29 | 2008-10-02 | Research In Motion Limited | Method, system and mobile device for prioritizing a discovered device list |
EP2015274A1 (en) | 2007-07-09 | 2009-01-14 | Alcatel Lucent | A system and related method for appliance control |
US20090320098A1 (en) | 2008-06-19 | 2009-12-24 | Microsoft Corporation | Hosted network device user interface |
US20100105409A1 (en) | 2008-10-27 | 2010-04-29 | Microsoft Corporation | Peer and composite localization for mobile applications |
WO2010108235A1 (en) | 2009-03-26 | 2010-09-30 | Xped Holdings Pty Ltd | An arrangement for managing wireless communication between devices |
US9158395B2 (en) | 2009-04-02 | 2015-10-13 | Samsung Electronics Co., Ltd | Method and system for controlling other devices using a remote user interface |
US20110037610A1 (en) | 2009-08-12 | 2011-02-17 | International Business Machines Corporation | Locating computer-controlled entities |
US20110066850A1 (en) | 2009-09-11 | 2011-03-17 | Nokia Corporation | Communication using multiple apparatus identities |
KR20110032370A (en) | 2009-09-22 | 2011-03-30 | 삼성전자주식회사 | Distributed resource allocation method and apparatus for multiple piconet environment |
US20110103428A1 (en) | 2009-10-29 | 2011-05-05 | Avago Technologies Eccbu Ip (Singapore) Pte. Ltd. | Method and device for intelligent frequency hopping in a shared frequency band |
US20110281519A1 (en) | 2010-05-11 | 2011-11-17 | Plantronics, Inc. | Information Exchange Via Bluetooth Service Discovery Protocol Service Records |
WO2012048442A1 (en) | 2010-10-13 | 2012-04-19 | Intel Corporation | Mechanism for proximity detection based on wi-fi signals |
WO2012127095A1 (en) | 2011-03-18 | 2012-09-27 | Nokia Corporation | Non-networked wireless communication |
US20120289159A1 (en) | 2011-05-13 | 2012-11-15 | Nokia Corporation | Multiple apparatus selection via touch |
US20130065584A1 (en) | 2011-09-12 | 2013-03-14 | Microsoft Corporation | Low energy beacon encoding |
US20130136033A1 (en) * | 2011-11-28 | 2013-05-30 | Abhishek Patil | One-click connect/disconnect feature for wireless devices forming a mesh network |
US20130138786A1 (en) | 2011-11-29 | 2013-05-30 | At&T Intellectual Property I, Lp | Facilitating virtual personal area networks |
WO2013083868A1 (en) | 2011-12-07 | 2013-06-13 | Nokia Corporation | Close proximity based event triggering |
US20130165044A1 (en) | 2011-12-22 | 2013-06-27 | Broadcom Corporation | Bluetooth Low Energy Module Systems and Methods |
US20140082185A1 (en) * | 2012-09-19 | 2014-03-20 | Qualcomm Incorporated | Systems and methods for transmitting and receiving discovery messages |
US20150341876A1 (en) | 2012-10-26 | 2015-11-26 | Qualcomm Incorporated | Systems and methods for synchronization of wireless devices in a peer-to-peer network |
US20140133584A1 (en) * | 2012-11-12 | 2014-05-15 | Mediatek Inc. | Bluetooth device and related communications establishing method |
US20150304209A1 (en) | 2012-12-18 | 2015-10-22 | Juniper Networks, Inc. | Dynamic control channel establishment for software-defined networks having centralized control |
US20150373083A1 (en) | 2012-12-21 | 2015-12-24 | Koninklijke Philips N.V. | Electronic devices for, a system and a method of controlling one of the electronic devices |
US20140358685A1 (en) | 2013-06-03 | 2014-12-04 | Google Inc. | Method and System for Providing Sign Data and Sign History |
US20140373100A1 (en) | 2013-06-18 | 2014-12-18 | Google Inc. | NFC Triggered Two Factor Protected Parental Controls |
US20140380159A1 (en) | 2013-06-24 | 2014-12-25 | Sonos, Inc. | Intelligent Amplifier Activation |
US20150135087A1 (en) | 2013-11-08 | 2015-05-14 | Ceruus Oy | User interface for sensor system |
US20150193198A1 (en) | 2014-01-06 | 2015-07-09 | Harman International Industries, Inc. | Apparatus and method for automatic device selection for wireless media devices |
US20150256954A1 (en) | 2014-03-06 | 2015-09-10 | Sony Corporation | Networked speaker system with follow me |
US20160072573A1 (en) | 2014-09-10 | 2016-03-10 | Kabushiki Kaisha Toshiba | Communication device, relay device, and, communication method |
Non-Patent Citations (4)
Title |
---|
"Bluetooth Specification version 4.2", Bluetooth SIG, Dec. 2, 2014 (Dec. 2, 2014), XP055359393, Retrieved from the Interernet: URL:https:// www.bluetooth.com/specificatio.ns/adopted-specifications [retrieved on Mar. 28, 2017] * p. 255, paragraph 4.1.4-p. 255, paragraph 4.1.4 *. |
European Search Report completed Apr. 24, 2017 for Application No. EP 17 15 4094. |
Greg Stewart: "Can BLE advertise while being connected ?", TI E2E Community-Bluetooth low energy Forum, Nov. 20, 2014 (Nov. 20, 2014), XP002769355, Retrieved from the Internet: URL:https://e2e.ti.com/support/wireless_connectivity/bluetooth_low_energy/f/538/t/383746 [retrieved on Apr. 19, 2017] * the whole document *. |
Greg Stewart: "Can BLE advertise while being connected ?", TI E2E Community—Bluetooth low energy Forum, Nov. 20, 2014 (Nov. 20, 2014), XP002769355, Retrieved from the Internet: URL:https://e2e.ti.com/support/wireless_connectivity/bluetooth_low_energy/f/538/t/383746 [retrieved on Apr. 19, 2017] * the whole document *. |
Also Published As
Publication number | Publication date |
---|---|
US20140206286A1 (en) | 2014-07-24 |
US9258694B2 (en) | 2016-02-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
USRE47488E1 (en) | Method, apparatus, and computer program product for wireless device discovery process | |
US9635690B2 (en) | Method, apparatus, and computer program product for improving security for wireless communication | |
US9451436B2 (en) | Method, apparatus, and computer program product for wireless device discovery | |
US8879993B2 (en) | Method, apparatus, and computer program product for wireless short-range communication establishment | |
US20150289124A1 (en) | Method, apparatus, and computer program product for seamless switching of communication connection | |
EP2672764B1 (en) | Method, apparatus, and computer program product for wireless short-range communication disconnection | |
US9042829B2 (en) | Method, apparatus, and computer program product for wireless short-range communication | |
US9860297B2 (en) | Method, apparatus, and computer program product for media selection for moving user | |
US9265080B1 (en) | Method, apparatus, and computer program product for multi-device output mode configuration | |
US9338635B2 (en) | Method, apparatus, and computer program product for device tracking | |
CN107105386B (en) | Method, apparatus and computer program product for wireless short-range communication channel selection | |
US20120256726A1 (en) | Method, apparatus, and computer program product for special dedicated inquiry and inquiry response process for dedicated device search | |
EP2922261B1 (en) | A method and technical equipment for short range data transmission | |
KR101396038B1 (en) | System and method for mitigating the effects of interferers while performing conditional device scan | |
US20120196534A1 (en) | Method, apparatus, and computer program product for broadcasting in short-range communication | |
US11032769B2 (en) | Hierarchical wakeup apparatus and method | |
US11310063B2 (en) | Ultra-low power mesh network | |
CN108834121B (en) | Bluetooth device ad hoc network method and system | |
KR101581327B1 (en) | System and method for location awareness of mobile device, and system and method for communication of between mobile devices | |
CN107241763B (en) | Probe response method and device | |
Krohn et al. | SDJS: Efficient statistics in wireless networks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NOKIA TECHNOLOGIES OY;NOKIA SOLUTIONS AND NETWORKS BV;ALCATEL LUCENT SAS;REEL/FRAME:043877/0001 Effective date: 20170912 Owner name: NOKIA USA INC., CALIFORNIA Free format text: SECURITY INTEREST;ASSIGNORS:PROVENANCE ASSET GROUP HOLDINGS, LLC;PROVENANCE ASSET GROUP LLC;REEL/FRAME:043879/0001 Effective date: 20170913 Owner name: CORTLAND CAPITAL MARKET SERVICES, LLC, ILLINOIS Free format text: SECURITY INTEREST;ASSIGNORS:PROVENANCE ASSET GROUP HOLDINGS, LLC;PROVENANCE ASSET GROUP, LLC;REEL/FRAME:043967/0001 Effective date: 20170913 |
|
AS | Assignment |
Owner name: NOKIA US HOLDINGS INC., NEW JERSEY Free format text: ASSIGNMENT AND ASSUMPTION AGREEMENT;ASSIGNOR:NOKIA USA INC.;REEL/FRAME:048370/0682 Effective date: 20181220 |
|
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 |
|
AS | Assignment |
Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKETS SERVICES LLC;REEL/FRAME:058983/0104 Effective date: 20211101 Owner name: PROVENANCE ASSET GROUP HOLDINGS LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CORTLAND CAPITAL MARKETS SERVICES LLC;REEL/FRAME:058983/0104 Effective date: 20211101 Owner name: PROVENANCE ASSET GROUP LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:NOKIA US HOLDINGS INC.;REEL/FRAME:058363/0723 Effective date: 20211129 Owner name: PROVENANCE ASSET GROUP HOLDINGS LLC, CONNECTICUT Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:NOKIA US HOLDINGS INC.;REEL/FRAME:058363/0723 Effective date: 20211129 |
|
AS | Assignment |
Owner name: RPX CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PROVENANCE ASSET GROUP LLC;REEL/FRAME:059352/0001 Effective date: 20211129 |
|
AS | Assignment |
Owner name: BARINGS FINANCE LLC, AS COLLATERAL AGENT, NORTH CAROLINA Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:RPX CORPORATION;REEL/FRAME:063429/0001 Effective date: 20220107 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |