TECHNICAL FIELD

The present embodiments relate to establishment and verification of connections between devices, such as for example robots, autonomously or un-autonomously moving physical platforms, or other objects. The present embodiments may further relate to gesture recognition, approach recognition, contact detection, smart wearables, industrial object control, gaming, and/or automatic data processing.

BACKGROUND

[0001] Real time tracking of objects is a key technology in many fields and various technologies. Different technologies and methods may be used for tracking objects in relatively small circle or restricted space with high resolution. Satellite communications, satellite positioning systems (GPS), radio frequency devices in general, and technologies such as Bluetooth, near field communication (NFC) and zig-bee may be used for real time tracking of objects. There are diverse fields of applications that benefit from tracking objects in space and mapping their presence with respect to other objects in their near vicinity.

SUMMARY

[0002] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. [0003] It is an object to provide a method, apparatus, and computer program for verifying a greeting event between two devices or a plurality of devices. The object is achieved by the features of the independent claims. Further implementation forms are provided in the dependent claims, the description and the figures.

[0004] According to a first aspect, an apparatus comprises means for detecting at least one other apparatus in vicinity of the apparatus; means for detecting an event, wherein the event comprises a first event associated with the apparatus and a second event associated with the at least one other apparatus; means for determining whether at least one characteristic of the first event corresponds to at least one characteristic of the second event; and means for providing a verification of the event in response to determining that the at least one characteristic of the first event corresponds to the at least one characteristic of the second event.

[0005] According to a second aspect, a method comprises: detecting at least one other apparatus in vicinity of the apparatus; detecting an event, wherein the event comprises a first event associated with the apparatus and a second event associated with the at least one other apparatus; determining whether at least one characteristic of the first event corresponds to at least one characteristic of the second event; and determining to verify the event in response to determining that the at least one characteristic of the first event corresponds to the at least one characteristic of the second event.

[0006] According to a third aspect, a computer program product is provided, comprising program code configured to cause an apparatus to perform a method according to the second aspect, when the program code is executed by the apparatus .

[0007] Many of the attendant features will be more readily appreciated as they become better understood by reference to the following detailed description considered in connection with the accompanying drawings.

DESCRIPTION OF THE DRAWINGS

[0008] The present description will be better understood from the following detailed description read in light of the accompanying drawings, wherein:

[0009] FIG. 1 illustrates examples of schematic diagrams of a first apparatus and a second apparatus, according to an embodiment;

[001 0] FIG. 2 illustrates an example of a received radio signal strength when two devices approach, according to an embodiment;

[001 1] FIG. 3 illustrates an example of motion sensor signals associated with a high five greeting gesture at an apparatus, according to an embodiment.

[001 2] FIG. 4 illustrates an example of motion sensor signals associated with a high five greeting gesture at another apparatus, according to an embodiment.

[001 3] FIG. 5 illustrates an example of motion sensor signals associated with a handshaking gesture at an apparatus, according to an embodiment.

[001 4] FIG. 6 illustrates an example of motion sensor signals associated with a handshaking gesture at another apparatus, according to an embodiment.

[001 5] FIG. 7 illustrates an example of a method for launching a handshake activity, according to an embodiment . [001 6] FIG. 8 illustrates a method for providing verification of an event, according to an embodiment.

[001 7] Like references are used to designate like parts in the accompanying drawings.

DETAILED DESCRIPTION

[001 8] The detailed description provided below in connection with the appended drawings is intended as a description of the embodiments and is not intended to represent the only forms in which the embodiment may be constructed or utilized. However, the same or equivalent functions and structures may be accomplished by different embodiments.

[001 9] An objective of the embodiments is to provide a reliable, fast, low-energy consuming, and low-cost method to enable approach detection and verification of physical rendezvous of two or more objects. The rendezvous may involve for example handshaking, a 'high- five' greeting, or any other predetermined gestures. Example embodiments provide an approach-and-gesture type rendezvous that may enable control or feedback of an external object, for example a computer.

[0020] The object is achieved by providing an apparatus, a method, and a computer program to verify physical rendezvous, for example handshaking, between two or more apparatuses in digital domain. The detection and processing of the handshaking event may be done within a central processing unit of the apparatus.

[0021] According to an embodiment, a first device or an object may detect a second device or another object approaching the first device. When two similar devices detect approaching of the other device, they may be configured to perform a predetermined greeting, which may include for example predetermined gestures. It is an object of the example embodiments to detect whether an approaching device performs the predetermined greeting gesture in order to identify the other device. For example, motion sensor data or other gesture related data may be exchanged to verify that a corresponding gesture has been performed by both devices, in some embodiments substantially simultaneously. In general, the rendezvous may comprise a first event performed by the first device and a second event performed by the second device. One or both of the devices may then determine whether the events correspond to each other for example by creating a handshaking or other predetermined greeting event between the devices. The disclosed means and method can be applied to a group of devices and provide verification of a greeting gesture performed by a plurality of devices at the same time, or substantially simultaneously.

[0022] Different solutions and methods may be used to record object entrance to a confined space, for example a room or office space. Object's position in the space may be also measured. Such technology could apply for example radio frequency signals or other electromagnetic signals to map objects. Accuracy, speed, and spatial resolution of detecting approaching objects may be improved by using methods that are based on radio frequency signals, optical signals, electrical signals, or a combination thereof. Alternatively, or additionally, sound waves may be also used. Through the wall methods may use Terahertz waves and may be applied if detection is done through a physical obstacle. Semiconductor radar components working at 2.4 gigahertz frequency and above are miniature sized and offer another radio frequency method to detect objects and approach, when considering small perimeter applications. Optical methods include image recognition from a camera signal to record and identify objects in space.

[0023] Electrical methods, such as capacitive sensing can be applied to sense objects approaching a target. In addition to the object's approach also the verification of the physical contact may be done based on various techniques which may apply for example electrical contact layers or optical methods. These methods may apply a separate complex sensing structure to verify physical contact or for example the handshaking. However, in some applications such complex structures may have shortcomings which restrict their applicability. Sensing layers or external sensors may increase cost, be sensitive for example to humidity and/or to other corrosive substances. Therefore, it may be more difficult to use them in industrial environment, for example because of hindering cleaning or washing of the object surface. Methods which apply imaging with CMOS camera at visible or infrared wavelengths may require good lighting to enable high quality image or video recording and relatively high computation power to extract the desired information from image or video data. Methods for tracking object's position in space and making decision when object has touched the target or another object are quite limited. Methods for touch sensing may apply for example surface embedded sensors. Such sensors could be based on optical, piezoelectric, or capacitive detection. For example, capacitive sensing may detect a hovering object, for example a human finger, above the sensor active area, and detect the touch. This type of detection provides immediate touch information but does not provide identification of the object nor provide the wanted verification of acceptable predetermined gesture.

[0024] To solve this problem, the embodiments disclosed herein provide an apparatus, a method, and a computer program for detecting an approaching object and verifying object's identity. For example, embodiments verify approach and touch when two similar devices approach and eventually become in contact and perform a greeting or rendezvous in a predetermined manner.

Embodiments provide a camera free implementation, require low computing power, and reduce energy consumption due to an advantageous handshaking verification algorithm. Embodiments enable identification of physical handshaking without any external or fragile sensor layers, thereby enabling to produce a washable object with a lower number of components, still providing feasible means to verify the process of physical handshaking in the digital domain.

[0025] FIG. 1 illustrates examples of a first apparatus 100 and a second apparatus 120, according to one or more embodiments. Apparatus 100 may be part of a first object and apparatus 120 may be part of a second obj ect .

[0026] Apparatus 100 may comprise a central processing unit (CPU) 101. CPU 101 may comprise at least one processor. The at least one processor may comprise, for example, one or more of various processing devices, such as for example a co-processor, a microprocessor, a controller, a digital signal processor (DSP) , a processing circuitry with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) , a microcontroller unit (MCU) , a hardware accelerator, a special-purpose computer chip, or the like.

[0027] Apparatus 100 may further comprise at least one memory 108. The memory may be configured to store, for example, computer program code and the like, for example an operating system and application software. The memory may comprise one or more volatile memory devices, one or more non-volatile memory devices, and/or a combination of one or more volatile memory devices and non-volatile memory devices. For example, the memory may be embodied as magnetic storage devices (such as hard disk drives, floppy disks, magnetic tapes, etc.), optical magnetic storage devices, and semiconductor memories (such as mask ROM, PROM (programmable ROM) , EPROM (erasable PROM) , flash ROM, RAM (random access memory) , or the like) .

[0028] When apparatus is configured to implement some functionality, some component and/or components of the apparatus, such as for example the at least one processor and/or the memory, may be configured to implement this functionality. Furthermore, when the at least one processor is configured to implement some functionality, this functionality may be implemented using program code comprised, for example, in the memory.

[0029] The functionality described herein may be performed, at least in part, by one or more computer program components such as software components. According to an embodiment, the apparatus comprises a processor or processor circuitry, configured by the program code, when executed, to execute the embodiments of the operations and functionality described herein. Alternatively, or in addition, the functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs) , application-specific Integrated Circuits (ASICs) , application-specific Standard Products (ASSPs) , System-on-a-chip systems (SOCs) , Complex Programmable Logic Devices (CPLDs) , Graphics Processing Units (GPUs) .

[0030] Apparatus 100 may further comprise a clock or a clock circuit 102 configured to generate one or more clock signals for CPU 101 via bus 103. The clock circuit 102 may comprise an electronic oscillation circuit, for example at least one crystal oscillator, or the like, to generate a timer signal. Clock 102 may be for example be able to maintain its internal time base within accuracy of 0.01 s for a period of one hour at room temperature.

[0031] Apparatus 100 may further comprise at least one communication interface 104. The communication interface 104 may apply any suitable technology. The communication interface 104 may for example comprise a short-range or near field wireless communication interface such as for example a Bluetooth interface, an RFID (Radio Frequency Identification) interface, NFC interface, a wireless local area network or wireless personal area network interface, for example as provided in IEEE 802.11 and 802.15 standards, a ZigBee interface. The communication interface 104 may also comprise an optical interface such as for example an infrared light interface or visible light interface comprising at least one light emitting diode (LED) controlled by CPU101, or the like. The communication interface 104 may comprise circuitry, for example one or more antennas, to enable apparatus 100 to communicate with another device, for example with apparatus 120 via at least one communication channel 110. The communication interface may be for example capable of transmitting data within a range of ten meters at a data rate of at least 1 kbps.

[0032] Apparatus 100 may further comprise at least one motion sensor 106. Motion sensor 106 may comprise circuitry configured to detect acceleration in one or more axes, for example in three axes. Motion sensor may comprise an accelerometer or a gyroscope configured to generate one or more signals representing acceleration with respect to time in one or more dimensions. Communication interface 104 and/or motion sensor 106 may communicate with CPU 101 via bus 105 and/or bus 107, Bus

105 may be used for example to deliver data from communication channel 110 to CPU 101, or from CPU 101 to communication channel 110. Communication interface 104 may be controlled by the CPU 101 via bus 105. Bus 107 may be used to deliver motion data, for example one or more motion sensor signals, to CPU 101. Motion sensor

106 may be controlled by CPU 101. For example, in one embodiment motion sensor 106 may be enabled by CPU 101 in response to detecting an approaching object.

[0033] Apparatus 100 may further comprise at least one switch 109. The switch may be coupled to CPU 101 by bus 111 such that a switch signal may be delivered to CPU 101 upon actuation of the switch. Apparatus 100 may further comprise a user interface configured to interact with a user with one or more user interface elements such as a display, a keyboard, a touch screen, a signal LED, or the like.

[0034] The second apparatus 120 may comprise functions similar to apparatus 100. For example, a CPU 121 similar to CPU 101, a clock circuit 122 similar to clock circuit 102, communication interface 124 similar to communication interface 104, a motion sensor 126 similar to motion sensor 106, switch 129 similar to switch 109, buses 123, 125, 127, 130 similar to buses 103, 105, 107, 111, or other components similar to apparatus 100. It is appreciated that even though components of apparatus 120 may implement functionality similar to apparatus 100, the components need not be identical to those of apparatus 100.

[0035] In general, apparatuses 100 and 120 comprise means for performing at least one method described in the appended claims and throughout the description. In one example, the means comprises at least one memory including program code, at least one processor, and program code configured to, when executed by the at least one processor, cause performance of the method (s) .

[0036] According to an embodiment, apparatus 100 may be configured to detect approach of another object, for example apparatus 120. Apparatus 100 may be further configured to recognize at least one predetermined gesture, for example a handshaking gesture performed by apparatus 100. Apparatus 100 may be further configured to verify the gesture, for example a physical handshaking or rendezvous with apparatus 120.

[0037] According to an example scenario, two objects comprising apparatus 100 and apparatus 120 with disclosed embedded electronic devices may become in near vicinity of each other. In this scenario a physical greeting event may take place between the two objects. The communication interfaces 104 and 124 may be configured, or controlled by CPU 101 and 121, respectively, to transmit periodically such that apparatus 100 is able to detect nearby apparatus 120. The central processing unit 101 may be configured to track the received radio signal strength, which the communication interface 104 may report over bus 105. Based on the received radio signal strength, CPU 101 may sense approach of another object or apparatus. It can be expected that if the two radio devices approach each other, the antenna signal strength increases. Detecting the approach may be based on detecting an increase in the received signal strength. For example, apparatus 100 may compare received signal strength to a threshold. The threshold may be set for a value of received signal strength, for example in dBm, or as a relative threshold value, expressed for example as a relative increase compared to a previous signal strength measurement. An example of received signal strength with respect to distance between objects is illustrated in FIG. 2.

[0038] According to an embodiment, apparatus 100 may be configured to establish a communication channel 110 to apparatus 120. Communication channel 110 may comprise for example a Bluetooth connection, or any other suitable connection. Apparatus 100 may determine whether apparatus 120 is a similar apparatus, for example of a similar type. To enable this, apparatus 100 and 120 may exchange identification information, for example a type identification after establishment of the communication channel 110. In response to determining that the other apparatus 120 is of a suitable type, a time synchronization procedure may be initiated by one of the devices, for example apparatus 100. It is noted that it is enough that the apparatuses share a substantially common time base. In one example, time bases may be synchronized such that they are within 100 ms, but smaller or higher values may be used depending on the application. Other examples of an acceptable time differences include 5 ms, 20 ms, or 50 ms.

[0039] The time synchronization may comprise for example exchanging information about a current time at each device. For example, in response to receiving an indication of a current time from apparatus 120, apparatus 100 may adjust it's time base such that it corresponds to the time base of apparatus 120. Alternatively, apparatus 100 may compensate the difference in the time bases by other means, for example by adjusting the time stamp received from apparatus 120. Alternatively, apparatus 100 may send an indication of a current time value to apparatus 120, which may adjust its time base accordingly.

[0040] The central processing unit 101 may track the signal from motion sensor 106 to detect a predetermined gesture, for example a handshaking or other greeting gesture at apparatus 100. According to an embodiment, memory 108 may store information about one or more predetermined reference signals associated with the predetermined gesture (s) . CPU 101 may monitor the motion sensor signal received from motion sensor 106 and compare the motion sensor signal to at least one reference signal .

[0041] In response to detecting the predetermined gesture based on the motion sensor signal, CPU 101 may determine to record a time stamp for the event associated with the predetermined gesture. For example, a time stamp may be given to the moment of handshaking. Time stamp may be stored in memory 108. Alternative to a time stamp, a time period comprising the predetermined event may be stored. CPU 101 may also identify the detected gesture as one of a plurality of predetermined gestures and store an identifier of the detected gesture in its memory 108.

[0042] At the other apparatus 120, the central processing unit 121 may track the signal from motion sensor 126 to detect the predetermined gesture. Similar to apparatus 100, the CPU 121 of apparatus 100 may monitor the signal received from motion sensor 126 and compare the motion sensor signal to at least one reference signal stored in memory 128.

[0043] Similar to apparatus 100, apparatus 120 may determine to record time stamp for the event associated with the predetermined gesture in response to detecting the predetermined gesture. For example, a time stamp may be given to the moment of handshaking. Time stamp may be stored in memory 128. Alternative to a time stamp, a time period comprising the predetermined event may be stored and/or communicated to apparatus 100. CPU 121 may also identify the detected gesture as one of a plurality of predetermined gestures and store an identifier of the detected gesture in memory 128.

[0044] According to an embodiment, characteristics of the detected events may be compared to provide a verification of the physical greeting event. For example

[0045] Apparatus 120 may communicate the identifier of the detected gesture and/or the recorded time stamp to apparatus 100. Alternatively, or additionally, apparatus 120 may communicate at least one motion sensor signal to apparatus 100. The central processing unit 101 may compare the characteristics of the gesture detected at apparatus 120 to the characteristics of the gesture detected at apparatus 100. For example, apparatus 100 may compare the identifier of the detected gesture or the motion sensor signal the identifier of the gesture detected at apparatus 100 or a corresponding motion sensor signal received from motion sensor 106. Apparatus 100 may further compare the time stamp received from apparatus 120 to the time stamp stored at apparatus 100.

[0046] If at least one characteristic of the event at apparatus 120 corresponds to the at least one characteristic of the event at apparatus 100, apparatus 100 may determine to provide a verification of the event. For example, verification may be provided if the signals of motion sensors 106 and 126 indicate a corresponding simultaneous event, or if the identifier of the event received from the other apparatus 120 corresponds to the identifier stored at apparatus 100.

[0047] According to an embodiment, the time stamps may be also considered. For example, if the time stamps are same or with margin of error, apparatus 100 may provide the verification of the event.

[0048] Providing verification may comprise for example apparatus 100 sending a verification signal or message to the other apparatus 120. Apparatus 120 may receive the verification signal from apparatus 100. Apparatus 120 may then determine that the handshaking event was successful. Apparatus 100 and/or apparatus 120 may indicate a successful handshaking event, for example at their user interface.

[0049] FIG. 3 illustrates an example of motion sensor signals 301, 302, and 303 corresponding to three orthogonal axes x, y, and z, respectively, at apparatus 100. Motion sensor signals may generally comprise acceleration signals, which may be associated with a predetermined gesture. Reference signal (s) associated with the predetermined gesture or event may be stored in memory of apparatus 100 or 120. FIG. 4 illustrates an example of motion sensor signals 401, 402, and 403 corresponding to three orthogonal axes x, y, and z, respectively, at apparatus 120.

[0050] In the examples of FIG. 3 and FIG. 4, the gesture is a high five greeting. A high five greeting gesture event creates acceleration signal (s) corresponding to identifiable fingerprint ( s ) or relative changes, which may be identified by the CPU 101 or 121. Such acceleration signals may have orthogonal x, y, and z components varying in signal strength (acceleration units m/s ^A 2) and with different vector values, or opposite vector direction, at least for one component.

[0051] A high five greeting event may be characterized by creating an acceleration vector, axl (tl) 301, which is in opposite direction of the acceleration vector, ax2 (tl) 401, measured in the other apparatus substantially at the same time moment tl. For example, in FIG. 3 and FIG. 4, it is evident that x components 301 and 401 have characteristic peaks in opposite directions around tl = 6 s. Comparison of the acceleration signals may be used to verify the physical handshaking or greeting event.

[0052] FIG. 5 illustrates another example of motion sensor signals 501, 502, and 503 corresponding to three orthogonal axes x, y, and z, respectively, at apparatus 100. FIG. 6 illustrates corresponding motion sensor signals 601, 602, and 603 corresponding to three orthogonal axes x, y, and z, respectively, at apparatus 120.

[0053] In the example of FIG. 5 and FIG. 6 the gesture is a physical handshaking event. A handshaking event creates acceleration signal (s) corresponding to identifiable fingerprint ( s ) or relative changes, which may be identified by the CPU 101 or 121. As can be seen in FIG. 5, a physical handshaking event creates an acceleration vector a (tl), which shows oscillation in one of the component vectors alx (tl) 501, aly (tl) 502, or alz (tl) 503. In the other apparatus one of the acceleration vectors a2x(tl) 601, a2y (tl) 602, or a2z (tl) 603 oscillates in a similar fashion substantially at the same period of time tl = 3.5 s to 5 s. In FIG. 5, the hand shake greeting creates an oscillating x component at motion sensor 106 of apparatus 100 and an oscillating z component at motion sensor 126 at apparatus 1 at time period tl = 3.5 s to 5 s .

[0054] As the devices communicate relatively fast over the established communication channel 110, for example a Bluetooth channel, the greeting gesture may be also verified based on just detecting the characteristic changes in the acceleration signals without considering the time moment of the event. According to an embodiment apparatus 100 may detect at least one characteristic of a motion sensor signal caused by a high five greeting performed by apparatus 100. Apparatus 100 may instantly send a request message or signal to the other apparatus 120 to verify if a high five greeting event actually happened. In response to receiving the request from apparatus 100, the other apparatus 120 may determine to initiate searching for a possible typical characteristics of a high five gesture from the motion sensor data recorded during a predetermined or configurable time period. According to an embodiment, the period comprises the last 0 to 2000 milliseconds. In response to determining that such event is found, the other apparatus 120 may send a confirmation message or signal to apparatus 100. The confirmation may indicate that a characteristic signature of a high five greeting has been found, and that the handshaking event is thus confirmed .

[0055] It is possible that there is a delay before the other apparatus 120 begins the search for the characteristic acceleration signal. Because of this delay, in some circumstances the system may also compare the time stamps of the gestures to provide more reliable event verification, as described earlier

[0056] According to an embodiment, the event comprises detecting actuations of switches at apparatus 100 and the other apparatus 120. A switch may comprise an electrical or mechanical switch, or textile switch, but in other embodiments it may be implemented by other means, for example based on a touch screen.

[0057] According to an embodiment, an initially open switch is embedded on the surface of apparatus 100 and connected to the central processing unit 101. Two objects can 'handshake' by pressing against the switch areas of the respective device surfaces. The switch data on the two electronic devices, for example apparatus 100 and the other apparatus 120, may be compared to verify possible effective simultaneous closures.

[0058] For example, apparatus 100 may detect that apparatus 120 is approaching, as described earlier. Apparatus 100 may be configured to perform a greeting gesture by pressing a switch at apparatus 120. In a similar fashion, apparatus 120 may detect apparatus 100 approaching and may be configured to press a second switch at apparatus 100. Apparatus 100 and 120 may be configured to perform a greeting gesture, for example by closing their respective switches. Apparatus 100 and apparatus 120 may be further configured to store a time stamp associated with actuation of their switch, for example in memories 108 and 128, respectively. According to an embodiment, apparatus 120 may be configured to send an indication of the actuation of the switch at apparatus 120. Furthermore, the indication may include information about a time, for example a time stamp, associated with the actuation of the switch at apparatus 120.

[0059] In response to receiving, the indication from apparatus 120, apparatus 100 may determine whether actuation of its own switch occurred during a predetermined time period. According to an embodiment, apparatus 100 may determine whether the time associated with actuation of the switch at apparatus 120 corresponds to the time of actuation of its own switch. In response to determining that actuations of the two switched occurred substantially at the same time, or within an acceptable time period, apparatus 100 may determine to provide a verification signal of the greeting event.

[0060] According to an embodiment, the switches may be located on the objects such that a greeting gesture, for example a high five greeting or a physical handshaking event causes the switches to be actuated. Apparatus 100 may then compare the motion sensor signal (s) or identifiers of detected gestures and the indication of switch actuation received from the other apparatus, to provide a verification of the greeting event. Such greeting event may cause a substantially simultaneous closure of the two switches on both apparatuses. Comparison of the time stamps of the switch signals may increase reliability of the verification of the physical handshaking or greeting gesture.

[0061] FIG. 7 illustrates an example of a method for verifying a greeting event and launching a successful handshake activity between apparatus 100 apparatus 120. Even though certain operations of the procedure have been described as being performed by apparatus 100 or 120, it is appreciated that roles in the procedure may be swapped.

[0062] The procedure may be initiated while apparatus

100 is in a hibernating state 701. It is however appreciated that the method may be initiated also when the apparatus 100 is in a non-hibernating state.

[0063] Operation 702 may comprise determining whether a radio signal is received. In response to determining that a radio signal is received, the procedure may continue by waking up the apparatus at 703, or a particular component thereof.

[0064] At operation 704, a communication channel may be established. For example, apparatuses 100 and 120 may exchange information about communication parameters. For example, apparatus 100 may send a configuration message to apparatus 120. The configuration message may for example include information about time slots allocated for transmission for apparatus 100 and/or apparatus 120.

[0065] At operation 705, apparatus 100 may determine whether the other apparatus 120 is a similar apparatus. This may be done for example based on device type information received from apparatus 120, or some other characteristic of apparatus 120.

[0066] At operation 706, apparatus 100 may determine whether a communication channel was successfully established. If the communication channel was not established, apparatus 100 may be configured to enter the hibernating state 701. If the communication channel was established, the procedure may proceed to operation 707.

[0067] At operation 707, apparatus 100 may identify the other apparatus 120. For example, apparatus 100 may receive an identifier of apparatus 120 over the communication channel 110. Apparatus 100 may at least temporarily store the identifier of the other apparatus 120 in its memory 108.

[0068] At operation 708, apparatus 100 may synchronize its clock 102, for example time and date, with apparatus 120, as described above.

[0069] At operation 709, apparatus 100 may record a received radio signal strength (RSSI) . This may be done for example during time slots allocated to apparatus 102 in operation 704.

[0070] At operation 710, apparatus 100 may determine whether the received signal strength increases. For example, apparatus 100 may determine whether the signal strength increases above a threshold or whether an increment from a previous measurement exceeds a threshold, as discussed above. In response to determining that signal strength does not increase, the procedure may continue monitoring the signal strength at operations 709 and 710 until a time-out value is reached at operation 711. In response to determining that signal strength increases, the procedure may proceed to operation 712.

[0071] At operation 712, apparatus 100 may determine whether a gesture is detected. The gesture may comprise for example a particular hand motion such as a high five greeting, or a physical handshake gesture. Alternatively, or additionally, the gesture may comprise actuation of a switch, as discussed above.

[0072] At operation 713, apparatus 100 may share a time stamp associated with the gesture and/or the received signal strength value with apparatus 120, for example by sending a message to apparatus 120 over the communication channel.

[0073] At operation 714, the other device may determine whether motion of apparatus 100 is synchronized with apparatus 120. For example, apparatus 102 may compare motion sensor signals and/or switch actuation data to its own motion sensor data and/or switch actuation data, as described above. Optionally, apparatus 120 may also compare the time stamps associated with switch actuation or event (s) detected in the motion sensor signals. [0074] At operation 715, apparatus 120 may determine that the greeting event, for example a handshaking event, is verified. This may be done based on the determinations at operation 714. Apparatus 120 may further send an indication about the confirmed greeting event to apparatus 100.

[0075] At operation 716, apparatus 100 may determine that the greeting event was verified, for example based on the indication received from apparatus 120. It is however noted that alternatively, or additionally, apparatus 100 may perform similar operations as apparatus 120 in 714 and 715. For example, verify the greeting event based on motion sensor signals and/or switch actuation data of both apparatuses.

[0076] At operation 717, in response to a verified greeting event, apparatus 100 may record the identify of apparatus 120 in a database. The database may include identifiers for any devices, which have completed a successful greeting procedure with apparatus 100. These apparatuses may be for example regarded as trusted devices in any subsequent interactions. The database may be located in memory 108, or be external to apparatus 100.

[0077] At operation 718, a successful handshaking activity may be launched at apparatus 100 and apparatus 120. It is noted that handshake activity may refer to any activity dependent on verification of the greeting event at operations 715 and 716.

[0078] The procedure 700 may also comprise a general time out operation 719, which may be associated with one or more operations of the procedure. Whenever this time out is triggered, the procedure may proceed to the hibernating state 710, or another initiation state. [0079] FIG. 8 illustrates an example of a method for verifying a greeting event, according to an embodiment.

[0080] At 801, the method may comprise detecting at least one other apparatus.

[0081] At 802, the method may comprise detecting an event, for example a greeting event. The event may comprise a first event associated with a first apparatus and a second event associated with the at least one other apparatus .

[0082] At 803, the method may comprise determining that at least one characteristic of the first event corresponds to at least one characteristic of the second event .

[0083] At 804, the method may comprise determining to verify the event.

[0084] The operations of the methods described herein may be carried out in any suitable order, or simultaneously where appropriate. Additionally, individual blocks may be deleted from any of the methods without departing from the scope of the subject matter described herein. Aspects of any of the embodiments described above may be combined with aspects of any of the other embodiments described to form further embodiments without losing the effect sought.

[0085] Any range or device value given herein may be extended or altered without losing the effect sought. Also, any embodiment may be combined with another embodiment unless explicitly disallowed.

[0086] Although the subject matter has been described in language specific to structural features and/or acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as examples of implementing the claims and other equivalent features and acts are intended to be within the scope of the claims.

[0087] It will be understood that the benefits and advantages described above may relate to one embodiment or may relate to several embodiments. The embodiments are not limited to those that solve any or all of the stated problems or those that have any or all of the stated benefits and advantages. It will further be understood that reference to 'an' item may refer to one or more of those items.

[0088] The term 'comprising' is used herein to mean including the method, blocks or elements identified, but that such blocks or elements do not comprise an exclusive list and a method or apparatus may contain additional blocks or elements.

[0089] It will be understood that the above description is given by way of example only and that various modifications may be made by those skilled in the art. The above specification, examples and data provide a complete description of the structure and use of exemplary embodiments. Although various embodiments have been described above with a certain degree of particularity, or with reference to one or more individual embodiments, those skilled in the art could make numerous alterations to the disclosed embodiments without departing from scope of this specification.