Touch inquiry
Abstract
This record has no abstract on file.
Term
No projected expiry on record.
- Priority
- Filed
- Published
- Today
14 claims: 7 independent, 7 dependent
- 1Patent claims Zastrzeżenia patentowe 1. The method includes:1. Sposób obejmuje: przesyłanie (902) komunikatów wykrywania z urządzenia (100,500);transmitting (902) detection messages from the device (100,500);odbieranie (904) komunikatów odpowiedzi na komunikaty wykrywania, gdzie każdy z komunikatów odpowiedzi zawiera co najmniej pakiet synchronizacji przeskoku częstotliwości zawierający adres urządzenia źródłowego (502,504,506) dla komunikatu odpowiedzi;receiving (904) response messages to detection messages, wherein each of the response messages includes at least a frequency hopping synchronization packet comprising the source device address (502,504,506) for the response message;determining (914) by the device (100,500) whether a predetermined response criterion is met, characterized in that the predetermined response criterion includes receiving multiple response messages from the source device (506) with a measured signal strength at or above a predetermined signal strength level , including the extended query response packet containing additional information about the source device;and if the device (100,500) determines that a predefined response criterion is met, initiating an automatic wireless connection (916) between the device and the source device (506) meeting the predefined response criterion. określanie (914) przez urządzenie (100,500), czy spełnione jest wcześniej określone kryterium odpowiedzi, znamienny tym, że wcześniej określone kryterium odpowiedzi obejmuje odbiór wielu komunikatów odpowiedzi z urządzenia źródłowego (506) o zmierzonej siły sygnału na poziomie lub powyżej wcześniej określonego poziomu siły sygnału, w tym rozszerzony pakiet odpowiedzi na zapytanie zawieraj ący dodatkowe informacje na temat urządzenia źródłowego;i jeśli urządzenie (100,500) ustali, że wcześniej określone kryterium odpowiedzi jest spełnione, zainicjowanie automatycznego nawiązania połączenia bezprzewodowego (916) pomiędzy urządzeniem a urządzeniem źródłowym (506) spełniającym wcześniej określone kryterium odpowiedzi.
- 4The method of any one of the preceding claims further comprising displaying (802) on the device (100,500) an indication that a wireless connection will be established automatically between the device and the source device (506) meeting the predetermined response criterion. 4. Sposób według dowolnego z poprzednich zastrzeżeń obejmujący ponadto wyświetlanie (802) w urządzeniu (100,500) wskazania, że połączenie bezprzewodowe zostanie nawiązane automatycznie między urządzeniem a urządzeniem źródłowym (506) spełniającym wcześniej określone kryterium odpowiedzi.
- 5The method according to any one of the preceding claims, wherein the extended query response packet includes information about the transmission power of the source device (502,504,506). 5. Sposób według dowolnego z poprzednich zastrzeżeń, w którym rozszerzony pakiet odpowiedzi na zapytanie zawiera informację o mocy transmisji urządzenia źródłowego (502,504,506).
- 7A computer program comprising a computer program executable program code configured to cause the method according to any of the preceding claims when the program is run on the computer. 7. Program komputerowy zawierający wykonywalny przez komputer kod programu skonfigurowany tak, że spowoduje wykonanie sposobu według dowolnego z poprzednich zastrzeżeń, gdy program jest uruchamiany na komputerze.
- 9A device (100,500) containing:9. Urządzenie (100.500) zawierające: means for (154, 156) transmitting detection messages;środki do (154,156) przesyłania komunikatów wykrywania;means for receiving (154,156) response messages on detection messages, wherein each of the response messages comprises at least a frequency hopping synchronization packet comprising the source device address (502,504,506) for the response message;środki do odbierania (154,156) komunikatów odpowiedzi na komunikaty wykrywania, gdzie każdy z komunikatów odpowiedzi zawiera co najmniej pakiet synchronizacji przeskoku częstotliwości zawierający adres urządzenia źródłowego (502,504,506) dla komunikatu odpowiedzi;means for determining (102) whether a predetermined response criterion is met, characterized in that the predetermined response criterion comprises receiving a plurality of response messages from the source device (506) with a measured signal strength at or above a predetermined signal strength level, including extended query response package containing additional information about the source device;and means for initiating (154, 156) establishing a wireless connection between the device and the source device meeting the predefined response criterion. środki do określania (102), czy spełnione jest wcześniej określone kryterium odpowiedzi, znamienne tym, że wcześniej określone kryterium odpowiedzi zawiera odbiór wielu komunikatów odpowiedzi z urządzenia źródłowego (506) o zmierzonej sile sygnału na poziomie lub powyżej wcześniej określonego poziomu siły sygnału, w tym rozszerzony pakiet odpowiedzi na zapytanie zawierający dodatkowe informacje na temat urządzenia źródłowego;i środki do inicjowania (154, 156) nawiązania połączenia bezprzewodowego pomiędzy urządzeniem a urządzeniem źródłowym spełniającym wcześniej określone kryterium odpowiedzi.
- 12The device according to any of claims 9-11, also containing:12. Urządzenie według dowolnego z zastrz. 9-11, zawierające ponadto: means for displaying (172) an indication that a wireless connection will be established automatically between the source device and the device (506) meeting the predetermined response criterion. środki do wyświetlania (172) wskazania, że połączenie bezprzewodowe zostanie nawiązane automatycznie między urządzeniem źródłowym a urządzeniem (506) spełniającym wcześniej określone kryterium odpowiedzi.
- 13The device according to any of claims 9-12, wherein the expanded query response packet contains information about the transmission power of the source device (502,504,506). 13. Urządzenie według dowolnego z zastrz. 9-12, przy czym rozszerzony pakiet odpowiedzi na zapytanie zawiera informację o mocy transmisji urządzenia źródłowego (502,504,506).
Independent claims7
72 paragraphs, as filed
[0001] The invention relates to wireless communication, and in particular to facilitating the establishment of wireless connections between closely located devices.
2. Background:
[0002] The ability of wireless communication devices has evolved beyond simply transmitting voice information to include many types of electronic data. For example, emerging devices that support wireless connectivity can exchange text data (e.g., text messages, e-mail messages, etc.), machine-readable data files, multimedia files, area data, Internet-related data such as a website, etc. Electronic data can be transferred through various wireless carriers, for example through long-range cellular architectures, such as: Code Divisional Multiple Access (CDMA), the Global System for Mobile Communications, GSM) etc., via short-range wireless networks, e.g. Bluetooth, wireless LAN (WLAN) etc. or through direct interactions between devices over very short distances, such as in the field of Near Field Communication (NFC).
[0003] Each of the forms of communication available to devices supporting wireless connectivity may have advantages suitable in specific situations. For example, short-range wireless communication can operate in an unregulated band between two or more devices, either directly or through a local master device. Communication carried out through such carriers (e.g. Bluetooth, WLAN, etc.) can have the advantage that localized data transfer can be done relatively quickly with the ability to ensure data integrity and security during transfer. For example, short-range wireless communication may allow peripherals that support wireless connectivity (e.g. keyboards, headsets, etc.) to be used in portable wireless communication devices to improve user experience. Such action may occur alone or together with data (e.g. business card photos, movies, sound files etc.) exchanged between these devices without the need for support from long-range wireless networks, which may not be available in some areas (e.g. indoors) .
[0004] However, in addition to the above-mentioned benefits, short-range wireless communication may also entail some configuration difficulties. Unlike long-range wireless communications, where a fixed configuration profile can be used that can be recognized by every cell in the network, short-range wireless communications may need to be configured on a network-to-network basis. Therefore, users of devices involved in short-range wireless communication must have some knowledge of the configuration procedure for establishing a short-range wireless network connection, and even if the user has the required knowledge, the time and / or effort put into setting up the wireless connection may have a negative impact on the overall user experience.
[0005] Document WO00 / 51293 discloses a method and device for wireless telecommunications, associated with establishing a wireless connection between two communication devices. Registration / authorization data must be exchanged between devices before devices can be connected to each other. This exchange of information is initiated by placing the devices at such a physical distance from each other that the signal transmitted from at least one of the devices is received by the other device with a power level that exceeds the threshold level. A much higher threshold level is selected than the minimum power level required to detect the signal to ensure that the devices are placed very close to each other, and thus allow a clear connection between them.
[0006] WO2007 / 040398 discloses a method of installing a wireless network element. The signal strength of the data packet transmitted between the wireless network element and the further network element is measured. The measured signal strength is used to enable the installation of a wireless network element. Several embodiments are described using the measured signal strength. The method allows quick installation of a reliable connection of a wireless network element, wherein the wireless network element is associated with another network element.
[0007] US2010 / 093280 discloses a method of connecting Bluetooth ™ and a device for detecting and connecting Bluetooth ™ peripherals. The query signal is sent with a minimum transmit power. It is determined whether a query response signal was received while waiting. When multiple query response signals are received during the waiting time, the path loss corresponding to each query response signal is calculated, the calculated path loss is compared and a Bluetooth ™ connection is established with the Bluetooth ™ device that has sent the response signal to the query having the lowest path loss.
SUMMARY [0008] Various embodiments of the invention may be directed to a method, device and computer program product for accelerating the establishment of a wireless connection between devices supporting wireless communication.
[0009] According to a first embodiment, the device is provided with means for transmitting detection messages; means for receiving response messages, each of the response messages comprising at least one frequency hopping synchronization packet comprising the address of the source device; means for determining whether any of the one or more response messages meets a predetermined response criterion, the predetermined response criterion comprises receiving multiple response messages from a source device having a measured signal strength at or above a predetermined signal strength level, including an extended response packet on request, containing additional information about the source device; and means for accelerating the establishment of a wireless connection between the device and the source device meeting the predefined response criteria.
[0010] According to a second embodiment, a method is provided comprising transmitting detection messages from the device; receiving response messages to detection messages, each of the response messages containing at least a frequency hopping synchronization packet comprising the address of the source device; device determination of whether predetermined response criteria are met, a predetermined response criterion includes the receipt of multiple response messages from a source device with a measured signal strength at or above a predetermined signal strength level, including an extended query response packet containing additional information on source device topic; and, if it is determined by the device that a predefined response criterion is met, initiating an automatic wireless connection between the device and the source device meeting the predefined response criteria.
[0011] According to a third embodiment, a computer program product is disclosed adapted to cause the method of the second embodiment to be performed when the program is run on a computer.
[0012] The above summary includes embodiments of this invention that are not intended to be limiting. The above embodiments are only for explaining selected aspects or steps that may be used in the practice of this invention. However, it is clear that one or more aspects or steps relating to an embodiment can be combined with one or more aspects or steps of other embodiments to create new embodiments still within the scope of the invention. Therefore, those of ordinary skill in the art would appreciate that various embodiments of the invention may include aspects of other embodiments, or may be implemented in conjunction with other embodiments.
BRIEF DESCRIPTION OF THE FIGURES [0013] The invention will become more apparent from the following description of various embodiments, in conjunction with the accompanying drawings, in which:
Fig. 1A illustrates example devices, systems, configurations, etc. that can be used in the practice of various embodiments of the invention.
Fig. 1B discloses further details about an exemplary device configuration that can be used when implementing various embodiments of the invention.
Fig. 2 discloses an exemplary tactile action according to at least one embodiment of the invention.
Fig. 3 discloses an example of a user interface display indication, according to at least one embodiment of the invention.
Fig. 4 discloses an example of establishing a connection to a wireless network according to at least one embodiment of the invention.
Fig. 5 discloses an exemplary transmission of an ID packet, according to at least one embodiment of the invention.
Fig. 6 discloses an example of measuring signal strength, according to at least one embodiment of the invention.
Fig. 7 discloses another example of measuring signal strength, according to at least one embodiment of the invention.
Fig. 8 discloses a modified example of a user interface display indication, according to at least one embodiment of the invention.
Fig. 9 discloses a block diagram of an exemplary communication process from a transmission point of view, according to at least one embodiment of the invention.
Fig. 10 discloses a block diagram of an exemplary communication process from a receiving point of view, according to at least one embodiment of the invention.
DESCRIPTION OF EMBODIMENTS [0014] Although the invention has been described below with reference to many embodiments, various changes can be made thereto without departing from the scope of the invention as defined in the appended claims.
I. Example of a system in which embodiments of the invention may be implemented [0015] An example of a system that is useful for implementing various embodiments of the invention is disclosed in Fig. 1A. The system contains elements that can be included or omitted in the configuration depending on, for example, the requirements of the application and hence is not intended to limit the invention in any way.
[0016] The computing device 100 may be, for example, a laptop. Elements that are a basic example of components comprising functional elements in the computing device 100 are disclosed in 102-108. Processor 102 may include one or more devices configured to execute instructions. In at least one scenario, program code execution (e.g. groups of computer executable instructions stored in memory) by the processor 102 may cause the computing device 100 to perform a process, including, for example, method steps that may result in data, events or other output activities. Processor 102 may be a dedicated (e.g., monolithic) microprocessor device or may be part of a complex device, such as ASIC, gate matrix, multi-chip module (MCM, etc.)
[0017] The processor 102 may be electronically coupled to other functional components of the computing device 100 via a wired or wireless bus. For example, the processor 102 may access memory 104 to retrieve stored information (e.g., program code, data, etc.) for use during processing. Memory 104 may generally contain removable or permanent embedded memories (e.g. non-transparent computer-readable storage media) that work in static or dynamic mode. In addition, memory 104 may include read-only memory (ROM), random access memory (RAM), and rewritable memory such as Flash, EPROM, etc. Examples of removable media based on magnetic, electronic and / or optical technologies are shown per 100 I / O in Fig. 1A, and they can serve, for example, as input / output means Input / Output) for 100 computing device. The code may contain any interpreted or compiled computer language, including computer executable instructions. Code and / or data can be used to create program modules, such as operating systems, communication tools, user interfaces, more specialized program modules, etc.
[0018] One or more interfaces 106 may also be coupled to various components of the computing device 100. These interfaces may allow communication between devices (e.g., software or protocol interface), device-device communication (e.g., a wired or wireless communication interface), and even communication devices with the user (e.g. user interface). These interfaces allow components of the computing device 100, other devices and users to interact with the computing device 100. In addition, the interfaces 106 may communicate machine-readable data, e.g., electronic, magnetic and optical signals contained on a computer-readable medium, or may translate user actions into activities that can be understood by computing device 100 (e.g. typing, talking to the receiver on a cell phone, touching an icon on a touch screen device, etc.). Interfaces 106 may further allow processor 102 and / or memory 104 to interact with other modules 108. For example, other modules 108 may include one or more components supporting more specialized functionalities provided by computing device 100.
[0019] The computing device 100 may interact with other devices through various networks, as further shown in Fig. 1A. For example, hub 110 may provide wired and / or wireless support for devices such as computer 114 and server 116. Hub 110 may be further coupled to router 112, which allows devices to interact in a local area network (LAN) with devices in a wide area network (WAN, example, Internet 120). In such a scenario, another router 130 may send information to and receive information from router 112, so that devices on each LAN can communicate. In addition, all the elements shown in this example configuration are not necessary to implement the invention. For example, no additional hub is needed on the LAN supported by router 130 because this functionality may be supported by the router.
[0020] In addition, interaction with remote devices may be supported by various short- and long-range wireless communication providers 140. These providers may use, for example, long-range terrestrial IT cellular systems and satellite communications and / or short-range wireless access points for provide a wireless connection to the Internet 120. For example, PDA
142 (Personal Digital Assistant) and mobile phone 144 can communicate with the computing device 100 via an internet connection provided by the wireless communications provider 140. Similar functionality can be included in devices such as the 146 laptop in the form of hardware resources and / or software configured to allow short and / or long range wireless communication. In addition, any or all of the disclosed devices may engage in direct interaction, e.g., the short range wireless interaction shown between laptop 146 and device 148 supporting wireless connectivity. Exemplary devices 148 supporting wireless connectivity may range from more complex stand-alone devices supporting wireless connectivity to peripheral devices to support functionality in devices such as the laptop 146.
[0021] Further details regarding the exemplary interface element 106 disclosed with reference to the computing device 100 in Fig. 1A are now discussed with reference to Fig. 1B. As previously stated, interfaces 106 may include interfaces for both communicating data to computing device 100 (e.g., as defined in 150) and other interface types 170, including, for example, user interface 172. A representative group of interfaces at the device level were disclosed in 150. For example, multi-radio controller 152 can manage the cooperation of long-range wireless interfaces 154 (e.g., voice cellular data and data), short-range wireless interfaces 156 (e.g., Bluetooth and WLAN), short-range wireless interfaces 158 (e.g., for interactions in which electronic, magnetic, electromagnetic and optical information scanners interpret machine-readable data), 160 wired interfaces (e.g. Ethernet), etc. The exemplary interfaces shown in Fig. 1B are for the purpose of explanation only in this description and are therefore not intended to limit the various embodiments of the invention to the use of any particular interface. Embodiments of this invention may also use interfaces that are not specifically indicated in Fig. 1B.
[0022] Multi-radio controller 152 may manage the operation of some or all of the 154-160 interfaces. For example, the multi-radio controller 152 may prevent interfaces that could interfere with each other at the same time by allocating specific periods in which each interface is allowed to operate. In addition, multi-radio controller 152 may be able to process environmental information, such as detected interference in an operational environment, to select an interface that will be more resistant to interference. These multi-radio control scenarios are not intended to provide an exhaustive list of possible control functions, but only serve as examples of how multi-radio controller 152 may interact with interfaces 154-160 in Fig. 1B.
II. Example of device interaction [0023] The transmission of electronic information is no longer associated with the requirement of prior encoding on physical media for transmission. For example, data can go from creation through distribution to end-user consumption without contacting the game cassette, compact disc (CD), digital video disc (DVD), etc. The removal of physical media as an intermediary has affected the evolution of newly designed electronic devices so that traditional resources used to gain access (e.g., read and / or write) to physical media are disappearing. This evolution has placed a new emphasis on efficiency and ease of use in communication between devices.
[0024] While wired communication can still provide reliable data transfer between stationary devices, users of mobile devices require flexibility without hindrance in the form of cables, physical media, etc. While long-range wireless communication media can direct information between devices, communication does not occur directly between devices (e.g. is guided by the architecture of the cellular base station), which may result in costs for the user for access to the licensed band of the provider, delays caused by indirect routing and traffic in the service provider's network, as well as possible unavailability due to the fact that long-range wireless data networks are not always are available (e.g. indoors). Alternatively, short-range wireless networks can be considered a better solution because they provide relatively fast and secure communication between devices.
[0025] However, short-range wireless communication may require initial configuration. This configuration may include user manipulation of various menus on the device to enable communication modes that allow devices participating in the wireless interaction to obtain communication configuration information needed to access other devices. For example, devices communicating via Bluetooth may initially go through "discovery" and then "pairing" processes, during which participating devices obtain information about device identification, protection, channel hopping, etc., which are useful when accessing other devices. These configuration tasks require time and skill, which may work against the growing expectations of users towards more direct and automatic communication operations when using mobile devices.
III. Example of device interaction [0026] According to at least one embodiment of the invention, an example of wireless interaction is shown in Figure 2 which, from the user's point of view, may be desirable because it greatly simplifies the exchange of information. In the example interfaces shown in Figure 2, two users may want to wirelessly exchange electronic data between their mobile devices. At stage 200, users can "touch" their devices together, which can trigger the occurrence of a certain configuration, and thus lead to short-range wireless communication between devices at stage 202. Touching, at least for the purposes of this disclosure, does not require devices to actually enter physical contact with each other. Holding devices close together for a short time may be sufficient to trigger operations after which these devices can be separated and used within the range of wireless communication regardless of the wireless communication medium used to support the interaction between devices. This wireless interaction can be accomplished using various types of short-range wireless communication. While many wireless communication media are available, the various embodiments disclosed herein use Bluetooth for clarification. The use of Bluetooth in the disclosure is intended to serve only as an example, and therefore other short range wireless communication media may be used in implementing various embodiments.
[0027] Bluetooth is an example of short-range communication technology that was originally intended to replace the cables connecting portable and / or stationary electronic devices, but has developed, facilitating more general wireless communication between different devices. Some of the key features of Bluetooth are reliability, low power consumption and low cost. Many of the features set out in the main Bluetooth technology description are optional, enabling product differentiation. Existing Bluetooth interactions are based on the method of querying for device detection, whereby the device asks for other devices within the transmission range, and other devices interested in interacting with the querying device respond to the query. More specifically, the device performing the query by scanning is detectable, i.e. it can respond to query packets sent from other devices in the query state (e.g., trying to find discoverable devices). The polling device and all answering devices can then proceed to create a wireless network (e.g., a Bluetooth piconet) through which the devices interact.
[0028] During the query process, when the lower level communication control resources in the interrogator receive a response from another device, for example a frequency hopping synchronization (FHS) packet, "found" devices are usually reported to the host (e.g. higher level processing resources on the interrogator). Although many response messages can be received from each corresponding device, it is recommended that the driver only report each device to the host once. An exemplary user interface (UI) work for this process is disclosed in Figure 3. In UI 300, the query process has only just begun and two devices responded. In the UI 300, the query process is completed and all corresponding devices are displayed in the list, with each device responding to the query being listed only once.
[0029] According to various embodiments of the invention, there may be a utility problem that may impede the implementation of a touch system in which all devices within the range of the questioning device can answer the query. Given the existing operations, the user of the questioning device would then have to recognize which answering device is intended for tactile work by confirming its name on the list, for example in UI 302. Identification may not be easy for the user because, for example, two or more corresponding devices may have the same default name (e.g. the manufacturer's device name that has not been changed by the user) or the user of the query device is not the owner of the target device ( e.g. as in the example in Fig. 2, where the second device in touch operation is owned by another user). The user of the query device will then be forced to ask the user of the other device for the name of the target device, which may not be known to many users.
[0030] In an existing solution to this problem, the interrogator can measure the signal strength (e.g., Received Signal Strength Indication, or RSSI) of each response message that can be used to order the corresponding devices in UI 302, so that the device with the highest measured signal strength is listed first (e.g. where the measured signal strength may correlate with the distance between the interrogator and the corresponding devices). However, this solution does not provide reliable results because the measurement is limited to the first receipt of a response message (e.g. due to the fact that only one response is recorded for each device), and therefore the list in UI 302 may be inaccurate for moving devices such as shown in the touch example in Fig. 2. Furthermore, it may happen that due to the irregularity of the wireless communication medium, the signal strength of a single transmission may cause erroneous results. Another possible solution may be the implementation of other forms of wireless interaction having a substantially shorter transmission range, such as radio frequency (RF) or infrared (IR) communication, whereby communication via a secondary shorter wireless medium may serve as an indicator that the devices are in touch range. However, the obvious obstacle to implementing this approach is that hardware / software resources must be implemented to support the second form of wireless interaction using space, power and processing that are limited in mobile devices.
IV. Tactile Implementation Example [0031] Various embodiments of the invention do not have the above deficiencies, and thus may enable continuous detection of touch operations between devices within a single wireless communication carrier. Touch operations, in at least one embodiment, can detect when devices are held or moved closer to each other and can cause automatic wireless connection between the only devices that are a short distance away. In particular, the features available in the Bluetooth 4.0 Specification may be used because of the extended query response (EIR), in which EIR responses are repeatedly reported to the host during query scanning. These features can also be enabled for devices not configured to send EIR packets, requesting that these devices be reported to the host more than once, which is allowed in the specification but is usually not implemented.
[0032] In the Bluetooth example, the interrogating devices send ID packets that can be scanned by discoverable devices. Discoverable devices can then respond to ID packets by sending an FHS packet. The detectable devices may further send an ESP packet after the FHS packet to provide additional information including, for example, device name, transmission power (Tx) etc. An example of wireless interaction is shown in Figure 4. The default Bluetooth query scan time is 11.25 ms when performing a standard scan and 22.5 ms when performing interlaced scan. The default value of the query scan interval is 2.56 s. In the example in Fig. 4, the time interval for the master to slave device can be 625 μs, and the total time interval for master to slave and slave to master can be 1250 μs. The query can be implemented to find discoverable devices within the transmission range. Devices in discovery mode that receive packets with an inquiry (e.g. ID packets, typically with a duration of 68 μs) can send a response containing an FHS packet. The FHS packet may contain at least a Bluetooth address, device class, information on whether an EIR response occurs, page scan mode and clock phase. Clock offset and address information can be used by interrogators to estimate channel, hop (k) information, so that communication can be continued on subsequent channels, hop (f + k) in accordance with the frequency hop pattern. An estimation of the hop pattern information may allow the interrogator to follow the hopping of the corresponding device to establish a network connection with the corresponding device.
[0033] The EIR procedure can also be performed by devices responding to the query. The extended query response procedure may include the transmission of an EIR packet, which may contain various information in addition to that provided in the basic query response (e.g., in the FHS packet). An EIR packet may generally contain information about, for example, the services offered by the device or about a particular service provider. An upcoming EIR packet transmission may be indicated by an EIR pointer bit that is set in the FHS packet. For example, device discovery can be accelerated by not sending user-friendly names in FHS packets, and therefore, to show the user-friendly name of the discovered device, it must be provided in the EIR packet (e.g., except when the Bluetooth address is already assigned to user-friendly names in the device's memory). If the FHS packet indicates that it is followed by an EIR packet (e.g., the EIR bit is set), the transmission of the EIR packet may begin in the next slave to master range and may extend to up to five (5) intervals. EIR packets are asynchronous connectionless (ACL) packets of the DM1, DM3, DM5, DH1, DH3 or DH5 type.
[0034] Some behaviors may be embedded in devices to facilitate detection. For example, to avoid repetitive collisions between devices that are simultaneously waking up on the same hop request channel, the device should retreat for a random time. Therefore, if the device receives an ID packet and responds by sending an FHS packet, it should generate a random number, RAND, between 0 and MAX_RAND. MAX_RAND can be 1023 for scan intervals> 1.28 s. For scan intervals <1.28 s, MAX_RAND can be as low as 127. Profiles with a special DIAC code can select MAX_RAND> 1023, even when the scan interval is> 1.28 s. Detectable devices can return to CONNECTION (connections) or STANDBY for at least RAND time intervals. Before returning to CONNECTION or STANDBY, the machine may go through the page scan sub status.
[0035] At least after the RAND time interval, the detectable device must add a "1" offset to the phase in the query hopping sequence (eg, the phase has a resolution of 1.28 s) and then return to query or sub-state scanning again. If a detectable device is called again, it must repeat the procedure using the new RAND. A clock offset is collected whenever an FHS packet is returned. During the sampling window, the detectable device may respond many times, but at different frequencies and at different times. Reserved synchronous intervals should have priority over response packets, but if the response packet overlaps with the reserved synchronous interval, it should not be sent, but wait for the next query message. If the device has EIR data to transfer, but the EIR packet overlaps with the reserved synchronous interval, the FHS packet can be sent with the EIR bit set to zero according to the Bluetooth v4.0 specification, which was enabled as a reference.
[0036] In light of the above, the reply to the query can be received by the interrogating device within approximately 80 to 640 ms, depending on the scan interval of the detected devices. Random delay for devices using the scan interval <1.28 s is from 0 to 79 375 ms, and for other devices (e.g. using the default query interval) is from 0 to 639 375 ms. In light of these operational characteristics, to collect responses from all devices within the communication range in an ideal (e.g. error-free) environment, the sub-state test can last 10.24 s, unless the interrogating device receives enough responses and interrupts the sub-state of the query earlier . In some cases (e.g. in an error-prone environment), the interrogating device can also extend the sub-status of the query to increase the likelihood of receiving all responses. Due to the extended state of the query and the relatively short delay time, many responses may be received from some or all of the corresponding devices.
As mentioned above, the latest Bluetooth specification includes functions that can be used, according to at least one embodiment of the invention. For example, in chapter 7.1.1 of the Bluetooth v4.0 specification entitled "Command
Inquiries "(Inquiry Command) stated that" A device that responds during a query or query period should always be reported to the Host as part of the Inquiry Result event if the device was not previously reported in during the current query or query period and the device has not been filtered using the Set_Event_Filter command. If the device was reported earlier during the inquiry or the inquiry period, it may or may not be reported depending on the implementation (depending on whether previous results were saved in the BR / EDR controller and in this case how many answers were saved). It is recommended that the BR / EDR driver attempt to report a specific device only once during a query or query period. When reporting detected devices to the host, the RSSI parameter measured during the FHS packet by any corresponding device may be returned. " In addition, in Chapter 7.7.38 entitled "Extended Inquiry Result Event" it was stated: "... If an extended query response packet from the same device is correctly received in a later reply, another should be generated happening". Thus, the lower-level communication driver can generate events for each received EIR packet, regardless of whether the query response has already been reported. It is the continuous generation of events that can prove beneficial to the implementation of automated communication configuration and connection in various example implementations.
[0038] For example, four devices 500-506 may be in communication range with each other, as shown in Fig. 5. All devices 500-506 may be able to communicate using the same wireless communication medium (e.g., Bluetooth). In the example application scenario, the user of the device 500 may want to exchange data (e.g. business cards, photos, music, multimedia files, etc.) with the device 506. The device 500 can then go into query mode in which ID packets are sent. The ID packet can be a general inquiry access code packets (GIAC) or DIAC packet. Devices 502-506 can then receive these ID packets.
[0039] In Figure 6, devices 502-506 may send packets corresponding to the ID packets received in Figure 5. In particular, devices 502 and 506 may send EIR (e.g., FHS packet, followed by EIR packet), while device 504 may send only an inquiry response (IR) containing only the FHS package. Host at device 500 can receive EIR events caused by device responses 502 and 506, but not 504. According to at least one embodiment of the invention, this lack of EIR event reporting for device 504 can be used as a pre-filter excluding device 504 as a potential touch device (e.g., devices that do not send EIR packets are not touch devices). It is important to note, however, that other embodiments of the invention may be configured for devices that are not capable of sending EIR packets. A system in which no EIR response is used as a filter is just one example.
[0040] Reported EIR events may include RSSI measurement values, as shown, for example, for devices 502 and 506. Based on the RSSI values, the host in device 500 can detect when the device is most animated in "touch range" (e.g. at a distance from the interrogating device that indicates that touch operations should be performed). For example, there may be pre-defined response criteria, containing one or more events indicating that the device is in touch, are required to check if the device is located close enough.
[0041] It may also be possible to determine when the devices are moved closer to another device to "touch" the devices or, alternatively, when the interrogating device is moved closer to the other devices. The first example is shown in Fig. 7. In the disclosed example, the Bluetooth driver in the device 500 may receive multiple query responses from devices 502 to 506. The response from the 504 device does not contain EIR, so the Bluetooth driver can only report the first of many responses to the host software stack as the HCI Query Event, which may contain the RSSI value of the received response. This may enable the device 500 to respond in a "standard" manner, the device being displayed in UI 302 in an order depending on the strength of the RSSI signal. In cases where EIR responses are received (e.g. from devices 502 and 506), the Bluetooth controller may report any EIR response received as an EIR HCI event. This becomes important when the device 506 in Fig. 7 is moved closer to the device 500. Since the controller also reports RSSI for each EIR response, it is easy to track changes in the RSSI level and the movement of the device 506. When the measured RSSI strength meets predetermined response criteria (e.g. the measured RSSI strength is at or above a certain level), the appropriate device can be selected for touch operations (e.g. accelerated connection establishment). According to at least one embodiment of the invention, information from the device sensor (e.g., motion or acceleration sensors in the device) can be used to determine when, for example, the interrogating device has stopped moving, which may indicate in the device when touch measurement can be started (e.g. . when the user of the device has stopped moving it towards the other device to contact both devices). Devices having a sufficiently high RSSI value in this position can be selected for touch related processing.
[0042] In Fig. 7, the device 500 is a questioning device. Devices 502 and 506 provide EIR responses, and device \ 504 provides normal IR responses. The BT device driver 500 reports these responses to its host, which also has touch selection software running. Typical response criteria, as shown in Fig. 7, occur when RSSI values are expected to exceed a certain predetermined threshold, e.g. -30 dBm. Detection of a -30 dBm response packet will then trigger device selection, while at -31 dBm this will not happen. There is also the possibility that the corresponding devices may send Tx power information in the EIR packet, because there is such a feature in the Bluetooth v4.0 specification. In cases where Tx power information is available in the EIR packet, predefined response criteria may include an adjustable RSSI threshold that takes into account the Tx power. For example, the threshold value can be set at 30 dBm below the Tx EIR power, so that if the Tx power level in the FHS package is +20 dBm, the threshold value that will cause the selection will be a FHS package with a measured value of -10 dBm, or 30 dBm below the Tx power level. Second, to ensure that devices are placed in close proximity, predefined response criteria may require that more than one EIR response contain the detected RSSI strength for the corresponding FHS packet with a threshold value above or above it. In addition, different thresholds may be used in different phases, for example, the threshold may first be set above 45 dBm, to select one or more devices as candidates, and then finally the critical threshold may be set above -30 dBm.
[0043] Another filtering agent for selecting touch operation devices may be based on the services available in the corresponding device. For example, EIR packets may contain service level information, so that only responses above a certain measured signal strength level and from a device (or devices) supporting some types of BT services (e.g. RSSI above -30 dBm and with supported OBEX file transfer) may be selected for touch operations. Multiple devices (e.g., two devices next to each other) can be selected, which causes an accelerated connection between the interrogating device and the two devices selected. It is also possible to select multiple devices by touching them one after the other, with all addresses meeting pre-defined response criteria (e.g. having RSSI above the threshold) can be selected in a specific order. Thus, you can easily choose a distribution group containing more than one device.
[0044] For the responding device it may also be important to make sure that the interrogating device is placed in touch range and not another device that is far away to ensure that communication is established with the desired device. There are several options for checking tactile proximity. The connection between devices can be created after touching and checking by the corresponding device whether the RSSI level meets the criteria of a device placed in close proximity. The responding device may use a command specified by its provider that provides RSSI information for a given connection. If the criteria are met, this data can be accepted from the interrogating device, otherwise the connection can be refused. Operating with this type of check may cause delays in the process of establishing a connection, because the devices must be close to each other at all times. The corresponding device equipped for touch operations may also be configured to measure the RSSI values of all received ID packets in certain cases (e.g. when touch mode is active). The presence of this information at the beginning will speed up this process because the connection does not have to be established before checking the RSSI value of the ID packets received from the given query device (e.g. the responding device does not send reply messages to the given interrogating device). According to at least one embodiment of the invention, the touch mode may be initiated by the movement of touching devices. In particular, movement can be recorded by an acceleration sensor that can activate touch mode by performing steps such as activating Bluetooth on the device and switching the device into visible Bluetooth pairing mode for a specified period of time (e.g. 10 s). The interrogating device may then forward the ID packets received by the responding device that accepts the connection (e.g., if it is determined that it meets the predefined response criteria).
[0045] Fig. 8 is an example of user interface response according to at least one embodiment of the invention. As in Figure 3, UI 800 displays the start of the query process when information is first received by the interrogating device. Some of the corresponding response devices (e.g. "Nokia N900" and "x61s") are already detected and displayed by the user at this stage. A touch device has been identified in UI 802. According to previously disclosed embodiments, certain information was determined in the interrogating device, which led to the finding that the corresponding "Nokia N900" device meets the predefined response criteria, which resulted in that the device was selected for touch operations. In this example, touch operations include the accelerated connection set up in UI 802, in which the user is presented with an indication that the "Nokia N900" will be automatically connected to the interrogating device within 4 seconds. It should be noted that the UI 802 and the specific indications given therein are for the purpose of explaining the invention only. Various embodiments of the invention are not specifically limited to the operations illustrated in Fig. 8, and therefore other activities related to establishing a wireless connection between two or more devices may also be implemented as a result of determining that the corresponding device meets the predefined response criteria.
[0046] A block diagram of an exemplary process from the point of view of an interrogating device according to at least one embodiment of the invention is shown in Fig. 9. The process may be initiated at step 900, followed by packet transmission from the device, the detection packets being (e.g. ID packs for devices using Bluetooth communication). The process may then proceed to step 904, where it may be determined whether any initial responses have been received from other devices (e.g., FHS packets for Bluetooth). If no FHS packets are received at the device, the process may continue sending ID packets and checking responses at steps 902-904 until it is determined that a stop condition exists at step 906. The stop condition may be, for example, the query period, the number of ID messages sent, the state of the device (e.g. power level), etc. If it is determined at step 906 that a stop condition exists, the process may be ended at step 908 and reinitialized at stage 900.
[0047] If it is determined at step 904 that an FHS packet has been received, the process may proceed to step 910, where further determinations may be made as to whether an extended response has been received (e.g., an EIR packet in the case of Bluetooth). If it is determined at step 910 that no EIR packets have been received, the device may perform the standard identification and operation of the device in accordance with the wireless communication medium used. In the case of Bluetooth, such identification and handling may include identifying device-relevant information corresponding to FHS responses in the user interface, and possibly displaying the device in the user interface in the order determined by the signal strength (e.g., RSSI) measured for the FHS packet. The process may then return to step 906 to perform the forwarding and receiving steps 902904 until it is determined that there is a stop condition at which the process can be completed at step 908.
[0048] Alternatively, if it is determined at step 910 that an EIR packet has been received, the process may proceed to step 914, where it can be further determined whether the response comprising the EIR packet meets the predefined response criteria. For example, predefined response criteria may include measured signal strength (e.g. RSSI) at a predetermined level or above it for an FHS packet corresponding to at least one received EIR packet, which may possibly be assessed together with offering some services, etc. If it is determined at step 914 that the response containing the EIR packet does not meet the pre-defined criteria In response, the process may return to step 912 for standard device identification and operation. Otherwise, the process may proceed to step 916, at which "tactile" identification and operation of the device may be performed. For example, the devices designated for touch operations at step 916 may be specified for the user in the user interface of the device as touch devices that will automatically be coupled to the device, followed by proper accelerated connection between the device and the corresponding device according to the EIR packet response which meets the pre-defined response criteria. Processing may then proceed to step 918, where it may be determined whether a device has a stop condition similar to step 906. At step 908, there may be one additional stop condition stating that at least one other device is coupled to the device via touch operation. If it is determined at step 918 that there is a stop condition, the process may be terminated again at step 908 and re-initiated at step 900. Otherwise, the process may return to step 902 for additional transmission of the ID packet.
[0049] A block diagram of another exemplary process from the viewpoint of the corresponding device, according to at least one embodiment of the invention, is shown in Figure 10. The process may be initiated at step 1000, followed by initiation of touch mode on the device at optional step 1002. Step 1002 may be optional so that software related to touch operations can always be active on the device (e.g. as a background service). Alternatively, the initiation of touch mode at step 1002 may occur manually (e.g., in a manner configured by the user in the device user interface) or by actions detected by the sensors in the device. For example, specific motion can be detected by motion sensors in the device, some type of acceleration can be detected by the acceleration sensor, some orientation of the device can be detected by the gyroscope, etc. Activating touch mode can initiate touch-related software, as well as activating the resources of the wireless communication medium (e.g. activating Bluetooth on the device, as well as enabling the visibility of the device to establish a connection).
[0050] The process may then proceed to step 1004, where it can be determined whether messages have been received at the device (e.g., detection packets sent from another device). If it is determined at step 1004 that messages have not been received, the process may proceed to step 1006, where it may be further determined whether there is a stop condition. The condition for stopping may be, for example, a predetermined listening time, device status (e.g. power level) etc. If it is determined that a stop condition exists, then the process can be terminated at step 1008 and reinitialized at step 1000. Otherwise, the process can return to step 1004 until it is determined that the message has been received. After determining that the message has been received, the process can proceed to step 1010, where it can be further determined whether the message meets the predetermined criteria. Predefined criteria may include, for example, measured signal strength (RSSI) for a message received at step 1004 at a predetermined strength level or above it. If at step 1010 the received message does not meet the predefined criteria, the process may return to steps 1002-1006 to wait for additional messages to be received.
[0051] Alternatively, if it is determined at step 1010 that the message meets the predetermined criteria, the process may proceed to step 1012, at which "tactile" identification and operation of the device may be performed. The tactile identification and operation of the device may include, for example, accelerated connection with the interrogating device (e.g., the device that sent the message received at step 1004). The process can then end at step 1008 and be reinitiated at step 1000.
[0052] Various embodiments of the invention are not limited to the actions disclosed above and may include other configurations or implementations.
[0053] For example, embodiments of the invention may include a device comprising means for transmitting detection messages, means for receiving one or more messages corresponding to invitation messages, means for determining whether any of one or more response messages meets predetermined response criteria, and means to, if the device determines that any of one or more response messages meets a predetermined response criteria, an accelerated wireless connection between the device and the source device for each of the one or more response messages that meet the predetermined criteria.
[0054] At least one other embodiment of the invention may include a device comprising means for activating the touch mode, means for receiving a message from at least one other device, means for determining whether the message meets predetermined criteria, and means for, if the device determines, that the message meets the pre-defined criteria for accelerated wireless connection between the device and at least one other device.
[0055] At least one other embodiment of the invention may include electronic signals that cause the device to send detection messages, receive one or more messages responding to invitation messages, determine whether any of one or more response messages meet predetermined criteria answers, and if the device determines that any of one or more response messages meets the predefined response criteria, accelerates the establishment of a wireless connection between the device and the source device for each of the one or more response messages that meet the predefined criteria.
[0056] At least one other embodiment of the invention may include electronic signals that cause the device to activate the touch mode, receive a message from at least one other device, determine whether the message meets predetermined criteria, and if the device determines that the message fulfills earlier specified criteria, speeds up establishing a wireless connection between the device and one or more other devices.
[0057] Accordingly, it will be apparent to those skilled in the relevant art that various changes can be made to the form and details of the invention without departing from the scope of the invention. The width and scope of the invention should not be limited by any of the embodiments described above, but should only be determined according to the following claims and their equivalents.
Magdalena Pietrosiuk Patent Attorney
31 members in 11 offices
Priority claims5
| Document | Office | Kind | Date |
|---|---|---|---|
| 201113107145 | United States of America | A | |
| 201113107145 | United States of America | A | |
| 12166717 | European Patent Office (EPO) | A | |
| EP20120166717 | – | – | – |
| US201113107145 | – | – | – |
Members31
| Document | Office | Kind | |
|---|---|---|---|
| CA2775268A1 | Canada | A1 | |
| EP2523481A1 | European Patent Office (EPO) | A1 | |
| EP2523482A1 | European Patent Office (EPO) | A1 | |
| US2012289157A1 | United States of America | A1 | |
| US2012289158A1 | United States of America | A1 | |
| US2012289159A1 | United States of America | A1 | |
| US2012289160A1 | United States of America | A1 | |
| CN102791043A | China | A | |
| WO2012156578A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2012156580A1 | World Intellectual Property Organization (WIPO) | A1 | |
| SG185886A1 | Singapore | A1 | |
| CN102869036A | China | A | |
| RU2012119001A | Russian Federation | A | |
| CN103518417A | China | A | |
| ZA201203437B | South Africa | B | |
| RU2516482C2 | Russian Federation | C2 | |
| US8929816B2 | United States of America | B2 | |
| US8929817B2 | United States of America | B2 | |
| US8965285B2 | United States of America | B2 | |
| US8965286B2 | United States of America | B2 | |
| CN102869036B | China | B | |
| US2015156739A1 | United States of America | A1 | |
| EP2523482B1 | European Patent Office (EPO) | B1 | |
| EP2523481B1 | European Patent Office (EPO) | B1 | |
| ES2547807T3 | Spain | T3 | |
| PL2523481T3This record | Poland | T3 | |
| MY157333A | Malaysia | A | |
| CN102791043B | China | B | |
| CA2775268C | Canada | C | |
| US9603112B2 | United States of America | B2 | |
| CN103518417B | China | B |
Numbers
- Publication, DOCDB
- 2523481
- Publication, EPODOC
- PL2523481T
- Application
- 166717
- Application, DOCDB
- 12166717
- Application, EPODOC
- PL20120166717T
Titles2
- English
- TOUCH INQUIRY
- Polish
- Zapytanie dotykowe
Classification
- CPC, 5
- H04W56/002
- H04W4/80
- H04W76/14
- H04W8/24
- H04W72/0473
- IPC, 2
- H04W8 00
- H04W4 80