Security verification method and device, electronic equipment and storage medium

Abstract

Embodiments of the present application provide a security verification method and device, electronic equipment and storage medium, the method comprises: obtaining the UUID identifier corresponding to the smart device, the IMSI identifier and the identifier length corresponding to the IMSI identifier;According to the identifier length, the encryption information used for data encryption is extracted from the UUID identifier, and the IMSI identifier is encrypted by using the encryption information, and the target IMSI identifier is obtained;The UUID identifier, the target IMSI identifier and the identifier length are encrypted by private key, and the encryption request data is obtained, and the encryption request data is sent to the server, the private key is the key returned by the server after the smart device is successfully registered in the server;Receive the verification pass information returned by the server for the encryption request data, the verification pass information includes identity information;Based on the identity information, the identity authentication of the smart device is completed.

Description

Technical Field

[0001] This invention relates to the field of security verification technology, and in particular to a security verification method, a security verification device, an electronic device, and a computer-readable storage medium. Background Technology

[0002] The development of the Internet of Things (IoT) has made life smarter and more convenient, allowing users to remotely control various smart devices through smart terminals. With the increasing variety and number of smart devices, user authentication has become particularly important; otherwise, criminals can easily impersonate users and maliciously control these devices, leading to incidents. For example, smart terminals often control devices through applications on the terminal. The server needs to verify the user's identity (the smart terminal's identity) first, typically involving multiple data interactions. During these interactions, the user requests a verification code from the platform, the platform sends the code to the user, and the user then returns the code to the platform for verification, confirming the user's identity. This method requires users to manually enter the verification code, making it complex. More importantly, the lack of encryption measures in the user's request and return of the verification code, as well as the server's return and verification of the verification code, makes the returned verification code easily intercepted. Criminals can then steal the user's identity by simulating the phone number. Summary of the Invention

[0003] This invention provides a secure verification method, apparatus, electronic device, and computer-readable storage medium to solve or partially solve the problem of low security and easy data leakage during user identity authentication.

[0004] This invention discloses a security verification method applied to smart devices, the method comprising:

[0005] Obtain the UUID identifier, IMSI identifier, and identifier length corresponding to the IMSI identifier of the smart device;

[0006] Based on the identifier length, the encryption information for data encryption is extracted from the UUID identifier, and the encryption information is used to encrypt the IMSI identifier to obtain the target IMSI identifier;

[0007] The UUID identifier, the target IMSI identifier, and the identifier length are encrypted using a private key to obtain encryption request data, which is then sent to the server. The private key is the key returned by the server after the smart device has successfully registered with the server.

[0008] The system receives verification information returned by the server regarding the encrypted request data. This verification information is generated by the server decrypting the encrypted request data using the public key corresponding to the private key to obtain the UUID identifier, the target IMSI identifier, and the identifier length, successfully verifying the smart device based on the UUID identifier, the target IMSI identifier, and the identifier length, and then encrypting the identity information queried based on the UUID identifier and the target IMSI identifier using the UUID identifier.

[0009] The identity of the smart device is authenticated based on the identity information.

[0010] Optionally, extracting encryption information for data encryption from the UUID identifier based on the identifier length includes:

[0011] Information corresponding to the length of the identifier is extracted from the last digit of the UUID identifier and used as encryption information to encrypt the IMSI identifier.

[0012] Optionally, it also includes:

[0013] The UUID identifier and the IMSI identifier are sent to the server, and the registration encrypted data and decryption program returned by the server are received. The registration encrypted data is the data generated by the server using an asymmetric encryption algorithm to generate the corresponding private key and public key, and then encrypting the private key using the UUID identifier.

[0014] Run the decryption program to decrypt the registered encrypted data using the UUID identifier to obtain the private key.

[0015] Optionally, receiving the verification pass information for the encrypted request data returned by the server includes:

[0016] The decryption program is run to decrypt the verification information using the UUID identifier to obtain the identity information corresponding to the smart device. The identity information includes at least the MSISDN identifier and the user identifier.

[0017] Optionally, it also includes:

[0018] The server receives verification failure information for the encrypted request data returned by the server. The verification failure information is generated by the server after decrypting the encrypted request data with the public key corresponding to the private key to obtain the UUID identifier and the target IMSI identifier, and then failing to verify the smart device with the UUID identifier and the target IMSI identifier.

[0019] Output a prompt message corresponding to the verification failure information.

[0020] This invention also discloses a security verification method applied to a server, the method comprising:

[0021] Obtain encrypted request data sent by smart devices;

[0022] The encrypted request data is decrypted using a public key to obtain the UUID identifier corresponding to the smart device, the target IMSI identifier, and the identifier length for the target IMSI identifier;

[0023] Based on the identifier length, the corresponding encrypted information is extracted from the UUID identifier, and the target IMSI identifier is decrypted using the encrypted information to obtain the IMSI identifier corresponding to the smart device;

[0024] If identity information matching the smart device is found based on the UUID identifier and the IMSI identifier, then the corresponding encryption program is run to encrypt the identity information using the UUID identifier, generate corresponding test pass information, and send the test pass information to the smart device. The identity information is used to authenticate the smart device.

[0025] Optionally, extracting the corresponding encrypted information from the UUID identifier based on the identifier length includes:

[0026] Information corresponding to the length of the identifier is extracted from the last digit of the UUID identifier and used as encryption information to encrypt the IMSI identifier.

[0027] Optionally, if identity information matching the smart device is found based on the UUID identifier and the IMSI identifier, a corresponding encryption program is run to encrypt the identity information using the UUID identifier, generating corresponding test pass information, including:

[0028] Query the target MSISDN identifier and target user identifier corresponding to the UUID identifier and the IMSI identifier, and obtain the preset MSISDN identifier and preset user identifier when the smart device registered on the server;

[0029] If the target MSISDN identifier is the same as the preset MSISDN identifier, and / or the target user identifier is the same as the preset user identifier, then the corresponding encryption program is run to encrypt the identity information using the UUID identifier, and generate the corresponding test pass information.

[0030] Optionally, it also includes:

[0031] If the target MSISDN identifier is different from the preset MSISDN identifier, and the target user identifier is different from the preset user identifier, then a verification failure message corresponding to the encrypted request data is generated, and the verification failure message is sent to the smart device.

[0032] Optionally, it also includes:

[0033] Obtain the UUID identifier and the IMSI identifier sent by the smart device;

[0034] Query the preset MSISDN identifier and preset user identifier corresponding to the UUID identifier and the IMSI identifier, and establish the corresponding association relationship between the UUID identifier, the IMSI identifier, the preset MSISDN identifier and the preset user identifier for the registration of the smart device;

[0035] A corresponding private key and public key are generated using an asymmetric encryption algorithm, and the private key is encrypted using the UUID identifier to generate corresponding registration encrypted data;

[0036] The registration encryption data and the decryption program corresponding to the encryption program are sent to the smart device.

[0037] This invention also discloses a security verification device for use in smart devices, the device comprising:

[0038] The identifier acquisition module is used to acquire the UUID identifier, IMSI identifier, and identifier length corresponding to the IMSI identifier of the smart device.

[0039] An identifier encryption module is used to extract encryption information for data encryption from the UUID identifier according to the identifier length, and to encrypt the IMSI identifier using the encryption information to obtain the target IMSI identifier;

[0040] The data encryption module is used to encrypt the UUID identifier, the target IMSI identifier, and the identifier length using a private key to obtain encryption request data, and send the encryption request data to the server. The private key is the key returned by the server after the smart device successfully registers with the server.

[0041] The information receiving module is used to receive the verification pass information returned by the server for the encrypted request data. The verification pass information is generated by the server decrypting the encrypted request data according to the public key corresponding to the private key to obtain the UUID identifier, the target IMSI identifier, and the identifier length, and successfully verifying the smart device according to the UUID identifier, the target IMSI identifier, and the identifier length, and encrypting the identity information queried based on the UUID identifier and the target IMSI identifier using the UUID identifier.

[0042] The identity authentication module is used to authenticate the identity of the smart device based on the identity information.

[0043] Optionally, the identifier encryption module is specifically used for:

[0044] Information corresponding to the length of the identifier is extracted from the last digit of the UUID identifier and used as encryption information to encrypt the IMSI identifier.

[0045] Optionally, it also includes:

[0046] The identifier sending module is used to send the UUID identifier and the IMSI identifier to the server, and receive the registration encrypted data and decryption program returned by the server. The registration encrypted data is data generated by the server using an asymmetric encryption algorithm to generate the corresponding private key and public key, and then encrypting the private key using the UUID identifier.

[0047] The key acquisition module is used to run the decryption program to decrypt the registration encrypted data using the UUID identifier and obtain the private key.

[0048] Optionally, the information receiving module is specifically used for:

[0049] The decryption program is run to decrypt the verification information using the UUID identifier to obtain the identity information corresponding to the smart device. The identity information includes at least the MSISDN identifier and the user identifier.

[0050] Optionally, it also includes:

[0051] The failure information receiving module is used to receive the verification failure information returned by the server for the encrypted request data. The verification failure information is generated by the server after decrypting the encrypted request data according to the public key corresponding to the private key to obtain the UUID identifier and the target IMSI identifier, and failing to verify the smart device according to the UUID identifier and the target IMSI identifier.

[0052] The prompt message output module is used to output prompt messages corresponding to the verification failure information.

[0053] This invention also discloses a security verification device applied to a server, the device comprising:

[0054] The data acquisition module is used to acquire encrypted request data sent by smart devices;

[0055] The data decryption module is used to decrypt the encrypted request data using a public key to obtain the UUID identifier corresponding to the smart device, the target IMSI identifier, and the identifier length for the target IMSI identifier;

[0056] The identifier decryption module is used to extract corresponding encrypted information from the UUID identifier according to the identifier length, and decrypt the target IMSI identifier through the encrypted information to obtain the IMSI identifier corresponding to the smart device;

[0057] The information sending module is used to run a corresponding encryption program to encrypt the identity information using the UUID identifier if the identity information matching the smart device is found based on the UUID identifier and the IMSI identifier, generate corresponding test pass information, and send the test pass information to the smart device. The identity information is used to authenticate the smart device.

[0058] Optionally, the identifier decryption module is specifically used for:

[0059] Information corresponding to the length of the identifier is extracted from the last digit of the UUID identifier and used as encryption information to encrypt the IMSI identifier.

[0060] Optionally, the information sending module is specifically used for:

[0061] Query the target MSISDN identifier and target user identifier corresponding to the UUID identifier and the IMSI identifier, and obtain the preset MSISDN identifier and preset user identifier when the smart device registered on the server;

[0062] If the target MSISDN identifier is the same as the preset MSISDN identifier, and / or the target user identifier is the same as the preset user identifier, then the corresponding encryption program is run to encrypt the identity information using the UUID identifier, and generate the corresponding test pass information.

[0063] Optionally, it also includes:

[0064] The failure information sending module is used to generate verification failure information corresponding to the encrypted request data and send the verification failure information to the smart device if the target MSISDN identifier is different from the preset MSISDN identifier and the target user identifier is different from the preset user identifier.

[0065] Optionally, it also includes:

[0066] The identifier acquisition module is used to acquire the UUID identifier and the IMSI identifier sent by the smart device;

[0067] The registration module is used to query the preset MSISDN identifier and preset user identifier corresponding to the UUID identifier and the IMSI identifier, and establish the corresponding association relationship between the UUID identifier, the IMSI identifier, the preset MSISDN identifier and the preset user identifier in order to register the smart device;

[0068] The key generation module is used to generate corresponding private and public keys using an asymmetric encryption algorithm, and to encrypt the private key using the UUID identifier to generate corresponding registration encrypted data.

[0069] The data sending module is used to send the registration encrypted data and the decryption program corresponding to the encryption program to the smart device.

[0070] This invention also discloses an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0071] The memory is used to store computer programs;

[0072] When the processor executes a program stored in the memory, it implements the method described in the embodiments of the present invention.

[0073] This invention also discloses a computer-readable storage medium storing instructions that, when executed by one or more processors, cause the processors to perform the methods described in this invention.

[0074] The embodiments of the present invention have the following advantages:

[0075] In this embodiment of the invention, when a smart device needs to perform identity authentication to complete a corresponding operation, the smart device can obtain its corresponding UUID identifier, IMSI identifier, and the identifier length corresponding to the IMSI identifier. Then, based on the identifier length, it extracts encryption information for data encryption from the UUID identifier and uses this encryption information to encrypt the IMSI identifier to obtain the target IMSI identifier. Next, it can encrypt the UUID identifier, the target IMSI identifier, and the identifier length using a private key to obtain encryption request data. This encryption request data is then sent to the server. The private key is the key returned by the server after the smart device successfully registers with the server. The device also receives verification information from the server regarding the encrypted request data. The server decrypts the first encrypted data using the public key corresponding to the private key to obtain the UUID identifier, the target IMSI identifier, and the identifier length. Based on the UUID identifier, target IMSI identifier, and identifier length, the server successfully verifies the smart device. The server then encrypts the identity information retrieved based on the UUID identifier and target IMSI identifier using the UUID identifier, generating the final information. This identity information is then used to complete the smart device's authentication. Thus, during the security verification process, encryption is achieved by extracting corresponding encrypted information from the UUID identifier based on the IMSI identifier's length, effectively ensuring data encryption security. Simultaneously, associating private information with the UUID identifier and IMSI identifier improves the accuracy of security authentication. Attached Figure Description

[0076] Figure 1 This is a flowchart of the steps of a security verification method provided in an embodiment of the present invention;

[0077] Figure 2 This is a schematic diagram of the security verification process provided in an embodiment of the present invention;

[0078] Figure 3 This is a flowchart of the steps of a security verification method provided in an embodiment of the present invention;

[0079] Figure 4 This is a structural block diagram of a security verification device provided in an embodiment of the present invention;

[0080] Figure 5 This is a structural block diagram of a security verification device provided in an embodiment of the present invention;

[0081] Figure 6 This is a block diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0082] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0083] As an example, smart devices are often controlled through on-device applications. The server needs to verify the user's identity (the smart device's identity) first, typically involving multiple data interactions. During these interactions, the user requests a verification code from the platform, the platform sends the code to the user, and the user then returns the code to the platform for verification, confirming the user's identity. This method requires the user to manually enter the verification code, making it complex. More importantly, no encryption measures are used in the user's request and return of the verification code, or in the server's return and verification of the verification code. Therefore, the returned verification code is easily intercepted, and criminals can steal the user's identity by simulating the phone number.

[0084] One of the core inventive points of this invention is that when a smart device needs to perform identity authentication to complete a corresponding operation, the smart device can obtain its corresponding UUID identifier, IMSI identifier, and the identifier length of the IMSI identifier. Then, based on the identifier length, it extracts encryption information for data encryption from the UUID identifier and uses this encryption information to encrypt the IMSI identifier to obtain the target IMSI identifier. Finally, it can encrypt the UUID identifier, the target IMSI identifier, and the identifier length using a private key to obtain encryption request data, and send this data to the server. The private key is the key returned by the server after the smart device successfully registers with the server. The invention also receives verification information from the server regarding the encrypted request data. The verification information is obtained by the server decrypting the first encrypted data using the public key corresponding to the private key to obtain the UUID identifier, the target IMSI identifier, and the identifier length. Based on the UUID identifier, target IMSI identifier, and identifier length, the server successfully verifies the smart device. The information generated is then generated by encrypting the identity information retrieved based on the UUID identifier and target IMSI identifier using the UUID identifier. Finally, the identity information is used to complete the smart device's identity authentication. Thus, during the security verification process, encryption is achieved by extracting the corresponding encrypted information from the UUID identifier based on the IMSI identifier length, effectively ensuring the security of data encryption. Simultaneously, associating private information with the UUID identifier and IMSI identifier improves the accuracy of security authentication.

[0085] It should be noted that smart devices can include mobile terminals, personal computers, digital keys, etc. When a user needs to authenticate their identity while using a smart device, the smart device can interact with the server to complete the authentication process, thereby enabling the user to perform corresponding functions. In this case, the smart device can be considered an application. Optionally, in this embodiment of the invention, a mobile terminal is used as an example for illustrative purposes. For a mobile terminal, corresponding functions can be implemented through a corresponding application; however, this invention does not impose any limitations on this.

[0086] Reference Figure 1 The diagram illustrates a flowchart of a security verification method provided in an embodiment of the present invention, which is applied to a smart device and may specifically include the following steps:

[0087] Step 101: Obtain the UUID identifier, IMSI identifier, and identifier length corresponding to the IMSI identifier of the smart device;

[0088] Optionally, this invention can be applied to the Internet of Things (IoT). In the IoT, for mobile terminals, it can involve mobile operators, USIM cards, etc. When a user joins the network, they need to register relevant real-name information with the mobile operator's system. The mobile operator assigns a USIM card (Universal Subscriber Identity Module) to the user upon joining. The USIM card stores the IMSI (International Mobile Subscriber Identity), the correspondence between the IMSI and MSISDN (Mobile Subscriber Integrated Services Digital Number), and the corresponding user's real-name information, which is saved in the operator's customer relationship management system. It should be noted that the MSISDN and the user's real-name information are merely examples of confidential data; these two pieces of information can be replaced with other confidential data, as long as they correspond to the IMSI.

[0089] In this embodiment of the invention, before a smart device can perform related functions (access, unlock, query, etc.), the smart device can first register with the server and obtain authorization from the server to perform the corresponding functions. Specifically, the smart device can obtain the UUID and IMSI identifiers, and then send them to the server. After receiving the UUID and IMSI identifiers from the smart device, the server can first query the corresponding preset MSISDN and preset user identifiers, establishing the association between the UUID, IMSI, preset MSISDN, and preset user identifiers for smart device registration. Simultaneously, it uses an asymmetric encryption algorithm to generate corresponding private and public keys, and encrypts the private key using the UUID identifier to generate corresponding encrypted registration data. Then, it sends the encrypted registration data and the corresponding decryption program to the smart device. After receiving the encrypted registration data and decryption program, the smart device can run the decryption program to decrypt the encrypted registration data using the UUID identifier, obtaining the private key. Thus, after successfully registering with the server, the smart device can obtain the private key returned by the server for data encryption, enabling subsequent data interaction to be encrypted based on the private key, ensuring the security of data exchange.

[0090] In the specific implementation, the registration and authorization process for smart devices first involves opening an IMSI query service on the server side. The server, through a certain security mechanism, authorizes smart devices to access and query IMSI, MSISDN, and corresponding user real-name information via encrypted transmission. Next, for the authorization process, the smart device reports its UUID and collected IMSI identifiers to the server interface for registration. Upon receiving the registration information from the smart device, the server generates a key pair using an asymmetric encryption algorithm based on the UUID identifier. It then associates the UUID and IMSI identifiers locally with the MSISDN and user identifiers, respectively. Simultaneously, it creates a corresponding encryption program to encrypt the private key using the UUID identifier. The encrypted private key and decryption program are then sent back to the smart device, completing the authorization. When the smart device receives the data, the decryption program automatically obtains the smart device's UUID identifier and automatically decrypts the encrypted data. The decryption program is not released at this stage; intercepted data by malicious actors will be unable to be decrypted due to the mismatched UUID identifiers, thus ensuring data security. Furthermore, the decryption program is a set of automatically executed code statements that consumes very few resources. The decryption program is configured to execute automatically, automatically acquiring data and performing decryption operations. The pre-configured decryption algorithm corresponds to the encryption method mentioned above.

[0091] After the smart device completes the registration and authorization process on the server, it can then perform corresponding functions such as data access, device unlocking, and data querying by performing the corresponding identity authentication.

[0092] In practical implementation, in scenarios requiring identity authentication, smart devices can first obtain the corresponding UUID identifier, IMSI identifier, and the identifier length corresponding to the IMSI identifier. The UUID identifier and IMSI identifier can be used to authenticate the smart device, while the identifier length corresponding to the IMSI identifier is used for data encryption to ensure the security of data interaction.

[0093] Step 102: Extract encryption information for data encryption from the UUID identifier according to the identifier length, and encrypt the IMSI identifier using the encryption information to obtain the target IMSI identifier;

[0094] In this embodiment of the invention, during the identity authentication process, after the smart device obtains the IMSI identifier, since the IMSI identifier can be a string of numbers, the smart device can identify the string of numbers and obtain the identifier length corresponding to the IMSI identifier, that is, how many digits it contains, assuming it is n. Further, the smart device can extract the corresponding encryption information from the UUID identifier based on n, and encrypt the IMSI identifier based on the encryption information to obtain the encrypted target IMSI identifier. Thus, by using the length corresponding to the IMSI identifier and the uniqueness of the UUID identifier, the IMSI identifier is encrypted, effectively ensuring the security of data encryption.

[0095] In a specific implementation, a smart device can extract information corresponding to the length of the identifier from the last bit of the UUID identifier as encryption information to encrypt the IMSI identifier. For example, assuming n is 10, the smart device can extract 10 bits from the last bit of the UUID identifier as encryption information to encrypt the IMSI identifier. Then, it performs an XOR operation with the unencrypted IMSI identifier based on these 10 bits to obtain an encrypted target IMSI identifier. Thus, by using the length of the IMSI identifier and the uniqueness of the UUID identifier, the IMSI identifier is encrypted, effectively ensuring the security of data encryption. Furthermore, by using the UUID identifier for encryption, legitimate terminals do not need to know the encryption key, while for malicious actors, even if they intercept the corresponding data packets, they cannot obtain the process data and confidential information, thus ensuring the security of data during data interaction.

[0096] Step 103: Encrypt the UUID identifier, the target IMSI identifier, and the identifier length using a private key to obtain encryption request data, and send the encryption request data to the server. The private key is the key returned by the server after the smart device successfully registers with the server.

[0097] In the above process, after encrypting the IMSI identifier using the UUID identifier, the terminal can also encrypt related data using the private key returned by the server. Specifically, the smart device can encrypt the UUID identifier to be sent to the server, the encrypted target IMSI identifier, and the corresponding identifier length using the private key to obtain the encryption request data. Then, the encrypted request data is sent to the server so that the server can authenticate the smart device based on the encrypted request data sent by the smart device. In this process, the data is encrypted a second time based on the private key. Even if the IMSI identifier is intercepted first, the corresponding data cannot be cracked, further ensuring the security of data interaction.

[0098] Step 104: Receive verification pass information returned by the server for the encrypted request data. The verification pass information is generated by the server decrypting the encrypted request data using the public key corresponding to the private key to obtain the UUID identifier, the target IMSI identifier, and the identifier length, and successfully verifying the smart device based on the UUID identifier, the target IMSI identifier, and the identifier length, and then encrypting the identity information queried based on the UUID identifier and the target IMSI identifier using the UUID identifier.

[0099] For the server, after receiving the encrypted request data sent by the smart device, it can encrypt the encrypted request data using the public key generated during the registration process to obtain the UUID identifier corresponding to the smart device, the target IMSI identifier, and the identifier length for the target IMSI identifier. Then, based on the identifier length, it extracts the corresponding encrypted information from the UUID identifier and decrypts the target IMSI identifier using the encrypted information to obtain the IMSI identifier corresponding to the smart device. Then, it queries the identity information based on the UUID identifier and the IMSI identifier. If the query finds identity information matching the smart device based on the UUID identifier and the IMSI identifier, it runs the corresponding encryption program to encrypt the identity information using the UUID identifier, generates the corresponding test pass information, and sends the test pass information to the smart device so that the smart device can complete identity authentication based on the identity information in the test pass information.

[0100] In the specific implementation, for the decryption of the target IMSI identifier, the server can extract information corresponding to the identifier length from the last bit of the UUID identifier as the encryption information for encrypting the IMSI identifier. For example, assuming n is 10, the server can extract 10 bits from the last bit of the UUID identifier as the encryption information for decrypting the target IMSI identifier. Then, based on these 10 bits, an XOR operation is performed with the encrypted target IMSI identifier to obtain the IMSI identifier corresponding to a smart device. Thus, by using the length of the IMSI identifier and the uniqueness of the UUID identifier, the IMSI identifier can be decrypted, effectively ensuring the security of data encryption.

[0101] The identity information may include the MSISDN identifier and the user identifier (such as the user's real name information). After decrypting the IMSI identifier, the server can query the target MSISDN identifier and target user identifier corresponding to the UUID identifier and IMSI identifier, and obtain the preset MSISDN identifier and preset user identifier of the smart device when it was registered on the server. If the target MSISDN identifier is the same as the preset MSISDN identifier, and / or the target user identifier is the same as the preset user identifier, the corresponding encryption program is run to encrypt the identity information through the UUID identifier and generate the corresponding test pass information; if the target MSISDN identifier is different from the preset MSISDN identifier, and the target user identifier is different from the preset user identifier, the verification failure information corresponding to the encryption request data is generated and sent to the smart device.

[0102] In one example, the server authenticates the information submitted by the smart device to confirm its legitimacy. The server-side authentication process includes: decrypting the encrypted data in the request using a public key to obtain a UUID identifier and an encrypted IMSI identifier; then, performing an XOR operation between the last n bits of the UUID identifier and the decrypted encrypted IMSI identifier to recover a new IMSI identifier to be checked (referred to as the "to be checked IMSI identifier" since legitimacy verification has not yet been performed); and checking the tables for the UUID identifier and the target MSISDN identifier and target user real-name information associated with it to determine if the target MSISDN identifier is the same as the preset MSISDN identifier used during smart device registration (or, alternatively, whether the user real-name information (i.e., user identifier) ​​is the same, or whether both data are identical). If they are the same, the request is considered legitimate. Thus, even if malicious actors intercept the UUID and IMSI identifiers, the server processes the IMSI identifier, resulting in a new IMSI identifier that will not match the original. Therefore, the comparison of the associated information will fail the legitimacy verification. For smart devices that pass authentication, the server can query the MSISDN identifier corresponding to the IMSI identifier and the user's real name information. The server can return the corresponding MSISDN identifier and user's real name information to the smart device. For smart devices that fail authentication, the server can return the corresponding verification failure information to the smart device to inform it that its identity authentication has failed.

[0103] For smart devices, after receiving a successful test response from the server, they can run a decryption program to decrypt the successful verification information using the UUID identifier, obtaining the smart device's identity information, which includes at least the MSISDN identifier and the user identifier. Conversely, if a verification failure message for the encrypted request data is received from the server, this failure message is generated after the server decrypts the first encrypted data using the public key corresponding to the private key to obtain the UUID identifier and the target IMSI identifier, and fails to verify the smart device based on the UUID identifier and the target IMSI identifier. The smart device can then output a prompt message corresponding to the verification failure message. Thus, during the security verification process, encryption is achieved by extracting the corresponding encrypted information from the UUID identifier based on the length of the IMSI identifier, effectively ensuring the security of data encryption. Simultaneously, associating private information with the UUID identifier and the IMSI identifier improves the accuracy of security authentication.

[0104] In the specific implementation, the server returns the MSISDN identifier corresponding to the queried IMSI identifier and the user identifier to the smart device via TCP protocol messages. Furthermore, the server can encrypt the data packets using an encryption program, encrypting the data (MSISDN identifier and user identifier) ​​using the UUID identifier. In the aforementioned embodiment, when the smart device registers, the server provides a decryption program and has already obtained the UUID identifier. At this point, the decryption program can directly decrypt the encrypted data to obtain the MSISDN identifier and user identifier, and automatically release the decryption program itself after decryption to reduce the performance overhead of the smart device.

[0105] Step 105: Complete the identity authentication of the smart device based on the identity information.

[0106] Once the server successfully authenticates the smart device and returns the corresponding MSISDN identifier and user identifier, the smart device can perform identity authentication based on the MSISDN identifier and user identifier, such as login. After successful identity authentication, the smart device can use the corresponding functions provided by the smart device. During the security verification process, encryption is achieved by extracting the corresponding encrypted information from the UUID identifier based on the length of the IMSI identifier, which effectively ensures the security of data encryption. At the same time, associating private information with the UUID identifier and the IMSI identifier improves the accuracy of security authentication.

[0107] In one example, refer to Figure 2This diagram illustrates a security verification process provided in an embodiment of the present invention. Assuming that the corresponding function is implemented through an App (Application), and identity verification is required during this process, the App can interact with the operator (server) to exchange data. Specifically, the App can first send its UUID and IMSI to the operator for registration. Upon receiving the UUID and IMSI, the operator can generate a key pair based on an asymmetric algorithm and associate the UUID and IMSI with confidential information (MSISDN identifier and user real-name information, etc.). Simultaneously, the operator encrypts the private key within the key pair using the UUID and returns the encrypted private key and the corresponding decryption program to the App. The App obtains the UUID through the decryption program and decrypts it to obtain the corresponding private key. When the App initiates a query request to the operator, it can encrypt the IMSI based on the UUID to obtain the encrypted IMSI, then encrypt both the UUID and the encrypted IMSI based on the private key, and finally send the encrypted result to the operator. After receiving the encryption result, the operator can first decrypt it using the public key to obtain the UUID and encrypted IMSI. Then, it can decrypt the encrypted IMSI using the UUID to obtain the IMSI to be inspected. Next, it can look up the corresponding confidential information using the UUID and the IMSI to be inspected. If found, it can encrypt the confidential information using the UUID based on the encryption program and return the encrypted confidential information to the APP. The APP can decrypt the encrypted confidential information using the decryption program to obtain the corresponding confidential information and release the decryption program. Thus, during the security verification process, encryption is achieved by extracting the corresponding encrypted information from the UUID based on the length of the IMSI identifier, effectively ensuring the security of data encryption. Simultaneously, associating private information with the UUID identifier and the IMSI identifier improves the accuracy of security authentication.

[0108] In this embodiment of the invention, when a smart device needs to perform identity authentication to complete a corresponding operation, the smart device can obtain its corresponding UUID identifier, IMSI identifier, and the identifier length corresponding to the IMSI identifier. Then, based on the identifier length, it extracts encryption information for data encryption from the UUID identifier and uses this encryption information to encrypt the IMSI identifier to obtain the target IMSI identifier. Next, it can encrypt the UUID identifier, the target IMSI identifier, and the identifier length using a private key to obtain encryption request data. This encryption request data is then sent to the server. The private key is the key returned by the server after the smart device successfully registers with the server. The device also receives verification information from the server regarding the encrypted request data. The server decrypts the first encrypted data using the public key corresponding to the private key to obtain the UUID identifier, the target IMSI identifier, and the identifier length. Based on the UUID identifier, target IMSI identifier, and identifier length, the server successfully verifies the smart device. The server then encrypts the identity information retrieved based on the UUID identifier and target IMSI identifier using the UUID identifier, generating the final information. This identity information is then used to complete the smart device's authentication. Thus, during the security verification process, encryption is achieved by extracting corresponding encrypted information from the UUID identifier based on the IMSI identifier's length, effectively ensuring data encryption security. Simultaneously, associating private information with the UUID identifier and IMSI identifier improves the accuracy of security authentication.

[0109] Reference Figure 3 The diagram illustrates a flowchart of a security verification method provided in an embodiment of the present invention, applied to a server, and specifically includes the following steps:

[0110] Step 301: Obtain the encrypted request data sent by the smart device;

[0111] Step 302: Decrypt the encrypted request data using the public key to obtain the UUID identifier corresponding to the smart device, the target IMSI identifier, and the identifier length for the target IMSI identifier;

[0112] Step 303: Extract the corresponding encrypted information from the UUID identifier according to the identifier length, and decrypt the target IMSI identifier using the encrypted information to obtain the IMSI identifier corresponding to the smart device;

[0113] Step 304: If identity information matching the smart device is found based on the UUID identifier and the IMSI identifier, then the corresponding encryption program is run to encrypt the identity information using the UUID identifier, generate corresponding test pass information, and send the test pass information to the smart device. The identity information is used to authenticate the smart device.

[0114] In one optional embodiment, the step of extracting the corresponding encrypted information from the UUID identifier based on the identifier length includes:

[0115] Information corresponding to the length of the identifier is extracted from the last digit of the UUID identifier and used as encryption information to encrypt the IMSI identifier.

[0116] In one optional embodiment, if identity information matching the smart device is found based on the UUID identifier and the IMSI identifier, then a corresponding encryption program is run to encrypt the identity information using the UUID identifier, generating corresponding test pass information, including:

[0117] Query the target MSISDN identifier and target user identifier corresponding to the UUID identifier and the IMSI identifier, and obtain the preset MSISDN identifier and preset user identifier when the smart device registered on the server;

[0118] If the target MSISDN identifier is the same as the preset MSISDN identifier, and / or the target user identifier is the same as the preset user identifier, then the corresponding encryption program is run to encrypt the identity information using the UUID identifier, and generate the corresponding test pass information.

[0119] In one alternative embodiment, it further includes:

[0120] If the target MSISDN identifier is different from the preset MSISDN identifier, and the target user identifier is different from the preset user identifier, then a verification failure message corresponding to the encrypted request data is generated, and the verification failure message is sent to the smart device.

[0121] In one alternative embodiment, it further includes:

[0122] Obtain the UUID identifier and the IMSI identifier sent by the smart device;

[0123] Query the preset MSISDN identifier and preset user identifier corresponding to the UUID identifier and the IMSI identifier, and establish the corresponding association relationship between the UUID identifier, the IMSI identifier, the preset MSISDN identifier and the preset user identifier for the registration of the smart device;

[0124] A corresponding private key and public key are generated using an asymmetric encryption algorithm, and the private key is encrypted using the UUID identifier to generate corresponding registration encrypted data;

[0125] The registration encryption data and the decryption program corresponding to the encryption program are sent to the smart device.

[0126] In this embodiment of the invention, when a smart device needs to perform identity authentication to complete a corresponding operation, the server can obtain the encrypted request data sent by the smart device; encrypt the encrypted request data using a public key to obtain the UUID identifier corresponding to the smart device, the target IMSI identifier, and the identifier length for the target IMSI identifier; extract the corresponding encrypted information from the UUID identifier according to the identifier length, and decrypt the target IMSI identifier using the encrypted information to obtain the IMSI identifier corresponding to the smart device; if identity information matching the smart device is found based on the UUID identifier and the IMSI identifier, the corresponding encryption program is run to encrypt the identity information using the UUID identifier, generating corresponding test pass information, and sending the test pass information to the smart device. The identity information is used to authenticate the smart device. Thus, during the security verification process, encryption is achieved by extracting the corresponding encrypted information from the UUID identifier based on the length of the IMSI identifier, effectively ensuring the security of data encryption. At the same time, associating private information with the UUID identifier and the IMSI identifier improves the accuracy of security authentication.

[0127] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0128] Reference Figure 4 The diagram illustrates a structural block diagram of a security verification device provided in an embodiment of the present invention, which is applied to a smart device and may specifically include the following modules:

[0129] The identifier acquisition module 401 is used to acquire the UUID identifier, IMSI identifier, and identifier length corresponding to the IMSI identifier of the smart device.

[0130] The identifier encryption module 402 is used to extract encryption information for data encryption from the UUID identifier according to the identifier length, and use the encryption information to encrypt the IMSI identifier to obtain the target IMSI identifier;

[0131] The data encryption module 403 is used to encrypt the UUID identifier, the target IMSI identifier, and the identifier length using a private key to obtain encryption request data, and send the encryption request data to the server. The private key is the key returned by the server after the smart device successfully registers with the server.

[0132] The information receiving module 404 is used to receive the verification pass information returned by the server for the encrypted request data. The verification pass information is generated by the server decrypting the encrypted request data according to the public key corresponding to the private key to obtain the UUID identifier, the target IMSI identifier, and the identifier length, and successfully verifying the smart device according to the UUID identifier, the target IMSI identifier, and the identifier length, and encrypting the identity information queried based on the UUID identifier and the target IMSI identifier using the UUID identifier.

[0133] The identity authentication module 405 is used to complete the identity authentication of the smart device based on the identity information.

[0134] In one optional embodiment, the identifier encryption module 402 is specifically used for:

[0135] Information corresponding to the length of the identifier is extracted from the last digit of the UUID identifier and used as encryption information to encrypt the IMSI identifier.

[0136] In one alternative embodiment, it further includes:

[0137] The identifier sending module is used to send the UUID identifier and the IMSI identifier to the server, and receive the registration encrypted data and decryption program returned by the server. The registration encrypted data is data generated by the server using an asymmetric encryption algorithm to generate the corresponding private key and public key, and then encrypting the private key using the UUID identifier.

[0138] The key acquisition module is used to run the decryption program to decrypt the registration encrypted data using the UUID identifier and obtain the private key.

[0139] In one optional embodiment, the information receiving module 404 is specifically used for:

[0140] The decryption program is run to decrypt the verification information using the UUID identifier to obtain the identity information corresponding to the smart device. The identity information includes at least the MSISDN identifier and the user identifier.

[0141] In one alternative embodiment, it further includes:

[0142] The failure information receiving module 404 is used to receive the verification failure information returned by the server for the encrypted request data. The verification failure information is generated by the server after decrypting the encrypted request data according to the public key corresponding to the private key to obtain the UUID identifier and the target IMSI identifier, and failing to verify the smart device according to the UUID identifier and the target IMSI identifier.

[0143] The prompt message output module is used to output prompt messages corresponding to the verification failure information.

[0144] Reference Figure 5 The diagram illustrates a structural block diagram of a security verification device provided in an embodiment of the present invention, which is applied to a server and may specifically include the following modules:

[0145] The data acquisition module 501 is used to acquire encrypted request data sent by the smart device;

[0146] The data decryption module 502 is used to decrypt the encrypted request data using a public key to obtain the UUID identifier corresponding to the smart device, the target IMSI identifier, and the identifier length for the target IMSI identifier;

[0147] The identifier decryption module 503 is used to extract corresponding encrypted information from the UUID identifier according to the identifier length, and decrypt the target IMSI identifier through the encrypted information to obtain the IMSI identifier corresponding to the smart device;

[0148] The information sending module 504 is used to run a corresponding encryption program to encrypt the identity information using the UUID identifier if the identity information matching the smart device is found based on the UUID identifier and the IMSI identifier, generate corresponding test pass information, and send the test pass information to the smart device. The identity information is used to authenticate the smart device.

[0149] In one optional embodiment, the identifier decryption module 503 is specifically used for:

[0150] Information corresponding to the length of the identifier is extracted from the last digit of the UUID identifier and used as encryption information to encrypt the IMSI identifier.

[0151] In one optional embodiment, the information sending module 504 is specifically used for:

[0152] Query the target MSISDN identifier and target user identifier corresponding to the UUID identifier and the IMSI identifier, and obtain the preset MSISDN identifier and preset user identifier when the smart device registered on the server;

[0153] If the target MSISDN identifier is the same as the preset MSISDN identifier, and / or the target user identifier is the same as the preset user identifier, then the corresponding encryption program is run to encrypt the identity information using the UUID identifier, and generate the corresponding test pass information.

[0154] In one alternative embodiment, it further includes:

[0155] The failure information sending module 504 is used to generate verification failure information corresponding to the encrypted request data and send the verification failure information to the smart device if the target MSISDN identifier is different from the preset MSISDN identifier and the target user identifier is different from the preset user identifier.

[0156] In one alternative embodiment, it further includes:

[0157] The identifier acquisition module is used to acquire the UUID identifier and the IMSI identifier sent by the smart device;

[0158] The registration module is used to query the preset MSISDN identifier and preset user identifier corresponding to the UUID identifier and the IMSI identifier, and establish the corresponding association relationship between the UUID identifier, the IMSI identifier, the preset MSISDN identifier and the preset user identifier in order to register the smart device;

[0159] The key generation module is used to generate corresponding private and public keys using an asymmetric encryption algorithm, and to encrypt the private key using the UUID identifier to generate corresponding registration encrypted data.

[0160] The data sending module is used to send the registration encrypted data and the decryption program corresponding to the encryption program to the smart device.

[0161] As the device embodiment is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0162] In addition, this invention also provides an electronic device, including: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the various processes of the above-described security verification method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0163] This invention also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it implements the various processes of the security verification method embodiments described above and achieves the same technical effect. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0164] Figure 6 A schematic diagram of the hardware structure of an electronic device for implementing various embodiments of the present invention.

[0165] The electronic device 600 includes, but is not limited to, components such as: a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, a user input unit 607, an interface unit 608, a memory 609, a processor 610, and a power supply 611. Those skilled in the art will understand that the electronic device structure involved in the embodiments of the present invention does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than illustrated, or combine certain components, or have different component arrangements. In the embodiments of the present invention, the electronic device includes, but is not limited to, mobile phones, tablet computers, laptop computers, PDAs, in-vehicle terminals, wearable devices, and pedometers.

[0166] It should be understood that, in this embodiment of the invention, the radio frequency unit 601 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink data from the base station and processes it with the processor 610; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 601 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc. Furthermore, the radio frequency unit 601 can also communicate with networks and other devices through a wireless communication system.

[0167] The electronic device provides users with wireless broadband internet access through the network module 602, such as helping users send and receive emails, browse web pages, and access streaming media.

[0168] The audio output unit 603 can convert audio data received by the radio frequency unit 601 or the network module 602 or stored in the memory 609 into audio signals and output them as sound. Furthermore, the audio output unit 603 can also provide audio output related to specific functions performed by the electronic device 600 (e.g., call signal reception sound, message reception sound, etc.). The audio output unit 603 includes a speaker, a buzzer, and a receiver, etc.

[0169] Input unit 604 is used to receive audio or video signals. Input unit 604 may include a graphics processing unit (GPU) 6041 and a microphone 6042. The GPU 6041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on display unit 606. The image frames processed by GPU 6041 can be stored in memory 609 (or other storage media) or transmitted via radio frequency unit 601 or network module 602. Microphone 6042 can receive sound and process such sound into audio data. The processed audio data can be converted into a format that can be transmitted to a mobile communication base station via radio frequency unit 601 in telephone call mode.

[0170] The electronic device 600 also includes at least one sensor 605, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 6061 according to the ambient light level, and the proximity sensor can turn off the display panel 6061 and / or backlight when the electronic device 600 is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used to identify the posture of the electronic device (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. The sensor 605 may also include a fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared sensor, etc., which will not be described in detail here.

[0171] The display unit 606 is used to display information input by the user or information provided to the user. The display unit 606 may include a display panel 6061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0172] User input unit 607 can be used to receive input numerical or character information, and to generate key signal inputs related to user settings and function control of electronic devices. Specifically, user input unit 607 includes a touch panel 6071 and other input devices 6072. Touch panel 6071, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 6071). Touch panel 6071 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to processor 610, which receives and executes commands from processor 610. In addition, touch panel 6071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. Besides touch panel 6071, user input unit 607 may also include other input devices 6072. Specifically, other input devices 6072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, joysticks, etc., which will not be described in detail here.

[0173] Furthermore, the touch panel 6071 can cover the display panel 6061. When the touch panel 6071 detects a touch operation on or near it, it transmits the information to the processor 610 to determine the type of touch event. Subsequently, the processor 610 provides corresponding visual output on the display panel 6061 according to the type of touch event. It is understood that in one embodiment, the touch panel 6071 and the display panel 6061 are implemented as two independent components to realize the input and output functions of the electronic device. However, in some embodiments, the touch panel 6071 and the display panel 6061 can be integrated to realize the input and output functions of the electronic device. The specific implementation is not limited here.

[0174] Interface unit 608 serves as an interface for connecting external devices to electronic device 600. For example, external devices may include a wired or wireless headphone port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 608 can be used to receive input from external devices (e.g., data, power, etc.) and transmit the received input to one or more components within electronic device 600, or it can be used to transmit data between electronic device 600 and external devices.

[0175] The memory 609 can be used to store software programs and various data. The memory 609 may primarily include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). Furthermore, the memory 609 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0176] The processor 610 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 609, and by calling data stored in the memory 609, it performs various functions and processes data, thereby providing overall monitoring of the electronic device. The processor 610 may include one or more processing units; preferably, the processor 610 may integrate an application processor and a modem processor. The application processor mainly handles the operating system, user interface, and applications, while the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 610.

[0177] The electronic device 600 may also include a power supply 611 (such as a battery) that supplies power to various components. Preferably, the power supply 611 can be logically connected to the processor 610 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system.

[0178] In addition, the electronic device 600 includes some functional modules not shown, which will not be described in detail here.

[0179] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0180] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0181] The embodiments of the present invention have been described above with reference to the accompanying drawings. However, the present invention is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of the present invention without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of the present invention.

[0182] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this invention can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0183] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0184] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0185] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0186] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0187] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0188] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A security verification method, characterized in that, Applied to smart devices, the method includes: Obtain the UUID identifier, IMSI identifier, and identifier length corresponding to the IMSI identifier of the smart device; Based on the identifier length, the encryption information for data encryption is extracted from the UUID identifier, and the encryption information is used to encrypt the IMSI identifier to obtain the target IMSI identifier; The UUID identifier, the target IMSI identifier, and the identifier length are encrypted using a private key to obtain encryption request data, which is then sent to the server. The private key is the key returned by the server after the smart device has successfully registered with the server. The system receives verification information returned by the server regarding the encrypted request data. This verification information is generated by the server decrypting the encrypted request data using the public key corresponding to the private key to obtain the UUID identifier, the target IMSI identifier, and the identifier length, successfully verifying the smart device based on the UUID identifier, the target IMSI identifier, and the identifier length, and then encrypting the identity information queried based on the UUID identifier and the target IMSI identifier using the UUID identifier. The identity of the smart device is authenticated based on the identity information.

2. The method according to claim 1, characterized in that, The step of extracting encryption information for data encryption from the UUID identifier based on the identifier length includes: Information corresponding to the length of the identifier is extracted from the last digit of the UUID identifier and used as encryption information to encrypt the IMSI identifier.

3. The method according to claim 1, characterized in that, Also includes: The UUID identifier and the IMSI identifier are sent to the server, and the registration encrypted data and decryption program returned by the server are received. The registration encrypted data is the data generated by the server using an asymmetric encryption algorithm to generate the corresponding private key and public key, and then encrypting the private key using the UUID identifier. Run the decryption program to decrypt the registered encrypted data using the UUID identifier to obtain the private key.

4. The method according to claim 3, characterized in that, The receipt of the verification pass information for the encrypted request data returned by the server includes: The decryption program is run to decrypt the verification pass information using the UUID identifier to obtain the identity information corresponding to the smart device. The identity information includes at least the MSISDN identifier and the user identifier.

5. The method according to any one of claims 1-4, characterized in that, Also includes: The server receives verification failure information for the encrypted request data returned by the server. The verification failure information is generated by the server after decrypting the encrypted request data with the public key corresponding to the private key to obtain the UUID identifier and the target IMSI identifier, and then failing to verify the smart device with the UUID identifier and the target IMSI identifier. Output a prompt message corresponding to the verification failure information.

6. A security verification method, characterized in that, Applied to the server side, the method includes: Obtain encrypted request data sent by smart devices; The encrypted request data is decrypted using a public key to obtain the UUID identifier corresponding to the smart device, the target IMSI identifier, and the identifier length for the target IMSI identifier; Based on the identifier length, the corresponding encrypted information is extracted from the UUID identifier, and the target IMSI identifier is decrypted using the encrypted information to obtain the IMSI identifier corresponding to the smart device; If identity information matching the smart device is found based on the UUID identifier and the IMSI identifier, then the corresponding encryption program is run to encrypt the identity information using the UUID identifier, generate corresponding test pass information, and send the test pass information to the smart device. The identity information is used to authenticate the smart device.

7. The method according to claim 6, characterized in that, The step of extracting the corresponding encrypted information from the UUID identifier based on the identifier length includes: Information corresponding to the length of the identifier is extracted from the last digit of the UUID identifier and used as encryption information to encrypt the IMSI identifier.

8. The method according to claim 6, characterized in that, If identity information matching the smart device is found based on the UUID and IMSI identifiers, then a corresponding encryption program is run to encrypt the identity information using the UUID identifier, generating corresponding test pass information, including: Query the target MSISDN identifier and target user identifier corresponding to the UUID identifier and the IMSI identifier, and obtain the preset MSISDN identifier and preset user identifier when the smart device registered on the server; If the target MSISDN identifier is the same as the preset MSISDN identifier, and / or the target user identifier is the same as the preset user identifier, then the corresponding encryption program is run to encrypt the identity information using the UUID identifier, and generate the corresponding test pass information.

9. The method according to claim 8, characterized in that, Also includes: If the target MSISDN identifier is different from the preset MSISDN identifier, and the target user identifier is different from the preset user identifier, then a verification failure message corresponding to the encrypted request data is generated, and the verification failure message is sent to the smart device.

10. The method according to claim 6, characterized in that, Also includes: Obtain the UUID identifier and the IMSI identifier sent by the smart device; Query the preset MSISDN identifier and preset user identifier corresponding to the UUID identifier and the IMSI identifier, and establish the corresponding association relationship between the UUID identifier, the IMSI identifier, the preset MSISDN identifier and the preset user identifier for the registration of the smart device; A corresponding private key and public key are generated using an asymmetric encryption algorithm, and the private key is encrypted using the UUID identifier to generate corresponding registration encrypted data; The registration encryption data and the decryption program corresponding to the encryption program are sent to the smart device.

11. A security verification device, characterized in that, The device, used in smart devices, includes: The identifier acquisition module is used to acquire the UUID identifier, IMSI identifier, and identifier length corresponding to the IMSI identifier of the smart device. An identifier encryption module is used to extract encryption information for data encryption from the UUID identifier according to the identifier length, and to encrypt the IMSI identifier using the encryption information to obtain the target IMSI identifier; The data encryption module is used to encrypt the UUID identifier, the target IMSI identifier, and the identifier length using a private key to obtain encryption request data, and send the encryption request data to the server. The private key is the key returned by the server after the smart device successfully registers with the server. The information receiving module is used to receive the verification pass information returned by the server for the encrypted request data. The verification pass information is generated by the server decrypting the encrypted request data according to the public key corresponding to the private key to obtain the UUID identifier, the target IMSI identifier, and the identifier length, and successfully verifying the smart device according to the UUID identifier, the target IMSI identifier, and the identifier length, and encrypting the identity information queried based on the UUID identifier and the target IMSI identifier using the UUID identifier. The identity authentication module is used to authenticate the identity of the smart device based on the identity information.

12. A security verification device, characterized in that, Applied to the server side, the device includes: The data acquisition module is used to acquire encrypted request data sent by smart devices; The data decryption module is used to decrypt the encrypted request data using a public key to obtain the UUID identifier corresponding to the smart device, the target IMSI identifier, and the identifier length for the target IMSI identifier; The identifier decryption module is used to extract corresponding encrypted information from the UUID identifier according to the identifier length, and decrypt the target IMSI identifier through the encrypted information to obtain the IMSI identifier corresponding to the smart device; The information sending module is used to run a corresponding encryption program to encrypt the identity information using the UUID identifier if the identity information matching the smart device is found based on the UUID identifier and the IMSI identifier, generate corresponding test pass information, and send the test pass information to the smart device. The identity information is used to authenticate the smart device.

13. An electronic device, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; The memory is used to store computer programs; When the processor executes a program stored in the memory, it implements the method as described in any one of claims 1-10.

14. A computer-readable storage medium having instructions stored thereon that, when executed by one or more processors, cause the processors to perform the method as described in any one of claims 1-10.

Images