WO2018176670A1 - Handshake method and device for wireless communication - Google Patents

Handshake method and device for wireless communication Download PDF

Info

Publication number
WO2018176670A1
WO2018176670A1 PCT/CN2017/091424 CN2017091424W WO2018176670A1 WO 2018176670 A1 WO2018176670 A1 WO 2018176670A1 CN 2017091424 W CN2017091424 W CN 2017091424W WO 2018176670 A1 WO2018176670 A1 WO 2018176670A1
Authority
WO
WIPO (PCT)
Prior art keywords
device
touch
touch information
information
time
Prior art date
Application number
PCT/CN2017/091424
Other languages
French (fr)
Chinese (zh)
Inventor
柴良玉
李永哲
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to CN201710205323.8 priority Critical
Priority to CN201710205323 priority
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2018176670A1 publication Critical patent/WO2018176670A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements, e.g. access security or fraud detection; Authentication, e.g. verifying user identity or authorisation; Protecting privacy or anonymity ; Protecting confidentiality; Key management; Integrity; Mobile application security; Using identity modules; Secure pairing of devices; Context aware security; Lawful interception
    • H04W12/001Protecting confidentiality, e.g. by encryption or ciphering
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements, e.g. access security or fraud detection; Authentication, e.g. verifying user identity or authorisation; Protecting privacy or anonymity ; Protecting confidentiality; Key management; Integrity; Mobile application security; Using identity modules; Secure pairing of devices; Context aware security; Lawful interception
    • H04W12/02Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements, e.g. access security or fraud detection; Authentication, e.g. verifying user identity or authorisation; Protecting privacy or anonymity ; Protecting confidentiality; Key management; Integrity; Mobile application security; Using identity modules; Secure pairing of devices; Context aware security; Lawful interception
    • H04W12/06Authentication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/14Direct-mode setup

Abstract

The embodiments of the present application relate to a handshake method and device for wireless communication. The method comprises: a first device physically touching a second device; the first device acquiring first touch information, the first touch information being generated when the first device physically touches the second device; the first device sending the first touch information to the second device; if the first touch information matches second touch information, the first device establishing a connection to the second device, the second touch information being the information generated when the first device physically touches the second device, collected by the second device. The embodiments of the present application do not rely on an NFC device, can realize reliable communication handshakes between devices with low costs, and then can be widely used in communication devices.

Description

Handshake method and device for wireless communication Technical field

The embodiments of the present application relate to the field of communications technologies, and in particular, to a handshake method for communications.

Background technique

In recent years, with the rapid development of wireless communication technology, the close-range information exchange between mobile phones and mobile phones and mobile phones and computers has developed rapidly. One of the existing short-range communication technologies is near field communication (NFC) technology, also known as short-range wireless communication technology. NFC technology is a short-range high-frequency wireless communication technology that evolves from the integration of contactless radio frequency identification (RFID) and interoperability technologies, combining inductive readers, inductive cards and peer-to-peer on a single chip. Function to identify and exchange data with compatible devices within a short distance.

NFC technology allows non-contact point-to-point data transmission between electronic devices to exchange data. The near field communication service realizes various functions such as electronic payment, identity authentication, ticketing, data exchange, anti-counterfeiting, advertisement, etc., and is a new type of business in the field of mobile communication. However, the module cost and patent cost of NFC technology are high, and the technology of mobile phones and various service providers is adapted.

Another short-range wireless communication technology available is the wireless transmission technology HotKnot launched by MediaTek. The HotKnot technology uses the touch chip as the main sensing medium, and the transmission of the mobile phone to the mobile phone or the mobile phone to the computer can be realized through the optical sensing original and the gravity sensing original. However, HotKnot technology also relies on devices and is slow to develop.

The prior art discloses an access control using a device containing an accelerometer with the goal of enabling a trusted connection between mobile devices with accelerometers by utilizing certain systems, devices, and methods. In the method, the first device and the second device generate physical interaction data between the two devices by physical contact with each other, and the two devices may be mobile terminals. The second device can be a sales terminal, an access point device, or any fixed device on a certain line, door, or entrance. Through the interactive connection between devices, the server can confirm whether physical contact has been made between devices. After the server confirms that the two devices are in contact, it will initiate a connection between the two devices. When the device to be connected allows access to a secure specific area through the access control permission, the connection between the two devices allows information exchange between the devices, and even the interaction of the credential information. One possible application of this method is transaction authentication, for example in the relevant fields of financial transactions and online payments. The method requires server support and data comparison verification, poor anti-interference ability, large network delay, and slow processing speed.

Summary of the invention

The embodiment of the present application provides a communication handshake method and a terminal. The embodiment of the present application solves the communication handshake problem of the credit by using the devices to touch each other at the lowest cost.

In a first aspect, an embodiment of the present application provides a handshake method for wireless communication. The method includes: first setting The first device acquires the first touch information, and the first touch information is information generated when the first device and the second device are physically touched; The first device sends the first touch information to the second device; if the first touch information matches the second touch information, the first device establishes a connection with the second device, The second touch information is information generated when the first device and the second device collected by the second device are physically touched.

In a second aspect, an embodiment of the present application provides a first device. The first device and the second device are physically touched; the first device includes: a processor and a transmitter; the processor is configured to acquire first touch information, where the first touch information is the first Information generated when a device and the second device are physically touched; the transmitter is configured to send the first touch information to the second device; and the processor is further configured to: if the first touch The touch information is matched with the second touch information, and the second device is connected to the second device, where the second touch information is when the first device and the second device collected by the second device are physically touched. The information generated.

In the embodiment of the present application, the communication handshake between the first device and the second device is achieved by the uniqueness of the information touched by the first device and the second device, which has high security and saves cost.

In one example, the first device establishes a connection with the second device, including: the first device sends a connection request to the second device; and the first device receives the connection sent by the second device In response, the first device establishes a connection with the second device; the connection response is a response of the second device to the connection request.

In an example, the first device establishes a connection with the second device, including: the first device receives a connection request sent by the second device; and the first device sends a connection to the second device. In response, the first device establishes a connection with the second device; the connection response is a response of the first device to the connection request.

In an example, the sending, by the first device, the first touch information to the second device is that the first device sends the encrypted first touch information to the second device.

In one example, the touch information is one or more of the following: time information of the occurrence of the touch, audio information generated by the touch, acceleration information generated by the touch, generated by the touch Rotation information.

In one example, the time information of the touch occurrence is determined by the first device, the power-on duration according to the touch time of the first device, the second device, and the power-on time of the calibration time of the first device; The time period of the touch of the first device and the second device is the time difference between the first device and the second device being touched by the first device; The booting time of the calibration time of the first device is the time difference between the first device and the second device calibration time from the power-on and power-on of the first device.

In one example, before the first device acquires the first touch information, the first device and the second device perform time calibration to determine a booting time of the calibration time.

In one example, before the first device sends the encrypted first touch information to the second device, the method includes: generating encrypted first touch information; and generating the encrypted first touch information, including The first device generates a private key according to the first touch information;

The first device generates a first random sequence, and the first device encrypts the first random sequence according to the private key to generate the encrypted first touch information.

In one example, before the generating the encrypted first touch information, the first device determines a time when the second device answers the first device; the first device is according to the private key Encrypting the first random sequence to generate the encrypted first touch information, specifically: the first device, according to the private key, the random sequence corresponding to the first random sequence and the response time Encryption is performed to generate the encrypted first touch information.

In an example, after the first device sends the encrypted first touch information to the second device, the method includes: the first device receiving an encrypted second touch from the second device Information, the first device decrypts the encrypted second touch information according to the first random sequence;

In an example, after the generating the encrypted first touch information, the method includes: the first device broadcasting the encrypted first touch information.

In an example, the first device generates a private key according to the touch information, specifically, extracting the touch occurrence time information, the audio information generated by the touch, the acceleration information generated by the touch, and the touch generated. A plurality of features in the angle information, and performing mathematical operations on the plurality of features to generate the private key.

In one example, before the first device and the second device are physically touched, the first device includes retrieving other devices in the vicinity of the first device, and generating a first list according to the device identifier of the retrieved device. L1, whether each device in the first list L1 is in a pre-pairing state, and the device identifier corresponding to the device in the pre-paired state is formed into the second list L2.

In a third aspect, an embodiment of the present application provides a computer program product comprising instructions, when the computer program product is run on a computer, causing the computer to perform the method described in the above aspects.

In a fourth aspect, an embodiment of the present application provides a computer readable storage medium. The computer readable storage medium stores a computer program that, when executed by the processor, implements the methods described in the various aspects above.

In a fifth aspect, an embodiment of the present application provides a handshake method for wireless communication. The method includes: the first device and the second device are physically touched; the first device receives the first touch information sent by the second device, where the first touch information is the first device and The second device generates information when the physical touch occurs; if the first touch information matches the second touch information, the first device establishes a connection with the second device, and the second touch The information is information generated when the first device and the second device collected by the first device are physically touched.

In a sixth aspect, an embodiment of the present application provides a second device. The second device and the first device are physically touched; the second device includes: a receiver, configured to receive first touch information sent by the first device, where the first touch information is The first device and the second device generate information when the physical touch occurs; the processor is configured to: if the first touch information matches the second touch information, the second device and the first device Establishing a connection, where the second touch information is information generated when the first device and the second device collected by the second device are physically touched.

The embodiment of the present application obtains the first encrypted information, and decrypts the first encrypted information by using a private key, where the private key is two device touch information, thereby implementing a mutual communication communication handshake between the two communication devices. .

In an example, the first device establishes a connection with the second device, including: the first device receives a connection request of the second device; and the first device sends a connection response to the second device The first device establishes a connection with the second device; the connection response is a response of the first device to the connection request.

In one example, the first device establishes a connection with the second device, including: the first device sends a connection request to the second device; and the first device receives the connection sent by the second device In response, the first device establishes a connection with the second device; the connection response is a response of the second device to the connection request.

In an example, the first device receives the first touch information, specifically: the first device receives the encrypted first touch information.

In an example, the first touch information is matched with the second touch information, and the first device decrypts the encrypted first touch information according to the private key of the first device. Obtained for verifying the first device Determining, by the first random sequence, a first random sequence for the second device, determining, according to the first random sequence, that the first touch information matches the second touch information; wherein, the first device is private The key is generated by the first device according to the touch information of the first device and the second device.

In one example, the touch information is one or more of the following: time information of the occurrence of the touch, audio information generated by the touch, acceleration information generated by the touch, and rotation information generated by the touch. .

In one example, the first device decrypts the encrypted first touch information and also obtains the time of the first response determined by the second device.

In an example, after the first device decrypts the encrypted touch information, the method includes: the first device encrypts the first random sequence according to the private key, to obtain an encrypted a first random sequence; the first device transmits the encrypted first random sequence at the first response time.

In a seventh aspect, an embodiment of the present application provides a computer program product comprising instructions, when the computer program product is run on a computer, causing the computer to perform the method described in the above aspects.

In an eighth aspect, an embodiment of the present application provides a computer readable storage medium. The computer readable storage medium stores a computer program that, when executed by the processor, implements the methods described in the various aspects above.

In a ninth aspect, the embodiment of the present application provides a first handshake device.

The first handshake device and the second handshake device are physically touched.

The first handshake device includes an acquisition unit, a transmission unit, and a connection establishment unit.

The acquiring unit is configured to acquire first touch information, where the first touch information is information generated when the first handshake device and the second handshake device are physically touched.

The sending unit is configured to send the first touch information to the second handshake device.

The establishing connection unit is configured to establish a connection with the second handshake device if the first touch information matches the second touch information, and the second touch information is collected by the second handshake device. The information generated when the first handshake device and the second handshake device are physically touched.

In one example, the first handshake device further includes a receiving unit. The sending unit is further configured to send a connection request to the second handshake device. The receiving unit is configured to receive a connection response sent by the second handshake device, so that the first handshake device establishes a connection with the second handshake device; and the connection response is the second handshake device to the connection The requested response.

In one example, the first handshake device further includes a receiving unit. The receiving unit is configured to receive a connection request sent by the second handshake device. The sending unit is further configured to send a connection response to the second handshake device, so that the first handshake device establishes a connection with the second handshake device. The connection response is a response of the first handshake device to the connection request.

In an example, the sending unit is specifically configured to send the encrypted first touch information to the second handshake device.

In one example, the touch information is one or more of the following: time information of the occurrence of the touch, audio information generated by the touch, acceleration information generated by the touch, generated by the touch Rotation information.

In one example, the time information of the touch occurrence is determined by the first handshake device according to the start time of the first handshake device, the touch time of the second handshake device, and the calibration time of the first handshake device. The boot time is determined;

The booting time of the first handshake device and the second handshake device is the first handshake a time difference between a time when the device and the second handshake device touch the power of the first handshake device;

The power-on duration of the calibration time of the first handshake device is a time difference between the first handshake device and the second handshake device calibration time from the first handshake device being powered on.

In one example, the first handshake device further includes a calibration time unit. And the calibration time unit is configured to perform time calibration with the second handshake device before the first handshake device acquires the first touch information to determine a boot duration of the calibration moment.

In one example, the first handshake device further includes a generating unit. The generating unit includes, before the first handshake device sends the encrypted first touch information to the second handshake device, the generated first touch information. The generating unit further includes: generating a subunit of the private key according to the first touch information, generating a subunit of the first random sequence, encrypting the first random sequence according to the private key to generate the encryption The first sub-unit of the touch information.

In one example, the first handshake device further includes a determination unit. The determining unit is configured to determine a time when the second handshake device answers the first handshake device before the generating the encrypted first touch information.

The generating unit encrypts the first random sequence according to the private key to generate the encrypted first touch information, specifically: the generating unit pairs the first random sequence according to the private key The random sequence corresponding to the response time is encrypted to generate the encrypted first touch information.

In one example, the first handshake device further includes a decryption unit. The receiving unit is further configured to: after the first handshake device sends the encrypted first touch information to the second handshake device, receive the encrypted second touch information from the second handshake device . The decrypting unit is configured to decrypt the encrypted second touch information according to the first random sequence.

In a tenth aspect, the embodiment of the present application provides a second handshake device.

The second handshake device and the first handshake device physically touch.

The second handshake device includes a receiving unit and a connection establishing unit.

The receiving unit is configured to receive first touch information sent by the first handshake device, where the first touch information is generated when the second handshake device and the first handshake device are physically touched information.

The establishing connection unit is configured to establish a connection with the first handshake device if the first touch information matches the second touch information, and the second touch information is collected by the second handshake device. The information generated when the second handshake device and the first handshake device are physically touched.

In one example, the second handshake device further includes a transmitting unit. The receiving unit is further configured to receive a connection request of the first handshake device. The sending unit is configured to send a connection response to the first handshake device, so that the second handshake device establishes a connection with the first handshake device. The connection response is a response of the second handshake device to the connection request.

In one example, the second handshake device further includes a transmitting unit. The sending unit is configured to send a connection request to the first handshake device. The receiving unit is further configured to receive a connection response sent by the first handshake device, so that the second handshake device establishes a connection with the first handshake device. The connection response is a response of the first handshake device to the connection request.

In an example, the receiving unit is specifically configured to receive the encrypted first touch information.

In one example, the second handshake device further includes a decryption unit, a match determination unit. The decrypting unit is configured to decrypt the encrypted first touch information according to the private key of the second handshake device, and obtain the verification The second handshake device makes a first random sequence of the first response to the first handshake device. The matching determining unit is configured to determine that the first touch information matches the second touch information based on the first random sequence.

The private key of the second handshake device is generated by the second handshake device according to the touch information of the second handshake device and the first handshake device.

In one example, the touch information is one or more of the following: time information of the occurrence of the touch, audio information generated by the touch, acceleration information generated by the touch, and rotation information generated by the touch. .

In one example, the decryption unit decrypts the encrypted first touch information and also obtains the time of the first response determined by the first handshake device.

In an example, the second handshake device further includes an encryption unit and a transmission unit. The encryption unit is configured to encrypt the first random sequence according to the private key after the second handshake device decrypts the encrypted touch information, to obtain an encrypted first random sequence. . The sending unit is configured to send the encrypted first random sequence at the first response time.

In the embodiment of the present application, the data generated by the collision caused by the collision between the two devices is unique in time and space as an objective basis for the credit verification, and the feature code is extracted from the information generated by the vibration, thereby confirming the collision object, and further Realize handshake and mutual trust. The embodiment of the present application can obtain the information generated by the vibration by using the existing sensors of the mobile device without relying on the NFC device, so that the communication handshake between the devices with higher reliability can be realized with the lowest device cost. .

DRAWINGS

FIG. 1 is a schematic diagram of a scenario for implementing handshake between devices by touch according to an embodiment of the present application;

2 is a schematic diagram of searching for a device in a handshake listening state and performing time calibration on a device in a handshake listening state according to an embodiment of the present application;

3 is a schematic diagram of a handshake method for wireless communication provided by an embodiment of the present application;

4 is a flowchart of a device request handshake provided by an embodiment of the present application;

FIG. 5 is a flowchart of a response pairing handshake request provided by an embodiment of the present application; FIG.

6 is a flowchart of a connection establishment request provided by an embodiment of the present application;

7 is a flowchart of a response connection request provided by an embodiment of the present application;

FIG. 8 is a block diagram of a first wireless communication device according to an embodiment of the present application;

FIG. 9 is a block diagram of a second wireless communication device according to an embodiment of the present application.

detailed description

The technical solutions of the present application are further described in detail below through the accompanying drawings and embodiments.

FIG. 1 is a schematic diagram of an application scenario for implementing handshake between devices by touch according to an embodiment of the present application.

In FIG. 1, the device 1 and the device 2 are physically touched, and the device 1 and the device 2 respectively acquire the touch information, including at least vibration waveform information and vibration occurrence time information. The vibration waveform information is obtained by a piezoelectric sensor, a pickup, or the like.

The device 1 and the device 2 respectively obtain corresponding touch information, and the touch information is information generated when the device 1 and the device 2 are physically touched. The touch information includes one or more of time information of occurrence of a touch, audio information generated by the touch, acceleration information generated by the touch, and rotation information generated by the touch. If the device The acquired touch information matches the touch information acquired by the device 2, and the device 1 establishes a connection with the device 2. Specifically, the device 1 and the device 2 respectively extract features from the touch information respectively acquired by the device 1, and generate a private key. Since the touch generated by the device 1 and the device 2 are the same, the touch information is also the same, and the generated private keys are the same, so as to implement the mutual handshake process between the device 1 and the device 2. Then, the device 1 and the device 2 can communicate with each other. For example, the device 1 and the device 2 can transmit data or implement payment.

The following is an example in which the touch time information acquired according to the device 1 and the device 2 is the same, and then the touch information of the device 1 is matched with the touch information of the device 2 as an example.

In order to improve the security of the wireless communication handshake, the embodiment of the present application needs to obtain more accurate information about the collision occurrence time. In order to obtain more accurate collision occurrence time information, the embodiment of the present application is implemented by calibrating time.

The device 1 and the device 2 perform time calibration, and the device 1 and the device 2 respectively record the booting time of the calibration time. Elapsed Real-Time (ERT) refers to the duration of the recording from the start-up time to the current time, whether the device is powered on or not, whether it is hibernating or not. For example, device 1 is powered on at 3:00:00.000, and the boot time at 15:00:15.151 is 43215151 ms. For another example, device 1 is turned on at 3:00:00.000, and the time is changed to 11:00:00.000 at 13:00:00.000, and then the boot time of milliseconds at device time 13:00:15.151 is still 43215151ms. . It can be seen that the boot duration has nothing to do with the system setup time. The power-on duration of the calibration time refers to the duration from the start-up time to the calibration time after the device is powered on.

After the device 1 collides with the device 2, the device 1 and the device 2 respectively record the booting time of the collision time. The power-on duration of the collision time refers to the duration of the recorded time from the start-up time to the collision time after the device is powered on.

Since the boot duration of the calibration time is the difference between the calibration time and the boot time, the boot duration of the collision time is the difference between the collision time and the boot time. Therefore, although the local power-on time of the device 1 and the device 2 may be different, since the calibration time and the collision time of the device 1 and the device 2 are the same, that is, the device 1 and the device 2 are simultaneously calibrated with each other while colliding with each other. Therefore, the difference between the power-on duration of the collision time of the device 1 and the power-on duration of the calibration time of the device 1 is equal to the difference between the power-on duration of the collision time of the device 2 and the power-on duration of the calibration time of the device 2. Here, the collision time information of the device 1 is referred to as the difference between the power-on duration of the collision time of the device 1 and the power-on time of the calibration time, and is also the calibration duration of the collision time. The collision time information of the device 2 is the difference between the power-on duration of the collision time of the device 2 and the power-on time of the calibration time, and is also the calibration duration of the collision time. Therefore, the collision time information of the device 1 is the same as the collision time information of the device 2.

This will be explained in detail below through Figure 2.

2 is a schematic diagram of searching for a device in a handshake listening state and performing time calibration on a device in a handshake listening state according to an embodiment of the present application.

In FIG. 2, the devices d1-d7 are, for example, mobile phone devices, tablet devices, and the like. Devices d1, d2, and d7 are in the handshake listening mode. The handshake listening mode refers to a mode capable of listening to devices that are in a wireless communication handshake with the periphery.

In one example, the user initiates a handshake listening mode. For example, the user of the mobile device d1, d2, d7 activates the handshake button in the mobile phone, thereby entering the handshake listening mode. As another example, the user initiates the handshake listening mode by scanning the two-dimensional code. The device d1 in the handshake listening mode searches its peripheral devices d2-d7, and the device d1 filters out that the devices d2 and d7 are in the handshake listening mode. In the same manner, device d2 filters out that devices d1, d7 are in the handshake listening mode; device d7 filters out that devices d1, d2 are in the handshake listening mode. If the two devices in the handshake listening mode implement the mutual handshake by the handshake method of the wireless communication provided by the embodiment of the present application, the two devices can perform the number According to communication, for example, transmission of data or payment by mobile phone.

Specifically, after the device d1 determines that the device d2 and the device d7 are in the handshake listening mode, the device d1 will perform time calibration with the device d2 and the device d7, respectively. And record the boot time table of the calibration time of the device d1, see Table 1 below. The table 1 stores the booting time of the calibration time at which the device d1 is calibrated with the devices d2 and d7, respectively.

The power-on duration of the calibration time of the device d1 and the device d2 is the time difference between the device d1 and the device d2, the time difference from the local power-on time of the device d1. Similarly, the booting time of the device d1 and the device d7 at the time of calibration is the time difference between the device d1 and the device d7, and the time difference from the device d1. Table 1 below is a calibration record of device d1 relative to other devices:

Equipment Identity Start-up time at calibration time D2 189578982839ns D7 190687321593ns

Table 1

In Table 1, the boot duration of the calibration time recorded by the device d1 - 189578982839 ns indicates that the time difference between the device d1 and the device d2 calibration time and the local power-on time of the device d1 is 189578982839 ns (nanoseconds). Similarly, the boot duration of the calibration time recorded by the device d1 -190687321593ns indicates that the time difference between the device d1 and the device d7 is 190687321593ns (nanoseconds) from the local boot time of the device d1.

In the same manner, the device d2 records a list of calibration times for d2, see Table 2 below, which holds the power-on duration of the calibration time at which the device d2 and the devices d1, d7 are respectively calibrated.

The booting time of the device d2 and the calibration time of the device d1 is the time difference between the device d2 and the device d1, the time difference from the local start time of the device d2. Similarly, the booting time of the device d2 and the device d7 at the time of calibration is the time difference between the device d2 and the device d7, and the time difference from the local start time of the device d2. Table 2 below is a calibration record of device d2 relative to other devices:

Equipment Identity Start-up time at calibration time D1 536745826423ns D7 537783548961ns

Table 2

In Table 2, the booting time of the calibration time recorded by the device d2 - 536745826423 ns indicates that the time difference between the device d2 and the device d1 calibration time and the local power-on time of the device d2 is 536745826423 ns (nanoseconds). Similarly, the boot duration of the calibration time recorded by the device d2 - 190687321 593 ns indicates that the time difference between the device d2 and the device d7 calibration time and the local power-on time of the device d2 is 190,687,321, 593 ns (nanoseconds).

It can be seen from Table 1 and Table 2 that the boot duration of the calibration time of the device d1 and the device d2 recorded by the device d1 is 189578982839 ns, and the boot duration of the calibration time of the device d2 and the device d1 recorded by the device d2 is 536745826423 ns. different. However, the calibration time that the device d1 actually takes place with the device d2 is the same. The reason is that the booting time of the calibration time of the device d1 and the device d2 recorded by the device d1 is the time difference between the local time of the device 1 and the time when the device d1 is calibrated and the device d1 is powered on. value. Device d2 The recorded calibration time information of the device d2 and the device d1 is the time difference between the local time of the device 1 and the device d2 when the device d1 is calibrated. Obviously, the power-on time of the device d1 is different from the power-on time of the device d2. Therefore, the boot time of the calibration time recorded by the device device d1 is different from the boot time of the calibration time recorded by the device d2. Although the boot time of the calibration time recorded by the device d1 is different from the boot time of the calibration time recorded by the device d2, both are used to indicate the time when the device d1 and the device d2 are calibrated.

In the same manner, the device d7 records a list of calibration times for d7, see Table 3 below, which holds the power-on duration of the calibration time at which the device d7 and the devices d1, d2 are respectively calibrated.

The booting time of the device d7 and the calibration time of the device d1 is the time difference between the device d7 and the device d1, the time difference from the local start time of the device d7. Similarly, the boot duration of the device d7 and the device d2 calibration time is the time difference between the device d7 and the device d2 calibration time, and the local boot time of the device d7. Table 3 below is a calibration record of device d7 relative to other devices:

Equipment Identity Start-up time at calibration time D1 354931546152ns D2 355689845615ns

table 3

In Table 3, the boot duration of the calibration time recorded by the device d7 - 536745826423 ns indicates that the time difference between the device d7 and the device d1 calibration time and the local power-on time of the device d7 is 536745826423 ns (nanoseconds). Similarly, the boot duration of the calibration time recorded by the device d7 - 190687321593 ns indicates that the time difference between the device d7 and the device d2 calibration time and the local power-on time of the device d7 is 190,687,321, 593 ns (nanoseconds).

In one example, before the device performs time calibration with other devices, such as device 1 prior to time calibration with device 2, device 7, it first determines the devices it discovers, such as device 2, device 7, and device 1 The distance allows a device that is within a certain threshold range from the device, such as device 1, to perform the next operation, such as performing a time calibration operation.

In one scenario, device d1 first searches for other devices in its vicinity, and performs time alignment with the devices it searches after searching for devices around it. If the device 1 searches for devices in its vicinity, after searching for the device 2 and the device 7, the device 2 and the device 7 are time-aligned. The following describes in detail how the embodiments of the present application find other devices in their vicinity. Specifically, the device 1 scans the devices around it and determines the distance of the device it scans from the device 1. For example, the distance between the device 1 and the device it scans is determined by the strength of the received signal or the delayed response of the request. When the device 1 determines the distance between a device to which it is scanned, such as the device 2, is less than its set threshold, such as 10 meters, the scanned device, such as device 2, is recorded in the device list of the device 1. When the device 1 determines that the distance between a device it scans, such as the device 3, is greater than its set threshold, such as 10 meters, the device 3 will not be recorded in the device list of the device 1, and therefore will not Time calibration is performed with the device 3. That is to say, device 1 only performs time calibration with devices within the valid range.

In summary, the embodiment of the present application obtains more accurate time information of the occurrence of the touch of the device 1 and the device 2 by the calibration time, and determines that the time information of the touch of the device 1 and the device 2 is the same. The touch information of the device 1 matches the touch information of the device 2.

FIG. 3 is a schematic diagram of a handshake method for wireless communication provided by an embodiment of the present application.

In step 310, the device 1 sends a handshake request message to the device 2.

Specifically, the device 1 touches the device 2, and the device 1 acquires information generated by the touch. The private key PK1 is generated based on the information generated by the touch. The device 1 encrypts the data consisting of the token token1 and the sequence corresponding to the response time set by the private key PK1 to obtain the first encrypted message E1. The device 1 then broadcasts the first encrypted message E1. In addition, since the device 1 collides with the device 2, the information generated by the device 2 is the same as that of the device 1, and the private key PK2 generated by the device 2 is the same as the private key PK1 generated by the device 1, that is, PK1=PK2. .

In computers, tokens represent objects that perform certain operations for authentication. There are several ways to generate this token. For example, the token may be a random sequence randomly generated by device 1; it may also be a sequence of sequences generated from private key PK; or it may be a sequence represented by a timestamp that generated the token. In one example, device 1 uses an agreed response time mechanism, ie the response time is set by the device 1, and the response time is used to agree on the time to answer the first encrypted message E1.

The specific method will be explained by Figure 4 and related content.

In step 320, the device 2 verifies the handshake request of the device 1.

Specifically, after the device 2 receives the first encrypted message E1, the device 2 decrypts the first encrypted message E1 by using the private key PK2 to obtain the token token2 and the response time. The device 2 encrypts the data consisting of the token token2 and the request connection time corresponding sequence according to the token token2, and generates a second encrypted message E2 for verifying the handshake request message of the device 1.

Step 330: The device 2 responds to the device 1 according to the verification result of the handshake request from the device 1.

In one example, device 1 uses an agreed response time mechanism, ie, device 2, when the response time arrives, transmits the second encrypted message E2 to respond to the pairing request of device 1. That is, the appointment response time is specified by the device 1.

In one example, device 2 uses an agreed connection time mechanism, ie the request connection time is set by the device 2, which is used to stipulate when device 1 requests device 2 to establish a connection.

Since the device 1 and the device 2 are physically touched, the touch information generated by the device 1 and the device 2 is the same. Therefore, the device 2 can decrypt the first encrypted message E1 according to the PK1 based on the private key PK2 generated by the touch information and the private key PK2=private key PK1.

In addition, since the device 1 and the device 2 are touched, the device 1 and the device 2 want to complete the handshake process of mutual trust, and the private key PK1 generated by the device 1 is the same as the private key PK2 generated by the device 2. Therefore, the token token2 obtained by the device 2 decrypting the first encrypted message E1 is the token token1 generated by the device 1.

The specific process can be illustrated by Figure 5 and the corresponding content.

In step 340, the device 1 requests the device 2 to establish a connection.

Specifically, after the device 1 receives the second encrypted message E2 from the device 2, the device 1 decrypts the second encrypted message E2 through the token token1 it generates, thereby decrypting the connection established by the token token3 and the device 2. Request time. The device 1 determines that the token token3 obtained by decrypting the second encrypted message E2 is the same as the token token1 it generates, and transmits a connection establishment request message to the device 2.

In one example, the device 1 transmits a connection establishment request message to the device 2 when the connection request time set by the device 2 arrives. The specific process will be explained through Figure 6 and the corresponding content.

It should be noted that the embodiment of the present application is an appointment time, for example, an appointment response time and an agreed connection time. The purpose is to improve the security of handshaking between devices. In fact, the embodiment of the present application is not limited thereto, that is, the embodiment of the present application may not adopt an appointment time mechanism.

In step 350, the device 2 responds to the connection establishment request of the device 1, that is, the device 2 sends a connection establishment request response message to the device 1.

Step 360, connection establishment request message The device 1 determines that the device 1 has received the connection establishment request message from the device 2. And in the device 1, the device 2 agrees to establish a connection request of the other device.

In step 370, the device 1 successfully establishes a connection with the device 2, and completes the handshake process of mutual trust.

That is, the device 2 also needs to send a handshake request to the device 1, and then the device 1 verifies the handshake request of the device 2 and responds to the device 1, and then the device 2 requests the device 1 to establish a connection, and finally the device 1 A connection will be established with device 2.

The specific process will be explained through Figure 7 and the corresponding content.

FIG. 4 is a flowchart of a device request pairing handshake provided by an embodiment of the present application.

In step 401, the device 1 sends a handshake request message to the device 2 to start the handshake listening mode. The handshake listening mode refers to a mode capable of listening to devices that are in a wireless communication handshake with the periphery.

In one example, the user initiates a handshake listening mode. For example, the user turns on the handshake button in device 1 and activates the handshake mode of device 1. As another example, the device 1 initiates a handshake listening mode by scanning a two-dimensional code. In step 402, the device 1 searches for nearby devices, and records the unique identifiers of the devices in the vicinity thereof that are searched in a tabular manner. For example, device 1 searches for nearby device 2 - device 7 and records the physical address of device 2-7, such as a Media Access Control (MAC) address, to list L0.

In step 403, the device 1 determines the device status of each device in the list L0, and the device status includes a handshake listening state and a non-handshake listening state. The device 1 filters out the device in the handshake listening state from the list L0, and composes the device in the handshake listening state into the list L1.

In one example, device 1 is tagged with a device state, such as a handshake listening state or a non-handshake listening state, in a data packet in which device 1 interacts with other devices while searching for devices in its vicinity.

In step 404, the device 1 performs time calibration with each device in the list L1, and separately records the booting time of the corresponding calibration time, as shown in Table 1 above.

Taking FIG. 2 as an example, the booting time of the calibration time of the device 1 and the device 2 recorded by the device 1 is the difference between the local time of the device 1 and the power-on time of the device 1 during calibration; the device 1 records The booting time of the calibration time of the device 1 and the device 7 is the difference between the local time of the device 1 and the power-on time of the device 1 during calibration.

In step 405, the device 1 touches the device 2, as shown in FIG. 1, the device 1 acquires the touch information.

In one example, the device 1 records time information that the device 1 has touched the device 2.

In another example, the audio information generated by the device 1 touching the device 2 is acquired using a pickup of the device 1, such as a microphone.

In yet another example, the accelerometer of the device 1 is used to obtain acceleration information generated by the device 1 touching the device 2.

In another example, the angular velocity meter of the device 1 is used to obtain rotation information generated by the device 1 touching the device 2, including angular velocity, acceleration, rotational moment, and the like.

In yet another example, the device 1 integrates a low cost piezoelectric sensor for acquiring the device 1 and the device 2 Touch the generated vibration signal.

The embodiments of the present application can obtain the lowest information of existing devices, such as a pickup, an accelerometer, an angular velocity meter, etc., or by adding a low-cost sensor such as a piezoelectric sensor to obtain information generated by mutual contact between devices, thereby being able to minimize The device cost solves the handshake problem between devices.

Step 406: Extract features according to information generated by the touch of the device 1 and the device 2, and generate a private key PK.

For example, a plurality of features in the information such as the time information of the touch of the device 1, the device 2, the audio information, the acceleration information, the angular velocity information, and the like are extracted, and a mathematical algorithm such as a weighted average algorithm is used for the plurality of features to generate the private key PK. For example, the rotation information is recorded by an angular velocity meter, including angular velocity, acceleration, rotational moment, and the like.

Different devices or different types of devices may use different values to represent audio information, acceleration information, and angle information generated by the same touch. For example, device 1 collides with device 2, the collision amplitude recorded by device 1 is 5, and the collision pressure recorded by device 2 is 10. The waveforms of the collision between the device 1 and the device 2 are the same, except that the values recorded by different devices are different.

In order to solve the above problem, the embodiment of the present application may perform a normalization process by using a normalization algorithm for one or more of the multiple information generated by the touch. For example, set the maximum pressure for all equipment collisions to be 1, and use this ratio to calculate other pressure values. The embodiment of the present application processes the information generated by the touch by a normalization algorithm, so that different devices generate the same value in the information generated by the same touch.

In another example, the information extracted from the information generated by the collision is extracted from the time information of the audio information generated by the touch or the peak of the acceleration information or the angle information. For example, the device 1 records the change of the audio information of the device 1 with time in a waveform manner, and extracts a set of power-on durations corresponding to the peaks of the audio waveform, and calculates a private key as an original parameter.

It should be noted that there are various ways to extract features according to information generated by collisions, and examples are not given here.

In step 407, the device 1 generates a token token1 and generates an agreed response time T1; wherein the response time is represented by a set of sequences.

It should be noted that the response time T1 that the device 1 generates the appointment is only an example, and the embodiment of the present application is not limited thereto. That is to say, the device 1 may also not generate an agreed response time.

There are various ways to generate the token, for example, the token token1 is a set of random sequences generated by the device 1. See step 301 for details.

In step 408, the device 1 uses the generated private key PK (the specific generation mode participates in step 406), and encrypts the data composed of the sequence D1 corresponding to the token token1 and the response time T1 to obtain the first encrypted message E1.

In step 409, the device 1 broadcasts the first encrypted message E1.

Further, the device 1 broadcasts the first encrypted message E1 to each device in the list L1.

It should be noted that FIG. 4 only exemplifies the request of the device 1 for the touch. In fact, the device that touches the device, such as the device 2, needs to perform the above steps 401 to 409 to establish a handshake process of mutual trust. The device 2 requests the touch method to be the same as the device 1 requesting the touch method, and details are not described herein again.

FIG. 5 is a flowchart of a response pairing handshake request provided by an embodiment of the present application. FIG. 5 is an example in which the device 2 verifies the handshake request of the device 1 and responds as an example.

In step 501, the device 2 receives the first encrypted message E1 broadcast by the device 1.

Step 502, the device 2 verifies whether the device 1 exists in its recorded L1 list, and the L1 list is used for storage. The device retrieved by device 1 in the handshake listening state.

Further, the device 2 determines whether the device 1 broadcasts the handshake request ciphertext E1 more than once, and if the request exceeds once, the process ends. The reason is that if device 1 repeatedly broadcasts a handshake request, device 1 is likely to be a malicious attack device. The embodiment of the present application may filter a target device that attempts to falsify other devices by determining the number of times the target device broadcasts the ciphertext.

In step 503, the device 2 decrypts the first encrypted message E1 from the device 1 according to its private key PK, and extracts the sequence D1 and the token corresponding to the response time.

In an example, when the device 1 generates the first encrypted message E1, the first encrypted message E1 includes an order relationship between the token and the response time. For example, the first to nth bits are tokens, and the (n+1)th to mth bits are response times; wherein n, m are integers greater than 1, and n is less than m.

In one example, device 2 generates a request connection time, which is the time T2 at which device 1 set by device 2 requests device 2 to establish a connection, the request connection time T2 being represented by a set of sequences. Step 504: The device 2 encrypts the sequence D2 corresponding to the request connection time T2 and the data composed of the token according to the token obtained by the decryption to obtain a second encrypted message E2.

In step 505, the device 2 sends the second encrypted message E2 to the device 1 when it reaches the response time agreed by the device 1.

For example, the time when the device 2 sends the second encrypted message E2 to the device 1 is the sum of the response time decrypted by the device 2 and the calibration time of the device 1 and the device 2.

That is to say, the response time agreed by the device 1 is only a value, such as 231123 ns. This step 507 indicates that the device 2 transmits the second encrypted message E2 to the device 1 when the device 2 and the device 1 perform 231123 ns (nanoseconds) after time calibration.

FIG. 6 is a flowchart of a connection establishment request provided by an embodiment of the present application. FIG. 6 is an example in which the device 1 requests the device 2 to establish a connection.

In step 601, the device 1 receives the second encrypted message E2 from the device 2.

Step 602: The device 1 acquires the identifier of the device 2 from the second encrypted message E2, and records the time T3 of receiving the second encrypted message. Wherein, the time T3 is shown by a set of sequences.

In step 603, the device 1 determines whether the reception time T3 is the response time T1 set by the device 1.

Specifically, the device 1 determines that the time T3 when the device 1 receives the second encrypted message E2 is the sum of the response time T1 set by the device 1 and the calibration time of the device 1 and the device 2.

That is to say, the response time T1 agreed by the device 1 is only a value, for example 231123 ns. This step 603 indicates that the device 2 receives the second encrypted message E2 when the device 2 and the device 1 perform 231123 ns (nanoseconds) after time calibration.

Step 604, the device 1 determines whether the device 2 exists in its recorded L1 list, and the L1 list is used to store the device that the device 1 searches for in the handshake listening state.

Those skilled in the art can understand that step 603 and step 604 have no sequential relationship. Step 603 and step 604 may be performed at the same time. Step 603 may be performed first and then step 604 may be performed. Step 604 may be performed first and then step 603 may be performed.

In one example, to filter a maliciously attacked device, device 1 determines that device 2 sends a second encrypted message. The number of times of E2 determines whether the number of times exceeds one time. If it exceeds one time, the process ends.

In another example, device 1 determines the aforementioned steps 401 - 409 and steps 501 - 508 have been performed. That is, the device 1 determines that the device 1 has sent a handshake request to the device 2, and the device 2 verifies and responds to the handshake request. If device 1 does not send a handshake request to device 2, and/or device 2 does not verify and respond to the handshake request, it is a malicious request, ending the process.

Step 605: The device 1 decrypts the second encrypted message E2 received by the device according to the generated token token1, obtains the request connection time T2, and obtains the token token2.

In step 606, the device 1 determines whether the decrypted token token2 is equal to the token token1 generated by the device 1. If not, the process ends.

In step 607, the device 1 terminates the request sent to it by the other devices of the device 2, and only receives the connection establishment request from the device 2.

Step 608, when the device 1 arrives at the request connection time T2, it sends a message to the device 2 to establish a connection request.

Specifically, the time when the device 1 sends the connection establishment request message to the device 2 is the sum of the calibration time of the device 1 and the device 2, the response time agreed by the device 1, and the connection request time obtained by decrypting the second encrypted message E2.

That is to say, the connection request time agreed by the device 2 is only a value, for example, 43252 ns. This step 607 indicates that the device 1 transmits a connection establishment request message to the device 2 at the time of 43252 ns after the response time.

In one example, the response time is the sum of the response time agreed by device 1 and the time of calibration of device 1 and device 2.

FIG. 7 is a flowchart of a response connection request provided by an embodiment of the present application. FIG. 7 is an illustration of the case where the device 2 responds to the connection request of the device 1 as an example.

In step 701, the device 2 receives a connection establishment request message from the device 1.

Step 702: The device 2 acquires the identifier of the device 1 from the connection establishment request message, and records the time T4 of receiving the connection establishment request message.

In step 703, the device 2 determines whether the identifier of the device 1 exists in the L1 list of its record, and the L1 list is used to store the device in the handshake listening state searched by the device 2.

In one example, in order to filter the malicious attack device, the device 2 determines the number of times the connection establishment request message is sent by the device 1, determines whether the number of times exceeds the number of times, and if it exceeds once, ends the process.

In another example, device 2 determines the aforementioned steps 401 - 409, and steps 501 - 508, which have been performed. That is, the device 1 determines that the device 1 has issued a handshake request to the device 2, and the device 2 verifies and responds to the handshake request, and the device 1 transmits a connection establishment request message to the device 2. If device 1 does not send a handshake request to device 2, and/or device 2 does not verify and respond to the handshake request, and/or device 1 has not sent a connection setup request message to device 2, it is a malicious request, ending the process .

In step 704, the device 2 stores the connection establishment request message identifier it receives, and the identifier of the device 1 acquired from the message, and the time T4 at which the message is received, are stored in a connection list.

Step 705, the device 2 determines whether the current device 1 only receives the connection establishment request of the device 2, and has terminated any request of other devices.

Step 706, the device 2 determines that the device that requests the connection from the device 2, that is, the device 1, is the device to which the device 2 previously requested to connect. That is to say, the device 2 determines that the device 2 has requested to establish a connection to the device 1, and the device 1 also requests the device 2 to establish a connection.

Step 707, the device 2 determines that the time T4 when the device 2 receives the connection establishment request message is the time agreed by the device 1 and the device 2. That is, the time T4 at which the device 2 receives the connection establishment request message is the sum of the calibration time of the device 1 and the device 2, the response time T1 generated by the device 1, and the request connection time T2 generated by the device 2.

Those skilled in the art can understand that step 706 and step 707 have no sequential relationship. Step 706 and step 707 may be performed at the same time. Step 706 may be performed first, and then step 707 may be performed. Step 707 may be performed first and then step 706 is performed.

In step 708, the device 2 sends a response message of the connection establishment request to the device 1, and agrees to the connection establishment request of the device 1.

Step 709, if the device 1 agrees to the connection establishment request of the device 2, the connection establishment of the device 1 and the device 2 is successful, thereby completing the handshake process of the mutual trust.

FIG. 8 is a schematic diagram of a first wireless device according to an embodiment of the present application. The first wireless device 800 includes a processor 810, a receiver 820, and a transmitter 830.

The first wireless device and the second wireless device are physically touched.

The processor 810 is configured to acquire first touch information, where the first touch information is information generated when the first wireless device and the second wireless device are physically touched.

The transmitter 830 is configured to send the first touch information to the second wireless device.

The processor 810 is further configured to establish a connection with the second wireless device if the first touch information matches the second touch information, where the second touch information is collected by the second wireless device. Information generated when the first wireless device and the second wireless device are physically touched.

In one example, the transmitter 830 is further configured to send a connection request to the second wireless wireless device. The receiver 820 is configured to receive a connection response sent by the second wireless device. The processor 810 is further configured to establish a connection with the second wireless device; the connection response is a response of the second wireless device to the connection request.

In one example, the receiver 820 is configured to receive a connection request sent by the second wireless device. The transmitter 830 is further configured to send a connection response to the second wireless device. The processor 810 is further configured to establish a connection with the second wireless device; the connection response is a response of the first wireless device to the connection request.

In one example, the transmitter 830 is specifically configured to send the encrypted first touch information to the second wireless device.

In one example, the touch information is one or more of the following: time information of the occurrence of the touch, audio information generated by the touch, acceleration information generated by the touch, generated by the touch Rotation information.

FIG. 9 is a schematic diagram of a second wireless communication device according to an embodiment of the present application. The second wireless communication device 900 includes a receiver 910, a processor 920, and a transmitter 930.

The second wireless device and the first wireless device physically touch.

The receiver 910 is configured to receive first touch information sent by the first wireless device, where the first touch information is generated when the first wireless device and the second wireless device are physically touched. Information.

The processor 920 is configured to: if the first touch information matches the second touch information, the second wireless device establishes a connection with the first wireless device, where the second touch information is Information generated when the first wireless device and the second wireless device collected by the second wireless device are physically touched.

In one example, the receiver 910 is further configured to receive a connection request of the first wireless device. The transmitter 930 is configured to send a connection response to the first wireless device, the second wireless device establishes a connection with the first wireless device, and the connection response is that the second wireless device requests the connection the response to.

In one example, the transmitter 930 is configured to send a connection request to the first wireless device. The receiver 910 is further configured to receive a connection response sent by the first wireless device, where the second wireless device establishes a connection with the first wireless device, and the connection response is that the second wireless device pairs the The response to the connection request.

In one example, the receiver 910 is specifically configured to receive the encrypted first touch information. It should be noted that the embodiment of the present application further provides a computer readable storage medium. A computer program is stored on the computer readable storage medium, the program being executed by the processor of FIG.

Another embodiment of the present application provides a computer readable storage medium. A computer program is stored on the computer readable storage medium, the program being executed by the processor of FIG.

The embodiment of the present application also provides a computer program product including instructions. When the computer program product is run on a computer, the computer is caused to perform the method described above with respect to FIG. 3 or FIG. 4 or FIG. 5 or FIG. 6 or FIG.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer loads and executes the computer program instructions, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).

A person skilled in the art should further appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both, in order to clearly illustrate hardware and software. Interchangeability, the composition and steps of the various examples have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

It will be understood by those skilled in the art that all or part of the steps of implementing the above embodiments may be performed by a program, and the program may be stored in a computer readable storage medium, which is non-transitory ( English: non-transitory) media, such as random access memory, read-only memory, flash memory, hard disk, solid state disk, magnetic tape (English: magnetic tape), floppy disk (English: floppy disk), CD (English: optical disc) And any combination thereof.

The above description is only a preferred embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or within the technical scope disclosed in the present application. Replacement should be covered by the scope of this application. Therefore, the scope of protection of this application should be in the scope of protection of the claims. Prevail.

Claims (31)

  1. A handshake method for wireless communication, characterized in that the method comprises:
    Physical contact between the first device and the second device;
    The first device acquires first touch information, where the first touch information is information generated when the first device and the second device are physically touched;
    Sending, by the first device, the first touch information to the second device;
    If the first touch information matches the second touch information, the first device establishes a connection with the second device, and the second touch information is the first device collected by the second device. Information generated when a physical touch is made with the second device.
  2. The method of claim 1, wherein the establishing, by the first device, the second device comprises:
    Sending, by the first device, a connection request to the second device;
    Receiving, by the first device, a connection response sent by the second device, where the first device establishes a connection with the second device; and the connection response is a response of the second device to the connection request.
  3. The method of claim 1, wherein the establishing, by the first device, the second device comprises:
    Receiving, by the first device, a connection request sent by the second device;
    The first device sends a connection response to the second device, the first device establishes a connection with the second device; and the connection response is a response of the first device to the connection request.
  4. The method according to any one of claims 1 to 3, wherein the sending, by the first device, the first touch information to the second device is that the first device sends the second device to the second device The first touch information after encryption.
  5. The method according to any one of claims 1 to 4, wherein the touch information is one or more of the following: time information of a touch occurrence, audio information generated by the touch, by Touch the generated acceleration information and the rotation information generated by the touch.
  6. The method according to claim 5, wherein the time information of the occurrence of the touch is determined by the first device, the booting time according to the touch time of the first device, the second device, and the first device The start time of the calibration time is determined;
    The time period of the touch of the first device and the second device is the time difference between the first device and the second device being touched by the first device.
    The booting time of the calibration time of the first device is the time difference between the first device and the second device calibration time from the power-on and power-on of the first device.
  7. The method of claim 6, wherein before the first device acquires the first touch information, the method includes:
    The first device performs time calibration with the second device to determine a boot duration of the calibration time.
  8. The method of claim 4, before the sending, by the first device, the encrypted first touch information to the second device, generating the encrypted first touch information;
    The generating the encrypted first touch information includes:
    The first device generates a private key according to the first touch information;
    The first device generates a first random sequence, and the first device encrypts the first random sequence according to the private key to generate the encrypted first touch information.
  9. The method according to claim 8, wherein before the generating the encrypted first touch information, the first device determines a time when the second device answers to the first device;
    The first device encrypts the first random sequence according to the private key, and generates the encrypted first touch information, specifically:
    The first device encrypts the first random sequence and the random sequence corresponding to the response time according to the private key, and generates the encrypted first touch information.
  10. The method according to claim 9, wherein after the first device sends the encrypted first touch information to the second device, the method includes:
    The first device receives the encrypted second touch information from the second device, and the first device decrypts the encrypted second touch information according to the first random sequence.
  11. A handshake method for wireless communication, characterized in that the method comprises:
    Physical contact between the first device and the second device;
    Receiving, by the first device, the first touch information sent by the second device, where the first touch information is information generated when the first device and the second device are physically touched;
    If the first touch information matches the second touch information, the first device establishes a connection with the second device, and the second touch information is the first device collected by the first device. Information generated when a physical touch is made with the second device.
  12. The method of claim 11, wherein the establishing, by the first device, the connection with the second device comprises:
    Receiving, by the first device, a connection request of the second device;
    The first device sends a connection response to the second device, the first device establishes a connection with the second device; and the connection response is a response of the first device to the connection request.
  13. The method of claim 11, wherein the establishing, by the first device, the connection with the second device comprises:
    Sending, by the first device, a connection request to the second device;
    Receiving, by the first device, a connection response sent by the second device, where the first device establishes a connection with the second device; and the connection response is a response of the second device to the connection request.
  14. The method according to any one of claims 11 to 13, wherein the first device receives the first touch information, specifically: the first device receives the encrypted first touch information.
  15. The method of claim 14, wherein the first touch information matches the second touch information comprises:
    Decrypting the encrypted first touch information according to the private key of the first device, to obtain a first method for verifying that the first device makes a first response to the second device a random sequence, determining, according to the first random sequence, that the first touch information matches the second touch information;
    The private key of the first device is generated by the first device according to the touch information of the first device and the second device.
  16. The method according to claim 15, wherein the touch information is one or more of the following: time information of the occurrence of the touch, audio information generated by the touch, acceleration information generated by the touch, Rotation information generated by touch.
  17. The method according to claim 15, wherein said first device decrypts said encrypted first touch information and further obtains a time of said first response determined by said second device.
  18. The method according to claim 17, wherein after the decrypting the encrypted touch information by the first device, the method includes: the first device pairs the first random according to the private key The sequence is encrypted to obtain an encrypted first random sequence; the first device transmits the encrypted first random sequence at the first response time.
  19. A first device, wherein the first device and the second device are physically touched; the first device includes: a processor and a transmitter;
    The processor is configured to acquire first touch information, where the first touch information is information generated when the first device and the second device are physically touched;
    The transmitter is configured to send the first touch information to the second device;
    The processor is further configured to establish a connection with the second device if the first touch information matches the second touch information, and the second touch information is the first collected by the second device Information generated when a device and the second device are physically touched.
  20. The first device of claim 19, wherein the first device further comprises a receiver;
    The transmitter is further configured to send a connection request to the second device;
    The receiver is configured to receive a connection response sent by the second device;
    The processor is further configured to establish a connection with the second device; the connection response is a response of the second device to the connection request.
  21. The first device of claim 19, wherein the first device further comprises a receiver;
    The receiver is configured to receive a connection request sent by the second device;
    The transmitter is further configured to send a connection response to the second device;
    The processor is further configured to establish a connection with the second device; the connection response is a response of the first device to the connection request.
  22. The first device according to any one of claims 19 to 21, wherein the transmitter is specifically configured to send the encrypted first touch information to the second device.
  23. The first device according to any one of claims 19 to 22, wherein the touch information is one or more of the following: time information of the occurrence of the touch, and audio information generated by the touch. The acceleration information generated by the touch and the rotation information generated by the touch.
  24. A second device, wherein the second device and the first device are physically touched; the second device includes:
    a receiver, configured to receive first touch information sent by the first device, where the first touch information is information generated when the first device and the second device are physically touched;
    a processor, configured to establish a connection between the first device and the second device, where the second device is connected to the first device, where the second touch information is collected by the second device The information generated when the first device and the second device are physically touched.
  25. A second device according to claim 24, wherein said second device further comprises a transmitter;
    The receiver is further configured to receive a connection request of the first device;
    The transmitter is configured to send a connection response to the first device, the second device establishes a connection with the first device; and the connection response is a response of the second device to the connection request.
  26. A second device according to claim 24, wherein said second device further comprises a transmitter;
    The transmitter is configured to send a connection request to the first device;
    The receiver is further configured to receive a connection response sent by the first device, the second device establishes a connection with the first device, and the connection response is a response of the second device to the connection request.
  27. The second device according to any one of claims 24 to 26, wherein the receiver is specifically configured to receive the encrypted first touch information.
  28. A computer program product comprising instructions, wherein the computer program product, when run on a computer, causes the computer to perform the method of any of claims 1-10.
  29. A computer program product comprising instructions, wherein the computer program product, when run on a computer, causes the computer to perform the method of any of claims 11-18.
  30. A computer readable storage medium, wherein the computer readable storage medium stores a computer program, the computer program being executed by a processor to implement the method of any of claims 1-10.
  31. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program, the computer program being executed by a processor to implement the method of any one of claims 11-18.
PCT/CN2017/091424 2017-03-31 2017-07-03 Handshake method and device for wireless communication WO2018176670A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201710205323.8 2017-03-31
CN201710205323 2017-03-31

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201780009413.8A CN108702606A (en) 2017-03-31 2017-07-03 A kind of handshake method and equipment of wireless communication

Publications (1)

Publication Number Publication Date
WO2018176670A1 true WO2018176670A1 (en) 2018-10-04

Family

ID=63675039

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/091424 WO2018176670A1 (en) 2017-03-31 2017-07-03 Handshake method and device for wireless communication

Country Status (2)

Country Link
CN (1) CN108702606A (en)
WO (1) WO2018176670A1 (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120105346A1 (en) * 2010-10-29 2012-05-03 International Business Machines Corporation Establishing an authenticated wireless connection between short-range wireless terminals more conveniently
CN102545964A (en) * 2010-12-16 2012-07-04 国民技术股份有限公司 Communication method and system for triggering information interaction by collision
CN102869121A (en) * 2012-09-24 2013-01-09 东莞宇龙通信科技有限公司 Method and device for automatically establishing wireless connection
CN105321070A (en) * 2014-07-18 2016-02-10 中国电信股份有限公司 Data processing method and system based on touching manner of mobile terminals

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101959347B1 (en) * 2012-05-25 2019-03-18 삼성전자주식회사 Multiple-display method using a plurality of communication terminals, machine-readable storage medium and communication terminal
CN104378838B (en) * 2014-11-11 2018-05-25 广东欧珀移动通信有限公司 A kind of method and device for establishing wireless connection
CN106355689A (en) * 2016-05-13 2017-01-25 新疆农业大学 RFID-based (radio frequency identification-based) intelligent access control system and method of using same

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120105346A1 (en) * 2010-10-29 2012-05-03 International Business Machines Corporation Establishing an authenticated wireless connection between short-range wireless terminals more conveniently
CN102545964A (en) * 2010-12-16 2012-07-04 国民技术股份有限公司 Communication method and system for triggering information interaction by collision
CN102869121A (en) * 2012-09-24 2013-01-09 东莞宇龙通信科技有限公司 Method and device for automatically establishing wireless connection
CN105321070A (en) * 2014-07-18 2016-02-10 中国电信股份有限公司 Data processing method and system based on touching manner of mobile terminals

Also Published As

Publication number Publication date
CN108702606A (en) 2018-10-23

Similar Documents

Publication Publication Date Title
US10111268B2 (en) System and method for NFC peer-to-peer authentication and secure data transfer
US9763063B2 (en) Secure broadcast beacon communications
US9813236B2 (en) Multi-factor authentication using a smartcard
US20160277933A1 (en) Secure Data Communication system between IoT smart devices and a Network gateway under Internet of Thing environment
US9276753B2 (en) System and method for data authentication among processors
JP2015136121A (en) Updating mobile devices with additional elements
US20160232509A1 (en) System and method for initially establishing and periodically confirming trust in a software application
CN105408910B (en) System and method for being verified using wireless communication to user
US10044512B2 (en) Decoupling of measuring the response time of a transponder and its authentication
US8533123B2 (en) Systems and methods for conducting contactless payments using a mobile device and a magstripe payment card
US20150089586A1 (en) Systems and methods for nfc access control in a secure element centric nfc architecture
US8458776B2 (en) Low-latency peer session establishment
EP1922632B1 (en) Extended one-time password method and apparatus
KR101198120B1 (en) Iris information based 3-factor user authentication method for otp generation and secure two way authentication system of wireless communication device authentication using otp
JP6092415B2 (en) Fingerprint authentication system and fingerprint authentication method based on NFC
US8368516B2 (en) Secure data exchange with a transponder
US8422672B2 (en) Authenticated device, authenticating device and authenticating method
WO2014106546A1 (en) Rfid tag and method for operating an rfid tag
US9749131B2 (en) System and method for implementing a one-time-password using asymmetric cryptography
WO2015160711A1 (en) Service authorization using auxiliary device
US8086868B2 (en) Data communication method and system
US9363670B2 (en) Systems and methods for restricting access to network resources via in-location access point protocol
US9456344B2 (en) Systems, methods and apparatuses for ensuring proximity of communication device
JP4545197B2 (en) Wireless network system and communication method using the same
US20100281261A1 (en) Device and method for near field communications using audio transducers

Legal Events

Date Code Title Description
NENP Non-entry into the national phase in:

Ref country code: DE