Method and device for wearable device to make friends across brands based on public cloud

Abstract

The invention discloses a public cloud-based cross-brand friend making method and device for wearable devices, and the method comprises the steps: a friend making center server obtains a friend making message of a first wearable device, stores a Bluetooth address of a second wearable device in the friend making message in a Bluetooth address pool of the friend making center server, scans the Bluetooth address pool according to a preset interval, and sends the Bluetooth address to the first wearable device; and after determining that the Bluetooth address of the first wearable device uploaded by the second wearable device exists in the Bluetooth address pool and the timestamp difference is less than the preset time, sending a friend-making matching result to the first wearable device and the second wearable device, and sending a friend-making success notification to the first wearable device and the second wearable device. According to the technical scheme, the friend-making center server is set, according to the Bluetooth addresses mutually uploaded by the wearable devices of the two friend-making parties of different brands, after it is determined that the wearable devices of the different brands have friend-making willingness, friend-making matching is determined, friend-making between the wearable devices of the different brands is achieved, the friend-making modes are increased, and the user experience is improved.

Description

Technical Field

[0001] An embodiment of the present invention relates to the technical field of wearable devices, and in particular, to a method and device for cross-brand friend-making of wearable devices based on a public cloud. Background Art

[0002] In recent years, wearable devices have been very popular. A wearable device is a portable device that can be directly worn on the body or integrated into the user's clothes or accessories. A wearable device is not just a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. Wearable devices will bring great changes to our lives and perceptions.

[0003] Currently, with the increase in the number of users of wearable devices, the demand for friend-making among users of wearable devices is also increasing day by day. However, due to the differences in their respective systems and protocols, different brands of wearable devices cannot communicate with each other for friend-making, and only wearable devices of the same brand can complete friend-making, which causes users to be dissatisfied with the friend-making methods of wearable devices. Summary of the Invention

[0004] An embodiment of the present invention provides a method and device for cross-brand friend-making of wearable devices based on a public cloud, which can realize cross-brand friend-making of wearable devices, is not restricted by different brands, increases friend-making methods, and improves the user experience.

[0005] In a first aspect, a method for cross-brand friend-making of wearable devices based on a public cloud provided by an embodiment of the present invention includes:

[0006] A friend-making center server obtains a friend-making message of a first wearable device, where the friend-making message is generated after the first wearable device and a second wearable device scan each other's Bluetooth addresses;

[0007] The friend-making center server stores the Bluetooth address of the second wearable device in the friend-making message in a Bluetooth address pool of the friend-making center server;

[0008] The friend-making center server scans the Bluetooth address pool at a preset interval. After determining that the Bluetooth address of the first wearable device uploaded by the second wearable device exists in the Bluetooth address pool and the timestamp difference is less than a preset time, the friend-making center server sends a friend-making matching result to the first wearable device and the second wearable device;

[0009] After receiving the friend-making confirmation messages of the first wearable device and the second wearable device, the friend-making center server sends a friend-making success notification to the first wearable device and the second wearable device.

[0010] Optionally, the friend-making center server obtains a friend-making message of a first wearable device, including:

[0011] The friend-making center server obtains the friend-making message directly sent by the first wearable device through the public cloud network or the friend-making message generated by the brand server of the first wearable device through the public cloud network according to the friend-making request sent by the first wearable device to the brand server of the first wearable device.

[0012] Optionally, the friend-making center server sends the friend-making matching result to the first wearable device and the second wearable device, including:

[0013] The friend-making center server, based on the brands of the first wearable device and the second wearable device, calls the APIs and SDKs of the brand server of the first wearable device to send the friend-making matching result to the first wearable device, and calls the APIs and SDKs of the brand server of the second wearable device to send the friend-making matching result to the second wearable device.

[0014] Optionally, the method further includes:

[0015] The friend-making center server sends the friend-making matching result to the mobile terminals associated with the first wearable device and the second wearable device respectively.

[0016] Optionally, the friend-making message includes the Bluetooth address of the first wearable device, the Bluetooth address of the second wearable device, device category, protocol number, protocol version number, unique serial number SN of this request, token of this request, and timestamp of this request.

[0017] Optionally, the interaction process between the friend-making center server and the first wearable device and the second wearable device based on the public cloud network adopts a hybrid encryption method of RSA and AESCBC.

[0018] In a second aspect, an embodiment of the present invention provides a device for cross-brand friend-making of wearable devices based on a public cloud, including:

[0019] An obtaining unit, configured to obtain a friend-making message of a first wearable device, where the friend-making message is generated after the first wearable device and a second wearable device scan each other's Bluetooth addresses;

[0020] A processing unit, configured to store the Bluetooth address of the second wearable device in the friend-making message into a Bluetooth address pool of the friend-making center server; scan the Bluetooth address pool at a preset interval, and after determining that the Bluetooth address of the first wearable device uploaded by the second wearable device exists in the Bluetooth address pool and the timestamp difference is less than a preset time, send a friend-making matching result to the first wearable device and the second wearable device;

[0021] After receiving the friend-making confirmation messages of the first wearable device and the second wearable device, send a friend-making success notification to the first wearable device and the second wearable device.

[0022] Optionally, the obtaining unit is specifically configured to:

[0023] Obtain the friend-making message directly sent by the first wearable device through the public cloud network or the friend-making message generated by the brand server of the first wearable device based on the friend-making request sent by the first wearable device to the brand server of the first wearable device through the public cloud network.

[0024] Optionally, the processing unit is specifically configured to:

[0025] According to the brands of the first wearable device and the second wearable device, call the APIs and SDKs of the brand server of the first wearable device to send the friend-making matching result to the first wearable device, and call the APIs and SDKs of the brand server of the second wearable device to send the friend-making matching result to the second wearable device.

[0026] Optionally, the processing unit is further configured to:

[0027] Send the friend-making matching result to the mobile terminals associated with the first wearable device and the second wearable device respectively.

[0028] Optionally, the friend-making message includes the Bluetooth address of the first wearable device, the Bluetooth address of the second wearable device, the device category, the protocol number, the protocol version number, the unique serial number SN of this request, the token of this request, and the timestamp of this request.

[0029] Optionally, the interaction process between the friend-making central server and the first wearable device and the second wearable device based on the public cloud network adopts a hybrid encryption method of RSA and AESCBC.

[0030] In a third aspect, an embodiment of the present invention further provides a computing device, including:

[0031] A memory for storing program instructions;

[0032] A processor for calling the program instructions stored in the memory and executing the method for cross-brand friend-making of wearable devices based on the public cloud according to the obtained program.

[0033] In a fourth aspect, an embodiment of the present invention further provides a computer-readable non-volatile storage medium, including computer-readable instructions, when a computer reads and executes the computer-readable instructions, enabling the computer to execute the method for cross-brand friend-making of wearable devices based on the public cloud.

[0034] In the embodiment of the present invention, the friendship center server obtains the friendship messages of the first wearable device. The friendship messages are generated after the first wearable device and the second wearable device scan each other's Bluetooth addresses. The Bluetooth address of the second wearable device in the friendship messages is stored in the Bluetooth address pool of the friendship center server. The Bluetooth address pool is scanned at a preset interval. After determining that there is the Bluetooth address of the first wearable device uploaded by the second wearable device in the Bluetooth address pool and the time stamp difference is less than the preset time, a friendship matching result is sent to the first wearable device and the second wearable device. After receiving the friendship confirmation messages of the first wearable device and the second wearable device, a friendship success notification is sent to the first wearable device and the second wearable device. By setting up a friendship center server to determine the friendship matching after determining the friendship willingness of wearable devices of different brands based on the Bluetooth addresses uploaded by each other of the friendship parties of different brands, the friendship between wearable devices of different brands is realized, the friendship methods are increased, and the user experience is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0036] Figure 1 FIG. [X] is a schematic diagram of a system architecture provided by an embodiment of the present invention;

[0037] Figure 2 FIG. [X] is a schematic flowchart of a method for cross-brand friendship of wearable devices based on a public cloud provided by an embodiment of the present invention;

[0038] Figure 3 FIG. [X] is a schematic diagram of the structure of a binary data packet provided by an embodiment of the present invention;

[0039] Figure 4 FIG. [X] is a schematic diagram of the structure of a device for cross-brand friendship of wearable devices based on a public cloud provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0040] In order to make the objectives, technical solutions and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the drawings. Obviously, the described embodiments are only some of the embodiments of the present invention, rather than all of them. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0041] Figure 1Exemplarily, a system architecture applicable to embodiments of the present invention is shown. The system architecture may be a dating center server 100, a first wearable device 200, and a second wearable device 300.

[0042] Among them, the dating center server 100 is a server for making friends between wearable devices of different brands. It is used to confirm the existence of a willingness to make friends between wearable devices of different brands, so as to complete the making of friends between wearable devices of different brands.

[0043] The first wearable device 200 and the second wearable device 300 are wearable devices of different brands, and can interact with the dating center server 100 through a public cloud network. The first wearable device 200 and the second wearable device 300 may be children's smart watches, children's smart bracelets, or other Bluetooth-enabled devices that children can wear.

[0044] It should be noted that the above Figure 1 shown structure is only an example, and the embodiments of the present invention do not limit this.

[0045] Figure 2 Exemplarily, a process for cross-brand friend-making of wearable devices based on a public cloud provided by embodiments of the present invention is shown. This process can be executed by a device for cross-brand friend-making of wearable devices based on a public cloud. The device may be a dating center server or may be located within the dating center server.

[0046] As Figure 2 shown, this process specifically includes:

[0047] Step 201, the dating center server obtains a friend-making message of the first wearable device.

[0048] In embodiments of the present invention, this friend-making message is generated after the first wearable device and the second wearable device scan each other's Bluetooth addresses. The first wearable device and the second wearable device are wearable devices of different brands. Since some brands of wearable devices are relatively old and do not have the function of directly interacting with the dating center server, and they need to be forwarded by their corresponding brand servers for the corresponding friend-making messages, when the dating center server obtains the friend-making message of the first wearable device, specifically, it may be: the dating center server obtains the friend-making message directly sent by the first wearable device through the public cloud network or the friend-making message generated by the brand server of the first wearable device according to the friend-making request sent by the first wearable device to the brand server of the first wearable device through the public cloud network.

[0049] That is to say, considering that if the old equipment already on the market needs to be upgraded to access the dating center and the user upgrade time is too long, it can also connect to the dating center through the servers of each brand, upload dating messages, and the protocol for server connection is the same as that of the device. Old devices of each brand send old dating messages to their own servers, and the servers of each brand package the messages required by the dating center and transparently transmit them to the dating center for pairing processing.

[0050] The above-mentioned dating center server is a dating center node built based on the public cloud network. It can be built by region or across the entire server. When configuring the dating center server, a virtual machine with a CPU higher than 4 cores and more than 16G of memory is selected, the system selects a version of Linux CentOS release 7.5 or higher, the server has public network access, and it has Java JDK 1.8 or higher to run Java application processes. The dating center server can utilize the currently open public network APIs and SDKs of each wearable device brand. The dating center server integrates the APIs and SDKs of each wearable device brand and has basic capabilities such as information query and message sending for wearable devices.

[0051] The above-mentioned dating messages include the Bluetooth address of the first wearable device, the Bluetooth address of the second wearable device, device category, protocol number, protocol version number, unique request number SN for this request, token for this request, and timestamp for this request. That is to say, the necessary fields for wearable devices to upload dating messages to the dating center using the common network include their own Bluetooth address btMac, scanned addresses scanMacs, device category deviceType, protocol number CID, protocol version number Version, unique request number SN for this request, token for this request, and timestamp for this request accurate to milliseconds.

[0052] In the actual application process, the JSON data format can be adopted and the entire package is encrypted and then sent to the dating center. An example request for this dating message can be as follows:

[0053] {

[0054] "PL": {

[0055] "btMac": ”xx:xx:xx:xx:xx:xx”,

[0056] "scanMacs": [

[0057] "xx:xx:xx:xx:xx:xx" ]

[0059] },

[0060] "timestamp": ”20241216174620123”,

[0061] "deviceType":"xiaoxun",

[0062] "token":"E14D46C614404B3B812E7C9F02284E5C",

[0063] "SN":1611738150,

[0064] "Version":"00910000",

[0065] "CID":10281

[0066] }

[0067] Step 202: The dating center server stores the Bluetooth address of the second wearable device in the friendship message into the Bluetooth address pool of the dating center server.

[0068] After the dating center server receives a friendship message, it can store the Bluetooth address of the second wearable device in the friendship message into the Bluetooth address pool of the dating center server. This Bluetooth address pool is mainly used to match the Bluetooth addresses of wearable devices that want to be friends with each other to confirm the existence of a friendship intention between the two.

[0069] Step 203: The dating center server scans the Bluetooth address pool at a preset interval. After determining that the Bluetooth address of the first wearable device uploaded by the second wearable device exists in the Bluetooth address pool and the timestamp difference is less than a preset time, it sends a friendship matching result to the first wearable device and the second wearable device.

[0070] Specifically, this preset interval time can be set based on experience. For example, it can be 100 milliseconds. The dating center server sets a scheduled task to scan the Bluetooth address pool every 100 milliseconds at regular intervals. This preset time can be set based on experience. For example, it can be 30 seconds.

[0071] In the actual operation process, after a wearable device uploads its Bluetooth address and stores it in the dating center Bluetooth address pool, an expiration duration of 2 minutes is set for each device's Bluetooth address, and the expiration time can be adjusted according to the actual situation. The dating center scheduled task scans the Bluetooth address pool every 100 milliseconds. If it is found that wearable devices upload each other's Bluetooth addresses, that is, device A uploads the Bluetooth address of device B, and device B also uploads the Bluetooth address of device A, and the timestamp difference between both sides is less than 30 seconds (considering that the time of each wearable device may not be accurate, here the time is calculated based on the server time when the dating center server receives the request when the device uploads the message), it is regarded that both sides have the intention to be friends and the friendship pairing is completed.

[0072] Step 204, after receiving the friend-making confirmation messages from the first wearable device and the second wearable device, the friend-making center server sends a friend-making success notification to the first wearable device and the second wearable device.

[0073] Specifically, the friend-making center server calls the APIs and SDKs of the brand server of the first wearable device to send the friend-making matching result to the first wearable device according to the brand of the first wearable device and the brand of the second wearable device, and calls the APIs and SDKs of the brand server of the second wearable device to send the friend-making matching result to the second wearable device.

[0074] Furthermore, in order to better pay attention to the safety of the users of the wearable devices, the parents of the users of the wearable devices also need to confirm the friend-making process. Therefore, the friend-making center server can also send the friend-making matching result to the mobile terminals respectively associated with the first wearable device and the second wearable device.

[0075] Considering the particularity of the wearable devices, the embodiment of the present invention also has a friend-making authorization mechanism. The pairing result of each friend-making is pushed by the friend-making center server to the parent APP related to the wearable device. The parent APP selects whether to agree to authorize. Only after both parent APPs agree, is it regarded as the completion of the friend-making. If considering the flexibility of friend-making, the friend-making center server can also not push to the parent APP, and the friend-making is completed as soon as the pairing is successful. The specific selection can be determined according to the product plan and the actual scenario. This friend-making mechanism has this authorization ability and can be selected according to the actual situation.

[0076] After the friend-making pairing is completed, through the integrated APIs and SDKs of each brand, call the message push interfaces of each family to send the pairing result to the open platforms of each brand. The open platforms of each brand push to their own watches and APPs according to the key information such as pushtoken in the message. If parent-end authorization is required, you can choose to call the push SDK of the mobile phone manufacturer to send it to the parent APP. Currently, mainstream mobile phone manufacturers such as Huawei, Xiaomi, Oppo, Vivo, and Apple all have open platforms and push SDKs or APIs on their official websites. Send the message to the corresponding model platform, and the platform pushes it to the user's mobile phone. After the friend-making message is pushed to the user's mobile phone, the whole friend-making forms a closed loop.

[0077] Considering the particularity of the users of the wearable devices, the safety of the friend-making process is also a part that needs to be focused on. The interaction process between the friend-making center server and the first wearable device and the second wearable device based on the public cloud network adopts a mixed encryption method of RSA and AESCBC.

[0078] Specifically, the protocol communication between the wearable device and the dating center server adopts the RSA+AESCBC hybrid encryption method. The public key is issued to the wearable device. Each time the wearable device requests the dating center server, a 16-byte secret key is randomly generated. The random secret key is encrypted with the RSA public key, and then the message content is encrypted with the random secret key. After the overall message is encrypted, it is communicated and transmitted with the dating center server.

[0079] Use RSA+AESCBC encryption. The AES secret key is randomly generated by the wearable device side. The RSA public key is used to encrypt the AES secret key, and the AES secret key is used to encrypt the data content. The RSA public key is issued by the dating center server. After each wearable device accesses the dating center server and submits relevant information, the dating center server issues the public key for data communication encryption. The AES secret key is randomly generated by the wearable device and is used to encrypt the data content during the communication process.

[0080] The AES encryption method is AES / CBC / PKCS5Padding, the RSA encryption method is SHA1WithRSA, and the key length is 1024. The corresponding encryption method can be adjusted according to the access situation of the wearable device in the future.

[0081] The AES secret key is generated by the wearable device. The subsequent message up and down uses this secret key for encryption, and a Key is randomly generated each time the wearable device requests. The overall packet assembly reference message is as follows. PT1 is the part encrypted with the RSA public key and is used to store the random secret key of AES; PT2 is the part of the AES encrypted request message and is used to store the message encrypted after the service:

[0082] {"PT1": "AES secret key encrypted string", "PT2": "JSON message AES encrypted string"}.

[0083] Among them, the structure of the binary data packet can be as Figure 3 shown. Among them, the data header packet uses 2 bytes to represent the length, and then the encrypted whole packet content is followed.

[0084] In the embodiment of the present invention, each wearable device has a Bluetooth address. Since the Bluetooth address, that is, btMac, has global uniqueness, it can be regarded as the unique feature value of each wearable device. Moreover, after the device turns on the Bluetooth, it will also be scanned by other wearable devices with Bluetooth scanning functions. The dating center uses the btMac of the wearable device to develop its own dating pairing algorithm for dating pairing processing. In combination with the integrated APIs and SDKs of each brand, it realizes the query of wearable devices and the sending of dating result messages, thus realizing a complete dating process.

[0085] The above embodiments show that the friend-making center server obtains the friend-making messages of the first wearable device. The friend-making messages are generated after the first wearable device and the second wearable device scan each other's Bluetooth addresses. The Bluetooth address of the second wearable device in the friend-making messages is stored in the Bluetooth address pool of the friend-making center server. The Bluetooth address pool is scanned at a preset interval. After determining that there is the Bluetooth address of the first wearable device uploaded by the second wearable device in the Bluetooth address pool and the timestamp difference is less than the preset time, a friend-making matching result is sent to the first wearable device and the second wearable device. After receiving the friend-making confirmation messages of the first wearable device and the second wearable device, a friend-making success notification is sent to the first wearable device and the second wearable device. By setting up a friend-making center server to determine the friend-making matching after determining the friend-making willingness of wearable devices of different brands based on the Bluetooth addresses uploaded by each other of the friend-making parties of different brands, the friend-making between wearable devices of different brands is realized, the friend-making methods are increased, and the user experience is improved.

[0086] Based on the same technical concept, Figure 4 Exemplarily, the structure of a device for cross-brand friend-making of wearable devices based on a public cloud provided by an embodiment of the present invention is shown. This device can execute the process of cross-brand friend-making of wearable devices based on a public cloud.

[0087] As Figure 4 shown, the device may include:

[0088] An obtaining unit 401, configured to obtain the friend-making messages of the first wearable device, where the friend-making messages are generated after the first wearable device and the second wearable device scan each other's Bluetooth addresses;

[0089] A processing unit 402, configured to store the Bluetooth address of the second wearable device in the friend-making messages in the Bluetooth address pool of the friend-making center server; scan the Bluetooth address pool at a preset interval, and after determining that there is the Bluetooth address of the first wearable device uploaded by the second wearable device in the Bluetooth address pool and the timestamp difference is less than the preset time, send a friend-making matching result to the first wearable device and the second wearable device;

[0090] After receiving the friend-making confirmation messages of the first wearable device and the second wearable device, send a friend-making success notification to the first wearable device and the second wearable device.

[0091] Optionally, the obtaining unit 401 is specifically configured to:

[0092] Obtain the friend-making messages directly sent by the first wearable device through the public cloud network or the friend-making messages generated by the brand server of the first wearable device through the public cloud network according to the friend-making requests sent by the first wearable device to the brand server of the first wearable device.

[0093] Optionally, the processing unit 402 is specifically configured to:

[0094] According to the brands of the first wearable device and the second wearable device, call the APIs and SDKs of the brand server of the first wearable device to send the friend-making matching result to the first wearable device, and call the APIs and SDKs of the brand server of the second wearable device to send the friend-making matching result to the second wearable device.

[0095] Optionally, the processing unit 402 is further configured to:

[0096] Send the friend-making matching result to the mobile terminals associated with the first wearable device and the second wearable device respectively.

[0097] Optionally, the friend-making message includes the Bluetooth address of the first wearable device, the Bluetooth address of the second wearable device, the device category, the protocol number, the protocol version number, the unique serial number SN of this request, the token of this request, and the timestamp of this request.

[0098] Optionally, the interaction process between the friend-making center server and the first wearable device and the second wearable device based on the public cloud network adopts a hybrid encryption method of RSA and AESCBC.

[0099] Based on the same technical concept, an embodiment of the present invention further provides a computing device, including:

[0100] A memory for storing program instructions;

[0101] A processor for calling the program instructions stored in the memory and executing the method for cross-brand friend-making of wearable devices based on the public cloud according to the obtained program.

[0102] Based on the same technical concept, an embodiment of the present invention further provides a computer-readable non-volatile storage medium, including computer-readable instructions, which when read and executed by a computer, cause the computer to execute the method for cross-brand friend-making of wearable devices based on the public cloud.

[0103] The present invention is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, and the combination of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate for implementing in the process Figure 1one or more processes and / or blocks Figure 1 means for the functions specified in one or more blocks.

[0104] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means that implement the functions in the process Figure 1 one or more processes and / or blocks Figure 1 specified in one or more blocks.

[0105] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable apparatus provide steps for implementing the functions in the process Figure 1 one or more processes and / or blocks Figure 1 specified in one or more blocks.

[0106] Although the preferred embodiments of the present invention have been described, additional changes and modifications can be made by those skilled in the art once they learn of the basic inventive concept. Therefore, the appended claims are intended to be construed to include the preferred embodiments and all changes and modifications falling within the scope of the present invention.

[0107] Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention is also intended to include these modifications and variations.

Claims

1. A method for cross-brand friendship of wearable devices based on public cloud, characterized in that: include: The friendship center server obtains a friendship message from the first wearable device, where the friendship message is generated after the first wearable device and the second wearable device scan each other's Bluetooth addresses; The dating center server stores the Bluetooth address of the second wearable device in the dating message into the Bluetooth address pool of the dating center server; The dating center server scans the Bluetooth address pool at a preset interval, and after determining that the Bluetooth address of the first wearable device uploaded by the second wearable device exists in the Bluetooth address pool and the timestamp difference is less than a preset time, sends a dating matching result to the first wearable device and the second wearable device; After receiving the friendship confirmation message from the first wearable device and the second wearable device, the friendship center server sends a friendship success notification to the first wearable device and the second wearable device.

2. The method according to claim 1, characterized in that The friendship center server obtains the friendship message of the first wearable device, including: The friendship center server obtains a friendship message directly sent by the first wearable device through the public cloud network or a friendship message generated by the brand server of the first wearable device through the public cloud network according to a friendship request sent by the first wearable device to the brand server of the first wearable device.

3. The method according to claim 1, characterized in that The friendship center server sends a friendship matching result to the first wearable device and the second wearable device, including: The friendship center server calls the API and SDK of the brand server of the first wearable device to send the friendship matching result to the first wearable device, and calls the API and SDK of the brand server of the second wearable device to send the friendship matching result to the second wearable device according to the brand of the first wearable device and the brand of the second wearable device.

4. The method according to claim 3, characterized in that The method further comprises: The dating center server sends the dating matching result to the mobile terminals associated with the first wearable device and the second wearable device respectively.

5. The method according to claim 1, characterized in that The dating message includes the Bluetooth address of the first wearable device, the Bluetooth address of the second wearable device, the device category, the protocol number, the protocol version number, the unique number SN of this request, the token of this request, and the timestamp of this request.

6. The method according to any one of claims 1 to 5, characterized in that: The interaction process between the friendship center server and the first wearable device and the second wearable device based on the public cloud network adopts RSA and AESCBC hybrid encryption method.

7. A device for making friends across brands using a wearable device based on a public cloud, characterized in that: include: An acquiring unit, configured to acquire a friendship message from the first wearable device, wherein the friendship message is generated after the first wearable device and the second wearable device scan each other's Bluetooth addresses; A processing unit, configured to store the Bluetooth address of the second wearable device in the dating message into a Bluetooth address pool of a dating center server; scan the Bluetooth address pool at a preset interval, and after determining that the Bluetooth address of the first wearable device uploaded by the second wearable device exists in the Bluetooth address pool and the timestamp difference is less than a preset time, send a dating matching result to the first wearable device and the second wearable device; After receiving the friendship confirmation messages from the first wearable device and the second wearable device, a friendship success notification is sent to the first wearable device and the second wearable device.

8. The device according to claim 7, characterized in that The acquisition unit is specifically used for: Obtain a friendship message directly sent by the first wearable device through the public cloud network or a friendship message generated by the brand server of the first wearable device through the public cloud network according to a friendship request sent by the first wearable device to the brand server of the first wearable device.

9. A computing device, characterized in that include: A memory for storing program instructions; A processor, configured to call the program instructions stored in the memory, and execute the method according to any one of claims 1 to 6 according to the obtained program.

10. A computer-readable non-volatile storage medium, characterized in that: The method comprises computer-readable instructions, and when a computer reads and executes the computer-readable instructions, the computer is caused to execute the method according to any one of claims 1 to 6.

Images