Point-to-point identity authentication method for devices with same account number

Abstract

The invention relates to the technical field of communication, and particularly provides a point-to-point identity authentication method for equipment with the same account number. The same-account device point-to-point identity authentication method applied to a first device comprises the steps that the first device receives second device same-account authentication information sent by a second device, and the second device same-account authentication information at least comprises a second same-account device certificate; the second same-account device certificate comprises account ID information and device ID information corresponding to the second device; the first device judges whether the first device and the second device belong to the same account number device or not according to the same account number authentication information of the second device; and if the first equipment and the second equipment belong to the same account number equipment, the first equipment sends first equipment same account number authentication information to the second equipment, so that the second equipment judges whether the first equipment and the second equipment belong to the same account number equipment based on the first equipment same account number authentication information. Therefore, data synchronization between different devices under the same account number is realized.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and specifically provides a method for point-to-point identity authentication of devices with the same account. Background Art

[0002] With the vigorous development of Internet technology, communication terminals are used more and more widely. Many users own multiple communication terminals at the same time, and users change communication terminals more and more frequently.

[0003] In multi-device interconnected businesses, it is necessary to be user-centric and achieve data synchronization and sharing between multiple devices of the same user (for example, mobile phones and car terminals).

[0004] In the traditional data synchronization solution for devices with the same account, such as Figure 1 As shown, each device needs to log in to the account, bind the device and the account, and achieve data synchronization and sharing with the assistance of the account cloud.

[0005] However, for a device that is not always connected to the Internet, there is no guarantee that the account can be successfully logged in at every moment. Therefore, the above solution is not applicable to the car computer.

[0006] Accordingly, a new solution is needed in the art to solve the above problems. Summary of the invention

[0007] In order to overcome the above-mentioned defects, the present invention is proposed to provide a point-to-point identity authentication method for devices with the same account, so as to solve or at least partially solve the technical problem that data synchronization and sharing cannot be achieved due to the inability of the vehicle computer to connect to the Internet in real time.

[0008] In a first aspect, the present invention provides a method for peer-to-peer identity authentication of devices with the same account number, which is applied to a first device, and the method comprises the following steps:

[0009] The first device receives second device same-account authentication information sent by the second device, where the second device same-account authentication information at least includes a second same-account device certificate, and the second same-account device certificate includes account ID information and device ID information corresponding to the second device;

[0010] The first device determines, based on the same account authentication information of the second device, whether the first device and the second device are devices with the same account;

[0011] If the first device and the second device are devices with the same account, the first device sends the first device same-account authentication information to the second device, so that the second device determines whether the first device and the second device are devices with the same account based on the first device same-account authentication information.

[0012] In a technical solution of the above-mentioned method for peer-to-peer identity authentication of devices with the same account, the method further includes the first device obtaining a first device certificate with the same account based on at least the following steps:

[0013] The first device initiates a device authentication request to the third device, or initiates an account authentication request and a device authentication request;

[0014] The first device receives a first same-account device certificate issued by a third device, where the first same-account device certificate is issued by the third device in response to a device authentication request being passed, or an account authentication request and a device authentication request being passed.

[0015] In a technical solution of the above-mentioned same-account device peer-to-peer identity authentication method, the first device initiates an account authentication request to the third device, including:

[0016] The first device logs in to the account and initiates an account authentication request to the third device;

[0017] In response to the account authentication request being approved, the first device obtains the account login credentials from the third device.

[0018] In one technical solution of the above-mentioned same-account device point-to-point identity authentication method, the first device is pre-installed with a first device certificate and a first device public-private key pair;

[0019] The first device initiates a device authentication request to the third device, including:

[0020] The first device signs the account login credential based on the preset first device private key, and sends the first device certificate, the signature result, and the first device public key to the third device, so that the third device verifies the validity of the first device certificate, the signature result, and the account login credential respectively, and then issues the first same-account device certificate to the first device;

[0021] Or, the first device initiates a device authentication request to the third device, including:

[0022] The first device signs the first device certificate based on the preset first device private key, and sends the first device certificate, the signature result and the first device public key to the third device, so that the third device verifies the validity of the first device certificate and the signature result respectively, and then issues the first same-account device certificate to the first device.

[0023] In a technical solution of the above-mentioned method for peer-to-peer identity authentication of devices with the same account, the first device is a device shared by multiple accounts, and the method further includes:

[0024] Acquiring current user information of the first device based on the image acquisition device;

[0025] Determine an account number of a current user of the first device based on the current user information;

[0026] The first device initiates a device authentication request to the third device, further comprising:

[0027] If the first device is currently bound to another account that is different from the account of the current user, the first device receives revocation information issued by the third device for revoking the certificate corresponding to the other account, and receives the first same-account device certificate issued by the third device, where the first same-account device certificate includes the account ID information and device ID information of the current user of the first device.

[0028] In a technical solution of the above-mentioned peer-to-peer identity authentication method for devices with the same account, the first device determines whether the first device and the second device are devices with the same account according to the authentication information of the second device with the same account, including:

[0029] The first device compares the account ID information of the first same-account device certificate and the second same-account device certificate;

[0030] Determine whether they belong to the same account device based on the comparison result.

[0031] In a technical solution of the above-mentioned peer-to-peer identity authentication method for devices with the same account, the second device same-account authentication information also includes a public key in a second random key pair and a second digital signature, and the method further includes:

[0032] The first device generates a first random key pair, and sends a public key in the first random key pair to the second device;

[0033] The first device receives a public key in a second random key pair and a second digital signature sent by the second device, wherein the second digital signature is a signature of the public key in the first random key pair and the public key in the second random key sent by the first device based on the private key in the second random key.

[0034] Judging whether the devices belong to the same account based on the comparison results includes:

[0035] If the account ID information of the first same-account device certificate and the second same-account device certificate is the same, the first device verifies the second digital signature, and after the verification is passed, it is confirmed that the first device and the second device belong to the same-account devices.

[0036] In a technical solution of the above-mentioned same-account device point-to-point identity authentication method, the first device is pre-installed with a first same-account device certificate key pair; the first device sends the first device same-account authentication information to the second device, including:

[0037] The first device uses the private key in the first same-account device certificate key pair to sign the public key in the second random key pair sent by the second device and the public key in the first random key pair to generate a first digital signature;

[0038] The first device generates hash data based on the first digital signature and the second digital signature;

[0039] The first device sends the first digital signature, hash data and the first same-account device certificate to the second device, so that the second device determines whether the first device and the second device are same-account devices based on the first digital signature, hash data and the first same-account device certificate.

[0040] In a second aspect, the present invention provides a method for peer-to-peer identity authentication of devices with the same account number, which is applied to a second device, and the method comprises the following steps:

[0041] The second device sends second device same-account authentication information to the first device, where the second device same-account authentication information at least includes a second same-account device certificate, where the second same-account device certificate includes account ID information and device ID information corresponding to the second device;

[0042] After the first device determines that the first device and the second device are devices with the same account, the second device receives the first device same account authentication information sent by the first device;

[0043] The second device determines whether the first device and the second device are devices with the same account based on the same account authentication information of the first device.

[0044] In a technical solution of the above-mentioned method for peer-to-peer identity authentication of devices with the same account, the method further includes the second device obtaining a second device certificate with the same account based on at least the following steps:

[0045] The second device initiates a device authentication request to the third device, or initiates an account authentication request and a device authentication request;

[0046] The second device receives a second same-account device certificate issued by the third device, where the second same-account device certificate is issued by the third device in response to a device authentication request being passed, or an account authentication request and a device authentication request being passed.

[0047] In a technical solution of the above-mentioned same-account device point-to-point identity authentication method, the second device initiates an account authentication request to the third device, including:

[0048] The second device logs in to the account and initiates an account authentication request to the third device;

[0049] In response to the account authentication request being approved, the second device obtains the account login credentials from the third device.

[0050] In one technical solution of the above-mentioned same-account device point-to-point identity authentication method, the second device is pre-installed with a second device certificate and a second device public-private key pair.

[0051] The second device initiates a device authentication request to the third device, including:

[0052] The second device signs the account login credential based on the preset second device private key, and sends the second device certificate, the signature result, and the second device public key to the third device, so that the third device verifies the validity of the second device certificate, the signature result, and the account login credential respectively, and then issues the second same-account device certificate to the second device;

[0053] Or, the second device initiates a device authentication request to the third device, including:

[0054] The second device signs the second device certificate based on the preset second device private key, and sends the first device certificate, signature result and second device public key to the third device, so that the third device verifies the validity of the second device certificate and signature result respectively, and then issues the second same-account device certificate to the second device.

[0055] In a technical solution of the above-mentioned method for peer-to-peer identity authentication of devices with the same account, the second device is a device shared by multiple accounts, and the method further includes:

[0056] Acquiring current user information of the second device based on the image acquisition device;

[0057] Determine the account of the current user of the second device based on the current user information;

[0058] The second device initiates a device authentication request to the third device, further comprising:

[0059] If the second device is currently bound to another account that is different from the account of the current user, the second device receives the revocation information issued by the third device for revoking the certificate corresponding to the other account, and receives the second same-account device certificate issued by the third device, where the second same-account device certificate includes the account ID information and device ID information of the current user of the second device.

[0060] In a technical solution of the above-mentioned same-account device point-to-point identity authentication method, the first device same-account authentication information also includes a public key in the first random key pair, and the second device is pre-installed with a second same-account device certificate key pair, and the method also includes:

[0061] The second device receives the public key in the first random key pair sent by the first device;

[0062] The second device generates a second random key pair, uses the private key in the second same-account device certificate key pair to sign the received public key in the first random key pair and the public key in the second random key pair, generates a second digital signature, and sends it to the first device;

[0063] After the first device verifies the second digital signature, the second device receives the first digital signature, hash data, and the first same-account device certificate sent by the first device;

[0064] Judging whether the devices belong to the same account based on the comparison results includes:

[0065] If the account ID information of the first same-account device certificate and the second same-account device certificate is the same, the first device verifies the first digital signature and the hash data. After the verification is successful, it is confirmed that the first device and the second device belong to the same-account devices.

[0066] In a third aspect, the present invention provides an information transmission method, which is applied to an information transmission system, wherein the system includes a first device and a second device, and is characterized in that:

[0067] The first device performs same-account device point-to-point identity authentication on the second device based on the same-account device point-to-point identity authentication method described in any one of the technical solutions of the same-account device point-to-point identity authentication method;

[0068] The second device performs same-account device point-to-point identity authentication on the first device based on the same-account device point-to-point identity authentication method described in any one of the technical solutions of the above-mentioned same-account device point-to-point identity authentication method;

[0069] After the first device and the second device are both authenticated, obtaining a session key negotiated by the first device and the second device;

[0070] Information is transmitted between the first device and the second device based on the session key.

[0071] In a fourth aspect, the present invention provides a terminal device, comprising:

[0072] Memory;

[0073] Processor; the memory is suitable for storing multiple program codes, and the program codes are suitable for being loaded and run by the processor to execute the same-account device point-to-point identity authentication method described in any of the technical solutions of the same-account device point-to-point identity authentication method applied to the first device.

[0074] In a fifth aspect, the present invention provides a vehicle computer, comprising:

[0075] Memory;

[0076] Processor; the memory is suitable for storing multiple program codes, and the program codes are suitable for being loaded and run by the processor to execute the same-account device point-to-point identity authentication method described in any one of the technical solutions of the same-account device point-to-point identity authentication method applied to the second device.

[0077] In a sixth aspect, the present invention provides an information transmission system, comprising the terminal device described in the technical solution of the above terminal device and the vehicle computer described in the technical solution of the above vehicle computer;

[0078] The terminal device is provided with a first same-account device certificate, the vehicle computer is provided with a second same-account device certificate, and the terminal device and the vehicle computer are configured to perform same-account device point-to-point identity authentication based on the first same-account device certificate and the second same-account device certificate;

[0079] The first same-account device certificate includes account ID information and device ID information corresponding to the first device, and the second same-account device certificate includes account ID information and device ID information corresponding to the second device.

[0080] In a technical solution of the above information transmission system, it also includes a cloud;

[0081] The terminal device and the vehicle computer are respectively connected to the cloud for communication;

[0082] The cloud is configured to perform device authentication and account authentication on the terminal device, and issue a first device certificate with the same account to the terminal device based on the authentication result; and to perform device authentication on the vehicle computer, and issue a second device certificate with the same account to the vehicle computer based on the authentication result.

[0083] In the seventh aspect, the present invention provides a computer-readable storage medium storing a plurality of program codes, wherein the program codes are suitable for being loaded and run by a processor to execute the point-to-point authentication method for devices with the same account described in any one of the technical solutions of the above-mentioned point-to-point authentication method for devices with the same account, or the information transmission method described in the technical solution of the above-mentioned information transmission method.

[0084] Solution 1. A method for peer-to-peer identity authentication of devices with the same account number, applied to a first device, characterized in that the method comprises the following steps:

[0085] The first device receives second device same-account authentication information sent by the second device, where the second device same-account authentication information at least includes a second same-account device certificate, and the second same-account device certificate includes account ID information and device ID information corresponding to the second device;

[0086] The first device determines, based on the same account authentication information of the second device, whether the first device and the second device are devices with the same account;

[0087] If the first device and the second device are devices with the same account, the first device sends the first device same-account authentication information to the second device, so that the second device determines whether the first device and the second device are devices with the same account based on the first device same-account authentication information.

[0088] Solution 2. The peer-to-peer identity authentication method for devices with the same account as claimed in claim 1, characterized in that the method further comprises the first device obtaining a first device certificate with the same account at least based on the following steps:

[0089] The first device initiates a device authentication request to the third device, or initiates an account authentication request and a device authentication request;

[0090] The first device receives a first same-account device certificate issued by a third device, where the first same-account device certificate is issued by the third device in response to a device authentication request being passed, or an account authentication request and a device authentication request being passed.

[0091] Solution 3. The peer-to-peer identity authentication method for devices with the same account as claimed in claim 2, wherein the first device initiates an account authentication request to the third device, comprising:

[0092] The first device logs in to the account and initiates an account authentication request to the third device;

[0093] In response to the account authentication request being approved, the first device obtains the account login credentials from the third device.

[0094] Solution 4. The peer-to-peer identity authentication method for devices with the same account as claimed in claim 3, characterized in that the first device is pre-installed with a first device certificate and a first device public-private key pair;

[0095] The first device initiates a device authentication request to the third device, including:

[0096] The first device signs the account login credential based on the preset first device private key, and sends the first device certificate, the signature result, and the first device public key to the third device, so that the third device verifies the validity of the first device certificate, the signature result, and the account login credential respectively, and then issues the first same-account device certificate to the first device;

[0097] Or, the first device initiates a device authentication request to the third device, including:

[0098] The first device signs the first device certificate based on the preset first device private key, and sends the first device certificate, the signature result and the first device public key to the third device, so that the third device verifies the validity of the first device certificate and the signature result respectively, and then issues the first same-account device certificate to the first device.

[0099] Solution 5. According to claim 4, the peer-to-peer identity authentication method for devices with the same account, wherein the first device is a device shared by multiple accounts, and the method further comprises:

[0100] Acquiring current user information of the first device based on the image acquisition device;

[0101] Determine an account number of a current user of the first device based on the current user information;

[0102] The first device initiates a device authentication request to the third device, further comprising:

[0103] If the first device is currently bound to another account that is different from the account of the current user, the first device receives revocation information issued by the third device for revoking the certificate corresponding to the other account, and receives the first same-account device certificate issued by the third device, where the first same-account device certificate includes the account ID information and device ID information of the current user of the first device.

[0104] Solution 6. The peer-to-peer identity authentication method for devices with the same account as claimed in claim 1, wherein the first device determines whether the first device and the second device are devices with the same account according to the same account authentication information of the second device, comprising:

[0105] The first device compares the account ID information of the first same-account device certificate and the second same-account device certificate;

[0106] Determine whether they belong to the same account device based on the comparison result.

[0107] Solution 7. The peer-to-peer identity authentication method for devices with the same account as claimed in claim 6, wherein the second device same-account authentication information further includes a public key in a second random key pair and a second digital signature, and the method further includes:

[0108] The first device generates a first random key pair, and sends a public key in the first random key pair to the second device;

[0109] The first device receives a public key in a second random key pair and a second digital signature sent by the second device, wherein the second digital signature is a signature of the public key in the first random key pair and the public key in the second random key sent by the first device based on the private key in the second random key.

[0110] Judging whether the devices belong to the same account based on the comparison results includes:

[0111] If the account ID information of the first same-account device certificate and the second same-account device certificate is the same, the first device verifies the second digital signature, and after the verification is passed, it is confirmed that the first device and the second device belong to the same-account devices.

[0112] Solution 8. The peer-to-peer identity authentication method for devices with the same account according to claim 1, characterized in that the first device is pre-installed with a first device certificate key pair with the same account; the first device sends the first device same-account authentication information to the second device, comprising:

[0113] The first device uses the private key in the first same-account device certificate key pair to sign the public key in the second random key pair sent by the second device and the public key in the first random key pair to generate a first digital signature;

[0114] The first device generates hash data based on the first digital signature and the second digital signature;

[0115] The first device sends the first digital signature, hash data and the first same-account device certificate to the second device, so that the second device determines whether the first device and the second device are same-account devices based on the first digital signature, hash data and the first same-account device certificate.

[0116] Solution 9. A method for peer-to-peer identity authentication of devices with the same account number, applied to a second device, characterized in that the method comprises the following steps:

[0117] The second device sends second device same-account authentication information to the first device, where the second device same-account authentication information at least includes a second same-account device certificate, where the second same-account device certificate includes account ID information and device ID information corresponding to the second device;

[0118] After the first device determines that the first device and the second device are devices with the same account, the second device receives the first device same account authentication information sent by the first device;

[0119] The second device determines whether the first device and the second device are devices with the same account based on the same account authentication information of the first device.

[0120] Solution 10. The peer-to-peer identity authentication method for devices with the same account as claimed in claim 9, characterized in that the method further comprises the second device obtaining a second device certificate with the same account based on at least the following steps:

[0121] The second device initiates a device authentication request to the third device, or initiates an account authentication request and a device authentication request;

[0122] The second device receives a second same-account device certificate issued by the third device, where the second same-account device certificate is issued by the third device in response to a device authentication request being passed, or an account authentication request and a device authentication request being passed.

[0123] Solution 11. The peer-to-peer identity authentication method for devices with the same account as claimed in claim 10, wherein the second device initiates an account authentication request to the third device, comprising:

[0124] The second device logs in to the account and initiates an account authentication request to the third device;

[0125] In response to the account authentication request being approved, the second device obtains the account login credentials from the third device.

[0126] Solution 12. The peer-to-peer identity authentication method for devices with the same account as claimed in claim 11, wherein the second device is pre-installed with a second device certificate and a second device public-private key pair.

[0127] The second device initiates a device authentication request to the third device, including:

[0128] The second device signs the account login credential based on the preset second device private key, and sends the second device certificate, the signature result, and the second device public key to the third device, so that the third device verifies the validity of the second device certificate, the signature result, and the account login credential respectively, and then issues the second same-account device certificate to the second device;

[0129] Or, the second device initiates a device authentication request to the third device, including:

[0130] The second device signs the second device certificate based on the preset second device private key, and sends the first device certificate, signature result and second device public key to the third device, so that the third device verifies the validity of the second device certificate and signature result respectively, and then issues the second same-account device certificate to the second device.

[0131] Solution 13. The peer-to-peer identity authentication method for devices with the same account as claimed in claim 12, wherein the second device is a device shared by multiple accounts, and the method further comprises:

[0132] Acquiring current user information of the second device based on the image acquisition device;

[0133] Determine the account of the current user of the second device based on the current user information;

[0134] The second device initiates a device authentication request to the third device, further comprising:

[0135] If the second device is currently bound to another account that is different from the account of the current user, the second device receives the revocation information issued by the third device for revoking the certificate corresponding to the other account, and receives the second same-account device certificate issued by the third device, where the second same-account device certificate includes the account ID information and device ID information of the current user of the second device.

[0136] Solution 14. The peer-to-peer identity authentication method for devices with the same account as claimed in claim 9, wherein the first device authentication information for the same account further includes a public key in a first random key pair, and the second device is pre-installed with a second device certificate key pair for the same account, and the method further includes:

[0137] The second device receives the public key in the first random key pair sent by the first device;

[0138] The second device generates a second random key pair, uses the private key in the second same-account device certificate key pair to sign the received public key in the first random key pair and the public key in the second random key pair, generates a second digital signature, and sends it to the first device;

[0139] After the first device verifies the second digital signature, the second device receives the first digital signature, hash data, and the first same-account device certificate sent by the first device;

[0140] Judging whether the devices belong to the same account based on the comparison results includes:

[0141] If the account ID information of the first same-account device certificate and the second same-account device certificate is the same, the first device verifies the first digital signature and the hash data. After the verification is successful, it is confirmed that the first device and the second device belong to the same-account devices.

[0142] Solution 15. An information transmission method, applied to an information transmission system, the system comprising a first device and a second device, characterized in that:

[0143] The first device performs peer-to-peer identity authentication of the second device with the same account based on any one of claims 1 to 8;

[0144] The second device performs peer-to-peer identity authentication of the first device with the same account based on any one of claims 9 to 14;

[0145] After the first device and the second device are both authenticated, obtaining a session key negotiated by the first device and the second device;

[0146] Information is transmitted between the first device and the second device based on the session key.

[0147] Solution 16. A terminal device, comprising:

[0148] Memory;

[0149] Processor; the memory is suitable for storing multiple program codes, characterized in that the program codes are suitable for being loaded and run by the processor to execute a point-to-point identity authentication method for devices with the same account as described in any one of claims 1-8.

[0150] Solution 17: A vehicle computer, characterized by comprising:

[0151] Memory;

[0152] Processor; the memory is suitable for storing multiple program codes, characterized in that the program codes are suitable for being loaded and run by the processor to execute a point-to-point identity authentication method for devices with the same account as described in any one of claims 9-14.

[0153] Solution 18: An information transmission system, comprising: the terminal device according to claim 16, the vehicle computer according to claim 17;

[0154] The terminal device is provided with a first same-account device certificate, the vehicle computer is provided with a second same-account device certificate, and the terminal device and the vehicle computer are configured to perform same-account device point-to-point identity authentication based on the first same-account device certificate and the second same-account device certificate;

[0155] The first same-account device certificate includes account ID information and device ID information corresponding to the first device, and the second same-account device certificate includes account ID information and device ID information corresponding to the second device.

[0156] Solution 19. The information transmission system according to claim 18, further comprising a cloud;

[0157] The terminal device and the vehicle computer are respectively connected to the cloud for communication;

[0158] The cloud is configured to perform device authentication and account authentication on the terminal device, and issue a first device certificate with the same account to the terminal device based on the authentication result; and to perform device authentication on the vehicle computer, and issue a second device certificate with the same account to the vehicle computer based on the authentication result.

[0159] Solution 20. A computer-readable storage medium storing a plurality of program codes, characterized in that the program codes are suitable for being loaded and run by a processor to execute the point-to-point identity authentication method for devices with the same account as described in any one of claims 1 to 12, or the information transmission method described in claim 15.

[0160] The above one or more technical solutions of the present invention have at least one or more of the following beneficial effects:

[0161] In the technical solution for implementing the present invention, it is applied to the first device, the first device receives the second device same-account authentication information sent by the second device, the second device same-account authentication information at least includes the second same-account device certificate, and the second same-account device certificate includes the account ID information and device ID information corresponding to the second device; the first device determines whether the first device and the second device belong to the same-account device according to the second device same-account authentication information; if the first device and the second device belong to the same-account device, the first device sends the first device same-account authentication information to the second device, so that the second device determines whether the first device and the second device belong to the same-account device based on the first device same-account authentication information. Therefore, through the mutual authentication between the first device and the second device, data synchronization between different devices under the same account is realized, and the authentication process can be performed when the first device and the second device are not connected to the Internet, that is, the authentication process of the first device and the second device does not depend on the network. In addition, the authentication process does not require user participation, which improves the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0162] The disclosure of the present invention will become more easily understood with reference to the accompanying drawings. It will be readily understood by those skilled in the art that these drawings are only for illustrative purposes and are not intended to limit the scope of protection of the present invention. In addition, similar numbers in the drawings represent similar components, wherein:

[0163] Figure 1 It is a schematic flow chart of a method for synchronizing data between devices with the same account in the prior art;

[0164] Figure 2 1. is a flowchart of the main steps of the peer-to-peer identity authentication method for devices with the same account number applied to a first device according to the present invention;

[0165] Figure 3 It is a schematic flow chart of the point-to-point identity authentication method for devices with the same account provided by the present invention;

[0166] Figure 4 It is a schematic diagram of detailed steps of the first device of the present invention obtaining the first same-account device certificate from the third device;

[0167] Figure 5 It is a schematic flow chart of the present invention for obtaining a device certificate for the same account based on account ID information and device ID information;

[0168] Figure 6 is a flow chart of an authentication process between a first device and a second device of the present invention;

[0169] Figure 7 It is a flowchart of the main steps of the peer-to-peer identity authentication method for devices with the same account number applied to a second device of the present invention;

[0170] Figure 8 It is a flow chart of the main steps of the information transmission method of the present invention applied to the information transmission system;

[0171] Fig. 9 is a flowchart of the steps of a method for peer-to-peer identity authentication of devices with the same account in one embodiment of the present invention;

[0172] Fig.10 It is a main structural block diagram of a terminal device for executing the same-account device point-to-point identity authentication method of the present invention;

[0173] Fig.11 It is a main structural block diagram of a vehicle computer for executing the same-account device point-to-point identity authentication method of the present invention;

[0174] Fig.12 It is a main structural block diagram of an information transmission system for executing the information transmission method of the present invention. DETAILED DESCRIPTION

[0175] Some embodiments of the present invention are described below with reference to the accompanying drawings. It should be understood by those skilled in the art that these embodiments are only used to explain the technical principles of the present invention and are not intended to limit the protection scope of the present invention.

[0176] In the description of the present invention, "module" and "processor" may include hardware, software or a combination of the two. A module may include hardware circuits, various suitable sensors, communication ports, and memories, and may also include software parts, such as program codes, or a combination of software and hardware. The processor may be a central processing unit, a microprocessor, an image processor, a digital signal processor, or any other suitable processor. The processor has data and / or signal processing functions. The processor may be implemented in software, hardware, or a combination of the two. Non-temporary computer-readable storage media include any suitable medium that can store program codes, such as a magnetic disk, a hard disk, an optical disk, a flash memory, a read-only memory, a random access memory, and the like. The term "A and / or B" means all possible combinations of A and B, such as only A, only B, or A and B. The term "at least one A or B" or "at least one of A and B" has a similar meaning to "A and / or B", and may include only A, only B, or A and B. The singular terms "one" and "the" may also include plural forms.

[0177] The present invention provides a point-to-point identity authentication method for devices with the same account, which is applied to a first device.

[0178] Please see attached Figure 2 and Figure 3 , Figure 2is a flowchart of the main steps of the peer-to-peer identity authentication method for devices with the same account number applied to a first device of the present invention, Figure 3 is a schematic flow chart of a peer-to-peer identity authentication method for devices with the same account number according to the present invention, wherein: Figure 3 Device 1, device 2 and device 3 are the first device or the second device in the present invention.

[0179] like Figure 2 As shown, the peer-to-peer identity authentication method for devices with the same account in the embodiment of the present invention mainly includes the following steps S201-S203.

[0180] Step S201, the first device receives second device same-account authentication information sent by the second device, the second device same-account authentication information at least includes a second same-account device certificate, and the second same-account device certificate includes account ID information and device ID information corresponding to the second device.

[0181] Step S202: The first device determines whether the first device and the second device are devices with the same account based on the same account authentication information of the second device.

[0182] Step S203: If the first device and the second device are devices with the same account, the first device sends the first device same-account authentication information to the second device, so that the second device determines whether the first device and the second device are devices with the same account based on the first device same-account authentication information.

[0183] In the present invention, data synchronization between different devices under the same account is achieved through mutual authentication between the first device and the second device, and the authentication process of the first device and the second device can be performed without being connected to the Internet, that is, the authentication process of the first device and the second device does not depend on the network. In addition, the authentication process does not require user participation, thereby improving the user experience.

[0184] In one embodiment, the method further includes the first device obtaining the first same-account device certificate based on at least the following steps:

[0185] The first device initiates a device authentication request to the third device, or initiates an account authentication request and a device authentication request;

[0186] The first device receives a first same-account device certificate issued by a third device, where the first same-account device certificate is issued by the third device in response to a device authentication request being passed, or an account authentication request and a device authentication request being passed.

[0187] Furthermore, the first device initiates an account authentication request to the third device, including:

[0188] The first device logs in to the account and initiates an account authentication request to the third device;

[0189] In response to the account authentication request being approved, the first device obtains the account login credentials from the third device.

[0190] Furthermore, the first device is pre-installed with a first device certificate and a first device public-private key pair; the first device initiates a device authentication request to the third device, including:

[0191] The first device signs the account login credential based on the preset first device private key, and sends the first device certificate, the signature result, and the first device public key to the third device, so that the third device verifies the validity of the first device certificate, the signature result, and the account login credential respectively, and then issues the first same-account device certificate to the first device;

[0192] Or, the first device initiates a device authentication request to the third device, including:

[0193] The first device signs the first device certificate based on the preset first device private key, and sends the first device certificate, the signature result and the first device public key to the third device, so that the third device verifies the validity of the first device certificate and the signature result respectively, and then issues the first same-account device certificate to the first device.

[0194] Please refer to the attached Figure 4 , Figure 4 It is a schematic diagram of detailed steps for the first device of the present invention to obtain the first same-account device certificate from the third device.

[0195] In the present invention, the first device may be a terminal device or a vehicle computer.

[0196] The following will explain through a specific embodiment how the first device obtains the first same-account device certificate from the third device.

[0197] Example 1: When the first device is a terminal device, the first device needs to initiate an account authentication request and a device authentication request to the third device. Specifically, Figure 4 As shown, the first device logs in to the account and initiates an account authentication request to the third device. After the account authentication request is passed, the first device obtains the account login credentials from the third device; the first device signs the obtained account login credentials based on the preset first device private key, and sends the first device certificate, signature result and first device public key to the third device. The third device verifies the validity of the first device certificate, signature result and account login credentials respectively, and after verification, sends the first device certificate with the same account to the first device.

[0198] Example 2: When the first device is a vehicle computer, since the vehicle computer is not a real-time connected device, the vehicle computer does not need to send an account authentication request to the third device, but only needs to send a device authentication request to the third device. Specifically, Figure 4 As shown, no need to execute Figure 4 In steps 1 to 4, the first device signs the first device certificate based on the preset first device private key, and sends the first device certificate, the signature result and the first device public key to the third device. The third device verifies the validity of the first device certificate and the signature result respectively, and after verification, sends the first same-account device certificate to the first device.

[0199] Please see attached Figure 5 , Figure 5 It is a schematic flow chart of the present invention for obtaining a device certificate for the same account based on account ID information and device ID information.

[0200] Specifically, when the first device obtains the first same-account device certificate from the third device, the first device same-account authentication information sent by the first device to the third device includes the account ID information and device ID information corresponding to the first device, so that the third device issues the first same-account device certificate to the first device, wherein the first same-account device certificate includes the account ID information and device ID information corresponding to the first device.

[0201] In one embodiment, step S202 specifically includes:

[0202] The first device compares the account ID information of the first same-account device certificate and the second same-account device certificate;

[0203] Determine whether they belong to the same account device based on the comparison result.

[0204] In one embodiment, the second device and account authentication information further includes a public key in a second random key pair and a second digital signature, and the method further includes:

[0205] The first device generates a first random key pair, and sends a public key in the first random key pair to the second device;

[0206] The first device receives a public key in a second random key pair and a second digital signature sent by the second device, wherein the second digital signature is a signature of the public key in the first random key pair and the public key in the second random key sent by the first device based on the private key in the second random key.

[0207] Judging whether the devices belong to the same account based on the comparison results includes:

[0208] If the account ID information of the first same-account device certificate and the second same-account device certificate is the same, the first device verifies the second digital signature, and after the verification is passed, it is confirmed that the first device and the second device belong to the same-account devices.

[0209] In one embodiment, the first device is pre-installed with a first same-account device certificate key pair; the first device sends the first device same-account authentication information to the second device, including:

[0210] The first device uses the private key in the first same-account device certificate key pair to sign the public key in the second random key pair sent by the second device and the public key in the first random key pair to generate a first digital signature;

[0211] The first device generates hash data based on the first digital signature and the second digital signature;

[0212] The first device sends the first digital signature, hash data and the first same-account device certificate to the second device, so that the second device determines whether the first device and the second device are same-account devices based on the first digital signature, hash data and the first same-account device certificate.

[0213] Please see attached Figure 6 , Figure 6 is a flow chart of an authentication process between a first device and a second device of the present invention.

[0214] The following description is given by taking the first device as a terminal device and the second device as a vehicle computer as an example.

[0215] The first device randomly generates a first random key pair (A_Tpk, A_Tsk), the first device has obtained a first same-account device certificate (A_TCcert), and the first device is pre-set with a first same-account device certificate key pair (A_TCsk, A_TCpk);

[0216] The second device randomly generates a second random key pair (B_Tpk, B_Tsk), the second device has obtained a second same-account device certificate (B_TCcert), and the second device is pre-set with a second same-account device certificate key pair (B_TCsk, B_TCpk);

[0217] Specifically, the first device generates a first random key pair, and sends a public key in the first random key pair to the second device;

[0218] The second device receives the public key in the first random key pair sent by the first device, generates a second random key pair, and uses the private key in the second same-account device certificate key pair to sign the received public key in the first random key pair and the public key in the second random key to generate a second digital signature, and the second device sends the second digital signature, the public key in the second random key, and the second same-account device certificate to the first device;

[0219] The first device compares the received second same-account device certificate with the first same-account device certificate. If the two are inconsistent, the authentication process ends; if the two are consistent, the first device uses the private key in the first same-account device certificate key pair to sign the public key in the second random key pair sent by the second device and the public key in the first random key to generate a first digital signature. The first device generates hash data based on the first digital signature and the second digital signature, and the first device sends the first digital signature, the hash data and the first same-account device certificate to the second device;

[0220] The second device compares the received first device certificate with the second device certificate. If the two are inconsistent, the authentication process ends. If the two are consistent, the first device verifies the first digital signature and hash data. After the verification is successful, it is confirmed that the first device and the second device are devices with the same account.

[0221] After the first device and the second device are both authenticated, a session key negotiated by the first device and the second device is obtained, and information is transmitted between the first device and the second device based on the session key.

[0222] In one embodiment, the first device is a device shared by multiple accounts, and the method further includes:

[0223] Acquiring current user information of the first device based on the image acquisition device;

[0224] Determine an account number of a current user of the first device based on the current user information;

[0225] The first device initiates a device authentication request to the third device, further comprising:

[0226] If the first device is currently bound to another account that is different from the account of the current user, the first device receives revocation information issued by the third device for revoking the certificate corresponding to the other account, and receives the first same-account device certificate issued by the third device, where the first same-account device certificate includes the account ID information and device ID information of the current user of the first device.

[0227] To illustrate, since the first device is a shared device, multiple user accounts may have been logged into the first device. In this case, the current user information of the first device can be obtained through the image acquisition device to determine the account of the current user of the first device.

[0228] Specifically, when the first device is currently bound to the account of the current user, the third device sends a first same-account device certificate including the account ID information and device ID information of the current user to the first device;

[0229] When the first device is currently bound to an account different from the current user's account, the third device sends revocation information for revoking the certificate corresponding to the other account, and sends the first same-account device certificate with the current user's account ID information and device ID information to the first device.

[0230] The present invention also provides a point-to-point identity authentication method for devices with the same account, which is applied to a second device.

[0231] See attached Figure 7 , Figure 7 It is a flow chart of the main steps of the point-to-point identity authentication method of the same account device applied to the second device of the present invention.

[0232] like Figure 7 As shown, the peer-to-peer identity authentication method for devices with the same account in the embodiment of the present invention mainly includes the following steps S701 to S703.

[0233] Step S701: The second device sends second device same-account authentication information to the first device, where the second device same-account authentication information at least includes a second same-account device certificate, and the second same-account device certificate includes account ID information and device ID information corresponding to the second device.

[0234] Step S702: After the first device determines that the first device and the second device are devices with the same account, the second device receives the first device same-account authentication information sent by the first device.

[0235] Step S703: The second device determines whether the first device and the second device are devices with the same account based on the same account authentication information of the first device.

[0236] In the present invention, data synchronization between different devices under the same account is achieved through mutual authentication between the first device and the second device, and the authentication process can be performed when the first device and the second device are not connected to the Internet, that is, the authentication process of the first device and the second device does not depend on the network. In addition, the authentication process does not require user participation, thereby improving the user experience.

[0237] In one embodiment, the method further includes the second device obtaining a second same-account device certificate based on at least the following steps:

[0238] The second device initiates a device authentication request to the third device, or initiates an account authentication request and a device authentication request;

[0239] The second device receives a second same-account device certificate issued by the third device, where the second same-account device certificate is issued by the third device in response to a device authentication request being passed, or an account authentication request and a device authentication request being passed.

[0240] Furthermore, the second device initiates an account authentication request to the third device, including:

[0241] The second device logs in to the account and initiates an account authentication request to the third device;

[0242] In response to the account authentication request being approved, the second device obtains the account login credentials from the third device.

[0243] Furthermore, the second device is pre-installed with a second device certificate and a second device public-private key pair.

[0244] The second device initiates a device authentication request to the third device, including:

[0245] The second device signs the account login credential based on the preset second device private key, and sends the second device certificate, the signature result, and the second device public key to the third device, so that the third device verifies the validity of the second device certificate, the signature result, and the account login credential respectively, and then issues the second same-account device certificate to the second device;

[0246] Or, the second device initiates a device authentication request to the third device, including:

[0247] The second device signs the second device certificate based on the preset second device private key, and sends the first device certificate, signature result and second device public key to the third device, so that the third device verifies the validity of the second device certificate and signature result respectively, and then issues the second same-account device certificate to the second device.

[0248] The second device in the present invention may be a terminal device or a vehicle computer.

[0249] It should be noted that the process for the second device to obtain the second same-account device certificate is the same as the process for the first device to obtain the first same-account device certificate. Please refer to the above content for details, and the repeated parts will not be repeated here.

[0250] In one embodiment, the second device is a device shared by multiple accounts, and the method further includes:

[0251] Acquiring current user information of the second device based on the image acquisition device;

[0252] Determine the account of the current user of the second device based on the current user information;

[0253] The second device initiates a device authentication request to the third device, further comprising:

[0254] If the second device is currently bound to another account that is different from the account of the current user, the second device receives the revocation information issued by the third device for revoking the certificate corresponding to the other account, and receives the second same-account device certificate issued by the third device, where the second same-account device certificate includes the account ID information and device ID information of the current user of the second device.

[0255] One thing to note is that since the second device is a shared device, multiple user accounts may have been logged into the second device. In this case, the current user information of the second device can be obtained through the image acquisition device to determine the account of the current user of the second device.

[0256] Specifically, when the second device is currently bound to the account of the current user, the third device sends a second same-account device certificate including the account ID information and device ID information of the current user to the second device;

[0257] When the second device is currently bound to an account different from the current user's account, the third device sends revocation information for revoking the certificate corresponding to the other account, and sends a second same-account device certificate with the current user's account ID information and device ID information to the second device.

[0258] In one embodiment, the first device same account authentication information also includes a public key in a first random key pair, and the second device is pre-set with a second same account device certificate key pair, and the method further includes:

[0259] The second device receives the public key in the first random key pair sent by the first device;

[0260] The second device generates a second random key pair, uses the private key in the second same-account device certificate key pair to sign the received public key in the first random key pair and the public key in the second random key pair, generates a second digital signature, and sends it to the first device;

[0261] After the first device verifies the second digital signature, the second device receives the first digital signature, hash data, and the first same-account device certificate sent by the first device;

[0262] Judging whether the devices belong to the same account based on the comparison results includes:

[0263] If the account ID information of the first same-account device certificate and the second same-account device certificate is the same, the first device verifies the first digital signature and the hash data. After the verification is successful, it is confirmed that the first device and the second device belong to the same-account devices.

[0264] See attached Figure 8 , Figure 8It is a flow chart of the main steps of the information transmission method of the present invention applied to the information transmission system.

[0265] like Figure 8 As shown, the present invention also provides an information transmission method, which is applied to an information transmission system, wherein the system includes a first device and a second device, and mainly includes the following steps S801 to S804:

[0266] Step S801: The first device performs same-account device point-to-point identity authentication on the second device based on the same-account device point-to-point identity authentication method described in any one of the technical solutions of the same-account device point-to-point identity authentication method applied to the first device;

[0267] Step S802, the second device performs same-account device point-to-point identity authentication on the first device based on the same-account device point-to-point identity authentication method described in any one of the technical solutions of the same-account device point-to-point identity authentication method applied to the second device;

[0268] Step S803, after the first device and the second device are both authenticated, obtaining a session key negotiated by the first device and the second device;

[0269] Step S804: Transmit information between the first device and the second device based on the session key.

[0270] In order to specifically illustrate the above-mentioned point-to-point identity authentication method for devices with the same account, the present invention provides an embodiment, please refer to the attached Fig. 9 .

[0271] Fig. 9 1 is a flowchart of the steps of a peer-to-peer identity authentication method for devices with the same account according to an embodiment of the present invention. Fig. 9 As shown, the peer-to-peer identity authentication method for devices with the same account according to this embodiment includes the following steps:

[0272] The following description is given by taking the first device as a terminal device and the second device as a vehicle computer device as an example.

[0273] S901, the first device initiates an account authentication request and a device authentication request to the third device;

[0274] S902: In response to the account authentication request and the device authentication request being passed, the third device issues a first device certificate with the same account to the first device;

[0275] S903: The second device initiates a device authentication request to the third device;

[0276] S904: In response to the device authentication request being approved, the third device issues a second device certificate with the same account number to the second device;

[0277] S905, the first device receives the first same-account device certificate sent by the second device, and determines whether the first device and the second device are same-account devices; if so, execute step S906; if not, the process ends;

[0278] S906, the second device receives the second same-account device certificate sent by the first device, and determines whether the first device and the second device are same-account devices; if so, execute step S907; if not, the process ends;

[0279] S907: Acquire a session key negotiated between the first device and the second device, and transmit information between the first device and the second device based on the session key.

[0280] Among them, the specific method for the first device to obtain the first same-account device certificate, the specific method for the second device to obtain the second same-account device certificate, and the specific method for determining whether the first device and the second device are same-account devices can be referred to as described above, and the repeated parts will not be repeated here.

[0281] It should be pointed out that although the various steps in the above embodiments are described in a specific order, those skilled in the art can understand that in order to achieve the effects of the present invention, different steps do not have to be performed in such an order. They can be performed simultaneously (in parallel) or in other orders. These changes are within the scope of protection of the present invention.

[0282] All the above optional technical solutions can be arbitrarily combined to form optional embodiments of the present application, which will not be described one by one here.

[0283] See attached Fig.10 , Fig.10 It is a main structural block diagram of a terminal device used to execute the same-account device point-to-point identity authentication method of the present invention.

[0284] Furthermore, the present invention also provides a terminal device, the terminal device 1004 includes:

[0285] Processor 1001 and memory 1002, memory 1002 can be configured to store program code 1003 for executing the point-to-point identity authentication method for devices with the same account in the above method embodiment, processor 1001 can be configured to execute program code 1003 in memory 1002, and program code 1003 includes but is not limited to program code 1003 for executing the point-to-point identity authentication method for devices with the same account in the above method embodiment.

[0286] See attached Fig.11 , Fig.11 It is a main structural block diagram of a vehicle computer used to execute the same-account device point-to-point identity authentication method of the present invention.

[0287] Furthermore, the present invention also provides a vehicle computer, the vehicle computer 1104 includes

[0288] Processor 1101 and memory 1102, memory 1102 can be configured to store program code 1103 for executing the point-to-point identity authentication method for devices with the same account in the above method embodiment, processor 1101 can be configured to execute program code 1103 in memory 1102, and program code 1103 includes but is not limited to program code 1103 for executing the point-to-point identity authentication method for devices with the same account in the above method embodiment.

[0289] See attached Fig.12 , Fig.12 It is a main structural block diagram of an information transmission system for executing the information transmission method of the present invention.

[0290] Furthermore, the present invention also provides an information transmission system, the information transmission system 1201 comprises: a terminal device 1003, a vehicle computer 1104;

[0291] The terminal device is provided with a first same-account device certificate, the vehicle computer is provided with a second same-account device certificate, and the terminal device and the vehicle computer are configured to perform same-account device point-to-point identity authentication based on the first same-account device certificate and the second same-account device certificate;

[0292] The first same-account device certificate includes account ID information and device ID information corresponding to the first device, and the second same-account device certificate includes account ID information and device ID information corresponding to the second device.

[0293] In one embodiment, a cloud 1202 is also included;

[0294] The terminal device and the vehicle computer are respectively connected to the cloud for communication;

[0295] The cloud is configured to perform device authentication and account authentication on the terminal device, and issue a first device certificate with the same account to the terminal device based on the authentication result; and to perform device authentication on the vehicle computer, and issue a second device certificate with the same account to the vehicle computer based on the authentication result.

[0296] For ease of explanation, only the parts related to the embodiments of the present invention are shown. For specific technical details not disclosed, please refer to the method part of the embodiments of the present invention.

[0297] Exemplarily, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0298] The memory can be an internal storage unit of an electronic device, for example, a hard disk or memory of the electronic device; the memory can also be an external storage device of the electronic device, for example, a plug-in hard disk, a smart memory card (SmartMediaCard, SMC), a secure digital (SecureDigital, SD) card, a flash card (FlashCard), etc. equipped on the electronic device. Furthermore, the memory can also include both the internal storage unit of the electronic device and the external storage device. The memory is used to store computer programs and other programs and data required by the electronic device. The memory can also be used to temporarily store data that has been output or is to be output.

[0299] In some possible implementations, the electronic device may include multiple processors and memories. The program code for executing the point-to-point authentication method for devices with the same account number in the above method embodiment can be divided into multiple subprograms, and each subprogram can be loaded and run by the processor to execute different steps of the point-to-point authentication method for devices with the same account number in the above method embodiment. Specifically, each subprogram can be stored in different memories, and each processor can be configured to execute programs in one or more memories to jointly implement the point-to-point authentication method for devices with the same account number in the above method embodiment, that is, each processor executes different steps of the point-to-point authentication method for devices with the same account number in the above method embodiment to jointly implement the point-to-point authentication method for devices with the same account number in the above method embodiment.

[0300] The above-mentioned multiple processors may be processors deployed on the same device. For example, the above-mentioned electronic device may be a high-performance device composed of multiple processors, and the above-mentioned multiple processors may be processors configured on the high-performance device. In addition, the above-mentioned multiple processors may also be processors deployed on different devices. For example, the above-mentioned electronic device may be a server cluster, and the above-mentioned multiple processors may be processors on different servers in the server cluster.

[0301] The electronic device may be a desktop computer, a notebook, a PDA, a cloud server, or other electronic device, such as the smart cockpit and the cloud payment center in the above embodiment. The electronic device may include but is not limited to a processor and a memory. Those skilled in the art will understand that Figure 10 to Figure 11 These are merely examples of electronic devices and do not constitute a limitation of the electronic device. The electronic device may include more or fewer components than those shown in the figure, or a combination of certain components, or different components. For example, the electronic device may also include input and output devices, network access devices, buses, etc.

[0302] Furthermore, the present invention also provides a computer-readable storage medium. In a computer-readable storage medium embodiment according to the present invention, the computer-readable storage medium can be configured to store a program for executing the same-account device point-to-point identity authentication method of the above-mentioned method embodiment, and the program can be loaded and run by the processor to implement the above-mentioned same-account device point-to-point identity authentication method. For ease of explanation, only the parts related to the embodiment of the present invention are shown. For specific technical details not disclosed, please refer to the method part of the embodiment of the present invention. The computer-readable storage medium can be a storage device formed by various electronic devices. Optionally, the computer-readable storage medium in the embodiment of the present invention is a non-temporary computer-readable storage medium.

[0303] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0304] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments of the present invention can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0305] In the embodiments provided by the present invention, it should be understood that the disclosed electronic devices and methods can be implemented in other ways. For example, the electronic device embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices or units, which may be electrical, mechanical or other forms.

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

[0307] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0308] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. The computer program may include computer program code, and the computer program code may be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, the computer-readable medium does not include electric carrier signals and telecommunication signals.

[0309] So far, the technical solutions of the present invention have been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it is easy for those skilled in the art to understand that the protection scope of the present invention is obviously not limited to these specific embodiments. Without departing from the principle of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will fall within the protection scope of the present invention.

Claims

1. A peer-to-peer identity authentication method for devices with the same account, applied to a first device, characterized in that: The method comprises the following steps: The first device receives second device same-account authentication information sent by the second device, where the second device same-account authentication information at least includes a second same-account device certificate, and the second same-account device certificate includes account ID information and device ID information corresponding to the second device; The first device determines, based on the same account authentication information of the second device, whether the first device and the second device belong to the same account device; If the first device and the second device are devices with the same account, the first device sends the first device same-account authentication information to the second device, so that the second device determines whether the first device and the second device are devices with the same account based on the first device same-account authentication information.

2. The peer-to-peer identity authentication method for devices with the same account number according to claim 1, characterized in that: The method also includes the first device obtaining a first same-account device certificate based on at least the following steps: The first device initiates a device authentication request to the third device, or initiates an account authentication request and a device authentication request; The first device receives a first same-account device certificate issued by a third device, where the first same-account device certificate is issued by the third device in response to a device authentication request being passed, or an account authentication request and a device authentication request being passed.

3. The peer-to-peer identity authentication method for devices with the same account number according to claim 2, characterized in that: The first device initiates an account authentication request to the third device, including: The first device logs in to the account and initiates an account authentication request to the third device; In response to the account authentication request being approved, the first device obtains the account login credentials from the third device.

4. The peer-to-peer identity authentication method for devices with the same account number according to claim 3, characterized in that: The first device is pre-installed with a first device certificate and a first device public-private key pair; The first device initiates a device authentication request to the third device, including: The first device signs the account login credential based on the preset first device private key, and sends the first device certificate, the signature result, and the first device public key to the third device, so that the third device verifies the validity of the first device certificate, the signature result, and the account login credential respectively, and then issues the first same-account device certificate to the first device; Or, the first device initiates a device authentication request to the third device, including: The first device signs the first device certificate based on the preset first device private key, and sends the first device certificate, the signature result and the first device public key to the third device, so that the third device verifies the validity of the first device certificate and the signature result respectively, and then issues the first same-account device certificate to the first device.

5. The peer-to-peer identity authentication method for devices with the same account according to claim 4, wherein the first device is a device shared by multiple accounts, and the method further comprises: Acquiring current user information of the first device based on the image acquisition device; Determine an account number of a current user of the first device based on the current user information; The first device initiates a device authentication request to the third device, further comprising: If the first device is currently bound to another account that is different from the account of the current user, the first device receives revocation information issued by the third device for revoking the certificate corresponding to the other account, and receives the first same-account device certificate issued by the third device, where the first same-account device certificate includes the account ID information and device ID information of the current user of the first device.

6. The peer-to-peer identity authentication method for devices with the same account number according to claim 1, characterized in that: The first device determines, based on the same account authentication information of the second device, whether the first device and the second device are devices with the same account, including: The first device compares the account ID information of the first same-account device certificate and the second same-account device certificate; Determine whether they belong to the same account device based on the comparison result.

7. The peer-to-peer identity authentication method for devices with the same account number according to claim 6, characterized in that: The second device and account authentication information also includes a public key in a second random key pair and a second digital signature, and the method further includes: The first device generates a first random key pair, and sends a public key in the first random key pair to the second device; The first device receives a public key in a second random key pair and a second digital signature sent by the second device, wherein the second digital signature is a signature of the public key in the first random key pair and the public key in the second random key sent by the first device based on the private key in the second random key. Judging whether the devices belong to the same account based on the comparison results includes: If the account ID information of the first same-account device certificate and the second same-account device certificate is the same, the first device verifies the second digital signature, and after the verification is passed, it is confirmed that the first device and the second device belong to the same-account devices.

8. The peer-to-peer identity authentication method for devices with the same account number according to claim 1, characterized in that: The first device is pre-installed with a first device certificate key pair with the same account; The first device sends the first device same account authentication information to the second device, including: The first device uses the private key in the first same-account device certificate key pair to sign the public key in the second random key pair sent by the second device and the public key in the first random key pair to generate a first digital signature; The first device generates hash data based on the first digital signature and the second digital signature; The first device sends the first digital signature, hash data and the first same-account device certificate to the second device, so that the second device determines whether the first device and the second device are same-account devices based on the first digital signature, hash data and the first same-account device certificate.

9. A method for peer-to-peer identity authentication of devices with the same account number, applied to a second device, characterized in that: The method comprises the following steps: The second device sends second device same-account authentication information to the first device, where the second device same-account authentication information at least includes a second same-account device certificate, where the second same-account device certificate includes account ID information and device ID information corresponding to the second device; After the first device determines that the first device and the second device are devices with the same account, the second device receives the first device same account authentication information sent by the first device; The second device determines whether the first device and the second device are devices with the same account based on the same account authentication information of the first device.

10. The peer-to-peer identity authentication method for devices with the same account number according to claim 9, characterized in that: The method also includes the second device obtaining a second same-account device certificate based on at least the following steps: The second device initiates a device authentication request to the third device, or initiates an account authentication request and a device authentication request; The second device receives a second same-account device certificate issued by the third device, where the second same-account device certificate is issued by the third device in response to a device authentication request being passed, or an account authentication request and a device authentication request being passed.

Images