Patent Application
20170289155
This disclosure relates to communications between devices and more particularly to non-persistent communications.
Devices may communicate wirelessly via appropriate apparatus for receiving and transmitting signals. For example, a user may have a communication device such as a smart phone or a laptop and an auxiliary device such as a wearable device connected to each other via a short range link for data communications. The short range link can be provided based on an appropriate short range protocol, for example based on the Bluetooth-protocol. Short range protocols such as the Bluetooth protocol can require the devices to have a persistent connection to be ready for communication of data. To set up a secure persistent connection between the devices, a process known as pairing is needed requiring a user to interact with both devices in a defined sequence of steps. A persistent connection subsequently established can consume considerable amounts of power which typically is not desirable, in particular in portable devices. Persistent connections are also susceptible of connection failures. The user may not even be aware that the persistent connection has failed.
In accordance with an aspect there is provided a method comprising receiving by a device a first broadcast from a broadcasting device, the first broadcast advertising information identifying the broadcasting device, obtaining security information associated with the broadcasting device based on the received broadcast, authenticating the broadcasting device based on the security information, receiving a second broadcast from the broadcasting device, determining that the broadcasting device is an associated device capable of non-connected communications between the devices, and communicating at least one data packet with the broadcasting device subsequent to the second broadcast without establishing a persistent connection between the devices.
In accordance with another aspect there is provided a method comprising sending by a broadcasting device a first broadcast for advertising information identifying the broadcasting device, receiving from a responding device information identifying the responding device, sending security information calculated based on said information identifying the broadcasting device and security information associated with the broadcasting device to associate the broadcasting device with the responding device, sending by the broadcasting device a second broadcast including said information identifying the responding device to confirm completion of the association with the responding device, and communicating at least one data packet with the responding device subsequent to the second broadcast without establishing a persistent connection between the devices.
In accordance with another aspect there is provided an apparatus for a communication device, the apparatus comprising at least one processor, and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, cause the communication device at least to receive a first broadcast from a broadcasting device, the first broadcast advertising information identifying the broadcasting device, obtain security information associated with the broadcasting device based on the received broadcast, authenticate the broadcasting device based on the security information, receive a second broadcast from the broadcasting device, determine that the broadcasting device is an associated device capable of non-connected communications between the devices, and communicate at least one data packet with the broadcasting device subsequent to the second broadcast without establishing a persistent connection between the devices.
In accordance with yet another aspect there is provided an apparatus for a device, the apparatus comprising at least one processor, and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured, with the at least one processor, cause the device at least to send a first broadcast for advertising information identifying the broadcasting device, receive from a responding device information identifying the responding device, send security information calculated based on said information identifying the broadcasting device and security information associated with the broadcasting device to associate the broadcasting device with the responding device, send by the broadcasting device a second broadcast including said information identifying the responding device to confirm the association with the responding device, and communicate at least one data packet with the responding device subsequent to the second broadcast without establishing a persistent connection between the devices.
In accordance with a more detailed aspect the first broadcast comprises information of at least one of an address, universal resource identifier and the model and/or type of the broadcasting device.
Data may be encrypted based on at least one key computed based on said security information associated with the broadcasting device.
The communicating of at least one data packet may comprise communicating data to the broadcasting device in a connection request packet and/or communicating data from the broadcasting device in a further broadcast packet.
The security information associated with the broadcasting device may comprise at least one key. The security information associated with the broadcasting device may be obtained at the device by downloading the security information from a server based on the first broadcast. In the broadcasting device the information can be fetched from an internal storage of the broadcasting device.
In accordance with one specific embodiment information identifying the device is transmitted to the broadcasting device in response to the first broadcast, a first key is calculated based on the obtained security information and information identifying the broadcasting device, the obtained security information comprising a second key available also for the broadcasting device, a third key is communicated from the broadcasting device, in response to determining a match between the first key and the third key, a fourth key is calculated based on the addresses of the device and the broadcasting device and the second key and a fifth key is calculated based on the fourth key and the address of the device, the fifth key is transmitted to the broadcasting device in a request for connection, a successful security association is determined based on receipt of the second broadcast from the broadcasting device, and data encrypt based on the fourth key is transmitted to the broadcasting device.
In accordance with one specific embodiment information a first key is calculated based on a second key available for the broadcasting device and information identifying the broadcasting device and the first key is sent to the responding device, a third key is calculated based on the addresses of the responding and broadcasting devices and the second key, a fourth key is received from the responding device, a fifth key is calculated based on the third key and the address of the responding device, the fourth and the fifth key are compared and in response to a match, determining a successful security association and providing the second broadcast, where after data encrypt based on the third key is communicated from the responding device.
In accordance with one specific embodiment the first broadcast and/or the second broadcast are periodic. Address information for at least one of the devices may be changed periodically and/or randomly.
At least one of the devices can comprise a mobile device provided with a short range radio for short range communications and radio apparatus for accessing a mobile communication system and at least one other of the devices comprises an auxiliary device provided with a short range radio for short range communications with the mobile device.
Short range radio apparatus of at least one of the devices may be switched between on/off states based on predefined criteria.
A device comprising the described apparatus and arranged to implement the embodiments can also be provided. The device may comprise a communication device, for example a mobile user device. The mobile user devices can be a mobile communication device such as a mobile phone, a smart phone, a personal data assistant, a notebook, a tablet computer or a laptop computer. An auxiliary device can comprise a wearable device such as a smart watch, smart eyeglasses or clothing, decorative items or jewelry, for example rings, bracelets, necklaces and pedants with short range communication and data processing capabilities. A system comprising at least one of such device can also be provided.
A computer program comprising program code adapted to perform the herein described methods may also be provided. In accordance with further embodiments apparatus and/or computer program product that can be embodied on a computer readable medium for providing at least one of the above methods is provided.
It should be appreciated that any feature of any aspect may be combined with any other feature of any other aspect.
Embodiments will now be described in further detail, by way of example only, with reference to the following examples and accompanying drawings, in which:
In the following certain illustrative examples for enabling communication between devices in a non-connected mode will be described. Before explaining certain principles and procedures to implement this, a brief explanation of devices that may be used is given with reference to
A user of the communication device 10 may be using at least one auxiliary device also adapted for wireless communications. An example of an auxiliary device is denoted by numeral 20 in
A device can be provided with wireless communication capabilities and appropriate electronic control apparatus for enabling operation thereof in accordance with the herein described principles. The mobile device 10 of
The user may control the operation of the mobile device 10 by means of a suitable user interface such as a control button(s), touch sensitive display screen or pad 12 and/or a key pad, voice commands, combinations of these or the like. A speaker and a microphone are also typically provided. Similarly, the other device 20 can be provided with a display 21 and one or more control buttons 22 and/or other user interface elements, as appropriate depending on the application and features of the device. As shown by
There are various use scenarios where it is desirable for at least two devises of a user to communicate with each other. For example, for a case of a smart phone and a wearable device, e.g. a watch, a user can receive alerts of incoming calls or incoming messages (e.g. short message service (SMS) or multimedia service (MMS) message, emails, alarms, meeting reminders, etc.) on the wearable device. This can be useful in particular when the phone is in a pocket or otherwise out of sight. An auxiliary device may also have a display to show at least a part, e.g. a few characters of the message. A user can also answer/reject an incoming call using the user interface (UI) on the auxiliary device without needing to handle the actual phone unit. For example, answering a call may be done by use of a handsfree headset or a smart watch. User can also set the configuration of the auxiliary device from the phone. For example, information on configurations such as set time, set alarm time, change display mode, etc. may be communicated to the auxiliary device. User can also update the software of the wearable device. In general, the UI on the phone can be used instead of the UI on the wearable device. In addition of the size, better capabilities and more sophisticated functionalities, a user can be more comfortable and familiar in using the UI of the phone than the UI of the auxiliary device.
Devices 10 and 20 may communicate wirelessly over a short range link 1 via appropriate apparatus for receiving and transmitting signals. In
Current short range protocols such as the Bluetooth protocol can require the devices to be in ‘connected’ mode to be able to be ready for communication of data there between. To set up a secure persistent connection between the devices, a process known as pairing has to be completed first. In pairing a user interacts with both devices to complete the pairing process. For example, in accordance with the Bluetooth protocol this requires the user to turn on a Bluetooth low energy (BLE) radio of the wearable device, perform ‘Add a device’ procedure on the phone, authenticate the devices by entering passkey and/or comparing passkeys, and save the paired device for future use (‘bonding’). The Bluetooth pairing process thus requires the user to interact with both devices in a defined sequence and involves several steps. A user may need to attempt this several times before the pairing completes successfully which can be frustrating. A persistent connection can then be set up between the paired devices on a short range link based on the Bluetooth protocol. A persistent connection can consume considerable amounts of power thus reducing the battery lifetime. This is not desirable in particular in portable/small devices with limited battery capacities. Persistent connections between the devices can also suffer from intermittent connection failures, for example because of radio fading due to movement of the user. If the connection fails, the user has to re-connect the devices. The user may not even be aware that the persistent connection has failed which means the user will not get any alerts on the wearable device.
The auxiliary device can broadcast at 100 data based on which at least one key can be determined by a responding device and the device can be associated with at least one other device for close range communications without establishing a persistent close range connection between the devices.
It shall be appreciated that if the operation of both interacting devices is considered on a system level, step 100 of
Also, it shall be appreciated that after the association data may be communicated at 110 in either direction. That is, after the association data can also be communicated from the broadcasting device to the responding device. For example, the broadcasting device can send data such as acknowledgements, reports, user inputs and so forth.
More detailed examples are described in the following with the reference to signaling flows shown in
In accordance with an example the procedure to provide a security association can be executed when a user has bought a new auxiliary device and switches on the device for the first time. For example, the user can switch on the device 20 of
The communication device 10 of the user receives the broadcast. At this stage the user may be given the option to select ‘add a new device’ on his smart phone or other communication device. Alternatively, the broadcasting device is added automatically in the list of devices stored in a memory of the communication device 20. The user can be provided with a message prompting him to download a specific application associated with the device or other information of credentials associated with the device and needed for the association and subsequent communications from an appropriate location. For example, an application can be provided by a server in a cloud computing system accessed based on the broadcast data. The user can then select to save device credentials in the phone.
The association protocol may thus be automatic or be initiated by the user. For example, the user can select ‘add new device’ in response to the phone receiving ‘Broadcast1’ message of
If the device 10 is in a mode where it can receive the broadcast and linking thereof with the broadcasting device is desired, the device 10 can respond with a message including information of its identity. For example, the device 10 can respond the broadcast by sending its Bluetooth address BD_ADDR_P if the linking between the devices is desired. The user can be prompted to obtain further information of the device 20. The further information can be obtained by downloading a company specific application and/or information file. The downloaded information can include predefined security parameter(s) such as a key associated with the device. The information is saved in a record of associated devices in the communication device 10.
In the following examples the surety information comprises a key obtained from a company or other organisation associated with the device 20. In the particular illustrative example this key is referred to as Comp_Key.
In accordance with a possibility a manufacturer of certain devices can provide a common key for a certain group of devices, such as for a particular model or type. In the
Once the communication device 10 has received the Comp_key it can calculate a further key for use in communications between the communication device 10 and device 20. This further key is denoted in this example as P_Key, and is computed:
P_Key=hash(BD_ADDR_D, BD_ADDR_P, Comp_Key),
wherein BD_ADDR_D is a Bluetooth address of the device 20, BD_ADDR_P is a Bluetooth address of the communication device 10, and Comp_key is a key associated with the device 20.
The device 20 receives a scan request message from the communication device including address information of the communication device 10, for example the Bluetooth address BD_ADDR_P.
The device 20 can pre-calculate a verification key. This is D_Key=Hash (BD_ADDR_D, Comp_Key) in the example. The device 20 then sends the D_Key in a Scan_Response message to the communication device 20. The communication device 10 can also calculate a corresponding verification key for the device (e.g. the D_Key) and compare the received key and the calculated key. If the keys match, the communication device 10 calculates and sends a further key, or Conf_Key=Hash(BD_ADDR_P, P_Key) in a connection request message (Conn_request message in
Device 20 also calculates P_Key=Hash(BD_ADDR_D, BD_ADDR_P, Comp_Key) for use in decryption of data from the communication device 10. Device 20 can thus also calculate the further key based on this key. In this example device 20 can thus also compute the Conf_Key=Hash(BD_ADDR_P, P_Key). The device 20, after receiving the Conf_Key in Conn_request message, can compare the received and calculated Conf_Keys, and if there is a match, the device 20 determines the association successful and can use the P_Key for encryption. If there is no match then the device 20 can continue broadcasting of ‘Broadcast1’ packets.
In case of a match the device 20 can alert the user of the association. For example a sound, visual and/or vibrating signal can be given.
The device 20 is now ready to broadcast ‘Broadcast2’ packets. When the communication device 10 receives a ‘Broadcast2’ packet it can treat this as a confirmation of completion of the association procedure. The determination can be based on the change in the type of the broadcast packet or any other appropriate indication. If another ‘Broadcast1’ packet is received, device 10 can determine this to mean that the device 20 is attempting again to become an associated device and that the previous association attempt failed.
The device 20 sends ‘Broadcast2’ packet with BD_ADDR_P. The sending can be periodic, for example once every second according to the Bluetooth protocol. When the phone receives ‘Broadcast2’ packet with BD_ADDR_P it can send in response the calculated Enc_data1 and nounce1 in the shown ‘Conn_Request2’.
The device 20 then receives Enc_Data1 and nounce1 in ‘Conn_Request2’. Enc_Data1 is decrypted using P_Key and nounce1. Thus the device 20 can receive Data1 from the communication device 10 without a need for a persistent connection between the devices.
This procedure can be repeated as many times as needed.
The device can respond to the ‘Scan_request’ packet of
Packets for communication of data are shown in
In the above examples the broadcasting device was provided by an auxiliary device, e.g. a wearable device, and the responding device was provided by a communication device, e.g. a mobile or smart phone. The arrangement can also work other way around, i.e. the auxiliary device can receive broadcasts from a communication device. In this scenario the auxiliary device does not need to constantly transmit anything but can simply listen to periodic transmissions by other devices. The auxiliary device can be switched off when not needed, e.g. when the main communication device is in use, for example in users hand. Switching can be controlled manually or automatically, e.g. based on time, location, or other triggering event. In this scenario power saving can be obtained at the auxiliary device.
In addition to the main device sending data to the auxiliary device data can be communicated in the other direction. For example, the auxiliary device can send acknowledgements or other data in response to receiving anything from the main device. Also, status information such as “battery low”, “update required” and so forth and control commands can be communicated from the auxiliary device. The data can be send e.g. in Broadcast2 messages of
The above describes communications between two devices. However, a device can be associated with more than one device and simultaneously communicate with more than one device. For example, the first broadcast by a broadcasting device can be received by more than one device and more than one device can then request for a scan and in response to confirmed association communicate data with the broadcasting device.
Once the association is completed the communication device 10 can go in a sleep mode as there is no need for constant communications to maintain a connection. The radio thereof can be switched off. If data such as an alert message needs to be sent to the auxiliary device the radio can be switched on and a message including the data can be send to the auxiliary device. In the
In accordance with a further example the main communication device can be configured for selective communication with the auxiliary device. For example, the auxiliary device can be used to provide alerts and/or show messages when the main communication device is out of sight/hand e.g. in a pocket. In such state the main device can transmit data to the auxiliary device to trigger the alerts. However, if the main device is already hi use, e.g. out of pocket and possibly in the hand of the user, the alerts and messages would be provided anyway through the main device, and there might not be a need to send data to the auxiliary device. To avoid unnecessary communications of data the main device can be configured to send the data only when it is in a predefined state/not in use, for example in pocket. This can be determined e.g. based on the display status of the device. When the display screen is on it can be determined that the device is in use and when the display is off it can be determined that it is not in use l in pocket. Other possibilities include detection based on lighting sensors where brightness of light can be used to determine whether the phone is in hand of the user or at least out of pocket, handbag and so forth.
The above described examples may provide certain benefits. For example, need for a persistent connection between the devices can be removed by use of a data protocol that enables communications in a non-connected mode. The data protocol is secure. Certain embodiments also support privacy as a user cannot be associated with constant data that is transmitted by the wearable device. Data protocol can reduce power consumption in wearable device and/or in the main communication device. For example, if assuming total of one hundred messages to the wearable device during one day, a persistent connection with 1 s connection interval would consume power for 86400 transactions during the day compared to one hundred scanning transactions. This can provide considerable power saving, even if allowing for scanning times that are longer than sending data in connected mode. Power saving on the wearable device is comparable between advertising and connection modes for one connection if all advertising channels are used. The power saving is even more when the wearable device is associated with two or more main communication devices. Users may find it easier to control auxiliary devices through the more familiar and typically larger mobile device user interfaces. Also, user may not need to (repeatedly) go through the pairing procedure which some users may find confusing. Instead, a less complex association procedure where only a few messages needs to be exchanged and the devices can stay in non-connected modes can be provided.
It is noted that whilst embodiments have been described using a mobile communication device such as a smart phone and a wearable device such as a smart watch as examples, similar principles can be applied to any other user devices where short range communication between the devices is desired. Therefore, although certain embodiments were described above by way of example with reference to certain exemplifying mobile devices and technologies and uses thereof, the principles can be applied to any other suitable forms of devices, applications and services than those illustrated and described herein.
The required data processing apparatus, functions and circuitry at the relevant devices may be provided by means of one or more data processors and other hardware and software. The described functions may be provided by separate processors or by an integrated processor. The data processing apparatus may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), gate level circuits and processors based on dual-core or multi-core processor architecture, as non-limiting examples. The data processing may be distributed across several data processing modules. A data processor may be provided by means of, for example, at least one chip. Appropriate memory capacity can also be provided in the relevant devices. The memory or memories may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, including appropriate types of random access memory (RAM) and read-only memory (ROM).
In general, the various embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects of the invention may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the invention is not limited thereto. While various aspects of the invention may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, for example for controlling communications, user interface, and data processing, general purpose hardware or controller or other computing devices, or some combination thereof. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD, and a cloud storage arrangement.
As used in this specification, the term circuitry or the like refers to all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and (b) to combinations of circuits and software (and/or firmware), such as (as applicable): (i) to a combination of processor(s) or (ii) to portions of processor(s)/software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (c) to circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that requires software or firmware for operation, even if the software or firmware is not physically present. This definition of circuitry applies to all uses of this term in this specification, including in any claims. As a further example, as used in this specification, the term circuitry also covers an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or applications processor integrated circuit for a mobile device.
The foregoing description has provided by way of exemplary and non-limiting examples a full and informative description of the exemplary embodiment of this invention. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of this invention will still fall within the spirit and scope of this invention as defined in the appended claims. Indeed there is a further embodiment comprising a combination of one or more of any of the other embodiments previously discussed.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/IB2014/064416 | 9/11/2014 | WO | 00 |
