Device Authentication Networking Method, Device, Equipment and Storage Medium

Abstract

The present application discloses a device authentication networking method, apparatus, device, and storage medium. The method includes: when discovering a second device to be authenticated and networked based on a distributed soft bus, obtaining the device information of the second device; obtaining the device information of the second device through a short-range wireless communication method; if the device information obtained twice is consistent, initiating networking with the second device and sending the device information to a cloud server, so that the cloud server queries a database that stores the device information of each device based on the device information, and if the device information is queried from the database, determining that the authentication of the second device is passed and returning a passing result; when receiving the passing result returned by the cloud server, confirming that the networking is successful, thereby improving the applicability of device authentication networking based on a distributed soft bus.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a device authentication networking method, apparatus, device, and storage medium. Background Art

[0002] Distributed soft bus technology can achieve unified distributed communication management capabilities among near-field devices, providing discovery, connection, networking, and transmission capabilities between devices without distinguishing links. Currently, when networking with a distributed soft bus, only pin (Personal Identification Number) code authentication is supported, and an authorization prompt interface, a pin code display interface, and a pin code input interface for pin code authentication need to be provided. That is, the authentication of the distributed soft bus only supports identity authentication through pin code display and input, and authentication networking cannot be performed on screenless devices, so its applicability is limited.

[0003] Therefore, how to improve the applicability of device authentication networking based on a distributed soft bus has become an urgent problem to be solved. Summary of the Invention

[0004] Embodiments of this application provide a device authentication networking method, apparatus, device, and storage medium, which can improve the applicability of device authentication networking based on a distributed soft bus.

[0005] In a first aspect, embodiments of this application provide a device authentication networking method, and the device authentication networking method includes:

[0006] When a second device to be authenticated and networked is discovered based on a distributed soft bus, obtain the device information of the second device;

[0007] Obtain the device information of the second device through a short-range wireless communication method;

[0008] If the device information obtained twice is the same, initiate networking with the second device, and send the device information to a cloud server for the cloud server to query a database that stores the device information of each device based on the device information. If the device information is queried from the database, it is determined that the authentication of the second device is passed, and a passing result is returned;

[0009] When receiving the passing result returned by the cloud server, confirm that the networking is successful.

[0010] In a second aspect, embodiments of this application further provide a device authentication networking apparatus, and the device authentication networking apparatus includes a processor and a memory. A computer program is stored in the memory, and when the processor calls the computer program in the memory, it executes the above device authentication networking method.

[0011] In a third aspect, an embodiment of the present application further provides a device, and the device includes the device authentication networking device as described above.

[0012] In a fourth aspect, an embodiment of the present application further provides a storage medium, which is used to store a computer program. When the computer program is executed by a processor, the processor implements the above-mentioned device authentication networking method.

[0013] An embodiment of the present application provides a device authentication networking method, device, device and storage medium. When a second device to be authenticated and networked is discovered based on a distributed soft bus, the device information of the second device is obtained, and the device information of the second device is obtained through a short-range wireless communication method. The device information obtained twice is compared. If the device information obtained twice is the same, a network connection is initiated to the second device, and the device information is sent to a cloud server. Based on the received device information, the cloud server queries a database that stores the device information of each device. If consistent device information is found in the database, it is determined that the authentication of the second device is passed, and a passing result is returned. When the passing result returned by the cloud server is received, it is confirmed that the network connection is successful. During the whole process, there is no need to provide an authorization prompt interface for PIN code authentication, a PIN code display interface, a PIN code input interface, etc. The authentication and networking can also be realized for a device without a screen. Therefore, the applicability of device authentication networking based on a distributed soft bus is improved. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0015] Figure 1 It is a schematic flowchart of the authentication and networking process of a currently screen-equipped device;

[0016] Figure 2 It is a schematic flowchart of the steps of a device authentication networking method provided by an embodiment of the present application;

[0017] Figure 3 It is a schematic flowchart of the process of configuring the TAG label of a device provided by an embodiment of the present application;

[0018] Figure 4 It is a schematic diagram of a PAD service flow provided by an embodiment of the present application;

[0019] Figure 5 It is a schematic flowchart of the steps of sending the device information to the cloud server provided by an embodiment of the present application;

[0020] Figure 6 It is a schematic diagram of the authentication process of a device provided by an embodiment of the present application;

[0021] Figure 7 It is a schematic block diagram of a device authentication networking device provided by an embodiment of the present application. Detailed implementation manners

[0022] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts belong to the scope of protection of the present application.

[0023] It should be noted that the descriptions involving "first", "second", etc. in the present application are only for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the quantity of the indicated technical features. Thus, the features defined with "first" and "second" may explicitly or implicitly include at least one of such features.

[0024] The reference to "one embodiment" or "some embodiments" etc. described in the specification of the present application means that a specific feature, structure or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, the statements "in one embodiment", "in some embodiments", "in other some embodiments", "in partial embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "include", "comprise", "have" and their variants all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0025] In addition, the technical solutions between various embodiments can be combined with each other, but it must be based on the ability of those of ordinary skill in the art to implement. When the combination of technical solutions results in contradictions or cannot be implemented, it should be considered that such a combination of technical solutions does not exist and is not within the scope of protection required by the present application.

[0026] The flowcharts shown in the accompanying drawings are only illustrative examples, and do not necessarily include all contents and operations / steps, nor do they necessarily need to be executed in the described order. For example, some operations / steps can also be decomposed, combined or partially merged, so the actual execution order may be changed according to the actual situation.

[0027] Distributed soft bus technology can achieve unified distributed communication management capabilities among near-field devices, providing device discovery, connection, networking, and transmission capabilities regardless of the link. Currently, when networking with the distributed soft bus, only PIN (Personal Identification Number) code authentication is supported, and an authorization prompt interface for PIN code authentication, a PIN code display interface, and a PIN code input interface need to be provided. For example, as Figure 1 shown, the specific authentication process is as follows:

[0028] Step (a1): Device A initiates negotiation to confirm whether the negotiation with Device B is successful; if not, the authentication fails; if so, proceed to step (a2);

[0029] Step (a2): Enter the authentication confirmation process. A authentication confirmation dialog box pops up on Device B. If the confirmation based on the dialog box is no, the authentication fails; if the confirmation based on the dialog box is yes, Device B creates a group, displays the generated PIN code on the interface, and encapsulates it into a token and sends it to Device A;

[0030] Step (a3): A device screen displays a PIN code input box. After entering the PIN, check whether it is consistent with the PIN code of the received token; if they are consistent, the authentication passes; if they are inconsistent, the authentication fails.

[0031] Therefore, the authentication of the distributed soft bus only supports identity authentication through PIN code display and input, and it is impossible to perform authentication networking for screenless devices, so the applicability is limited.

[0032] To solve the above problems, the embodiments of the present application provide a device authentication networking method, device, equipment, and storage medium. Among them, the method obtains the device information of the second device to be authenticated and networked when discovering the second device based on the distributed soft bus; obtains the device information of the second device through a short-range wireless communication method; if the device information obtained twice is the same, initiate networking with the second device, send the device information to the cloud server, so that the cloud server queries the database storing the device information of each device based on the device information. If the device information is queried from the database, it is determined that the authentication of the second device passes, and a passing result is returned; when receiving the passing result returned by the cloud server, confirm that the networking is successful. The entire process does not require an authorization prompt interface for PIN code authentication, a PIN code display interface, a PIN code input interface, etc., and it is also possible to implement authentication networking for screenless devices. Therefore, the applicability of device authentication networking based on the distributed soft bus is improved.

[0033] Please refer to Figure 2 , Figure 2It is a schematic flowchart of a device authentication networking method provided by an embodiment of the present application. This method can be applied to a device, where the device can be any one of a mobile phone, a camera, a tablet computer, a wearable device, a vehicle-mounted device, an augmented reality (AR) / virtual reality (VR) device, a laptop computer, a personal computer (PC), a netbook, and a personal digital assistant (PDA), and there is no limitation in the embodiments of the present application. For the convenience of distinction and description, the device to which this method is applied is hereinafter referred to as the first device.

[0034] As Figure 2 shown, the device authentication networking method provided by the embodiment of the present application includes steps S101 to S104.

[0035] S101. When discovering a second device to be authenticated for networking based on the distributed soft bus, obtain the device information of the second device.

[0036] For the convenience of distinction and description, the device to be authenticated for networking is hereinafter referred to as the second device. The first device and the second device are in the same local area network, and the second device sends a broadcast through the CoAP (The Constrained Application Protocol) protocol, and the device information of the second device is carried in the broadcast. Among them, the device information includes but is not limited to information such as device type, device version, and device ID.

[0037] When the first device discovers the second device based on the distributed soft bus, that is, when receiving the broadcast sent by the second device, the first device parses the broadcast to obtain the device information of the second device.

[0038] S102. Obtain the device information of the second device through a short-range wireless communication method.

[0039] Among them, the short-range wireless communication method includes but is not limited to NFC (Near Field Communication) method, Bluetooth method, WiFi (Wireless Fidelity) method, etc.

[0040] In some embodiments, the first device is provided with an NFC module, and the second device is pre-configured with a TAG label, where the TAG label contains information such as the device information of the second device and the Bluetooth mac address (media access control address).

[0041] Obtaining the device information of the second device through the short-range wireless communication method includes: reading the pre-configured TAG label of the second device through the NFC module to obtain the device information.

[0042] That is, the device information of the second device is obtained by using the "touch and touch" method to read the TAG label of the second device through the NFC module of the first device.

[0043] Exemplarily, for different situations where the device is equipped with an NFC module and not equipped with an NFC module, the configuration methods of the TAG labels of the device are different. Taking the second device as an example, the configuration of the TAG label of the second device includes the following methods:

[0044] If the second device is equipped with an NFC module, the second device automatically reads the device information of its own device and writes the device information into the TAG label paper to generate the TAG label.

[0045] If the second device is not equipped with an NFC module, a TCP (Transmission Control Protocol) connection is established between the management terminal equipped with an NFC module and the second device. The second device transmits the device information to the management terminal through TCP, and the management terminal writes the device information into the TAG label paper to generate the TAG label.

[0046] For the case where the second device is factory-set with an NFC module, during factory initialization, the second device runs the factory initialization program, automatically reads the device information of its own device through the system interface, and writes the device information into the TAG label paper, and then pastes the TAG label paper on the second device.

[0047] For the case where the second device is not factory-set with an NFC module, during factory initialization, an NFC module-equipped management terminal, such as a PAD (Portable Android Device, tablet computer), can be used to configure the TAG label of the second device. For example, Figure 3 As shown, the specific process of configuring the TAG label of the second device is as follows:

[0048] Step (b1): The management terminal turns on the WiFi AP hotspot, for example, the hotspot name is agreed to be XXX, and starts the TCP server, for example, the port number is agreed to be 8888;

[0049] Step (b2): The second device powers on and turns on the WiFi, and attempts to connect to the WiFi AP hotspot named XXX three times, with a preset time interval between each attempt, such as 10 seconds. If the connection fails, the configuration operation ends. If the connection is successful, it attempts to connect to the TCP server with the port number 8888, also three times. If the connection fails, the configuration operation ends. If the connection is successful, step (b3) is executed;

[0050] Step (b3): The second device reads the device information of the local device through the system interface, and then transmits the device information to the management terminal via TCP;

[0051] Step (b4): The management terminal writes the device information of the second device onto the TAG label paper, and finally pastes the TAG label paper onto the second device.

[0052] Since the second device does not need to have an NFC module, the cost is further reduced.

[0053] In some other embodiments, obtaining the device information of the second device through the short-range wireless communication method includes: obtaining the device information of the second device through the Bluetooth method or the WiFi method, where the first device and the second device are provided with a Bluetooth module or a WiFi module, and a unique device identifier is preset.

[0054] Different from the above method of obtaining device information by reading the TAG label through the NFC module, in this embodiment, the first device does not need to be provided with an NFC module. Usually, a Bluetooth module or a WiFi module is set at the factory of the device. When both the first device and the second device are provided with a Bluetooth module or a WiFi module, only a unique device identifier needs to be preset, where the device identifier includes but is not limited to the Bluetooth mac address, etc. The first device and the second device turn on the Bluetooth or WiFi, and obtain the device information of the second device through the Bluetooth method or the WiFi method.

[0055] In some other embodiments, obtaining the device information of the second device through the short-range wireless communication method includes: obtaining the device information of the second device through the NFC P2P point-to-point communication method, where the first device and the second device are both provided with an NFC module.

[0056] Different from the above method of obtaining device information by reading the TAG label through the NFC module, in this embodiment, it is required that both the first device and the second device are provided with an NFC module, but the operation of configuring the TAG label of the second device is not required. The first device and the second device establish an NFC communication connection through the NFC module, and the first device obtains the device information of the second device based on the NFC P2P communication method.

[0057] It can be understood that, according to the actual scenario, a suitable method can be flexibly selected from the above-listed multiple embodiments to obtain the device information of the second device.

[0058] S103. If the device information obtained twice is the same, initiate networking with the second device, send the device information to the cloud server, so that the cloud server queries the database storing the device information of each device based on the device information. If the device information is queried from the database, it is determined that the authentication of the second device is passed, and a passing result is returned.

[0059] S104. When receiving the passing result returned by the cloud server, confirm that the networking is successful.

[0060] Through the operations in steps S101 and S102, the device information of the second device is obtained respectively, and the device information obtained twice is compared. If the device information obtained twice is different, it indicates that the second device discovered based on the distributed soft bus and the second device of the short-range wireless communication are not the same device. At this time, the operation is ended, or the second device is reconfirmed. If the device information obtained twice is the same, it indicates that the second device discovered based on the distributed soft bus and the second device of the short-range wireless communication are the same device. At this time, networking is initiated with the second device. The most direct way is to send the device information of the second device to the cloud server.

[0061] Exemplarily, the cloud server is correspondingly configured with a corresponding database, and the device information of each device is stored in the database.

[0062] In some embodiments, the database stores the device information of each device in the following ways:

[0063] The management terminal equipped with an NFC module reads the pre-configured TAG tags of each device to obtain the device information of each device, and sends the device information of each device to the database.

[0064] Exemplarily, for any device pre-configured with a corresponding TAG tag, the management terminal reads the pre-configured TAG tag of the device through RFID (Radio Frequency Identification) to obtain the device information of the device, and then sends the device information of the device to the database, and the database stores the device information of the device.

[0065] After the cloud server receives the device information of the second device, it queries the database that stores the device information of each device. If it finds in the database that the stored device information of a certain device is the same as the device information of the received second device, the authentication of the second device is passed, and the authentication pass result is returned to the first device. When the first device receives the pass result returned by the cloud server, it confirms that the networking is successful.

[0066] For example, as Figure 4 shown, taking the management terminal as a PAD as an example, device B is pre-configured with corresponding TAG tags. The PAD reads the TAG tags of device B to obtain the device information of device B, and then reports the device information of device B to the cloud server. The cloud server saves the device information of device B to the database.

[0067] In some embodiments, as Figure 5 shown, step S103 may include sub-step S1031 and sub-step S1032.

[0068] S1031. Encrypt the device information to generate a ciphertext;

[0069] S1032. Send the ciphertext to the cloud server for the cloud server to decrypt the ciphertext to obtain the device information.

[0070] Exemplarily, the first device initiates networking with the second device. After negotiation and confirmation of in-sequence delivery, the device information of the second device is encrypted using an asymmetric key or a symmetric key to generate a corresponding ciphertext. Then, the ciphertext is sent to the cloud server. After receiving the ciphertext, the cloud server decrypts the ciphertext to obtain the device information of the second device.

[0071] By encrypting the device information, the security of the information is ensured.

[0072] In some embodiments, the encrypting the device information to generate a ciphertext includes: encrypting the device information using a first key, and encrypting the first key using the public key in the key pair created by the cloud server. Based on the encrypted device information and the encrypted first key, the ciphertext is generated; the sending the ciphertext to the cloud server for the cloud server to decrypt the ciphertext to obtain the device information includes: sending the ciphertext containing the encrypted device information and the encrypted first key to the cloud server for the cloud server to decrypt the encrypted first key using the private key in the key pair to obtain the first key, and decrypting the encrypted device information using the first key to obtain the device information.

[0073] Exemplarily, the cloud server creates a key pair. For example, the cloud server creates an RSA key pair, including an RSA public key and an RSA private key.

[0074] It should be noted that the key pair created by the cloud server can be other types of key pairs in addition to the RSA key pair, and specific limitations are not imposed in this application.

[0075] In some embodiments, before encrypting the first key with the public key in the key pair created by the cloud server, it includes: receiving the public key sent by the management terminal through a short-range wireless communication method, where the cloud server sends the public key to the management terminal.

[0076] Still taking the cloud server creating an RSA key pair as an example, the cloud server retains the RSA private key by itself and sends the RSA public key to the management terminal, such as a PAD. The management terminal establishes a short-range wireless communication connection with the first device. For example, the management terminal establishes a Bluetooth connection with the first device through the Bluetooth MAC address, and the management terminal transmits the RSA public key to the first device through Bluetooth. The first device receives and obtains the RSA public key in the RSA key pair created by the cloud server. For example, as Figure 4 shown, after the cloud server creates an RSA key pair, it retains the RSA private key by itself and sends the RSA public key to the PAD, and the PAD transmits the RSA public key to device A through Bluetooth.

[0077] The first device creates a corresponding first key, where the first key includes but is not limited to an AES key. Exemplarily, the first device encrypts the device information of the second device with the created AES key, and encrypts the AES key with the public key in the key pair created by the cloud server obtained, such as the RSA public key, to generate a corresponding ciphertext from the encrypted device information and the encrypted AES key. Then, the first device sends the ciphertext containing the encrypted device information and the encrypted AES key to the cloud server. After receiving the ciphertext, the cloud server first decrypts the encrypted AES key with the RSA private key it retains to obtain the AES key, and then decrypts the encrypted device information with the AES key to obtain the device information of the second device.

[0078] The encryption process of the device information by the above RSA+AES encryption method further ensures the security of the information.

[0079] Next, taking device A and device B as examples, as Figure 6 shown, the authentication process of the device will be described:

[0080] Step (c1): Device B sends a broadcast carrying its own device information;

[0081] Step (c2): Device A receives the broadcast and obtains the device information of Device B;

[0082] Step (c3): Device A touches Device B to read the TAG label of Device B and obtain the device information in the TAG label;

[0083] Step (c4): Whether the device information obtained twice is consistent; if not, the authentication fails; if so, Device A initiates networking with Device B;

[0084] Step (c5): Device A creates an AES key, encrypts the device information of Device B using the AES key, and encrypts the AES key using the RSA public key created by the cloud server;

[0085] Step (c6): Device A sends the encrypted device information and the encrypted AES key to the cloud server;

[0086] Step (c7): The cloud server decrypts the encrypted AES key using the RSA private key to obtain the AES key, and decrypts the encrypted device information using the AES key to obtain the device information of Device B;

[0087] Step (c8): The cloud server queries whether the device information of Device B is saved in the database; if so, execute Step (c9); if not, the authentication fails;

[0088] Step (c9): The cloud server returns the result to Device A, and the authentication passes.

[0089] In this application, the authentication logic is separated from the authentication management to achieve decoupling and customization. It is no longer limited to using PIN code authentication. Through operations such as cloud server collaboration, database synchronization, and key management, customized authentication is achieved, with stronger security and scalability. Moreover, compared with the method of inputting PIN code authentication, it is more convenient and faster to operate, enhancing the user experience.

[0090] In the above embodiments, when a second device to be authenticated for networking is discovered based on the distributed soft bus, the device information of the second device is obtained, and the device information of the second device is obtained by means of short-range wireless communication. The device information obtained twice is compared. If the device information obtained twice is the same, a network connection is initiated to the second device, and the device information is sent to the cloud server. Based on the received device information, the cloud server queries the database that stores the device information of each device. If consistent device information is found in the database, it is determined that the authentication of the second device is passed, and a passing result is returned. When the passing result returned by the cloud server is received, it is confirmed that the networking is successful. During the whole process, there is no need to provide an authorization prompt interface for PIN code authentication, a PIN code display interface, a PIN code input interface, etc. Authentication networking can also be realized for screenless devices. Therefore, the applicability of device authentication networking based on the distributed soft bus is improved.

[0091] Please refer to Figure 7 , Figure 7 which is a schematic block diagram of a device authentication networking device provided by an embodiment of the present application.

[0092] As Figure 7 shown, the device authentication networking device 200 may include a processor 211 and a memory 212. The processor 211 and the memory 212 are connected by a bus, and this bus is, for example, an I2C (Inter-integrated Circuit) bus.

[0093] Specifically, the processor 211 may be a microcontroller unit (MCU), a central processing unit (CPU), or a digital signal processor (DSP), etc.

[0094] Specifically, the memory 212 may be a Flash chip, a read-only memory (ROM), a magnetic disk, an optical disc, a USB flash drive, or a mobile hard disk, etc. Various computer programs for the processor 211 to execute are stored in the memory 212.

[0095] Among them, the processor 211 is used to run the computer program stored in the memory processor 211, and when executing the computer program, the following steps are implemented:

[0096] When a second device to be authenticated for networking is discovered based on the distributed soft bus, obtain the device information of the second device;

[0097] Obtain the device information of the second device by means of short-range wireless communication;

[0098] If the device information obtained twice is consistent, initiate network formation with the second device and send the device information to the cloud server, so that the cloud server can query the database storing the device information of each device based on the device information. If the device information is found in the database, it is determined that the authentication of the second device is passed, and a pass result is returned.

[0099] When receiving the pass result returned by the cloud server, confirm that the network formation is successful.

[0100] In some embodiments, the first device is provided with a Near Field Communication (NFC) module. When the processor 211 obtains the device information of the second device by means of short-range wireless communication, it is configured to:

[0101] Read the pre-configured TAG label of the second device through the NFC module to obtain the device information.

[0102] In some embodiments, the configuration of the TAG label includes the following methods:

[0103] If the second device is provided with an NFC module, automatically read the device information of the local device through the second device and write the device information into the TAG label paper to generate the TAG label.

[0104] If the second device is not provided with an NFC module, establish a Transmission Control Protocol (TCP) connection with the second device through a management terminal provided with an NFC module. The second device transmits the device information to the management terminal through TCP, and the management terminal writes the device information into the TAG label paper to generate the TAG label.

[0105] In some embodiments, when the processor 211 obtains the device information of the second device by means of short-range wireless communication, it is configured to:

[0106] Obtain the device information of the second device through Bluetooth or Wireless Fidelity (WiFi) means, where the first device and the second device are provided with Bluetooth modules or WiFi modules and are pre-set with unique device identifiers.

[0107] In some embodiments, when the processor 211 obtains the device information of the second device by means of short-range wireless communication, it is configured to:

[0108] Obtain the device information of the second device through NFC Peer-to-Peer (P2P) communication means, where both the first device and the second device are provided with NFC modules.

[0109] In some embodiments, when the processor 211 implements sending the device information to the cloud server, it is used to implement:

[0110] Encrypt the device information to generate a ciphertext;

[0111] Send the ciphertext to the cloud server for the cloud server to decrypt the ciphertext to obtain the device information.

[0112] In some embodiments, when the processor 211 implements encrypting the device information to generate a ciphertext, it is used to implement:

[0113] Encrypt the device information with a first key, and encrypt the first key with the public key in the key pair created by the cloud server. Based on the encrypted device information and the encrypted first key, generate the ciphertext;

[0114] When the processor 211 implements sending the ciphertext to the cloud server for the cloud server to decrypt the ciphertext to obtain the device information, it is used to implement:

[0115] Send the ciphertext containing the encrypted device information and the encrypted first key to the cloud server for the cloud server to decrypt the encrypted first key with the private key in the key pair to obtain the first key, and decrypt the encrypted device information with the first key to obtain the device information.

[0116] In some embodiments, before the processor 211 implements encrypting the first key with the public key in the key pair created by the cloud server, it is used to implement:

[0117] Receive the public key sent by the management terminal through near-field wireless communication, where the cloud server sends the public key to the management terminal.

[0118] In some embodiments, the database stores the device information of each device in the following manner:

[0119] Read the TAG tags pre-configured on each device through a management terminal equipped with an NFC module to obtain the device information of each device, and send the device information of each device to the database.

[0120] An embodiment of the present application further provides a device, and the types of the device include but are not limited to mobile phones, cameras, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR) / virtual reality (VR) devices, laptop computers, personal computers (PCs), netbooks, personal digital assistants (PDAs), etc., and no limitation is made in the embodiments of the present application.

[0121] Among them, the device includes a device authentication networking device. Exemplarily, the device authentication networking device may be the device authentication networking device 200 described in the above embodiment. The device can execute any device authentication networking method provided by the embodiments of the present application. Therefore, the beneficial effects that can be achieved by any device authentication networking method provided by the embodiments of the present application can be realized. For details, refer to the previous embodiments and will not be elaborated here.

[0122] An embodiment of the present application further provides a storage medium. The storage medium stores a computer program, and the computer program includes program instructions. The processor executes the program instructions to implement the steps of the device authentication networking method provided in the above embodiment. For example, when the computer program is loaded by the processor, the following steps may be executed:

[0123] When a second device to be authenticated and networked is discovered based on the distributed soft bus, obtain the device information of the second device;

[0124] Obtain the device information of the second device through a short-range wireless communication method;

[0125] If the device information obtained twice is the same, initiate networking with the second device, and send the device information to the cloud server for the cloud server to query a database storing the device information of each device based on the device information. If the device information is queried from the database, it is determined that the authentication of the second device is passed, and a passing result is returned;

[0126] When receiving the passing result returned by the cloud server, confirm that the networking is successful.

[0127] For the specific implementation of each of the above operations, refer to the previous embodiments and will not be elaborated here.

[0128] Among them, the storage medium may be the device authentication networking device or the internal storage unit of the device in the foregoing embodiments, such as the hard disk or memory of the device authentication networking device or the device. The storage medium may also be an external storage device of the device authentication networking device or the device, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) card, a Flash Card, etc. equipped on the device authentication networking device or the device.

[0129] Since the computer program stored in this storage medium can execute any device authentication networking method provided by the embodiments of the present application, the beneficial effects achievable by any device authentication networking method provided by the embodiments of the present application can be realized. For details, refer to the foregoing embodiments and will not be elaborated herein.

[0130] The above are only the preferred embodiments of the present application, and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made by using the content of the specification and drawings of the present application, or directly or indirectly applied in other related technical fields, shall be equally included in the patent protection scope of the present application.

Claims

1. A device authentication networking method, characterized in that, applied to a first device, the device authentication networking method includes: When discovering a second device to be authenticated and networked based on a distributed soft bus, obtaining the device information of the second device; Obtaining the device information of the second device through a short-range wireless communication method; If the device information obtained twice is consistent, initiate networking with the second device, and send the device information to a cloud server, so that the cloud server queries a database that stores the device information of each device based on the device information. If the device information is queried from the database, it is determined that the authentication of the second device is passed, and a passing result is returned; When receiving the passing result returned by the cloud server, confirm that the networking is successful.

2. The method according to claim 1, characterized in that, The first device is provided with a Near Field Communication (NFC) module. The obtaining the device information of the second device through the short-range wireless communication method includes: Reading a pre-configured TAG label of the second device through the NFC module to obtain the device information.

3. The method according to claim 2, characterized in that, The configuration of the TAG label includes the following methods: If the second device is provided with an NFC module, automatically read the device information of the local device through the second device, and write the device information into a TAG label paper to generate the TAG label; If the second device is not provided with an NFC module, establish a Transmission Control Protocol (TCP) connection with the second device through a management terminal provided with an NFC module. The second device transmits the device information to the management terminal through TCP, and the management terminal writes the device information into a TAG label paper to generate the TAG label.

4. The method according to claim 1, characterized in that, The obtaining the device information of the second device through the short-range wireless communication method includes: Obtaining the device information of the second device through Bluetooth or Wireless Fidelity (WiFi) method, wherein the first device and the second device are provided with a Bluetooth module or a WiFi module, and a unique device identifier is pre-set.

5. The method according to claim 1, characterized in that, The obtaining the device information of the second device through the short-range wireless communication method includes: Obtaining the device information of the second device through NFC Peer-to-Peer (P2P) communication method, wherein both the first device and the second device are provided with NFC modules.

6. The method according to claim 1, characterized in that, The sending the device information to the cloud server includes: Encrypting the device information to generate a ciphertext; Sending the ciphertext to the cloud server for the cloud server to decrypt the ciphertext to obtain the device information.

7. The method according to claim 6, characterized in that, The encrypting the device information to generate a ciphertext includes: Encrypt the device information using a first key, and encrypt the first key using the public key in the key pair created by the cloud server. Based on the encrypted device information and the encrypted first key, generate the ciphertext; Sending the ciphertext to the cloud server for the cloud server to decrypt the ciphertext to obtain the device information includes: Sending the ciphertext containing the encrypted device information and the encrypted first key to the cloud server for the cloud server to decrypt the encrypted first key using the private key in the key pair to obtain the first key, and decrypt the encrypted device information using the first key to obtain the device information.

8. The method according to claim 7, wherein, Before encrypting the first key using the public key in the key pair created by the cloud server, it includes: Receiving the public key sent by the management terminal through a short-range wireless communication method, wherein the cloud server sends the public key to the management terminal.

9. The method according to any one of claims 1 to 8, wherein, The database stores the device information of each device in the following manner: Reading the pre-configured TAG tags of each device through a management terminal provided with an NFC module to obtain the device information of each device, and sending the device information of each device to the database.

10. A device authentication networking device, wherein, The device authentication networking device includes a processor and a memory. The memory stores a computer program executable by the processor. When the computer program is executed by the processor, it implements the device authentication networking method according to any one of claims 1 to 9.

11. A device, wherein, The device includes the device authentication networking device according to claim 10.

12. A storage medium for computer-readable storage, wherein, The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of the device authentication networking method according to any one of claims 1 to 9.

Images